Develop Bugs

accidentally format bootloader

I accidentally formatted bootloader, and now my device unable to detect,boot or anything. Is there anything I can do of ?
(might try everything to work it out )

Can you boot into the preloader with volume up and power pressed?

flash ROM via FlashTool

BlueFlame4 said:
Can you boot into the preloader with volume up and power pressed?
Click to expand...
Click to collapse
no, i could not

Kittehdispenser said:
no, i could not
Click to expand...
Click to collapse
Sounds like a hard brick, which means your phone is destroyed. What exactly did you do?

BlueFlame4 said:
Sounds like a hard brick, which means your phone is destroyed. What exactly did you do?
Click to expand...
Click to collapse
welp, i tried to install custom rom ( which need to download the rar and paste it into INTERNAL) but i accidentally paste it to my SD card. Then i start to install it.
Then i said it's uninstallable, I just restart my phone and everthing went normal buy my wallpaper screen turns black and unable to read it tho USB ( Just the standby screen shows wallpaper)
Then my brothers came out and said that all you need to do is format it again and reinstall. We tired countless times . But then it have another option which above Format everything but not bootloader and another is Format everything and bootloader.
Then my bro press it and ... It became bricked.
it's still warrantyable so .. I plan to play dumb to the warranty company if I can't fix it.
( even if i play dumb idk what reason I need to come off, if i say yesterday the battery from 70% drop to 0% then it unable to open again )
PS: before this happen my battery happens from 70% drop to 0%, after charged. it's fine
PPS: give me a good excuses to play dumb C::

Wait, wait. How did you format the bootloader? No recovery should have this option! The only possible option to hard brick the P8000 is to pull out the USB cable in the exact moment when the SPFlash Tool writes it. So, can you elaborate a bit more about what you've done? I'm pretty sure you're missing something.

Soft Bricked HTC Desire 616
BlueFlame4 said:
Wait, wait. How did you format the bootloader? No recovery should have this option! The only possible option to hard brick the P8000 is to pull out the USB cable in the exact moment when the SPFlash Tool writes it. So, can you elaborate a bit more about what done? I'm pretty sure you're missing something.
Click to expand...
Click to collapse
Hi,
I did something similar with my HTC Desire 616. I choose "Format All + Download" option with SP Flash Tool. The phone soft bricked. Later I tried "format whole flash (including bootloader)". It's still soft bricked...
Is there a way to revive my phone back??? :crying:

I had the same problem - but it is possible to set the phone to a special bootloader mode called META mode - see this video: https://www.youtube.com/watch?v=A3TmXtOA0IA
To do so you have to open the phone and disconnect the battery. You can find a howto easily on youtube.
Then set up everything to flash the phone (SP-Flashtool, scatter file, etc.) and push the volume down button while connecting the phone to the computer. This switches the phone to META mode, the computer can recognize the phone, installs the preloader driver and finally flashes the phone
Maybe you have to do the procedure twice because on the first connection only the preloader driver will be installed.
This worked for my P8000(B) which I treated with SP-Flash Tool and "Format All + download"
Be aware that you formatted the NVRAM and lost your IMEI's

FrauHofrat said:
P8000(B)
Click to expand...
Click to collapse
What the meaning of (B)? Just asking because i have (W)

Tecno spark 3 pro clone flash file mt6570 android 9.0 firmware
Hi
I need your assistance, please help me find the firmware for the above phone. I recently tried to flash it with a Spark 3 clone firmware i got online but it gives an error STATUS_PARTITION_NOT_FOUND and also i accidentally formatted the bootloader on SP Flash Tool so the phone is a brick, it can't charge, and it can't turn on. I have screenshots of the About section when the phone was working, which contains the phone's features model and build but on opening the back cover of the device, i realized its a clone phone and i cannot determine its real model to get the exact right flash file.
Thanks

Boot loop after OTA upgrade

Hi everyone, today my Elephone p8000 with stock rom (no root nor recovery installed) proposed me an OTA update, and I did it.
After installing the update the phone is stuck at the boot animation logo. If I boot in factory mode (volume down + power button) I am presented with a bunch of options in Chinese, which I don't understand. If I go in recovery mode (volume down + power button) it says "no command".
What can I do? What are my options? Is it bricked?

