Database Users

help! Defy wont boot, white light at top, rsdlite doesnt recognise

Deleted by user

I suggest you to completely charge your phone for half a day and then try to power it on. It should at least get stuck in the M logo.
Sent from my MB525 using XDA App

Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.

Was your battery low when you tried flashing? It will not charge in bootloader mode so if you're battery is low you will have issues. If you boot with volume up pressed does it give you a message?
Try the Mcgyver battery fix found in this forum.
skateguitar00 said:
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Click to expand...
Click to collapse

Deleted by user

I had that problem while trying the "Flash FroYo without losing downgradeability" solution: SBF Problem
After downloading, flashing every other available official ROM, and failing with each one, and seeing that no other SBF fro T-Mo exists anywhere, I bit the bullet and flashed the T-Mo signed FroYo ROM. And it worked!
So now I may have screwed myself over by flashing the leaked ROM but hey, it works well and is fast. Plus, it's FroYo so I now have A2SD and built-in Tethering...
gookia2000 said:
Hi all, I am a proud owner of a t-mobile defy (for about 2 months now!) and my hands got itchy today and went ahead to "debrand" it following the guide by Higgsy.
I was trying to flash a uk 2.21 rom onto my t-mobile defy (rooted with z4root).
Well, I managed to do all the steps of the guide. my phone was recognised by rsdlite, i selected the uk 2.21 sbf file, i clicked start, and it started flashing the different code groups. Finally, it said "finished" and "PASS". Here is when the problem started. The phone did not reboot into android. It was just a blank screen with a white light on the top (where the green led is to inform you about new messages.)
i panicked and disconnected the phone (the white light turns off after disconnecting), took out the battery, tried rebooting, tried rebooting into recovery (power + vol down), tried rebooting into bootloader (power + vol up). Nothing worked. it just stayed dead.
I then plugged it back into the computer. immediately the white light came back on and rsdlite recognised my phone. i tried flashing again - same result. I then tried flashing the 2.52 uk rom - same result.
even more panicky now, i unplugged everything and decided to take a nap and hopefully think of some ingenious solution to the problem. now, after a 3 hour rest, i tried plugging the phone back into the computer. the white light comes on, but now rsdlite doesnt even recognise the phone.
In essence, is my phone bricked? I cannot:
1) load into recovery to do a nandroid restore (yes, i have a nandroid backup copy)
2) load sbf files from rsdlite. every sbf file i tried doesnt seem to work. now its worse as rsdlite doesnt even recognise my phone.
i have even tried doing a nandroid restore via adb. but i get the error message that no phone was detected in the command prompt. perhaps its because the phone was not started in recovery mode.
The only explanation i can think of is that i have recently updated to the t-mobile 3.6.360 update and that might be the reason why so many people before me were able to flash their defy's roms successfully while i got stuck.
Can anyone please help? I LOVED my defy more than any other phone, and 2 months was too shortlived!
Click to expand...
Click to collapse
skateguitar00 said:
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Click to expand...
Click to collapse

Deleted by user

Actually, all you have to do is press the power button while the LED is on and RSDLite is running. You will hear the USB detection sound and your phone will appear on the list. It won't appear as it normally would but it will be listed.
Then just choose the Froyo ROM and then click start to flash it. It'll take less than 10 minutes...
There's no other way that I know of to get it working. Even in the link that I posted, you can check and see that no one even bothered to give me an idea of what to do. I had to figure this out myself.
I figured it was the bootloader protection that was causing the problem so the logical choice was to flash the only T-Mo ROM available which happens to be the leaked Froyo.
It's been almost 24 hours and I've had no problems with FroYo so as far as I'm concerned, I'm good.
gookia2000 said:
Beach Head, thanks for your reply. you have provided me with a glimmer of hope!!! the leaked tmobile froyo sbf is one i have not tried. I will certainly try to flash my defy with that once i have gotten it recognised by rsdlite.
I believe my phone is currently not being recognised by rsdlite due to insufficient battery. (cant confirm this, as all i see when i plug in the usb is a white light on my phone. but ever since i started this entire nightmare, i think i have attempted flashing at least 5 different sbf files and considerable battery has been drained.) I will try the Mcgyver battery fix next.
skateguitar, THERE IS HOPE!!! i havent confirmed it yet but i think we all got stuck cos we were trying to flash from a "non-downgradeable" 3.6.360 firmware. and rsdlite does not recognise our phones due to low battery (your phone was left with a white light on after flashing for 1 whole night.) SO... i propose this course of action: 1) perform the Mcgyver battery fix and try to get our phones recognised by rsdlite first. 2) once recognised, flash with the leaked tmobile froyo sbf.
Does anyone have any better suggestions before i plunge head first to save my phone?
Click to expand...
Click to collapse

