Hi, I really need your assistance for my pixel. I locked my bootloader after unrooting my phone. This process totally bricked my phone(I can't even get to the booting process of the phone) (I get a message saying that my phone is corrupt). I am able to gain access to my fastboot. So I was wondering if there was a way for me to flash the factory image to my phone and get it to work again. Please of there is anything you can do, please help me.
Its_joey_k23 said:
Hi, I really need your assistance for my pixel. I locked my bootloader after unrooting my phone. This process totally bricked my phone(I can't even get to the booting process of the phone) (I get a message saying that my phone is corrupt). I am able to gain access to my fastboot. So I was wondering if there was a way for me to flash the factory image to my phone and get it to work again. Please of there is anything you can do, please help me.
Click to expand...
Click to collapse
I'm really afraid there's nothing you can do. Before relocking the bootloader, you must go back to an approved stock firmware. (See, when you rooted it, you changed it.)
quangtran1 said:
I'm really afraid there's nothing you can do. Before relocking the bootloader, you must go back to an approved stock firmware. (See, when you rooted it, you changed it.)
Click to expand...
Click to collapse
I unrooted my device, so then after I can lock my bootloader. I'm just wondering if that's how I was supposed to do it.
If you have downloaded the full image from Google servers, try if you can fastboot using the boot image from the full image. It that boots your phone, you could try enabling unlock, get into fastboot to unlock for flashing. You can then flash the full image from unlocked fastboot
hackworks said:
If you have downloaded the full image from Google servers, try if you can fastboot using the boot image from the full image. It that boots your phone, you could try enabling unlock, get into fastboot to unlock for flashing. You can then flash the full image from unlocked fastboot
Click to expand...
Click to collapse
Is there any way you could lead my step by step. I don't want to screw up my phone even more. + I'm new to the community and don't know much.
You can use the fastboot continue command.
This will boot up your phone normally and then you will be able to go to developer settings and enable oem unlocking again.
After this you will be able to unlock from fastboot again.
http://forum.xda-developers.com/pixel/help/accomplished-hardbricked-pixel-d-t3516717
Its_joey_k23 said:
Is there any way you could lead my step by step. I don't want to screw up my phone even more. + I'm new to the community and don't know much.
Click to expand...
Click to collapse
If you can put your phone in fastboot mode, you're not bricked yet.
hackworks said:
If you have downloaded the full image from Google servers, try if you can fastboot using the boot image from the full image. It that boots your phone, you could try enabling unlock, get into fastboot to unlock for flashing. You can then flash the full image from unlocked fastboot
Click to expand...
Click to collapse
You saved my life! Thank you.
Related
Hi folks, I just got a Rogers Nexus S 1020a off a buddy that is hopefully just soft-bricked. It won't boot past the Google logo. I can however get into the 'unlock bootloader?' screen, but I am not given the option to unlock it. I can get into recovery, but a factory reset does not fix the problem.
Can anybody offer any suggestions? Is there a one-click stock recovery method that works without actually being able to boot up the device?
When trying to run the ADB command to unlock it, I get "The program can't start because AdbWinApi.dll is missing"
amace04 said:
Hi folks, I just got a Rogers Nexus S 1020a off a buddy that is hopefully just soft-bricked. It won't boot past the Google logo. I can however get into the 'unlock bootloader?' screen, but I am not given the option to unlock it. I can get into recovery, but a factory reset does not fix the problem.
Can anybody offer any suggestions? Is there a one-click stock recovery method that works without actually being able to boot up the device?
When trying to run the ADB command to unlock it, I get "The program can't start because AdbWinApi.dll is missing"
Click to expand...
Click to collapse
So the bootloader is unlocked? Is recovery CWM or TWRP or stock?
jayjay3333 said:
So the bootloader is unlocked? Is recovery CWM or TWRP or stock?
Click to expand...
Click to collapse
Sorry... Is locked, completely stock. I'm going it's now hardware failure, but I can get into bootloader which leads me to believe is a soft brick
**EDIT***
I got it booted, took a little playing around. I can't get Windows to recognize it though. Can't run the one-click root, won't recognize adb commands. Can't do a factory wipe.
What do you think? Device a goner? Any way to save it?
So I bought my shield tablet back in March, used it until about may I think. Was browsing the internet then it suddenly crashed and got stuck on the Nvidia boot screen. tried to reboot several times. Nothing. So I forgot about it and thought I would just google the reset option later when I had time. Now since June I have tried everything! From factory reset to fast boot and adb my pc won't even recognize my tablet. Also I never turned on usb dbugging cause I didn't even know what that was. I even gave it to the IT guys at work and they couldn't fix it. Now after reading everything there is to read on this problem and trying to fix it myself I'm stuck on the no command screen with the dead android robot. And now I hear there is a recall do to the battery, I can't even check what type I have. So if someone can please help me I would be much appreciative. Also this happened after updating to the latest OS.
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Can you flash twrp and boot to it?
Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Hello,
Did you use "Fastboot flash recovery.img" as your command line??
I believe it is "Fastboot flash recovery recovery.img"
If you were able to unlock bootloader you're on the right track.
Sent from a Locked Bootloader
Yes I used "fastboot flash recovery recovery.img" but every command after that keeps telling me "failed to write file"
danjull said:
Can you flash twrp and boot to it?
Click to expand...
Click to collapse
I'm a complete noob when it comes to this stuff, what is twrp? Haha
Ace0169 said:
I'm a complete noob when it comes to this stuff, what is twrp? Haha
Click to expand...
Click to collapse
TWRP (Team Win Recovery Project) is a custom recovery that you can flash on your device. You can flash it like the stock recovery over fastboot. With TWRP you can make full system backups, installing roms or other stuff, wipe partitions and more. Keep trying to install the drivers on your pc. Try to use another usb slot or boot your pc into test mode to install the driver. If you can still access the bootloader, you have really good chances to rescue your device.
Okay will try that. Thanks man.
Ace0169 said:
Okay will try that. Thanks man.
Click to expand...
Click to collapse
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5
Mojar7070 said:
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5
Click to expand...
Click to collapse
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader
Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
Those official nVidia recovery images come with smaller .img files such as recovery.img, system.img, etc. You'll need to flash those one by one ("fastboot flash recovery recovery.img", then run "fastboot flash system system.img", etc. etc.) or you can just run the flashall script that I think is included in the nVidia images.
Otherwise, if you want to flash TWRP, you'll need to download the TWRP recovery (you can rename it to "twrp-recovery.zip"). Then you'll need to "fastboot flash twrp-recovery.zip" in order to flash the twrp recovery to your tablet.
Mojar7070 said:
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader
Click to expand...
Click to collapse
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.
Ace0169 said:
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.
Click to expand...
Click to collapse
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5
Mojar7070 said:
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5
Click to expand...
Click to collapse
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?
Ace0169 said:
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?
Click to expand...
Click to collapse
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.
koop1955 said:
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.
Click to expand...
Click to collapse
Select "fastboot protocol"? Is that correct?
Ace0169 said:
Select "fastboot protocol"? Is that correct?
Click to expand...
Click to collapse
So i selected "fastboot protocol" it blipped for a second then brought me back to the bootloader. tried flashing again and once i reached the fastboot flash system system.img it said write failed again. did it not engage the "fastboot protocol"?
Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.
koop1955 said:
Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.
Click to expand...
Click to collapse
@Ace0169 Same, not sure what else to tell you. Sorry sir.
Sent from a Locked Bootloader
After reading the news that a new method had been found for Verizon/EE-UK Google Pixel (Sailfish) Phones to unlock the Bootloader - I decided to do so and then proceed to flash Magisk for root and other benefits however as there was recently a new update which was showing as 'Failed to Install'.
Of cause I wanted to update the device so I attempted to re-lock the Bootloader using 'fastboot flashing lock' and proceeding to select Yes from the prompt. Which seemed to be acceptable and worked to lock the Bootloader.
Now my phone is stuck in a crazy boot-loop where by the phone will turn on - flash the Google logo on the white background for a split second then shut itself down and repeat.
Does anybody have any tips for me to recover the phone from this awful state?
Mr Ian said:
After reading the news that a new method had been found for Verizon/EE-UK Google Pixel (Sailfish) Phones to unlock the Bootloader - I decided to do so and then proceed to flash Magisk for root and other benefits however as there was recently a new update which was showing as 'Failed to Install'.
Of cause I wanted to update the device so I attempted to re-lock the Bootloader using 'fastboot flashing lock' and proceeding to select Yes from the prompt. Which seemed to be acceptable and worked to lock the Bootloader.
Now my phone is stuck in a crazy boot-loop where by the phone will turn on - flash the Google logo on the white background for a split second then shut itself down and repeat.
Does anybody have any tips for me to recover the phone from this awful state?
Click to expand...
Click to collapse
Man, when you lock the bootloader you need to make sure you're 100% back on stock without any modifications flashed. Seems to me you tried locking while having magisk flashed.
Try to see if you're able to get into recovery. Get into bootloader menu by pressing power button+volume down and the press volume upp until you get to recovery and then press power button. If you're able to get into recovery then download the full ota image for Google pixel sailfish from here https://developers.google.com/android/ota and then while you're in there should be an option to update using adb. You need to adb sideload the update from your computer to your phone. I know this should work on a non Verizon phone but I hope and assume that is what's needed this time. If you're not able to get into recovery and your bootloader is still locked then you pretty much have a bricked device.
Arju said:
Man, when you lock the bootloader you need to make sure you're 100% back on stock without any modifications flashed. Seems to me you tried locking while having magisk flashed.
Try to see if you're able to get into recovery. Get into bootloader menu by pressing power button+volume down and the press volume upp until you get to recovery and then press power button. If you're able to get into recovery then download the full ota image for Google pixel sailfish from here removed-link and then while you're in there should be an option to update using adb. You need to adb sideload the update from your computer to your phone. I know this should work on a non Verizon phone but I hope and assume that is what's needed this time. If you're not able to get into recovery and your bootloader is still locked then you pretty much have a bricked device.
Click to expand...
Click to collapse
At the minute I've taken it to a Phone shop hoping they will be able to figure a way to get to the recovery menu - baring in mind I had TWRP flashed.
Yeah, It will go to the Bootloader menu but when trying to go into recovery it will just repeat the same process as before where by it will flash the Google splash-screen then restart. Any notes on how to go about hard flashing the image?
have you tried fastboot boot twrp.img? does it bootloop aswell? if so, you might have hard bricked your pixel... last solution is to try flash stock image and then try again with stock recovery / twrp img.
Mr Ian said:
At the minute I've taken it to a Phone shop hoping they will be able to figure a way to get to the recovery menu - baring in mind I had TWRP flashed.
Yeah, It will go to the Bootloader menu but when trying to go into recovery it will just repeat the same process as before where by it will flash the Google splash-screen then restart. Any notes on how to go about hard flashing the image?
Click to expand...
Click to collapse
If you can't access stock recovery and your bootloader is locked then your device is pretty much hard bricked unfortunately. Don't think the phone shop would figure it out, they might change the motherboard as a solution if they don't have the right tools to reflash on a deeper level. Hope they figure it out. Please let us know if they managed to fix it. If not then someone else might have some suggestions. I'll try to think of something else.
Try either of these commands to see if you can unlock the bootloader again:
fastboot oem unlock
or
Code:
fastboot flashing unlock
And then try what the post above me suggests.
Hey, did you ever figure out a solution to this? I did the same thing to myself today...
any solution??
---------- Post added at 03:49 PM ---------- Previous post was at 03:48 PM ----------
Mr Ian said:
After reading the news that a new method had been found for Verizon/EE-UK Google Pixel (Sailfish) Phones to unlock the Bootloader - I decided to do so and then proceed to flash Magisk for root and other benefits however as there was recently a new update which was showing as 'Failed to Install'.
Of cause I wanted to update the device so I attempted to re-lock the Bootloader using 'fastboot flashing lock' and proceeding to select Yes from the prompt. Which seemed to be acceptable and worked to lock the Bootloader.
Now my phone is stuck in a crazy boot-loop where by the phone will turn on - flash the Google logo on the white background for a split second then shut itself down and repeat.
Does anybody have any tips for me to recover the phone from this awful state?
Click to expand...
Click to collapse
Did you managed to unlock it???
You can unlock the bootloader with htc-fastboot if you have a bricked android 7-8.
They patched it on Android 9.
On android 9 your only chance is to reflash it in edl mode. Anyone here who can help me to enter edl mode with my pixel?
Help. I was so excited for my new phone that I made a n00b mistake - Booted into TWRP and flashed the TWRP zip to permanently install before I remembered to allow oem unlocking in the OS - Developer Setting. Now my phone won't boot because of the custom recovery, I can't flash anything because the bootloader is locked, and I can't get into the OS to allow unlocking.
The only thing I can do is fastboot boot twrp.
How do I fix this?
BikerFry said:
Help. I was so excited for my new phone that I made a n00b mistake - Booted into TWRP and flashed the TWRP zip to permanently install before I remembered to allow oem unlocking in the OS - Developer Setting. Now my phone won't boot because of the custom recovery, I can't flash anything because the bootloader is locked, and I can't get into the OS to allow unlocking.
The only thing I can do is fastboot boot twrp.
How do I fix this?
Click to expand...
Click to collapse
Try flashing the stock boot img, it should but back stock recovery, you should be able to do it in fastboot too.
BikerFry said:
Help. I was so excited for my new phone that I made a n00b mistake - Booted into TWRP and flashed the TWRP zip to permanently install before I remembered to allow oem unlocking in the OS - Developer Setting. Now my phone won't boot because of the custom recovery, I can't flash anything because the bootloader is locked, and I can't get into the OS to allow unlocking.
The only thing I can do is fastboot boot twrp.
How do I fix this?
Click to expand...
Click to collapse
Follow steps here https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Sent from my OnePlus6 using XDA Labs
I can't flash anything. I get "Failed remote flashing is not allowed in lock state".
I can fastboot boot twrp so maybe could try flashing that way, but I can't get the phone to show up in windows explorer to transfer any files.
Wrong forum.
matze19999 said:
Wrong forum.
Click to expand...
Click to collapse
Sorry about that.
Might have just made a little progress. Learned the ADB Push command, loading an ota.zip and a boot image now. Hopefully can flash one or the other or both via twrp. Fingers crossed. Thanks either way guys.
tried Flash Image - boot image I had downloaded. It flashed successfully lol but I still can't boot the OS. And now I can't fastboot boot twrp either. ****. What have I done? lol. Come on it's android there has to be a way.
I appear to now be officially ****ed. Must have somehow been the wrong boot image, now I can't even boot into TWRP. I think I'm dead in the water. Can't flash anything, can't boot into TWRP. Any ideas? Will happily paypal a few bucks to anyone who can un**** me.
BikerFry said:
tried Flash Image - boot image I had downloaded. It flashed successfully lol but I still can't boot the OS. And now I can't fastboot boot twrp either. ****. What have I done? lol. Come on it's android there has to be a way.
I appear to now be officially ****ed. Must have somehow been the wrong boot image, now I can't even boot into TWRP. I think I'm dead in the water. Can't flash anything, can't boot into TWRP. Any ideas? Will happily paypal a few bucks to anyone who can un**** me.
Click to expand...
Click to collapse
have you tried the unbricking tool
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Will try it now. Thanks!
BikerFry said:
Will try it now. Thanks!
Click to expand...
Click to collapse
how are getting on with the unbrick tool ??
hallelujia the unbrick tool worked!!! So excited to be back making playing with the new toy! I was sure I was screwed, somehow didn't come across that tool in my googling. Thanks man. Imma kick a couple bucks your way with that donate button. Saved me from sending it back to oneplus and going a couple weeks without the new phone.
Now carefully...
BikerFry said:
hallelujia the unbrick tool worked!!! So excited to be back making playing with the new toy! I was sure I was screwed, somehow didn't come across that tool in my googling. Thanks man. Imma kick a couple bucks your way with that donate button. Saved me from sending it back to oneplus and going a couple weeks without the new phone.
Now carefully...
Click to expand...
Click to collapse
its fine my friend dont need the money just glad it helped ya :good::good::good::good:
Well thank you very much. I'm not too proud to freely admit I'm a happy kid with a new toy now. Thanks!
My husband's phone deviced to completely shut down. When he tries to use the bootloader, it shows a message about being corrupt and not trusted. Any idea how to fix this?
-Selecting Bootloader, Recovery, Restart and Off all take him back to the same screen about corrupted phone.
Phone will go into FASTBOOT but will not go into RECOVERY mode.
kimball_mom said:
My husband's phone deviced to completely shut down. When he tries to use the bootloader, it shows a message about being corrupt and not trusted. Any idea how to fix this?
-Selecting Bootloader, Recovery, Restart and Off all take him back to the same screen about corrupted phone.
Phone will go into FASTBOOT but will not go into RECOVERY mode.
Click to expand...
Click to collapse
This is what a half unlocked bootloader looks like. What device and build?
mattie_49 said:
This is what a half unlocked bootloader looks like. What device and build?
Click to expand...
Click to collapse
OnePlus 9 for TMobile.
If he's rooted, that means he didn't unlock the bootloader first. This is what causes that and I've done it myself.
I don't know if either of these will work but worth a shot in this order.
Option 1: *FLASH* UNMODIFIED stock boot.img via fastboot flash boot.img (whatever your filename is, or just drag and drop it in the adb cmd window)
2: Use the TMobile MSM tool to revert back to stock. I believe I tried this on the 6t and it didn't fix the issue somehow but in theory it should cause this is how OnePlus's legendary horrid tech support does it.