Develop Bugs

[Q] Accidentally deleted boot...any way to fix?

Yeah, I'm an idiot...
I was trying to root my 2013 N7 and I thought I had the factory image for it (it was actually the factory image for the 2012 N7). Anyhow, I ran through the "flash-all" script which proceeded to erase everything, including "boot". Now I can't boot anything even after installing the makeshift system.img here:
http://forum.xda-developers.com/showthread.php?t=2380913
Because my situation is a little different, I'm guessing it's because I hosed the boot on my machine.
Right now I can still get into the bootloader and go into recovery using TWRP, but when I try to boot into system I just get stuck at the Google logo .
Is there any way to fix this before google releases the factory image?

I do not believe so since the architecture of the old and new devices are differwnt that when you flashalled the old image something got messed up. You could try locking the bootloadewr and exchanging your nexus or wait for official image which should be soon
Sent from my Nexus 7 using xda app-developers app

Fastboot flash boot boot.IMG
Boot.IMG is your kernel
Sent from my Nexus 7 using xda premium

jporter396 said:
I do not believe so since the architecture of the old and new devices are differwnt that when you flashalled the old image something got messed up. You could try locking the bootloadewr and exchanging your nexus or wait for official image which should be soon
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Sorry, I should mention that I didn't actually get to flash the old image because there was a signature mismatch. So I didn't actually install the old image...now I'm just left in a state where everything was deleted (including boot).

smirkis said:
Fastboot flash boot boot.IMG
Boot.IMG is your kernel
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I don't have boot.IMG for a 2013 Nexus 7, where can I get it?

petersellers said:
Sorry, I should mention that I didn't actually get to flash the old image because there was a signature mismatch. So I didn't actually install the old image...now I'm just left in a state where everything was deleted (including boot).
Click to expand...
Click to collapse
I would try doing what I did again, maybe on the off chance it works. Try downloading the image again. Good luck !
Sent from my Nexus 7 using xda app-developers app

stock image needed
Since you fully flashed an old factory image, the best option is to wait for Google to post the Factory image for Nexus 7 - Razor (maybe by Tuesday?). I had flashed an old recovery.img and my new nexus wouldn't boot. I got someone to pull it from their nexus and give it to me. It worked for me, but that was only one partition. All yours are messed.

treoo0_1 said:
Since you fully flashed an old factory image, the best option is to wait for Google to post the Factory image for Nexus 7 - Razor (maybe by Tuesday?). I had flashed an old recovery.img and my new nexus wouldn't boot. I got someone to pull it from their nexus and give it to me. It worked for me, but that was only one partition. All yours are messed.
Click to expand...
Click to collapse
I didn't actually flash the old image, there was a version mismatch.
I have the system partition thanks to the link in my post, I have the TWRP recovery partition, I think all I need is a boot partition. I'm guessing here since I'm new at android stuff.

petersellers said:
I didn't actually flash the old image, there was a version mismatch.
I have the system partition thanks to the link in my post, I have the TWRP recovery partition, I think all I need is a boot partition. I'm guessing here since I'm new at android stuff.
Click to expand...
Click to collapse
I can try help you.Just tell me one thing when you try starting the device what do you see?
And don't worry there is a way for this

decianV West
nsnarayan10 said:
I can try help you.Just tell me one thing when you try starting the device what do you see?
And don't worry there is a way for this
Click to expand...
Click to collapse
I see the google logo in the middle of the screen, with an unlocked lock logo at the bottom "since I have unlocked the bootloader".
If I press the volume rockers I get the choice to power off, start, restart bootloader, or recovery mode. Restart bootloader takes me to the standard android bootloader with the robot on its side, recovery takes me to TWRP.

I'm uploading boot.img for you.
BOOT.IMG HERE

petersellers said:
I see the google logo in the middle of the screen, with an unlocked lock logo at the bottom "since I have unlocked the bootloader".
If I press the volume rockers I get the choice to power off, start, restart bootloader, or recovery mode. Restart bootloader takes me to the standard android bootloader with the robot on its side, recovery takes me to TWRP.
Click to expand...
Click to collapse
Probably u got two choice.
1- find stock ROM for the device and flash it.
2- find someone with the exact same device, ask he/she to create backup of his/her device and flash it to yours.
And did you try flashing your device with proper factory image anyhow?

