Hi All,
Help required with my HTC One 801n. I have read and search numourse posts but still cant load a ROM or anything back onto it
The phone details
M7 UL
Hboot 1.54
Radio 4A.17.3250.14
CID HTC_001
S ON
The phone was unlocked and rooted shortly after I bought it in July. I was using a Google edition Revolution HD 22 Rom, but I decided to try a CM10.2 ROM and this is where it all started to go wrong. I downloaded the CM Rom and started to flash it on my phone but I got a boot loop with a different screen repeating over the recovery screen so I tried to wipe it and reflash but in doing so I deleted everything. At that time I could get into the recovery screen where it said there wasn’t a ROM installed, so I tried flashing the ROM again but this time I can only get into the boot loader and Fastboot, with no option into recovery.
Things I have tried
unlocked In fastboot tried flashing various ROMs but at the end it says FAILED: (remote:not allowed
ROMs i have tried are the latest from HTC dev web site PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1 & CM10.2 roms and bootimg files but just get the Failed message at the end.
I have tried locking the boot loader and trying a RUU file but the same thing with failed messages at the end or wrong signature.
Is there something pretty basic I am missing because the fastboot cmds seem to work just not for flashing.
Aslo tried the adb side load but it doesn’t list my device and the cmd don’t work, they work fine in fastboot.
Any help would be appreciated before it ends up in bits!!
The cid on the phone and the ruu has to be the same.
---------- Post added at 07:03 PM ---------- Previous post was at 07:03 PM ----------
Try -off
andyp1 said:
Hi All,
Help required with my HTC One 801n. I have read and search numourse posts but still cant load a ROM or anything back onto it
The phone details
M7 UL
Hboot 1.54
Radio 4A.17.3250.14
CID HTC_001
S ON
The phone was unlocked and rooted shortly after I bought it in July. I was using a Google edition Revolution HD 22 Rom, but I decided to try a CM10.2 ROM and this is where it all started to go wrong. I downloaded the CM Rom and started to flash it on my phone but I got a boot loop with a different screen repeating over the recovery screen so I tried to wipe it and reflash but in doing so I deleted everything. At that time I could get into the recovery screen where it said there wasn’t a ROM installed, so I tried flashing the ROM again but this time I can only get into the boot loader and Fastboot, with no option into recovery.
Things I have tried
unlocked In fastboot tried flashing various ROMs but at the end it says FAILED: (remote:not allowed
ROMs i have tried are the latest from HTC dev web site PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1 & CM10.2 roms and bootimg files but just get the Failed message at the end.
I have tried locking the boot loader and trying a RUU file but the same thing with failed messages at the end or wrong signature.
Is there something pretty basic I am missing because the fastboot cmds seem to work just not for flashing.
Aslo tried the adb side load but it doesn’t list my device and the cmd don’t work, they work fine in fastboot.
Any help would be appreciated before it ends up in bits!!
Click to expand...
Click to collapse
Based on your CID you got the incorrect RUU. You should have gotten this one: RUU_m7_ul_k44_sense55_mr_htc_europe_4-19-401-9_r_radio_4a-23-3263-28_10-38r-1157-04l_release_353069_signed_2-1-exe Going forward once you get back up, you should think of getting S-OFF. It would give you more flexibility with ROM etc. But you also have to be more carefull.
Also, to run the RUU your bootloader must be locked/relocked since you are S-ON.
majmoz said:
Based on your CID you got the incorrect RUU. You should have gotten this one: RUU_m7_ul_k44_sense55_mr_htc_europe_4-19-401-9_r_radio_4a-23-3263-28_10-38r-1157-04l_release_353069_signed_2-1-exe Going forward once you get back up, you should think of getting S-OFF. It would give you more flexibility with ROM etc. But you also have to be more carefull.
Click to expand...
Click to collapse
that wont work as he is s-on, his HBOOT is 1.54 and that RUU has HBOOT 1.56, too many steps up, it will fail with image error.
you need to use this: http://www.htc1guru.com/2013/10/guru-reset-3-62-401-1-stock-rom/
or this one is probably better for you which is probably the same version you had on the phone to start with: http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
push it to your internal storage and flash like a custom rom, select wipe data, install stock recovery and install stock radio when prompted, you should get OTAs after that.
Related
Basically I successfully did everything necessary to unlock the bootloader and root the phone and I also flashed Superuser and had it confirmed by rootchecker. Where my phone got screwed is when i attempted to flash Android Revolution HD.
After flashing the ROM and pressing restart within TWRP recovery my phone went straight to the bootloader. Anything I did, from attempting to enter recovery or even power off the phone just sent me back to the bootloader.
I managed to re-flash TWRP and am able to access recovery BUT my entire phone is wiped (no backups ,roms, etc.) and my attempt to revert back to the original Sprint RUU has failed 3 times.
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Desperately in need of help as this phone is not even 2 weeks old.
MrAdrianP said:
Basically I successfully did everything necessary to unlock the bootloader and root the phone and I also flashed Superuser and had it confirmed by rootchecker. Where my phone got screwed is when i attempted to flash Android Revolution HD.
After flashing the ROM and pressing restart within TWRP recovery my phone went straight to the bootloader. Anything I did, from attempting to enter recovery or even power off the phone just sent me back to the bootloader.
I managed to re-flash TWRP and am able to access recovery BUT my entire phone is wiped (no backups ,roms, etc.) and my attempt to revert back to the original Sprint RUU has failed 3 times.
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Desperately in need of help as this phone is not even 2 weeks old.
Click to expand...
Click to collapse
Here you can find the RUU. I don't know wich one you want ..
Install this RUU in Fastboot (USB) otherwise it won't recognize your phone!
MrAdrianP said:
Basically I successfully did everything necessary to unlock the bootloader and root the phone and I also flashed Superuser and had it confirmed by rootchecker. Where my phone got screwed is when i attempted to flash Android Revolution HD.
After flashing the ROM and pressing restart within TWRP recovery my phone went straight to the bootloader. Anything I did, from attempting to enter recovery or even power off the phone just sent me back to the bootloader.
I managed to re-flash TWRP and am able to access recovery BUT my entire phone is wiped (no backups ,roms, etc.) and my attempt to revert back to the original Sprint RUU has failed 3 times.
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Desperately in need of help as this phone is not even 2 weeks old.
Click to expand...
Click to collapse
If you can still access TWRP, load another ROM onto a USB drive and plug it into your phone with an adapter. Flash properly by doing a complete wipe with TWRP and do a boot. It could have been a bad download initially. Did you do a MD5 sum check? As for the RUU, I've never done one (As I've never required an RUU *Knock on wood*) but from what I've read and seen, you need to revert everything you've done as in relocking the bootloader and reverting S-OFF if you've done that.
Athrun88 said:
If you can still access TWRP, load another ROM onto a USB drive and plug it into your phone with an adapter. Flash properly by doing a complete wipe with TWRP and do a boot. It could have been a bad download initially. Did you do a MD5 sum check? As for the RUU, I've never done one (As I've never required an RUU *Knock on wood*) but from what I've read and seen, you need to revert everything you've done as in relocking the bootloader and reverting S-OFF if you've done that.
Click to expand...
Click to collapse
Didn't check the MD5 & when attempting to use the RUU I did have S-ON(Never had S-OFF) and had the bootloader locked. But is there a way for me to push a rom to the phone using adb? I've tried before but it always says device not found.
Also, whenever i try to use the RUU the error I get has to with an incorrect Hboot version. Currently my Hboot is 1.44.0000.
MrAdrianP said:
Didn't check the MD5 & when attempting to use the RUU I did have S-ON(Never had S-OFF) and had the bootloader locked. But is there a way for me to push a rom to the phone using adb? I've tried before but it always says device not found.
Also, whenever i try to use the RUU the error I get has to with an incorrect Hboot version. Currently my Hboot is 1.44.0000.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2318497
Try this
MrAdrianP said:
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Click to expand...
Click to collapse
If your are S-ON you cannot flash an RUU that is older than your current firmware that's why its not working, you either have to stay on the same firmware or upgrade but you cannot downgrade so what you have to do is sideload a ROM using the tutorial dgtiii provided and everything will be back to normal, don't worry
im a HTC one user. Currently on a formatted sd card. that is, no android rom or software. All I have right now on my phone is an unlocked bootloader 1.54
CWM Recovery Touch v6.0.3.6
I am familiar with pushing roms from mac through adb commands on the sd card. learnt that when i bricked it last time. this time, i cant understand the problem. Umm.. I updated my ARHD rom to 4.3 stock google one from 4.2.2 sense based roms. After that, i remember, going through several roor related issues. So i tried switching roms. i tried flashing various roms but i couldnt get any of em to work. i tried flashing roms after wiping cache and everything recommended, but every rom got stuck on reboot. except the nandroid backup. nandroid backup worked fine. so i tried formatting the sd card as well and flashing a rom after pushng it by adb commands. i think i have problems with my root access. i tried flashing cwm recovery all over again through fastboot, but it still boots up randomly. and im still stuck on the google splashup screen. it keeps rebooting and getting stuck on the splashup screen and doesnt get past that to the htc reboot screen. I dont know what to do. splash up screen doesnt let me access adb commands. and i think i have improper root access as whenever i try to reboot from cwm recovery, it warns me about the su binary and then gets stuck stuck in a loop again.
please help me guys?
:crying:
ayeyokp said:
im a HTC one user. Currently on a formatted sd card. that is, no android rom or software. All I have right now on my phone is an unlocked bootloader 1.54
CWM Recovery Touch v6.0.3.6
I am familiar with pushing roms from mac through adb commands on the sd card. learnt that when i bricked it last time. this time, i cant understand the problem. Umm.. I updated my ARHD rom to 4.3 stock google one from 4.2.2 sense based roms. After that, i remember, going through several roor related issues. So i tried switching roms. i tried flashing various roms but i couldnt get any of em to work. i tried flashing roms after wiping cache and everything recommended, but every rom got stuck on reboot. except the nandroid backup. nandroid backup worked fine. so i tried formatting the sd card as well and flashing a rom after pushng it by adb commands. i think i have problems with my root access. i tried flashing cwm recovery all over again through fastboot, but it still boots up randomly. and im still stuck on the google splashup screen. it keeps rebooting and getting stuck on the splashup screen and doesnt get past that to the htc reboot screen. I dont know what to do. splash up screen doesnt let me access adb commands. and i think i have improper root access as whenever i try to reboot from cwm recovery, it warns me about the su binary and then gets stuck stuck in a loop again.
please help me guys?
:crying:
Click to expand...
Click to collapse
Flash stock recovery, then run it to flash stock.
ayeyokp said:
im a HTC one user. Currently on Renoir atted sd card. that is, no android rom or software. All I have right now on my phone is an unlocked bootloader 1.54
CWM Recovery Touch v6.0.3.6
I am familiar with pushing roms from mac through adb commands on the sd card. learnt that when i bricked it last time. this time, i cant understand the problem. Umm.. I updated my ARHD rom to 4.3 stock google one from 4.2.2 sense based roms. After that, i remember, going through several roor related issues. So i tried switching roms. i tried flashing various roms but i couldnt get any of em to work. i tried flashing roms after wiping cache and everything recommended, but every rom got stuck on reboot. except the nandroid backup. nandroid backup worked fine. so i tried formatting the sd card as well and flashing a rom after pushng it by adb commands. i think i have problems with my root access. i tried flashing cwm recovery all over again through fastboot, but it still boots up randomly. and im still stuck on the google splashup screen. it keeps rebooting and getting stuck on the splashup screen and doesnt get past that to the htc reboot screen. I dont know what to do. splash up screen doesnt let me access adb commands. and i think i have improper root access as whenever i try to reboot from cwm recovery, it warns me about the su binary and then gets stuck stuck in a loop again.
please help me guys?
:crying:
Click to expand...
Click to collapse
If you are unlocked but still S-ON...use revone to make it S-OFF
Than:
1) hold power button until the phone force reboots and in the meantime press vol - button to get into bootloader
2) now go to fastboot and plug the phone to the pc
3) through command line "fastboot writecid 11111111"
4) reboot bootloader
5) now you have supercid, flash any RUU and start using again your HTC one
I think it should work, sorry for my bad english
OsarcotL said:
If you are unlocked but still S-ON...use revone to make it S-OFF
Click to expand...
Click to collapse
He's on 1.54, he can't go s-off.
OsarcotL said:
If you are unlocked but still S-ON...use revone to make it S-OFF
Than:
1) hold power button until the phone force reboots and in the meantime press vol - button to get into bootloader
2) now go to fastboot and plug the phone to the pc
3) through command line "fastboot writecid 11111111"
4) reboot bootloader
5) now you have supercid, flash any RUU and start using again your HTC one
I think it should work, sorry for my bad english
Click to expand...
Click to collapse
i have a unlocked bootloader. and i have a s-off too! i achieved s-off through revone only!
OsarcotL said:
If you are unlocked but still S-ON...use revone to make it S-OFF
Than:
1) hold power button until the phone force reboots and in the meantime press vol - button to get into bootloader
2) now go to fastboot and plug the phone to the pc
3) through command line "fastboot writecid 11111111"
4) reboot bootloader
5) now you have supercid, flash any RUU and start using again your HTC one
I think it should work, sorry for my bad english
Click to expand...
Click to collapse
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?
ayeyokp said:
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?
Click to expand...
Click to collapse
i know that with supercid you can flash any RUU beacuse it bypasses the normal country control during the istallation of the program...
now, i don't know if you cant flash anything with the 1.54 hboot, but i dont think so. according to me, you can try to flash and in the worst case the istallation wont start...but obviously is your phone and your decisone, just as it is your responsability
ayeyokp said:
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?
Click to expand...
Click to collapse
Since you're S-Off and SuperCID you can flash any RUU, so just go ahead and you won't loose S-Off either.
The 1.54 restrictions only apply if you're not S-Off, because S-On won't allow you to downgrade. Since you're S-Off it will allow the RUU downgrade.
ayeyokp said:
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?
Click to expand...
Click to collapse
Being s-off means you can flash anything, even stuff not for this phone. So be careful.
Ruu.exe for Asia
http://www.androidruu.com/getdownlo...50.13_10.33.1150.01_release_311678_signed.exe
Or Europe
http://www.androidruu.com/getdownlo...31.27_10.31.1131.05_release_310878_signed.exe
Download the Ruu of your choice to your pc.
Connect phone via usb2 to pc with phone in fastboot usb mode
Run ruu you downloaded , answer questions as appropriate
Approximately ten minutes to have stock Rom and stock recovery
Will retain s off . Can accept ota updates without losing s off
Sent from my HTC One using xda app-developers app
Hi all.
I tried to flash my HTC one from recovery (twrp) after doing a factory reset within twrp. (I thought at the time a had stock recovery, I didn't. I had twrp.
Now my phone won't boot. Gets stuck on splash screen. If i enter the bootloader (which works no problem) and choose recovery, it starts recovery, pops up with twrp splash screen for second, then reboots to frozen htc splash screen.
Fastboot is working.
I've tried clearing the cache using fastboot. samething
I've tried flashing other recoveries,. nothing samething. (others in different predicaments have been able to do this successfully)
I've been reading that returning back to stock using RUU.zip method is the only way to go.
I want to try that, but before I do, I must make sure I understand it correctly and I've done all I can.
Relock the bootloader? Can I unlock it again?
Find a RUU.Zip that matches my OS version
Flash using fastboot.
I've been looking through HTC1GURU at his collection of ruu.zip but can't find anything that really matches my OS.
Any suggestions and advice will be most welcome.
Thanks in advance
Phone info.....
my Original CID was....orang001
profixit said:
Hi all.
I tried to flash my HTC one from recovery (twrp) after doing a factory reset within twrp. (I thought at the time a had stock recovery, I didn't. I had twrp.
Now my phone won't boot. Gets stuck on splash screen. If i enter the bootloader (which works no problem) and choose recovery, it starts recovery, pops up with twrp splash screen for second, then reboots to frozen htc splash screen.
Fastboot is working.
I've tried clearing the cache using fastboot. samething
I've tried flashing other recoveries,. nothing samething. (others in different predicaments have been able to do this successfully)
I've been reading that returning back to stock using RUU.zip method is the only way to go.
I want to try that, but before I do, I must make sure I understand it correctly and I've done all I can.
Relock the bootloader? Can I unlock it again?
Find a RUU.Zip that matches my OS version
Flash using fastboot.
I've been looking through HTC1GURU at his collection of ruu.zip but can't find anything that really matches my OS.
Any suggestions and advice will be most welcome.
Thanks in advance
Phone info.....
my Original CID was....orang001
Click to expand...
Click to collapse
There isn't any ruu for orange (.61 base) only a nandroid backup which require a working recovery to be flashed. if you don't really care about staying with the orange sw, you could simply restore your phone to international EU version (.401 base). You already have s-off and the proper mid, so it will only require to downgrade hboot to 1.44, change cid to HTC__001 and run the 1.29.401 ruu.exe. you can use this guide
Thanks for the quick reply and the guide.
I don't care about orange sw. I'll do some reading. I do have a nandroid backup. No good to me, unless I get recovery working.
Not too confident about downgrading the Hboot, but i'll read and read.
profixit said:
Thanks for the quick reply and the guide.
I don't care about orange sw. I'll do some reading. I do have a nandroid backup. No good to me, unless I get recovery working.
Not too confident about downgrading the Hboot, but i'll read and read.
Click to expand...
Click to collapse
downgrading hboot is pretty easy
just follow the steps under ''If you’re on hboot which is above 1.44'' from nkk71's guide
then change cid
then run ruu.exe
but do not use a win 8.1 computer (compatibility issue with hboot 1.44)
Thanks for that last bit, what about Win8.
I've spotted the steps that apply to me, just playing them out in my head.
Out of curiosity after a downgrade the HBoot, will it be locked and s-on?
profixit said:
Thanks for that last bit, what about Win8.
Click to expand...
Click to collapse
windows 8.0 should be fine, but definitively not 8.1
alray said:
There isn't any ruu for orange (.61 base) only a nandroid backup which require a working recovery to be flashed. if you don't really care about staying with the orange sw, you could simply restore your phone to international EU version (.401 base). You already have s-off and the proper mid, so it will only require to downgrade hboot to 1.44, change cid to HTC__001 and run the 1.29.401 ruu.exe. you can use this guide
Click to expand...
Click to collapse
I noticed that particular 1.29.401 ruu exe has a different model ID, gonna course problems?
profixit said:
I noticed that particular 1.29.401 ruu exe has a different model ID, gonna course problems?
Click to expand...
Click to collapse
sry my bad
use this one: http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_htc_europe_1-28-401-7_radio_4a-13-3231-27_10-31-1131-05_release_310878_signed-exe/
1.28.401
No worries, Thanks.
Can you try fastboot erase cache from fastboot menu and re enter recovery?
Tried that, thanks
Sent from my HTC One using Tapatalk
OK, a little lucky positive progress.
I managed to flash clockworkMod recovery, don't ask me how, maybe erasing the cache lots of times did it, i'm sure it was a recovery I had already tried. I checked my download list and confirmed I did download it., so i would of tried to flash it two days ago. Funny.
Still stuck on splash screen, but can boot into recovery. (clockworkmod)
Please, what is the best way to proceed, I'm thinking nandroid backup, but like I said, I couldn't care less about orange. I would love to put Mike1986 stock rom 4.3 or 4.4
I'm unable or don't know how to get folders or files on the phone's internal SD card, because it doesn't boot up a rom any more. Y-cable?
I'm concerned with all the "can't" at the bottom of recovery screen.
im not really sure what happened...
i was trying to root then s-off today. i got htcdev.com unlocked, was able to flash custom recovery (philz) and flash superuser. when i tried to s-off (firewater) i got the whelp this sucks error (im still not really sure why or what that means)
i tried to then flash a custom rom, and now it wont boot past the htc flash screen with the red text ( this may be because i didnt flash firmware with the rom i tried to install?)
i have tried to flash firmware, and run a ruu and nothing is doing anything...
please please please someone help
What firmware version do you currently have installed? What ROM were you trying to flash?
Take a look at this thread below for info on how to flash the latest RUU. If you have a HK version you'll need the HK RUU. After you run the RUU you'll need to reroot your phone. You'll also need to use the SunShine exploit to gain S-off (the "whelp" message means Firewater won't work on your device). I also recommend Captain Throwback's TWRP 2.8.0.0. recovery.
http://forum.xda-developers.com/showthread.php?t=2880328
im not sure which of these are the firmware...
hboot - 3.16.0.0000
radio - 1.05.20.0321_2
os - 1.54.654.9
Firmware is your radio version. Use the RUU from the link below. Follow the instructions for the manual system update. You'll need to relock your bootloader beforehand using the command "fastboot oem lock" while connected via Fastboot USB mode.
http://www.htc.com/us/support/htc-one-m8-harman-kardon-edition-sprint/news/
ohh i forgot about having to relock for ruu
trying that now
I downloaded the ruu, but when I run it it can't find my phone... I think it wants me to be booted into the ROM but I can't boot the only thing I can access is the bootloader
knock.back said:
I downloaded the ruu, but when I run it it can't find my phone... I think it wants me to be booted into the ROM but I can't boot the only thing I can access is the bootloader
Click to expand...
Click to collapse
RUU's are run from the bootloader...make sure it says fastbootusb when connected to your PC.
it did say that
Make sure you have HTC Sync installed on your computer.
I have that installed too... I got it to boot, ended up flashing different recovery then a different rom and that worked... Never got the ruu to work tho... Anyway, thanks for your help
Hi all,
So let me explain. I was given a HTC One for repair and the person just told me that her child did something wrong in the settings and the phone didn't boot anymore. The phone was on an older stock ROM and didn't get past the HTC One logo. Something was corrupted because the startup sound was cutting off before it had played like it should.
anyways: the phone is S-ON and I have unlocked the bootloader via HTCDev. I can install CWM, CWM Touch and TWRP but can't install any Sense rom because of the antique HBoot 1.56. I can however boot into CM 10.2.1 stable with no problems and ARHD 9.4 but with nou touch. On both ROMs firewather and rumrunner fail (usb debugging is on and root also for adb and apps).
Possible fixes I think off:
-Install an older ARHD version like 42 or 61 or 62 that is compitable with my firmware (but can't find them anywhere);
-install an insecure kernel compatible with CM10.2 (can't find one);
-Somehow just revert back to a Sense rom, wich I can't.
I just want S-off but every s-off tool fails. Is there another way to instal RUU exe or ZIP without S-OFF or at least upgrade the damn antique radio image that belongs in a museum ?
Thanks in advance
soulaiman said:
Hi all,
So let me explain. I was given a HTC One for repair and the person just told me that her child did something wrong in the settings and the phone didn't boot anymore. The phone was on an older stock ROM and didn't get past the HTC One logo. Something was corrupted because the startup sound was cutting off before it had played like it should.
anyways: the phone is S-ON and I have unlocked the bootloader via HTCDev. I can install CWM, CWM Touch and TWRP but can't install any Sense rom because of the antique HBoot 1.56. I can however boot into CM 10.2.1 stable with no problems and ARHD 9.4 but with nou touch. On both ROMs firewather and rumrunner fail (usb debugging is on and root also for adb and apps).
Possible fixes I think off:
-Install an older ARHD version like 42 or 61 or 62 that is compitable with my firmware (but can't find them anywhere);
-install an insecure kernel compatible with CM10.2 (can't find one);
-Somehow just revert back to a Sense rom, wich I can't.
I just want S-off but every s-off tool fails. Is there another way to instal RUU exe or ZIP without S-OFF or at least upgrade the damn antique radio image that belongs in a museum ?
Thanks in advance
Click to expand...
Click to collapse
Hboot 1.56 is not that old the current is 1.57! You can install RUU being S-ON the RUU must be the same or higher version, signed and the bootloader has to be locked/relocked. For Sense ROMs you might try TWRP 2.6.3.3 it seems to work best. ARHD 81 should work with your phone you have to wipe in Aroma before you install it.
I couldn't get ARHD 81 to work, but if someone is in the same situation here is what I did:
1) Relock your bootloader with this command:
fastboot oem lock
2) download this signed radio file : https://www.androidfilehost.com/?w=file-thanks&fid=23622183712460395&mid=70&download_id=t0kvkiiupbv0r5gakftasij7d5&tid=1412801244&hc=731cbdd91c39e4104b17bb47e6236fd9614838fa88b158009a1006be6b2ec5ea
3) Place the file in the same platform-tools directory for ease of use and insert this command:
fastboot oem rebootRUU
4) Once the phone reboots into a black HTC screen enter:
fastboot flash zip <name_of_the_file_here_without_quotes>
5) Normally it should succeed and tell you to immediatly flush, if it fails reattempt to flash the zip and it will succeed.
6) Download your prefered Recovery, mine is CWM but TWRP is even better sometimes and enter:
fastboot reboot-bootloader and then fastboot flash recovery <recovery.img>
6B) EDIT: to be able to flash a recovery IMG with S-On you need to unlock you bootloader again.
fastboot flash unlocktoken Unlocktoken_bin or whatever your unlocktoken is called
Then accept the security warning on your phone with the volume keys and power key.
7) Once succeed enter recovery and flash Maximus HD
8) Once done please enter bootloader again by pressing vol- + power or bij selecting advanced, reboot bootloader in recovery.
9) Because we're S-On, we need to manually flash boot.img
fastboot flash boot boot.img and if you get bootloops fastboot erase cache
Once this is done you should be able to boot into the rom and everything should work. Flashing this has upgraded my hboot to 1.57. Now I will report if I succeed to get S-off.
Well I couldn't find an RUU that was signed and for my version. Also I don't know why but I couldn't get ARHD to work. Maybe I need s-off or another recovery but even with elemental X it didn't boot.
soulaiman said:
Well I couldn't find an RUU that was signed and for my version. Also I don't know why but I couldn't get ARHD to work. Maybe I need s-off or another recovery but even with elemental X it didn't boot.
Click to expand...
Click to collapse
Okay so what I want to suggest you do is for starters go in unlock the bootloader as re locking it before doing anything is pointless when once everything is fixed is when you'd need to do it. Also I recommend that you install the custom recovery first and flash the rom from there rather than trying to flash it using fastboot as then at least we can get a standard recovery message which may be easier to find an answer for, I recommend using the very latest twrp recovery from their site as that should be able to flash all roms but make sure you install a stock sense 6 rom as the phone needs to be on the latest update with the kk radios and obviously that means having an hboot of 1.57 which would allow you to install custom roms that are running on kk otherwise you'll have issues and if you've followed what I suggest and it doesn't work a logcat and even a video of what is actually happening will help a lot to see what's going on but first things first is make sure that phone is on the latest hboot and the latest radio.
Also what version of phone is it? is it a m7ul? I'll send you an ruu link if I know what version we're looking at
dc959 said:
Okay so what I want to suggest you do is for starters go in unlock the bootloader as re locking it before doing anything is pointless when once everything is fixed is when you'd need to do it. Also I recommend that you install the custom recovery first and flash the rom from there rather than trying to flash it using fastboot as then at least we can get a standard recovery message which may be easier to find an answer for, I recommend using the very latest twrp recovery from their site as that should be able to flash all roms but make sure you install a stock sense 6 rom as the phone needs to be on the latest update with the kk radios and obviously that means having an hboot of 1.57 which would allow you to install custom roms that are running on kk otherwise you'll have issues and if you've followed what I suggest and it doesn't work a logcat and even a video of what is actually happening will help a lot to see what's going on but first things first is make sure that phone is on the latest hboot and the latest radio.
Also what version of phone is it? is it a m7ul? I'll send you an ruu link if I know what version we're looking at
Click to expand...
Click to collapse
Thanks for the info and help.
The phone is allready been returned to the owner, it was just a repair job because the phone was out of waranty and nobody in this town could fix it. in fact, some idiot that didn't know what he was doing flashed the wrong hboot version (other phone/model) on it somehow and it was a mess.
I did manage to repair it trough an RUU I found I think or I did install a custom sense 6 rom... I don' remember exactly but it had a mismatching hboot version that's all I remember