Hey guys, first post here and I couldn't find a good thread title. Hope that's not a problem
Anyways I need a little help with my m8, because I don't know what else to do.
I'll start from the beginning:
It's a One m8, bought from O2 Germany a few months ago. There were no O2 apps installed as I bought it, though.
I unlocked the bootloader, rooted the phone, flashed the TWRP recovery and the Venom m8 ROM. It was S-On over the whole time. Tried to make it S-OFF with the help of firewater but it didn't worked, so I didn't tried it anymore.
I just wanted to flash the newest Venom ROM, but to do so, I had to flash the newest firmware (Kitkat 4.4, have 4.2 right now)
So I relocked the bootloader, because that's what people on the internet said you have to do, to flash the newest stock firmware. After that I wanted to go back to Venom m8.
After relocking the bootloader, I rebooted the phone, and now I'm stuck in there. But in the fastboot mode.
Tried to enter the recovery -> can't access it
Tried to make a factory reset -> didn't worked
Everytime klick on recovery or factory reset, the phone reboots and comes back into fastboot.
Normaly you boot into hboot I think.
At the top of the screen stands:
***TAMPERED***
***RELOCKED***
***Security Warning***
I've seen the first two the whole time, but the third one is new :/
Here are the things I tried until now:
Flashing a stock ROM (it was a OTA_m8_O2___102...) I could try to find the actual link, if that helps.
Flashing a custom recovery (tried TWRP, after that CWM) Yea I already have custom recovery, but I tought it might help somehow.
Erased fastboot cache
None of these things worked. Fastboot is the only thing that works.
So my question now is, if anyone of you guys got any other idea how to solve that problem?
I really would appreciate any help.
If you need some more informations about the phone, just let me know. I guess there's missing some important informations
Sorry for the long text and if I misspelled something
EDIT: I just remembered that the flashing of TWRP or CWM didn't worked. It said FAILED: signature verify fail
Flashing of the Stock ROM worked I guess. There was the silver HTC logo on the phone. Then I flashed it in fastboot mode.
I tried to find this RUU software, but I couldn't find it :/
And "adb" in cmd also not working. It says "device not found"
Have you tried unlocking it again ?
Sent from my HTC One_M8 using XDA Free mobile app
---------- Post added at 12:10 AM ---------- Previous post was at 12:08 AM ----------
Oh, and what are your CID / MID / bootloader version / firmware version / etc. ?
Sent from my HTC One_M8 using XDA Free mobile app
You're bootloader needs to be unlocked, not re-locked. Go to HTC Dev to unlock in again, just like the first time. Then you can flash a recovery.
Like said above, phone HAS to have unlocked bootloader to flash custom ROMs and recovery(which is why you're getting FAILED: signature verify fail). Can't flash custom recovery/ROMs with a locked bootloader.
Go to HTCDev.com and unlock the bootloader like before, then head over to the collection of stock backups thread(in general section) download a nandroid backup for your device and restore it. After that you can flash back the stock recovery(also in the collection thread) and just do the OTA updates until you get to 4.4.4 to use the latest ViperROM.
SunShine don't work with a modifyed custom Rom like ViperS. I flashed ARHD (or stock Rom) and got S-Off with SunShine.
Firewater don't work at all anymore so you have to use SunShine and pay the 25$ it cost.
3fiddy said:
Hey guys, first post here and I couldn't find a good thread title. Hope that's not a problem
Click to expand...
Click to collapse
Its not a bad one. At least better than many thread titles that say things like "Need help". Which of course is obvious, since its a Q&A, help forum! At least you tried to classify your issue!
Although the question of whether its a "soft brick" is not a critical one. IMO the term "soft brick" really doesn't mean anything. It simply means the user just got himself into a jam and doesn't know how to recover. And recovering is usually just a matter of knowing the right simple steps. More important to whether its a "soft brick", is whether the phone is truly bricked or not. And as long as the screen comes on, this phone is virtually never bricked.
RUUs don't exist for Euro versions (only the US versions, as far as I know).
The bootloader needs to be UNLOCKED to flash anything. Either just use the previous unlock bin code and fastboot command, or go through HTCDev.com unlock process again (as previously suggested). Then flash custom recovery, and flash a custom ROM or restore a stock nandroid.
Hey guys, sorry for the late response.
I did what you all said and unlocked the bootloader again. And that was it.
After unlocking it everything works normal.
You guys are the best, I knew this is the right place to come
Even the Venom ROM is on the phone. Everything else is gone, but the ROM is there.
Alright but I still would like to get the newest firmware for the phone. Could you guys give me a little help with this?
What do I have to do first?
I read a lot about how to do this. But as you can see something still went wrong :/
On the phone is currently Android 4.4.2 and ViperOneM8 1.7.0
First thing I have to do is, to grab a Nandroid Backup with the stock ROM, right?
I did this before, but then I read somewhere that the bootloader has to be locked, or relocked to update the newest stock ROM/ the newest firmware.
So if anyone knows how to do this correctly, please let me know.
Also when I flashed the nandroid backup (my own backup from before I flashed venom) I tried to update the firmware, but it wanted to update the latest Venom update.
Is this considered as normal?
Bootloader version (Hboot) is 3.16.0.0... At least I think this is the right one.
@jkolner: Didn't know that firewater doesn't work anymore. How long is this?
@redpoint73: Thanks for the heads-up Also I didn't know that there are no RUUs for the european versions. Good to know that now.
Thank you all for your answers
EDIT: I just tried to enter the recovery and it worked as well.
Oh and when I wrote above that I flashed the stock nandroid backup and the phone wanted to update the latest venom update, I think it was because the rom was still the Venom Rom, right?
Sure it was a nanroid backup, but the ROM was not the stock ROM? Or am I mix-up something there?
3fiddy said:
Alright but I still would like to get the newest firmware for the phone.
I read somewhere that the bootloader has to be locked, or relocked to update the newest stock ROM/ the newest firmware.
Click to expand...
Click to collapse
It sounds like you are trying to return to stock, and install official OTA to update firmware. In that case, unlocked bootloader is OK for OTA (no need to relock). But you need stock ROM and stock recovery.
3fiddy said:
Also when I flashed the nandroid backup (my own backup from before I flashed venom) I tried to update the firmware, but it wanted to update the latest Venom update.
Is this considered as normal?
Oh and when I wrote above that I flashed the stock nandroid backup and the phone wanted to update the latest venom update, I think it was because the rom was still the Venom Rom, right?
Sure it was a nanroid backup, but the ROM was not the stock ROM? Or am I mix-up something there?
Click to expand...
Click to collapse
You are mixing something up. The point of restoring a stock nandroid, is to return to the stock ROM. It sounds like your nandroid is made while on Viper ROM, not stock ROM. Either that, or the nandroid just didn't restore the ROM properly. Make sure "system" is checked on partitions to restore in recovery.
3fiddy said:
Bootloader version (Hboot) is 3.16.0.0... At least I think this is the right one.
Didn't know that firewater doesn't work anymore. How long is this?
Click to expand...
Click to collapse
Its been that way for months now. But your hboot version is old; so firewater might work, might not. Worth a few tries; as firewater is free and doesn't take long. If it still fails, you need to use sunshine to s-off.
redpoint73 said:
It sounds like you are trying to return to stock, and install official OTA to update firmware. In that case, unlocked bootloader is OK for OTA (no need to relock). But you need stock ROM and stock recovery.
Click to expand...
Click to collapse
Exactly this. Alright, then I read something wrong. I thought to flash the stock ROM you have to have a relocked bootloader.
I'll search a stock ROM and recovery. Hoperfully it will work.
redpoint73 said:
You are mixing something up. The point of restoring a stock nandroid, is to return to the stock ROM. It sounds like your nandroid is made while on Viper ROM, not stock ROM. Either that, or the nandroid just didn't restore the ROM properly. Make sure "system" is checked on partitions to restore in recovery.
Click to expand...
Click to collapse
This could be it. I don't know if there was already the Venom ROM in use. Could be.
redpoint73 said:
Its been that way for months now. But your hboot version is old; so firewater might work, might not. Worth a few tries; as firewater is free and doesn't take long. If it still fails, you need to use sunshine to s-off.
Click to expand...
Click to collapse
Okay I'll try it with firewater again.
Thanks for your help
EDIT: After I flashed the Nadroid Backup, do I have to wipe something, like Dalvik or anything?
3fiddy said:
EDIT: After I flashed the Nadroid Backup, do I have to wipe something, like Dalvik or anything?
Click to expand...
Click to collapse
I wipe Dalvik and cache when I flash anything.
Recovery will wipe system as it flashed the ROM. No need to do so manually.
If restoring a nandroid without data partition backed up, you may or may not have to wipe user data. It might not play well with the restored ROM, but it depends on what ROM you are coming from. If error occur, wipe data and restore again.
If you are restoring a nandroid with data partition backup, it will be wiped during restore. No need to do so manually.
Alright I flashed my own stock nandroid backup. Guess I just read something wrong because I thought it will get the latest Venom Update.
Then I downloaded and installed the latest updates. Now the phone has finally Android 4.4.
After everything went good, I flashed the twrp recovery, made a Backup, rooted the phone, did another backup and flashed the latest Venom ROM.
Before flashing something I wiped everything, like you said.
All is good now.
I think now I can totally forget to gain S-OFF with firewater. But I'll save the link to sunshine. Maybe I'll give it a try
Thanks again everyone, couldn't have done it without your help
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.
Update: Well, I took the plunge on my own, and everything worked fine. Flashed firmware.zip, went to stock recovery and flashed OTA, and voila, all good.
So I've bought an HTC device for the first time. I did S-Off and unlocked bootloader and rooted as well. Now, there's an OTA available (I have the Asia_India variant), and I wanted to ask just how would I go about updating.
Here's what I've surmised till now:
1. Revert changes to system partition or it will fail to update (I moved some system APKs, but I saved them for such a scenario.)
2. Flash Firmware.zip to get stock recovery back.
3. Install OTA normally from the notification.
However, I'm still not sure what else I'd need to do (unroot, using the option in SuperSU?), so was wondering if someone could help me out. I've made backups in Philz and TWRP recovery both just to be sure.
P.S.: I extracted the firmware.zip file from the OTA, and tried to open it, but it doesn't open in apps like WinRAR. Is that normal, with the file only flashable via fastboot?
Personally, I'd say remove root just incase it stops the OTA but others will say it doesn't matter so long as the rest of the system is 100% stock as HTC intended it
For OTA updates after having a custom recovery, just flash your ROM stock recovery (search XDA all are available) then run OTA as you normally would and then flash your custom recovery again (if you like to get root again). However personally I would not do this with S-ON device, probably it's better if you're S-OFF while doing this to avoid any problem.
I am also interested in this. What would be the risk if I do this with S-ON? Assume I flash the wrong stock recovery or do some other mistake, won't I still be able to flash my custom recovery back from fastboot and get everything back up and running?
Thanks to whom will answer. :good:
Black Antitoon said:
I am also interested in this. What would be the risk if I do this with S-ON? Assume I flash the wrong stock recovery or do some other mistake, won't I still be able to flash my custom recovery back from fastboot and get everything back up and running?
Thanks to whom will answer. :good:
Click to expand...
Click to collapse
So long as the phone still boots to fastboot, yes (although unlocking the boot loader will delete any backups so make sure you backup the backup to your PC before doing anything else!)
Thank you for your answer. As far as you know, being S-ON, is there really any kind of mistake one can do to brick the phone so that it doesn't even boot to fastboot?
Also, if my bootloader is already unlocked, no data wipe is going to happen again flashing a firmware/OTA in any predictable case, right?
Once again, thank you or anybody else who knows the answer.
By the way, are there any FAQs answering these questions? There are some FAQs here and there, but none seems to be very clear on these matters.
Black Antitoon said:
Thank you for your answer. As far as you know, being S-ON, is there really any kind of mistake one can do to brick the phone so that it doesn't even boot to fastboot?
Also, if my bootloader is already unlocked, no data wipe is going to happen again flashing a firmware/OTA in any predictable case, right?
Once again, thank you or anybody else who knows the answer.
By the way, are there any FAQs answering these questions? There are some FAQs here and there, but none seems to be very clear on these matters.
Click to expand...
Click to collapse
If you're S-ON there's not a lot you can do to brick the phone. You could wipe the ROM and have it not boot but you should always be able to get back to fastboot. This is where S-OFF is only handy to have if RUUs are about (it's the ONLY reason I am S-OFF, it's purely for a 'going back to stock' standpoint)
Yes, if the bootloader is already unlocked then you're good to go
Hey guys, please help me out. I tried reverting back to stock AT&T HTC One M8 but I seem to have managed to remove the entire OS. I was following a guide on here on how to revert back but whatever I did in RUU, it completely ruined the phone so far. I can't load past the HTC logo. I'm able to install a custom recovery program but I don't know how to get back to anything at this point. I'm going to try to flash a custom ROM and see if that works but ultimately I'd like to go back to completely stock ROM. Thank you for the responses in advance.
First, flash a ROM in recovery to get it working again. Secondly, read the guides on going back to stock more thoroughly and make sure you understand what you're actually doing before trying to go back to stock again (the same is true before you even think about unlocking the phone - why do something when you have no idea what to do if something goes wrong?!?!).
I know my response may sound harsh but if you'd read up on everything first before doing anything then this question wouldn't have to be asked over and over again by multiple people every day...
EddyOS said:
First, flash a ROM in recovery to get it working again. Secondly, read the guides on going back to stock more thoroughly and make sure you understand what you're actually doing before trying to go back to stock again (the same is true before you even think about unlocking the phone - why do something when you have no idea what to do if something goes wrong?!?!).
I know my response may sound harsh but if you'd read up on everything first before doing anything then this question wouldn't have to be asked over and over again by multiple people every day...
Click to expand...
Click to collapse
Thank you for the response, appreciate it! I do read almost everything before flashing my devices, I like to see what problems people encounter before I attempt to mess with my phone. But I just found my mistake I ran into. The guide I was reading was about going from GPE to Sense Stock (I had maybe 4hrs of sleep in my defense on being brain dead). I did flash back to a custom ROM for now, I'll just do some more further research on going back to stock sense. Is it just as simple as getting the ROM and flashing like the custom ROMs?
Jayanyway said:
Thank you for the response, appreciate it! I do read almost everything before flashing my devices, I like to see what problems people encounter before I attempt to mess with my phone. But I just found my mistake I ran into. The guide I was reading was about going from GPE to Sense Stock (I had maybe 4hrs of sleep in my defense on being brain dead). I did flash back to a custom ROM for now, I'll just do some more further research on going back to stock sense. Is it just as simple as getting the ROM and flashing like the custom ROMs?
Click to expand...
Click to collapse
So, were you running a GPe ROM or a Sense ROM? If you were running a Sense ROM you just need to restore a backup to get it back to stock. What software build was the phone on when you bought it new?
EddyOS said:
So, were you running a GPe ROM or a Sense ROM? If you were running a Sense ROM you just need to restore a backup to get it back to stock. What software build was the phone on when you bought it new?
Click to expand...
Click to collapse
I was on a Sense ROM. Android Revolution to be exact. And if you're talking about this number: 1.54.401.5 then I was that?
So just find a backup and restore to it? And that'll allow me to grab OTA updates too?
Jayanyway said:
I was on a Sense ROM. Android Revolution to be exact. And if you're talking about this number: 1.54.401.5 then I was that?
So just find a backup and restore to it? And that'll allow me to grab OTA updates too?
Click to expand...
Click to collapse
If your phone was on 1.54.401.5 when you first got it (or before you flashed a custom ROM), and if you're S-OFF, you can follow the guide in my signature to go back to 100% stock
EddyOS said:
If your phone was on 1.54.401.5 when you first got it (or before you flashed a custom ROM), and if you're S-OFF, you can follow the guide in my signature to go back to 100% stock
Click to expand...
Click to collapse
Now what if I'm not 100% sure what build number I was before messing with my phone? Good chance of bricking? And one last question I promise, If I do go back to stock Sense ROM, can I still be rooted. S-Off, bootloader unlocked and still receive OTA updates? Or would I have to lock down again? I did read your guide, I was just wondering if I would still receive em before I decide to do all this work again lol
I really appreciate the quick responses. You're awesome.
Jayanyway said:
Now what if I'm not 100% sure what build number I was before messing with my phone? Good chance of bricking? And one last question I promise, If I do go back to stock Sense ROM, can I still be rooted. S-Off, bootloader unlocked and still receive OTA updates? Or would I have to lock down again? I did read your guide, I was just wondering if I would still receive em before I decide to do all this work again lol
I really appreciate the quick responses. You're awesome.
Click to expand...
Click to collapse
If you're not sure on the original build then I wouldn't follow my guide. Do you know the CID of your phone? to check, run the following fastboot command:
fastboot getvar all
And post the results (blanking out the S/N and IMEI)
EddyOS said:
If you're not sure on the original build then I wouldn't follow my guide. Do you know the CID of your phone? to check, run the following fastboot command:
fastboot getvar all
And post the results (blanking out the S/N and IMEI)
Click to expand...
Click to collapse
Well I recently changed my CID to that 11111111 CID but here's what I got from that command:
Jayanyway said:
Well I recently changed my CID to that 11111111 CID but here's what I got from that command:
Click to expand...
Click to collapse
Looks like an AT&T model to me.
Something that is not clear to me: Did you convert your phone to GPE or not? The partiton sizes are different so, if you did a GPE conversion you would need to convert your firmware partitions back.
If you didn't convert to GPE, you should just be able to restore a CWS__001 backup from the stock backups thread in the general section, flash stock recovery and download/install the OTA.
exad said:
Looks like an AT&T model to me.
Something that is not clear to me: Did you convert your phone to GPE or not? The partiton sizes are different so, if you did a GPE conversion you would need to convert your firmware partitions back.
If you didn't convert to GPE, you should just be able to restore a CWS__001 backup from the stock backups thread in the general section, flash stock recovery and download/install the OTA.
Click to expand...
Click to collapse
Yes, I have an AT&T HTC One M8. As far as I know, I never converted to GPE. Here's a history of what I've done as far as flashing goes.
Unlocked bootload, rooted, went S-Off, flashed Android Revolution, flashed Viper ROM, went back to Android Revolution then tried to go back to stock and broke my phone. Now I'm back on Android Revolution. I did a whole bunch of factory resets/dalvik wipes and such so maybe that's why it looks confusing?
exad said:
If you didn't convert to GPE, you should just be able to restore a CWS__001 backup from the stock backups thread in the general section, flash stock recovery and download/install the OTA.
Click to expand...
Click to collapse
Sent from my HTC One_M8 using XDA Free mobile app
Same Problem?
Hey folks!
I have the same question I think and I don't want to open a new thread.
I flashed SinlessRom over ViperOne without converting to GPe and now I'm stuck in a bootloop...
Can I restore a CWS__001 backup from the stock backups thread, flash stock recovery and I'm good to go?
Edit: Ok, my m8 is working now after flashing ViperOne, because it fixed the partitions
Edit2: There is still no information about the os when I'm booting into the bootloader
Does nobody know, why there is no firmware version?
Missing OS in HBOOT resolution
Finally got the answer I was looking for!
Download the modified TWRP from here:
http://forum.xda-developers.com/showthread.php?p=54054835
You are going to have to flash your current firmware first before installing it for the OS info to show up again in HBOOT. You can use the Flashify app to install it or else just do it the PC/ADB way using command prompt like I did. It totally worked for me, so go ahead and try it!!
If you have questions on how to flash anything, lemme know.
RockStar2005
Lintux_ said:
Does nobody know, why there is no firmware version?
Click to expand...
Click to collapse
Deleted.
Sorry didn't see your post @RockStar2005
Disregard this message!!
HTCNerdYoda said:
Deleted.
Sorry didn't see your post @RockStar2005
Click to expand...
Click to collapse
Yoda,
Hey........ disregard my previous message. That version of TWRP DOES work (fixing "Blank OS" issue), HOWEVER........ I created a new backup using it and then tried to restore it over the weekend........... IT DIDN'T WORK! I think something is corrupted with it. So anyone who clicked on that link and got that version of twrp, delete it and ANY BACKUPS YOU CREATED WITH IT immediately. They are corrupted and useless.
Fortunately though, I was able to find a fully-operational version of TWRP over the weekend that has no issues and it too fixes the "Blank OS" problem too. Here you go:
http://themikmik.com/showthread.php?16278-SPRINT-RECOVERY-TWRP-Recovery-(UNOFFICIAL)-v2-7-0-4 (Control + F this: "Downloads TWRP Recovery 2.7.1.0 (DH) | Mirror (AFH) - build date: July 13, 2014". I downloaded from the Mirror link.)
Don't worry about it saying Sprint...... the dev CONFIRMED it works for all variants/carriers. So after creating a new backup using the standard twrp, I went back to stock recovery, re-flashed my most recent firmware (2.22.401.5), and then switched over to that new version of twrp........ created a new backup and then restored it using that new version. Worked like a charm!! And the "blank OS" issue........... gone! I highly recommend it!!
So please delete that old twrp and any backups you created using it, and you should be good to go!
P.S. My thanks to Midasgalp and also Captain Throwback!!
RockStar2005
Thanks.
Sent from my HTC One_M8 using XDA Free mobile app
Thanks.
Sent from my HTC One_M8 using XDA Free mobile app[/QUOTE]
Anytime buddy!
RockStar2005
Alright. So I'm rooted with s-off. I had TWRP recovery. I flashed the stock recovery and got that going. Then I downloaded the OTA update and hit "Install Now". The phone instantly reboots, but goes into the stock recovery. I reboot the phone and I still have 4.4.2. What am I missing here?
PiperCub49 said:
Alright. So I'm rooted with s-off. I had TWRP recovery. I flashed the stock recovery and got that going. Then I downloaded the OTA update and hit "Install Now". The phone instantly reboots, but goes into the stock recovery. I reboot the phone and I still have 4.4.2. What am I missing here?
Click to expand...
Click to collapse
This has been discussed many times,but is your boot loader unlocked? If so, your data/preload folder was wiped when the bl was unlocked and that is needed. Your system files must be 100% stock... Otherwise the update Will fail... You could always find the 4.4.3 ruu and flash in fastboot... That's what I did n worked flawlessly...
A few post debranding questions
Hi,
I've recently been exploring this forum and finally bit the bullet this evening and decided to try and de-brand my EE branded M8.
Steps I took were:
1) Used Sunshine to S-Off
2) Installed TWRP
3) Changed my SID from ORANG001 to HTC__001
3) Installed SuperUser
4) Downloaded the TWRP Nandroid for 1.54.401.5 - TWRP from http://forum.xda-developers.com/showthread.php?t=2701376
5) Used TWRP to restore the Nandroid and confirmed the software version was now 1.54.401.5
I have a few questions:
A) After the install the apps I had installed, my unlock pattern, contacts and wallpapers were all still visibile - is this normal? I had assumed the Nandroid backup would act like a factory reset
B) Is it safe to perform a factory reset, or do I need to somehow install a new image for it to restore from? I mean going through Settings -> Backup and Restore. Ideally having downgranded the software I'd like a "clean slate" - but I'm worried it will try and install a newer version and fail
C) Is it safe to perform an OTA update (this was one of my reasons for debranding)? Anything else I need to do?
D) Anything else I should be aware of? Any danger to leaving S-OFF and the bootloader unlocked? TWRP as the Recovery image?
Thanks
bdizzle1686 said:
This has been discussed many times,but is your boot loader unlocked? If so, your data/preload folder was wiped when the bl was unlocked and that is needed. Your system files must be 100% stock... Otherwise the update Will fail... You could always find the 4.4.3 ruu and flash in fastboot... That's what I did n worked flawlessly...
Click to expand...
Click to collapse
Thanks for the help. For the life of me, I couldn't find anything about having to have that bootloader locked. It's now locked (as confirmed by the "Locked" banner on the recovery screen), but the same thing is happening. Is there anything I can do short of flashing an RUU? Maybe there are some other major things that aren't stock?
PiperCub49 said:
Thanks for the help. For the life of me, I couldn't find anything about having to have that bootloader locked. It's now locked (as confirmed by the "Locked" banner on the recovery screen), but the same thing is happening. Is there anything I can do short of flashing an RUU? Maybe there are some other major things that aren't stock?
Click to expand...
Click to collapse
You don't have to lock the bootloader again, whether you are S-ON or S-OFF doesn't matter.
When it boots to stock recovery, does it give a error message to you? If there was a problem during updating it'll show the problem to you.
pryonic said:
A) After the install the apps I had installed, my unlock pattern, contacts and wallpapers were all still visibile - is this normal? I had assumed the Nandroid backup would act like a factory reset
Click to expand...
Click to collapse
Maybe the nandroid backup doesn't have data part, so restoring the backup alone will not erase your data because it doesn't get replaced. The best is make a factory reset in TWRP before you restore the backup
pryonic said:
B) Is it safe to perform a factory reset, or do I need to somehow install a new image for it to restore from? I mean going through Settings -> Backup and Restore. Ideally having downgranded the software I'd like a "clean slate" - but I'm worried it will try and install a newer version and fail
Click to expand...
Click to collapse
When you have TWRP installed, the best way to factory reset is Factory Reset in TWRP itself.
pryonic said:
C) Is it safe to perform an OTA update (this was one of my reasons for debranding)? Anything else I need to do?
Click to expand...
Click to collapse
You won't be able to perform OTA as the system will say you have modified variant. What you need (a step that you're missing) is the proper firmware is flashed after your step 3. (also you may need a change of MID if the MID for ORANG001 is different from HTC__001; if they are same then skip this)
pryonic said:
D) Anything else I should be aware of? Any danger to leaving S-OFF and the bootloader unlocked? TWRP as the Recovery image?
Click to expand...
Click to collapse
No danger, in fact you should leave it as it is, except when doing OTA you need stock recovery installed first (OTA won't work on TWRP)
PiperCub49 said:
Thanks for the help. For the life of me, I couldn't find anything about having to have that bootloader locked. It's now locked (as confirmed by the "Locked" banner on the recovery screen), but the same thing is happening. Is there anything I can do short of flashing an RUU? Maybe there are some other major things that aren't stock?
Click to expand...
Click to collapse
Sorry I wish I woulda been more specific, there was really no point in relocking it... Once u unlock it the 1st time, the data/preload is wiped and relocking it doesn't bring it back..so u could've just left it
I have a Htc One M8 ; s-off, hboot 3.16, running 4.4.2. CID is Roger001, unlocked boot
Problem I have is I'm trying to restore the phone to stock because I want to do OTA updates. I followed the guide to return Canadian HTC1m8 to stock - downloaded the nandroid backup, restored it, flashed a stock image through fastboot;
However, now if I try a OTA it just reboots my phone and normally stalls out on the HTC screen. Nothing gets updated . If i try a factory reset, same thing, and it won't boot into bootloader until I wait a while then restart it. My data won't work anymore and TWRP recovery has disappeared. I think my issue is i flashed the wrong recovery .img, I'm a fairly noob. Checked all the related links and can't figure it out.
Any help would be amazing.
Use an ruu For your phone to update your hboot and make your you flash to recovery partition for twrp
htcspark said:
Use an ruu For your phone to update your hboot and make your you flash to recovery partition for twrp
Click to expand...
Click to collapse
I would but
I can't find an ruu that would work, there doesn't seem to be one for rogers...I dunno if any US carriers would work?
htcspark said:
Use an ruu For your phone to update your hboot and make your you flash to recovery partition for twrp
Click to expand...
Click to collapse
I got an update to work, I think I had the wrong stock installed so it wouldn't work properly. Only thing now is my data isn't working, any assistance with that that could be??
Instead of trouble shooting, I would just flash this TWRP backup tested to work on Rogers M8:
http://forum.xda-developers.com/showthread.php?p=58611288
See end of 1st post in above link.
It is already in lollipop. No OTA update needed.
Use latest TWRP recovery, see 2nd post in above link.