Need help, locked up phone - Google Pixel 2 XL Questions & Answers

Long story short, I bought my awesome Pixel 2 XL back in December, right away I unlocked the bootloader, installed TWRP Recovery and rooted it. Since then I have done nothing to the phone , besides app updates, but never updated top the latest security patches pr anything. Partly because being rooted can't take OTA updates, and didn't want to wipe anything flashing new updates.
Tonight, I wanted to get on the latest, I was currently on 3.2.1.0, so I downloaded the 3.2..1.2 zip, rebooted into Recovery, and flashed the zip, and rebooted into Recovery again, all good, on the latest current TWRP version.
I press reboot system, but it keeps going back into Recovery, every time, always reboots back into Recovery for some strange reason ? Doesn't load the system. So I select the other partition A, I was on B, I put it in A, select reboot system, and it just hangs on the white Goggle screen FOREVER. I then get back into Recovery, now I can't even get into Recovery, the swipe right feature not working, acting like it's not registering my input, I can't swipe the arrow to move it. Now it's just stuck on the opening page in Recovery.
Now what ?

Zorachus said:
Long story short, I bought my awesome Pixel 2 XL back in December, right away I unlocked the bootloader, installed TWRP Recovery and rooted it. Since then I have done nothing to the phone , besides app updates, but never updated top the latest security patches pr anything. Partly because being rooted can't take OTA updates, and didn't want to wipe anything flashing new updates.
Tonight, I wanted to get on the latest, I was currently on 3.2.1.0, so I downloaded the 3.2..1.2 zip, rebooted into Recovery, and flashed the zip, and rebooted into Recovery again, all good, on the latest current TWRP version.
I press reboot system, but it keeps going back into Recovery, every time, always reboots back into Recovery for some strange reason ? Doesn't load the system. So I select the other partition A, I was on B, I put it in A, select reboot system, and it just hangs on the white Goggle screen FOREVER. I then get back into Recovery, now I can't even get into Recovery, the swipe right feature not working, acting like it's not registering my input, I can't swipe the arrow to move it. Now it's just stuck on the opening page in Recovery.
Now what ?
Click to expand...
Click to collapse
Fastboot the boot.img from whatever build your on now and let it boot up. That will remove twrp, then you can go back and fastboot twrp again.

