SlateDroid.com: Recovery Methods for a Bad FW Update (Cruz Reader) - SlateDroid.com

Jump to content


  • 2 Pages +
  • 1
  • 2
  • You cannot start a new topic
  • You cannot reply to this topic

Recovery Methods for a Bad FW Update (Cruz Reader) How to recover bad update

#1 User is offline   rushman 

  • Advanced Member
  • PipPipPip
  • Group: Jr. Member
  • Topics: 5
  • Posts: 32
  • Joined: 14-May 11

Posted 28 May 2011 - 02:55 PM

I wanted to start this this topic as there are several posts on this that cover the ground but they are all over the forum. It would be really nice to have a topic that that list the known ways the a FW Update can go bad. I wanted to call it "Cruz Reader, Faces of Death" but maybe that would be too morbid.

Anyway here is what I have found in level of severity.
UPDATE 6/3: A very short comment something I found about JTAG added at the bottom. For PDN but interesting. This is not the topic to discuss that, read the link and if you try it on your CRUZ Reader, post the results. If you cannot follow the thread on the link, PLEASE DO NOT post asking for help on this it is not something that is "explained" any better than that.

1.) Immediate Exclamation Andy
**SYMPTOM: You get to the update, and quickly go to the warning screen with an exclamation mark with Andy the Android.

**PROBLEM: Likely the ROM is bad or corrupt and nothing happened. This is usually a ZIP with the wrong name or wrong structure, or zipped inproperly. Did you make sure your SD card was not read only locked?

**SOLUTION: Unbend a paperclip and stick it in the reset hole to press the reset button and everything will be fine. Else goto #2

2.) Progress Bar for a while and then Exclamation Andy.
WARNING: NEVER RESET ON THE UPDATE SCREEN WITH THE PROGRESS BAR, WAIT TILL YOU SEE THE EXCLAMATIION MARK.
**SYMPTOM: You see progress bar goes for a while and then you get Exclamation Andy midway through the update.

**PROBLEM: Update process failed. There was some process, such as file permissions, that failed the update you have half an FW which is not good, but can usually be recovered.

**SOLUTION: Get a new good ROM in the SD and then do a "3 hand reset". Hold VolumeUp+Power and then have a second person insert the paperclip for you to reset (I suppose doable by yourself maybe but it certainly seem designed for someone with 3 hands). The important thing is to continue holding the buttons during reset to start an update from the new ROM as normal. Hopefully the new ROM should load otherwise you might have now have a "boot loop", or "white screen o' death"

3.) Boot Loop
** SYMPTOM: FW Update completes restarts but then boots to white screen, CRUZ logo, back to white screen, back to CRUZ logo, etc, etc, over and over.

** PROBLEM: Some bad pookie in the FW. Either your machine does not like a 800Mhz ROM (no one knows why) or "hacking" in the ROM you had did not take for various reasons, if you flashed several ROMs as some of them do only incremental changes and could have the system be placed into a bad state.

** SOLUTION: Same as #2 do a "3 hand reset" with a another good FW on the SD and hope it works. Also if you have ADB setup and you are able to get to your device you use the command "flash_image recovery /sdcard/recovery.img" or maybe "flash_image recovery /sdcard1/recovery.img" if you pull the recovery.img out (not sure of this) of the stock firmware and place directly in the SD. Otherwise goto #4.

4.) White Screen O' Death (WSOD)
** SYMPTOM: Your device has turned into a $100 flashlight. All you see is a white screen and nothing else happens.

** PROBLEM: VERY BAD pookie in the FW. Probably the same as #2 but worse symptoms.

** SOLUTION: From the consensus of the forum you are now in goat sacrificing territory maybe throw in a few virgins for good measure. Try ADB recovery above otherwise you basically you need to open the case unplug the battery and format the internal and external SD cards, then retry the firmware see post here. If that does not work, see post here. Note that I think the poster mixed up the URL and Text in his link for the ROM he used. Just cut and paste the URL in that post clicking did not work for me.

5.) Stuck on CRUZ Screen.
** Have not read a recovery on this or this might just be another description of the boot loop. If you just flashed wait a couple of minutes and just see if this is you FW update just needing to complete. Otherwise maybe try #4.

