Related
i dont know exactly whats happened here, but i've tried to get my WFS sorted with a different rom than the carriers bloated version.
what i've done is updated hboot to 1.08.0099 and unlocked the boot loader sucessfully (hboot has *** UNLOCKED *** across the top; i used the HTCDEV.com process).
i believe i've got permanent root too.
when i attempt to flash CWM (via PG76IMG.zip), it appears to flash ok, but if i reboot the phone and try to access recovery, it just gets stuck on a white HTC screen.
i've redownloaded the CWM file to see if it's a corrupt download, but still the same problem.
CWM isnt a big issue, although it is nice to have.
however i also am unable to flash another rom either via the PG76IMG.zip SD method, or RUU.
i beleive i've done everything right, and i'm not entirely new to unlocking/rooting devices; only did my HTC Desire last week so the general process is still new in my head.
If your rooted install rom manager and flash recovery from there.
I had problems installing cwm from sd, so used the tool from here http://forum.xda-developers.com/showthread.php?t=1431969
previously was this one mediafire.com/?b0bsb4ms4lo714b
just plug the usb in sync and folow the instructions
Hey guys,
fairly new to this all and it seems I have messed up at some point...
I managed to root my phone and i do have TWRP on it and wanted to install a rom (blade elite 1.1). went into bootloader and flashed the boot.img with the tool, then went into recovery, cleared all the caches/factory reset/system and flashed the rom which i had previously copied onto my sd card. then i pressed reboot. It didnt start up for a few minutes so i kind of panicked and went into recovery again. I had made a backup previously, which I then restored. But it's still stuck on the screen where it sais htc one on the white screen with the beats audio thing on the bottom... Waited for around 20 mins. I can still get into recovery, so I'm hoping not all hope is lost.
What do I do now? :/ Do I have to flash the stock kernel or something first before I can restore with twrp?
Please help :/ I kinda really need my phone...
Oh yeah I forgot one thing. The tool said "error: device not found" in the first cmd window when I flashed the kerel, but when I clicked it away a second one popped up and it said it flashed correctly. It did the same thing when I flashed twrp and thats definitely on my phone, so Im guessing it has flashed the kernel correctly. Just thought I'd mention that.
fastboot getvar version-main
gave me:
2.17.401.2
aaaalright.
I installed fastboot, found the correct ruu for my device, relocked the bootloader and installed the ruu and my phone is now up and running again! and i feel like a genius :S
however! something went wrong and I would like to know where my mistake was. i still want that custom rom!
since i installed the ruu, that means everything is gone again right? no unlocked bootloader, no root, no twrp? so ill just use the tool again to get that back?
quick question for that. will i need a new token id and register again, or can i use the old one?
its 5:30am here and i'll need to get some sleep now... maybe i can get it tomorrow. still appreciating any help !
Your hboot is to low, you need to update. Since you used the ruu, go into settings - about menu and update the phone with the software update utility.
You are still on ICS and need to update to JB.
You can also update your Hboot yourself by check your cid number using this app
https://play.google.com/store/apps/...sMSwxLDEsIm9yZy50cml0b25zb2Z0LmNpZGdldHRlciJd
Finding the Hboot to match your cid number here
http://forum.xda-developers.com/showthread.php?t=1957376
And upgrade your Hboot manually or by using a tool like this one here (you'll need to put the correct Hboot in the relevent folder of the app first!)
http://forum.xda-developers.com/showthread.php?t=1924003
Read through the full guide and comments first before proceeding!
Hope this helps.
Easiest is to update with the official ota now as he already installed the ruu
And yes you can use the old unlock code again
StreamOfLife said:
aaaalright.
I installed fastboot, found the correct ruu for my device, relocked the bootloader and installed the ruu and my phone is now up and running again! and i feel like a genius :S
however! something went wrong and I would like to know where my mistake was. i still want that custom rom!
since i installed the ruu, that means everything is gone again right? no unlocked bootloader, no root, no twrp? so ill just use the tool again to get that back?
quick question for that. will i need a new token id and register again, or can i use the old one?
its 5:30am here and i'll need to get some sleep now... maybe i can get it tomorrow. still appreciating any help !
Click to expand...
Click to collapse
You can use the original Token they sent you. No need to go through the whole HTCDev process again :good:
You guuuuuys, it worked !!
Thanks a bunch! Was totally easy with the ota update too, very smart!
Good ! Enjoy
CASE CLOSED !
Hi, I've got a Desire HD phone which I got unlocked and unbranded from the start and it came with some version of Froyo out of the box. Since then I've updated it through via wifi and currently it's on GB 2.3.5 and after the last update the phone has been telling me that it has no updates available. Furthermore, I have never flashed or rooted this phone so it's still a virgin
Further information on my phone is as follows:
Android Version: 2.3.5
HTC Sense Version: 3.0
Software Number: 3.13.707.4
AND some pics of the specs are in the attachment, please check them out.
Now due to some performance issues I wanted to reinstall either 2.3.5 or lower version of gingerbread or if possible the latest version of Froyo available for my phone. I have already tried restarting, taking out the battery, doing factory reset, wiping the phone and sdcard both from within the phone settings and from the HBoot and Recovery menu as well to no avail.
So I would like to ask you guys for steps and possible links to correct RUU for re-flashing the stock version of unbranded 2.3.5 or lower version of gingerbread or if possible the latest version of Froyo. I don't want to mess with the phone too much by going into the rooting and installing custom ROMS just yet, but that would be my last resort if all else fails.
I'm a newbie so please be gentle in replies
Thanks in advance!
STOP STOP STOP DONT DO ANYTHING!
don't flash any froyo ruu or wwe this will mess your hboot and you'll be in a whole world of hurt.
If you've done a factory reset you shouldn't be having performance issues as that takes you back to factory condition of course.
How ever
Your first course of action now should be goto market and get emmc checker and see if you have the bad chips (sain I think).
If you dont have issue I suggest you do HTCDEV unlock and root your phone or flash a new rom, ive only used SVHD which is ics sense rom which is pretty damn awesome, but im moved on to samsung galaxy s4 (unrooted) now so haven't used newest version yet.
Have a look around the dev forum there are a few really good guides .
Sent from my GT-I9505 using xda app-developers app
I recommend getting s-off and unlocking the HBoot to get the best performance from your phone. I must say that this is not for the faint-of-heart and things sometimes can and do go wrong .
I bought a second hand Desire HD running stock Telus GB for very little money so I didn't have much to lose if I pooched the phone. If you do decide to unlock the HBoot, make sure you upgrade to 2.00.0029 first.
What performance issues were you having?
ranger4740 said:
STOP STOP STOP DONT DO ANYTHING!
don't flash any froyo ruu or wwe this will mess your hboot and you'll be in a whole world of hurt.
If you've done a factory reset you shouldn't be having performance issues as that takes you back to factory condition of course.
How ever
Your first course of action now should be goto market and get emmc checker and see if you have the bad chips (sain I think).
If you dont have issue I suggest you do HTCDEV unlock and root your phone or flash a new rom, ive only used SVHD which is ics sense rom which is pretty damn awesome, but im moved on to samsung galaxy s4 (unrooted) now so haven't used newest version yet.
Have a look around the dev forum there are a few really good guides .
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Ran that app and it says " Brick Bug? NO. Sane Chip "
So I'm guessing my phone is good, right?
I've been having some major bugs popping up on my phone ever since I upgraded to the 2.3.5 update. My phone camera gets stuck while taking pictures, at times it has restarted my phone when I take a picture, the GPS/Location keeps popping up at every boot and I can't seem to disable it, the Connect To Computer message which used to let me select in which mode I want to connect my phone to the PC has stopped showing up and the phone only connects in charging mode to the PC, the speaker phone keeps turning itself on whenever I make a call or receive a call. I've read up on all these bugs on many forums and tried all the solutions to no avail, I have already done factory resets, battery pulls, cleaning of the usb connector, tried different usb cables on different computers, formatted the memory card etc, but none of these things worked for me.
So I'm left with one choice only, that is to erase everything on this phone and flash a fresh ROM onto it to see if it fixes the issue. And just to be on the safe side I want to install anything lower than 2.3.5 since that's when all these bugs popped up one by one for me. And I don't want to root my phone just yet or unlock it or do any experiments with it yet.
So my question is, how do I backup my current ROM in case if anything goes wrong I could revert back to this one and then how do I flash an official earlier version of GB compatible with my phone and where to get this ROM. Since my phone came unbranded and unlocked, I'm assuming the WWE versions would work well for me right? I once saw in my phone somewhere that it told me I have htc_asia_WWE version on my phone, if that helps. But I would rather get an English only version which has no other language settings in it, like chinese, vietnemese etc etc which my phone currently has.
Thanks in advance!
vxdesigns said:
Ran that app and it says " Brick Bug? NO. Sane Chip "
So I'm guessing my phone is good, right?
I've been having some major bugs popping up on my phone ever since I upgraded to the 2.3.5 update. My phone camera gets stuck while taking pictures, at times it has restarted my phone when I take a picture, the GPS/Location keeps popping up at every boot and I can't seem to disable it, the Connect To Computer message which used to let me select in which mode I want to connect my phone to the PC has stopped showing up and the phone only connects in charging mode to the PC, the speaker phone keeps turning itself on whenever I make a call or receive a call. I've read up on all these bugs on many forums and tried all the solutions to no avail, I have already done factory resets, battery pulls, cleaning of the usb connector, tried different usb cables on different computers, formatted the memory card etc, but none of these things worked for me.
So I'm left with one choice only, that is to erase everything on this phone and flash a fresh ROM onto it to see if it fixes the issue. And just to be on the safe side I want to install anything lower than 2.3.5 since that's when all these bugs popped up one by one for me. And I don't want to root my phone just yet or unlock it or do any experiments with it yet.
So my question is, how do I backup my current ROM in case if anything goes wrong I could revert back to this one and then how do I flash an official earlier version of GB compatible with my phone and where to get this ROM. Since my phone came unbranded and unlocked, I'm assuming the WWE versions would work well for me right? I once saw in my phone somewhere that it told me I have htc_asia_WWE version on my phone, if that helps. But I would rather get an English only version which has no other language settings in it, like chinese, vietnemese etc etc which my phone currently has.
Thanks in advance!
Click to expand...
Click to collapse
No actually read what EMMC chip you have, that app is made for samsung phones and will only check for those.Type out the one you have
audit13 said:
I recommend getting s-off and unlocking the HBoot to get the best performance from your phone. I must say that this is not for the faint-of-heart and things sometimes can and do go wrong .
I bought a second hand Desire HD running stock Telus GB for very little money so I didn't have much to lose if I pooched the phone. If you do decide to unlock the HBoot, make sure you upgrade to 2.00.0029 first.
What performance issues were you having?
Click to expand...
Click to collapse
If I want to flash the stock ROM, do I still need to do s-off and unlock the HBoot or are these only necessary to flash custom ROMS???
Steam. said:
No actually read what EMMC chip you have, that app is made for samsung phones and will only check for those.Type out the one you have
Click to expand...
Click to collapse
Not sure what you are saying ...
The eMMC app shows this info:
Phone Model
HTC htc_ace
eMMC chip
Type: SEM04G
Brick Bug?
NO. Sane chip
vxdesigns said:
Not sure what you are saying ...
The eMMC app shows this info:
Phone Model
HTC htc_ace
eMMC chip
Type: SEM04G
Brick Bug?
NO. Sane chip
Click to expand...
Click to collapse
I guess you could run the RUU but since you think its wwe_asia it will be tricky to get a proper link for your RUU.I'd suggest unlocking the BL and if you're only after the stock ROM, flash Android Revolution HD 6.6, it's stock.First you need to upgrade the HBOOT though, you need .0029 for the unlocking process.You unlock the BL via HTC's site afterwards.
http://forum.xda-developers.com/showpost.php?p=38947050&postcount=10
Download HBOOT Update Kit and rom.zip from attachments there.Put the rom.zip exactly in C, and the update kit doesn't really matter, aslong as it's in a folder.Make sure you have your drivers installed, found here , install them.Run the hboot update.bat, but turn on usb debugging first.
Steam. said:
I guess you could run the RUU but since you think its wwe_asia it will be tricky to get a proper link for your RUU.I'd suggest unlocking the BL and if you're only after the stock ROM, flash Android Revolution HD 6.6, it's stock.First you need to upgrade the HBOOT though, you need .0029 for the unlocking process.You unlock the BL via HTC's site afterwards.
http://forum.xda-developers.com/showpost.php?p=38947050&postcount=10
Download HBOOT Update Kit and rom.zip from attachments there.Put the rom.zip exactly in C, and the update kit doesn't really matter, aslong as it's in a folder.Make sure you have your drivers installed, found here , install them.Run the hboot update.bat, but turn on usb debugging first.
Click to expand...
Click to collapse
I did get a RUU which meets my specs exactly, or so I think:
http://www.shipped-roms.com/downloa...60.29_26.14.04.28_M_release_234022_signed.exe
I ran it, updated my phone, it's the same version which is already on my phone, it completed without any issues, but the bugs are still there. So I'm assuming it didn't really reinstall the software from scratch, it just updated the software without making much changes to it, pretty much like a factory reset, right???
Can you please tell me why we need to unlock the HBoot??? Is it to enable us to flash custom roms???
What I want to do is erase the 2.3.5 GB software completely from my phone so it has no trace of it, then install stock/untouched 2.3.3 GB or any other GB version compatible with my phone. So please provide steps and insight into this process.
Thanks
Steam. said:
I guess you could run the RUU but since you think its wwe_asia it will be tricky to get a proper link for your RUU.I'd suggest unlocking the BL and if you're only after the stock ROM, flash Android Revolution HD 6.6, it's stock.First you need to upgrade the HBOOT though, you need .0029 for the unlocking process.You unlock the BL via HTC's site afterwards.
http://forum.xda-developers.com/showpost.php?p=38947050&postcount=10
Download HBOOT Update Kit and rom.zip from attachments there.Put the rom.zip exactly in C, and the update kit doesn't really matter, aslong as it's in a folder.Make sure you have your drivers installed, found here , install them.Run the hboot update.bat, but turn on usb debugging first.
Click to expand...
Click to collapse
Updated and unlocked my Hboot and now it's on 29 with S-Off.
I flashed CWM recovery, installed SuperUser and flashed the latest version of SVHD and rebooted but phone won't start, after the HTC logo with a white background, the screen goes black as if the ROM can't boot.
Could this be a SuperUser issue or a S-Off issue? I'm not sure if SVHD requires S-On to function properly and it's nowhere mentioned on the thread either.
Advice required :crying:
vxdesigns said:
Updated and unlocked my Hboot and now it's on 29 with S-Off.
I flashed CWM recovery, installed SuperUser and flashed the latest version of SVHD and rebooted but phone won't start, after the HTC logo with a white background, the screen goes black as if the ROM can't boot.
Could this be a SuperUser issue or a S-Off issue? I'm not sure if SVHD requires S-On to function properly and it's nowhere mentioned on the thread either.
Advice required :crying:
Click to expand...
Click to collapse
Never mind your actually s-off...
Did you do full wipe before flash?
Apparently you really should be using 4ext recovery on dhd as clockwork doesnt quite do the job right?.
Sent from my GT-I9505 using xda app-developers app
vxdesigns said:
Updated and unlocked my Hboot and now it's on 29 with S-Off.
I flashed CWM recovery, installed SuperUser and flashed the latest version of SVHD and rebooted but phone won't start, after the HTC logo with a white background, the screen goes black as if the ROM can't boot.
Could this be a SuperUser issue or a S-Off issue? I'm not sure if SVHD requires S-On to function properly and it's nowhere mentioned on the thread either.
Advice required :crying:
Click to expand...
Click to collapse
Choose full wipe in aroma installer. i recommend you to used SVHD 1.70 then upgrade OTA 1.73. does not flash version 1.74. this got so much error.
vxdesigns said:
Updated and unlocked my Hboot and now it's on 29 with S-Off.
I flashed CWM recovery, installed SuperUser and flashed the latest version of SVHD and rebooted but phone won't start, after the HTC logo with a white background, the screen goes black as if the ROM can't boot.
Could this be a SuperUser issue or a S-Off issue? I'm not sure if SVHD requires S-On to function properly and it's nowhere mentioned on the thread either.
Advice required :crying:
Click to expand...
Click to collapse
Flash 4ext, wipe everything and reflash 1.7.0, and then update to 1.7.3.CWM never wiped my partitions properly, it blows compared to 4ext.
Hi,
I recently managed to root my HTC One M8s with TWRP recovery and everything works perfectly, except that I can't install the new OTA (1.16.401.1).
After searching I have flashed my recovery back to the stock for my version (which is 1.11.401.1) and tried applying the OTA again, but it still fails.
I downloaded the recovery from this website: ruu.lalleman.net/HTC_M8S%28QL_UL%29/Recovery/HTC%20Recovery/ (I can't post URLs yet).
Below is the error I receive when trying to update on stock recovery, TWRP recovery also gave the same error when I tried updating there.
(Code -1)
E:Find no match PARTITION: for package path @/cache/recover/block.map
Finding update package...
Opening update package...
Verifying update package...
Installing update...
L50QCT.01.105.019
Verifying current sytem...
Package expects build fingerprint of htc/m8qlul_htc_europe/htc_m8qlul:5.0.2/LRX22G/531284.2:user/release-keys or htc/m8qlul_htc_europe/htc_m8qlul:5.0.2/LRX22G/555949.10:user/release-keys;
This device has htc/m8qlul_htc_europe/htc_m8qlul:5.0.2/LRX22G/53128
E:Error in @/cache/recovery/block.map
(Status 7)
From what I can see my build fingerprint is incorrect, but I have no idea how to fix it...
Seems to me it's likely that you've altered some system files while rooted and the Ota doesn't like it.
Now, I don't own an M8s...i have an M8, but I'd say the easiest route would be to flash your stock ruu again. After that the OTA should work.
It's that or figure out what system changes have been made and correct it. Xposed can mess you up, Uninstalled system apps can stop the Ota... MODS that changed system files... Etc. The Ota us looking for a stock system, then it updates it.
Good luck!
Thanks for the answer, I will see if I can try this solution tomorrow. I just have 2 questions:
What does the RUU do exactly? Should I see it as a complete stock reset of my phone?
And can I simply flash it using fastboot or is there a special method for a RUU?
My previous phone had an automated root and I always updated with OTA afterwards so I never flashed before now.
Im on the same boat. Tried to sim unlock by rooting and playing with CID but didnt work, now ive a rooted m8s and no ota. Tried to ruu but kept getting an error something like not enough space although i had 10gb free, cleared cache rebooted. Cant even factory reset. If anyone know how to unroot it and bring it back to stock that would be fantastic. Kind of want to delete the "flag" too make it "LOCKED" and "OFFICIAL" incase for warranty. Any ideas?
You guys have flashed 1.16 before, haven't you...?
See here: http://forum.xda-developers.com/htc-one-m8/help/help-thread-htc-one-m8s-to-stock-howto-t3190238
Err, oops, posted too soon. You said you have flashed to 1.11. What is the full filename of the RUU you flashed?
voidzero said:
You guys have flashed 1.16 before, haven't you...?
See here: http://forum.xda-developers.com/htc-one-m8/help/help-thread-htc-one-m8s-to-stock-howto-t3190238
Err, oops, posted too soon. You said you have flashed to 1.11. What is the full filename of the RUU you flashed?
Click to expand...
Click to collapse
When I got my phone I updated with OTA to version 1.11, after that I flashed TWRP recovery and rooted my phone. Now that OTA 1.16 is out I tried to update but couldn't, so I tried to flash back to stock recovery but it still wouldn't work because of the error above. Now it would seem that I am doing this the wrong way, and you cannot use OTA on a rooted/unlocked/custom recovery M8s.
Manual OTA flash worked on my previous phone with root which was an ASUS Padfone Infinity A80 as ASUS would release them on their own website for you.
Apparently HTC does not do this, or I am not looking in the right place.
I have never flashed a RUU before, and I don't know how to lock my bootloader again. From what I understand, every time there is a new OTA I will have to lock my bootloader, flash original recovery, flash RUU and then update. That sounds like a lot of trouble every time a new OTA comes out.
Is there no way to manually flash the new OTA without losing root, custom recovery and locking the bootloader? Will I have to follow these steps every time? Also I use the built in back-up to Google as well as HTC back-up but I don't know if all my data is in those back-ups or if I will lose something.
Codyksp said:
(...) so I tried to flash back to stock recovery but it still wouldn't work because of the error above. Now it would seem that I am doing this the wrong way, and you cannot use OTA on a rooted/unlocked/custom recovery M8s.
(..)
I have never flashed a RUU before, and I don't know how to lock my bootloader again. From what I understand, every time there is a new OTA I will have to lock my bootloader, flash custom recovery, flash RUU and then update. That sounds like a lot of trouble every time a new OTA comes out.
(...)
Is there no way to manually flash the new OTA without losing root, custom recovery and locking the bootloader? Will I have to follow these steps every time? Also I use the built in back-up to Google as well as HTC back-up but I don't know if all my data is in those back-ups or if I will lose something.
Click to expand...
Click to collapse
If you restore a RUU, and afterwards don't flash your recovery and boot partitions, You will see "Software status: official" in fastboot.
Now here's the trick: if you just boot a custom recovery with "fastboot boot my_recovery.img" (TWRP for example) then it will boot TWRP, but you can make the modifications to your system partition without losing "Software status: official" in fastboot.
So: If you just boot your recovery with 'fastboot boot' and don't flash anything, you can make all the modifications you want and still be able to install OTAs later, I think. I've rooted my phone, even installed XPosed, done all kinds of funky things to it but Fastboot still shows me that I'm on official software.
How does that sound?
So since there is no decent guide at all about flashing RUU for a HTC One M8s (the s makes a difference!). I have assumed that I need to have the bootloader locked first, as I unlocked it. According to all the M8 guides I have to gain S-OFF before I can lock the bootloader again. So I followed a guide to wipe with TWRP and flash a ROM called InsertCoin so that I can S-OFF my phone.
Now after going through the ROM's setup my phone is stuck in a bootloop, constantly trying to boot up. There is NO way at all for me to get it to stop, it just keeps booting the entire time. Not a single combination of buttons is working. Good thing the battery is non removable. How am I supposed to fix this? I've tried every volume up/down/power combination possible. The phone just boots to the HTC - Power by Android screen, shuts off after about 5 seconds and then repeats the same thing over and over. I can't turn it off and I can't get to the bootloader either.
What I need is a guide that tells me all the steps required to get an HTC One M8s (NOT M8!) back to 100% stock. This means, stock ROM, stock recovery, locked bootloader and S-ON. I am getting extremely frustrated by the lack of information and the amount of redicilous things I need to do just so I can root my phone and have OTA as well.
All I want is root on my phone for 1 app that I use with my car radio and I want to be able to update to the newest OTA afterwards, is that really so much to ask?
I am fine with installing a custom ROM with root and easy updates too, as long as the damn phone will boot after installing it and it's actually made for the M8s.
Deleted......
Well I finally managed to get the damn thing to the bootloader, and I've used "fastboot oem lock" to relock my bootloader. It now shows ***Software status: Modified ***, *** RELOCKED *** and ***Security Warning ***.
I will now have to go to my parents where my laptop is to be able to copy the RUU to my SD card, from what I understand it has to be named 0PKVIMG.zip and then it should automatically install.
Now the phone says it can't find the image or the image is incorrect.... It searches for, 0PKVDIAG.zip, 0PKVDIAG.nbh, 0PKVIMG.zip or 0PKVIMG.img. and it seems to find 0PKVIMG.zip and loads it but it cannot find the .img file and does absolutely nothing. Am I supposed to have both?
So it turns out that the RUU zip from http://ruu.lalleman.net/HTC_M8S%28QL_UL%29/RUU/ is actually not correct and I had to use rom.zip which was inside the folder. The phone is now running the "update" as it calls it. Fingers crossed...
Yes, possible you need to use rom.zip inside the zip, depending on the version, but I think this applies to 1.16 which I advice against using for reasons previously specified.
---------- Post added at 07:47 PM ---------- Previous post was at 07:47 PM ----------
By the way, I did write an RUU restoration thread specifically for this subject. Did you not find it?
Apparently I also needed to use the rom.zip for the 1.11 version, in the meantime I have also updated with OTA to 1.16. Afterwards I also unlocked my bootloader, restored my settings and installed SuperSU by booting TWRP. Let's hope the next OTA still works...
I did read your thread but I got stuck at first on relocking the bootloader, as I couldn't find the exact instructions for a while. Afterwards I got stuck on flashing the RUU because I didn't know that I needed to use the rom.zip file to get it to work.
After all that I got quite frustrated and I just wished there was 1 thread with instructions for everything (unlocking, relocking, flashing, compatible ROMs, booting to keep OTA, etc.) which is why I was angry at the time and couldn't properly read everything or find solutions. In the end it all worked out so far though.
I would ask you to create a compilation thread though if you wanted to improve the available information. Either way, thanks for the information that you've already provided.
Codyksp said:
Apparently I also needed to use the rom.zip for the 1.11 version, in the meantime I have also updated with OTA to 1.16. Afterwards I also unlocked my bootloader, restored my settings and installed SuperSU by booting TWRP. Let's hope the next OTA still works...
I did read your thread but I got stuck at first on relocking the bootloader, as I couldn't find the exact instructions for a while. Afterwards I got stuck on flashing the RUU because I didn't know that I needed to use the rom.zip file to get it to work.
After all that I got quite frustrated and I just wished there was 1 thread with instructions for everything (unlocking, relocking, flashing, compatible ROMs, booting to keep OTA, etc.) which is why I was angry at the time and couldn't properly read everything or find solutions. In the end it all worked out so far though.
I would ask you to create a compilation thread though if you wanted to improve the available information. Either way, thanks for the information that you've already provided.
Click to expand...
Click to collapse
The next ota won't work because you rooted it. Root changes binaries which lead to a fail on ota.
You need a non rooted (read : never rooted before) stock rom.
Mr Hofs said:
The next ota won't work because you rooted it. Root changes binaries which lead to a fail on ota.
You need a non rooted (read : never rooted before) stock rom.
Click to expand...
Click to collapse
So in that case I just unroot it before updating then?
Codyksp said:
So in that case I just unroot it before updating then?
Click to expand...
Click to collapse
Read my post again...... "a never rooted rom" so that means you need a stock rom before its ever been rooted. NOT an unrooted one because it leaves traces which will cause the ota to fail !
People should learn to create a nandroid backup before flashing ANY mods/superuser.zip/roms etc......etc
Well developers shouldn't make this such a hassle... My previous phone was an ASUS Padfone Infinity (A80) and it didn't receive any OTAs after being rooted but ASUS simple lets you download the firmware updates on their website and then you can manually update it without any problems. If HTC provides a bootloader unlock, why can't they allow OTA or at least provide manual firmware updates?
I wouldn't mind using a custom ROM either but I have no idea which ROMs work for the HTC One M8s. Would any M8 ROM be compatible? The phones aren't identical, the "s" is there for a reason...
Codyksp said:
Well developers shouldn't make this such a hassle... My previous phone was an ASUS Padfone Infinity (A80) and it didn't receive any OTAs after being rooted but ASUS simple lets you download the firmware updates on their website and then you can manually update it without any problems. If HTC provides a bootloader unlock, why can't they allow OTA or at least provide manual firmware updates?
I wouldn't mind using a custom ROM either but I have no idea which ROMs work for the HTC One M8s. Would any M8 ROM be compatible? The phones aren't identical, the "s" is there for a reason...
Click to expand...
Click to collapse
I would say that M8 roms wouldn't be compatible, and could even mess up your device badly. Sorry!
Codyksp said:
Well developers shouldn't make this such a hassle... My previous phone was an ASUS Padfone Infinity (A80) and it didn't receive any OTAs after being rooted but ASUS simple lets you download the firmware updates on their website and then you can manually update it without any problems. If HTC provides a bootloader unlock, why can't they allow OTA or at least provide manual firmware updates?
I wouldn't mind using a custom ROM either but I have no idea which ROMs work for the HTC One M8s. Would any M8 ROM be compatible? The phones aren't identical, the "s" is there for a reason...
Click to expand...
Click to collapse
Your point of view is a bit off if you ask me. Developers (in this case HTC) do not have to support custom modding of your phone. They support the device in the state you buy it !
If you want to mod it that's YOUR call not theirs. Do some homework before modding it. Getting a phone back to stock for future updates is relatively easy but many people don't read first how to as they think it's not important.
HTC has no obligation at all towards you regarding custom software !
And indeed M8 roms do NOT work on your M8s !
So roughly two years ago I decided to root my phone. I flashed TWRP, got S-OFF, and root. Well somebody hacked my phone and I freaked out. They were remotely downloading and inventorying all my devices' files, serial numbers, hardware info, accessing my camera, I mean everything, it was truly frightening the level of which whomever was doing this was able to to do it. I freaked out, went into TWRP, and started deleting everything that looked suspicious. I deleted my OS and probably a bunch of other things I shouldn't have on accident through TWRP. My device still has TWRP recovery functioning. I tried using ADB on my Windows 10 PC but I have no idea what I'm doing. I kept getting errors to the effect of "wrong version" etc. Being unable to use ADB I resorted to copying Viper OS to a flash card and I used TWRP to install it from flash. Once installed it "ran" but my Wifi radio did not work at all. When I tried to enable it in settings it stayed grey. Figuring I screwed up royally again, I decided to copy and paste a folder I created in 2014 with a TWRP recovery. It had the OS, cache, etc backed up. After using TWRP recovery it said I had no OS again. I'm freaking out, my phone is trashed, and I don't want to do anything else without a babysitter. I just want my original phone back, no custom roms, nothing. I don't want to turn S-ON because I know there is a possibility of bricking and quite frankly, I'm an idiot. Somebody just please walk me through what I need to do to get a fully functioning OS back on my phone. SD card methods preferred, as I can't get ADB to work or I'm too stupid to use it. I saw something mentioned that the firmware may need updating and that may have been the cause for the WiFi issue, since all I did was install Viper through a .zip through TWRP.
I just have no clue what I'm doing, the forums were no use. I don't understand any of it. To be honest, I don't know how I managed to root my device in the first place without bricking it. I need someone to baby me through the reinstallation of an OS. I mean every moot detail.
My "POWER ON + VOL DWN" Menu:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT: 3.16.0.0000
RADIO: 1.16.21331931.LA11G
OpenDSP v38.2.2-005420M8974.0311
OS: N/A
eMMC-boot: 2048MB
Apr 18 2014,16:06:33.0
TWRP version is 2.7.0.2
lgally80 said:
I just have no clue what I'm doing, the forums were no use. I don't understand any of it. To be honest, I don't know how I managed to root my device in the first place without bricking it. I need someone to baby me through the reinstallation of an OS. I mean every moot detail.
My "POWER ON + VOL DWN" Menu:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT: 3.16.0.0000
RADIO: 1.16.21331931.LA11G
OpenDSP v38.2.2-005420M8974.0311
OS: N/A
eMMC-boot: 2048MB
Apr 18 2014,16:06:33.0
TWRP version is 2.7.0.2
Click to expand...
Click to collapse
First things first.
Yes, you need to update your firmware, but you also really need to update your recovery as well.
Download this version of ViperOneM8 and flash it from your extSD. That will get you an OS that works.
Next, update your recovery. I would suggest 2.8.7.0 or newer. You can find the downloads for that here and instructions on how to flash the recovery here. ( I usually use the fastboot method myself )
After that you can update your firmware. You can find downloads for your firmware and instructions on how to flash it in this thread.
After you have the new recovery and new firmware, you will be able to flash a ROM built for the newer Android versions with working wifi.
You could also update via RUU from HTC's official US website, but you didn't give enough information for that. An RUU will return your phone to stock.
If you want to RUU your phone, plug into your PC and get into fastboot, enter fastboot getvar all and post the results here minus your IMEI and serial#. Either me or someone else here will be able to direct you to the proper RUU.
I'm guessing from your profile that you are on AT&T? If so, you can find the RUU for your device and instructions to update manually here.
Good luck!
xunholyx said:
First things first.
Yes, you need to update your firmware, but you also really need to update your recovery as well.
Download this version of ViperOneM8 and flash it from your extSD. That will get you an OS that works.
Next, update your recovery. I would suggest 2.8.7.0 or newer. You can find the downloads for that here and instructions on how to flash the recovery here. ( I usually use the fastboot method myself )
After that you can update your firmware. You can find downloads for your firmware and instructions on how to flash it in this thread.
After you have the new recovery and new firmware, you will be able to flash a ROM built for the newer Android versions with working wifi.
You could also update via RUU from HTC's official US website, but you didn't give enough information for that. An RUU will return your phone to stock.
If you want to RUU your phone, plug into your PC and get into fastboot, enter fastboot getvar all and post the results here minus your IMEI and serial#. Either me or someone else here will be able to direct you to the proper RUU.
I'm guessing from your profile that you are on AT&T? If so, you can find the RUU for your device and instructions to update manually here.
Good luck!
Click to expand...
Click to collapse
So, I first flashed the latest TWRP, and it did not work. Upon boot, I got the HTC on white background, with red "development purposes" warning, and it stayed there. I reflashed openrecovery-twrp-2.7.0.2-m8.img over the twrp-3.0.2-0-m8.img and got my recovery back using "flash recovery *.img" through ADB. thank god. Was this due to S-ON?
Next step, going to try flashing the OS/Rom you suggested. Will update in a sec...
Update 1:
Crap, that .zip has a bunch of stuff in it... Do I need to "build" an image to flash manually? Going to use the OS *.img by itself instead of leaving it as a whole .zip and trying to flash the whole .zip. There is a boot.img file and I don't want to mess with boot, so I will extract the zip and use only the OS in TWRP and see how that goes...
Update 2:
Opened the original OS Viper I flashed, it was a .zip with boot also, so going to leave this new one alone and go ahead and flash as a whole...
Update 3:
Flashed as whole, last screen on install said successful, rebooted. On HTC screen, waiting to see what happens... 3 minutes into waiting...
Update 4:
Holy mother of gaben, booted into setup, and my WiFi radio is detecting my networks, that's all I needed. You deserve just as many blowjobs as you do internets. Don't know what was wrong with that last Viper ROM but this did it. Many thanks. Not even going to bother with the new TWRP and everything else, my phone works as is and that's that. +1 for you mate.
lgally80 said:
So, I first flashed the latest TWRP, and it did not work. Upon boot, I got the HTC on white background, with red "development purposes" warning, and it stayed there. I reflashed openrecovery-twrp-2.7.0.2-m8.img over the twrp-3.0.2-0-m8.img and got my recovery back using "flash recovery *.img" through ADB. thank god. Was this due to S-ON?
Next step, going to try flashing the OS/Rom you suggested. Will update in a sec...
Click to expand...
Click to collapse
I did say to flash the ROM first to get back your OS, so.....
Anyway, that recovery version won't work until you update your firmware. Try 2.8.7.0 first, update your firmware, then you can use the 3.x.x.x recovery
I should have been clearer in my instructions
lgally80 said:
Crap, that .zip has a bunch of stuff in it... Do I need to "build" an image to flash manually? Going to use the OS *.img by itself instead of leaving it as a whole .zip and trying to flash the whole .zip. There is a boot.img file and I don't want to mess with boot, so I will extract the zip and use only the OS in TWRP and see how that goes...
Click to expand...
Click to collapse
You don't need to mess with or open a custom ROM zip to flash it. You just flash the whole zip. Yes, there is a lot in there, the OS (particularly a Sense one) is big, about 1.5 GB.
Mess with taking things out of the zip, and it probably won't flash. Or even if it does, it won't boot.
lgally80 said:
Holy mother of gaben, booted into setup, and my WiFi radio is detecting my networks, that's all I needed.
Don't know what was wrong with that last Viper ROM but this did it.
Click to expand...
Click to collapse
There is nothing wrong with the current Viper ROM.
The problem is your firmware is ancient (release KitKat firmware). Firmware meaning a number of modules needed for the OS to work, but are not contained in a ROM, which include hboot, radio, and a number of other modules including . . . WiFi.
Using your outdated KitKat firmware with almost any later ROMs (Lollipop or Marshmallow) will result in the same issue of WiFi broken, and also possibly extreme long boot time or no boot.
If you want to flash any remotely updated ROMs, you will need to update firmware as xunholyx already directed.
redpoint73 said:
You don't need to mess with or open a custom ROM zip to flash it. You just flash the whole zip. Yes, there is a lot in there, the OS (particularly a Sense one) is big, about 1.5 GB.
Mess with taking things out of the zip, and it probably won't flash. Or even if it does, it won't boot.
There is nothing wrong with the current Viper ROM.
The problem is your firmware is ancient (release KitKat firmware). Firmware meaning a number of modules needed for the OS to work, but are not contained in a ROM, which include hboot, radio, and a number of other modules including . . . WiFi.
Using your outdated KitKat firmware with almost any later ROMs (Lollipop or Marshmallow) will result in the same issue of WiFi broken, and also possibly extreme long boot time or no boot.
If you want to flash any remotely updated ROMs, you will need to update firmware as xunholyx already directed.
Click to expand...
Click to collapse
Yes I probably "should" update TWRP and my firmware, buuuut....
If it ain't broke, don't fix it.
Also in reply to your comments:
1. Flashing ViperOneM8_6.1.0.zip caused WiFi loss. Maybe Bluetooth also, don't remember. Flashing ViperOneM8_2.5.0.zip and now my phone is 100% functioning.
2. That "Old" firmware works fine now that it matches the ROM requirements, all radios functioning stable for several days now. I don't mind staying on older releases.
3. Nah I'm good, I use this M8 as a tool or entertainment device at home, and nothing else. It has no service, no AT&T signal here. Hasn't had service since 3 years after public release.
Anyway, thank you everyone who contributed. Anyone who's just showing up:
The Lesson of the Day - If your Hardware Radios do not function, the solution is your ROM probably requires a different Firmware revision than the one installed.
Cheers.