Related
I got myself in a bit of a dead zone here.
I have my HTC one. Its HTC__001 WWE Europe. It OTA upgraded to 2.24.401.1.
When I saw that you can convert to a GPE I really wanted to check it out specially after users reported success in getting OTA updates. But I quickly realized I needed S-Off and thats not available yet.
I decided to at least take it to a test drive with ARHD GPE 3.0. I downloaded the latest RUU for my device (1.28.401.7) thinking I would need that to get back to stock. I went and unlocked the bootloader at HTC dev. Flashed CWM recovery and flashed ARHD GPE 3.0. Played around with it for a bit and now when I needed to go back to stock.
RUU.exe file got stuck at updating signature then returned 155 unknown. I realized maybe its attempting to downgrade the bootloader so i looked around for a 2.24.401.1 RUU but its not available yet.
I looked at Nandroid backups and found 1.28.401.7 HTC__001 but its UK unbranded. When I restored this version it loaded up but my touch screen didnt work at all. I flashed back ARHD to get touch capability back.
So my question is... Any chance anyone can nandroid backup the stock 2.24.401.1 i need? How can I go to stock now? Am I stuck with custom roms untill atleast s-off or HTC decides 2.24.401.1 RUU should be made available?
Thanks!
+1
Are you s off?? Downgrade your hboot to 1.44 and then flash the ruu for your device....
Sent from my HTC One using xda premium
No unfortunately im s-on... Funny how being a good boy and being s-on HTC rewards me with no option to go back to stock...
Sent from my HTC One using xda app-developers app
LOL............ I am in same postion . want to go back to stock for updates but cant !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
http://forum.xda-developers.com/showthread.php?t=2224752 ... Flash ROM, install stock recovery, relock bootloader, done. The official firmware will be about soon no doubt so you will be able to fastboot it and have the newest base, stock and all before HTC release it in whatever region.
Obviously you'll need S-Off for Hboot 1.54 if/when it happens in order to remove the tampered flag and change relocked back to locked but what I mentioned above is the closest you'll get without being able to run an RUU.
AllAboutTheCore said:
http://forum.xda-developers.com/showthread.php?t=2224752 ... Flash ROM, install stock recovery, relock bootloader, done. The official firmware will be about soon no doubt so you will be able to fastboot it and have the newest base, stock and all before HTC release it in whatever region.
Obviously you'll need S-Off for Hboot 1.54 if/when it happens in order to remove the tampered flag and change relocked back to locked but what I mentioned above is the closest you'll get without being able to run an RUU.
Click to expand...
Click to collapse
You cant s-off on hboot 154 yet. Unless I am mistaken.
Like op says we need a nandroid of firmware think that's only way until ruu is releasee ; (
Sent from my GT-I9100 using xda app-developers app
ipmanwck said:
You cant s-off on hboot 154 yet. Unless I am mistaken.
Like op says we need a nandroid of firmware think that's only way until ruu is releasee ; (
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
2 things:
1) I'll quote what I said, I never said S-Off was available .. "Obviously you'll need S-Off for Hboot 1.54 if/when it happens"
2) What I said above for going to stock is a way of doing it, a Nandroid is not the only way.
AllAboutTheCore said:
http://forum.xda-developers.com/showthread.php?t=2224752 ... Flash ROM, install stock recovery, relock bootloader, done. The official firmware will be about soon no doubt so you will be able to fastboot it and have the newest base, stock and all before HTC release it in whatever region.
Obviously you'll need S-Off for Hboot 1.54 if/when it happens in order to remove the tampered flag and change relocked back to locked but what I mentioned above is the closest you'll get without being able to run an RUU.
Click to expand...
Click to collapse
I actually did this and Im running it right now without problems...
But Im not sure id be getting OTAs as the bootloader main ver still says 2.24.401.1 and not 2.24.401.8. I dont think Mike made a 2.24.401.1 available.
Its a bit disappointing. Im fine with having my bootloader tampered and relocked and s-on as long as I got stock running like it should be. i dont understand why HTC gives you the option to unlock ur bootloader to play around with custom firmware but not allow you to go back to stock. im guessing the RUU is on the way but I have my doubts... Just like s-off.
Sent from my HTC One using xda app-developers app
ossman said:
I actually did this and Im running it right now without problems...
But Im not sure id be getting OTAs as the bootloader main ver still says 2.24.401.1 and not 2.24.401.8. I dont think Mike made a 2.24.401.1 available.
Its a bit disappointing. Im fine with having my bootloader tampered and relocked and s-on as long as I got stock running like it should be. i dont understand why HTC gives you the option to unlock ur bootloader to play around with custom firmware but not allow you to go back to stock. im guessing the RUU is on the way but I have my doubts... Just like s-off.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Nah, the stock firmware for 2.24.401.8 is not available yet, only a customised one which would require S-Off anyway. The method I mentioned is the only way at the moment to get as close to stock as possible without being able to go S-Off and flash an older RUU. When Mike gets hold of the stock firmware to post, I'm sure he will ... I can't see any 2.24 RUU's being available seeing that HTC are pushing for a 4.3 release by the end of September, so I'd wait anyways, unless you need to return your device for warranty purposes of course.
As for you getting OTA updates ... I haven't installed the .8 ROM but it shouldn't affect it as the base you are on is still an older base than what you'd be trying to update to but I'm not 100% on that as I haven't flashed it as my device is away for repair lol. I would imagine that the 2.24.401.8 firmware would be about soon enough and then you would be able to revert to stock with the newest base but obviously as you said yourself, without S-Off you wouldn't be able to wipe any trace of you flashing and modding.
I think HTC only allow you to unlock your bootloader because they can void so many warranties that way and bill for repairs lol ... Maybe I'm being cynical but I do agree that they could provide a stock RUU for people to return to stock, without all the hassle of S-Off or waiting months before any suitable RUU is available but sometimes you have to just suck it up and live with what we have lol
ossman said:
I got myself in a bit of a dead zone here.
I have my HTC one. Its HTC__001 WWE Europe. It OTA upgraded to 2.24.401.1.
When I saw that you can convert to a GPE I really wanted to check it out specially after users reported success in getting OTA updates. But I quickly realized I needed S-Off and thats not available yet.
I decided to at least take it to a test drive with ARHD GPE 3.0. I downloaded the latest RUU for my device (1.28.401.7) thinking I would need that to get back to stock. I went and unlocked the bootloader at HTC dev. Flashed CWM recovery and flashed ARHD GPE 3.0. Played around with it for a bit and now when I needed to go back to stock.
RUU.exe file got stuck at updating signature then returned 155 unknown. I realized maybe its attempting to downgrade the bootloader so i looked around for a 2.24.401.1 RUU but its not available yet.
I looked at Nandroid backups and found 1.28.401.7 HTC__001 but its UK unbranded. When I restored this version it loaded up but my touch screen didnt work at all. I flashed back ARHD to get touch capability back.
So my question is... Any chance anyone can nandroid backup the stock 2.24.401.1 i need? How can I go to stock now? Am I stuck with custom roms untill atleast s-off or HTC decides 2.24.401.1 RUU should be made available?
Thanks!
Click to expand...
Click to collapse
i got an nandroid backup for you fully stock unrooted : https://mega.co.nz/#!AUZGkKwC!EAfhUXYAgjpAR42jGzG_mhzWJjwcs1j7R_tm_HPMDAo
So I'm trying to flash a new RUU for GPE HTC One Jelly Bean 4.3. The RUU is suppose to work for unlocked devices; the person who posted the download links had two, with one for unlocked devices and the other for locked devices. I think I messed up somewhere because I had a custom kernel installed via .zip, then booted back to the stock GPE kernel with "fastboot flash boot boot.img"; the system booted up fine but the 3 dot menu was missing so I went back to the customer kernel. The system wouldn't get past the Google screen and now I'm trying to flash the RUU but it won't work. If I do it on my computer via commands, I get "<bootloader> zip info parsing," then "FAILED <remote: 99 unknown fail>". So now I'm in TWRP recovery with the RUU on my SD card; tried flashing it on my phone and it says "Updating partition details...", "E: unable to mount ' /data'", "E: unable to mount internal storage", E: unable to mount ' /data," then lastly "Error flashing zip." I wiped the cache, data, and system; it won't wipe the Dalvik cache and gives me the same error when I do it. Can someone help me?
Edit: When I also try to wipe via "fastboot -w" it comes up with an error saying "FAILED <remote: not allowed>.
You need S-off to ruu to another firmware that's not made for your particular model/carrier.
Once you s-off enter fastboot oem rebootRUU
fastboot flash zip firmware.zip
(Firmware.zip being the actually name of the ruu zip)
It will begin to flash, then fail and say to flush image immediately. Simply press the "up" arrow on keyboard to repeat the exact same command. It will work the second time.
For some reason fastbooting a ruu in that mode always fails the first time, so you have to do it twice without exiting.
Good luck and enjoy
Sent from my HTC One using Tapatalk 2
InflatedTitan said:
You need S-off to ruu to another firmware that's not made for your particular model/carrier.
Once you s-off enter fastboot oem rebootRUU
fastboot flash zip firmware.zip
(Firmware.zip being the actually name of the ruu zip)
It will begin to flash, then fail and say to flush image immediately. Simply press the "up" arrow on keyboard to repeat the exact same command. It will work the second time.
For some reason fastbooting a ruu in that mode always fails the first time, so you have to do it twice without exiting.
Good luck and enjoy
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
I think the GPE RUU supports MID: PN0713000 and CID: T-MOB010. http://forum.xda-developers.com/showthread.php?t=2358781
Edit: Oh, never mind; it says S-Off needed...
Any advice on what to do now since my HBoot is 1.54? The HBoot for the latest T-Mobile Sense 5 RUU is 1.44... I'm stuck now...
May be the alcohol but I'm having trouble keeping up lol. You're having questions with the hboot trying to s-off? If you can't s-off, nor ruu BC the firmware doesn't match with the most recent ruu then you may be stuck or hopefully someone with more advanced knowledge can help you a little better
Sent from my HTC One using Tapatalk 2
yorkies88888 said:
I think the GPE RUU supports MID: PN0713000 and CID: T-MOB010. http://forum.xda-developers.com/showthread.php?t=2358781
Edit: Oh, never mind; it says S-Off needed...
Any advice on what to do now since my HBoot is 1.54? The HBoot for the latest T-Mobile Sense 5 RUU is 1.44... I'm stuck now...
Click to expand...
Click to collapse
For some reason Google firmware will flash on certain s-on phones when it shouldn't. First we need to know if this happened.
When booted into the boot loader, is the screen black or white?
Now if there's an RUU available for your cid and mid (an official ruu.exe not an unsigned zip) that is greater than the firmware version currently on the phone, flashing that will fix everything.
If not, head over to original android development and grab a GPE ROM ( you could also use sense or AOSP, but I'm assuming you want GPe) and attempt to flash the ROM in recovery just like you normally would.
AT&T HTC M7ul
Baad Newz's InsertCoin 3.4-2
Flar2's Bulletproof 6.2
CoryTallman said:
For some reason Google firmware will flash on certain s-on phones when it shouldn't. First we need to know if this happened.
When booted into the boot loader, is the screen black or white?
Now if there's an RUU available for your cid and mid (an official ruu.exe not an unsigned zip) that is greater than the firmware version currently on the phone, flashing that will fix everything.
If not, head over to original android development and grab a GPE ROM ( you could also use sense or AOSP, but I'm assuming you want GPe) and attempt to flash the ROM in recovery just like you normally would.
AT&T HTC M7ul
Baad Newz's InsertCoin 3.4-2
Flar2's Bulletproof 6.2
Click to expand...
Click to collapse
So basically I accidentally put security back on BEFORE flashing back to stock so now I'm stuck here. The bootloader screen is black and since I upgraded to HBoot 1.54 via OTA update for stock Jelly Bean when I was S-Off, there is no compatible HBoot for me since the one for T-Mobile is 1.44 currently. My biggest worries right now is that I screwed something up with the partitions or if there's a bigger issue here because it's saying it can't mount the data and SD card, and I can't even wipe the phone via commands. If it's just the CID, MID, and HBoot not matching, then I'm not worried since I can still flash a custom ROM right?
yorkies88888 said:
So basically I accidentally put security back on BEFORE flashing back to stock so now I'm stuck here. The bootloader screen is black and since I upgraded to HBoot 1.54 via OTA update for stock Jelly Bean when I was S-Off, there is no compatible HBoot for me since the one for T-Mobile is 1.44 currently. My biggest worries right now is that I screwed something up with the partitions or if there's a bigger issue here because it's saying it can't mount the data and SD card, and I can't even wipe the phone via commands. If it's just the CID, MID, and HBoot not matching, then I'm not worried since I can still flash a custom ROM right?
Click to expand...
Click to collapse
This is why going back to s-on is almost always a bad idea. You can't flash any unsigned RUUs or firmware packages now, so you can't return your phone to stock.
It sounds like you may have corrupted your sdcard during all this. Try reformatting it from your PC. This will wipe all your data, but if it's corrupted, it's gone anyway. Then you can push a new rom and kernel and flash.
here is the latest signed RUU for TMOB.
http://forum.xda-developers.com/showthread.php?t=2427325
wwjdd44 said:
here is the latest signed RUU for TMOB.
http://forum.xda-developers.com/showthread.php?t=2427325
Click to expand...
Click to collapse
It's of no use to him; he can't run it because he's on 1.54 and s-on.
iElvis said:
This is why going back to s-on is almost always a bad idea. You can't flash any unsigned RUUs or firmware packages now, so you can't return your phone to stock.
It sounds like you may have corrupted your sdcard during all this. Try reformatting it from your PC. This will wipe all your data, but if it's corrupted, it's gone anyway. Then you can push a new rom and kernel and flash.
Click to expand...
Click to collapse
So even if T-Mobile releases an RUU with HBoot 1.54, I can't go back to stock? And how do I reformat it on my PC? CMD? And can you recommend me a ROM that's closest to stock Sense 5? And do I flash the ROM first or the kernel? Sorry about all the questions; I'm just freaking out right now.
yorkies88888 said:
So even if T-Mobile releases an RUU with HBoot 1.54, I can't go back to stock? And how do I reformat it on my PC? CMD? And can you recommend me a ROM that's closest to stock Sense 5? And do I flash the ROM first or the kernel? Sorry about all the questions; I'm just freaking out right now.
Click to expand...
Click to collapse
You still have an unlocked bootloader right?
Then I would just flash a custom recovery and "format sdcard" from there.
Then "adb push Rom.zip /sdcard/" (or sideload) and flash the Rom.
I personally use ARHD 13.x which is very close to stock Sense 5.
ROMs already include a kernel, so no need to flash separately.
Sent from my HTC One using xda app-developers app
nkk71 said:
You still have an unlocked bootloader right?
Then I would just flash a custom recovery and "format sdcard" from there.
Then "adb push Rom.zip /sdcard/" (or sideload) and flash the Rom.
I personally use ARHD 13.x which is very close to stock Sense 5.
ROMs already include a kernel, so no need to flash separately.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yes, I have an unlocked bootloader but TWRP doesn't seem to have a "format SD card" option.
Edit: And do you know if it's still possible to use the T-Mobile RUU when they come out with Jelly Bean 4.3 update with HBoot 1.54? Or am I just stuck with custom ROMS now?
yorkies88888 said:
Yes, I have an unlocked bootloader but TWRP doesn't seem to have a "format SD card" option.
Click to expand...
Click to collapse
I haven't used TWRP, but I'm sure it's there somewhere. Usually under advanced.
Might be called something else? What format options does TWRP have? Maybe /data/media
Sent from my HTC One using xda app-developers app
nkk71 said:
I haven't used TWRP, but I'm sure it's there somewhere. Usually under advanced.
Might be called something else? What format options does TWRP have? Maybe /data/media
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Oh, I found it! Thanks! Woot! Do you recommend ARHD 13.x or 21.x?
yorkies88888 said:
Oh, I found it! Thanks! Woot! Do you recommend ARHD 13.x or 21.x?
Click to expand...
Click to collapse
Personal preference. Why don't you try both. 13.x is based on official 4.2.2 and 21.x is based on leaked 4.3 (but still very good)
Just note on 21.0 you have to enter APN settings manually to get mobile data & mms, and there's a bug which won't let you access SIM card contacts.
Sent from my HTC One using xda app-developers app
nkk71 said:
Personal preference. Why don't you try both. 13.x is based on official 4.2.2 and 21.x is based on leaked 4.3 (but still very good)
Just note on 21.0 you have to enter APN settings manually to get mobile data & mms, and there's a bug which won't let you access SIM card contacts.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Well is 13.x compatible with HBoot 1.54? And I have Google's bootloader and when I boot up the phone it has a Google logo on it; will it be able to install and get rid of the Google logo and bootloader? Thanks for the help by the way; I finally got past the corrupt files.
yorkies88888 said:
Edit: And do you know if it's still possible to use the T-Mobile RUU when they come out with Jelly Bean 4.3 update with HBoot 1.54? Or am I just stuck with custom ROMS now?
Click to expand...
Click to collapse
You can't use unsigned RUUs. If T-Mo releases a RUU with 1.54 or later hboot, then yes, you should be able to use it (unless you changed your MID or CID).
yorkies88888 said:
Well is 13.x compatible with HBoot 1.54? And I have Google's bootloader and when I boot up the phone it has a Google logo on it; will it be able to install and get rid of the Google logo and bootloader? Thanks for the help by the way; I finally got past the corrupt files.
Click to expand...
Click to collapse
Yes it is, but you're stuck with the Google bootloader for now, until there is an s-off exploit for 1.54 or T-Mo releases that RUU.
yorkies88888 said:
Well is 13.x compatible with HBoot 1.54? And I have Google's bootloader and when I boot up the phone it has a Google logo on it; will it be able to install and get rid of the Google logo and bootloader? Thanks for the help by the way; I finally got past the corrupt files.
Click to expand...
Click to collapse
It is compatible with 1.54, but I've never tried GPe, so I can't answer that. Don't know if it is firmware, ROM related, or if GPe hboot is different.
Can someone pitch in?
Sent from my HTC One using xda app-developers app
iElvis said:
You can't use unsigned RUUs. If T-Mo releases a RUU with 1.54 or later hboot, then yes, you should be able to use it (unless you changed your MID or CID).
Yes it is, but you're stuck with the Google bootloader for now, until there is an s-off exploit for 1.54 or T-Mo releases that RUU.
Click to expand...
Click to collapse
nkk71 said:
It is compatible with 1.54, but I've never tried GPe, so I can't answer that. Don't know if it is firmware, ROM related, or if GPe hboot is different.
Can someone pitch in?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Well it's a good thing I changed my CID back to T-MOB010 before I put security back on then... I had SuperCID so not like it would've mattered... But thanks for the good news! And the GPE ARHD is compatible because it's Jelly Bean 4.3, but would flashing the ARHD 13.x ROM change the bootloader and start-up screen to HTC instead of Google?
yorkies88888 said:
Well it's a good thing I changed my CID back to T-MOB010 before I put security back on then... I had SuperCID so not like it would've mattered... But thanks for the good news! And the GPE ARHD is compatible because it's Jelly Bean 4.3, but would flashing the ARHD 13.x ROM change the bootloader and start-up screen to HTC instead of Google?
Click to expand...
Click to collapse
No. No rom will change your bootloader or splash screen. You need s-off to do that.
Hi, I want to get 3.22 firmware and 4.3.
So, i'm planning to go back to stock by using recovery mode (odexed) by mike1986's guide.
http://forum.xda-developers.com/showthread.php?t=2265618
Then, after going to stock, i would update through HTC OTA to get the 3.22 firmware.. would this work?
By the way, I'm s-on with 1.54 hboot, so i think the only way for me to get the latest firmware(3.22) is through HTC OTA update in the stock rom.
Thanks everybody!!
Anyone? will this work?
If you're just going to flash a custom ROM and kernel, why are you trying to get the OTA?
Sent from my HTC One using XDA Premium 4 mobile app
so I could get 3.22 firmware? haha does that make sense?
Is there anyway that I can get 3.22 firmware with s-on and 1.54 hboot?
rainierzam said:
so I could get 3.22 firmware? haha does that make sense?
Is there anyway that I can get 3.22 firmware with s-on and 1.54 hboot?
Click to expand...
Click to collapse
Nope, only through official stock updates afaik...
But yeah, I think you're steps are right:
1. Restore stock nandroid backup
2. Restore stock recovery
3. Re-lock the device using (I believe) fastboot...
But not completely sure myself still either...
I'm also wondering how to go back to stock. HBoot 1.54, S-on. Im on .206 so the first method wont work for me I think. I can't find a decent tutorial. Still quite noobish when it comes to this stuff
Hi guys,
I am the same, S-ON with hboot 1.54 ,, and all I want to do is to get the last update firmware , as I understand it is something that can't be flashed with a ROM like ARHD 22 so what are the right steps please. and what are the risks if there is any.
thanks.
It seems this is the way:
1. Restore stock rom/nandroid backup
2. Restore stock recovery
3. Relock the bootloader using fastboot, with this command: fastboot oem lock
That SHOULD be it I think,
Should I get the odexed of v4.1.2 1.29.1540.17 then wait for the htc one update in the phone to get the 3.22 firmware?
rainierzam said:
Should I get the odexed of v4.1.2 1.29.1540.17 then wait for the htc one update in the phone to get the 3.22 firmware?
Click to expand...
Click to collapse
I've been asking myself the same questions today and researched about it, then made this post for clarification http://forum.xda-developers.com/showthread.php?t=2462048
Basically, afaik I'm running 3.22 having updated from 3.17 (Maximus HD 13.0) to 3.22 (Maximus HD 14.0) via OTA. I also have and always have had hboot 1.54 and S-On
Ah, you're looking for the firmware upgrade. When I flashed the 1.29.1540.16 RUU to grab the update and get a system dump I had to downgrade my firmware and hboot in order to get the RUU to flash. I'm s-off and I was on GPe firmware, so this may not pertain to anyone in this thread.
I believe the stock nandroid and recovery would be the only way to go for s-on devices. If you're already on the latest firmware (prior to the new 4.3 OTA) and hboot, there isn't a newer RUU yet. And since you can't downgrade due to s-on, you'll have to use a nandroid and flash a stock recovery.
I may be completely wrong, so please correct me if I am.
Sent from my HTC One using XDA Premium 4 mobile app
CoryTallman said:
Ah, you're looking for the firmware upgrade. When I flashed the 1.29.1540.16 RUU to grab the update and get a system dump I had to downgrade my firmware and hboot in order to get the RUU to flash. I'm s-off and I was on GPe firmware, so this may not pertain to anyone in this thread.
I believe the stock nandroid and recovery would be the only way to go for s-on devices. If you're already on the latest firmware (prior to the new 4.3 OTA) and hboot, there isn't a newer RUU yet. And since you can't downgrade due to s-on, you'll have to use a nandroid and flash a stock recovery.
I may be completely wrong, so please correct me if I am.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was under the same impression, but as it turns out 'build number' in your Settings/About/Software/More IS the firmware version, and mine is 3.22.1540, and I don't have S-On, I have hboot 1.54 and I just did an OTA from a custom rom on base 3.17 to the one on 3.22
ieldra said:
I was under the same impression, but as it turns out 'build number' in your Settings/About/Software/More IS the firmware version, and mine is 3.22.1540, and I don't have S-On, I have hboot 1.54 and I just did an OTA from a custom rom on base 3.17 to the one on 3.22
Click to expand...
Click to collapse
So it was the official OTA from HTC, or an OTA that the developer of the custom rom pushed out?
But if you have S-off you could just downgrade, RUU, then receive the OTA anyway, so it doesn't really apply.
Sent from my HTC One using XDA Premium 4 mobile app
CoryTallman said:
So it was the official OTA from HTC, or an OTA that the developer of the custom rom pushed out?
But if you have S-off you could just downgrade, RUU, then receive the OTA anyway, so it doesn't really apply.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Custom developer, but I still am running the latest firmware am I not? Only thing I am uncertain about is whether the baseband version corresponds to the one on 3.22, and why does it say "OS-2.24.901.1" on my bootloader
ieldra said:
Custom developer, but I still am running the latest firmware am I not? Only thing I am uncertain about is whether the baseband version corresponds to the one on 3.22, and why does it say "OS-2.24.901.1" on my bootloader
Click to expand...
Click to collapse
OTA's from dev's will not include firmware. The version you are seeing in the setting menu is the version listed in the build.prop, it isn't actually showing the devices firmware version.
Sent from my HTC One using XDA Premium 4 mobile app
CoryTallman said:
OTA's from dev's will not include firmware. The version you are seeing in the setting menu is the version listed in the build.prop, it isn't actually showing the devices firmware version.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So having S-On, hboot 1.54 and no recovery of my stock android, what can I do to update my firmware and radio ? My CID is CID_401, I can't find any RUUs or nandroid backs for it
Edit:I think I have a TWRP backup of my phone i made one day after buying it, although I think it is after I upgraded to 4.2.2 OTA (stock) and unlocked and rooted. However it should still be a stock backup. Will this help in anyway? (Note: I use CWM now)
ieldra said:
So having S-On, hboot 1.54 and no recovery of my stock android, what can I do to update my firmware and radio ? My CID is CID_401, I can't find any RUUs or nandroid backs for it
Edit:I think I have a TWRP backup of my phone i made one day after buying it, although I think it is after I upgraded to 4.2.2 OTA (stock) and unlocked and rooted. However it should still be a stock backup. Will this help in anyway? (Note: I use CWM now)
Click to expand...
Click to collapse
Radios are flashable in recovery.
The backup will work if you can find a stock recovery to flash, then relock the boot loader and receive OTA. If there's even an OTA for your CID yet.
Though the backup being rooted may cause the OTA to fail.
Sent from my HTC One using XDA Premium 4 mobile app
CoryTallman said:
Radios are flashable in recovery.
The backup will work if you can find a stock recovery to flash, then relock the boot loader and receive OTA. If there's even an OTA for your CID yet.
Though the backup being rooted may cause the OTA to fail.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
is the stock recovery CID dependent ? Also, can I not simply unroot if I am rooted?
ieldra said:
is the stock recovery CID dependent ? Also, can I not simply unroot if I am rooted?
Click to expand...
Click to collapse
These are questions I do not know the answers to. I'm one of the lucky ones with s-off, but hopefully someone more knowledgeable on the subject can help.
Sent from my HTC One using XDA Premium 4 mobile app
Hey, on returning to stock using stock recovery, could i use the odexed or de odexed version of 4.3 to get the 3.22 firmware? The rom is posted in the one android development. Coukd i use this instead of mike1986's stock rom?
Sent from my HTC One using Tapatalk 2
Hey,
I'm finding it really difficult to get a definitive answer on the following question. So I'm just going to ask: if my HTC One has been updated to 4.2.2 by my carrier, does this mean I cannot use moonshine or revone to turn S-off? I've been trying all morning and I've read that this might be the case? Which is a damn shame as I wanted stock android with those lovely OTA updates.
Cheers, Jav
JavLange said:
Hey,
I'm finding it really difficult to get a definitive answer on the following question. So I'm just going to ask: if my HTC One has been updated to 4.2.2 by my carrier, does this mean I cannot use moonshine or revone to turn S-off? I've been trying all morning and I've read that this might be the case? Which is a damn shame as I wanted stock android with those lovely OTA updates.
Cheers, Jav
Click to expand...
Click to collapse
If you updated using OTA your bootloader would have been updated to 1.54 (you can check by going to bootloader. POWER + VOL DOWN)
and revone or moonshine will not work on 1.54.
Sent from my HTC One using xda app-developers app
nkk71 said:
If you updated using OTA your bootloader would have been updated to 1.54 (you can check by going to bootloader. POWER + VOL DOWN)
and revone or moonshine will not work on 1.54.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Ah - that's what I was thinking. So there isn't a way to "convert" my own to a Google Play Edition until a new way to turn S-off is found?
Thanks for your help - it's good to have clarity! =)
You can flash a GE rom based.
But you can't receive the OTA from htc
You need the s-off for the full convert to GE edition
JavLange said:
Ah - that's what I was thinking. So there isn't a way to "convert" my own to a Google Play Edition until a new way to turn S-off is found?
Thanks for your help - it's good to have clarity! =)
Click to expand...
Click to collapse
What do you mean by convert? If you mean flashing different ROMs, then you can use HTCdev to unlock your bootloader, and flash different ROMs, Radios, and kernels.
It will show your bootloader as TAMPERED and and UNLOCKED / RELOCKED (ie never again simply LOCKED). And you will loose OTA capability unless u go back to stock ROM and recovery and relock.
You will also not be able to flash unsigned firmware.
If you do decide to unlock, make a nandroid backup of your stock ROM before flashing anything new, so that you can always go back to stock ROM for OTAs.
Sent from my HTC One using xda app-developers app
nkk71 said:
What do you mean by convert? If you mean flashing different ROMs, then you can use HTCdev to unlock your bootloader, and flash different ROMs, Radios, and kernels.
It will show your bootloader as TAMPERED and and UNLOCKED / RELOCKED (ie never again simply LOCKED). And you will loose OTA capability unless u go back to stock ROM and recovery and relock.
You will also not be able to flash unsigned firmware.
If you do decide to unlock, make a nandroid backup of your stock ROM before flashing anything new, so that you can always go back to stock ROM for OTAs.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
He means this
The full convert to GE Phone.
Guich said:
He means this
The full convert to GE Phone.
Click to expand...
Click to collapse
I do =)
So to make it all legit, I'd have to somehow revert my bootloader back to a version that supported turning S-off? I'm pretty sure that's beyond my feeble skills!
Never mind then - cheers all =)
Guich said:
He means this
The full convert to GE Phone.
Click to expand...
Click to collapse
But he could still use a GPe ROM, right? He wouldn't get the black bootloader or GOOGL001 CID, but the custom GPe ROMs out there would give him GPe experience.
Or am I missing something?
Sent from my HTC One using xda app-developers app
JavLange said:
I do =)
So to make it all legit, I'd have to somehow revert my bootloader back to a version that supported turning S-off? I'm pretty sure that's beyond my feeble skills!
Never mind then - cheers all =)
Click to expand...
Click to collapse
You can't downgrade the hboot for acheive the s-off...
nkk71 said:
But he could still use a GPe ROM, right? He wouldn't get the black bootloader or GOOGL001 CID, but the custom GPe ROMs out there would give him GPe experience.
Or am I missing something?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yes, he can.
But if he will have the ota from htc/google of the ge he need the s-off
He can usa a GE based rom.
Sent from One with XDAHoloApp
Guich said:
You can't downgrade the hboot for acheive the s-off...
Yes, he can.
But if he will have the ota from htc/google of the ge he need the s-off
He can usa a GE based rom.
Sent from One with XDAHoloApp
Click to expand...
Click to collapse
Oh I see! So the best I can do is install the RUU from this and manually keep my phone up to date thereafter?
JavLange said:
Oh I see! So the best I can do is install the RUU from this and manually keep my phone up to date thereafter?
Click to expand...
Click to collapse
Not an RUU, a custom ROM.
You would have to
1- unlock bootloader using HTCdev (will completely wipe your phone)
2- install custom recovery (CWM or TWRP)
3- make a nandroid backup of your stock ROM for the future
4- flash a GPe ROM from the development thread
That's it in a nutshell.
You will need your stock ROM and stock recovery later to get your official OTA, because that will be the only way to update your firmware. Everything else is pretty much covered in the custom ROMs out there.
I recommend reading the guides to familiarize yourself with the procedures.
I personally am on ARHD Sense 5 ROM, but there's also a GPe version, as well as others of course. Read a bit through these threads to get a "feeling" about them.
Sent from my HTC One using xda app-developers app
I have a rooted htc one m8 hk edition with S-On, I would like to install the new update that sprint rolled out so I was thinking about using the RUU from another thread here. My question is, since I have the HK edition can i install the RUU without S-Off? I noticed that SuperCID was required for the non hk version only and was not required for my version. Is this correct? Also will the RUU return me to 100% stock? I couldn't post this in the RUU thread itself due to being new to xda, sorry for the inconvenience. Thanks!
cristhefur said:
I have a rooted htc one m8 hk edition with S-On, I would like to install the new update that sprint rolled out so I was thinking about using the RUU from another thread here. My question is, since I have the HK edition can i install the RUU without S-Off? I noticed that SuperCID was required for the non hk version only and was not required for my version. Is this correct? Also will the RUU return me to 100% stock? I couldn't post this in the RUU thread itself due to being new to xda, sorry for the inconvenience. Thanks!
Click to expand...
Click to collapse
You can use the RUU with S-ON as long as it is not an older version than what is already on your phone - I believe you are probably talking about 1.54.654.9 right? Check the about settings on your phone to see if you have upgraded from that (1.54.654.13 or 1.54.654.15 or the 2.16 something).
If the phone version is newer, you will not be able to use the RUU without S-OFF. Since you actually have the HK version, you will not need to change your CID. Successfully running the RUU will flash all the major partions, radios, and more and will bring you completely back to stock. It will also wipe your data/media partition (internal SC card) so make sure you backup anything you need to keep.
Thank you so much for your response it was exactly what I needed. If I wanted to remove the tampered flag could I do it before flashing the RUU? Or will that get removed along with the root in the process? Thanks again!
Sent from my 831C using XDA Free mobile app
cristhefur said:
Thank you so much for your response it was exactly what I needed. If I wanted to remove the tampered flag could I do it before flashing the RUU? Or will that get removed along with the root in the process? Thanks again!
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
The RUU will actually remove the TAMPERED banner because that flag is in mmcblk0p6, named "pg2fs", which is one of the images that the RUU overwrites. UNLOCKED, if you have it, will remain because that flag is mmcblk0p2, named "pg1fs" which does not get overwritten by the RUU. It can be removed by hex editing that block with an echo command http://forum.xda-developers.com/showthread.php?t=2708571
If you are already unlocked, rooted, and have version 1.54.654.9, I would highly suggest you run sunshine and get S-OFF before you run the RUU and update the OTAs; who knows if that exploit will be blocked in further updates.
I see, I'm running 1.54.654.15...can I still s-off with sunshine?
Sent from my 831C using XDA Free mobile app
cristhefur said:
I see, I'm running 1.54.654.15...can I still s-off with sunshine?
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
Not sure since I did it on .9, but I would definitely try it - in fact, if you are on 15, the only way you will be able to run the .9 RUU is if you S-OFF.
Sunshine will not ask you to pay until it has run compatibility tests and verified that it can get S-OFF on your phone - so run it and if you see the message to pay, you are good to go. Having S-OFF just makes things SO much easier.
Just follow the directions on the sunshine site http://theroot.ninja/ and run it entirely from the phone; couldn't be easier. You will need to sideload the APK, easiest if you just run the command "adb install SunShine-latest.apk" after making sure Unknown Sources is checked in your phone settings.
Wait a sec, I thought you said I could use the RUU as long as it was of an older version than the one I currently had..so I was thinking about the .9 RUU since I am on .15... That actually wouldn't work? Sorry I'm a bit confused.
Sent from my 831C using XDA Free mobile app
cristhefur said:
Wait a sec, I thought you said I could use the RUU as long as it was of an older version than the one I currently had..so I was thinking about the .9 RUU since I am on .15... That actually wouldn't work? Sorry I'm a bit confused.
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
It's the other way around - look a few posts up - there's a "not older than your phone's version" in front of that statement.
To be clear, the .9 RUU will not work on a .15 phone if you are S-ON, you must be S-OFF to do that. However, if you had a .15 RUU (which doesn't exist) it would work on a .9 phone.
Sorry about the confusion. That is just one of the benefits of being S-OFF (not to get sidetracked but my favorite benefit is being able to flash from hboot or fastboot rebootRUU with the bootloader locked)
Ah yes, I see that now- my mistake. I guess I'll s-off tomorrow afternoon then. Thank you very much for your help!
Sent from my 831C using XDA Free mobile app
It's encouraging that the Sunshine devs recently made fixes to deal with Sprint 4.4.3 M8 devices - that's version 2.16.654.4 which is higher than yours, so I think you have a good chance of success. Good luck!
Are you sure that it wouldn't work on a phone that is already updated to a newer software?
I have been on the previous version (final 4.4.2 version), and I have certainly used the RUU to flash back to the .9 version. To my knowledge, the RUU should work regardless of which version that your phone is running. If you're S-On, you just have to be locked & using the stock recovery.
AarSyl said:
Are you sure that it wouldn't work on a phone that is already updated to a newer software?
I have been on the previous version (final 4.4.2 version), and I have certainly used the RUU to flash back to the .9 version. To my knowledge, the RUU should work regardless of which version that your phone is running. If you're S-On, you just have to be locked & using the stock recovery.
Click to expand...
Click to collapse
I'm fairly certain that if you're S-on you can only run a RUU with the same software & firmware version that's installed on the phone. It was that way on the EVO LTE and I'm fairly certain that's how it is now.
Sent from my HTC M8
you may want to try http://firewater-soff.com/ first, if nogo, then sunshine
AarSyl said:
Are you sure that it wouldn't work on a phone that is already updated to a newer software?
I have been on the previous version (final 4.4.2 version), and I have certainly used the RUU to flash back to the .9 version. To my knowledge, the RUU should work regardless of which version that your phone is running. If you're S-On, you just have to be locked & using the stock recovery.
Click to expand...
Click to collapse
nope, you can't flash a older RUU if you're s-on
Oh ok...my apologies.
Is there a reason that my phone boots directly into the bootloader every time that I relock it?
I am unable to boot into anything after using fastboot oem lock, and it only loads the bootloader until I run the RUU (granted, this was before the latest update).
So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?
neudof said:
So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?
Click to expand...
Click to collapse
The red triangle is indicative of the stock recovery, which was updated with everything else when you did the OTA. Being S-ON with SuperSU means you must have been UNLOCKED at one point - if you are still are UNLOCKED, simply flash custom recovery back onto your device. If not UNLOCKED (if you relocked for the OTA, which is not necessary if S-OFF, not sure about S-ON), you will need to HTCDEV unlock again before flashing the custom recovery.
PillowMetal said:
The red triangle is indicative of the stock recovery, which was updated with everything else when you did the OTA. Being S-ON with SuperSU means you must have been UNLOCKED at one point - if you are still are UNLOCKED, simply flash custom recovery back onto your device. If not UNLOCKED (if you relocked for the OTA, which is not necessary if S-OFF, not sure about S-ON), you will need to HTCDEV unlock again before flashing the custom recovery.
Click to expand...
Click to collapse
Is it possible to flash the recovery from SD card or do I need to use my computer?
neudof said:
Is it possible to flash the recovery from SD card or do I need to use my computer?
Click to expand...
Click to collapse
When you download say TWRP from their webiste, you get an image file (IMG) that is meant to be flashed using fastboot from your computer. But you can rename it to "recovery.img", place that in a zip file along with an android.txt file with specific contents onto your external SD Card, and then you can flash it from the bootloader (if you are S-OFF). The file has to be specifically named as well - e.g., the Sprint HTC One M8 is "0P6BIMG.zip".
If you don't have an external SD Card, you may also be able to flash from the bootloader using a powered USB-OTG cable (like we did on the M7). Again, this is only if you are S-OFF, otherwise you will have to fastboot flash the image from your computer because bootloader flashes with S-ON have to be signed.
One last method that doesn't require S-OFF, is to copy the image file anywhere on internal or external SD cards, then use the "dd" command to copy the image over your recovery block (specific numeric device block depending on phone) using either your computer or a terminal emulator on the phone.
So yeah, you have options.
Update: I achieved S-Off as suggested, locked my boot loader using an adb command from another thread then ran the HK .9 RUU. I went through the 3 updates then took the phone to sprint, had no problems at all. Thanks for your help guys. :thumbup: