Database Develop

[Q] Bricked Phone - Save Photos/Videos? (Stock Everything, No Root)

Hey,
I have a AT&T HTC-One, all stock with locked bootloader.
Currently, stuck in boot loop where if you turn on the phone - it will just keep rebooting itself over and over until the battery drains. Only way to shut off would be to boot into bootloader and power down.
I could care less about fixing the phone at this point. But I have lots of pictures that I would rather not lose.
I searched around and tried to flash TWRP recovery in order to mount the sd card to my PC. However TWRP failed to flash since my boot loader is locked. I can unlock the bootloader but I will lose all my data.
Is there any way I can salvage data off my phone? Any help will be appreciated.

ashens said:
Hey,
I have a AT&T HTC-One, all stock with locked bootloader.
Currently, stuck in boot loop where if you turn on the phone - it will just keep rebooting itself over and over until the battery drains. Only way to shut off would be to boot into bootloader and power down.
I could care less about fixing the phone at this point. But I have lots of pictures that I would rather not lose.
I searched around and tried to flash TWRP recovery in order to mount the sd card to my PC. However TWRP failed to flash since my boot loader is locked. I can unlock the bootloader but I will lose all my data.
Is there any way I can salvage data off my phone? Any help will be appreciated.
Click to expand...
Click to collapse
did you try fastboot erase cache
Extract the zip below to c:\
then from c:\fastboot - right click - command prompt here
in the command windowtype
fastboot devices
your device serial no will be here
then
fastboot erase cache
fastboot reboot
hopefully your phone will reboot on it's own
Your case reminds me why I unlock and flash custom recovery the first day I get a new phone. Backups !!

clsA said:
did you try fastboot erase cache
Extract the zip below to c:\
then from c:\fastboot - right click - command prompt here
in the command windowtype
fastboot devices
your device serial no will be here
then
fastboot erase cache
fastboot reboot
hopefully your phone will reboot on it's own
Your case reminds me why I unlock and flash custom recovery the first day I get a new phone. Backups !!
Click to expand...
Click to collapse
Thank you for the quick reply.
Yes, just tried it and still no dice. Reboot still puts it back into the bootloop.
...definitely lesson learned.

ashens said:
Thank you for the quick reply.
Yes, just tried it and still no dice. Reboot still puts it back into the bootloop.
...definitely lesson learned.
Click to expand...
Click to collapse
sorry to here that ... unfortunately everything else will be destructive... but your phone may be savable
If you want to proceed post your fastboot getvar all results minus your serial no and IMEI and I'll help you get the phone going again

[Q] Nexus 6 stuck in bootloop

Ok so, this is my first post on xda, and because my (sprint) Nexus 6 is stuck on a boot loop. When powered on, goes to googles boot animation, then says "Android is starting... optimizing apps # of 127, and then once it reaches the end, it just goes into the animation again. I somehow have usb debugging disabled, and oem locked. I have no idea what i did to cause this, but esentially I unlocked the phone, and rooted it, and then i tried to disable encryption, and thats where things went south. clearing chache does not help, niether does factory reset. Attempts at flashing factory images are fails. even the guy at sprint cant do it. Besides fixing it, my only other option is to send it in to google and get a reaplacement...for $200. PLease help me solve this issue and i will be eternally grateful :3

SorryLols said:
Ok so, this is my first post on xda, and because my (sprint) Nexus 6 is stuck on a boot loop. When powered on, goes to googles boot animation, then says "Android is starting... optimizing apps # of 127, and then once it reaches the end, it just goes into the animation again. I somehow have usb debugging disabled, and oem locked. I have no idea what i did to cause this, but esentially I unlocked the phone, and rooted it, and then i tried to disable encryption, and thats where things went south. clearing chache does not help, niether does factory reset. Attempts at flashing factory images are fails. even the guy at sprint cant do it. Besides fixing it, my only other option is to send it in to google and get a reaplacement...for $200. PLease help me solve this issue and i will be eternally grateful :3
Click to expand...
Click to collapse
OK. So...do u know how to use fastboot? If yes...do a fastboot format data and fastboot format cache..also...do u have stock recovery or twrp?

