Related
My question is similar to 'nikpmr's troubles but different enough I think they deserve a separate post.
The Problem as UnderstoodI was trying to root my device following the guide at this website. It's so simple it's a wonder I messed up. I think my failure was that I thought the drivers installed when I connected the phone were enough so I skipped that step. Then when running fastboot flash recovery.img the install failed. So I saw on some forum that it was supposed to be fastboot flash boot recovery.img of course now I know if anything it ought to have been "recovery" not "boot".
What I've Tried & Partial SolutionAt first I was just stuck in a boot loop and selecting "sideload" from the CWM recovery failed to allow me to connect with ADB or fastboot. i.e. Running "fastboot devices" and "adb devices" both returned as having no devices connected to my computer. So I installed the HTC Sync and promptly uninstalled the non driver parts of the app. Then I installed USBdeview and used it to uninstall all the USB devices associated with my HTC First. After doing that I learned booting into HBOOT allowed me to connect to the computer using fastboot and after then booting to the CWM Recovery I was able to connect using ADB to do a sideload. So I guess I'm about halfway there. Unfortunately after looking up the newest RUU and attempting to sideload it using "adb sideload OTA_MYST_UL_1.08.502.1-1.08.502.4.zip" the sideload failed. After selecting "- install zip from sideload" I get a message twice of "failed to open driver control: No such file or directory". It also failed when I attempted it with a similar fastboot command. So from all that I surmise my ROM is ruined and just needs to be replaced.
QuestionSo how do I go about replacing this ROM and boot partition? And, which ROM should I use? Is the one I got from the RUU site suitable? And what about the radio? I just need my phone to work. I can worry about rooting later. At this point I think I know what's happened but I don't know where to begin reading to figure out how to fix it myself.
Thanks for reading,
Relevant HBOOT text:
Code:
*** TAMPERED ***
*** UNLOCKED ***
MYSTUL PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-1.15.40.00.13_2
OpenDSP-v9.2.0268.1214
eMMC-boot
Mar 22 2013,21:29:50:1682
1. you had to type in fastboot flash recovery recovery.img NOT fastboot flash boot recovery.img
Well there was an actual all in 1 tool to get cwm/twrp & root with a click for this specific device somewhere around these threads.
1) what exactly is the problem? (Sorry it was just so many words)
I don't think side loading the RUU would work bc I haven't heard its possible to flash it in the phone itself.
2) why don't you just sideload an existing pre-rooted ROM instead of the RUU file?
3) I see you're s-on, did you try flashing just the boot.IMG from the ROM you've got on it?
BTW I've only had luck with twrp on having it successfully detected when wanting to sideload
abrahammmmmmm_ said:
Well there was an actual all in 1 tool to get cwm/twrp & root with a click for this specific device somewhere around these threads.
1) what exactly is the problem? (Sorry it was just so many words)
I don't think side loading the RUU would work bc I haven't heard its possible to flash it in the phone itself.
2) why don't you just sideload an existing pre-rooted ROM instead of the RUU file?
3) I see you're s-on, did you try flashing just the boot.IMG from the ROM you've got on it?
BTW I've only had luck with twrp on having it successfully detected when wanting to sideload
Click to expand...
Click to collapse
1) The issue is I did "fastboot flash boot recovery.img" rather than "fastboot flash recovery.img" now I don't seem to have a boot mount point.
2) That sounds best. I didn't realize the RUU want a flashable ROM. More I just have to find the updated stable stock ROM.
3) I didn't have a ROM on it. I was just trying to root stock. Seems like I'm pretty close once I find that ROM.
Thanks y'all! Between your answers I think I have enough to go on. Feel free to point me to your preferred stable ROM. I'm content with stock but it would be nice to have Tiranium BU.
bnjo said:
1) The issue is I did "fastboot flash boot recovery.img" rather than "fastboot flash recovery.img" now I don't seem to have a boot mount point.
2) That sounds best. I didn't realize the RUU want a flashable ROM. More I just have to find the updated stable stock ROM.
3) I didn't have a ROM on it. I was just trying to root stock. Seems like I'm pretty close once I find that ROM.
Thanks y'all! Between your answers I think I have enough to go on. Feel free to point me to your preferred stable ROM. I'm content with stock but it would be nice to have Tiranium BU.
Click to expand...
Click to collapse
Right now our most stable stock ROM is our rooted stock ROM
http://forum.xda-developers.com/showthread.php?t=2287811
We currently have 2 very able recognized devs working on CyanogenMod. You can expect something new in the near future but until then what I've showed you is the best.
Have any problems just come back to the thread
Success!
abrahammmmmmm_ said:
Right now our most stable stock ROM is our rooted stock ROM
http://forum.xda-developers.com/showthread.php?t=2287811
We currently have 2 very able recognized devs working on CyanogenMod. You can expect something new in the near future but until then what I've showed you is the best.
Have any problems just come back to the thread
Click to expand...
Click to collapse
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
bnjo said:
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
Click to expand...
Click to collapse
Great! glad to hear I could help. Yes it's always nice knowing when something I've said has helped someone in any way
bnjo said:
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
Click to expand...
Click to collapse
i think what happened, when you typed in "fastboot flash boot recovery.img" is this
boot, is also known as kernel in aosp and rom building terms, because if you look inside a rom.zip, you will see that the kernel is the boot.img
so what happened is you flashed a recovery as kernel, and duh it wont boot cause if the kernel doesnt work, the os doesnt either
so what YOU did is you simply reflashed the stock kernel, usually after changing a kernel, it takes a while to boot cause...well you get it right?
the kernel is what android is based off of, kind of like ubuntu, its a linux os based on the original linux kernel.
russian392 said:
usually after changing a kernel, it takes a while to boot cause...well you get it right?
Click to expand...
Click to collapse
Yes I get it.
russian392 said:
i think what happened, when you typed in "fastboot flash boot recovery.img" is this
boot, is also known as kernel in aosp and rom building terms, because if you look inside a rom.zip, you will see that the kernel is the boot.img
so what happened is you flashed a recovery as kernel, and duh it wont boot cause if the kernel doesnt work, the os doesnt either
so what YOU did is you simply reflashed the stock kernel, usually after changing a kernel, it takes a while to boot cause...well you get it right?
the kernel is what android is based off of, kind of like ubuntu, its a linux os based on the original linux kernel.
Click to expand...
Click to collapse
That's what I thought happened. If I had stopped to read the help on fastboot before running "fastboot flash boot recovery.img" I wouldn't have made that mistake because I would have seen I wanted to flash recovery. One thing I *did not* know, which I'm glad to know, was that the boot.img contains the kernal. I was thinking Android was more similar to IBM style PCs than it is and therefore the boot.img was analogous to a bootloader like grub or lilo.
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
bnjo said:
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
Click to expand...
Click to collapse
in a nutshell yes, the boot.img uses the fstab
btw 10 posts you'll be "verified"
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
Click to expand...
Click to collapse
Yep that's correct.
The name correlation is booting up requires kernel there for kernel is called beet.IMG
Thing about custom kernels, they aren't like that and simply contain modded files and pretty much an in packaged kernel.
Sent from my HTC first using xda app-developers app
stock recovery
please can anyone send me the stock recovery.img
when i try to get it from RUU it says archive is corrupted
astrit1995 said:
please can anyone send me the stock recovery.img
when i try to get it from RUU it says archive is corrupted
Click to expand...
Click to collapse
here:
http://androidfiles.org/getdownload.php?file=MystUL/Stock_Roms/stockrecovery.img
if you help, press thanks!!
Serupo said:
here:
http://androidfiles.org/getdownload.php?file=MystUL/Stock_Roms/stockrecovery.img
if you help, press thanks!!
Click to expand...
Click to collapse
Thank you for your help,i solved my problem yesterday but i think im gona need this sometime...
Okay, so I have an HK m8 on sprint, FW 1.54.654.13.
I was originally on Viper 1.8.0, but wanted to upgrade to 2.0.0, so I went back to my stock backup, with the aforementioned software version.
After restoring that backup I realized I needed to also flash a stock recovery in order to take the OTA. So I flashed the 'Stock Recovery From 1.54.651.8 OTA' over adb from this thread: http://forum.xda-developers.com/showthread.php?t=2736048
So, since flashing that recovery my phone seems to not have a recovery anymore; infact, it constantly reboots after about 1 minute of being booted to system. When I boot into recovery, I get a symbol of a phone with an "!" in a triangle over it.
Where did I go wrong? What recovery should I be using? I can re-flash TWRP, but it seems I still get the bootloop, even though it does actually boot into system (which I've never seen happen from a bootloop). It's been like this for 12+ hours, and no amount of searching has helped me out thus far, so I'm hoping someone here could help me out a little.
xLoveHateLegend said:
Okay, so I have an HK m8 on sprint, FW 1.54.654.13.
I was originally on Viper 1.8.0, but wanted to upgrade to 2.0.0, so I went back to my stock backup, with the aforementioned software version.
After restoring that backup I realized I needed to also flash a stock recovery in order to take the OTA. So I flashed the 'Stock Recovery From 1.54.651.8 OTA' over adb from this thread: http://forum.xda-developers.com/showthread.php?t=2736048
So, since flashing that recovery my phone seems to not have a recovery anymore; infact, it constantly reboots after about 1 minute of being booted to system. When I boot into recovery, I get a symbol of a phone with an "!" in a triangle over it.
Where did I go wrong? What recovery should I be using? I can re-flash TWRP, but it seems I still get the bootloop, even though it does actually boot into system (which I've never seen happen from a bootloop). It's been like this for 12+ hours, and no amount of searching has helped me out thus far, so I'm hoping someone here could help me out a little.
Click to expand...
Click to collapse
When I boot into recovery, I get a symbol of a phone with an "!" in a triangle over it.
Click to expand...
Click to collapse
This is stock recovery
You could pull the stock recovery from the HK firmware...hopefully that will get you back to normal.
Worse comes to worse run the RUU.
I do not have the recovery.img in my backup. I'm also not S-off, so I think the only way I can upgrade my firmware is through OTA from what I understand, correct? If I could just flash the proper stock recovery I think I would be fine from there?
xLoveHateLegend said:
I do not have the recovery.img in my backup. I'm also not S-off, so I think the only way I can upgrade my firmware is through OTA from what I understand, correct? If I could just flash the proper stock recovery I think I would be fine from there?
Click to expand...
Click to collapse
You can flash the full firmware while being s-on.
Alright, thanks! Can I go ahead and RUU 2.22.401.4 directly, or should I just RUU to my current stock firmware and just OTA from there?
Sent from my 831C using XDA Free mobile app
xLoveHateLegend said:
Alright, thanks! Can I go ahead and RUU 2.22.401.4 directly, or should I just RUU to my current stock firmware and just OTA from there?
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
2.22.401.4 is not for Sprint.
I would go with the current HK RUU and start fresh.
BD619 said:
2.22.401.4 is not for Sprint.
I would go with the current HK RUU and start fresh.
Click to expand...
Click to collapse
Damn. Alright, well from what I can see 2.16.654.4 is the latest for Sprint. After downloading O.M.J.'s RUU, would I be good to go straight to viper 2.0.0?
Sent from my 831C using XDA Free mobile app
xLoveHateLegend said:
Damn. Alright, well from what I can see 2.16.654.4 is the latest for Sprint. After downloading O.M.J.'s RUU, would I be good to go straight to viper 2.0.0?
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
After you install TWRP recovery, yes.
For future reference Viper does OTA's which are not the same as Sprint OTA's...download the Viper OTA and flash in twrp.
Magnum_Enforcer said:
After you install TWRP recovery, yes.
Click to expand...
Click to collapse
Yes of course, thank you.
BD619 said:
For future reference Viper does OTA's which are not the same as Sprint OTA's...download the Viper OTA and flash in twrp.
Click to expand...
Click to collapse
Yes, I am aware. But on 1.8.0 I did not get an OTA. Maybe because I'll get it after I upgrade my FW. So after RUUing then reinstalling TWRP, if I restore my viper 1.8.0 backup, I can just OTA to 2.0.0?
xLoveHateLegend said:
Yes of course, thank you.
Yes, I am aware. But on 1.8.0 I did not get an OTA. Maybe because I'll get it after I upgrade my FW. So after RUUing then reinstalling TWRP, if I restore my viper 1.8.0 backup, I can just OTA to 2.0.0?
Click to expand...
Click to collapse
Should be able to...
But if you are going to RUU why not just download the full rom and clean flash.
BD619 said:
Should be able to...
But if you are going to RUU why not just download the full rom and clean flash.
Click to expand...
Click to collapse
I tried flashing the full Rom per your suggestion, but after flashing the 2.0.0 Rom, it's like my phone has no OS and can only boot to bootloader or recovery, not system at all.
I also tried extracting the latest hk ruu to the root of my external SD card and running it through bootloader to no avail.
I feel like I'm missing a vital part of information here. I've never really ruu'd before so I'm new to that but I'm pretty stumped on this whole thing.
xLoveHateLegend said:
I tried flashing the full Rom per your suggestion, but after flashing the 2.0.0 Rom, it's like my phone has no OS and can only boot to bootloader or recovery, not system at all.
I also tried extracting the latest hk ruu to the root of my external SD card and running it through bootloader to no avail.
I feel like I'm missing a vital part of information here. I've never really ruu'd before so I'm new to that but I'm pretty stumped on this whole thing.
Click to expand...
Click to collapse
get the drivers for your phone + adb, rename the firmware update to firmware.zip, put it in /sdk/platform-tools
put the phone in fastboot, make sure it says fastboot USB and type fastboot devices in terminal to confirm it's connected.
then type in terminal Fastboot oem rebootRUU (capitalization matters.)
your screen will go black with a greyish HTC logo, then type in fastboot flash zip firmware.zip
once it's done doing it's thing type fastboot reboot
this method is pretty much failproof
EDIT: also, if you're flashing ONLY the sprint 2.0.0 update, you'll have to be on capt's twrp 2.7.0.7, otherwise you'll have to flash the full rom, boot into it, reboot into 2.7.1.0, and dirty flash the sprint viper ROM. Hope that helps, cheers >;3
yorisou said:
get the drivers for your phone + adb, rename the firmware update to firmware.zip, put it in /sdk/platform-tools
put the phone in fastboot, make sure it says fastboot USB and type fastboot devices in terminal to confirm it's connected.
then type in terminal Fastboot oem rebootRUU (capitalization matters.)
your screen will go black with a greyish HTC logo, then type in fastboot flash zip firmware.zip
once it's done doing it's thing type fastboot reboot
this method is pretty much failproof
EDIT: also, if you're flashing ONLY the sprint 2.0.0 update, you'll have to be on capt's twrp 2.7.0.7, otherwise you'll have to flash the full rom, boot into it, reboot into 2.7.1.0, and dirty flash the sprint viper ROM. Hope that helps, cheers >;3
Click to expand...
Click to collapse
Thanks for the reply! From my understanding, you need to be S-Off for that method, which I am not.
The method I attempted to use is this one, from O.M.J's thread here http://forum.xda-developers.com/showthread.php?t=2729173
using 7zip, extract 0P6BIMG.zip to ext sd card
-boot into bootloader
-make sure*hboot*is highlighted, press power button
-it will scan your ext_sd card, then ask if you want to start the update
-press volume up & let it do it's thing...
The problem is, it scans my external SD card just fine but never asks if I want to start the update, nor do I get the option to press volume up etc... I am on captains twrp 2.7.0.7, as I've seen many other users confirm success with this recovery.
Also, I don't see just an update, it seems the Sprint version of the Rom I downloaded is the full rom. I actually did get it to boot once and got this (see screenshot), but it was a dirty flash.
Sent from my 831C using XDA Free mobile app
xLoveHateLegend said:
Thanks for the reply! From my understanding, you need to be S-Off for that method, which I am not.
The method I attempted to use is this one, from O.M.J's thread here http://forum.xda-developers.com/showthread.php?t=2729173
using 7zip, extract 0P6BIMG.zip to ext sd card
-boot into bootloader
-make sure*hboot*is highlighted, press power button
-it will scan your ext_sd card, then ask if you want to start the update
-press volume up & let it do it's thing...
The problem is, it scans my external SD card just fine but never asks if I want to start the update, nor do I get the option to press volume up etc... I am on captains twrp 2.7.0.7, as I've seen many other users confirm success with this recovery.
Also, I don't see just an update, it seems the Sprint version of the Rom I downloaded is the full rom. I actually did get it to boot once and got this (see screenshot), but it was a dirty flash.
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
Did you re-lock your bootloader?
xLoveHateLegend said:
Thanks for the reply! From my understanding, you need to be S-Off for that method, which I am not.
The method I attempted to use is this one, from O.M.J's thread here http://forum.xda-developers.com/showthread.php?t=2729173
using 7zip, extract 0P6BIMG.zip to ext sd card
-boot into bootloader
-make sure*hboot*is highlighted, press power button
-it will scan your ext_sd card, then ask if you want to start the update
-press volume up & let it do it's thing...
The problem is, it scans my external SD card just fine but never asks if I want to start the update, nor do I get the option to press volume up etc... I am on captains twrp 2.7.0.7, as I've seen many other users confirm success with this recovery.
Also, I don't see just an update, it seems the Sprint version of the Rom I downloaded is the full rom. I actually did get it to boot once and got this (see screenshot), but it was a dirty flash.
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
http://venomroms.com/htc-one-m8/
download the full one and the sprint one, flash the first, reboot all the way (doubt you have to finish the automatic setup) then reboot into recovery and dirty flash the sprint one without wiping anything. It'll connect to the CDMA network instead of the GSM one with no problems, you don't even need to be on 2.7.0.7
And if it isn't working in HBOOT just go into recovery and adb sideload it, you shouldn't need to be s-off to do that. Enter adb sideload and just type in a terminal adb sideload (filename)
EDIT: idk why but that picture made me lol irl, KEEP CALM AND KANG AWAY
Alright giving that a shot now, thanks
That message is hilarious to me now, but it wasn't at the time xD
Edit: is it safe to dirty flash the first one, coming from 1.8.0? Also no, I haven't relocked my boot loader.
xLoveHateLegend said:
Alright giving that a shot now, thanks
That message is hilarious to me now, but it wasn't at the time xD
Edit: is it safe to dirty flash the first one, coming from 1.8.0? Also no, I haven't relocked my boot loader.
Click to expand...
Click to collapse
RUU won't run unless you re-lock the bootloader since you are s-on
BD619 said:
RUU won't run unless you re-lock the bootloader since you are s-on
Click to expand...
Click to collapse
Ahhh, okay makes sense now. My m7 was s-off and that was the first and last time I ever did a RUU. If I re-lock the boot loader, do I have to go through htcdev again to unlock once more, or will having it locked again not effect root?
Sent from my 831C using XDA Free mobile app
xLoveHateLegend said:
Ahhh, okay makes sense now. My m7 was s-off and that was the first and last time I ever did a RUU. If I re-lock the boot loader, do I have to go through htcdev again to unlock once more, or will having it locked again not effect root?
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
fastboot oem relock
should do it
Hellos guys,
I am trying to find the stock recovery for T-mobile US 6.10.531.10 (NOT 6.10.531.9) . Does anybody has it or point me on the right direction? I want to update my phone through OTA so I can get lollipop however I cannot find the stock recovery.
I am S-On all stock except for the recovery, I had TWRP so I can make backups. Now I want to install back the stock recovery so i can upgrade but I don't seem to find it anywhere. I managed to find the RUU but the recovery image is not inside the "rom.zip" on my Temp folder when I run it. These are the only files that it shows:
android-info.txt
dzdata_16g.hdr
dzdata_32g.hdr
dzdata_64g.hdr
tp_HMX852XD.img
boot_signed.img
dzdata_16.img
dzdata_32.img
dzdata_64.img
Am I missing something? Please help. I have tried to find it the whole day with no luck.
Also see the the screenshot.
adtamez said:
Hellos guys,
I am trying to find the stock recovery for T-mobile US 6.10.531.10 (NOT 6.10.531.9) . Does anybody has it or point me on the right direction? I want to update my phone through OTA so I can get lollipop however I cannot find the stock recovery.
I am S-On all stock except for the recovery, I had TWRP so I can make backups. Now I want to install back the stock recovery so i can upgrade but I don't seem to find it anywhere. I managed to find the RUU but the recovery image is not inside the "rom.zip" on my Temp folder when I run it. These are the only files that it shows:
android-info.txt
dzdata_16g.hdr
dzdata_32g.hdr
dzdata_64g.hdr
tp_HMX852XD.img
boot_signed.img
dzdata_16.img
dzdata_32.img
dzdata_64.img
Am I missing something? Please help. I have tried to find it the whole day with no luck.
Also see the the screenshot.
Click to expand...
Click to collapse
just run the Lollipop RUU, same as the OTA but its the full thing rather than an OTA: http://www.htc.com/us/support/htc-one-t-mobile/news/ follow the manual update instructions, download is at the bottom.
edit: it will wipe your phone, so backup anything you want to keep first.
Seanie280672 said:
just run the Lollipop RUU, same as the OTA but its the full thing rather than an OTA: http://www.htc.com/us/support/htc-one-t-mobile/news/ follow the manual update instructions, download is at the bottom.
edit: it will wipe your phone, so backup anything you want to keep first.
Click to expand...
Click to collapse
Seanie, thank you for your reply. I need the stock recovery because precisely I was trying to avoid wiping my phone. I am just a very small step away to be able to update without wiping, I just can't find this stock recovery. Why is it that the recovery.img it is not inside the rom.zip RUU? Am I missing something?
Currently I flashed the stock recovery 6.10.5310.9 and i tried to install the OTA but when it gets to the recovery it looks like it starts installing moving the green line a little bit but soon after I get a red triangle and stops, which I am assuming it is because i do not have the proper recovery.
Any help so i do not need to wipe will be greatly appreciate it.
Thanks!
adtamez said:
Seanie, thank you for your reply. I need the stock recovery because precisely I was trying to avoid wiping my phone. I am just a very small step away to be able to update without wiping, I just can't find this stock recovery. Why is it that the recovery.img it is not inside the rom.zip RUU? Am I missing something?
Currently I flashed the stock recovery 6.10.5310.9 and i tried to install the OTA but when it gets to the recovery it looks like it starts installing moving the green line a little bit but soon after I get a red triangle and stops, which I am assuming it is because i do not have the proper recovery.
Any help so i do not need to wipe will be greatly appreciate it.
Thanks!
Click to expand...
Click to collapse
ok, you cant take it out of the RUU.zip as its an encrypted RUU, so take it out of the OTA.
download the OTA as normal, but select install later, then plug your phone into the computer and copy the OTA.zip to your computer from your phone, its in the internal storage, downloads folder, its just a zip file, so once its on your computer, open it with WinRAR or whatever you use to open zip files and in there you will see firmware.zip, open that too and take out recovery.img, flash it like any other recovery, then reboot and try and update again.
If the OTA then fails again, it will be down to modified system files or root, you will have no choice but to backup and use the full RUU.
Seanie280672 said:
ok, you cant take it out of the RUU.zip as its an encrypted RUU, so take it out of the OTA.
download the OTA as normal, but select install later, then plug your phone into the computer and copy the OTA.zip to your computer from your phone, its in the internal storage, downloads folder, its just a zip file, so once its on your computer, open it with WinRAR or whatever you use to open zip files and in there you will see firmware.zip, open that too and take out recovery.img, flash it like any other recovery, then reboot and try and update again.
Click to expand...
Click to collapse
oh I see. Thank you very much...quick question though: I am currently on version 6.10.513.10 the OTA is to upgrade to version 7.18.513.2, if i extract the recovery from this OTA i will be flashing the 7.18. recovery, isn't? Don't I need the recovery from 6.10 in order to be able to upgrade? If so, this is why i was looking also for the 6.10.513.10 OTA but I cannot find it.
Thank you again!
adtamez said:
oh I see. Thank you very much...quick question though: I am currently on version 6.10.513.10 the OTA is to upgrade to version 7.18.513.2, if i extract the recovery from this OTA i will be flashing the 7.18. recovery, isn't? Don't I need the recovery from 6.10 in order to be able to upgrade? If so, this is why i was looking also for the 6.10.513.10 OTA but I cannot find it.
Thank you again!
Click to expand...
Click to collapse
the OTA will check to see if you have 6.10.513.10 or 7.18.513.2 recovery, cant be anything earlier than those 2, current or previous, recovery update by the OTA will just be skipped.
Seanie280672 said:
the OTA will check to see if you have 6.10.513.10 or 7.18.513.2 recovery, cant be anything earlier than those 2, current or previous, recovery update by the OTA will just be skipped.
Click to expand...
Click to collapse
I see! Great news! Good to know. So the OTA can be install with a newer stock recovery (matching the OTA I presume).
I am currently at work without my cell phone but I will try this, as soon as I get back home and post the results.
One last thing, to flash the stock recovery is as simple as "fastboot flash recovery recovery.img" (or whatever the recovery file .img name is), correct?
I do not need to lock the bootloader in order to upgrade using the OTA as long as everything else is still stock. ...I do have root though, but I also read that this shouldn't be a problem either, correct?
Thank you sooo much!
adtamez said:
I see! Great news! Good to know. So the OTA can be install with a newer stock recovery (matching the OTA I presume).
I am currently at work without my cell phone but I will try this, as soon as I get back home and post the results.
One last thing, to flash the stock recovery is as simple as "fastboot flash recovery recovery.img" (or whatever the recovery file .img name is), correct?
I do not need to lock the bootloader in order to upgrade using the OTA as long as everything else is still stock. ...I do have root though, but I also read that this shouldn't be a problem either, correct?
Thank you sooo much!
Click to expand...
Click to collapse
No need to lock the bootloader for an ota, root might be a problem as it modifies system files, just give it a go, and yes, the flash of the recovery is the same as any other recovery file.
Seanie280672 said:
No need to lock the bootloader for an ota, root might be a problem as it modifies system files, just give it a go, and yes, the flash of the recovery is the same as any other recovery file.
Click to expand...
Click to collapse
Got it. I'll try and post results. Thank you very much.
adtamez said:
Got it. I'll try and post results. Thank you very much.
Click to expand...
Click to collapse
Seanie, all went as expected! It worked. I was able to extract the recovery.img file from the firmware.zip inside the 7.18 OTA zip file that was downloaded to the internal storage. Then proceed to flash it as any other recovery with fastboot. Afer that, the OTA update installed with o problem. Having root did not mattered. I did have to root it again though.
Thank you so much for your support!!! :good:
Worked for me as well, thank you.
I received a push notice to download and install Sprint HTC One (M8) Software Update 4.25.651.14 which was released on 4/9/15 with Wi-Fi Calling enhancements. My phone is rooted. I use Super SU Pro. I use TWRP (Sprint) for my custom recovery. Never had any problems with applying previous OTA updates. I connect via ADB shell and flash stock recovery for version 4.20.651.10 currently installed on my phone. I use One_M8_All-In-One_Kit_v2.0 to perform the shell commands.
I apply the OTA update in the stock recovery from my phone and everything looks good, but when the phone restarts it gets frozen in the white "splash" screen where it says "HTC One powered by Android". I waited over 15 minutes and nothing happened. I was able to recover my phone by booting into the bootloader and flashing TWRP then restoring my nandroid. I could see in the bootloader screen that the firmware was updated to the latest version.
Does anyone know what is causing the phone to freeze after the firmware is updated and the system restarts?
I tried to manually install the OTA zip file using TWRP from my phone to update the software. I selected the Zip file saved in the phone's root folder and used TWRP to apply the update, but got an error message that it "failed".
Does anyone know what steps are necessary to manually apply the OTA software update?
daodeltaforce said:
I received a push notice to download and install Sprint HTC One (M8) Software Update 4.25.651.14 which was released on 4/9/15 with Wi-Fi Calling enhancements. My phone is rooted. I use Super SU Pro. I use TWRP (Sprint) for my custom recovery. Never had any problems with applying previous OTA updates. I connect via ADB shell and flash stock recovery for version 4.20.651.10 currently installed on my phone. I use One_M8_All-In-One_Kit_v2.0 to perform the shell commands.
I apply the OTA update in the stock recovery from my phone and everything looks good, but when the phone restarts it gets frozen in the white "splash" screen where it says "HTC One powered by Android". I waited over 15 minutes and nothing happened. I was able to recover my phone by booting into the bootloader and flashing TWRP then restoring my nandroid. I could see in the bootloader screen that the firmware was updated to the latest version.
Does anyone know what is causing the phone to freeze after the firmware is updated and the system restarts?
I tried to manually install the OTA zip file using TWRP from my phone to update the software. I selected the Zip file saved in the phone's root folder and used TWRP to apply the update, but got an error message that it "failed".
Does anyone know what steps are necessary to manually apply the OTA software update?
Click to expand...
Click to collapse
You might wanna try posting this in the m8 thread. This is for the m7
sent from your moms house
janke438 said:
You might wanna try posting this in the m8 thread. This is for the m7
sent from your moms house
Click to expand...
Click to collapse
Um he stated it was the M8 update and this is the M8 Forum.
schmeggy929 said:
Um he stated it was the M8 update and this is the M8 Forum.
Click to expand...
Click to collapse
Lol my bad. Don't know why I ended up in this thread considering I never look outside of favorites. Disregaurd my previous post .
sent from your moms house
daodeltaforce said:
I received a push notice to download and install Sprint HTC One (M8) Software Update 4.25.651.14 which was released on 4/9/15 with Wi-Fi Calling enhancements. My phone is rooted. I use Super SU Pro. I use TWRP (Sprint) for my custom recovery. Never had any problems with applying previous OTA updates. I connect via ADB shell and flash stock recovery for version 4.20.651.10 currently installed on my phone. I use One_M8_All-In-One_Kit_v2.0 to perform the shell commands.
I apply the OTA update in the stock recovery from my phone and everything looks good, but when the phone restarts it gets frozen in the white "splash" screen where it says "HTC One powered by Android". I waited over 15 minutes and nothing happened. I was able to recover my phone by booting into the bootloader and flashing TWRP then restoring my nandroid. I could see in the bootloader screen that the firmware was updated to the latest version.
Does anyone know what is causing the phone to freeze after the firmware is updated and the system restarts?
I tried to manually install the OTA zip file using TWRP from my phone to update the software. I selected the Zip file saved in the phone's root folder and used TWRP to apply the update, but got an error message that it "failed".
Does anyone know what steps are necessary to manually apply the OTA software update?
Click to expand...
Click to collapse
I believe it is is still true that you cant OTA with a unlocked bootloader regardless if you reinstall the stock recovery. You need to relock bootloader install stock recovery. It is much safer and easier to wait until there is a flashable firmware upgrade. The OTA did not install correctly hence the white splash screen.
Look here and READ carefully and install the right zip.
---------- Post added at 10:10 PM ---------- Previous post was at 10:07 PM ----------
janke438 said:
Lol my bad. Don't know why I ended up in this thread considering I never look outside of favorites. Disregaurd my previous post .
sent from your moms house
Click to expand...
Click to collapse
Haha I was like WTH? I had to look twice to make sure I wasn't in the M7 forum.
schmeggy929 said:
Um he stated it was the M8 update and this is the M8 Forum.
Click to expand...
Click to collapse
janke438 said:
Lol my bad. Don't know why I ended up in this thread considering I never look outside of favorites. Disregaurd my previous post .
sent from your moms house
Click to expand...
Click to collapse
Guess I should have noted I move it
flash the recovery from the ota.zip in fastboot then rename the ota to update.zip and manually install it from the stock recovery. also "fastboot erase cache" before booting your phone. Btw if you are using xposed(or any scripts) it can cause problems, reinstall any mods after first booting the phone.
daodeltaforce said:
I received a push notice to download and install Sprint HTC One (M8) Software Update 4.25.651.14 which was released on 4/9/15 with Wi-Fi Calling enhancements. My phone is rooted. I use Super SU Pro. I use TWRP (Sprint) for my custom recovery. Never had any problems with applying previous OTA updates. I connect via ADB shell and flash stock recovery for version 4.20.651.10 currently installed on my phone. I use One_M8_All-In-One_Kit_v2.0 to perform the shell commands.
I apply the OTA update in the stock recovery from my phone and everything looks good, but when the phone restarts it gets frozen in the white "splash" screen where it says "HTC One powered by Android". I waited over 15 minutes and nothing happened. I was able to recover my phone by booting into the bootloader and flashing TWRP then restoring my nandroid. I could see in the bootloader screen that the firmware was updated to the latest version.
Does anyone know what is causing the phone to freeze after the firmware is updated and the system restarts?
I tried to manually install the OTA zip file using TWRP from my phone to update the software. I selected the Zip file saved in the phone's root folder and used TWRP to apply the update, but got an error message that it "failed".
Does anyone know what steps are necessary to manually apply the OTA software update?
Click to expand...
Click to collapse
I'm assuming you're s-on? From what I know if you have a system file that has been modified, the OTA won't work, you have to have a stock non-rooted ROM if you're going to take the OTA.
Check out this link http://forum.xda-developers.com/showthread.php?t=2729173 if you're s-on relock your bootloader first.
Hope this helps, good luck!
OTA.zip
Vcek said:
flash the recovery from the ota.zip in fastboot then rename the ota to update.zip and manually install it from the stock recovery. also "fastboot erase cache" before booting your phone. Btw if you are using xposed(or any scripts) it can cause problems, reinstall any mods after first booting the phone.
Click to expand...
Click to collapse
Thank you Vcek. It sounds like I need to do these steps while tethered to my PC in the ADB shell? I will try this method. Maybe one of my mistakes was I did not use the stock recovery from the latest OTA.zip. I had used the previous version OTA.zip's stock recovery to perform the software update installation from my phone.
Some people say I need to RELOCK the bootloader but I have never needed to do this to perform any of the previous OTA.zip updates. In fact, updating my rooted phone has been very easy until I ran into this problem with the latest OTA.zip update. I simply flashed the previous OTA.zip stock recovery tethered to my PC in ADB shell, then ran the latest OTA.zip update saved to my phone's internal storage while my phone remained rooted. Of course, after the OTA.zip was installed, I had to run SuperSU.zip in TWRP recovery from my phone to re-root the phone. Everything was always perfect after those steps.
I don't want to RELOCK my bootloader because then my phone internal storage will be wiped. I am trying to keep my phone from returning to a factory fresh installation. Perhaps there's a step in between that I am missing to restore the phone's apps and data but when I use TWRP to restore my nandroid, the previous OS is restored too.
Tried with stock recovery from OTA
daodeltaforce said:
Thank you Vcek. It sounds like I need to do these steps while tethered to my PC in the ADB shell? I will try this method. Maybe one of my mistakes was I did not use the stock recovery from the latest OTA.zip. I had used the previous version OTA.zip's stock recovery to perform the software update installation from my phone.
Some people say I need to RELOCK the bootloader but I have never needed to do this to perform any of the previous OTA.zip updates. In fact, updating my rooted phone has been very easy until I ran into this problem with the latest OTA.zip update. I simply flashed the previous OTA.zip stock recovery tethered to my PC in ADB shell, then ran the latest OTA.zip update saved to my phone's internal storage while my phone remained rooted. Of course, after the OTA.zip was installed, I had to run SuperSU.zip in TWRP recovery from my phone to re-root the phone. Everything was always perfect after those steps.
I don't want to RELOCK my bootloader because then my phone internal storage will be wiped. I am trying to keep my phone from returning to a factory fresh installation. Perhaps there's a step in between that I am missing to restore the phone's apps and data but when I use TWRP to restore my nandroid, the previous OS is restored too.
Click to expand...
Click to collapse
daodeltaforce I am facing similar issue with the current OTA update. I tried keeping it for almost half and hour in frozen mode still it did not boot. Even I have tried with stock recovery from OTA but no help.
Sprint HTC One (M8) 4.25.651.14
mukeshdaiv said:
daodeltaforce I am facing similar issue with the current OTA update. I tried keeping it for almost half and hour in frozen mode still it did not boot. Even I have tried with stock recovery from OTA but no help.
Click to expand...
Click to collapse
mukeshdaiv thanks for reporting your similar problem with this latest OTA.zip update. I think our solution to this problem is to manually install the update from the ADB shell tethered to a PC to run the commands to override the phone's recovery. If your phone is still frozen just press the power button while pressing the volume down button to get into the bootloader, then tether your phone to your PC and run the ADB to flash TWRP or other custom recovery and then restore your nandroid. After that, you will see that your phone's firmware was updated to the latest version. So all that's left to do is to update your phone's OS. That's the part I am not sure how to do in ADB.
daodeltaforce said:
mukeshdaiv thanks for reporting your similar problem with this latest OTA.zip update. I think our solution to this problem is to manually install the update from the ADB shell tethered to a PC to run the commands to override the phone's recovery. If your phone is still frozen just press the power button while pressing the volume down button to get into the bootloader, then tether your phone to your PC and run the ADB to flash TWRP or other custom recovery and then restore your nandroid. After that, you will see that your phone's firmware was updated to the latest version. So all that's left to do is to update your phone's OS. That's the part I am not sure how to do in ADB.
Click to expand...
Click to collapse
You don't use ADB-you use a RUU (ROM Update Utility), which is a exe file run from your computer. The RUU includes both software and firmware, as well as the stock recovery.
RUU
Magnum_Enforcer said:
You don't use ADB-you use a RUU (ROM Update Utility), which is a exe file run from your computer. The RUU includes both software and firmware, as well as the stock recovery.
Click to expand...
Click to collapse
Thank you Magnum_Enforcer. I knew a little bit about RUU but never used it to update my phone before. I will try to find the ROM Update Utility for Sprint HTC One (M8) software update number 4.25.651.14. Thank you.
daodeltaforce said:
Thank you Magnum_Enforcer. I knew a little bit about RUU but never used it to update my phone before. I will try to find the ROM Update Utility for Sprint HTC One (M8) software update number 4.25.651.14. Thank you.
Click to expand...
Click to collapse
Look in the first post in the thread linked below:
http://forum.xda-developers.com/showthread.php?t=2729173
Magnum_Enforcer said:
Look in the first post in the thread linked below:
http://forum.xda-developers.com/showthread.php?t=2729173
Click to expand...
Click to collapse
Thanks again Magnum_Enforcer! I see OMJ's post with a variety of RUU's. It looks like mine is the first one listed. So these RUU's have both the firmware and the software? Do I need to S-Off first before I execute the RUU? If so, I've got some notes how to do that in the ADB shell. Thank you!
daodeltaforce said:
Thanks again Magnum_Enforcer! I see OMJ's post with a variety of RUU's. It looks like mine is the first one listed. So these RUU's have both the firmware and the software? Do I need to S-Off first before I execute the RUU? If so, I've got some notes how to do that in the ADB shell. Thank you!
Click to expand...
Click to collapse
S-off is not required. You'll need to relock your bootloader using the command fastboot oem lock. Then double-click the RUU to start the installer. Once it starts simply follow the prompts on your computer to complete the process. For more info hit the second link in my sig and scroll down & read the RUU section.
Magnum_Enforcer said:
S-off is not required. You'll need to relock your bootloader using the command fastboot oem lock. Then double-click the RUU to start the installer. Once it starts simply follow the prompts on your computer to complete the process. For more info hit the second link in my sig and scroll down & read the RUU section.
Click to expand...
Click to collapse
Magnum_Enforcer thanks very much for your guidance, I really appreciate it. Relocking the bootloader and then unlocking it (so I can re-root my phone) will wipe my phones internal memory, right? How do I restore my Apps & Data with my nandroid since it will restore the previous OS. Then I would have only updated the firmware and the latest OS would be replaced by the nandroid, right? Or am I missing a step? I'll read up on your RUU instructions and do some searching. Thank you!
Searching to flash via ADB
daodeltaforce said:
mukeshdaiv thanks for reporting your similar problem with this latest OTA.zip update. I think our solution to this problem is to manually install the update from the ADB shell tethered to a PC to run the commands to override the phone's recovery. If your phone is still frozen just press the power button while pressing the volume down button to get into the bootloader, then tether your phone to your PC and run the ADB to flash TWRP or other custom recovery and then restore your nandroid. After that, you will see that your phone's firmware was updated to the latest version. So all that's left to do is to update your phone's OS. That's the part I am not sure how to do in ADB.
Click to expand...
Click to collapse
daodeltaforce I have already flashed recovered from nadroid backup. Thanks for the information. Hope we can flash via ADB. As relocking and unlocking bootloader will clear all the memory.
mukeshdaiv said:
daodeltaforce I have already flashed recovered from nadroid backup. Thanks for the information. Hope we can flash via ADB. As relocking and unlocking bootloader will clear all the memory.
Click to expand...
Click to collapse
mukeshdaiv I am glad you were able to restore your Nandroid. Now we need to figure out how to apply the latest OTA.zip for our UNLOCKED (rooted) phones without losing our Apps and Data. I was informed in this forum that we need to run the RUU.exe that OMJ has posted. I asked OMJ to confirm that the RUU.exe will also update the OS (not just the firmware). AND that it can be installed without losing my Apps & Data. I've been told in this forum the bootloader needs to be RELOCKED. That means to UNLOCK the bootloader to ROOT the phone will wipe the phone's internal storage. I will not do that. There is no way I am going lose my Apps and Data to update the OS. I for one will not start from scratch. I have not received a reply from OMJ. I also asked Captain_Throwback the same question if there is a way to apply the RUU.exe, update the firmware and OS without having to wipe my Apps & Data. I have not received a reply from Captain_Throwback. At this point, I think I will need to move to more resources to get some help and answers. I wish you good luck and if you find a solution that works for your phone, please post it here, and I will do the same. Thanks!
i'm having the same problem where y phone is stuck at the white htc one screen as you, and haven't been able to get it to restart from there. i restored the stock recovery and started the ota and it looked to install right but i'm stuck where you mentioned. i think maybe i forgot to relock the bootloader? anyway, i've tried holding the power button and everything and i still can't get anywhere. any help would be greatly appreciated.
edit: i was able to get into the bootloader, and after rebooting it just stays at a black screen right after the first powerup screen. dunno where to go from there though.
I was trying to install clockwork mod to my devices. I have TWRP (And NOTHING but TWRP at that...) and that i accidentally wiped my whole OS off of my device... Help me? It's Cricket Wireless btw. Black.
candyman0629 said:
I was trying to install clockwork mod to my devices. I have TWRP (And NOTHING but TWRP at that...) and that i accidentally wiped my whole OS off of my device... Help me? It's Cricket Wireless btw. Black.
Click to expand...
Click to collapse
You need to do a XDA search and look for some kernels and roms to put on a micro SD card and flash it
candyman0629 said:
I was trying to install clockwork mod to my devices. I have TWRP (And NOTHING but TWRP at that...) and that i accidentally wiped my whole OS off of my device... Help me? It's Cricket Wireless btw. Black.
Click to expand...
Click to collapse
At this point I will suggest that you download a RUU and use that to restore your phone. Or you could flash a custom rom for the 32bit version of this phone, If the TWRP recovery is working. If the recovery is not working your only option would be the RUU. If you still have any questions don't hesitate to ask.
I am in the same boat!
I know I can NOT get into recovery TWRP. I know I am still unlocked. I am going to make sure I know which version I have. I know it was Boost Mobile. I have searched for correct RUU. Not sure if I can find a good one. To install the RUU I need to mount my SD. I can not find a way to mount. Since I am rooted I thought ES explorer will let me in. No Dice. RUU sources?
Reason for doing this: I want to flash a 5.1 rom. I was directed to update TWRP to fix the failed message I was receiving on flashing the ROM file. That is where I lost recovery altogether.