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!
Related
I've been (at least trying to) patiently wait for Deck to post full install instructions for CM10 but the CM10 op is still bare as bones. Has anyone else posted an install guide or instructions yet?
I'm currently rooted with RegawMod and running MeanRom 2.1 and it's really terribly laggy and frustrating, I can't wait any longer for CM10. Do I need S-off to install CM10 or do I just wipe, flash, and go?
Thanks for any help or links!
If you are on hboot 1.15 or higher you have to fast boot flash the kernel.
Other than that its just like a normal aosp install. Wipe flash rom flash gapps.
Its been my daily for 3 weeks.
Sent from my EVO using Tapatalk 2
You don't need s-off. You will however have to flash the boot IMG separately by using fastboot or the app flash image GUI and a full wipe is definitely required. There is a helpful thread in Q&A called "don't panic" that will answer all your questions
Good luck
Sent from my EVO using xda app-developers app
corcgaigh said:
You don't need s-off. You will however have to flash the boot IMG separately by using fastboot or the app flash image GUI and a full wipe is definitely required. There is a helpful thread in Q&A called "don't panic" that will answer all your questions
Good luck
Click to expand...
Click to collapse
Dont use flash image gui unless you know how to do it manually through fastboot. You are just asking for issues
Instructions:
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-a.html
Rxpert said:
If you are on hboot 1.15 or higher you have to fast boot flash the kernel.
Other than that its just like a normal aosp install. Wipe flash rom flash gapps.
Click to expand...
Click to collapse
I'm on hboot 1.12, so does that mean I can just flash normally?
edit - From what I can tell from reading, hboot 1.12 doesn't have the same restrictions that 1.15+ do, so I think I'm OK but I would like verification.
Thanks for the help everyone.
Yes hboot 1.12 allows for access to the boot partition
Also luuuuucckkyyyyyy...
EdhyMonker said:
I'm on hboot 1.12, so does that mean I can just flash normally?
edit - From what I can tell from reading, hboot 1.12 doesn't have the same restrictions that 1.15+ do, so I think I'm OK but I would like verification.
Thanks for the help everyone.
Click to expand...
Click to collapse
If you are on Hboot 1.12 I'd strongly suggest looking into getting S-OFF. Theres really no reason not to.
Up to you though, its not required
Bit off topic, anyone check to see if you can push a new splash, right now I'm too lazy to start my PC just to fastboot one measly splash
Rxpert said:
If you are on Hboot 1.12 I'd strongly suggest looking into getting S-OFF. Theres really no reason not to.
Up to you though, its not required
Click to expand...
Click to collapse
The S-OFF guide was way over my head so I just let it be. If there's not a real good reason for doing it, and I can still run CM10, then I'd rather not.
It allows you to directly flash new firmware like radios to fix any problems a device might be having. If you have Son and want the latest firmware you have to revert back to stock and accept ota, then unlock reflash recovery and reflash custom ROM or rooted stock, you could also just flash root installer if you want to just root stock
om4 said:
It allows you to directly flash new firmware like radios to fix any problems a device might be having. If you have Son and want the latest firmware you have to revert back to stock and accept ota, then unlock reflash recovery and reflash custom ROM or rooted stock, you could also just flash root installer if you want to just root stock
Click to expand...
Click to collapse
No, S-ON people with 1.12 H-boot can flash radios and firmware from recovery. They can do whatever they please in recovery just like S-OFF. S-OFF users can flash things from bootloader and even change the appearance of their h-boot to read S-ON and **locked** even though they are S-OFF
To the OP, this is the best rooting guide I've seen. It really explains everything step by step. http://androidforums.com/evo-4g-lte...panda-s-htc-dev-ltevo-root-dummies-guide.html Its recommended to have Linux at least bootable, because in the small chance the phone gets bricked... the unbricker program requires linux.
I ran it in windows before the unbricker was available, no issues here
You basically just hook the phone up to it and run the program like you do for most other root programs. All 1-click
Ah yeah forgot to mention that, most everyone is on 1.15 or 1.19 sorry
om4 said:
Ah yeah forgot to mention that, most everyone is on 1.15 or 1.19 sorry
Click to expand...
Click to collapse
Alright, I got S-Off using Lazy Panda and it went better than expected!
Do I need to flash updated firmware / radios separately from CM10, or does CM10 include latest firmware?
Sorry to ask dumb questions, but I do hope this thread will also be a good resource for others like me.
You don't have to flash any firmware updates. There are a few users with issues although they may be related to the ROM update and not necessarily the firmware included. I haven't really checked since I'm s on. If you want to update the radios there's an update zip here somewhere, be sure to read through everything carefully. Radios are more risky then every day flashing
Alright everyone now I need some help!
I flashed CM10 after s-off, was on stocked 1.13 rooted rom.
Now when CM10 boots up I am faced with a phone activation screen. It says something like "you will not be able to place calls or access the mobile network until the device is activated". I am unable to make calls or receive calls or access the internet. I have tried reflashing cm10 and the problem persists.
In the mean time, I will try flashing a nand backup and see where that gets me. I appreciate any and all help, and I have found no posts in the CM10 thread with a similar issue.
Update: I wiped and restored a back-up, MeanRom 2.1. Upon boot, hands-free activation ran and activated the phone and downloaded a PRL update. Everything is working fine now. Not sure if I should try CM10 again or what? Any advice?
EdhyMonker said:
Alright everyone now I need some help!
I flashed CM10 after s-off, was on stocked 1.13 rooted rom.
Now when CM10 boots up I am faced with a phone activation screen. It says something like "you will not be able to place calls or access the mobile network until the device is activated". I am unable to make calls or receive calls or access the internet. I have tried reflashing cm10 and the problem persists.
In the mean time, I will try flashing a nand backup and see where that gets me. I appreciate any and all help, and I have found no posts in the CM10 thread with a similar issue.
Update: I wiped and restored a back-up, MeanRom 2.1. Upon boot, hands-free activation ran and activated the phone and downloaded a PRL update. Everything is working fine now. Not sure if I should try CM10 again or what? Any advice?
Click to expand...
Click to collapse
ive only ever seen this issue with cyanogenmod and the old htc vogues, still great phones for what they were
EdhyMonker said:
Alright, I got S-Off using Lazy Panda and it went better than expected!
Do I need to flash updated firmware / radios separately from CM10, or does CM10 include latest firmware?
Sorry to ask dumb questions, but I do hope this thread will also be a good resource for others like me.
Click to expand...
Click to collapse
Yes, you should be flashing the upgraded firmware. You'll see the full firmware as the very first downloadable link. Flash that
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
Rename the file to "PJ75IMG.zip", place on root of SD card, and boot into HBOOT to flash. Check the md5 to make sure its right. With radios you want to make sure its the correct file.
Welcome to S-OFF my friend
Rxpert said:
Yes, you should be flashing the upgraded firmware. You'll see the full firmware as the very first downloadable link. Flash that
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
Rename the file to "PJ75IMG.zip", place on root of SD card, and boot into HBOOT to flash. Check the md5 to make sure its right. With radios you want to make sure its the correct file.
Welcome to S-OFF my friend
Click to expand...
Click to collapse
Thanks, but I tried this and it says "no image or wrong image" when trying to flash the PJ75IMG.zip file.
Did you type in PJ75IMG.zip or PJ75IMG and kept it a zip file...you should do the 2nd.
joebarkho said:
Did you type in PJ75IMG.zip or PJ75IMG and kept it a zip file...you should do the 2nd.
Click to expand...
Click to collapse
I thought that might've been the issue so I tried it both ways, didn't work either way. I'll take another shot at it tomorrow.
Hello! I used to be very engrossed in the modding community for the Rezound a few months ago. But because of a forced phone switch I haven't been in the loop for a while.
Well now I'm back on a Rezound and I was wanting to know a few things.
Fair warning. When I left we had just achieved S-off and were delving into the new things we could do from then on, so if my questions seem dated; I'm sorry.
Also, my phone atm is on stock ICS, I wanted to get a feel for everything again before I went and rooted it.
*Which are the most prominent ROMs right now? (Preferrably sense with beats)
*Do any of those ROMs have a working DSP Manager with Virtual room or ability to get it working on it?
*What is this whole GSM thing I'm seeing on some ROMs lists? Are we able to use the rezound easily overseas or on different networks now or something?
I have looked through some of the forums but haven't been able to find any concrete information, so I figured I would just post my own thread.
Thank you for your time and any replies!
The most prominent roms are any of the ones on the first two pages of the development sections. I know that neo includes a Beats mod in his AOSP roms which works as well as any stock beats you'll find in a sense rom. The DSP manager included with cyanogenmod is 100% functional as far as I can tell. And yes, we can use the rezound on AT&T (siul does MIUI and uses his rezound on AT&T) but I'm not sure as to what frequencies we have access to and if its HSPA or not.
Since you've been gone we received a global ruu that gives the rezound service over seas. The most prominent roms sense based are viperrez, newts one xxx, ecliptic rez and so on.. Those are just the ones I've tried. I'm running newts hybrid rom now and it's doing well though it's not as optimized as his one xxx rom
Sent from my ADR6425LVW using xda app-developers app
Alright, thanks for the info! And what are the best recoveries to use, now?
Volkaru said:
Alright, thanks for the info! And what are the best recoveries to use, now?
Click to expand...
Click to collapse
all the recoverys are about the same now. its up to you on what you want it to do. TWRP and CWMT are both great touch based recoveries. if you want more of the menu scroll classic way. go with AmonRA 3.15
Volkaru said:
Alright, thanks for the info! And what are the best recoveries to use, now?
Click to expand...
Click to collapse
TWRP, unbeatable! Not sure if it's available for your phone though..
Vangelis13 said:
TWRP, unbeatable! Not sure if it's available for your phone though..
Click to expand...
Click to collapse
It is. Installed it.
I think I'm all set now except for one thing. Is it normal now after you unlock and install a recovery for it to say TAMPERED? Last I saw that was when people were installing the leaked ICS RUUs.
The order of which I rooted my phone in case I did anything wrong was. Unlock bootloader with HTCDev, Phone restarted, let it load up then went into the menu and enabled Debugging again, shut it off. Reloaded fastboot. Then installed TWRP 2.3.3.0 using the All-in-one tool. After that my bootloader said TAMPERED.
Thanks again for all the help.
Volkaru said:
It is. Installed it.
I think I'm all set now except for one thing. Is it normal now after you unlock and install a recovery for it to say TAMPERED? Last I saw that was when people were installing the leaked ICS RUUs.
The order of which I rooted my phone in case I did anything wrong was. Unlock bootloader with HTCDev, Phone restarted, let it load up then went into the menu and enabled Debugging again, shut it off. Reloaded fastboot. Then installed TWRP 2.3.3.0 using the All-in-one tool. After that my bootloader said TAMPERED.
Thanks again for all the help.
Click to expand...
Click to collapse
Tampered is ok. It just means there's a custom recovery installed. Every now and then TWRP has some issues flashing certain files just so you know, most likely you'll never see it, but just in case it keeps you from chasing your tail I mentioned it.
We're s off now, that's the big change for when you want to do some wild modification. But thanks to snuzzo there's no harm done in being s on it's easier now than it used to be.
Anything else, send me a PM if you'd like and we can catch up on gtalk.
So is your hboot 2.25 and your radio basebands end in .421r and .424r?
CharliesTheMan said:
Tampered is ok. It just means there's a custom recovery installed. Every now and then TWRP has some issues flashing certain files just so you know, most likely you'll never see it, but just in case it keeps you from chasing your tail I mentioned it.
We're s off now, that's the big change for when you want to do some wild modification. But thanks to snuzzo there's no harm done in being s on it's easier now than it used to be.
Anything else, send me a PM if you'd like and we can catch up on gtalk.
So is your hboot 2.25 and your radio basebands end in .421r and .424r?
Click to expand...
Click to collapse
Alright, thanks for all the info. Will PM you later.
Everything was fully updated as far as stock goes.
I think I've done it this time. I was able to unlock the bootloader and also able to put TWRP recovery onto the phone. The mistake I made was trying to flash MIUI to the phone without backing anything up, so here I am and have been for the last 4 hours trying to figure out how to get my phone to boot into a ROM of any sort to try and S-OFF using the FacePalm method.
I honestly don't know what I should do at this point. I can still enter recovery and flash ROMs. Just, none of them actually load. The only time I can get any of them to load is when I flash it via recovery, then flash the boot.img via fastboot. However, when I do it this way, my touch screen within the ROM no longer works. So I can't press or do anything, to give my phone super user permissions. I'm really frustrated and just want to fix my phone. Can anyone offer some help or advice so I can try and fix this sometime between now and my death?
Thank you in advance.
cdboss said:
I think I've done it this time. I was able to unlock the bootloader and also able to put TWRP recovery onto the phone. The mistake I made was trying to flash MIUI to the phone without backing anything up, so here I am and have been for the last 4 hours trying to figure out how to get my phone to boot into a ROM of any sort to try and S-OFF using the FacePalm method.
I honestly don't know what I should do at this point. I can still enter recovery and flash ROMs. Just, none of them actually load. The only time I can get any of them to load is when I flash it via recovery, then flash the boot.img via fastboot. However, when I do it this way, my touch screen within the ROM no longer works. So I can't press or do anything, to give my phone super user permissions. I'm really frustrated and just want to fix my phone. Can anyone offer some help or advice so I can try and fix this sometime between now and my death?
Thank you in advance.
Click to expand...
Click to collapse
Relax
Check the link in my sig. Should answer most of your questions regarding your issues.
You are S-on, most likely on Hboot 1.15 or newer. You have to flash the kernel separately from the ROM for the ROM to boot when you are S-on. This is why fastboot flashing the kernel (boot.img) worked.
Regarding your other issue, it sounds like you have the updated touch panel driver that came with the most recent OTA. You need to use TWRP 2.4+ and you can only run ROM's that are software version 3.16. Once you get S-off you can downgrade the driver and run whatever ROM you want
Sent from my EVO using xda premium
certain putesbi
FinZ28 said:
Relax
Check the link in my sig. Should answer most of your questions regarding your issues.
You are S-on, most likely on Hboot 1.15 or newer. You have to flash the kernel separately from the ROM for the ROM to boot when you are S-on. This is why fastboot flashing the kernel (boot.img) worked.
Regarding your other issue, it sounds like you have the updated touch panel driver that came with the most recent OTA. You need to use TWRP 2.4+ and you can only run ROM's that are software version 3.16. Once you get S-off you can downgrade the driver and run whatever ROM you want
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Thank you for your reply and help.
I'm running HBOOT 2.09 to be exact. I'm also running TWRP 2.5, so I'm good there as well. Right now I can't boot into a ROM appropriately to achieve S-OFF. I tried creating a Ubuntu Live CD and the Kernel got messed up I guess when putting it on the disc. That was another frustration of mine, lol. I can't achieve the FacePalm method because I can't boot into a ROM to adb shell as super user, since it physically needs to be accepted on the phone.
I'm going to read what you suggested, though, perhaps that will give me the answer.
Edit: I'm going to go with your suggestion of flashing a ROM that's made for 3.16, and see if my touch panel works so I can S-OFF and flash whatever I want. I'll let you know how that goes.
cdboss said:
Thank you for your reply and help.
I'm running HBOOT 2.09 to be exact. I'm also running TWRP 2.5, so I'm good there as well. Right now I can't boot into a ROM appropriately to achieve S-OFF. I tried creating a Ubuntu Live CD and the Kernel got messed up I guess when putting it on the disc. That was another frustration of mine, lol. I can't achieve the FacePalm method because I can't boot into a ROM to adb shell as super user, since it physically needs to be accepted on the phone.
I'm going to read what you suggested, though, perhaps that will give me the answer.
Click to expand...
Click to collapse
What ROM are you trying to run? If it isn't based on software version 3.16 it WON'T WORK.
Sent from my EVO using xda premium
FinZ28 said:
What ROM are you trying to run? If it isn't based on software version 3.16 it WON'T WORK.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Just edited my post. I'm an idiot and didn't completely read your post. My apologies. I'm in the process of getting Viper4G at the moment, to try and achieve S-OFF.
cdboss said:
Just edited my post. I'm an idiot and didn't completely read your post. My apologies. I'm in the process of getting Viper4G at the moment, to try and achieve S-OFF.
Click to expand...
Click to collapse
I was able to get into Viper, tried doing the FacePalm S-OFF and it wasn't successful, for whatever reason. However, at least I'm better off than I was before. Any suggestions from here? I really want to get MIUI on this and not really feeling up to installing Ubuntu tonight.
If not, I really want to thank you. At least I'm able to use my phone again, lol.
cdboss said:
I was able to get into Viper, tried doing the FacePalm S-OFF and it wasn't successful, for whatever reason. However, at least I'm better off than I was before. Any suggestions from here? I really want to get MIUI on this and not really feeling up to installing Ubuntu tonight.
If not, I really want to thank you. At least I'm able to use my phone again, lol.
Click to expand...
Click to collapse
You're going to have to go the Dirty Racun route, unfortunately
Sent from my EVO using xda premium
FinZ28 said:
You're going to have to go the Dirty Racun route, unfortunately
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Guess I'll have to try and make another Live CD. I have no interest in dual booting a copy of Ubuntu at the moment, lol.
Thanks for the help.
FinZ28 said:
Relax
Check the link in my sig. Should answer most of your questions regarding your issues.
You are S-on, most likely on Hboot 1.15 or newer. You have to flash the kernel separately from the ROM for the ROM to boot when you are S-on. This is why fastboot flashing the kernel (boot.img) worked.
Regarding your other issue, it sounds like you have the updated touch panel driver that came with the most recent OTA. You need to use TWRP 2.4+ and you can only run ROM's that are software version 3.16. Once you get S-off you can downgrade the driver and run whatever ROM you want
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I now was able to get S-OFF. What exactly do I do to downgrade those drivers and flash a ROM that I want?
cdboss said:
I now was able to get S-OFF. What exactly do I do to downgrade those drivers and flash a ROM that I want?
Click to expand...
Click to collapse
If you want to downgrade your touch panel, check out this thread:
http://forum.xda-developers.com/showthread.php?t=1704612
The above thread links to here:
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
The touch panel you want to downgrade to is located under the 3.15 firmware, so just follow the directions posted in order to downgrade.
Sent from my EVO using xda premium
FinZ28 said:
If you want to downgrade your touch panel, check out this thread:
http://forum.xda-developers.com/showthread.php?t=1704612
The above thread links to here:
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
The touch panel you want to downgrade to is located under the 3.15 firmware, so just follow the directions posted in order to downgrade.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Awesome, thank you. I was able to get the ROM I wanted on here and looks like everything is good to go. Appreciate the help, FinZ28.
cdboss said:
Awesome, thank you. I was able to get the ROM I wanted on here and looks like everything is good to go. Appreciate the help, FinZ28.
Click to expand...
Click to collapse
You're welcome
Sent from my EVO using xda premium
So while in process of s-off once I got to the part when you "fastboot oem rebootRUU" that went through. But right after trying to flash a zip im stuck looking at the blk HTC screen. I was given a "<Failed <remote: 99 unknown fail>". Now its just stuck.
I've been trying to figure out what happened but just have no where else to turn. Please lend a hand.
I think I already know the answer to this question, but what version is your firmware? Just for your knowledge, there hasn't been an RUU since ICS, or maybe the first release of JB. So, odds are, you flashed the wrong RUU.
But good news, you *might* not be bricked. Have you tried rebooting? This really your only option, anyway. Try to get into the bootloader. Flash a new recovery if the RUU has already wiped it, and flash a compatible rom.
Please also list your bootloader info.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
aarsyl said:
I think I already know the answer to this question, but what version is your firmware? Just for your knowledge, there hasn't been an RUU since ICS, or maybe the first release of JB. So, odds are, you flashed the wrong RUU.
But good news, you *might* not be bricked. Have you tried rebooting? This really your only option, anyway. Try to get into the bootloader. Flash a new recovery if the RUU has already wiped it, and flash a compatible rom.
Please also list your bootloader info.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
Click to expand...
Click to collapse
It's not a full RUU in the normal sense. It's the one for Facepalm.
To the OP, did you gain SuperCID prior to running those commands? If not, then the process will fail. You should simply be able to hold the power button down & reboot your phone. Also, as stated above, list your device info so we can make sure you're using the right S-off exploit.
Sent from my HTC EVO 4G LTE
So I did get the phone into the bootloader. I was trying to do the rumrunner s-off but being I was so damn tired lastnight I ended up forgetting a step. I am currently unlocked and rooted. I also somehow deleted my backup like a idiot and wiped the os. So I'm stuck from this point where I need to go.
So where we stand as of now:
bootloader unlocked
rooted
twrp 2.6.3.0
firmware 3.17.651.4
hboot 2.09
radio 1.13.11.0830
z3r0t0l0rEnCe said:
So I did get the phone into the bootloader. I was trying to do the rumrunner s-off but being I was so damn tired lastnight I ended up forgetting a step. I am currently unlocked and rooted. I also somehow deleted my backup like a idiot and wiped the os. So I'm stuck from this point where I need to go.
So where we stand as of now:
bootloader unlocked
rooted
twrp 2.6.3.0
firmware 3.17.651.4
hboot 2.09
radio 1.13.11.0830
Click to expand...
Click to collapse
Happens to all of us. Don't worry about wiping the OS. Look for Captain Throwback's stock rooted rom, and flash a custom kernel along with it, like the Dirty MAC kernel or Arc reactor. Doesn't matter which one...rumrunner just needs a custom kernel.
Captain Throwback's stock 3.17 base
http://forum.xda-developers.com/showthread.php?t=2468418
Dirty MAC kernel
http://forum.xda-developers.com/showthread.php?t=2178307
Arc Reactor
http://forum.xda-developers.com/showthread.php?t=1873824
After you flash these, then reboot into Android, set your phone to stay awake during charge Settings-->Display and Buttons, and also set SuperSU to automatically grant root access (open the app, swipe right twice, and scroll down a little). This way, you don't have to touch your phone. If you touch it, the process will fail....even to unlock the phone to grant root access. And of course, turn on USB debugging in Developer Options.
After you do all of these, then run the exploit.
aarsyl said:
Happens to all of us. Don't worry about wiping the OS. Look for Captain Throwback's stock rooted rom, and flash a custom kernel along with it, like the Dirty MAC kernel or Arc reactor. Doesn't matter which one...rumrunner just needs a custom kernel.
Captain Throwback's stock 3.17 base
http://forum.xda-developers.com/showthread.php?t=2468418
Dirty MAC kernel
http://forum.xda-developers.com/showthread.php?t=2178307
Arc Reactor
http://forum.xda-developers.com/showthread.php?t=1873824
After you flash these, then reboot into Android, set your phone to stay awake during charge Settings-->Display and Buttons, and also set SuperSU to automatically grant root access (open the app, swipe right twice, and scroll down a little). This way, you don't have to touch your phone. If you touch it, the process will fail....even to unlock the phone to grant root access. And of course, turn on USB debugging in Developer Options.
After you do all of these, then run the exploit.
Click to expand...
Click to collapse
This is odd to me, because I ran rumrunner at least 3 times using just my stock ROM (no custom kernel or anything), and it worked fine every time. I guess the new version of rumrunner added some limitations to make it more generic.
whats bothering me is that even after i check the MD5, it keeps failing to install capt zip. think maybe i can just use adb to push the zip file? just not sure how to word the command right to get it to load
z3r0t0l0rEnCe said:
whats bothering me is that even after i check the MD5, it keeps failing to install capt zip. think maybe i can just use adb to push the zip file? just not sure how to word the command right to get it to load
Click to expand...
Click to collapse
No, don't. If it fails, don't force it. Reflash TWRP 2.6.3 (not the kit kat version), and try to flash again.
@Captain_Throwback: Yes, I didn't remember needing a custom kernel when I used Dirty Racun, but rumrunner needs it now. Keep in mind that rumrunner isn't for this device exclusively. Maybe that's the purpose of the custom kernel.
i'd wager you're trying to flash files that aren't recovery flashable, then lying to the people who are trying to help you.
i got it running again using capt stock rooted rom. attempting rumrunners s-off again now that i got this part working.
Are you using a custom kernel?
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
now s-off and updated rumrunners hboot. now onto flashing roms finally.
Thank you all that helped me with my stupidness and not reading directions.
Last post. I can't say it enough that you must read read read when it comes to directions. If I would of followed directions as directed I would of never ran into the issues I did. It was a learning experience.
One thing for sure that I took from this experience is adb and directions. I've learned a lot in the last 24hrs alone.
I'd like to thank Capain_throwback and everyone in the irc for the help and you all here that assisted me.
Sent from my EVO using XDA Premium 4 mobile app
http://dl3.htc.com/application/RUU_M8_UL_K443_SENSE60_ATT_MR_Cingular_US_2.23.502.3_Radio_1.19.213311491.A22G_20.51A.4198.01L_F_release_387305_signed_2.exe from http://www.htc.com/us/support/htc-one-m8-att/news/
t5620 said:
http://dl3.htc.com/application/ruu_m8_ul_k443_sense60_att_mr_cingular_us_2.23.502.3_radio_1.19.213311491.a22g_20.51a.4198.01l_f_release_387305_signed_2.exe from http://www.htc.com/us/support/htc-one-m8-att/news/
Click to expand...
Click to collapse
sweet thank you!
Andrew149 said:
sweet thank you!
Click to expand...
Click to collapse
you are welcome.
Remember that for the ruu to work you need to relock the bootloader and have stock recovery. and unroot. it works with S-OFF so no need to S-ON
t5620 said:
you are welcome.
Remember that for the ruu to work you need to relock the bootloader and have stock recovery. and unroot. it works with S-OFF so no need to S-ON
Click to expand...
Click to collapse
Umm I've never needed to lock my boot loader with s off to ruu 4.4.2. Are you sure?
Andrew149 said:
Umm I've never needed to lock my boot loader with s off to ruu 4.4.2. Are you sure?
Click to expand...
Click to collapse
Bootloader lock only needed for s-on.
Wow, same day RUU as the OTA? Unbelievable!
Andrew149 said:
Umm I've never needed to lock my boot loader with s off to ruu 4.4.2. Are you sure?
Click to expand...
Click to collapse
I'm not 100% sure.. but ,I always re-lock the bootloader just in case
How can I install this with S-on? Couldn't get S-off because firewater is broken for me.
My phone is rooted and the bootloader is unlocked. How can I lock the bootloader without S-off?
iArtisan said:
How can I install this with S-on? Couldn't get S-off because firewater is broken for me.
My phone is rooted and the bootloader is unlocked. How can I lock the bootloader without S-off?
Click to expand...
Click to collapse
you could try Sunshine to get S-OFF it cost $25 dollars but it can S-OFF your device.
But I think that you do not need to be s-off to run the RUU, if you want to easily relock the bootloader use tthe HTC One 2014 (M8) All-In-One Toolkit http://forum.xda-developers.com/showthread.php?t=2699065 its the easiest way
Can I use this to go from Google Play Edition back to stock Sense assuming I change my CID back to AT&T?
I am S-OFF and Bootloader Unlocked and obviously ATT branded.
Yes
Sent from my HTC One_M8 using XDA Free mobile app
So for the people who been running this ruu for a few weeks have you found any bugs?
Andrew149 said:
So for the people who been running this ruu for a few weeks have you found any bugs?
Click to expand...
Click to collapse
X2. Would like to know as well. Thanks.
Andrew149 said:
So for the people who been running this ruu for a few weeks have you found any bugs?
Click to expand...
Click to collapse
no bugs so far but battery life isn't that great as with the last FW although there is no battery drain like with the OTA but I'm not impressed with the battery performance
Sent from my HTC One_M8 using XDA Free mobile app
I have my phone set up like I want it. Stable, everything works. Running 4.4.2 rooted, unlocked, twrp recovery, etc. All the apps I want. So on and so forth.
Will nandroid backup made now work after I run this ruu? Basically update the os and then recover everything the way I have it set up now?
Sorry for asking what seems, even to me, a basic beginners question.
Question
lostangelintx said:
I have my phone set up like I want it. Stable, everything works. Running 4.4.2 rooted, unlocked, twrp recovery, etc. All the apps I want. So on and so forth.
Will nandroid backup made now work after I run this ruu? Basically update the os and then recover everything the way I have it set up now?
Sorry for asking what seems, even to me, a basic beginners question.
Click to expand...
Click to collapse
In short...No. First off, you can't install the 4.4.3 update if you have a TWRP recovery installed. You have to have the stock recovery in order to do the update. But...for the sake of argument, you did the update and...then re-rooted and restored your nandroid. You would in effect overwrite the update and put yourself back to where you started (if that makes any sense).
My advice would be to install a custom ROM that containes the 4.4.3 update already...or put a stock recovery back on your phone and do the update. There is a nice all-in-one update you can run right off the sdcard using Hboot. I did it and it was flawless.
Either way, you'll most likely be setting up your phone again but that really shouldn't be too bad. Take some screenshots so you will remember just how you had things.
Hope this helps and good luck.
Scott
lostangelintx said:
I have my phone set up like I want it. Stable, everything works. Running 4.4.2 rooted, unlocked, twrp recovery, etc. All the apps I want. So on and so forth.
Will nandroid backup made now work after I run this ruu? Basically update the os and then recover everything the way I have it set up now?
Sorry for asking what seems, even to me, a basic beginners question.
Click to expand...
Click to collapse
I have to ask, if you went through all that trouble, why would you ever want to run ATT software? You could have easily converted to Dev Edition and never looked back.
hack14u said:
I have to ask, if you went through all that trouble, why would you ever want to run ATT software? You could have easily converted to Dev Edition and never looked back.
Click to expand...
Click to collapse
I can't answer for the OP, but coming from the factory unlocked version and having tried various firmwares and ROMs (including Dev), the ATT RUU is the only one that gives me true LTE speeds.
Scott, could you point me towards that update using Hboot?
scott500 said:
In short...No. First off, you can't install the 4.4.3 update if you have a TWRP recovery installed. You have to have the stock recovery in order to do the update. But...for the sake of argument, you did the update and...then re-rooted and restored your nandroid. You would in effect overwrite the update and put yourself back to where you started (if that makes any sense).
My advice would be to install a custom ROM that containes the 4.4.3 update already...or put a stock recovery back on your phone and do the update. There is a nice all-in-one update you can run right off the sdcard using Hboot. I did it and it was flawless.
Either way, you'll most likely be setting up your phone again but that really shouldn't be too bad. Take some screenshots so you will remember just how you had things.
Hope this helps and good luck.
Scott
Click to expand...
Click to collapse
Sure thing... Here it is..
http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486