Related
I'm currently running a Google Edition ROM, but I'd like to update the firmware (primarily for the new radio). What is the easiest way to do this?
I do not have S-off or SuperCID and I also have a nandroid of the stock T-mobile software before I started messing with my phone's ROM, etc.
Any help is greatly appreciated.
JohnnyTA said:
I'm currently running a Google Edition ROM, but I'd like to update the firmware (primarily for the new radio). What is the easiest way to do this?
I do not have S-off or SuperCID and I also have a nandroid of the stock T-mobile software before I started messing with my phone's ROM, etc.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Two questions...
1. Why aren't you S-OFF? 1.54 HBOOT?
2. Why don't you just flash the radio?
jrburkh said:
Two questions...
1. Why aren't you S-OFF? 1.54 HBOOT?
2. Why don't you just flash the radio?
Click to expand...
Click to collapse
My impression is that S-OFF is an arduous process to do - is this true? Additionally, I wasn't aware you could just flash the radio, I may try this and report back.
JohnnyTA said:
My impression is that S-OFF is an arduous process to do - is this true? Additionally, I wasn't aware you could just flash the radio, I may try this and report back.
Click to expand...
Click to collapse
I'm with you (not on GE ROM but VenomOne), did you flash the radio? I think we have to be S-Off to flash the radio though.
JohnnyTA said:
My impression is that S-OFF is an arduous process to do - is this true? Additionally, I wasn't aware you could just flash the radio, I may try this and report back.
Click to expand...
Click to collapse
I don't think it's particularly arduous so long as you have a compatible HBOOT, or can at least downgrade (i.e., you're not on 1.54). To be honest, though, I've never done it. BUT, I think just about anybody on here will tell you that if you can S-OFF, you should - and never go back S-ON, ever. Obviously you are unlocked and rooted if you are messing with ROMs, in which case you can indeed flash just the radio. You can flash just about anything on the phone with the phone unlocked and rooted. In my opinion, the only thing that sucks about being S-ON is not being able to reset to LOCKED and TAMPERED flags freely, and not being able to flash non-compatible RUUs, if you're into that sort of thing.
I would like to start out with saying that I am not new to rooting/roms but a lot has changed since I went to iOS. I have TWRP accessible and I can push files to my /sdcard/
I have tried several rooms but all of them fail to install.
Can someone please tell me the steps I need to take to go back to either stock or have another ROM working? (RUU fails as well, however it does detect the phone)
Any help is appreciated and trust me I spent hours reading threads so not just posting this for an easy way out.
chirayu said:
I would like to start out with saying that I am not new to rooting/roms but a lot has changed since I went to iOS. I have TWRP accessible and I can push files to my /sdcard/
I have tried several rooms but all of them fail to install.
Can someone please tell me the steps I need to take to go back to either stock or have another ROM working? (RUU fails as well, however it does detect the phone)
Any help is appreciated and trust me I spent hours reading threads so not just posting this for an easy way out.
Click to expand...
Click to collapse
First, this should probably be in the Q&A section
Second, gonna need WAY more info about your phone. I assume you're rooted? S-off or S-on? What hboot version are you on? What version of TWRP are you currently using? What ROM are you on now? What RUU are you trying to use? Gonna have to give a little bit for us to work with.
Edit: Your signature also says you have the Evo Shift? Are you on the write forum?
Greenfieldan said:
First, this should probably be in the Q&A section
Second, gonna need WAY more info about your phone. I assume you're rooted? S-off or S-on? What hboot version are you on? What version of TWRP are you currently using? What ROM are you on now? What RUU are you trying to use? Gonna have to give a little bit for us to work with.
Edit: Your signature also says you have the Evo Shift? Are you on the write forum?
Click to expand...
Click to collapse
I apologize for posting this in the wrong forum, like I was saying I haven't been here in a while and signature is outdated by about 6 years
Heres the info
TWRP v2.7.1.0
S-ON
HBOOT-2.10.0000
RADIO-1.13.11.1105
I had the last leaked RUU installed before I attempted flashing a custom ROM
Thank you for your reply!
chirayu said:
I apologize for posting this in the wrong forum, like I was saying I haven't been here in a while and signature is outdated by about 6 years
Heres the info
TWRP v2.7.1.0
S-ON
HBOOT-2.10.0000
RADIO-1.13.11.1105
I had the last leaked RUU installed before I attempted flashing a custom ROM
Thank you for your reply!
Click to expand...
Click to collapse
Is your goal to flash another ROM or to go back to stock?
If you're going to be trying to flash another ROM I'd highly recommend running rumrunner and getting s-off. Otherwise there are a lot of hoops you'll need to jump through in order to flash ROMs (for starters, you'll need to flash the kernel separately).
Code:
Greenfieldan said:
Is your goal to flash another ROM or to go back to stock?
Click to expand...
Click to collapse
Whichever one is faster, I just want the phone up and running again.
So it's not running at all now? I'm assuming you can boot into bootloader and recovery but nothing else, right? You can run an RUU while in fastboot if I recall, which will give you at least a usable phone. That's also probably the fastest thing to do.
After that I'd highly recommend using rumrunner to get s-off. Otherwise flashing new ROMs will be a bear.
Greenfieldan said:
So it's not running at all now? I'm assuming you can boot into bootloader and recovery but nothing else, right? You can run an RUU while in fastboot if I recall, which will give you at least asable phone. That's also probably the fastest thing to do.
After that I'd highly recommend using rumrunner to get s-off. Otherwise flashing new ROMs will be a bear.
Click to expand...
Click to collapse
RUU fails with errors and it gets stuck at "HTC" screen
Do you have HTC Sync installed on your computer?
Greenfieldan said:
Do you have HTC Sync installed on your computer?
Click to expand...
Click to collapse
Ah, I think something else made me delete it.
That'll do it. You need to have HTC Sync and all of the necessary drivers to run the RUU
Greenfieldan said:
That'll do it. You need to have HTC Sync and all of the necessary drivers to run the RUU
Click to expand...
Click to collapse
Thank you! giving that a try now
greenfieldan said:
that'll do it. You need to have htc sync and all of the necessary drivers to run the ruu
Click to expand...
Click to collapse
error [155]: Uknown error
chirayu said:
error [155]: Uknown error
Click to expand...
Click to collapse
D'oh! I bet your bootloader is still unlocked. It needs to be relocked before running the RUU.
Fastboot command 'fastboot oem lock' ought to do the trick.
Greenfieldan said:
D'oh! I bet your bootloader is still unlocked. It needs to be relocked before running the RUU.
Fastboot command 'fastboot oem lock' ought to do the trick.
Click to expand...
Click to collapse
You're a life saver! at least you can bet I have rooting/unrooting down for this EVO. Just like the old times
Moved to Q&A forum
Just updated to the 4.4.3 OTA then rooted flashed TWRP and install Venom One ROM. Now I get that annoying message on boot. My OCD is drving me nuts! found a few tutorials about flashing fastboot, but they all seem pretty old. Not sure if theres an update or an easy to fallow tutorial using adb or an AIO software. Thanks.
Need to wait for hboot to be modded to have that removed
Wonders_Never_Cease said:
Need to wait for hboot to be modded to have that removed
Click to expand...
Click to collapse
Ah okay thanks. Wasnt sure if Hboot was universal or if it was by build.
2.23.503.2 ota? If not s-off cannot flash firmware...if s-off the hboot has been modified already. Link is located in my thread in the at&t m8 section
Wonders_Never_Cease said:
2.23.503.2 ota? If not s-off cannot flash firmware...if s-off the hboot has been modified already. Link is located in my thread in the at&t m8 section
Click to expand...
Click to collapse
I'm on build 2.22.401.5 running VenomOne rom, S-Off, rooted all the good stuff. Will your hboot mod work for mine?
if on an att device its been discussed many times to use the appropriate firmware for us devices...2.22.1540.3/.4 is latest developer edition device firmware, 2.23.502.3 is latest for att devices...imo use one of those packages @firmware instead of euro.
Wonders_Never_Cease said:
if on an att device its been discussed many times to use the appropriate firmware for us devices...2.22.1540.3/.4 is latest developer edition device firmware, 2.23.502.3 is latest for att devices...imo use one of those packages @firmware instead of euro.
Click to expand...
Click to collapse
OK and I can just install either one of those hboots over my existing one and it wont brick my phone or is this more to this?
look in the htc one m8 forum since your using a euro firmware for the modified 2.22.401.5 hboot im sure its been done...
Wonders_Never_Cease said:
look in the htc one m8 forum since your using a euro firmware for the modified 2.22.401.5 hboot im sure its been done...
Click to expand...
Click to collapse
Found it, thanks man. Gonna mess with it a little later.
CavyS said:
Just updated to the 4.4.3 OTA then rooted flashed TWRP and install Venom One ROM. Now I get that annoying message on boot. My OCD is drving me nuts! found a few tutorials about flashing fastboot, but they all seem pretty old. Not sure if theres an update or an easy to fallow tutorial using adb or an AIO software. Thanks.
Click to expand...
Click to collapse
Hey Cavy..I got a couple of questions for you, if you don't mind. Were you completely stock after taking the 4.4.3 update? I just received my update a couple of days ago and I'm thinking about taking the plunge and rooting. How did you go about rooting and flashing Venom One? Thanks for your help!
thinkhope said:
Hey Cavy..I got a couple of questions for you, if you don't mind. Were you completely stock after taking the 4.4.3 update? I just received my update a couple of days ago and I'm thinking about taking the plunge and rooting. How did you go about rooting and flashing Venom One? Thanks for your help!
Click to expand...
Click to collapse
Yeah I was completely stock after updating. To root I used the AIO toolkit found here (http://forum.xda-developers.com/showthread.php?t=2699065) Once youre rooted reboot into recovery and make a backup. Then download the ViperOne rom here (http://venomroms.com/htc-one-m8/) copy the zip folder onto your SD or internal storage and reboot into recovery again and flash the ViperOne zip folder.
CavyS said:
Yeah I was completely stock after updating. To root I used the AIO toolkit found here (http://forum.xda-developers.com/showthread.php?t=2699065) Once youre rooted reboot into recovery and make a backup. Then download the ViperOne rom here (http://venomroms.com/htc-one-m8/) copy the zip folder onto your SD or internal storage and reboot into recovery again and flash the ViperOne zip folder.
Click to expand...
Click to collapse
You don't need to root if you are going to flash a custom ROM right away. Unlock bootloader, install custom recovery, then put the custom ROM on the phone and flash it.
So the toolkit still works?? Thought I read somewhere the 4.4.3 patched something. Are you also S-OFF??
Sent from my HTC One_M8 using XDA Free mobile app
redpoint73 said:
You don't need to root if you are going to flash a custom ROM right away. Unlock bootloader, install custom recovery, then put the custom ROM on the phone and flash it.
Click to expand...
Click to collapse
It was just easier for me to fallow a set of instructions going step by step than jumping around just to avoid 1 easy step.
thinkhope said:
So the toolkit still works?? Thought I read somewhere the 4.4.3 patched something. Are you also S-OFF??
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah still works, you might of read that Firewater for some people doesnt work on 4.4.3. For me Firewater worked and I'm S-Off for some people it doesnt and you have to use Sunshine in that case.
thinkhope said:
So the toolkit still works??
Click to expand...
Click to collapse
I highly recommend doing it manually and steering clear of toolkits. Using a toolkit robs you of an important learning opportunity, and leaves you with little understanding of the processes. Skills and knowledge that are important when things don't go quite right (which will inevitably happen).
redpoint73 said:
I highly recommend doing it manually and steering clear of toolkits. Using a toolkit robs you of an important learning opportunity, and leaves you with little understanding of the processes. Skills and knowledge that are important when things don't go quite right (which will inevitably happen).
Click to expand...
Click to collapse
I agree and that's the route I'm trying to take, however just need a bit more of a solid guide to lean on. I haven't messed around with adb or pushed anything via fastboot since my One X. Don't want to end up with a fancy paper weight.
Sent from my HTC One_M8 using XDA Free mobile app
thinkhope said:
I agree and that's the route I'm trying to take, however just need a bit more of a solid guide to lean on. I haven't messed around with adb or pushed anything via fastboot since my One X. Don't want to end up with a fancy paper weight.
Click to expand...
Click to collapse
If you did it on your One X, its really not any different on the M8. Actually, probably a good deal easier if you had the AT&T One X (EVITA), since that phone required temp root and SuperCID to unlock the bootloader, for the most part.
In short:
-Go to HTCDev.com to unlock the bootloader. The website walks you though step-by-step, so there is really nothing to that part.
- Use adb to flash your recovery of choice (TWRP or CWM)
- Flash SU/SuperSU or flash a custom ROM
-S-off, if you want
- That's it!
redpoint73 said:
If you did it on your One X, its really not any different on the M8. Actually, probably a good deal easier if you had the AT&T One X (EVITA), since that phone required temp root and SuperCID to unlock the bootloader, for the most part.
In short:
-Go to HTCDev.com to unlock the bootloader. The website walks you though step-by-step, so there is really nothing to that part.
- Use adb to flash your recovery of choice (TWRP or CWM)
- Flash SU/SuperSU or flash a custom ROM
-S-off, if you want
- That's it!
Click to expand...
Click to collapse
I definitely did have the evita. Had to alter the cid to make htc dev believe it was a different phone or something like that, if I remember correctly.
S-ON really is only if I want to mess with different radios, right? All I want is xposed and and maybe some cm 11 or gpe once Android L is out.
Well, sounds easy enough. I will be attempting later tonight after work. Thanks for all of your help. If it's OK, mind if I PM you if something goes wrong?
Sent from my HTC One_M8 using XDA Free mobile app
thinkhope said:
S-ON really is only if I want to mess with different radios, right? All I want is xposed and and maybe some cm 11 or gpe once Android L is out.
Click to expand...
Click to collapse
S-off is needed to flash radio, hboot, SIM unlock, and some other things. But not for root or to flash ROMs. Pretty much similar to how things were on the EVITA; with the exception that boot.img will flash automatically along with the ROM (not possible on most hboots on the EVITA, and had to be flashed manually with fastboot).
It sounds like you are already on the "official" 2.23 software (Android 4.4.3) by OTA? If so, you don't need to update firmware (radio, hboot, etc.) as the OTA already updated it. Otherwise, s-off is needed to flash the firmware manually; which is pretty much required for any 2.xx Sense based custom ROMs (otherwise there will be serious bugs like very long boot times, broken WiFi, Bluetooth). While s-off is not strictly needed to flash the ROM (it will flash correctly) things just won't run right if firmware is outdated. This is the only reason you would "need" to have s-off for flashing ROMs. AOSP and GPE ROMs won't suffer this issue.
But if you are already on the new OTA, this isn't an issue for flashing any ROM. You can verify by looking at the hboot version and baseband. If you are on hboot 3.18 and baseband 1.19; your firmware is up to date, and won't be an issue for running any ROMs.
thinkhope said:
mind if I PM you if something goes wrong?
Click to expand...
Click to collapse
I actually prefer you just posting to the forums. Either to an existing relevant thread, or start a new one if a relevant one does not already exist.
Couple reasons for this:
- Info given to you can help others reading the forums, and benefit the community as a whole instead of being hidden away in PM
- You can get help from more than just one user. I don't claim to even remotely know everything, and often its helpful to have more than one set of eyes on a problem (especially the tougher ones). And I might not even be online to help.
In particular for the 2nd point: my wife and I are going to be having a baby, with scheduled induction tomorrow (Sept. 5) unless it happens by itself sooner. So I won't be available to help you when that happens, anyway!
In any case, good luck!
Hello,
I have a Virgin Moblie version of the Desire 601, which I believe is Zara_CL. The phone is still on stock 4.2.2 but it is rooted. I've tried to get s-off but I always run into errors and I've given up on it (unless absolutely necessary).
The phone has gotten very sluggish and I want to wipe it out, preferribly with an RUU. I've found this Google Drive on this forum:
https://drive.google.com/folderview?id=0B-kSF8g8H7KuME12ai1OVHVqd3M&usp=sharing#list
and I've downloaded the JB422 RUU. Will this reset my phone to stock even though I'm rooted? Also, could I just use the K44 RUU instead and upgrade to Kitkat, or do I need to go back to stock 4.2.2 and upgrade via the OTA?
Thanks!
A kitkat RUU for US zara_cl was just released.
http://forum.xda-developers.com/showthread.php?t=3012200
PS. Getting s-off was a pain in the butt for me as well. Anything thay interferes with the network will cause it to fail; antivirus, firewall (pc or router), parental controls. Check this main thread below as it has lots of help. Check posts from me or directed at me as I posted a lot here about my issues. I formatted my hard drive. In the end it was likely a parental control application I use to block porn on my laptop.
http://forum.xda-developers.com/showthread.php?t=2528645
rubejb said:
Hello,
I have a Virgin Moblie version of the Desire 601, which I believe is Zara_CL. The phone is still on stock 4.2.2 but it is rooted. I've tried to get s-off but I always run into errors and I've given up on it (unless absolutely necessary).
The phone has gotten very sluggish and I want to wipe it out, preferribly with an RUU. I've found this Google Drive on this forum:
https://drive.google.com/folderview?id=0B-kSF8g8H7KuME12ai1OVHVqd3M&usp=sharing#list
and I've downloaded the JB422 RUU. Will this reset my phone to stock even though I'm rooted? Also, could I just use the K44 RUU instead and upgrade to Kitkat, or do I need to go back to stock 4.2.2 and upgrade via the OTA?
Thanks!
Click to expand...
Click to collapse
You can use either RUU. The newer one will upgrade you to KK, the other one will return you to stock JB like when you purchased the phone.
There's two things to note though ...
1) S-OFF will likely be easier to get on JB than it will on KK
2) Once you upgrade to KK you will NOT be able to use the JB RUU unless you are S-OFF (as you will need to downgrade your hboot to use it)
Also, you can try taking a look at this thread if haven't already to see if it helps with getting S-OFF.
Hedied4me said:
A kitkat RUU for US zara_cl was just released.
http://forum.xda-developers.com/showthread.php?t=3012200
PS. Getting s-off was a pain in the butt for me as well. Anything thay interferes with the network will cause it to fail; antivirus, firewall (pc or router), parental controls. Check this main thread below as it has lots of help. Check posts from me or directed at me as I posted a lot here about my issues. I formatted my hard drive. In the end it was likely a parental control application I use to block porn on my laptop.
http://forum.xda-developers.com/showthread.php?t=2528645
Click to expand...
Click to collapse
-Duir- said:
You can use either RUU. The newer one will upgrade you to KK, the other one will return you to stock JB like when you purchased the phone.
There's two things to note though ...
1) S-OFF will likely be easier to get on JB than it will on KK
2) Once you upgrade to KK you will NOT be able to use the JB RUU unless you are S-OFF (as you will need to downgrade your hboot to use it)
Also, you can try taking a look at this thread if haven't already to see if it helps with getting S-OFF.
Click to expand...
Click to collapse
Thank you both for the information!
Is there any reason not to do the KK upgrade? Does it run smoother or slower? Is root easy to obtain in KK?
I've heard there are some tighter restrictions on writing to the SD card with KK, is this easily bypassable?
I don't really care about S-OFF any more, as I don't plan on doing any ROMing.
Thanks!
rubejb said:
Thank you both for the information!
Is there any reason not to do the KK upgrade? Does it run smoother or slower? Is root easy to obtain in KK?
I've heard there are some tighter restrictions on writing to the SD card with KK, is this easily bypassable?
I don't really care about S-OFF any more, as I don't plan on doing any ROMing.
Thanks!
Click to expand...
Click to collapse
No issues with KitKat and rooting is easy. Just install TWRP and then boot into it and reboot and it will tell you that it didn't find root and offer to install it for you. The current version bundled with TWRP is 2.40 and runs fine, but there is also a newer version or SuperSU, version 2.45, which you can use if you prefer and can be downloaded as a flashable zip from here.
A couple things to note though:
You will need to get a new unlock token from HTC as your hboot will be newer and the old token will not work with it (you'll need to lock the bootloader for the RUU to successfully run).
When you unlock, there's a few apps that will be removed because HTC decided to put them on the data partition which gets wiped when you unlock the bootloader.
The only stock app really that gets removed is the calculator. You can still setup and use the calculator widget, but no direct access to the app.
One benefit to S-OFF before upgrading to KK is that you can then unlock the bootloader without using htcdev and not have data get wiped.
On stock KitKat, yes, there is a setting that limits how apps are able to access the sdcard. Once you have root, install this app from the Play store and it will fix it for you.
Hmmm, I'm getting "Fastboot has stopped working" when I try to run the KK RUU. Luckily, it's still leaving my phone in a workable condition.
I'm gong to attempt the JB RUU then do the OTA if possible.
edit:
No luck with the JB RUU either. I think I'm going to give up for now and just stick with my slow phone.
Fixed! (So far)
I got back to trying to RUU again since my phone had gotten even more deathly slow.
Another thread here:
http://forum.xda-developers.com/desire-601/help/easiest-to-return-phone-to-stock-to-t2859051
said that you had to relock your bootloader before doing the RUU. Seems to have fixed it for me. I was able to run the Jellybean RUU without issue. I just wanted to post the fix for me in case others where having the same problem.
As Child's Play said in that other post:
Get into fastboot and type fastboot oem lock
I backed up my phone and have had troubles restoring a rom, although I don't have access to it at the moment, if I restore a backup I made with htc sync manager will it restore the rom I had? and if not, I've had troubles installing a rom with a .zip, because every rom I find is for a different bootloader (I have 1.6) and .exe's fail because my bootloader is unlocked. if I relock it should the .exe work regardless of the bootloader version. if neither of these would work, what do you suggest I do? I'd send it in to htc but they estimated $220, then another person said $290 is average, but it could be up to $350 just to fix it, and at that price I could almost buy another (sorry if these are easy questions)
In order for someone to help, you should post the rom your on, whether your s-on or s-off, and what recovery you're using.
Evan092 said:
I've had troubles installing a rom with a .zip, because every rom I find is for a different bootloader (I have 1.6)
Click to expand...
Click to collapse
I think you mean hboot 3.16, as "1.6" is not a valid hboot number for this device.
There are ROMs for every hboot number.
Evan092 said:
.exe's fail because my bootloader is unlocked. if I relock it should the .exe work regardless of the bootloader version.
Click to expand...
Click to collapse
If you are s-on, the RUU will always fail with an unlocked bootloader.
Will it work regardless of hboot number? Technically no (although in your specific case, its sort of "yes"). The hboot number of the RUU needs to be equal and greater than what is on the phone. But as it appears you have hboot 3.16 on the phone, any correct RUU for AT&T will meet this requirement, as all official AT&T RUUs are that version or newer. But it must be an RUU for your version (AT&T) of the M8.
Evan092 said:
I'd send it in to htc but they estimated $220, then another person said $290 is average, but it could be up to $350 just to fix it, and at that price I could almost buy another (sorry if these are easy questions)
Click to expand...
Click to collapse
If the phone simply isn't working/booting due to attempted mods; I'd say its not necessary to send in for repairs. I think we can get the phone up and running again. It just sounds like you tried some mods, and not completely familiar with the processes, concepts, etc.
In addition to the info posted in the reply above, also explain in detail what you have done to get to this point. Its not even clear what state the phone is in. But if you are considering sending in for repair, I assume this means the phone won't boot.
redpoint73 said:
I think you mean hboot 3.16, as "1.6" is not a valid hboot number for this device.
There are ROMs for every hboot number.
If you are s-on, the RUU will always fail with an unlocked bootloader.
Will it work regardless of hboot number? Technically no (although in your specific case, its sort of "yes"). The hboot number of the RUU needs to be equal and greater than what is on the phone. But as it appears you have hboot 3.16 on the phone, any correct RUU for AT&T will meet this requirement, as all official AT&T RUUs are that version or newer. But it must be an RUU for your version (AT&T) of the M8.
If the phone simply isn't working/booting due to attempted mods; I'd say its not necessary to send in for repairs. I think we can get the phone up and running again. It just sounds like you tried some mods, and not completely familiar with the processes, concepts, etc.
In addition to the info posted in the reply above, also explain in detail what you have done to get to this point. Its not even clear what state the phone is in. But if you are considering sending in for repair, I assume this means the phone won't boot.
Click to expand...
Click to collapse
I relocked the bootloader and ran the RUU I downloaded right off of the htc website and it worked, thanks for the help
Evan092 said:
thanks for the help
Click to expand...
Click to collapse
You're welcome, and there's a button for that.