[delete

Badger50 said:
Fastboot the boot.img from whatever build your on now and let it boot up. That will remove twrp, then you can go back and fastboot twrp again.
Click to expand...
Click to collapse
Where do I get the December boot.img ?

Zorachus said:
Where do I get the December boot.img ?
Click to expand...
Click to collapse
Go here....https://developers.google.com/android/images
Download the December factory image, extract it, then extract the other zip you'll find, and in there you'll find the boot.img. Then place that in your platform-tools folder and run...fastboot boot boot.img
Then type fastboot reboot, and let the phone boot up. Then go back and fastboot the twrp.img
Once in twrp, flash the twrp installer zip, then custom kernel if you want, and then magisk for root if you want. Question, why are you still on the December build???

I think if you just flash magisk it will boot again. If you were rooted. Someone posted on the twrp thread. To get touch back on twrp just have to adb reboot recovery. Might worth a try.
Sent from my Pixel 2 XL using Tapatalk

Badger50 said:
Go here....https://developers.google.com/android/images
Download the December factory image, extract it, then extract the other zip you'll find, and in there you'll find the boot.img. Then place that in your platform-tools folder and run...fastboot boot boot.img
Then type fastboot reboot, and let the phone boot up. Then go back and fastboot the twrp.img
Once in twrp, flash the twrp installer zip, then custom kernel if you want, and then magisk for root if you want. Question, why are you still on the December build???
Click to expand...
Click to collapse
Ok I am downloading the 1.6GB December file. I will then extract that, and only need to grab the boot.img file from there ? What do you mean when you say "then extract the other zip you'll find" ?
And then connect my phone to my PC, and open Command Prompt, and run these lines. I need to be in fastboot mode I assume ?
"

Zorachus said:
Ok I am downloading the 1.6GB December file. I will then extract that, and only need to grab the boot.img file from there ? What do you mean when you say "then extract the other zip you'll find" ?
And then connect my phone to my PC, and open Command Prompt, and run these lines. I need to be in fastboot mode I assume ?
"
Click to expand...
Click to collapse
There's another large zip that you'll find after you extract the factory image. It is in that zip that you'll find the boot.img. And yes, you'll need to be in fastboot mode to install the boot.img :good:

Badger50 said:
There's another large zip that you'll find after you extract the factory image. It is in that zip that you'll find the boot.img. And yes, you'll need to be in fastboot mode to install the boot.img :good:
Click to expand...
Click to collapse
Ok so I extracted that 1.6gb December file. Inside the file I see the large 1.5GB file, I open that and see the boot.img, only like 40mb. or do I need to extract this 1.5GB file too ?

Zorachus said:
Ok so I extracted that 1.6gb December file. Inside the file I see the large 1.5GB file, I open that and see the boot.img, only like 40mb. or do I need to extract this 1.5GB file too ?
Click to expand...
Click to collapse
Yes, extract that file, then you can move the boot.img out of it :good:

Badger50 said:
Yes, extract that file, then you can move the boot.img out of it :good:
Click to expand...
Click to collapse
In Command Prompt I am typing " fastboot boot boot.img " and it says cannot load 'boot.img' : No such file or directory

Zorachus said:
In Command Prompt I am typing " fastboot boot boot.img " and it says cannot load 'boot.img' : No such file or directory
Click to expand...
Click to collapse
Ah crud, I messed up. How bout..fastboot flash boot boot.img
Does that work? And, is that boot.img in the platform-tools folder?

Badger50 said:
Ah crud, I messed up. How bout..fastboot flash boot boot.img
Does that work? And, is that boot.img in the platform-tools folder?
Click to expand...
Click to collapse
I moved that boot.img file into the Downloads section of my PC, and in Command Prompt typed cd Downloads, then once there the "fastboot boot boot.img" line, which that worked, and finished in 1.023s, and the phone rebooted, but now I'm back on that white G screen, and still just sitting there.
I have the "platform-tools" folder inside the Downloads folder, but now sure how to direct the Command Prompt to go there ?
EDIT: Silly me, easy to get Command Prompt to the platform-tools, just typed ' cd platform-tools ' and it's there. LOL. So I did that, and then 'fastboot boot boot.img' and the phone rebooted, but it's still hanging in that white G screen

Badger50 said:
Ah crud, I messed up. How bout..fastboot flash boot boot.img
Does that work? And, is that boot.img in the platform-tools folder?
Click to expand...
Click to collapse
Make sure your boot.img is in Android Tools folder along with fastboot.exe.
Then with phone in bootloader, type:
fastboot flash boot boot.img
---------- Post added at 07:31 PM ---------- Previous post was at 07:26 PM ----------
Zorachus said:
I moved that boot.img file into the Downloads section of my PC, and in Command Prompt typed cd Downloads, then once there the "fastboot boot boot.img" line, which that worked, and finished in 1.023s, and the phone rebooted, but now I'm back on that white G screen, and still just sitting there.
I have the "platform-tools" folder inside the Downloads folder, but now sure how to direct the Command Prompt to go there ?
EDIT: Silly me, easy to get Command Prompt to the platform-tools, just typed ' cd platform-tools ' and it's there. LOL. So I did that, and then 'fastboot boot boot.img' and the phone rebooted, but it's still hanging in that white G screen
Click to expand...
Click to collapse
This should cure your sticking at white screen: (wipes phone)
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

Zorachus said:
I moved that boot.img file into the Downloads section of my PC, and in Command Prompt typed cd Downloads, then once there the "fastboot boot boot.img" line, which that worked, and finished in 1.023s, and the phone rebooted, but now I'm back on that white G screen, and still just sitting there.
I have the "platform-tools" folder inside the Downloads folder, but now sure how to direct the Command Prompt to go there ?
Click to expand...
Click to collapse
What happens if you do a hard restart using the power button?
Your platform-tools folder is where? I just leave mine in the SDK folder, then move my stuff from my files from the download folder. But hey, if it works, that's cool :good:

michaelbsheldon said:
Make sure your boot.img is in Android Tools folder along with fastboot.exe.
Then with phone in bootloader, type:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Ok the boot.img is in there, in my CD:\Downloads section in the folder named "platform-tools" , in that folder is all the fastboot.exe, and boot.img, adb stuff, etc...
I go back to Command Prompt typed in 'fastboot flash boot boot.img; phone rebooted, and still hanging in the white G screen

Ran that [TOOL] Deuces thing, unlocked bootloader and erased data, and other stuff, it does all this in fastboot mode it seems.
So after it's done, I am in fastboot mode still, I press the power button on the Green Start arrow. It boots up, then a black screen and bright circle animation and underneath says erasing, it reboots and goes to the white G screen, then reboots again, and I am in some weird screen now ?
Android Recovery, but this sure the hell isn't TWRP Recovery. It's some strange super tiny lettering hard to barely read, gives me two options;
-Try again
-Factory data reset
Above that it says "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset, and erase all your data stored on this device"

Zorachus said:
Ran that [TOOL] Deuces thing, unlocked bootloader and erased data, and other stuff, it does all this in fastboot mode it seems.
So after it's done, I am in fastboot mode still, I press the power button on the Green Start arrow. It boots up, then a black screen and bright circle animation and underneath says erasing, it reboots and goes to the white G screen, then reboots again, and I am in some weird screen now ?
Android Recovery, but this sure the hell isn't TWRP Recovery. It's some strange super tiny lettering hard to barely read, gives me two options;
-Try again
-Factory data reset
Above that it says "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset, and erase all your data stored on this device"
Click to expand...
Click to collapse
I don't mess with tool kits, so may want to post it in that thread. That's the stock android recovery. Your best bet is to factory reset. Then hopefully it'll boot up.

Looks like I'm ****ed. I pressed Factory Data Reset, it rebooted, went to the white G screen, then rebooted back again to that stock Android recovery, with the same options.

Zorachus said:
Looks like I'm ****ed. I pressed Factory Data Reset, it rebooted, went to the white G screen, then rebooted back again to that stock Android recovery, with the same options.
Click to expand...
Click to collapse
That sounds like outdated Android Tools.
Have you tried to flash the March image from Google yet?
If not, download newest Tools, https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Then download March image and follow these instructions: https://developers.google.com/android/images#taimen.

Related

[Q] SD card appears empty, and phone is stuck on load screen.

A buddy of mine rooted my phone after I had so much difficulty trying to do it myself. I went to update my ROM this afternoon and was brought to the white HTC loading screen with no more activity. Tried getting into my phone to put a new ROM on the SD card and nothing comes up on the SD card folder. I am able to put a ROM in the empty SD card folder and install it, but than it just gets stuck on the same screen as before. I'm really just in the dark here and that friend isn't any longer available to help me out. Thank you all in advance, hopefully this is fixable. I am quite concerned. I should add that I would like to ultimately just get back to stock and be done with things I don't understand so as to avoid this happening again.
Did you flash the boot.img from the rom.zip? These are the correct steps to flash a ROM:
1. Flash the boot.img from ROM.zip via fastboot. "fastboot flash boot boot.img" then "fastboot erase cache"
2. Boot into recovery and use THIS by flashing it.
3. Now flash the ROM.zip and then gapps.zip via recovery.
4. Reboot.
vin4yak said:
Did you flash the boot.img from the rom.zip? These are the correct steps to flash a ROM:
1. Flash the boot.img from ROM.zip via fastboot. "fastboot flash boot boot.img" then "fastboot erase cache"
2. Boot into recovery and use ]THIS[/URL] by flashing it.
3. Now flash the ROM.zip and then gapps.zip via recovery.
4. Reboot.
Click to expand...
Click to collapse
I have tried flashing the boot.img but when I go to put the file onto my phone I don't have any folders such as the boot.img folder to put it in. As for flashing the link above, I am taking a stab in the dark here but I assume that I download that link, extract it and place it on my SD card somewhere. I'm not sure as to how I flash it. Sorry... I really have tried learning the ropes of this, but I can't seem to grasp it.
I somehow now have access to TWRP on my device... I am so confused.
Scalliedhooligan said:
I have tried flashing the boot.img but when I go to put the file onto my phone I don't have any folders such as the boot.img folder to put it in. As for flashing the link above, I am taking a stab in the dark here but I assume that I download that link, extract it and place it on my SD card somewhere. I'm not sure as to how I flash it. Sorry... I really have tried learning the ropes of this, but I can't seem to grasp it.
Click to expand...
Click to collapse
1. First you need to download a custom ROM like this one : http://tunsd.de/downloads/ICJ/IceColdJelly421/aokp_ICJ422-V3.0.zip , Gapps : http://goo.im/gapps/gapps-jb-20130301-signed.zip and Super wipe script: https://www.dropbox.com/s/0y31poo1kiaif4y/Super wipe script.zip
2. Open the aokp_ICJ422-V3.0.zip with winrar/winzip and extract the boot.img and place it in the "fastboot" folder in your PC. (since you have already unlocked/rooted it, I guess you know which is the fastboot folder)
3. Connect your Phone to your PC and make a new folder named "ROM" and put the aokp_ICJ422-V3.0.zip , gapps-jb-20130301-signed.zip and Super wipe script.zipin it.
4. Turn of your phone. Now hold the power button and volume down button together until the bootloader screen pops up. (White screen with 3 android figures at the bottom)
5. Now select "fastboot" using the volume up/down keys and press power button once you highlight it to get into fastboot. Now connect your phone again to your PC.
6. You will hear a sound on your pc and on the screen it will say "fastboot USB".
7. Now open fastboot folder on your PC and press shift key and simultaneously rightclick and click on "open command prompt here".
8. type the following lines:
fastboot erase cache
fastboot flash boot boot.img
fastboot erase cache
9. Now disconnect your phone and head back to "HBOOT" and then select "Recovery".
10. Now go to "install zip from sd" and select "ROM" folder which you had created earlier on the phone.
11. Now select "super wipe script" and install it. After everything is done you will come back to choose zip from sd.
12. Now again navigate to ROM folder and select "aokp_ICJ422-V3.0.zip" and install it. and then install "gapps-jb-20130301-signed.zip".
13. Now go back and select "reboot system now".
14. If you have done all the above steps correctly, you will boot into IceColdJelly Rom!
Scalliedhooligan said:
I somehow now have access to TWRP on my device... I am so confused.
Click to expand...
Click to collapse
Irrespective whether you have CWM or TWRP... Steps will be similar for flashing the ROM... Just the names of the buttons/options will be different!
If you want to use CWM, then download this : http://htcfanboys.com/download/seadersn/?action=list&file=2823
Put the recovery.img in your fastboot folder. Boot your phone in fastboot mode and fire the following lines in CMD.
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
Now you can follow the steps which I have given blindly!
My phone was unlocked and rooted from a different PC so I have no fastboot folders or any knowledge on what a fastboot folder is.
Scalliedhooligan said:
My phone was unlocked and rooted from a different PC so I have no fastboot folders or any knowledge on what a fastboot folder is.
Click to expand...
Click to collapse
Download HTC Sync Manager: (this is required so that correct drivers are installed on your PC)
http://www.htc.com/www/support/software/htc-sync-manager.aspx
After download is complete, install it and restart your pc.
Download Fastboot Folder:
http://www.mediafire.com/?cm2famr3xd2cnom
Extract it somewhere on your pc.
Now look at my previous post and follow the steps...
Everything went swell until step 10. Every time I tried to install anything it came up as failed. I repeated the steps several times with the same results. I really appreciate your efforts in trying to help me.
Scalliedhooligan said:
Everything went swell until step 10. Every time I tried to install anything it came up as failed. I repeated the steps several times with the same results. I really appreciate your efforts in trying to help me.
Click to expand...
Click to collapse
What error message do you get while you flash?
what is your HBoot version?
Go to bootloader(Power button+Volume Down)... once you get to that white screen, you should be able to see your hboot version... something like hboot 1.39...