I got that bootloop when I flashed a bad boot image. Easily fixed by flashing a good one...
But, let's clarify a couple of things:
Did you relock your bootloader while flashing?
Do you have a custom recovery (TWRP)?
If the answer to both of those are "yes", you might get out of this by using these commands:
fastboot format userdata
fastboot format cache
This will allow you to enter TWRP and restore a backup or flash a ROM.
If you didn't relock your bootloader you shouldn't have any problems flashing. Clarify what your trying to do, please (are you using a toolkit, etc).
If the answers are 1-yes and 2-no, then your probably SOL.

Didgeridoohan said:
I got that bootloop when I flashed a bad boot image. Easily fixed by flashing a good one...
But, let's clarify a couple of things:
Did you relock your bootloader while flashing?
Do you have a custom recovery (TWRP)?
If the answer to both of those are "yes", you might get out of this by using these commands:
fastboot format userdata
fastboot format cache
This will allow you to enter TWRP and restore a backup or flash a ROM.
If you didn't relock your bootloader you shouldn't have any problems flashing. Clarify what your trying to do, please (are you using a toolkit, etc).
If the answers are 1-yes and 2-no, then your probably SOL.
Click to expand...
Click to collapse
The answers are indeed 1-yes and 2-no. What is SOL an is there any way of fixing it?

SorryLols said:
The answers are indeed 1-yes and 2-no. What is SOL an is there any way of fixing it?
Click to expand...
Click to collapse
SOL = "S**t Out of Luck".
There is currently no know way of fixing it.
Your only avenue is to RMA it.

[Q] Stuck in endless bootloop and recovery is not working either.

Hi everyone
Since I restarted my phone last night, my phone has been in a endless bootloop and I can't even enter recovery, without it rebooting again and going into the same endless bootloop again, around 2 seconds after showing the "Teamwin" logo.
I'm using ARHD, and if I remember correctly it's version 71.1. TWRP is "openrecovery-twrp-2.6.3.3-m7" and running ElementalX kernel.
I expect my partition is somehow corrupted, but I'm at a loss of ideas as to how I can recover my phone again. I would apreciate if I could somehow manage to make a backup of my data, but it that's totaly hopeless, I'm thinking of going for the ArtMOD ROM instead and starting fresh.
Is there a helpfull soul out there, that could maybe give me some insights as to what I can do from here? Thanks in advance!

I was hoping I could install a stock ROM and start from scratch again, but I somehow suspect having used a modified ROM has gotten me in trouble now and the ROM Upgrade utility sees this as a downgrade. I've not been able to find a newer ROM for the .401. series than "RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe". Although the updater believes I'm updating from 4.19.401.11 (the ARHD ROM).
I can get into FASTBOOT USB and the phone goes to the black HTC logo screen when trying to update, but quickly fails on the PC during the process at "Updating 1/5". When unplugging the USB cable the phone shows:"
RUU
Security fail!
Update Fail!
I've attached two screenshots, to better explain
Can some kind soul out there please help me getting a working phone again? What ROM I'll end up with doesn't really matter

Since you're using unlocked bootloader, why don't you try RUU to get back on Stock ROM.
Here is the collection of ROMS
Download your ROM.
from Windows Command prompt
adb reboot bootloader #
If it didn't work, Press and Hold Power button along with Volume down of your phone,
When you reach to bootloader, get into fastboot mode.
Now follow the following commands to restore the STOCK Rom. (make sure your downloaded ROM are in the same directory where you have fastboot.exe, abd, and abdwin.api etc)
1) fastboot erase cache
2) fastboot oem rebootRUU
3) fastboot flash zip RUU.zip (RUU.zip is of course your downloaded Stock ROM). If it says Failed, try again.
4) fastboot erase cache
5) fastboot reboot-bootloader
6) fastboot reboot
Good Luck
Hope that helps.

