Related
Hey guys, not sure if this is in the right forum (so move over to dev forum if necessary) but does anyone know if there is a way to manually push the stock nook to update to version 1.1 software?
In the process of trying to update from rooted 1.0.1, I ended up bricking my nook and having to go back to stock. I downloaded the sideload_update.zip from the bn.com site and placed it in the root directory (per the instructions). I reset the device and waited for the update, and waited, and waited . . . nothing. Even overnight.
Is there a way to manually push the nook to read the sideload_update file? For right now, I'd like to just remain stock but I'd love to have the snappier response of 1.1 and the multi-touch browsing in the stock browser.
Agraceffa said:
Hey guys, not sure if this is in the right forum (so move over to dev forum if necessary) but does anyone know if there is a way to manually push the stock nook to update to version 1.1 software?
In the process of trying to update from rooted 1.0.1, I ended up bricking my nook and having to go back to stock. I downloaded the sideload_update.zip from the bn.com site and placed it in the root directory (per the instructions). I reset the device and waited for the update, and waited, and waited . . . nothing. Even overnight.
Is there a way to manually push the nook to read the sideload_update file? For right now, I'd like to just remain stock but I'd love to have the snappier response of 1.1 and the multi-touch browsing in the stock browser.
Click to expand...
Click to collapse
Do you mean this?
http://forum.xda-developers.com/showthread.php?t=932145
Edit: Sorry...Just saw you wanted to stay stock..
thanks. I may have to fall back on that if I can't get this worked out. Do you think its because the nook is sitting on v1.0.0 and not v1.0.1? If so, do you know where I would get v1.0.1 since its not on the bn.com website?
Agraceffa said:
thanks. I may have to fall back on that if I can't get this worked out. Do you think its because the nook is sitting on v1.0.0 and not v1.0.1? If so, do you know where I would get v1.0.1 since its not on the bn.com website?
Click to expand...
Click to collapse
You could do the prerooted rom on the Dev forum and flash it via clockwork recovery. That would work so you can stay rooted and get you to 1.0.1.
I just did the BN 1.0.1 update then re-Autonootered the device.
Actually, side loaded the v1.1 update this afternoon and it finally recognized it. Now I've just gotta wait for the new root method. Any suggestions?
Sent from my T-Mobile G2 using XDA App
I'm not sure whats going on with my D3. However, I have RSD and I have .890 and .959 downloaded as well as Fastboot.
What I want to do is just wipe the phone completely and just flash it like its a brand new phone.
Anyone know how to do so? Please post a link or instructions, I would greatly appreciate it.
atquick said:
I'm not sure whats going on with my D3. However, I have RSD and I have .890 and .959 downloaded as well as Fastboot.
What I want to do is just wipe the phone completely and just flash it like its a brand new phone.
Anyone know how to do so? Please post a link or instructions, I would greatly appreciate it.
Click to expand...
Click to collapse
http://goo.gl/7NoAv
Androidsims said:
http://goo.gl/7NoAv
Click to expand...
Click to collapse
Tried that. It keeps failing saying something about size was not as expected or something like that.
Redownload?
Avelnan said:
Redownload?
Click to expand...
Click to collapse
I have. MD5 sums match up each time. Should I try removing the ext sd card?
I would redownload everything and try agian
littleneutrino said:
I would redownload everything and try agian
Click to expand...
Click to collapse
Alright, attempt will be made again. Should I redownload RSD again or just the sbf's?
atquick said:
Alright, attempt will be made again. Should I redownload RSD again or just the sbf's?
Click to expand...
Click to collapse
Downloading the sbf's again. Went over to check and see if the phone was still on, The charging led is on, however the screen is off..
Held power, nothing. Held M + Power. Still nothing... Any thoughts on whats going on now?
I didn't see if you have pulled the SD card but yeah it can't hurt.
Sent from my DROID3 using XDA App
http://forum.xda-developers.com/showthread.php?t=1278056
Follow the first portion of the instructions on how to flash back to original 5.6.890. Note the making of a folder and it's name for the 890 flash.
Ignore the part about flashing the new ROM. These are the best instructions I've found so far for flashing back to stock via RSD lite.
Good luck, keep us posted.
Download and follow exactly and you'll be good to go.
Hope that helps.
Sent from my DROID3 using xda premium
wattnxt said:
http://forum.xda-developers.com/showthread.php?t=1278056
Follow the first portion of the instructions on how to flash back to original 5.6.890. Note the making of a folder and it's name for the 890 flash.
Ignore the part about flashing the new ROM. These are the best instructions I've found so far for flashing back to stock via RSD lite.
Good luck, keep us posted.
Download and follow exactly and you'll be good to go.
Hope that helps.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
It keeps failing.
Step 3 mbmloader.bin
Step 4 mbm.bin
Step 8 logo.bin
Step 9 'lbl'
I'm stuck.
Let me do some looking when I get home tonight. I remember there being a file for certain versions of XP that helped some people and they couldn't flash without it.
I never had it happen personally, but I know those that did were terribly frustrated.
I also hear the 959 version is easier to flash for some reason. Never flashed that version, so this is only hear-say. But I know it did flash easier according to posts.
I will try to dig up a link for you.
i am getting the same thing also getting the bad CG boot.. now this may be a fix but idk how this guy got it it.. i have been asking eveywhere maybe you guys could help me... here is the thread http://forum.xda-developers.com/showthread.php?t=1248721
I found this by Psouza. He is likely the foremost expert on making things easy as far as unbricking your D3. Rumor has it he has a set of unbrick tools floating around this forum somewhere, though I haven't found it yet. Try in the Development thread, for sure it has to be there somewhere.
Post number 84
psouza4 said:
For those of you having problems flashing this and/or are suspicious of flashing ebr, mbr, and parts of the bootloader, you can selectively just flash the rest of it.
See attachment.
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=715510&d=1315657647
Hope this helps.
I also saw that flashing the pre-installs file alone first helped someone. That file borked on me once, but I was able to adb it over and then execute it via adb to get my phone unbricked.
Please let us know what works for you, as all of this is a work in progress right now.
Good luck!
i don't know to much about adb and are looking for help on pre-installed files. I don't understand what that means or how to go about it? i also cant get past the bootloader screen, "invalid CG version". i can not boot up at all.
How bricked are you? can you boot into CWM? Are you able to boot into tools, or how far can you get?
What version were you running? 5.959 (stock) or 6.890 OTA or Leaked OTA or Soak test (all the same as far as 6.890 goes).
i can get into boot tools and just tryed another flash got to step 6 till it failed instead of 3.. I'm running stock. Cannot get passed boot tools... scratch all that just tried to flash again just on the off chance it mnight work and i got it. Going to try and re-root and CWN recovery with sdteel froids rom... will keep you in the loop
Awesome!!
Here is the link about the adb commands for preinstall.sh
http://forum.xda-developers.com/showpost.php?p=17196391&postcount=88
It helped me when I borked my leaked update. I ran into the same problem as limaxray did with too many files in /system. So make sure you clean out any apps you made into system apps before trying the update via the standard update route, and that all stock system apps are in place and properly named.
I had to remove some that updated partially with the leaked update when mine borked. I used the posted system dump to push them to the phone and then the update ran properly and updated them anyhow.
If for some reason re-rooting doesn't work for you. Go to /system/bin and remove su, busybox. Do the same in /system/xbin. For some reason if you already have them in there when you run the process, it will say success but no root after reboot. My 2c as it happened to me. You do not need to remove superuser.apk, but you will have to update it in the market after you re-root.
Congrats!!
I see now too there is a fastboot and moto-fastboot. moto-fastboot has worked for some who had issues from what I've found.
Keep us posted, and smile knowing you've recovered from a bork; none of us got where we are without doing it at least once, so you're in good company.
re-rooted and installed bootstrap, just got steel droid all loaded up and all is good.... thanks for your speedy responses and detailed instructions and links. I realy think all that happened was i took everything aet it sone last time tried to flash and it went threw. All i used was RSD lite and flashed the 8.6.590 fast boot file and after a several retries it went threw. If anyone needs help on this i will post the file links if you need the ones i used
Tivo to the rescue! (edit: added numbers to make it easier to specify where to look for users caught in the middle somewhere)
1. You can do one of two things to get back to 5.5.886
You can use RSD Lite to sbf back to stock 886
http://briefmobile.com/droid-bionic-receives-fastboot-recovery-files
Or you can use this One click restore and root to get back to stock 886
http://forum.xda-developers.com/showthread.php?t=1279825
Both of these will erase your data (but not your sd card). There's no way around that.
Because you already updated your radio files and theres no way to downgrade that, the one click root method will not work anymore. There's no stopping that, its already been done.
2. Because of P3droid, however, there is a manual method of rooting that still works.
Follow this link
http://www.mydroidworld.com/forums/...-your-phone-back-upgrade-path.html#post106072
Look at the second post. I tested this method after I, myself, went to 893 and SBFed back to 886. It works.
3. After that you can follow this guide starting from step 5 to get keep root through any upgrade.
http://androidforums.com/bionic-all-things-root/434407-how-flash-893-update-maintain-root.html
4. Then download the 886>893 file from here and put it on your SD card
http://www.mydroidworld.com/forums/...found-update-files-read-before-you-flash.html
5. Boot phone into STOCK RECOVERY (not clockwork mod recovery). When the triangle is up, press BOTH volume keys. Use Volume Down to navigate and Volume Up to select the install zip option. Select the 886>893 file you just downloaded and let it install. It will take a while.
Boot back up after that and you should be rooted and be running 5.5.893
Tivo7 said:
Tivo to the rescue!
You can do one of two things to get back to 5.5.886
You can use RSD Lite to sbf back to stock 886
http://briefmobile.com/droid-bionic-receives-fastboot-recovery-files
Or you can use this One click restore and root to get back to stock 886
http://forum.xda-developers.com/showthread.php?t=1279825
Both of these will erase your data (but not your sd card). There's no way around that.
Because you already updated your radio files and theres no way to downgrade that, the one click root method will not work anymore. There's no stopping that, its already been done.
Because of P3droid, however, there is a manual method of rooting that still works.
Follow this link
http://www.mydroidworld.com/forums/...-your-phone-back-upgrade-path.html#post106072
Look at the second post. I tested this method after I, myself, went to 893 and SBFed back to 886. It works.
After that you can follow this guide starting from step 5 to get keep root through any upgrade.
http://androidforums.com/bionic-all-things-root/434407-how-flash-893-update-maintain-root.html
Then download the 886>893 file from here and put it on your SD card
http://www.mydroidworld.com/forums/...found-update-files-read-before-you-flash.html
Boot phone into STOCK RECOVERY (not clockwork mod recovery). When the triangle is up, press BOTH volume keys. Use Volume Down to navigate and Volume Up to select the install zip option. Select the 886>893 file you just downloaded and let it install. It will take a while.
Boot back up after that and you should be rooted and be running 5.5.893
Click to expand...
Click to collapse
I will give this a try tonight... I hosed up one the Bionic's last night....
I was able to get it back to 866 but lost the root. I tired to re-root it and it failed. So I can not re-do cheesecake and get to [ROM] [R3]BLURR3D V2.0 PBX MOTO Kernel .
Crossing fingers....
~Socks
sockstobed said:
I will give this a try tonight... I hosed up one the Bionic's last night....
I was able to get it back to 866 but lost the root. I tired to re-root it and it failed. So I can not re-do cheesecake and get to [ROM] [R3]BLURR3D V2.0 PBX MOTO Kernel .
Crossing fingers....
~Socks
Click to expand...
Click to collapse
Yeah you wont be able to use the current version of any one click root method anymore because you upgraded your kernel and radio and those cant be downgraded.
The only method I know that works after updating kernel/radio is p3droid's manual method.
What if you flash the original full FXZ file using RSD lite, will that put back the original kernal and radios?
No. It is currently impossible to downgrade kernels and radios.
OK, so question, pardon my newbness, coming from a Thunderbolt and bought the Bionic yesterday, I rooted, flashed bionic bootstrap, and made a backup of my stock rom. Then I flashed Blurred 2.0 which is based on .893. If for what ever reason I need to go back stock, can I do so, or am I hosed?
You can always go back to 886 by flashing the system.img file.
If you're talking about doing that while still running that ROM, I don't think you should. I don't kno what would happen.
You will never be able to downgrade your kernel or radio files though (these keep you from using the root method most people know). P3droid's manual method works though.
Wait, so when I want to sell this phone in a few weeks, can somebody post a method to return back to stock, etc?
Sent from my DROID BIONIC using XDA App on UNL3ASH3D R3BLURR3D V2.0 and will continue to be sent from here until I buy the Galaxy Nexus 32GB
Nvm, I thought I had read that one click restore wouldn't work, but it will
Sent from my DROID BIONIC using XDA App on UNL3ASH3D R3BLURR3D V2.0 and will continue to be sent from here until I buy the Galaxy Nexus 32GB
Tivo7,
i am back to .889 rooted and ready to brick my phone again wow Motorola really trying but thanks to everyone involve we could continue modding our phones with no worries.
thank you again.
I just bootstrapped my backup of my stock .886 back no problem, from blurry 2.0. Booted up fine, everything appeared to be working fine. Then I went back to my back up of blurry 2.0 and it went back fine.
droid3d said:
Tivo7,
i am back to .889 rooted and ready to brick my phone again wow Motorola really trying but thanks to everyone involve we could continue modding our phones with no worries.
thank you again.
Click to expand...
Click to collapse
Just follow my guide and you can get to 893 rooted.
You're welcome.
stevessvt said:
I just bootstrapped my backup of my stock .886 back no problem, from blurry 2.0. Booted up fine, everything appeared to be working fine. Then I went back to my back up of blurry 2.0 and it went back fine.
Click to expand...
Click to collapse
Nice. You can go to 893 with my guide.
Th3ory works on 893.
Thats what I was on,...went from th3ory R3 Blurr3d 2.0, based on .893, back to my stock .886 backup I made in bootstrap, worked fine, and back to the back up of Blurr3y I made in bootstrap again. No problems at all.
stevessvt said:
Thats what I was on,...went from th3ory R3 Blurr3d 2.0, based on .893, back to my stock .886 backup I made in bootstrap, worked fine, and back to the back up of Blurr3y I made in bootstrap again. No problems at all.
Click to expand...
Click to collapse
Cool cool.
stevessvt said:
What if you flash the original full FXZ file using RSD lite, will that put back the original kernal and radios?
Click to expand...
Click to collapse
I was unable to use the original full FXZ. When I tried to go back to stock 886, RAD would fail to flash. I had to use P3's method to get back to 886, and then used his method to root.
This is P3's post...
How to get your phone back on the upgrade path...
http://www.mydroidworld.com/forums/droid-bionic-forum/9800-how-get-your-phone-back-upgrade-path.html
Thanks, but since asking that question Ive nandroided back to stock .886 with a backup ive made. I know the radios and kernals are still .893, but everything worked fine.
stevessvt said:
Thanks, but since asking that question Ive nandroided back to stock .886 with a backup ive made. I know the radios and kernals are still .893, but everything worked fine.
Click to expand...
Click to collapse
Awesome. Good to know.
stevessvt said:
OK, so question, pardon my newbness, coming from a Thunderbolt and bought the Bionic yesterday, I rooted, flashed bionic bootstrap, and made a backup of my stock rom. Then I flashed Blurred 2.0 which is based on .893. If for what ever reason I need to go back stock, can I do so, or am I hosed?
Click to expand...
Click to collapse
If that's all you did you don't have 893 radio or kernel you have to do forever root and cheesecake app to get OTA update blurred 2.0 is based on update but dose not flash kernel or radio
Sent from my DROID BIONIC using xda premium
This saved me. Forever root didn't take when I updated to .893 so I had to do it manually off of a nandroid restore. Thank you so much!
anuraj1 said:
This saved me. Forever root didn't take when I updated to .893 so I had to do it manually off of a nandroid restore. Thank you so much!
Click to expand...
Click to collapse
You're welcome
I just didn't want others to feel all the pain I did on this, so I posted the steps I took to fix it.
This is basically just a guide putting everyone else's guides together in one place.
When I bought this Nook a few months back it was shipped with v 1.2. Now that I have messed it up and recovered it I'm on 1.0.1. Is there a way to get back to 1.2?
Also now my Nook says I have no storage. I have no books downloaded, it's just after the factory reset.
It says there is no storage because you are not on 1.2 or above. Just update manually through BN.
---------------------------------
Sent from my LG Optimus V using Tapatalk
koopakid08 said:
It says there is no storage because you are not on 1.2 or above. Just update manually through BN.
---------------------------------
Sent from my LG Optimus V using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. My problem is now that when I connect the Nook to the computer (linux Ubuntu), two drives show up both named B&N eReader. Neither can be opened. I suspect it's due to the fact that it shows no storage. How do I go about upgrading through B&N?
Maybe I have to use Windows? The 1.2 version before I started tinkering was recognised by Ubuntu Linux. Any help so I don't get murdered by my 9 year old for breaking her Nook is appreciated.
So are you on 1.2 now? Try making a bootable clockwork card and flashing this.
http://forum.xda-developers.com/showthread.php?t=1050520
---------------------------------
Sent from my LG Optimus V using Tapatalk
koopakid08 said:
So are you on 1.2 now? Try making a bootable clockwork card and flashing this.
http://forum.xda-developers.com/showthread.php?t=1050520
---------------------------------
Sent from my LG Optimus V using Tapatalk
Click to expand...
Click to collapse
No I'm not on 1.2. I used to be but after "bricking" it and bringing it back I now have 1.0.1. I also have a bootable clockwork sd card. My question was how to get to 1.2 or 1.3 and you answered it by the link. Than you very much. I love you guys
loveubuntu said:
When I bought this Nook a few months back it was shipped with v 1.2. Now that I have messed it up and recovered it I'm on 1.0.1. Is there a way to get back to 1.2?
Also now my Nook says I have no storage. I have no books downloaded, it's just after the factory reset.
Click to expand...
Click to collapse
It would help us more if we knew what you did/tried to do when messing it up... was it one of the "restore nook to stock" cwr images you used?
Try using the 8 failed boot attempts.... if you haven't messed up your recovery partition it should restore you to the version that was originally installed on your NC.
To help troubleshoot and fix it is really helpful to tell us what happened... you could also try using the cwr restore to stock 1.2 or the cwr update to 1.2 or 1.3 files.
DizzyDen said:
It would help us more if we knew what you did/tried to do when messing it up... was it one of the "restore nook to stock" cwr images you used?
Try using the 8 failed boot attempts.... if you haven't messed up your recovery partition it should restore you to the version that was originally installed on your NC.
To help troubleshoot and fix it is really helpful to tell us what happened... you could also try using the cwr restore to stock 1.2 or the cwr update to 1.2 or 1.3 files.
Click to expand...
Click to collapse
Thanks for your reply DizzyDen. As I mentioned in the post before yours, I think I'm all OK now. I had made a bootable CM7 sd card to have stock/CM7 (without and with SD) but somehow had CWR installed on the emmc.
Then trying to upgrade to 1.3 from their website, I was not allowed. So what I had to do was to make a bootable CWR sd card, boot from the sd card and remove the CWR from emmc (used a flashable zip found on forums) and then flash a 1.0.1 image. Then I used the 1.2 update from the above link to update to 1.2 and then used the 1.3 from B&N website to upgrade to 1.3. Now I'm where I want to be but thinking about rooting again It's too much excitement but didn't have to be.
I think I must have tried to flash CWR recovery with the ROM Manager app when I had the CM7 bootable sd card in that caused all these problems. It's nice to have the bootable CWR though.
loveubuntu said:
When I bought this Nook a few months back it was shipped with v 1.2. Now that I have messed it up and recovered it I'm on 1.0.1. Is there a way to get back to 1.2?
Also now my Nook says I have no storage. I have no books downloaded, it's just after the factory reset.
Click to expand...
Click to collapse
You can get you Nook back to the factory 1.2 by following procedure the it described near the end of the first post at
http://forum.xda-developers.com/showthread.php?t=1054027
Look for the "Complete Wipe" heading.
BASIC! said:
You can get you Nook back to the factory 1.2 by following procedure the it described near the end of the first post at
http://forum.xda-developers.com/showthread.php?t=1054027
Look for the "Complete Wipe" heading.
Click to expand...
Click to collapse
thanks, i wonder why this isn't included in the guide sticky thread. Also, is there a simpler way to complete wipe than the 8 reboot sequence? a script?
loveubuntu said:
thanks, i wonder why this isn't included in the guide sticky thread. Also, is there a simpler way to complete wipe than the 8 reboot sequence? a script?
Click to expand...
Click to collapse
Here's a BootCnt file and a dos batch file that will make it a LOT easier for ya if you have adb running...
DizzyDen said:
Here's a BootCnt file and a dos batch file that will make it a LOT easier for ya if you have adb running...
Click to expand...
Click to collapse
Thank you. I have adb and will give it a whirl later. I'm still stcuk with trying to have a working ROM on the nook. The Phiremod7.1 which is based on CM7 seems to be working fine now but I can't get any CM7 nightlys to show any soft keys at the bottom, hence no back or notification bars. I'm going to try a stable one to see if that maybe the problem. Funny that I was able to run the nightlies when I was off of SD.
Also while I have your ear, , I'm a bit confused about this wiping and rooting business with the nook. I'd appreciate any help for me to understand it a litlle better. Excuse my ignorance.
Why can't a complete wipe be performed when booted from a CWM sd card? In the numerous phones I have rooted the sequence is easy: root, install custom recovery, nandroid back up, wipe data/system/cache/dalvik and then install a new rom. In the nook,, I still get residual from the last rom (my wifi settings, wallpaper, B&N registration info) unless I do the 8 reboot sequence. What does the 8 reboot wipe that we can't wipe any other way? What does emmc format accomplish then?
Also, how is it that I can install a rom through an SD card without ever rooting the nook?
TIA
loveubuntu said:
Thank you. I have adb and will give it a whirl later. I'm still stcuk with trying to have a working ROM on the nook. The Phiremod7.1 which is based on CM7 seems to be working fine now but I can't get any CM7 nightlys to show any soft keys at the bottom, hence no back or notification bars. I'm going to try a stable one to see if that maybe the problem. Funny that I was able to run the nightlies when I was off of SD.
Also while I have your ear, , I'm a bit confused about this wiping and rooting business with the nook. I'd appreciate any help for me to understand it a litlle better. Excuse my ignorance.
Why can't a complete wipe be performed when booted from a CWM sd card? In the numerous phones I have rooted the sequence is easy: root, install custom recovery, nandroid back up, wipe data/system/cache/dalvik and then install a new rom. In the nook,, I still get residual from the last rom (my wifi settings, wallpaper, B&N registration info) unless I do the 8 reboot sequence. What does the 8 reboot wipe that we can't wipe any other way? What does emmc format accomplish then?
Also, how is it that I can install a rom through an SD card without ever rooting the nook?
TIA
Click to expand...
Click to collapse
I have only recently noticed the remnant effect of previous data... I suspect it has something to do with B&N's newest software effecting the ability to wipe the partitions... perhaps formatting the partitions first would assist.
The 8 failed boots completely re-initializes the Nook with the factory backup data stored on mmcblk0p3... there is the complete rom and device specific backup stored in zip files there.
You can install a ROM by booting off the SD because B&N set our nooks up to boot from SD first... so when you do nothing from the Internal storage is loaded upon boot... so its not in use and can easily be manipulated.
Hey everyone. I rooted my phone a while back (around June), but it got unrooted during the update in July and I haven't bothered rooting it again. But now, when I try to update to Gingerbread, I always get a message saying "Update failed or incomplete" after downloading and rebooting. I noticed I still have SuperUser installed, so I tried unrooting with SuperOneClick, but SuperOneClick is stuck on "Waiting for Device". I have also tried to reset to factory settings, with the same result. Does anyone know how to fix this? Thanks.
rawrzar said:
Hey everyone. I rooted my phone a while back (around June), but it got unrooted during the update in July and I haven't bothered rooting it again. But now, when I try to update to Gingerbread, I always get a message saying "Update failed or incomplete" after downloading and rebooting. I noticed I still have SuperUser installed, so I tried unrooting with SuperOneClick, but SuperOneClick is stuck on "Waiting for Device". I have also tried to reset to factory settings, with the same result. Does anyone know how to fix this? Thanks.
Click to expand...
Click to collapse
You may not have updated like you thought. V6 should have gotten rid of root for you. I had to do a factory restore, wipe the data and image, all of it. When I went back to do all that stuff, I still had the Bionic splash screen, and it is because of that little change, that I was not able to update myself. You may have something similar going on with your phone, just in a different place. Anything beyond doing that, just ask, but it should take care of you. Make a backup first, just in case. You will have to set everything up again.
markapowell said:
You may not have updated like you thought. V6 should have gotten rid of root for you. I had to do a factory restore, wipe the data and image, all of it. When I went back to do all that stuff, I still had the Bionic splash screen, and it is because of that little change, that I was not able to update myself. You may have something similar going on with your phone, just in a different place. Anything beyond doing that, just ask, but it should take care of you. Make a backup first, just in case. You will have to set everything up again.
Click to expand...
Click to collapse
Thanks for your reply. I have performed a factory reset, but the update still fails. I also notice that after the reset, SuperUser is still listed under my installed apps.
rawrzar said:
Thanks for your reply. I have performed a factory reset, but the update still fails. I also notice that after the reset, SuperUser is still listed under my installed apps.
Click to expand...
Click to collapse
Does the update fail, or does it just say no update available?
Sent from my VS910 4G using xda premium
mtmichaelson said:
Does the update fail, or does it just say no update available?
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
It fails. the update downloads, and reboots to install. But about half way through the installation, the phone reboots again. when the home screen comes up, a screen pops up saying "update failed or incomplete".
I had the same problem. Did you reinstall the stock recovery program? I also had the bionic boot image from revolt1.5, which was messing things up. Once I reverted back to the stock boot image, the update went through.
JohnnyAn said:
I had the same problem. Did you reinstall the stock recovery program? I also had the bionic boot image from revolt1.5, which was messing things up. Once I reverted back to the stock boot image, the update went through.
Click to expand...
Click to collapse
How would I go about reverting back to stock image? sorry , I don't know much about this.
rawrzar said:
How would I go about reverting back to stock image? sorry , I don't know much about this.
Click to expand...
Click to collapse
The cubed had a stock revo file that he posted somewhere in the dev forum. Just flash that with CWM and you should be good to go.
Sent from my VS910 4G using XDA App
I am in a similar situation but when I try to update to gingerbread it says there is no update available. I too still have supreuser installed after reflashing from revolt 1.5 to thcubed zv4 rooted stock and then updating its to zv6. How can I get my phone to download zv7?
Sent from my VS910 4G using XDA App
jdleider said:
I am in a similar situation but when I try to update to gingerbread it says there is no update available. I too still have supreuser installed after reflashing from revolt 1.5 to thcubed zv4 rooted stock and then updating its to zv6. How can I get my phone to download zv7?
Sent from my VS910 4G using XDA App
Click to expand...
Click to collapse
Apparently the update hasn't been pushed to all phones yet...there's several of us on xda that still don't have it. Jackpot08 is working on a .tot but until then, we just have to wait.
Some people have called Verizon and they can't force the update to your phone, so don't bother with that.
JohnnyAn said:
The cubed had a stock revo file that he posted somewhere in the dev forum. Just flash that with CWM and you should be good to go.
Sent from my VS910 4G using XDA App
Click to expand...
Click to collapse
Thanks! Found it and got it working. Just waiting for the update now.
jamRwoo said:
Apparently the update hasn't been pushed to all phones yet...there's several of us on xda that still don't have it. Jackpot08 is working on a .tot but until then, we just have to wait.
Some people have called Verizon and they can't force the update to your phone, so don't bother with that.
Click to expand...
Click to collapse
Thanks for the info, guess the update hasn't been pushed to my phone yet.
I have been on stock for a week now, and its been horrible. I forgot how slow this was before devs streamlined the system, and how many rooted apps/functions I used.
I am going back to revolt today. I will see GB when the .TOT is available.
rawrzar said:
Hey everyone. I rooted my phone a while back (around June), but it got unrooted during the update in July and I haven't bothered rooting it again. But now, when I try to update to Gingerbread, I always get a message saying "Update failed or incomplete" after downloading and rebooting. I noticed I still have SuperUser installed, so I tried unrooting with SuperOneClick, but SuperOneClick is stuck on "Waiting for Device". I have also tried to reset to factory settings, with the same result. Does anyone know how to fix this? Thanks.
Click to expand...
Click to collapse
Were you attempting to update to gingerbread by using the TOT? Or was there an update available though your service provider?
If you were getting a failure through the network, it's likely because you haven't gone back to stock recovery and still have ClockWorkMod Recovery installed. Use DevToolKit to fix this.
If you are using the TOT and getting a failure, do a checksum on the TOT file.
I've been working on this actively as I have a revolution. LG has informed me the update push completed on November 2. Nobody at VZW or LG can tell me why some Revolutions haven't gotten the push.
VZW Engineering has apparently been alerted, but LG has been unresponsive to me to-date.
I'm not waiting and putting together a one-package manual update kit, but I do want to give LG and VZW time to give me an update. Thing is, it's been over 72 hours now and there hasn't been one, so my patience is wearing thin.
It's disappointing that LG hasn't responded to any of my inquiries... I'm asking the right people behind the scenes.
hatoncat said:
I've been working on this actively as I have a revolution. LG has informed me the update push completed on November 2. Nobody at VZW or LG can tell me why some Revolutions haven't gotten the push.
VZW Engineering has apparently been alerted, but LG has been unresponsive to me to-date.
I'm not waiting and putting together a one-package manual update kit, but I do want to give LG and VZW time to give me an update. Thing is, it's been over 72 hours now and there hasn't been one, so my patience is wearing thin.
It's disappointing that LG hasn't responded to any of my inquiries... I'm asking the right people behind the scenes.
Click to expand...
Click to collapse
I'm in Rochester NY and never got one. I gave it til 2 days ago and threw on the TOT.
Madert said:
I'm in Rochester NY and never got one. I gave it til 2 days ago and threw on the TOT.
Click to expand...
Click to collapse
Yeah, I'm leaning towards drafting an idiot-proof TOT guide, it's just going to be really upsetting if I have to do that. If this was Apple, and not LG, we wouldn't even have this thread right now.
Option-click .ipk and done... not that Apple would even let ~1-5% of a device "miss" an update.
So, I've confirmed a few things with LG officially:
1) The ZV7 update has not been pulled.
2) LG was not aware of this issue until I reported it.
3) LG is just now starting the process of investigating.
I can't flash a TOT on mine right now, as LG may want to capture my unit for evaluation. I'll know more soon, hopefully by Monday.
Verizon was trying to push an update on me back on the 11th. It was the V6 update, as I was running V4. It failed, and I manually ran the tot through with LGNPST. Since thecubed had posted the V7 tot as well, I ran that through as well.
I probably did not need to go from V4 to V6 to get to V7, but I figured it wouldn't hurt.
But as I said, the only push I had received was on the 11th, well after the 2nd.
As a semi-newbie, it was easier to push the tot on than anything else.
LG Engineering is at least listening... they have agreed to capture my unit and send me a brand new Revolution simultaneously.
antiwesley said:
Verizon was trying to push an update on me back on the 11th. It was the V6 update, as I was running V4. It failed, and I manually ran the tot through with LGNPST. Since thecubed had posted the V7 tot as well, I ran that through as well.
I probably did not need to go from V4 to V6 to get to V7, but I figured it wouldn't hurt.
But as I said, the only push I had received was on the 11th, well after the 2nd.
As a semi-newbie, it was easier to push the tot on than anything else.
Click to expand...
Click to collapse
Did you have clockwork recovery installed when you tried to get Verizon s update
Sent from my gingervolt`ed revolution