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?
Related
I bought a DX earlier this week. It was updated to system 2.3.340 before i left the store. I also have a D2 and experience flashing ROMs and SBFing. What is puzzling me here is that no matter what ROM I install i get random reboots. This happens no matter what apps, activities, etc... i am doing, even when just idle, i will look down and phone is rebooting. I haven't tried SBFing the DX yet because i can't find a clear answer on how i need to do it. I know that a full .340 SBF does not exist yet. I have a full .32 SBF file and a system only .340 file. I am assuming that i would flash the .32 full, then the .340, or could i just flash the .32 and then let the phone update the factory way to .340? I am getting this reboot problem with Rubix 1.9.5, Fission 2.4.3, and GummyJar 2.5. Any advice, input, or help would be greatly appreciated. THanks in asvance.
willjohnson said:
I bought a DX earlier this week. It was updated to system 2.3.340 before i left the store. I also have a D2 and experience flashing ROMs and SBFing. What is puzzling me here is that no matter what ROM I install i get random reboots. This happens no matter what apps, activities, etc... i am doing, even when just idle, i will look down and phone is rebooting. I haven't tried SBFing the DX yet because i can't find a clear answer on how i need to do it. I know that a full .340 SBF does not exist yet. I have a full .32 SBF file and a system only .340 file. I am assuming that i would flash the .32 full, then the .340, or could i just flash the .32 and then let the phone update the factory way to .340? I am getting this reboot problem with Rubix 1.9.5, Fission 2.4.3, and GummyJar 2.5. Any advice, input, or help would be greatly appreciated. THanks in asvance.
Click to expand...
Click to collapse
try here http://rootzwiki.com/index.php/Smartphones/Motorola/Droid-X/Droid-X.html#comment220 scroll down towards the end (idk if you use windows or linux but the linux method of sbf'ing is alot easier ive used both) except in their directions it says an older sbf file just insert the one you have, then go here http://www.mydroidworld.com/forums/...ystem-baseband-2-3-340-kernel-bootloader.html to download these zip files for kernel updater, 340 system update your baseband and bootloader should already be the correct ones, (i recently bought my X too) then once you finally root your newly sbf'd X and installed droid x bootstrap etc and get into clockwork mod recovery you can flash those 2 zips (recommend flashing only one at a time, reboot, and do the next) and then you should be updated to full .340
gl
http://forum.xda-developers.com/showthread.php?t=869007
heres a thread with discussion about those update zips
Thanks for the quick replies. Gonna try your suggestion tonight or tomorrow. Now i get random lock ups followed by a boot after about five minutes. The only upside right now is that its 4 days old so if i can get some resemblance of factory back on it then i can just exchange it Thanks again will report back with results.
And also by "insert the file you have", i assume you mean the file i have that is VRZ_MB810_2.3.32_01.sbf is the file i need to use in RSD Lite, then update the other files with clockwork recovery?
Thanks again.
willjohnson said:
And also by "insert the file you have", i assume you mean the file i have that is VRZ_MB810_2.3.32_01.sbf is the file i need to use in RSD Lite, then update the other files with clockwork recovery?
Thanks again.
Click to expand...
Click to collapse
correct tho the one i used had was labeled VRZ_MB810_2.3.32_1FF_01.sbf
I guess the one i got is ok? it came from the TBH app from the market? I would like to get ahold of the one you got too if thats possible, since you know that file works.
LOL i am a dumbass, left the FF part out for somereason, thats the exact file name i have. Thanks again.\
Edit- Just tried this, i don't know whats wrong but it has the start button in RSD Lite greyed out when i select the file, its the exact one listed above. Gonna try same file from different locations
Ok, so now i am starting to worry. Tried 3 different .320 full sbf's. All the same result. Failed process close to the begging. Then on the phone it says
Critical Error
FEBE
0047
Please Helppppp. I don't need a really expensive paperweight, all i need to do is get it so that GummyJar doesn't show on boot and i can take it back, its brand new.
Try removing the battery. Then boot into recovery (volume down + power) then do a factory reset/restore.
Sent from my ADR6300 using XDA App
Tried that, i finally got it to flash, i had the phone in the desk dock, didn't think about it. Once i plugged it into the usb cable direct everything went fine(so far). Also i noticed that with this phone and my wifes D2, i have to put a (1) at the end of the sbf file name to get RSD Lite to use it, otherwise the start button stays greyed out. THanks for the replies and help, will post again if there are any more problems.
willjohnson said:
Tried that, i finally got it to flash, i had the phone in the desk dock, didn't think about it. Once i plugged it into the usb cable direct everything went fine(so far). Also i noticed that with this phone and my wifes D2, i have to put a (1) at the end of the sbf file name to get RSD Lite to use it, otherwise the start button stays greyed out. THanks for the replies and help, will post again if there are any more problems.
Click to expand...
Click to collapse
ive heard there are several problems with rsd lol thats why ive stuck with my ubuntu/Linux its 10x easier
willjohnson said:
I guess the one i got is ok? it came from the TBH app from the market? I would like to get ahold of the one you got too if thats possible, since you know that file works.
LOL i am a dumbass, left the FF part out for somereason, thats the exact file name i have. Thanks again.\
Edit- Just tried this, i don't know whats wrong but it has the start button in RSD Lite greyed out when i select the file, its the exact one listed above. Gonna try same file from different locations
Click to expand...
Click to collapse
i also believe you DO have to have it all in specific locations but idk i use linux to do it, if you continue to play with the X after u get new one i would read up on how to dual boot ubuntu its a whole lot easier once you find ur way around i have it booting off of a 1TB external hard drive no need to install the correct moto drives etc..just plain easy lol
Finally total success!!!! Flashed .320 Full SBF, then used the Kernel and System updates you referenced and bam, back to stock. Now i feel better about ROM flashing, cause i can recover from most anything with this process. THanks again for your help and info.
willjohnson said:
Finally total success!!!! Flashed .320 Full SBF, then used the Kernel and System updates you referenced and bam, back to stock. Now i feel better about ROM flashing, cause i can recover from most anything with this process. THanks again for your help and info.
Click to expand...
Click to collapse
it only takes once correctly doing it to feel comfortable lol also make sure using droid x bootstrap recovery make sure to tap the first choice and let it do its thing, otherwise it will constantly reboot to recovery EVERY time you turn it back on
Well... the SBF and updating where successful. But even after the SBF, SD Card Formating(Long format in windows, then 3 times on phone to be sure), clean install and download of all Fission stuff i normally use, still get random reboots. Gonna SBF again and try Rubix and see how that goes. If it still has problems too, i may SBF again and go to the store and return phone for a new one.
willjohnson said:
Well... the SBF and updating where successful. But even after the SBF, SD Card Formating(Long format in windows, then 3 times on phone to be sure), clean install and download of all Fission stuff i normally use, still get random reboots. Gonna SBF again and try Rubix and see how that goes. If it still has problems too, i may SBF again and go to the store and return phone for a new one.
Click to expand...
Click to collapse
try something blurless like darkslide, which im currently running, no random reboots
Funnyface19 said:
try something blurless like darkslide, which im currently running, no random reboots
Click to expand...
Click to collapse
LOL funny you should mention, thats what i actually decided to go with instead. It really looks great, seems to be seemless too. Since you use it maybe you could tell me... Can you overclock? I downloaded the blurless version from their link and it has the blur alarm clock and a few others? is this right or is something wrong with the link? Thanks again.
willjohnson said:
LOL funny you should mention, thats what i actually decided to go with instead. It really looks great, seems to be seemless too. Since you use it maybe you could tell me... Can you overclock? I downloaded the blurless version from their link and it has the blur alarm clock and a few others? is this right or is something wrong with the link? Thanks again.
Click to expand...
Click to collapse
Well I haven't overclocked yet anyway the phone gets hot enuf lol plus coming from an Eris 1k is fast lol
Um yeah it should be wright depends on what the blur clock looks like lol
Sent from my DROIDX using XDA App
I looked back at there post in another forum and it actually says that they added a few Blur parts in the blurless rom. I guess some blur things just work better.
willjohnson said:
I looked back at there post in another forum and it actually says that they added a few Blur parts in the blurless rom. I guess some blur things just work better.
Click to expand...
Click to collapse
yeah but the obsidian rom is completely blurless just not everything working
Running DarkSlide4.1 can't tell u last I had a reboot
Sent from my DROIDX using XDA App
I had the Liberty 1.5 ROM on my Droid Rooted with Rom Manager Clock Work recovery and everything was fine until..
I found a file on the web called Monster_D2_2.3.2_4.5.153 I used Clock Work recovery and installed it.
Now my phone says I have Android Version 2.3.3 Build Number STAB
Kernal Version: 2.6.32.9-gd72dc5da20523
It's running fine but I have lost ClockWork Recovery. I can not root the phone after trying several different methods. I can not install anything on it with its stock recovery without getting a signiture failure in the stock recovery and worst of all I can not uninstall it or overwrite it with anything I have loaded on the SD card.
I would be happy to remove this build and re-install Liberty.
I would be even more happy If I could just get this rooted and have my clockwork recovery back.
can anyone help me by pointing me to a thread or link that can help?
Thanks SO much
Gingerbread Dead :0
The problem is that there isn't a known process for rooting Gingerbread (except for installing a pre-rooted ROM)
SBF back to stock, and then you should be able to root, install clockworkmod, and then reinstall Liberty.
pcwebiz said:
I had the Liberty 1.5 ROM on my Droid Rooted with Rom Manager Clock Work recovery and everything was fine until..
I found a file on the web called Monster_D2_2.3.2_4.5.153 I used Clock Work recovery and installed it.
Now my phone says I have Android Version 2.3.3 Build Number STAB
Kernal Version: 2.6.32.9-gd72dc5da20523
It's running fine but I have lost ClockWork Recovery. I can not root the phone after trying several different methods. I can not install anything on it with its stock recovery without getting a signiture failure in the stock recovery and worst of all I can not uninstall it or overwrite it with anything I have loaded on the SD card.
I would be happy to remove this build and re-install Liberty.
I would be even more happy If I could just get this rooted and have my clockwork recovery back.
can anyone help me by pointing me to a thread or link that can help?
Thanks SO much
Gingerbread Dead :0
Click to expand...
Click to collapse
Yup, SBF is the way to go.
SBF Guide:
http://forum.xda-developers.com/showthread.php?t=770224 (be sure to use RSDlite 4.9)
SBF Download:
h t t p://www.mydroidworld.com/forums/droid-2-discussion/5323-tbh-mydroidworld-present-droid-2-2-3-20-triple-threat.html
If you made a backup of liberty before you installed 2.3.3, after you root and put clockwork on, you should be able to just restore it.
It's always good to do as much research as you can before trying anything like that.
I installed VRZ_A955_2.3.20_1FF_01.sbf
Then I was able to root the phone and use my root applications. The device is very slow and too sketchy to complete anyone task so it was a failure.
Now with your advice I should get back on the right track. Thank You very much for the response. I thought for a moment I might have to drop my phone on the pavement and go to phoneclaim dot com. But you cant learn anything taking the easy way out. lol I'll post the outcome.
pcwebiz said:
I installed VRZ_A955_2.3.20_1FF_01.sbf
Then I was able to root the phone and use my root applications. The device is very slow and too sketchy to complete anyone task so it was a failure.
Now with your advice I should get back on the right track. Thank You very much for the response. I thought for a moment I might have to drop my phone on the pavement and go to phoneclaim dot com. But you cant learn anything taking the easy way out. lol I'll post the outcome.
Click to expand...
Click to collapse
Yup, as long as you can get the phone into bootloader mode, the phone isn't bricked.
Hope everything works out!
Sent from my Liberated DROID 2
I've had that performance problem after SBF'ing as well. I think I cleared data and rebooted a couple times to address the issue...
Complete Recovery!
Thank You SO much!
I began having a black screen.after a few weeks on gingerbread so I decided to sbf back to froyo but it failed now my phone gives the MOTO logo and goes directly to a black screen. I can't get it into flash mode even with holding the arrow up key. I'm out of ideas here so I'm really hoping to find a way to get this working again without being worried that its truly bricked. Any help would be greatly appreciative.
Have you been able to boot into anything else, such as the stock recovery?
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 i was on liberty rom 2.0.1 and wanted to upgrade to the latest version in the nightlys. So i SBF back to version 2.3.320.MB810 and when i go to settings -> about phone -> systems update, it says i am already up to date. Can i get to gingerbread from this version or do i need to sbf to 2.3.340 to get to gingerbread.
I think you have to be on. 340, but I wouldn't encourage you to take the OTA to GB, download a prerooted .596 GB (team black hat...) then go from there.
Sent from my Xoom using XDA Premium App
So i sbf to .340 and tried to install the tbh .596 GB update, with the part1 and part 2 files. When i boot into recovery and try to apply the zip it give a error code of 7 during validation of the current system. According to the instructions the only thing i am not doing exactly is i am using the droid x boot straper not the droid 2. would that cause this. dont see the need to spend 3 bucks on something i already have
Try turning off USB Debugging prior to booting into recovery. I think I read somewhere that Droid X bootstrapper works fine as long as you do that first.
Ok so i hope someone can help me out on this i finally got to a TBH rooted GB install.
My next step is to get back on liberty because i just cant stand motoblur, gingerblut is a bit better than what came with froyo but it still sucks. the battery life is terrible and i cant stand all the bloat ware and crappy widgets.
I am not sure what issue i am having 3g data worked fine in liberty GB0.4 but if i ever moved past that it would stop working. So i spent a day and sbf to .340 then installed the TBH rooted stock GB. I then downloaded the libertyGB0.8 did a data wipe and installed it. No 3g data. I really love liberty have donated to them buying the pro toolbox and such. I really want to get back to liberty but i guess if i have to find a different rom i will . Anyone have any idea as to why if i go past liberty 0.4 i loose 3g?
Ok so this issue has expanded past just liberty. I tried to flash apex 2.0 rc1 with the same issue no 3g data. Phone calls and all of that work but no 3g data. i would really like some help with this dont want to get stuck on moto ginger. Will more than likely just go buy a different phone if i cant get this to work
You just need to flash the updated kernal. I had the same problem, and fixed it. let me see if I can find the thread with the info. All u need to do is download the zip file, put on sd card and flash. and itll work just fine. Ill look it up and post back. The 591_kernel_update.zip is what you need
Here is the file:
http://www.droidforums.net/forum/liberty-rom-dx/151857-no-3g-liberty-gb-0-7-a.html
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...