RECOVERY MODES SUMMARY:
A.) Reset - Just unbend a paper clip and push the into the reset hole to reset the device back to power on stage.
B.) SD Update - Hold Volume-up then press Power to power on launch and use an FW update ROM from the SD Card
C.) "3 Hand Reset" or Update Reset.- Hold Volume-up + Power and continue holding and press reset to reboot a device and go into update mode. Used when cannot be manually powered down (boot loop or white screen)
D.) Let out the Factory Air - Open the case unpluging the battery and reformatting the SD cards have been indicated as something that has help recovery.
E.) JTAG - Link here. *Might* be possible but this is for PDN (Reader should be very similiar) and requires a much higher level of techincal knowledge and even need make your own breakout board. You should not post here about this, try some of this info FIRST. If you get somewhere with the Reader then make your own topic about what you discovered, and post a solution if you find it. Don't ask someone how to do it, if you cant follow it here then no one is going to be able to explain it to you. Not saying this is even possible or that it is the same from the Reader. Serial access has been discovered in the Pandigital and this is noted to be same as the Cruz Reader. You should also note the memory offsets are likely different than this post as PDN is a 512 NAND and Cruz is a 256.

Thought it would be good to have these all together. If anyone else knows of others I will update. Hope it helps...

This post has been edited by rushman: 04 June 2011 - 10:26 AM

1

#2 User is offline   gjbnh 

  • Advanced Member
  • PipPipPip
  • Group: Jr. Member
  • Topics: 5
  • Posts: 211
  • Joined: 18-December 10

Posted 28 May 2011 - 03:06 PM

Good job. This should be made a sticky, and we should call it "DON"T PANIC", after the Hitchhiker's Guide to the Galaxy galactic guide LOL.

This post has been edited by mrsburnout: 28 May 2011 - 04:55 PM
Reason for edit: Entire 1st post quote not needed in 2nd post. :-)

0

#4 User is offline   mrsburnout 

  • Double Post Deleter
  • Group: Administrators
  • Topics: 81
  • Posts: 5,849
  • Joined: 13-August 10

Posted 28 May 2011 - 04:57 PM

View Postgjbnh, on 28 May 2011 - 03:06 PM, said:

Good job. This should be made a sticky, and we should call it "DON"T PANIC", after the Hitchhiker's Guide to the Galaxy galactic guide LOL.

Agreed. Stickied and nice job rushman. :good:

+1 Thank you.

"Dream as if you'll live forever. Live as if you'll die today." ~James Dean
"Slatedroid: Where all the advice is free, even advice you don't want." ~Mark Adams~
Posted Image
1

#5 User is offline   rushman 

  • Advanced Member
  • PipPipPip
  • Group: Jr. Member
  • Topics: 5
  • Posts: 32
  • Joined: 14-May 11

Posted 29 May 2011 - 08:14 AM

I have seen several posters reference "recovery mode". Is this just another name for the Vol-up+Power mode to start the upgrade process?

If not could someone who has tried it document "recovery mode" a bit so I can describe it up top? The "3 hand reset" has worked for me but it appears the there is a recovery.img which can be booted. It also appears that whatever default function VM built it might get messed up by the app2sd.sh partitions as this is on the internal SD card I believe.

This post has been edited by rushman: 29 May 2011 - 08:43 AM

0

#6 User is offline   Gors 

  • Newbie
  • Pip
  • Group: Jr. Member
  • Topics: 1
  • Posts: 3
  • Joined: 17-May 11

Posted 01 June 2011 - 08:56 AM

Good post, thank you.
0

#7 User is offline   fredworrell 

  • Newbie
  • Pip
  • Group: Jr. Member
  • Topics: 0
  • Posts: 1
  • Joined: 02-June 11

Posted 02 June 2011 - 12:19 PM

I've actually had the white screen of death several times. First, remove the back cover and unplug the battery. Second, you reformat your external sd card to fat32 and put a known to work copy of the firmware on it. Third, given some time has past, say like 10-15 minutes, insert your external sd card and then plug in the battery. Fourth, try the flash sequence again, power and volume up together. This will start the install process again. Has worked for me at least a handful of times.
0

#8 User is offline   SilverMane 

  • Member
  • PipPip
  • Group: Jr. Member
  • Topics: 1
  • Posts: 14
  • Joined: 27-May 11

Posted 06 June 2011 - 10:16 AM

I've had #3,4 and 5 so many times since getting my CR last month that its starting to be fun. NOT!

The following always worked for me. (restating above)

1. Pull battery to stop loop
2. Pull BOTH flash cards
3. Backup any data from flash cards (APKs, books)
4. Format BOTH cards to FAT32
5. Load VM Official ROM to external card
6. Insert flash cards
7. Connect battery
8. "3 Hand Reset" until your hands bleed!

I timed it once, took 2 mins. 13 seconds. Some times its less, some times its more, but this always worked.

I think the key is the battery pull and the formatting of the internal card.


