Database Info

Magic bricked

Test methods need to unbrick my magic, so far I've tried one that I have not worked. If someone want to try things that I communicate them and I try.
After an upgrade of radio has been fried. I can not get into recovery, or fastboot. Even so I try to send commands and the command window stays and even restart <waiting for device> clicking to enter recovery fastboot or does nothing.
Excuse the translation but my English is very bad and I use the google translator

edugg said:
Test methods need to unbrick my magic, so far I've tried one that I have not worked. If someone want to try things that I communicate them and I try.
Click to expand...
Click to collapse
wow so much information don't know where to start!!!

hard to say..someone managed to the the phone to respond to fastboot/adb by starting up ADB..
wait for the waiting for device msg, then connect the phone to usb and turn it on.
if all method fails, bring it back to claim for warranty.

edugg said:
Test methods need to unbrick my magic, so far I've tried one that I have not worked. If someone want to try things that I communicate them and I try.
After an upgrade of radio has been fried. I can not get into recovery, or fastboot. Even so I try to send commands and the command window stays and even restart <waiting for device> clicking to enter recovery fastboot or does nothing.
Excuse the translation but my English is very bad and I use the google translator
Click to expand...
Click to collapse
What OS are you using on your computer?

zeroplace said:
What OS are you using on your computer?
Click to expand...
Click to collapse
I tested with Windows 7, Vista and XP and the same.

You know any way to flash as factory?

Will it actually turn on or does it just flash a red led when you press power?

bonesy said:
Will it actually turn on or does it just flash a red led when you press power?
Click to expand...
Click to collapse
Starts, appears the splash but only gets to that point

In that case it isnt bricked its just stuck...Bricked is when it wont turn on at all
Do you have a nandroid backup?
Have you taken the battery out and the power lead so it has no power?
i have had this problem
If you have a backup get it ready, Once you have let the phone power down totally (battery out and no lead) hold back and press power (keep holding back) this should get you into fastboot.if it doesnt unplug the lead and try again.
If thats successful.... using your nandroid files
FASTBOOT COMMANDS
fastboot erase system -w
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
Sorry if you cant get this to work i have to go out and wont be back to check till tomorrow so just giving you all the info

bonesy said:
In that case it isnt bricked its just stuck...Bricked is when it wont turn on at all
Do you have a nandroid backup?
Have you taken the battery out and the power lead so it has no power?
i have had this problem
If you have a backup get it ready, Once you have let the phone power down totally (battery out and no lead) hold back and press power (keep holding back) this should get you into fastboot.if it doesnt unplug the lead and try again.
If thats successful.... using your nandroid files
FASTBOOT COMMANDS
fastboot erase system -w
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
Sorry if you cant get this to work i have to go out and wont be back to check till tomorrow so just giving you all the info
Click to expand...
Click to collapse
I have tried many times to do this and nothing ever stays <waiting for device> and does nothing

Phone is not bricked, so this shouldnt be a problem.
If you cant get into fastboot with current setups, then use another recovery image and a custom rom.
(all that stuff is on SD-card.. its not that hard)
Update SDK.

daihiep said:
Phone is not bricked, so this shouldnt be a problem.
If you cant get into fastboot with current setups, then use another recovery image and a custom rom.
(all that stuff is on SD-card.. its not that hard)
Update SDK.
Click to expand...
Click to collapse
Great! And how should the recovery image and custom rom be put into the Magic? Sledgehammer?
The problem that almost everyone seems to not understand is that it's impossible to access fastboot, adb or any other (known) means.
The magic will hang at the first splashscreen no matter which buttons are pushed during power up. If the track ball is pressed during power on, the led lights up blue (still hanging at first splash). All other combos of buttons during power on makes no difference at all.
I have tried keeping fastboot waiting while power cycling the device (as explained in another thread), but there are no reaction. I have tried in xp, vista and linux.
I have also tried with a gold card, but since the phone seems unable to get any further than the first splash, this will not work.
So unless someone has a _NEW_ method to actually enter fastboot/ADB mode, these devices are BRICKED!
People have been discussing what the criteria for calling a phone a brick, but as far as I have care my Magic can only function as a paper weight and can therefore be called bricked.

Help
I have the same problem , the fastboot can not acces, i stay at the vodafone logo.
Any ideas?
HHHHHHHHHHHEEEEEEEEEEEELLLLLLLLLLPPPPPPPPPP.