Yup mine too. Mine has root, with no custom recovery. Get the same boot loop and the sad open Android 'no command'.
Haven't had a chance to dig around for a solution but I suspect it is a case of using the flash tool to wipe and load a standard ROM? Hopefully an easier way.

kevvyboy said:
Yup mine too. Mine has root, with no custom recovery. Get the same boot loop and the sad open Android 'no command'.
Haven't had a chance to dig around for a solution but I suspect it is a case of using the flash tool to wipe and load a standard ROM? Hopefully an easier way.
Click to expand...
Click to collapse
Damn. I had huge problems with the flash tool in the past (I don't have a Windows PC) and the idea of spending the weekend trying to get the damn thing work is not a fun one.

Got this issue too this morning on way to work, I guess my phones useless today until I get home to try and flash it.
seem to be able to get to the boot select screen but nothing is different anyway, also managed to get into a "PCBA" mode that did a load of tests to the phone but thats it.

it now just died, not powering on, think its bricked :crying:

skea said:
it now just died, not powering on, think its bricked :crying:
Click to expand...
Click to collapse
Probably just out of power. Try charging it for a while and/or download and flash entire rom using sp flash except for data-partition so as you don't lose your data.

pitrus- said:
Probably just out of power. Try charging it for a while and/or download and flash entire rom using sp flash except for data-partition so as you don't lose your data.
Click to expand...
Click to collapse
thanks it was out of power lol

I just had the same problem. Did you solved it?
Like, exactly the same... Crazy

Another one
My p8000 also in bootloop after ota update. Only have an old vista PC w8ll dust it off tonight and see what happens

mines doing the same i thought it was too good to be true and it was lol

Cannot get pc (win 10) to install all the drivers, PC cannot see the phone so unable to run flash tool.
Suggestions? I presume the ROM cannot be flashed through the recovery (standard)?
EDIT: Driver package installed by disabling 'driver verification' setting in Windows. Phone only recognised as a MTP USB Device in devide manager, and flash tool does not seem to want to do anything. Might try this on a Win 7 laptop tomorrow. HJow you guys getting on with this?

Success - I Have a Working Phone
(or, How Chest Pains and Rage Focused the Mind)
So. This is what worked for me. Win 10. P8000 bootloop.
1) put p8000 into recovery, chose 'power off'. (I couldn't seem to stop it rebooting using the power button)
2) installed driver pack by disabling the Windows install signed drivers only setting. Rebooted. This turns the setting back on, but the drivers have alrwady been installed, no issue with that.
3) installed the flash tool. Brief panic at Chinese chars, located English. Calmed down.
4) loaded flash tool, with ROM ready to go.
5) this is the biggie, this is what brought it all together.........connected the powered down p8000 via USB and IMMEDIATELY hit the download button in the flash tool - ie BEFORE a new instance of USB bing-bong-device-connected sound.
6) once all downloaded, disconnect phone, reboot. Took an extended time (few mins) to boot, enough time to almost start swearing under my breath, but it just needed some patience.
Now, what I spent some time unsuccessfully trying to fix - needlessly as it turns out - was what my phone appeared under 'Device Manager'. It still lists it as an MTP USB Device under the 'Portable Devices' submenu. It did not seem to matter, as long as all the driver were installed.
I wish you all the best of luck in solving your issues, hopefully some of what I wrote can be helpful.

pitrus- said:
download and flash entire rom using sp flash except for data-partition so as you don't lose your data.
Click to expand...
Click to collapse
I have the same boot loop after ota. I did no backup before, so data partition contains my apps right ?
I never used the flash tool , where should I start , any good link for beginners ?
I read some things about the flash options months ago, must I disable/uncheck some options ?
Thanks for help.

