ok can't get this to work. first i was on 1.5.7 with gingerblur, tried updating to the latest through rsd lite and after it finished my phone shows
Failed to boot 2
Starting RSD mode
i've tried everything and always end up with this outcome. whats going on?
CustomA313 said:
ok can't get this to work. first i was on 1.5.7 with gingerblur, tried updating to the latest through rsd lite and after it finished my phone shows
Failed to boot 2
Starting RSD mode
i've tried everything and always end up with this outcome. whats going on?
Click to expand...
Click to collapse
If rsd mode is working then try and go back to 1.26. At least I would try that to get a fresh start and then reupdate and root and everything again.
Gutterball said:
If rsd mode is working then try and go back to 1.26. At least I would try that to get a fresh start and then reupdate and root and everything again.
Click to expand...
Click to collapse
i also did that. i went back to 1.26, updated OTA to 1.57 and tried again to get to 1.83 but same thing happenedd
Where are you getting 4.1.83 from?
a post from the development forums
I had the same problem, it failed as it went to update the radio as I had already done the hsupa update.
The found I could not restore any sbf over the top. Update your Rsd to a version 5 or higher and then apply either 1.2.6 or 1.5.7 sbf and all is well.
Sent from my MB860 using XDA App
jysue said:
I had the same problem, it failed as it went to update the radio as I had already done the hsupa update.
The found I could not restore any sbf over the top. Update your Rsd to a version 5 or higher and then apply either 1.2.6 or 1.5.7 sbf and all is well.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
i'm using version 5.0 and did a full restore back to 1.2.6, then updated to 1.5.7 so shouldn't that fix any radio issues that your talking about? everytime i try i get the same 'failed to boot 2' error
CustomA313 said:
i'm using version 5.0 and did a full restore back to 1.2.6, then updated to 1.5.7 so shouldn't that fix any radio issues that your talking about? everytime i try i get the same 'failed to boot 2' error
Click to expand...
Click to collapse
everytime you update 1.8.3 after restoring all the way back to the start and upgrading?
I was using Tenfars to apply the Zip file update and noticed it failed to apply the radio everytime, I ended up applying it 10 times in a row (at wits end) and when I rebooted everything worked but I had the old radio. Then I applied the HSUPA updated radio (again).
Previously everytime I applied it would fail and then reboot would show failed to boot 2.
My RSD Lite version is 5.3.1, before when I could not apply 1.2.6 or 1.5.7 it was version 4.9
jysue said:
everytime you update 1.8.3 after restoring all the way back to the start and upgrading?
I was using Tenfars to apply the Zip file update and noticed it failed to apply the radio everytime, I ended up applying it 10 times in a row (at wits end) and when I rebooted everything worked but I had the old radio. Then I applied the HSUPA updated radio (again).
Previously everytime I applied it would fail and then reboot would show failed to boot 2.
My RSD Lite version is 5.3.1, before when I could not apply 1.2.6 or 1.5.7 it was version 4.9
Click to expand...
Click to collapse
yea pretty much and now i think my phone is toast. it's dead and so it's not recognized when i plug it in my computer and when i plug it in the wall it just goes to the error screen with the moto logo on it and just gets really hot -_-
CustomA313 said:
yea pretty much and now i think my phone is toast. it's dead and so it's not recognized when i plug it in my computer and when i plug it in the wall it just goes to the error screen with the moto logo on it and just gets really hot -_-
Click to expand...
Click to collapse
pull the battery and let it sit a while, have a go in a few minutes. if it's not booting straight to fail 2 then try forcing RSD mode with vol up and see how you go getting it back to flashable mode.
I thought I was toast a dozen times when mine went off the rails...not quite sure still how having the HSUPA update on rooted 1.5.7 made me incompatible with 1.8.3 update since it contains a new radio image not a patch - maybe someone smarter can figure it out!
Related
So being a n00b, I forgot the ever so important unroot before I accepted the newest update to .340. I have tried everthing in the forums that I have read over the last few days. Have I forever lost my ability to root my DX?
Any help greatly appreciated! Sorry if this is in the wrong spot, I have never posted a thread b4!
Try z4root. Should root you just fine. Easily.
http://www.addictivetips.com/mobile...root-app-for-samsung-galaxy-s-android-phones/
And if you're running into any trouble using it, refer to this thread
http://forum.xda-developers.com/showthread.php?t=867694
FYI, you don't have to unroot for an OTA anyway.
O...I did not know that...I though u have to unroot for all updates...now I am even more confused. I lost my root privelages after the udate and have not been able to regain access. I have tried z4, rageagainstthecage, and a couple other methods. I am going to try using rsd lite next to flash, but some forums say this will work and others say u can not flash with the .340
SBF
could always do a 2.3.320 sbf and do the ota update again correct?
Haven't had to SBF in a while, but last I checked 2.3.320 was the last full SBF released. so while a there is a .340 System SBF if I were trying to make sure it wiped everything out of there, i'd go with the full sbf.
dnice102 said:
I am going to try using rsd lite next to flash, but some forums say this will work and others say u can not flash with the .340
Click to expand...
Click to collapse
Since you are running the newest update, (.340) make sure you don't use the 2.3.15 sbf since it will no longer work with your bootloader and your phone will be stuck until you flash a newer SBF. That is probably what you are hearing from other posts, with .340 you cant flash 2.3.15.
There are patches to go from .320 to .340, but for me, nothing is more simple than clicking accecpt update and going to make a sandwich.
If he SBF's to .320 he won't be able to get .340 with the OTA. Verizon doesn't
recognize .320 so the OTA won't happen. He can just go SBF .320 and use the
patches after that. It's what I did.
http://www.mydroidworld.com/forums/...ystem-baseband-2-3-340-kernel-bootloader.html
update.zip
ah, didn't know that, what about this?
http://forum.xda-developers.com/showthread.php?t=906191
update.zip to .340.
haven't tried this yet, just ran across it.
Thanks for everyone's help. The flash to .320 did the trick. However after the phone's battery died n I recharged, I am stuck on the motorola screen during boot. I can get into the factory recover, but that didnt help. Also, I can no longer access the bootloader. Am I permanantly bricked or is this a possible battery problem?
When you get into motorola recovery (holding the home button down until the android with triangle shows up), clear your cache and wipe data to factory. This might do the trick. You're just gonna have to add your google account again.
Sent from my DROIDX using XDA App
Yeah... I wiped the data and the cache a couple times...no luck. The device will not do anything unless its plugged in, so I am hoping its just the battery. I will find out later today!
Thanks for the support!
went to verizon. the rep said the last .340 update had corrupt files in it. they are overnighting a new phone at no charge!
thanks again for everyones help!
Hey,
Basically I flashed to gingerblur, but now I noticed that my atrix phone settings wont save. E.g. screen timeout has been the most noticeable one, constantly resetting.
Any advice on changing this.
Thanks
Kenneth has stated in the Gingerblur thread in the dev forum that its a known issue. I imagine the next release will correct it. For now, as long as you don't reboot your phone then whatever amount of time you set screen timeout for will work, but will revert back to 15 seconds upon reboot.
I have these problems with gingerblur if anyone can help:
Dont save settings like mentioned above
Home and search buttons does not work ( vibrates but dont do nothing)
Any lockscreen works, fingerprint, pattern, numerical, none, i press power button and i`m already on home screen unlocked, no matter if i had set up fingerprint + pattern + numerical...
kurogana.inc said:
I have these problems with gingerblur if anyone can help:
Dont save settings like mentioned above
Home and search buttons does not work ( vibrates but dont do nothing)
Any lockscreen works, fingerprint, pattern, numerical, none, i press power button and i`m already on home screen unlocked, no matter if i had set up fingerprint + pattern + numerical...
Click to expand...
Click to collapse
reboot sticks the screentimeout for me sometimes (mines is 1 minute). sometimes it reverts, sometimes it sticks, kinda strange, but yeah, that's a known bug.
everything else works fine that you mentioned above.
You made sure to flash to 1.83 first then install Gingerblur 3 correct?
It may be how you went about updating your firmware and Gingerblur.
You didn't specifically say what versions you were running. I just updated to 1.83 SBF and went to Gingerblur 3.0 with no problems at all, was previously on 1.57 and GB 2.5.
Heres what I did:
Use RSD Lite to flash back to 1.26 SBF
Get 1.57 update OTA by checking for updates on your phone
Use RSD Lite to flash the 1.83 SBF
Use ADB to install Gingerbreak and attain root
Use ADB to install CWM and then install Gingerblur 3.0
The only issue I've run in to doing it this way was the previously mentioned screen timeout not saving, but as my phone is never off and only reboot after flashing a new SBF/ROM it doesn't affect me much.
Hope this helps.
hondapower said:
It may be how you went about updating your firmware and Gingerblur.
You didn't specifically say what versions you were running. I just updated to 1.83 SBF and went to Gingerblur 3.0 with no problems at all, was previously on 1.57 and GB 2.5.
Heres what I did:
Use RSD Lite to flash back to 1.26 SBF
Get 1.57 update OTA by checking for updates on your phone
Use RSD Lite to flash the 1.83 SBF
Use ADB to install Gingerbreak and attain root
Use ADB to install CWM and then install Gingerblur 3.0
The only issue I've run in to doing it this way was the previously mentioned screen timeout not saving, but as my phone is never off and only reboot after flashing a new SBF/ROM it doesn't affect me much.
Hope this helps.
Click to expand...
Click to collapse
Why not RSD right to 1.83 from 1.26? Doesn't 1.83 SBF contain all 1.57 changes?
Yea going too 1.26 then updating than flashing was all wasted time since 1.86 is everything all in one.
Sent from my MB860 using XDA Premium App
Only issue for me is screen timer after reboot. That's definitely ok given the benefits if GingerBlur.
Sent from WinBorg 4G using XDA Premium App
Ok guys, I have a good one for you. Tuesday I SBF'd my phone from my version of the .340 build to the factory VRZ_MB810_2.3.34_1FF_01 build that's on here. Reasoning was that I wanted to play with the OTA update to 2.3 and I was rooted and running Rubix 2.0 on it at the time.
That went fine and the OTA went without a hitch as well.
Now comes the fun part. Being the tinkerer that I am, I decided that I couldn't live without root access so I decided today that I would just SBF back to the VRZ_MB810_2.3.34_1FF_01 build and I was going to flash P3Droid's rooted GB release.
So I ran RSD, located my sbf file just I like I had, put the phone into bootloader (30.04 didn't change with the update) Let th SBF do it's work and now I'm bootlooping...
I wondered if this was just a Windows issue because I had to SBF a few times the other day just to get it to work. With that in mind, I exited my Windows virtual machine and tried it on my Linux box but to no avail.
I'm running out of options here...
Ideas?
Laramie1997 said:
Ok guys, I have a good one for you. Tuesday I SBF'd my phone from my version of the .340 build to the factory VRZ_MB810_2.3.34_1FF_01 build that's on here. Reasoning was that I wanted to play with the OTA update to 2.3 and I was rooted and running Rubix 2.0 on it at the time.
That went fine and the OTA went without a hitch as well.
Now comes the fun part. Being the tinkerer that I am, I decided that I couldn't live without root access so I decided today that I would just SBF back to the VRZ_MB810_2.3.34_1FF_01 build and I was going to flash P3Droid's rooted GB release.
So I ran RSD, located my sbf file just I like I had, put the phone into bootloader (30.04 didn't change with the update) Let th SBF do it's work and now I'm bootlooping...
I wondered if this was just a Windows issue because I had to SBF a few times the other day just to get it to work. With that in mind, I exited my Windows virtual machine and tried it on my Linux box but to no avail.
I'm running out of options here...
Ideas?
Click to expand...
Click to collapse
Boot into stock recovery and do a factory reset...
Sent from my DROIDX using XDA App
Nope, can't do that. There isn't a recovery to go back to. I don't have clockworks on this phone anymore.
Laramie1997 said:
Nope, can't do that. There isn't a recovery to go back to. I don't have clockworks on this phone anymore.
Click to expand...
Click to collapse
Its stock recovery...power off phone and then hold power and home button until you get the Android with the exclamation point. Then hit the search button
Sent from my DROIDX using XDA App
That wasn't quite what I was looking for since I don't have /sdcard/update.zip still on the card anymore. What IT DID allow me to get in and do was wipe cache which allowed a clean SBF.
THANKS!
So I've been running MIUI 1.8.whatever for a few weeks and finally realized there hadn't been an update in a while. After discovering MIUI move into the 1.9.Xs I downloaded 1.9.16 and proceeded to update via CWM. While updating it told me 1.9.16 runs off the Gingerbread kernel. At that point I got worried since I had been running the Froyo kernel since I rooted my DX.
After the update I told it to reboot and now it gets stuck at the white M logo. I can boot into regular recovery but I CANNOT get my phone to boot into CWM recovery so I can run the backup!
I've tried every button combination with no luck. i've booted into regular recovery and selected reboot having read that it will boot back into CWM recovery. Needless to say that didn't work either. And lastly I tried running RSDLite to SBF the phone to .602 but since the phone can't fully boot up RSDLite doesn't see the phone.
That is where I am at and I seek the help and guidance of you much smarter folks to help me get my phone at minimum to CWM recovery.
PLEASE HELP!!!
Boot the phone into bootloader mode, then SBF.
Sent from my DROIDX using XDA App
I got it into bootloader mode now, but my computer isn't finding the OMAP drivers and the installation keeps failing. How can I get these drivers onto my computer? RSD isn't seeing the phone even in bootloader so these drivers seem to be the key.
You can find the drivers in this thread:
http://forum.xda-developers.com/showthread.php?t=1258599
Sent from my DROIDX using XDA App
I got RSDLite to see the phone. Now when I try to flash it, it makes it all the way to checking the checksums (which all pass) then tries to switch the phone to BP passthrough. It keeps failing to switch the phone to BP passthrough and now my phone will only boot to the Bootloader screen and says Code Corrupt. It'll let me run the flash again but RSDLite keeps failing at that BP passthrough switch.
Thats where i'm at now.
Try a different SBF file. I had problems like this when i tried to SBF once, but once I found the SBF file that works for me, its always worked since. (I've had to SBF like 6 times now haha)
will find an older sbf file and try that. Wil let you know.
Alright we've made progress! I was able to finally get the phone SBF'd to .602. Then I rocked the Pete's Droid Rooting program and all seemed to have gone smoothly... Except I cannot boot into CWM recovery at all! I've ensured ROM Manager has the correct flash for CWM installed, but when I click Reboot into CWM Recovery, it'll reboot normally. So I turned the phone off and held the Home + Power button to boot into regular recovery. I get the ! logo with the green android, but when I hit hte Search button nothing happens.
So now I'm rooted, but can't get to CWM Recovery to install ROMS.
What do you guys think?
Yeah, Reboot into Recovery from ROM Manager doesn't work for me usually either...in fact, I had to go into the Bootstrapper app, install the recovery again, and then hit Reboot Recovery. This is on Apex though, but can't hurt to try it.
Yea I finally got it figured out. Its been so long since I originally rooted my phone I forgot all about D2Bootstrapper. And I didn't read the how-to guide for updating to MIUI 1.9.16 so that was all on me.
I've been running Liberty on my Droid X for some time now and love it compared to the stock Blur interface. But it's gotten to the point where I'd like to update from Froyo to one of the more modern versions and see if that can liven up the phone again. So my question is this - from what I've read before I can update Liberty (or any other ROM for that matter) from a Froyo based version I need to restore the phone to a semi-stock state, update via an official OTA release, re-root and go from there. Is that true? If so, any convenient guide on how to do so? I did a bit of searching and couldn't find much and while I'm pretty technically inclined my skills do not extend into the phone region and back when I originally modified the phone there were many handy guides and videos to walk me through it.
Any help would be greatly appreciated.
Nate
If your bootloader version is 30.04, SBF to 4.5.602. From there you can flash any Gingerbread or ICS rom of your choice.
If your bootloader version is 30.03, SBF to 2.3.15 and take the OTA update.
Sent from my Transformer TF101 using Tapatalk
Let the stupid questions begin...
Ok, I confirmed that I'm running 30.04 and I found a site that maintains the correct 4.5.602 file so I downloaded that. Is there anything that I need to back up before installing? Also, I read that a special program is required to install the SBF files so any assistance there would be appreciated as well.
Thanks!
Ok, so I managed to track down RSD-Lite and got it to recognize the device and start loading the sbf file however the phone couldn't get past the "manually power up the phone" phase (or something like that). It just kept showing the boot animation over and over again regardless of what I did - it would cycle between the red eye and the DROID text. I tried pushing and holding the power button, no good and none of the other buttons did anything either. Nothing worked. So I'm rerunning it again and we'll see if the second time is a charm...
Well crap, I got through the SBF install process and got the pass message from RSD but now my phone is stuck at the animation and won't go any further. I've left it running for the better part of 10 minutes and it just hangs. I'm now performing a manual factory data wipe to see if that will help.
EDIT: It appears that the factory data wipe got me through the locked animation. Still having minor issues getting through the programing and setup phase but I think it'll work eventually.
Thanks again for the help.
infazzdar said:
If your bootloader version is 30.04, SBF to 4.5.602. From there you can flash any Gingerbread or ICS rom of your choice.
If your bootloader version is 30.03, SBF to 2.3.15 and take the OTA update.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Minor question/problem for you, sir.
Wouldn't the OTA take you all the way to .621?
Wonderful...yet another thing we need to worry about that damn update <_<
OP:
Glad you got it worked out.
Well, it's sort of worked out.
Everything is up and running but ROM Toolbox isn't able to load any ROMs. It gets granted Superuser permission so I'm pretty sure that I've got the X rooted correctly but when it tries to boot into Clockwork it appears to get an error (icon with an exclamation point) and reboots into the regular Blur interface. I'm going to have a go at loading something like Liberty Gingerbread or 3.0 via zip file but it makes me nervous that the Toolbox Pro App can't get this done.
After determining that the Toolbox App was not booting into Clockwork I downloaded and installed the Droid X Bootstrapper App and got that running. It was able to correctly boot into recovery from which allowed me to install the Liberty 3 ROM. I'm now going back through the process of setting the phone up with the new ROM so we'll see how that goes. It appears to be working, but only time will tell if it's stable. One thing is for sure, a few hours on Blur'd Gingerbread and I was ready for something else again.
Jubakuba said:
Minor question/problem for you, sir.
Wouldn't the OTA take you all the way to .621?
Wonderful...yet another thing we need to worry about that damn update <_<
OP:
Glad you got it worked out.
Click to expand...
Click to collapse
I was actually wondering whether it would or not, but I can't think of another way to update the bootloader.
Sent from my DROIDX using Tapatalk
Ok, so here's an issue that I'd appreciate some guidance on. After installing Liberty 3.0 it appears as if the phone can't fully charge. It was plugged in for 10hrs last night and yet this morning the battery only reads 61%. I don't know if it would be best to boot into recovery and wipe the battery stats not knowing if it's fully charged or not.
Thoughts?