frankiboy1 said:
Great! And how should the recovery image and custom rom be put into the Magic? Sledgehammer?
Click to expand...
Click to collapse
take out the sd card, put it in a usb adaptor and copy them over.
Also search for a thread "how i unbricked my phone"

frankiboy1 said:
Great! And how should the recovery image and custom rom be put into the Magic? Sledgehammer?
The problem that almost everyone seems to not understand is that it's impossible to access fastboot, adb or any other (known) means.
Click to expand...
Click to collapse
Think before answering.
Btw, question answered by htcmagic.

daihiep said:
Think before answering.
Btw, question answered by htcmagic.
Click to expand...
Click to collapse
I repeat: The problem that almost everyone seems to not understand is that it's impossible to access fastboot, adb or any other (known) means.
Having a recovery image and a custom rom on the SD card is useless if you are not able to get the phone accessing those files.
I have tried the "how I unbricked my phone" method (like I wrote in my first post) without any success. If you read the whole "how I unbricked my phone" thread you can see that there are several guys that did not have success with this method.
I have done a lot of thinking.... and searching...
Thanks

http://forum.xda-developers.com/showthread.php?t=571457 try there

Wrong HBOOT = real brick
Guys,
With a wrong HBOOT (what happend to me), the phone is a real brick...
And they refused to repair it... I bought a new phone. But I keep the old one in case someone break his screen. Then I can get the mobo.

just curious.
superkikim said:
Guys,
With a wrong HBOOT (what happend to me), the phone is a real brick...
And they refused to repair it... I bought a new phone. But I keep the old one in case someone break his screen. Then I can get the mobo.
Click to expand...
Click to collapse
How did you brick it?
Btw, have you tried to run any RUU update?
At least singapore one.

help.

i just installed pacman rom using clockworkmod recovery something..

fastboot flash boot boot.img.
Google that, instead of spamming threads in all the forums. This is the most commonly occurring beginner error, it's stated multiple times in multiple places, and still people keep asking instead of reading.
If it's not your case - look at "non-Sony screen" thread.

Jack_R1 said:
fastboot flash boot boot.img.
Google the damn thing, instead of spamming threads in all the forums.
Click to expand...
Click to collapse
m extremely sorry..
but i have been trying since 2 hrs..
still could not find a solution..
pleae help!

jigi1993 said:
m extremely sorry..
but i have been trying since 2 hrs..
still could not find a solution..
pleae help!
Click to expand...
Click to collapse
please guys help..
the bloody boot.img is not supportted by winzip..
'fastboot' is not recognized as
operable program or batch file.
error

Jack_R1 said:
fastboot flash boot boot.img.
Google that, instead of spamming threads in all the forums. This is the most commonly occurring beginner error, it's stated multiple times in multiple places, and still people keep asking instead of reading.
If it's not your case - look at "non-Sony screen" thread.
Click to expand...
Click to collapse
jigi1993 said:
please guys help..
the bloody boot.img is not supportted by winzip..
'fastboot' is not recognized as
operable program or batch file.
error
Click to expand...
Click to collapse
Did you do what Jack said and GOOGLE IT????? Go away and put some effort in for yourself - it will be much better for you to understand WHAT and WHY you need to do things - or next time you will brick your phone beyond recovery.

SimonTS said:
Did you do what Jack said and GOOGLE IT????? Go away and put some effort in for yourself - it will be much better for you to understand WHAT and WHY you need to do things - or next time you will brick your phone beyond recovery.
Click to expand...
Click to collapse
Sir m damn serious..
i hve been googling in around 4 hrs now..
i did my best but i cant now..
please provide an easy solution..
the boot image error comes in..
i cant extract that file .

Here you go

SimonTS said:
Here you go
Click to expand...
Click to collapse
kk.

So you've installed ADB then?

SimonTS said:
So you've installed ADB then?
Click to expand...
Click to collapse
i downloaded pacman rom.
copied it into root of sd.
wiped data and installed it through clockmod recovery .!
it was installed properly but after reboot it stuck on htc white screen..

:banghead:

teadrinker said:
:banghead:
Click to expand...
Click to collapse
I couldn't agree more - I give up on this guy, if he can't even deal with what I asked then there is no hope for him.

Ok I don't know why I'm doing this but your answer is in this thread
http://forum.xda-developers.com/showthread.php?t=1525100
[Guide] How to root, install EXT4 recovery and custom ROM on HBOOT 2.00.0002
Everyone has a right to be stupid. Some just abuse the privilege