Boot.IMG was pulled by me here.
http://forum.xda-developers.com/showthread.php?t=2380380

Nburnes said:
Boot.IMG was pulled by me here.
http://forum.xda-developers.com/showthread.php?t=2380380
Click to expand...
Click to collapse
You're my messiah. I had unlocked, installed twrp, and booted into twrp. It asks if you want to root, I said yes then no boot. Fastbooted the system.img, but after the bootloader the screen would stay black but if plugged into my computer it would show the MTP device and I could access it. Flashed the stock boot.img you posted, and tada I get boot animation and actualy boot.

Thanks guys! I tried nburnes' boot.img and it worked great!
This was an educational experience, for sure

petersellers said:
Thanks guys! I tried nburnes' boot.img and it worked great!
This was an educational experience, for sure
Click to expand...
Click to collapse
Good and next time make sure not to repeat this mistake and how did u install it?

jporter396 said:
"exchanging your nexus"
Click to expand...
Click to collapse
Lets not promote this since it's fixable even if it means waiting for Google to release the official image. Don't screw over the store and others in queue waiting to buy because of self induced error.

nsnarayan10 said:
Good and next time make sure not to repeat this mistake and how did u install it?
Click to expand...
Click to collapse
/fastboot flash boot boot-flo-JSS15J-stock.img

[Very serious]Non-booting/non-changing/not working problem

I woke up today to a bootloop. After pulling out the battery, I cant turn it on, it was stuck at the google logo. I thought it was some rom issue or something. When I had the time, in the afternoon, I just boot to recovery, and wiped data+sd card. Turns out sd card was not wiped.
Just now, I found a way to boot it. (AFTER WIPING DATA) I used the gnex toolkit and boot with insecure image, and guess wat? My old rom boots. Everything was the way it was, and then it crashed and stuck on the google logo again.(I made sure i wiped things two to three times, data and sd) I did a few experiments:
1) Flash using ODIN
2) Flash CWM using toolkit--it changed back to twrp after reboot
3) Changing the icon on my homescreen after boot--- everything was the same again after booting
4) Flash stock image using toolkit
5) Wipe data using manual adb
6) Try to lock my bootloader
Everything I tried changing, change back to the original state after reboot. What is the problem?
Device: Galaxy Nexus
ROM: Purity 7 sept release
Kernel: Fancy r42
Logs in twrp are showing updating partition, not FAIL. So I really don't think there is a need to show the recovery log.
HELP ME!

are you flashing your recovery or just booting the recovery?
fastboot oem unlock
fastboot flash recovery recovery.img
use ClockWorkMod. I've heard nothing but problems with TWRP.

player911 said:
are you flashing your recovery or just booting the recovery?
fastboot oem unlock
fastboot flash recovery recovery.img
use ClockWorkMod. I've heard nothing but problems with TWRP.
Click to expand...
Click to collapse
umm, i can boot recovery. i cannot flash cwm. i tried, but when i reboot, it went back to twrp.
what is oem unlock for? coz its smth i havent tried.

jacktay94 said:
umm, i can boot recovery. i cannot flash cwm. i tried, but when i reboot, it went back to twrp.
what is oem unlock for? coz its smth i havent tried.
Click to expand...
Click to collapse
Oem unlock will unlock your bootloader and wipe the internal storage in the process. I saw you didn't use fastboot. You could try that. Flash the Factory image via fastboot. If that fails try omap flash.
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
Oem unlock will unlock your bootloader and wipe the internal storage in the process. I saw you didn't use fastboot. You could try that. Flash the Factory image via fastboot. If that fails try omap flash.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Yup,I tried it already thru toolkit. Not working either.

Dude the toolkit blows, flash back to stock manually via adb command prompt. There are tutorials around here on how to do it. It's guaranteed to work if you don't screw it up.
Honestly flashing back to stock via adb should be something everyone should learn if you plan on flashing roms.

SoHaunted said:
Dude the toolkit blows, flash back to stock manually via adb command prompt. There are tutorials around here on how to do it. It's guaranteed to work if you don't screw it up.
Honestly flashing back to stock via adb should be something everyone should learn if you plan on flashing roms.
Click to expand...
Click to collapse
i did adb bro, its the last thing i tried, i learnt and try.
Sent to Samsung centre, they told me its my flash IC thats blown. sobs