same issue
Hi everyone!
I've got the same issue: I allowed the OTA update to 20151105 firmware release from previous version (20150725), after the upgrade, the phone keeps in a bootloop with a new colored Elephone logo.
I can't find a valid set of drivers, I tried a lot over the night, but windows don't recognize the phone.
PLEASE some kind soul could link a valid driver package to use SP tool ?
thanks a lot in advance!
mr..speed said:
I have the same boot loop after ota. I did no backup before, so data partition contains my apps right ?
I never used the flash tool , where should I start , any good link for beginners ?
I read some things about the flash options months ago, must I disable/uncheck some options ?
Thanks for help.
Click to expand...
Click to collapse
kevvyboy said:
Success - I Have a Working Phone
(or, How Chest Pains and Rage Focused the Mind)
So. This is what worked for me. Win 10. P8000 bootloop.
1) put p8000 into recovery, chose 'power off'. (I couldn't seem to stop it rebooting using the power button)
2) installed driver pack by disabling the Windows install signed drivers only setting. Rebooted. This turns the setting back on, but the drivers have alrwady been installed, no issue with that.
3) installed the flash tool. Brief panic at Chinese chars, located English. Calmed down.
4) loaded flash tool, with ROM ready to go.
5) this is the biggie, this is what brought it all together.........connected the powered down p8000 via USB and IMMEDIATELY hit the download button in the flash tool - ie BEFORE a new instance of USB bing-bong-device-connected sound.
6) once all downloaded, disconnect phone, reboot. Took an extended time (few mins) to boot, enough time to almost start swearing under my breath, but it just needed some patience.
Now, what I spent some time unsuccessfully trying to fix - needlessly as it turns out - was what my phone appeared under 'Device Manager'. It still lists it as an MTP USB Device under the 'Portable Devices' submenu. It did not seem to matter, as long as all the driver were installed.
I wish you all the best of luck in solving your issues, hopefully some of what I wrote can be helpful.
Click to expand...
Click to collapse

kevvyboy said:
Success - I Have a Working Phone
(or, How Chest Pains and Rage Focused the Mind)
So. This is what worked for me. Win 10. P8000 bootloop.
1) put p8000 into recovery, chose 'power off'. (I couldn't seem to stop it rebooting using the power button)
2) installed driver pack by disabling the Windows install signed drivers only setting. Rebooted. This turns the setting back on, but the drivers have alrwady been installed, no issue with that.
3) installed the flash tool. Brief panic at Chinese chars, located English. Calmed down.
4) loaded flash tool, with ROM ready to go.
5) this is the biggie, this is what brought it all together.........connected the powered down p8000 via USB and IMMEDIATELY hit the download button in the flash tool - ie BEFORE a new instance of USB bing-bong-device-connected sound.
6) once all downloaded, disconnect phone, reboot. Took an extended time (few mins) to boot, enough time to almost start swearing under my breath, but it just needed some patience.
Now, what I spent some time unsuccessfully trying to fix - needlessly as it turns out - was what my phone appeared under 'Device Manager'. It still lists it as an MTP USB Device under the 'Portable Devices' submenu. It did not seem to matter, as long as all the driver were installed.
I wish you all the best of luck in solving your issues, hopefully some of what I wrote can be helpful.
Click to expand...
Click to collapse
pretty much did the same thing and it worked!! Cheers!! (also had the rage and it took ages to find english on the tool lol :laugh: )

when you get the android with the "no command" message, let go of the volume and power buttons. Then hold the POWER BUTTON for 1-2 seconds and TAP VOLUME UP while still holding the power button. this will open the recovery options

omg!!
disabling the Windows install signed drivers only setting!!
i thought we wouldnt have to do things like this since Windows 95
Lol

Worked for me
Had I only found this tutorial before yesterday... it took me hours to figure this out.
I can, however, now confirm this works.
Regarding point 5):
(i) Power down phone (ii) start flash tool/go to download tab (iii) select scatter file (iv) hit "download" with no phone attached (v) attach the powered down phone
...and things will be fine. Doing anything fast is not required.
The point is to install SP_Drivers_v2.0 first, as described here. After this, everything goes smooth.
kevvyboy said:
Success - I Have a Working Phone
(or, How Chest Pains and Rage Focused the Mind)
So. This is what worked for me. Win 10. P8000 bootloop.
1) put p8000 into recovery, chose 'power off'. (I couldn't seem to stop it rebooting using the power button)
2) installed driver pack by disabling the Windows install signed drivers only setting. Rebooted. This turns the setting back on, but the drivers have alrwady been installed, no issue with that.
3) installed the flash tool. Brief panic at Chinese chars, located English. Calmed down.
4) loaded flash tool, with ROM ready to go.
5) this is the biggie, this is what brought it all together.........connected the powered down p8000 via USB and IMMEDIATELY hit the download button in the flash tool - ie BEFORE a new instance of USB bing-bong-device-connected sound.
6) once all downloaded, disconnect phone, reboot. Took an extended time (few mins) to boot, enough time to almost start swearing under my breath, but it just needed some patience.
Now, what I spent some time unsuccessfully trying to fix - needlessly as it turns out - was what my phone appeared under 'Device Manager'. It still lists it as an MTP USB Device under the 'Portable Devices' submenu. It did not seem to matter, as long as all the driver were installed.
I wish you all the best of luck in solving your issues, hopefully some of what I wrote can be helpful.
Click to expand...
Click to collapse

