Can't get my data after flashing factory image - Google Pixel 2 Questions & Answers

After updating using factory image without -w key my phone boots until lockscreen appears, then if I will try to unlock - phone will reboot after ~2 seconds, also it shows com.android.phone error. Then it boot to recovery with message "can't load android system your data may be corrupt" and I can choose "try again" or "factory reset".
Updating was from 8.1 DP2 (walleye-opp6.171019.012) to stable 8.1 (walleye-opm1.171019.011), unlocked bootloader.
How to save/decrypt my data? When phone boots I can only touch fingerprint scanner but can't enter graphic key because it even doesn't appear. Flashing DP2 back causes infinte boot with G logo.

I encountered this once as well, what fixed it for me:
-From bootloader, flash the stock recovery back if it Isn't already.
-Download the latest OTA files.
- Boot to stock recovery, and select update from ADB.
- ADB sideload the OTA.
When it's done, reboot, should should boot back into Android with all your data intact.
Edit - For whatever reason the OTA file straightened out whatever error flashing the full imagine created for me.. I don't have the answer as to why, but it worked.

-Michael_ said:
-Download the latest OTA files.
Click to expand...
Click to collapse
You mean latest January OTA or firmware that I tried to update before?

wmcdrugs said:
You mean latest January OTA or firmware that I tried to update before?
Click to expand...
Click to collapse
If that's what factory image you tried to install...

-Michael_ said:
If that's what factory image you tried to install...
Click to expand...
Click to collapse
sideloading OTA after factory image doesn't help

wmcdrugs said:
sideloading OTA after factory image doesn't help
Click to expand...
Click to collapse
You probably need to flash your phone with the -W then.
I had this happen to me, couldn't fix it until I factory reset.

kinfam said:
You probably need to flash your phone with the -W then.
Click to expand...
Click to collapse
yep, but I need my data, complicating the situation is that everything is encrypted and TWRP doesn't promt to enter password for decrypt

wmcdrugs said:
yep, but I need my data, complicating the situation is that everything is encrypted and TWRP doesn't promt to enter password for decrypt
Click to expand...
Click to collapse
Under the mount options there should be an option, then enter your code. If you use a pattern, that is also numbered like a phone would be so top layer is 1,2,3, etc.

D3RP_ said:
Under the mount options there should be an option, then enter your code. If you use a pattern, that is also numbered like a phone would be so top layer is 1,2,3, etc.
Click to expand...
Click to collapse
I don't have that option
Recovery log says
Code:
begin failed, code -62Upgrading key: /data/misc/vold/user_keys/de/0upgrade_key failed, code -33e4crypt_init_user0 returned fail

Related

[Q] I can't boot into recovery mode after rooting

