Related
Hello, I need some serious help with my friends HTC m8.
We unlocked the phone of my friend and wanted to install a custom recovery. After installing TWRP latest version everything still worked fine, the device still booted normally. After that we tried to install the GPE ROM of the M8 through TWRP without realizing the phone isn't s-off. By itself the installation failed and we just rebooted the device and saw that it wouldn't boot anymore, it was stuck on the boot screen, even though it aborted the installation because the MD5 numbers weren't matching.
Now we don't know what to do, the M8 won't boot and is s-on. We tried downloading: http://forum.xda-developers.com/htc-one-m8/general/htc-one-m8-european-signed-ruu-0p6bimg-t2911563 the stock file and pushing the update by renaming the zip file to 0P6BIMG.zip but gave us the error "halted due to large image update fail". So this didn't help us either
CiD of the device = HTC_E11
After all we're just idiots by not researching enough before doing anything. Hopefully some experienced people can help us out!
Thanks in advance,
Pepie.
Pepie said:
Hello, I need some serious help with my friends HTC m8.
We unlocked the phone of my friend and wanted to install a custom recovery. After installing TWRP latest version everything still worked fine, the device still booted normally. After that we tried to install the GPE ROM of the M8 through TWRP without realizing the phone isn't s-off. By itself the installation failed and we just rebooted the device and saw that it wouldn't boot anymore, it was stuck on the boot screen, even though it aborted the installation because the MD5 numbers weren't matching.
Now we don't know what to do, the M8 won't boot and is s-on. We tried downloading: http://forum.xda-developers.com/htc-one-m8/general/htc-one-m8-european-signed-ruu-0p6bimg-t2911563 the stock file and pushing the update by renaming the zip file to 0P6BIMG.zip but gave us the error "halted due to large image update fail". So this didn't help us either
CiD of the device = HTC_E11
After all we're just idiots by not researching enough before doing anything. Hopefully some experienced people can help us out!
Thanks in advance,
Pepie.
Click to expand...
Click to collapse
Firstly, I don't think it has anything to do with "not researching" enough but more to do with NOT reading what you "researched" already. You post a link to the RUU .zip that you wanted to use and obviously haven't picked up on the fact that the OP in that thread specifically stated: S-Off is Required with Eurpean CID right after admitting that you are NOT S-OFF.
Secondly: You don't need S-OFF to flash a custom ROM. You just need an unlocked bootloader and a custom recovery, that's it. You'll need S-OFF to fully convert the device to GPE though, as it makes changes to partition sizes.
Try to get back into bootloader again. Hold Volume UP + Power for 10 seconds the moment the feel a vibration and/or screen goes dark immediately hold Power + Volume Down to enter bootloader. You should still have TWRP on the device you didn't mention anything about taking it off. Head over to the RUUs, OTAs, Stock TWRP Backups, Firmware & More Collection grab a nandroid backup for your device. Unpack it and place it inside the TWRP backup folder on your device. If you don't have one, make a backup of just "Boot" it'll then create the path for you.
Once done, restore the nandroid. That'll take you back to "stock" then.
Else, just place a custom ROM on the SDcard enter TWRP again and try to flash a custom ROM again.
What ROM did you try to flash? Perhaps give the link...
Oh and remove the 0P6BIMG.zip from the SDCard else it'll just keep on trying to flash it through HBoot.
Hi guys,
Verizon HTC One M8 rooted, S-off,with CWM, running the old digital high GPE 4.4.4.
HBOOT 3.16.0
RADIO 0.89.20.0321
10G storage
I did the firewater procedure when I first got the phone with no problems. Now I am trying to install the new LolliGPE on here and getting nothing but headaches. I have tried to install TWRP(different versions) via Flashify AND fastboot, but when it reboots, it stays on the white HTC One screen-"loading recovery". I have done this multiple times, and then adb reboot, install CWM via flashboot, and no problems. I don't know what else to do, and don't wanna mess my phone up especially as the next step is updating RUU, etc. I'm thinking I may have to update hboot, I just don't want to do anything un-neccesary to brick my phone. Any ideas? Thanks!!
Your older hboot requires an older version of TWRP. Plus, on older TWRP versions, depending on which TWRP version exactly, the CDMA M8 variants had a different TWRP recovery image (as recovery is stored on a different partition location for that version versus the "GSM" or non-CDMA M8). So you need to be really careful (I think a brick is even possible).
I'd suggest updating to the current Verizon Lollipop firmware before proceeding. Your hboot is ancient, and will cause all sorts of issues. After that, the current version TWRP 2.8.7 should install fine.
Thanks for the reply..
So update Hboot first, then install TWRP, then RUU, then ROM?
dl12458 said:
So update Hboot first, then install TWRP, then RUU, then ROM?
Click to expand...
Click to collapse
Shouldn't be a need to flash new hboot, RUU will do that.
Further, you don't want to install TWRP before the RUU; as RUU will wipe it out with stock recovery, anyway.
So in general, you want to:
1) Backup your personal data, RUU will wipe the phone including internal storage.
2) RUU
3) Install TWRP
4) Flash the custom ROM of your choice
Although it should be noted that some folks have had trouble installing TWRP after installing the OTA (the one with Stagefright fix in particular), at least on "GSM" versions of the M8. So you might research and see if VZN folks are having the same issue on the RUU with Stagefright fix that you linked in your PM to me. But at least in browsing the last few pages of the thread, I don't see any mention of TWRP issues (and some confirmations of TWRP working okay):
http://forum.xda-developers.com/verizon-htc-one-m8/development/exe-zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
Great, the update worked!!
I have one final question regarding the LolliGPE ROM (if you have any experience with it). Since I am now on 5.0.1, I tried installing the LolliGPE ROM, and once it is through with its inital bootup, Google prompts me to download a 600mb update. I allow to it to, but then it just gets stuck. It doesn't download anything, and I cannot procede any further. Do I need to flash the Verizon firmware listed, even though the RUU updated? I used the following to try and flash the VZN firmware 1. "fastboot oem rebootRUU" (Phone goes into RUU mode) 2."fastboot flash zip firmware.zip", but I get a response "cannot load firmware.zip" Any ideas?? Thanks again!!
Forum
http://forum.xda-developers.com/showthread.php?t=2716306
redpoint73 said:
Shouldn't be a need to flash new hboot, RUU will do that.
Further, you don't want to install TWRP before the RUU; as RUU will wipe it out with stock recovery, anyway.
So in general, you want to:
1) Backup your personal data, RUU will wipe the phone including internal storage.
2) RUU
3) Install TWRP
4) Flash the custom ROM of your choice
Although it should be noted that some folks have had trouble installing TWRP after installing the OTA (the one with Stagefright fix in particular), at least on "GSM" versions of the M8. So you might research and see if VZN folks are having the same issue on the RUU with Stagefright fix that you linked in your PM to me. But at least in browsing the last few pages of the thread, I don't see any mention of TWRP issues (and some confirmations of TWRP working okay):
http://forum.xda-developers.com/verizon-htc-one-m8/development/exe-zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
Click to expand...
Click to collapse
dl12458 said:
I tried installing the LolliGPE ROM, and once it is through with its inital bootup, Google prompts me to download a 600mb update. I allow to it to, but then it just gets stuck. It doesn't download anything, and I cannot procede any further. Do I need to flash the Verizon firmware listed, even though the RUU updated?
Click to expand...
Click to collapse
I don't use that ROM, or any GPE ROMs, for that matter. So I'll be of limited help on this one.
What I can say, I've seen another post or 2 reporting a similar issue: GPE or AOSP custom ROM installed, will prompt to download an update upon setup (with no option to do otherwise), then phone is stuck.
So you might check the ROM thread, to see if others reported this. Or other help threads, as I've mentioned, I know others have posted this same issue; and that thread(s) may have some insight on a fix.
This issue is pretty weird. You won't normally see a custom ROM accept any type of OTA update, and certainly not a "forced" one like this at startup. In general, custom ROMs won't play well with any type of official OTA update (and updates are often disabled for this reason). And it seems you had no choice to bypass it, which is also odd.
dl12458 said:
Great, the update worked!!
Do I need to flash the Verizon firmware listed, even though the RUU updated? I used the following to try and flash the VZN firmware 1. "fastboot oem rebootRUU" (Phone goes into RUU mode) 2."fastboot flash zip firmware.zip", but I get a response "cannot load firmware.zip" Any ideas?? Thanks again!!
Click to expand...
Click to collapse
Again, I'm not sure what is going on with the forced "update". But I doubt flashing firmware will fix anything.
The error "cannot load" when trying to fastboot flash a file, almost always means the file is not present (meaning not located where it should be, or named wrong). You need to have the desired firmware zip in the same folder where fastboot.exe is located (assuming you are using a PC). And for the command you listed, the firmware actually/literally has to be named "firmware.zip" (with no quotes). If the firmware file is named something else, you either need to rename the file to "firmware.zip" or use the actual exact file name in the fastboot command. Another common problem, is on Windows, folks often have the option enabled to hide file extensions (this is typically enabled by default, and I highly recommended you turn this off). So if you already renamed the file, it may actually be named "firmware.zip.zip" even though Windows will display it as "firmware.zip". If you see a lot of file types with not extensions at all, its very likely you have the option enabled to hide file extensions.
But again, I'm not sure that flashing the firmware is going to help.
If you can't find an easier fix for the "forced" update and stuck on boot screen; my thought would be to try flashing another ROM. Or at worst, RUU to stock again, and try another ROM.
Update- I was trying to install the 5.0.1 update, and when I tried the 5.1 it worked!! Thanks for your help.
redpoint73 said:
I don't use that ROM, or any GPE ROMs, for that matter. So I'll be of limited help on this one.
What I can say, I've seen another post or 2 reporting a similar issue: GPE or AOSP custom ROM installed, will prompt to download an update upon setup (with no option to do otherwise), then phone is stuck.
So you might check the ROM thread, to see if others reported this. Or other help threads, as I've mentioned, I know others have posted this same issue; and that thread(s) may have some insight on a fix.
This issue is pretty weird. You won't normally see a custom ROM accept any type of OTA update, and certainly not a "forced" one like this at startup. In general, custom ROMs won't play well with any type of official OTA update (and updates are often disabled for this reason). And it seems you had no choice to bypass it, which is also odd.
Again, I'm not sure what is going on with the forced "update". But I doubt flashing firmware will fix anything.
The error "cannot load" when trying to fastboot flash a file, almost always means the file is not present (meaning not located where it should be, or named wrong). You need to have the desired firmware zip in the same folder where fastboot.exe is located (assuming you are using a PC). And for the command you listed, the firmware actually/literally has to be named "firmware.zip" (with no quotes). If the firmware file is named something else, you either need to rename the file to "firmware.zip" or use the actual exact file name in the fastboot command. Another common problem, is on Windows, folks often have the option enabled to hide file extensions (this is typically enabled by default, and I highly recommended you turn this off). So if you already renamed the file, it may actually be named "firmware.zip.zip" even though Windows will display it as "firmware.zip". If you see a lot of file types with not extensions at all, its very likely you have the option enabled to hide file extensions.
But again, I'm not sure that flashing the firmware is going to help.
If you can't find an easier fix for the "forced" update and stuck on boot screen; my thought would be to try flashing another ROM. Or at worst, RUU to stock again, and try another ROM.
Click to expand...
Click to collapse
I wanted to make a small guide how to return your HTC one m9 to stock with RUU exe installer. The steps are pretty simple so please follow them. Please note that this is only for WWE international models. Same procedure can be done for other regions, however, the files are different. Doing this, you will also get a latest Marshmallow and 3.35.401.12 update! This will save you of hassle to copy and flash your phone several times over to get it done, this procedure does all that. You will not even need to open a command prompt.
Before you do this procedure backup yours files somewhere safe. This will wipe everything you have on the phone to stock settings. This will also unroot your device and remove custom recovery if you had any.
Follow this guide step by step. Do not open / run anything if I haven't said so.
1. For sake of being organized make a new folder on your desktop called "RUU" and make sure your phone has more than 30% battery otherwise RUU procedure wont work.
2. Download HTC sync manager from here and install it (this can help if RUU installer starts derping with USB connections etc : http://www.htc.com/us/support/software/htc-sync-manager.aspx
3. Download the RUU exe from here and put it in the RUU folder you created on the desktop: https://www.androidfilehost.com/?fid=23991606952597788
4. Download the rom.zip file from here and put it in the RUU folder on your desktop. File name needs to be rom.zip
5. Navigate to TEMP folder by typing %temp% in the search bar. If you can't find the temp folder this way then simply navigate to: C:\Users\PCname\AppData\Local\Temp
6. Select all folders you see there and delete them. If you get a file in use or skip message then please do so.
7. Go back to the RUU folder we created earlier and run the RUU exe file from step 3 as an admin. Give it a little time to load and once you are here don't press on next.
8. Copy rom.zip file from RUU folder and navigate to %temp% folder. Paste rom.zip file here: http://prntscr.com/a5gwae
9. Once copying is finished go back to the RUU exe window from step 7 and start clicking next until it prompts you to update. Click on update to 3.35.401.12.
10. During this procedure the phone will go on and off for a few times and after several minutes it will give the message that procedure has been finished successfully.
- Please note that all files are official. Hope this little guide helped you.
TnQ so much man. I was searching for this RUU for a while but couldn't find it. I'm gonna test it tomorrow. BTW i have an unlocked bootloader and s-on, do i need to relock bootloader before installing RUU?
No, you don't have to.
Or just rename the rom.zip to 0PJAIMG.zip copy to the sd card root, after that power off the phone hold vol- and power select download mode and follow the instructions on the screen.
BTW thx for the rom
why is this not stickied?
Please I need marshmallow RUU for hima_uhl my camera and flashlight stopped working only flashing RUU will fix it
Quick question guys, running marshmallow 6, 3.39.531.7, I want to roll back to Android 5.0.2, 1.32.531.33. Is this possible via this method? Phone is not rooted and s-on? T-Mobile is the carrier
Sent from my HTC One M9 using Tapatalk
cloves said:
Quick question guys, running marshmallow 6, 3.39.531.7, I want to roll back to Android 5.0.2, 1.32.531.33. Is this possible visa this method? Phone is not rooted and s-on? T-Mobile is the carrier
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Downgrades are not possible as long as you are S-ON. You need S-OFF to do this.
Send by the swarm intelligence of my coffee machine ?.
Ok so I could flash the same firmware via this method so long as the ruu matches? Unless of course I could s-off then s-on before sending the phone back in.
Sent from my HTC One M9 using Tapatalk
Question: Once I RUU to Marshmallow from this, am I able to install CM13? I assume so. ( My phone is Htc One m9 (att/cingular) (502)) or will this not work, seeing you have the International (401))
ROM DL problem
After downloading "ROM" it says that is corrupted...!!! What now?
thanks
BR
HTC One M9, Help to get back to stock to install 3.5
Good Morning I have tried all this step by step, i cannot not get this to work does everything except put on my phone, phone is connected to pc via usb and through HTC sync Manager and reconised and have done exactly every step, can someone please help, i have Viper installed 3.5 as i am only on os-2.9.841.5 as i have accidently deleted backed up firmware, Can someone Please help, Regards Freddy
i got S-ON and **LOCKED** i tried to run the RUU(not the one on this thread but in htc/download the UNLOCKED/DEVELOPER HTC One M9) but it gives me error 131(which is wrong region) So is there a RUU international? and is there a possible way to S-OFF free?
error 158 image error.
i tired updating my m9 to 6.0 with ruu.exe but i get this image error message.now am stock at just the startup screen.pls i need help.the phone has no carrier
THANK YOU VERY MUCH FOR THIS GUIDE!!!
I had problems with my M9, now everything is ok! http://forum.xda-developers.com/one-m9/help/m9-freezes-t3456653
I'm on 3.35.401.12 100% will work? Anything I need to do first?
Thank you so much for this!
my M9 CID is HTC__002. Is it true if I flashed the RUU, my phone will be flashed into demo mode?
thanks
Eayip1 said:
my M9 CID is HTC__002. Is it true if I flashed the RUU, my phone will be flashed into demo mode?
thanks
Click to expand...
Click to collapse
Please don't post more or less the same question in several threads. It's considered as rude behaviour on xda.
An xda search for "demo" would have been enough for finding this thread. If you read the whole thread you'll learn everything about the problems that arise with the latest firmware and the Demo-CID HTC__002.
Flippy498 said:
Please don't post more or less the same question in several threads. It's considered as rude behaviour on xda.
An xda search for "demo" would have been enough for finding this thread. If you read the whole thread you'll learn everything about the problems that arise with the latest firmware and the Demo-CID HTC__002.
Click to expand...
Click to collapse
Oh, i didnt know that. Im so sorry man..
Thanks
Hello,
Usually i don't write messages on English forums, but nobody in Poland is able to help me. My friend asked me to update hes stock software of HTC ONE M9 by manufacturer update from 2.10.206.2 to 2.10.206.180. because this update is available. He couldn't do it by himself because somebody flash this phone with TWRP. I've installed stock recovery, but phone still does not allow me to install update or force install it by flashing with bootloader (OTA and recovery software downloaded from xda). I wanted to post some pictures but forum rules doesn't allow me to do it. So I will just point you guys to my polish thread so you can look at the photos. forum.android.com.pl/topic/273151-aktualizacja-stockowego-romu-z-twrp/
You need an untouched system image. File-based OTAs aren't used anymore on "newer" devices like the M9. Block-based OTAs can't be installed anymore as soon as you flash anything via twrp. Either use one of the backups or the Android M RUU for the SKU 206 which you can find both in my google sheet (link can be found in my signature).
Sent from my HTC One M9 using XDA Labs
I know that probably for you it is a stupid question but which file would be the best for me? can you paste this file name? And would I be able to install it by standart ''fastboot oem rebootRUU ;htc_fastboot flash zip firmware.zip'' commands?
Boot to Download Mode and look at the line with OS at the beginning. That's your current firmware version. Either restore the corresponding backup and then install the updates via the OTA function in settings>about or flash a RUU that has at least the same firmware version (in this case you need to install the OTAs via settings>about) or a newer one (in this case the phone will get updated automatically). [Hint: There only is one O2/206 RUU which fulfills this requirement.] Flashing instructions or restoring instructions can be found directly above the downloads.
You could flash a RUU via fastboot but I personally prefer recommending the SD card method since there are so many reasons why fastboot can fail (missing drivers, still installed Sync Manager, general problems with Win 8/8.1/10 - just to name a few) and it's easier for me to help if you use more fail-safe method.
I've tried to install two stock backups Stock_Backup_2.10.206.180.zip and Stock_Backup_2.10.206.2.zip, neither of them didnt want to flash. I've tried two ways, first in recovery partition via update from sd and second from download mode via 0PJAIMG.ZIP and this is what i got.
postimg.org/image/xz9gtdrdv/
and
postimg.org/image/mnrdgk8vv/
After trying to update from recovery i got:
postimg.org/image/ma887fuub
I didn't do any RUU because i dont see any that would fit my phone, if I'm wrong please correct me. And please help me
I actually don't understand why you completely ignore the instructions above the download links. I'm not going to rephrase every step you have to make since they're all explained in the google sheet.
As mentioned in the sheet those are TWRP backups so you have to restore them with TWRP. Neither the stock recovery nor the SD card method are able to handle them. (The latter is only meant to be used for RUUs.) Besides I told you to look at the line with OS at the beginning when you boot to Download Mode. I highly doubt that it states 2.10.206.8 and 2.10.206.180 at the same time. Choose the one that corresponds to your current firmware version and restore it via TWRP.
Concerning your search for the correct RUU: I told you that the SKU has to match and that you need to look at the 206 RUUs. There are only four RUUs which can be found in the sheet and fulfill this requirement [in chronological order]: 1.32.206.6, 1.32 206.15, 1.40.206.8 and 3.35.206.13. I told you to choose the one that has at least the same firmware version as your phone or a higher one. From your previous posts I know that your firmware is 2.10.206.x. So which of the four has the same or a newer version?
Sent from my HTC One M9 using XDA Labs
No its not 2.10.206.8 or 2.10.206.180 its 2.10.206.2, as I shown in my first post. Ok I will give it another try, thanks for help.
galusxx said:
No its not 2.10.206.8...
Click to expand...
Click to collapse
That was a typo. I was referring to the backup versions you tried to use and mentioned in the post above mine.
Sent from my HTC One S using XDA Labs
You are my savior, thanks mate for you help
I really don't know where you see that eight mate, but it doesn't matter everything is working now, if you'll ever come in to uk let me know I need to buy you a beer
Good to hear that your problem is solved now. As said before I made a typo. The version 2.10.206.8 doesn't even exist.
Sent from my HTC One S using XDA Labs
Hi, I tried to install Android_Revolution_HD-One_M8_53.1_c8bf38 for my HTC one m8 eye device using twrp and it said installed successful but after that the phone is rebooting only into bootloader and recovery.
I don't have a recovery back up and I can't find one online for my version so what shall I do to get my phone working again?
Thank you in-advance.
Get a desire EYE compatible rom !
Mr Hofs said:
Get a desire EYE compatible rom !
Click to expand...
Click to collapse
can you please help me with a link? and my device is M8 one eye not desire, do they use the same ROM?
I tried flashing-0p6bimg-zip using this download http://forum.xda-developers.com/showpost.php?p=58457494&postcount=375 but it said large file and went into rebooting loop which didn't end till I removed the file from the sd card
Then I found somebody recommending this download RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WWE_4.20.651.10_Radio_1.09.20.0119_NV_SPCS_1.52_003_release_418488_signed_2 and I tried it but finally I found my version is 4.35.40.1.3 and the one I was trying install is 4.20.651.10 and it said please get the correct ROM update utility and try again.
Sorry my bad, I meant M8 eye rom. Check the rom threads for a compatible one if they are there. I never used a eye and not up to date, but i think the normal M8 roms don't just work on the eye
Perhaps you can finde somthig you can use in this thread about How to root M8 Eye.
Aboemn said:
I tried flashing-0p6bimg-zip using this download http://forum.xda-developers.com/showpost.php?p=58457494&postcount=375 but it said large file and went into rebooting loop which didn't end till I removed the file from the sd card
Then I found somebody recommending this download RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WWE_4.20.651.10_Radio_1.09.20.0119_NV_SPCS_1.52_003_release_418488_signed_2 and I tried it but finally I found my version is 4.35.40.1.3 and the one I was trying install is 4.20.651.10 and it said please get the correct ROM update utility and try again.
Click to expand...
Click to collapse
Those RUUs won't work on your device. The first is for the Euro M8 (not the EYE), and second is for Sprint M8. The RUU has to match your carrier version (CID) and model ID (MID). In fact, those RUUs are for a different hardware, and will fail to install. If they installed, they probably would brick your phone.
You need to find a 4.35.40.1.3 RUU, if it exists.