jugg1es said:
Ok I don't know why I'm doing this but your answer is in this thread
http://forum.xda-developers.com/showthread.php?t=1525100
[Guide] How to root, install EXT4 recovery and custom ROM on HBOOT 2.00.0002
Everyone has a right to be stupid. Some just abuse the privilege
Click to expand...
Click to collapse
Because we are too nice...
@op cd ( http://en.wikipedia.org/wiki/Cd_(command) ) in the directory where your fastboot and adb in located ( path-to/platform-tools) and fastboot commands should be working.

Oh c'mon guys don't be so rude. You've been noobs too.
To return in topic:
1) you have the clockwork mod recovery, so I'm assuming that you already have unlocked the boot loader but you still S-ON ( you can check it by powering up the phone by pressing TOGETHER the volume down AND the power button). But i may ask you to verify that you have installed on your PC at least ADB and FASTBOOT? If you're not, please install them, otherwise you won't be able to get your phone work.
2) now, you say that you have flashed the pacman ROM but you are stuck on the HTC logo. Don't panic. It is a common issue, i have done it a lot of times. Just check from adb if it can see you device (you have to plug in the phone to the computer via your recharge cable). If it sees the phone it is quite simple to return to the boot loader. Simply open a terminal on your pc, navigate on the folder in which you have saved adb and write "adb reboot bootloader". This will bring you to the bootloader screen. Check now if there is written "FASTBOOT USB". If not and it is written HBOOT USB navigate with the volume keys on fastboot. This should bring you to the fastboot usb.
Now double click on the .zip containing the pacman ROM you've installed. Extract ONLY the boot.img and place it in the same directory in which you've placed fastboot. Now in the terminal of you PC write "fastboot flash boot boot.img" and then reboot the phone. This should solve your issue.
If the adb doesn't see you phone you have to pull out the battery, WAIT at least 30 seconds, replace it, and then press TOGETHER volume down and power button to enter into bootloader. From there follow the step that i wrote you previously and you'll be good to go!
Sent from my Desire S using xda app-developers app

Jedioscuro said:
Oh c'mon guys don't be so rude. You've been noobs too.
To return in topic:
1) you have the clockwork mod recovery, so I'm assuming that you already have unlocked the boot loader but you still S-ON ( you can check it by powering up the phone by pressing TOGETHER the volume down AND the power button). But i may ask you to verify that you have installed on your PC at least ADB and FASTBOOT? If you're not, please install them, otherwise you won't be able to get your phone work.
2) now, you say that you have flashed the pacman ROM but you are stuck on the HTC logo. Don't panic. It is a common issue, i have done it a lot of times. Just check from adb if it can see you device (you have to plug in the phone to the computer via your recharge cable). If it sees the phone it is quite simple to return to the boot loader. Simply open a terminal on your pc, navigate on the folder in which you have saved adb and write "adb reboot bootloader". This will bring you to the bootloader screen. Check now if there is written "FASTBOOT USB". If not and it is written HBOOT USB navigate with the volume keys on fastboot. This should bring you to the fastboot usb.
Now double click on the .zip containing the pacman ROM you've installed. Extract ONLY the boot.img and place it in the same directory in which you've placed fastboot. Now in the terminal of you PC write "fastboot flash boot boot.img" and then reboot the phone. This should solve your issue.
If the adb doesn't see you phone you have to pull out the battery, WAIT at least 30 seconds, replace it, and then press TOGETHER volume down and power button to enter into bootloader. From there follow the step that i wrote you previously and you'll be good to go!
Sent from my Desire S using xda app-developers app
Click to expand...
Click to collapse
Hey, i wasn't rude. I gave e a thread that is a good starting point to solve his issue without talking him through it
A word to the wise ain't necessary -- it's the stupid ones that need the advice.
Bill Cosby

jugg1es said:
Hey, i wasn't rude. I gave e a thread that is a good starting point to solve his issue without talking him through it
Click to expand...
Click to collapse
^^^^ This ^^^^ There is a HUGE difference between helping someone when they need help and helping someone when they are just being too lazy to actually read and find things out themselves.
I see it as no different to when I need tech-support from one of my equipment suppliers. If I call them up with a genuine problem they will help me, but if I phone them and say "Where do I plug the keys in?" or "I've turned the kit on but didn't bother reading the instructions first, now it's broken" - what do you think their reply to me will be?