Hey all,
I used the "root your phone with Ubuntu" guide from the Nexus S Development forum, and then did a "fastboot oem lock" but when I try to reboot into recovery mode, the phone just sticks at the Google logo. I never see the /!\ icon to proceed further to install the 2.3.2 update manually.
I tried an "adb reboot recovery" to see if that would get me into recovery, but no luck there either, it just sits at the Google logo.
I have to remove the battery in order to boot the phone properly.
I'm curious how to proceed.
cormyn said:
Hey all,
I used the "root your phone with Ubuntu" guide from the Nexus S Development forum, and then did a "fastboot oem lock" but when I try to reboot into recovery mode, the phone just sticks at the Google logo. I never see the /!\ icon to proceed further to install the 2.3.2 update manually.
I tried an "adb reboot recovery" to see if that would get me into recovery, but no luck there either, it just sits at the Google logo.
I have to remove the battery in order to boot the phone properly.
I'm curious how to proceed.
Click to expand...
Click to collapse
you need to flash a recovery via fastboot.
Download the clockwork recovery recovery-clockwork-3.0.0.0-crespo.img image, and save it to the ..\android-sdk-windows\tools directory
renamed it to recovery.img
then type...
fastboot flash recovery recovery.img
and hit enter
Click to expand...
Click to collapse
simms22 said:
you need to flash a recovery via fastboot.
Click to expand...
Click to collapse
There's a new version of CWM to flash...that one you're linking is causing issues to people trying to apply updates. CWM is now 3.0.0.5
http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.5-crespo.img
distortedloop said:
There's a new version of CWM to flash...that one you're linking is causing issues to people trying to apply updates. CWM is now 3.0.0.5
http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.5-crespo.img
Click to expand...
Click to collapse
fixed it, thanks!
simms22 said:
you need to flash a recovery via fastboot.
Click to expand...
Click to collapse
Huh, I thought the recovery reset itself... Thanks for the info.
Ah, drag, I had already locked my nexus back up, and unlocking it is going to wipe the phone all over again.
I think if I'm going to wipe my phone anyway, I'll just wipe it back to factory and leave the phone unrooted... Too much hassle with the internal SD getting wiped every time.
cormyn said:
Huh, I thought the recovery reset itself... Thanks for the info.
Click to expand...
Click to collapse
Only after a successful reboot to the normal system, and only if you're on 2.3.1 or greater, and only if you've not renamed the /etc/install-recovery.sh file.
cormyn said:
Ah, drag, I had already locked my nexus back up, and unlocking it is going to wipe the phone all over again.
I think I'm just going to unroot my phone. Too much hassle with the internal SD getting wiped every time.
Click to expand...
Click to collapse
Yeah, that sucks. I don't relock my bootloader.
Incidentally, I had flashed a recovery, it was called recovery-clockwork-herring.img as suggested in the original "root your nexus s with ubuntu" guide. Maybe someone should tell that author to suggest a newer/better recovery.
cormyn said:
Incidentally, I had flashed a recovery, it was called recovery-clockwork-herring.img as suggested in the original "root your nexus s with ubuntu" guide. Maybe someone should tell that author to suggest a newer/better recovery.
Click to expand...
Click to collapse
Use this one: http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.5-crespo.img
Thanks for the info, distortedloop. I think I'm just going to factory wipe and leave my phone unrooted for a while.
... assuming of course that a factory reset will get me back to a place where I can install OTA updates, or a recovery mode where I can manually install update.zip files?
distortedloop said:
Use this one: http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.5-crespo.img
Click to expand...
Click to collapse
i was using the older CW recovery 3.0.0.0 also, so i just decided to flash version 3.0.0.5. since im at work, i cant fastboot it to my phone. i did it via the terminal emulator on my phone. 1st time i got a bunch of out of space errors so i booted into recovery just to check, and it was gone. nothing there. so i rebooted and tried it again via terminal. 2nd time was a success. to flash the recovery in the terminal emulator, download the recovery and put it on the root of your sd card and rename it recovery.img . now open the terminal and type...
su(press enter)
flash_image recovery /sdcard/recovery.img(press enter)
reboot recovery(press enter)
well, apparently a factory wipe was a bad move, 'cause now the phone rebooted and is stuck at the Google logo, like it's trying to get back into the recovery.
cormyn said:
Thanks for the info, distortedloop. I think I'm just going to factory wipe and leave my phone unrooted for a while.
... assuming of course that a factory reset will get me back to a place where I can install OTA updates, or a recovery mode where I can manually install update.zip files?
Click to expand...
Click to collapse
Factory reset won't remover the su binary and symlinks it makes. Factory reset only wipes the /data partition, not the /system one.
An oem lock, then oem unlock might, but I'm not sure...that definitely wipes the sdcard, though, unlike a factory reset does, so back that up first!
There's some thread on here someplace about how to completely remove root.
Pulled the battery, went back into bootloader mode, did a 'fastboot oem unlock', then flashed the crespo 3.0.5 img, and then 'fastboot oem lock' and the phone reboots properly.
Thanks again!

[Q] Nexus 5, internal storage 0Mb

