[SOLVED] - Phone severely bricked - Samsung Galaxy S10 Questions & Answers

Hello,
I was on CrDoid 7.2. (Android 11) It was working normally.
I rebooted to recovery (TWRP 3.5), and flashed CrDroid 6.2 (Android 10).
And it bricked severely the phone. At startup, i get a message
"REV CHECK FAIL, DEVICE:9, BINARY:8 (DTB)"
I really think the situation is hopeless :
- impossible to reach download mode
- impossible reach recovery mode
- BixBy + Volume down + Power + plugging the cable doesn't work
- if the telephone stays plugged, i get a boot-loop (before the message "your bootloader is unlocked, please press power button to continue")
Any help is welcome but i really think i lost my phone. Quite painful. I'm not so rich.
I think the device tree of the ROM i flashed is mistaken.
I played i lost.
Jean

jean_michmich said:
Hello,
I was on CrDoid 7.2. (Android 11) It was working normally.
I rebooted to recovery (TWRP 3.5), and flashed CrDroid 6.2 (Android 10).
And it bricked severely the phone. At startup, i get a message
"REV CHECK FAIL, DEVICE:9, BINARY:8 (DTB)"
I really think the situation is hopeless :
- impossible to reach download mode
- impossible reach recovery mode
- BixBy + Volume down + Power + plugging the cable doesn't work
- if the telephone stays plugged, i get a boot-loop (before the message "your bootloader is unlocked, please press power button to continue")
Any help is welcome but i really think i lost my phone. Quite painful. I'm not so rich.
I think the device tree of the ROM i flashed is mistaken.
I played i lost.
Jean
Click to expand...
Click to collapse
Try the FRP Hijacker Tool. It has also happened to me that nothing worked anymore. The cell phone does not appear in the list, but still worked with the SC-01C and SoftBrick Fixer.

This also happened to me before, and I also couldn't get back to TWRP.
The error "REV CHECK FAIL, DEVICE:9, BINARY:8 (DTB)" means that the version of your device is at 9 and the binary you flashed is at 8. You can't simply downgrade Android versions on Samsung devices.
Are you sure you can't enter download mode? The key combination to enter download mode isn't what you said (" BixBy + Volume down + Power + plugging the cable doesn't work "). Try PLUGGING YOUR PHONE IN YOUR PC + VOLUME DOWN + BIXBY.
If you can access download mode, let me know so I can help you get your device unbricked.