Nexus 7 (2013) self-bricked??

Hello everyone!
I suspect that my N7(2013) bricked itself overnight. Before going to sleep, I was watching videos on YouTube. If I remember correctly it was around 45% of battery left. I just put it to sleep as usually, and gone to sleep. In the morning it was dead, so I plugged it to charger and left it that way. After an hour, when I came back I turned it on. It showed the google screen and I put it down. After a while I noticed, that it's still on google logo. I decided to hold the power button so it could reboot. After a reboot, nothing has changed. Next idea I came up with was to enter the bootloader. Tablet booted to bootloader normally and then:
-Start option hangs on google logo
-power off works just fine
-reboot bootloader also works
-recovery mode hangs indefinitely on TeamWin logo.
By now, I have no idea what to do with it. The point is would like to save my data. Is there anything that could be done?
Nexus 7 (2013) Wi-Fi
Stock KOT49H - rooted with Xposed Framework
Stock kernel
TWRP 2.6.3.0 if i'm not mistaken
Thanks in advance.

jakubmi9 said:
Hello everyone!
I suspect that my N7(2013) bricked itself overnight. Before going to sleep, I was watching videos on YouTube. If I remember correctly it was around 45% of battery left. I just put it to sleep as usually, and gone to sleep. In the morning it was dead, so I plugged it to charger and left it that way. After an hour, when I came back I turned it on. It showed the google screen and I put it down. After a while I noticed, that it's still on google logo. I decided to hold the power button so it could reboot. After a reboot, nothing has changed. Next idea I came up with was to enter the bootloader. Tablet booted to bootloader normally and then:
-Start option hangs on google logo
-power off works just fine
-reboot bootloader also works
-recovery mode hangs indefinitely on TeamWin logo.
By now, I have no idea what to do with it. The point is would like to save my data. Is there anything that could be done?
Nexus 7 (2013) Wi-Fi
Stock KOT49H - rooted with Xposed Framework
Stock kernel
TWRP 2.6.3.0 if i'm not mistaken
Thanks in advance.
Click to expand...
Click to collapse
Sound like pretty much your only option is to flash a factory image thru fastboot, you can download them from here
https://developers.google.com/android/nexus/images#razor
Make sure your boot loader is unlocked
Boot the tablet in to fastboot and run the flash-all.bat file if your using windows, of flash-all.sh for Mac and Linux.you should now have a stock tablet, with the stock recovery, I would also perform a factory data reset thru the stock recovery before rebooting the tablet.
If you would rather use a toolkit, wugs fresh is a good toolkit, and should be able to automate the above steps.
http://www.wugfresh.com
I should also point out that you need to have the proper driver's installed on your PC wugs fresh should guide you thru the process, if you don't already have them installed

I forgot to mention: Yes my bl is unlocked, but doesn't flashing factory image wipe all data? I have one more question: On my PC xperia fastboot drivers are installed. Can I use them, or do I have to install some other drivers? Fastboot recognizes device but I want to be sure.
Sent from my HTC One S using Tapatalk

jakubmi9 said:
I forgot to mention: Yes my bl is unlocked, but doesn't flashing factory image wipe all data? I have one more question: On my PC xperia fastboot drivers are installed. Can I use them, or do I have to install some other drivers? Fastboot recognizes device but I want to be sure.
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
If it is recognize in fastboot you should be good to go, and yes it will wipe you data unfortunately if you can't enter recovery, there's not much that can be done. I have never been in this situation myself, and maybe someone with more experience than I will have a solution, such as reformatting your partitions thru fastboot, but as I said I've never found myself in this situation, and if it were me I would just flash back to stock, if you happen to have a backup on your PC, you can reinstall your recovery, and restore your backup, anything else is above my understanding of this, or is not possible.

All backups are on tablet both titanium and TWRP. I just wanted to know if it's possible to recover it. I'll try to flash everything w/out wiping data. I think there was such option in wugfresh's toolkit. Maybe it's just one partition that's broken. But I've got feeling like it's going to be data partition that's broken. Thanks for help anyway. I'll try that tomorrow, because it's late night now.
Sent from my HTC One S using Tapatalk

