Database Develop

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] Stuck on boot after KK update

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

[CLOSED]HTC One not entering recovery

Recently I tried to root my One. I unlocked bootloader using HTCDev.com and flashed TWRP using my PC. When I try to enter recovery from fastboot it just enters a bootloop and doesn't enter recovery. I tried flashing CWM and tried all versions from 2.5.0.0 to 2.8.0.2 of TWRP. Also I cannot root due to no recovery. Pls help. Any help will be appreciated.

*bump*

Did u use fastboot to clear cache? Might Google a bit on the command I forget, fastboot erase cache.. maybe format cache. If you did not clear cache you can get a boot loop for sure.

Still not able to enter recovery.

I am assuming when you flash recovery your getting a confirmation that it goes smoothly? Also, just a thought, hboot 2.49.0000 is Sprint HTC one max.? Did u get the recovery from that thread?

MrLizm said:
I am assuming when you flash recovery your getting a confirmation that it goes smoothly? Also, just a thought, hboot 2.49.0000 is Sprint HTC one max.? Did u get the recovery from that thread?
Click to expand...
Click to collapse
Yeah, it confirms that it goes smoothly and mine is hoot 2.49.0000 HTC One dual sim.

http://forum.xda-developers.com/showthread.php?t=2559891 says for that device you need s-off and its flashed in hboot.. which opens a while other can of worms. Not sure of a work around at this point....

MrLizm said:
http://forum.xda-developers.com/showthread.php?t=2559891 says for that device you need s-off and its flashed in hboot.. which opens a while other can of worms. Not sure of a work around at this point....
Click to expand...
Click to collapse
Thank you very much. Didn't find that anywhere.

Can you still boot regularly? If so follow the steps there to achieve s-off and you'll be golden. Also mentioned its compatibility with other roms. Unless your just going for stock root. Good luck!

Yes, I can boot normally. And thanx once again.

Help getting back to 100% stock with encryption

I flashed the decryption img file and then did ADB back to stock including system, cache, etc, and now my phone is bricked and won't let me in it or the bootloader because its not encrypted. I want my phone back 100% stock now with encryption please anyone let me know how. I know how to ADB back to stock just not back to stock with encrypted. I was using my phone fine after ADB to stock until I rebooted and tried flashing TWRP+Root, then it messed up and I can't get in it.

imablackhat said:
I flashed the decryption img file and then did ADB back to stock including system, cache, etc, and now my phone is bricked and won't let me in it or the bootloader because its not encrypted. I want my phone back 100% stock now with encryption please anyone let me know how. I know how to ADB back to stock just not back to stock with encrypted. I was using my phone fine after ADB to stock until I rebooted and tried flashing TWRP+Root, then it messed up and I can't get in it.
Click to expand...
Click to collapse
ADB won't help you in this situation. You need to use fastboot and flash the factory image. Power off your device and boot directly into bootloader holding power and volume down simultaneously. Once in bootloader, connect to PC, navigate to your platform tools folder, (or if you have ADB/fastboot set as a path environment) open a command window and type:
fastboot devices
If your serial number comes up, you may proceed to flashing the factory image. Those instructions are here:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

I did this fastboot adb back to stock with all the proper images, and then I went to install custom recovery and root after the restore and now I'm locked out of my device because of the no encryption??? what am I missing

imablackhat said:
I did this fastboot adb back to stock with all the proper images, and then I went to install custom recovery and root after the restore and now I'm locked out of my device because of the no encryption??? what am I missing
Click to expand...
Click to collapse
What do you mean locked out? Is TWRP asking for a password? Or is your bootloader locked?

twrp is asking for a password an when I try and boot into system it says unencrypted and only shows the power off button from there, it knows its still unencrypted.

imablackhat said:
twrp is asking for a password an when I try and boot into system it says unencrypted and only shows the power off button from there, it knows its still unencrypted.
Click to expand...
Click to collapse
Post #2 in the TWRP thread.
http://forum.xda-developers.com/showthread.php?p=56891965

so if I enter the default password in TWRP it will unlock my Recovery and I'll be able to reboot system and my phone will be normal again?? and encrypted?, I don't want a password on TWRP or on my phone.

entering the password works for TWRP and thats fine but I still cannot access my phones system when restarting, it comes up and says encryption unsuccessful, and i can only restart.

imablackhat said:
entering the password works for TWRP and thats fine but I still cannot access my phones system when restarting, it comes up and says encryption unsuccessful, and i can only restart.
Click to expand...
Click to collapse
Flash a ROM in TWRP.

Just flash the stock factory image and be done with it.. Do NOT relock the bootloader yet.

rootSU said:
Just flash the stock factory image and be done with it.. Do NOT relock the bootloader yet.
Click to expand...
Click to collapse
You have set a standard that we all need to follow. i.e. always including that last sentence.

Nexus 6 Bootloop after updating to Nougat