Thank you so much for helping out!
After several tries, tries and retries, I finally managed to get the phone back up and running with the stock ROM. I believe what finaly did the trick, was to use "fastboot oem lock" to get the stock ROM installed. From here, I'm now able to unlock it again and install a custom recovery (TWRP) and ROM (I went for ARTMOD). Thanks again!!!

Think I broke my bootloader flashing TWRP, stuck with no phone, need help!

I've on an older version of Android. I've never had a problem using TWRP on other phones but due to the lack of having it on my Pixel 4XL, I've just never had it.
I haven't upgraded in ages, I see we have a working TWRP now. I tried to flash it via Magik and I think I flashed the wrong one.
My phones stuck in a boot loop mode and IF I can get to the screen that says "fastboot mode", I cant do anything with it.
"adb devices" returns nothing so I cant even attempt to flash the correct recovery.
Help!

kdoggy said:
I've on an older version of Android. I've never had a problem using TWRP on other phones but due to the lack of having it on my Pixel 4XL, I've just never had it.
I haven't upgraded in ages, I see we have a working TWRP now. I tried to flash it via Magik and I think I flashed the wrong one.
My phones stuck in a boot loop mode and IF I can get to the screen that says "fastboot mode", I cant do anything with it.
"adb devices" returns nothing so I cant even attempt to flash the correct recovery.
Help!
Click to expand...
Click to collapse
When you get to the screen that says "fastboot mode", do "fastboot devices", not "adb devices". If that works, flash the boot image with "fastboot flash boot boot.img". Make sure the boot.img matches what you had on the phone before breaking it. Either the stock boot.img or magisk patched boot image should work, but you'll loose root with the stock boot.img.
It is best to boot TWRP without installing it. "fastboot boot twrp.img".

Hey.
Yeah check "fastboot devices". If you get something on terminal, use Google flash tool to reflash the original firmware, this will repair any damaged/corrupted file.
If you don't get anything your phone is very likely bricked. You can still try the emergency mode but I believe it won't work. In this case there is still a way to recover your phone, and it's using the EDL mode(which is contain in every phone that has a Qualcomm Chipset). From there you can force flash firmware and boot image.
Tell me how it goes

OK I got TWRP working.
Phones updated to September 2021, turned out I was still on March 2021! Anyway, all updated, rooted etc!
Thanks very much folks!

Nice

dcarvil said:
When you get to the screen that says "fastboot mode", do "fastboot devices", not "adb devices". If that works, flash the boot image with "fastboot flash boot boot.img". Make sure the boot.img matches what you had on the phone before breaking it. Either the stock boot.img or magisk patched boot image should work, but you'll loose root with the stock boot.img.
It is best to boot TWRP without installing it. "fastboot boot twrp.img".
Click to expand...
Click to collapse
Glad to know that my habit of fastboot booting twrp images on 2XL will keep me safe here on 4XL too

Bricked after attempting to unlock bootloader. What now?

I was attempting to unlock the bootloader on my V40 at&t(405ua) using the guide by Xsavi. I booted into EDL mode and used Qfil to flash the V35 bootloader to abl_a and it was successful but when i tried to enter fastboot mode it would just restart to the normal boot. I read in one of the comments that this could be fixed by flashing the V35 file to abl_b also, so i tried that. I flashed the file to both abl's but when i tried to boot i got a screen saying "Your device has failed a security check." and at the bottom says "All slots are unbootable!"
What can i do to fix this?

