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.
Okay here it goes.....
I am not new by any means. I know how to use adb and fastboot
Last night i had ARHD 11 and I wanted to go back to ViperOne. I had been restoring backups of both all day. When I got home, I dowloaded the ViperOne Rom again (not restoring recovery ) to reflash after a factory reset. I hit factory reset, flashed viper, and as soon as it rebooted I went into boot loop. I tried everything to get out of boot loop whenever I tried factory reset or recovery it just boot looped. I even flashed the RUU for 2.17,401. Then I decided for the hell of it change cid to CWS__001 because its an ATT phone. That did it.... I rebooted into viper one with no issue. the only problem now is I cannot change my CID anymore. When I do it Boot loops, Is it possible that the 2.19 base in ARHD closed the CID write? I know its not firmware just a base, but I never had this problem when I was just restoring backups. Any thoughts or Ideas? I am going to try to restore my backups now, I just hope I can change my CID.
Edit: After Restoring My Backup I was able to change CID again. Just a heads up if anyone bootloops and when they enter recovery it just keeps rebooting change CID to Factory CID then restore backup.
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
hi all,
sorry to sound like a complete idiot in advance !
I have been trying for over a month now to find some way to return my phone to stock so I can get the new ota update but im just having no luck !
I have tried everything to unroot , relock boot loader, and return to stock, I can successfully unroot, successfully relock the boot loader but cannot update OTA everytime I download the ota and allow the phone to start update process the phone boots into bootlaoder and a new line appears in the normal messages **** security warning*** when this happens I loose recovery and the phone hasn't updated. I then have to re-unlock the bootloader to then flash a recovery.
I cant flash RUU as there isn't an RUU available for me, H3G_001 , I have tried the suggested CWM nandroid backup, but this fails half way through something to do with android_secure
I cant seem to get the phone to successfully grant s-off to try the change cid method, I have tried to do this using HTC one kit by hasoon but no luck,
if anyone could please help it would me much appreciated
regards
okz19
Probably you don't have the stock rom or the recovery, because the secure warning come out when you aren't fully stock..
Look on this site: http://www.htc1guru.com/downloads/stock-rom-downloads/
Mine One works now fine and i have update to the latest OTA.
Justin2003 said:
Look on this site: http://www.htc1guru.com/downloads/stock-rom-downloads/
Mine One works now fine and i have update to the latest OTA.
Click to expand...
Click to collapse
Is better link to XDA
still stuck!
hi all as you can probably tell form the age of this topic, I have been stuck for a while !!! (11 October ! )
I am still having problems trying to get the new update 2.24.771.3
my phone is carrier locked to three uk
it is unrooted
custom recovery cwm touch
bootloader unlocked / tampered
I understand I need stock recovery and to lock bootloader
I don't have stock rom
my problem is as follows, my phone has been telling me for atleast 4 months now that I have a software update, when I click it it restarts takes me to cwm recovery verifys install then gets stuck on cannot mount data ....
I understand I need to flash stock recovery, I have tried to do this using the "all in one kit" however when I click flash my own recovery, (phone reboots into bootloader) I then proceed to select the stock recovery.img the cmd box then hangs "waiting for device" I am then alerted by my computer that the usb device has malfunctioned. ( I am on windows 8 and have turned of signature verification)
I cannot use the supposed simple method of RUU as there isn't one available for my stupid network!!
I have tried to use a cwm recovery image, this usually starts then spits out android_secure is missing.
yes I do have a hammer ready to hit the phone with, but just before I do this is there ANYONE with any last tips to help me, because ive just about had enough with this stupid phone !
the phone has 24 hours left to live, can you save its life ?
thanks in advance for any help.
1. You cannot install an OTA with a custom recovery.
2. I've encountered a CWM bug having to do with .android_secure. There's a hidden folder in /sdcard that caused it, I don't remember whether this file is ".android_secure" or another. You can probably wipe the sdcard before restoring the backup. If that fails, you can probably manually restore the backup with ADB (this will be hard).
3. If you want to install the custom recovery, boot to the fastboot and use USB to install the recovery. Don't use a toolkit because they're useless when anything goes wrong.
hello there,
i own an htc one m7 from o2 uk CID o2__001 . More specific the phone was routed and i decided to go back to the stock rom in order to get the updates , when accidentally i erased the system files and the phone now has no OS.
The main problem is that the phone is S-ON HBOOT 1.57 and doesnt allow me to change the CID in order to install any rom. I think the only way to get this thing work is to find an RUU or rom.zip file of the version 5.21.206.3 which was the previous and original one. Both CWM and TWRP recoveries fails to install any rom except the revolution hd which uses aroma installer, but it also fails in the end of the process , it throws me back to recovery when it starts to boot.
I tried to turn the S to Off but i read that the phone has to be able to boot to the main screen which is impossible at this time .
i would appreciate if anyone could find the suitable rom for my phone or at least if someone can backup his rom and give me the backup files.
if there is any other way to make the phone work i would be pleased to inform me !
thanks in advance
Chris
tongez said:
hello there,
i own an htc one m7 from o2 uk CID o2__001 . More specific the phone was routed and i decided to go back to the stock rom in order to get the updates , when accidentally i erased the system files and the phone now has no OS.
The main problem is that the phone is S-ON HBOOT 1.57 and doesnt allow me to change the CID in order to install any rom. I think the only way to get this thing work is to find an RUU or rom.zip file of the version 5.21.206.3 which was the previous and original one. Both CWM and TWRP recoveries fails to install any rom except the revolution hd which uses aroma installer, but it also fails in the end of the process , it throws me back to recovery when it starts to boot.
I tried to turn the S to Off but i read that the phone has to be able to boot to the main screen which is impossible at this time .
i would appreciate if anyone could find the suitable rom for my phone or at least if someone can backup his rom and give me the backup files.
if there is any other way to make the phone work i would be pleased to inform me !
thanks in advance
Chris
Click to expand...
Click to collapse
latest ruu for your version is a dowgrade and will require s-off to be flashed. Unless you find a nandroid backup of your version, you'll have to s-off in order to restore your phone back to stock.
Which version of twrp are you using?
The latest ruu i have found is the 4.20.206.16, but it stucks at 5% and either gives the error (htc_fastboot stoped working) with twrp recovery but just stacks there without the error if i use cwm or the stock of the 5.21.206.3. If i try to push it manualy it returns an error that the file is verry big. The newest recoveries that i can use is twrp 2.6.0.3 and cwm 6.0.3.1 and doesnt accepts any newer version of them, if i use newer it starts bootloop. I m 99% sure that if give me a nandroid backup it will work for sure.
tongez said:
The latest ruu i have found is the 4.20.206.16, but it stucks at 5% and either gives the error (htc_fastboot stoped working) with twrp recovery but just stacks there without the error if i use cwm or the stock of the 5.21.206.3. If i try to push it manualy it returns an error that the file is verry big. The newest recoveries that i can use is twrp 2.6.0.3 and cwm 6.0.3.1 and doesnt accepts any newer version of them, if i use newer it starts bootloop. I m 99% sure that if give me a nandroid backup it will work for sure.
Click to expand...
Click to collapse
you can not flash 4.20.206.16 RUU over 5.21.206.3, it require s-off. For ARHD, you need twrp 2.6.3.3 in order to flash it correctly. Try updating twrp to 2.6.3.3:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-boodloader
Thank you Alray for your help you are the best it worked as you said