If adb is working then you can adb pull your files assuming the file path it not corrupted
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.

jakubmi9 said:
All backups are on tablet both titanium and TWRP. I just wanted to know if it's possible to recover it. I'll try to flash everything w/out wiping data. I think there was such option in wugfresh's toolkit. Maybe it's just one partition that's broken. But I've got feeling like it's going to be data partition that's broken. Thanks for help anyway. I'll try that tomorrow, because it's late night now.
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
Just Swipe to factory reset in TWRP (leaves data in tact) and flash your Nandroid. Then reboot into system. You can adb sideload onto TWRP from your computer as well. This requires adb not fastboot.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

jakubmi9 said:
All backups are on tablet both titanium and TWRP. I just wanted to know if it's possible to recover it. I'll try to flash everything w/out wiping data. I think there was such option in wugfresh's toolkit. Maybe it's just one partition that's broken. But I've got feeling like it's going to be data partition that's broken. Thanks for help anyway. I'll try that tomorrow, because it's late night now.
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
There is a file called flash-all in the factory images, open it and remove the -w from the command line, that is what wipes the data.

LinearEquation said:
Just Swipe to factory reset in TWRP (leaves data in tact) and flash your Nandroid. Then reboot into system. You can adb sideload onto TWRP from your computer as well. This requires adb not fastboot.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I believe he cannot boot into recovery, so he cannot simply factory reset, no? I also thought that to use the adb side load feature, you had to be able to access twrp advanced>adb Sideload and that's for installing zips, no? I was thinking maybe he could adb pull a backup from the device, then install factory image, flash twrp, then restore from there? Or maybe simply reflashing the recovery? (I personally wasn't going to recommend any of this, since I don't have any personal experience in the situation) Maybe I'm missing something? or maybe I'm just an idiot, and I'm in over my head, and I need to read into things more before I post? feel free to tell me so. I'm always trying to learn about anything I can, and someone with more experience setting me straight is always a good way to achieve this lol. I like mpdamaged idea, but isn't that pretty much a dirty flash, and carries some inherent risks, seeing as how he's using xposed, I know it doesn't make any permanent changes to your system, but wouldn't this be the same concept as accepting an ota, in witch case you would need to first remove the xposed framework? Anyway hopefully someone can fill me in and he fixes his tablet, and I learn something lol.

mdamaged said:
There is a file called flash-all in the factory images, open it and remove the -w from the command line, that is what wipes the data.
Click to expand...
Click to collapse
This. You can flash a factory image without data getting cleared and it's a very simple mod. Alternative is to extract the factory image until U have all .img files extracted (have to extract twice if I remember right) then u can fastboot flash system.img and boot.img only and that should work
Another thing, have you tried to reflash TWRP since it stopped working? Could just be corrupted and a reflash could fix it.
Nexus 7 LTE
Carbon Rom
Faux Kernel
---------- Post added at 01:04 PM ---------- Previous post was at 12:58 PM ----------
@ Thisguysayswht flashing just the system.img will wipe any system mods such as Xposed, used to do it when I was on stock to be able to install OTA
Nexus 7 LTE
Carbon Rom
Faux Kernel

Don't know if you figured out how to save your data before flashing factory image but there is a very easy way to save your Titanium Backups and TWRP backups,
Plug your Nexus 7 into your computer and using MTP (assuming that still works) and look for the TB and TWRP files you can copy them to your computer and once you get your N7 back working just copy the files back to your N 7 and all your backups will be there for you to use. You can even open the files and save just what is important or save everything.

Yes I know that, but as I said tablet is totally unconnectable via adb. Can't boot to Android and can't boot to recovery. By the way I realized that when I hotbooted stock kernel from fastboot it froze on the bootloader screen but I left it plugged to PC and after a while my PC recognized "unknown MTP device" but couldn't find any drivers for it. If I hotboot TWRP.img is it gonna boot to recovery or it doesn't work like that?
Sent from my HTC One S using Tapatalk