I also noticed the "recovery.img" in the ROM file, but haven't had any experience with it.
R101 v2.0
Rooted
JGM 533Mhz v3.1 Rom
0

#9 User is offline   Strick 

  • Member
  • PipPip
  • Group: Jr. Member
  • Topics: 4
  • Posts: 13
  • Joined: 18-July 11

Posted 06 August 2011 - 08:05 PM

Not working... I have #4 and nothing in this thread has helped. Any ideas? Any ideas at all?
0

#10 User is offline   SilverMane 

  • Member
  • PipPip
  • Group: Jr. Member
  • Topics: 1
  • Posts: 14
  • Joined: 27-May 11

Posted 23 August 2011 - 04:08 PM

View PostStrick, on 06 August 2011 - 08:05 PM, said:

Not working... I have #4 and nothing in this thread has helped. Any ideas? Any ideas at all?


Go here, get the latest ROM...

http://cruzsupport.v...-R101-R102-R103

Then follow my steps above...

It should work.
R101 v2.0
Rooted
JGM 533Mhz v3.1 Rom
0

#11 User is offline   captnshacky 

  • Newbie
  • Pip
  • Group: Jr. Member
  • Topics: 0
  • Posts: 7
  • Joined: 27-October 11

Posted 27 October 2011 - 02:04 PM

Good news everyone!!!! I've solved one issue on my r102.
For those of you unable to boot into recovery mode, I was able to flash my recovery partition through adb.

step 1
a. download the stock firmware for your cruz
b. extract the recovery.img to the root of your c: drive

step 2
a. connect your reader through adb. even if you are stuck at a white screen or cruz logo or black screen sometimes you have adb access.
b. from cmd prompt paste the following without quotes "adb push c:/recovery.img /system/bin/recovery.img" i used this folder because it is not a read only and there for does not need root access. a return message should say something about number of bytes transferred overtime.
c. next type "adb shell" you should now see a # sign
d. next paste in "flash_image recovery /system/bin/recovery.img" if everything goes right you should not receive a return message.
e. type "reboot recovery"

And thats it. your device should boot into recovery mode again. if it does not hold down power and up vol and reset button for about 60 sec. let up on reset while still holding the other two. continue holding from about 5 - 10 secs and release and you should be in recovery.

thanks to everyone who contributed to this thread. it took all of your help for me to figure this out.
0

#12 User is offline   confusedandneedhelp 

  • Newbie
  • Pip
  • Group: Jr. Member
  • Topics: 0
  • Posts: 3
  • Joined: 28-November 11

Posted 28 November 2011 - 08:12 PM

I tried to use giga8547 method but the link is no longer working...
0

#13 User is offline   captnshacky 

  • Newbie
  • Pip
  • Group: Jr. Member
  • Topics: 0
  • Posts: 7
  • Joined: 27-October 11

Posted 29 November 2011 - 07:55 AM

View Postconfusedandneedhelp, on 28 November 2011 - 08:12 PM, said:

I tried to use giga8547 method but the link is no longer working...


what issue are you having?
0

#14 User is offline   sk8er4l515 

  • Newbie
  • Pip
  • Group: Jr. Member
  • Topics: 1
  • Posts: 6
  • Joined: 29-November 11

Posted 29 November 2011 - 08:55 PM

How do i use and set up adb? i have rooted my evo i have some know how...
0

#15 User is offline   captnshacky 

  • Newbie
  • Pip
  • Group: Jr. Member
  • Topics: 0
  • Posts: 7
  • Joined: 27-October 11

Posted 29 November 2011 - 10:45 PM

View Postsk8er4l515, on 29 November 2011 - 08:55 PM, said:

How do i use and set up adb? i have rooted my evo i have some know how...


search the forums at rootzwiki or xda developers. easiest. places to find out
0

#16 User is offline   Soothsayer_138 

  • Newbie
  • Pip
  • Group: Jr. Member
  • Topics: 1
  • Posts: 5
  • Joined: 04-December 11

Posted 05 December 2011 - 08:22 PM

This may be a stupid question, (droid n00b) but if I pull my stock 4 gig micro sd with my original firmware could I replace and flash another rom to a different micro sd and keep the first as back-up incase anything goes wrong with alternate Rom?
0

#17 User is offline   captnshacky 

  • Newbie
  • Pip
  • Group: Jr. Member
  • Topics: 0
  • Posts: 7
  • Joined: 27-October 11

Posted 05 December 2011 - 08:29 PM

the firmware is not on the SD. it is in the cruz's internal memory
0

#18 User is offline   droidfan386 

  • Newbie
  • Pip
  • Group: Jr. Member
  • Topics: 0
  • Posts: 2
  • Joined: 06-December 11