SimonTS said:
^^^^ This ^^^^ There is a HUGE difference between helping someone when they need help and helping someone when they are just being too lazy to actually read and find things out themselves.
I see it as no different to when I need tech-support from one of my equipment suppliers. If I call them up with a genuine problem they will help me, but if I phone them and say "Where do I plug the keys in?" or "I've turned the kit on but didn't bother reading the instructions first, now it's broken" - what do you think their reply to me will be?
Click to expand...
Click to collapse
Yeah, you're right. But from the disperation of the guy It seemed to me pointless to leave him with a non-functioning phone without any advise. After all this is a forum plenty of people that know how to do practically everything with an android device, but I don't think that everyone have started from a solid programming base or a perfect hardware knowledge.
Regarding me, I have looked into this forum a couple of months BEFORE even try to unlock my phone and flashing something other than the horrible desire's gingerbread stock rom, but I understand the people who wants to try something new, even if they are not so expert.
For the next time, don't worry I'll be mercyless

I'm always ready to help where i can but. It seems like the op followed half a guide then just assumed it would work, i must of read all the guides until my head hurt, and most of my first posts were silly questions already posted. I learnt far more about my phone from searching than i think i could have from my first posts
A word to the wise ain't necessary -- it's the stupid ones that need the advice.
Bill Cosby

He would have avoided all the pain if he used the boot img flashing software
Sent from my Desire S using xda premium

[Q] Sudden Bootlooping! Please HELP!!!

Hi, guys! Signed up just to ask this since everyone on here seems helpful. Long story short, my digitizer got damaged, so I replaced it today. First time doing something like that, but I was EXTREMELY careful and followed a repair guide on YouTube to the dot! Phone is currently (or possibly WAS) running CM11, Android 4.4 BEAUTIFULLY! No problems whatsoever before the damage occurred.
Got the piece replaced today, turned the phone on and it started bootlooping :crying: I don't know why it started, so I opened it up again, checked every single connection and they're all good. No damaged ribbon cables, nothing. Still looping....Flashed back to stock ICS with RSD 6.1.5, still looping....Reflashed CM11, still doin' it.
I cannot for the life of my figure out what's going on. I have CWM Recovery 6.0.1.2 on it right now and got an error log to show on the screen. Here's what it says, word for word:
CWM Based Recovery v6.0.1.2
ro.hardware=gcom
ro.revision=33456
ro.emmc=1
ini.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
i: Checking for extendedcommand...
i: Skipping execution of extendedcommand. file not found...
i: Can't partition non-vfat: datamedia
i: Can't partition unsafe device: /dev/black/mmcblk1p1
i: Can't format unknown volume: /emmc
So, that's everything it says on the screen in the exact order, spacing and lettering. Does any of this mean anything to anybody? I don't know what to make of it....I'm not real into this kinda thing, other then being able to know how to flash new ROMS and root my phone. I would reflash the stock firmware, try and relock the bootloader and send it in for repair, but I know they'll know I was into it. If someone could PLEASE help me, I'd GREATLY appreciate it!

I didn't see you mention it...
Did you factory reset in recovery?

arrrghhh said:
I didn't see you mention it...
Did you factory reset in recovery?
Click to expand...
Click to collapse
Yes, a few times. Also did Dalvik
EDIT: I just found this, but I'm not sure if it's what I'm looking for: http://forum.xda-developers.com/showthread.php?t=2295643
I noticed it has emmc files in it. Could it help? They mention you need TWRP, but I can't use it. The touchscreen is still unresponsive.

StarlitSnowWolf said:
Yes, a few times. Also did Dalvik
Click to expand...
Click to collapse
Hm. You might have to RSD back to stock

arrrghhh said:
Hm. You might have to RSD back to stock
Click to expand...
Click to collapse
I mentioned in my first post I flashed stock ICS with RSD, but still no change

StarlitSnowWolf said:
I mentioned in my first post I flashed stock ICS with RSD, but still no change
Click to expand...
Click to collapse
Was the flash successful? Did you try JB? Do you have any logs? Does adb start up even?

arrrghhh said:
Was the flash successful? Did you try JB? Do you have any logs? Does adb start up even?
Click to expand...
Click to collapse
Flash seemed successful, currently downloading 4.1.2 stock ROM to flash, only log I know of is the one I described in first post, and I'm not sure what you mean by the ADB. Fastboot works

