Related
I have an unlocked HTC One X, running Stock Rom and CMW recovery. CID 621. (never installed any custom roms, only CMW recovery and unlocking the phone)
I haven't updated my phone in a while since OTA failed due to the recovery. Last night I reverted back to the stock recovery and updated, successfully, OTA version 2.18.751.7.
After updating my One X informs me there's a JB OTA update, 3.14.751.20 but when I try to run it, it reboots, shows the green progress bar for about 30 seconds then shows the red rectangular of failure (rebooting starts up the device normally).
I tried reflashing the stock recovery, tried the recovery from the latest RUU for my CID (RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_2.1204.136.21_release_275588_signed) but the OTA update keeps failing.
I also tried disabling SuperSU and used Voodoo Root Keeper to disable root, still the same red rectangular. Tried using the nandroid backup and running through the updates again, but same issue (2.18.751.7 installs correctly, but 3.14.751.20 fails).
Any help would be appreciated!
Thanks,
Maya
mayashoval said:
I have an unlocked HTC One X, running Stock Rom and CMW recovery. CID 621. (never installed any custom roms, only CMW recovery and unlocking the phone)
I haven't updated my phone in a while since OTA failed due to the recovery. Last night I reverted back to the stock recovery and updated, successfully, OTA version 2.18.751.7.
After updating my One X informs me there's a JB OTA update, 3.14.751.20 but when I try to run it, it reboots, shows the green progress bar for about 30 seconds then shows the red rectangular of failure (rebooting starts up the device normally).
I tried reflashing the stock recovery, tried the recovery from the latest RUU for my CID (RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_2.1204.136.21_release_275588_signed) but the OTA update keeps failing.
I also tried disabling SuperSU and used Voodoo Root Keeper to disable root, still the same red rectangular. Tried using the nandroid backup and running through the updates again, but same issue (2.18.751.7 installs correctly, but 3.14.751.20 fails).
Any help would be appreciated!
Thanks,
Maya
Click to expand...
Click to collapse
Have you tried relocking your bootloader? 'fastboot oem lock'
Also, maybe try flashing the stock kernel as well?
Did you remove anything?
You might try running an RUU if you can one one new enough, or restoring a backup (there are threads here for both backups and RUU, but look on htcruu.com, the device is endeavoru)
ArmedandDangerous said:
Also, maybe try flashing the stock kernel as well?
Click to expand...
Click to collapse
I'm hesitant about flashing a kernel, as I did not change the original stock one, and it feels too risky.
BenPope said:
Did you remove anything?
You might try running an RUU if you can one one new enough, or restoring a backup (there are threads here for both backups and RUU, but look on htcruu.com, the device is endeavoru)
Click to expand...
Click to collapse
I thought about that, but the most recent RUU for my CID is older than what getvar is telling me (INFOversion-main: 2.18.751.7. latest RUU I found is: RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_2.1204.136.21_release_275588_signed).
As to relock, I went through quite a few similar threads and in all relocking did not make any difference. Also, if that was the case, I don't think the first OTA update would have gone through.
mayashoval said:
I thought about that, but the most recent RUU for my CID is older than what getvar is telling me (INFOversion-main: 2.18.751.7. latest RUU I found is: RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_2.1204.136.21_release_275588_signed).
As to relock, I went through quite a few similar threads and in all relocking did not make any difference. Also, if that was the case, I don't think the first OTA update would have gone through.
Click to expand...
Click to collapse
I think the update to hboot requires it to be locked, your previous update was most likely ok with the hboot it was on.
mayashoval said:
I thought about that
Click to expand...
Click to collapse
Then look for a backup of your ROM version in the backup thread.
BenPope said:
Then look for a backup of your ROM version in the backup thread.
Click to expand...
Click to collapse
Sorry to be a noob but what do you mean? I thought I couldn't use a backup older than the one listed under "main version". Or am I confusing things?
Edit:
Can I install the most recent RUU?
INFOversion-main: 2.18.751.7.
latest RUU is: RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_ 2.1204.136.21_release_275588_signed.
Update: locking the phone did not help
I locked the phone, but the update still fails at the same location. The green bar expands for about 20 seconds, covering about a quarter of the bar, and the the red triangle appears.
You could always attempt to update the firmware/hboot manually download it here for your cid http://forum.xda-developers.com/showthread.php?t=1957376
Or there is a tool here http://forum.xda-developers.com/showthread.php?t=1924003
sorry for being a noob
gffmac said:
You could always attempt to update the firmware/hboot manually download it here for your cid http://forum.xda-developers.com/showthread.php?t=1957376
Or there is a tool here http://forum.xda-developers.com/showthread.php?t=1924003
Click to expand...
Click to collapse
the tool looks easy enough, but they ask to include the custom JB rom of my choice. I want the Stock update, so what do I do?
The manual update list points to a broken link. I did find it somewhere else. How do I manually update? are these the commands?
fastboot oem rebootRUU
fastboot flash zip firmware.zip
do I need to unlock my phone again? can I use the same Unlock_code.bin I got from HTC last time (saved it) or do I have to go through the process again?
I'm asking all these questions because I don't want to end up with a bricked phone.
mayashoval said:
the tool looks easy enough, but they ask to include the custom JB rom of my choice. I want the Stock update, so what do I do?
The manual update list points to a broken link. I did find it somewhere else. How do I manually update? are these the commands?
fastboot oem rebootRUU
fastboot flash zip firmware.zip
do I need to unlock my phone again? can I use the same Unlock_code.bin I got from HTC last time (saved it) or do I have to go through the process again?
I'm asking all these questions because I don't want to end up with a bricked phone.
Click to expand...
Click to collapse
There are a couple of really good stock looking ROMs on there with enhanced performance. There's one mentioned in my sig, it may also be the easiest route out of your issue using the tool posted above
exocetdj said:
There are a couple of really good stock looking ROMs on there with enhanced performance. There's one mentioned in my sig, it may also be the easiest route out of your issue using the tool posted above
Click to expand...
Click to collapse
Yes I am running to issues... turns out that manually flashing the firmware.zip just got my phone into a bootloop since it turns out you must install a custom rom after it. I did not want to install a custom rom just to get the OTA update to install. now my phone keeps rebooting and I'm waiting for ADHD to download (takes FOREVER! for some reason).
This really sucks. I wanted to stay with stock, and it looks like I can't even go back anymore, can't even restore with a RUU.
mayashoval said:
Yes I am running to issues... turns out that manually flashing the firmware.zip just got my phone into a bootloop since it turns out you must install a custom rom after it. I did not want to install a custom rom just to get the OTA update to install. now my phone keeps rebooting and I'm waiting for ADHD to download (takes FOREVER! for some reason).
This really sucks. I wanted to stay with stock, and it looks like I can't even go back anymore, can't even restore with a RUU.
Click to expand...
Click to collapse
There should be a RUU out for your region soonish but Until then, a stock style custom rom is a brilliant option beleive me
exocetdj said:
There should be a RUU out for your region soonish but Until then, a stock style custom rom is a brilliant option beleive me
Click to expand...
Click to collapse
don't really have a choice now...
downloading maXimus as per your recommendation (and because ADHD will take another 9 hours
You can restore an older backup, it's just like installing a custom ROM.
You might also be able to install a 2.17 RUU on 2.18, I'm not sure the hboot was updated. It's also possible to dissect an RUU and install the bits manually.
You have a few options.
i am having the same issue, I have the stock rom (never flashed) on a rooted phone. So i relocked the bootloader and flashed stock recovery, but im getting the red triangle when installing the update.
OP, did you already find a solution?
plaktoets said:
i am having the same issue, I have the stock rom (never flashed) on a rooted phone. So i relocked the bootloader and flashed stock recovery, but im getting the red triangle when installing the update.
OP, did you already find a solution?
Click to expand...
Click to collapse
Sorry did not find a solution. Ended up installing a custom rom, even though I wanted to keep using the stock one
plaktoets said:
i am having the same issue, I have the stock rom (never flashed) on a rooted phone. So i relocked the bootloader and flashed stock recovery, but im getting the red triangle when installing the update.
OP, did you already find a solution?
Click to expand...
Click to collapse
I hope you did this the other way around......first flash the recovery and the relock the bootloader.....
But if you are on stock rom, kernel and recovery you do not have to relock the bootloader, it updates fine with a unlocked one.
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
I originally had a stock sense M8 (bought it first day) but since October, I changed my phone to GPE (GPE Firmware and everything) and have been using 5.0 eversince using SkyDragon rom. Ran into issues a few weeks ago, and i've been waiting hard to go back to sense and use the newer 5.0 sense version.
However, today I ran into multiple issues, I thought installing the latest Sense Lollipop firmware and installing the latest ARHD 5.0 rom would do the trick, sadly that did not work.
I flashed the latest sense firmware and the ROM only for it to boot saying my Data is corrupt and i have to reset my phone, i say okay(was going to do that anyway) but then I access my recovery (TWRP) and my Internal storage/Cache/Data will not mount. I tried going back to GPE (atleast so my phone would work) but I cant do that either because even with the GPE firmware, the data partition wont mount and my internal storage shows 0 MB in TWRP, now im just stick in a bootloop/bricked device for hours. Any help would really be appreciated...thanks a lot.
Dev Edition RUU is what I would recommend. Partitioning is different on GPE versus Sense. So I'm guessing running the firmware only, since its not a complete image, did not change the partitioning back to the Sense partition scheme.
Converting from GPE back to Sense is not trivial, and not to be taken lightly. It seems like you tried to make up your own process instead of following any definitive guide or advice, which I do not recommend.
redpoint73 said:
Dev Edition RUU is what I would recommend. Partitioning is different on GPE versus Sense. So I'm guessing running the firmware only, since its not a complete image, did not change the partitioning back to the Sense partition scheme.
Converting from GPE back to Sense is not trivial, and not to be taken lightly. It seems like you tried to make up your own process instead of following any definitive guide or advice, which I do not recommend.
Click to expand...
Click to collapse
Thanks for your reply, to get this clear:
I should flash the Dev Edition RUU from (http://forum.xda-developers.com/htc-one-m8/development/ruu-m8-developer-edition-sense-1-54-t2884777) (3.28.1540.5) and then update the firmware to 4.16.1540.8 by just flashing that separate zip. However, if I flash the RUU wouldn't it relock my bootloader and put me on S-On and lose root and the custom recovery(Im terribly sorry if this sounds dumb, but my phone is soft bricked and I really need to get everything right this time), Is that the case if I flash the dev edition RUU? Thanks again.
Austin3161337 said:
However, if I flash the RUU wouldn't it relock my bootloader and put me on S-On and lose root and the custom recovery
Click to expand...
Click to collapse
No, RUU will not relock the bootloader. The only way the bootloader gets locked/unlocked is if you do so yourself.
Same with s-off, there is nothing that can change that aside from you making it s-on yourself.
Yes, you will lose custom recovery, as RUU will install stock recovery. So just flash stock recovery by fastboot after RUU. Then flash the ROM you want, which should already be rooted (so losing root is a moot point).
Official firmware.zip will also write stock recovery. So doing so would have caused the loss of TWRP anyway (unless it was a user modified firmware zip).
redpoint73 said:
No, RUU will not relock the bootloader. The only way the bootloader gets locked/unlocked is if you do so yourself.
Same with s-off, there is nothing that can change that aside from you making it s-on yourself.
Yes, you will lose custom recovery, as RUU will install stock recovery. So just flash stock recovery by fastboot after RUU. Then flash the ROM you want, which should already be rooted (so losing root is a moot point).
Official firmware.zip will also write stock recovery. So doing so would have caused the loss of TWRP anyway (unless it was a user modified firmware zip).
Click to expand...
Click to collapse
So I downloaded the RUU from (http://www.htc.com/us/support/htc-one-m8/news/) but its an .exe which requires me to plug my phone in which my computer cannot recognize because the phone won't boot at all, is there anyway I can install the RUU by not really needing to connect the phone to the computer? (Put the file in the external SD and install it via the bootloader maybe?) Any tips on that? Thanks
Austin3161337 said:
So I downloaded the RUU from (http://www.htc.com/us/support/htc-one-m8/news/) but its an .exe which requires me to plug my phone in which my computer cannot recognize because the phone won't boot at all
Click to expand...
Click to collapse
The phone doesn't need to boot into OS to run the RUU. It just needs to be able to get into bootloader/fastboot mode, which it can if the screen comes on.
If the device doesn't show on your PC, its a different issue. USB connectivity issue is almost always a driver issue. Install HTC Sync and HTC drivers, if you haven't already. Or uninstall and install them again.
I have a similiar issue. I had a tombile ruu.zip that a flashed as a 0P6Bimg.zip a kitkiat sense version for tmobile. Everything is cool and it runs fine. When I change cid and mid then flashed the sense lollipop firmware I lost my internal memory and twrp read storage as 0mb.
So idk
I flashed the Dev RUU as recommended by redpoint73, booted up and now it says that its updating to the latest firmware android 5.0 (OTA Update) However, I am going to install a custom recovery (TWRP) and put on ARHD instead, thanks for the help, and pretty much unbricking my device, lol.
Austin3161337 said:
I flashed the Dev RUU as recommended by redpoint73, booted up and now it says that its updating to the latest firmware android 5.0 (OTA Update) However, I am going to install a custom recovery (TWRP) and put on ARHD instead, thanks for the help, and pretty much unbricking my device, lol.
Click to expand...
Click to collapse
You're very welcome. Happy to help.
Did you have to do anything to get the RUU to run (like install drivers), or did you just end up running the RUU exe, and it worked?
redpoint73 said:
You're very welcome. Happy to help.
Did you have to do anything to get the RUU to run (like install drivers), or did you just end up running the RUU exe, and it worked?
Click to expand...
Click to collapse
I already had HTC Sync installed, had to boot into Fastboot USB for the thing to get recognized.
Hi guys i'll explaine what happened:
1. I was on nougat rom rooted trying to get back to stock.
2. I run an old lollipop ruu.exe from my computer but it reboots the phone to bootloader mode without going on.
3. I manually reboot to bootloader to see it if does move on but nothing.
4. I disconnect the phone.
Now there's no OS and recovery and flashing TWRP succeeds but when I try to reboot to recovery it say that's not possible.
I tried to flash via sdcard the OPJAIMG but it seems like it doesn't see it (screenshot in attachements).
I can access download mode
I'm S-OFF on Nougat firmware.. what can i do?
EDIT: I tried to live-boot TWRP but it stays forever on booting in cmd and flashing in phone
@Flippy498 maybe you have an idea? You have so much knowledge on this!
I haven't seen a 4.x RUU for the SKU 401, yet. You therefore would need to flash one of Sneakyghost's 3.x firmware packs before you're able to use a 3.x RUU, again. The encryption key changed between firmware 3.x and 4.x. Therefore you can't use 4.x RUUs on firmware 1.x to 3.x and vice versa.
In contrast to the flashing command the command for booting TWRP via fastboot needs to be used while the phone is booted to the bootloader instead of the download mode. However, since I haven't seen a publicly available TWRP backup for the latest 401 firmware, yet, TWRP won't help you much in your situation. (Or do you have your own backup?)
That means on the other hand that you currently need to downgrade to 3.35.401.12 and to re-install the OTAs for 3.35.401.32 and 4.14.401.7 since the latest RUU is for version 3.35.401.12.
Edit: Oh, and the only RUU.exe for SKU 401 that I know is for that 1.x firmware wird the 17 at the end. You shouldn't use that one. The corresponding OTA only got distributed for one single CID (I forgot which one it was). That means that you won't receive OTAs if you aren't using that specific CID on your phone. That means you would need to flash another RUU afterwards for getting away from that firmware version. And instead of flashing two RUUs you could save some time and directly flash the second one.
Sent from my HTC One M9 using XDA Labs
mrsmtt said:
Hi guys i'll explaine what happened:
1. I was on nougat rom rooted trying to get back to stock.
2. I run an old lollipop ruu.exe from my computer but it reboots the phone to bootloader mode without going on.
3. I manually reboot to bootloader to see it if does move on but nothing.
4. I disconnect the phone.
Now there's no OS and recovery and flashing TWRP succeeds but when I try to reboot to recovery it say that's not possible.
I tried to flash via sdcard the OPJAIMG but it seems like it doesn't see it (screenshot in attachements).
I can access download mode
I'm S-OFF on Nougat firmware.. what can i do?
EDIT: I tried to live-boot TWRP but it stays forever on booting in cmd and flashing in phone
Click to expand...
Click to collapse
1 - Try 0(zero)PJAIMG and not O
2 - Restore to stock recovery
3 - Start phone in download mode and push volume UP
benshoes said:
1 - Try 0(zero)PJAIMG and not O
Click to expand...
Click to collapse
Oh, I missed that typo.
benshoes said:
2 - Restore to stock recovery
Click to expand...
Click to collapse
That's actually not needed. The RUU will flash the stock recovery by its own. You only need a working download mode.
Flippy498 said:
Oh, I missed that typo.
That's actually not needed. The RUU will flash the stock recovery by its own. You only need a working download mode.
Click to expand...
Click to collapse
Tried to live-boot TWRP from bootloader since I have my own backup but it fails with the following message:
FAILED (remote: dtb not found)
About 0PJAIMG it is named correctly in SD it's just me that made a mistake writing here.
So last chance for me is to head to Sneakyghost's thread and flash the 3.35.401.32 fullstock firmware then head to your google sheet and pick the 3.35.401.12 RUU and flash it right?
mrsmtt said:
Tried to live-boot TWRP from bootloader since I have my own backup but it fails with the following message:
FAILED (remote: dtb not found)
About 0PJAIMG it is named correctly in SD it's just me that made a mistake writing here.
So last chance for me is to head to Sneakyghost's thread and flash the 3.35.401.32 fullstock firmware then head to your google sheet and pick the 3.35.401.12 RUU and flash it right?
Click to expand...
Click to collapse
Correct. Although you can use the 3.35.401.12 firmware pack, as well. It doesn't matter which one of the two firmware versions you choose.
Flippy498 said:
Correct. Although you can use the 3.35.401.12 firmware pack, as well. It doesn't matter which one of the two firmware versions you choose.
Click to expand...
Click to collapse
Thanks for your support! Anyway i'm going to do the whole thing tomorrow.. I was reading the instructions on Sneakyghost's thread and he recommend to use his tool because it contains the htc_fastboot that works better than google's one but I don't see any option to lunch the flash zip firmware command from the tool so I decided to get the htc_fastboot.exe file and move it inside another folder (a new one) in wich i'll put both firmware and rom zip to flash. I'm saying this because i'm not 100% sure this is correct so just to clear all doubts..
Once again @Flippy498 you saved me and I say thank you a million times I promise i'll take a break at trying to destroy my m9 so you'll definitely not hear me / see me here anymore hehe
Hi guys,
I've updated my M9 to 7.0 through OTA update. After installing my phone boots directly in to the bootloader. I can enter download and recovery mode without any trouble but that's about it. When i try to boot in to the phone it boots back to the bootloader. My phone is S-ON so i can't flash a RUU through ADB, however the phone is unlocked.
I tried to flash a RUU through the external micro SD card method but that failed because the firmware is lower than my firmware.
Current M9 Status:
*Unlocked*
S-On
Firmware 4.14.401.7
Stuck in bootloader/recovery/downloadmode
I tried everything to my knowledge. Is there someone who encountered the same problems as i do? Or is there someone who knows a solution to all of this?
ruubs said:
Hi guys,
I've updated my M9 to 7.0 through OTA update. After installing my phone boots directly in to the bootloader. I can enter download and recovery mode without any trouble but that's about it. When i try to boot in to the phone it boots back to the bootloader. My phone is S-ON so i can't flash a RUU through ADB, however the phone is unlocked.
I tried to flash a RUU through the external micro SD card method but that failed because the firmware is lower than my firmware.
Current M9 Status:
*Unlocked*
S-On
Firmware 4.14.401.7
Stuck in bootloader/recovery/downloadmode
I tried everything to my knowledge. Is there someone who encountered the same problems as i do? Or is there someone who knows a solution to all of this?
Click to expand...
Click to collapse
Some questions:
Did you have a completely stock device when you applied the OTA?
Did it ever successfully boot into Nougat, or did the OTA immediately result in the current condition?
I wonder if you could either flash TWRP or use it via your computer (there's a way to run it in your phone without installing it) so that you could apply the OTA again. I'm not sure if it would fix whatever went wrong, though.
Alternatively, you could flash a ROM (again, via TWRP), obtain S-OFF, change your MID & CID to the developer version and apply that RUU.
computerslayer said:
Some questions:
Did you have a completely stock device when you applied the OTA?
Did it ever successfully boot into Nougat, or did the OTA immediately result in the current condition?
I wonder if you could either flash TWRP or use it via your computer (there's a way to run it in your phone without installing it) so that you could apply the OTA again. I'm not sure if it would fix whatever went wrong, though.
Alternatively, you could flash a ROM (again, via TWRP), obtain S-OFF, change your MID & CID to the developer version and apply that RUU.
Click to expand...
Click to collapse
I did have a completely stock device before i installed the OTA.
It did never successvully booted into nougat. Right after the install it booted in to the bootloader.
How can i flash TWRP or another ROM while im S-ON? Or am i wrong in this? Please help me out
ruubs said:
I did have a completely stock device before i installed the OTA.
It did never successvully booted into nougat. Right after the install it booted in to the bootloader.
How can i flash TWRP or another ROM while im S-ON? Or am i wrong in this? Please help me out
Click to expand...
Click to collapse
S-ON is no obstacle to flashing TWRP or another ROM. You will need to unlock your bootloader in order to do either but I assumed that you had already done this since you posted that your status is unlocked.
computerslayer said:
S-ON is no obstacle to flashing TWRP or another ROM. You will need to unlock your bootloader in order to do either but I assumed that you had already done this since you posted that your status is unlocked.
Click to expand...
Click to collapse
The phone status is indeed unlocked.
I didn't know I could flash TWRP or a ROM. I thought I needed S-OFF for that.
I want my phone to be as stock as possible. Can I flash a stock ROM or does it have to be a custom one.
And do i need to flash TWRP in order to flash a ROM?
So i've searched around and came to the conclusion to fix my phone is to flash TWRP first. After that FLASH a custom ROM, if that goes as planned S-OFF my phone with the SunShine method. After that go back to stock and hope everything goes well.
ruubs said:
So i've searched around and came to the conclusion to fix my phone is to flash TWRP first. After that FLASH a custom ROM, if that goes as planned S-OFF my phone with the SunShine method. After that go back to stock and hope everything goes well.
Click to expand...
Click to collapse
That's the route I would take too. The readme thread has a section dedicated to changing your SKU in order to use other RUUs.