Related
Sent from my Nexus 7 using Tapatalk 2
My N4 is from PlayStore USA, and I live outside of US. A few days ago I did a stupid mistake and flashed a wrong bootloader (please don't ask why - the embarrassment still hurts! ). The N4 is now totally dead - cannot be turned on, and won't boot no matter which sets of buttons I hold down.
I have been searching the net for solutions but have not found any simple enough (for me) solution. I read of several similar cases and the solution has been to send back to Google/LG. As I live outside of US, this isn't much of an option. I have also read about use of Gtag to unbrick devices but this is beyond my capability and this service is also not available in my country. Sending the N4 to my local LG service centre for repairs (there's no International warranty) is a last resort but I am not sure whether they have tbe tools and knowhow to unbrick my N4. They may not even want to get involved!
So I am writing in this forum to ask for help. Any advice will be appreciated. Thanks in advance.
Why the hell would you even flash the bootloader manually?
Anyway, there was a thread recently about Qualcomm's debugging mode. However, you'll need the appropriate drivers and most likely other software for it to work.
I don't know if anyone actually got it working, though
I dont know why I did it too - just following wrong instructions ; out of sheer stupidity!
Sent from my Nexus 7 using Tapatalk 2
download the quacomm usb high speed drivers and install them you might have to do have disk to install them in device manager. then doqnload the QPST qualcomm tool. this will allow you to flash phone images and other files here. It should pick your phone up in download state. Only problem now is that the Qualcomm tool only allows hex image files to be flashed. this is where i was stuck
Thanks for the qualcomm suggestion. I will look through it when I return to my home country in a week`s time. But from what you have described, the procedure seems too complex for me. I am also following the other `bricked Nexus 4` thread in this section which I was not aware of till yesterday. All indications are that my bricked Nexus 4 will be a total loss - LG in my country has told me that they will not touch my unit until Nexus 4 is officially launched in my country (that could be a couple of months away), and returning the unit back to Google USA will be extremely difficult, complex and cumbersome as I just learned that the unit has to be returned by the original purchaser from USA (I bought the N4 from a 3rd party in my country). Its an expensive mistake and I can only blame myself for the stupid mistake I made.
Thats how far i got with my bricked nexus thing was there was no images in hex to flash. the only thing i can think of is that you coulld try acking up a phone in QPST and the flash to bricked one. but you would need to enter the *# code to change usb on working phone to diagnostics
chwads2k8 said:
Thats how far i got with my bricked nexus thing was there was no images in hex to flash. the only thing i can think of is that you coulld try acking up a phone in QPST and the flash to bricked one. but you would need to enter the *# code to change usb on working phone to diagnostics
Click to expand...
Click to collapse
Not that simple. If you want, read this thread for some good info: http://forum.xda-developers.com/showthread.php?t=1914359
What where you trying to flash?
Anyone tried succesfully?
1 hour ago, I was checking Facebook, and a moment later, my phone started to restart... After a few moments, I realized that my phone was in bootloop. I tried booting into recovery, but It started a bootloop again. Flashed TWRP, nothing happens, still bootloop. Flashed vendor, system, boot, cache, recovery, radio, bootloader from lastest factory image. I have very important data on my phone, so the last thing I want to do is to do a factory reset. But I still hope that I can somehow get the userdata partition from bootloader or somehow make it boot. Can you help me? The only thing I can open right now is bootloader.
I'm having an exactly the same problem with you.
The only difference is that I didn't use Facebook.
I dared to lose my every data so I formatted userdata partition of my phone and flashed stock image, but it didn't fix mine.
I failed at figuring out the solution yet, but there's still one hope.
When I contacted with huawei, they said there's an upcoming update, and it will fix bricked phones.
I don't know if it will work, but considering you had your bootloader unlocked and can access it, and you have some important datas that you don't wanna lose, I recommend you keep your phone until the update gets released, then manually flash it without wiping your user data.
Given our phone's symptom is exactly the same and you tried similar methods I've tried, this is the best way I think you can try.
Good luck. You're in the same boat with me.
frostydawn said:
I'm having an exactly the same problem with you.
The only difference is that I didn't use Facebook.
I dared to lose my every data so I formatted every partition of my phone and flashed stock image, but it didn't fix mine.
I failed at figuring out the solution yet, but there's still one hope.
When I contacted with huawei, they said there's an upcoming update, and it will fix bricked phones.
I don't know if it will work, but considering you had your bootloader unlocked and can access it, and you have some important datas that you don't wanna lose, I recommend you keep your phone until the update gets released, then manually flash it without wiping your user data.
Given our phone's symptom is exactly the same and you tried similar methods I've tried, this is the best way I think you can try.
Good luck. You're in the same boat with me.
Click to expand...
Click to collapse
Yes, but we can wait for this update for months.. Also, when you flash a factory image, you lose you data (correct me if I'm wrong). So, it doesn't matter to me, if I try to format user data, or wait for the update. Hm...
fftorettol said:
Yes, but we can wait for this update for months.. Also, when you flash a factory image, you lose you data (correct me if I'm wrong). So, it doesn't matter to me, if I try to format user data, or wait for the update. Hm...
Click to expand...
Click to collapse
Well, android 7.1.2 beta for nexus 5x, pixel, or etc was released a few days ago, and for nexus 6p, it'll be released soon.
This is just my imagination, but maybe they're taking some times fixing boot loop so the release for 6p is getting late.
Also, you can flash factory images without user data lose by manually flashing it using fastboot commands.
The released image will contain some .img files, then you can extract it and then only flash required files without formatting userdata partition.
Don't use flash-all.bat, and use fastboot commands to selectively install image files except for userdata.
frostydawn said:
Well, android 7.1.2 beta for nexus 5x, pixel, or etc has been released a few days ago, and for nexus 6p, it'll be released soon.
This is just my imagination, but maybe they're taking some times fixing boot loop so the release for 6p is getting late.
Also, you can flash factory images without user data lose by manually flashing it using fastboot commands.
The released image will contain some .img files, then you can extract it and then only flash required files without formatting userdata partition.
Don't use flash-all.bat, and use fastboot commands to selectively install image files except for userdata.
Click to expand...
Click to collapse
Right! I've just got an idea to try older factory image versions for Nexus 6P... Mabye I get it working . I will let you now
I'm on the same boat as both of you guys. I tried installing TWRP but it continues to bootloop.
I have some important data I didn't get a chance to backup. and would not want to send it back/factory reformat.
Here's my thread:
https://forum.xda-developers.com/nexus-6p/help/nexus-6p-bootloop-to-recover-files-t3551455
Please keep us updated.
stillwind said:
I'm on the same boat as both of you guys. I tried installing TWRP but it continues to bootloop.
I have some important data I didn't get a chance to backup. and would not want to send it back/factory reformat.
Here's my thread:
https://forum.xda-developers.com/nexus-6p/help/nexus-6p-bootloop-to-recover-files-t3551455
Please keep us updated.
Click to expand...
Click to collapse
frostydawn said:
Well, android 7.1.2 beta for nexus 5x, pixel, or etc was released a few days ago, and for nexus 6p, it'll be released soon.
This is just my imagination, but maybe they're taking some times fixing boot loop so the release for 6p is getting late.
Also, you can flash factory images without user data lose by manually flashing it using fastboot commands.
The released image will contain some .img files, then you can extract it and then only flash required files without formatting userdata partition.
Don't use flash-all.bat, and use fastboot commands to selectively install image files except for userdata.
Click to expand...
Click to collapse
Guys, did you manage to fix it? I was doing some research, talking to some persons, and they said that it is probably a hardware problem. So, I went to the nearest Huawai servis, and they told me, that if the problem is really on hardware, it will cost me around 340€ (363 dollars) to replace motherboard... I can't afford that much... Its is almost a price of a new phone. I hope you came up with some better solutions.
fftorettol said:
Guys, did you manage to fix it? I was doing some research, talking to some persons, and they said that it is probably a hardware problem. So, I went to the nearest Huawai servis, and they told me, that if the problem is really on hardware, it will cost me around 340€ (363 dollars) to replace motherboard... I can't afford that much... Its is almost a price of a new phone. I hope you came up with some better solutions.
Click to expand...
Click to collapse
For now, I failed.
New 7.1.1 minor build update didn't fix my phone.
And google said they can't assure there will be update that will fix my phone.
I'm waiting for 7.1.2 beta, and if that doesn't work, well.. I don't know.
Maybe I should await 7.1.2 official, or.. just give up everything.
My hope is getting faded, and yeah.. for now, I can do nothing but wait for update.
Actually, I don't think those updates will work.
I'm just giving it a last chance, since repair service at here also costs about 350$, and if I fail, I should keep using Nexus 5.
Ah... It didn't took 2 weeks for my phone to be bricked after I bought this phone.
I really want to get this phone back, but the hope is too faint.
frostydawn said:
For now, I failed.
New 7.1.1 minor build update didn't fix my phone.
And google said they can't assure there will be update that will fix my phone.
I'm waiting for 7.1.2 beta, and if that doesn't work, well.. I don't know.
Maybe I should await 7.1.2 official, or.. just give up everything.
My hope is getting faded, and yeah.. for now, I can do nothing but wait for update.
Actually, I don't think those updates will work.
I'm just giving it a last chance, since repair service at here also costs about 350$, and if I fail, I should keep using Nexus 5.
Ah... It didn't took 2 weeks after I bought this phone.
I really want to get this phone back, but the hope is too faint.
Click to expand...
Click to collapse
Exactly... I was thinking... What if we lock the bootloader and send the phone to repair service with warranty papers... Do you think that can actually work out? Can they see that the phone was rooted, if we lock the bootloader with ADB Shell?
fftorettol said:
Exactly... I was thinking... What if we lock the bootloader and send the phone to repair service with warranty papers... Do you think that can actually work out? Can they see that the phone was rooted, if we lock the bootloader with ADB Shell?
Click to expand...
Click to collapse
I live in South Korea and in my country, they provide repair by post service for devices in the warranty period.
For me, my warranty is expired, so I had to bring it to the service center myself.
I've locked the bootloader and brought it the center.
They didn't check if it was ever unlocked or rooted.
The engineer only tried rebooting my phone several times, and said he should replace the motherboard. And they said they couldn't fix it for free because the warranty is expired.
I don't know how Huawei in your country will handle it, but I think if you flash the stock image and lock your phone, maybe they won't see that was ever rooted.
But I also don't know if they will provide free repair.
No luck on my end. I tried everything... I've been flashing and repairing problems like these since the nexus one but I'm totally stumped. Lucky/Unlucky for me I've only had the device for 3 months so I have an RMA ready since it is under warranty.
Most importantly tho is that I want to recover the files on the device which will not happen if I take it to the repair center as they reflash all the devices before proceeding to fix it.
I tried getting TWRP but the device reboots back into the boot as soon as I select recovery.
Also tried flashing everything but user data using flashboot and the nexus 6 .img files but still in the same situation.
I just wished they would've at least added a microsd option so I could at least have some of my files back...
I don't think I will ever get a phone without microsd option again or root and unlock bootloader on every device I get. This was the first phone I decided not to mess around with since everyone kept telling me to enjoy the stock experience....
Worse experience to date with android.
Well I gave up trying to fix it by software, and found another solution.
My warranty is expired, so it wasn't cost-efficient to bring my phone to official service center.
Now I bought a display-broken phone at about 60 dollars.
Gonna bring it to an engineer and replace my phone's motherboard with its intact one.
frostydawn said:
Now I bought a display-broken phone at about 60 dollars.
Click to expand...
Click to collapse
That's a great price. Is it the H1512 (International) and where did you purchase? Haenguneul bileoyo.
v12xke said:
That's a great price. Is it the H1512 (International) and where did you purchase? Haenguneul bileoyo.
Click to expand...
Click to collapse
It seems like you're Korean like me.
I bought it from Naver Cafe Google Reference Nexus Forum's market.
And yeah. It's H1512.
No, i'm not Korean but I spent a couple of years working in Okpo and Ulsan on several projects. There is a guy from KL in another thread looking for an H1512 motherboard. I'll pass your info on to him. Thanks.
v12xke said:
No, i'm not Korean but I spent a couple of years working in Okpo and Ulsan on several projects. There is a guy from KL in another thread looking for an H1512 motherboard. I'll pass your info on to him. Thanks.
Click to expand...
Click to collapse
Well, then tell him this too.
Naver Cafe 'Joonggonara'
This is one of the largest market for used stuffs.
frostydawn said:
Well, then tell him this too.
Naver Cafe 'Joonggonara'
This is one of the largest market for used stuffs.
Click to expand...
Click to collapse
Link Product
VN_Optimus said:
Link Product
Click to expand...
Click to collapse
It was a one-off purchase of a broken phone on a Korean market equivalent of Craigslist. You'll have to dig around and find one locally... and be lucky, too.
I just had reboots today for the first lasting about 20 minutes. I was able to get into Recovery and clear the cache and then shut down the phone. Upon restart it looped a few times and then fully booted (thankfully). I have placed the latest firmware in the phone in the hope that if this happens again I can flash the firmware and access the phone.
I hope this helps a bit.
I am rooted and running N2G47H.
Doc
DocEsq said:
I just had reboots today for the first lasting about 20 minutes. I was able to get into Recovery and clear the cache and then shut down the phone. Upon restart it looped a few times and then fully booted (thankfully). I have placed the latest firmware in the phone in the hope that if this happens again I can flash the firmware and access the phone.
I hope this helps a bit.
I am rooted and running N2G47H.
Doc
Click to expand...
Click to collapse
Hopefully it will but realistically this could be the beginning of the end for your phone given the 6P history with the boot loop of death. Presumably your phone is out of warranty?
Hey guys,
Not having much fun with the Axon 7's, got one a while ago and was running Linage OS and dropped it in water and it's fully dead.
Decided that I'd grab a deal on one, and got sick of the stock ROM real quick so went to Flash Linage OS 14.1 as before with the Axon 7 Toolkit.
However when flashing the bootloader, I accidentally left the Android version set to 7.0 instead of 6.0. Which appears to have bricked my Axon 7.. Not sure if this is what bricked it or something else, regardless that's the last thing I did.
I can see it in Windows appearing as "ZTE Handset Diagnostic Interface (DFU)" - With a COM port listed.
The Axon 7 Toolkit now does not detect the phone no matter what I do, nor does Xiaomi Miflash or whatever it's called.
The phone boots to a black screen, with a red LED notification icon that stays solid red. Force restarting it boots it back into the same state as it has no bootloader or is corrupt at a guess.
Starting to get desperate here..
Windows 10 x64 Based PC and the original USB cable.
Any help or assistance is greatly appreciated.
Mattie86 said:
Hey guys,
Not having much fun with the Axon 7's, got one a while ago and was running Linage OS and dropped it in water and it's fully dead.
Decided that I'd grab a deal on one, and got sick of the stock ROM real quick so went to Flash Linage OS 14.1 as before with the Axon 7 Toolkit.
However when flashing the bootloader, I accidentally left the Android version set to 7.0 instead of 6.0. Which appears to have bricked my Axon 7.. Not sure if this is what bricked it or something else, regardless that's the last thing I did.
I can see it in Windows appearing as "ZTE Handset Diagnostic Interface (DFU)" - With a COM port listed.
The Axon 7 Toolkit now does not detect the phone no matter what I do, nor does Xiaomi Miflash or whatever it's called.
The phone boots to a black screen, with a red LED notification icon that stays solid red. Force restarting it boots it back into the same state as it has no bootloader or is corrupt at a guess.
Starting to get desperate here..
Windows 10 x64 Based PC and the original USB cable.
Any help or assistance is greatly appreciated.
Click to expand...
Click to collapse
I'm not sure about this, but based on the description you gave, it looks like you have a 4th category DFU brick.
Try zadig, maybe you will be able to get the drivers to work and get recognized as QUSB BULK but if not, then 4th category brick guide will be the only way to fix it.
troy5890 said:
I'm not sure about this, but based on the description you gave, it looks like you have a 4th category DFU brick.
Click to expand...
Click to collapse
Kantastisch said:
Try zadig, maybe you will be able to get the drivers to work and get recognized as QUSB BULK but if not, then 4th category brick guide will be the only way to fix it.
Click to expand...
Click to collapse
Yep, did have a fiddle around more. Seems like it's a 4th category brick.
I'm waiting for it to go flat,as some people have suggested that might work. I have tried zadig and no luck thus far.
If that fails I'm going to contact ZTE and see what they can offer..
If that fails I'll open it up, and I have my water damaged phone for reference purposes.
Thanks for the heads up and advice guys.
Mattie86 said:
Yep, did have a fiddle around more. Seems like it's a 4th category brick.
I'm waiting for it to go flat,as some people have suggested that might work. I have tried zadig and no luck thus far.
If that fails I'm going to contact ZTE and see what they can offer..
If that fails I'll open it up, and I have my water damaged phone for reference purposes.
Thanks for the heads up and advice guys.
Click to expand...
Click to collapse
Yeah I'd contact ZTE if it doesn't work out. I'm glad I helped you out man
troy5890 said:
Yeah I'd contact ZTE if it doesn't work out. I'm glad I helped you out man
Click to expand...
Click to collapse
Couldn't get anywhere, contacted ZTE but the level 1 person got mad at me when I said it wasn't entering recovery and told me to call senior support..
I said that it froze during updating and so I had to turn it off as it was stuck there for an hour or more.. I mean I'm not lying just didn't specify what update I was doing.
Tried to call the senior advisor line? (It's really weird that they have a separate line?) I'm Senior support for another company and we just transfer calls directly.
Their hours suck, 10-4PM... Ergh, don't know how far I'll be getting. I could always take it back to where I got it, but that's an hour away and they won't have any stock (so it'd be a refund)
Mattie86 said:
Couldn't get anywhere, contacted ZTE but the level 1 person got mad at me when I said it wasn't entering recovery and told me to call senior support..
I said that it froze during updating and so I had to turn it off as it was stuck there for an hour or more.. I mean I'm not lying just didn't specify what update I was doing.
Tried to call the senior advisor line? (It's really weird that they have a separate line?) I'm Senior support for another company and we just transfer calls directly.
Their hours suck, 10-4PM... Ergh, don't know how far I'll be getting. I could always take it back to where I got it, but that's an hour away and they won't have any stock (so it'd be a refund)
Click to expand...
Click to collapse
So you break your phone and now expect someone else to take care of it for you? Just follow the guide and fix it yourself. Pretty sure using miflash is not covered under warranty.
lafester said:
So you break your phone and now expect someone else to take care of it for you? Just follow the guide and fix it yourself. Pretty sure using miflash is not covered under warranty.
Click to expand...
Click to collapse
I have heard and seen others do it however, which is why I'm trying. If it was a flat out "no" I'd be fine with it.
Mattie86 said:
I have heard and seen others do it however, which is why I'm trying. If it was a flat out "no" I'd be fine with it.
Click to expand...
Click to collapse
On windows 10 there could be some issues with drivers, I had huge problems installig the QUSB Bulk driver but I wasn't Zte H... Interface but Qdloader 9008 but maybe it'll still work for you. I disconnected my pc completwly from the internet (becauss windows updated my drivers automaticcly, no matter what I did) and uninstalled the QDloader driver and installed the zadig driver a few times, it was a really tricky process but eventually it worked out. But as stated I was recognized as QDLOADER and ZTE Handset user interface or whatever is way worse, so I think it won't work but you could give it a try.
Kantastisch said:
Try zadig, maybe you will be able to get the drivers to work and get recognized as QUSB BULK but if not, then 4th category brick guide will be the only way to fix it.
Click to expand...
Click to collapse
Never works...
---------- Post added at 05:19 PM ---------- Previous post was at 05:14 PM ----------
Mattie86 said:
I have heard and seen others do it however, which is why I'm trying. If it was a flat out "no" I'd be fine with it.
Click to expand...
Click to collapse
Look, the FTM method only works with much more mild bricks. You flashed the wrong bootstack there probably. It's fried.
Use my DFU unbrick guide, the 4th categ guide is less detailed.
If you don't wanna do it you can risk it and try the failed update thing again, some people here convinced them. But you might face the $80 fee if they find out
Choose an username... said:
Never works...
---------- Post added at 05:19 PM ---------- Previous post was at 05:14 PM ----------
Look, the FTM method only works with much more mild bricks. You flashed the wrong bootstack there probably. It's fried.
Use my DFU unbrick guide, the 4th categ guide is less detailed.
If you don't wanna do it you can risk it and try the failed update thing again, some people here convinced them. But you might face the $80 fee if they find out
Click to expand...
Click to collapse
It worked for me, but I wasn't ZTE Handset ... device though
Kantastisch said:
It worked for me, but I wasn't ZTE Handset ... device though
Click to expand...
Click to collapse
That's the point, you are ignoring the circumstances. He made a disaster with the software; maybe he flashed a Nougat bootstack on Marshmallow. Do you think that would have changed the driver, and that magically it would still be EDL in disguise?
It worked for you because it was Qualcomm HS-USB QDLoader 9008. Or QUSB_BULK but on the unknown devices list. That has nothing to do with a 4th category brick
troy5890 said:
Yeah I'd contact ZTE if it doesn't work out. I'm glad I helped you out man
Click to expand...
Click to collapse
lafester said:
So you break your phone and now expect someone else to take care of it for you? Just follow the guide and fix it yourself. Pretty sure using miflash is not covered under warranty.
Click to expand...
Click to collapse
Choose an username... said:
Never works...
---------- Post added at 05:19 PM ---------- Previous post was at 05:14 PM ----------
Look, the FTM method only works with much more mild bricks. You flashed the wrong bootstack there probably. It's fried.
Use my DFU unbrick guide, the 4th categ guide is less detailed.
If you don't wanna do it you can risk it and try the failed update thing again, some people here convinced them. But you might face the $80 fee if they find out
Click to expand...
Click to collapse
If it's $80 I'd be happy to pay it honestly. I will double check everything I do next time before doing it too..
Choose an username... said:
That's the point, you are ignoring the circumstances. He made a disaster with the software; maybe he flashed a Nougat bootstack on Marshmallow. Do you think that would have changed the driver, and that magically it would still be EDL in disguise?
It worked for you because it was Qualcomm HS-USB QDLoader 9008. Or QUSB_BULK but on the unknown devices list. That has nothing to do with a 4th category brick
Click to expand...
Click to collapse
I also installed a nougat bootstack on 6.0 and nothing happened.
Kantastisch said:
I also installed a nougat bootstack on 6.0 and nothing happened.
Click to expand...
Click to collapse
Well he clearly did something that provoked that brick, and it wasn't just forgetting to flash something, y'kno
My phone is totally bricked, and it will not respond to anything, a totally black screen, after flashing Android 12 Beta using Fastboot.
I was on A12 Beta, I hated it, I wanted to flash AOSP, it did not work, so I decided to flash OOS 11 from Fastboot, it did not work either, I tried EDL MSM tool, it did not work either, it kept on booting into fastboot, fastboot loop, I extracted the payload.bin from A12 Beta using payload_dumper, I ran flash-all script, the phone successfully booted into fastboot the at the first section from the script, flashed the remaining files, when the phone attempted to rebooted for the final time after the script was completed successfully with no errors, the phone died at the final part of the script, which is the final boot, and it will not respond to anything, no sign of anything, complete black screen, I tried EDL mode, I tried everything, it's not responding to anything, I opened the phone and reseated the battery and the motherboard, still nothing. So Sad
Flashing roms via fastboot never works for me.
You should read the threads next time, there is no custom rom that works from a12, every rom need a11 as a base. And yes the a12 custom roms too.
Your only option is and was the MSM tool.
I was in a similar situation, i got my phone back with pressing vol +, vol - and power for i think several minutes while connected with a third party cable to my pc with msm tool where i already pressed start.
It started to flash everything somehow and i got a working phone.
Good luck.
A quick note: EDL mode will show nothing nor vibrate. The only way you know it's in EDL mode is that it's going to show up in MSM tool.
Just try using the MSM tool.
Start the program.
Hold the Vol Up and Vol Down at the same time for 5 seconds, then connect your phone to your PC.
If it doesn't show up in the MSM tool list, just hit Enum.
If you see the phone just click Start and wait for it to complete. For me it's usually around 300 sec.
xtcislove said:
Flashing roms via fastboot never works for me.
You should read the threads next time, there is no custom rom that works from a12, every rom need a11 as a base. And yes the a12 custom roms too.
Your only option is and was the MSM tool.
I was in a similar situation, i got my phone back with pressing vol +, vol - and power for i think several minutes while connected with a third party cable to my pc with msm tool where i already pressed start.
It started to flash everything somehow and i got a working phone.
Good luck.
Click to expand...
Click to collapse
Yes, OSS 11 is a must, I have tried downgrading and I guess "downgrading" is the issue here.
I have been using OnePlus since its first release, I am very familiar with it,
I have tried everything, but nothing works, I read more about this, and looks like the circuit is out of order, it will not pass anything "signal", especially to the screen.
nkhater said:
Yes, OSS 11 is a must, I have tried downgrading and I guess "downgrading" is the issue here.
I have been using OnePlus since its first release, I am very familiar with it,
I have tried everything, but nothing works, I read more about this, and looks like the circuit is out of order, it will not pass anything "signal", especially to the screen.
Click to expand...
Click to collapse
Thats possible im not a pro. But from my understanding, its nearly impossible to brick a phone which is using a/b partitions via fastboot.
You tried a third party cable?
daviddosa said:
A quick note: EDL mode will show nothing nor vibrate. The only way you know it's in EDL mode is that it's going to show up in MSM tool.
Just try using the MSM tool.
Start the program.
Hold the Vol Up and Vol Down at the same time for 5 seconds, then connect your phone to your PC.
If it doesn't show up in the MSM tool list, just hit Enum.
If you see the phone just click Start and wait for it to complete. For me it's usually around 300 sec.
Click to expand...
Click to collapse
true, but no Qualcomm port is shown in the windows device manager, and no sound coming from the laptop, it's cooked
xtcislove said:
Thats possible im not a pro. But from my understanding, its nearly impossible to brick a phone which is using a/b partitions via fastboot.
You tried a third party cable?
Click to expand...
Click to collapse
Yes fail-safe a/b partition, and Yes I have tried several cables
nkhater said:
true, but no Qualcomm port is shown in the windows device manager, and no sound coming from the laptop, it's cooked
Yes fail-safe a/b partition, and Yes I have tried several cables
Click to expand...
Click to collapse
My last suggestion is to try to charge overnight and see if things are different tomorrow.
Other than that, only option is RMA as it's still under warranty.
Forgot that you already opened up the phone, so most likely they'll throw it back as it was opened by an unauthorized party.
daviddosa said:
My last suggestion is to try to charge overnight and see if things are different tomorrow.
Other than that, only option is RMA as it's still under warranty.
Forgot that you already opened up the phone, so most likely they'll throw it back as it was opened by an unauthorized party.
Click to expand...
Click to collapse
did that too, leaving it overnight did not work either.
I hope this will be an eye-opener for other flashaholics, things are different in A12
my phone has the same problem, have you fixed it, i need help
[email protected] said:
my phone has the same problem, have you fixed it, i need help
Click to expand...
Click to collapse
no fix has to call support and use your warranty, the logic board is fried, this is a disaster, everyone, be careful, I want to sue them so bad
nkhater said:
no fix has to call support and use your warranty, the logic board is fried, this is a disaster, everyone, be careful, I want to sue them so bad
Click to expand...
Click to collapse
Made a thread about it to warn others and hopefully prevent more bricks from happening.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
ProtoDeVNan0 said:
Made a thread about it to warn others and hopefully prevent more bricks from happening.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Click to expand...
Click to collapse
OMG
Nobody believed me in the threads when this happened (end of Feb/early Mar). This wasn't spiteful in anyway either. It was more/less just unheard of and my methods and adherence to the most vital aspects for EDL recovery, were justifiably questioned. Unfortunately, in my case, I have had years of experience jacking-up my devices and I immediately knew/felt there was something different with this situation. In my situation though, when introducing how I had entered the predicament, it was strictly self-inflicted, complacency at its finest and terrible terrible timing for a well overdue slap-in-the-head to interject itself into my life. Did I mention I was OMW to Disney with m/wife, kids.....driving. I had 7 days to deal with at Disney with a pre-planned, fresh-flashed A-12 OP8....I ended up using my LG G3 which I had been spending significant time trying to develop into a dedicated full-fledged Kali device (had success w/that actually).
So seeing these posts and threads now is dis-heartening but vindicating. Had I not flashed A-12 the way I did, I would've been fine. I can not blame OnePlus for anything, I bought a locked-down (carrier unlocked) Note 10+ in its place and its driving me bonkers. I thought I would be able to tolerate the non-rootiness, but I've been flashing since my 1st smartphone, one of the 1st Galaxy's, the Verizon Fascinate.....good ol' Jelly Bean. Meanwhile, my lifeless OP8 sits on my desk upstairs surrounded by older devices.....its the only one that doesn't turn on.
Mar 3rd I posted for the 1st time about it.
OxygenOS 12 [OB1] [Oneplus 8 Pro] - First Open Beta of Global OOS12
*Will update thread as rn im at work* The first Open Beta for Global OOS has been release really quietly (no announcemment so far) but here is the link from where i download it...
forum.xda-developers.com
djcrystals said:
Nobody believed me in the threads when this happened (end of Feb/early Mar). This wasn't spiteful in anyway either. It was more/less just unheard of and my methods and adherence to the most vital aspects for EDL recovery, were justifiably questioned. Unfortunately, in my case, I have had years of experience jacking-up my devices and I immediately knew/felt there was something different with this situation. In my situation though, when introducing how I had entered the predicament, it was strictly self-inflicted, complacency at its finest and terrible terrible timing for a well overdue slap-in-the-head to interject itself into my life. Did I mention I was OMW to Disney with m/wife, kids.....driving. I had 7 days to deal with at Disney with a pre-planned, fresh-flashed A-12 OP8....I ended up using my LG G3 which I had been spending significant time trying to develop into a dedicated full-fledged Kali device (had success w/that actually).
So seeing these posts and threads now is dis-heartening but vindicating. Had I not flashed A-12 the way I did, I would've been fine. I can not blame OnePlus for anything, I bought a locked-down (carrier unlocked) Note 10+ in its place and its driving me bonkers. I thought I would be able to tolerate the non-rootiness, but I've been flashing since my 1st smartphone, one of the 1st Galaxy's, the Verizon Fascinate.....good ol' Jelly Bean. Meanwhile, my lifeless OP8 sits on my desk upstairs surrounded by older devices.....its the only one that doesn't turn on.
Click to expand...
Click to collapse
That's so fed'ed up man, I am in the same boat as you, total loss, I am done with OnePlus, they can enjoy Oppo and ColorOS, A12 sucks and it's not for me.
Had to replace the motherboard (and flash the old persist partition to get the fingerprint sensor to work) due to this flash ddr mismatch crap. Shame on oneplus. They're being way too careless on this "unifying" trend.
Andre Cancian said:
Had to replace the motherboard (and flash the old persist partition to get the fingerprint sensor to work) due to this flash ddr mismatch crap. Shame on oneplus. They're being way too careless on this "unifying" trend.
Click to expand...
Click to collapse
how much did you pay for the motherboard?
nkhater said:
how much did you pay for the motherboard?
Click to expand...
Click to collapse
I paid something like 250 USD for a working 8 Pro with a broken screen. Motherboards on their own were available for a similar price on sites like aliexpress, but the wait was too much.
nkhater said:
My phone is totally bricked, and it will not respond to anything, a totally black screen, after flashing Android 12 Beta using Fastboot.
I was on A12 Beta, I hated it, I wanted to flash AOSP, it did not work, so I decided to flash OOS 11 from Fastboot, it did not work either, I tried EDL MSM tool, it did not work either, it kept on booting into fastboot, fastboot loop, I extracted the payload.bin from A12 Beta using payload_dumper, I ran flash-all script, the phone successfully booted into fastboot the at the first section from the script, flashed the remaining files, when the phone attempted to rebooted for the final time after the script was completed successfully with no errors, the phone died at the final part of the script, which is the final boot, and it will not respond to anything, no sign of anything, complete black screen, I tried EDL mode, I tried everything, it's not responding to anything, I opened the phone and reseated the battery and the motherboard, still nothing. So Sad
Click to expand...
Click to collapse
hello, did you solve your problem? Or did you change your motherboard? I'm having the same problem right now and I don't know what to do
you need to replace the motherboard, the phone is completely dead, it's gone
Howdy. Tried to root my OnePlus 8 Pro. First time trying such a thing... Having now bricked my phone into a boot loop, I'm pretty sure that the guide I followed missed an important step. It said to download the latest patch, extract it, then use magisk to patch it and flash it. I'm pretty sure that the part I missed was actually updating to that patch before flashing. So I have whatever latest patch that I didn't have the foresight to write down, but my original build was IN2025_11_C.33 . Am I boned completely and thoroughly or is there any hope of recovering? Thanks either way.
LOL, welcome. Wisely, you've chosen a phone that supports EDL, with known ROMs. EDL will allow you to reflash to factory, no matter how badly you've messed up, assuming you didn't brick the hardware (which, unfortunately, is actually possible with this phone- there's two different RAM voltages and you can flash something that writes the wrong one and literally fry the phone... sigh)
All the stuff you need is covered in other threads here, and in other OnePlus forums on XDA... too tired to summarize them all (sorry). Search for the MSM tool (I think the one you want is here but please double check) and how to use it. Happy flashing, and welcome to the best phone mfr to mod! (Note EDL requires a Qualcomm chipset, there are other OP phones that do NOT have them... so not EVERY phone is bailable-outable...)
SomeRandomGuy said:
LOL, welcome. Wisely, you've chosen a phone that supports EDL, with known ROMs. EDL will allow you to reflash to factory, no matter how badly you've messed up, assuming you didn't brick the hardware (which, unfortunately, is actually possible with this phone- there's two different RAM voltages and you can flash something that writes the wrong one and literally fry the phone... sigh)
All the stuff you need is covered in other threads here, and in other OnePlus forums on XDA... too tired to summarize them all (sorry). Search for the MSM tool (I think the one you want is here but please double check) and how to use it. Happy flashing, and welcome to the best phone mfr to mod! (Note EDL requires a Qualcomm chipset, there are other OP phones that do NOT have them... so not EVERY phone is bailable-outable...)
Click to expand...
Click to collapse
thanks!
dimlu said:
thanks!
Click to expand...
Click to collapse
In case you haven't sorted it yet - this is a great MSM guide which also links to the Windows drivers you need and the MSM tools for your device.
Good luck