Yes all i wanted to say was that you might have lost your downgradability and thats why phone does not boot. Simple thing is to flash the original sbf like what beachhead suggested. It definitely should work.
Sent from my MB525 using XDA App

Guess what, it works!!!
Deleted by user

Glad I could help you out!
Enjoy Froyo!
gookia2000 said:
OHMYGOODNESS!!! I LOVE YOU GUYS!!!
My Defy has been flashed with the t-mobile froyo leaked rom and IT WORKS!!! I was so mentally set with the idea that my defy has been bricked and I just threw $400 down the drain... NOW I AM SO HAPPY!!!
Anyway, just for your information, here is what I did:
- I first tried to get my defy recognised by rsdlite. I tried Beach Head's suggestion of pressing the power button while the led is on to no effect. I reckon that the battery has just been drained too low. So, i went ahead with the McGuyver battery fix.
- Alas, with the wires protruding precariously from my phone, rsdlite finally recognised my phone. I went to load the leaked t-mobile froyo rom and went ahead flashing it.
- And, guess what, IT WORKS!!!
Thank you all so much, especially beach head, for your help in this forum! I would have gone to the mobile store to get another phone if not for you guys!!!
Click to expand...
Click to collapse

I have the same problem, and will probably end up trying to flash the leaked Tmobile Rom.
Can you point me to where you downloaded this file? I think I found the thread, but I want to be sure

Deleted by user

got it! Thanks!
Now to ultimately decide if I want to flash this, since it's non-downgradeable

To update, flashing this rom has fixed my phone. Yay! Thanks!
I wonder if it was the 3.66x update that Moto pushed out - this phone was brand new, bought in Dec 2010, no other hacking done on it...

Beach_Head said:
I had that problem while trying the "Flash FroYo without losing downgradeability" solution: SBF Problem
After downloading, flashing every other available official ROM, and failing with each one, and seeing that no other SBF fro T-Mo exists anywhere, I bit the bullet and flashed the T-Mo signed FroYo ROM. And it worked!
So now I may have screwed myself over by flashing the leaked ROM but hey, it works well and is fast. Plus, it's FroYo so I now have A2SD and built-in Tethering...
Click to expand...
Click to collapse
How did you get it to show up in rsd

I'm not working on my phone because i think i messed it up enough, so i took it to a store that fixes phones. The guy told me that he had my battery on a universal charger and he still cant get rsd lite to recognize it... What can i do

