Okay, I haven't been able to update since LMY48I. Back then I was on stock recovery. Re-locking bootloader and all but still was not able to take OTA (always came up with dead android guy with "Error"). I'll skip the (probably) irrelevant stuff since then and give you the current situation:
Currently unlocked, rooted, with custom recovery. Still on LMY48I. I can't take OTAs obviously, and have tried flashing OTA updates manually with no luck and have tried flashing the entire Marshmallow image and that will not work either (sideload or flashing from internal storage in recovery). Sideload comes up with Closed error (device DOES show up in device list and I can do other things). Flashing from within recovery just says "Failed".
Please help me get to Marshamallow!
Edit: On Project Fi by the way.
Edit 2: Also, I've tried the flash-all script.
Now it says the device is corrupted when I boot up. I can still access recovery. Any help walking me through getting all of the correct firmware and latest build on would be much appreciated.
Thank you.
Edit: Looks like i'm good. I flashed each .img individually. I'm super curious why flash-all, sideload, and flashing from device wouldn't work though.
altvisionx said:
......./I flashed each .img individually. I'm super curious why flash-all, sideload, and flashing from device wouldn't work though.
Click to expand...
Click to collapse
Flashall.bat stops; only m-bootloader and m-radio are flash. Google's fault. You did the right thing by extracting the images and fasbiot flash them.
You cannot sideload the full factory image or flash from storage. Only fastboot
And just to clarify, you can't take an OTA (sideloading or otherwise) if your phone is rooted, have a custom recovery or a custom kernel (or any other modification to the system). The state of the bootloader (locked or unlocked) does not affect the ability to take an OTA update.
Related
ISSUE RESOLVED: keeping post since active since I still need the rom exe. But boot looping fixed.
My AT&T HTC One is stuck in boot loop, probably to do with the KK OTA update. I have looked everywhere, read posts all night, and tried all of the various reboots and reflashings of recovery files and firmware, erased caches, locked and unlocked bootloaders. Can anyone post the executable RUU for the stock ROM KK version 4.18.502.7? I'd really appreciate it. I can't sideload a zip (it stalls). I'm aware of the other post asking for the same thing and the response in it with a link to the file, but that link actually is only to a recovery zip with darkbootloader, which seems also to require S-OFF, even if I did have some way to sideload it.
The firmware updated before it began looping, so I can't just reinstall a prior stock ROM exe file, as far as I can tell. I tried anyway!
I hesitate to install the .1540. Dev. Ed. version of the ROM that's available because it says in the notes that it's "compatible" with my cid and PN, etc, but I think they mean for recovery file purposes and not for a full ROM install. So I think I just need the ROM exe, if anyone has it? Thanks!
more info
by the way, when it crashed i had installed the ota update and then restarted play around with it, then rebooted in bootloader and unlocked, reinstalled twrp and AndRev HD 51. I've noticed two problems there. The first is that the Xposed module's latest update totally defeats my internet wifi and especially crashes vpn sevice. prior versions did not and I could not down-install to prior version (is preinstalled in HD 51). The other problem is that in looking around for this boot loop probably, turns out that TWRP apparently doesn't get along well with the encryption. don't know why. this stuff may or may not be part of the problem, but at this point i have no OS, an erased cache and can't even get into recovery (tried flashing twrp, older twrps and CWM. thanks.
You are screwed if you have no recovery, and the phone is s-on. You need to find a way to get in recovery. Alternatively try to flash the firmware only from OTA to get stock recovery.
sent from my mobile device
randomOne1111 said:
My AT&T HTC One is stuck in boot loop, probably to do with the KK OTA update. I have looked everywhere, read posts all night, and tried all of the various reboots and reflashings of recovery files and firmware, erased caches, locked and unlocked bootloaders. Can anyone post the executable RUU for the stock ROM KK version 4.18.502.7? I'd really appreciate it. I can't sideload a zip (it stalls). I'm aware of the other post asking for the same thing and the response in it with a link to the file, but that link actually is only to a recovery zip with darkbootloader, which seems also to require S-OFF, even if I did have some way to sideload it.
The firmware updated before it began looping, so I can't just reinstall a prior stock ROM exe file, as far as I can tell. I tried anyway!
I hesitate to install the .1540. Dev. Ed. version of the ROM that's available because it says in the notes that it's "compatible" with my cid and PN, etc, but I think they mean for recovery file purposes and not for a full ROM install. So I think I just need the ROM exe, if anyone has it? Thanks!
Click to expand...
Click to collapse
This RUU does not exist yet, only the FOTA version - I've been in talks with HTC about this very thing. They do not have an ETA for the RUU, unfortunately.
SaHiLzZ said:
You are screwed if you have no recovery, and the phone is s-on. You need to find a way to get in recovery. Alternatively try to flash the firmware only from OTA to get stock recovery.
sent from my mobile device
Click to expand...
Click to collapse
Hm. I did flash the firmware from an OTA. But couldn't actually boot into recovery after that. I can flash custom recoveries but can sideload without the intall stalling about a third of the way through (just hangs, no error messages). Then after that if I restart it loops. I can maybe fix the "tampered" warning and swap it out somewhere. I think it's the encryption while using twrp maybe resulted in some hiccup. But I thought the firmware flash would fix that. And I'm not sure how you can actually tell whether the flashed firmware is successful. (it says it is in the command prompt, but the phone doesn't really do anything all that different and i already updated with the OTA so the numbers won't change).
Looking at the board today and reading through the posts I see many people reporting basically being in the same boot loop boat after the OTA update, though with diff versions maybe there's some FW problem. weird so many posts of similar boot looping.
Thanks for responding.
This issue is temporarily resolved, was able to push ARHD in TWRP (would not sideload without erroring out during install, but was able to push zip to sdcard and then install from there) after much wiping using both twrp and cwm. Did notice when using CWM recovery would not install ARHD off sdcard push, and would flag unknown files .... android..security during wipes, so i am guessing that encrypting a custom ROM at least with TWRP as recovery was a bad idea. hopefully this will stay stable until the KK OEM RUU EXE is available. Thanks for the help.
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
Hello all again. It's been almost year since last here, and clearly I have learnt nothing in the meanwhile.
First, specifications:
I have an HTC One M7 (AT&T) that had been updated to 4.3 OTA, then unlocked via htcdev, flashed with CWM 6.0.4.3 recovery, and then rooted with the Superuser zip on the CWM site. The device remains S-On.
Now, for the detailed inquiry:
I've been in the Stone Ages (see, Jelly Bean) for a while and have been planning on updating my phone for some time. However, the easy way, i.e. OTA, requires that I return to stock recovery. Now, as far as I know, this would require the use of an RUU (I'm not quite sure which one - perhaps "RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2.exe" from AndroidRUU?) which would require that I lock my bootloader (correct?) which would also happen to wipe my device. I was hoping that I might be able to flash the stock recovery image (which I have been unsuccessful thus far in finding on my friend Google, since I assume it was deleted from my phone when I flashed CWM?) without having to go through an RUU. Is such a thing feasible? Where would I find the appropriate stock recovery image file to do so? And is there a way, once I (hopefully) receive the OTA update, to copy that new stock recovery image to my PC before I switch back to custom recovery to avoid bothering all you fine folks about this again?
Thank you all for taking a look, and I appreciate any direction you may provide. (Seriously, though, I'm suspecting that the reason I haven't gotten an LTE signal the past couple months is because my radio is so outdated.)
You can install stock recovery using fastboot command.
However to apply OTA, if your phone is S-On, you must lock the bootloader.
You don't have to lock bootloader if your phone is Soff, for OTA, just stock recovery is good enough.
lyciansarpedon said:
Hello all again. It's been almost year since last here, and clearly I have learnt nothing in the meanwhile.
First, specifications:
I have an HTC One M7 (AT&T) that had been updated to 4.3 OTA, then unlocked via htcdev, flashed with CWM 6.0.4.3 recovery, and then rooted with the Superuser zip on the CWM site. The device remains S-On.
Now, for the detailed inquiry:
I've been in the Stone Ages (see, Jelly Bean) for a while and have been planning on updating my phone for some time. However, the easy way, i.e. OTA, requires that I return to stock recovery. Now, as far as I know, this would require the use of an RUU (I'm not quite sure which one - perhaps "RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2.exe" from AndroidRUU?) which would require that I lock my bootloader (correct?) which would also happen to wipe my device. I was hoping that I might be able to flash the stock recovery image (which I have been unsuccessful thus far in finding on my friend Google, since I assume it was deleted from my phone when I flashed CWM?) without having to go through an RUU. Is such a thing feasible? Where would I find the appropriate stock recovery image file to do so? And is there a way, once I (hopefully) receive the OTA update, to copy that new stock recovery image to my PC before I switch back to custom recovery to avoid bothering all you fine folks about this again?
Thank you all for taking a look, and I appreciate any direction you may provide. (Seriously, though, I'm suspecting that the reason I haven't gotten an LTE signal the past couple months is because my radio is so outdated.)
Click to expand...
Click to collapse
Just flashing the stock recovery will probably not allow you to successfully install OTAs. You have to have stock rom, stock recovery and possibly some /preload/ files that were deleted when you unlocked your bootloader. The quickest way to stock for OTA would be to flash a RUU. I would propose this route:
Option A
Lock your bootloader
Flash RUU 3.17.502.3
Receive OTA updates if they are still available
Option B
Lock your bootloader
Flash in bootloader: firmware 4.18.502.7
Flash RUU 4.18.502.7
Flash in bootloader: firmware 5.12.502.2
Flash TWRP 2.6.3.3
Download Guru Reset 5.12.502.2 and place on your sdcard
Boot into TWRP and install GURU Reset
For complete stock Say no to installing Root when exiting TWRP and Flash the Stock Recovery
Thanks for the feedback. I was a bit surprised to find out about needing to re-lock the bootloader even with stock recovery since a bunch of other places I looked said that I could use an unlocked bootloader as long as everything else was stock (just couldn't find a way to return to stock recovery without an RUU - which would require re-locking the bootloader - at the time). Used this (http://forum.xda-developers.com/showthread.php?t=2545227) from Majmoz's signature and got the relevant recovery.img from it. Since I had it, I figured I might as well try it before going through the process of re-locking the bootloader since being bounced out of the OTA and then going through the full process of relock-RUU-OTA anyhow was the worst that could happen. Turns out it worked.
So, for posterity's sake in case anyone else should come across a similar issue, everything I did (most of it probably unnecessary, but who knows):
-Made CWM backup (in case I happened to need to re-lock the bootloader which would wipe the device data to factory)
-Pulled that backup to my PC in case flashing to stock recovery wiped it (adb pull [backup directory, e.g. /mnt/shell/emulated/clockworkmod/backup/[folder]])
-Went into recovery from the bootloader, fastboot, plugged in the usb, and flashed the stock recovery (fastboot flash recovery [the downloaded stock recovery .img file in the platform-tools directory])
-Went back to the bootloader menu and entered the stock recovery and rebooted the device from there (I recall having to do that when I flashed CWM for the recovery to "stick", not sure if it was necessary here)
-Went into AT&T Software Update, let it download off the Wi-Fi, and let it apply. Did its thing with the image of the green downward arrow within the circulating arrows followed by reboot a few times, the "Android Update" screen where it runs through your applications, and voila, I am now on 4.4.2.
Updates:
-Have downloaded the updated stock recovery image.
-Flashed CWM Recovery back onto device
-Re-rooted via CWM (confirmed root)
-Made a new backup through CWM.
Now, if only I could figure out what the issue with the LTE signal is since I've never fiddled with that - guess I can heckle AT&T tech support for that.
lyciansarpedon said:
-Pulled that backup to my PC in case flashing to stock recovery wiped it (adb pull [backup directory, e.g. /mnt/shell/emulated/clockworkmod/backup/[folder]])
Click to expand...
Click to collapse
Flashing a recovery will not wipe anything but its a good call to backup on your computer :good:
-Went back to the bootloader menu and entered the stock recovery and rebooted the device from there (I recall having to do that when I flashed CWM for the recovery to "stick", not sure if it was necessary here)
Click to expand...
Click to collapse
no but again its a good practice to check if the recovery is working correctly.
Now, if only I could figure out what the issue with the LTE signal is since I've never fiddled with that - guess I can heckle AT&T tech support for that.
Click to expand...
Click to collapse
Have you checked you preferred network setting (GSM/CMDA/LTE AUTO)?
Is your apn correctly configured?
alray said:
Flashing a recovery will not wipe anything but its a good call to backup on your computer :good:
Click to expand...
Click to collapse
Good to know: the backup directory actually showed as empty while I still had stock, and then each backup's folder reappeared when I put CWM back on - was patting myself on the back for a few minutes there.
alray said:
Have you checked you preferred network setting (GSM/CMDA/LTE AUTO)?
Click to expand...
Click to collapse
It worked! Used *#*#4636#*# to pull that up (didn't know one could do that!) and, sure enough, it was on "WCDMA Preferred" for some reason. Switched it back to "GSM/CDMA/LTE AUTO" and my long-lost signal has returned.
Thanks a ton!
lyciansarpedon said:
Good to know: the backup directory actually showed as empty while I still had stock, and then each backup's folder reappeared when I put CWM back on - was patting myself on the back for a few minutes there.
It worked! Used *#*#4636#*# to pull that up (didn't know one could do that!) and, sure enough, it was on "WCDMA Preferred" for some reason. Switched it back to "GSM/CDMA/LTE AUTO" and my long-lost signal has returned.
Thanks a ton!
Click to expand...
Click to collapse
youre welcome glad it worked!
Hello everyone,
as a beginner in flashing roms/kernels, I flashed the dt2w (which is present on this forum) on my HTC One Mini 2. When I tried to reboot it, the screen was all blac. You could tell the thing was running, because of the vibration and sounds, but no image at all.
That's why I now need the stock kernel (original one?) and I don't know where to find it, neither if I have saved it somewhere, which I will flash using fastboot/adb.
Thank you
Linkalex1 said:
Hello everyone,
as a beginner in flashing roms/kernels, I flashed the dt2w (which is present on this forum) on my HTC One Mini 2. When I tried to reboot it, the screen was all blac. You could tell the thing was running, because of the vibration and sounds, but no image at all.
That's why I now need the stock kernel (original one?) and I don't know where to find it, neither if I have saved it somewhere, which I will flash using fastboot/adb.
Thank you
Click to expand...
Click to collapse
I believe someone has posted the stock boot.img somewhere(I can't seem to find it). You can also take the boot.img from the Stock Rom here
I am doing so right now, but will I be able to do the official upgrades? And is this a ROM or a kernel? Thank you
Linkalex1 said:
I am doing so right now, but will I be able to do the official upgrades? And is this a ROM or a kernel? Thank you
Click to expand...
Click to collapse
No , you won't be able to install official updates once you unlock your bootloader. But you can do so manually by flashing it through stock recovery with a relocked one. Just make sure you backup everything in the phone storage if you do it since it is wiped if every time you reunlock the bootloader.
csoulr666 said:
No , you won't be able to install official updates once you unlock your bootloader. But you can do so manually by flashing it through stock recovery with a relocked one. Just make sure you backup everything in the phone storage if you do it since it is wiped if every time you reunlock the bootloader.
Click to expand...
Click to collapse
How can I flash an OTA manually?
I've got an OTA (OTA_M8_MINI_UL_K44_SENSE60_Vodafone_CH-DE_2.18.166.2-2.18.166.1_release_448149.zip) but I am not able to install it.
I've already tried flashing a stock kernel (the boot.img from the link you've posted), I've flashed a stock recovery (M8_MINI_UL_Stock_Recovery_2.19.401.2.img) and I've relocked the bootloader.
But when I get the update notification and try to update, the phone goes to the stock recovery and the update proceeds but after about one quarter of the progress bar, it stops and shows the red exclamation mark (!).
I've also tried flashing the kernel and the recovery which are included in the OTA update, but still the same error.
Do you have an idea how I can manage to successfully update?
TomTomGo! said:
How can I flash an OTA manually?
I've got an OTA (OTA_M8_MINI_UL_K44_SENSE60_Vodafone_CH-DE_2.18.166.2-2.18.166.1_release_448149.zip) but I am not able to install it.
I've already tried flashing a stock kernel (the boot.img from the link you've posted), I've flashed a stock recovery (M8_MINI_UL_Stock_Recovery_2.19.401.2.img) and I've relocked the bootloader.
But when I get the update notification and try to update, the phone goes to the stock recovery and the update proceeds but after about one quarter of the progress bar, it stops and shows the red exclamation mark (!).
I've also tried flashing the kernel and the recovery which are included in the OTA update, but still the same error.
Do you have an idea how I can manage to successfully update?
Click to expand...
Click to collapse
I managed to do it, but it was a really dirty method. What I did was find the firmware.zip file from the Firmware I got from here, locked the bootloader and then flashed it via the bootloader(renaming it to PXXXIMG.zip,check exact file name before proceeding). Make sure you find the firmware of the OTA, or just get the firmware.zip from it.
This gets messy because it will result in you reunlocking the bootloader(which I assume you probably will) which will in turn wipe the internal storage completely. So backup up the Internal Storage AND your SD card before you proceed.
csoulr666 said:
I managed to do it, but it was a really dirty method. What I did was find the firmware.zip file from the Firmware I got from here, locked the bootloader and then flashed it via the bootloader(renaming it to PXXXIMG.zip,check exact file name before proceeding). Make sure you find the firmware of the OTA, or just get the firmware.zip from it.
This gets messy because it will result in you reunlocking the bootloader(which I assume you probably will) which will in turn wipe the internal storage completely. So backup up the Internal Storage AND your SD card before you proceed.
Click to expand...
Click to collapse
I've tried what you did. Seemed to update Bootloader, Recovery and Radio.
Then I rebooted, again got the update notification and tried to install it.
Bit still the same error, software update still fails.
I have read so much and information seems contradictory. One thing says if you root and take custom recovery you will never be able to update your phone via OTA. But I have been updating with fastboot so is updating like that still possible? And I understand you can get back to stock to take an OTA anyway. Is that correct?
It has been said that you cannot decrypt your N6 after taking 5.xx? (can't remember which) OTA. Is it not possible to decrypt with fastboot or adb after that particular update? If I just take all the OTA's before flashing twrp and rooting will I still be able to decrypt at the 5.1.1 version if I want to? And, there are custom kernels that allow things that the stock one won't allow. Currently using a 2013 Moto X rooted and twrp on 5.1. I've been updating by flashing stock recovery and system.img from sbf files and then taking the OTA successfully. Will the N6 still work that way?
Groid said:
I have read so much and information seems contradictory. One thing says if you root and take custom recovery you will never be able to update your phone via OTA. But I have been updating with fastboot so is updating like that still possible? And I understand you can get back to stock to take an OTA anyway. Is that correct?
It has been said that you cannot decrypt your N6 after taking 5.xx? (can't remember which) OTA. Is it not possible to decrypt with fastboot or adb after that particular update? If I just take all the OTA's before flashing twrp and rooting will I still be able to decrypt at the 5.1.1 version if I want to? And, there are custom kernels that allow things that the stock one won't allow. Currently using a 2013 Moto X rooted and twrp on 5.1. I've been updating by flashing stock recovery and system.img from sbf files and then taking the OTA successfully. Will the N6 still work that way?
Click to expand...
Click to collapse
OTA checks system and kernel and if anything is changed, OTA will fail. That includes root.
Fastboot flashing a system.img, boot.img and recovery.img would be enough to unroot and get back to stock however, you would only want to OTA if the rom you wanted didn't have a factory image.
Decryption is possible on all ROMs. It's just a custom kernel (boot.img) that doesn't force encryption on boot, then format userdata to get rid of existing encryption. Of course you're modified now so no OTA.
People care so pointlessly about OTA. Advice: forget about it and fastboot flash to update, or easier yet, wait for someone to package it up into a recovery flashable zip