StarlitSnowWolf said:
Flash seemed successful, currently downloading 4.1.2 stock ROM to flash, only log I know of is the one I described in first post, and I'm not sure what you mean by the ADB. Fastboot works
Click to expand...
Click to collapse
When your phone is "bootlooping" see if the computer can "see" the phone - adb devices typically.

arrrghhh said:
When your phone is "bootlooping" see if the computer can "see" the phone - adb devices typically.
Click to expand...
Click to collapse
How would one do that? The computer makes it "ding" sound like it does when a device is connected to a USB port and RSD Lite will show it if it's in fastboot mode

StarlitSnowWolf said:
How would one do that? The computer makes it "ding" sound like it does when a device is connected to a USB port and RSD Lite will show it if it's in fastboot mode
Click to expand...
Click to collapse
Just like fastboot devices, adb devices from command prompt.

arrrghhh said:
Just like fastboot devices, adb devices from command prompt.
Click to expand...
Click to collapse
I'm pretty sure the ADB works. I'm able to flash recoveries with it and do the "fastboot devices" and it shows up

StarlitSnowWolf said:
I'm pretty sure the ADB works. I'm able to flash recoveries with it and do the "fastboot devices" and it shows up
Click to expand...
Click to collapse
Then use adb to pull logs when you say the device is booting.......

So, how do I do that? I don't know how to pull logs during boot, or do I do it in fastboot mode?

Bump....I left it on the charger all night long and at some point, it booted into Android, but I wasn't able to do anything. Screen was on "Hands Free Activation" and said something about a failure ota_apn. No touch response whatsoever, so I powered it back off and it's boot looping again. Can someone PLEASE help me!?!? I posted a log for CWM when I had it installed, so does any of it mean anything!?

StarlitSnowWolf said:
So, how do I do that? I don't know how to pull logs during boot, or do I do it in fastboot mode?
Click to expand...
Click to collapse
adb logcat

So, when would I want to run that? In fastboot or while the phone is trying to boot?

StarlitSnowWolf said:
So, when would I want to run that? In fastboot or while the phone is trying to boot?
Click to expand...
Click to collapse
While the phone is trying to boot... I need a log from the bootloop failure.

arrrghhh said:
While the phone is trying to boot... I need a log from the bootloop failure.
Click to expand...
Click to collapse
I just got home from dropping it off at a repair shop. If I'd known about getting the log sooner, I would've.

Oneplus 6 stuck in fastboot mode

Hello everybody,
I was glad to receive my OnePlus 6 3 days ago. But this morning, the phone rebooted itself and I am now stuck into fastboot mode.
So just to be clear, I already tried the following things :
- Rebooting into system by pressing "Power" while fastboot mode is selected on "START"
- Rebooting into system by using fastboot.exe utility "fastboot.exe reboot"
- Rebooting into recovery by selecting the option in fastboot menu and pressing "Power"
- Trying to unlock the bootloader by using fastboot.exe utility "fastboot.exe oem unlock" (Can't do it since I didn't turn on the option in Developer Settings)
At this point, my phone is just a brick rebooting into fastboot and I'm thinking about sending the device back to OP. Would someone have an idea what could I do to boot the phone or at least access the recovery ?
Thanks.

Is it still stock? Have you done anything to it? If you haven't unlocked it, I don't think the unbrick tools will work for you, and you should contact OP.
You might give this a try: https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051

Have you looked into this: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665

iElvis said:
Is it still stock? Have you done anything to it? If you haven't unlocked it, I don't think the unbrick tools will work for you, and you should contact OP.
You might give this a try: https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Click to expand...
Click to collapse
Hi, Thanks for your reply. I didn't do anything to the phone. It was 100% stock. I'm now trying some tools I can found on xda but with no luck :/
I'm gonna try the tool you linked right now. Will keep updated.

Gr8man001 said:
Have you looked into this: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Click to expand...
Click to collapse
That tool requires an unlocked bootloader, which the OP does not have.

Gr8man001 said:
Have you looked into this: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Click to expand...
Click to collapse
Thanks for your reply.
Yes I tried it like 15 min ago, and I get an error because my bootloader is locked ... I can't unlock because it has to be done in the system.