[Q] Stuck in HTC logo, no power

Hi guys,
I am stuck REALLY stuck. I have or now had a rooted htc one x. I tried to flash a rom but this kept on stucking on the logo (carbon logo, cause it was a Carbon rom). When I saw this I got confused so I deleted everything from recovery mode. EVERYTHING the rom and what was on the sd card. Now when i try to turn oi on it is stuck on the htc logo (the first one that appears). I presume its doing so cause it is finding no rom to load. My other problem is the power. The battery got drained and I cannot even see my SD card on the pc ! I found somewhere that in recovery mode i could go to advanced and to side load but i cannot even see this side load option. PLEASSSSE help me I am really desperate!!
When you're in recovery, connect to your PC and mount your sdcard, in twrp it's advanced/mount. The card should then show up on your PC, put the rom zip on your card and let the phone charge for a while. Use fastboot to erase cache then flash the rom.
sinkster said:
when you're in recovery, connect to your pc and mount your sdcard, in twrp it's advanced/mount. The card should then show up on your pc, put the rom zip on your card and let the phone charge for a while. Use fastboot to erase cache then flash the rom.
Click to expand...
Click to collapse
thanks for your reply.at the moment i am trying to charge the bat. To tell you the truth i tried mount sdcard in advance mode but still int memory didnt show up on pc. I shall retry when i get some power up
sinkster said:
when you're in recovery, connect to your pc and mount your sdcard, in twrp it's advanced/mount. The card should then show up on your pc, put the rom zip on your card and let the phone charge for a while. Use fastboot to erase cache then flash the rom.
Click to expand...
Click to collapse
nothing cant do it!!!!!!!!!!!!!!!!!!!did i brick my phone???
Why cant i see it on my pc. Doesit have to do with the cable i am using???
xxinterboyxx said:
nothing cant do it!!!!!!!!!!!!!!!!!!!did i brick my phone???
Why cant i see it on my pc. Doesit have to do with the cable i am using???
Click to expand...
Click to collapse
Try the original cable together with a 2.0 usb port,
if it still doesnt work flash another recovery like philz touch when you have enough juice
xxinterboyxx said:
Hi guys,
I am stuck REALLY stuck. I have or now had a rooted htc one x. I tried to flash a rom but this kept on stucking on the logo (carbon logo, cause it was a Carbon rom). When I saw this I got confused so I deleted everything from recovery mode. EVERYTHING the rom and what was on the sd card. Now when i try to turn oi on it is stuck on the htc logo (the first one that appears). I presume its doing so cause it is finding no rom to load. My other problem is the power. The battery got drained and I cannot even see my SD card on the pc ! I found somewhere that in recovery mode i could go to advanced and to side load but i cannot even see this side load option. PLEASSSSE help me I am really desperate!!
Click to expand...
Click to collapse
You should flash boot.img and it should boot fine
So another time read, read, read so you won't get in trouble and be without phone few hours/days
nikola016 said:
You should flash boot.img and it should boot fine
So another time read, read, read so you won't get in trouble and be without phone few hours/days
Click to expand...
Click to collapse
Thanks for the advise..but could you please be more specific like making a step by step proceedure. please note that mob is saying "battery level is lowto flash" and i cannot see my sd card on my pc.
thanks again
Extract the boot.img file from the rom, place it in the same location as your adb set up. Reboot to fastboot mode, connect to PC, open cmd window at same location as abd and type:
fastboot erase cache
fastboot flash boot boot.img
Reboot.
sinkster said:
Extract the boot.img file from the rom, place it in the same location as your adb set up. Reboot to fastboot mode, connect to PC, open cmd window at same location as abd and type:
fastboot erase cache
fastboot flash boot boot.img
Reboot.
Click to expand...
Click to collapse
cache erase but getting cannot open boot.img!!!!!!!!!
Don't open it. Just extract it to your adb folder, and flash it via fastboot. If it's not called boot.img then either use fastboot flash boot (bootname).img or rename it to boot.img. Plus if you've erased the system you'll need to flash the rom again via recovery.
sinkster said:
Don't open it. Just extract it to your adb folder, and flash it via fastboot. If it's not called boot.img then either use fastboot flash boot (bootname).img or rename it to boot.img. Plus if you've erased the system you'll need to flash the rom again via recovery.
Click to expand...
Click to collapse
i am typing "C:\android\sdk\platform-tools\fastboot flash boot boot.img" is it good? cause its replying cannot open boot.img and the file i extracted is called boot.img. I cant understand were i am wrong. Perhaps cause the battery is still very low?
The extracted boot.img should be in the sdk folder, for example mine is C:\Users\Sinclair\Downloads\adb_fastboot_and_other_tools\adb_fastboot_and_other_tools\Android. Open the folder, shift+right click and choose 'open command window here'. Try 'fastboot devices' to ensure it's been detected, if so it should work. Possibly a bad download.
sinkster said:
The extracted boot.img should be in the sdk folder, for example mine is C:\Users\Sinclair\Downloads\adb_fastboot_and_other_tools\adb_fastboot_and_other_tools\Android. Open the folder, shift+right click and choose 'open command window here'. Try 'fastboot devices' to ensure it's been detected, if so it should work. Possibly a bad download.
Click to expand...
Click to collapse
please you are my only hope before i throw this device in the rubbish can. could you send me a detailed step by step proceedure of what to do cause I am completely lost. the files i need to down load where to put themand commands i should write down in command mode. I am completely noob on this and all these words you all use.If you cant and i completly understand could you recomend wewre i can post my problem for more veterans to see or perhaps there is somewhere where i can ship my device and get it fixed at a cost of course.
THANKS
You put literally the boot.img file in that state in the Fastboot.exe folder on the pc. So it goes into the platform tools folder !
Then you put the phone in the bootloader where you see "Fastboot usb" in red text
Then you point with the mouse inside the platform tools folder and hold down shift and click the right button and select "open command window here"
Then you type the command in that window
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
By your reply I'm presuming you don't have a full adb/fastboot setup. Read this http://forum.xda-developers.com/showthread.php?p=42407269,
and follow the instructions.
Mr Hofs said:
You put literally the boot.img file in that state in the Fastboot.exe folder on the pc. So it goes into the platform tools folder !
Then you put the phone in the bootloader where you see "Fastboot usb" in red text
Then you point with the mouse inside the platform tools folder and hold down shift and click the right button and select "open command window here"
Then you type the command in that window
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
Click to expand...
Click to collapse
t
Hi there
Thanks for your interest in helping me out. After i do this right click thing i go to the black window and give these commands as they are no previous path like c:\ etc etc before the commands you gave me? Cause the funny thing i did the erase cache thing and it did it but this boot boot.img isnt doing it. And bdw i redownloaded another rom, copied it to the file tools and extracted it there. In it there was a boot.img file. Did i do the right thing?
Thanks again
When you open the cmd window by right click in a folder then all commands you enter are for that folder path, so it's fastboot flash boot xxx.img(replace xxx with the boot name), and it's only the boot.img for your rom you need extracted to the folder.
I think you are confusing yourself. Just stay calm and read carefully ! It's not rocket science. Open the rom.zip with 7Zip and just drag out the boot.img file to the exact same folder as where your fastboot.exe file is located. Open the command window there and type the commands.
The command fail cannot open is only because the file is just not there !
---------- Post added at 10:20 AM ---------- Previous post was at 09:30 AM ----------
http://forum.xda-developers.com/showthread.php?t=2069904
Mr Hofs said:
I think you are confusing yourself. Just stay calm and read carefully ! It's not rocket science. Open the rom.zip with 7Zip and just drag out the boot.img file to the exact same folder as where your fastboot.exe file is located. Open the command window there and type the commands.
The command fail cannot open is only because the file is just not there !
---------- Post added at 10:20 AM ---------- Previous post was at 09:30 AM ----------
http://forum.xda-developers.com/showthread.php?t=2069904
Click to expand...
Click to collapse
I opened the foldet where my fastboot command is pointed the arrow inside the file, pressed down and holded the shift key when i right click the mouse cant see the command open command window here!!!!!!! What I am doing wrong i cant understand http://forum.xda-developers.com/images/icons/icon9.gif
xxinterboyxx said:
I opened the foldet where my fastboot command is pointed the arrow inside the file, pressed down and holded the shift key when i right click the mouse cant see the command open command window here!!!!!!! What I am doing wrong i cant understand http://forum.xda-developers.com/images/icons/icon9.gif
Click to expand...
Click to collapse
AND THE boot.img file is there cause I am seeing it!!!!!!