protatocrisp said:
I was attempting to unlock the bootloader on my V40 at&t(405ua) using the guide by Xsavi. I booted into EDL mode and used Qfil to flash the V35 bootloader to abl_a and it was successful but when i tried to enter fastboot mode it would just restart to the normal boot. I read in one of the comments that this could be fixed by flashing the V35 file to abl_b also, so i tried that. I flashed the file to both abl's but when i tried to boot i got a screen saying "Your device has failed a security check." and at the bottom says "All slots are unbootable!"
What can i do to fix this?
Click to expand...
Click to collapse
Well if it's "bricked", then you can't fix it. Bricked means it's a brick, and doesn't respond.
But since it's actually NOT bricked, then maybe flash the original abl's back? Using qfil. That's the thing about edl mode, you can get to it from any screen, it doesn't have to be booted. The only thing you won't get is a timer count down from 5, so you'll have to kind of time that yourself, to start spamming the vol up key.
One other thing, with the engineering abl, the device isn't intended to be able to boot, it's only suppose to be used to unlock the bootloader, then use fastboot to flash the original ones back. The device (almost always) won't boot with those abl's.

AsItLies said:
Well if it's "bricked", then you can't fix it. Bricked means it's a brick, and doesn't respond.
But since it's actually NOT bricked, then maybe flash the original abl's back? Using qfil. That's the thing about edl mode, you can get to it from any screen, it doesn't have to be booted. The only thing you won't get is a timer count down from 5, so you'll have to kind of time that yourself, to start spamming the vol up key.
One other thing, with the engineering abl, the device isn't intended to be able to boot, it's only suppose to be used to unlock the bootloader, then use fastboot to flash the original ones back. The device (almost always) won't boot with those abl's.
Click to expand...
Click to collapse
Thats the thing. I booted into fastboot mode and unlocked the bootloader but when i tried to flash the original abl's it says it cant flash when the bootloader is unlocked and if i reboot it only boots into fastboot mode and when i flash the abl's in Qfil i get the screen saying that the device has failed a routine check. Thats why im unsure of what to do now.

protatocrisp said:
Thats the thing. I booted into fastboot mode and unlocked the bootloader but when i tried to flash the original abl's it says it cant flash when the bootloader is unlocked and if i reboot it only boots into fastboot mode and when i flash the abl's in Qfil i get the screen saying that the device has failed a routine check. Thats why im unsure of what to do now.
Click to expand...
Click to collapse
sounds like you've got some files mismatched / mislabeled. The engineering abl won't give you the message 'can't flash when the bootloader is unlocked'. But the fastboot you get when deleting the laf partition will give you that message.
and if you're using qfil and flashing the original abl's back, and that's all you've changed, and you get the message 'fail routine...', then you're doing something wrong. Either yer flashing to the wrong partitions, flashing the wrong files, or you've changed something else also.

AsItLies said:
sounds like you've got some files mismatched / mislabeled. The engineering abl won't give you the message 'can't flash when the bootloader is unlocked'. But the fastboot you get when deleting the laf partition will give you that message.
and if you're using qfil and flashing the original abl's back, and that's all you've changed, and you get the message 'fail routine...', then you're doing something wrong. Either yer flashing to the wrong partitions, flashing the wrong files, or you've changed something else also.
Click to expand...
Click to collapse
Well im not exactly sure where i went wrong, but i can still enter download mode so would i be able to flash the stock android 9 rom?
Also if i reflash the v35 file and try the fastboot flash abl_a and abl_b it flashes successfully but when it press the power button on the phone it restarts to fastboot mode.

protatocrisp said:
Well im not exactly sure where i went wrong, but i can still enter download mode so would i be able to flash the stock android 9 rom?
Also if i reflash the v35 file and try the fastboot flash abl_a and abl_b it flashes successfully but when it press the power button on the phone it restarts to fastboot mode.
Click to expand...
Click to collapse
well if there's a lesson here it's that it's exceptionally important to pay attention to exactly what you're doing. Double check everything; that you're flashing the correct files, that you back up the correct files and name them appropriately, read directions over and over to be sure u understand.
it sounds like if you keep going back to fastboot when trying to start system, then you're probably re-flashing the engineering abl and not the original abl, which yer suppose to save off first.
yeah, maybe start over again by flashing a stock rom.