Hey guys, I updated my mom's Nexus 6 OTA to 7 point something and it was working at first but after a month, idk what happened but the phone is in a bootloop now. The Nexus Root Toolkit doesn't work as it requires the bootloader to be unlocked and this was a completely stock phone. HALP

xida1125 said:
Hey guys, I updated my mom's Nexus 6 OTA to 7 point something and it was working at first but after a month, idk what happened but the phone is in a bootloop now. The Nexus Root Toolkit doesn't work as it requires the bootloader to be unlocked and this was a completely stock phone. HALP
Click to expand...
Click to collapse
Wipe cashes in the recovery, if it doesn't help flash latest factory image without userdata
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

xida1125 said:
Hey guys, I updated my mom's Nexus 6 OTA to 7 point something and it was working at first but after a month, idk what happened but the phone is in a bootloop now. The Nexus Root Toolkit doesn't work as it requires the bootloader to be unlocked and this was a completely stock phone. HALP
Click to expand...
Click to collapse
In my experience with bootloops is that when you you update to an new ROM sometimes the kernel gets affected in the process. It's happened to me a few times but my phone is rooted so I do a lot more flashing and updating.
It's an easy fix tho, use the Toolkit and open the Launch screen look at the top middle and there should be a tab for flashing the boot.img, in your case since your on stock ROM just restore the image file for the build number that is currently running. So if you just updated to Android N, the build number will start with an N. The toolkit will install the correct file to restore the phone back to normal working order.

His bootloader is locked, thus he can't use the toolkit or fastboot.
@xida1125: Enter into the recovery and wipe the cache. That may fix the bootloop. If it doesn't, download the latest OTA and sideload it. Be prepared for the possibility of having to factory reset the device if nothing else works.

Strephon Alkhalikoi said:
His bootloader is locked, thus he can't use the toolkit or fastboot.
@xida1125: Enter into the recovery and wipe the cache. That may fix the bootloop. If it doesn't, download the latest OTA and sideload it. Be prepared for the possibility of having to factory reset the device if nothing else works.
Click to expand...
Click to collapse
I'm gonna try that tonight, not sure how to sideload it but I'm sure I'll figure it out. I already gave my mom my Nexus 6P to use and she likes it because it has a better camera. I tried factory reset in bootloader but it didn't do anything. Forgot to try and go into recovery menu.

If you've switched devices with your Mom, you can probably factory reset in recovery without issue. Sideloading an OTA is reasonably easy. Download the OTA, move it to internal storage, and from recovery there should be a menu option to sideload the OTA.
Once you've gotten everything fixed, dig into the developer options and enable oem unlocking in both the N6 and the N6P. Doing so will not unlock the bootloader, but will give you the opportunity to unlock the bootloader if the need or want arises in the future.

Strephon Alkhalikoi said:
If you've switched devices with your Mom, you can probably factory reset in recovery without issue. Sideloading an OTA is reasonably easy. Download the OTA, move it to internal storage, and from recovery there should be a menu option to sideload the OTA.
Once you've gotten everything fixed, dig into the developer options and enable oem unlocking in both the N6 and the N6P. Doing so will not unlock the bootloader, but will give you the opportunity to unlock the bootloader if the need or want arises in the future.
Click to expand...
Click to collapse
-Tried going into recovery via bootloader, just bootlooped
-Tried factory reset in boatloader, doesn't do anything
I don't think I can sideload can I? I can't even get to recovery menu...

Based upon your descriptions, it's sounding more and more likely that you have a dead emmc chip. In other words, hardware failure.

xida1125 said:
-Tried going into recovery via bootloader, just bootlooped
-Tried factory reset in boatloader, doesn't do anything
I don't think I can sideload can I? I can't even get to recovery menu...
Click to expand...
Click to collapse
May you try the steps without a inserted simcard, otherwise I hope for you it's not the hardware

xida1125 said:
-Tried going into recovery via bootloader, just bootlooped
-Tried factory reset in boatloader, doesn't do anything
I don't think I can sideload can I? I can't even get to recovery menu...
Click to expand...
Click to collapse
OK... Here we go...
You have fastboot and adb on your computer?
Boot to fastboot... On your phone
Use fastboot to wipe userdata and cache... (I forget the commands... Google is your friend)
Try and boot... Be patient... It's gotta rebuild ART... Will take some time
If no boot...
I THINK... THINK (repeated because I don't know for sure) you can flash the factory images without unlocking the bootloader... Because they are signed by Google...
FWIW... It's something on your data partition... Or in cache...
It sounds like the phone shutdown while writing to disk...
As long as you haven't done something really dumb... Like wiping boot, aboot, system, etc... You should be able to bring it back...
Also... There is a fastboot command that will tell you partitions on the device... Not sure if the N6 has the command... That would give you more information...
This... Is a textbook example of why you shouldn't use toolkits... You're stuck... And haven't read enough or experimented enough to know how to fix your device...