Another Happy Defy User
Just to confirm, I was seeing the same thing gookia2000 was seeing. Here was my resolution in case it helps anyone:
I was able to get mine working by flashing the US Stock Froyo build as explained in this thread: http://forum.xda-developers.com/showthread.php?t=938708&highlight=bricked&page=2
I found this thread to be super helpful as it helped me confirm my suspicion that the battery being low was the issue: http://forum.xda-developers.com/wik...#Recover_Nearly_Bricked_Phone_.28hopefully.29
Thankfully my wife has the same phone so I borrowed her battery, otherwise I would have been going McGyver style per Sorensiim (da' man) as seen here:
http://forum.xda-developers.com/showthread.php?t=892026
So happy this nightmare is over - running Froyo is a little bonus love!
Thanks to all @ XDA!!!
-Dave

Defy wont come on get a white light!
im having the same prob i did the the steps but its not working is there anything else i can do or is there a video of the proceeder

I have the same issue with a Telstra defy. I can get RSD to recognise something is connected but it isnt listed as MB525 like before but as "S Flash OMAP3630" I have flashed various SBF files but nothing is changing.

Exceptionally Soft-bricked Atrix: Please Help

Long story short, I think I'm soft bricked.
I've tried wading through DG's soft brick recovery thread and ADB is just kinda beyond me.
As well, I cannot enter fast boot. I've tried holding both volume up + power and volume down + power, and both flash the white letters "Failed to boot 4" then the next line reads "Starting RSD mode"
Honestly, I'm just looking for help that I can understand, or a pretty forgiving walkthrough.
Thanks in advance to anybody who can help.

xyrovice said:
Long story short, I think I'm soft bricked.
I've tried wading through DG's soft brick recovery thread and ADB is just kinda beyond me.
As well, I cannot enter fast boot. I've tried holding both volume up + power and volume down + power, and both flash the white letters "Failed to boot 4" then the next line reads "Starting RSD mode"
Honestly, I'm just looking for help that I can understand, or a pretty forgiving walkthrough.
Thanks in advance to anybody who can help.
Click to expand...
Click to collapse
If you get the starting RSD mode you might have a chance. Put your phone back into that mode and try flash back to stock SBF using rsd lite. Follow this guide: http://forum.xda-developers.com/showthread.php?t=991072&highlight=flash+sbf

What version of software were you running before the brick? 1.26, 1.57 or 1.83? You will need RSD Lite - Download As well as the sbf for your version of software. Post back your version and I can give more guidance.
You may not need to flash all the way back to 1.26, I soft bricked today - as in can't get past the initial Moto screen with a flashing red light, and flashed 1.83 sbf.

I've actually tried to flash some of the SBFs- well, all of them, now that I think of it.
It always ends up in an error, though, and stops.
If you give me a sec, I'll try and recreate it. Off the top of my head, I remember it saying something about "Bypassing BP" or something like that.
Thanks for the fast responses. Lemme try and RSD flash here right quick.
PS (EDIT): I was on 1.5.7 running GladiAtrix 4.2.3 (if that makes any difference). I just started flashing 1.2.6 via RSD. I'll let it sit and see where it sinks.
Thanks again guys.
EDIT #2: So it gets to "Interface AP-OS: Flashing Code Group 57" - 13%, then it just chills for a few minutes, then says [Phone 0000]: Switching device to BP passthrough mode" - still at 13%, then it stops and says "Flashing Process Failed" and, if it hadn't stopped responding, it looks like it would go on to say something about "Interface A..." and the ellipses is where it's cut off. I'm sorry about that.
Any thoughts?

If you were on 1.57 I would try flashing the 1.57 SBF - this will retain a lot of your info, whereas the 1.26 will wipe your phone clean and take more work.
1.57 SBF Thread
You will need to root with gingerbreak to regain root if you flash the 1.57 SBF, Gingerbreak Thread. Make sure to copy the contents of mnt/sdcard and mnt/sdcard-ext to your computer so you can replace them after gingerbreak cleans them out.

xyrovice said:
EDIT #2: So it gets to "Interface AP-OS: Flashing Code Group 57" - 13%, then it just chills for a few minutes, then says [Phone 0000]: Switching device to BP passthrough mode" - still at 13%, then it stops and says "Flashing Process Failed" and, if it hadn't stopped responding, it looks like it would go on to say something about "Interface A..." and the ellipses is where it's cut off. I'm sorry about that.
Any thoughts?
Click to expand...
Click to collapse
Just putting that up there.
Also, I was in the process of trying to wipe my phone for a clean 1.8.3 flash, so a 1.57 flash to retain info isn't a big deal.
I went straight to 1.2.6 in the hopes that the retail version would be more likely to go through (for whatever reason).
Thanks for bearing with me.

Take out your SIM card and SD card if you have one, restart your computer and don't start any other programs besides RSD Lite to allow it the most resources (I've had it fail a few times without enough resources). Start RSD Lite and load up the SBF, turn on the phone and boot to RSD mode with the volume up button, once in RSD mode plug the phone in and start the flash. I don't know if any of this will work for sure but these are all steps to help the process.

try multiple cables, computers, OS's, and USB ports. Sometimes any combination of things helps

Got it. Rebooting now and starting nothing but RSD Lite. Also gonna change the USB port. (SIM and SD gone as of awhile ago, so no worries there. Thanks for checking though)

Well.
I. Will. Be.
I never thought I'd be happy to see that Motoblur login screen.
Phone's up and running. Looks like the reboot + USB port swap did the trick.
And you bros, no matter how simple your advice may have been, are pure gods right now.
Thank you thank you thank you a million times (little girl style- yet there is no shame in prostrating myself before you pros).
Seriously though, I owe you guys a lot. Thanks a ton.

xyrovice said:
Well.
I. Will. Be.
I never thought I'd be happy to see that Motoblur login screen.
Phone's up and running. Looks like the reboot + USB port swap did the trick.
And you bros, no matter how simple your advice may have been, are pure gods right now.
Thank you thank you thank you a million times (little girl style- yet there is no shame in prostrating myself before you pros).
Seriously though, I owe you guys a lot. Thanks a ton.
Click to expand...
Click to collapse
Glad to hear it worked for you, I know what its like to sh*t bricks over a phone snafu so congrats and welcome back to the land of the living.