What if no Windows?
Edit: Never mind, I got myself a windows computer and succeeded. Thanks for all the orientation!
Hi all,
Thanks a lot for posting a solution to this problem so quickly. I am affected by the same issue. Looking to buy some LSD to better enjoy the psychtrip my phone seems to be stuck in. Also looking to fix the phone.
Unfortunately, I'm running Ubuntu 14.04 LTS. I did find a guide to use the flash tool on Ubuntu, but my phone does not seem to connect. I'm guessing this has something to do with that pack of drivers 2.0, for which I have no equivalent. I would really appreciate any ideas!
I might end up returning my phone to Amazon, though. It's only been a few days since I've had it, and you can imagine that although I was really liking it, I'm beginning to change my mind.
Your advice?
EDIT: I am getting the following error message:
BROM ERROR: S_COM_PORT_OPEN_FAIL (1013)
[COM]: Failed to open COM port.
[HINT]:
I did some googling, but didn't find anything worth mentioning.

yslsl said:
Had I only found this tutorial before yesterday... it took me hours to figure this out.
I can, however, now confirm this works.
Regarding point 5):
(i) Power down phone (ii) start flash tool/go to download tab (iii) select scatter file (iv) hit "download" with no phone attached (v) attach the powered down phone
...and things will be fine. Doing anything fast is not required.
The point is to install SP_Drivers_v2.0 first, as described here. After this, everything goes smooth.
Click to expand...
Click to collapse
Ahh good stuff. Connect phone last after hitting download - thanks for the heads up. Got my wife's p8000 today so will be doing some flashing later.
Cheers!

Oneplus 3 just died out of no where

So i was using my phone and decided to restart it after updating my adaway files but my phone never turned back on. The two press the power button screens did not show up either. I tried to uses the MSMdownload tool since i thought my phone was somehow bricked but that didnt work either, it just kept restarting the download process after everything was completed. my computer makes a sound when its connected and it connects correctly as a quallcomm 9008 device but even after all this nothing is working. has anyone experienced something like this or does anyone have any advice?

did you try to long press both power button and vol up ...you should feel a vibration...
maybe it's not turned of maybe it's error causing the screen to be off... also is there any heat?

Which method of the unbrick tool did you use? First or second? If the first, then maybe you should give the second also a try.
Sent from my ONEPLUS A3003 using Tapatalk

I've tried everything and I used th me second method yet nothing happened. I can see my phone get recognized by the computer and get listed on the MSN device list yet nothing happens after it finishes the process. After the green line shows up telling me that it's completed everything the process restarts writhing a few minutes unless I unplug it. No vibration no nothing the phone just died on me after I restarted it .

Try doing MSM on a different PC with all drivers installed , hope it helps

Try to repeat flashing again, there is no other way. Use method 2only. Extract tool again and try flash.

