hello. i have a question about being s-off, i have a m9 with telcel stock room, MM and firm 3.44.600.1, and i tried to flash a custom rom, but the base was another firmware, so i got softbricked, i did revive the phone with a backup from another page, everything was fine, but the phone started to do some restarts, 2or3 per day, and everytime he does that, some settings, like the ringtone, screen time, bluethoot, and other things change. idk if the backup was corrupted, or if the phone restarts because i didnot do a full wipe before restoring from that backup. So the question is, there none flasheable roms for this firmware or ruu's. but theres alot of roms for the 3.35.... firm, so, if i buy the soff sunshine software, will i be able to flash those roms? to get rid of these crashes? ty
Yes, after changing Your CID and MID to developer ones, You will be able to flash any RUU. To do that, You need to perform S-OFF. There is great tutorial for that - http://forum.xda-developers.com/att-one-m9/general/att-developer-edition-ruu-how-to-t3086948 (be carefull with that!)
Related
Hello,
I own a HTC One V that is t-mobile(germany)-branded.
I s-off'ed it using the official HTC procedure and then rooted it using this guide (theandroidsoul.com/root-one-v).
Ever since then, I am having connection problems, as in, no connection unless I reboot it. This especially occurs while talking on the phone,
but also at random. I then attempted to apply the RUU_PRIMO_U_ICS_40A_HTC_Europe_2.08.401.2_Radio_20.72.30.0833U_3831.17.00.18_M_release_263376_signed.exe following tutorials
-> first, locking the bootloader, then flash the recovery, then apply the RUU - flashing the recovery worked, however, the RUU failed because the CID does not match. Changing to SuperCID does not seem to be possible at the moment.
Plus, ever since I flashed the RUU recovery, I can't change sounds anymore, so whenever I try to change alarms/ringtones/notification sounds, the personalizer oder settings application crashes.
In order to check if the connection issue is related to the rooting process (and if it isn't, to get it replaced by t-mobile) I need to revert to the stock t-mobile ROM, however, I can't find any.
Is there any other way to solve this dilemma or can you help me?
Chikari said:
Hello,
I own a HTC One V that is t-mobile(germany)-branded.
I s-off'ed it using the official HTC procedure and then rooted it using this guide (theandroidsoul.com/root-one-v).
Ever since then, I am having connection problems, as in, no connection unless I reboot it. This especially occurs while talking on the phone,
but also at random. I then attempted to apply the RUU_PRIMO_U_ICS_40A_HTC_Europe_2.08.401.2_Radio_20.72.30.0833U_3831.17.00.18_M_release_263376_signed.exe following tutorials
-> first, locking the bootloader, then flash the recovery, then apply the RUU - flashing the recovery worked, however, the RUU failed because the CID does not match. Changing to SuperCID does not seem to be possible at the moment.
Plus, ever since I flashed the RUU recovery, I can't change sounds anymore, so whenever I try to change alarms/ringtones/notification sounds, the personalizer oder settings application crashes.
In order to check if the connection issue is related to the rooting process (and if it isn't, to get it replaced by t-mobile) I need to revert to the stock t-mobile ROM, however, I can't find any.
Is there any other way to solve this dilemma or can you help me?
Click to expand...
Click to collapse
Now just hold on a sec. You can't S-Off at the moment, as far as I know, and there is no HTC software for it. You just unlocked the bootloader, to give yourself some priviledges, but that is not S-Off, so you cannot change the CID of the phone (or debrand it).
Stock ROM for T-Mobile is not available at the moment (or at least for the public) Ask Football for it, but it will cost some EUR for you.
If the RUU sees anything wrong with the phone (including CID) it won't even start flashing the device, so it cannot do any harm for you. But since you unlocked BL I suggest to install custom firmware to see if anything is wrong with the hardware. Just be sure to do a nandroid backup before, so you can revert to the "stock" if possible.
Hi
My M8 was rooted, and trying to unroot it I made a mess, can't get out of it.
Unlocked, S ON, International.
It's stuck in Bootloader but I can enter the Recovery (Clockworkmod PhilzTouch 6)
The problem is, no matter witch rom I try, the phone needs to be S OFF, but mine is S ON, unlocked.
So, I don't know how to S OFF it from the Recovery if it's at all possible.
Is there any way to make his heart beat again?
First off, this section is specifically for the AT&T version of the M8. For international, you should post to the following section (you will probably also get more response there): http://forum.xda-developers.com/htc-one-m8
But in regards to your questions,NO ROMs require s-off. However, the ROM needs to correspond to your phone's firmware (hboot, radio, etc.) to work properly, and the easiest way (but certainly not the only way) to update firmware is by s-off.
Sunshine is the only s-off method, and requires a working OS. But as mentioned, if your intent is to get the phone running again, you do not need s-off for that.
redpoint73 said:
First off, this section is specifically for the AT&T version of the M8. For international, you should post to the following section (you will probably also get more response there): http://forum.xda-developers.com/htc-one-m8
But in regards to your questions,NO ROMs require s-off. However, the ROM needs to correspond to your phone's firmware (hboot, radio, etc.) to work properly, and the easiest way (but certainly not the only way) to update firmware is by s-off.
Sunshine is the only s-off method, and requires a working OS. But as mentioned, if your intent is to get the phone running again, you do not need s-off for that.
Click to expand...
Click to collapse
I succeeded installing a custom rom, but now every time I restart the device it keeps restarting (not fully loading the system, but just till logo). Now I have to keep it charged all the time and if battery dies or a restart is required I have to flash it again... every time! It's driving me mad.
Thank you for the answer and time spent on it. I appreciate it.
nakharmoz said:
I succeeded installing a custom rom, but now every time I restart the device it keeps restarting (not fully loading the system, but just till logo). Now I have to keep it charged all the time and if battery dies or a restart is required I have to flash it again... every time! It's driving me mad.
Thank you for the answer and time spent on it. I appreciate it.
Click to expand...
Click to collapse
You probably need to update your firmware and use a up-to-date recovery (Philz has not been update in a very long time).
What ROM did you flash?
What is your hboot number?
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 !
Hey so here's my situation:
Installed the CM Nightly on my AT&T One M9, didn't like it, so I tried to revert to stock. I didn't want to pay $25 to S-OFF so I just tried installing various RUUs, but none would work. I read somewhere that I needed to relock my bootloader in order for the RUUs to work, so I did that, and now my phone just boots to Recovery Mode. I've tried installing AT&T RUU 2.6.502.16 (which didn't work because my phone is on a more recent firmware) and reinstalling 2.11.502.18/flashing its 0PJAIMG.zip (which didn't work because it's apparently broken). I've even tried installing T-Mobile's 2.11.531.19 RUU, which of course didn't work because my CID doesn't match and I can't change it because I'm S-ON.
I realize I went about this very badly almost from the start--no stock backup in TWRP, etc. This is my first Android phone so I've been learning this as I go and I was a bit sloppy.
I'm pretty sure I'm screwed, at least until a new update comes out or the current AT&T RUU is fixed, but I'm wondering if there's something else I can try. Any ideas? Thanks.
StageProps said:
Hey so here's my situation:
Installed the CM Nightly on my AT&T One M9, didn't like it, so I tried to revert to stock. I didn't want to pay $25 to S-OFF so I just tried installing various RUUs, but none would work. I read somewhere that I needed to relock my bootloader in order for the RUUs to work, so I did that, and now my phone just boots to Recovery Mode. I've tried installing AT&T RUU 2.6.502.16 (which didn't work because my phone is on a more recent firmware) and reinstalling 2.11.502.18/flashing its 0PJAIMG.zip (which didn't work because it's apparently broken). I've even tried installing T-Mobile's 2.11.531.19 RUU, which of course didn't work because my CID doesn't match and I can't change it because I'm S-ON.
I realize I went about this very badly almost from the start--no stock backup in TWRP, etc. This is my first Android phone so I've been learning this as I go and I was a bit sloppy.
I'm pretty sure I'm screwed, at least until a new update comes out or the current AT&T RUU is fixed, but I'm wondering if there's something else I can try. Any ideas? Thanks.
Click to expand...
Click to collapse
I downloaded and flashed the 2.11.502.18 ruu from the HTC website with no problem. Ate you getting an error?
Edit: in my experience, if an ruu.exe starts to run and then never does (like you get the spinning wheel for a minute and then nothing) it's either a bad download or antivirus is blocking the file. But just to repeat...the exe on the HTC website works fine. I used it about three weeks ago.
Hm. Out of the myriad RUU.exes I've tried the most recent AT&T one was the only one I couldn't get to start, and when I tried installing it via .zip it would just restart the phone and nothing else. That in combination with other posts I've seen on this forum saying it's borked (although I might have misread the numbers/misinterpreted the jargon) just lead me to think it was broken. I'll redownload and try again. Thanks!
Edit: Well, it worked! I don't know what I was doing wrong. Thanks a lot!
Hello;
So, i got a HTC M8 On 6.20.531.5, and currently is is S-ON with Unlocked Bootloader, sadly, each time the battery dies, the settings reset, i do know this is a problem with this device, but i read that flashing another rom might fix it.
So i found ViperRom and Xenon HD, already got a Nandroid Backup, however, yesterday i tried to flash the same RUU that the device is currently. 6.20.351.5, and it got stuck at Sending,
<T103747><DEBUG><OUT>sending 'zip' (53953 KB)...</OUT>
after that, nothing happened so i re-unlocked the device and everything was the same, TWRP was there, among everything.
My questions are:
What do i need to do, in order to flash the RUU without issues?
What do i need to flash the RUU correctly?
Is there a fix for the "Reset Issue"?
It also happens once the device is turned on agian after a battery drain, it always get the "Sense has stopped working + Gapps has stopped working", so i always have to factory reset, is there a known fix for this?
Flashing a Custom Rom, do i need to flash first boot.img then flash the rom via TWRP? or i can do it all on TWRP?
Can i flash the RUU in case something happen on the Custom Rom?
Can i flash the Same RUU that the device is currently on?
Will tag @redpoint73 since i have seen that you are pretty much on the HTC section those days.
Sorry I am just now responding. Was out of the country for work, and working 12+ hours a day (and therefore not on xda).
My responses below in red font:
ScarletDreamz said:
So i found ViperRom and Xenon HD, already got a Nandroid Backup, however, yesterday i tried to flash the same RUU that the device is currently. 6.20.351.5, and it got stuck at Sending,
Pretty sure you mean 6.20.531.5, and the above is just a typo.
I am confused about why you are trying to RUU, if you intend to flash a custom ROM. The 2 things do not really have anything to do with each other. Fastboot flash TWRP, make a nandroid backup (which you did) then flash the custom ROM.
<T103747><DEBUG><OUT>sending 'zip' (53953 KB)...</OUT>
This doesn't look right. Are you trying to use adb to flash the RUU zip? Post your entire set of commands, so I can take a look. If you are trying to flash by adb, that isn't correct, you need to use fastboot, and the htc_fastboot version at that. I can give more details. But I'm not even sure RUU is what you really need to do (per my response above).
after that, nothing happened so i re-unlocked the device and everything was the same, TWRP was there, among everything.
My questions are:
What do i need to do, in order to flash the RUU without issues?
What do i need to flash the RUU correctly? Already addressed this above.
Is there a fix for the "Reset Issue"? I never suffered this issue personally. Haven't dug too deep into it, myself.
It also happens once the device is turned on agian after a battery drain, it always get the "Sense has stopped working + Gapps has stopped working", so i always have to factory reset, is there a known fix for this? Same response as #2 above.
Flashing a Custom Rom, do i need to flash first boot.img then flash the rom via TWRP? or i can do it all on TWRP? Never need to flash boot.img separately from the ROM. Folks need to stop implying or thinking that you do. This never applied to the M8 (only to older HTC devices).
Can i flash the RUU in case something happen on the Custom Rom? You can. Or just restore the nandroid you made of the stock ROM. Which is the reason you made the nandroid in the first place, right?
Can i flash the Same RUU that the device is currently on? Yes. That is the only one that will work. "Newer" RUUs are typically allowed. But for the M8, there are no newer version RUU (since device is EOL). So like I said, that RUU is the only one that will work.
Will tag @redpoint73 since i have seen that you are pretty much on the HTC section those days.
Click to expand...
Click to collapse