[Q] Stuck on boot after KK update - One (M7) Q&A, Help & Troubleshooting

This is for my friend's ATT One. Bone stock, unrooted, S-On, no changes made to the device from the store. He took the OTA for Kit Kat and was running fine, then his phone rebooted on him a couple days later and won't go past the white HTC boot screen.
Two problems: First, I cannot use ADB, as it does not detect his phone. When I plug in his phone, it says drivers failed to install for HTC MTP device. I also have an HTC One, unlocked, S-Off, etc., and when I plug mine in, it's detected and ADB works just fine like always (so it's not that I need to reinstall drivers).
Problem 2: the phone seems to hang trying to do a factory reset from the bootloader menu, or from the stock recovery menu. It will start the reset, reboot to the white HTC screen then hang. I left it for more than an hour twice. Nothing doing.
Is there a way to reflash/restore his phone without wiping his sdcard? He's OK losing the data partition, but wiping sdcard is last resort. Using an RUU .exe will wipe his sdcard, as will unlocking his bootloader to try to install a custom recovery. Just not really sure what tools I have at my disposal with a stock recovery and no adb. Will fastboot flashing a rom.zip extracted from the ATT RUU also wipe his sdcard? Or does that only happen with the RUU .exe? Any ideas appreciated..

Shott3r said:
This is for my friend's ATT One. Bone stock, unrooted, S-On, no changes made to the device from the store. He took the OTA for Kit Kat and was running fine, then his phone rebooted on him a couple days later and won't go past the white HTC boot screen.
Click to expand...
Click to collapse
Did you tried wiping /cache?
Shott3r said:
Two problems: First, I cannot use ADB, as it does not detect his phone.
Click to expand...
Click to collapse
ADB can only be used when phone is booted+usb debug on or via custom recovery
Shott3r said:
He's OK losing the data partition
Click to expand...
Click to collapse
I hope so, factory reset is a /data wipe... probably already wiped from your first attempt to factory reset
Shott3r said:
but wiping sdcard is last resort. Using an RUU .exe will wipe his sdcard
Click to expand...
Click to collapse
And the available ruu.exe for at&t is a downgrade in version so it will require s-off.
Shott3r said:
Will fastboot flashing a rom.zip extracted from the ATT RUU also wipe his sdcard? Or does that only happen with the RUU .exe? Any ideas appreciated..
Click to expand...
Click to collapse
you can't flash a rom directly from fastboot. You can flash a rom via a custom recovery or flash a ruu.zip from RUUmode (fastboot oem rebootRUU).
Unfortunately I think there is no way to save /sdcard. You will need to unlock bootloader to flash a custom recovery.
easy way:
flash twrp custom recovery
flash guru reset rom for your version
or
flash twrp custom recovery
flash and use arhd rom
or the long way:
flash twrp
flash arhd
s-off
flash ruu.zip

alray said:
Did you tried wiping /cache?
...
you can't flash a rom directly from fastboot. You can flash a rom via a custom recovery or flash a ruu.zip from RUUmode (fastboot oem rebootRUU).
Unfortunately I think there is no way to save /sdcard. You will need to unlock bootloader to flash a custom recovery.
...
Click to expand...
Click to collapse
I did erase cache first thing. Regarding flashing the ruu.zip from RUUmode, my question is whether flashing the ruu.zip will erase the sdcard? Also does it even matter, since he has KK firmware, and is S-On? Will the ruu.zip from Jellybean 4.3 even flash on his (current) KK firmware?
Any ideas on why the factory reset would hang? Cuz that's best case scenario is to simply factory reset, but it seems not to work presently.

Shott3r said:
I did erase cache first thing. Regarding flashing the ruu.zip from RUUmode, my question is whether flashing the ruu.zip will erase the sdcard? Also does it even matter, since he has KK firmware, and is S-On? Will the ruu.zip from Jellybean 4.3 even flash on his (current) KK firmware?
Any ideas on why the factory reset would hang? Cuz that's best case scenario is to simply factory reset, but it seems not to work presently.
Click to expand...
Click to collapse
ruu will wipe everything.
and no you can't use ruu with s-on because its a downgrade in version.

