Will the monster .340 zip from TBH allow me to revert to Froyo after the OTA? I'm using wireless tether (I know, shut it) to TETHER TO MY XOOM instead of bluetooth. The bluetooth connection is just too unreliable. I get disconnects, hung downloads, slow innernets (lol), etc. So I use wireless tether. If the official GB doesn't solve my bluetooth tether woes, will this work? I've noticed it updates pretty much everything during the install, including the kernel.
if you dont get help here, go here
http://androidforums.com/droid-x-all-things-root/
It depends on whether or not the bootloader version is changed. If it is, well we're stuck on gb
To answer your question: no. I've tried and you just bootloop even with wipes and what not. Sbf is the only way (so far) to revert from gb to froyo.
Sent from my DROIDX using Tapatalk
I'm using the SBF-like-update.zip from TBH. I've used this on numerous occasions to go from .588 to stock. I just wasn't sure if it will work with the OTA. I believe the zip contains the boot logo, boot animation, kernel, mbm, cdrom, and software version.
Oh my bad I thought you were talking about maderstcok... But you won't be able to flash a zip on the ota until it's rooted.
Sent from my DROIDX using Tapatalk
Related
I was rooted using the one step rook but started having issues with my Windows & laptop not wanting to see my Epic conected to USB.
When I reverted back to stock it downloaded 2.2.1 so I have Froyo but need to be able to root off my sd card. I tried Z4Root but it did not get me rooted and I do not think it works for 2.2.1.
Any ideas on a another app I could root with?
Thanks
The .1 update to froyo was to close off the exploit z4root used, there are no other apps that root.
Did you flash back to dk28 stock or di18?
Sent from my SPH-D700 using Tapatalk
You mean you got froyo? The ota?
Sent from my SPH-D700 using XDA App
turn on adb and try this from your computer,
http://forum.xda-developers.com/showthread.php?t=803682
dont worry that the computer cant see you.
mattallica76 said:
Did you flash back to dk28 stock or di18?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I did the wipe/factory reset. I had updated to Froyo prior and reset trying to get my Usb to computer back
spent my two days off playing with my phone finally sucess.
Used odin and installed the dk28 tar with clockwork mod.
My wifi was acting like a crack addict...the shakes when I turned on wifi the phone would vibrat and reset.
Put the truly epic experiance latest and installed with the clockwork mod update picking this zip.
The USB is back and working. I am rooted. I can use my wifi tether.
God is great and I am back in business.....
So last night I used the flashable .zip to install HKTW 2.3.4 and then realized there was no fix for mobile data, at least not one that I can find to work. The data issue is the only reason I dont want the HKTW 2.3.4 right now, until I can flash it with fastboot. So, today, I restored back to 1.83 via CWM. Everything seemed to go great until my touch screen didnt work. I then had to flash back to the HKTW 2.3.4. Has anyone else had this problem? I would rather fix the data issue on 2.3.4 and run that if it is possible to fix the flashable .zip. If not, I would rather go back to 1.83. I dont have a PC that I can use right now, so any suggestions will have to be attempted completely on the phone. Also, I have the N_01.97.00R Radio installed, if that makes a difference.
Thank you all in advance!
I had the exact same problem. I believe the issue has to do with the older cwm not restoring your pds. I ended up having to flash the full 1.8.3 signed sbf to fix mine. The updated cwm has a pds backup and restore on it now so once you get it fixed, you should be able to recover like you did and it work. But for now your stuck flashing a full sbf.
Sent from my MB860 using XDA App
SOB! Thats what i was afraid of! I really just wish there was a way to turn cellular data on with this 2.3.4!!!
Sent from my MB860 using XDA App
lyon21 said:
SOB! Thats what i was afraid of! I really just wish there was a way to turn cellular data on with this 2.3.4!!!
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I flash with CM recovery and it doesnt matter what i tried, i can't get the cellular data to work. I use fastboot to install gingerbread and everything work.
I'm concerned about rooting or modifying my Atrix a second time. My first Atrix that I had rooted stopped working when I tried to update the OS through the wi-fi download of the update. Mid-way through, the Android mascot and the exclamation sign came up and I had to pull the battery. When I rebooted the phone it said the modem failed to start up. I don't know the reason for it but I went to the store and used my insurance to get a fresh one. Since then, I have only sideloaded apps and now with the Gingerbread update I don't have to use a USB cord to install apps anymore. I'm afraid to try to root or modify my Atrix again.
Bagel Bear said:
I'm concerned about rooting or modifying my Atrix a second time. My first Atrix that I had rooted stopped working when I tried to update the OS through the wi-fi download of the update. Mid-way through, the Android mascot and the exclamation sign came up and I had to pull the battery. When I rebooted the phone it said the modem failed to start up. I don't know the reason for it but I went to the store and used my insurance to get a fresh one. Since then, I have only sideloaded apps and now with the Gingerbread update I don't have to use a USB cord to install apps anymore. I'm afraid to try to root or modify my Atrix again.
Click to expand...
Click to collapse
Rooting should not have given you that problem. I've rooted numerous A4g's on froyo and they are all running GB fine after the ota. I also re-rooted them all now that they have GB. No issues. Also if your atrix didn't give you a boot error right when you turned it on you could have manually flashed a build and wouldn't have had to use you insurance.
Sent from my MB860 using XDA App
Alright, that eases my mind. Perhaps I just had some hardware failure.
How does rooting affect everything? Like you said, you are able to update via OTA when rooted and everything is fine. I also have a question about how to root exactly. I saw the sticky but it only mentioned the leaked release of Gingerblur and not the OTA version. Does the information still apply?
Its a little more involved if don't have your bootloader unlocked. Follow the post mramirezusa has about automatic unlocked bootloader and root.
Sent from my MB860 using XDA App
Be sure to read the instructions twice, then read it again for good measure!
Also check out the [HOWTO] Root after sbf flash thread in the dev section
Sent from my MB860 using XDA App
I had encounter ICS, which was great, but isn't ready to be a daily rom, so I use koush's app to reboot into recovery.
then I got stuck at the boot animation, so I decided to open up the stock recovery, and wiped data/factory reset like an idiot. So now all i have is stuck at the M logo, or stock recovery.
Am I going to have to use an official update.zip to flash, then root my phone again?
You are going to have to sbf.
Sent from my DROID2 using xda premium
okay, so I sbf'd back to stock froyo (only GB sbf I can find around the net is a megaupload link, which is obviously not very helpful nowadays) and let it do an OTA update to GB.
I then root, just like i have before, using the motorola one click root program on my computer.
I get root, install koush's bootstrap, and reboot into recovery. I then try to install libertyv3 2.0, which seems to go well...
until i reboot. once i reboot my phone, I'm stuck back at the bootloader, and can't do anything except SBF all over again.
seriously, what's going on? maybe this liberty .zip is broken or something? (i had to find a mirror, because A team gummy's site seems to be down, and B the only other official mirror is megaupload)
I'm going to try another rom, probably encounter ICS because i already have it on my SD card.
this time, I actually read the instructions and tried to install Liberty with clockwork recovery instead of koush.
still. effing. happening.
I reboot after flashing the zip and I can't get past the bootloader screen.
Code:
Bootloader
D2.37
Err:A5,69,35,00,23
Battery OK
OK to Program
Connect USB
Data Cable
I'm seriously at wit's end here. I just got this phone but a couple days ago after I lost my original. it's an insurance replacement. I rooted with the moto one click root, and used koush to install encounter ICS. after not knowing about encounter's wonky way of activation the custom bootloader, I mistakenly wiped the phone with the stock bootloader. I SBf'd back to stock froyo, then OTA updated to gingerbread.
That is my entire history with this phone. what the hell could possibly be wrong with it?
Do you wipe data/cache/dalvic once before you flash and twice after? Liberty is dead use ICS.
Sent from my DROID2 ICS using xda premium
Albinoman said:
Do you wipe data/cache/dalvic once before you flash and twice after? Liberty is dead use ICS.
Sent from my DROID2 ICS using xda premium
Click to expand...
Click to collapse
I did certainly wipe before flashing, but have never not once heard of wiping twice after flashing. wouldn't that undo the flash? what's the point of that? And like I said, I would use encounter ICS, but it's nowhere near stable enough for daily use.
When you wipe after its just to make sure everything is stock. As long as you don't wipe /system the rom will still be there. Actually if you can live without a camera EncounterICS is an amazing daily driver. Also never use bootstrap unless you're on stock gb.
Sent from my DROID2 ICS using xda premium
I can live without a camera, but google music barely works, which is something I can't live without. I'm thinking about going back to Apex until encounter gets really good (had apex for months up until i lost my original phone)
Google music is working fine for me. Good idea apex is great.
Sent from my DROID2 using xda premium
I have a droid x that is rooted and has the hack so I can wirelessly tether. I used the voodoo ota root keeper to try and keep my root. When I try to install the update it fails. I also have clockworkmod recovery installed. Any suggestions?
rkshack
Rkshack said:
I have a droid x that is rooted and has the hack so I can wirelessly tether. I used the voodoo ota root keeper to try and keep my root. When I try to install the update it fails. I also have clockworkmod recovery installed. Any suggestions?
rkshack
Click to expand...
Click to collapse
If you do take it there is quite a hassle getting it back to be rootable but if you must? You will need the latest version of rsdlite the desired sbf .602 or .605 which will revert it back to stock then you can take the OTA. My guess is somewhere along the way you froze or uninstalled some of the preinstalled bloatware? Which can cause the update to fail this was my case at least I sbfed to. 602 then took 2 OTA'S to .621 unfortunatley I regreted it you may want to look around at method to freeze updater instead your rooted try a different rom or 2 before making the decision
rom question
Thepooch said:
If you do take it there is quite a hassle getting it back to be rootable but if you must? You will need the latest version of rsdlite the desired sbf .602 or .605 which will revert it back to stock then you can take the OTA. My guess is somewhere along the way you froze or uninstalled some of the preinstalled bloatware? Which can cause the update to fail this was my case at least I sbfed to. 602 then took 2 OTA'S to .621 unfortunatley I regreted it you may want to look around at method to freeze updater instead your rooted try a different rom or 2 before making the decision
Click to expand...
Click to collapse
Where are the best areas to look for info on roms. I have clorkwork rom manager but there are not any roms I recognize.
If I were to back up my rom and then use titatanium back up would I be able to restore to my current state.
rkshack
Rkshack said:
Where are the best areas to look for info on roms. I have clorkwork rom manager but there are not any roms I recognize.
If I were to back up my rom and then use titatanium back up would I be able to restore to my current state.
rkshack
Click to expand...
Click to collapse
RootzWiki is the best place to find roms.
You can make complete backups in ClockworkMod Recovery of your entire rom. I would use MyBackup Root to backup things like individual apps, data, SMS, etc.
Sent from my DROIDX using Tapatalk
update failed
Rkshack said:
I have a droid x that is rooted and has the hack so I can wirelessly tether. I used the voodoo ota root keeper to try and keep my root. When I try to install the update it fails. I also have clockworkmod recovery installed. Any suggestions?
rkshack
Click to expand...
Click to collapse
I also had the same failure, it was due to my having removed some of the bloatware. I loaded the 605 SBF file and rooted this installed al the root programs i would need along with voodoo ota and made a root backup, ran all my programs and did the update, all went ell and I was able to renew root with voodoo ota keeper. so far i have had no problems and am on the 621 update and fully rooted. Titanium backup works fine and I have been able to remove the bloatware.
Hope this helps and i am not too late.
From what every been saying, don't upgrade to 621. Just flash a custom rom right now since you are rooted and you can sbf back to 602 or 605 as needed.
I have 2 Droid X and both running CM7 and its awesome. I tried MIUI and Gummy but couldn't get into it.
4.5.621 install failure
Greetings. This looks like the right thread for this issue, but if not, please redirect me.
Some background:
DroidX
Android version 2.3.3
System version 4.5.605.MB810.en.US
currently rooted
Being a laggard, I did not accept the 621 update when first offered through OTA. My 4.5.605 DroidX was rooted and I'd read that I'd have to either unroot or "hide" root in some manner. It seemed like a bit of trouble and I had other life issues at the time.
After things cleared, I contacted VZ and they pushed the upgrade again. After "unrooting", I accepted the OTA upgrade, but each installation attempt failed after a successful download. No other diagnostics, just "the update failed". I tried this multiple times after reboots, battery removal, cache clearing and such. I then did a factory reset and tried again - still the same sequence, successful download, install now, update failed.
So I called VZ and Moto. They suggested accepting the update while attached to a solid WiFi. All the same tricks were turned as with the OTA (another factory reset, clear cache, remove/replace battery) only these attempts used the WiFi (excellent signal). Same failure.
Moto then suggested I ship in the unit and for $110 they would handle it. Right.
So I found Blur_Version.4.5.621.MB810.Verizon.en.US.zip, downloaded it to the SD card and attempted to install using the recovery mode menu. This also fails but at least offers up the message: assert failed apply_patch ("system/app/AccountAndSyncSettings, apk", "-" then some odd number letter sequences followed by "error in /tmp/sideload/package.zip status 7.
I've since rerooted just out of curiosity to see if that would still work.
All this to fix the irritating bug of the phone powering back on by itself.
Any hints or advice?
Thanks.
-Joe
Sending your device in is not necessary at all.
It seems that you have removed one of the systems stock apps. Replace any apps that you may have removed and attempt to take the update again.
Or, you can SBF back to 602 and take the OTA update to .621. Just be sure to back up everything that you need (not including app data).
Sent from my Galaxy Nexus using Tapatalk 2
missteps
Bloatware was renamed but I've been pretty careful not to delete anything... even kept a list of what was renamed and to what. All that has been rolled back but clearly something was missed. The only thing that threw me a curve was the symlink on the Madden Football app, but even that now looks pre-modified.
I take it that changes to ACLs would also glitch the update, but what about file timestamps? How pristine do these stock apps have to be?
I'll check them again since there's little to lose in doing so. If I can't find a discrepancy, the sbf to 602 will be the next step.
Ironically, the reason for embarking on the bloat removal at the outset was to cure the auto-power on bug, which is now supposedly fixed in 621.
But it's all about the learning.
Thanks again.
Help me please 2.3.3 to 2.3.4
I recently tried updating my phone....When I go to system settings and then go to About phone and then system updates.... I get this update 4.5.621.en.us. Then I click download and then when it finishes...I click install and then it shuts off and then it boots up and says " Failed to update software" Click ok... Then that's it... Someone please help me....
DETAILS of FIRMWARE and ETC..
System Version: 4.5.605.MB810.Verizon.en.us
Model number: DroidX
Android Version: 2.3.3 Gingerbread
Someone please help me with this annoying error
Legit-Reflex said:
I recently tried updating my phone....When I go to system settings and then go to About phone and then system updates.... I get this update 4.5.621.en.us. Then I click download and then when it finishes...I click install and then it shuts off and then it boots up and says " Failed to update software" Click ok... Then that's it... Someone please help me....
DETAILS of FIRMWARE and ETC..
System Version: 4.5.605.MB810.Verizon.en.us
Model number: DroidX
Android Version: 2.3.3 Gingerbread
Someone please help me with this annoying error
Click to expand...
Click to collapse
Have you tried downloading the update via wifi? Is the update appoximately 32MB? Have you tried to flash the 621 sbf?
Sent from my MB860 using xda app-developers app
palmbeach05 said:
Have you tried downloading the update via wifi? Is the update appoximately 32MB? Have you tried to flash the 621 sbf?
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
I don't know how to flash, and yes i've tried multiple times downloading the update....help
Legit-Reflex said:
I don't know how to flash, and yes i've tried multiple times downloading the update....help
Click to expand...
Click to collapse
Download RSD Lite, i think the latest revision is 5.7. then download the 621 sbf, any necessary drivers, and it also helps to have the fastboot/adb package as well (even though fastboot is useless for us, still something good to have).
backup anything you need backed up or do a nandroid. reboot to bootloader. connect device to computer. start up RSD Lite. click show device. click the button that lets you browse for files. select 621 sbf. click start. sit back and let it do its thing and you'll be back up and running in no time
Links files and instruction on how to flash a sbf, are in my list
sd_shadow's [Collection] of Links for: Droid X (MB810)
Sent from my XT862 using Tapatalk
deboyz1014 said:
From what every been saying, don't upgrade to 621. Just flash a custom rom right now since you are rooted and you can sbf back to 602 or 605 as needed.
I have 2 Droid X and both running CM7 and its awesome. I tried MIUI and Gummy but couldn't get into it.
Click to expand...
Click to collapse
621 isn't all bad. It's easy enough to root it now with an apk called Framaroot and you will then have all the latest security updates from Motorola. If you do go with 621 you are then"stuck" there as it is not possible to go back to any earlier versions. Most of the most recently updated Roms work fine with it.
Sent from my SCH-I535 using Tapatalk