Related
I decided to write a guide on how to recover from a bricked OnePlus One. This is my first guide.
About me: I am a newbie on Android.However, the XDA community has taught me a lot about my Android phone for the first month of using it. That's right! I have only been using Android for less than one month so take this guide with a grain of salt. But if you happen to soft brick your One, this is the guide to turn to. I have created two mind-bending/heartbreaking/frightening scenarios that I have experienced. Though, resolved thanks to this community.
Note: This will wipe your phone!
Scenario 1:
Soft bricked, (CM gear keeps spinning but won't boot to lock screen)
Scenario 2: Updated kernel on a non-compatible firmware.
Soft bricked, screen on 1+ logo and won't boot to lock screen.
Solution:
1. Download the toolbox from: (Make sure you download your version)
http://forum.xda-developers.com/oneplus-one/development/toolbox-oneplus-one-toolbox-t2808987
2. Install the file.
3. Disconnect your OnePlus One from computer and power off your phone.
4. Go into Fastboot Mode (Volume Up + Power button) wait on vibrate
5. Plug in your OnePlus One.
6. Locate and open the OPO Toolbox.
7. Click Flash CM XNPH22R.
8. You should see command prompt open, just wait until it finishes doing it's thing.
9. Unplug and power off your phone.
10. Power ON your phone and wait until it prompts you re-setup your phone.
Congrats you have just fixed your phone from a soft brick. Simply follow the video from the link provided on step 1 to re-root your phone.
Note: If you have unlocked your bootloader, you do not need to unlock it again.
How to find out if you have unlocked bootloader:
1. Locate the folder where you installed the OPO Toolbox.
2. Hold Shift and right click on ANY white area within the folder.
3. Left click 'Open command window here'
4. Type:
fastboot oem device-info
If it returns True on tampered. Then you have unlocked your bootloader.
I hope this guide helps solve your soft-bricked problem. Good luck!
I suggest that a mod moves this to the General section
pandasa123 said:
I suggest that a mod moves this to the General section
Click to expand...
Click to collapse
Report the thread if you think its necessary.
Well I got this FAILED in the command line, and afterwards didnt got a re- setup...
what am I doing wrong here?:crying:
Digital Arm said:
Well I got this FAILED in the command line, and afterwards didnt got a re- setup...
what am I doing wrong here?:crying:
Click to expand...
Click to collapse
You don't have an unlocked bootloader.
Transmitted via Bacon
timmaaa said:
You don't have an unlocked bootloader.
Transmitted via Bacon
Click to expand...
Click to collapse
Thx got it:cyclops:
Scenario 2: Updated kernel on a non-compatible firmware.
Soft bricked, screen on 1+ logo and won't boot to lock screen.
Solution:
1. Download the toolbox from: (Make sure you download your version)
http://forum.xda-developers.com/oneplus-one/development/toolbox-oneplus-one-toolbox-t2808987
2. Install the file.
3. Disconnect your OnePlus One from computer and power off your phone.
4. Go into Fastboot Mode (Volume Up + Power button) wait on vibrate
5. Plug in your OnePlus One.
6. Locate and open the OPO Toolbox.
7. Click Flash CM XNPH22R.
8. You should see command prompt open, just wait until it finishes doing it's thing.
9. Unplug and power off your phone.
10. Power ON your phone and wait until it prompts you re-setup your phone.
Congrats you have just fixed your phone from a soft brick. Simply follow the video from the link provided on step 1 to re-root your phone.
Note: If you have unlocked your bootloader, you do not need to unlock it again.
Hi i am stuck in scenario 2...I did all a u said but i cant flash CM XNPH22R ...where do i find this file...i cant find it on my phone either ..pls help ??
Thank god for this thread omg, saved my life
Locked Bootloader
This didn't work...
My phone is Soft Bricked (oneplus logo freeze) locked bootoader and usb debuging is not enabled.
What can I do to fix it??
RiccoSuave said:
This didn't work...
My phone is Soft Bricked (oneplus logo freeze) locked bootoader and usb debuging is not enabled.
What can I do to fix it??
Click to expand...
Click to collapse
But why happened this ? Whats the last actions attempted to do with the phone before the brick?
Tecleado desde mi 1+1.
Champi12301 said:
But why happened this ? Whats the last actions attempted to do with the phone before the brick?
Tecleado desde mi 1+1.
Click to expand...
Click to collapse
I did an ota update and it went in to a boot-loop, so I went into fast-boot and accidentally locked the boot-loader.
I think I have to try to hard-brick it and try the hard-brick solution with the qualcom drivers.
RiccoSuave said:
I did an ota update and it went in to a boot-loop, so I went into fast-boot and accidentally locked the boot-loader.
I think I have to try to hard-brick it and try the hard-brick solution with the qualcom drivers.
Click to expand...
Click to collapse
Then first you need to unlock the bootloader via fastboot,but that action erases all data. I assume,if you modified the boot via fastboot, USB DEBUGGING is working,so after try to do the softbrick tutorial of the thread.
Tecleado desde mi 1+1.
how do i know which tool box version is mine ?
---------- Post added at 07:42 PM ---------- Previous post was at 07:26 PM ----------
i tried the fastboot method, i successfully run alll the commands but still stuck in the bootloop.
i even tried adb, but i cant go into recovery mode for my computer to detect it. The weird thing is i can easily go into the fastboot mode but for some reason i can go into recovery mode. i tried turning of the phone by holding power button too long and then vol down + power button, still no luck, now im stuck with 2 options,
1. the toolkit solution
2. the qualcom thingy. It's been two days without my opo, and i feel so lost ! PLS if anyone sees my comments plss respond to me PLS! i willl forever be grateful to you!
deanwinchester370 said:
how do i know which tool box version is mine ?
---------- Post added at 07:42 PM ---------- Previous post was at 07:26 PM ----------
i tried the fastboot method, i successfully run alll the commands but still stuck in the bootloop.
i even tried adb, but i cant go into recovery mode for my computer to detect it. The weird thing is i can easily go into the fastboot mode but for some reason i can go into recovery mode. i tried turning of the phone by holding power button too long and then vol down + power button, still no luck, now im stuck with 2 options,
1. the toolkit solution
2. the qualcom thingy. It's been two days without my opo, and i feel so lost ! PLS if anyone sees my comments plss respond to me PLS! i willl forever be grateful to you!
Click to expand...
Click to collapse
Did you find a solution ?
I'm facing the exact same issue on my OPO.
>> bootloader locked
>> no recovery
>> impossible to unlock the bootloader
>> OPO stuck at 1+ logo and keep rebooting agin and again and again...
....i think my OPO is dead T_T
Is it a way to force the bootloader unlock ?
Please HELP !!!
Didn't work for me
I'll give the background first as it might help. I long while back I did a manual upgrade to CM12s using the guide in this video "How to Install CM12S on OnePlus One - No Root or TWRP Required, No Data LOSS" from the oneplus exclusive Youtube channel.
It worked great no problems.
I recently I got the OTA update to CM13. There were several features I didn't like so I decided to go back. I repeated the process shown in the video but now my phone gets stuck on the CM logo screen and won't go past. I tried again but the same result. Then (I can see heads shaking, sorry) I tried a factory reset from the recovery screen, still the same goes past the 1+ logo but gets stuck at the CM logo. Then I found this guide, downloaded the toolbox but when I try to plash it says "fastboot is not recognized as an internal or external command.
Any ideas?
Found a link on one of the threads here that said a guide on Reddit was useful, that didn't work as well. I am trying.
All done
davmeva said:
I'll give the background first as it might help. I long while back I did a manual upgrade to CM12s using the guide in this video "How to Install CM12S on OnePlus One - No Root or TWRP Required, No Data LOSS" from the oneplus exclusive Youtube channel.
It worked great no problems.
I recently I got the OTA update to CM13. There were several features I didn't like so I decided to go back. I repeated the process shown in the video but now my phone gets stuck on the CM logo screen and won't go past. I tried again but the same result. Then (I can see heads shaking, sorry) I tried a factory reset from the recovery screen, still the same goes past the 1+ logo but gets stuck at the CM logo. Then I found this guide, downloaded the toolbox but when I try to plash it says "fastboot is not recognized as an internal or external command.
Any ideas?
Found a link on one of the threads here that said a guide on Reddit was useful, that didn't work as well. I am trying.
Click to expand...
Click to collapse
No one replied to this but never mind, took me two days but I now have a working phone. So you can call in the dogs, cheers
hi davmeva
did you fixed your oneplus one till now or not because i have also same situation here and no success till now .
i did by mistake all this stuff and now nothing work still same condition
if you got any solution please share it
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the "Deuces" script or to flash a new system image.
I have tried all of the basic stuff to get to my device to be recognized. I downloaded and installed the latest ADB & Fastboot and I have tried different cables and USB ports and still have no luck. I'm really worried and not sure what to do if I cannot get my device to accept fastboot commands so I can recover.
Please let me know if you have any ideas that may help me.
Jason
EDIT:
I still have no idea what I did, but I decided to use the Skipsoft Tool to see if it would work. Lucky for me it did and I was able to restore the factory image. Sorry for the fire-drill, I should have tried this before I posted. Thank you for the replies!!
Grab the latest Google platform tools and USB drivers. When your device is plugged in, do you see any unknown devices in your device manager? Or anything that looks like it could be your phone?
jascolli said:
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the "Deuces" script or to flash a new system image.
I have tried all of the basic stuff to get to my device to be recognized. I downloaded and installed the latest ADB & Fastboot and I have tried different cables and USB ports and still have no luck. I'm really worried and not sure what to do if I cannot get my device to accept fastboot commands so I can recover.
Please let me know if you have any ideas that may help me.
Jason
Click to expand...
Click to collapse
I've seen that before.
When you select reboot bootloader does that message go away?
Try it without the cable plugged in does it go away then?
I just want to know if you can actually get that message to go away or not at this point.
Also can you link the tools you are downloading
jascolli said:
I still have no idea what I did, but I decided to use the Skipsoft Tool to see if it would work. Lucky for me it did and I was able to restore the factory image. Sorry for the fire-drill, I should have tried this before I posted. Thank you for the replies!!
Click to expand...
Click to collapse
For future learning, I'd recommend you familiarize yourself with how to do this without toolkits. A toolkit is nice, but it really helps to understand what the toolkit is doing so that if you have an issue you know what to do next.
Telperion said:
For future learning, I'd recommend you familiarize yourself with how to do this without toolkits. A toolkit is nice, but it really helps to understand what the toolkit is doing so that if you have an issue you know what to do next.
Click to expand...
Click to collapse
Solid advice, thank you.
I did this same thing and solved it the same way. I think things just get funky and the tool you mentioned to fix it.
nolimit78 said:
I did this same thing and solved it the same way. I think things just get funky and the tool you mentioned to fix it.
Click to expand...
Click to collapse
Yeah I'm baffled. I could not for the life of me get fastboot to work. That Skipsoft tool is pretty impressive.
HELP!!!!
I have same problem, so which functions you use to fix it????
jascolli said:
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the "Deuces" script or to flash a new system image.
I have tried all of the basic stuff to get to my device to be recognized. I downloaded and installed the latest ADB & Fastboot and I have tried different cables and USB ports and still have no luck. I'm really worried and not sure what to do if I cannot get my device to accept fastboot commands so I can recover.
Please let me know if you have any ideas that may help me.
Jason
EDIT:
I still have no idea what I did, but I decided to use the Skipsoft Tool to see if it would work. Lucky for me it did and I was able to restore the factory image. Sorry for the fire-drill, I should have tried this before I posted. Thank you for the replies!!
Click to expand...
Click to collapse
Same thing happened to me. I need help. Please tell me how you unbricked your phone
same problem
i have the same problem already download skipsoft program but dont have results can you tell me the steps what you do please
---------- Post added at 07:48 AM ---------- Previous post was at 07:43 AM ----------
yuva_cool said:
Same thing happened to me. I need help. Please tell me how you unbricked your phone
Click to expand...
Click to collapse
do you already unbricked your phone?
my pixel still cant be detected by that toolkit, can u list the step by step procedure what u did to unbrick the device?
I was having the exact same issue as OP. I wound up fixing it by entering fastboot and making it display barcodes until the battery died. Then I put a rubber band over the power button so the red led would blink (I wanted to completely drain the battery). When it stopped blinking, I hooked my dead phone up to my PC via a USB 3 port and held Power + vol down to boot into fastboot (the battery was still too low for the phone to boot normally -- it would just show the battery icon). Surprisingly, my PC recognized my phone (made the little USB sound) and I was able to fastboot flash-all the newest factory image on it!! No toolkits required!
I'm so happy because this was a last ditch effort before I sent my original phone back to google and would have to live with the RMA they sent me which could not be bootloader unlocked (this is a whole other issue!)
I hope this helps!
EDIT: Info I provided in a PM
Unfortunately I didn't take any photos of the process... I didn't want to push my luck and things are working now. But The photo I've attached was exactly what I was seeing except I was on the December update (Now I'm on the January update) ... and:
UFS: 128 GB Hynix
DRAM: 4096MB Micron LPDDR4
Device State: unlocked (I had been unlocked since April 2018)
Until I had entirely drained my battery, I couldn't do anything. Download mode and recovery mode were impossible to access. I forgot the specific error, but it was the same as a lot of other people who have been having this problem.
The only thing I could do was to restart bootloader, which removed the error message until I tried to do anything. I couldn't boot at all or do anything conducive to fixing my phone until I drained the battery entirely. I couldn't get any PCs to even acknowledge the existance of my phone until after the battery was drained.
Keep in mind, I NEVER got my RMA phone to work. I was only able to fix my original NEW phone that I had purchased directly from google.
Until I had entirely drained my battery, I couldn't do anything. Download mode and recovery mode were impossible to access. I forgot the specific error, but it was the same as a lot of other people who have been having this problem.
The only thing I could do was to restart bootloader, which removed the error message until I tried to do anything. I couldn't boot at all or do anything conducive to fixing my phone until I drained the battery entirely. I couldn't get any PCs to even acknowledge the existance of my phone until after the battery was drained.
Click to expand...
Click to collapse
This is the correct resolution to this issue.
I had the same issue, no usb in bootloader. I drained the phone and rebooted into the Bootloader flash A and B side bootloader the Aug 2018 (previously working for me) and A and B side Radio, as well as the System image. After that everything booted fine.
Attempted to install the January update the same way and it worked as well.
Seems like they messed up A and B side flashing
My steps::: For Lurkers having this issue.
1. Drain battery DEAD!
2. Boot Bootloader (Vol Down + Power)
3. fastboot flash bootloader bootloader-walleye-mw8998-002.0073.02.img (or whatever image)
3. fastboot set_active b (opposite of the one on screen)
4. fastboot reboot-bootloader
5. fastboot flash bootloader bootloader-walleye-mw8998-002.0073.02.img (or whatever image) (Again)
6. fastboot reboot-bootloader
7. fastboot flash radio radio-walleye-g8998-00253-1809191716.img (or whatever image)
8. fastboot set_active a (opposite of the one on screen)
9. fastboot reboot-bootloader
10. fastboot flash radio radio-walleye-g8998-00253-1809191716.img (or whatever image)
11. fastboot reboot-bootloader
12. fastboot update image-walleye-pq1a.190105.004.zip (or whatever image)
Phone boots properly, and is updated.
thedude9821 said:
I was having the exact same issue as OP. I wound up fixing it by entering fastboot and making it display barcodes until the battery died. Then I put a rubber band over the power button so the red led would blink (I wanted to completely drain the battery). When it stopped blinking, I hooked my dead phone up to my PC via a USB 3 port and held Power + vol down to boot into fastboot (the battery was still too low for the phone to boot normally -- it would just show the battery icon). Surprisingly, my PC recognized my phone (made the little USB sound) and I was able to fastboot flash-all the newest factory image on it!! No toolkits required!
I'm so happy because this was a last ditch effort before I sent my original phone back to google and would have to live with the RMA they sent me which could not be bootloader unlocked (this is a whole other issue!)
I hope this helps!
EDIT: Info I provided in a PM
Unfortunately I didn't take any photos of the process... I didn't want to push my luck and things are working now. But The photo I've attached was exactly what I was seeing except I was on the December update (Now I'm on the January update) ... and:
UFS: 128 GB Hynix
DRAM: 4096MB Micron LPDDR4
Device State: unlocked (I had been unlocked since April 2018)
Until I had entirely drained my battery, I couldn't do anything. Download mode and recovery mode were impossible to access. I forgot the specific error, but it was the same as a lot of other people who have been having this problem.
The only thing I could do was to restart bootloader, which removed the error message until I tried to do anything. I couldn't boot at all or do anything conducive to fixing my phone until I drained the battery entirely. I couldn't get any PCs to even acknowledge the existance of my phone until after the battery was drained.
Keep in mind, I NEVER got my RMA phone to work. I was only able to fix my original NEW phone that I had purchased directly from google.
Click to expand...
Click to collapse
omg after months of figuring it out ,and almost opt for warranty,finally my pixel is aliveeeee, thanks alot for the fix im so glad.. and whats more important for me is the data is still intact! i cant thank you enough.. google messed up december update pretty bad.
I just received my 4th RMA and the bootloader wasn't able to unlock. So to my surprise Google is giving me a full refund? I purchased my Pixel 2 back in Nov 2017 ?
Dajax2 said:
3. fastboot flash bootloader bootloader-walleye-mw8998-002.0073.02.img (or whatever image)
Click to expand...
Click to collapse
@Dajax2 Super new to this and it may be a total waste since my bootloader screen says "Device State: locked" but in trying to flash or even sideload ota, the command returns "error: cannot load (file location/name): no such file or directory found". Again, total noob and I don't even know if I'm supposed to unzip the folder or not but have tried both ways with the same error.
It returns the serial number for fastboot devices but nothing for adb devices. I obviously didn't have OEM or USB debugging enabled prior. Hoping I can at least get in to retrieve data before giving up all hope :/
Solved. Enter barcode mode. In this screen, check for devices from adb or fastboot. It should be there. You are now able to switch slots and do all the fastboot things.
Great workaround that I would never have thought - good info here, thanks everyone!
dianea said:
Solved. Enter barcode mode. In this screen, check for devices from adb or fastboot. It should be there. You are now able to switch slots and do all the fastboot things.
Click to expand...
Click to collapse
Edit - My phone wasn't detected when on the barcode screen, just like from the main bootloader screen.
HOWEVER... to my surprise.. the above method of draining the battery completely to 0% actually worked. I'm a little dumbfounded why this allowed the bootloader to connect via fastboot again, but it did. I was able to flash the latest factory image (without wipe) and boot back up like nothing ever happened. Thank you so much for the tip. I passed this along to Google support and they also said they appreciate the troubleshooting and asked me to just send back the replacement phone with the RMA package/label.
---------- Post added at 06:36 PM ---------- Previous post was at 06:18 PM ----------
thedude9821 said:
Keep in mind, I NEVER got my RMA phone to work. I was only able to fix my original NEW phone that I had purchased directly from google.
Click to expand...
Click to collapse
Did they accept the RMA phone back and remove the temp auth on your card?
thedude9821 said:
I was having the exact same issue as OP. I wound up fixing it by entering fastboot and making it display barcodes until the battery died. Then I put a rubber band over the power button so the red led would blink (I wanted to completely drain the battery). When it stopped blinking, I hooked my dead phone up to my PC via a USB 3 port and held Power + vol down to boot into fastboot (the battery was still too low for the phone to boot normally -- it would just show the battery icon). Surprisingly, my PC recognized my phone (made the little USB sound) and I was able to fastboot flash-all the newest factory image on it!! No toolkits required!
I'm so happy because this was a last ditch effort before I sent my original phone back to google and would have to live with the RMA they sent me which could not be bootloader unlocked (this is a whole other issue!)
I hope this helps!
EDIT: Info I provided in a PM
Unfortunately I didn't take any photos of the process... I didn't want to push my luck and things are working now. But The photo I've attached was exactly what I was seeing except I was on the December update (Now I'm on the January update) ... and:
UFS: 128 GB Hynix
DRAM: 4096MB Micron LPDDR4
Device State: unlocked (I had been unlocked since April 2018)
Until I had entirely drained my battery, I couldn't do anything. Download mode and recovery mode were impossible to access. I forgot the specific error, but it was the same as a lot of other people who have been having this problem.
The only thing I could do was to restart bootloader, which removed the error message until I tried to do anything. I couldn't boot at all or do anything conducive to fixing my phone until I drained the battery entirely. I couldn't get any PCs to even acknowledge the existance of my phone until after the battery was drained.
Keep in mind, I NEVER got my RMA phone to work. I was only able to fix my original NEW phone that I had purchased directly from google.
Click to expand...
Click to collapse
Dajax2 said:
This is the correct resolution to this issue.
I had the same issue, no usb in bootloader. I drained the phone and rebooted into the Bootloader flash A and B side bootloader the Aug 2018 (previously working for me) and A and B side Radio, as well as the System image. After that everything booted fine.
Attempted to install the January update the same way and it worked as well.
Seems like they messed up A and B side flashing
My steps::: For Lurkers having this issue.
1. Drain battery DEAD!
2. Boot Bootloader (Vol Down + Power)
3. fastboot flash bootloader bootloader-walleye-mw8998-002.0073.02.img (or whatever image)
3. fastboot set_active b (opposite of the one on screen)
4. fastboot reboot-bootloader
5. fastboot flash bootloader bootloader-walleye-mw8998-002.0073.02.img (or whatever image) (Again)
6. fastboot reboot-bootloader
7. fastboot flash radio radio-walleye-g8998-00253-1809191716.img (or whatever image)
8. fastboot set_active a (opposite of the one on screen)
9. fastboot reboot-bootloader
10. fastboot flash radio radio-walleye-g8998-00253-1809191716.img (or whatever image)
11. fastboot reboot-bootloader
12. fastboot update image-walleye-pq1a.190105.004.zip (or whatever image)
Phone boots properly, and is updated.
Click to expand...
Click to collapse
Gifted both of you Ad-Free for this.
You saved me $300 and the annoyance of having to wait for shipping for either RMA or another phone on Swappa.
Phone memory was almost totally full and my sister was still shooting videos on it.
During one shoot the phone turned off and I can't turn it back on again.
Here is my problem, the phone just doesn't boot.
Shows only first screen with 1+ logo and then reboots. Not even the system boot animation.
When I try to enter recovery mode it shows TWRP screen and then reboots again. So I can't even access recovery.
And when I try to enter Fastboot Mode it turns on but the PC won't see it in adb.
What are my options here?
try charging the phone for a few hours
se7enlyn said:
try charging the phone for a few hours
Click to expand...
Click to collapse
yeah, forgot to mention that. can't even charge it. when I plug it in it does the same. tries to turn on. shows the first splash screen and reboots doing the same again and again. doesnt even show the charging screen with chinese text and battery animation.
sounds like u need a new battery
ireaper4592 said:
sounds like u need a new battery
Click to expand...
Click to collapse
already tried that too. had a replacement battery laying around. changed it and still no luck.
@bmark240
help please
se7enlyn said:
@bmark240
help please
Click to expand...
Click to collapse
hi you need to follow this guide :https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Hi.
Firstly, you have recovery installed, so that is good.
Some things for you to try:
Can you hold down the power button for longer than 10 seconds. This will clear temporary memory and hard reboot.Press power button & volume 'down' button until you enter TWRP.
Try this firstly.
Can you access ADB at all?
15 second ADB drivers should work.
What Operating system is on your Computer?
TWRP should pop up & be accessible
If you have Windows 10 on. If it doesn't recognize your phone you will have to run an update for Media Center for Windows 10 (64 bit...I'm assuming its not 32bit).
TWRP should be read by your computer if you can access it as it contains the drivers inbuilt.
If it still is inaccessible you might have to flash TWRP again through fastboot mode using ADB.
bmark240 said:
Hi.
Firstly, you have recovery installed, so that is good.
Some things for you to try:
Can you hold down the power button for longer than 10 seconds. This will clear temporary memory and hard reboot.Press power button & volume 'down' button until you enter TWRP.
Try this firstly.
Can you access ADB at all?
15 second ADB drivers should work.
What Operating system is on your Computer?
TWRP should pop up & be accessible
If you have Windows 10 on. If it doesn't recognize your phone you will have to run an update for Media Center for Windows 10 (64 bit...I'm assuming its not 32bit).
TWRP should be read by your computer if you can access it as it contains the drivers inbuilt.
If it still is inaccessible you might have to flash TWRP again through fastboot mode using ADB.
Click to expand...
Click to collapse
Yes, I have TWRP installed, but cant access it. Shows the TWRP splash screen and then reboots after like 10 seconds or so.
ADB does not see device. Only shows the device during that 10 second TWRP splash screen time, but even then no commands are effective and it just reboots.
Already tried holding down power button for few seconds. No luck.
I already installed all the possible drivers and media feature packs on my Windows 10. Still no luck.
And yes, I am running latest Windows 10 Pro x64.
And no, since I cant access Fastboot, I can not re-flash TWRP either.
kallum7 said:
hi you need to follow this guide :https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
Gonna try that right now. Hopefully that will fix it.
Daaaamn I really frankensteined the sh*t out of this one
I tried that Color OS unbrick method but it did not work. I mean the process itself worked, but the phone would not boot past the logo.
So I grabbed the system.img from old CM13 image, grabbed 2016 modem.img, then placed twrp.img instead of CM recovery and pressed START.
AAAAAND IT WORKED!!! The phone is alive!!!
Now I am in TWRP and I'm going to flash a new ROM. Hopefully everything will go perfectly.
Thanks a lot for your help @kallum7
EDIT: Flashed new ROM. Everything went just fine.
THEVAN3D said:
Daaaamn I really frankensteined the sh*t out of this one
I tried that Color OS unbrick method but it did not work. I mean the process itself worked, but the phone would not boot past the logo.
So I grabbed the system.img from old CM13 image, grabbed 2016 modem.img, then placed twrp.img instead of CM recovery and pressed START.
AAAAAND IT WORKED!!! The phone is alive!!!
Now I am in TWRP and I'm going to flash a new ROM. Hopefully everything will go perfectly.
Thanks a lot for your help @kallum7
EDIT: Flashed new ROM. Everything went just fine.
Click to expand...
Click to collapse
because i had bricked my phone a few months ago and that is how i got my phone back using the colour os
THEVAN3D said:
Phone memory was almost totally full and my sister was still shooting videos on it.
During one shoot the phone turned off and I can't turn it back on again.
Here is my problem, the phone just doesn't boot.
Shows only first screen with 1+ logo and then reboots. Not even the system boot animation.
When I try to enter recovery mode it shows TWRP screen and then reboots again. So I can't even access recovery.
And when I try to enter Fastboot Mode it turns on but the PC won't see it in adb.
What are my options here?
Click to expand...
Click to collapse
This is Bacon Root Toolkit (BRT) by WugFresh's
install file
https://drive.google.com/file/d/1DdFXrHPhVDlSzPqAk1PVfjK_Q0J_UzxO/view?usp=sharing
If you need stock rom
https://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
If you have any question find me on discord FiveO#8241 I will try help you out
FairuzOnn said:
This is Bacon Root Toolkit (BRT) by WugFresh's
install file
https://drive.google.com/file/d/1DdFXrHPhVDlSzPqAk1PVfjK_Q0J_UzxO/view?usp=sharing
If you need stock rom
https://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
If you have any question find me on discord FiveO#8241 I will try help you out
Click to expand...
Click to collapse
Thanks, but I already fixed it.
i had it in the past for some reason too. Managed to fix it using the color os method. Carefully followed the steps until i could flash again. That was a year ago tohugh. There should be some thread around wit some all-in-one solution against bricks.
Hello,
I recently unlocked, flashed TWRP and flashed Pixel Experience onto my Mi Mix 2s. After some time a notification of an available update appeared. I tried to install it but it didn't work. After some troubleshooting it appeared that I couldn't get my device booted into TWRP recovery mode.
I tried reflashing it via fastboot but that didn't work. It did not give any errors upon executing the command lines in the fastboot command prompt but just nothing happened. It just sat still like it was waiting, and waiting, and waiting.
So i thought, let's just reset the phone via the normal settings menu in Android. In hindsight that was quite a dumb move I guess, because after all the phone used to be working. But still I followed through and now it wound up in a bootloop. I can still get it into the bootloader mode, and in fastboot it shows my device when I execute <fasboot devices> but flashing or erasing the recovery doesn't work. It looks as if it sees the phone, can get info from it but is not able or allowed to flash anything to it. But it doesn't give any errors, it just seems to keep waiting on something, I don't know.
I hope any of you guys can help me because searching this forum or googling hasn't helped me getting any further. All topics I found at least had some errors in fastboot/bootloader mode which gave them a direction to go into...
So please help me!
Whoops, I solved it myself. On another laptop it magically worked the first time. Probably an issue with either the USB port or the drivers.
Thread closed at OP request
Hello.
I did something wrong while trying to flash TWRP on my pixel 2, I am now stuck at the bootloader, and I cannot boot System or Recovery. While at the bootloader screen, it says Device State : unlocked. If I try to get to download mode, it says "ERROR: Operation Denied". If I try to go into recovery, it says "ERROR: Slot Unbootable: Load Error". If I try "Start", I get the same error message.
Also, adb or fastboot don't seem to be able to "see" the pixel connected to the computer. I believe my cables are good since I was able to flash Magisk and reflash the whole system with them before bricking it.
Can anyone help?
Thanks!
stanelie said:
Hello.
I did something wrong while trying to flash TWRP on my pixel 2, I am now stuck at the bootloader, and I cannot boot System or Recovery. While at the bootloader screen, it says Device State : unlocked. If I try to get to download mode, it says "ERROR: Operation Denied". If I try to go into recovery, it says "ERROR: Slot Unbootable: Load Error". If I try "Start", I get the same error message.
Also, adb or fastboot don't seem to be able to "see" the pixel connected to the computer. I believe my cables are good since I was able to flash Magisk and reflash the whole system with them before bricking it.
Can anyone help?
Thanks!
Click to expand...
Click to collapse
happened to my walleye too , and managed to bring it back to life . check this thread for a possible solution. https://forum.xda-developers.com/pixel-2/help/december-factory-image-to-broken-t3875213
Thanks!
I missed that thread while researching this issue.
I will try these things when I get back from work next week.
Thanks again!
stanelie said:
Thanks!
I missed that thread while researching this issue.
I will try these things when I get back from work next week.
Thanks again!
Click to expand...
Click to collapse
Just as a reference for anyone else who needs the fix and can't be bothered opening another thread.
SOLUTION: At the menu where it is stuck and saying device fail etc, plug in your usb cable to the mobile, press and hold the POWER button for 10 seconds, it will now recognise your phone under fastboot.
Once that is cleared, it's pretty much straightforward flashing latest pixel 2 image via fastboot and problem solved.
sidenote: Issue came with anyone who tried to flash december security updates and above as of what I heard.
I will try that, thanks.
So, several things :
Holding down the power button had no effect other than restarting the boot menu, but Fastboot never became available.
Opening up the phone and disconnecting the battery and reconnecting it made Fastboot available again. This would be in line with other users that let the phone battery discharge completely before regaining fastboot access.
Sidenote : opening up this phone is not for the faint of heart. I managed to damage something on the motherboard doing so (probably a static electricity discharge), the screen ended up displaying gibberish. I was able to salvage my phone by replacing the motherboard. I had ordered a replacement motherboard when I thought all was lost with no fastboot, and I had it on hand. Expensive little sucker...
stanelie said:
Hello.
I did something wrong while trying to flash TWRP on my pixel 2, I am now stuck at the bootloader, and I cannot boot System or Recovery. While at the bootloader screen, it says Device State : unlocked. If I try to get to download mode, it says "ERROR: Operation Denied". If I try to go into recovery, it says "ERROR: Slot Unbootable: Load Error". If I try "Start", I get the same error message.
Also, adb or fastboot don't seem to be able to "see" the pixel connected to the computer. I believe my cables are good since I was able to flash Magisk and reflash the whole system with them before bricking it.
Can anyone help?
Thanks!
Click to expand...
Click to collapse
Same thing happened to me except I never even tried to root. Just pulled the phone out of my pocket, and the little Android dude was belly up. It's showing device locked - and although I had it in Dev. mode from weeks back (thought USB Debugging was enabled) it fails to respond to adb commands, boot-loader mode, etc.
...Looks like Google laid an egg with this one.
Pixel 2 - "ERROR: Slot Unbootable: Load Error"
If you get the above error you will find that you cannot boot into recovery and the phone stays in the bootloader screen each time you try to start the phone. If your bootloader is unlocked you might be able to recover your phone to flash a stock image and revive. My problem started when I tried to restore a nandroid backup after trying out Android Q beta 1. I got the error mentioned above.
Most of the people recommended that I get a replacement from Google support as they had tried everything but it didn't work. Well right here in XDA Pixel 2 forum there is a solution waiting to be used. I am reproducing it from the post titled
"December factory image seems to have broken fastboot enumeration"
Quote
A possible way to resurrect a bricked Pixel 2...
Hey guys, I have just been able to get mine alive. The device started to be recognized (USB/fastboot) after about 10 unsuccessful attempts to start the system: "Start", from bootloader.
So what exactly happened and what I did:
1. Bricked a Pixel 2.
2. It started into bootloader and showed the "slot unbootable" error.
3. The device was not recognized by any of my machines at all, lsusb did not show anything new in the system, and, respectively, fastboot did not see the device.
4. The default option in the bootloader is "Start" if I remember correctly. So I just pressed the power button and did not release it until I noticed a vibration. It were about 10 unsuccessful attempts of system loading before that vibration.
5. Right after that vibration I connected a generic (NONAME) USB-C <-> USB-A cable to both the device and my Linux machine, and fortunately the device was recognized by the system and fastboot was able to detect the device correctly. So I flashed the a factory image, and it went just fine.
Unquote
Let me confirm that this works. I kept the power button down while the phone was connected via USB to the PC for at least 5 mins. During several reboots suddenly I got a beep from the PC which indicated that ADB was working. I flashed a stock image and voila the pixel 2 is back in operation.
Hope this helps several other people who might have this problem.
ashokabs said:
If you get the above error you will find that you cannot boot into recovery and the phone stays in the bootloader screen each time you try to start the phone. If your bootloader is unlocked you might be able to recover your phone to flash a stock image and revive. My problem started when I tried to restore a nandroid backup after trying out Android Q beta 1. I got the error mentioned above.
Most of the people recommended that I get a replacement from Google support as they had tried everything but it didn't work. Well right here in XDA Pixel 2 forum there is a solution waiting to be used. I am reproducing it from the post titled
"December factory image seems to have broken fastboot enumeration"
Quote
A possible way to resurrect a bricked Pixel 2...
Hey guys, I have just been able to get mine alive. The device started to be recognized (USB/fastboot) after about 10 unsuccessful attempts to start the system: "Start", from bootloader.
So what exactly happened and what I did:
1. Bricked a Pixel 2.
2. It started into bootloader and showed the "slot unbootable" error.
3. The device was not recognized by any of my machines at all, lsusb did not show anything new in the system, and, respectively, fastboot did not see the device.
4. The default option in the bootloader is "Start" if I remember correctly. So I just pressed the power button and did not release it until I noticed a vibration. It were about 10 unsuccessful attempts of system loading before that vibration.
5. Right after that vibration I connected a generic (NONAME) USB-C <-> USB-A cable to both the device and my Linux machine, and fortunately the device was recognized by the system and fastboot was able to detect the device correctly. So I flashed the a factory image, and it went just fine.
Unquote
Let me confirm that this works. I kept the power button down while the phone was connected via USB to the PC for at least 5 mins. During several reboots suddenly I got a beep from the PC which indicated that ADB was working. I flashed a stock image and voila the pixel 2 is back in operation.
Hope this helps several other people who might have this problem.
Click to expand...
Click to collapse
I don't even know how to thank you. I almost had a heart attack watching my Pixel bricked. Thanks man!
Save my day! I just keep pressing power button and fastboot response finally!
Can this be done if the device is locked?
_Kalyan said:
I don't even know how to thank you. I almost had a heart attack watching my Pixel bricked. Thanks man!
Click to expand...
Click to collapse
Does ur bootloader locked or unlocked?
---------- Post added at 11:36 AM ---------- Previous post was at 11:36 AM ----------
ashokabs said:
If you get the above error you will find that you cannot boot into recovery and the phone stays in the bootloader screen each time you try to start the phone. If your bootloader is unlocked you might be able to recover your phone to flash a stock image and revive. My problem started when I tried to restore a nandroid backup after trying out Android Q beta 1. I got the error mentioned above.
Most of the people recommended that I get a replacement from Google support as they had tried everything but it didn't work. Well right here in XDA Pixel 2 forum there is a solution waiting to be used. I am reproducing it from the post titled
"December factory image seems to have broken fastboot enumeration"
Quote
A possible way to resurrect a bricked Pixel 2...
Hey guys, I have just been able to get mine alive. The device started to be recognized (USB/fastboot) after about 10 unsuccessful attempts to start the system: "Start", from bootloader.
So what exactly happened and what I did:
1. Bricked a Pixel 2.
2. It started into bootloader and showed the "slot unbootable" error.
3. The device was not recognized by any of my machines at all, lsusb did not show anything new in the system, and, respectively, fastboot did not see the device.
4. The default option in the bootloader is "Start" if I remember correctly. So I just pressed the power button and did not release it until I noticed a vibration. It were about 10 unsuccessful attempts of system loading before that vibration.
5. Right after that vibration I connected a generic (NONAME) USB-C <-> USB-A cable to both the device and my Linux machine, and fortunately the device was recognized by the system and fastboot was able to detect the device correctly. So I flashed the a factory image, and it went just fine.
Unquote
Let me confirm that this works. I kept the power button down while the phone was connected via USB to the PC for at least 5 mins. During several reboots suddenly I got a beep from the PC which indicated that ADB was working. I flashed a stock image and voila the pixel 2 is back in operation.
Hope this helps several other people who might have this problem.
Click to expand...
Click to collapse
Works on bootloader state locked or not?
SoKa1993 said:
Does ur bootloader locked or unlocked?
---------- Post added at 11:36 AM ---------- Previous post was at 11:36 AM ----------
Works on bootloader state locked or not?
Click to expand...
Click to collapse
If the boot loader is locked look for a script for unlocking the bootloader from recovery or bootloader state. I did find it but cannot remember. My bootloader was unlocked so I did not have to use it.
ashokabs said:
Pixel 2 - "ERROR: Slot Unbootable: Load Error"
If you get the above error you will find that you cannot boot into recovery and the phone stays in the bootloader screen each time you try to start the phone. If your bootloader is unlocked you might be able to recover your phone to flash a stock image and revive. My problem started when I tried to restore a nandroid backup after trying out Android Q beta 1. I got the error mentioned above.
Most of the people recommended that I get a replacement from Google support as they had tried everything but it didn't work. Well right here in XDA Pixel 2 forum there is a solution waiting to be used. I am reproducing it from the post titled
"December factory image seems to have broken fastboot enumeration"
Quote
A possible way to resurrect a bricked Pixel 2...
Hey guys, I have just been able to get mine alive. The device started to be recognized (USB/fastboot) after about 10 unsuccessful attempts to start the system: "Start", from bootloader.
So what exactly happened and what I did:
1. Bricked a Pixel 2.
2. It started into bootloader and showed the "slot unbootable" error.
3. The device was not recognized by any of my machines at all, lsusb did not show anything new in the system, and, respectively, fastboot did not see the device.
4. The default option in the bootloader is "Start" if I remember correctly. So I just pressed the power button and did not release it until I noticed a vibration. It were about 10 unsuccessful attempts of system loading before that vibration.
5. Right after that vibration I connected a generic (NONAME) USB-C <-> USB-A cable to both the device and my Linux machine, and fortunately the device was recognized by the system and fastboot was able to detect the device correctly. So I flashed the a factory image, and it went just fine.
Unquote
Let me confirm that this works. I kept the power button down while the phone was connected via USB to the PC for at least 5 mins. During several reboots suddenly I got a beep from the PC which indicated that ADB was working. I flashed a stock image and voila the pixel 2 is back in operation.
Hope this helps several other people who might have this problem.
Click to expand...
Click to collapse
I have same problem. I use Pixel 2 and Fedora. My question is, what i exactly should do? I mean the steps. I didn't get that beep from my laptop. But I got the vibration when I hold the power button when it's not connected to USB. Please Help me.
Sorry my english isn't that good.