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.
Hi and thanks for reading. I have searched for the solution but found no definitive answer.
I am used to flashing Samsung mobiles and a few others and have used the toolkits to get the custom recoveries installed.
In this case i simply cannot get a reliable CWM installed on my unlocked bootloader version of this RAZR i.
The bootloader screen mentions a maximum size of "100mb" but the recovery imgs i use are well under this, i am also using the Fastboot method to get the recovery installed but always receive this error and am now at a dead-end in regards to flashing this phone.
---
Incidentally flashing an original ROM through RSD-Lite also failed at a certain stage of the process but didn't cause any issue actually booting into the phone itself.
Thanks in advance for any assistance! :good:
I realised I haven't re-encrypted my Titan yet since wiping it to correct some issues but when I tried, it just reboots. I've run into this issue before, which is caused by having a custom recovery (in my case TWRP) installed as Android uses the stock recovery to do the encryption. I don't particularly want to mess around flashing back the stock recovery and then back to TWRP, so is there a way to encrypt the phone without doing that, perhaps using ADB?
Bump. If the only way to encrypt it is to flash back the stock Recovery, could someone point me to where I can find some instructions on doing this and a download link please?
EDIT: Never mind, I found this now http://forum.xda-developers.com/showthread.php?t=2635706 so I'll use that to flash stock recovery.
Hi Nexus 6 Community
Im new to own a Nexus 6 but Im an "enthusiastic flasher" per say. I've being looking around with no luck so I was hopping someone will point me to the right direction:
Usually whenever I flash anything on my previous phones I like to flash TWRP again in case of boot loops or something flashing bad that could delete or corrupt my custom recovery. I'm rooted and installed the latest TWRP through fastboot, but as I previously said, I would like to have a flashable zip to ensure my recovery will be installed and have a higher chance of not being locked out of my phone.
Or I'd notice you can flash images through TWRP, will this re-install my recovery using the TWRP .img file?
I really appreciate all for your help, thanks
Once you boot into twrp for the first time it patches /system to prevent the stock rom from replacing it unless you choose the "keep system mounted as read-only." This option is only offered to you if you boot into twrp with an untouched /system. And as for worrying about being locked out of your phone, as long as you have an unlocked bootloader you can always use a google factory image to get back to stock w/o a custom recovery.
I'd assume no one's made a flashable zip for twrp because reflashing it wouldn't accomplish much of anything if you already have twrp to flash it in.
Trying to flash TWRP to a smart watch. Found the correct version on TWRP.ME and flash it.
Everything good until I let the watch reboot into system and then try to boot back into TWRP.
Stock recovery has replaced TWRP. I know this is a known problem with some stock ROMS, but I DON'T
know how to get around it. This is an old Samsung Gear Live and I've seen threads where others have claimed to be
successful with this installation.
Anyone??