Posted 07 December 2011 - 09:56 PM

Tried it and it worked!

Thanks
0

#19 User is offline   Jayfronius 

  • Newbie
  • Pip
  • Group: Jr. Member
  • Topics: 0
  • Posts: 4
  • Joined: 20-December 11

Posted 20 December 2011 - 02:52 PM

....just another sad WSOD story

Cruz Reader R102
Flash my ROM with the Macho ROM, left it alone over lunch, came back to the WSOD. Tried to reflash to no avail. While I don't want to believe it, I really think it's Bricked... as in KAPUT! Thank for playing, game over.

I've combed through just about every post on this topic and/or WSOD. I have tried just about everything I've read with no success. Here are some of the things I've tried.

- hold down vol up and power button
- hold down vol up, power button and reset button
- format internal card to FAT 32
- format external card to FAT 32
- format external card to FAT 32 and download factory ROM from VC website
- Tried various vanilla ROMs
- Tried with AC plug in, and out
- USB in and out
- ancient tribal dances and prayers...

Again, with each effort, same result. White screen, no logo, no flicker, no andy or exclamation - just steady white either until the batteries dies or I pull the Charging Cord. If there is anyone who may offer any other solutions not previously mentioned.

Oh and just to add insult to injury, I've managed to pull out 2 of the leads out of the little plastic battery connector (this just happened) - so if anyone can offer any advice on that - that would be .... mmmm greeeat. (Yeah, it's been that kind of day)

I can still power up the reader with the Charging/AC plug but same result. White screen.

Return isn't an option - this was one of those 1saleaday.com specials... no returns. It was only $59 so I'm not ready to jump out of any buildings, but I can't believe I may have become a statistic! That sucks. I still have this little flicker of hope.

So I find myself feeling like I'm in one of those medical drama shows where the patient is on their last breath I'm the Doc pounding their chest trying to revive them saying "NOOOO! I know I can save em'!" Is it time to "call it?"

Thx in advance for your consideration.
0

#20 User is offline   captnshacky 

  • Newbie
  • Pip
  • Group: Jr. Member
  • Topics: 0
  • Posts: 7
  • Joined: 27-October 11

Posted 20 December 2011 - 03:23 PM

View PostJayfronius, on 20 December 2011 - 02:52 PM, said:

....just another sad WSOD story

Cruz Reader R102
Flash my ROM with the Macho ROM, left it alone over lunch, came back to the WSOD. Tried to reflash to no avail. While I don't want to believe it, I really think it's Bricked... as in KAPUT! Thank for playing, game over.

I've combed through just about every post on this topic and/or WSOD. I have tried just about everything I've read with no success. Here are some of the things I've tried.

- hold down vol up and power button
- hold down vol up, power button and reset button
- format internal card to FAT 32
- format external card to FAT 32
- format external card to FAT 32 and download factory ROM from VC website
- Tried various vanilla ROMs
- Tried with AC plug in, and out
- USB in and out
- ancient tribal dances and prayers...

Again, with each effort, same result. White screen, no logo, no flicker, no andy or exclamation - just steady white either until the batteries dies or I pull the Charging Cord. If there is anyone who may offer any other solutions not previously mentioned.

Oh and just to add insult to injury, I've managed to pull out 2 of the leads out of the little plastic battery connector (this just happened) - so if anyone can offer any advice on that - that would be .... mmmm greeeat. (Yeah, it's been that kind of day)

I can still power up the reader with the Charging/AC plug but same result. White screen.

Return isn't an option - this was one of those 1saleaday.com specials... no returns. It was only $59 so I'm not ready to jump out of any buildings, but I can't believe I may have become a statistic! That sucks. I still have this little flicker of hope.

So I find myself feeling like I'm in one of those medical drama shows where the patient is on their last breath I'm the Doc pounding their chest trying to revive them saying "NOOOO! I know I can save em'!" Is it time to "call it?"

Thx in advance for your consideration.

when your at the white screen can you access your device through adb?
0

#21 User is offline   walangley 

  • Member
  • PipPip
  • Group: Jr. Member
  • Topics: 1
  • Posts: 15
  • Joined: 24-August 10

Posted 20 December 2011 - 04:42 PM

I have had the same experience with a r101. I have tried the adb but the computer does not recognise the reader is even there so the adb does not work. There has to be some way of forcing a flash but so far I have not found one. I think the tablet is not reading the sd or the internal drive. I keep checking hoping someone will find the solution.
0

Share this topic:


  • 2 Pages +
  • 1
  • 2
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users