jakubmi9 said:
Yes I know that, but as I said tablet is totally unconnectable via adb. Can't boot to Android and can't boot to recovery. By the way I realized that when I hotbooted stock kernel from fastboot it froze on the bootloader screen but I left it plugged to PC and after a while my PC recognized "unknown MTP device" but couldn't find any drivers for it. If I hotboot TWRP.img is it gonna boot to recovery or it doesn't work like that?
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
TWRP will work like that.
fastboot boot twrp-whaetver.img

If my memory serves me right, Titanium Backup can restore apps from TWRP backup, right? That way I should be able to save all my data.
Sent from my HTC One S using Tapatalk

jakubmi9 said:
If my memory serves me right, Titanium Backup can restore apps from TWRP backup, right? That way I should be able to save all my data.
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
Yes, so does Nandroid Manager.

I've just tried to hotboot TWRP 2.7 but it got stuck on TeamWin logo. It's been two or three minutes now. I don't think it will boot anymore, am I right?
Sent from my HTC One S using Tapatalk

jakubmi9 said:
I've just tried to hotboot TWRP 2.7 but it got stuck on TeamWin logo. It's been two or three minutes now. I don't think it will boot anymore, am I right?
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
Yeah, it would come up pretty quick. Something's not right...try an older version to rule that out, I know 2.6.3 worked for me using fastboot boot.

TWRP is still hanged but device manager showed up "nexus 7" with everything else unknown and code 28 which is no driver installed. Which driver should I install for it?
Sent from my HTC One S using Tapatalk

jakubmi9 said:
TWRP is still hanged but device manager showed up "nexus 7" with everything else unknown and code 28 which is no driver installed. Which driver should I install for it?
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
Officially these: http://developer.android.com/sdk/win-usb.html#download
This one worked for me until I figured out how to do it right but must be with PTP not MTP: http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi

I think that my nexus boots up everything normally but the screen just hangs on first frame of that thing. Any ideas what would that mean?
Sent from my HTC One S using Tapatalk

Bootloader - No Command Error [solved]

Here are the steps that got me to where I am.
1. Stock Pixel XL March 2017
2. Installed TWRP
3. Installed SU
4. All worked correctly for the last month
5. Saw that there was a new April release
a. It would not install as I was rooted
b. I installed the April OTA using TWRP
c. Rebooted
6. Saw that I was no longer rooted
7. Tried to go to Bootloader
8. Got dead droid with no command error
9. Went to recovery (Power + up vol) to enter sideload
10. Sideloaded the April updated
11. Rebooted
a. Same no command error
b. Went to recovery (Power + up vol) to enter factory restore
c. Rebooted
12. Tried to go into boot loader
a. Same no command error
13. Problem is that twrp was not asking for pattern And would not install correctly with image file. Solution was to keep loading the twrp image file until it asks for pattern. Then follow standard twrp /su instructions.
Thanks.

Power device off, use key combo (power+voldown) to boot bootloader. Fastboot flash stock boot.img to both slot a and b. Then reboot, take the OTA, or sideload it. Reboot. Now reboot to bootloader, fastboot boot TWRP, then reboot to twrp. Now you can flash TWRP to keep it as the recovery, or just su then reboot. Should be good.
Sent from my Pixel XL using Tapatalk

This should be posted under Q&A not development

wyrdtrtle said:
Power device off, use key combo (power+voldown) to boot bootloader. Fastboot flash stock boot.img to both slot a and b. Then reboot, take the OTA, or sideload it. Reboot. Now reboot to bootloader, fastboot boot TWRP, then reboot to twrp. Now you can flash TWRP to keep it as the recovery, or just su then reboot. Should be good.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Bootloader does not load.

When you get the dead Droid just hit vol up, no power button.
Sent from my Pixel XL using Tapatalk

Then what?

bschatzow said:
Then what?
Click to expand...
Click to collapse
I think I know where you went wrong you installed an incremental OTA with TW RP. If I'm not mistaken that new firmware had an updated bootloader and I believe that's dangerous to do. You may be out of luck

Why would the built in factory restore fix it?

bschatzow said:
Why would the built in factory restore fix it?
Click to expand...
Click to collapse
Can you get into fastboot?

So no bootloader.
Just my thoughts. I don't know if that's even possible.
Isn't it possible to edit the ota script to flash a bootloader?
Or even make a full factory update like this?

To use fastboot you need to be in bootloader mode.