When I was used Xperia Z1, I bricked my phone with a soft brick. So I installed driver in my PC and flash Kernel though FASTBOOT(ADB) either it's not show Device in my PC (I show just "Unknown Device").
After that my phone can connect to my PC again (Now It shown C9303 or something that meant it know it's a phone).
So I can flash by Flashtools again. Soft brick is not scary as Hard brick, you'll find some way to bring it back easily.
Hope this help!
PS. Bricked Phone is WEAK in Battery, always connect it with charger.

Question Bricked my Prixel 6 after flashing stock rom

Hi there,
I am looking for some guidance on my bricked Pixel 6 Pro.
I transfered the data from my old pixel, but then decided to do a full flash to refresh. Downloaded the stock image from google, used the fastboot-all script to flash the phone, but as soon as it was done, I never reboot. my phone is looking completely dead since.
Attempt # 1
- black screen, with no sound to any actions of response to any key combination (power or volume keys).
- tried holding the power button for 60 secs, no response
- tried holding power and volume down, no response
- tried holding power and volume up, no response
- when I plug the phone on charge, no response. neither the charging display.
Atempt # 2
- Only time the phone shows some sign of life, is when I connect the phone to my PC, it makes a sound of detecting a device, but then instantly it get a disconnect sound, (in 2-3 sec).
- I tried holding the power button, while plugged in. it makes a sound of usb detection, (but no visual response on the phone) after holder for 30 secs, it makes another sound of usb detach.
- While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone.
Not sure, if I have bricked the bootloader, and if yes, what can be done? Any guidance in this regards will be highly appreciated.
Thanks

Call whoever you bought the phone from and do warranty claim.

I struggled with a soft bricked / bootlooping phone after removing Magisk. Although my phone at least booted to bootloader and a connection via fastboot was working, the factory images wouldn't flash properly. Google support couldn't help me and I thought I had to send it to repair.
In the end I could solve the issue by switching to the Android SDK 31. I know your case is different, because your phone is bricked worse than mine was, but you could give it a try.

Baumhouse said:
I struggled with a soft bricked / bootlooping phone after removing Magisk. Although my phone at least booted to bootloader and a connection via fastboot was working, the factory images wouldn't flash properly. Google support couldn't help me and I thought I had to send it to repair.
In the end I could solve the issue by switching to the Android SDK 31. I know your case is different, because your phone is bricked worse than mine was, but you could give it a try.
Click to expand...
Click to collapse
rao_hamza said:
Hi there,
I am looking for some guidance on my bricked Pixel 6 Pro.
I transfered the data from my old pixel, but then decided to do a full flash to refresh. Downloaded the stock image from google, used the fastboot-all script to flash the phone, but as soon as it was done, I never reboot. my phone is looking completely dead since.
Attempt # 1
- black screen, with no sound to any actions of response to any key combination (power or volume keys).
- tried holding the power button for 60 secs, no response
- tried holding power and volume down, no response
- tried holding power and volume up, no response
- when I plug the phone on charge, no response. neither the charging display.
Atempt # 2
- Only time the phone shows some sign of life, is when I connect the phone to my PC, it makes a sound of detecting a device, but then instantly it get a disconnect sound, (in 2-3 sec).
- I tried holding the power button, while plugged in. it makes a sound of usb detection, (but no visual response on the phone) after holder for 30 secs, it makes another sound of usb detach.
- While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone.
Not sure, if I have bricked the bootloader, and if yes, what can be done? Any guidance in this regards will be highly appreciated.
Thanks
Click to expand...
Click to collapse
rao_hamza said:
Hi there,
I am looking for some guidance on my bricked Pixel 6 Pro.
I transfered the data from my old pixel, but then decided to do a full flash to refresh. Downloaded the stock image from google, used the fastboot-all script to flash the phone, but as soon as it was done, I never reboot. my phone is looking completely dead since.
Attempt # 1
- black screen, with no sound to any actions of response to any key combination (power or volume keys).
- tried holding the power button for 60 secs, no response
- tried holding power and volume down, no response
- tried holding power and volume up, no response
- when I plug the phone on charge, no response. neither the charging display.
Atempt # 2
- Only time the phone shows some sign of life, is when I connect the phone to my PC, it makes a sound of detecting a device, but then instantly it get a disconnect sound, (in 2-3 sec).
- I tried holding the power button, while plugged in. it makes a sound of usb detection, (but no visual response on the phone) after holder for 30 secs, it makes another sound of usb detach.
- While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone.
Not sure, if I have bricked the bootloader, and if yes, what can be done? Any guidance in this regards will be highly appreciated.
Thanks
Click to expand...
Click to collapse
Bootloader unlocked?

cultofluna said:
Bootloader unlocked?
Click to expand...
Click to collapse
If I remeber correctly flashing factory images forces you to unlock the device. So yes, the bootloader of rao_hamza's device should be unlocked.

From memory you can revive it through QPST and orher Qualcomm utilities, however hard part is to get the files. the phone is too new and many shops dont have the unlock tools yet.
" While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone. " - this is still good news, as phone is being detected by windows, try to install Qualcomm drivers and see if you can get it to boot into EDL. GOOD LUCK.

Pixel 6 uses Google's own new Tensor chip - so no Qualcomm tools

Like @Baumhouse I went through something similar. Two things for me: it took way longer to hold power and volume down than any other phone I've owned. I was seriously concerned I wasn't going to get there. Two, the factory images all made it to fastbootd and then failed all because I hadn't updated to the latest SDK.
Just throwing this out in hopes you don't have to send it back.

What @ridobe said. Make sure you're using the latest official Google Platform Tools (there's a link in my thread at the top of my signature below if you need it, or just Google for it). If I had a nickel every time someone didn't update the tools when they went to use them...

