My x2 doesnt seem to wont to update to gingerbread i tried to install the pre rooted gingerbread from p3 yesterday to no avail ..i tried wiping data and cache after several failed installs coming rooted 2.2 i decided to try the locked down offical update from vzw. The update always fails to install after it reboots and goes into the recovery. Upon rebooting and goin back to the homescreen the installation still fails. Any suggestions . i even tried unrooting and removing apps that required super user access and still no luck.
You need to SBF your phone back to complete stock in order to install either update. There can't be any removed system apps, or modified system files.
uhh186 said:
You need to SBF your phone back to complete stock in order to install either update. There can't be any removed system apps, or modified system files.
Click to expand...
Click to collapse
yeah do that also you understand that both versions Are exactly THE SAME XDDDDD, The only difference is the rooted one has a patch
gcforreal said:
My x2 doesnt seem to wont to update to gingerbread i tried to install the pre rooted gingerbread from p3 yesterday to no avail ..i tried wiping data and cache after several failed installs coming rooted 2.2 i decided to try the locked down offical update from vzw. The update always fails to install after it reboots and goes into the recovery. Upon rebooting and goin back to the homescreen the installation still fails. Any suggestions . i even tried unrooting and removing apps that required super user access and still no luck.
Click to expand...
Click to collapse
You are not the only one. I did a pre-emptive total defrost and factory reset before downloading the update, so everything should have been stock. The update starts to install, makes it about a fourth of the way through, then the phone reboots and tells me the update failed. After spending an hour with Verizon's tech support I finally convinced them to replace the phone, hopefully with one that already has the update installed..
God, I'm starting to hate smartphones. My old Moto KRZR never gave me this kind of trouble ... I'm seriously thinking of going back to it.
Ok, Just so I have this right. I have to reset the phone to factory settings, then update to GB. A simple unroot will not do the trick. (I tried this and the update failed)
I factory reset my wife's DX before updating to GB and had no issues.
Also as of this post it appears there is no way to root GB 2.3.3 correct?
depco164 said:
Ok, Just so I have this right. I have to reset the phone to factory settings, then update to GB. A simple unroot will not do the trick. (I tried this and the update failed)
I factory reset my wife's DX before updating to GB and had no issues.
Also as of this post it appears there is no way to root GB 2.3.3 correct?
Click to expand...
Click to collapse
Nope. Needs to be prerooted because the exploit used by gingerbreak is fixed in the update.
Go to my thread here, it explains how to install the update.
Here's what I did:
From a rooted 2.2.2 - unrooted using gingerbreak, then followed the spf tutorial.
Now back to stock with all my apps, ran the update. Installed fine.
SBF
Just do the SBF procedure listed on several threads and it will work fine. Something that has been done to your phone isn't playing nice with either update. There is virtually no difference between the updates other than the patch for root. I format and factory reset, then sbf and then wipe/data in recovery every time before I flash new roms or updates, just to eliminate any crap that might cause problems. Helps to narrow down what I need and don't need. If I forget to re-install it, I probably don't need it anyways. Good Luck. After root try the eclipse rom it pretty basic mostly just a debloat.
so you can not yet root when you do the GB update......
Related
Okay, so I see there are many people that have the same questions I had yesterday trying to apply this update with a custom ROM already on my phone. Here is what you'll need and how to get your phone updated. This isn't the only way to do it, but it's what I did and it was pretty easy. It was harder finding out how to do all of this, and in what order than actually doing the process.
It will take a little while to do this, roughly 30-45 minutes.
Here are the steps I had to use being on 1.5.7 with GingerBlur:
Here is what you'll need after backing up your apps/files to the SD Card, in this order:
Download RSD Lite 5.0
Download 1.8.3 sbf
Gingerbreak
GladEnable
Tenwar's System Recovery
GreyBlur 2.X (Or insert custom ROM here)
1: Flash the 1.8.3 update on to your phone using RSD Lite, this will reset your phone completely to stock.
2: Run GingerBreak to root the device.
3: At this point I was unable to install Tenwar's, so I used GladEnable to sideload it.
4: Installed Tenwar's and loaded up my custom ROM.
5: Restore your backup.
This should get you all updated and with your custom ROM installed.
Awesome! Thanks man
quick question: how do we make a backup (Ti Backup?) on our current setups? And will restoring the backup we make bring back all apps and settings and everything?
Thanks a lot for this....
spitefulcheerio said:
Awesome! Thanks man
quick question: how do we make a backup (Ti Backup?) on our current setups? And will restoring the backup we make bring back all apps and settings and everything?
Click to expand...
Click to collapse
Yes, use Titanium Backup to backup your User Apps and Data, not the system apps or data. And make sure to backup to your SD Card as the flash with wipe your internal memory and your backup will be lost. I had that issue and had to reinstall all of my apps. It's minor, but still a pain in the ass.
Flashing 1.83 should not wipe anything; as far as apps or info. goes. Some people have had a problem with gingerbreak wiping some things though. I flashed 1.83 and ran ginerbreak with no problems, except for having the bloatware re-installed and loosing my root, but that's to be expected.
Swiftks said:
Flashing 1.83 should not wipe anything; as far as apps or info. goes. Some people have had a problem with gingerbreak wiping some things though. I flashed 1.83 and ran ginerbreak with no problems, except for having the bloatware re-installed and loosing my root, but that's to be expected.
Click to expand...
Click to collapse
When I flashed 1.8.3 through RSD Lite, it completely put everything back to bone stock. It wiped the entire internal memory. So I'm not sure if it should or shouldn't, but it did. I know it wasn't GingerBreak because you flash the update before installing GB.
IrateCustomer said:
When I flashed 1.8.3 through RSD Lite, it completely put everything back to bone stock. It wiped the entire internal memory. So I'm not sure if it should or shouldn't, but it did. I know it wasn't GingerBreak because you flash the update before installing GB.
Click to expand...
Click to collapse
that's weird, b/c when I flashed it, it didn't wipe anything just added the bloat ware back and changed the radio, etc. still had homescreen the same with all my apps, etc.... oh well
Swiftks said:
that's weird, b/c when I flashed it, it didn't wipe anything just added the bloat ware back and changed the radio, etc. still had homescreen the same with all my apps, etc.... oh well
Click to expand...
Click to collapse
Maybe because I was on 1.5.7, and flashed 1.8.3 instead of going back and OTAing the phone. That would make sense because the OTA process probably does a backup/restore during the process. As mentioned in the OP, it's only one way to do it, but there are other options.
the sbf download is sending me to Motorola site,, dont I need the sbf not the exe??
Datblkbro said:
the sbf download is sending me to Motorola site,, dont I need the sbf not the exe??
Click to expand...
Click to collapse
I've updated the link in the OP so you can download the correct file. My apologies.
Regarding 1.8.3 sbf, which of the sfb files from the link you provided is it? They vary in size. Thanks.
You want the one with the most hits and the ridiculously long filename.
It actually has 1.8.3 buried in the name of the file. It's a few from the top.
THANK YOU this has been a big question mark for me ever since 1.83 came out. Fantastic guide.
Swiftks said:
Flashing 1.83 should not wipe anything; as far as apps or info. goes. Some people have had a problem with gingerbreak wiping some things though. I flashed 1.83 and ran ginerbreak with no problems, except for having the bloatware re-installed and loosing my root, but that's to be expected.
Click to expand...
Click to collapse
Did the GingerBlur 3.1 get fixed when it comes to the Webtop mod? Cuz I read something about it having a problem with actually working on this Rom? Maybe that was on the 3.0, so I figure 3.1 fixed it?
PLease just a simple "yes it works" or "No, it doesn't" will suffice
Thanks
Just wanted to post my initial experience with using RSDlite to update afterting and gingerblurring it.
I followed your how to as much as I could (You should provide a link to RSDlite instructions, I had to search for it because I didn't know how to do it exactly... not a big deal but it would make it easier/idiot proof)
When I first updated via RSDlite, something must hve went wrong. At first, A triangle and lil android was haunting me on my screen... so I went to reboot.. **** [I thought I bricked it]... Then I restarted it again... DOUBLE ****... Couldn't load into recovery... I restarted a third time and it loaded up(**** YES). But for some odd reason, it said I still had to update (even though it said the firmware was @ 1.8.3.)
Everything seemed to work fine, and was able too root and ginger blur it. About a few hours later, wifi seemed wonky (kept randomly disconnecting and the update dialog came up every 15 minutes).
I ended up reflashing to 1.2.8 and OTA's all the way up to 1.8.3 and then re-rooted and blurred it. No problems since the full refresh
Hopefully everybody elses experience goes better than mine!
Also, Random question. How do you remove Tenwars System Recovery app after using it to load up a rom?
winky! said:
Also, Random question. How do you remove Tenwars System Recovery app after using it to load up a rom?
Click to expand...
Click to collapse
You can use Uninstaller for Root (I found it on the Market), and you can uninstall from there if you wish. Personally I see no real reason to remove it, but you can if you need to with the above referenced Uninstaller. There are a few others that can do it, but UfR is free, which is clearly a win.
564mb for the sfb??? Thats freaking huge
GreyBlur on 1.8.3
After following the steps I still show
"System Version 4.1.57MB860.ATT.us"
rooted and sideloading enabled by gladroot then flashed greyblur 2.1....little help for the n00b?
Guys I'm new to the forum but have been messing around with custom pseudo-roms for the Atrix for a little while now. I was running Adeo, then Gingerblur, then Greyblur all without a hitch when I heard about the new OTA update coming to the phone and Gingerbread coming up, so I wanted to go back to any build that would allow me to get the HSUPA update as well as the gingerbread update, but when I went to flash my phone to sbf using rsdlite, it said internal programming fail and nothing else happened. I installed gingerblur over greyblur in an attempt to see if it would flash, but nothing. Have done a factory data wipe, still can't flash. I can't even get into the stock Android Recovery, all that comes up is a triangle and exclamation point. Could someone please help me out here, I'm running gingerblur on a rooted Atrix on 1.5.7 and cannot get it to flash sbf, all I want to do is go back to stock att rom for the coming updates.
Thanks,
BK
Hey,
I have the same exact set up as you. It seems vague in your post if you re-flashed back to 1.26, and that may be why you're getting errors? Every time I update roms, I re-flash to 1.26 using the method in the link below.
http://forum.xda-developers.com/showthread.php?t=991072
Then I ran Gladroot to unlock, enable sideloading, etc.
http://forum.xda-developers.com/showthread.php?t=1016060
Downloaded and install the 1.83 update online (not on-air because I didn't get prompted)
http://www.motorola.com/consumers/v/index.jsp?vgnextoid=9098bc50a569f210VgnVCM10000081bbb00aRCRD
I ran the 'afterupdate.bat' on Gladroot after installing the update.
And I now have 2.2.2 / 1.8.3
Thanks bud, what I ended up doing was trying to manually uninstall gingerblur and greyblur and the adeo rom by using scripts etc but it never worked. My phone started acting weird, the home button stopped working, no 3g connectivity, it would say I have superuser but it wouldn't be rooted... something was seriously messed up. I tried to get into the stock android recovery but it wouldn't boot, I think something was corrupted. I knew sbf files rewrite system and boot data, so I went into tenfar's custom recovery (after rooting for the 10th time) and deleted system and boot data, system data was deleted, but boot data had an error. I wiped the caches and all and I tried to sbf flash to 1.8.3 but nothing and the phone bricked. I then tried it on another computer with more memory than mine (mine was running kind of low because of a linux partition) and the flash worked and I'm on 1.8.3. I think I'll wait for official gingerbread and unlocked bootloader in July before I mess with my phone again.
After unlocking my bootloader i haven't been able to install apps but every once in a wail after restarting it then trying to update them real quick. I'm at a loss and would love to be able to use my phone again, thanks.
Adam
Were you trying to download a plethora of apps after flashing.? I just learned the hard way myself Google has a "floodgate" installed in the Android Market to prevent mass downloading of apps all at once. After flashing my Cap a few days ago I was downloading hundreds of apps when all of a sudden I started getting the unsuccessful download message. I got the same message on the Atrix as well (same Google account). The solution for me was to wait 24 hours. And yes I know I should have just restored from TiBU, lesson learned.
Ya but I cant even install apps from the net and I have sideloading enabled
Sent from my MB860 using XDA App
I factory wiped it and started over and now I cant install any apps to get get my backups. Any ideas I would love it if you can help me out, ill even donate to you just hate not having a working phone.
please,
Adam
What firmware are you using ? 1.8.3 / 2.3.4 ?
AdamsBig said:
After unlocking my bootloader i haven't been able to install apps but every once in a wail after restarting it then trying to update them real quick. I'm at a loss and would love to be able to use my phone again, thanks.
Adam
Click to expand...
Click to collapse
I had this problem too!! Where absolutely nothing would install after I went back to stock (flashed a full 1.26 sbf) after unlocking the bootloader and installing hk2.3.4
I was going crazy cause I couldn't even unmount my storages or anything and drivers kept constantly trying to reinstall on my comp!
The way I solved this is to install the newest tenfars CWM recovery and then I formatted every single thing that could be formatted and that finally did the trick! I'm so happy to finally have my atrix working normal again! I thought flashing a full sbf undoes most everything you do to the phone but I was definetly wrong!
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Thanks for the reply!
I didn't check the MD5 last night but I did just now and it matches.
I did a cache wipe the first time but not a system wipe. Then I started getting more desperate and tried reinstalling w/ system wipes and factory resets, but it didn't change anything.
No, I didn't change the ROM. Doing the Bootloader unlock exploit was about the absolute maximum of my technical abilities! The only thing I know I did wrong was that I didn't downgrade to the old boot version the first time (mainly because the wifi thing sounded inconsequential and I didn't want to learn the procedure if I didn't have to).
Anyway, I just tried Ultimate KangBang and it seems to work--no error messages so far. I don't know what I did wrong, but hopefully this keeps working!
IceDragon59 said:
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
Click to expand...
Click to collapse
andybones said:
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Click to expand...
Click to collapse
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
franklin411 said:
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
Click to expand...
Click to collapse
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
in the future it is always good practice to backup(nandroid) your current ROM. I have been burned too many times, always do a nandroid before you do anything in recovery.
your photos are normally saved to the SD, flashing ROMs or wiping the system will not delete them
andybones said:
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
Click to expand...
Click to collapse
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
franklin411 said:
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
Click to expand...
Click to collapse
na the name has nothing to do with it. it can be named whatever.
im guessing the wipe worked.
franklin411 said:
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Click to expand...
Click to collapse
weird, i was having the same problem with the same processes stopped working. i wiped cache dalvik and system but not factory reset. once i factory reset, it worked fine. i figured a system wipe would have been enough....
Ok, so my Droid RAZR MAXX is still on Android 4.0.4. It is rooted and I've tried SO MANY different things to do the OTA update. Most recently I backed everything up, temp un-rooted & did a factory data reset, then tried updating again. I may have removed a program with TitaniumBackup so the update may be failing the check. Though I don't know how to see which program was removed.
How do I manually update to stock 4.1.2? Yes, I searched but I either didn't find it or I did and it got lost among the many tabs I had open trying to find the answer.
help...
Have you tried this? http://www.droidrzr.com/index.php/t...inux-all-in-one/page__pid__227369#entry227369
I did see that before I was ready to wipe everything on my phone and forgot about it, I'll give it a try.
Ok, so that worked. Wow, wish I tried that a long time ago. Thanks!
amlamarra said:
Ok, so my Droid RAZR MAXX is still on Android 4.0.4. It is rooted and I've tried SO MANY different things to do the OTA update. Most recently I backed everything up, temp un-rooted & did a factory data reset, then tried updating again. I may have removed a program with TitaniumBackup so the update may be failing the check. Though I don't know how to see which program was removed.
How do I manually update to stock 4.1.2? Yes, I searched but I either didn't find it or I did and it got lost among the many tabs I had open trying to find the answer.
help...
Click to expand...
Click to collapse
Wow, I am having the exact same issue. Matter of fact I posted here too but did not get a reply but have seen the utility you used. Guess I will give that a shot. Of course I already did a factory reset and to no avail, it didn't work. Not sure what I could have done to cause the issue with no OTA success, but I will now try the Utility. Glad you posted and someone answered.
Matt's Utility is amazing. Saved me a lot of time trying to fix problems and its a one stop shop for the OTA update and rooting your phone. Just be aware that this puts you on the .16 kernel and I only know of 6 roms that will work with it right now and not put you in a boot loop (which was my orig problem.)
renrut23 said:
Matt's Utility is amazing. Saved me a lot of time trying to fix problems and its a one stop shop for the OTA update and rooting your phone. Just be aware that this puts you on the .16 kernel and I only know of 6 roms that will work with it right now and not put you in a boot loop (which was my orig problem.)
Click to expand...
Click to collapse
http://www.droidrzr.com/index.php/t...l-switch-between-jellybean-kernels-with-ease/
You can use that to take you to the .8 leak so you can install ROMs based on the leak