Hi everyone,
I am French and I use a translator to talk to you, sorry for language mistakes.
I just ask for your help because at last my nexus one days is blocked.
When I go into TWRP he asks me a passeword and my internal memory shows 0MB
Unable to flash a rom stock, steps go well but it does not change anything in the nexus.
Unable to update bootloader, the old version back
I focused in fastboot and recovery (TWRP)
Do you have a solution?
Thanking you in advance
Loïc
Sounds like uv messed up the partitions. unsure if theres a fix on this
Try
fastboot flash cache cache.img
Where cache.img is from the factory image
jd1639 said:
Try
fastboot flash cache cache.img
Where cache.img is from the factory image
Click to expand...
Click to collapse
This is happening without any problems but it does not change the problem.
I'm lost ...
in TWRP i have
E:Unable to mount ' /cache'
E:Unable to mount ' /persist'
E:Unable to mount storage
Problems:
Internal-memory found in TWRP (internal storage: 0MB)
-In flash, everything seems to work well but the file does not replace those on the laptop (eg when I erase bootloader and flash I HHZ11K to replace HHZ11D there was the nexus, the ben 11D never deletes
-Unable to wipe dalvik Cache
TWRP-request a password, so I'm Cancel to use the recovery
Impossible to replace the recovery with a stock version everything seems ok but always returns TWRP
Thank you for your help
worfeur said:
Problems:
Internal-memory found in TWRP (internal storage: 0MB)
-In flash, everything seems to work well but the file does not replace those on the laptop (eg when I erase bootloader and flash I HHZ11K to replace HHZ11D there was the nexus, the ben 11D never deletes
-Unable to wipe dalvik Cache
TWRP-request a password, so I'm Cancel to use the recovery
Impossible to replace the recovery with a stock version everything seems ok but always returns TWRP
Thank you for your help
Click to expand...
Click to collapse
What version of twrp are you using?
jd1639 said:
What version of twrp are you using?
Click to expand...
Click to collapse
I use twrp 2.6.3.2
worfeur said:
I use twrp 2.6.3.2
Click to expand...
Click to collapse
Try to flash this in fastboot, fastboot flash recovery recovery.img. Where recovery.img is the file below. If it installs, wipe cache within it
http://d-h.st/nbu. It's 2.6.3.4
This very same thing happened to me this morning, and a friends Nexus 5 the other day. Not sure why but the fact that you are the third I have seen in the last few days is making me believe it's a common issue. It happened to me, I watched a movie, fell asleep, and woke up to "Type password to decrypt storage" message, and the same message you have in Recovery as well. To my knowledge, I never set a password, let alone while I slept.
What happened is somehow the "userdata" partition on the phone got corrupt. When this happens, for some reason it thinks the partition was encrypted. You can attempt to fix it with a repair utility, or
Go to the bootloader (Hold Volume Down and Power when turning the phone on) then install and use adb and type this
Code:
adb e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
Or from recovery, run a command and and run
Code:
e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
See if that works. If it does, your data will be fine. I did not find this fix until after I tried a full reset but it worked for my friend.
If that does not work, you will have to factory reset your phone. You will lose all data on the phone. Hopefully you have a backup. This worked for me.
Use tools from here:
https://developers.google.com/android/nexus/images#hammerhead
and follow instructions here http://forum.xda-developers.com/showthread.php?t=2513701
I see you mentioned you tried this, however you may want to try it again, and follow those steps, make sure to go to the Nexus 5's factory recovery after and "Reset to Factory". Likewise it needs to be run from bootloader, not recovery. And you must have unlocked bootloader.
**EDIT** What firmware were you running? CyanogenMod?
N5
1. you unlock it
2. recovery with software.
Thanks
Wergin said:
1. you unlock it
2. recovery with software.
Thanks
Click to expand...
Click to collapse
What firmware were you using prior to this happening? I would like to know as me and a friend were on CyanogenMod11 (CM11) and this happened to us as well. If CyanogenMod or TWRP is causing it, it should be reported as a bug.
worfeur said:
Hi everyone,
I am French and I use a translator to talk to you, sorry for language mistakes.
I just ask for your help because at last my nexus one days is blocked.
When I go into TWRP he asks me a passeword and my internal memory shows 0MB
Unable to flash a rom stock, steps go well but it does not change anything in the nexus.
Unable to update bootloader, the old version back
I focused in fastboot and recovery (TWRP)
Do you have a solution?
Thanking you in advance
Loïc
Click to expand...
Click to collapse
Why don't you try Clock work mod recovery. Sounds like twrp isn't meshing well with you device. I had issues with all the way to lastest version.Maybe CWM might help.
WoodburyMan said:
What firmware were you using prior to this happening? I would like to know as me and a friend were on CyanogenMod11 (CM11) and this happened to us as well. If CyanogenMod or TWRP is causing it, it should be reported as a bug.
Click to expand...
Click to collapse
Sorry, I do not know the firmware that was installed
It is a device used
habitformer said:
Why don't you try Clock work mod recovery. Sounds like twrp isn't meshing well with you device. I had issues with all the way to lastest version.Maybe CWM might help.
Click to expand...
Click to collapse
when I flash a custom-recovery (stock or cwn) TWRP 2.6.3.2 always returns
I had this same issue.
I went into fastboot and erased recovery and userdata, then ran the flashall.bat in the factory image.
TWRP had a Password. It happened after I tried to flash Cataclysm and it bootlooped (Forgot to check MD5's, not sure why a corrupt download flashed).
WoodburyMan said:
This very same thing happened to me this morning, and a friends Nexus 5 the other day. Not sure why but the fact that you are the third I have seen in the last few days is making me believe it's a common issue. It happened to me, I watched a movie, fell asleep, and woke up to "Type password to decrypt storage" message, and the same message you have in Recovery as well. To my knowledge, I never set a password, let alone while I slept.
What happened is somehow the "userdata" partition on the phone got corrupt. When this happens, for some reason it thinks the partition was encrypted. You can attempt to fix it with a repair utility, or
Go to the bootloader (Hold Volume Down and Power when turning the phone on) then install and use adb and type this
Code:
adb e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
Or from recovery, run a command and and run
Code:
e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
See if that works. If it does, your data will be fine. I did not find this fix until after I tried a full reset but it worked for my friend.
If that does not work, you will have to factory reset your phone. You will lose all data on the phone. Hopefully you have a backup. This worked for me.
Use tools from here:
https://developers.google.com/android/nexus/images#hammerhead
and follow instructions here http://forum.xda-developers.com/showthread.php?t=2513701
I see you mentioned you tried this, however you may want to try it again, and follow those steps, make sure to go to the Nexus 5's factory recovery after and "Reset to Factory". Likewise it needs to be run from bootloader, not recovery. And you must have unlocked bootloader.
**EDIT** What firmware were you running? CyanogenMod?
Click to expand...
Click to collapse
thank you for your help
I have access to adb fastboot mode by boot recovery.img (recovery stock google)
and using the control slidload ADB
but impossible to get the command line
but when I type ADB Devices, my phone is found
otherwise I can not do a stock restoration because the bootloader does not update (KKX11D then I flashed back KKX11K) when I do well:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
Beauenheim said:
I had this same issue.
I went into fastboot and erased recovery and userdata, then ran the flashall.bat in the factory image.
TWRP had a Password. It happened after I tried to flash Cataclysm and it bootlooped (Forgot to check MD5's, not sure why a corrupt download flashed).
Click to expand...
Click to collapse
thank you I'll try it tonight but I think I already tried
worfeur said:
thank you I'll try it tonight but I think I already tried
Click to expand...
Click to collapse
In twrp 2.6.3.4 go into wipe and format data. You will lose all your data but should fix your problem
jd1639 said:
In twrp 2.6.3.4 go into wipe and format data. You will lose all your data but should fix your problem
Click to expand...
Click to collapse
the problem when another flash recovery is that the 2.6.3.2 version still returns
let me explain:
fastboot erase recovery
fastboot flash recovery recovery TWRP 2.6.3.4.img
* I go into the recovery but still 2.6.3.2
I feel that TWRP to secure or encrypted my internal memory
worfeur said:
the problem when another flash recovery is that the 2.6.3.2 version still returns
let me explain:
fastboot erase recovery
fastboot flash recovery recovery TWRP 2.6.3.4.img
* I go into the recovery but still 2.6.3.2
I feel that TWRP to secure or encrypted my internal memory
Click to expand...
Click to collapse
Can you format data in 2.6.3.2? I'm thinking you have a bigger problem as you've already tried to flash the factory image and it did not work.

[Q] TF 700 only boots into TWRP - please advise this NOOB!

Greetings -
I have an unlocked TF700 (twrp v 2.5.0.0) and I was running cromi-x. it began to crash a lot so i tried to flash a new rom and i must've done something wrong because now the tablet will not boot up. I can get into twrp and perform the options listed (install, backup, restore, wipe, mount, settings, advanced, reboot) but nothing seems to help. I haven't played with this in probably 6 months so i'm not sure where to start. Navigating these forums is like reading latin to me. I'm sure there is an explanation for this but I can't find it. Can some one link me to an existing thread if this has been discusses previously or help me out? I can't seem to get anything working on this and it's driving me crazy. I know I need to provide extra information to help identify this issue but i'm not sure what that info that is. Any help would be appreciated!
Also, I've tried a factory reset from twrp as well and it gives me the following messages
E:unable to mount '/external_sdcard
Updating partition details...
E:Mount: Unable to find partition, for path '/'
When I reboot following this, it takes me directly to TWRP.
I'm guessing my tablet can't find my SD card? Maybe that's an easy fix?
Thanks everyone for looking at this and thanks for anyone that takes some time to educate me.
Most if all: Do not do anything desperate anymore. Your tablet is savable at this point but close to being bricked! Wait for help, I have to go to work now, but will be back tonight.
In the meantime write up a list of things you did as good as you can remember, find your bootloader version and post that.
berndblb said:
Most if all: Do not do anything desperate anymore. Your tablet is savable at this point but close to being bricked! Wait for help, I have to go to work now, but will be back tonight.
In the meantime write up a list of things you did as good as you can remember, find your bootloader version and post that.
Click to expand...
Click to collapse
Thank you for the reply. My bootloader is "<1.00 e> released by 10.6.1.14.8-20130514"
It also says "key driver not found" immediately before the bootloader data upon turn on
Ok, good start. Now - what's you situation exactly? Can you boot into the bootloader or is recovery the only thing accessible right now?
berndblb said:
Ok, good start. Now - what's you situation exactly? Can you boot into the bootloader or is recovery the only thing accessible right now?
Click to expand...
Click to collapse
I can enter the bootloader (hold power on and volume down correct?) and it displays RCK, android and wipe data options. It only takes me to recovery tho.
Hoggs17 said:
I can enter the bootloader (hold power on and volume down correct?) and it displays RCK, android and wipe data options. It only takes me to recovery tho.
Click to expand...
Click to collapse
Please try to be very specific. When you enter the bootloader, does it stay there or does it automatically, without your interaction, boot into TWRP?
Did you use the Wipe Data option from the bootloader or do a Factory Reset from the Settings menu?
Do you have fastboot setup on your PC?
If not, find the instructions to setup fastboot here: http://forum.xda-developers.com/showthread.php?t=2688891
You will need it.
berndblb said:
Please try to be very specific. When you enter the bootloader, does it stay there or does it automatically, without your interaction, boot into TWRP?
Did you use the Wipe Data option from the bootloader or do a Factory Reset from the Settings menu?
Do you have fastboot setup on your PC?
If not, find the instructions to setup fastboot here: http://forum.xda-developers.com/showthread.php?t=2688891
You will need it.
Click to expand...
Click to collapse
When i enter the bootloader, it stays on the screen. If i reboot without entering the bootloader, it goes directly into TWRP. I am not sure if i used the wipe data option or the factory reset (it has been probably 6 months). I will install fastboot on my PC now.
Interesting.
I assume you do not have any data on the tablet you need to preserve, right?
Once you got fastboot setup and "fastboot devices" returns the serial number we'll clear your misc partition (just in case) and fastboot erase your data partition. I think after that you should be able to boot the rom.
Actually, remind me, what was the last thing you flashed? Did you update TWRP already or are you still on 2.5.0?
berndblb said:
Interesting.
I assume you do not have any data on the tablet you need to preserve, right?
Once you got fastboot setup and "fastboot devices" returns the serial number we'll clear your misc partition (just in case) and fastboot erase your data partition. I think after that you should be able to boot the rom.
Actually, remind me, what was the last thing you flashed? Did you update TWRP already or are you still on 2.5.5?
Click to expand...
Click to collapse
Correct, i don't need any data on this tablet; i can wipe it clean. I think the last thing i flashed was Cromi-X (not sure the number; was back in August probably. My TWRP is 2.5.0.0; i haven't updated that one. I will try to do the fast stuff tomorrow morning; too late tonight. Thanks for all your help.
Cool. I need to sleep too
Yeah we're going to have to update your TWRP version. 2.5.0 is too old to flash anything recent. And while we're at it we'll update your bootloader too. All in good time. See ya tomorrow
berndblb said:
Cool. I need to sleep too
Yeah we're going to have to update your TWRP version. 2.5.0 is too old to flash anything recent. And while we're at it we'll update your bootloader too. All in good time. See ya tomorrow
Click to expand...
Click to collapse
I have installed the fastboot on my PC, ran it figured out my serial number as well. I will wait for your next instruction so that I don't mess anything up (again).
Hoggs17 said:
I have installed the fastboot on my PC. I will wait for your next instruction so that I don't mess anything up (again).
Click to expand...
Click to collapse
Till Bernd wakes up you could read his excellent guide; most question are answered here:
http://forum.xda-developers.com/showthread.php?t=2688891
das chaos said:
Till Bernd wakes up you could read his excellent guide; most question are answered here:
http://forum.xda-developers.com/showthread.php?t=2688891
Click to expand...
Click to collapse
yes, i have been reading that as well but as I don't want to make a mistake and completely brick this thing; i will research this document and educate myself
Hoggs17 said:
yes, i have been reading that as well but as I don't want to make a mistake and completely brick this thing; i will research this document and educate myself
Click to expand...
Click to collapse
Ok, here's my thinking:
I don't know why the tablet reboots to recovery if you try to boot Android - never seen that before.
That it refuses to boot the rom - seen that plenty
That it only boots to recovery and not even to the bootloader - seen that quite a few times if the user used Wipe Data or factory reset from settings.
You seem to a have a mix of both which makes it unique.
So my advice is:
to clear the misc partition (where a "format data" request may still be lurking) in fastboot
wipe the data partition in fastboot - just general housekeeping
flash a new bootloader and recovery using your current recovery
Use the new recovery to flash the rom of your choice - which one do you have in mind?
So let's start. First make sure you have a fastboot connection:
Code:
fastboot devices
Then erase misc and user data
Code:
fastboot erase misc
fastboot erase userdata
You are still in the bootloader menu, push the Vol Up button on the flashing RCK to enter recovery
Flash the 10.6.1.14.10 bootloader, packaged with TWRP 2.8.4.0 from this post (2nd zip from the bottom)
http://forum.xda-developers.com/showpost.php?p=55238386&postcount=3
You have to reboot after this step for the bootloader and recovery to install.
You'll see a brief blue progress bar, then the tablet will reboot again. At this point hold Vol Down to enter the bootloader and then enter recovery which should be 2.8.4.0 at this point.
Flash the rom
Good luck!
"Flash the 10.6.1.14.10 bootloader, packaged with TWRP 2.8.4.0 from this post (2nd zip from the bottom)
http://forum.xda-developers.com/showpost.php?p=55238386&postcount=3
You have to reboot after this step for the bootloader and recovery to install.
You'll see a brief blue progress bar, then the tablet will reboot again. At this point hold Vol Down to enter the bootloader and then enter recovery which should be 2.8.4.0 at this point.
Flash the rom"
I have successfully completed the steps preceeding the above suggestions; I am not sure how to flash the bootloader. I am trying to follow the guide posted here (http://forum.xda-developers.com/showthread.php?t=2688891) by using the command code
fastboot -i 0x0B05 flash recovery twrp.blob
however, i cannot rename my blob file (contained in the 10.6.1.14.10 bootloader "second zip from the bottom" that you linked me to) to twrp.blob. it is simply called blob. am I doing this wrong? i tried using the above command with just blob and it didn't do anything.
on another thread (http://forum.xda-developers.com/showthread.php?t=2688891) you recommend visiting (http://techerrata.com/browse/twrp2/tf700t) and downloading the latest version of twrp. Should I download this file (openrecovery-twrp-2.8.5.0-tf700t.blob) and rename this to twrp.blob?
Also I am not sure on a new custom rom; i've been out of the game for a while; any suggestions?
No the zip is a flashable package. You install just like a rom zip:
Choose Install in TWRP, navigate to the zip, check the box for signature verification and swipe the button.
This will write the bootloader and recovery to the staging partition. When you reboot the bootloader writes them to their proper partitions, then it reboots the tablet again. That's when you can "catch" the boot process to go straight back into recovery and flash the rom.
Maybe you want to try CROMI-X first. Still a very good rom and very stable. Or check the dev section, many to choose from...
berndblb said:
No the zip is a flashable package. You install just like a rom zip:
Choose Install in TWRP, navigate to the zip, check the box for signature verification and swipe the button.
This will write the bootloader and recovery to the staging partition. When you reboot the bootloader writes them to their proper partitions, then it reboots the tablet again. That's when you can "catch" the boot process to go straight back into recovery and flash the rom.
Maybe you want to try CROMI-X first. Still a very good rom and very stable. Or check the dev section, many to choose from...
Click to expand...
Click to collapse
gotcha. the only problem is; after i use the command on the bootloader and i go to Install on twrp; i don't see the zip to install...i retried it again (repeated the commands) but i'm not seeing the zip in my directory anywhere. hmmm...
Hoggs17 said:
gotcha. the only problem is; after i use the command on the bootloader and i go to Install on twrp; i don't see the zip to install...i retried it again (repeated the commands) but i'm not seeing the zip in my directory anywhere. hmmm...
Click to expand...
Click to collapse
You got the zip on your microSD, right?
Tap on the field where it says Internal Storage and switch to external
berndblb said:
You got the zip on your microSD, right?
Tap on the field where it says Internal Storage and switch to external
Click to expand...
Click to collapse
oops; yeah i was blind; forgot to switch the internal to external storage. ok now I see twrp and I am able to swipe to flash but the flash fails and gives me the following message
Updating partition details...
Installing '/external_sdcard/TF700_10.6.1.14.10_US_Boot_TWRP_2840-signed.zip
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Verifying zip signature...
E: Zip signature verification failed: 1
Error flashing zip '/external_sdcard/TF700_10.6.1.14.10_US_Boot_TWRP_2840-signed.zip'
Updating partition details...
with a big red Failed right above the home key.
Hoggs17 said:
oops; yeah i was blind; forgot to switch the internal to external storage. ok now I see twrp and I am able to swipe to flash but the flash fails and gives me the following message
Updating partition details...
Installing '/external_sdcard/TF700_10.6.1.14.10_US_Boot_TWRP_2840-signed.zip
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Verifying zip signature...
E: Zip signature verification failed: 1
Error flashing zip '/external_sdcard/TF700_10.6.1.14.10_US_Boot_TWRP_2840-signed.zip'
Updating partition details...
with a big red Failed right above the home key.
Click to expand...
Click to collapse
..... which means the file got corrupted during download or copy to the card.
That's what signature verification is for.
Download it again.

Error after Installing twrp

So I just installed twrp 3.2.2 using the img and then flashing the zip file and it seemed to work correctly, however when I tried to reboot the system, it became stuck on the loading screen, the one with the red dot that moves around. Then I went into the twrp install menu and saw that for the sdcard menu, I have a bunch of files that are just a series of letters like 7kWTXiU752ZJOHWv9DjsYD. Does anyone know how to fix this? Never seen this error before.
blaster42 said:
So I just installed twrp 3.2.2 using the img and then flashing the zip file and it seemed to work correctly, however when I tried to reboot the system, it became stuck on the loading screen, the one with the red dot that moves around. Then I went into the twrp install menu and saw that for the sdcard menu, I have a bunch of files that are just a series of letters like 7kWTXiU752ZJOHWv9DjsYD. Does anyone know how to fix this? Never seen this error before.
Click to expand...
Click to collapse
the quick and dirty way of fixing would be to format data in twrp and phone will boot. the series of number is your files on the phone that are encrypted. When you first start twrp. it should have asked for password which is your lock screen password. You could try installing Magisk-v16.7 link https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589. it could allow the os to boot.
MrSteelX said:
the quick and dirty way of fixing would be to format data in twrp and phone will boot. the series of number is your files on the phone that are encrypted. When you first start twrp. it should have asked for password which is your lock screen password. You could try installing Magisk-v16.7 link https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589. it could allow the os to boot.
Click to expand...
Click to collapse
Huh, it never asked for the lock screen password. My password wasn't set up when I first installed twrp.
blaster42 said:
Huh, it never asked for the lock screen password. My password wasn't set up when I first installed twrp.
Click to expand...
Click to collapse
if no password is setup, then it would not ask 1. are you on stock 5.1.9?
MrSteelX said:
if no password is setup, then it would not ask 1. are you on stock 5.1.9?
Click to expand...
Click to collapse
Yup
blaster42 said:
Yup
Click to expand...
Click to collapse
here is patch boot.img http://www.mediafire.com/file/4gbcsjd1ph41140/boot.img/file
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
you will still need to flash twrp again after flashing this if you want twrp.
MrSteelX said:
here is patch boot.img http://www.mediafire.com/file/4gbcsjd1ph41140/boot.img/file
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
you will still need to flash twrp again after flashing this if you want twrp.
Click to expand...
Click to collapse
I've formatted data and now my phone boots again, so thanks so much for the help. I rebooted into recovery and still have twrp on there, is it a faulty one? Should I reflash? Will these img work with twrp 3.2.2?
The phone defaults to being encrypted . . .
I would give myself a security PIN number first and power off and on to see the PIN is working okay first.

can I install custom bootloader without losing data

My pixel 3 is not booting up right now. Asks me to do a factory reset. Can I install a custom bootloader like twrp now without losing my data? I want to mount the data partition, backup my files and then do a factory reset. The phone is stock and locked right now, have never installed a custom rom/bootloader on it.
sdxda said:
My pixel 3 is not booting up right now. Asks me to do a factory reset. Can I install a custom bootloader like twrp now without losing my data? I want to mount the data partition, backup my files and then do a factory reset. The phone is stock and locked right now, have never installed a custom rom/bootloader on it.
Click to expand...
Click to collapse
If you are still on Android Pie and have an unlocked bootloader, you should be able to install TWRP. If your bootloader is still locked, you can't install a custom bootloader until you unlock the bootloader. Unlocking it will wipe the phone. If you have Android 10, you can't install TWRP. TWRP does not work on a Pixel 3 with Android 10.
dcarvil said:
If you are still on Android Pie and have an unlocked bootloader, you should be able to install TWRP. If your bootloader is still locked, you can't install a custom bootloader until you unlock the bootloader. Unlocking it will wipe the phone. If you have Android 10, you can't install TWRP. TWRP does not work on a Pixel 3 with Android 10.
Click to expand...
Click to collapse
Thanks, I'm on 10 and unlocked :/
sdxda said:
Thanks, I'm on 10 and unlocked :/
Click to expand...
Click to collapse
What happens when you boot to recovery mode? You might have to wait a really long time (30 to 60 minutes) for it to recover.
If that doesn't work, and you enabled USB debugging when you unlocked the boot loader, you should be able to flash a factory image. Be sure to edit flash-all.bat (or flash-all.sh if on Linux) to remove the -w from the flashboot command at the bottom of the file. Removing the -w will prevent it from wiping your data. Be sure you execute the edited file, and not the original file. Also, be sure to get the factory image, not an OTA image, and to download the latest platform-tools. This thread is a good guide to follow to flash the image. https://forum.xda-developers.com/pixel-3/how-to/complete-pixel-3-how-to-guide-newbie-t3922269
I'd try to flash an Android 10 image and recover the data instead of trying to downgrade to Android Pie and install TWRP.
dcarvil said:
What happens when you boot to recovery mode? You might have to wait a really long time (30 to 60 minutes) for it to recover.
If that doesn't work, and you enabled USB debugging when you unlocked the boot loader, you should be able to flash a factory image. Be sure to edit flash-all.bat (or flash-all.sh if on Linux) to remove the -w from the flashboot command at the bottom of the file. Removing the -w will prevent it from wiping your data. Be sure you execute the edited file, and not the original file. Also, be sure to get the factory image, not an OTA image, and to download the latest platform-tools. This thread is a good guide to follow to flash the image. https://forum.xda-developers.com/pixel-3/how-to/complete-pixel-3-how-to-guide-newbie-t3922269
I'd try to flash an Android 10 image and recover the data instead of trying to downgrade to Android Pie and install TWRP.
Click to expand...
Click to collapse
Recovery mode is fine. I sideloaded the latest ota 10.0.0 (QP1A.191105.003, Nov 2019).. it's 1.3 gigs. Still didnt help. Should I try an older OTA version before trying the factory image?
And my bootloader is locked, so can I flash the factory image? I'm getting the image now and will try anyways, just not sure if I want to try an older OTA first.
sdxda said:
Recovery mode is fine. I sideloaded the latest ota 10.0.0 (QP1A.191105.003, Nov 2019).. it's 1.3 gigs. Still didnt help. Should I try an older OTA version before trying the factory image?
And my bootloader is locked, so can I flash the factory image? I'm getting the image now and will try anyways, just not sure if I want to try an older OTA first.
Click to expand...
Click to collapse
okay so can't flash without unlocking. Going to try an older ota.
sdxda said:
okay so can't flash without unlocking. Going to try an older ota.
Click to expand...
Click to collapse
I don't think an OTA will fix a boot problem. According to https://developers.google.com/android/images you have to unlock the bootloader to flash a factory image. Unlocking the bootloader will wipe your data. I'm not sure the unlock command will work if you have not enabled OEM unlocking in Developer Options.
Sorry, I don't see any way to preserve your data. Maybe someone smarter than me will have some ideas.

Categories

Resources