Nexus 5x Recovery Startup Loop

Hi
When I start up the boot loader or hit start, it just goes into recovery mode
When I turn my phone off normally and start it up, it just goes into recovery mode
I have an unlocked phone that's rather new, and I can't start it up
Thanks for the help
RingPvP said:
Hi
When I start up the boot loader or hit start, it just goes into recovery mode
When I turn my phone off normally and start it up, it just goes into recovery mode
I have an unlocked phone that's rather new, and I can't start it up
Thanks for the help
Click to expand...
Click to collapse
Running stock rom and stock kernel? Or custom rom kernel? Twrp recovery? Any other info
Sent from my Nexus 5X using Tapatalk
The_Automator said:
Running stock rom and stock kernel? Or custom rom kernel? Twrp recovery? Any other info
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I did *fastboot flash boot twrp.img. I mean't to flash it, but I was thinking twrp.img when trying to use boot.img
I couldn't undo it, and I knew I damaged my phone from this, but if there is a possible chance to fix it I am in even if I loose my data.
I was pretty sure this was the reason my Nexus 5x doesn't work, but I did nothing else other then that. Thanks for the help
RingPvP said:
I did *fastboot flash boot twrp.img. I mean't to flash it, but I was thinking twrp.img when trying to use boot.img
I couldn't undo it, and I knew I damaged my phone from this, but if there is a possible chance to fix it I am in even if I loose my data.
I was pretty sure this was the reason my Nexus 5x doesn't work, but I did nothing else other then that. Thanks for the help
Click to expand...
Click to collapse
So you can not boot to bootloader but can boot straight into twrp? But you can't flash the boot image from twrp because you cant use fastboot commands in twrp correct? maybe try this thread dedicated to unbricking phones
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Sent from my Nexus 5X using Tapatalk
The_Automator said:
So you can not boot to bootloader but can boot straight into twrp? But you can't flash the boot image from twrp because you cant use fastboot commands in twrp correct? maybe try this thread dedicated to unbricking phones
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
No no no, I can boot into the bootloader. When I turn on my phone normally, it goes into recovery mode or in twrp. When I load the bootloader and start, it also goes into twrp.
I am pretty sure I can still fastboot commands in twrp, so that's good.
Sorry that I didn't add that, but I hope you know what the problem is because I really want my phone back.
RingPvP said:
No no no, I can boot into the bootloader. When I turn on my phone normally, it goes into recovery mode or in twrp. When I load the bootloader and start, it also goes into twrp.
I am pretty sure I can still fastboot commands in twrp, so that's good.
Sorry that I didn't add that, but I hope you know what the problem is because I really want my phone back.
Click to expand...
Click to collapse
To be clear recovery mode is the same as twrp and you can not use fastboot commands within TWRP you can use adb shell commands (im less familiar with these). You can not flash stock images from twrp only aftermarket roms, kernels, zips etc. Factory images are flashed from the bootloader using fastboot.
But if you can boot into the bootloader and use fastboot (verify by typing fastboot devices)
Download chainfires modified boot image (select bullhead for the Nexus 5X)
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
extract the file so you have the .img file
Verify that your fastboot commands work fastboot devices (should always work from bootloader)
place chainfires image in the same folder as your fastboot exe.
fastboot flash boot boot.img
this should over write the boot image.
You could also just download the factory google image
https://developers.google.com/android/nexus/images?hl=en
Latest bullhead image ends with M. Extract the tar and place the extracted content in your (fastboot/adb folder) on your computer and just double click the flash-all.bat (note this will erase all data and give you a clean phone)
leave your phone until it says press any key to exit.
The_Automator said:
If you can boot into bootloader than the simplest thing to do is to download the nexus 5x image from googles factory image site. Extract that zip into your fastboot folder and double click flash all.bat. This will restore youre ur phone to factory defaults on the latest factory image. Alternatively you can just extract the boot image and use fastboot flash boot boot.img (but for this method youd have to download the factory image you already have installed which is why googlea self installer (flash-all.bat) would be easier
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I just flashed all.bat double clicking it, and it said finished. I turned on my phone already on bootloader, and it went back to twrp. I might have set my fastboot folder wrong, but the location is
C:\Program Files (x86)\Android\android-sdk\bullhead-mda89e if that helps.
Sorry if I am taking to much of your time away, but you've helped me a lot already
RingPvP said:
I just flashed all.bat double clicking it, and it said finished. I turned on my phone already on bootloader, and it went back to twrp. I might have set my fastboot folder wrong, but the location is
C:\Program Files (x86)\Android\android-sdk\bullhead-mda89e if that helps.
Sorry if I am taking to much of your time away, but you've helped me a lot already
Click to expand...
Click to collapse
usually the folder you would want to place the image into is the platform tools folder and you would want to place the files in the directory (not a sub directory) and the mda89e is the first release the newest release from google is
6.0.0 (MDB08M) Link f5233f827a44f99e26722e349f3c9445 5867cc27a23257a47688fe180ec272f1152ddde2
But within the factory image there should be a zip called something like image-bullhead-MDB08M.zip open that zip and extract just the boot.img to your platform tools folder. Then you should be able to use
fastboot flash boot boot.img
RingPvP said:
I just flashed all.bat double clicking it, and it said finished. I turned on my phone already on bootloader, and it went back to twrp. I might have set my fastboot folder wrong, but the location is
C:\Program Files (x86)\Android\android-sdk\bullhead-mda89e if that helps.
Sorry if I am taking to much of your time away, but you've helped me a lot already
Click to expand...
Click to collapse
In your case, it should be: C:\Program Files (x86)\Android\android-sdk\platform-tools\bullhead-mda89e
In this folder your should see fastboot.exe
The_Automator said:
To be clear recovery mode is the same as twrp and you can not use fastboot commands within TWRP you can use adb shell commands (im less familiar with these). You can not flash stock images from twrp only aftermarket roms, kernels, zips etc. Factory images are flashed from the bootloader using fastboot.
But if you can boot into the bootloader and use fastboot (verify by typing fastboot devices)
Download chainfires modified boot image (select bullhead for the Nexus 5X)
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
extract the file so you have the .img file
Verify that your fastboot commands work fastboot devices (should always work from bootloader)
place chainfires image in the same folder as your fastboot exe.
fastboot flash boot boot.img
this should over write the boot image.
You could also just download the factory google image
https://developers.google.com/android/nexus/images?hl=en
Latest bullhead image ends with M. Extract the tar and place the extracted content in your (fastboot/adb folder) on your computer and just double click the flash-all.bat (note this will erase all data and give you a clean phone)
leave your phone until it says press any key to exit.
Click to expand...
Click to collapse
I don't know what to say, but thank you so much! I literally had a heart attack when it happened. You deserve more than a thanks for this .
RingPvP said:
I don't know what to say, but thank you so much! I literally had a heart attack when it happened. You deserve more than a thanks for this .
Click to expand...
Click to collapse
Happy to help glad you got your phone sorted
Sent from my Nexus 5X using Tapatalk

Unlocked, stuck boot, where is Download folder?

Followed the instructions here for Rooting and fastbooting to TWRP. Could not locate the Download folder where I put Magisk, so rebooted and put it in a few other folders. Rebooted back to TWRP image and still cannot the Magisk zip or extracted files anywhere. Switched to the B partition and looked around there with no luck. Then went to reboot in TWRP. Now I have a spinning white screen with the "scrolling G" ...15 minutes and counting.
How do I get it out of this stuck boot.
Why can I not find the Download or Android folders in TWRP File Manager where I put Magisk?
Thanks
Downloads from your phone should be in /sdcard/downloads.
If you are stuck with a non-booting system, you need to flash the factory image, you can try to flash it and remove the '-w' from flash-all.bat to keep your data.
Edit: btw to root stock, simply boot twrp image and flash magisk.zip, then reboot system. You can then boot twrp and flash twrp.zip if desired.
boostedduece said:
Downloads from your phone should be in /sdcard/downloads.
If you are stuck with a non-booting system, you need to flash the factory image, you can try to flash it and remove the '-w' from flash-all.bat to keep your data.
Edit: btw to root stock, simply boot twrp image and flash magisk.zip, then reboot system. You can then boot twrp and flash twrp.zip if desired.
Click to expand...
Click to collapse
From what I recall, in the /sdcard/ I had 2 folders /0/ and /00b/? Both had "scrambled" folder names within, nothing that was Download or the like.
So, it's been at least an hour and I still have the scrolling boot screen. In hindsight I recall I went to B before restarting. Can't see device from ADB. Tried the previous Nexus methods of holding power and up/down keys...still white screen G with scroll. Edit: I tried again holding Power and it will now shut off. Holding volume down and power I can get to the boot menu and see Fast Mode. It won't boot on it's own, but I can get to the boot menu. So I'll try connecting again in the morning. Edit #2: after trying recovery and power button a few times the phone booted.
So it looks like I am back to finding Magisk in the Download folder-which I copied from my computer to the Download folder on the 3xl. I installed ES File Explorer and see the zips are in storage/emulated/0/Download but I do not see Download after I reboot with the TWRP image.
There is one /sdcard folder, the other 2 in /storage/emulated/.. have different attributes, but I recommend dealing with /sdcard.
Sounds like it did not decrypt the partition in twrp, that's why the names were garbled.
Holding both volume buttons and power for a while should hard shutdown the device.
You should be able to get to bootloader from power + volume down, flash-all.bat should work from here, you are definitely not bricked though.
Still unable to locate Download Folder
So, I can get the phone to boot and reboot.
From a command prompt:
adb devices (device is available)
adb reboot bootloader
fastboot boot twrp-3.2.2-3-crosshatch.img
Boots to TWRP asking for password, I hit cancel.
It then asks if I want write protection. Initially, I went this route, but tried again allowing full access.
I can see /sdcard/ and 2 folders /0/ and /0bb/, /0bb/ is empty.
when I go into /0/ the folder names are scrambled. Some have sub-folders that are also scrambled.
Why are the names scrambled? Where is my Download folder with my .zip and unzip files?
vette8t7 said:
So, I can get the phone to boot and reboot.
From a command prompt:
adb devices (device is available)
adb reboot bootloader
fastboot boot twrp-3.2.2-3-crosshatch.img
Boots to TWRP asking for password, I hit cancel.
It then asks if I want write protection. Initially, I went this route, but tried again allowing full access.
I can see /sdcard/ and 2 folders /0/ and /0bb/, /0bb/ is empty.
when I go into /0/ the folder names are scrambled. Some have sub-folders that are also scrambled.
Why are the names scrambled? Where is my Download folder with my .zip and unzip files?
Click to expand...
Click to collapse
You have to enter your password that unlocks your phone when you first boot into TWRP so that it can decrypt your phone. Don't hit cancel
vette8t7 said:
So, I can get the phone to boot and reboot.
From a command prompt:
adb devices (device is available)
adb reboot bootloader
fastboot boot twrp-3.2.2-3-crosshatch.img
Boots to TWRP asking for password, I hit cancel.
It then asks if I want write protection. Initially, I went this route, but tried again allowing full access.
I can see /sdcard/ and 2 folders /0/ and /0bb/, /0bb/ is empty.
when I go into /0/ the folder names are scrambled. Some have sub-folders that are also scrambled.
Why are the names scrambled? Where is my Download folder with my .zip and unzip files?
Click to expand...
Click to collapse
TWRP is failing to decrypt your phone. This used to be a big issue, but has been solved for some time. What version of TWRP are you using?
@vette8t7 if you haven't figured this out yet, as others have said, twrp is not decrypting your device. If you haven't you'll need to boot into your system and enable a pin security. Without that twrp doesn't have any info to decrypt your device.
Sent from my [device_name] using XDA-Developers Legacy app
hatdrc said:
You have to enter your password that unlocks your phone when you first boot into TWRP so that it can decrypt your phone. Don't hit cancel
Click to expand...
Click to collapse
Oh man, THAT makes sense. I thought it was wanting me to create one and I didn't want to have to track ANOTHER password.
Okay, I'm in, see Downloads and .zip files!!:good:
hatdrc said:
You have to enter your password that unlocks your phone when you first boot into TWRP so that it can decrypt your phone. Don't hit cancel
Click to expand...
Click to collapse
vette8t7 said:
Oh man, THAT makes sense. I thought it was wanting me to create one and I didn't want to have to track ANOTHER password.
Okay, I'm in, see Downloads and .zip files!!:good:
Click to expand...
Click to collapse
Geez, back in the day I unlocked and rooted my Galaxy Nexus without issue and did most of the same on a Note 4. Didn't really have a need to do either on my Nexus 6p-which I have gone back to using while I straighten out the 3XL. I'd leave the 3XL alone except I need to unlock and root to run the commands to prevent the service check for hotspot on my Verizon GUDP. The 6p has gotten sluggish as of late, thus the 3XL upgrade.
So...I found my Magisk-v18.0.zip (the non-beta) in TWRP after entering the passcode. Hit install. It went through to restart adn white screen scrolling G and now I keep landing on an Android Recovery page:
google/crosshatch/crosshatch
9/PQ1A.181205.006/5108886
user/release-keys
Use volume up/down and power.
Can't load Android System. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device.
Try again
Factory data reset.​
So after trying the "Try again" and it try to load and then reboots and tries to load and I come to the same screen above.
I finally tried selecting "Factory data reset" only to come to the same menu.
I was able to run fastboot from the cmd and run twrp-3.2.3-3-crosshatch.img again.
In /sdcard/ I have an empty /obb/ and an empty /TWRP/ folder.
Performed an adb push of magisk.zip and twrp.zip to /0bb/directory and this time performed magisk followed by twrp install and now I get the Google setup window..I don't see Magisk installed.
vette8t7 said:
Geez, back in the day I unlocked and rooted my Galaxy Nexus without issue and did most of the same on a Note 4. Didn't really have a need to do either on my Nexus 6p-which I have gone back to using while I straighten out the 3XL. I'd leave the 3XL alone except I need to unlock and root to run the commands to prevent the service check for hotspot on my Verizon GUDP. The 6p has gotten sluggish as of late, thus the 3XL upgrade.
So...I found my Magisk-v18.0.zip (the non-beta) in TWRP after entering the passcode. Hit install. It went through to restart adn white screen scrolling G and now I keep landing on an Android Recovery page:
google/crosshatch/crosshatch
9/PQ1A.181205.006/5108886
user/release-keys
Use volume up/down and power.
Can't load Android System. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device.
Try again
Factory data reset.​
So after trying the "Try again" and it try to load and then reboots and tries to load and I come to the same screen above.
I finally tried selecting "Factory data reset" only to come to the same menu.
Any ideas what I did now and how I get out of it?
Click to expand...
Click to collapse
I'd start fresh by flashing the factory image by running the flash-all batch file. BUT, edit it first to remove the -w you'll see a number of times down. If you don't your device will be wiped. Then boot twrp with fastboot boot, don't flash it. Then install magisk within twrp. If you want to keep twrp permanently then install the twrp zip file. I generally install twrp, then boot back into recovery and then install magisk.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I'd start fresh by flashing the factory image by running the flash-all batch file. BUT, edit it first to remove the -w you'll see a number of times down. If you don't your device will be wiped. Then boot twrp with fastboot boot, don't flash it. Then install magisk within twrp. If you want to keep twrp permanently then install the twrp zip file. I generally install twrp, then boot back into recovery and then install magisk.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I've gotten to the point where TWRP is installed. If I install TWRP.zip I can get the phone to boot to an image that doesn't appear to have Magisk installed. So I installed the Magisk Manager. It indicates Magisk isn't installed. So I reboot into TWRP select Magisk v18 and install, then reboot system. The phone will go to the Google white screen spin for a bit and then reboot to TWRP. If I install the twrp.zip I can get back into the phone and see Magisk still isn't installed. Ihave tried combinations of installing TWRP.zip then Magisk.zip and vice versa, but I never seem to get Magisk installed.
I've seen mention of the flash-all batch, but I don't seem to have it in anything I have downloaded from these two guides:
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
I see it in #4 here: https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3857195
so I'll try what you suggest.
vette8t7 said:
I've gotten to the point where TWRP is installed. If I install TWRP.zip I can get the phone to boot to an image that doesn't appear to have Magisk installed. So I installed the Magisk Manager. It indicates Magisk isn't installed. So I reboot into TWRP select Magisk v18 and install, then reboot system. The phone will go to the Google white screen spin for a bit and then reboot to TWRP. If I install the twrp.zip I can get back into the phone and see Magisk still isn't installed. Ihave tried combinations of installing TWRP.zip then Magisk.zip and vice versa, but I never seem to get Magisk installed.
I've seen mention of the flash-all batch, but I don't seem to have it in anything I have downloaded from these two guides:
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
I see it in #4 here, so I'll try what you suggest.
Click to expand...
Click to collapse
I assume you've found the factory image and extracted the zip file. In there is the flash-all.bat. Edit that, notepad++ is a good editor. Save the file after you've edit it and run that. Make sure you save it or you'll run the unedited version. Then start the process of booting twrp and installing magisk.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I assume you've found the factory image and extracted the zip file. In there is the flash-all.bat. Edit that, notepad++ is a good editor. Save the file after you've edit it and run that. Make sure you save it or you'll run the unedited version. Then start the process of booting twrp and installing magisk.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes, found the factory image and extracted the zip. Is started to take the -w out and yes, Notepad++), but decided to leave it in to start fresh. I put the phone in Fastboot. Ran the flash-all, it worked for a while and then indicated there waasn't a recovery.img and a few other things and then "ended" with any key to exit. So I restarted to find everything was still there. So I rebooted to TWRP and installed the Magisk.zip, only to result in the same boot and restart into TWRP. So, convinced the factory image didn't wipe I performed that step again. Boot phone to Fastboot. Opened a command prompt in the image directory. flash-all. It ran for a while complained about the few .img files, but seemed to do more than it did the first time. This time I reloaded the boot loader and fastboot boot twrp.img only to go in and find I still had file in the Download folder (I was expecting to push them from a wipe). So of course when I install magisk.zip and restart it goes to the white google spinning rescreen and eventually restarts back into TWRP.
Your instructions lineup with #4 and 7 or 8 here: https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3857195
For some reason I can't seem to wipe for 1 and ever get Magisk to install 2. Of course my phone has the December OTA update if that has added any new variables here?
I reran this flash-all again to a log file (attached).
vette8t7 said:
Yes, found the factory image and extracted the zip. Is started to take the -w out and yes, Notepad++), but decided to leave it in to start fresh. I put the phone in Fastboot. Ran the flash-all, it worked for a while and then indicated there waasn't a recovery.img and a few other things and then "ended" with any key to exit. So I restarted to find everything was still there. So I rebooted to TWRP and installed the Magisk.zip, only to result in the same boot and restart into TWRP. So, convinced the factory image didn't wipe I performed that step again. Boot phone to Fastboot. Opened a command prompt in the image directory. flash-all. It ran for a while complained about the few .img files, but seemed to do more than it did the first time. This time I reloaded the boot loader and fastboot boot twrp.img only to go in and find I still had file in the Download folder (I was expecting to push them from a wipe). So of course when I install magisk.zip and restart it goes to the white google spinning rescreen and eventually restarts back into TWRP.
Your instructions lineup with #4 and 7 or 8 here: https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3857195
For some reason I can't seem to wipe for 1 and ever get Magisk to install 2. Of course my phone has the December OTA update if that has added any new variables here?
I reran this flash-all again to a log file (attached).
Click to expand...
Click to collapse
- first, make sure you have the latest SDK Platform-tools r28.0.1 (see guide 'Prerequisites c.' for link).
- extract the December factory image in the Platform-tools folder.
- Open a command prompt in the Platform-tools folder.
- type flash-all at the prompt.
- when it finishes, do #8 for root.
Homeboy76 said:
- first, make sure you have the latest SDK Platform-tools r28.0.1 (see guide 'Prerequisites c.' for link).
- extract the December factory image in the Platform-tools folder.
- Open a command prompt in the Platform-tools folder.
- type flash-all at the prompt.
- when it finishes, do #8 for root.
Click to expand...
Click to collapse
I have the r28.0.1
I was researching the Image and I had downloaded and used the A1.docomo, which, as jd1639 pointed out in another thread is for japanese phones. I've just finished downloading the non-docomo for December and see where I get.
Oh, now I see what I am doing wrong. The image .zip needs to be extracted into the platform folder. I noticed you said run the command from "platform-tools" folder.
vette8t7 said:
I have the r28.0.1
I was researching the Image and I had downloaded and used the A1.docomo, which, as jd1639 pointed out in another thread is for japanese phones. I've just finished downloading the non-docomo for December and see where I get.
Click to expand...
Click to collapse
If you have r28.0.1 where is the Platform-tools folder?
---------- Post added at 05:54 AM ---------- Previous post was at 05:50 AM ----------
vette8t7 said:
I have the r28.0.1
I was researching the Image and I had downloaded and used the A1.docomo, which, as jd1639 pointed out in another thread is for japanese phones. I've just finished downloading the non-docomo for December and see where I get.
Oh, now I see what I am doing wrong. The image .zip needs to be extracted into the platform folder. I noticed you said run the command from "platform-tools" folder.
Click to expand...
Click to collapse
Yes, the Factory image zip needs to be extracted to the Platform-tools folder.
Homeboy76 said:
If you have r28.0.1 where is the Platform-tools folder?
C:\adb\platform-tools_r28.0.1-windows\platform-tools
Within that is adb, fastboot, twrp-pixel-installer-crosshatch-3.2.3-3.img (renamed twrp.img), december factory image (extracted) as well as the Magisk-v18.0.zip and twrp.zip (for copying or pushing)
---------- Post added at 05:54 AM ---------- Previous post was at 05:50 AM ----------
Yes, the Factory image zip needs to be extracted to the Platform-tools folder.
Click to expand...
Click to collapse
So once the factory image is done, I go through setup (skipping through most for later) to get the usb debugging enabled and copy Magisk.zip and twrp.zip.
adb reboot bootloader
fastboot boot twrp.img
put in passcode
Swiped to allow for modifications
First time I just installed the magisk.zip only to have it reboot twice into the loop of my #10 post again.
The second time I repeated the whole factory image process up to fastbooting twrp.img and this time installed twrp.zip, reboot recovery, install Magisk-v18.0.zip. Reboot system. It boots and No Magisk in the app tray! Err...well now it is there and it shows Magisk installed!
Holy Moly what a PITA!! On a positive note, I kind of refreshed some of this stuff I hadn't done in years :good:
I got stuck a couple of months back when my wife's nexus 6p died (not battery-which I later swapped into mine), something with the processor board. I got a Verizon 3XL with the locked bootloaderL...so if anything ever develops there, I can root that phone for the GUDP hotspot as well.
I followed the steps here: https://forum.xda-developers.com/pixel-3-xl/how-to/how-to-native-tethering-rooted-pixel-3-t3858662
So far, so good. Great Success! Thanks for your help!
homeboy76 said:
If you have r28.0.1 where is the Platform-tools folder?
Click to expand...
Click to collapse
vette8t7 said:
C\adb\platform-tools_r28.0.1-windows\platform-tools
Within that is adb, fastboot, twrp-pixel-installer-crosshatch-3.2.3-3.img (renamed twrp.img), december factory image (extracted) as well as the Magisk-v18.0.zip and twrp.zip (for copying or pushing)
Click to expand...
Click to collapse
"twrp-pixel-installer-crosshatch-3.2.3-3.img (renamed twrp.img)"
I think you mean 'twrp-3.2.3-3-crosshatch.img (renamed twrp.img)
vette8t7 said:
...The second time I repeated the whole factory image process up to fastbooting twrp.img and this time installed twrp.zip, reboot recovery, install Magisk-v18.0.zip. Reboot system. It boots and No Magisk in the app tray! Err...well now it is there and it shows Magisk installed!...
Click to expand...
Click to collapse
@vette8t7
Yes

