I'm a noob so go easy. My wife has a stock HTC one and I'm rooted with s-off running viper rom. Recently there was an OTA radio update. My question is, can I pull the radio from my wife's stock ONE and push it to my Viper ONE? If so, can someone give me the ADB commands....
Kyle
copekyle said:
I'm a noob so go easy. My wife has a stock HTC one and I'm rooted with s-off running viper rom. Recently there was an OTA radio update. My question is, can I pull the radio from my wife's stock ONE and push it to my Viper ONE? If so, can someone give me the ADB commands....
Kyle
Click to expand...
Click to collapse
Check the general thread.
Edit, general development
Sent from Taptalk on HTC One on some awesome custom Rom!
avwheeler said:
Check the general thread.
Edit, general development
Sent from Taptalk on HTC One on some awesome custom Rom!
Click to expand...
Click to collapse
I've been there and I'm guessing you're referring to this thread.
Sprint One Stock 1.31.651.2 Rooted / Unrooted / Firmware / OTA Package
I've been through that whole thread and no one gives an answer to my question. All I want is the radio, someone said they tried a radio update with adb but didn't think it worked and no one gave a yes or no whether or not that would work. That's what I'm asking in the Q&A forum.
copekyle said:
I've been there and I'm guessing you're referring to this thread.
Sprint One Stock 1.31.651.2 Rooted / Unrooted / Firmware / OTA Package
I've been through that whole thread and no one gives an answer to my question. All I want is the radio, someone said they tried a radio update with adb but didn't think it worked and no one gave a yes or no whether or not that would work. That's what I'm asking in the Q&A forum.
Click to expand...
Click to collapse
I think you need to fastboot one of the provided zips, there was reference they are signed. The s-off without the bootimg and hoot were no issues for me, think if you exclude the other stuff in that one, it will work, but might set up for an issue on next update. More will come the next few days, better to wait until ironed out, usually there are a few that brick until the firmware is better understood.
Anyway, the soff, no hoot, no bootimg did not cause any issues, extra flashes, or having to reload rom.
Sent from Taptalk on HTC One on some awesome custom Rom!
It's not fastboot per se, I'm pretty sure you have to flash new radios on the One with the RUU command (which I can't remember for the life of me, I think it's fastboot rebootRUU and then you can flash radio).
You have to flash one of the firmware zips and then either restore your backup, reflash the rom, or reflash your kernel if you have any problems - not sure if an early problem was resolved from just flashing the firmware
Sent from my HTCONE using xda app-developers app
copekyle said:
I'm a noob so go easy. My wife has a stock HTC one and I'm rooted with s-off running viper rom. Recently there was an OTA radio update. My question is, can I pull the radio from my wife's stock ONE and push it to my Viper ONE? If so, can someone give me the ADB commands....
Kyle
Click to expand...
Click to collapse
I just used the revone s-off method and flashed the s-off firmware zip. Gives the new radio and leaves the boot components intact. Viper rom still running flawlessly with no need to wipe or reload anything.
Tardeaux said:
I just used the revone s-off method and flashed the s-off firmware zip. Gives the new radio and leaves the boot components intact. Viper rom still running flawlessly with no need to wipe or reload anything.
Click to expand...
Click to collapse
I too simply flashed the s-off firmware for the radio using: fastboot rebootRUU then fastboot flash "firmware".zip. End result got the new radio and nothing else was altered. I am running eclipticone Rom 3.7
Sent from my jacked HTC One!!
did you guys have to re lock your boot loader? because i keep getting an error when trying the fastboot flash zip firmware.zip command
Jahspree said:
did you guys have to re lock your boot loader? because i keep getting an error when trying the fastboot flash zip firmware.zip command
Click to expand...
Click to collapse
No. Just make sure you are using the firmware for S-Off not the regular one.
raptoro07 said:
No. Just make sure you are using the firmware for S-Off not the regular one.
Click to expand...
Click to collapse
No you don't want to relock just make sure you get the correct firmware for s-off users, and you obviously must be s-off then flash in fastboot. fastboot oem rebootRUU then fastboot flash zip "firmware".zip
Sent from my jacked HTC One!!
Related
I just got a HTC vivid from a friend .first thing I did is unlock bootloader flash recovery s-off root . Phone is running gb . Here is where I need your help.I try to.flash jb Rom and it would boot. And when I touch screen phone would freeze and reboot.so I restore. What do I have to do to run jellybean ?
Sent from my HTC PH39100 using xda app-developers app
please read the stickies in the dev forum. in order to flash ics or jb you must flash the RUU if you are running gb. just flash the ics RUU and flash whatever jb rom you want after
ZeRo2o9 said:
please read the stickies in the dev forum. in order to flash ics or jb you must flash the RUU if you are running gb. just flash the ics RUU and flash whatever jb rom you want after
Click to expand...
Click to collapse
thanks!!
I'm having a similar problem, but i just dont find the right ICS RUU to flash it seems.
I live in austria, have the htc velocity 4g, with 2.3.7 gingerbread.
Bootloader tells me:
*** UNLOCKED ***
HOLIDAY PVT SHIP S-ON RL
HBOOT-1.85.0023
eMMC-boot
Feb 1 2012,01:02:37
what i did for now:
i unlocked the bootloader (with htcdev), put on the twrp-recovery (2.4.4.0) (with hasoons-tool) and also tried wcxrecovery.img (for BoRKed)
wiped it clear, installed the cm10 [cm-10-20130310-NIGHTLY-holiday] and gapps / later BoRKed
since i am s-on i ran the "fastboot flash boot boot.img" command.
And the result is the reboot-cycle (cyanogenmod10 - with freezing short after the pin-code / permanently rebooting with BoRKed).
I read through the forums and found out that i need a newer hboot (ICS) to be able to install Jellybean ROMS.
as mentioned before, i think that i should lock my bootload and flash the right ICS RUU like told in the vivid-developers-forum.
i tried out the htc_vivid_att_RUU_3.26.502.56_US.exe but it told me [error130] wrong model, so i couldnt finish the RUU.
the wire-trick for s-off is a little bit scary to me, so i didnt try that for the time being.
so, for the time being i am a little bit out of clues and would be very glad if somebody could help me out with the right version of the RUU i should flash (and where i could get it) or am i completely off track here?
thnx, joe
Don't you flash the boot.IMG before you flash the ROM?
HTC_Vivid said:
Don't you flash the boot.IMG before you flash the ROM?
Click to expand...
Click to collapse
the step-by-step written guide from hasoon2000 (link) tells me to do it after i installed the ROM.
Now go back and press install. Go to the folder where the ROM you downloaded, is located in. Select the ROM and slide the screen to flash it. After it flashes, press the back button. Press Reboot and Reboot into bootloader. Open the ROM you downloaded from your computer. You should see boot.img. Extract it to your computer. Open my toolkit and press Flash a Kernel. Locate the boot.img and it will flash it.
After it flashes, press reboot from the phone.
Congrats! Enjoy your fully working or borked ROM! Remember, DO NOT ASK FOR ETAs, DO NOT BUG/PM A DEV ABOUT UPDATES, and BE RESPECTFUL TO THE DEVELOPERS!
Click to expand...
Click to collapse
Don't use twrp 2.4.4...
Switch to 2.4.2.0
Sent from my Vivid 4G using Tapatalk 2
oh, but right now i found it just the other way around.... in the
[SUPERGUIDE] ICS-Root-Flash-Stock
(Optional) Flash a custom Kernel/Recovery (Three options, I suggest the THIRD)
*ATTENTION* IF FLASHING A KERNEL FOR A NEW ROM YOU WANT, YOU MUST FLASH THE ROM IMMEDIATELY AFTER FLASHING THE KERNEL WITHOUT BOOTING UP, THE KERNEL COMES FIRST. OTHERWISE, YOU MIGHT BOOT LOOP.
Click to expand...
Click to collapse
i will give it a try, thanks!
--
edit:
will switch to 2.4.2.0
kernel flash first and then rom (with trwp-2420 recovery) led to the same boot - freeze - cycle with cyanogenmod10 as described before...
i still think that i have to flash to an ICS RUU first, but i just need a working one (without the 130 model-id error)
Joehittn said:
kernel flash first and then rom with trwp-2420 recovery led to the same boot - freeze - cycle with cyanogenmod10 as described before...
i still think that i have to flash to an ICS RUU first, but i just need a working one (without the 130 model-id error)
Click to expand...
Click to collapse
The model id error is because you're trying to flash a Vivid RUU to a Velocity. You'll either need to s-off and super CID, then you can run whatever RUU you want, or you need to get the correct RUU for your device. I was pretty sure that 1.85.0023 and 1.85.0025 were bootloaders that came with ICS though. Maybe I'm remembering wrong about that, but I thought that the first ATT leak had .0023 and the official release had .0025
please run this (from fastboot USB) and reply back with the return
fastboot getvar mainver
(I have the Telstra ICS RUU uploading now if that's what you'll need)
Edit: Here is RUU_HOLIDAY_ICS_35_S_Telstra_WWE_3.25.841.4_Radio_3.02.4740.09_34.20.701040.19_release_246698_signed
Also - if you'd like to try this before any of that, it may work as well (others have had success). From fastboot USB:
fastboot erase cache
Now flash recovery, ROM, boot.img (from my experience, it doesn't matter if the boot.img is flashed before or after the ROM, as long as it's flashed BEFORE trying to actually boot the ROM)
(note that if the problem is your bootloader version, this won't work.)
homeslice976 said:
The model id error is because you're trying to flash a Vivid RUU to a Velocity. You'll either need to s-off and super CID, then you can run whatever RUU you want, or you need to get the correct RUU for your device. I was pretty sure that 1.85.0023 and 1.85.0025 were bootloaders that came with ICS though. Maybe I'm remembering wrong about that, but I thought that the first ATT leak had .0023 and the official release had .0025
please run this (from fastboot USB) and reply back with the return
fastboot getvar mainver
(I have the Telstra ICS RUU uploading now if that's what you'll need)
Edit: Here is RUU_HOLIDAY_ICS_35_S_Telstra_WWE_3.25.841.4_Radio_3.02.4740.09_34.20.701040.19_release_246698_signed
Also - if you'd like to try this before any of that, it may work as well (others have had success). From fastboot USB:
fastboot erase cache
Now flash recovery, ROM, boot.img (from my experience, it doesn't matter if the boot.img is flashed before or after the ROM, as long as it's flashed BEFORE trying to actually boot the ROM)
(note that if the problem is your bootloader version, this won't work.)
Click to expand...
Click to collapse
Camo has a ruu index too.. I think in dev thread
Sent from my HTC PH39100 using Tapatalk 2
mainver: (shows nothing...)
CID: VODAP120
i gave the telstra ruu you uploaded (thank you very much) a try, but it also gave me the model-id-error.
do i have to flash the recovery back (where do i find the stock-recovery? in the backup?), i am always using the twrp242-recovery now.
i tried the steps you wrote down with the same result (boot-cycle).
i think i will have to give the "s-off and super CID" as u mentioned before a try and then use the telstra-ruu. i read that this worked out for some guys in germany. i will do this on saturday, i need to be fully concentrated to do that, not next to work...
thank you very much for now!
One other thing.. you are relocking your bootloader before trying to run the ruu, and you're trying to run the ruu from fastboot?
Sent from my HTC PH39100 using Tapatalk 2
homeslice976 said:
One other thing.. you are relocking your bootloader before trying to run the ruu, and you're trying to run the ruu from fastboot?
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
yes, always relocked.
first i ran the RUU (telstra) from the gb-2.3.7 screen, now i tried it from fastboot.
same result - error 130 (model-id)
---------- Post added at 01:36 PM ---------- Previous post was at 01:16 PM ----------
XxSHaDoWxSLaYeRxX said:
Camo has a ruu index too.. I think in dev thread
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
I think you mean this thread [Collection] Stock Roms [3/25/13] but i cant find my provider (austria / a1 [telekom]) there. also there has been no OTA ICS launched in austria...
seems that i have to postpone the s-off, cant find the time to do it right now...
i will revive the thread when i finally went through it.
thanks for your help till now.
cyas
Hello all. First off, great resource here :cyclops:
I am currently trying to update my HTC One (AT&T) so that I can run the 4.3 Google Play Rom (it sticks on boot screen at the moment)
After that I tried to update firmware as seen here http://forum.xda-developers.com/showthread.php?t=2182823
(I am using model PN0712000 and CID CWS__001)
I have downloaded the appropriate file and followed the instructions but get stuck after step 6 "Type: fastboot oem rebootRUU and wait for device to reboot"
When I type the reboot command it boots to a black screen that just says "HTC" and sticks there. And I try to load the firmware it says "cannot load firmware.zip unknown error"
For reference the device is currently running a 4.2.2 rom (ends TBalden) if that matters
Any thoughts?
Thanks!
S-OFF? Unless you have a legit GE one, you'll have to be s-off to do it.
If you are, you'll need to delete the zip you are trying to flash in fastboot, reboot comp and try a fresh download.
Also id personally say run the command
fastboot oem writecid 11111111
after you have s-off
EDIT: failed to see that you are att... You'll only be able to ruu to the Cingular ruu without s-off. I can't tell which stock firmware you linked as it brought me to some random post in that thread lol
Sent from my One using Tapatalk 2
InflatedTitan said:
S-OFF? Unless you have a legit GE one, you'll have to be s-off to do it.
If you are, you'll need to delete the zip you are trying to flash in fastboot, reboot comp and try a fresh download.
Also id personally say run the command
fastboot oem writecid 11111111
after you have s-off
Sent from my One using Tapatalk 2
Click to expand...
Click to collapse
Oh I missed that detail. S-On at the moment. Based upon my limited tenure with rooting and my understanding of the potential flops in S-OFF I will probably stay away from anything that requires that (for the time being at least).
Is there some reason that I can install the 4.2.2 Rom but this 4.3 and Bigxie 4.3 both fail? Do they require firmware change? Something else I'm missing? The installer for this ROM is pretty self explanatory. And I am wiping before hand (both in the ROM install and in TWRP).
Same result every time though (never ending HTC screen)
Thanks again
Not sure why it won't boot. There should be no extra steps with this phone such as flashing separate boot.img....
Other ROMs flash fine?
S-off does have it warnings and potentials... But the revone s-off method carries and extreemmmeelllyy small chance of being fatal to your phone. I'd usually try to talk someone out of modding if you're not comfortable with it. But revone is a couple adb commands that are pretty newb friendly
Sent from my One using Tapatalk 2
InflatedTitan said:
Not sure why it won't boot. There should be no extra steps with this phone such as flashing separate boot.img....
Other ROMs flash fine?
S-off does have it warnings and potentials... But the revone s-off method carries and extreemmmeelllyy small chance of being fatal to your phone. I'd usually try to talk someone out of modding if you're not comfortable with it. But revone is a couple adb commands that are pretty newb friendly
Sent from my One using Tapatalk 2
Click to expand...
Click to collapse
Well I'm 1 for 3 as outlined above. The bigxie_m7_GPe_odexed_tbalden 4.2.2 works fine. The two 4.3 roms do not work... including ARHD and bigxie_m7_GPe_JWR66V_odexed-signed.
Is there an easy way to just "go back to stock" and then try again? The back to stock tutorials all seem a good bit involved.
Edit: Bigxie 4.3 just worked...maybe I'll just stick with that presuming there are no big issues with it?
Are there any big reasons to update the radio? If so can I do after ROM load?
Thanks for all your help btw.
Still wondering why this particular rom won't load. Any other takers? Bigxie still running at the moment.
I bet mike1986. knows!
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 All,
I have the M7 UL with a CID of HTC__001, it has hboot 1.44 s-off and I want to know if I really need to update the firmware/radio at all? I believe the current firmware is that of the 1.29.401.1 and since this was from the time of the Android 4.1.2 ROM and I am running a custom 4.3 ROM, I'm not sure what to do. I'm, not actually having any problems, so is it really necessary?
If so, do I need to upgrade hboot as well or can I get newer firmware/radio while keeping hboot 1.44 ?
beartiger said:
Hi All,
I have the M7 UL with a CID of HTC__001, it has hboot 1.44 s-off and I want to know if I really need to update the firmware/radio at all? I believe the current firmware is that of the 1.29.401.1 and since this was from the time of the Android 4.1.2 ROM and I am running a custom 4.3 ROM, I'm not sure what to do. I'm, not actually having any problems, so is it really necessary?
If so, do I need to upgrade hboot as well or can I get newer firmware/radio while keeping hboot 1.44 ?
Click to expand...
Click to collapse
At this point in time, you don't NEED to upgrade firmware, but there COULD be benefits such as the updated touchscreen drivers.
And since you're s-off, you can flash new firmware(s) including updated hboot, and still be able to downgrade anytime you choose.
Updating firmware or hboot will not change your s-off status, and therefore allow you to downgrade at your choice.
Sent from my HTC One using xda app-developers app
Ive got a quick question regarding this, is firmware ROM dependent - i.e does it matter if im on the 4.3 Sense ROM or the 4.3 Play ROM to flash the 4.3 Firmware?
TheOozyMan said:
Ive got a quick question regarding this, is firmware ROM dependent - i.e does it matter if im on the 4.3 Sense ROM or the 4.3 Play ROM to flash the 4.3 Firmware?
Click to expand...
Click to collapse
Nope. Like I said, currently the ROMs are firmware independent. This could change in the future, but for now it doesn't matter.
Sent from my HTC One using xda app-developers app
Thanks again for the help, I have another question about firmware flashing. I want to flash the latest firmware.zip on my HTC one and I'm already S-OFF. Can I just do this in TWRP and can I do it anytime or do I need to do it before I flash a ROM?
TheOozyMan said:
Thanks again for the help, I have another question about firmware flashing. I want to flash the latest firmware.zip on my HTC one and I'm already S-OFF. Can I just do this in TWRP and can I do it anytime or do I need to do it before I flash a ROM?
Click to expand...
Click to collapse
Firmware needs to be flashed in fastboot.
"fastboot oem rebootRUU"
"fastboot flash zip firmware.zip"
"fastboot flash zip firmware.zip"
(Yes, twice)
Be sure to check an make sure everything was successful.
"fastboot reboot"
Sent from my HTC One using XDA Premium 4 mobile app
Thanks, but I read somewhere that you need to flash firmware and then flash a ROM? Is that true?
Also whats the worst thing that could happen if I messed something up, could I just restore a nandroid?
TheOozyMan said:
Thanks, but I read somewhere that you need to flash firmware and then flash a ROM? Is that true?
Also whats the worst thing that could happen if I messed something up, could I just restore a nandroid?
Click to expand...
Click to collapse
The worst thing that could happen is a brick-- but that's unlikely.
Nandroids don't backup/restore firmware.
I'd recommend NOT updating hboot.img, or sbl??.img when updating firmware.
Only include these in firmware.zip: android-info.txt, adsp.img, radio.img, rcdata.img, tp_SYN3302.img, rpm.img and tz.img.
These get you (in order) the DSP, radio, radio config data, touch pad driver, and some misc stuff (rpm and tz).
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: