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 urgent help! Didn't OEM unlock in Dev and now stuck!!

Ok, so got my brand new shiny Oneplus 3T yesterday after waiting aged for it to come in.
Using it for a bit, noticed an OTA update to nougat came out (about 900mb) which downloaded in the background.
Triggered the upgrade, now the phone won't boot. I'm also having trouble installing any recovery roms on to it, because I was never intending to root the phone in the first place, and as a result didn't unlock the bootloader using the phone interface when it was on.
So now, it appears I'm stuck! My phone won't accept any side-load roms, (fails), full roms don't read (cannot open file) and fastboot won't unlock the bootloader (Not allowed)
....um.. not having a clue what I'm doing here....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"
}

try going to stock oxygen recovery. wipe data and cache there. see if it boots.
try the unbricking thread too.
if all else fail, call OP customer service.
let us know what happens.

To fix it - see "[UNBRICK] Unbrick Tutorial For The OnePlus 3T!!!!!!!! by Harris K". You have to download his two files onto a laptop or desktop computer and install a qualcomm driver (one of the files). The qualcomm driver will open a serial port into the phone's chipset. The other file will download a stock system, recovery, and fastboot to your phone through the qualcomm serial port. Harris is a genius, buy him a beer. This will fix the following problems.
1) It sounds like the OTA patch screwed up your /system where it doesn't even try to boot. You can still boot into /recovery and /fastboot but just not into /system. Since the phone is still "locked" (flashing prohibited) you cannot flash anything to fix it.
2) dm-verity does not allow any changes to /system. dm-verity checks a hash of hashes of /system. If the hash check fails when you boot /system, dm-verity will "brick" your phone (by design) leaving you with a black screen.
The OTA updates the system and downloads a hash key corresponding to that version. After the OTA, everyone has to end up with exactly the same system in order to pass the dm-verity check.
When you enable flashing (called "unlocking the bootloader") dm-verity will wipe /data to prevent someone from flashing a non-stock recovery to access your data.

infamousvincci said:
try going to stock oxygen recovery. wipe data and cache there. see if it boots.
try the unbricking thread too.
if all else fail, call OP customer service.
let us know what happens.
Click to expand...
Click to collapse
Ok, so went to the unbricking thread. The tool worked! I'm back up and running

bunburyist said:
Ok, so went to the unbricking thread. The tool worked! I'm back up and running
Click to expand...
Click to collapse
I deserve a thank you button haha

Question I locked the bootloader by misstake

Hello, what I did was the following:
1. signed on a new phone with account A, waited a week and unlocked the bootloader
2. signed on the same phone with account B
3. flashed fastboot rom on the device with mi flash tool, but forgot to uncheck the " lock the bootloader"
4. the phone is not starting - i can only get the recovery and the fastboot mode.
5. mi flash tool wont let me flash to locked device . Mi flash tool2 makes me go into Mi assistant mode, starts the instalation process but failes after a few mins ( on the pc i reach ~ 700% but on the phone the bar is on 4.99 or 52.78 % )
6. Xiaomi ADB/Fastboot Tools doesnt want to flash as the device is locked and if i try the OEM UNLOCK button i get "FAILED (status read failed (Too many links))"
7. If I try to unlock the bootloader again and I log account B i get message that i need to log on the phone and wait for a week
If i log accont A i get 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"
}
Any Idea how to fix it
Thanks in advance, and sorry if this is the wrong place for this question

As far as I know, the only way is to ask after-sale for help.

ddspj said:
As far as I know, the only way is to ask after-sale for help.
Click to expand...
Click to collapse
They might have more underlying tools to unlock and flash your phone.

fastboot flashing unlock
for most of aosp rom this is the command. but i'm not sure that works on miui. i found a java tool that maybe can help you. https://miui.blog/any-devices/xiaomi-adb-fastboot-tools-one-utility/ i have used to debrand my phone without unlock it

I had to send it to a friend of mine who was able to install chaina rom, using EDL mode, but now, for some reason the IMEI's are gone. I can not add mi account, and for that reason I can't unlock the bootloader, right now I am battaling with the IMEI restoration ( i have the original imei's on the phone case) I am trying to use modem_meta_tool, but with no suxcess . I can't get my phone connected
Long story short, EDL mode was needed to get out of my original situation

seem you have lost imei cause you have installed china rom. or a rom incompatible with your region. try install global rom via edl. but if you lost imei, restore it is not simply... you can try to enter into engineering mode. i'm not sure but there's a function to change imei. but not working for all mtk processors

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.

S10 stuck on boot after custom ROM flash

Hi good evening, this is my first post in xda, I've used the forum since my first android back in the htc era, since 7 years I used my s8 with the hadesRom and everything was amazing, then I've broken my beloved s8, really the best smartphone ever, and I've bought an s10 a couple of month ago
Then, yesterday I start to follow the Magisk guide for unlock the bootloader and root my S10 G973F-DS and after it the the one for install the TWRP with the PlayStore method.
Unlocked the bootloader, rooted it, Magisk was installed, then I had the first problem: the internal storage was down to 25gb, I've wiped from recovery data and cache and the storage came back to normal, I've installed the twrp with the appstore method, rebooted to twrp, and wiped again data and cache as said in the hadesRom install guide and then all the system was gone, the twrp refuse to reboot to the stock one so I've tried to flash the HadesRom and now it's stuck in the Samsung GalazyS10 bootup splash screen, it just reboot with Bixby+volumeDown+Power but it always just go back to the splash screen, it doesn't recognize any other button sequence neithe the adb devices recognize it...
can I save it?
Thanks in advance..

Use ODIN to flash latest firmware again. Then use ODIN to flash LineageOS, then install lastest PixelExperience and boot on it. After boot PE, use ODIN again to flash TWRP and flash any rom u like.

Thanks for the answer, but I can't flash anything, it's stuck in this splashscreen, It only reboot with volume- bixby and power, but it just goes back to this one again.
I've tried flashing the orIginal fw, but it's not recognized by Odin so if I start Odin nothing appens actually.
{
"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"
}

Samsung Galaxy S10 G973F Test Point – EDL 9008 Mode
By using the Samsung Galaxy S10 G973F Test Point, you can easily restore the stock ROM, bypass FRP lock, or reset user data on your device via UFi Box. In
www.mobilerdx.com
This link may help u