Alright so here is my predicament.
I have a T-Mobile HTC ONE.
I am S-OFF, have TWRP 2.5.0.0 installed on my device, my bootloader says ***LOCKED*** because I locked it using revone after performing S-OFF.
I tried to install ElementalX 1.1 and after installation, my phone would not boot.
I have tried pushing a different kernel to the device and flashing that in recovery as well but I got the same result - a nonbooting device.
I tried to fastboot flash a kernel, I tried to fastboot flash a different recovery to see if that would allow me to flash the kernel and get my phone booting. No dice. I get "REMOTE FAILED" or not allowed error.
I'm at a loss right now because I didn't back up my boot partition before trying to flash this kernel and I honestly don't know what to do short of doing the HTC Unlock process again and literally losing everything on my phone.. Photos and everything. I don't have a recent PC backup either so that absolutely has to be the last resort.
ANY and ALL help will be greatly appreciated. This is the first time I've ever been in this position and not known what to try next.
Thanks in advance,
Dan
Ok so I was able to use revone to unlock the bootloader again and was able to successfully flash CWM. I tried re-flashing the kernel using CWM and the phone still will not boot.
Does anyone else have any ideas?
dharvey4651 said:
Ok so I was able to use revone to unlock the bootloader again and was able to successfully flash CWM. I tried re-flashing the kernel using CWM and the phone still will not boot.
Does anyone else have any ideas?
Click to expand...
Click to collapse
Did you manage to get back your stuffs (photos and such) yet?
What rom were you running? Just dirty flash it
Sent from my Tricked out HTC One
ryryzz said:
Did you manage to get back your stuffs (photos and such) yet?
Click to expand...
Click to collapse
No I never was able to back up my stuff but I haven't given up yet. I'm refusing to re-flash an RUU until I have exhausted all other options.
Squirrel1620 said:
What rom were you running? Just dirty flash it
Sent from my Tricked out HTC One
Click to expand...
Click to collapse
I was running Trickdroid. I'm still trying to get it back up and running.. Going to try and fastboot flash boot.img from stock 1.29 T-Mobile ROM next and see if that can get it to boot.
EDIT>> Trying a dirty re-flash now.
EDIT2>> Seems a dirty re-flash was just what I needed. Phone is booting now. I appreciate the tip.
Wonder why trying to flash a kernel while running TrickDroid would result in a non-booting device though. Makes no sense.
dharvey4651 said:
No I never was able to back up my stuff but I haven't given up yet. I'm refusing to re-flash an RUU until I have exhausted all other options.
I was running Trickdroid. I'm still trying to get it back up and running.. Going to try and fastboot flash boot.img from stock 1.29 T-Mobile ROM next and see if that can get it to boot.
Click to expand...
Click to collapse
I believe that you can boot into your recovery, right? Did you try adb pull to grab your stuffs?
TrickDorid has its own boot.img, if you try to flash stock T-Mobile boot.img over, then I think it'll cause a mess to you ROM. Try to avoid doing that.
I advice you to try adb pull to get your stuffs and then flash a RUU over
ryryzz said:
I believe that you can boot into your recovery, right? Did you try adb pull to grab your stuffs?
TrickDorid has its own boot.img, if you try to flash stock T-Mobile boot.img over, then I think it'll cause a mess to you ROM. Try to avoid doing that.
I advice you to try adb pull to get your stuffs and then flash a RUU over
Click to expand...
Click to collapse
Well I did a dirty flash and re-flashed TrickDroid. It got my phone booting and it seems there were minimal side effects.
Think I got lucky this time.
Still don't know why a kernel flash would have resulted in a non-booting phone if it said successful.
The strangest thing is that it would actually boot but non-responsive and with a black screen. I was still able to use adb and that's how I was able to re-unlock the bootloader and try fastboot flash the kernel.
Wish I had ENG or modded hboot though so that I had extended fastboot commands and I didn't have to mess with revone but it all worked out for now.
Related
Hi all,
Got a sensation XL here which isn't rooted, nor has it been altered in anyway, not sure what happened to it to be honest and it's not actually mine either.
It's still s-on, I can get to the bootloader no problem, but factory reset just doesn't do anything, it just puts it back in the boot loop.
Any ideas?
Thanks.
PS: I'm thinking it's bricked.
Lock the bootloader (if that's been unlocked) and then try flashing the RUU to put it back to factory.
You're in england, so unless it's branded, the RUU you need is in the RUU thread in the dev forum, and it's 1.05.401.x that you want.
MinecraftZombi.es said:
Lock the bootloader (if that's been unlocked) and then try flashing the RUU to put it back to factory.
You're in england, so unless it's branded, the RUU you need is in the RUU thread in the dev forum, and it's 1.05.401.x that you want.
Click to expand...
Click to collapse
It's not been unlocked, it's just a stock handset, not branded, so with the official ruu, how do i flash it?
Thanks for replying m8.
make sure htc sync is installed on a PC (just for the drivers, you don't want to actually use it)
Plug the phone in via the USB (Direct, not through a hub)
Run RUU file on PC.
that should be it.
Thanks pal, fingers crossed eh.
Will let you know if it worked.
It didn't work
Tried both of the Europe RUU's but it still hasn't worked, says signature error?
Both of the files took an hour to download each.
Seriously hating this now
Any other ideas??
Thanks.
if that hasn't worked, next thing i'd try is to flash a custom ROM.
Can it get into fastboot?
If so, i'd unlock the bootloader, install the recovery and see if you can flash one of the custom ROMs.
MinecraftZombi.es said:
if that hasn't worked, next thing i'd try is to flash a custom ROM.
Can it get into fastboot?
If so, i'd unlock the bootloader, install the recovery and see if you can flash one of the custom ROMs.
Click to expand...
Click to collapse
Yea i went ahead and unlocked it but it's not letting me into the recovery, any ideas?
dladz said:
Yea i went ahead and unlocked it but it's not letting me into the recovery, any ideas?
Click to expand...
Click to collapse
Actually no i didn't i just used the HTC method.
What can i flash to get this thing working man, it's killing me, even factory reset doesn't work? That's just not normal, i'm s-on, i don't think theres an s-off method for the XL yet? Maybe there is.
But i'm really restricted as to what i can do, i've got fastboot and it works fine but besides that i'm lost.
factory reset uses the recovery partition. if that's chuffed, so's your hard reset.
I have attached the stock recovery from 1.05
go into fastboot.
when there, enter
Code:
fastboot flash recovery recovery.img
That should re-flash the recovery as long as your bootloader is unlocked. that might bring it back to life.
if it fails, flash the CWM recovery and then use a custom ROM
download the paul o'brien recovery and then use the same command as above, but using the name of the modaco recovery file
Code:
fastboot flash recovery r1-recovery-clockwork-5.0.2.7-modaco-runnymede.img
that should then allow you to flash a custom ROM
Ok so it's not bootlooping now on factory reset, it's just stopped on the white HTC screen after hitting factory reset.
I'll leave it there for a bit and see how it goes, i don't think it's going to progress though.
The device is defo unlocked.
Going into recovery brings it back to the bootloop.
It's different on factory reset just not recovery and neither are progressing, i'll give the other recovery a whirl.
Lol failed battery low
MinecraftZombi.es said:
factory reset uses the recovery partition. if that's chuffed, so's your hard reset.
I have attached the stock recovery from 1.05
go into fastboot.
when there, enter
Code:
fastboot flash recovery recovery.img
That should re-flash the recovery as long as your bootloader is unlocked. that might bring it back to life.
if it fails, flash the CWM recovery and then use a custom ROM
download the paul o'brien recovery and then use the same command as above, but using the name of the modaco recovery file
Code:
fastboot flash recovery r1-recovery-clockwork-5.0.2.7-modaco-runnymede.img
that should then allow you to flash a custom ROM
Click to expand...
Click to collapse
Nah m8, none of them worked or changed anything, the only difference being that factory reset on the stock recovery just stayed on the white htc screen, no change besides that.
Any other ideas? and thanks for taking the time to help me too.
I appreciate it.
I'm really not sure what else to suggest. if recovery just isn't loading after being flashed, then it suggests some sort of brick i think...
Even if there's no ROM installed, once a recovery is flashed, you should be able to at least access the recovery and from there install some sort of rom.
I'm beginning to suspect that it is indeed bricked, as you did in the first post.
MinecraftZombi.es said:
I'm really not sure what else to suggest. if recovery just isn't loading after being flashed, then it suggests some sort of brick i think...
Even if there's no ROM installed, once a recovery is flashed, you should be able to at least access the recovery and from there install some sort of rom.
I'm beginning to suspect that it is indeed bricked, as you did in the first post.
Click to expand...
Click to collapse
well i've been looking for some official ruu's to flash, one up from the one i'm on would do it i reckon, or at least give me a starting block.
I tried the test rom from a thread and now i can't find it
Will look again, find it and flash it, the test one didn't work, so i'm going to try a slightly older one.
fingers crossed, again.
Tried a new ROM but it froze on me. Then tried my back up and it would reboot after like a minute. So decided to do a full wipe but it deleted everything. I can get into the bootloader screen and TWRP but Windows can't read the phone and when it tries to install the drivers some of them fail. I have a copy of my recovery but need to know how to push it back to my phone and get the drivers installed right so that my PC can read my phone. Help.
TWRP seems to now act funny too where it'll like go to sleep and I have to press the home button or power button for a while before it turns the screen back on. Sometimes though I have to do the button combo to get back into recovery.
RUU
So I RUU'd the phone and it's working now, thanks. But it still shows unlocked and with S-OFF. So at this point can I just proceed with rooting it or do I have to lock it and put it back to S-ON before trying to re-root it? Or can I just try rooting it and putting a recovery image on it? It's been a while since I rooted it and obviously there was no 4.3 out at that time.
No need to re-lock or s-on just flash recovery and flash a rooted rom
bigdaddy619 said:
No need to re-lock or s-on just flash recovery and flash a rooted rom
Click to expand...
Click to collapse
Thanks for taking the time to help me out. So I installed v.2.5 of TWRP that I had instead of the newer version and it just freezes at the main screen. I can reflash it but it does the same thing. I get an error when trying to flash the newer version. How can I remove/delete the recovery image to flash the latest version?
QuiQNeZZ said:
Thanks for taking the time to help me out. So I installed v.2.5 of TWRP that I had instead of the newer version and it just freezes at the main screen. I can reflash it but it does the same thing. I get an error when trying to flash the newer version. How can I remove/delete the recovery image to flash the latest version?
Click to expand...
Click to collapse
You should be able to flash right over the older version make sure you download a fresh version of 2.6.3.0 from here http://techerrata.com/browse/twrp2/m7wls
Also remember after flashing the recovery.img type fastboot erase cache
The other thing is go into settings/screen and disable screen timeout that should take care of the "freezing" problem
Hi guys,
I seem to have a problem
So I was running 4.4.2 with Sense 5.5 on my phone. Vodafone (my phone company in Aus) sent out an OTA update for my phone. I'd already rooted my phone and had a custom recovery, so I knew I wasn't able to install it without going back to stock. So I tried following the procedure to go back to stock. Used 'Guru_Reset_M7_2.24.980.2' to do it and it seemed to work pretty well. It was 4.3, so I did an OTA, first one (like a 3mb file) installed fine, then the second one for 4.4.2 Sense 5.5 downloaded and installed, but not it is stuck in a boot loop. So I tried to do a factory reset from the bootloader which sent it back into the bootloop, then as nothing was working, I thought I'd install the custom recovery (TWRP) and install the ROM again and just leave it at that so at least I have a phone. Only problem is I had to unlock the bootloader again which wiped everything on the internal storage. And I'm stuck.
There's nothing in the internal memory. It's stuck in a bootloop after an OTA. I have TWRP installed as my recovery. I can access both recovery and bootloader.
Any idea's?
Also, for some reason, I can't download or access anything from this website; http://ww35.bugsylawson.com/ which I've seen used in multiple places to try and unbrick your phone
Thanks all!
Gunny007 said:
Hi guys,
I seem to have a problem
So I was running 4.4.2 with Sense 5.5 on my phone. Vodafone (my phone company in Aus) sent out an OTA update for my phone. I'd already rooted my phone and had a custom recovery, so I knew I wasn't able to install it without going back to stock. So I tried following the procedure to go back to stock. Used 'Guru_Reset_M7_2.24.980.2' to do it and it seemed to work pretty well. It was 4.3, so I did an OTA, first one (like a 3mb file) installed fine, then the second one for 4.4.2 Sense 5.5 downloaded and installed, but not it is stuck in a boot loop. So I tried to do a factory reset from the bootloader which sent it back into the bootloop, then as nothing was working, I thought I'd install the custom recovery (TWRP) and install the ROM again and just leave it at that so at least I have a phone. Only problem is I had to unlock the bootloader again which wiped everything on the internal storage. And I'm stuck.
There's nothing in the internal memory. It's stuck in a bootloop after an OTA. I have TWRP installed as my recovery. I can access both recovery and bootloader.
Any idea's?
Also, for some reason, I can't download or access anything from this website; http://ww35.bugsylawson.com/ which I've seen used in multiple places to try and unbrick your phone
Thanks all!
Click to expand...
Click to collapse
instructions
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_31.6.zip
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
Click to expand...
Click to collapse
clsA said:
instructions
Click to expand...
Click to collapse
Will this enable me to go fully back to stock and perform OTA updates, or is this just a way to get me out of a rut?
Thanks for the help by the way, currently in the process of doing the sideload.
Gunny007 said:
Will this enable me to go fully back to stock and perform OTA updates, or is this just a way to get me out of a rut?
Thanks for the help by the way, currently in the process of doing the sideload.
Click to expand...
Click to collapse
your just flashing a rom ...nothing to do with getting updates
clsA said:
your just flashing a rom ...nothing to do with getting updates
Click to expand...
Click to collapse
Thanks for the help man, I tried doing an ADB before I posted this and it didn't work for some reason, but when I used this ROM, worked perfectly fine. Just updated to 71.1 just then as well, so now phones working a-okay. Thanks again man!
Gunny007 said:
Thanks for the help man, I tried doing an ADB before I posted this and it didn't work for some reason, but when I used this ROM, worked perfectly fine. Just updated to 71.1 just then as well, so now phones working a-okay. Thanks again man!
Click to expand...
Click to collapse
Good to here
Hi,
I just got a brand new HTC One 7 (WWE, CID E_11) after my last one died. Im trying to root it and install a custom recovery to install arhd or insertcoin. I used htc one toolkit for this. Everything seemed to work ok, but after booting the installed rom (ARHD or insertcoin) the phone reboots after i see the login screen. I somehow managed to reinstall my phone again yesterday, as it was a complete (soft) brick.
I used this to return to stock:
http://forum.xda-developers.com/showthread.php?t=2759000
Now does anyone know why I get a reboot loop? Does anyone know if i installed this stock rom if I get the normal OTA updates again? And do i need to relock the bootloader for this? I would really like to install stock roms again but I'm a little anxious after yesterday. (I've installed custom roms since the old HD2/HTC desire, and also on my old HTC One M7, never had any problems, I think it has to do with the Hboot).
Hoping to hear from you guys,
best wishes,
Olaf
Agil1ty said:
Hi,
I just got a brand new HTC One 7 (WWE, CID E_11) after my last one died. Im trying to root it and install a custom recovery to install arhd or insertcoin. I used htc one toolkit for this. Everything seemed to work ok, but after booting the installed rom (ARHD or insertcoin) the phone reboots after i see the login screen. I somehow managed to reinstall my phone again yesterday, as it was a complete (soft) brick.
I used this to return to stock:
http://forum.xda-developers.com/showthread.php?t=2759000
Now does anyone know why I get a reboot loop? Does anyone know if i installed this stock rom if I get the normal OTA updates again? And do i need to relock the bootloader for this? I would really like to install stock roms again but I'm a little anxious after yesterday. (I've installed custom roms since the old HD2/HTC desire, and also on my old HTC One M7, never had any problems, I think it has to do with the Hboot).
Hoping to hear from you guys,
best wishes,
Olaf
Click to expand...
Click to collapse
Flash the stock firmware 5.11.401.10! I think your firmware is mismatched.
By flashing the firmware after installing the Rom I might fix the bootloop? Or is the stock firmware necesarry to go back to stock? Sorry bit confused, thanks for your response btw
Sent from my HTC One using XDA Free mobile app
Agil1ty said:
By flashing the firmware after installing the Rom I might fix the bootloop? Or is the stock firmware necesarry to go back to stock? Sorry bit confused, thanks for your response btw
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Flashing the firmware might fix the boot-loop, since you flashed the stock rom! If it does stop the boot-loops, you can re-install TWRP or CWM to get the custom recovery.
Agil1ty said:
By flashing the firmware after installing the Rom I might fix the bootloop? Or is the stock firmware necesarry to go back to stock? Sorry bit confused, thanks for your response btw
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
when using a sense custom rom you need to make sure you use twrp 2.6.3.3 recovery, do not use the toolkits, most of the time they are out of date and not updated, this would explain the bootloops, take the time to learn how to use adb and fastboot, you'll never look back.
nothing to do with the firmware and no need to flash it, if your firmware was knackered, you would have a hard brick.
Seanie280672 said:
when using a sense custom rom you need to make sure you use twrp 2.6.3.3 recovery, do not use the toolkits, most of the time they are out of date and not updated, this would explain the bootloops, take the time to learn how to use adb and fastboot, you'll never look back.
nothing to do with the firmware and no need to flash it, if your firmware was knackered, you would have a hard brick.
Click to expand...
Click to collapse
First of all thanks for the quick response. I know how to use adb and fastboot (at least I think).
If i would (in this order) do the following, would that be correct?:
unlock using htdev
Flash twrp 2.6.3.3 using fastboot command: "fastboot flash recovery recovery.img" (naming twrp 2.6.3.3.img = recovery.img)
reboot bootloader
Flash SuperSU.zip in TWRP
reboot twrp
flash custom rom (ARHD).
The thing is it isn't a normal bootloop (which normally would come with the HTC logo all the time)
It reboots when I try to setup the phone (in the setup menu). Restoring the phone with the link in the OP, ive recoverd my phone, but I would still love to use custom roms again.
Agil1ty said:
First of all thanks for the quick response. I know how to use adb and fastboot (at least I think).
If i would (in this order) do the following, would that be correct?:
unlock using htdev
Flash twrp 2.6.3.3 using fastboot command: "fastboot flash recovery recovery.img" (naming twrp 2.6.3.3.img = recovery.img)
reboot bootloader
Flash SuperSU.zip in TWRP
reboot twrp
flash custom rom (ARHD)
Click to expand...
Click to collapse
unlock using HTC Dev
flash TWRP 2.6.3.3
fastboot erase cache
fastboot reboot-bootloader
enter recovery
no need to flash super user it will be included in the rom you flash
flash custom rom, or stock reset rom, if its not rooted, twrp will ask you if you would like to root upon exit.
Seanie280672 said:
unlock using HTC Dev
flash TWRP 2.6.3.3
fastboot erase cache
fastboot reboot-bootloader
enter recovery
no need to flash super user it will be included in the rom you flash
flash custom rom, or stock reset rom, if its not rooted, twrp will ask you if you would like to root upon exit.
Click to expand...
Click to collapse
It seems that insertcoin had a problem in it's installer:
http://insertcoin-roms.org/category/devices/one_m7/one_sense6/
the changelog says: Fixed SuperSU install (might solve the sudden reboot issue in SetupWizard)
It left me without any rom to install, so i had to sideload ARHD, which it didnt want to install via sideload... The next step I isntalled stock again, which I'm using right now.. but I miss xposed framework and other tweaks too much..
I'm gonna try to unlock it again this afternoon and install insertcoin again, but this time ill make a backup first. Does installing the recovery wipe anything?
Agil1ty said:
It seems that insertcoin had a problem in it's installer:
http://insertcoin-roms.org/category/devices/one_m7/one_sense6/
the changelog says: Fixed SuperSU install (might solve the sudden reboot issue in SetupWizard)
It left me without any rom to install, so i had to sideload ARHD, which it didnt want to install via sideload... The next step I isntalled stock again, which I'm using right now.. but I miss xposed framework and other tweaks too much..
I'm gonna try to unlock it again this afternoon and install insertcoin again, but this time ill make a backup first. Does installing the recovery wipe anything?
Click to expand...
Click to collapse
no it doesn't wipe anything, but you can use xposed and its tweaks on stock rom, you just need to root first, just install TWRP, enter recovery and again upon exit it will offer to root stock rom for you.
I have an AT&T HTC One that was converted a Developer Edition, so it is S-OFF and has an unlocked bootloader, otherwise it is running completely stock non-rooted Lollipop firmware. I want to flash a custom recovery, but the safer side of my mind always tests it by doing "fastboot boot recovery.img" first before flashing it. The problem is on this phone it will load, I can see the green bar on the side of the Hboot screen go up, and fastboot says it sent the file successfully, but it just locks up and does nothing, I have to long-press power for 15 seconds or so to get it to shutdown to get it to respond again.
I have tried several versions of TWRP from here: http://techerrata.com/browse/twrp2/m7 and all have the same results. I am very familiar with using fastboot and adb, so I don't think I am doing anything wrong, but I am scared to flash the recovery image if I can't boot it.
Any ideas?
acejavelin said:
I have an AT&T HTC One that was converted a Developer Edition, so it is S-OFF and has an unlocked bootloader, otherwise it is running completely stock non-rooted Lollipop firmware. I want to flash a custom recovery, but the safer side of my mind always tests it by doing "fastboot boot recovery.img" first before flashing it. The problem is on this phone it will load, I can see the green bar on the side of the Hboot screen go up, and fastboot says it sent the file successfully, but it just locks up and does nothing, I have to long-press power for 15 seconds or so to get it to shutdown to get it to respond again.
I have tried several versions of TWRP from here: http://techerrata.com/browse/twrp2/m7 and all have the same results. I am very familiar with using fastboot and adb, so I don't think I am doing anything wrong, but I am scared to flash the recovery image if I can't boot it.
Any ideas?
Click to expand...
Click to collapse
Only hboot 1.44 will boot recovery .. all the others need to be flashed
TWRP 2.6.3.3 is the most stable
TWRP 2.8.4.0 is what I use with no problems
clsA said:
Only hboot 1.44 will boot recovery .. all the others need to be flashed
Click to expand...
Click to collapse
OK, that makes sense then... I am on 1.61 I think, and when I got it it was on 1.5 something.
Seems odd that being S-off and unlocked prevents fastboot booting to occur... wonder why?
acejavelin said:
OK, that makes sense then... I am on 1.61 I think, and when I got it it was on 1.5 something.
Seems odd that being S-off and unlocked prevents fastboot booting to occur... wonder why?
Click to expand...
Click to collapse
it was patched in the hboot to not allow it
clsA said:
it was patched in the hboot to not allow it
Click to expand...
Click to collapse
I guess I can see why they would do that, sort of, not that I agree... On my old HTC Rezound you could boot recovery and backup, wipe caches, etc, as long as you didn't write to boot/system/etc, without triggering the TAMPERED flag, you had to flash recovery or write to a system partition in order to set that flag. Oh well, Ill flash it up soon and play with it. I am actually kind of liking the stock lollipop Sense ROM, might just leave it like that for a bit though. Just came back from the range and had a little time before work so I was playing with it and it kind of frustrated me.
Thanks for your help and info.