I performed the update on my brand new HTC Hero and I found out I am stuck in the middle of nowhere with no chance to root until somebody fixes the problem. During my reading, I tried almost everything, and the closest I got was to try and flash an update.zip with the original ROM back onto my device. Yet, at the moment of truth just a stupid white triangle with an exclamation mark appeared instead of the other icon meaning the thingh is working. I can't wait to root for a number of reasons, if I am getting this wrong and there actually IS another solution please help :-((
Ciao!
Vico
Same Boat
Hi mate,
I'm new to the Android OS and just got my hero as well. The first thing I did with it was to update the firmware (as recommended by Orange). Little did I know that this would prevent me from rooting.
I've tried several steps:
1. The One-Step Root Process
2. Flashing an image with the SDK
3. Rolling back to a previous version of the RUU
Nothing works, anyone have any ideas about how to get round this problem or if there's a way to 'un-update' the device, please help!
FYI: I have an HTC Hero on Orange UK running the latest HTC firmware, unrooted http://www.youtube.com/watch?v=9VZHT389eR4
Thanks in advance.
if your phone is NOT CID locked (no clue about orange) you can go here
http://forum.xda-developers.com/showthread.php?t=559622
and download an older RUU (1.76.405.1_R3) and downgrade, then root and upgrade.
problem obviously is that this only works if your phone is not cid locked, or somebody find away to bypass the cid check on the ruu process or finds a way to do this
http://forum.xda-developers.com/showthread.php?t=559806
on updated rom versions......
Thanks
Thanks for the link, I'll take a look into it.
closing this one as currently it can't be solved.
I've started a thread that looks into this here:
http://forum.xda-developers.com/showthread.php?p=4704200
I recently tried updating my (previously functional) HTC One M8 I converted to a Google Play Edition phone. I hadn't realized the version of the GPE RUU was rooted, so after using Android's stock updater, the phone is busted. I've been tearing my hair out for the last six hours trying to flash something or get it to work in a way that's acceptable, but I can't seem to get access to it.
I should note that once the RUU was updated to GPE, I didn't bother reinstalling TWRP, so I'm also stuck on a stock recovery.
There are a couple of significant issues beyond the phone just not starting up. When I go into the bootloader, it states that it's missing OP6BDIAG.zip, and that no images were found. It then says a few more things in separate lines so quickly I can't really read them. I think they're either .exe or .zip files.
MTP is not currently working, I can't access the file structure. ADB and Fastboot are giving me errors, saying they can't find the device. I've pushed FACTORY RESET in the bootloader with no difference at all. I've gone into the recovery and wiped data, cache, everything. My NANDroid backups are all of Sense, because I have only converted this phone to GPE a week ago.
I'm not a software developer, I'm not an Android systems expert, and in all honesty when it comes down to it I'm skilled enough to read a manual and know usually what I'm saying when I type in command prompts. I need some help. I've officially spent more time trying to figure out how to fix this than converting the phone in the first place.
Some more info: For those of you who don't know, to do the conversion I've done, my phone is unlocked, has s-off, I've changed the CID to google's, and I changed the RUU to the stock android from a member of this forum's instructions. The bootloader is still HTC, and it is running the HTC GPE RUU, not a Nexus or other RUU.
Update: I got TWRP on my phone! ADB wasn't communicating with my device so I looked up how to do it all through fastboot. It's turned my phone into an MTP device and I can access everything. My NANdroid backups to Sense were deleted when my RUU updated it to a Play Edition phone, so I'm out of luck there, but I assume I can just use TWRP tools to get my phone working again? What's my next step?
DiscoKing said:
Update: I got TWRP on my phone! ADB wasn't communicating with my device so I looked up how to do it all through fastboot. It's turned my phone into an MTP device and I can access everything. My NANdroid backups to Sense were deleted when my RUU updated it to a Play Edition phone, so I'm out of luck there, but I assume I can just use TWRP tools to get my phone working again? What's my next step?
Click to expand...
Click to collapse
No official RUU is pre-rooted, and unfortunately Lollipop has been very rough on root users. It isn't like the old days when it would just blow away your root files and move on.
If you want to run GPE, get the official RUU and try it again. Just keep in mind that OTAs will break if you root it.
That worked, after a few failures. Thank you.
Please help me I have the exact same problem. How did you manage to install TWRP?
Hi,
I recently managed to root my HTC One M8s with TWRP recovery and everything works perfectly, except that I can't install the new OTA (1.16.401.1).
After searching I have flashed my recovery back to the stock for my version (which is 1.11.401.1) and tried applying the OTA again, but it still fails.
I downloaded the recovery from this website: ruu.lalleman.net/HTC_M8S%28QL_UL%29/Recovery/HTC%20Recovery/ (I can't post URLs yet).
Below is the error I receive when trying to update on stock recovery, TWRP recovery also gave the same error when I tried updating there.
(Code -1)
E:Find no match PARTITION: for package path @/cache/recover/block.map
Finding update package...
Opening update package...
Verifying update package...
Installing update...
L50QCT.01.105.019
Verifying current sytem...
Package expects build fingerprint of htc/m8qlul_htc_europe/htc_m8qlul:5.0.2/LRX22G/531284.2:user/release-keys or htc/m8qlul_htc_europe/htc_m8qlul:5.0.2/LRX22G/555949.10:user/release-keys;
This device has htc/m8qlul_htc_europe/htc_m8qlul:5.0.2/LRX22G/53128
E:Error in @/cache/recovery/block.map
(Status 7)
From what I can see my build fingerprint is incorrect, but I have no idea how to fix it...
Seems to me it's likely that you've altered some system files while rooted and the Ota doesn't like it.
Now, I don't own an M8s...i have an M8, but I'd say the easiest route would be to flash your stock ruu again. After that the OTA should work.
It's that or figure out what system changes have been made and correct it. Xposed can mess you up, Uninstalled system apps can stop the Ota... MODS that changed system files... Etc. The Ota us looking for a stock system, then it updates it.
Good luck!
Thanks for the answer, I will see if I can try this solution tomorrow. I just have 2 questions:
What does the RUU do exactly? Should I see it as a complete stock reset of my phone?
And can I simply flash it using fastboot or is there a special method for a RUU?
My previous phone had an automated root and I always updated with OTA afterwards so I never flashed before now.
Im on the same boat. Tried to sim unlock by rooting and playing with CID but didnt work, now ive a rooted m8s and no ota. Tried to ruu but kept getting an error something like not enough space although i had 10gb free, cleared cache rebooted. Cant even factory reset. If anyone know how to unroot it and bring it back to stock that would be fantastic. Kind of want to delete the "flag" too make it "LOCKED" and "OFFICIAL" incase for warranty. Any ideas?
You guys have flashed 1.16 before, haven't you...?
See here: http://forum.xda-developers.com/htc-one-m8/help/help-thread-htc-one-m8s-to-stock-howto-t3190238
Err, oops, posted too soon. You said you have flashed to 1.11. What is the full filename of the RUU you flashed?
voidzero said:
You guys have flashed 1.16 before, haven't you...?
See here: http://forum.xda-developers.com/htc-one-m8/help/help-thread-htc-one-m8s-to-stock-howto-t3190238
Err, oops, posted too soon. You said you have flashed to 1.11. What is the full filename of the RUU you flashed?
Click to expand...
Click to collapse
When I got my phone I updated with OTA to version 1.11, after that I flashed TWRP recovery and rooted my phone. Now that OTA 1.16 is out I tried to update but couldn't, so I tried to flash back to stock recovery but it still wouldn't work because of the error above. Now it would seem that I am doing this the wrong way, and you cannot use OTA on a rooted/unlocked/custom recovery M8s.
Manual OTA flash worked on my previous phone with root which was an ASUS Padfone Infinity A80 as ASUS would release them on their own website for you.
Apparently HTC does not do this, or I am not looking in the right place.
I have never flashed a RUU before, and I don't know how to lock my bootloader again. From what I understand, every time there is a new OTA I will have to lock my bootloader, flash original recovery, flash RUU and then update. That sounds like a lot of trouble every time a new OTA comes out.
Is there no way to manually flash the new OTA without losing root, custom recovery and locking the bootloader? Will I have to follow these steps every time? Also I use the built in back-up to Google as well as HTC back-up but I don't know if all my data is in those back-ups or if I will lose something.
Codyksp said:
(...) so I tried to flash back to stock recovery but it still wouldn't work because of the error above. Now it would seem that I am doing this the wrong way, and you cannot use OTA on a rooted/unlocked/custom recovery M8s.
(..)
I have never flashed a RUU before, and I don't know how to lock my bootloader again. From what I understand, every time there is a new OTA I will have to lock my bootloader, flash custom recovery, flash RUU and then update. That sounds like a lot of trouble every time a new OTA comes out.
(...)
Is there no way to manually flash the new OTA without losing root, custom recovery and locking the bootloader? Will I have to follow these steps every time? Also I use the built in back-up to Google as well as HTC back-up but I don't know if all my data is in those back-ups or if I will lose something.
Click to expand...
Click to collapse
If you restore a RUU, and afterwards don't flash your recovery and boot partitions, You will see "Software status: official" in fastboot.
Now here's the trick: if you just boot a custom recovery with "fastboot boot my_recovery.img" (TWRP for example) then it will boot TWRP, but you can make the modifications to your system partition without losing "Software status: official" in fastboot.
So: If you just boot your recovery with 'fastboot boot' and don't flash anything, you can make all the modifications you want and still be able to install OTAs later, I think. I've rooted my phone, even installed XPosed, done all kinds of funky things to it but Fastboot still shows me that I'm on official software.
How does that sound?
So since there is no decent guide at all about flashing RUU for a HTC One M8s (the s makes a difference!). I have assumed that I need to have the bootloader locked first, as I unlocked it. According to all the M8 guides I have to gain S-OFF before I can lock the bootloader again. So I followed a guide to wipe with TWRP and flash a ROM called InsertCoin so that I can S-OFF my phone.
Now after going through the ROM's setup my phone is stuck in a bootloop, constantly trying to boot up. There is NO way at all for me to get it to stop, it just keeps booting the entire time. Not a single combination of buttons is working. Good thing the battery is non removable. How am I supposed to fix this? I've tried every volume up/down/power combination possible. The phone just boots to the HTC - Power by Android screen, shuts off after about 5 seconds and then repeats the same thing over and over. I can't turn it off and I can't get to the bootloader either.
What I need is a guide that tells me all the steps required to get an HTC One M8s (NOT M8!) back to 100% stock. This means, stock ROM, stock recovery, locked bootloader and S-ON. I am getting extremely frustrated by the lack of information and the amount of redicilous things I need to do just so I can root my phone and have OTA as well.
All I want is root on my phone for 1 app that I use with my car radio and I want to be able to update to the newest OTA afterwards, is that really so much to ask?
I am fine with installing a custom ROM with root and easy updates too, as long as the damn phone will boot after installing it and it's actually made for the M8s.
Deleted......
Well I finally managed to get the damn thing to the bootloader, and I've used "fastboot oem lock" to relock my bootloader. It now shows ***Software status: Modified ***, *** RELOCKED *** and ***Security Warning ***.
I will now have to go to my parents where my laptop is to be able to copy the RUU to my SD card, from what I understand it has to be named 0PKVIMG.zip and then it should automatically install.
Now the phone says it can't find the image or the image is incorrect.... It searches for, 0PKVDIAG.zip, 0PKVDIAG.nbh, 0PKVIMG.zip or 0PKVIMG.img. and it seems to find 0PKVIMG.zip and loads it but it cannot find the .img file and does absolutely nothing. Am I supposed to have both?
So it turns out that the RUU zip from http://ruu.lalleman.net/HTC_M8S%28QL_UL%29/RUU/ is actually not correct and I had to use rom.zip which was inside the folder. The phone is now running the "update" as it calls it. Fingers crossed...
Yes, possible you need to use rom.zip inside the zip, depending on the version, but I think this applies to 1.16 which I advice against using for reasons previously specified.
---------- Post added at 07:47 PM ---------- Previous post was at 07:47 PM ----------
By the way, I did write an RUU restoration thread specifically for this subject. Did you not find it?
Apparently I also needed to use the rom.zip for the 1.11 version, in the meantime I have also updated with OTA to 1.16. Afterwards I also unlocked my bootloader, restored my settings and installed SuperSU by booting TWRP. Let's hope the next OTA still works...
I did read your thread but I got stuck at first on relocking the bootloader, as I couldn't find the exact instructions for a while. Afterwards I got stuck on flashing the RUU because I didn't know that I needed to use the rom.zip file to get it to work.
After all that I got quite frustrated and I just wished there was 1 thread with instructions for everything (unlocking, relocking, flashing, compatible ROMs, booting to keep OTA, etc.) which is why I was angry at the time and couldn't properly read everything or find solutions. In the end it all worked out so far though.
I would ask you to create a compilation thread though if you wanted to improve the available information. Either way, thanks for the information that you've already provided.
Codyksp said:
Apparently I also needed to use the rom.zip for the 1.11 version, in the meantime I have also updated with OTA to 1.16. Afterwards I also unlocked my bootloader, restored my settings and installed SuperSU by booting TWRP. Let's hope the next OTA still works...
I did read your thread but I got stuck at first on relocking the bootloader, as I couldn't find the exact instructions for a while. Afterwards I got stuck on flashing the RUU because I didn't know that I needed to use the rom.zip file to get it to work.
After all that I got quite frustrated and I just wished there was 1 thread with instructions for everything (unlocking, relocking, flashing, compatible ROMs, booting to keep OTA, etc.) which is why I was angry at the time and couldn't properly read everything or find solutions. In the end it all worked out so far though.
I would ask you to create a compilation thread though if you wanted to improve the available information. Either way, thanks for the information that you've already provided.
Click to expand...
Click to collapse
The next ota won't work because you rooted it. Root changes binaries which lead to a fail on ota.
You need a non rooted (read : never rooted before) stock rom.
Mr Hofs said:
The next ota won't work because you rooted it. Root changes binaries which lead to a fail on ota.
You need a non rooted (read : never rooted before) stock rom.
Click to expand...
Click to collapse
So in that case I just unroot it before updating then?
Codyksp said:
So in that case I just unroot it before updating then?
Click to expand...
Click to collapse
Read my post again...... "a never rooted rom" so that means you need a stock rom before its ever been rooted. NOT an unrooted one because it leaves traces which will cause the ota to fail !
People should learn to create a nandroid backup before flashing ANY mods/superuser.zip/roms etc......etc
Well developers shouldn't make this such a hassle... My previous phone was an ASUS Padfone Infinity (A80) and it didn't receive any OTAs after being rooted but ASUS simple lets you download the firmware updates on their website and then you can manually update it without any problems. If HTC provides a bootloader unlock, why can't they allow OTA or at least provide manual firmware updates?
I wouldn't mind using a custom ROM either but I have no idea which ROMs work for the HTC One M8s. Would any M8 ROM be compatible? The phones aren't identical, the "s" is there for a reason...
Codyksp said:
Well developers shouldn't make this such a hassle... My previous phone was an ASUS Padfone Infinity (A80) and it didn't receive any OTAs after being rooted but ASUS simple lets you download the firmware updates on their website and then you can manually update it without any problems. If HTC provides a bootloader unlock, why can't they allow OTA or at least provide manual firmware updates?
I wouldn't mind using a custom ROM either but I have no idea which ROMs work for the HTC One M8s. Would any M8 ROM be compatible? The phones aren't identical, the "s" is there for a reason...
Click to expand...
Click to collapse
I would say that M8 roms wouldn't be compatible, and could even mess up your device badly. Sorry!
Codyksp said:
Well developers shouldn't make this such a hassle... My previous phone was an ASUS Padfone Infinity (A80) and it didn't receive any OTAs after being rooted but ASUS simple lets you download the firmware updates on their website and then you can manually update it without any problems. If HTC provides a bootloader unlock, why can't they allow OTA or at least provide manual firmware updates?
I wouldn't mind using a custom ROM either but I have no idea which ROMs work for the HTC One M8s. Would any M8 ROM be compatible? The phones aren't identical, the "s" is there for a reason...
Click to expand...
Click to collapse
Your point of view is a bit off if you ask me. Developers (in this case HTC) do not have to support custom modding of your phone. They support the device in the state you buy it !
If you want to mod it that's YOUR call not theirs. Do some homework before modding it. Getting a phone back to stock for future updates is relatively easy but many people don't read first how to as they think it's not important.
HTC has no obligation at all towards you regarding custom software !
And indeed M8 roms do NOT work on your M8s !
Hi all,
I've been spending the last couple of days on these forums and google trying to resolve the issues I have been having nonstop since I decided to unlock and flash my HTC One M9 but I've run into a wall and don't know what else I can do to fix my phone. Stupidly I did not create a backup before flashing so I think I am up **** creek as I cannot install stock roms either. I've have been following the guides but having issues the whole time through with the M9 for some reason.
HTC One M9 - Telstra (Australia) S-ON
After lots of ****ing around I have successfully managed to Unlock, Install TWPR, Flash SuperSU, Flash Android Revolution custom rom. This has wiped all my IMEI/SIM settings etc. I managed to find the stock telstra RUU to got back to stock rom as this is how to fix this problem, except when I try to install I get errors saying 'Device id/information not found'
Does anyone have any similiar experiences or know of anyway to fix this? Any and all help is appreciated.
It's impossible to help without knowing your current firmware and the firmware of the RUU you wanted to flash.
Be aware that there is not "the stock telstra RUU". RUUs are always stock and normally HTC creates one for each firmware version of their phones. The catch is that they don't get distributed officially (unless they're made for US carriers) but leaked by insiders.
However, the problem with the IMEI is explained in the ReadMe thread.
Hi guys. I used to be up on my HTC flashing etc. but I've moved away from them over the last couple of years and a friend has come to me with a problem and I'm not sure what to suggest.
Please see attached image for reference to software/hboot/radio versions etc.
Basically I've quizzed him on what he's done to get to this state. He hasn't tried to flash a rom or new hboot, root, s-off or anything like that. In fact I'm pretty certain he wouldn't know where to start. He said it was charging overnight and in the morning it would only boot to hboot. Selecting any of the options from there results in a blank screen before eventually looping back to hboot.
Any help or guidance I what to try would be massively appreciated. Thanks!
Your friend has a variant of the M8, known as the M8s.
It might be tough to find an RUU tool to restore the device, or a stock TWRP backup (stock ROM).
If no RUU for that OS number, restoring a stock TWRP backup (if you can find the right one) would be an involved process:
- unlock bootloader
- install TWRP custom recovery
- restore the right stock TWRP backup
So not sure how far you want to go with this. My experience with the M8s is limited, and resources for the "s" variant are also limited.