roirraW edor ehT said:
What @ridobe said. Make sure you're using the latest official Google Platform Tools (there's a link in my thread at the top of my signature below if you need it, or just Google for it). If I had a nickel every time someone didn't update the tools when they went to use them...
Click to expand...
Click to collapse
This and a bad/wrong cable seem to be the most common culprits

ridobe said:
Like @Baumhouse I went through something similar. Two things for me: it took way longer to hold power and volume down than any other phone I've owned. I was seriously concerned I wasn't going to get there. Two, the factory images all made it to fastbootd and then failed all because I hadn't updated to the latest SDK.
Just throwing this out in hopes you don't have to send it back.
Click to expand...
Click to collapse
Any idea how long you had to hold that button combinaiton? I tried longer, maybe 60 sec, but still no response from the phone.
tids2k said:
From memory you can revive it through QPST and orher Qualcomm utilities, however hard part is to get the files. the phone is too new and many shops dont have the unlock tools yet.
" While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone. " - this is still good news, as phone is being detected by windows, try to install Qualcomm drivers and see if you can get it to boot into EDL. GOOD LUCK.
Click to expand...
Click to collapse
What is EDL? and had the Google usb drivers installed, to get the fastboot working.
Baumhouse said:
I struggled with a soft bricked / bootlooping phone after removing Magisk. Although my phone at least booted to bootloader and a connection via fastboot was working, the factory images wouldn't flash properly. Google support couldn't help me and I thought I had to send it to repair.
In the end I could solve the issue by switching to the Android SDK 31. I know your case is different, because your phone is bricked worse than mine was, but you could give it a try.
Click to expand...
Click to collapse
Yes, I don't know who to get into a bootloader in this situation, if that were working I would have some hope.

If you can get to the bootloader you can use google's flashing website, flash.android.com. I just use that to go back to stock, even with an unlocked bootloader.

pysklona said:
If you can get to the bootloader you can use google's flashing website, flash.android.com. I just use that to go back to stock, even with an unlocked bootloader.
Click to expand...
Click to collapse
Thanks @pysklona. you are right, but the problem is I can't get into the bootloader. This is what I am seeking help for.

rao_hamza said:
Thanks @pysklona. you are right, but the problem is I can't get into the bootloader. This is what I am seeking help for.
Click to expand...
Click to collapse
Sorry, misread the post.

@pysklona came here because I'm in the same boat, hard-bricked my device after running the flash-all script. Was using the most recent version of platform tools and the brand new cable that came with the phone.
Was getting the same result, attaching it to a windows pc makes the attached device chime, but disconnects after a few seconds. It came up first as "Setting up Pixel ROM Recovery". I let it sit overnight and now it doesn't auto-disconnect and I get a serial device under com3 on windows. Attaching it to macos gives me a "Pixel ROM Recovery" device. Despite "recovery" in the name, I think it's actually in EDL mode, not recovery mode. No devices come up for adb or fastboot on windows, linux or macos. Screen is completely blank no matter what.
Not being a Qualcomm chip makes this whole process from here a bit of an unknown, but will assume the process for recovery is more or less the same. Looking into QPST/MsmDownloadTool/OpenPST, although as pointed out, I'm not sure any of those tools will work since this isn't a qualcomm chip. MsmDownloadTool is for oneplus, but maybe something can be modded.

