I have searched and tried different things but I'm getting nowhere. I have been running Purity rom on this for a while but when I woke up this morning, I found my screen black and only being able to boot to the bootloader and and google screen (which quickly goes away and goes black again). When I tried to go to recovery at first I believe it was just shutting off. Now it goes to a light black screen.
The first thing I did was flashed the factory image .bat file and everything seemed to go ok but when trying to go to recovery after it went to the light black screen. I turned it off and it booted to the Google screen then off again. Then it booted to the google screen and it froze that way. I can always get it back to the bootloader screen and got it to recovery once by flashing TWRP again using ADB.
TWRP opened once and I tried to do a factory reset but it couldn't find anything and couldn't mount to anything. I got it back to the bootloader again but the recovery has disappeared again. I tried to flash the factory image again but it definitely failed this time.
Please help.
aburn95 said:
I have searched and tried different things but I'm getting nowhere. I have been running Purity rom on this for a while but when I woke up this morning, I found my screen black and only being able to boot to the bootloader and and google screen (which quickly goes away and goes black again). When I tried to go to recovery at first I believe it was just shutting off. Now it goes to a light black screen.
The first thing I did was flashed the factory image .bat file and everything seemed to go ok but when trying to go to recovery after it went to the light black screen. I turned it off and it booted to the Google screen then off again. Then it booted to the google screen and it froze that way. I can always get it back to the bootloader screen and got it to recovery once by flashing TWRP again using ADB.
TWRP opened once and I tried to do a factory reset but it couldn't find anything and couldn't mount to anything. I got it back to the bootloader again but the recovery has disappeared again. I tried to flash the factory image again but it definitely failed this time.
Please help.
Click to expand...
Click to collapse
@bitdomo might be able to help you lol
Might be bad eMMC or something?
when youre flashing recovery, which command are you using.. fastboot boot recovery recoveryname.img or fastboot flash recovery recoveryname.img?
aburn95 said:
I have searched and tried different things but I'm getting nowhere. I have been running Purity rom on this for a while but when I woke up this morning, I found my screen black and only being able to boot to the bootloader and and google screen (which quickly goes away and goes black again). When I tried to go to recovery at first I believe it was just shutting off. Now it goes to a light black screen.
The first thing I did was flashed the factory image .bat file and everything seemed to go ok but when trying to go to recovery after it went to the light black screen. I turned it off and it booted to the Google screen then off again. Then it booted to the google screen and it froze that way. I can always get it back to the bootloader screen and got it to recovery once by flashing TWRP again using ADB.
TWRP opened once and I tried to do a factory reset but it couldn't find anything and couldn't mount to anything. I got it back to the bootloader again but the recovery has disappeared again. I tried to flash the factory image again but it definitely failed this time.
Please help.
Click to expand...
Click to collapse
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
simms22 said:
when youre flashing recovery, which command are you using.. fastboot boot recovery recoveryname.img or fastboot flash recovery recoveryname.img?
Click to expand...
Click to collapse
Hey I'm using "fastboot flash recovery recovery.img" and that's what I've used in the past. I've had a fully functioning rom with fully functioning recovery for a while until yesterday.
bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Ok thanks I'll try this and check the text in fastboot after work today. Thanks for the responses guys.
After reading some more last night I'm afraid it's an emmc problem but I like to be proven wrong sometimes.
Maybe also try this?
http://forum.xda-developers.com/showthread.php?t=2577447
beekay201 said:
Maybe also try this?
http://forum.xda-developers.com/showthread.php?t=2577447
Click to expand...
Click to collapse
I actually have that thread open on my computer. It was my next attempt of repair before starting the thread late last night. Thanks for the suggestion I will certainly try it.
Update: I tried pushing Philz recovery to the phone which seemed to work fine until I selected go to recovery mode. It just went back to that barely light black screen. I'll try again when I get home. Going to try Bitdomo's advice about locking bootloader first.
bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Out of curiosity what's the reason for using two brands, or were they just available so they were used?
bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Bitdomo I'm trying the Flashtool but it's staying at 0% on the firmware update and nothing is popping up on computer or in Device Manager. Had no connection issues prior to the brick or with adb/fastboot. My Ports aren't evening showing at all in DM even if I select show hidden devices.
aburn95 said:
How do I lock the bootloader without being able to put the .zip on my internal memory?
Click to expand...
Click to collapse
In fastboot type
fastboot oem lock
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
In fastboot type
fastboot oem lock
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I honestly wanted to do that but it seemed too easy. I was trying to lock it like I did before when i had to send original back to T-Mobile. Sorry and thanks.
bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Ok so it stayed locked so that's a start. I'm back in download mode again but it's staying at 0% and nothing on computer.
I tried to re-download the factory images and flash again using adb. It failed again. Here's a picture of what happened:
Unzip the zip and use manual flash commands. Clikc the link in my signature and read my "adb and fastboot. What is it?" thread of you're unsure of the commands.
Sent from my Nexus 5 using Tapatalk
aburn95 said:
I tried to re-download the factory images and flash again using adb. It failed again. Here's a picture of what happened:
Click to expand...
Click to collapse
You have "remote: flash write failure" error. It means your emmc (internal storage) is broken and you cannot modify the data on it. You have to rma your device.
Just for matter of research can you enter to fastboot and post the variable line here?
Mine is: hammerhead D821(H) 16GB
bitdomo said:
You have "remote: flash write failure" error. It means your emmc (internal storage) is broken and you cannot modify the data on it. You have to rma your device.
Just for matter of research can you enter to fastboot and post the variable line here?
Mine is: hammerhead D821(H) 16GB
Click to expand...
Click to collapse
Sorry I meant to tell you yesterday... D820H 16GB. Should I still be able to toggle the tamper tag so they will take it back with no problems? Or am I screwed?
aburn95 said:
Sorry I meant to tell you yesterday... 820H. Should I still be able to toggle the tamper so they will take it back with no problems? Or am I screwed?
Click to expand...
Click to collapse
You should be able to if you managed to lock the bootloader. The name of the zip does not came into my mind which you have to flash, but you have to do it with the adb sideload command because you cant copy anything to your phone, or use adb push command to push it to the "/" folder because it is mounted to the ram which you can write not like your storage . If you bought your phone from google it does not matter you have tamper flag set to 1.
bitdomo said:
You should be able to if you managed to lock the bootloader. The name of the zip does not came into my mind which you have to flash, but you have to do it with the adb sideload command because you cant copy anything to your phone, or use adb push command to push it to the "/" folder because it is mounted to the ram which you can write not like your storage . If you bought your phone from google it does not matter you have tamper flag set to 1.
Click to expand...
Click to collapse
Ok thanks. I haven't quite figured out the adb sideload function yet. I tried doing it through TWRP but it just sits there and does nothing after selecting. Maybe I'm trying the wrong thing. I got my phone from T-Mobile so I'll need to solve this. Thanks for the help.
This phone is being a real a-hole. I'm trying to boot to stock recovery but it just sits on a screen with a really big android with wiggling antennae. I pressed up+power many times but it stayed that way. So I tried booting to TWRP again and it did but went immediately to an "OpenRecoveryScript," had a little bar at the bottom for a while with some other stuff on the screen, then turned off.
I tried stock recovery again and it went to the little dead android this time but still nothing when I press up+power.
Related
Hi all,
Been given a Nexus S i9023 by my brother who has been "tampering" with it and now it seems a bit messed up.
When booting up - it gets stuck on the "Google" screen with a padlock on it... I can get into fastboot and I can flash recovery but when I attempt to load any recovery - I get that same Google screen with the padlock! I've downloaded a stock rom and even flashed system etc via fastboot but that still gets me nowhere past the damn padlock!!
I've tried to "fastboot boot recovery.img" and I still get the Google screen with the padlock but it says "Fastboot status - OK" on the bottom left.
I've searched and searched but everyone just seems to give tips on how to flash recovery. I know how to flash recovery; it just seem to be going into it though! Could the internal memory be screwed?
Thanks for any advice!
Sounds strange for sure. You try from within the OS? Enable USB debugging and adb reboot recovery.
Doubt it will work but its worth a shot
albundy2010 said:
Sounds strange for sure. You try from within the OS? Enable USB debugging and adb reboot recovery.
Doubt it will work but its worth a shot
Click to expand...
Click to collapse
The phone stops at Google with the padlock on boot! Can't even get into the OS. Going to try to unbrick it and Odin but left my ubuntu laptop at my parents and can't be bothered to go get it... couldn't get it to work booting off cd rom. Kept giving me the "SBL Injection Failure Failed to find device" error booting ubuntu on a CD!
You may have a storage issue.
I seen you tried to flash system and boot recovery with fastboot ( which should have booted) but did you try to flash them all and wipe. The command is fastboot -w update file name.
I think Odin is a windows only tool anyways by the way.
albundy2010 said:
You may have a storage issue.
I seen you tried to flash system and boot recovery with fastboot ( which should have booted) but did you try to flash them all and wipe. The command is fastboot -w update file name.
I think Odin is a windows only tool anyways by the way.
Click to expand...
Click to collapse
No idea why I said Odin - I meant the unbrickable recovery thing.
I tried Odin with a Jig last night; got it into download mode and flashed with odin. Got the same result.
fastboot -w also gives the same issue...
If I have a storage issue - is there any way I can tell?
Basically you can tell by the issues you're having. Doing all the proper stuff to flash images etc and still having a booting/working device.
As far as a actual diagnostic tool I don't know of one. But it sure sounds like a hw issue to me.
I have the following problem: since a few weeks I'm unable to enter recovery.
This is what I do:
- shut down my phone
- press the power button while holding the volume up
- than I get a screen where I can choose from 4 options using the volume controls and selecting an option with the power button
- I select 'Recovery' and press the power button
- I get the usual black screen with Google logo and padlock
- but instead of getting into my recovery, I get a black screen with a Droid lying down, the 'chest' opened and some kind of small warning triangle above it..somebody who knows what I have to do??
Thanks in advance
Pironi90 said:
I have the following problem: since a few weeks I'm unable to enter recovery.
This is what I do:
- shut down my phone
- press the power button while holding the volume up
- than I get a screen where I can choose from 4 options using the volume controls and selecting an option with the power button
- I select 'Recovery' and press the power button
- I get the usual black screen with Google logo and padlock
- but instead of getting into my recovery, I get a black screen with a Droid lying down, the 'chest' opened and some kind of small warning triangle above it..somebody who knows what I have to do??
Thanks in advance
Click to expand...
Click to collapse
Reflash your recovery using fastboot.
polobunny said:
Reflash your recovery using fastboot.
Click to expand...
Click to collapse
And where can I find how to do this? I'm a total newbie for this kind of stuff and I found some hits on google (e.g. http://forum.xda-developers.com/showthread.php?t=1757146) but I'm actually a bit scared to damage my phone or something by doind something wrong or applying some method that's actually made for another device or so.. :s
Pironi90 said:
And where can I find how to do this? I'm a total newbie for this kind of stuff and I found some hits on google (e.g. http://forum.xda-developers.com/showthread.php?t=1757146) but I'm actually a bit scared to damage my phone or something by doind something wrong or applying some method that's actually made for another device or so.. :s
Click to expand...
Click to collapse
Flash custom recovery.img part
http://wiki.cyanogenmod.org/wiki/fastboot#Flash_Custom_Recovery.img
You need ADB (and ADB drivers installed, strongly recommend PDANet Android Drivers) and fastboot executable.
Custom recovery I suggest you use Clockworkmod Recovery.
I imagine your phone is already unlocked?
polobunny said:
I imagine your phone is already unlocked?
Click to expand...
Click to collapse
I think so yes, I could access recovery before if that's what you mean by unlocked
Pironi90 said:
I think so yes, I could access recovery before if that's what you mean by unlocked
Click to expand...
Click to collapse
When u boot on the Google screen on the bottom centre does it have a padlock? If so then it is unlocked.
You are entering recovery. Stock recovery
If you want a custom one either flash with fastboot or if you're rooted with a app. Goo manager. Rom manager etc.
Keep it mind that if you're on a stock ROM the custom recovery gets overwritten back to stock when the phone boots up the os
Q
UselessSniper001 said:
When u boot on the Google screen on the bottom centre does it have a padlock? If so then it is unlocked.
Click to expand...
Click to collapse
Then my phone is unlocked yes
polobunny said:
You need ADB (and ADB drivers installed, strongly recommend PDANet Android Drivers) and fastboot executable.
Custom recovery I suggest you use Clockworkmod Recovery.
I imagine your phone is already unlocked?
Click to expand...
Click to collapse
In installed the drivers and I installed the fastboot executable, but what do I have to do next? If I run the fastboot.exe, it just quickly shows a CMD-window and then disappears.
Edit:
I just discovered that, when I'm at the bootloader (I think it's called that way, the screen where you can select recovery), and I choose to reboot, I get the same 'error' as when I try to enter recovery.
Edit:
Alright, I was able to flash a new recovery, using cmd, but now when I try to enter my recovery, the phone gets stuck at a black screen with Google logo and padlock...
I have same problem as wolverine_2k who made the post. My nexus, can't start, I tried reboot and recovery but didn't work. After reboot or recovery I see Google logo, than Nexus screen and that is it. It didn't move to home screen and it stay with lighting screen all the time till I remove the battery. I can't power off it and don't know what to do. I can't transfer data with my PC (it don't recognize the device - only notice that "unknown device" is connected). Please any ideas?
P.S.: My English is not good, if someone answer do it simple please
Thanks!
Again...
Three days ago, I wake up and the Nexus 5 doesn't work. I reboot it, and it is stuck on the Google logo screen. When I went in the TWRP recovery, I couldn't find nothing. Everything erased. Today I received my PC (Ram problems with it) and I tried to flash the factory image 4.4.4, but, when writing the bootloader, the cmd says "remote: flash write failure".
It is happened one month ago, and I had to send it to a LG Center because nothing worked (here the post)
There is something that I can do or I have to send it again to a LG Center? And why diid it happened again?
Again it's probably dead eMMC lol
Giolte_ said:
Again...
Three days ago, I wake up and the Nexus 5 doesn't work. I reboot it, and it is stuck on the Google logo screen. When I went in the TWRP recovery, I couldn't find nothing. Everything erased. Today I received my PC (Ram problems with it) and I tried to flash the factory image 4.4.4, but, when writing the bootloader, the cmd says "remote: flash write failure".
It is happened one month ago, and I had to send it to a LG Center because nothing worked (here the post)
There is something that I can do or I have to send it again to a LG Center? And why diid it happened again?
Click to expand...
Click to collapse
Emmc is corrupt you have to send it again. Juat coincedence that it happened again
So I have to send again to LG?
Giolte_ said:
So I have to send again to LG?
Click to expand...
Click to collapse
I just said that -.-
Sorry, I have reloaded the page when only Lethargy had posted
Strange thing... I was following this post, and when I do fastboot boot twrp.img it reboots to twrp and it reboots again, and now there is on my screen the SlimKat boot animation since 5 minutes (SlimKat is the rom that I was running 3 days ago)... what I have to do?
Giolte_ said:
Strange thing... I was following this post, and when I do fastboot boot twrp.img it reboots to twrp and it reboots again, and now there is on my screen the SlimKat boot animation since 5 minutes (SlimKat is the rom that I was running 3 days ago)... what I have to do?
Click to expand...
Click to collapse
Sure looks like you have to rma the device again
Sent from my Nexus 5 using XDA Free mobile app
I can't RMA, I buy it from a retail, in fact I have to reset the temper flag, but when I do this it reboots the system...
Giolte_ said:
I can't RMA, I buy it from a retail, in fact I have to reset the temper flag, but when I do this it reboots the system...
Click to expand...
Click to collapse
Have you tried LG Flashtool?
No, I have not understood how to use it..
I have not understood things like the factory version change, and I don't want to brick the phone... there is anything else that I can do?
The phone is already pretty much bricked imo.. Flash write failure means write access to the eMMC has gone kaappuuuttt!
You need to send the device back to LG as already stated by others. It's very unfortunate that this happened to you twice in such a short period.
Sorry for all these posts, but I don't understand this:
I have locked the bootloader, than I unlock it again. When I navigate to start and "click" it, the device opens TWRP recovery and run a process called "Open Recovery" or something like this.
How is it possible? If I unlock the bootloader why the TWRP recovery is always here?
___
Yes Vin, but how can I send it to LG if I don't reset it?
Giolte_ said:
Sorry for all these posts, but I don't understand this:
I have locked the bootloader, than I unlock it again. When I navigate to start and "click" it, the device opens TWRP recovery and run a process called "Open Recovery" or something like this.
How is it possible? If I unlock the bootloader why the TWRP recovery is always here?
___
Yes Vin, but how can I send it to LG if I don't reset it?
Click to expand...
Click to collapse
Locking the bootloading doesn't wipe your recovery. You will need to flash the stock recovery via fastboot to replace twrp. However, I doubt whether you will be able to replace it since the eMMC has gone bad. Anyways, there;'s nothing to loose.. Give it a shot.
I only have to flash the stock recovery in the google factory image 4.4.4 or I have to do particular passages?
Giolte_ said:
I only have to flash the stock recovery in the google factory image 4.4.4 or I have to do particular passages?
Click to expand...
Click to collapse
1. Unlock the bootloader (if it's locked).
2. Flash stock recovery.img via fastboot.
3. Reboot and use command "fastboot boot twrp.img" //This will boot your device into twrp.
4. Sideload this file in twrp: http://forum.xda-developers.com/attachment.php?attachmentid=2467503&d=1387666907
The above file will reset the tamper flag and lock the bootloader!
When I extract the files from the zip, the boot, system and recovery are dated 12/12/2008... is this normal?
Yes..
Ok, last questions... if I'll flash the zip, I have to use in sideload this: "adb sideload cwm-Nexus.BootUnlocker.zip"?
And why, there is "cwm" in the name? Sorry for all these questions, but I don't want to burn my last hope...
Hi,
My Moto G XT1032 was on 5.0.2 when I finally decided to root it. I followed the instructions here (reddit.com/r/MotoG/comments/22mimr/the_guide_to_rooting_the_motog_with_a_howto) and all was going well until right at the end after I installed the supersu zip and rebooted.
Right now, every time I try booting up my phone, it shows the Moto G logo (without the bootloader warning since I flashed the original logo), the Motorola animation, and then my screen goes black. I don't however think it's off, since when I plug my phone into my computer, it's eventually detected (but nothing is there when I open the internal storage; likewise, 'adb devices' reveals nothing attached).
When I use volume down + power, I can reach the fastboot screen, but selecting recovery only brings me to a screen with the text 'no command'. The only strange thing I can recall during the entire root process is that when I was in CWM and making my backup image, the screen was flickering slightly.
Does anyone know what I can try at this point?
Thanks for your time and any help you can provide,
indavidual
indavidual said:
Hi,
My Moto G XT1032 was on 5.0.2 when I finally decided to root it. I followed the instructions here (reddit.com/r/MotoG/comments/22mimr/the_guide_to_rooting_the_motog_with_a_howto) and all was going well until right at the end after I installed the supersu zip and rebooted.
Right now, every time I try booting up my phone, it shows the Moto G logo (without the bootloader warning since I flashed the original logo), the Motorola animation, and then my screen goes black. I don't however think it's off, since when I plug my phone into my computer, it's eventually detected (but nothing is there when I open the internal storage; likewise, 'adb devices' reveals nothing attached).
When I use volume down + power, I can reach the fastboot screen, but selecting recovery only brings me to a screen with the text 'no command'. The only strange thing I can recall during the entire root process is that when I was in CWM and making my backup image, the screen was flickering slightly.
Does anyone know what I can try at this point?
Thanks for your time and any help you can provide,
indavidual
Click to expand...
Click to collapse
You can try reflashing the ROM or restore stock. http://forum.xda-developers.com/showthread.php?t=2542219
dominati said:
You can try reflashing the ROM or restore stock. http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Unfortunately, flashing anything doesn't seem to work (with my cmd open, whatever commands I type give me "error: device not found"). Is there anything else I can try?
indavidual said:
Unfortunately, flashing anything doesn't seem to work (with my cmd open, whatever commands I type give me "error: device not found"). Is there anything else I can try?
Click to expand...
Click to collapse
With the phone off, hold the power and volume down buttons simultaneously for 5 seconds to access the bootloader. From there you can you fastboot commands to restore stock. Find your stock firmware here http://www.filefactory.com/folder/c6cdedc45a775d27
Follow the steps in the guide I posted originally.
Edit: You could also reflash recovery via fastboot. fastboot flash recovery recovery.img
Also the line on your screen is do to Lollipop bootloader. The recovery you are using is probably for KitKat bootloader. There may not be a Lollipop bootloader compatible recovery available for you device yet.
dominati said:
With the phone off, hold the power and volume down buttons simultaneously for 5 seconds to access the bootloader. From there you can you fastboot commands to restore stock.
Follow the steps in the guide I posted originally.
Edit: You could also reflash recovery via fastboot. fastboot flash recovery recovery.img
Also the line on your screen is do to Lollipop bootloader. The recovery you are using is probably for KitKat bootloader. There may not be a Lollipop bootloader compatible recovery available for you device yet.
Click to expand...
Click to collapse
I ended up just flashing cwm, clearing everything, then re-installing super su, and it works Thanks a bunch for your help!
EDIT
Turns out I was two versions of adb/fastboot behind instead of one. Ignore me!
Hey all,
Yesterday I went to flash the factory image on my Pixel 2 that was running unlocked and rooted with Magisk and Snoke kernel, but it failed while trying to erase the cache partition. I found out that I wasn't using the latest fastboot because the Pixel doesn't use a cache partition so I updated and tried again, and the flash-all script seemed to work fine. But when it finished an rebooted the phone, I was back at the bootloader. I tried the start, recovery, and download mode buttons but they all sent me back to the bootloader. If I turn the phone off and plug it into a charger, the charging icon will come up on the screen for a second and then send me to the bootloader.
I tried flashing the files manually, but the process was hit or miss and would either hang forever or return a generic error (either a generic load error or check device console).
I can't boot the alpha TWRP because it returns a generic load/authentication error and quits.
At this point the flash-all will go through the motions and seem to work every time now, but when it reboots I'm back at square one. I can lock and unlock the bootloader and confirm it on the phone screen, I can flash the bootloader, boot, and system images, I can erase those images, I seem to be able to do everything I can usually do in there, but it's almost like my computer says it's working, but the phone isn't actually doing anything. Short of an RMA I'm not entirely sure what to do. Does anyone have any insight?
Click to expand...
Click to collapse
I'm new to pixels phones but i read about the slot a and slot b maybe you have to change the boot to other slot?
There is a tool in development section maybe it can help u some how.
gm007 said:
I'm new to pixels phones but i read about the slot a and slot b maybe you have to change the boot to other slot?
There is a tool in development section maybe it can help u some how.
Click to expand...
Click to collapse
I set the active slot to b and rebooted and I got the warning message that the bootloader was unlocked and to continue, which brought me to the boot logo for a little bit, and then back to the bootloader.
virgilante said:
I set the active slot to b and rebooted and I got the warning message that the bootloader was unlocked and to continue, which brought me to the boot logo for a little bit, and then back to the bootloader.
Click to expand...
Click to collapse
Maybe you need to flash the stock image again in the second slot?
I have faced the same issue and reflash the factory image do not work, is there anyone resolve this?
# updated
https://forum.xda-developers.com/pixel-2/help/fastboot-update-resulted-bricked-device-t3694761
as this thread， just flash every img manually resolved this issue.
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.