Related
Hi,
my HTC desire S stuck on the htc splash screen
this is what it says on my boot screen when i hold my volume down button and press power button:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.002
RADIO-3305.06.02.03_M
eMMC-boot
Mar 30 2011,17:29,31
i tried to do a factory reset but when i select "FACTORY RESET" it freeze !!
when i get into recovery mode the screen went black and the phone vibrated 7 times and did not start
i installed all needed drivers, so the phone is recognized as "Android ADB interface"
then i tried to use some tools (in fastboot mode) and this is the result :
- adb tools
"adb devices" : List of attached devices is empty => the phone is not recognized by adb
"fastboot devices" : HT13STJ25285 fastboot => the phone is recognized
"fastboot getvar cid" : cid:VODAP120
when i use fastboot command to flash the phone it always says :
< waiting for device >
sending 'radio' (25856 KB)... OKAY
writing 'radio'... INFOsignature checking
FAILED (remote: signature verify fail)
same error message for radio.img and boot.img
- Whenever I try revolutionary, it always gets stuck on waiting for device...
- RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410 (the official ROM)
the RUU detect that the phone has the version 1.47.163.2 and says that it will be upgraded to 1.47.401.4 but it always get stuck on "rebooting to bootloader..."
- i downloaded the file PG88IMG.zip, put it on the sd card and rebooted into bootloader but nothing happened, it show me the bootloader menu and don't detect the file
I also tried to de all steps using HTC drivers witth HTC Sync installed, but always no solution !
Any help is appreciated!
thanks you
Radhouane
According to the internetZ you need a ROM branded by A1 (Vodafone France) (because the red number is the code for it ^^ 1.47.163.2)
Try this one (the blue button)
I recommend you to stay on that ROM afterwards and go S-OFF.
radhouanev12 said:
Hi,
my HTC desire S stuck on the htc splash screen
this is what it says on my boot screen when i hold my volume down button and press power button:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.002
RADIO-3305.06.02.03_M
eMMC-boot
Mar 30 2011,17:29,31
i tried to do a factory reset but when i select "FACTORY RESET" it freeze !!
when i get into recovery mode the screen went black and the phone vibrated 7 times and did not start
i installed all needed drivers, so the phone is recognized as "Android ADB interface"
then i tried to use some tools (in fastboot mode) and this is the result :
- adb tools
"adb devices" : List of attached devices is empty => the phone is not recognized by adb
"fastboot devices" : HT13STJ25285 fastboot => the phone is recognized
"fastboot getvar cid" : cid:VODAP120
when i use fastboot command to flash the phone it always says :
< waiting for device >
sending 'radio' (25856 KB)... OKAY
writing 'radio'... INFOsignature checking
FAILED (remote: signature verify fail)
same error message for radio.img and boot.img
- Whenever I try revolutionary, it always gets stuck on waiting for device...
- RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410 (the official ROM)
the RUU detect that the phone has the version 1.47.163.2 and says that it will be upgraded to 1.47.401.4 but it always get stuck on "rebooting to bootloader..."
- i downloaded the file PG88IMG.zip, put it on the sd card and rebooted into bootloader but nothing happened, it show me the bootloader menu and don't detect the file
I also tried to de all steps using HTC drivers witth HTC Sync installed, but always no solution !
Any help is appreciated!
thanks you
Radhouane
Click to expand...
Click to collapse
You may solve this issue by following the given procedure:
Required
1. one micro sd card (any one, any capacity)
2. battery fully charged or minimum 50 %
Procedure
1. Turn off phone
2. Remove battery for 30 seconds
3. Put back battery.
4. Press Volume down (first) + Power button (last) [boot-loader screen will appear]
5. Go to recovery by using volume down key and press power button.
The recovery logo with red triangle sign will appear on the screen
6. Press Volume Up + Power button several times
You will see the option menu appears with blue color font stating 3 - 4 options
1, Reboot
2. Wipe dalvik cache / format (dont remember exactly what appears)
3. Wipe cache
Select the option 3 first by wiping cache and then select the 2nd option by wiping format (or something written)
and finally select the Reboot option.
Then i hope your phone will start up and run smoothly.
If it works for you Just give me a thanks
arif01 said:
You may solve this issue by following the given procedure:
Required
1. one micro sd card (any one, any capacity)
2. battery fully charged or minimum 50 %
Procedure
1. Turn off phone
2. Remove battery for 30 seconds
3. Put back battery.
4. Press Volume down (first) + Power button (last) [boot-loader screen will appear]
5. Go to recovery by using volume down key and press power button.
The recovery logo with red triangle sign will appear on the screen
6. Press Volume Up + Power button several times
You will see the option menu appears with blue color font stating 3 - 4 options
1, Reboot
2. Wipe dalvik cache / format (dont remember exactly what appears)
3. Wipe cache
Select the option 3 first by wiping cache and then select the 2nd option by wiping format (or something written)
and finally select the Reboot option.
Then i hope your phone will start up and run smoothly.
If it works for you Just give me a thanks
Click to expand...
Click to collapse
Hello Arif, thank you for your reply.
I have already done this manipulation, but when it displays the red triangle, I press the button Vol UP + Power button, then the screen goes black and the phone vibrates 7 times
radhouanev12 said:
Hello Arif, thank you for your reply.
I have already done this manipulation, but when it displays the red triangle, I press the button Vol UP + Power button, then the screen goes black and the phone vibrates 7 times
Click to expand...
Click to collapse
The phone only restarts when you press Vol down at that stage regardless of pressing power button at the same time, please check your volume buttons and ensure that you are pressing Vol up + power button.
arif01 said:
The phone only restarts when you press Vol down at that stage regardless of pressing power button at the same time, please check your volume buttons and ensure that you are pressing Vol up + power button.
Click to expand...
Click to collapse
my volume buttons are working very well and i'am sure that i have pressed volume up and power button, but the phone always vibrate 7 times and the screen goes black
radhouanev12 said:
my volume buttons are working very well and i'am sure that i have pressed volume up and power button, but the phone always vibrate 7 times and the screen goes black
Click to expand...
Click to collapse
Sorry friend than i do not have any other solution
but you can try to S-off and than install recovery from Clockwork
than try to wipe all the caches and make a backup of your current ROM
hope this will help you
Have you tried the RUU from my link?
Jann F said:
Have you tried the RUU from my link?
Click to expand...
Click to collapse
yes jaan F, but it get stuck on "rebooting to bootloader..."
Where are you from, maybe we can S-OFF it via XTC Clip or check the phone with the diag.
So I just got my Shield Tablet today and of course I get notifications of OTA updates. I applied the first two (1.something and 2.1) just fine. Then the 2.2 update downloads and I tell it to install, which it starts to do. Little Android with his chest open shows up and the status bar does it's thing, then it reboots back to the nvidia boot image.... and hangs there. For over an hour I let it stay to see if it was doing some updating in the background, but nothing else happens. So I power it down by holding the power button, then turn it back on. Same deal. Stuck at the boot image.
Of course I'm not unlocked or rooted, so I only have the stock recovery. Any suggestions on how to resurrect this, or am I headed to customer support for an exchange?
Nastybutler said:
So I just got my Shield Tablet today and of course I get notifications of OTA updates. I applied the first two (1.something and 2.1) just fine. Then the 2.2 update downloads and I tell it to install, which it starts to do. Little Android with his chest open shows up and the status bar does it's thing, then it reboots back to the nvidia boot image.... and hangs there. For over an hour I let it stay to see if it was doing some updating in the background, but nothing else happens. So I power it down by holding the power button, then turn it back on. Same deal. Stuck at the boot image.
Of course I'm not unlocked or rooted, so I only have the stock recovery. Any suggestions on how to resurrect this, or am I headed to customer support for an exchange?
Click to expand...
Click to collapse
you need to unlock the bootloader
Daniele12 said:
you need to unlock the bootloader
Click to expand...
Click to collapse
I am facing the same problem after OTA 3.0 update.
I tried all methods of unlocking bootloader but couldn't.
Please help me if any new method of unlocking bootloader is available.
VijayBais said:
I am facing the same problem after OTA 3.0 update.
I tried all methods of unlocking bootloader but couldn't.
Please help me if any new method of unlocking bootloader is available.
Click to expand...
Click to collapse
Can you not get it to boot into the bootloader? (Press and hold Vol - and then press the power button)
Keithn said:
Can you not get it to boot into the bootloader? (Press and hold Vol - and then press the power button)
Click to expand...
Click to collapse
yes i can get into the fastboot mode.
But the point is that i couldn't unlock the device using "fastboot oem unlock" command.
Also USB Debugging is disabled, and cant boot inside android to enable it.
VijayBais said:
yes i can get into the fastboot mode.
But the point is that i couldn't unlock the device using "fastboot oem unlock" command.
Also USB Debugging is disabled, and cant boot inside android to enable it.
Click to expand...
Click to collapse
USB debugging isn't necessary, that's for ADB. What does it tell you when you try to use that command? Is it "waiting for device" ? I would check to make sure you have drivers for fastboot and that the shield is using them (sometimes it won't automatically load the proper driver).
Also, no custom recovery?
Keithn said:
USB debugging isn't necessary, that's for ADB. What does it tell you when you try to use that command? Is it "waiting for device" ? I would check to make sure you have drivers for fastboot and that the shield is using them (sometimes it won't automatically load the proper driver).
Also, no custom recovery?
Click to expand...
Click to collapse
It shows following unknown error
C:\Downloads\nv-recovery-image-shield-tablet-lte-row-update2_2_1\image>fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
FAILED (remote: (Unknown error code))
finished. total time: 5.003s
I know this won't help VijayBais, but after a while I guess the stock kernel and everything settled in and it stopped random restarting and when I did restart, after installing apps and whatnot, it booted right back up. Now that I'm on 5.1, I haven't had any issues with it freezing up, or random restarts. Crisis averted.
VijayBais said:
It shows following unknown error
C:\Downloads\nv-recovery-image-shield-tablet-lte-row-update2_2_1\image>fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
FAILED (remote: (Unknown error code))
finished. total time: 5.003s
Click to expand...
Click to collapse
Not sure what else to do. Is your recovery stock? Have you tried to do a factory reset then unlock?
Keithn said:
Not sure what else to do. Is your recovery stock? Have you tried to do a factory reset then unlock?
Click to expand...
Click to collapse
No, I haven't done any factory reset till now.
Even the recovery option doesn't proceed to further options on bootloader page.
You can't get into the recovery menu? When you chose it and get the dead android do you quickly tap the power+volume up combo?
655/5000
Hello everybody,
I have a small or big problem.
I wanted to flash a new ROM. Unfortunately, I can not flash the TWRP.
Each time:
PHP:
C: \ Users \ Marcel \ Downloads \ adb 1.0.36 and fastboot> fastboot flash recovery twrp-3.1.1-0-frd.img
Target reported max download size of 471859200 bytes
Sending 'recovery' (25184 KB) ...
OK [0.544s]
Writing 'recovery' ...
FAILED (remote: Command not allowed)
finished. Total time: 0.557s
In Fastboot mode, PHONE is unlocked (in red) and FRP lock (in green). Does the FRP have anything to do with it?
Since then I can not use the Honor Recovery. He wants to download something, but that does not work.
Also with the "dload" upgrade he makes a rebootart and the Screen " YOur devices is booting now..."
Can anyone give me a hint?
It's the FRP lock. Delete all the Google accounts on your phone, that should free up the FRP lock and let you flash recovery.
Hello,
Thank you very much. About settings I could disable the FRP.
FRP and Phone ist UNLOCK.
TWRP I can copy. About the one Huawei multitool I came 1 time in the recovery mode. There I made a wipe. The installation of the new Custom Rome did not work (Error Code 7).
Now I'm only in the fastboot mode. In the TWRP I come no more pure.
The mobile phone is constantly running again.
It is not recognized in the Huawei Multitool. From the console (cmd) I can use fastboot mode.
How can I save it?
I've never used the multitool, so I can't help you there. I always flash directly from ADB.
Via the cmd I can copy the recovery (twrp). But if I want to restart the devices, the twrp does not start. Therefore, I try the tool.
It is very annoying that you can not just start the twrp.
Also delete or copy system, boot, etc is not (FAILED (remote: Command not allowed))
Use the button combo to get into TWRP. Power the device off, then hold down Power + Vol Up. When you feel the short vibrate, let go of power, keep holding Vol Up. It should boot you into TWRP.
many thanks for the help. Apparently I must be too stupid for it.
I have only 2 options.
1. Volume down (-) with power to fastboot mode.
2. Volume high (+) (the topmost pressure point (head)) with power. Here I get into the overview:
Your devices has been unlocked and can't be trusted.
(1) Presspower key to continue
(2) Press VOlumen Up key to 2 Secondary to restore your device.
(3) Your devices will continue to boot 5 seconds later if there is no operation
No matter how, it always stands YOur devices is booting now ...
After a few minutes he makes a reboot
EDIT: After I have done the Unbrick with the tool, the mobile phone starts again. But if I install TWRP or get to use, then it is only version 3.0.2.0
Ive scoured the web for the solution to this but for the life of me can not get my boot loader to unlock. I know enough of this to get me by, but obviously I am not an expert by any means. This is one of the pre recall tablets that I had rooted to avoid the kill code. It was so long ago when I did this that I don't completely remember how I did it. But apparently I didn't have to unlock the bootloader to root it.
I haven't used this tablet in ages and decided to pick it up again but was getting errors that I needed to update google play services but it was not allowing me to do so. I have the Custom Rom Blisspop installed but it appears that they have quite support for it. So I was going to wipe that off and load Lineage. so I tried to get into recovery and it kept just stalling at the loading screen. So now I am wondering if I even flashed a recovery to it to make a backup. Regardless I wouldn't want to restore and risk getting the kill code delivered.
So the next thing I tried to do was flash twrp (and yes I did use the NVidia shield tablet version) and it said that it was successful but still could not boot into recovery. Then I noticed that it said my bootloader was locked on the bootloader screen. So I installed the platform tools and the drivers and adb was recognizing my tablet and everything was good. Until.... I did "adb reboot bootloader" and then "fastboot devices" or even "fastboot oem unlock" nothing worked. No devices would show up. But this whole time adb works. No matter what drivers I install or anything, I cannot get fastboot to recognize the device. I even changed the USB port to the back of my pc straight off the mobo and ran the cmd as admin and nothing is working.
I am starting to get discourage that my efforts are going to be for naught. Expecially since I am not sure exactly how I rooted it in the first place? which is completely my fault for not documenting it. Any and all help is greatly appreciate and I apologize if this has already been solved else were or is being posted to an incorrect location.
Thank you!
Brandon
Ok, i finally figured out that the fastboot driver wasnt working. I ran "adb reboot bootloader" and while in fastboot mode, i found in the PC's device manager that there was an error with the driver. I manually updated it and i am finally able to successfully run "fastboot oem unlock".
But now im getting an error with it saying it failed....
Code:
C:\WINDOWS\system32>fastboot oem unlock
...
FAILED (command write failed (No error))
finished. total time: 0.002s
I am unsure what this means and will do some more researching. I will post back if i make any headway. Once again, i thank anyone in advance for any assistance they may be able to provide.
Apparently i had to unplug the tablet after installing the driver for fastboot before "fastboot oem unlock" would work. But it now says "Device = unlocked"!!!! hopefully i dont mess anything else up...
So now the tablet is "unlocked". I went to do "fastboot flash recovery twrp.img" and said it succeeded. I then proceeded to to do "fastboot reboot" and read that you should immediately load back into bootloader because some tablets will overwrite the recovery to stock if twrp isnt given a chance to correct this. So i did just that then volume keyed down to recovery and its back to doing the same thing where i am stuck on the nvidia logo loading screen. Does anyone have any suggestions on a fix for this? It appears that the tablet is refusing to enter recovery mode?
The reason why i need to get into recovery is for A: to make a backup. and B: to clear my current blisspop rom so that i can load a different Rom. I doubt it would be a good idea to install an OS on top of another OS. But who knows, maybe thats fine?
Code:
C:\Users\bwach>fastboot flash recovery twrp.img
target reported max download size of 570425344 bytes
sending 'recovery' (12426 KB)...
OKAY [ 0.431s]
writing 'recovery'...
OKAY [ 0.579s]
finished. total time: 1.015s
C:\Users\bwach>fastboot reboot
rebooting...
finished. total time: 0.004s
Once again, I thank you for the help.
I was up all hours of the no ight last night trying to solve this with no luck. Is there anyone here who might be able to help me?
Still can't get recovery to load... Tried everything. I did "fastboot - w", I tried flashing lineage on top of bliss pop. Nothing I do will give me access to recovery...
Any ideas?
You have to use hardware keys combination (power + volume + or - not sure exactly which) to boot to twrp for the first time after flashing. So hold the combination while you're still in fastboot (bootloader) mode and release when you see nvidia logo. Good luck
Edit : fastboot reboot is a command that takes you to system, not recovery, to reboot to recovery by using commands you habe to type fastboot reboot recovery. But still, I believe you have to enter for the first time using the buttons combination but it may work with fastboot reboot recovery
It's possible the bootloader is too old for the current twrp release to boot. Which version of android is on the tablet? If it's like L, then you'll have to either update the bootloader manually or update stock first, then twrp will work. There's a note about this on the twrp device page.
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.