Hello,
My mistake is that I downgraded from 11 to 10. You are probably right.
I think (but i'm not sure) that during downgrading, the sboot.bin is not anymore matching with the Device Tree and it generates a crash during flashing.
@WSC Productions : Huge thanks for the advice about the combo buttons.
@bininga59 : I'll give a try to your solution with the software FRP Hijacker Tool. But the phone is restarting itslef every 5 seconds..I wonder how a connection can be established.
Tonight will be a long night again

jean_michmich said:
Hello,
My mistake is that I downgraded from 11 to 10. You are probably right.
I think (but i'm not sure) that during downgrading, the sboot.bin is not anymore matching with the Device Tree and it generates a crash during flashing.
@WSC Productions : Huge thanks for the advice about the combo buttons.
@bininga59 : I'll give a try to your solution with the software FRP Hijacker Tool. But the phone is restarting itslef every 5 seconds..I wonder how a connection can be established.
Tonight will be a long night again
Click to expand...
Click to collapse
You can definitely go back from A11 to A10. It's the same bootloader (9). If it keeps restarting, then you should get into download mode too. Emergency off and then immediately quieter + Bixby immediately push the USB plug in.

jean_michmich said:
Hello,
My mistake is that I downgraded from 11 to 10. You are probably right.
I think (but i'm not sure) that during downgrading, the sboot.bin is not anymore matching with the Device Tree and it generates a crash during flashing.
@WSC Productions : Huge thanks for the advice about the combo buttons.
@bininga59 : I'll give a try to your solution with the software FRP Hijacker Tool. But the phone is restarting itslef every 5 seconds..I wonder how a connection can be established.
Tonight will be a long night again
Click to expand...
Click to collapse
No problemo. Try @bininga59 's advice, it'll probably work - he probably knows more than I do about Samsung ROMs tbh. If it doesn't though, let me know.

What i didn't know :
Doing Volume down + BixBy Button + plugging cable for simple electric supply
Is not the same as
Doing Volume down + BixBy Button + plugging cable linked to a computer
The cable you plug to the telephone while you are pressing volume down + BixBy must be linked to a computer.
I finally reached the Download Mode
Many thanks again

Related

Brick/Bootloop Huawei P8 Lite 2017

Hello everyone, I saw a few posts on this forum about other bricked phones, but my case is different (if its not then please link me the thread, Thanks).
Story: Today I decided that my unrooted phone wasn't enough for me, so I said: "Why not root?" . I have to add that I owned a LG Magna 3G before this Huawei P8 LIte 2017 and oh boi was the rooting procedure WAY HARDER(the huawei procedure)... I did well with my LG, but not so well with my Huawei. To be honest I was almost done but because I couldnt boot into TWRP, I decided to follow a guide I cant find cause I followed so many that my History is a mess (if anyone requests I will do some digging though). The guy suggested to someone that couldnt boot into TWRP (like me) that he should falsh TWRP>relock his OEM>Shutdown>Press a combination to go into recovery mode>???>Profit. I did just that but my device is now a 180 Euro brick.
Probelm: My device bootloops. Every time I shut it down (hold power key for 10sec), it reboots and gets stuck on the famous "Your device has been locked and can't be trusted. To learn more, BLAH BLAH BLAH. Your device is booting now...
I tried several key combinations, but whatever I do, when I hold my power key for 10sec, The huawei logo pops up for a second or two and then I get stuck on this screen again...
Sadly, I seem to have no connection between my PC and my device (adb can't find any connected device).
I also want to add that, after I was promted to relock my OEM, I removed the USB cable whoopsie.
What Im looking for:
A way to regain contact between my PC (adb) and my phone
A way to shutdown my device for now (and not forever... just for the night)
Someone to tell me that he had the same issue and took the following steps (Need clear answers and steps)
Anything else whatsoever
I don't think it's necessary to provide the files I used, since the reason my device is like this is because of my own stupidity:silly:
Thank you for your time.
You have to hold Power and Volume Up button pressed to boot into erecovery, not only power, check it.
grgzz said:
You have to hold Power and Volume Up button pressed to boot into erecovery, not only power, check it.
Click to expand...
Click to collapse
Sorry for replying after 2 hours, I didn't get a notification.
I tried:
1. Holding the buttons until I see the "your device is booting..." message
2.Holding the buttons until it vibrates
3.Holding the buttons until I see the Huawei logo
Thanks for your time anyway
You press Volume Up + Power simultaneously, when you see the Huawei logo you release Power and hold Volume Up only until it boots to erecovery.
grgzz said:
You press Volume Up + Power simultaneously, when you see the Huawei logo you release Power and hold Volume Up only until it boots to erecovery.
Click to expand...
Click to collapse
Tried this several times, no result.
Is there a more drastic solution to my stubborn phone?
Aneom7331 said:
Tried this several times, no result.
Is there a more drastic solution to my stubborn phone?
Click to expand...
Click to collapse
The most drastic solution is the DC Phoenix software, not for free, if i am right they ask 15€ for 72 hours.
Not going to bother with this one tho... if I am very desperate, I might try to "borrow" it, but Im gonna seek other solutions until then.
Thanks for your time
On the "your device has been unlocked" hold the Volume up button until you boot to eRecovery. From there connect to wifi and restore stock rom. Afaik, erecovery should boot on bootlooped device. Give it a try
If this doesnt work, plug in to pc, and hold volume up + power, on huawei logo leave power button and hold volume up until you get to erecovery
aciupapa said:
On the "your device has been unlocked" hold the Volume up button until you boot to eRecovery. From there connect to wifi and restore stock rom. Afaik, erecovery should boot on bootlooped device. Give it a try
If this doesnt work, plug in to pc, and hold volume up + power, on huawei logo leave power button and hold volume up until you get to erecovery
Click to expand...
Click to collapse
Hello, thanks for replying
My device is now good, only gapps are missing but I don't care too much. Here is what happened:
So, I left my phone unplugged from any power source during the night (meanwhile the screen couldn't turn off), although I swear I did this 20 times already, when I booted my device after I came back from my University, my phone booted into eRecovery... I downloaded the latest package and it seems to work just fine now, the only problem is that the gapps need to be flased via TWRP (that I don't think I have anymore, how ironic).
Thanks to all of you who cared about giving me a solution :victory: Have a fantastic day
If you want to have a complete working system, i suggest you to try to update using erecovery again. It should download full firmware with gapps etc
Aneom7331 said:
Hello, thanks for replying
My device is now good, only gapps are missing but I don't care too much. Here is what happened:
So, I left my phone unplugged from any power source during the night (meanwhile the screen couldn't turn off), although I swear I did this 20 times already, when I booted my device after I came back from my University, my phone booted into eRecovery... I downloaded the latest package and it seems to work just fine now, the only problem is that the gapps need to be flased via TWRP (that I don't think I have anymore, how ironic).
Thanks to all of you who cared about giving me a solution :victory: Have a fantastic day
Click to expand...
Click to collapse
aciupapa said:
If you want to have a complete working system, i suggest you to try to update using erecovery again. It should download full firmware with gapps etc
Click to expand...
Click to collapse
Well, that was what we told you to do at first time. Erecovery can bring it back to life easily. Now as you have already been told erecovery flashes the complete firmware, including gapps.
You can also try to update it through the settings menu, in the system update settings you press the three dots menu on the upper right corner and select download latest complete package.
grgzz said:
Well, that was what we told you to do at first time. Erecovery can bring it back to life easily. Now as you have already been told erecovery flashes the complete firmware, including gapps.
You can also try to update it through the settings menu, in the system update settings you press the three dots menu on the upper right corner and select download latest complete package.
Click to expand...
Click to collapse
I know you told me first but, the difference was that, my phone had to ran out of battery to do this. In the end of my last reply I said thanks to all of you who cared, including you, you cared the most actualy
Aneom7331 said:
I know you told me first but, the difference was that, my phone had to ran out of battery to do this. In the end of my last reply I said thanks to all of you who cared, including you, you cared the most actualy
Click to expand...
Click to collapse
Well, at least it works now.

Bricked Note 9 - N960F

I have been flashing roms for years on Samsung Devices and every time I had an issue in the past, I was able to fix it - somehow - some way - until now - I believe I have finally - really bricked my phone but in a last ditch desperate effort am hoping someone can help.
Here is the issue:
I was using the most recent Odin to flash the most recent firmware for N960F - the odin flash failed halfway thru - don't know why - it just failed. No error message - but in the top of the column where it usually says PASS when you finish flashing - it said fail.
The phone screen was a blue screen that said the update to my phone has failed - use Smart Switch emergency recovery.
I connected my PC to the phone via USB and when I started Smart Switch - it says my device is not supported. I tried to reboot the phone - tried to turn it off - tried to put it in download mode - and each time it simply goes back to the screen saying that I needed to use Smart Switch Emergency Recovery. Which doesn't work, each time I attempt to use it. Device Not Supported.
I tried to power off the phone and it won't power off. Held power button and volume downfor over 1 minute and nothing happens. (Same thing with power and volume up - power, bixby and volume down) I also tried getting into download mode by holding Volume Down and Bixby and then plugged phone into USB and PC (with Odin open on my PC) and nothing happens.
I have trued everything I can think of - hoping there is something someone can suggest that might work to help me do an emergency recovery or flash stock back onto my phone? Or am I holding an ineffective boat anchor ?
Thanks in advance for your assistance - hoping someone can help.
Geekser said:
I have been flashing roms for years on Samsung Devices and every time I had an issue in the past, I was able to fix it - somehow - some way - until now - I believe I have finally - really bricked my phone but in a last ditch desperate effort am hoping someone can help.
Here is the issue:
I was using the most recent Odin to flash the most recent firmware for N960F - the odin flash failed halfway thru - don't know why - it just failed. No error message - but in the top of the column where it usually says PASS when you finish flashing - it said fail.
The phone screen was a blue screen that said the update to my phone has failed - use Smart Switch emergency recovery.
I connected my PC to the phone via USB and when I started Smart Switch - it says my device is not supported. I tried to reboot the phone - tried to turn it off - tried to put it in download mode - and each time it simply goes back to the screen saying that I needed to use Smart Switch Emergency Recovery. Which doesn't work, each time I attempt to use it. Device Not Supported.
I tried to power off the phone and it won't power off. Held power button and volume downfor over 1 minute and nothing happens. (Same thing with power and volume up - power, bixby and volume down) I also tried getting into download mode by holding Volume Down and Bixby and then plugged phone into USB and PC (with Odin open on my PC) and nothing happens.
I have trued everything I can think of - hoping there is something someone can suggest that might work to help me do an emergency recovery or flash stock back onto my phone? Or am I holding an ineffective boat anchor ?
Thanks in advance for your assistance - hoping someone can help.
Click to expand...
Click to collapse
Have you tried using a different usb c cable? Just a thought
Geekser said:
I have been flashing roms for years on Samsung Devices and every time I had an issue in the past, I was able to fix it - somehow - some way - until now - I believe I have finally - really bricked my phone but in a last ditch desperate effort am hoping someone can help.
Here is the issue:
I was using the most recent Odin to flash the most recent firmware for N960F - the odin flash failed halfway thru - don't know why - it just failed. No error message - but in the top of the column where it usually says PASS when you finish flashing - it said fail.
The phone screen was a blue screen that said the update to my phone has failed - use Smart Switch emergency recovery.
I connected my PC to the phone via USB and when I started Smart Switch - it says my device is not supported. I tried to reboot the phone - tried to turn it off - tried to put it in download mode - and each time it simply goes back to the screen saying that I needed to use Smart Switch Emergency Recovery. Which doesn't work, each time I attempt to use it. Device Not Supported.
I tried to power off the phone and it won't power off. Held power button and volume downfor over 1 minute and nothing happens. (Same thing with power and volume up - power, bixby and volume down) I also tried getting into download mode by holding Volume Down and Bixby and then plugged phone into USB and PC (with Odin open on my PC) and nothing happens.
I have trued everything I can think of - hoping there is something someone can suggest that might work to help me do an emergency recovery or flash stock back onto my phone? Or am I holding an ineffective boat anchor ?
Thanks in advance for your assistance - hoping someone can help.
Click to expand...
Click to collapse
I actually ran into the same exact issue about a week ago, and was sure I bricked my phone. However, when it is stuck on that screen saying to use the emergency Smart Switch recovery, it is actually already in download mode.
After realizing that, I simply used Odin, saw that it detected the phone, and flashed back to my original N960U1 firmware which worked perfectly. I see that you mentioned you tried Odin, but was that when you were trying to go into download mode/rebooting? See if it shows it is connected when it's on the stuck blue screen.
a63548 said:
I actually ran into the same exact issue about a week ago, and was sure I bricked my phone. However, when it is stuck on that screen saying to use the emergency Smart Switch recovery, it is actually already in download mode.
After realizing that, I simply used Odin, saw that it detected the phone, and flashed back to my original N960U1 firmware which worked perfectly. I see that you mentioned you tried Odin, but was that when you were trying to go into download mode/rebooting? See if it shows it is connected when it's on the stuck blue screen.
Click to expand...
Click to collapse
Wow - sometimes the most simple solutions are the right ones. Thank you so much. I was so worried over bricking the device that I didn't realize it was still being recognized by Odin.
I reloaded ODIN and flashed the firmware and it worked. PHone is booting up now. NEver seen an issue like this before - but glad you had the experience to share to help me figure it out. Thanks so much for your help!
Geekser said:
Wow - sometimes the most simple solutions are the right ones. Thank you so much. I was so worried over bricking the device that I didn't realize it was still being recognized by Odin.
I reloaded ODIN and flashed the firmware and it worked. PHone is booting up now. NEver seen an issue like this before - but glad you had the experience to share to help me figure it out. Thanks so much for your help!
Click to expand...
Click to collapse
Awesome to hear it is booting up! Happy to be able to help
Had same problem and i download my firmware from sammy ( its asually the one from tmobile) while i have the international version. The bootloader is all i flashed and it boot back on
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 08:40 PM ---------- Previous post was at 08:39 PM ----------
Just flash same bootloader on your version through odin and it will boot back on
Sent from my [device_name] using XDA-Developers Legacy app
I had the same issue on S7 exynos trying to downgrade firmware. Flashing latest firmware via Odin solved it.

Huawei P20 Pro ANYWAY TO Flashboot? Or bypass the FRP ?

Hi Everyone! Well, today is my time to ask for some help! :fingers-crossed:
I got my hands on a great looking Huawei P20 PRO, unfortunately the Phone is locked FRP... But as i had searched around, there was a method to bypass that by a simple bug they had on the "TALKBACK", like one week ago people was doing that bypass successfully , but this phone has a newer version of talk back, 7.1.x.x...
On the videos people have the previous 6.1.x.x version... That means i don't have the same "help" option as they have.
-After that i tried to get the phone into Fastboot mode, but i can't get the phone on that mode, i press volume down and hold for a while with the device turned off, then i plug the usb, and it just starts charging...
-I press Both vol up and vol down buttons with power at same time, it goes to a screen "EMUI" that says "SOFTWARE INSTALL FAILED! GET HELP FROM xxxx.EMUI COM/BLABLABLA) and says "Reboot system now"...i then press reboot now, and i does a regular reboot and starts up to select language etc, all good... BUT FRP locked...
- Then last night i tried to press VOLUME UP then plug the USB and it got into Erecovery mode, that gave me the option to download the latest version, wipe the current one, shutdown, or reboot... well i had nothing to lose and i did the first to download the latest version, after a 4gb download and install the phone is on the same situation, same version, same everything....
Makes me wonder if someone already done bad attempts before me.
Is there anyway to get the phone on Flashboot? Or bypass the FRP ?
Same
I have exactly the same
Any help????
Thebuckers1986 said:
I have exactly the same
Any help????
Click to expand...
Click to collapse
have you tried the wifi update? it didnt work with me... search for "Upgrade to Android Pie through eRecovery and the Wifi - Firmware Finder PC"

Bootloader / device boot issue

Hoping someone can offer some advice.
So a few days ago my Nokia 8 stopped saving pictures (it was doing this regularly after I flashed the latest (5150) build).
I rebooted the phone only it froze on the Nokia boot logo.
It wouldn't do a forced reboot via the power button, I had to just let the power drain completely to get it to do anything.
I am trying to now flash the latest qlz but I cant get the device in to Download Mode in order to flash.
If I connect it to power (plug or usb) and it gets enough power to turn on then this is what I get:
1. Power and vol+ button held down - boots to Nokia logo, freezes
2. Power and vol- button held down - stays on bootloader unlocked warning screen
3. No buttons held down - stays on bootloader unlocked warning screen
Can anyone advise?
Its almost as if my bootloader is corrupt.
If I try option (1) I do see the device listed via
Code:
adb devices
but its shown as
Code:
NBXXXXXXX unauthorized
and since I have no filesystem access to the device I cant push the key to authorise it.
Any advice humbly appreciated as I really need access to my phone now.
Thanks
Dan
dt_matthews said:
Hoping someone can offer some advice.
So a few days ago my Nokia 8 stopped saving pictures (it was doing this regularly after I flashed the latest (5150) build).
I rebooted the phone only it froze on the Nokia boot logo.
It wouldn't do a forced reboot via the power button, I had to just let the power drain completely to get it to do anything.
I am trying to now flash the latest qlz but I cant get the device in to Download Mode in order to flash.
If I connect it to power (plug or usb) and it gets enough power to turn on then this is what I get:
1. Power and vol+ button held down - boots to Nokia logo, freezes
2. Power and vol- button held down - stays on bootloader unlocked warning screen
3. No buttons held down - stays on bootloader unlocked warning screen
Can anyone advise?
Its almost as if my bootloader is corrupt.
If I try option (1) I do see the device listed via
Code:
adb devices
but its shown as
Code:
NBXXXXXXX unauthorized
and since I have no filesystem access to the device I cant push the key to authorise it.
Any advice humbly appreciated as I really need access to my phone now.
Thanks
Dan
Click to expand...
Click to collapse
The fastest way to fix it is taking to a care centre near you. or any Nokia certified store to reflash it for you. if it's out of warranty they will probably charge you ~$20

How to stop Nokia 2.3 from auto boot when charger is plugged in?

1. Automatic boot when charger is connected, power off this Nokia 2.3 then connecting the charger is like pressing the power button, it just do a normal start, also power it down while connected to to charger still it just do a normal rebooting.
2. Factory reset is locked (settings>backup and restore>factory reset>) that function is greyed out meanwhile it's not working even if you touch for ages.
3. Build number is not working, (settings>about phone>build number) tapping this function Has to unlock developer options hence this function is not working too There's no way I can enable debugging mode.
4. Recovery boot is locked, pressing power button + Vol- it display this massage "as fastboot is locked..... your phone will restart in (3)s"....., Pressing power button + Vol+ the device just start normally,. Pressing all the three buttons device will not react at all, I tried holding these 3 buttons for 2 minutes but nothing happened.
5. No updates to fix this online currently running android 10 which means there's no android 11 patches for Nokia 2.3 to fix this issues
6. Can't root this device as almost every possibility is off.
PLEASE NOTE: THIS ANDROID 10 ROM AM USING WAS FLASHED TO THIS DEVICE BY A FRIEND MEANWHILE THE UPDATE FROM ANDROID PIE(9) TO ANDROID 10 (R) WAS DONE OFFLINE
IF THERE'S ANYWAY TO FIX THIS PLEASE ADVISE ON WHAT TO BE DONE OR IF THERE'S ANY SOFTWARE THAT CAN FIX THIS PLEASE HELP THIS IS KILLING ME .
Lin12 said:
1. Automatic boot when charger is connected, power off this Nokia 2.3 then connecting the charger is like pressing the power button, it just do a normal start, also power it down while connected to to charger still it just do a normal rebooting.
2. Factory reset is locked (settings>backup and restore>factory reset>) that function is greyed out meanwhile it's not working even if you touch for ages.
3. Build number is not working, (settings>about phone>build number) tapping this function Has to unlock developer options hence this function is not working too There's no way I can enable debugging mode.
4. Recovery boot is locked, pressing power button + Vol- it display this massage "as fastboot is locked..... your phone will restart in (3)s"....., Pressing power button + Vol+ the device just start normally,. Pressing all the three buttons device will not react at all, I tried holding these 3 buttons for 2 minutes but nothing happened.
5. No updates to fix this online currently running android 10 which means there's no android 11 patches for Nokia 2.3 to fix this issues
6. Can't root this device as almost every possibility is off.
PLEASE NOTE: THIS ANDROID 10 ROM AM USING WAS FLASHED TO THIS DEVICE BY A FRIEND MEANWHILE THE UPDATE FROM ANDROID PIE(9) TO ANDROID 10 (R) WAS DONE OFFLINE
IF THERE'S ANYWAY TO FIX THIS PLEASE ADVISE ON WHAT TO BE DONE OR IF THERE'S ANY SOFTWARE THAT CAN FIX THIS PLEASE HELP THIS IS KILLING ME .
Click to expand...
Click to collapse
Any help on this please?

Categories

Resources