I am currently running .901 update and i am trying to go back to .886. Whenever i try to run RSDlite, it always gets stuck on flashing system.img. I will wait for like 20 minutes and finally just close the program. I have also tried to do it from the command line by running moto-fastboot flash system system.img. Do I just need to wait longer? Any suggestions?
RSDlite was slow for me also, you must be patient. If that doesn't work try path saver http://forum.xda-developers.com/showthread.php?t=1433783 . but it also takes its time...are you using the minimal fxz or full?
use the Bionic Path Saver 1-Click Method it will get you to 5.5.893 unrooted
If you were on .901, download the 901fix, unzip and place both files into the path saver folder. Let the path saver do it's thing, install the .893 when it tells you to (root will fail, it does for me anyhow) reboot, it will throw you into a fastboot cdt failure, click on the 901fix and your phone will reboot into stock 5.5.893, DONE!
use this method, to get to .886, you will need the radio zip file floating on the boards, put it on your SD card, path saver installs stock .886 rooted, when it boots to recovery, install the radio zip instead of the .893, it will kicks you into the fastoot cdt failure, do the 901fix. If you want to remove root, you can try forever root restore, but it will probably send you back to the cdt failure again.
You're better off staying with the current stock .893.
5.5.902 will be released by friday anyhow.
Related
Alright, I give up.
I've wasted one full day and all I do is keep going in circles. I have an unlocked bootloader but I am not able to flash custom recovery to it. When I do:
fastboot flash recovery recovery-RA-passion-v2.2.1.img
it is successful but am having the problem mentioned here:
"Make sure that init.rc isn't calling any install-recovery.sh script, otherwise you'll boot back to stock recovery (exclamation mark with a little Android)."
http://forum.xda-developers.com/showpost.php?p=10467058&postcount=1638
So, no custom rom because I cant turn off verification in order to flash custom rom zip file. Now the problem is that I can't even fix this problem because I don't have root so I can't delete the following files:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
When I try adb shell it keeps saying "permission denied"
It gets better - I've managed to mess things up royally even further. I tried flashing FRG83 system image using "flashboot update update.zip". It was successful but now my phone is going in boot loop!!
Can someone please help me before I lose hope in humanity?
Recovery is only restored when you boot into system, so the idea is that you flash recovery, and go straight into it via the on phone menu, and then install what you need to...
You can either flash a pre-rooted GB, flash the su.zip and then you'll have su access to delete the files when in system or adb, or flash this zip which will remove the two files...
http://db.tt/cp7De8G
Sent from my Nexus One using XDA App
danger-rat said:
Recovery is only restored when you boot into system, so the idea is that you flash recovery, and go straight into it via the on phone menu, and then install what you need to...
Click to expand...
Click to collapse
I totally did not know this. Thanks a lot buddy
Hi, I'm having trouble taking the OTA 5.03.651.3 update.
Running:
stock rooted 4.06.651.9.
TWRP
I'm S-OFF
What I've done:
Flashed stock recovery
Rebooted into stock recovery to verify it's actually there and such
What's happening:
I've flashed stock recovery twice using fastboot (MD5SUM verified on the stock recovery, downloaded from two different sources)
I reboot into the phone OS and it prompts me to download the OTA 5.03.651.3 update.
Download completes, phone reboots to run OTA update
Phone sits for a while at the stock recovery screen (Device icon with a red triangle and exclamation point)
Phone reboots into OS and has not updated anything.
Cycle repeats, upgrade prompt, download, reboot, again...again....
I'm not a complete noob, but I don't know where to turn next except to just run the older RUU I have and let it start taking OTA updates from a few releases back.
Or would it better at this point to just flash TWRP again, find/flash firmware and 5.03.651.3? I have my data backed up, but I'd really rather not have to go about restoring it again if I can help it.
Can anyone provide any possible insight on this? Feeling a bit lost.
Never mind, I just ended up flashing the OTA rom and firmware instead of trying to take the lazy way out.
The more I read the more confused I get. Could someone sort me out?
<complain>I got the moto x because of the quick OTA updates. Now it seems that because I installed TWRP and froze a few apps with TB that this feature is totally borked!</complain> is that correct? I cannot update without stock recovery and all the original apps installed / unfrozen?
In my predicament would the easiest thing to do be
1. Unfreeze any system apps I've frozen.
2. Use msfastboot to reflash stock recovery?
3. Accept the OTA or somehow flash it manually (I'm not sure about this last one see below)
I accidentally accepted the OTA download and now it bugs me to install. I won't install because it just reboots into TWRP. But it does keep prompting me to set at time to install. If I simply flash stock recovery I think i will still get this prompt. Would that be the easiest way to go?
Thanks for any advice.
pairustwo said:
The more I read the more confused I get. Could someone sort me out?
<complain>I got the moto x because of the quick OTA updates. Now it seems that because I installed TWRP and froze a few apps with TB that this feature is totally borked!</complain> is that correct? I cannot update without stock recovery and all the original apps installed / unfrozen?
In my predicament would the easiest thing to do be
1. Unfreeze any system apps I've frozen.
2. Use msfastboot to reflash stock recovery?
3. Accept the OTA or somehow flash it manually (I'm not sure about this last one see below)
I accidentally accepted the OTA download and now it bugs me to install. I won't install because it just reboots into TWRP. But it does keep prompting me to set at time to install. If I simply flash stock recovery I think i will still get this prompt. Would that be the easiest way to go?
Thanks for any advice.
Click to expand...
Click to collapse
1. - You do not need to unfreeze apps. The apps are still there untouched in the file system, and in recovery the OS hasn't booted enough to know that the apps are "frozen". By the way, frozen apps are basically just tagged in the OS as not available....so with the OS not running (just recovery is), they aren't "frozen" in recovery.
2. - Yes, fastboot to flash stock recovery. Boot to bootloader mode, fastboot flash recovery recovery.img (you don't need mfastboot for recovery, though you can still use it.)
3. - Accept the OTA. Since yours is trying to install, you should be able to boot to bootloader, flash stock recovery and on reboot it will start the install of the OTA. When done and booted.....reflash TWRP if you like.
That would be the way to go, yes.
Flash stock recovery and try to upgrade. If you cannot, try to unfreeze all sys apps. That should do it. ?
OK. So maybe not such a huge PIA as I had thought. I will track down the recovery file and read the instructions for flashing.
Thanks
@pairustwo
Every time another OTA comes out, people who modify their phones ask the same question. I've written up a FAQ based on the past OTA's.. -> http://mark.cdmaforums.com/MotoX-OTA.html if you want to read it to get more info.
Part of the issues you are talking about when taking an OTA is that the OTAs want to patch and replace only SOME files on your phone, so it checks to make sure the update is for your phone and its android version by evaluating certain files on the phone, that they exist and that their check sums match what the update expects.
i.e. change/modify/delete files the OTA update checks before installing, and the OTA will refuse to install.
If it didn't do this, the wrong update could possibly flash to your phone, replacing files with incompatible versions and making a big mess.
So yeah, "getting back to stock" (or as close to it as you can) is always recommended before taking an OTA so the "check" doesn't fail and prevent the OTA from applying.
In the past, freezing apps with Ti Backup was enough of a modification to cause the OTA's to fail. So often it is still suggested to un-freeze those done with TiBackup.
The OTA zip file (as downloaded) will only flash from Stock Recovery. TWRP and CWM for example don't properly process and flash them, so if you try to install when stock recovery is NOT on your phone, you get stuck in a bootloop. Using mFastboot to flash stock recovery back on is fine for those with unlocked bootloaders. Locked Bootloader users, is another matter.
There is a way "side load" the OTA, IF you have stock recovery, your phone hasn't received the push from Moto or your Carrier yet, and the OTA Zip file has leaked. But it still requires you get back to stock, etc. just as if you were getting it OTA.
So I've tried to flash back to stock but am having an issue. Does anyone have a link to a stock recovery image? Maybe the one I have is corrupt.
pairustwo said:
So I've tried to flash back to stock but am having an issue. Does anyone have a link to a stock recovery image? Maybe the one I have is corrupt.
Click to expand...
Click to collapse
Answered here -> http://forum.xda-developers.com/moto-x/moto-x-qa/dead-android-red-exclamation-t2778189
and I made this -> http://mark.cdmaforums.com/MotoX-EnterStockRecovery.htm
I've been flashing phones since way back with the tmobile G1, but I just don't have the time to be constantly fiddling around with my phone. To that end, I want to update from 5.0 to stock but rooted 5.0.1 (or 2) but I don't want to have to do a full wipe. It takes forever to get everything back just the way I like it. Is it possible? I'm getting the stupid OTA update notification and its driving me crazy.
By the way I did search before I posted a new thread. Found lots that say you can't take the OTA but nothing specifically pointing me to a stock ROM that won't require a wipe.
Thanks for taking the time to help.
ripsphone said:
I've been flashing phones since way back with the tmobile G1, but I just don't have the time to be constantly fiddling around with my phone. To that end, I want to update from 5.0 to stock but rooted 5.0.1 (or 2) but I don't want to have to do a full wipe. It takes forever to get everything back just the way I like it. Is it possible? I'm getting the stupid OTA update notification and its driving me crazy.
By the way I did search before I posted a new thread. Found lots that say you can't take the OTA but nothing specifically pointing me to a stock ROM that won't require a wipe.
Thanks for taking the time to help.
Click to expand...
Click to collapse
Options are:
1) Download full factory image and remove the -w flag from the flash-all script (Will replace your recovery)
2) individually fastboot flash the system, boot and radio image using fastboot from above factory image
3) find a recovery flashable rom.zip if you have a custom recovery
If you want root, flash it from recovery before booting.
ripsphone said:
I've been flashing phones since way back with the tmobile G1, but I just don't have the time to be constantly fiddling around with my phone. To that end, I want to update from 5.0 to stock but rooted 5.0.1 (or 2) but I don't want to have to do a full wipe. It takes forever to get everything back just the way I like it. Is it possible? I'm getting the stupid OTA update notification and its driving me crazy.
By the way I did search before I posted a new thread. Found lots that say you can't take the OTA but nothing specifically pointing me to a stock ROM that won't require a wipe.
Thanks for taking the time to help.
Click to expand...
Click to collapse
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
I have had my Droid turbo since launch and as such followed the path the getting root on it for some time. I used Mofo to get root back on android 4.4.4, used it again to upgrade to 5.1 while keeping root, used sunshine to unlock the bootloader when that came out, and finally installed TWRP recovery on it. I had not done much to it since, but had Intended to install cyanogenmod for a while.
Well I thought I would finally get to it this weekend. I made a nandroid back-up with TWRP, copied it to my computer, backed up some files I didn't want to lose, and went ahead and installed the latest version of cyanogenmod 13 for quark (Moto MAXX and Droid Turbo) and the necessary gapps. It all went very well. I booted into cyanogenmod just fine, and signed in to google.
I was in the process of setting things up, like preferences/wallpapers/wigets etc, while google downloaded my apps. Not long after I started doing this, nova launcher would repeatedly crash, as well as cyanogenmod's built in launcher. I got fed up with it and rebooted. But the phone shut down and started acting odd. It would show what looked like the bootloader, but the open android guy was not there, and I had no options at the top. Sometimes it would just say AP Fastboot Flash Mode (Secure) with no other text.
I got it to go to the bootloader after holding down the power and volume down button, and got it to boot to TWRP. But TWRP said there is no OS installed, and it refused to install anything, wipe anything, and TWRP itself crashed after a bit when I left it there to try and use ADB to push my nandroid back up to it.
Now TWRP will not load from the bootloader, and I cannot flash anything. I wanted to just re-flash the stock firmware. So I downloaded fresh copies of it from the root thread here on XDA, but no matter what, i get the error "(bootloader) Failed to erase partition" It does this for anything. I tried flashing TWRP and the fresh system image. I tried following the steps on the root thread that flash things that you need to prepare the phone for the system image, but all attempts to flash fail with the same message.
I also tried using mofo to flash a clean system image. But it just stops and quits at 7%. I have had this problem before, and got around it by using mofo 0.0.2. But I no longer have that version.
I am at a loss here. I need my phone back ASAP. Any help would be much appreciated.