mikaole said:
So no bootloader.
Just my thoughts. I don't know if that's even possible.
Isn't it possible to edit the ota script to flash a bootloader?
Or even make a full factory update like this?
Click to expand...
Click to collapse
If it is, I don't know how. I would need it to be able to load from Sideload.

Does phone boot at all? To OS?

Yes it does. Only thing not working is bootloader. Without out this I can't root.

bschatzow said:
Yes it does. Only thing not working is bootloader. Without out this I can't root.
Click to expand...
Click to collapse
Ok..if phone boots ur bootloader is still there. Phone wouldnt boot without it. You on stock rom? Hit me up on hangouts and I will try to help you if you want. For the sake of time. Im sure you wanna get this resolved ASAP.

Sent you a pm requesting contact info.

Moderator Close
Worked for a long time with BDogg718. He generously spent a great deal of his time with me and opened several Chats with Developers and No one had a solution. He is very knowledgeable and really did not want to give up. For now the solutions seems to be send it back to Google and get a replacement. It would be nice if someone could talk to Google, as a phone that has a recovery built in firmware should be able to restore itself. The dual slots seems to be a problem for them as well.

I think I had the same thing happen with me! I installed the update via TWRP. The update installation seemed to crash at the end, resulting in a reboot. The phone did install 7.1.2 successfully, but I lost root and the ability to successfully boot into any recovery. I tried flashing TWRP again, but it failed "FAILED (remote: partition recovery doesn't exist). It appeared to attempt to flash it into slot "_b", if that means anything.

TWRP will not boot on 7.1.2. At least that's the conclusion formed last night in #twrp while the devs were working with someone else with this issue. I don't think they know why yet, but I doubt it will be overly long til they figure it out.
Sent from my Pixel XL using Tapatalk

Glad to hear someone is on the case. I will be sure to send a few shekels their way for my clumsiness.

help twrp frozen in recovery

when in twrp recovery its stuck/frozen cant swipe or put in pin or flash mods. any help would be appericiated

freddienuxx said:
when in twrp recovery its stuck/frozen cant swipe or put in pin or flash mods. any help would be appericiated
Click to expand...
Click to collapse
Remove lock screen security and set it to swipe. Then boot into twrp a couple of times. If it starts working, then add your security back in.

Badger50 said:
Remove lock screen security and set it to swipe. Then boot into twrp a couple of times. If it starts working, then add your security back in.
Click to expand...
Click to collapse
ok thx gonna try now

freddienuxx said:
ok thx gonna try now
Click to expand...
Click to collapse
thank you so much that worked

freddienuxx said:
thank you so much that worked
Click to expand...
Click to collapse
Happy to help my friend :good:

After helping one of my friends troubleshoot this on his pixel 2 xl we came to the conclusion that twrp doesnt seem to like the phone having a saved fingerprint either. disabling the fingerprint and keeping the password works. we havent tried turning it back on after the first decrypt though, will post after further testing
---------- Post added at 12:55 AM ---------- Previous post was at 12:50 AM ----------
KittyRgnarok said:
After helping one of my friends troubleshoot this on his pixel 2 xl we came to the conclusion that twrp doesnt seem to like the phone having a saved fingerprint either. disabling the fingerprint and keeping the password works. we havent tried turning it back on after the first decrypt though, will post after further testing
Click to expand...
Click to collapse
so during our initial testing we had two fingerprints which seemed to upset twrp. after a successful decrypt we added one single fingerprint and now it decrypts properly

I'm getting this suddenly even though I deleted pin and fingerprints. Maybe I need to return to stock recovery again somehow? Then flash twrp all over again. Anybody know where to get stock recovery?

benjmiester said:
I'm getting this suddenly even though I deleted pin and fingerprints. Maybe I need to return to stock recovery again somehow? Then flash twrp all over again. Anybody know where to get stock recovery?
Click to expand...
Click to collapse
Flash the boot.img. That's where the stock recovery now resides.

Badger50 said:
Flash the boot.img. That's where the stock recovery now resides.
Click to expand...
Click to collapse
Thanks again Badger. It gives me "no command" with the mr. droid in surgery. Is that normal? It at least got rid of TWRP so I can try that again.