Is there any way that you know of to get access to the sdcard in the circumstance I've described to try to rescue some files before I set about with the rescue? Doubt it, but just asking.

Shott3r said:
Is there any way that you know of to get access to the sdcard in the circumstance I've described to try to rescue some files before I set about with the rescue? Doubt it, but just asking.
Click to expand...
Click to collapse
maybe you could use remote recovery booting (booting a custom recovery without installing it). Not sure if it still can be done (think it was disabled in 4.2.2)
fastboot boot name_of_recovery.img
then use adb from recovery to copy sdcard content to your computer
adb pull /sdcard C:\somefolder
If you can't boot from a remote recovery, then I think you can say goodbye to those files in your /sdcard

Related

Boot loop prior to rooting or s-off, on stock, can't get to main screens

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.

[Q] Phone wont boot into ROM properly

HTC Vivid
I am new to this so i know I'm probably just doing something stupid. I searched the other forums but i couldn't find what i needed for my phone.
The WiFi on my phone wouldn't work and i read that flashing a new ROM onto the phone could fix that problem. I rooted the phone and tried to flash a ROM. The first ROM i downloaded didnt have a boot.img. So i flashed the entire zip file. I did a factory reset on CWM recovery because i was in a bootoop and now i try to install another ROM it wont work.
I also wiped the cache partition, formated the /cache, /data, and /system following this fourm. http://forum.xda-developers.com/showthread.php?t=1926754
The ROM still didnt work properly. Help plz???
Unzip rom, take boot.img out of it, and fastboot flash boot.img should get you ready to roll.
Sent from my Vivid 4G using xda app-developers app
it just goes to a black screen on startup. would this be because the ROM isnt finished/working?
When you reboot it just goes to black screen? If I was u just relock the bootloader, and flash stock ruu, than unlock it again, install twrp, flash rom, flash boot.img, wipe cache and dalvik, reflash boot.img, and reboot and you're good to go!
HTC Vivid with Sense 4+ ICS 4.0.4
[email protected] said:
When you reboot it just goes to black screen? If I was u just relock the bootloader, and flash stock ruu, than unlock it again, install twrp, flash rom, flash boot.img, wipe cache and dalvik, reflash boot.img, and reboot and you're good to go!
HTC Vivid with Sense 4+ ICS 4.0.4
Click to expand...
Click to collapse
I tried the ruu but when i click open for directions it wont open the instructions ( using hasoon2000s toolkit). Error saying it cant open a url. Try retyping it and try again
airraid823 said:
I tried the ruu but when i click open for directions it wont open the instructions ( using hasoon2000s toolkit). Error saying it cant open a url. Try retyping it and try again
Click to expand...
Click to collapse
Ment s off for bootloader not ruu. Sorry
airraid823 said:
Ment s off for bootloader not ruu. Sorry
Click to expand...
Click to collapse
I hate when people fail to mention to obvious noobs that they need a stock recovery to run the RUU. I found that out the hard way when I decided to attempt it because I got tired of being stuck in a bootloop.

[Q] Rooted with stock sense and recovery ota

Hello,
I'd like to ask few question about using the factory reset option with a stock 4.3 sense rom (unlocked bootloader, rooted and twrp recovery)
So, i rooted my device to try out viper4android but turns out its completely useless to me as i later learned that stock does not allow read/write to system partition and now i'm wondering how to go back safely.
As i said above, i'm still using the stock 4.3 rom with an unlocked bootloader no other changes made, so my question is to go back stock (using factory reset) do i need to:
1. Flash stock recovery and do a factory reset.
2. Flash stock recovery, relock bootloader and do a factory reset.
3. Guru reset M7
4. Other?
Thanks ~
EDIT:
Quick update, so just flashed stock recovery and used factory reset, now ofc the root did remain, so now my question is, can i
take ota safely with stock rom/recovery but rooted?
Thanks ~
Anyone please, are any of my choices the good one (if so wich one)?
Goolum said:
Anyone please, are any of my choices the good one (if so wich one)?
Click to expand...
Click to collapse
This is the way to go back to a stock ROM:
http://forum.xda-developers.com/showthread.php?t=2541082
If you’re on hboot which is above 1.44, then first thing is to downgrade that:
so download this: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
in bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip <---- just in case the above said “failed flush again”
fastboot reboot-bootloader
--> and confirm hboot is now 1.44
Thank you for your help, the problem is i'm on hboot 1.55 and rumrunner ain't working because of the
secure stock kernel, so i cannot go with the ruu way, wich is why i was wondering if i could simply use
the factory reset option since other than being rooted it is fully stock, or else the htc1 guru reset option.
Goolum said:
Anyone please, are any of my choices the good one (if so wich one)?
Click to expand...
Click to collapse
Post ur getvar all if ur confused as to which RUU to flash
As i said above flashing a ruu ain't an option since i'm s-on, what i meant by factory reset is the built in option (either through fastboot
or settings) with stock sense since i did not change anything, just unlocked the bootloader and rooted, and if that's not possible then if
guru reset utility for peoples with s-on is a good idea.
So i ended flashing stock recovery and used factory reset, everything did go alright tho ofc the root did remain, so now my question is, can i
take kitkat ota safely with stock rom/recovery but rooted? Or the fact that it's rooted risk messing up stuff? Oh and i dont mind loosing root.
Thanks ~
Goolum said:
So i ended flashing stock recovery and used factory reset, everything did go alright tho ofc the root did remain, so now my question is, can i
take kitkat ota safely with stock rom/recovery but rooted? Or the fact that it's rooted risk messing up stuff? Oh and i dont mind loosing root.
Thanks ~
Click to expand...
Click to collapse
Your fine...you will lose root tho...

[Q] Bricked. Boot Loop. No Data in SD Card.

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

Data recovery on stock brick htc one

Hi,
I've just gotten a friend's HTC one that is soft bricked. Bootloader, Recovery and RUU are accessible, but normal boot hangs. hboot is 1.55
There's some important data on the phone he asked me to recover, pics, contacts etc. However, I can't think of a way to access the data. ADB is unauthorized ofcourse.
Can anyone think of a way to authorize adb, pull the whole emmc or just make the whole system boot somehow, maybe issuing some command for minimal/safe boot using fastboot -c?
Thanks,
Nemesis_00 said:
Hi,
I've just gotten a friend's HTC one that is soft bricked. Bootloader, Recovery and RUU are accessible, but normal boot hangs. hboot is 1.55
There's some important data on the phone he asked me to recover, pics, contacts etc. However, I can't think of a way to access the data. ADB is unauthorized ofcourse.
Can anyone think of a way to authorize adb, pull the whole emmc or just make the whole system boot somehow, maybe issuing some command for minimal/safe boot using fastboot -c?
Thanks,
Click to expand...
Click to collapse
is the bootloader locked?
alray said:
is the bootloader locked?
Click to expand...
Click to collapse
Yes, it's fully stock. Otherwise I would have flashed a different recovery and pulled everything off it.
Unlocking the bootloader will wipe the phone.
Nemesis_00 said:
Yes, it's fully stock. Otherwise I would have flashed a different recovery and pulled everything off it.
Unlocking the bootloader will wipe the phone.
Click to expand...
Click to collapse
yeah I know.
You probably already tried every basic thing to make the reboot to the OS? Like erasing cache, re-flashing the kernel or even the entire firmware?
alray said:
yeah I know.
You probably already tried every basic thing to make the reboot to the OS? Like erasing cache, re-flashing the kernel or even the entire firmware?
Click to expand...
Click to collapse
I had erased the cache, it didnt help.
How can I re-flash only the kernel or the system partition with a locked bootloader and S-ON?
I can flash the whole RUU, but it will wipe the device.
Any other ideas?
Thanks

Categories

Resources