I wanted to root my HTC One M8 to uninstall unnecessary applications. I describe the procedure that I survived:
1- I unlock the HTC One M8 bootloader
2- I installed the CWM Recovery: recovery-clockwork-6.0.4.8-m8.img
3- I proceeded to the root with UPDATE-SuperSU-v2.46.zip
And at restart it's where everything gets complicated. It remains stuck on the logo of the boot and can not restart anything. I left for more than an hour to see but nothing moved.
I managed to enter bootloader by associating the volume + and Power key to restart, and when the phone turns off before restarting I do volume- and power.
And the I'm stuck I know more manipulation to make my HTC one M8 work again.
Is the phone ****ing kind unrecoverable?
How to recover my phone?
Help me please
The files (custom recovery and SuperSU) you used are horribly outdated. Unless your current firmware is something like Kitkat, the stuck on boot situation is expected.
Additionally, CWM never officially supported this phone, and that in itself may cause some problems (in addition to being outdated as well).
Correct versions depends on your current firmware number. Most folks (but not all) are on Marshmallow at this point. But you can tell us more by posting what it says for OS number on the bootloader screen. Also, if you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
But likely, you should use a TWRP version 2.8.7 or later. And SuperSU 2.79 or later. Or Magisk to root (latest is 13.3, which should work).
redpoint73 said:
The files (custom recovery and SuperSU) you used are horribly outdated. Unless your current firmware is something like Kitkat, the stuck on boot situation is expected.
Additionally, CWM never officially supported this phone, and that in itself may cause some problems (in addition to being outdated as well).
Correct versions depends on your current firmware number. Most folks (but not all) are on Marshmallow at this point. But you can tell us more by posting what it says for OS number on the bootloader screen. Also, if you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
But likely, you should use a TWRP version 2.8.7 or later. And SuperSU 2.79 or later. Or Magisk to root (latest is 13.3, which should work).
Click to expand...
Click to collapse
Yes indeed I had chosen the wrong files (custom recovery and SuperSU). The phone was on Marshmallow. I opted for a simple solution: to install a stock rom Android Jelly Bean 4.4.2 and wait for the update Marshmallow. But before I have installed last version of TWRP. After installing my rom stock, I installed stock recovery and I relock the bootloader.
thank you for your help
Koukougnon said:
I opted for a simple solution: to install a stock rom Android Jelly Bean 4.4.2 and wait for the update Marshmallow.
After installing my rom stock, I installed stock recovery and I relock the bootloader.
Click to expand...
Click to collapse
I don't think this will work. Your firmware indicated by OS number (in bootloader, not in OS Settings) will still read as updated (MM) and you won't be prompted to update.
Additionally, just as FYI, it is not necessary to relock the bootloader for an OTA update, only for RUU or flashing stock signed firmware.
Stuck on HTC logo screen due to old version TWRP and SuperSU, can often be fixed simply by using the proper updated files. But in the current condition, you will need to unlock the bootloader again. In light of that, it might make sense to restore by RUU (if you version has one - you haven't provided the info requested) or otherwise restore to MM (so ROM matches your firmware) before trying to root again.
Excuse me for my absence. I need your help.
As I said earlier, I opted to go back to a Stock ROM.
Actually as you said, I can not install the update to Marshmallow. It downloads the update but it crashes at installation.
I am sending you the information you requested:
OS number on the bootloader
*** Software statut: Modified ***
*** UNLOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.29.214500021.12G
OpenDSP-v51.2.2-00593-M8674_FO.1015
OS-6.12.401.4
eMMC-boot 2048MB
Dec 17 2015, 14:15:48.0
fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 3.19.0.0000
INFOversion-baseband: 1.29.214500021.12G
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 6.12.401.4
INFOversion-misc: PVT SHIP S-ON
INFOimei2: Not Support
INFOmeid: 00000000000000
INFOproduct: m8_ul
INFOplatform: hTCBmsm8974
INFOmodelid: 0P6B10000
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 76df2b54
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.024s
I still have the TWRP installed and unlock bootloader
Can you help me?
Koukougnon said:
Excuse me for my absence. I need your help.
As I said earlier, I opted to go back to a Stock ROM.
Actually as you said, I can not install the update to Marshmallow. It downloads the update but it crashes at installation.
Click to expand...
Click to collapse
No surprise there. It's best you follow the advice given, instead of making up your own solutions, unless you really know what you are doing. This device has a lot of nuances, and what seems like common sense or a simple solution, often doesn't apply.
OTAs will not install on this device with TWRP, but rather require stock recovery. But it probably doesn't matter, as I stated before, since you are trying to load an update (ROM + firmware), when the firmware is already updated (even if the ROM is not updated), it will likely not install. Basically you have mismatched components, and this will prevent the update from installing. ROM is older, but firmware is updated (version main in getvar indicates firmware is Marshmallow 6.12.401.4).
Koukougnon said:
I still have the TWRP installed and unlock bootloader
Click to expand...
Click to collapse
What version TWRP? You mentioned before the "latest" but did not give a version number. I've had a lot of cases where folks thing they have the "latest" but when prompted for specific version number, it turns out to be an old version.
Just want to be sure before we proceed. After all, the other files you used are going on 3 years old.
redpoint73 said:
No surprise there. It's best you follow the advice given, instead of making up your own solutions, unless you really know what you are doing. This device has a lot of nuances, and what seems like common sense or a simple solution, often doesn't apply.
OTAs will not install on this device with TWRP, but rather require stock recovery. But it probably doesn't matter, as I stated before, since you are trying to load an update (ROM + firmware), when the firmware is already updated (even if the ROM is not updated), it will likely not install. Basically you have mismatched components, and this will prevent the update from installing. ROM is older, but firmware is updated (version main in getvar indicates firmware is Marshmallow 6.12.401.4).
What version TWRP? You mentioned before the "latest" but did not give a version number. I've had a lot of cases where folks thing they have the "latest" but when prompted for specific version number, it turns out to be an old version.
Just want to be sure before we proceed. After all, the other files you used are going on 3 years old.
Click to expand...
Click to collapse
I had installed a stock recovery and relocked the bootloader after installing the rom stock. I received an update for Marshmallow but that crashed at the installation.
After I wanted to install a Rom Custom Nougat for HTC M8, so I unlocked the bootloader, installed TWRP (version twrp-3.1.1-0-m8) then root with SuperSU (the SR1-SuperSU-v2 version. 82-SR1-20170608224931). I installed the rom that no more.
So I reinstalled the rom stock Jelly Bean 4.4.2. That's why I have the TWRP installed and the bootloader unlocked.
Koukougnon said:
.
After I wanted to install a Rom Custom Nougat for HTC M8, so I unlocked the bootloader, installed TWRP (version twrp-3.1.1-0-m8) then root with SuperSU (the SR1-SuperSU-v2 version. 82-SR1-20170608224931). I installed the rom that no more.
Click to expand...
Click to collapse
I'm not sure what that means (what the problem was after flashing the custom ROM). You may have some words missing/wrong in the last sentence.
Flashing the custom ROM should work (seems that it was the real goal here). Did you also flash gapps (Google Apps) which is normally required for AOSP type ROMs? This (or trying a different gapps) is a frequent cause for an AOSP ROM not booting after flashing.
If you still want to return to stock, restore the stock TWRP backup from the collection, using the instructions and files on the following thread. Only need to do through Step 9, and reboot: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Also, keep in mind best practice is to make a TWRP backup of your stock ROM, before trying to root of flash a custom ROM. If you did that, returning to stock would have been as easy as restoring the backup you made.
redpoint73 said:
I'm not sure what that means (what the problem was after flashing the custom ROM). You may have some words missing/wrong in the last sentence.
Flashing the custom ROM should work (seems that it was the real goal here). Did you also flash gapps (Google Apps) which is normally required for AOSP type ROMs? This (or trying a different gapps) is a frequent cause for an AOSP ROM not booting after flashing.
If you still want to return to stock, restore the stock TWRP backup from the collection, using the instructions and files on the following thread. Only need to do through Step 9, and reboot: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Also, keep in mind best practice is to make a TWRP backup of your stock ROM, before trying to root of flash a custom ROM. If you did that, returning to stock would have been as easy as restoring the backup you made.
Click to expand...
Click to collapse
The problem I had with the Custom Rom was that I could not see my Sim contacts. It was a Rom Mokee 7.1.2 for HTC M8.
And I did not backup either the Rom Stock or the Custom Rom.
That's why I installed the Rom Stock 4.4.2 again
Can I install a RUU for HTC M8?
I found this zip file : 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed
Koukougnon said:
The problem I had with the Custom Rom was that I could not see my Sim contacts. It was a Rom Mokee 7.1.2 for HTC M8.
Click to expand...
Click to collapse
The description of events that got you to the current condition, gets more and more convoluted every time you post.
Not critical in this case (returning to stock is fairly simple, and doesn't rely that much on the history). But for other issues, conveying the information this way could be a real problem for those trying to help you.
Koukougnon said:
Can I install a RUU for HTC M8?
I found this zip file : 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed
Click to expand...
Click to collapse
You can. It would require relocking the bootloader. Then if you want TWRP, root or custom ROM, you will need to unlock the bootloader again after RUU. RUU will also wipe all data on the phone.
Must flash with SD card method, or using htc_fastboot
Not gaining much versus what I previously recommended, especially if you want to still have TWRP for root, custom ROM, etc.
redpoint73 said:
The description of events that got you to the current condition, gets more and more convoluted every time you post.
Not critical in this case (returning to stock is fairly simple, and doesn't rely that much on the history). But for other issues, conveying the information this way could be a real problem for those trying to help you.
You can. It would require relocking the bootloader. Then if you want TWRP, root or custom ROM, you will need to unlock the bootloader again after RUU. RUU will also wipe all data on the phone.
Must flash with SD card method, or using htc_fastboot
Not gaining much versus what I previously recommended, especially if you want to still have TWRP for root, custom ROM, etc.
Click to expand...
Click to collapse
I understand I was wrong at first to solve my problem. I got into that. I did not think well before applying the solutions. Thank you for your help.
So, if I understood correctly to flash the RUU,
- relocked the bootloader
- to be S-ON
- flash by SD Card or Fastboot
Should I install a recovery stock before relocking the bootloafer?
My comments/responses below in red font:
Koukougnon said:
So, if I understood correctly to flash the RUU,
- relocked the bootloader yes, using fastboot command: fastboot oem lock
- to be S-ON It's not a requirement to be s-on, but it's your current condition. With s-off, the requirement to lock the bootloader is bypassed (and RUU still works).
- flash by SD Card or Fastboot Either SD card method, or htc_fastboot specifically. Trying to use the "generic" fastboot will fail since the RUU file is too large. IF you need further info, see here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Should I install a recovery stock before relocking the bootloafer? NO. It's not needed when doing RUU.
Click to expand...
Click to collapse
I managed to flash the RUU with your advice. Everything works well.
The only problem is the recovery. When I go into the recovery it shows me a red triangle and nothing happens. But I intend to install the TWRP.
Thank you for your help.
Koukougnon said:
I managed to flash the RUU with your advice. Everything works well.
The only problem is the recovery. When I go into the recovery it shows me a red triangle and nothing happens.
Click to expand...
Click to collapse
That isn't a "problem", it is working as it should. It's the stock recovery. Press vol up and tap the power button to show the recovery menu options (although not much you can do in stock recovery).
Koukougnon said:
Thank you for your help.
Click to expand...
Click to collapse
You're welcome. Please click the "Thanks" button for any post you found helpful.
Some advice and "best practices" as it seems that you've missed a lot of important info when trying to mod the phone:
1) Always research the most up to date info on rooting a device, before you start anything. Files are updated often, and using old methods can (and will) lead to a lot of problems. I know a lot of the info for this device is outdated, or not entirely organized. So feel free to ask questions if you are confused.
2) Always make a TWRP backup of your stock ROM, before doing any mods (root, custom ROM, etc.).
3) Always know how to return to stock, before doing the mods.
4) At least for this device, after installing TWRP, you don't need to root, if you are then going to immediately flash a custom ROM. In other words, you don't need root to flash a ROM. Most ROMs are pre-rooted But the few that are not, you need to flash root (SuperSU or Magisk) after you flash the ROM.
redpoint73 said:
That isn't a "problem", it is working as it should. It's the stock recovery. Press vol up and tap the power button to show the recovery menu options (although not much you can do in stock recovery).
You're welcome. Please click the "Thanks" button for any post you found helpful.
Some advice and "best practices" as it seems that you've missed a lot of important info when trying to mod the phone:
1) Always research the most up to date info on rooting a device, before you start anything. Files are updated often, and using old methods can (and will) lead to a lot of problems. I know a lot of the info for this device is outdated, or not entirely organized. So feel free to ask questions if you are confused.
2) Always make a TWRP backup of your stock ROM, before doing any mods (root, custom ROM, etc.).
3) Always know how to return to stock, before doing the mods.
4) At least for this device, after installing TWRP, you don't need to root, if you are then going to immediately flash a custom ROM. In other words, you don't need root to flash a ROM. Most ROMs are pre-rooted But the few that are not, you need to flash root (SuperSU or Magisk) after you flash the ROM.
Click to expand...
Click to collapse
I understood well. Thank you.
Related
My M8 has the CID of HTC_044 and I would like to flash latest ROM. However it requires latest firmware, ie 2.22.401.4, I am wondering if it is safe to flash the firmware to my device being with different CID as the firmware's android-info does not contain my device CID.
I have S-OFF on my device, I am wondering if I change mt CID to supercid would allow my device to run the firmware without issue.
Thanks in advance.
Yep,if your phone is supercid,u can flash that firmware...
hellcommando said:
My M8 has the CID of HTC_044 and I would like to flash latest ROM. However it requires latest firmware, ie 2.22.401.4, I am wondering if it is safe to flash the firmware to my device being with different CID as the firmware's android-info does not contain my device CID.
I have S-OFF on my device, I am wondering if I change mt CID to supercid would allow my device to run the firmware without issue.
Thanks in advance.
Click to expand...
Click to collapse
If your firmware for CID HTC__044 is 2.22.707.3, it is not necessary for you to flash another firmware to run a 2.22.401.4 ROM.
As long as the firmware is 2.22.xxx.x ... you're good to go.
Anyway it's up to you if you want to flash 2.22.401.4 firmware but your Radio will be the EU region if the firmware that you flash come with radio image. If you currently in Asia, it's best to keep 2.22.707.3 firmware
hdorius said:
Yep,if your phone is supercid,u can flash that firmware...
Click to expand...
Click to collapse
Thank you!
ckpv5 said:
If your firmware for CID HTC__044 is 2.22.707.3, it is not necessary for you to flash another firmware to run a 2.22.401.4 ROM.
As long as the firmware is 2.22.xxx.x ... you're good to go.
Anyway it's up to you if you want to flash 2.22.401.4 firmware but your Radio will be the EU region if the firmware that you flash come with radio image. If you currently in Asia, it's best to keep 2.22.707.3 firmware
Click to expand...
Click to collapse
Thank you! However I have heard there was one 2.22.7xx posted but was meant for M7, and at the moment I could not find 2.22.707.3 firmware from any firmware repository. I'm from Asia, could you please kindly post the link so that I wont brick my phone? Thank you!!
hellcommando said:
Thank you! However I have heard there was one 2.22.7xx posted but was meant for M7, and at the moment I could not find 2.22.707.3 firmware from any firmware repository. I'm from Asia, could you please kindly post the link so that I wont brick my phone? Thank you!!
Click to expand...
Click to collapse
When we read firmware we look at x.xx.707.x not 2.22.7xx.x
You don't need 2.22.707.3 firmware if you already done the OTA update.
Please advise your current firmware that you have ... check what is written on the bootloader ... is it 1.54.707.7 or 2.22.707.3 ?
If it is 1.54.707.7 then you need to do OTA update.
If it is 2.22.707.3 then you're good to flash any ROM.
ckpv5 said:
When we read firmware we look at x.xx.707.x not 2.22.7xx.x
You don't need 2.22.707.3 firmware if you already done the OTA update.
Please advise your current firmware that you have ... check what is written on the bootloader ... is it 1.54.707.7 or 2.22.77.3 ?
If it is 1.54.707.7 then you need to do OTA update.
If it is 2.22.707.3 then you're good to flash any ROM.
Click to expand...
Click to collapse
Couldn't check my firmware version as the OS field is empty in the bootloader.
Hboot: 3.16.0.0000
Radio: 1.16.2133156.UA10G
But I highly doubt my firmware is 2.22.707.3, I would think it is more likely to be 1.54.707.7 as I have rooted by phone before newer firmware roll out.
So can I use your firmware in http://forum.xda-developers.com/showthread.php?t=2701376&page=141
and flash it by using this guide? http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
hellcommando said:
Couldn't check my firmware version as the OS field is empty in the bootloader.
Hboot: 3.16.0.0000
Radio: 1.16.2133156.UA10G
But I highly doubt my firmware is 2.22.707.3, I would think it is more likely to be 1.54.707.7 as I have rooted by phone before newer firmware roll out.
So can I use your firmware in http://forum.xda-developers.com/showthread.php?t=2701376&page=141
and flash it by using this guide? http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
Click to expand...
Click to collapse
Right ... your current hboot is 3.16 so it's 1.54.707.7
I suggest that you restore 1.54.707.7 stock Backup, flash back stock recovery and do the OTA (no need to relock bootloader or S-On .. OTA update work on unlocked bootloader and S-Off)
I don't post firmware on XDA. Those that I posted are recovery and stock backup.
If you insist to update firmware without OTA update .. that's you call. Someone maybe will guide you how to do it as I don't feel comfortable telling how to update firmware.
ckpv5 said:
Right ... your current hboot is 3.16 so it's 1.54.707.7
I suggest that you restore 1.54.707.7 stock Backup, flash back stock recovery and do the OTA (no need to relock bootloader or S-On .. OTA update work on unlocked bootloader and S-Off)
I don't post firmware on XDA. Those that I posted are recovery and stock backup.
If you insist to update firmware without OTA update .. that's you call. Someone maybe will guide you how to do it as I don't feel comfortable telling how to update firmware.
Click to expand...
Click to collapse
Awesome! I just followed your advice by doing the safe way, flashed stock recovery and backup. I'm running on 2.22.707.x now! Thanks a lot :good:
hellcommando said:
Awesome! I just followed your advice by doing the safe way, flashed stock recovery and backup. I'm running on 2.22.707.x now! Thanks a lot :good:
Click to expand...
Click to collapse
Great
Now you can flash any Sense 6 custom ROM that you like.
Only remember that you don't need to flash another firmware, your current one is good enough.. just flash ROM.
I am having the same issue - I have the HTC__044 and need new firmware to get the newest ROM.
I am S-On and CANT get S-off (s-off needed to flash firmware)...firewater does not work with my phone after multiple tries.
I tried getting Sunshine to work for s-off, but I need to be on a stock Sense ROM (I am on Viper 1.8) and don't have a stock backup. I can't find ANY stock ROM's online! Once I have supercid i was going to flash firmware, but without S off...I'm going nowhere (it seems)
anyone have an idea where I should start?
charkswitlazers said:
I am having the same issue - I have the HTC__044 and need new firmware to get the newest ROM.
I am S-On and CANT get S-off (s-off needed to flash firmware)...firewater does not work with my phone after multiple tries.
I tried getting Sunshine to work for s-off, but I need to be on a stock Sense ROM (I am on Viper 1.8) and don't have a stock backup. I can't find ANY stock ROM's online! Once I have supercid i was going to flash firmware, but without S off...I'm going nowhere (it seems)
anyone have an idea where I should start?
Click to expand...
Click to collapse
Stock ROMs and recoveries for HTC__044
http://forum.xda-developers.com/showthread.php?t=2701376
charkswitlazers said:
anyone have an idea where I should start?
Click to expand...
Click to collapse
Everything that you need is here : http://forum.xda-developers.com/showthread.php?t=2701376
1. Restore nandroid backup 1.54.707.7
2. flash stock recovery 1.54.707.7
3. reboot and check for OTA
4. install OTA
5. done .. your ROM will be 4.4.3 - 2.22.707.3
6. flash any 4.4.3 custom ROM that you like if any
All above no need to relock bootloader or S-Off, it works on S-On
If you want to S-Off with sunshine, step 1 & 2 then sunshine
or after step 5 then sunshine (both way should work)
ckpv5 said:
Everything that you need is here
1. Restore nandroid backup 1.54.707.7
2. flash stock recovery 1.54.707.7
3. reboot and check for OTA
4. install OTA
5. done .. your ROM will be 4.4.3 - 2.22.707.3
6. flash any 4.4.3 custom ROM that you like if any
All above no need to relock bootloader or S-Off, it works on S-On
If you want to S-Off with sunshine, step 1 & 2 then sunshine
or after step 5 then sunshine (both way should work)
Click to expand...
Click to collapse
I'm still a little on the noob side with rooting/flashing..I am at work and don't have time to read much - i will go home and give it a go... I'm sure I will have lots of questions
A quick look at the site, i saw lots of recoveries but not very many stock ROMs. I mainly just need a plain/rooted stock Sense rom to run Sunshine. After which i can flash new firmware, then the new custom ROM i've been wanting. Also, does a nandroid HAVE to be HTC__044, or can it be any WWE cid? (like anything that's "HTC__xxx")?
Excuse my ignorance...trying to learn as much as possible
I just got my m8 from Tmobile today, and I am on firmware 157.531.7
I've checked several times for updated firmware, but always comes back nothing.
Am I stuck on this, or will it take awhile for the network to "see me" and send it?
not rooted, fully stock for now
thanks so much!
charkswitlazers said:
I'm still a little on the noob side with rooting/flashing..I am at work and don't have time to read much - i will go home and give it a go... I'm sure I will have lots of questions
A quick look at the site, i saw lots of recoveries but not very many stock ROMs. I mainly just need a plain/rooted stock Sense rom to run Sunshine. After which i can flash new firmware, then the new custom ROM i've been wanting. Also, does a nandroid HAVE to be HTC__044, or can it be any WWE cid? (like anything that's "HTC__xxx")?
Excuse my ignorance...trying to learn as much as possible
Click to expand...
Click to collapse
If your main purpose to restore to stock to get SunShine working, then any nandroid backup will do either HTC__044 or WWE. You don't really need a rooted stock as SunShine works on non-rooted ROM too.
As you said you're a noob, that is why I suggest to restore to 1.54.707.7 then OTA to 2.22.707.3 so you don't need to manually flash firmware to get other custom ROMs running flawlessly. It is not necessary to have 2.22.401.4 firmware but it is necessary to have a 2.22.xxx.x firmware for those custom ROMs, unless you're not in Asia.
As you can see in my sig, I'm on 2.22.707.3 firmware, I can run any ROM without problem.
Being a noob, you may make a stupid mistake when flashing firmware.
There is also by mike or so a stock Rom as a zip.
Flash it like a custom Rom Flash the stock kernel and better the recovery and do sunshine...easier then with getting nandroid backup etc
Slow Booting & Sense 6 Toolbox Not Working On ARHD v10.2
One-M8-Master said:
There is also by mike or so a stock Rom as a zip.
Flash it like a custom Rom Flash the stock kernel and better the recovery and do sunshine...easier then with getting nandroid backup etc
Click to expand...
Click to collapse
Hi One-M8-Master,
I've read quite a few of your posts & given that your moniker seems appropriate, I'm wondering if you might be able to help me?
I've posted this on another thread but haven't got very far as yet, so am hoping that you might be able to get me out of the stupid hole I've dug myself into :fingers-crossed:
It is quite a long description but if you don't fall asleep reading it, I'd really appreciate any help you might be able to give me.....Here goes:
"Hi Guys,
Now I know you're all already thinking that I didn't update my firmware before I flashed ARHD & now I'm getting all the problems that come along with not doing that......& you'd be correct....kind of. HOWEVER, as it turns out, I already seem to have it. Let me explain.
As you can see, I'm relatively new to all this but successfully unlocked, rooted & installed a custom ROM on my ASUS TF700T tablet, so I wanted to do it with my One M8. I always do loads of reading before I start anything (I even read the instructions for new games before I attempt to play them because I'm a bit weird like that!) but what happened on this occasion was that I did the reading, unlocked the phone, flashed TWRP, & rooted it but then ran into the problem that some people appear to have had when trying to s-off via the adb commands & Firewater, that is, my pc could see the phone but when I gave the reboot command, it told me it wasn't connected.
I then got into hours of reading to try & solve this issue, discovered that (without Sunlight) on some devices it just doesn't work once you've accepted the 'should we allow this pc to connect every time' message (which I NEVER normally say 'yes' to), unless you install the Android Studio & Java Develpers Kits, update your version of adb, & force the phone to ask again (which I did but it turned out that I already had the latest version of adb, so that route proved fruitless!). I actually missed a night's sleep trying to resolve the problem, so work wasn't good the next day! but I think it is here is where my problems started because I was so tired & frustrated that I just picked a ROM & flashed it. I had even read the warning about not flashing it if you didn't have the correct firmware but I think that being so tired, it didn't really sink in, or I'd forgotten about it by the time I just flashed the ROM.
By this point, I'd been sat in front of my pc for about 30 hours & needed to go to work but the phone was actually booting through to ARHD, so I was relatively happy in the knowledge that at least I hadn't bricked it! On starting to use the phone that evening, I noticed the long boot times & then that my Sense 6 Toolbox didn't seem to be making any changes, even if I rebooted the device, so I went back to the beginning of this thread & started reading again. Thus, I re-read the firmware warning & panicked (my 2nd mistake!), thinking that I was getting the problems because I hadn't updated the firmware (it still didn't occur to me to just check because I think I just assumed that I wouldn't have it). So.....I tried to restore my TWRP backup of the stock ROM that I made after I had unlocked/rooted, with the intention of reverting to the stock ROM, getting the OTA update & then re-flashing ARHD but despite TWRP telling me that the backup had been successful, the phone went into a bootloop back into TWRP. I solved this by re-flashing the ARHD ROM that I knew at least would get my phone out of the bootloop & back into KitKat, which it did. I then checked what version of the firmware I had & to my surprise, my Build Number in About\Software Information\More says "2.22.401.4 CL365360 release-keys", so it looks like I had the correct firmware version all along?
The above being the case, I'm now puzzled as to why I'm getting the problems that I'm getting with ARHD? Does anyone have any clues/answers that might get me out of this hole I've dug for myself & get my awesome One M8 working like it should?
I know I've caused this problem by doing things when I was too tired to think straight but I'm fresh as a daisy now (still fairly noobish but fresh ) & now I need your help to sort myself out. I would be so grateful for any help anyone can give me to get me back on track.
I hope all of that makes sense & thanks in advance."
@dan5001
The firmware you speak of is the displayed version main number of the flashed rom. It has no relation to your actual installed firmware. Check your bootloader and post here what it says. I bet it is still hboot 3.16 and if that's the case your firmware is not updated.
Mr Hofs said:
@dan5001
The firmware you speak of is the displayed version main number of the flashed rom. It has no relation to your actual installed firmware. Check your bootloader and post here what it says. I bet it is still hboot 3.16 and if that's the case your firmware is not updated.
Click to expand...
Click to collapse
Hi.
This is my own fault but I'm getting really frustrated with it because I've probably spent a total of 40 hours on it so far
I tell you that because I know that I needed S-OFF & SUPER CID to be able to update my firmware, so I just thought "screw it" & I paid for Sunshine. I now have S-OFF & following Vomer's guide here:
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
I now have S-OFF & SUPER CID. I thought that would be the end of my issues but it would appear not!
Looking at my bootloader, you are correct, HBOOT is 3.16.0.0000!
However, I've tried to upgrade this firmware by downloading what I think is the correct update .zip from the list at the bottom of the aforementioned Vomer's guide (v2.22.401.5 (Rename to firmware.zip after downloading)), renaming it as suggested, & then flashing it in TWRP but it just keeps telling me that the update has failed!
Do I have to do it using the adb commands on Vomers guide? I didn't think so but it's just not working??
I appreciate any help you can give me with this. Given that I've spent so long on this & have paid for Sunshine, you can see that I'm trying to help myself but I've still got rain!!
EDIT
Just a thought, I do still have ARHD v10.2 installed at the moment because even though it's not working properly without the correct firmware, it's the only ROM I've got at the moment, so it means I can use the M8 to a degree; would that cause the problem with upgrading the firmware?
Firmware flash can be done via fastboot commands, that's how i did it
Installed rom has no influence on the to flash firmware, try it via fastboot
Hi All,
I have a UK HTC One M8, rooted, S-off, and with ViperOne installed, an old version - 1.8.0
I have flashed a new firmware in order to update ViperOne, and I have lost root access. I used root checker app to verify.
I used this method to flash the firmware:http://forum.xda-developers.com/showthread.php?t=2696282
I obtained the firmware from here: http://android-revolution-hd.blogspot.co.uk/p/android-revolution-hd-mirror-site-var.html
I had changed the cid to supercid, as I am S-off, and i checked that the modelid was correct in "android-info.txt"
The flash went fine, no errors, phone turned on first time, but root access is lost.
This thread I just found says that upgrading the firmware will always cause you to lose root. This is surprising as it wasn't mentioned in any of the guides I read to flashing firmware.
http://forum.xda-developers.com/showthread.php?t=2417442
I was wondering if somebody knowledgeable could reassure me that everything is fine, and perhaps point me to the most appropriate method for getting root access back. I am a little out of my depth here, I learned how to do most of this stuff a year ago when i first rooted, but I haven't been back to update since then, and have forgotten a lot of what I learned before.
Would appreciate any assistance you can offer
Cheers
Will
Willr01 said:
This thread I just found says that upgrading the firmware will always cause you to lose root. This is surprising as it wasn't mentioned in any of the guides I read to flashing firmware.
http://forum.xda-developers.com/showthread.php?t=2417442
Click to expand...
Click to collapse
Different device manufacturers do things in very different ways, so I wouldn't take that thread to mean anything, one way or another, regarding losing root when updating firmware. I also think in that thread, they may be talking about firmware = ROM (as opposed to something very different on HTC devices). In which case, yes, installing a stock ROM will in fact usually remove root on most Android devices.
In any case, see if you still have TWRP installed. That depends on whether the firmware package was modified or not to remove the stock recovery. If TWRP was replaced by stock recovery, simply install TWRP again using your method of choice (personally I prefer installing by fastboot). Then download the SuperSU zip to your phone from here and flash in TWRP.
In reality, I think you may not even have to download SuperSU. If you boot into TWRP and select reboot, I believe TWRP will automatically sense your ROM is not rooted, and ask you if you want it to do so. But I'm not 100% on that, and the SuperSU method is a sure thing.
Thanks a lot for your input. I don't have a recovery installed, so I have tried to flash twrp.
I tried flashing it twice, after reading it can be necessary to do that, and erasing the cache before attempting to boot to recovery. When I try and enter recovery, I get stuck on the startup htc screen with "Entering Recovery..." in pink.
Snippets off other threads have suggested my hboot might not be compatible with the new version of twrp. Is it straightforward to update hboot?
Thanks in advance
Willr01 said:
Snippets off other threads have suggested my hboot might not be compatible with the new version of twrp. Is it straightforward to update hboot?
Click to expand...
Click to collapse
Updating your firmware updates the hboot. 3.19 is the current hboot, and you can check no the bootloader screen.
Make sure its a current version TWRP (2.8.7.0) and I think the opposite is also true (old versions of TWRP don't work with current hboot).
And to clarify, you want to fastboot erase cache, then flash TWRP; as this often clears up issues with TWRP not installing properly.
redpoint73 said:
Updating your firmware updates the hboot. 3.19 is the current hboot, and you can check no the bootloader screen.
Make sure its a current version TWRP (2.8.7.0) and I think the opposite is also true (old versions of TWRP don't work with current hboot).
And to clarify, you want to fastboot erase cache, then flash TWRP; as this often clears up issues with TWRP not installing properly.
Click to expand...
Click to collapse
So my hboot is 3.16, and the twrp was the latest version. I guess i need to find a more up to date firmware file. Any suggestions as to the best sources for firmware?
Willr01 said:
So my hboot is 3.16, and the twrp was the latest version. I guess i need to find a more up to date firmware file. Any suggestions as to the best sources for firmware?
Click to expand...
Click to collapse
What exactly did you flash from the Android Revolution website (what you linked in the top post)?
That website has up-to-date firmware, but what you want is 4.xx version firmware, found under the "Firmware collection" link on that webpage.
Since your hboot number is 3.16, you either did not properly flash a firmware (flashed something else) or flashed a really old firmware (hboot 3.16 corresponds to firmware version 1.xx).
Hi
hope any can help with the issue i am facing, simply i deleted my os & the back up file while trying to flash a rom
all i can access now is twrp recovery screen, i tried flashing a couple of custom rom with no luck
my device is HTC one M8, it was rooted but i don't think it is anymore since it says that i don't have su installed
excuse my lack of android knowledge, as i am new to this whole thing
thanks for reading and any help is appreciated
I never fail to be frustrated at the nearly countless reports here of "I deleted everything on my phone and now its stuck".
If you lack knowledge of Androids mods, the proper way to proceed is to familiarize yourself and understand what you are doing before doing it. The absolute wrong thing to do, is to delete things without knowing what the result will be, and not knowing how to revert from that condition. Plus, the default wipe (user data, cache and Dalvik) on TWRP clearly states that "most of the time, this is the only wipe you need". It says this for good reason, and the additional wipe options are labelled "Advanced" also for good reason. So there were a couple warning signs against doing what you did, that you chose to ignore.
You didn't specify what ROMs you tried (makes it hard to help) and whether you put those on the phone before you wiped the OS; or if you know how to put ROMs on the phone in the current condition (using adb push, or removable SD).
Also, missing some key info:
1) hboot number
2) OS number on hboot screen (or main version as determined by adb getvar all)
3) CID (carrier version) of your phone
4) S-on or s-off
5) What version TWRP
while in TWRP, plug your phone into a computer and under mount you mount the phone as USB, and you copy over a ROM zip, and you flash it as you would normally. that should have fixed it.
ashypanda said:
while in TWRP, plug your phone into a computer and under mount you mount the phone as USB, and you copy over a ROM zip, and you flash it as you would normally. that should have fixed it.
Click to expand...
Click to collapse
While your advice is generally true, the specific ROM (or TWRP version) may part of the issue. OP will need to be careful to flash a ROM that supports his current firmware (hboot, radio, etc.) otherwise he may have some serious problems.
The fact that he said he tried a few ROMs that didn't work, leads me to believe he either has old firmware, or old TWRP.
OP should provide the info I requested in my last post, so we can more specifically help.
thank you for your assitance
1) hboot number:3.16..0.000
2) OS number on hboot screen: nothing apears next to OS on Hboot screen
3) CID (carrier version) of your phone-HTC__j15
4)s-off
5) What version TWRP: 2.7.0.2
hope this info helps
please advise me which rom to use as i am totally lost here
sorry if i caused any disturbance
ahmed.abdelradi said:
thank you for your assitance
1) hboot number:3.16..0.000
2) OS number on hboot screen: nothing apears next to OS on Hboot screen
3) CID (carrier version) of your phone-HTC__j15
4)s-off
5) What version TWRP: 2.7.0.2
hope this info helps
please advise me which rom to use as i am totally lost here
sorry if i caused any disturbance
Click to expand...
Click to collapse
To bring your phone up to date, you can flash the 4.16.1540 firmware posted here. Then update to TWRP 2.8.7 (flash in fastboot), then flash most any current ROM for the M8.
Another option you can flash an old Android 4.4.2 ROM based on software version 1.xx (1.12, 1.54, etc.) to match your old firmware. But in this case, don't update to the latest TWRP before doing so, as it won't work with hboot 3.16.
redpoint73 said:
To bring your phone up to date, you can flash the 4.16.1540 firmware posted here. Then update to TWRP 2.8.7 (flash in fastboot), then flash most any current ROM for the M8.
Another option you can flash an old Android 4.4.2 ROM based on software version 1.xx (1.12, 1.54, etc.) to match your old firmware. But in this case, don't update to the latest TWRP before doing so, as it won't work with hboot 3.16.
Click to expand...
Click to collapse
Personally, I would rather go with a "combined" firmware, such as the ones provided here: http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
Mike's firmwares are incremental afaik (pulled from the OTAs), so jumping from from a 1.xx firmware all the way to an [incremental] 4.16 version, is going to cause problems.
i did the same..
htc one m8
UNLOCKED
S-OFF
cid-11111111
hboot- 3.18.0.0000
radio-1.08.20.0612_4
opendsp- v38.2.2-00542-M8974.0311
os-1.54.651.8
eMMC-boot 2048mb
jul 7 2014, 20:03:18.23767
this is displayed when i turn on my device and i can enter recovery( teamwin recovery project 3.1.1-0 )
i was running on 4.2.2 version and wanted to upgrade to viper rom (i ended up flashing a rom for some other device and deleting every stuff on my internal and sdcard by wiping it in recovery.
kindly help me to how should i get back to 4.2.2 or how can i still get viper rom flashed ...!
thank you.. been trying to get my phone back to 4.2.2 for the past week and havent tried doing viper yet..
plzzzz help...
srijan0008 said:
i did the same..
htc one m8
UNLOCKED
S-OFF
cid-11111111
hboot- 3.18.0.0000
radio-1.08.20.0612_4
opendsp- v38.2.2-00542-M8974.0311
os-1.54.651.8
eMMC-boot 2048mb
jul 7 2014, 20:03:18.23767
this is displayed when i turn on my device and i can enter recovery( teamwin recovery project 3.1.1-0 )
i was running on 4.2.2 version and wanted to upgrade to viper rom (i ended up flashing a rom for some other device and deleting every stuff on my internal and sdcard by wiping it in recovery.
kindly help me to how should i get back to 4.2.2 or how can i still get viper rom flashed ...!
thank you.. been trying to get my phone back to 4.2.2 for the past week and havent tried doing viper yet..
plzzzz help...
Click to expand...
Click to collapse
Dude, your firmware is super old and you won't be able to run the latest ViperROM with it.
Be aware what I'm telling you to do will wipe your phone, (you'll need to do a full wipe to flash the ViperROM anyway)
Go here to download the official RUU from HTC's US website
Scroll down to the "Manual System Update Instructions" and read them. The RUU download is at the end of the instructions
After the RUU has run, reflash TWRP, then flash the ROM
srijan0008 said:
i did the same..
Click to expand...
Click to collapse
A word of advice, I know you are new here, but posting "I did the same" or similar ("same problem" etc.) is never true. Especially since you are responding to a thread from 2 years ago, different M8 versions, different ROM, different TWRP version.
There are simply far too many differences to say you "did the same" and that statement is therefore meaningless. Better to just describe the exact issue (which you did) and not bother with such vague statements.
srijan0008 said:
os-1.54.651.8
this is displayed when i turn on my device and i can enter recovery( teamwin recovery project 3.1.1-0 )
i was running on 4.2.2 version and wanted to upgrade to viper rom
Click to expand...
Click to collapse
As xunholyx explained you need to update the firmware, not just the ROM. Firmware includes a whole bunch of other partitions (hboot, radio, WiFi, and more) that ROM doesn't touch. Old firmware (your is very old) is not compatible with a more recent version ROM.
Old firmware is also not compatible with the current TWRP 3.1.1-0, so the ROM won't flash properly, either.
So as already suggested, flash RUU to update all the firmware. Then flash TWRP 3.1.1-0 back to the phone, and flash Viper.
srijan0008 said:
i ended up flashing a rom for some other device and deleting every stuff on my internal and sdcard by wiping it in recovery.
Click to expand...
Click to collapse
Another good rule of thumb, do NOT wipe things in TWRP "Advanced" wipe options, unless you know exactly what it is, and what the result will be. Wiping internal storage and/or SD will in most cases not help matter, but just make them worse (wipe backups, ROM zips, etc.).
Ragazzi ho acquistato un m8 di seconda mano con su la viperone...vorrei tornare a stock.. Mi potere aiutare per favore? Non ho esperienza di modding con htc
Guys I buy a m8 used on the viperone ... I would go back to stock .. can you help me please? I have no experience of modding with htc.. Sorry forma my english
Do you know how to boot to bootloader ? And write here what's written on it ?
ckpv5 said:
Do you know how to boot to bootloader ? And write here what's written on it ?
Click to expand...
Click to collapse
hey ckpv5
I want too to return my htc one m8 to complete factory stock, stock rom with ota updates
I am currently S-OFF and bootloader unlocked
any help to do this please ?
You can read this : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Without info, can't help much. You need to provide your fastboot getvar all details
Being S-Off, I believe it is very much easier to return to stock (unless your stock is a rare version)
ckpv5 said:
You can read this : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Without info, can't help much. You need to provide your fastboot getvar all details
Being S-Off, I believe it is very much easier to return to stock (unless your stock is a rare version)
Click to expand...
Click to collapse
hey again
here are the details :
INFOversion: 0.5
INFOversion-bootloader: 3.19.0.0000
INFOversion-baseband: 1.22.21331147A1.29G
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.28.401.9
INFOversion-misc: PVT SHIP S-OFF
INFOimei2: Not Support
INFOmeid: 00000000000000
INFOproduct: m8_ul
INFOplatform: hTCBmsm8974
INFOmodelid: 0P6B10000
INFOcidnum: HTC__002
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: df77f8b7
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.020s
dave_lp said:
hey again
here are the details :
INFOversion: 0.5
INFOversion-bootloader: 3.19.0.0000
INFOversion-baseband: 1.22.21331147A1.29G
INFOversion-main: 3.28.401.9
INFOversion-misc: PVT SHIP S-OFF
INFOmodelid: 0P6B10000
INFOcidnum: HTC__002
Click to expand...
Click to collapse
First - delete the serial no. & imei no. on your above post.
Now you have two options:
1. The RUU way - you need a Windows PC with USB2.0, latest HTC USB driver installed.
RUU will wipe everything and make your phone out of the box state, so make backup of your important files like music, photos & etc from your internal storage
Download the RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed.exe
Here : http://androidruu.com/?developer=M8
Connect your device to PC (preferable put it on bootloader/fastboot mode)
Right click the RUU exe and select run as administrator and follow all the instructions until it completes the process.
This will take you directly to lollipop and then do OTA to 4.16.401.13
2. The nandroid backup way - the link that I gave you earlier and read thoroughly the 14 steps on post #1
Install TWRP 2.8.70
Restore the 3.28.401.9 backup
Install the 3.28.401.9 stock recovery
Reboot, then do OTA to 4.16.401.10 then OTA to 4.16.401.13
I will follow all the steps and I will keep you informed.
Thank you very much for your help ckpv5
ckpv5 said:
First - delete the serial no. & imei no. on your above post.
Now you have two options:
1. The RUU way - you need a Windows PC with USB2.0, latest HTC USB driver installed.
RUU will wipe everything and make your phone out of the box state, so make backup of your important files like music, photos & etc from your internal storage
Download the RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed.exe
Here : http://androidruu.com/?developer=M8
Connect your device to PC (preferable put it on bootloader/fastboot mode)
Right click the RUU exe and select run as administrator and follow all the instructions until it completes the process.
This will take you directly to lollipop and then do OTA to 4.16.401.13
2. The nandroid backup way - the link that I gave you earlier and read thoroughly the 14 steps on post #1
Install TWRP 2.8.70
Restore the 3.28.401.9 backup
Install the 3.28.401.9 stock recovery
Reboot, then do OTA to 4.16.401.10 then OTA to 4.16.401.13
Click to expand...
Click to collapse
The RUU way not working, I tried it on 3 PC, an error comes up when I right click and try to run as administrator
An error (-5001 : 0x80070002) has occurred while running the setup.
Please make sure you have finished any previous setup and closed other application.
If the error still occurs, please contact your vendor.
dave_lp said:
The RUU way not working, I tried it on 3 PC, an error comes up when I right click and try to run as administrator
An error (-5001 : 0x80070002) has occurred while running the setup.
Please make sure you have finished any previous setup and closed other application.
If the error still occurs, please contact your vendor.
Click to expand...
Click to collapse
Tried on 3 PC but the same downloaded RUU ?
You may have bad download. Check the md5, it should match
8cb9b5d9091164cd57b6e04459bee3c6
ckpv5 said:
Tried on 3 PC but the same downloaded RUU ?
You may have bad download. Check the md5, it should match
8cb9b5d9091164cd57b6e04459bee3c6
Click to expand...
Click to collapse
Effectively, the MD5 doesn't match, I redownloaded it and everything was fine, the installation done without issue, actually I'm 4.16.401.13.
That's really nice I finally can do OTA updates
I could not have made it without your help.
Thank you so much
I'd like to reinstall a custom rom because this one eats a lot the battery
If it's not too much to ask again, I'd like to know in case I want to reinstall a custom rom, how do I proceed ?
because I saw your custom roms and they made me want to try them, they look awesome
Thanks in advance
dave_lp said:
If it's not too much to ask again, I'd like to know in case I want to reinstall a custom rom, how do I proceed ?
because I saw your custom roms and they made me want to try them, they look awesome
Thanks in advance
Click to expand...
Click to collapse
Give me 1/2 hour to respond.. bit busy, no need to bump again
ckpv5 said:
Tried on 3 PC but the same downloaded RUU ?
You may have bad download. Check the md5, it should match
8cb9b5d9091164cd57b6e04459bee3c6
Click to expand...
Click to collapse
If it's not too much to ask again, I'd like to know in case I want to reinstall a custom rom, how do I proceed ?
because I saw your custom roms and they made me want to try them, they look awesome besides the ota update eats a lot my battery
Thanks in advance
---------- Post added at 03:39 PM ---------- Previous post was at 03:38 PM ----------
ckpv5 said:
Give me 1/2 hour to respond.. bit busy, no need to bump again
Click to expand...
Click to collapse
ok sorry
dave_lp said:
If it's not too much to ask again, I'd like to know in case I want to reinstall a custom rom, how do I proceed ?
because I saw your custom roms and they made me want to try them, they look awesome
Thanks in advance
Click to expand...
Click to collapse
I don't release any personal custom ROM
What you see is the custom ROM that I use to help fixing things here & there.
Your device is S-Off and still bootloader unlocked, right ?
To install custom ROM :
1. Install TWRP 2.8.7.0 - you know where to get it because you've been in my thread before
2. Put the custom ROM.zip to your internal or external storage
3. In TWRP make a backup of your current ROM
4. In TWRP select install menu then select the ROM.zip to install
5. Reboot .. done
For you to read - http://forum.xda-developers.com/showthread.php?t=2744194
ckpv5 said:
I don't release any personal custom ROM
What you see is the custom ROM that I use to help fixing things here & there.
Your device is S-Off and still bootloader unlocked, right ?
To install custom ROM :
1. Install TWRP 2.8.7.0 - you know where to get it because you've been in my thread before
2. Put the custom ROM.zip to your internal or external storage
3. In TWRP make a backup of your current ROM
4. In TWRP select install menu then select the ROM.zip to install
5. Reboot .. done
For you to read - http://forum.xda-developers.com/showthread.php?t=2744194
Click to expand...
Click to collapse
well, so following these steps i can install any custom rom ?
thank you for all and for the link, this gonna answer lot of my questions
dave_lp said:
well, so following these steps i can install any custom rom ?
thank you for all and for the link, this gonna answer lot of my questions
Click to expand...
Click to collapse
Yes .. the basic steps to install any custom ROM. Anything extra you can read the ROM thread instructions
And thanks for that I just received. It is highly appreciated
ckpv5 said:
Yes .. the basic steps to install any custom ROM. Anything extra you can read the ROM thread instructions
And thanks for that I just received. It is highly appreciated
Click to expand...
Click to collapse
Well, I just installed TWRP 2.8.7.0 and made a backup of my current ROM, then I downloaded SkyDragon M8 v1.5.1 Sense 7 Android 6.0 from here : http://forum.xda-developers.com/htc-one-m8/development/rom-sd-4-0-sense7-port-sdkernel-t3062378
and before attempting the installation I wanted to be sure that I'm not wrong choosing the custom ROM
also after finishing the backup and the device was about rebooting, TWRP asked to swip to install supersu to root the device
so swiping to install supersu will root my device ?
and last question pls if it's not too much asking
In case I want to reinstall the stock ROM again, shall I run the stock ROM I downloaded as you explained me above through RUU way ?
asking too many questions because it's a demo unit device and I want to switch between stock and custom ROM without bricking it
and thanks to you too
dave_lp said:
Well, I just installed TWRP 2.8.7.0 and made a backup of my current ROM, then I downloaded SkyDragon M8 v1.5.1 Sense 7 Android 6.0 from here : http://forum.xda-developers.com/htc-one-m8/development/rom-sd-4-0-sense7-port-sdkernel-t3062378
and before attempting the installation I wanted to be sure that I'm not wrong choosing the custom ROM
also after finishing the backup and the device was about rebooting, TWRP asked to swip to install supersu to root the device
so swiping to install supersu will root my device ?
and last question pls if it's not too much asking
In case I want to reinstall the stock ROM again, shall I run the stock ROM I downloaded as you explained me above through RUU way ?
asking too many questions because it's a demo unit device and I want to switch between stock and custom ROM without bricking it
and thanks to you too
Click to expand...
Click to collapse
You can ask any question related to the ROM in the ROM thread because this thread is about stock ROM
When you want to reinstall stock ROM, just restore the backup that you made. The RUU was for a lower version, now your firmware/software is at higher version.
TWRP ask about root because you have non-rooted custom ROM. If you want to run a rooted stock ROM, yes just swipe to root.
If you want to install custom ROM, no need to root because custom ROM is pre-rooted.
I have no idea about demo unit, but I believe a clean stock ROM or a custom ROM will remove that. You run the RUU before and updated to the latest, it is no more demo feature running, right ?
ckpv5 said:
You can ask any question related to the ROM in the ROM thread because this thread is about stock ROM
When you want to reinstall stock ROM, just restore the backup that you made. The RUU was for a lower version, now your firmware/software is at higher version.
TWRP ask about root because you have non-rooted custom ROM. If you want to run a rooted stock ROM, yes just swipe to root.
If you want to install custom ROM, no need to root because custom ROM is pre-rooted.
I have no idea about demo unit, but I believe a clean stock ROM or a custom ROM will remove that. You run the RUU before and updated to the latest, it is no more demo feature running, right ?
Click to expand...
Click to collapse
Do I need to wipe everything before to select install in the TWRP menu or no need to wipe ? will I just select the ROM.zip in the TWRP install menu to install ?
I believe a custom rom will remove the demo unit but not the stock rom, after OTA update, an application called demo that I cant uninstall was installed itself and plays a demo video every 2 or so minutes and some others stuff like rebooting the device was removing my installed applications...
I couldn't do a factory reset as the OK button was greyed out, the developer mode can't be touched but USB debugging mode was on when I connect it to the PC so I tried to factory reset from the bootloader, it worked, and when the devide loaded I disabled all automatic updates so till now it works as a normal phone
updating it may mess it up again
I read HERE if I supercid! (11111111) will have a 100% generic device, OTA updates and all... Demo won't even install. Any knowledge about how to supercid ?
Thanks
Hi all, I am playing around with an HTC m8 to decide if I should use it as replacement of my Nexus 4 (so far, too big and heavy ).
But well, I unlocked the phone and installed TWRP. All worked fine, but then I flashed supersu and I'm stucked in a boot loop. I am reading a lot of things but I am unsure about what to do now and how to actually root the phone and start installing a different ROM as I don't know what´s the phone model. It says M8_UL in fastboot...
I´m looking at this but not sure if this phone is gpe.
http://forum.xda-developers.com/htc-one-m8/general/root-root-marshmallow-gpe-supersu-t3242210
Any ideas?
Thanks!
1. flash TWRP 3.0.20
2. boot TWRP
3. copy SuperSU v.[2].56 zip to SD card of device in TWRP if on Marshmallow.
4. Flash SuperSu v.[2].56 zip
5. You should boot if you were booting before flashing TWRP.
EDIT: corrected SuperSU version.
spideyngo said:
1. flash TWRP 3.0.20
2. boot TWRP
3. copy SuperSU v.1.56 zip to SD card of device in TWRP if on Marshmallow.
4. Flash SuperSu v.1.56 zip
5. You should boot if you were booting before flashing TWRP.
Click to expand...
Click to collapse
I did that but still stuck in the HTC screen. I flashed 1.56 and I have TWRP 3.0.20 but I'm S-ON, does it matter?
Thanks,
frozst said:
I am reading a lot of things but I am unsure about what to do now and how to actually root the phone and start installing a different ROM
Click to expand...
Click to collapse
You don't need to root in order to install a custom ROM. Once you have TWRP installed, just put a ROM on the phone (download ROM direct to phone, copy to SD card, adb push, etc.), boot into TWRP, and install the ROM (also recommended to backup the stock ROM before flashing a custom ROM, and also do default wipe in TWRP before ROM flash - data, cache and Dalvik).
All custom ROMs are pre-rooted, so you don't need to root separately after flashing a ROM, either. Although, some AOSP based ROMs need root enabled in phone Settings>Developer's Options.
---------- Post added at 11:07 AM ---------- Previous post was at 11:05 AM ----------
frozst said:
I did that but still stuck in the HTC screen. I flashed 1.56 and I have TWRP 3.0.20 but I'm S-ON, does it matter?
Click to expand...
Click to collapse
S-on is fine. I don't know why the previous user stated SuperSU 1.56. That build is ancient, and will definitely not work on Marshmallow. Might be a typo, or they were just thinking of the wrong number (maybe 2.56).
Latest stable version SuperSU 2.76 is recommended for rooting Marshmallow: https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip
But as already mentioned, you don't need root to flash custom ROMs.
frozst said:
I did that but still stuck in the HTC screen. I flashed 1.56 and I have TWRP 3.0.20 but I'm S-ON, does it matter?
Thanks,
Click to expand...
Click to collapse
EDIT: SuperSU version 2.56. Sorry about that.
I am have an AT&T HTC One M8 on stock Marshmallow. SuperSU 2.76 puts my Marshmallow M8 in a boot loop. You may need to flash a rooted stock ROM to repair booting. S-off not needed, but makes your life easier.
Thanks! the problem was the old SU version, solved now and testing different ROMs. Any recomendations?
spideyngo said:
I am have an AT&T HTC One M8 on stock Marshmallow. SuperSU 2.76 puts my Marshmallow M8 in a boot loop.
Click to expand...
Click to collapse
Hadn't heard that. I wonder if its a known issue experienced by others? If so, I'll fall back to my previous recommendation to use 2.65, which was the former "latest" STABLE version; and no complaints that I am aware of.
Hello, HTC One M9 (Sprint here) I'm stuck in a bootloop too after unlocking the bootloader and installing SU. Tried several version of SuperSU without anyluck. Can anyone help please ?
kbytes said:
Hello, HTC One M9 (Sprint here) I'm stuck in a bootloop too after unlocking the bootloader and installing SU. Tried several version of SuperSU without anyluck. Can anyone help please ?
Click to expand...
Click to collapse
This forum is for the M8, any advice you get may not be correct. Post in the M9 forum.
But what I can say, is if you say "several version" SuperSU is not specific enough (when you post to the correct device forum). Be specific as to what version numbers you tried. Nobody can help, if you don't give the proper info to see what you did wrong. In particular, you need to provide info on what Android version your phone is currently on, what TWRP version, what SuperSU version(s) you tried.
But again, post to the M9 forum, not here.
Stuck on HTC Screen.
I've read through here and see that someone got their M8 off of the HTC start screen. I've installed the SuperSU, and TWRP, the phone restarted and now is stuck on the HTC screen. I am unable to hard reset the phone at all. Its stuck on that screen. Help?
weismanak said:
I've read through here and see that someone got their M8 off of the HTC start screen. I've installed the SuperSU, and TWRP, the phone restarted and now is stuck on the HTC screen. I am unable to hard reset the phone at all. Its stuck on that screen. Help?
Click to expand...
Click to collapse
You probably used an old version TWRP and/or old version SuperSU.
TWRP 3.0.2 and SuperSU 2.76 is recommended.
Hold power+vol up for a minute or so, to force a reboot. Once the screen goes dark to reboot, let go of the buttons, and only hold vol down. Don't let go of vol down, until you are in bootloader. If the phone just gets stuck on the logo screen again, you just got the timing wrong; either didn't start pressing vol down soon enough, or let go too early. Just repeat the process, until you get to bootloader.
From there, restore TWRP backup (which you should always make before attempting to root) and try again, with the proper versions TWRP and SuperSU.
If no TWRP backup, flash proper version TWRP in fastboot, then get proper version SuperSU to the phone (adb push, or put the file on SD card).
Still stuck in boot loop... but different place.
Whew!! OK, so I got past that hurdle (Thank you so much). I'm using the WinDroid Toolkit version 3.1 to unlock the bootloader, flash the TWRP, then flash the SuperSU. The phone is now stuck at the bootloader. If I select "Recovery" it simply comes back to the "Fastboot-usb". I've attached a screen shot (maybe) to demonstrate what I'm seeing on the phone.
*** Software status: Modified ***
*** RELOCKED ***
*** Security Warning ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.000
[email protected]
Open DSP-v56.2.2-00593-M8974_FO.0126
OS-6.20.502.5
eMMC-boot 2048MB
Apr 14 2016,19:39:46.0
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
Click to expand...
Click to collapse
Thanks for all your help, I'm a noOb to this process. Recent convert from iOS.
weismanak said:
I'm using the WinDroid Toolkit version 3.1 to unlock the bootloader, flash the TWRP, then flash the SuperSU. .
Click to expand...
Click to collapse
Meaning you used the TWRP version and SuperSU version included with the toolkit? If so, that toolkit hasn't been updated in a long time, and likely is not using the versions TWRP and SuperSU that I specified previously.
Additionally, I don't personally recommend using such toolkits. Doing so robs you of a valuable learning experience, and therefore guarantees that you stay a n00b. Also, the toolkits constitute an additional point of failure (even when they are updated) that is not necessary. I've often seen processes fail using the toolkits, when the exact same steps complete just fine if done "manually".
Since it appears you've successfully unlocked the bootloader (can be verified if it says UNLOCKED near the top of the bootloader screen), than I would advise:
1) Manually flash TWRP 3.0.2 with fastboot using the instructions here: https://twrp.me/devices/htconem8gsm.html
2) Download SuperSU 2.76 from here, and put it on SD card (alternately, adb push to phone - but that may be a bit complicated for you).
3) Boot into TWRP, under Install, navigate to the SuperSU 2.76 zip, and flash it.
redpoint73 said:
You don't need to root in order to install a custom ROM. Once you have TWRP installed, just put a ROM on the phone (download ROM direct to phone, copy to SD card, adb push, etc.), boot into TWRP, and install the ROM (also recommended to backup the stock ROM before flashing a custom ROM, and also do default wipe in TWRP before ROM flash - data, cache and Dalvik).
All custom ROMs are pre-rooted, so you don't need to root separately after flashing a ROM, either. Although, some AOSP based ROMs need root enabled in phone Settings>Developer's Options.
---------- Post added at 11:07 AM ---------- Previous post was at 11:05 AM ----------
S-on is fine. I don't know why the previous user stated SuperSU 1.56. That build is ancient, and will definitely not work on Marshmallow. Might be a typo, or they were just thinking of the wrong number (maybe 2.56).
Latest stable version SuperSU 2.76 is recommended for rooting Marshmallow: https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip
But as already mentioned, you don't need root to flash custom ROMs.
Click to expand...
Click to collapse
but when checked with root checker, it is showing not rooted. i'm not able to install root apps like flashify, supersu, root explorer. they all say that the phone is not rooted. i'm on mokee 60.1 release running on my redmi 2
ajay vadaparthi said:
but when checked with root checker, it is showing not rooted. i'm not able to install root apps like flashify, supersu, root explorer. they all say that the phone is not rooted. i'm on mokee 60.1 release running on my redmi 2
Click to expand...
Click to collapse
have you flashed the latest supersu.zip ?
does the flashing process ended with success ?
you may try to enable root in developer options and see
also you are in the wrong forum
Sent from my HTC M8 using XDA Labs
Can I re-flash SuperSU over an existing one?
Hi - Long time listener, first time caller!
So, I have a similar issue. After having my HTC M9 for almost 2 years, I decided to take the plunge and get the bootloader unlocked in order for me to update to v7 Nougat (currently on v6 Marshmellow) as Vodafone UK are a little slow in getting the update push out.
I followed a UTube video and all seemed to be going well after I restarted the handset after the bootloader unlock. I then had to enable the Dev Options and enable the USB Debugging in order for me to flash SuperSU 2.46 via TWRP 3.0.2.0.
However, TWRP informed me that the root was successful and to go ahead and reboot. Which I did. But it's now stuck on the HTC One splashscreen and won't proceed any further.
I still have access to TWRP and my PC was able to find the phone when connected with a usb cable (so in a state of softbrick). The FOOLISH thing I now realise, is that I didn't do a back-up of the stock ROM before flashing SuperSU. I've tried to search for a suitable RUU that I can download and get back to stock ROM (and then to unlock the bootloader so I can get v7 Nougat OTA). I'm surprised that there isn't a suitable RUU for my device (details below) and the 2 zips that I have downloaded via XDA simply wouldn't extract for me to get into the tool to flash the stock.
I've decided to go for a custom ROM (one that is with Nougat architecture/feel) if I can't allocate an RUU for my device.
I've come across too many forums and advice that I'm now overloaded with info and not sure which one to follow! Any help would be greatly appreciated as this device is one of the best handsets I've ever had (I've had handsets from early 2000's inc. an iPoo) and need to get it back up and running.
From the bootloader menu these are the details I have:
HTC_HIMA UHL PVT S-ON
LK - 1.0.0.0000
Radio - 01.01_U11440792_96.00.51201G_F
OpenDSP - 15.6.1.0052.8994_1026
OS - 3.35.161.12
Dec 17 2015, 00:40:10 (671447)
MRA58K_Release-Keys
This is a UK Vodafone carrier, model OPJA100 fcc id NM8OPJA100 M9u.
As the title of this thread suggests; can I simply delete the SuperSU v2.46 zip from the root directory, and download / paste SuperSU v2.76 to fix the stuck bootloader screen?
Or, as I have 2 downloads of the RUU.zip file, can I rename one, place it on my external SD card (64gb), go to bootloader and let the device install the stock?
As this device is softbricked, I'm open to suggestions for either stock ROM or custom ROM install.
Thanks in advance.
tigarstyle said:
Hi - Long time listener, first time caller!
So, I have a similar issue. After having my HTC M9 for almost 2 years, I decided to take the plunge and get the bootloader unlocked in order for me to update to v7 Nougat (currently on v6 Marshmellow) as Vodafone UK are a little slow in getting the update push out.
I followed a UTube video and all seemed to be going well after I restarted the handset after the bootloader unlock. I then had to enable the Dev Options and enable the USB Debugging in order for me to flash SuperSU 2.46 via TWRP 3.0.2.0.
However, TWRP informed me that the root was successful and to go ahead and reboot. Which I did. But it's now stuck on the HTC One splashscreen and won't proceed any further.
I still have access to TWRP and my PC was able to find the phone when connected with a usb cable (so in a state of softbrick). The FOOLISH thing I now realise, is that I didn't do a back-up of the stock ROM before flashing SuperSU. I've tried to search for a suitable RUU that I can download and get back to stock ROM (and then to unlock the bootloader so I can get v7 Nougat OTA). I'm surprised that there isn't a suitable RUU for my device (details below) and the 2 zips that I have downloaded via XDA simply wouldn't extract for me to get into the tool to flash the stock.
I've decided to go for a custom ROM (one that is with Nougat architecture/feel) if I can't allocate an RUU for my device.
I've come across too many forums and advice that I'm now overloaded with info and not sure which one to follow! Any help would be greatly appreciated as this device is one of the best handsets I've ever had (I've had handsets from early 2000's inc. an iPoo) and need to get it back up and running.
From the bootloader menu these are the details I have:
HTC_HIMA UHL PVT S-ON
LK - 1.0.0.0000
Radio - 01.01_U11440792_96.00.51201G_F
OpenDSP - 15.6.1.0052.8994_1026
OS - 3.35.161.12
Dec 17 2015, 00:40:10 (671447)
MRA58K_Release-Keys
This is a UK Vodafone carrier, model OPJA100 fcc id NM8OPJA100 M9u.
As the title of this thread suggests; can I simply delete the SuperSU v2.46 zip from the root directory, and download / paste SuperSU v2.76 to fix the stuck bootloader screen?
Or, as I have 2 downloads of the RUU.zip file, can I rename one, place it on my external SD card (64gb), go to bootloader and let the device install the stock?
As this device is softbricked, I'm open to suggestions for either stock ROM or custom ROM install.
Thanks in advance.
Click to expand...
Click to collapse
your first post in the wrong forum this forum for m8 )
if you can flash a rom then flash it,will save the hassle of flashing RUU
and you used an outdated version of supersu ( i don't know if this will fix it but try to flash the latest version on top the older )
you can rename the RUU to 0PJAIMG.zip and put it in the sd card root ( formatted as fat32 or exfat , 3.xx can flash RUU from exfat cards ) then reboot to download mode and follow the instruction
if you have any question ask in the m9 forum as you may get a wrong answer here :silly:
Thanks a lot. I didn't realise this forum was for M8 only, my mistake. I've now posted in the correct forum.
I'll see what they suggest, but I didn't want to flash another SuperSU on top of another in case my phone was hard bricked. I guess I'm lucky that I have a connection with the PC as I can see the internal storage of my device still and I still have access to TWRP.
One thing that the other forums I've read so far didn't mention, is whether or not it matters that I can't extract the RUU.zip file on my PC. I'm I supposed to just place it on the SD Card and let it flash the Stock ROM, or do I need to extract the zip file in order to get to the utility program? Just thought it might be worth sharing for anyone who is on M8 and stuck on the HTC One splashscreen like I am.
tigarstyle said:
I'll see what they suggest, but I didn't want to flash another SuperSU on top of another in case my phone was hard bricked.
Click to expand...
Click to collapse
If the phone was hard bricked, you wouldn't be able to flash anything. The screen wouldn't come on at all. A hard brick means you need to open the phone to repair it (new motherboard or JTAG, at a minimum). You don't have a hard brick.
Do you mean to ask if flashing the proper SuperSU would brick the phone (if its safe to flash)? If that is the question, you best direct it to folks knowledgeable to the M9. On the M8, its fine to flash the newer SuperSU (and the proper fix after flashing obsolete SuperSU). But that doesn't meant the M9 is the same. And following advice meant for another device can possibly damage the device.
tigarstyle said:
One thing that the other forums I've read so far didn't mention, is whether or not it matters that I can't extract the RUU.zip file on my PC. I'm I supposed to just place it on the SD Card and let it flash the Stock ROM, or do I need to extract the zip file in order to get to the utility program?
Click to expand...
Click to collapse
Nowhere in any instructions for flashing RUU.zip will you see anything about extracting files from the RUU.zip.
Therefore, don't do it.
The file is encrypted and signed. Even if you were able to extract anything, you wouldn't be able to flash it with s-on (s-on can't flash unsigned RUU zips).
Excellent, thank you. I was wondering why the zip file wouldn't extract on the PC. I saw videos explaining that in other to get to Stock ROM, you'd do it via the RUU.zip. So when I downloaded the RUU.zip Stock ROM file, I thought I had to extract the zip in order to get to the application, then flash the device.
Thanks for taking the time out to explain in detail...much appreciated.