Database Develop

Device Bricked?

Here is my story. I've been at this for three hours including searching XDA and other sites. Can't get any options to work.
I was trying to gain S-OFF. I installed a custom recovery (TWRP) and in doing so I could not see any files to flash the new rom... I tried flash CWM, it ended up booting to the CWM text at the bottom left with the version number, and then booting to the plain white (with htc one logo) screen and sitting there and not booting into anything else. Just sits there. Every recovery I flash through fastboot (which is my ONLY option into the phone it seems) does not boot up, the device just restarts to that annoying HTC logo screen.
I was able to get ONE recovery of twrp working and it boots up into it and displays all the options, HOWEVER, it cannot mount... Nothing will mount via twrp.
What can I do?
Screenshot of twrp attached
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Flash twrp 2.6.3.3. Then run the fastboot erase cache. You should be able to get into recovery then. Any partitions that won't mount you will have to wipe in recovery. Then you can either adb sideload or adb push a Rom to your phone in recovery

nateboi81 said:
Flash twrp 2.6.3.3. Then run the fastboot erase cache. You should be able to get into recovery then. Any partitions that won't mount you will have to wipe in recovery. Then you can either adb sideload or adb push a Rom to your phone in recovery
Click to expand...
Click to collapse
That worked! You just fixed my phone! :laugh:
You sir are an :angel:
I had just about given up hope Awesome, learned something, too!
Looks like all TWRP features seem to work even install zip or flash rom.
Any ideas on the S-OFF? I can't seem to get it I tried Revone and Firewater. I have 1.56 HBOOT none of the options I''ve looked have worked.

Good to hear. What message do you get with firewater? If you get the whelp this sucks message only sunshine will work. Which will cost you $25

Need Help Fast! - HTC One m7 problems, can't fix. Help!

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Okay, firstly, this all started when I flashed the new Sense 7 Insert Coin Rom. My phone would not boot up after having turned off/lost battery.
Here is a list of the problems:
1. Cannot boot into recovery, gives purple loading text and then bootloops again
2. When charging it charges for 5-10 seconds minimum and then bootloops
3. The device has turned on before during these bootloops once before
4. The device could be left charging all night and bootloops all night, no way to power down
5. Upon attempting to power the device on after 12 hours of charging it has no battery charge left
6. Cannot flash a new recovery for some reason (via cmd)
7. Tried flashing TWRP, CWM and PhilZ again, none worked all resulting with the error code 'error: cannot load recovery.img' having put the code 'fastboot flash recovery recovery.img' with no results
8. Device can only boot into bootloader, nothing else.
9. And also, the above CMD error too..
I have been without my phone for 3 days now and having tried all the possible options I knew of this was my last resort.
Hope someone has a solution, thanks

I had a similar issue with my device. Turned out that the flash storage had died.
Took it in to my operator and they replaced it with a refurbished HTC One
Had to pay because the phone had some nicks and scratches.

Mat214 said:
I had a similar issue with my device. Turned out that the flash storage had died.
Took it in to my operator and they replaced it with a refurbished HTC One
Had to pay because the phone had some nicks and scratches.
Click to expand...
Click to collapse
Oh dear... was hoping this wasn't serious. Thanks.

Matthew.One said:
Oh dear... was hoping this wasn't serious. Thanks.
Click to expand...
Click to collapse
not so much a solution, but it sounds to me like your battery is dead dead, as in you need a new battery, if the phone is dyiong pretty much as soon as you unplug it from the charger then it has to be the battery, and as a safety feature, you cant flash anything with a battery that low, which would also explain the flashing error your getting.

Unfortunatelu, the process com.android.settings has stopped

Here is the situation I have an HTC ONE (M7) Here which does absolutely nothing but show this message...
It does not have usb debugging enabled and adb will not register it. I can however connect to it via fastboot....
Ive gotten as far as unlocking the bootloader... But now cannot seem to get any further as everything I have read uses ADB and i cannot get it to recognize ADB Device.
Basically from what i am reading.... Is flash custom recovery such as TWRP (Which i have downloaded) and i want to just reinstall stock rom etc. Not trying to root or anything here, just simply trying to reinstall factory software for HTC One (M7) - Telus Canada to hopefully resolve the issue.
Please any help is greatly appreciated I have been up now for nearly 20 Hours trying to get this done.
Exactly like this

dugie33 said:
Here is the situation I have an HTC ONE (M7) Here which does absolutely nothing but show this message...
It does not have usb debugging enabled and adb will not register it. I can however connect to it via fastboot....
Ive gotten as far as unlocking the bootloader... But now cannot seem to get any further as everything I have read uses ADB and i cannot get it to recognize ADB Device.
Click to expand...
Click to collapse
Because you are boote din bootloader mode. ADB can't work when in bootloader mode, only from custom recovery or from a booted rom + usb debug on. Here a nice table I made last week to explain the same thing to another guy:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Basically from what i am reading.... Is flash custom recovery such as TWRP (Which i have downloaded) and i want to just reinstall stock rom etc. Not trying to root or anything here, just simply trying to reinstall factory software for HTC One (M7) - Telus Canada to hopefully resolve the issue.
Click to expand...
Click to collapse
Post the output of "fastboot getvar all" (remove your imei and sn before posting)

[Q] How can i fix this fastboot issue? (xiaomi redmi 9c)

Basically i have been trying to root my phone (Redmi 9c) everything was going well until i got to the pathching the boot.img with magisk and got the error
'booting...
FAILED (status read failed (Too many links))'
and after that i was stuck on a boot loop i looked for a guide and i re-flashed (not sure if i'm using the correct terminology. sorry im a noob) the original xiaomi angelica boot.img it fixed the issue but i was still not rooted i went to another guide everything went smoothly until i got to the booting part and...... got the same error i have tried everything, (changing charger, usb port, using windows power shell and normal CMD) and nothing all i get is this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and once again to a boot loop. i have tried re-flashing the factory boot.img and nothing. Im seriously starting to go insane because i cant fix this problem and can't get the phone to boot again or even find something to help me.
thanks to anyone who might help me in advance

Elizabeth_304 said:
Basically i have been trying to root my phone (Redmi 9c) everything was going well until i got to the pathching the boot.img with magisk and got the error
'booting...
FAILED (status read failed (Too many links))'
and after that i was stuck on a boot loop i looked for a guide and i re-flashed (not sure if i'm using the correct terminology. sorry im a noob) the original xiaomi angelica boot.img it fixed the issue but i was still not rooted i went to another guide everything went smoothly until i got to the booting part and...... got the same error i have tried everything, (changing charger, usb port, using windows power shell and normal CMD) and nothing all i get is this:
View attachment 5373903
and once again to a boot loop. i have tried re-flashing the factory boot.img and nothing. Im seriously starting to go insane because i cant fix this problem and can't get the phone to boot again or even find something to help me.
thanks to anyone who might help me in advance
Click to expand...
Click to collapse
Hey has it been sorted out already? Try flashing with fastboot ROM. Also see thread about rooting redmi 9c under guides

You cant boot into recovery from fastboot command, just enter recovery manually by pressing vol+ and power button.

AOSP 11 fastboot flashing lock unknown command

Hi all,
By follow the sony open device aosp build instruction with all the steps successfully.
https://developer.sony.com/develop/...structions/build-aosp-android-android-11-0-0/
But when starting the phone, it shows an error message and nothing more
`Your device software can't be checked for corruption. Please lock the bootloader.`
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I try to relock the bootloader, it did shows that the device already unlocked
but when I try to lock, it shows 'unknown command'
Any ideas? thanks

Hey. Just a heads up--the screen notifying about unlocked bootloader is normal. Since unlocking the bootloader I get the same notification during startup and then it boots normally into the ROM. Whatever the startup issue is, I wouldn't conclude it's caused by unlocked bootloader based off that screen.
In regards to the issue with relocking the bootloader, I had ran into a similar nondescript error with adb while trying to flash TWRP, it read 'FAILED (Status read failed (No such device))' and after a lot of googling I found that the solution is to try different computers/USB ports. In my case I had to use another laptop's USB port while running Linux/EndeavourOS from thumb drive (fastboot was/is unreachable under Windows for my XZ1c).
upd. Oh, it seems relocking the bootloader is not as easy as fastboot oem lock. Nevermind.

I'm not sure which question you're asking.
If it's that you see the message, it's normal, because you (or someone else) unlocked your bootloader. It's normal, and a warning (not an error), not a sign that anything's broken. But you maybe want to check your ROM or recovery, if you weren't the one who installed them, or you don't trust the person that did.
If it's that you can't re-lock the bootloader, that's ... also expected. You can't. No one has found a way to re-lock the bootloader on the XZ1 compact. So that command will always fail. It's not supported on your phone.
If the phone won't boot or is broken, it's likely for some other reason.