Related
Ok, so I tired to dabble in custom roms and I got burnt!!!
First things first,
HTC One X+ (International)
Version Main: 1.17.708.1
CID: HTC_622
S-On
HBOOT: 1.35.0000
Radio: 3.1204.168.32
I'm trying to RUU the device back to the stock and then never tinker again!
Can someone please step me through this, all the links I'm finding are dead or the RUU doesn't run.
Many thanks =)
Get hasoons20000 one x+ toolkit it has a link for ruu
Gave this a shot, I cannot find the appropriate RUU for my device.
****...
CJMilsey said:
Gave this a shot, I cannot find the appropriate RUU for my device.
****...
Click to expand...
Click to collapse
What country did you buy it from and what is your CID?
I bought it online (from Asia) The CID is 622 as above.
Addicted2xda said:
What country did you buy it from and what is your CID?
Click to expand...
Click to collapse
Bump
CJMilsey said:
Bump
Click to expand...
Click to collapse
Refer to the posting rules. You should not bump a thread within 24 hours...
You can download the RUU (ENRC2B) from this :
http://forum.xda-developers.com/showthread.php?t=2094118
you need to relock your bootloader before running the RUU
http://www.androidfiles.org/ruu/get...Radio_3.1204.168.32_release_299722_signed.exe
I'm sorry, I must have missed that one :/
I Tried this before but the RUU used didn't work, but I'll try to re-download and go from there.
(RUU_ENRC2B_U_JB_45_hTC_Asia_WWE_1.17.707.1_Radio_3.1204.168.32_release_299722_signed.exe)
Will it be a problem that my phone is 1.17.708.1 and that this is 1.17.707.1 (0.0.001 lower)?
Also, do I need to flash the stock recovery. And If so where would I go about getting it?
You will only have to relock the bootloader again and then (while in fastboot) run the RUU. Remember that you will lose everything on the device.
To relock the bootloader use Hansoon's toolkit. It has all the commands build in for easy use.
"Wrong CID" I'm not sure why this is wrong. 662 came back from fastboot getvar cid, and does indeed correspond to Hong Kong.
What would you advise from here dear sir?
CJMilsey said:
"Wrong CID" I'm not why this is wrong. 662 came back from fastboot getvar cid, and does indeed correspond to Hong Kong.
What would you advise from here dear sir?
Click to expand...
Click to collapse
Are you sure it's a generic HK CID? And not an operator locked one? Maybe you need the RUU from a particular operator.....
Sent from my HTC One X+ using Tapatalk 4 Beta
AndroHero said:
Are you sure it's a generic HK CID? And not an operator locked one? Maybe you need the RUU from a particular operator.....
Sent from my HTC One X+ using Tapatalk 4 Beta
Click to expand...
Click to collapse
I looked up the CID and it's just for HK, the phone came unlock so I doubt it needs a locked RUU. But hey, I've been wrong before.
Is there any reason the phone would not accept the correct RUU?
Okk,
This might seem a bit weird but I had the same issue with my Intl HOX+ and I have given it to hTC and they asked me to shell out aroun 18K to change the motherboard! (Which of course we all know is not required since this is a software issue).
So here is what I did:
1. I relocked the boot loader (I hope you have the unlock_code.bin with you, else get it from hTCDev)
2. Of course it started giving relocked security warning.
3. Again unlocked the boot loader and voila - it booted straight in to Elegancia!
This essentiially happens because unlocking the bootloader formats all the partitions except system and boot (I guess, because my media files were gone...).
See if this gets you through.
But DO IT AT YOUR OWN RISK!
I am talking about International HOX+, I do not know if ATT works in a different way.
Unfortunately that hasn't worked and I'm still stuck with the stall during boot :/
I think my best bet will the RUU, but I just can't get one that will work.
Do you know a ROM that I could side-load onto my device and just use it with that?
Thanks
Addicted2xda said:
Okk,
This might seem a bit weird but I had the same issue with my Intl HOX+ and I have given it to hTC and they asked me to shell out aroun 18K to change the motherboard! (Which of course we all know is not required since this is a software issue).
So here is what I did:
1. I relocked the boot loader (I hope you have the unlock_code.bin with you, else get it from hTCDev)
2. Of course it started giving relocked security warning.
3. Again unlocked the boot loader and voila - it booted straight in to Elegancia!
This essentiially happens because unlocking the bootloader formats all the partitions except system and boot (I guess, because my media files were gone...).
See if this gets you through.
But DO IT AT YOUR OWN RISK!
I am talking about International HOX+, I do not know if ATT works in a different way.
Click to expand...
Click to collapse
I had a small bootloader problem and was just surfing this section.I used your method of relocking and again unlocking and my problem was solved.I found it obligatery for me to thank you.
---------- Post added at 10:30 AM ---------- Previous post was at 10:21 AM ----------
CJMilsey said:
Unfortunately that hasn't worked and I'm still stuck with the stall during boot :/
I think my best bet will the RUU, but I just can't get one that will work.
Do you know a ROM that I could side-load onto my device and just use it with that?
Click to expand...
Click to collapse
I have unbricked mine by efforts of two long days and nights from about same problem. Provide the details and I will try to help you out,
1. can you boot to recovery.
2. If yes.which recovery you use.
3. what were you doing when this happened.
faandrabi said:
I have unbricked mine by efforts of two long days and nights from about same problem. Provide the details and I will try to help you out,
1. can you boot to recovery.
2. If yes.which recovery you use.
3. what were you doing when this happened.
Click to expand...
Click to collapse
1. No recovery works, and by mistake I performed a full erase with TWRP (don't ask me how, I honestly don't know why I did this) so despite all that they don't even exist anymore.
3. I flashed to Boot File as I couldn't get CM10.1 (Lior's HOX+ plug) to install and considered that my solve it. (I was wrong)
From this stuff I'm pretty sure it's broke, but I can get to the boot loader and recovery. Though I ran the appropriate (so I thought) RUU and it didn't work due to CID which stumped me.
CJMilsey said:
1. No recovery works, and by mistake I performed a full erase with TWRP (don't ask me how, I honestly don't know why I did this) so despite all that they don't even exist anymore.
3. I flashed to Boot File as I couldn't get CM10.1 (Lior's HOX+ plug) to install and considered that my solve it. (I was wrong)
From this stuff I'm pretty sure it's broke, but I can get to the boot loader and recovery. Though I ran the appropriate (so I thought) RUU and it didn't work due to CID which stumped me.
Click to expand...
Click to collapse
flash twrp through fasboot as only twrp provides side load option.
when twrp is flashed ,boot to recovery.side load incertcoin rom through hasoons toolkit.
don't worry about 707 or 708 etc.Mine was 707.1 but i am using incertcoin which is 401.3
after falshing incertcoin if it is again in boot loop then
use this command from adb
adb shell
wipe data
and reboot
you will be done.
CJMilsey said:
1. No recovery works, and by mistake I performed a full erase with TWRP (don't ask me how, I honestly don't know why I did this) so despite all that they don't even exist anymore.
3. I flashed to Boot File as I couldn't get CM10.1 (Lior's HOX+ plug) to install and considered that my solve it. (I was wrong)
From this stuff I'm pretty sure it's broke, but I can get to the boot loader and recovery. Though I ran the appropriate (so I thought) RUU and it didn't work due to CID which stumped me.
Click to expand...
Click to collapse
I hope you are on TWRP 2.5? If not update it...
And then use adb sideload
Hi,
I have the exact same problem.. I can get to TWRP recovery and HBOOT and my PC only detects the phone if its in recovery.
my CID is HTC__001.
I am trying to find a working RUU to run..
I tried this one: RUU_ENRC2B_U_JB_45_hTC_Asia_TW_1.14.709.17_Radio_3.1204.167.31_release_291089_signed.exe
(But that didn't work)
Any suggestions?
Thanks in advance.
rmuruga said:
Hi,
I have the exact same problem.. I can get to TWRP recovery and HBOOT and my PC only detects the phone if its in recovery.
my CID is HTC__001.
I am trying to find a working RUU to run..
I tried this one: RUU_ENRC2B_U_JB_45_hTC_Asia_TW_1.14.709.17_Radio_3.1204.167.31_release_291089_signed.exe
(But that didn't work)
Any suggestions?
Thanks in advance.
Click to expand...
Click to collapse
download incertcoin rom from hox+ android development & hasoon toolkit v2.4
boot in recovery
connect to pc
run onex+.exe and side load the rom
after it is done flash boot.img inside rom through fasboot command
and you will be done
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
Does anyone know if it's possible to convert the HTC One M8 to a developer edition version? I've tried searching online and see that it was a possibility on last year's M7 but can't find anything specifically about the M8. Thanks.
NextNexus said:
Does anyone know if it's possible to convert the HTC One M8 to a developer edition version? I've tried searching online and see that it was a possibility on last year's M7 but can't find anything specifically about the M8. Thanks.
Click to expand...
Click to collapse
Yes, it's possible.
garyd9 said:
Yes, it's possible.
Click to expand...
Click to collapse
Thanks. Can you provide more detail on how to accomplish this or refer me to a thread that has that info?
garyd9 said:
Yes, it's possible.
Click to expand...
Click to collapse
I guess you want some details, huh?
You'll need to get a Developer Edition stock recovery and a Developer Edition nandroid backup. (I'm lazy, so will just use "DevEd" instead of Developer edition.)
To get BOTH of these things, hop on over to a thread in the non-carrier specific M8 section: http://forum.xda-developers.com/showthread.php?t=2701376
Find and download the nandroid (TWRP) for CID BS_US002. Specifically, you should get the 1.12.1540.17 version. (There's a good reason for getting the older version...) You should also get a current TWRP image. (.img, not a zip file.) If you don't know how to get this image, then I'd advise NOT converting your device.
Then you can follow these steps:
Boot your phone normally.
Unpack the TWRP nandroid and place the folder into the proper directory on your phone's sdcard (/sdcard/TWRP/Backups/SERIAL_NUMBER/ or /sdcard2/TWRP/Backups/SERIAL_NUMBER) Replace "SERIAL_NUMBER" with your device's serial number. You should end up with a folder structure similar to: "./TWRP/Backups/HTXXXXXXXX/BackupName/" with the actual backup files in that directory.
... at this point, you might want to go ahead and boot into TWRP recovery to make sure that the backup you put in there is visible. It's fairly common for people to put the nandroid in the wrong place. I even did that myself once....
reboot into fastboot mode.
change CID to BS_US002 (BS_US001 is the "unlocked" version, BS_US002 is the DevEd version): fastboot oem writecid BS_US002
If you're starting with an AT&T branded device, there's no need to change the model ID (MID) as it's identical to the DevEd device.
reboot back into fastboot (to make sure the CID change worked): fastboot reboot-bootloader
use fastboot to put the proper DevEd STOCK recovery in place: fastboot flash stock_recovery.img
Probably not needed, but while in fastboot go ahead and run this: fastboot erase cache
Use fastboot to boot into (but not flash) the appropriate custom recovery. Example: fastboot boot openrecovery-twrp-2.7.0.2-m8.img
Use the custom recovery to wipe the data/cache/dalvik cache partitions.
Use the custom recovery to do a full restore from the backup copied to the phone above.
Reboot to the normal system. You can now accept OTA's and they should work. (They did for me.)
.... The reason for installing the older firmware version was to "test" the system by allowing the OTA to happen. If the OTA fails, then you screwed up the above steps.
Thanks. Can you provide more detail on how to accomplish this or refer me to a thread that has that info?
Click to expand...
Click to collapse
I was typing.
Either will work, does not matter if its BS_XXXX1 or BS_XXXX2 as long as its the Brightstar cid, has no bearing on software whatsoever or the functionality of the software or phone...the ota comes with both so either will work regardless.....lol
garyd9 said:
I guess you want some details, huh?
You'll need to get a Developer Edition stock recovery and a Developer Edition nandroid backup. (I'm lazy, so will just use "DevEd" instead of Developer edition.)
To get BOTH of these things, hop on over to a thread in the non-carrier specific M8 section: http://forum.xda-developers.com/showthread.php?t=2701376
Find and download the nandroid (TWRP) for CID BS_US002. Specifically, you should get the 1.12.1540.17 version. (There's a good reason for getting the older version...) You should also get a current TWRP image. (.img, not a zip file.) If you don't know how to get this image, then I'd advise NOT converting your device.
Then you can follow these steps:
Boot your phone normally.
Unpack the TWRP nandroid and place the folder into the proper directory on your phone's sdcard (/sdcard/TWRP/Backups/SERIAL_NUMBER/ or /sdcard2/TWRP/Backups/SERIAL_NUMBER) Replace "SERIAL_NUMBER" with your device's serial number. You should end up with a folder structure similar to: "./TWRP/Backups/HTXXXXXXXX/BackupName/" with the actual backup files in that directory.
... at this point, you might want to go ahead and boot into TWRP recovery to make sure that the backup you put in there is visible. It's fairly common for people to put the nandroid in the wrong place. I even did that myself once....
reboot into fastboot mode.
change CID to BS_US002 (BS_US001 is the "unlocked" version, BS_US002 is the DevEd version): fastboot oem writecid BS_US002
If you're starting with an AT&T branded device, there's no need to change the model ID (MID) as it's identical to the DevEd device.
reboot back into fastboot (to make sure the CID change worked): fastboot reboot-bootloader
use fastboot to put the proper DevEd STOCK recovery in place: fastboot flash stock_recovery.img
Probably not needed, but while in fastboot go ahead and run this: fastboot erase cache
Use fastboot to boot into (but not flash) the appropriate custom recovery. Example: fastboot boot openrecovery-twrp-2.7.0.2-m8.img
Use the custom recovery to wipe the data/cache/dalvik cache partitions.
Use the custom recovery to do a full restore from the backup copied to the phone above.
Reboot to the normal system. You can now accept OTA's and they should work. (They did for me.)
.... The reason for installing the older firmware version was to "test" the system by allowing the OTA to happen. If the OTA fails, then you screwed up the above steps.
I was typing.
Click to expand...
Click to collapse
garyd9 said:
I guess you want some details, huh?
You'll need to get a Developer Edition stock recovery and a Developer Edition nandroid backup. (I'm lazy, so will just use "DevEd" instead of Developer edition.)
To get BOTH of these things, hop on over to a thread in the non-carrier specific M8 section: http://forum.xda-developers.com/showthread.php?t=2701376
Find and download the nandroid (TWRP) for CID BS_US002. Specifically, you should get the 1.12.1540.17 version. (There's a good reason for getting the older version...) You should also get a current TWRP image. (.img, not a zip file.) If you don't know how to get this image, then I'd advise NOT converting your device.
Then you can follow these steps:
Boot your phone normally.
Unpack the TWRP nandroid and place the folder into the proper directory on your phone's sdcard (/sdcard/TWRP/Backups/SERIAL_NUMBER/ or /sdcard2/TWRP/Backups/SERIAL_NUMBER) Replace "SERIAL_NUMBER" with your device's serial number. You should end up with a folder structure similar to: "./TWRP/Backups/HTXXXXXXXX/BackupName/" with the actual backup files in that directory.
... at this point, you might want to go ahead and boot into TWRP recovery to make sure that the backup you put in there is visible. It's fairly common for people to put the nandroid in the wrong place. I even did that myself once....
reboot into fastboot mode.
change CID to BS_US002 (BS_US001 is the "unlocked" version, BS_US002 is the DevEd version): fastboot oem writecid BS_US002
If you're starting with an AT&T branded device, there's no need to change the model ID (MID) as it's identical to the DevEd device.
reboot back into fastboot (to make sure the CID change worked): fastboot reboot-bootloader
use fastboot to put the proper DevEd STOCK recovery in place: fastboot flash stock_recovery.img
Probably not needed, but while in fastboot go ahead and run this: fastboot erase cache
Use fastboot to boot into (but not flash) the appropriate custom recovery. Example: fastboot boot openrecovery-twrp-2.7.0.2-m8.img
Use the custom recovery to wipe the data/cache/dalvik cache partitions.
Use the custom recovery to do a full restore from the backup copied to the phone above.
Reboot to the normal system. You can now accept OTA's and they should work. (They did for me.)
Click to expand...
Click to collapse
Worked for me as well. Downloading the OTA as I type this. Thank you for the detailed instructions. Attempted to do this before when coming from the GPE ROM and had several issues. This time was much more streamlined thanks to your input.
DG4FREE said:
Worked for me as well. Downloading the OTA as I type this. Thank you for the detailed instructions. Attempted to do this before when coming from the GPE ROM and had several issues. This time was much more streamlined thanks to your input.
Click to expand...
Click to collapse
Do I need to do anything different if I have twrp installed with stock Rom?
Alaris said:
Do I need to do anything different if I have twrp installed with stock Rom?
Click to expand...
Click to collapse
Stock rooted ROM or stock non rooted or stock Android (GPE or other ROM)?
Essentially follow the directions above, especially making sure you boot into TWRP recovery prior to flashing to the developer recovery since you already have it installed and go through the option to restore the developer edition nandroid backup. If it gives you the option to restore now, you should be fine to continue with the steps above. In short:
Reboot to bootloader.
Change your CID to BS_US002
Flash the developer recovery from the link above.
**Boot** into TWRP recovery (with the developer recovery still being the "installed recovery" using:
Code:
fastboot boot /location of recovery/recovery.img
TWRP should now open as if it was installed and allow you to restore from the developer edition nandroid even though you technically still have the developer edition recovery installed.
Once it restores you can reboot the phone and you should be good to go. Upon connecting to WiFi I was prompted to update to the latest OTA and everything has been working all day.
Sent from my HTC One_M8 using Tapatalk
Thanks debating on stay with att stock or this for faster updates.
Sent from my HTC One_M8 using Tapatalk
Alaris said:
Thanks debating on stay with att stock or this for faster updates.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Its been great for me so far. I was on GPE and the little hardware issues (M8 is just better with Sense) made me come back. I've rocked the Maximus HD 4.0 ROM over in the open M8 forum and it has full AT&T support but thought I'd try this out. Sometimes I think the custom Roms put to much extras packed in although Maximus is decently light.
Sent from my Nexus 7 using Tapatalk
Dumb question ?
What would be the main benefits to changing to lets say from the at&t m8 to a dev edition, other than faster updates ?
DG4FREE said:
Its been great for me so far. I was on GPE and the little hardware issues (M8 is just better with Sense) made me come back. I've rocked the Maximus HD 4.0 ROM over in the open M8 forum and it has full AT&T support but thought I'd try this out. Sometimes I think the custom Roms put to much extras packed in although Maximus is decently light.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thanks everyone had a couple of speed bumps but I got through it. Just out of curiousity would there be any difference between the Dev Ruu and doing this?
Alaris said:
Thanks everyone had a couple of speed bumps but I got through it. Just out of curiousity would there be any difference between the Dev Ruu and doing this?
Click to expand...
Click to collapse
Wasn't aware of a Dev RUU being posted (at least an official one) but from what I understand it'd be the same thing.
Sent from my HTC One_M8 using Tapatalk
---------- Post added at 08:36 PM ---------- Previous post was at 08:34 PM ----------
Roefastford said:
Dumb question ?
What would be the main benefits to changing to lets say from the at&t m8 to a dev edition, other than faster updates ?
Click to expand...
Click to collapse
No AT&T branding/bloat. I know there's Roms out there that are debloated but you'd still be required to manually flash updates and or use the built in OTA of that ROM if it has such a feature. This in a way gives you the best of both.
Sent from my HTC One_M8 using Tapatalk
Anyone notice the red writing during setup that said something along the lines of this being a test device and HTC will collect info like location etc.? Is this something that I should be worried about?
Roefastford said:
What would be the main benefits to changing to lets say from the at&t m8 to a dev edition, other than faster updates ?
Click to expand...
Click to collapse
Assuming you're comparing "stock" to "stock": No carrierIQ, faster updates, no AT&T bloatware. (However, you lose Isis and the visual voice mail integration.)
Alaris said:
Anyone notice the red writing during setup that said something along the lines of this being a test device and HTC will collect info like location etc.? Is this something that I should be worried about?
Click to expand...
Click to collapse
I never noticed that. My understanding is that the warning comes up if you're using a recovery or kernel that doesn't match the rest of the firmware. If you follow the instructions I posted, you should end up with a completely stock recovery + kernel, so won't see that red warning.
Oh, and if you DO see the warning, it's completely harmless.
Take care
Gary
garyd9 said:
Assuming you're comparing "stock" to "stock": No carrierIQ, faster updates, no AT&T bloatware. (However, you lose Isis and the visual voice mail integration.)
I never noticed that. My understanding is that the warning comes up if you're using a recovery or kernel that doesn't match the rest of the firmware. If you follow the instructions I posted, you should end up with a completely stock recovery + kernel, so won't see that red warning.
Oh, and if you DO see the warning, it's completely harmless.
Take care
Gary
Click to expand...
Click to collapse
Do you have s-off?
Alaris said:
Do you have s-off?
Click to expand...
Click to collapse
Yes.
Sent from my HTC One_M8
garyd9 said:
Yes.
Sent from my HTC One_M8
Click to expand...
Click to collapse
Do my a favor go to settings>about and there should be one that says tell HTC click it and scroll to the bottom. Do you see any red writing that says HTC will collect data? Because i did exactly what you did and I have that writing that says the will collect data and i cant opt out of it. It doesn't sound like me and you have anything that we did differently unless you didn't notice yours during the initial setup.
Alaris said:
Do my a favor go to settings>about and there should be one that says tell HTC click it and scroll to the bottom.
Click to expand...
Click to collapse
I don't have anything like "tell HTC". I did go through everything in settings->about, but nothing like what you described.
Sent from my HTC One_M8
I don't get why I that then
Sent from my HTC One_M8 using Tapatalk
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!
AT&T M8
unlocked boot loader
hboot 3.16
I used windroid universal htc toolkit v1.2 to get my token and then unlocked my bootloader. clicked on twrp under GSM one m8 (flash recovery) I got a message saying that it flashed successfully! and then got an error message saying an error occured!a log file to.....
now when I go into fastboot it says ***Tampered*** and ***unlocked*** at the top but i can't go into recovery. it will just loop me back to fastboot screen
I rebooted both phone and computer and tried again same thing. I tried to reflash twrp with windroid, same thing. tried to flash twrp manually through cmd and got another error message (cannot load twrp.img)
i also tried to flash a stock recovery with cmd and got the same error as with twrp..
where do i go from here. never had this issue before. and rooted all my htc's hero, og evo, evo lte. some I'm comfortable with this stuff..
Make sure you are using a good version of twrp and that you have a valid download package. That's where I would start
-Sent from a payphone...
http://m.youtube.com/watch?v=Krw6H4gQ6g0&feature=youtu.be
http://forum.xda-developers.com/showthread.php?t=2702325
A video and the thread for a different tool kit .I used it to unlock and flash recovery only
AT&T HTC ONE M8 ,S-OFF
Ditch the toolkits. Both Windroid and Hasoon's haven't been updated in a long time, have very obsolete versions of TWRP, and can only cause trouble.
Does the following command respond with your phone's ID?
fastboot devices
If so, try fastboot erase cache
Then install the latest version of TWRP or Philz recovery using fastboot. This solves the majority of issues with custom recovery not booting.
jball said:
http://m.youtube.com/watch?v=Krw6H4gQ6g0&feature=youtu.be
http://forum.xda-developers.com/showthread.php?t=2702325
A video and the thread for a different tool kit .I used it to unlock and flash recovery only
AT&T HTC ONE M8 ,S-OFF
Click to expand...
Click to collapse
thanks for helping out. I'll definitively check those out.
stumcmahan said:
thanks for helping out. I'll definitively check those out.
Click to expand...
Click to collapse
Hasoon's toolkit has not been updated for 6 months, and includes a version of TWRP that is many versions obsolete. I've seen this (installing old TWRP version) cause various issues for folks, so you are almost asking for trouble.
Just flash the latest TWRP with fastboot (after wiping cache with fastboot). If you don't know how, just learn, as its very easy.
redpoint73 said:
Ditch the toolkits. Both Windroid and Hasoon's haven't been updated in a long time, have very obsolete versions of TWRP, and can only cause trouble.
Does the following command respond with your phone's ID?
fastboot devices
If so, try fastboot erase cache
Then install the latest version of TWRP or Philz recovery using fastboot. This solves the majority of issues with custom recovery not booting.
Click to expand...
Click to collapse
hey thanks alot for helping. i was thinking the same thing about those tool kits. should have never used it. looked so easy though. i do get my phone ID when i fastboot devices so i will try clearing that catch first. and push that .img through fastboot. i'll post how it goes once i get home from work. thanks again.
stumcmahan said:
i was thinking the same thing about those tool kits. should have never used it. looked so easy though.
Click to expand...
Click to collapse
If you are already familiar with adb/fastboot (and as you have a good amount of experience with Android, you probably do) these toolkits don't really do anything. And I've seen folks have a lot of issues trying to do things with the toolkits; and switching to doing them manually works without a hitch. Toolkits are a needless middleman, and just another point of possible failure.
redpoint73 said:
If you are already familiar with adb/fastboot (and as you have a good amount of experience with Android, you probably do) these toolkits don't really do anything. And I've seen folks have a lot of issues trying to do things with the toolkits; and switching to doing them manually works without a hitch. Toolkits are a needless middleman, and just another point of possible failure.
Click to expand...
Click to collapse
yep if it looks to good to be true, probable is. fastboot from here on out. hopefully it works.
I used the tool kit I provided links to and had zero issues.it installed the outdated TWRP and with the outdated recovery I flashed the updated Supersu so Flashify would have root permission to flash the updated TWRP img.I wouldn't recommend something that wouldn't have worked if I didn't try it myself.another shortcut you might be interested in is in fact very reliable as far as
S-OFF when you reach that stage is "SunShine".
AT&T HTC ONE M8 ,S-OFF
jball said:
I used the tool kit I provided links to and had zero issues.it installed the outdated TWRP and with the outdated recovery I flashed the updated Supersu so Flashify would have root permission to flash the updated TWRP img.I wouldn't recommend something that wouldn't have worked if I didn't try it myself.
Click to expand...
Click to collapse
I didn't say toolkits don't work. But I've seen them cause problems for some folks as well. And those problems went away simply by doing things the "manual" way (command prompt) instead of using a GUI.
And just because it worked for you, doesn't mean its going to work 100% of the time.
Hassoon's toolkit to flash an obsolete TWRP, then flash SuperSU, then install Flashify to update TWRP seems a bit convoluted; when all it takes to flash TWRP in fastboot is a single command (after downloading .img file to your computer).
@redpoint73
Same number of steps as it would be if starting from scratch.I simply tried the tool kit cause the rumor that all tool kits will cause problems phrase.I assume op tried the tool kit in the first place possibly intimidated by adb/fastboot commands so I gave another option.again I do like your educated choice of words and thank you for being a major contributor on XDA
AT&T HTC ONE M8 ,S-OFF
jball said:
@redpoint73
Same number of steps as it would be if starting from scratch.I simply tried the tool kit cause the rumor that all tool kits will cause problems phrase.I assume op tried the tool kit in the first place possibly intimidated by adb/fastboot commands so I gave another option.
Click to expand...
Click to collapse
Options are always good when one is in a jam. The OP hasn't tried any of the suggestions yet, so its entirely possible that my approach fails and yours succeeds. Although I doubt it, as toolkits do the same thing as the "manual" way, just by adding a GUI.
@redpoint73
Well good ,than adb/fastboot would be the way to go and highly unlikely that it will fail considering adb/fastboot will be his option when removing the "tampered","redtext" and writing Supercid.
AT&T HTC ONE M8 ,S-OFF
redpoint73 said:
Ditch the toolkits. Both Windroid and Hasoon's haven't been updated in a long time, have very obsolete versions of TWRP, and can only cause trouble.
Does the following command respond with your phone's ID?
fastboot devices
If so, try fastboot erase cache
Then install the latest version of TWRP or Philz recovery using fastboot. This solves the majority of issues with custom recovery not booting.
Click to expand...
Click to collapse
still no luck. did a fastboot devices and got my phone ID. did fastboot erase cache and it erased the cache. flashed twrp.img and got
error: cannot load 'twrp.img'
stumcmahan said:
still no luck. did a fastboot devices and got my phone ID. did fastboot erase cache and it erased the cache. flashed twrp.img and got
error: cannot load 'twrp.img'
Click to expand...
Click to collapse
Do you have the option turned on in Windows to hide the file extensions? You might have accidentally renamed the file "twrp.img.img" and not realized it. This is the most common reason for the error message mentioned.
redpoint73 said:
Do you have the option turned on in Windows to hide the file extensions? You might have accidentally renamed the file "twrp.img.img" and not realized it. This is the most common reason for the error message mentioned.
Click to expand...
Click to collapse
Thanks! that was it man! i read that somewhere else i completely forgot to check.
stumcmahan said:
Thanks! that was it man! i read that somewhere else i completely forgot to check.
Click to expand...
Click to collapse
Yeah, there was another user that made the same mistake just the other day.
I suppose the particular mistake wouldn't happen if using a toolkit. But on the other hand the toolkit (at least Windroid) didn't work either. So there is never a perfect answer. The best thing is to have a variety of options open to you; and be armed with the proper tools and knowledge to handle an array of problems.
redpoint73 said:
Yeah, there was another user that made the same mistake just the other day.
I suppose the particular mistake wouldn't happen if using a toolkit. But on the other hand the toolkit (at least Windroid) didn't work either. So there is never a perfect answer. The best thing is to have a variety of options open to you; and be armed with the proper tools and knowledge to handle an array of problems.
Click to expand...
Click to collapse
couldn't agree more. and just wanted to say thanks again, you were a big help. appreciate it.
The only toolkit you might want is sneakyghost's quick batch kit,which contains a small adb/fastboot package...unless you plan on downloading the entire ADT