Related
Hi.
I am about to RMA my phone and need to lock the bootloader..
BUT - I cant get into recovery.
I have tried everything, reverted to stock image (followed the thread how to return to stock image) , but no matter what, I cant boot into recovery.
I can get into the bootloader / fastboot , ie and run adb commands, but I cant boot into recovery.. its just flashed the google logo and then gets tuck there ..
Is there any way I can relock the bootloader given my predicament?
it's doing some other pretty weird stuff.. pretty sure the battery is near flat, but If I plug it in to charge, it flashes the charging logo and then about 10 seconds tries to boot,.. flashes the google logo and then about 1 second ofthe spinning colour circles.. then just black screen.. even if I go into the bootloader and hit power off..
If anyone has any Ideas I would love to know.
Does anyone know if google will RMA with an unlocked bootloader or am i screwed? This sucks!
1) you cannot run adb commands from fastboot. Adb commands only work in android or recovery
2) you just use fastboot commands from fastboot (bootloader). Accessing recovery is not part of the process
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
You lock the bootloader from the bootloader, but it sounds like you have lots of problems. I would just send it back if you can't lock it
Sent from my Nexus 5
Just boot into bootloader and run fastboot oem lock. No need to go to recovery for locking the bootloader. If you have flashed the stock images already the data was already wiped.
Sent from my Nexus 5 using Tapatalk
Why is there a whole thread about relocking the bootloader and a zip to flash via CWM (talking about resetting the tamper flag?)
http://forum.xda-developers.com/showthread.php?t=2513701
If I just do fastboot oem lock isn't Google going to be able to tell I have been flashing..?
llewelld said:
Why is there a whole thread about relocking the bootloader and a zip to flash via CWM (talking about resetting the tamper flag?)
http://forum.xda-developers.com/showthread.php?t=2513701
If I just do fastboot oem lock isn't Google going to be able to tell I have been flashing..?
Click to expand...
Click to collapse
If you have a custom recovery/ROM on the phone then of course they'll know what you've done! You have to flash the factory image and then relock the bootloader and you'll be OK
EddyOS said:
If you have a custom recovery/ROM on the phone then of course they'll know what you've done! You have to flash the factory image and then relock the bootloader and you'll be OK
Click to expand...
Click to collapse
Why don't use Bootunlocker? You can unlock/relock directly from the Nex5 without loss data and no wipe!!
I seriously doubt that they will check the tamper flag. Maybe sprint would, but I doubt that Google will. Just relock the bootloader and send it in bro. You'll be OK. I've sent nexus 7, nexus 4 both back with an unlocked bootloader and got my replacement no questions asked.
Sent from my Nexus 5 using Tapatalk
enzippo said:
Why don't use Bootunlocker? You can unlock/relock directly from the Nex5 without loss data and no wipe!!
Click to expand...
Click to collapse
because I cant boot. - cant get past the google logo so I cant run any apps..
llewelld said:
because I cant boot. - cant get past the google logo so I cant run any apps..
Click to expand...
Click to collapse
What about trying Wugfresh toolkit he has a setting in it for recovering from a none booting/softbricked device.
Download the factory images, unzip the file, while in the bootloader, click on flash-all.bat. when that's done, get back into the bootloader, and open a command window, and type fastboot oem lock. Now you are back to a stock phone.
Sent from my Nexus 5 using XDA Premium 4 mobile app
lyall29 said:
Download the factory images, unzip the file, while in the bootloader, click on flash-all.bat. when that's done, get back into the bootloader, and open a command window, and type fastboot oem lock. Now you are back to a stock phone.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks.. did all that... and have had to RMA the phone.. its screwed just died.. I think the first time I have had a phone just die that is so new and not from any soft of physical damage. Thanks!
I tried to flash my Nexus 5 with the factory image from Google, downloaded a fresh SDK and the image, unzipped it, ran flash-all.bat and the bootloader image tells me
"invalid bootloader image"
Click to expand...
Click to collapse
Now my phone doesn't want to boot up, and trying to flash 5.0.1 hasn't solved a thing. I'm at a loss to what I'm supposed to do to recover from this situation, I can still boot into fastboot but recovery mode doesn't work.
What should I do?
LuckyMethod said:
I tried to flash my Nexus 5 with the factory image from Google, downloaded a fresh SDK and the image, unzipped it, ran flash-all.bat and the bootloader image tells me
Now my phone doesn't want to boot up, and trying to flash 5.0.1 hasn't solved a thing. I'm at a loss to what I'm supposed to do to recover from this situation, I can still boot into fastboot but recovery mode doesn't work.
What should I do?
Click to expand...
Click to collapse
What bootloader version are you on?
Have you tried redownloading/check md5?
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
Got today's 1.5 update - 3.7 MB. Figured it was minor fixes they discovered. Installed - now my phone is not working. When I restarted, it froze on the splash screen. Several tries - same result. Won't boot to recovery. Will boot to Fastboot - try Recovery or Start from there, freezes on splash screen. Only choice that works is turn off. If you get the 1.5 update, you might want to wait before installing it.
Update worked fine for me.
rbsummers said:
Got today's 1.5 update - 3.7 MB. Figured it was minor fixes they discovered. Installed - now my phone is not working. When I restarted, it froze on the splash screen. Several tries - same result. Won't boot to recovery. Will boot to Fastboot - try Recovery or Start from there, freezes on splash screen. Only choice that works is turn off. If you get the 1.5 update, you might want to wait before installing it.
Click to expand...
Click to collapse
If you can actually get to fastboot, you could try flashing the full image zip from the Essential website, assuming your BL is unlocked (is it?). You will lose your data, but still better than a non-working phone...
FWIW, this update worked for me. Rooted phone, no TWRP. Unrooted first by reverting to the original boot.img, did an OTA update, rebooted, then patched the new boot.img with Magisk, and flashed to get the root back, as usual. No issues. The only thing that was a bit weird was that it took a hell of a long time to optimize apps when apying the update - it was sitting at that status message for a good 10-15 min.
Same Problem
After update I have the same problem the phone will only boot to the splash screen. I can reach the boot loader but its locked so that is useless.
Yeah, always leave bootloader unlocked to salvage bad updates
HueyT said:
Yeah, always leave bootloader unlocked to salvage bad updates
Click to expand...
Click to collapse
Is it sufficient to have OEM unlock enabled in developer settings or must you also NOT use "fastboot flashing lock" ?
Verlog5454 said:
Is it sufficient to have OEM unlock enabled in developer settings or must you also NOT use "fastboot flashing lock" ?
Click to expand...
Click to collapse
OEM unlocking allows the bootloader to be unlocked. You must use fastboot to unlock the bootloader.
Fastboot flashing unlock.
Sent from my PH-1 using XDA Labs
DAE1964 said:
OEM unlocking allows the bootloader to be unlocked. You must use fastboot to unlock the bootloader.
Fastboot flashing unlock.
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
I was referring to the brick-like situation, if it happens do you or do you not get the chance to execute "fastboot flashing unlock" and "fastboot flashing unlock_critical"?
Hi,
I am incredibly new to this and I think I might have managed to destroy this google pixel I just bought. I had attempted to root the phone using magisk after unlocking the bootloader and installing TWRP though I had a little bit of trouble, I was following instructions here https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/. I managed to unlock the bootloader but after signing in to the phone again and attempting to install TWRP to get magisk It wouldn't let me access most of my downloads on the phone because TWRP was asking for a password for my user. I tried the passcode I had set but I didn't work I tried rebooting the phone and removing the lock but many apps on the phone once I booted it back no longer worked, specifically settings which is how I was planning on removing the password. I also tried using adb commands to wipe the lock but nothing really seemed to be working so I found a factory reset setting on TWRP and now I have been stuck at the google reset screen for about 5 hours now. Any help is appreciated.
Thanks
ajg32 said:
Hi,
I am incredibly new to this and I think I might have managed to destroy this google pixel I just bought. I had attempted to root the phone using magisk after unlocking the bootloader and installing TWRP though I had a little bit of trouble, I was following instructions here https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/. I managed to unlock the bootloader but after signing in to the phone again and attempting to install TWRP to get magisk It wouldn't let me access most of my downloads on the phone because TWRP was asking for a password for my user. I tried the passcode I had set but I didn't work I tried rebooting the phone and removing the lock but many apps on the phone once I booted it back no longer worked, specifically settings which is how I was planning on removing the password. I also tried using adb commands to wipe the lock but nothing really seemed to be working so I found a factory reset setting on TWRP and now I have been stuck at the google reset screen for about 5 hours now. Any help is appreciated.
Thanks
Click to expand...
Click to collapse
What do you mean by "remove the lock" and "wipe the lock"? If you relocked the bootloader, your recovery options are limited. Can you access the phone with adb and/or fastboot? If the bootloader is still unlocked, flash a stock factory image available at https://developers.google.com/android/images. Instructions for flashing are at that URL.
If your bootloader is now locked, can you get to fastboot? If not, I don't know of anything you can do. If you can get to fastboot, you can try to sideload a full OTA image from https://developers.google.com/android/ota. Instructions are at that URL.
If you can recover, forget rooting with TWRP - those instructions are outdated. Just install the Magisk app, and use it to patch boot.img, then flash the patched boot.img. If you need TWRP for other purposes, do not install it, just boot it with "fastboot boot twrp.img".
Never lock the bootloader unless you have a completely stock device. Even then, you risk bricking the phone.
dcarvil said:
What do you mean by "remove the lock" and "wipe the lock"? If you relocked the bootloader, your recovery options are limited. Can you access the phone with adb and/or fastboot? If the bootloader is still unlocked, flash a stock factory image available at https://developers.google.com/android/images. Instructions for flashing are at that URL.
If your bootloader is now locked, can you get to fastboot? If not, I don't know of anything you can do. If you can get to fastboot, you can try to sideload a full OTA image from https://developers.google.com/android/ota. Instructions are at that URL.
If you can recover, forget rooting with TWRP - those instructions are outdated. Just install the Magisk app, and use it to patch boot.img, then flash the patched boot.img. If you need TWRP for other purposes, do not install it, just boot it with "fastboot boot twrp.img".
Never lock the bootloader unless you have a completely stock device. Even then, you risk bricking the phone.
Click to expand...
Click to collapse
Sorry for the lack of clarity. The bootloader was still unlocked I was simply trying to access files in the TWRP menu but I had to enter the pin I put on the phone. When I mentioned that I was trying to remove the lock it was so that I could use the file manager to install through the TWRP menu. I believe the bootloader is still unlocked but I simply cannot really communicate with the phone. It is on, but its suck on a google logo with a loading bar. Aside from adb commands which don't seem to be working as the phone is not being detected Is there any sort of combination of clicking the power button or something similar that may shake the phone out of the resetting loop?
ajg32 said:
Sorry for the lack of clarity. The bootloader was still unlocked I was simply trying to access files in the TWRP menu but I had to enter the pin I put on the phone. When I mentioned that I was trying to remove the lock it was so that I could use the file manager to install through the TWRP menu. I believe the bootloader is still unlocked but I simply cannot really communicate with the phone. It is on, but its suck on a google logo with a loading bar. Aside from adb commands which don't seem to be working as the phone is not being detected Is there any sort of combination of clicking the power button or something similar that may shake the phone out of the resetting loop?
Click to expand...
Click to collapse
Try these instructions - https://www.hardreset.info/devices/google/google-pixel-3/fastboot-mode/
If you can get to fastboot mode, flash a stock image from the URL in my previous post.
If that does not work, google "plxel 3 recovery mode" or "pixel 3 fastboot mode" to try to find something that works. If you can get to fastboot mode, you have a good chance of recovering the phone. Don't try to do anything with TWRP.
dcarvil said:
Try these instructions - https://www.hardreset.info/devices/google/google-pixel-3/fastboot-mode/
If you can get to fastboot mode, flash a stock image from the URL in my previous post.
If that does not work, google "plxel 3 recovery mode" or "pixel 3 fastboot mode" to try to find something that works. If you can get to fastboot mode, you have a good chance of recovering the phone. Don't try to do anything with TWRP.
Click to expand...
Click to collapse
Thank you very much for all the help, I managed to restore the phone pre-TWRP mess. You mentioned rooting by only installing magisk. Would that method be similar to the one described here https://www.rootdroids.com/guides/how-to-root-google-pixel-3-with-magisk-without-twrp/?
ajg32 said:
Thank you very much for all the help, I managed to restore the phone pre-TWRP mess. You mentioned rooting by only installing magisk. Would that method be similar to the one described here https://www.rootdroids.com/guides/how-to-root-google-pixel-3-with-magisk-without-twrp/?
Click to expand...
Click to collapse
Yes, that is the method. Those instructions don't really tell you how to get boot.img though. Unzip the factory image you downloaded. Inside that zip is another zip. Unzip that second zip and boot.img will be extracted.
dcarvil said:
Yes, that is the method. Those instructions don't really tell you how to get boot.img though. Unzip the factory image you downloaded. Inside that zip is another zip. Unzip that second zip and boot.img will be extracted.
Click to expand...
Click to collapse
I believe I got the correct boot.img although now when I try to flash boot the patched img file I get an error. Specifically,
Warning: skip copying boot_a image avb footer (boot_a partition size: 67108864, boot_a image size: 100663296).
Sending 'boot_a' (98304 KB) OKAY [ 2.286s]
Writing 'boot_a' (bootloader) Image missing cmdline or OS version
FAILED (remote: 'Failed to write to partition Bad Buffer Size')
fastboot: error: Command failed
Looking it up it seems like the most common fix is to boot from TWRP
ajg32 said:
I believe I got the correct boot.img although now when I try to flash boot the patched img file I get an error. Specifically,
Warning: skip copying boot_a image avb footer (boot_a partition size: 67108864, boot_a image size: 100663296).
Sending 'boot_a' (98304 KB) OKAY [ 2.286s]
Writing 'boot_a' (bootloader) Image missing cmdline or OS version
FAILED (remote: 'Failed to write to partition Bad Buffer Size')
fastboot: error: Command failed
Looking it up it seems like the most common fix is to boot from TWRP
Click to expand...
Click to collapse
"boot_a image size: 100663296" is the wrong size. How are you transferring boot.img and the patched image between your phone and PC? You should be using adb push/pull. If you did use adb push/pull, I'd need to see all the commands you used, and a directory listing of all the files to see if I can spot something wrong. Also, what version of Magisk?
You could try renaming magisk.apk to magisk.zip and installing the zip with TWRP, but I don't know if that method still works on the Pixel 3. I've never tried that method. Make sure you just boot TWRP (fastboot boot twrp.img), and do not install TWRP. If that breaks things, at least you know how to recover now.