benjmiester said:
Thanks again Badger. It gives me "no command" with the mr. droid in surgery. Is that normal? It at least got rid of TWRP so I can try that again.
Click to expand...
Click to collapse
What's the "Mr droid in surgery"?? What gives you no command?? Did you run fastboot flash boot boot.img ??

Badger50 said:
What's the "Mr droid in surgery"?? What gives you no command?? Did you run fastboot flash boot boot.img ??
Click to expand...
Click to collapse
Sorry, yeah I ran fastboot flash boot boot.img, do I need to boot it like the 1st step of installing TWRP? The android symbol with the red triangle and 'no command' is what I get after trying to enter recovery after flashing stock boot (to verify stock recovery was back). I don't see stock recovery though, shows that no command and Droid red triangle instead. I'm still critical unlocked from when I fastboot flashed factory image yesterday.

benjmiester said:
Sorry, yeah I ran fastboot flash boot boot.img, do I need to boot it like the 1st step of installing TWRP? The android symbol with the red triangle and 'no command' is what I get after trying to enter recovery after flashing stock boot (to verify stock recovery was back). I don't see stock recovery though, shows that no command and Droid red triangle instead. I'm still critical unlocked from when I fastboot flashed factory image yesterday.
Click to expand...
Click to collapse
Ah, now I understand. The droid dude in surgery, is the stock recovery. You have to hold power button and volume up simultaneously a couple seconds, then release volume up. It's a little tricky though. You can just fastboot twrp now if you'd like.

Badger50 said:
Ah, now I understand. The droid dude in surgery, is the stock recovery. You have to hold power button and volume up simultaneously a couple seconds, then release volume up. It's a little tricky though. You can just fastboot twrp now if you'd like.
Click to expand...
Click to collapse
So turns out the problem both before and just now when I tried flashing twrp and it was still frozen.... I forgot to flash magisk after flashing the twrp installer zip :crying::crying: It was trying to run TWRP on an unrooted system. Doh! I booted twrp a 3rd time, flashed twrp installer AND magisk. Now all is working fine.
It's the little things that always mess me up :laugh:

benjmiester said:
So turns out the problem both before and just now when I tried flashing twrp and it was still frozen.... I forgot to flash magisk after flashing the twrp installer zip :crying::crying: It was trying to run TWRP on an unrooted system. Doh! I booted twrp a 3rd time, flashed twrp installer AND magisk. Now all is working fine.
It's the little things that always mess me up :laugh:
Click to expand...
Click to collapse
Been there myself more times than I can remember over the last 7 years I've been hacking these things. At least you figured it out ?

Badger50 said:
Been there myself more times than I can remember over the last 7 years I've been hacking these things. At least you figured it out
Click to expand...
Click to collapse
Badger50, you've been a great help and I hope you can come thru again for me. Maybe I'm missing something but I just finished updating my Pixel 2 XL to the June update and went to boot TWRP so I can flash Magisk and install TWRP but I get to the teamwin recovery project 3.2.1-2 splash screen and it's just frozen. I never got to flash anything. Any help is greatly appreciated.

rsnyc said:
Badger50, you've been a great help and I hope you can come thru again for me. Maybe I'm missing something but I just finished updating my Pixel 2 XL to the June update and went to boot TWRP so I can flash Magisk and install TWRP but I get to the teamwin recovery project 3.2.1-2 splash screen and it's just frozen. I never got to flash anything. Any help is greatly appreciated.
Click to expand...
Click to collapse
Do you have screen lock security disabled?

Badger50 said:
Do you have screen lock security disabled?
Click to expand...
Click to collapse
Yes sir. I set it to swipe.

rsnyc said:
Yes sir. I set it to swipe.
Click to expand...
Click to collapse
Did you let the OS boot up once? If so, then shut the phone off, and manually go into bootloader mode, then fastboot into twrp and try again

Badger50 said:
Did you let the OS boot up once? If so, then shut the phone off, and manually go into bootloader mode, then fastboot into twrp and try again
Click to expand...
Click to collapse
I didn't let the phone boot up. I just flashed the update and then ran the command fastboot boot twrp... I will do that and report back.

rsnyc said:
I didn't let the phone boot up. I just flashed the update and then ran the command fastboot boot twrp... I will do that and report back.
Click to expand...
Click to collapse
No worries. Let me know :good: