I accidentally downloaded the OTA. Now it boots into TWRP (3.02) and stops. I can flash a ROM and I can restore a backup but it still boots to TWRP.
Any way to load some system without having to flash stock?
Yeah you can download the stock image, extract it, and "fastboot flash system system.img"
fakecharles said:
I accidentally downloaded the OTA. Now it boots into TWRP (3.02) and stops. I can flash a ROM and I can restore a backup but it still boots to TWRP.
Any way to load some system without having to flash stock?
Click to expand...
Click to collapse
It would be good to know if your problem is resolved - it would save me the effort of typing this, for a start.
The simplest way is to download the OTA to your PC and sideload it. If you're already in TWRP there is a button which allows you to sideload via ADB.
Edit: Sorry, I see you say "not stock". Downloading the OTA doesn't do anything - I guess that you tried to install it? Which ROM were you on before you did this? And you know that there's a newer TWRP - 3.1?
I did resolve it. I found some instruction I could tie in the terminal. Sorry, I don't have a link.
Related
Like an idiot I wiped my System inside TWRP. Using TWRP 2.6.0.2
Earlier tonight my phone starting rebooting. I was inside GooManager and tapped reboot to recovery. When I did that, for some reason my phone lost root. Meaning when I went to reboot inside TWRP it stated that it looks as if my phone is not rooted. I rebooted anyway without installing SuperSU through TWRP. I was already rooted. Afterwards, it would boot up fine but kept constantly rebooting only after a minute or two.
I went back into TWRP and clicked through dalvik wipe and cache wipe. Still got reboots. I was planning on flashing CyanogenMod anyways so I thought I'd go on and wipe everything. I went in to advance wipe and check everything. As I swiped the slider to wipe I realized I checked System too, but it was too late.
Now my phone won't boot past the HTC logo with the red text underneath. I can boot into TWRP however so I hope all is not lost. I am currently at work so I have no way to try anything on the phone at the moment but was hoping for some advice on what to try later when I get home.
I'm thinking maybe I'll be able to use the "Mount" tab in TWRP to load a ROM on and flash and everything will be well again. Would I mistaken to think that? If not, I'll purchase an USB OTG cable and use a USB stick but I really need this up an running as quickly as possible.
Also, does anyone think it would be best just to go back to stock at this point (if I can) and start from scratch?
Much thanks for your help and advice,
dgb1891
So, oddly enough I did the same thing, How I managed to recover it so you can adb sideload a rom from TWRP and have access to a "working" phone again was to find your stock recovery.img, then flash it via fastboot, and then from the hboot menu, choose factory reset and let the stock recovery do it's thing, then reflash TWRP (I honestly like CWM doe) and adb sideload a rom (presumably what you were using before). It SHOULD fix your problem and you'll be able to mount files again.
hayame said:
So, oddly enough I did the same thing, How I managed to recover it so you can adb sideload a rom from TWRP and have access to a "working" phone again was to find your stock recovery.img, then flash it via fastboot, and then from the hboot menu, choose factory reset and let the stock recovery do it's thing, then reflash TWRP (I honestly like CWM doe) and adb sideload a rom (presumably what you were using before). It SHOULD fix your problem and you'll be able to mount files again.
Click to expand...
Click to collapse
By stock recovery.img you mean a stock HTC image? - or do you mean a recovery like TWRP or CWM?
dgb1891 said:
By stock recovery.img you mean a stock HTC image? - or do you mean a recovery like TWRP or CWM?
Click to expand...
Click to collapse
Literally stock recovery.img, not TWRP or CWM.
hayame said:
Literally stock recovery.img, not TWRP or CWM.
Click to expand...
Click to collapse
K. Thanks. I have a feeling this is going to be a bit more complicated than I first thought...
I followed what you suggested and got the phone back up and working. Thanks again.
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 got a NExus 7 wifi 2012 that was running 5.0. It was rooted, and used TWRP.
I got info about the updated and pressed install. Booted in to TWRP and nothing happened. I then pressed install in TWRP and in cache found the .zip and tried to install. Got an error.
I then booted in to android again, and flashed the stock recovery 5.0.2 (I guess it's like the stock 5.0?) and later I tried the OTA install again. Got an error.
I then read about the new "feature" in 5.0 about not allowing OTA if rooted, and I then in SuperSU completely uninstall the root and rebooted.
Later when I got the OTA update again, I thought it should work, but I still got the error.
What can I do? Right now I'm on a MAC. Can I in some way flash only the good stuff from the factory image, and in some way NOT have to factory reset the Nexus 7?
/Söder
Even when you unroot, your file system is tampered. Only way to update is using factory images.
I think you can flash the factory image without user data to prevent factory reset.
theliquid said:
Even when you unroot, your file system is tampered. Only way to update is using factory images.
I think you can flash the factory image without user data to prevent factory reset.
Click to expand...
Click to collapse
How is it I do that then? What files from the factory images (unpacked) is it that I need to flash? Is it fastboot or ADB I use to flash?
/Söder
soder said:
How is it I do that then? What files from the factory images (unpacked) is it that I need to flash? Is it fastboot or ADB I use to flash?
/Söder
Click to expand...
Click to collapse
I have done this with my rooted N5 and N7. You need to re-flash system.
Unpack the 5.0 factory image and
fastboot flash system system.img
goraps said:
I have done this with my rooted N5 and N7. You need to re-flash system.
Unpack the 5.0 factory image and
fastboot flash system system.img
Click to expand...
Click to collapse
I managed to do this now to. My biggest problem is now to root the device again. I've switched back to stock recovery, before I removes root, when I was trying to apply the ota.
Now when I try to flash twrp recovery, I get an error about the size. I can flash the stock recovery though, the same way I flashed system.img and boot.img.
What can be wrong? I do I get root now again?
/Söder
/Söder
soder said:
I managed to do this now to. My biggest problem is now to root the device again. I've switched back to stock recovery, before I removes root, when I was trying to apply the ota.
Now when I try to flash twrp recovery, I get an error about the size. I can flash the stock recovery though, the same way I flashed system.img and boot.img.
What can be wrong? I do I get root now again?
/Söder
/Söder
Click to expand...
Click to collapse
Are you saying you can't flash the TWRP recovery now? So are you now completely stock 5.0.2?
goraps said:
Are you saying you can't flash the TWRP recovery now? So are you now completely stock 5.0.2?
Click to expand...
Click to collapse
Yes, system, boot, recovery flashed with fastboot.
When in fastboot mode, I get error, something with size, when flashing twrp. I found a CWM recovery I could flash, but it didn't boot to recovery correctly.
The twrp file is not corrupt. Tried it again and also a different version.
/Söder
OMG. I'm so f-ing stupid. Blaming all the x-mas food.
Was trying to flash the Oneplus One recovery. Not the one for Nexus 7.
Hope it works better now...
/Söder
I have been having an issue flashing TWRP. I have previously had TWRP on my Nexus 6, but I recently flashed the latest security update, and now for the life of me, I cannot get TWRP to flash.
I run fastboot flash recovery twrp-3.0.2-0-shamu.img, it says it ran OKAY, I reboot the phone, then use ADB reboot recovery but it always comes back to the stock recovery. I have done this a hundred times, and never had an issue. Anyone else seen this?
lenard_hester said:
I have been having an issue flashing TWRP. I have previously had TWRP on my Nexus 6, but I recently flashed the latest security update, and now for the life of me, I cannot get TWRP to flash.
I run fastboot flash recovery twrp-3.0.2-0-shamu.img, it says it ran OKAY, I reboot the phone, then use ADB reboot recovery but it always comes back to the stock recovery. I have done this a hundred times, and never had an issue. Anyone else seen this?
Click to expand...
Click to collapse
boot up first, remove some system apps to clear up some space, then flash again with fastboot.
simms22 said:
boot up first, remove some system apps to clear up some space, then flash again with fastboot.
Click to expand...
Click to collapse
I can't remove any system apps. I need to have root first, and I need TWRP to install root. Besides, TWRP goes on the recovery partition not the system partition.
lenard_hester said:
I can't remove any system apps. I need to have root first, and I need TWRP to install root. Besides, TWRP goes on the recovery partition not the system partition.
Click to expand...
Click to collapse
true. you are using fastboot while you are in the bootloader?
simms22 said:
true. you are using fastboot while you are in the bootloader?
Click to expand...
Click to collapse
yes. I think I figured out a way around it. my mistake was rebooting. Instead of rebooting from the bootloader, I just went to recovery mode directly from there and TWRP booted right up.
lenard_hester said:
yes. I think I figured out a way around it. my mistake was rebooting. Instead of rebooting from the bootloader, I just went to recovery mode directly from there and TWRP booted right up.
Click to expand...
Click to collapse
I think you have to rename stock recovery files or when you reboot it will reinstall stock recovery.
cajun9924 said:
I think you have to rename stock recovery files or when you reboot it will reinstall stock recovery.
Click to expand...
Click to collapse
that is true, if the op is running stock android. or you can just delete that one file in /system/.
I need help, I was trying to root my Oneplus 3T, with stock OOS 4.0.2. After following all the steps, I flashed the dm-verity to keep with the steps, and that worked. But after formatting data, as it was suggested, it gave me an error. It showed like everything was encrypted which shouldn't due to the flash of the dm-verity and now I'm stucked in not a bootloop because the phone actually boots but I cant do anything because the encryption error takes me back to the recovery, which shows an error etc. Is there any tutorial to fully recover the phone from this point? Thank you very much in advance.
Did you try flashing SuperSU after flashing dm-verity? If the zip isn't on your phone at this point, you can go into bootloader mode and use adb to push the SuperSU zip on and flash it that way.
You can use the toolkit to push the files if you want, it'll be easier that way: https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729
If all else fails, flashing a clean rom always works.
Anova's Origin said:
Did you try flashing SuperSU after flashing dm-verity? If the zip isn't on your phone at this point, you can go into bootloader mode and use adb to push the SuperSU zip on and flash it that way.
You can use the toolkit to push the files if you want, it'll be easier that way: https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729
If all else fails, flashing a clean rom always works.
Click to expand...
Click to collapse
Now I'm stuck in a bootloop after reflashing stock recovery. If i reflash the boot.img via fastboot from the .zip of the official OOS 4.0.1, will it work? Thank you very much
Not sure why flashing recovery would cause a bootloop. Might be safer just to sideload a fresh ROM. If you're worried about losing files, you can use adb to pull whatever you need first from sdcard prior to flashing.
What I did in a similar situation was to reflash the stock recovery first using the unbrick-toolkit. When booting into recovery then, there is an option "forget password" when it asks you to enter the password. If you select that, it will simply wipe your phone completely and you can start over again.