Related
I am having problem updating to 2.340.
I just got a replacement DX from Verizon few days ago. As soon as I received it, I tried to do an update but the system said that I was up to date even though my software showed 2.315 so I decided to mod my DX right away since most people did not have problem updating with rooted DX.
Initially, I rooted my phone with Z4ROOT, reinstalled all the apps using Titanium Backup which i had on previous phone since I all the backups on my
SD card than I back up the stock ROM with Rom Manager. After that, I installed Bazinga2.1 Rom. Installed my apps again using titanium back up and back it up again using ROM Manager. After this, I installed BigDX blue theme. Couple a days ago, I got a notification that I have an update from Verizon which was 2.34 so I went back to recovery, restored back the Stock, using Z4Root, unrooted and download the 2.34 update and tried to install but the update failed. So I did a factory reset and put every thing back to stock and tried to update again and it still fails.
Once the update is down loaded, I try to install and its turns off the phone, than it shows a box with android next to it and it shows triangle with Exclamation and just reboots. Than it goes to clockwork mod recovery.
Why does my phone go to clockwork recovery even though I am UNROOTED?
Any help or input will be greatly appreciate it.
Thanks
johann718 said:
I am having problem updating to 2.340.
I just got a replacement DX from Verizon few days ago. As soon as I received it, I tried to do an update but the system said that I was up to date even though my software showed 2.315 so I decided to mod my DX right away since most people did not have problem updating with rooted DX.
Initially, I rooted my phone with Z4ROOT, reinstalled all the apps using Titanium Backup which i had on previous phone since I all the backups on my
SD card than I back up the stock ROM with Rom Manager. After that, I installed Bazinga2.1 Rom. Installed my apps again using titanium back up and back it up again using ROM Manager. After this, I installed BigDX blue theme. Couple a days ago, I got a notification that I have an update from Verizon which was 2.34 so I went back to recovery, restored back the Stock, using Z4Root, unrooted and download the 2.34 update and tried to install but the update failed. So I did a factory reset and put every thing back to stock and tried to update again and it still fails.
Once the update is down loaded, I try to install and its turns off the phone, than it shows a box with android next to it and it shows triangle with Exclamation and just reboots. Than it goes to clockwork mod recovery.
Why does my phone go to clockwork recovery even though I am UNROOTED?
Any help or input will be greatly appreciate it.
Thanks
Click to expand...
Click to collapse
Root and the bootstrapper are separate entities. Removing root, and removing the boostrapper manually (by renaming files in the system) will not fix your issue either.
The reason I know this is because I went through a number of ways to try to get the OTA, but could not.
I would suggest you hit MDW and get all of the latest files for the update, and do it that way.
You'll sbf, flash the leak for .320, then sbf .320, then flash the system for .340, then update the kernel, and radio afterwards. After that, you'll be back on the normal track.
It's a lot of steps, I guess, but it really doesn't take long.
Go grab the files ASAP, in case they get pulled, and follow all of the instructions carefully.
Whats MDW and why am I having this problem when everyone else is not. also, I removed Boostraper and it still go into recoverymod? I am just going to SBF reflash to 2.315 and see if it will work.
Here we go again!!!
Lots of people had that issue.
Mdw is mydroidworld.com
Sbf all you like. I stand behind the advice I gave.
Also, if you had actually removed the bootstrap correctly, you couldn't possibly still end up in clockwork.
Either way, in about the time it took you to post, you could have used the steps I suggested and have been done.
Sent from my DROIDX using Tapatalk
I'm in a bit of a hurry so I haven't read the whole thread thoroughly, but if you're just trying to get it to stop booting into CWM, go to terminal emulator
Run "su"
Run "mount -o remount,rw /dev/block/mmcblk1p21 /system"
Run "cp /system/bin/logwrapper.bin /system/bin/logwrapper"
Reboot
bladebarrier said:
Lots of people had that issue.
Mdw is mydroidworld.com
Sbf all you like. I stand behind the advice I gave.
Also, if you had actually removed the bootstrap correctly, you couldn't possibly still end up in clockwork.
Either way, in about the time it took you to post, you could have used the steps I suggested and have been done.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Thanks for the advice but I SBF my phone back to 2.315, than tried to do update again and it worked.
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!
Ok so as my previous post stated I just got my droid x and rooted it. I am in the process of installing a rom but have failed at this point.
For starters I have the droid x bootstrap installed and "running". Buy "running" I mean I can get to the clockwork recovery but only buy the bootstrap button or battery pull for 1min then boot. Booting while holding the home button stops at the exclamation android guy. I cant get past it no matter how hard I push the search button . So thats one of my problems but not a big one.
When I went to install liberty 1.5 I did a data factory reset and catch wipe then installed the rom. It got stuck on the liberty logo. So I tried again this time following the guide on these forms on how to install a rom correctly. Same thing. I tried three more times following three different guides and still was stuck at the liberty logo. So I gave up and followed the install guide on these forms again, but just restored from my backup. I am good and running again but I still have the liberty logo, which from what I read is normal.
When I got home from work I started digging into why it didn't work and found several things that may cause it. Now this is where I get lost. I have read the sometimes it just fails and you need to try again. But I also read the doing a SBF will also fix this. So I dug into what a SBF is and how to do it since this seams to be the #1 fix for everything. WHAT, UHH, MMMMM, K. So I read you will need to flash 2 files to SBF successfully. I have no problems with the RSD lite as it is only one file and you cant screw that up. But then I comes to choosing the right SBF file for your phone I get lost. All the versions listed are WAY below what I have. I am currently on 4.5.588. So I jumped over to androidforms to see if theirs anything their. They list x.x.596 as the most recent OTA but when I go to check for updates it says there are none.
SO, my questions are:
Is the reason I cant flash the liberty rom because I am running 4.5.588?
What do I flash if I need to SBF?
What am I missing about this OTA update? Is it being rolled out now or is my rom the most recent OTA?
Is their anything else I need to know that might help me in the future? Like I said I am new to this area of the forms and have not clew whats being released, changed, rooted, or what ever else.
I came from a rooted eris so Im not root dumb. But their is a big difference between the eris and the X.
ANY HELP WOULD BE AWESOME THANKS!!!!!!!!
BrownEye02 said:
Ok so as my previous post stated I just got my droid x and rooted it. I am in the process of installing a rom but have failed at this point.
For starters I have the droid x bootstrap installed and "running". Buy "running" I mean I can get to the clockwork recovery but only buy the bootstrap button or battery pull for 1min then boot. Booting while holding the home button stops at the exclamation android guy. I cant get past it no matter how hard I push the search button . So thats one of my problems but not a big one.
When I went to install liberty 1.5 I did a data factory reset and catch wipe then installed the rom. It got stuck on the liberty logo. So I tried again this time following the guide on these forms on how to install a rom correctly. Same thing. I tried three more times following three different guides and still was stuck at the liberty logo. So I gave up and followed the install guide on these forms again, but just restored from my backup. I am good and running again but I still have the liberty logo, which from what I read is normal.
When I got home from work I started digging into why it didn't work and found several things that may cause it. Now this is where I get lost. I have read the sometimes it just fails and you need to try again. But I also read the doing a SBF will also fix this. So I dug into what a SBF is and how to do it since this seams to be the #1 fix for everything. WHAT, UHH, MMMMM, K. So I read you will need to flash 2 files to SBF successfully. I have no problems with the RSD lite as it is only one file and you cant screw that up. But then I comes to choosing the right SBF file for your phone I get lost. All the versions listed are WAY below what I have. I am currently on 4.5.588. So I jumped over to androidforms to see if theirs anything their. They list x.x.596 as the most recent OTA but when I go to check for updates it says there are none.
SO, my questions are:
Is the reason I cant flash the liberty rom because I am running 4.5.588?
What do I flash if I need to SBF?
What am I missing about this OTA update? Is it being rolled out now or is my rom the most recent OTA?
Is their anything else I need to know that might help me in the future? Like I said I am new to this area of the forms and have not clew whats being released, changed, rooted, or what ever else.
I came from a rooted eris so Im not root dumb. But their is a big difference between the eris and the X.
ANY HELP WOULD BE AWESOME THANKS!!!!!!!!
Click to expand...
Click to collapse
im no pro but hopefully this info will help you, it did me.
http://forum.xda-developers.com/showthread.php?t=1073841 liberty info
http://forum.xda-developers.com/showthread.php?t=1085323 sbf'ing
The new 2.3.3 OTA is stable and very nice looking on my DX, OTA not rootable yet but give it time.
Biggest life saver about the DX is the the part of the phone that ppl mess up and turn their phones to bricks is extremely safe on the X, not bulletproof but all the info in these forums I believe can bring them back regardless of what happens. I was very overwhelmed at first with my X but very comfortable now that ive successfully managed the sbf.
Yeah that's one of the things I really noticed. If you brick your phone it seams its not the end. So im still a little confused with your explanation on SBFing. You say that 2.3.3 is the latest OTA but its not rootable. So am I looking at the wrong number when I say my version is 4.5.588.
Sent from my Rooted DROIDX.
Reading the noobs guide to droid x allowed me to figure out that I have the 30.04 bootloader and I will need to flash the 2.3.34 file. But I would still like to know why my version is so much higher then 2.3.34.
By far, this is the easiest way to sbf back to stock froyo
http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
Sent from my Xoom using XDA Premium App
chbennett said:
By far, this is the easiest way to sbf back to stock froyo
http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
WOW that is easy. To bad you cant select what version it flashes. But still EASY. Ill keep that in mind if I need to SBF. THANKS!
http://droidmodderx.wordpress.com/how-to-sbf-your-droid-x-full-2-3-340/
Good video tutorial there... It also has files there as well
Sent from my DROIDX using XDA App
Well I gave liberty 1.5 another try and it still got stuck on the liberty screen. Any ideas?
Sent from my Rooted DROIDX.
Was able to flash the liberty gingerbread rom tonight! I am kind of wondering if the version of ota/bootloader I have is the reason liberty 1.5 wouldn't work for me.
BrownEye02 said:
Reading the noobs guide to droid x allowed me to figure out that I have the 30.04 bootloader and I will need to flash the 2.3.34 file. But I would still like to know why my version is so much higher then 2.3.34.
Click to expand...
Click to collapse
your looking at the version of the software build, complete jargon here but say your on android 2.2.1 version blah blah blah, what i was referring to was although you may have a higher version of 2.2.1 than what you are reading, a lower version of a higher android software such as 2.3.3 is better than a higher version of 2.2.1 same page?
So this is a total longshot...but I have an R2 that's running stock D2 Froyo (because I'm an idiot and lost R2 Froyo), which has been fine, but now that the R2 GB has been released I'd like to get back where I need to be.
I know there's still no R2 SBF, but is there any other way to get my phone to recognize the R2 update?
I assume the OTA is based on the build.prop, and not the MEID or I'd be able to pull it already. Can I modify my build.prop to match the R2's, and then Blur will pull the correct OTA? Any other ideas? Thanks.....
If you search you'll find a nandroid for the r2. I used that to recover my wife's and then push the update. I'm at work or I would post the link
Sent from my DROID2 GLOBAL using Tapatalk
abalsor said:
If you search you'll find a nandroid for the r2. I used that to recover my wife's and then push the update. I'm at work or I would post the link
Sent from my DROID2 GLOBAL using Tapatalk
Click to expand...
Click to collapse
I guess I'm useless, lol....I've been searching for two hours and can't find an R2 nandroid? Do you remember where it was?
I'm in a similar boat. I rooted my R2-D2 for a while and then un-rooted it. Now I can not apply OTA Gingerbread update. I'm trying to find the R2-D2 SBF as well, but it seems that the majority of the links that I find are no longer up. As well as IIRC, in order to apply the OTA update from VZW, the entire phone has to be running stock, including the boot loader. This means no Nandroid or CWM.
I too have had no luck in finding a R2D2 Rom/SBF download that works.
I was running the leaked GB on my R2 since May and now cant get official. I SBF'd to stock D2 2.2 and flashed a backup i made with clockwork but i guess something isnt right because it only gets about 25% of unpacking the update before it stops and says it failed. I download some bloatware and put it back in the system folder and then unrooted with z4root.
I guess ill just sit here in the boat with you guys.
Is z4root the one click root method? If so, that's what I used and used only. I never flashed a different ROM on my R2-D2. My guess is is that the one-click root modified some other files that are interfering with the OTA update. Just my $0.02.
I think to successfully get the OTA update from VZW, RSDLite and an SBF will be needed. IIRC, for an OTA update to work from VZW, the boot loader can not be modified (no CWM or Nandroid).
Well my bootloader is now on 2.37 not 2.35 because i SBF'd to stock 2.2. if this is true that i cant update than this really bites.
Stock 2.2 for R2-D2 or D2? Two different builds there. R2-D2 GB build will not load if you're running a D2 ROM on your R2-D2. Clear as mud?
I was running stock R2D2 2.2, i SBF'd to stock D2 2.2, i installed leaked D2 2.3, now i SBF'd back to Stock D2 2.2, flashed R2D2 2.2 backup.
chasehammer said:
I was running stock R2D2 2.2, i SBF'd to stock D2 2.2, i installed leaked D2 2.3, now i SBF'd back to Stock D2 2.2, flashed R2D2 2.2 backup.
Click to expand...
Click to collapse
That's exactly what I did....except somewhere along the way I lost my R2 backup. I've been looking all day, but I can't find a stock R2 nandroid that abalsor mentioned anywhere.
My original thought was trying to figure out how to trick Blur into pulling the R2 update, even though I'm running the D2 software. I know they're different releases, but it's the only other option I can think of. It seems like updates should be based on your MEID, but obviously they're not. Do you think it's just the bootloader? I wonder if there's a bootloader SBF out there I could flash then?
I guess I'm just grasping at straws, I even tried calling Motorola to see if they'd push the R2 GB update manually, (if they even can?), but they told me there is no R2 update....
ive pretty much given up at this point. Only option is what you said go back to stock Droid 2 and pull the update but would lose R2D2 stuff. I guess better than nothing. Every forums ive asked no one responds or make stupid comments like "someone actually has a R2D2?"
and dont ask Verizon or Motorola, you wont get anywhere.
Do you think VZW has an SBF?
Hypothetically speaking, if my phone was to be stuck in a boot loop, and I took it to a VZW store, I wonder if they could/would re-flash it?
Hypothetically, of course......
sorry it took a while to get back to you. I've been trying to get my wifes r2d2 to take the GB update. here is the link R2D2 nandroid backup..
Do a standard nandroi recovery with the file. You'll have to start the phone in safe mode ( hold ok button and power up , hold till r2 goes away ) and then start the DL . It may take a while between the download and the install but it worked for me...
abalsor said:
sorry it took a while to get back to you. I've been trying to get my wifes r2d2 to take the GB update. here is the link R2D2 nandroid backup..
Do a standard nandroi recovery with the file. You'll have to start the phone in safe mode ( hold ok button and power up , hold till r2 goes away ) and then start the DL . It may take a while between the download and the install but it worked for me...
Click to expand...
Click to collapse
DUDE YOU ARE AWESOME! The download got me back to stock. However i got into Safe Mode by holding OK down while booting but when i check for Updates it says "Check for update was not available at this time. Try again later." how did you get the update to download?
abalsor said:
sorry it took a while to get back to you. I've been trying to get my wifes r2d2 to take the GB update. here is the link R2D2 nandroid backup..
Do a standard nandroi recovery with the file. You'll have to start the phone in safe mode ( hold ok button and power up , hold till r2 goes away ) and then start the DL . It may take a while between the download and the install but it worked for me...
Click to expand...
Click to collapse
Just to confirm, this is the stock Froyo nandroid, not the GB nandroid, right? After restoring this nandroid still need to do the upgrade?
ehrune said:
Just to confirm, this is the stock Froyo nandroid, not the GB nandroid, right? After restoring this nandroid still need to do the upgrade?
Click to expand...
Click to collapse
this is the stock froyo nandroid.. and i did the update the same way as before just pulling it from the about phone tab...
Thanks!!! You're gonna have about a million new friends....well, maybe not quite that many.
I used Z4 to unroot, and got it to recognize/download the update, but it keeps failing. I'm assuming because of the bootstrap? When it reboots it goes into clockworkmod....did you mess with that at all, or did you not bootstrap?
Seriously though, thanks again for posting this.
unfortunately this did not work
it flashed but still would not update. I noticed it still had Superuser, Root Explorer and others. But still fails at the same point as before.
Tried factory reset, booting into recovery and wiping data/cache, rooting/unrooting, even deleting the Superuser.apk.....still gets about 1/4 of the way through installation before it reboots and says "Installation Failed". Same for everyone else?
At least I'm on the right version now though....
not sure why the updates failed. I only flashed this nandroid and did the update. I did see it was rooted before i did so. Sorry guys, wish i knew more...
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?