ootri said:
@pysklona came here because I'm in the same boat, hard-bricked my device after running the flash-all script. Was using the most recent version of platform tools and the brand new cable that came with the phone.
Was getting the same result, attaching it to a windows pc makes the attached device chime, but disconnects after a few seconds. It came up first as "Setting up Pixel ROM Recovery". I let it sit overnight and now it doesn't auto-disconnect and I get a serial device under com3 on windows. Attaching it to macos gives me a "Pixel ROM Recovery" device. Despite "recovery" in the name, I think it's actually in EDL mode, not recovery mode. No devices come up for adb or fastboot on windows, linux or macos. Screen is completely blank no matter what.
Not being a Qualcomm chip makes this whole process from here a bit of an unknown, but will assume the process for recovery is more or less the same. Looking into QPST/MsmDownloadTool/OpenPST, although as pointed out, I'm not sure any of those tools will work since this isn't a qualcomm chip. MsmDownloadTool is for oneplus, but maybe something can be modded.
Click to expand...
Click to collapse
Thanks for sharing your experience. I just returned the device and got myself a new one.
anyways, i am not sure what is causing this hard brick. thats is something we all should be careful about it.

same thing here. pixel 6 from google store. magisk installed on the december update and i downgraded to the november one using the flash-all.bat script. phone reboots and am told the software is corrupt
reboot back into fastboot mode, run the script again. and get this software is corrupt message again
this time I cant' even boot into fastboot/bootloader mode. and plugging the phone into windows gives me the "pixel rom recovery" message
phone seems dead (black screen, not responding to hardware buttons)
any other solutions than to get it replaced?

Hmm, maybe plug it in to a PC via USB to supply it with power (maybe the battery is down) and just do a very long press of the power button - at least 30 seconds - until the phone starts up. If it does and isn't in fastboot you could try "Power-VolDown" to get into fastboot...
If it just doesn't react to all of this and waiting a bit (in case the battery was at 0% and needs some minimal charge) I think a replacement is the only way to go....

Enddo said:
same thing here. pixel 6 from google store. magisk installed on the december update and i downgraded to the november one using the flash-all.bat script. phone reboots and am told the software is corrupt
reboot back into fastboot mode, run the script again. and get this software is corrupt message again
this time I cant' even boot into fastboot/bootloader mode. and plugging the phone into windows gives me the "pixel rom recovery" message
phone seems dead (black screen, not responding to hardware buttons)
any other solutions than to get it replaced?
Click to expand...
Click to collapse
You could try Official Google Android Flash Tool. It's merely another method of doing what you effectively tried, but from what I've read, it's helped some folks. Sadly, others have reported that the Official Google Pixel Update and Software Repair hasn't been updated for the P6P yet.
If that doesn't help, hang in there. There are others in here who will likely have even better advice.

roirraW edor ehT said:
You could try Official Google Android Flash Tool. It's merely another method of doing what you effectively tried, but from what I've read, it's helped some folks. Sadly, others have reported that the Official Google Pixel Update and Software Repair hasn't been updated for the P6P yet.
If that doesn't help, hang in there. There are others in here who will likely have even better advice.
Click to expand...
Click to collapse
appreciate the links. right now, I can't even get into fastboot/bootloader mode. so neither of those tools detect the phone.
@s3axel the battery definitely isn't low. I charged it up before all this specifically so that I know it had plenty of juice (was at 93% or something).
I'm thinking maybe after letting the battery die, charging it back up will let me boot into a special boot mode
but any other ideas, please, I'm all ears

Question Oppo Reno 6 5G (PEQM00) bricked

Hello
I need help here I have tried everything to fix my oppo reno 6 5g chinese version and now I am at a dead end can anybody give any suggestion.?
My phone is on black screen and its showing only for 2 second on device manager as some other version which made mtkclient tool to failed handshake and sp flash tool to give error.
like attached screen shots.
In device manager it is showing as V_1632 which is idk what.
I tried all combination but phone is at black screen now.
Device is not going into BROM mode.
Any help will be much appreciated.