Question Stuck in fast boot

Is there a way i can recover my data ? I need to recover my kid's graduation pictures. I will pay for help if I need too.
I was rooted and using 11.2.4.4.LE15AA. I uninstalled Magisk then i tried updating to 11.2.5.5 via ota , it kept saying install failed i need to reboot and now I'm stuck in fastboot.
edit: and now it doesn't turn off.
Im a flipping idiot.
Thanks in advance.
https://mega.nz/file/7YQj3SIR#5yDfje2mVgPVRdZi-gYrDRvvQE2hx_DYD00vicZH8Fo
This is a zip from one of the top 3 pinned threads on this OP9P forum that has stock and patched boot.img from your 4.4AA build..(if thats what ur phone is still on). U may be able to download the zip, put on ur pc, extract it, then open cmd and fastboot boot (then drag the stock boot.img to the command prompt u typed in) and hit enter.. It may work to get u back booted unrooted...
Shooter7889 said:
https://mega.nz/file/7YQj3SIR#5yDfje2mVgPVRdZi-gYrDRvvQE2hx_DYD00vicZH8Fo
This is a zip from one of the top 3 pinned threads on this OP9P forum that has stock and patched boot.img from your 4.4AA build..(if thats what ur phone is still on). U may be able to download the zip, put on ur pc, extract it, then open cmd and fastboot boot (then drag the stock boot.img to the command prompt u typed in) and hit enter.. It may work to get u back booted unrooted...
Click to expand...
Click to collapse
Crap that didn't work. I'm so beyond screwed. I wonder IF and when TWRP comes out if I will be able to decrypt then.
Try flashing 4.4 or 5.5 full OTA via fastboot/fastbootd. If you are gonna try the 5.5 then you gotta use EU/India.
TWRP at this point is a pipe dream. Decrypt doesn't even work for A10 on OP and Android is moving faster than TWRP can keep up.
craznazn said:
Try flashing 4.4 or 5.5 full OTA via fastboot/fastbootd. If you are gonna try the 5.5 then you gotta use EU/India.
TWRP at this point is a pipe dream. Decrypt doesn't even work for A10 on OP and Android is moving faster than TWRP can keep up.
Click to expand...
Click to collapse
Is that where i flash all the individual .imgs with fastboot? or just system.img
Individual
In case this comes from magisk modules, just try to reboot in safe mode:
Safe Mode
1. Hold power until it goes off
2. Boot and wait for the bootloader warning
3. Hold vol up and down until boot animation
4. Once it's booted just reboot again and you're done
Now on boot all magisk modules are disabled
Other option, have you try to flash your original boot!
craznazn said:
Individual
Click to expand...
Click to collapse
I get this for several of the img files.
FAILED (remote: Flashing is not allowed for Critical Partitions
But I'm able to get to recovery now, with this error
boot reason fs_mgr_mount_all
Fastbootd for critical partitions (not fastboot)
I wiped it.
close the thread.
Oh too bad i had your solution, as ihad the same problem last week.
For anyone else in this situation you have to flash the stock boot img to opposite partition. Then boot to that partition. Get your data off at that point before you do anything else. Then try to re-root

Categories

Resources