Bricks? That may have happened when I flashed Adeo and got the red lights.
This time, I sh*t absolute trains.
And I'm beginning to like the Atrix more and more. I didn't lay down all that I had already done trying to recover my phone when I realized things had gone awry, but I'm sure that, on a software level, it was equivalent to repeatedly napalming a small Hawaiian tiki hut.
Thank you again, my friend. I'm almost done flashing 1.83 at this point, and I couldn't have done it without you guys.

Message to delete

I would think your problem lies in trying to flash US At&t software to your French Orange phone. Go to: http://forum.xda-developers.com/showthread.php?t=1125944 and find the French Orange firmware (there are two of them) and download them. If those don't work, try starting your own thread either here or in Q&A. Good luck!
Tim

It works
Happy
Thanks you

[Q] Corrupted partitions - phone won't boot (no bootloader nor recovery)

Hey community,
I think I have fully, irreparably bricked my N4. Here is my situation:
I was running the latest nightly of OmniRom
My battery was dying quick so I wanted to try and use Franco Kernel
My USB cable wasn't working so I needed an on-device way to flash
Francos latest kernel (209) is in a .img and not flashable .zip
I found a thread (which I can't find now) suggesting I dd if=boot.img of=/dev/block/mmcblk0p6
I get into adb shell over wifi and issues the command, but I make a HUGE mistake and miss the "p6" when copying (wrote the image to mmcblk0)
I panic and issue a reboot command
My phone will no longer boot. Even the 'recovery' way of holding volume down and power for 15 seconds only results in a single red pulse of the LED and causes my computer (Manjaro linux) to print the following error in its logs:
qcserial ttyUSB0: usb_wwan_indat_callback: resubmit read urb failed. (-19)
Click to expand...
Click to collapse
Is there anything to be done for my phone short of sending it off for repair? I'm a Canadian living in Peru and to get the N4 fixed I think I'll need to send it back home to Canada and then have someone there send it off. I can't even buy a new phone very easily because the cell phone market in Peru is so expensive. Even if I buy a new device on Google Play and have to get someone from Canada to send it to me in Peru and the import taxes could be as much as the phone.

If you can't get it to boot you're pretty much hosed. I'm not even sure what partition mmcblk0 is. For the future, don't use dd commands unless you really know what you're doing. If you'd issued the right command the 0p6 partition is the boot partition and it probably would have worked.
You're probably stuck with jtag right now
But, check out the flashify app. It would have flashed the kernel correctly.
Sent from my Nexus 5 using XDA Free mobile app

conorkickass said:
Hey community,
I think I have fully, irreparably bricked my N4. Here is my situation:
I was running the latest nightly of OmniRom
My battery was dying quick so I wanted to try and use Franco Kernel
My USB cable wasn't working so I needed an on-device way
My phone will no longer boot. Even the 'recovery' way of holding volume down and power for 15 seconds only results in a single red pulse of the LED and causes my computer (
Click to expand...
Click to collapse
Sometimes one has to find out the hard way that one should never try to flash anything with a low battery. [emoji33][emoji15][emoji45][emoji46]
If you have a wall charger, try letting it charge for awhile and see if you can boot into the recovery.
Sent with my Nexus® 10 minus 3

jd1639 said:
I'm not even sure what partition mmcblk0 is. For the future, don't use dd commands unless you really know what you're doing. If you'd issued the right command the 0p6 partition is the boot partition and it probably would have worked.
Click to expand...
Click to collapse
Yep, I had the command right but I copy-pasted wrong. One of those moments when a non-existent 'enter' is pasted into the terminal window.
Berrydroidcafe said:
If you have a wall charger, try letting it charge for awhile and see if you can boot into the recovery.
Click to expand...
Click to collapse
No luck, unfortunately.
Looks like I'm in the market for a new phone. *sigh*

conorkickass said:
Yep, I had the command right but I copy-pasted wrong. One of those moments when a non-existent 'enter' is pasted into the terminal window.
No luck, unfortunately.
Looks like I'm in the market for a new phone. *sigh*
Click to expand...
Click to collapse
How long did you charge it? If only the N4 would charge as fast as it discharge....

Berrydroidcafe said:
How long did you charge it? If only the N4 would charge as fast as it discharge....
Click to expand...
Click to collapse
Overnight. I'm thinking this red light is the Red Light of Death and not the read light of dead battery - it doesn't pulse, it only pulses on once and then goes out again.

conorkickass said:
Overnight. I'm thinking this red light is the Red Light of Death and not the read light of dead battery - it doesn't pulse, it only pulses on once and then goes out again.
Click to expand...
Click to collapse
first off, there is a zip folder in the franco´s server, that contains zip
second
mmcblk0 its the whole nand, if u rebooted it then it didnt finished flashing, so abootb can still be alive
get a Windows pc(needs to be win 7 or lower,8 causes problems), and try to use lgnpst or qpst,
lgnpst:
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
qpst(if abovedosent work)
http://forum.xda-developers.com/nexus-4/general/wip-unbricking-nexus-4-using-qpst-t2208289
(required files are in the last page)

opssemnik said:
first off, there is a zip folder in the franco´s server, that contains zip
Click to expand...
Click to collapse
The test kernel (209) wasn't available in zip yet, which led to my experimenting and utterly failing!
opssemnik said:
try to use lgnpst or qpst,
Click to expand...
Click to collapse
I will try these tonight or tomorrow night and post feedback. Thanks for the help.

Looks like JTAG is my only option. I think I've found a place that can do it in Lima. Anyone have any idea of JTAG services in Peru? (That might be a long shot). Thaks all for the suggestions and advice!

tmobile s8 boot loop-ish

hey all,
Saturday morning a wake up to my alarm on my phone (SM-G950U T-Mobile Stock since new) and turn off the alarm and proceed to check email and scroll social medias. A few minuted later phone turns off and starts boot looping. Occasionally it would boot to home screen and i could unlock it but then maybe 30 seconds later it would start boot loping again. Now it either just boot loops or boots straight to recovery . I have tried flashing current firmware in case it was corrupted and i have tried accessing it through ADB. I know for a fact USB debugging is on because I just used abd to pull wifi passwords 2 weeks ago, but when I try to [ abd devices] if comes up as unauthorized and I cannot proceed. I know everyone will suggest a factory reset, but I am hoping someone has a trick for extracting files. I dont care about most on my phone, but I would like to save the pics from my GF and I trip this past august. Apparently I didnt have my photo library set to sync to cloud -_-
thanks
-chip
update: it appears there is a pattern. it boot loops or boots to recovery (after a blue failed system update screen) 99% of the time. the 1% it boot fully and then crashes is only when battery is 0% . it for some reason is only trickle charging and isnt getting enough juice when it does boot fully to stay on . But if i leave it charging a while it will then only boot loop or boot to recovery. Strange...any way I had enough time this past boot to reauthorize usb debug.....wish me luck with adb
....nevermind. still shows up as unauthorized

chip102 said:
hey all,
Saturday morning a wake up to my alarm on my phone (SM-G950U T-Mobile Stock since new) and turn off the alarm and proceed to check email and scroll social medias. A few minuted later phone turns off and starts boot looping. Occasionally it would boot to home screen and i could unlock it but then maybe 30 seconds later it would start boot loping again. Now it either just boot loops or boots straight to recovery . I have tried flashing current firmware in case it was corrupted and i have tried accessing it through ADB. I know for a fact USB debugging is on because I just used abd to pull wifi passwords 2 weeks ago, but when I try to [ abd devices] if comes up as unauthorized and I cannot proceed. I know everyone will suggest a factory reset, but I am hoping someone has a trick for extracting files. I dont care about most on my phone, but I would like to save the pics from my GF and I trip this past august. Apparently I didnt have my photo library set to sync to cloud -_-
thanks
-chip
update: it appears there is a pattern. it boot loops or boots to recovery (after a blue failed system update screen) 99% of the time. the 1% it boot fully and then crashes is only when battery is 0% . it for some reason is only trickle charging and isnt getting enough juice when it does boot fully to stay on . But if i leave it charging a while it will then only boot loop or boot to recovery. Strange...any way I had enough time this past boot to reauthorize usb debug.....wish me luck with adb
....nevermind. still shows up as unauthorized
Click to expand...
Click to collapse
Ive had similar cases happen with older models. May be time for a battery. They will do crazy **** when the battery crashes. When you flashed stock firmware you lost adb authorisation. Need to get the system back first for that.

TheMadScientist said:
Ive had similar cases happen with older models. May be time for a battery. They will do crazy **** when the battery crashes. When you flashed stock firmware you lost adb authorisation. Need to get the system back first for that.
Click to expand...
Click to collapse
thank you very much. my battery life was greatly suffering and the USB-c port was worn pretty bad. Ill grab a new battery and hope that works.

chip102 said:
thank you very much. my battery life was greatly suffering and the USB-c port was worn pretty bad. Ill grab a new battery and hope that works.
Click to expand...
Click to collapse
Cheapest fix in my opinion. I saw another thread a guy dropped his. Now detects 9008 how to fix. More than likely a phone wont just not boot. Or lose programming unless a hardware issue. So if it was just running and quit. Not modding stuff really. More likely than not its gonna be some form of software. But hardware.

TheMadScientist said:
Cheapest fix in my opinion. I saw another thread a guy dropped his. Now detects 9008 how to fix. More than likely a phone wont just not boot. Or lose programming unless a hardware issue. So if it was just running and quit. Not modding stuff really. More likely than not its gonna be some form of software. But hardware.
Click to expand...
Click to collapse
Replaced Daughter board and battery. No improvement :/ bummer

the only time i can get it back into recovery is after a "successful" flash with odin. by successful i mean that it says it worked but it just continues to boot loop or boots to recovery. attached is a picture of the info i get in recovery every time. hope someone can shed some light in the issue. im using my old phone so i dont feel pressured to call the data a loss and try a factory reset just yet....my old phone is a POS though

chip102 said:
the only time i can get it back into recovery is after a "successful" flash with odin. by successful i mean that it says it worked but it just continues to boot loop or boots to recovery. attached is a picture of the info i get in recovery every time. hope someone can shed some light in the issue. im using my old phone so i dont feel pressured to call the data a loss and try a factory reset just yet....my old phone is a POS though
Click to expand...
Click to collapse
Yea some one tried to root it using the edl safestrap thread. Only wsy to fix it is filled the steps and reflash jrkruses pie rom. One of my mother boards are in the same state. That's the only way dm verity fails. Is his rom method.
There's some easy to flash a cache wipe in Odin but I hadn't found it yet. I have 2 mother boards and one is identical. I flash this stock and lose download or recovery. but the errors you show are only from doing that edl safestrap

Ill be honest..i have no idea what you are talking about. Ive messed with the software with previous devices and never heard of safe strap. This one has been bone stock since I got it from Tmobile and i haven't attempt to flash anything until i had this issue. never tried to root it
TheMadScientist said:
Yea some one tried to root it using the edl safestrap thread. Only wsy to fix it is filled the steps and reflash jrkruses pie rom. One of my mother boards are in the same state. That's the only way dm verity fails. Is his rom method.
There's some easy to flash a cache wipe in Odin but I hadn't found it yet. I have 2 mother boards and one is identical. I flash this stock and lose download or recovery. but the errors you show are only from doing that edl safestrap
Click to expand...
Click to collapse

chip102 said:
Ill be honest..i have no idea what you are talking about. Ive messed with the software with previous devices and never heard of safe strap. This one has been bone stock since I got it from Tmobile and i haven't attempt to flash anything until i had this issue. never tried to root it
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s8/development/root-t3904613. This thread can help you at least get pie back up and running. I wouldn't mess with no more. I haven't had much luck with mine. But I did get it booting again

[Bricked/Help] Just another moron f*d up

Tl;dr: I(dumbass) bricked my phone to the point, where I only can get the bootloader. No fastboot mode, no recovery, no boot.
How: I rooted my phone to a pretty good working state of stock OS+Magisk, right after I got it (Android 10). Later after a couple systemupdates and the patch to A11 and even more updates I thought, it would be time to patch magisk again, or revert to unroot, so I tried patching magisk, but somehow my phone got a lot of bugs, like no sound and very long boot times.
Then I tried reverting back by adding a stock boot image and stuff and a lot of things went unlike any tutorial said and now I'm stuck on beforementioned phonestate.
My PC(Asus Notebook) with installed Qualcomm-Drivers and Oneplus-drivers only recognizes the phone when I try to connect it via EDL-mode (vol-up+down+connect USB) but only for like 10 sec. Then bootloader starts up annd connection is lost.
What would be the most logical approach? How do I start?
And yes, I read a lot of posts trying to fix it myself, but I can only find so much.

This will work. https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/

MRobbo80 said:
This will work. https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/
Click to expand...
Click to collapse
Are you using the correct cable?

Thread can be closed.
I followed the beforementioned link already but on my homepc I had some issues with the tool and/or drivers, I think.
Now on my notebook Ijust wasn't quick enough, so the phone restartet into bootloader after a couple seconds.
After a couple tries it worked.

Whew, glad that worked out. I bricked my Optimus M and this guy Asdullah took time out of his day to video chat with me and help me unbrick my phone. Some folks in this community are ****ing awesome!