hmmm, at least you didn't flash the wrong preloader, so we can save this pretty easily actually.
Just simply follow this guide:
Download VCOM drivers: Mega Link
Install LibUSB and filter your device driver after connecting it through USB while pressing on both vol + and vol - buttons.
Install Python and install it's requirements using the command `pip install pyusb pyserial json5` in CMD.
Extract MTK bypass util anywhere and run the command `python main.py` in the extracted folder through CMD while your device is connected (KEEP HOLDING VOL + AND VOL - DURING THE BYPASSING!!!).
Open SP and flash the scatter file of your stock ROM (PLEASE ONLY FLASH YOUR STOCK ROM) (ONLY USE DOWNLOAD MODE).
Then reboot your device and it should work.
If you face any issue or don't know how to do a step of those just reply to the thread. I'll try to attach some pictures, just be aware I'm only online at about this time.

XDHx86 said:
hmmm, at least you didn't flash the wrong preloader, so we can save this pretty easily actually.
Just simply follow this guide:
Download VCOM drivers: Mega Link
Install LibUSB and filter your device driver after connecting it through USB while pressing on both vol + and vol - buttons.
Install Python and install it's requirements using the command `pip install pyusb pyserial json5` in CMD.
Extract MTK bypass util anywhere and run the command `python main.py` in the extracted folder through CMD while your device is connected (KEEP HOLDING VOL + AND VOL - DURING THE BYPASSING!!!).
Open SP and flash the scatter file of your stock ROM (PLEASE ONLY FLASH YOUR STOCK ROM) (ONLY USE DOWNLOAD MODE).
Then reboot your device and it should work.
If you face any issue or don't know how to do a step of those just reply to the thread. I'll try to attach some pictures, just be aware I'm only online at about this time.
Click to expand...
Click to collapse
I did everything like you described step by step first 3 steps were installations so that went ok but in step 4 I followed your instructions but nothing happend.
I pressed VOL up+VOL down buttons but nothing happend for long time.
Here is screen shot of CMD
I think preloader is damaged or something because not its not going in BROM mode at all only black screen.
If i press VOL up+VOL down+PWR buttons then in device manager phone is shown as I shared screenshot in post but only for like 2 seconds.
like this
Also in SP flash tool detects the phone but when I hit the downlad button it gives error STATUS_ERR instantly not even start the process.

Most likely you didn't use LibUSB right, just open the app connect the device and when you see it in the list of devices highlight it and press install

XDHx86 said:
Most likely you didn't use LibUSB right, just open the app connect the device and when you see it in the list of devices highlight it and press install
Click to expand...
Click to collapse
I did exactly what you said but the problem is phone is like not responding to VOL+andVOL- buttons command, in LibUsb where it says waiting for devicec i pressed both volume buttons and connect and waited for 1 minute atleast but nothing attached screenshot for rfrence. its just empty.
But when i press all HW buttons then LibUsb shows a device then I select it and install and completes it but thats the problem it only shows for 2 second then gone.
like this
what should i do now?

I think you fried the preloader mate, you need to do a test point connection and force the device to connect to the cpu directly.
If you're unsure how to do that please send your device to a professional instead.

XDHx86 said:
I think you fried the preloader mate, you need to do a test point connection and force the device to connect to the cpu directly.
If you're unsure how to do that please send your device to a professional instead.
Click to expand...
Click to collapse
yeah im not sure how to do that. I think too much flashing may have resulted in that.
Thank you for your help.
but in case if they didnt take it then im afraid im gonna have to try that is there any tool or process or help where i can learn more abt this test connection process?

mamomia said:
yeah im not sure how to do that. I think too much flashing may have resulted in that.
Thank you for your help.
but in case if they didnt take it then im afraid im gonna have to try that is there any tool or process or help where i can learn more abt this test connection process?
Click to expand...
Click to collapse
It's device specific so I'll need to look into it and reply to you, but generally speaking you're going to connect a USB to the device through specific CPU pins on the motherboard.

XDHx86 said:
It's device specific so I'll need to look into it and reply to you, but generally speaking you're going to connect a USB to the device through specific CPU pins on the motherboard.
Click to expand...
Click to collapse
Oh it means I need to open up the phone.
That will be the problem because I dont have the tools to do that.
I guess first I have to try and find some professional then.