So, if you don't mind losing your personal data on the internal storage, you might try unlocking the bootloader. This will wipe the internal storage. I had an issue where I was caught in a bootloop and I locked and then unlocked the bootloader and it got me out of the bootloop.
If you are stuck in fastboot, you should be able to unlock the bootloader via adb cmd line from your computer. I believe it's "fastboot oem unlock".

azsl1326 said:
So, if you don't mind losing your personal data on the internal storage, you might try unlocking the bootloader. This will wipe the internal storage. I had an issue where I was caught in a bootloop and I locked and then unlocked the bootloader and it got me out of the bootloop.
If you are stuck in fastboot, you should be able to unlock the bootloader via adb cmd line from your computer. I believe it's "fastboot oem unlock".
Click to expand...
Click to collapse
Thanks for you reply.
Unfortunately, the bootloader can't be unlocked. I have to check "OEM UNLOCK" in developer settings and since and I can't boot into the system ...

Krysou said:
Thanks for you reply.
Unfortunately, the bootloader can't be unlocked. I have to check "OEM UNLOCK" in developer settings and since and I can't boot into the system ...
Click to expand...
Click to collapse
Forgot about that setting...sorry. You might try and give OP Support a call. I have heard that they can remote into your phone and resolve issues like this one.

I am NOT an expert and there are smarter folks on this site who can explain. I had a similar issue with one of my previous phones and someone had suggested to turn off the phone (if you can otherwise just try it in fastboot mode) and hold BOTH volume up and down buttons while pressing the power button (keep it pressed for a good minute or so) and I was able to boot into "limited" OS (I think it's called safe mode or something). Not saying that it will fix the issue but may be worth the try. Just trying to help. Good luck.

Gr8man001 said:
I am NOT an expert and there are smarter folks on this site who can explain. I had a similar issue with one of my previous phones and someone had suggested to turn off the phone (if you can otherwise just try it in fastboot mode) and hold BOTH volume up and down buttons while pressing the power button (keep it pressed for a good minute or so) and I was able to boot into "limited" OS (I think it's called safe mode or something). Not saying that it will fix the issue but may be worth the try. Just trying to help. Good luck.
Click to expand...
Click to collapse
Thanks for your suggestion. Unfortunately, the device reboots into fast boot each time again and again.

time to call OnePlus and have them do a remote session to restore ur phone, get a keylogger and get the passcode for the zip for us lol

Ok guys, good news. I succesfully reseted the phone thanks to MsmDownload Tool.
The link provided by iElvis helped me identify which tool should I search. After downloading the .rar file from the link, I got an error when launching the program. I then searched another version of it and found :
https://www.******.com/unbrick-oneplus-6-using-msmdownload-tool/
This one worked perfectly. I am really happy it works again. I would like to understand what happend but whatever, let's hope it does not happen again.
Thank you all for your suggestions.

Krysou said:
Ok guys, good news. I succesfully reseted the phone thanks to MsmDownload Tool.
The link provided by iElvis helped me identify which tool should I search. After downloading the .rar file from the link, I got an error when launching the program. I then searched another version of it and found :
https://www.******.com/unbrick-oneplus-6-using-msmdownload-tool/
This one worked perfectly. I am really happy it works again. I would like to understand what happend but whatever, let's hope it does not happen again.
Thank you all for your suggestions.
Click to expand...
Click to collapse
can you give a download link of that tool and some simple instruction, please.

jkyoho said:
can you give a download link of that tool and some simple instruction, please.
Click to expand...
Click to collapse
Hello,
https://www[.]berga-tech[.]com/2018/05/how-to-guide-unbrick-oneplus-6-using.html?m=1
You will find all instructions and download link there.

Return
Krysou said:
Thanks for your reply.
Yes I tried it like 15 min ago, and I get an error because my bootloader is locked ... I can't unlock because it has to be done in the system.
Click to expand...
Click to collapse
Unfortunately sounds like you may have to return the phone. (that sucks)

https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
try the OOS5.1.5 MDMtool from link above. It works for me.
And if you unable to go to qualcomm 9008 mode from fastboot, try connect to pc with cable ,and press and hold power& vol_up, and wait for the connect sound from computer

Krysou said:
Ok guys, good news. I succesfully reseted the phone thanks to MsmDownload Tool.
The link provided by iElvis helped me identify which tool should I search. After downloading the .rar file from the link, I got an error when launching the program. I then searched another version of it and found :
This one worked perfectly. I am really happy it works again. I would like to understand what happend but whatever, let's hope it does not happen again.
Thank you all for your suggestions.
Click to expand...
Click to collapse
I'm experiencing the exact same issue than you Krysou. Thanks a lot for the solution which gives me a hope ! Could you please tell me if you were able to recover your data (photos / videos) after the unbricking procedure ? I'd like to know it before I run the MsmDownload Tool.
Thanks for your reply

groggy8888 said:
I'm experiencing the exact same issue than you Krysou. Thanks a lot for the solution which gives me a hope ! Could you please tell me if you were able to recover your data (photos / videos) after the unbricking procedure ? I'd like to know it before I run the MsmDownload Tool.
Thanks for your reply
Click to expand...
Click to collapse
OOps men, I'm sorry to answer that late to your question, doing it for the others searching for a solution.
So : You won't recover anything after running MsmDownloadTool. You get a pretty much completely stock phone, like when you got it after unboxing

Krysou said:
Thanks for your suggestion. Unfortunately, the device reboots into fast boot each time again and again.
Click to expand...
Click to collapse
try this metod https://forum.highonandroid.com/t/how-to-unroot-oneplus-6-using-fastboot/33

Bootloop and unable to access fastboot or recovery mode

welcome
I wanted to install twrp for xiaomi redmi 9 global version miui 12.5.1
These were the commands I used:
1 - fastboot flash recovery twrp-3.4.2B-0108.img
2 - fastboot flash misc misc.bin
3 - fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
4 - fastboot boot twrp-3.4.2B-0108.img
After that, the device restarted but MIUI did not start again. "Redmi" appears on the screen for a few seconds then restarts again and again.
And now comes the real problem and also the reason for this post...
I cannot access recovery or fastboot mode!
I can't even turn off the device.
I can't do anything but wait for the battery to run out.
If I hold Power + VolumeUp = It keeps rebooting
If I hold Power + VolumeDown = It keeps rebooting
If I only hold Power = It keeps rebooting
If I hold all of them it stops rebooting and keeps the black screen as if it's off, but when I stop holding, the bootloop starts again.
I don't know what to do, I hope any of you can help me.
Thanks for the attention.

Re-flash Stock ROM to get rid off of all modificatins you applied so far.

jwoegerbauer said:
Re-flash Stock ROM to get rid off of all modificatins you applied so far.
Click to expand...
Click to collapse
Hello
Thanks for the quick reply
Please can you explain how this works?

It's typically done via ADB Sideload method - what of course requires USB Debugging got enabled on phone and you have the Stock ROM in .ZIP-file format on hand.

jwoegerbauer said:
It's typically done via ADB Sideload method - what of course requires USB Debugging got enabled on phone and you have the Stock ROM in .ZIP-file format on hand.
Click to expand...
Click to collapse
I cannot access recovery or fastboot mode!
I can't even turn off the device.
I can't do anything but wait for the battery to run out.

You were told to to use ADB Sideload method: This has nothing to do with Recovery mode or Fastboot mode.

jwoegerbauer said:
You were told to to use ADB Sideload method: This has nothing to do with Recovery mode or Fastboot mode.
Click to expand...
Click to collapse
Sorry to bother you and thank you
But due to my lack of experience in the field, I was unable to find a detailed explanation of the ADB Sideload process that you told me about, could you please explain how this works Steps or send a link with details or a video, please Knowing that the phone does not appear on the computer due to its continuous restart all the time I am sorry again

That's another issue you report now,
My recommendation: Take phone to authorized service center and let them try to fix it.

I already took it to fix it but no result He told me that I have to replace the motherboard and this is wrong because my problem is a problem with the phone system
jwoegerbauer said:
That's another issue you report now,
My recommendation: Take phone to authorized service center and let them try to fix it.
Click to expand...
Click to collapse

hey..I know I'm a whole year late but i have a solution!!!
reply if you still need it

vader404 said:
hey..I know I'm a whole year late but i have a solution!!!
reply if you still need it
Click to expand...
Click to collapse
hello I wanna know how you did it.

vader404 said:
hey..I know I'm a whole year late but i have a solution!!!
reply if you still need it
Click to expand...
Click to collapse
hellow whay is the solution? i got this problem too now, i have experience to unbrick some android phone, but this thing is very rare. Because it repeatedly restarting cant go to fastboot to connect to pc or to recovery mode to reformat. Thank u in advance.