Related
Hey guys, so heres my history
Stock HTC One M8 on Verizon, rooted with weaksauce, then s-off with firewater (took one chug), then installed cwm unnofficial until twrp came out. when the 2.7.0.2 came out, I flashed it via terminal emulator. Suddenly, I could not boot past the recovery. it just would boot into recovery every time I rebooted. So I used the TWRP terminal emulator to flash it once more, thinking that would help. Now the phone wont boot at all, just rumbles and vibrates like its turning on and crashing off. Holding vol up+power and vol down+power does not seem to work, and im going to be so upset if I just bricked my phone. Does anyone have some tips?
wonkizzle said:
Hey guys, so heres my history
Stock HTC One M8 on Verizon, rooted with weaksauce, then s-off with firewater (took one chug), then installed cwm unnofficial until twrp came out. when the 2.7.0.2 came out, I flashed it via terminal emulator. Suddenly, I could not boot past the recovery. it just would boot into recovery every time I rebooted. So I used the TWRP terminal emulator to flash it once more, thinking that would help. Now the phone wont boot at all, just rumbles and vibrates like its turning on and crashing off. Holding vol up+power and vol down+power does not seem to work, and im going to be so upset if I just bricked my phone. Does anyone have some tips?
Click to expand...
Click to collapse
You are not bricked. Try flashing the stock recovery which can be found in this thread.
http://forum.xda-developers.com/showthread.php?t=2708291
droidkevlar said:
You are not bricked. Try flashing the stock recovery which can be found in this thread.
http://forum.xda-developers.com/showthread.php?t=2708291
Click to expand...
Click to collapse
How can I flash it if it wont even boot? The screen wont come on and it just rumbles.
wonkizzle said:
How can I flash it if it wont even boot? The screen wont come on and it just rumbles.
Click to expand...
Click to collapse
You cant get into fastboot?
Mode: press and hold Volume Down and Power simultaneously. You will soon see the LOCKED text and then you can release the keys.
droidkevlar said:
You cant get into fastboot?
Mode: press and hold Volume Down and Power simultaneously. You will soon see the LOCKED text and then you can release the keys.
Click to expand...
Click to collapse
No, the screen (barely) lights up for a split second, then shuts off, and vibrates. This repeats over and over. Ive tried holding all the buttons for 90 seconds, still just vibrates. Ive tried all button combinations for as long as I thought it was needed, and nothing is bringing any picture back to the screen. Just vibrations.
wonkizzle said:
No, the screen (barely) lights up for a split second, then shuts off, and vibrates. This repeats over and over. Ive tried holding all the buttons for 90 seconds, still just vibrates. Ive tried all button combinations for as long as I thought it was needed, and nothing is bringing any picture back to the screen. Just vibrations.
Click to expand...
Click to collapse
Not sure what else to try, but I know you're not hard bricked. You are just softbricked. I would go into the M8 channel on irc. andirc.net and channel is #m8
jcase and others hang out there and can be able to help you.
wonkizzle said:
Hey guys, so heres my history
Stock HTC One M8 on Verizon, rooted with weaksauce, then s-off with firewater (took one chug), then installed cwm unnofficial until twrp came out. when the 2.7.0.2 came out, I flashed it via terminal emulator. Suddenly, I could not boot past the recovery. it just would boot into recovery every time I rebooted. So I used the TWRP terminal emulator to flash it once more, thinking that would help. Now the phone wont boot at all, just rumbles and vibrates like its turning on and crashing off. Holding vol up+power and vol down+power does not seem to work, and im going to be so upset if I just bricked my phone. Does anyone have some tips?
Click to expand...
Click to collapse
What did you type into terminal emulator?
This thread might be of help to you: http://forum.xda-developers.com/showthread.php?t=2718562
sparky_005 said:
What did you type into terminal emulator?
This thread might be of help to you: http://forum.xda-developers.com/showthread.php?t=2718562
Click to expand...
Click to collapse
In my haste, before anyone figured out that the TWRP team listed the wrong partition to flash to, I decided to try and flash it again once more, using the same command I did before:
"su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p43"
Only this time I did it within the terminal emulator in TWRP, thinking maybe I hit a typo the first time or something, and also since adb didnt list my device on my computer. And THATS when it all went to ****.
Firstly, it only vibrates every 10-15 seconds, stuck in a bootloop and crashing. Only when I hold Volume Down in between vibrates does the phone go into the bootloader. But theres the next problem.
Screen does not illuminate anymore, and I can only see whats going on when I shine a flashlight onto the screen. It will only go to the bootloader, will not load recovery, will not factory reset, fastboot getvar all returns a garbled mess of text that does not resemble the S/N or IMEI, and it seems anything I try to load through fastboot is fruitless. I need some real pros to see this thread, or im ****ed. And I didn't get insurance on the phone when I ordered it, so a replacement is out of the question. Im real upset that I ****ed myself here. I dont hold anyone responsible but myself, but I really wish the proper command would have been included in the instructions instead of flashing it to the wrong partition, twice.
wonkizzle said:
In my haste, before anyone figured out that the TWRP team listed the wrong partition to flash to, I decided to try and flash it again once more, using the same command I did before:
"su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p43"
Only this time I did it within the terminal emulator in TWRP, thinking maybe I hit a typo the first time or something, and also since adb didnt list my device on my computer. And THATS when it all went to ****.
Firstly, it only vibrates every 10-15 seconds, stuck in a bootloop and crashing. Only when I hold Volume Down in between vibrates does the phone go into the bootloader. But theres the next problem.
Screen does not illuminate anymore, and I can only see whats going on when I shine a flashlight onto the screen. It will only go to the bootloader, will not load recovery, will not factory reset, fastboot getvar all returns a garbled mess of text that does not resemble the S/N or IMEI, and it seems anything I try to load through fastboot is fruitless. I need some real pros to see this thread, or im ****ed. And I didn't get insurance on the phone when I ordered it, so a replacement is out of the question. Im real upset that I ****ed myself here. I dont hold anyone responsible but myself, but I really wish the proper command would have been included in the instructions instead of flashing it to the wrong partition, twice.
Click to expand...
Click to collapse
As a side note, when you use fastboot getvar all or fastboot getvar serialno this is what happens "F:\Android-adb>fastboot getvar serialno
serialno: ≤º┴╛ ╤■ù╩■ù╚■u♀ "
Another side note, any type of attempt to flash with fastboot ends up with this: "target reported max download size of 1830711296 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.500s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 1.508s "
atirx7man said:
As a side note, when you use fastboot getvar all or fastboot getvar serialno this is what happens "F:\Android-adb>fastboot getvar serialno
serialno: ≤º┴╛ ╤■ù╩■ù╚■u♀ "
Another side note, any type of attempt to flash with fastboot ends up with this: "target reported max download size of 1830711296 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.500s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 1.508s "
Click to expand...
Click to collapse
This. He's been helping me figure this out. Anyone help?
wonkizzle said:
This. He's been helping me figure this out. Anyone help?
Click to expand...
Click to collapse
check your PM.
By the way, in the PM I said to boot to bootloader with power + vol up but meant power + vol down
dsEVOlve said:
check your PM.
By the way, in the PM I said to boot to bootloader with power + vol up but meant power + vol down
Click to expand...
Click to collapse
I will report back with results as soon as I can.
dsEVOlve said:
check your PM.
By the way, in the PM I said to boot to bootloader with power + vol up but meant power + vol down
Click to expand...
Click to collapse
Followed your directions exactly dsEVOlve. While the flash does complete successfully, it still did not fix the problem. Now, does flashing this way only flash recovery? I had another member who wrote some zip files trying to fix the serial number issue by replacing the mfg and misc folders. Both failed flashing through fastboot so I'm wondering if this method might have some way of working.
As I said, everything that we attempt to flash through fastboot returns the error FAILED (remote: not allowed)
Your help is greatly appreciated.
If you're a Verizon customer, take the phone back and tell them it won't turn on at all. They'll get you a new one.
Sent from my #6F6E71 M8
atirx7man said:
Followed your directions exactly dsEVOlve. While the flash does complete successfully, it still did not fix the problem. Now, does flashing this way only flash recovery? I had another member who wrote some zip files trying to fix the serial number issue by replacing the mfg and misc folders. Both failed flashing through fastboot so I'm wondering if this method might have some way of working.
As I said, everything that we attempt to flash through fastboot returns the error FAILED (remote: not allowed)
Your help is greatly appreciated.
Click to expand...
Click to collapse
Yes, it only had a recovery image in the ZIP. The ZIP you got from someone else wasn't bootloader flashable and now we've established that nothing can be flashed at this point except through the bootloader.
So you weren't able to boot to recovery through the bootloader after it updated?
I suppose the next thing I would try is reflashing the hboot through bootloader. You would follow the same process but with one of the bootloader flashable ZIPS from here: http://forum.xda-developers.com/showthread.php?t=2709976
dsEVOlve said:
Yes, it only had a recovery image in the ZIP. The ZIP you got from someone else wasn't bootloader flashable and now we've established that nothing can be flashed at this point except through the bootloader.
So you weren't able to boot to recovery through the bootloader after it updated?
I suppose the next thing I would try is reflashing the hboot through bootloader. You would follow the same process but with one of the bootloader flashable ZIPS from here: http://forum.xda-developers.com/showthread.php?t=2709976
Click to expand...
Click to collapse
Alright, just finished trying the hboot flash through bootloader. Same results. Flashes, says to press power to reboot, remove the sdcard and take file off, reboot into a bootloop with no screen illumination.
The only other change I notice is that the flag at the top that used to say "Unlocked" now says "Relocked"
atirx7man said:
Alright, just finished trying the hboot flash through bootloader. Same results. Flashes, says to press power to reboot, remove the sdcard and take file off, reboot into a bootloop with no screen illumination.
The only other change I notice is that the flag at the top that used to say "Unlocked" now says "Relocked"
Click to expand...
Click to collapse
I'll think on it some more but I'm out of ideas. The fact that it is relocked means you probably flashed the stock hboot which might hamper any future efforts. Might want to flash the no red text version to see if it unlocks but it won't fix any of the bigger problems.
dsEVOlve said:
I'll think on it some more but I'm out of ideas. The fact that it is relocked means you probably flashed the stock hboot which might hamper any future efforts. Might want to flash the no red text version to see if it unlocks but it won't fix any of the bigger problems.
Click to expand...
Click to collapse
I know this is for S3; but would some variant of this work? http://forum.xda-developers.com/showpost.php?p=47911843&postcount=165
OP, PM me, I've worked with a few devices like this already.
Hey drache, you already dealt with this phone you tried to help me with it on irc. We had no luck.
Sent from my HTC6435LVW using xda app-developers app
Good day, its my first thread here, so I'm sorry for my english and terminology.
My Photon Q had CM-13-Nightly installed, bootloader unlocked and Clockwork recovery installed. Everything was working fine, till few days ago. Phone was left unused with drained battery, so I charged it and powerd on. After that, all app started to crash one after another. I was trying to do factory reset from recovery, erase everything from bootloader menu or using bootloader commands (bootloader erase data, bootloader -w) but nothing worked. I still have my system, with same apps, wallpaper etc and apps still crash. Are these all symptoms of damaged partition or internal storage? Will be thankful for any help
Erasing in bootloader/fastboot mode can be dangerous... be careful.
I would just factory reset and reinstall the ROM. Don't use ClockworkMod for recovery tho, use TWRP. CWM hasn't had updates in a long time (and frankly I'm surprised it was able to flash the latest CM).
I have tried to change recovery, but it was also impossible. I also tried to wipe data / factory reset, after that flashed new Rom but nothing changed. Still all my apps and settings remains. There is one more thing to add, that I can copy file from device when connected to my laptop, but cannot delete anything. Anyway, how to change recovery? Phone doesn't keep any changes for example adb debugging in developer options. CWM update is turned off, but cannot change recovery
greedo85 said:
I have tried to change recovery, but it was also impossible. I also tried to wipe data / factory reset, after that flashed new Rom but nothing changed. Still all my apps and settings remains. There is one more thing to add, that I can copy file from device when connected to my laptop, but cannot delete anything. Anyway, how to change recovery? Phone doesn't keep any changes for example adb debugging in developer options. CWM update is turned off, but cannot change recovery
Click to expand...
Click to collapse
Boot to fastboot/bootloader mode, 'fastboot flash recovery twrp.img' assuming twrp.img is in the location you are running fastboot flash from...
How did you flash CWM recovery in the first place?
I have bought this phone with Cyanogen Recovery and Custom ROM flashed already. I tried what You posted, it shows that TWRP is flashed, but when I enter recovery again, I still have Cyanogen. I tried with 3 different versions of TWRP downloaded for Photon Q... I also don't know what does it mean "(bootloader) Variable not supported!"
HTML:
C:\fastboot>fastboot flash recovery twrp-2.3.0.0-asanti_c.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (6702 KB)...
OKAY [ 0.512s]
writing 'recovery'...
OKAY [ 1.786s]
finished. total time: 2.298s
arrrghhh said:
Boot to fastboot/bootloader mode, 'fastboot flash recovery twrp.img' assuming twrp.img is in the location you are running fastboot flash from...
How did you flash CWM recovery in the first place?
Click to expand...
Click to collapse
greedo85 said:
I have bought this phone with Cyanogen Recovery and Custom ROM flashed already. I tried what You posted, it shows that TWRP is flashed, but when I enter recovery again, I still have Cyanogen. I tried with 3 different versions of TWRP downloaded for Photon Q... I also don't know what does it mean "(bootloader) Variable not supported!"
Click to expand...
Click to collapse
I think you can safely ignore the bootloader message.
As for flashing TWRP, did you boot TWRP immediately after flashing, or did you boot Android?
I believe you need to make sure you boot TWRP immediately after flashing, otherwise CM Recovery will blow it out.
After flashing TWRP hold power until the device shuts off, release, and now hold power + vol down to enter recovery. Please use the latest version of TWRP from kabaldan, or the latest official TWRP.
I did exactly as You have posted. Still Cyanogen :/ I got recovery from here: https://dl.twrp.me/asanti/twrp-3.0.2-0-asanti_c.img.html , its the newest I think
greedo85 said:
I did exactly as You have posted. Still Cyanogen :/ I got recovery from here: https://dl.twrp.me/asanti/twrp-3.0.2-0-asanti_c.img.html , its the newest I think
Click to expand...
Click to collapse
Sorry it's power + vol UP (according to my own guide...)
3. Hit power - device turns off. Hold vol up + power, then release power when the screen comes on - continue holding vol up. When you see the moto logo dim a bit, release vol up. You should now be in TWRP!
Did that - Cyanogen again :/ Have any idea why is that happening? Internal memory broke down?
greedo85 said:
Did that - Cyanogen again :/ Have any idea why is that happening? Internal memory broke down?
Click to expand...
Click to collapse
I'm not sure why people have issues with this... I always thought it was how they 'completed' the flashing process. I don't recall being able to reproduce the condition.
Perhaps boot Android then boot TWRP? Or try to reboot directly to recovery from the fastboot cli? Try something different... or just fastboot boot the TWRP image? There is a problem in the process, I'm just not sure 'where' since I don't have the phone in front of me.
Already done that, before I started this thread... Nothing works. I have tried multiple combination, such as reboot to this (I don't know how to name it, B&W menu with APfastboot, recovery etc), boot system first than recovery, boot directly to recovery after flashing new one etc. Are there any fastboot commands, that I could use to forcefully erase recovery or data? You sure that it's not physical damage of internal memory?
greedo85 said:
Already done that, before I started this thread... Nothing works. I have tried multiple combination, such as reboot to this (I don't know how to name it, B&W menu with APfastboot, recovery etc), boot system first than recovery, boot directly to recovery after flashing new one etc. Are there any fastboot commands, that I could use to forcefully erase recovery or data? You sure that it's not physical damage of internal memory?
Click to expand...
Click to collapse
IIRC this device will let you 'fastboot boot' images directly - I think I suggested this - have you tried it?
I'll dig around and see what else I can find from the TWRP thread. I was pretty sure it had to do with the process, but I could be mistaken.
Edit - I'll flash CM Recovery on my old Q and see if I can recreate this as well. It's always bothered me...
How would I boot images directly? From where?
greedo85 said:
How would I boot images directly? From where?
Click to expand...
Click to collapse
Just like you fastboot flash them, but 'fastboot boot <imagefilename>"...
arrrghhh said:
Just like you fastboot flash them, but 'fastboot boot <imagefilename>"...
Click to expand...
Click to collapse
Did You mean this? Why is Command restricted?
Code:
C:\fastboot>fastboot boot twrp-3.0.2-0-asanti_c.img
downloading 'boot.img'...
OKAY [ 0.674s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.770s
greedo85 said:
Did You mean this? Why is Command restricted?
Code:
C:\fastboot>fastboot boot twrp-3.0.2-0-asanti_c.img
downloading 'boot.img'...
OKAY [ 0.674s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.770s
Click to expand...
Click to collapse
I guess they only allow fastboot booting kernels... at least I used to do that on this device.
So I just flashed CM Recovery no problem. Going to flash back TWRP.
Is there anything I can do now to put this phone back to work?
greedo85 said:
Is there anything I can do now to put this phone back to work?
Click to expand...
Click to collapse
I'm... kind of at a loss. Make sure you have the latest TWRP. I just downloaded the latest CM Recovery, fastboot flash recovery <cmrecimg> and it rebooted to Android on its own. I reboot to recovery, CM Recovery is installed. All good.
I reboot to bootloader mode, grab the latest official TWRP, fastboot flash recovery <twrpimg>, this time when I unplugged it was still in fastboot mode. So I hit the power button, phone turns off. Then I hold power + vol up until I see the screen turn on. Continue to hold vol up, but release power. Then when the screen dims (or when recovery starts if you can't tell) release vol up.
Maybe that'll help you? Good luck.
Did exactly the same procedure as You described. Still Cyanogen. I can even record it and send here...
Could You please send me a link where I can find another TWRP ( You mentioned some developer few posts above, I guess), differend that I have found?
greedo85 said:
Did exactly the same procedure as You described. Still Cyanogen. I can even record it and send here...
Could You please send me a link where I can find another TWRP ( You mentioned some developer few posts above, I guess), differend that I have found?
Click to expand...
Click to collapse
Dunno why it would make any difference at this point, but have at it.
I would REALLY appreciate help if possible. I'm trying to recover my honeymoon pictures from a Pixel that freezes as soon as it boots.
It has the locked, original bootloader, but debugging is enabled. Sailfish Oreo 8.1.0/OPM1.171019.012/4470837 installed.
I thought after enabling debug that I could adb shell or adb pull files in recovery mode, but I can't figure out how (assuming it's possible). I can boot into "no command" recovery, and get into the Android Recovery menu with "Apply update from ADB", "Mount /system", etc. I've even upgraded the OS with adb sideload successfully...
But booting into Android, it freezes almost always on the "G" loading screen...but rarely, it will display the clock and notifications and immediately freeze. Even more rarely (like once in a thousand boots), it will give me maybe 10 seconds before it freezes. The last time it did this, I had just enough time to enable dev options, enable debugging, and "always enable with this computer"...then it froze.
What are my options or the most likely way to recover my files? Is there anything I can do from recovery, or if I get another 10 seconds in Android, is there anything I should try?
Fastboot boot into twrp and then using adb pull grab your entire pictures directory.
Also booting into twrp and doing a factory wipe should fix the bootloop I had this happen this morning
KittyRgnarok said:
Fastboot boot into twrp and then using adb pull grab your entire pictures directory.
Also booting into twrp and doing a factory wipe should fix the bootloop I had this happen this morning
Click to expand...
Click to collapse
Thanks for the suggestion! I'll try this tonight, but I worry it won't work since my bootloader is the original and locked. If I understand correctly:
- you need an unlocked bootloader to do "fastboot boot"
- you have to factory reset and wipe all your files to unlock the bootloader
Is that not true?
Yes, it looks like I can't "fastboot boot" because it's not unlocked. Everything I've found says unlocking should wipe my device.
Is there any way to boot an img or get to adb shell/pull without wiping it?
Code:
>>> fastboot boot twrp-3.2.1-0-sailfish.img
downloading 'boot.img'...
OKAY [ 0.868s]
booting...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.967s
Oh yeah I forgot about that. Uhhhhh no I think ur boned sorry
are you sure you did not have google photos automatically backing up your photos?
mruno said:
are you sure you did not have google photos automatically backing up your photos?
Click to expand...
Click to collapse
Yes, I'm sure. I was away from any connection on my honeymoon and it crashed right before coming home.
If your phone is under warranty still you can likely RMA it to get a phone that isn't bootstuck but as far as the data I think it's pretty safe to say you can't access it unless you have already disabled forced full disk encryption prior(which I'm not even sure is safe to do on these devices).
Hi everyone,
I have bought a Nexus 5 for like 3 months, then one day suddenly, it started rebooting infinitely, I did a factory reset but it didn't solve the problem, so I tried as suggested to hit the power button against a corner, but unfortunately that made the button unresponsive, so I took it to a shop repair and they changed the button, and now I'm back to the bootloop problem, but the weird part is, when i enter the recovery mode what ever button combination i try (hold power button + press volume up etc ..), it will simply reboot the system, even if I don't press any command it will reboot after around 5 seconds of showing "no command" with the dead android guy.
I downloaded Nexus Root Toolkit to perform a Bootloader unlock, it displays the unlock screen on my phone, but after i select Yes, I have to enable USB debugging, which i can't do because the system simply starts to bootlooping.
PS : My bootlooping doesn't get stuck on the Google logo or the colored dots, it will freeze just before showing the colored dots (or after showing 2 of them) then it will restart.
Any idea ? Thanks in advance
If I recall correctly, USB debugging should not be required to unlock the bootloader as you are using fastboot commands to unlock the bootloader rather than ADB commands.
audit13 said:
If I recall correctly, USB debugging should not be required to unlock the bootloader as you are using fastboot commands to unlock the bootloader rather than ADB commands.
Click to expand...
Click to collapse
Awesome, that was fast lol, thank you so much, I'm able now to flash it, I'll let you know how it goes
audit13 said:
If I recall correctly, USB debugging should not be required to unlock the bootloader as you are using fastboot commands to unlock the bootloader rather than ADB commands.
Click to expand...
Click to collapse
It's still restarting after the flash, any idea ?
If it is restarting on its own in recovery or fastboot mode, there could still be an issue with the power button or the contacts on the power button.
audit13 said:
If it is restarting on its own in recovery or fastboot mode, there could still be an issue with the power button or the contacts on the power button.
Click to expand...
Click to collapse
Thank you, I will take it back to the repair shop.
Edit: I just found out actually that the previous flash was not a failure, here is the logs :
C:\Users\hp\Desktop\tools\platform-tools>fastboot flash recovery
target reported max download size of 1073741824 bytes
sending 'recovery' (12521 KB)...
OKAY [ 0.616s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.798s
Click to expand...
Click to collapse
I ran the command as an administrator
audit13 said:
If I recall correctly, USB debugging should not be required to unlock the bootloader as you are using fastboot commands to unlock the bootloader rather than ADB commands.
Click to expand...
Click to collapse
Do fastboot commands work when USB debugging is disabled?
anuragm13 said:
Do fastboot commands work when USB debugging is disabled?
Click to expand...
Click to collapse
They should. By enabling debugging in the os, it allows you to run ADB commands.
audit13 said:
They should. By enabling debugging in the os, it allows you to run ADB commands.
Click to expand...
Click to collapse
If i encrypt my device (secure startup), i.e. , it asks for password or pin to start android in the middle of the boot animation..
So will accessing the recovery mode and fastboot mode would also require the password?
i.e. will my fastboot and recovery partitions would be encrypted/protected with the password?
Btw, does xda require captcha verification everytime i reply?
anuragm13 said:
If i encrypt my device (secure startup), i.e. , it asks for password or pin to start android in the middle of the boot animation..
So will accessing the recovery mode and fastboot mode would also require the password?
i.e. will my fastboot and recovery partitions would be encrypted/protected with the password?
Click to expand...
Click to collapse
Accessing your /data partition from recovery will require your encryption password.
But you'll be able to run the recovery without providing a password and decrypting /data, your data will be inaccessible.
Fastboot mode won't be password-protected.
The bootloader, recovery, system and all other partitions but /data will be unencrypted.
No XDA, does not require captcha when I log in.
Are you using an VPN or smart DNS?
audit13 said:
No XDA, does not require captcha when I log in.
Are you using an VPN or smart DNS?
Click to expand...
Click to collapse
Its fixed.
I wasn't using any vpn.
After posting 4-5 times now it doesn't require captcha verification.
How do you all get notified if someone quoted you? Do you keep checking the threads or what?
I signed up for email notifications.
audit13 said:
I signed up for email notifications.
Click to expand...
Click to collapse
Ok
Bro, its the power button! Its a common problem for our lovely nexus5. Its like stucked, so after 5-12sec it turns off, and because it is still pressing, it turns on again.
again and again...
do u thinkn i can escape frm recovery loop if I power of my device (by making it 0% )
do u thinkn i can escape frm recovery loop if I power of my device (by making it 0% battrey)
i stuck in it very badly !!
havennt even unlocked the bootloader to flash other ! n I'm not getting whats ur solution is so tell me
pls help..i cant unlocl my bootloader..
when i flash error says"flash is not allowed in lock state"
I think you must try -wipe all data -factory reset.
I have a Pixel 2 which overnight stopped working - my guess is that it rebooted due to an automated software update.
I now only get the page with the robot on it's back.
Options in green on this page are Barcodes, Power Off, and Start.
After reading a lot online I've tried all the usual key press combinations to no avail.
I've also downloaded ADB and FASTBOOT to my Mac.
ADB doesn't see the phone when plugged in via USB (ie. ADB DEVICES doesn't return anything)
FASTBOOT DEVICES does, however, show the serial number as listed on the page with the robot on it's back (and the -l option adds "usb:" plus an 8 digit number and the letter "X"
FASTBOOT REBOOT restarts the phone and brings me back to the robot on it's back page.
Other information on the Robot on it's back page include -
Product Revision: walleye MP1
Boot-slot: b
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: locked
Advice online suggests I need to unlock the phone, so I've tried FASTBOOT FLASHING UNLOCK, and FASTBOOT OEM UNLOCK but neither work.
When I try these I get "FAILED (remote: Flashing Unlock is not allowed)"
An article on Android Police suggests this may have been a bug on the Pixel 2 originally and that it's now resolved?
Unfortunately, my cat 22 situation seems to be that I need to do a factory reset, but the steps I've found as to how to do a factory reset all lead back to the Robot on it's back page, so I can't see how to move forward to with recovering my phone?
Can anyone help please?
Really frustrated that my new phone can put itself into this state without me having done anything and that it's seemingly impossible to recover from this state now that it's in it.
At very least I'd like to wipe all data from the phone so I can send it off for repair.
Thanks in advance.
Unfortunately, I can't describe a situation to get around this because the bootloader is still locked -- you'll probably want to unlock the bootloader and then leave it unlocked permanently if flashing the images using this method on a regular basis... I have personal notes that I've written for two scenarios. (1) is to gain root from stock and directions (2) is to flash the latest Android image and retain the data... Perhaps try the bottom block of steps (re-installing the factory image) --- but also unlock the bootloader from the top block of steps:
=======================
Code:
ROOT FROM STOCK
0.5 - Download the following
Magisk-v16.7-1674.zip -- https://transfer.sh/YVFdi/Magisk-v16.7-1674-.zip
twrp-pixel2-installer-walleye-3.2.3-0.zip -- https://dl.twrp.me/walleye/
twrp-3.2.3-0-walleye.img -- https://dl.twrp.me/walleye/
1.0 - On phone: Settings > System > About Phone > tap on the 'build number' seven times.
2.0 - The Developer Options will now be visible in the main settings page. Enter it and turn on USB debugging and OEM unlocking
3.0 - Reboot into 'bootloader' and unlock bootloader (this will factory reset phone)
# adb reboot bootloader
# fastboot oem unlock
4.0 - Download 'twrp-3.2.3-0-walleye.img' to Desktop. Rename the File to 'pixeltwrp.img' (Not necessary to rename -- just did; https://dl.twrp.me/walleye/)
5.0 - Now boot your phone in bootloader mode. Turn off phone and Hold the Volume Down + Power, then release Power button or...
# adb reboot bootloader
6.0 - Run the following command
# fastboot boot ~/Desktop/pixeltwrp.img
7.0 - Phone will boot in the TWRP mode. Push 'twrp-pixel2-installer-walleye-3.2.3-0.zip' and 'Magisk-v16.7-1674.zip' to the phone's /data/ directory
# adb push ~/Downloads/twrp-pixel2-installer-walleye-3.2.3-0.zip /data/
# adb push ~/Downloads/Magisk-v16.7-1674.zip /data/
8.0 - Tap on 'Install' and flash 'twrp-pixel2-installer-walleye-3.2.3-0.zip' and 'Magisk-v16.7-1674.zip' files
9.0 - Reboot Phone
10.0 - Install busybox on /system/bin
UPDATE IMAGE TO LATEST WITHOUT WIPING PHONE
0.5 - Download the following
Magisk-v16.7-1674.zip -- https://transfer.sh/YVFdi/Magisk-v16.7-1674-.zip
twrp-pixel2-installer-walleye-3.2.3-0.zip -- https://dl.twrp.me/walleye/
twrp-3.2.3-0-walleye.img -- https://dl.twrp.me/walleye/
1.0 - Remove "PIN UNLOCK" for security reasons
2.0 - Download the latest factory image from https://developers.google.com/android/images#walleye
3.0 - Unzip the factory image's ZIP and remove '-w' from "flash-all.sh"
4.0 - Reboot to bootloader
# adb reboot bootloader
5.0 - Flash image
# ./flash-all.sh
6.0 - Re-install magisk (https://dl.twrp.me/walleye/)
# adb reboot bootloader
# fastboot boot ~/Desktop/pixeltwrp.img
7.0 - Tap on 'Install' and flash 'twrp-pixel2-installer-walleye-3.2.3-0.zip' and 'Magisk-v16.7-1674.zip' files (located on /data/) - If installing a new magisk version, run the magisk uninstaller first '/data/Magisk-uninstaller-20180719.zip'
7.1 - Wipe Dalvik/Cache and reboot
7.2 - Install MagiskManager and TWRP Manager if not installed
7.3 - Go to bootloader and flash kernel 'flashkernel-wahoo-v3.01.zip'
8.0 - Reboot phone
9.0 - Install busybox on /system/bin
10.0 - Re-add security unlock
=======================
...If these options don't work then the last thing I can think is to attempt to boot into the 'pixeltwrp.img' and switch the the primary slot (from Slot B to Slot A) and try to reboot.
Thanks @armordillo for your reply. I'm not planning on doing anything like this regularly - just trying to get my phone to boot or get the files off it so I can send it for repair.
Sadly I can't execute step 1 in either of your proposed processes - I literally can't get past the screen with the upturned robot
I can't turn on USB debugging, and I can't run OEM UNLOCK.
I'm completely stuck.
Can you get into the stock recovery?
On the screen with Andy in his back use the volume keys to scroll till you see Recovery Mode (or something similar) then hit the power button. At this point you should get another dead Andy. Press and hold Power button and then press the Volume UP button once. That should take you to the stock recovery. There will be a bunch of text with options for clearing cache adb sideload and other things.
Sent from my Pixel 2 using Tapatalk
Sadly not.
That option (Recovery mode) is in red and so are 'restart bootloader' and 'download mode' - when I choose any of these by pressing the power button to select, the phone screen goes black for 2 seconds and then the robot on his back image comes back on.
The power button and up volume combination takes me back to the same screen also.
I'm not sure it works on the pixel 2 but you can try changing to boot with slot a using the command:
fastboot --set-active=a
domonicwhite said:
Sadly not.
That option (Recovery mode) is in red and so are 'restart bootloader' and 'download mode' - when I choose any of these by pressing the power button to select, the phone screen goes black for 2 seconds and then the robot on his back image comes back on.
The power button and up volume combination takes me back to the same screen also.
Click to expand...
Click to collapse
Sent from my Pixel 2 using Tapatalk
It says I can't do that because it's locked.
PiousInquisitor said:
I'm not sure it works on the pixel 2 but you can try changing to boot with slot a using the command:
fastboot --set-active=a
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
You can try booting twrp. But if you had some form of security (pin/password) you probably won't be able to decrypt and access your files.
You probably won't even be able to boot twrp. It's worth a shot though.
fastboot boot twrp<version>.img
Sent from my Pixel 2 using Tapatalk
Thanks!
I don't mind not accessing my files - I'd be happy if I could just delete them.
I'm non technical and not familiar with TWRP but I'll do some searching and see what I can learn.
Based on an earlier post I'm guessing I need to download TWRP first? Or is that a part of FASTBOOT?
When you say version.img - I'm assuming that's also something I need to download?
Sorry for the newb questions (I literally just want my phone back)
Thanks again.
PiousInquisitor said:
You can try booting twrp. But if you had some form of security (pin/password) you probably won't be able to decrypt and access your files.
You probably won't even be able to boot twrp. It's worth a shot though.
fastboot boot twrp<version>.img
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
domonicwhite said:
Thanks!
Based on an earlier post I'm guessing I need to download TWRP first? Or is that a part of FASTBOOT?
When you say version.img - I'm assuming that's also something I need to download?
Click to expand...
Click to collapse
Yes, you'll need to download TWRP from https://dl.twrp.me/walleye/twrp-pixel2-installer-walleye-3.2.3-0.zip.html
To help clarify what PiousInquisitor was saying about the version.img is that you'd have to type in the version of TWRP, that I've linked to, in that particular command.
Thank you! Does it matter that I'm using a Mac / OSX?
SargeStryker said:
Yes, you'll need to download TWRP from https://dl.twrp.me/walleye/twrp-pixel2-installer-walleye-3.2.3-0.zip.html
To help clarify what PiousInquisitor was saying about the version.img is that you'd have to type in the version of TWRP, that I've linked to, in that particular command.
Click to expand...
Click to collapse
domonicwhite said:
Thank you! Does it matter that I'm using a Mac / OSX?
Click to expand...
Click to collapse
I'm pretty sure that it doesn't matter.
What they're describing, @domonicwhite , is my steps 4-6 in the first block. Skip to that and see if you can perform it. You will need to have adb/fastboot installed on your MacBook.
Sadly it won't let me do this in the locked state (assuming I did everything correctly).
Any further suggestions?
--
Last login: Tue Aug 21 09:45:09 on ttys001
Domonics-MacBook-Pro:~ domonicwhite$ adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
Domonics-MacBook-Pro:~ domonicwhite$ adb reboot
error: no devices/emulators found
Domonics-MacBook-Pro:~ domonicwhite$ fastboot reboot
Rebooting
Finished. Total time: 0.001s
Domonics-MacBook-Pro:~ domonicwhite$ fastboot reboot bootloader
rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
Domonics-MacBook-Pro:~ domonicwhite$ fastboot boot /Users/domonicwhite/Desktop/pixeltwrp.img.img
Downloading 'boot.img' OKAY [ 0.814s]
booting FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 0.832s
--
PiousInquisitor said:
You can try booting twrp. But if you had some form of security (pin/password) you probably won't be able to decrypt and access your files.
You probably won't even be able to boot twrp. It's worth a shot though.
fastboot boot twrp<version>.img
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Sadly it won't let me do this in the locked state (assuming I did everything correctly).
Any further suggestions?
--
Last login: Tue Aug 21 09:45:09 on ttys001
Domonics-MacBook-Pro:~ domonicwhite$ adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
Domonics-MacBook-Pro:~ domonicwhite$ adb reboot
error: no devices/emulators found
Domonics-MacBook-Pro:~ domonicwhite$ fastboot reboot
Rebooting
Finished. Total time: 0.001s
Domonics-MacBook-Pro:~ domonicwhite$ fastboot reboot bootloader
rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
Domonics-MacBook-Pro:~ domonicwhite$ fastboot boot /Users/domonicwhite/Desktop/pixeltwrp.img.img
Downloading 'boot.img' OKAY [ 0.814s]
booting FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 0.832s
--
PiousInquisitor said:
You can try booting twrp. But if you had some form of security (pin/password) you probably won't be able to decrypt and access your files.
You probably won't even be able to boot twrp. It's worth a shot though.
fastboot boot twrp<version>.img
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
armordillo said:
What they're describing, @domonicwhite , is my steps 4-6 in the first block. Skip to that and see if you can perform it. You will need to have adb/fastboot installed on your MacBook.
Click to expand...
Click to collapse
Computer says no
It won't let me do this in the locked state -
Domonics-MacBook-Pro:~ domonicwhite$ fastboot boot /Users/domonicwhite/Desktop/pixeltwrp.img.img
Downloading 'boot.img' OKAY [ 0.814s]
booting FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 0.832s
armordillo said:
What they're describing, @domonicwhite , is my steps 4-6 in the first block. Skip to that and see if you can perform it. You will need to have adb/fastboot installed on your MacBook.
Click to expand...
Click to collapse
And doing one or both of these don't work from the bootloader either?
# fastboot oem unlock
# fastboot flashing unlock
In red? The color doesn't matter you can still choose recovery. Then hold power for a second and press up. You can the ADB sideload an OTA zip.
I'm pretty sure mine is red too, but it still let's me choose it
Did you accidently reset the bootloader lock after tinkering with your phone? that can cause this, my kid did it to my other phone after i had it messed with. so it was erroring out. nothing you can do but call your company see if you can exchange it for *faulty udate*
since your phone is *locked* just say you tried updating the software, and it reset the phoen to this. phones still locked so you have a shot at exchange..
they exchanged my *faulty update* for a new one. actually recieved it 5 days after making the request. before i had even sent the non working one back.
Sorry I didn't read where you said that it leads back to fastboot. I had to do an RMA due to this because I didn't unlock the bootloader. I then received a phone that cannot be bootloader unlocked (apparently all refurb phones can't). Horrible situation really and probably going to result in me never buying another pixel.