I got my tf700 today for Christmas and I've run into a problem I can't seem to get past. I've upgraded to jellybean (i should have rooted first apparently) and used the asus download to unlock the bootloader, other than that no changes. For some reason my tablet will not start up in fastboot mode. I can select the option in the bootloader menu, however it just freezes, no new text or anything on the lefthand side (as happens with my brothers tf300). Any help would be much appreciated.
zopiclone said:
I got my tf700 today for Christmas and I've run into a problem I can't seem to get past. I've upgraded to jellybean (i should have rooted first apparently) and used the asus download to unlock the bootloader, other than that no changes. For some reason my tablet will not start up in fastboot mode. I can select the option in the bootloader menu, however it just freezes, no new text or anything on the lefthand side (as happens with my brothers tf300). Any help would be much appreciated.
Click to expand...
Click to collapse
Can you boot into the OS? during booting up, did you see the text "bootloader is unlocked" in the upper left hand corner?
You should see: "Starting Fastboot USB download protocol" and that IS Fastboot. There will not be any other text. Plug your device into the USB cable and use Fastboot on your PC.
Well I gave up, came back a couple hours later and it was working. For clarification there was no new text showing up announcing it was in fast boot mode at the time, but for whatever reason it started working a little while ago. Now rooted and playing GTA with my ps3 controller
Related
Whether my device is soft bricked or fully, i do not have the slightest. It accepts a charge but will not boot past the "This Device is UnLocked ASUS INSPIRING INNOVATION ....."" Screen nor will it boot into the RCK, Fastboot, menu.
Heres what happened:
I am on the JB Bootloader running CM10 Nightly-11.17 . This happened after upgrading to TWRP 2.3.1 and using terminal on my linux computer to push the TWRP 2.2.1.blob(as I was having issues with the Google Play Store saying it wasnt installed, despite the fact it was) So... I renamed the openrecovery-twrp-2.2.1 to twrp.blob (as per the directions on the TWRP website and look to have successfully pushed the lower version but now I am at a loss. I have yet to let it run completely out of battery but since i have voided the warranty I am not sure what to do. I can hold the power down and press the top volume button to turn it off but i cant boot into the screen with RCK, fastboot, and the other images.
Please help! I appreciate any advice you guys my have. Thanks
So this morning my brother was using his TF300T in its dock. He undocked it and the screen went blank. Screen was still on but nothing displayed. I rebooted it for him (volume down and power button for 10s). After a minute of it powered on the screen went blank again, so I rebooted it again, but this time the Asus splash screen displays and the lock screen flickers before quickly going blank.
Thought a reinstall of the ROM would fix the problem but I now can't even boot into recovery or fastboot! Had no problem the first time I rebooted and selected cold-boot in the bootloader options. With the tablet on and screen blank I plugged it into a PC and Win7 detected and installed the proper drivers (I think). ADB commands seem to work, but the command to boot into bootloader only resets the tablet. Fastboot command does not work. Also noticed the below message flash before a flicker of bootloader options are shown. The PC seems to have access to the internal storage (I can see folders from the tablet) when plugged in via USB.
"Key driver not found.. Booting OS
Android cardhu-user bootloader <2.00 e> released by "US_ePad-10.6.1.8-20130PPt" A03"
Could it be a hardware issue? I ask because I see similar problems with the Asus splash screen indicative of a logic board problem when diagnosing a PC (images pixelated)...
MaMMiTs said:
So this morning my brother was using his TF300T in its dock. He undocked it and the screen went blank. Screen was still on but nothing displayed. I rebooted it for him (volume down and power button for 10s). After a minute of it powered on the screen went blank again, so I rebooted it again, but this time the Asus splash screen displays and the lock screen flickers before quickly going blank.
Thought a reinstall of the ROM would fix the problem but I now can't even boot into recovery or fastboot! Had no problem the first time I rebooted and selected cold-boot in the bootloader options. With the tablet on and screen blank I plugged it into a PC and Win7 detected and installed the proper drivers (I think). ADB commands seem to work, but the command to boot into bootloader only resets the tablet. Fastboot command does not work. Also noticed the below message flash before a flicker of bootloader options are shown. The PC seems to have access to the internal storage (I can see folders from the tablet) when plugged in via USB.
"Key driver not found.. Booting OS
Android cardhu-user bootloader <2.00 e> released by "US_ePad-10.6.1.8-20130PPt" A03"
Could it be a hardware issue? I ask because I see similar problems with the Asus splash screen indicative of a logic board problem when diagnosing a PC (images pixelated)...
Click to expand...
Click to collapse
It is unlikely windows installed the proper drivers for adb and fastboot. The drivers for accessing the internal sdcard yes.
See my signature for installing proper drivers in windows 7 and another for entering the bootloader after you have the proper drivers.
When I have seen that message it does not relate to hardware but software.
I don't suggest plugging and unplugging the dock when powered.
tobdaryl said:
It is unlikely windows installed the proper drivers for adb and fastboot. The drivers for accessing the internal sdcard yes.
See my signature for installing proper drivers in windows 7 and another for entering the bootloader after you have the proper drivers.
When I have seen that message it does not relate to hardware but software.
I don't suggest plugging and unplugging the dock when powered.
Click to expand...
Click to collapse
Will try what you suggested, but does it matter that I'm using the same PC I used to initially fastboot TWRP to the tablet? I thought once the driver is installed it there would be no need to re-install the driver...
MaMMiTs said:
Will try what you suggested, but does it matter that I'm using the same PC I used to initially fastboot TWRP to the tablet? I thought once the driver is installed it there would be no need to re-install the driver...
Click to expand...
Click to collapse
It will probably be ok. I was going by your comment "I plugged it into a PC and Win7 detected and installed the proper drivers (I think)"
tobdaryl said:
It will probably be ok. I was going by your comment "I plugged it into a PC and Win7 detected and installed the proper drivers (I think)"
Click to expand...
Click to collapse
Yeah. My problem is I can't get to fastboot mode on the tablet itself, and based on what I saw on another thread it seems like I'm going to have to replace the mainboard .
MaMMiTs said:
Yeah. My problem is I can't get to fastboot mode on the tablet itself, and based on what I saw on another thread it seems like I'm going to have to replace the mainboard .
Click to expand...
Click to collapse
OK.
Good Luck!
I unplug mine and reconnect all the time when on. Never had a issue.
Sent from magical jelly bean.
My brother's TF300T is back up and running!
As a last resort I opened it up to disconnect the battery. Still could not get into fastboot, so I left the battery plugged in and let the battery run out. After 48 hours of the battery being completely dead I charged it fully to see if I could do anything. Battery LED indicator was green and the first thing I noticed was that the unit was still off. (I wasn't able to completely shut it down before letting the battery completely drain). I powered it on thinking it would display a blank screen, but it powered up as usual! Everything seems to be working. I immediately flashed CROMI-X 4.3b6 on it (what my brother originally wanted me to do).
Thought I'd post this as a last resort hope for those who think they may have bricked their machine. I do recall completely draining the battery then waiting over 24 hours as a solution for one of the many machines I've hacked. Just thought disconnecting the battery would achieve the same purpose. Guess I was wrong . Hopefully this is a solution for someone else out there who may have bricked their machine. Sure doesn't hurt to try .
I'm actually mystified as to why this worked. Anyone know? I'm guessing completely draining the battery reset whatever was inside. I also have noticed more users have reportedly bricked their machines after Android 4.2.1. Coincidental? Thank God I'm perfectly happy with Android 4.1.1 based CROMI v3.4.6 .
So, my new/used mobo boots,but is password protected. it was not set back to factory. Tried getting into rck, and I get a dead android. No other menu options except to wipe and Android. Anyone point me in the right direction?
n3tm0nk said:
So, my new/used mobo boots,but is password protected. it was not set back to factory. Tried getting into rck, and I get a dead android. No other menu options except to wipe and Android. Anyone point me in the right direction?
Click to expand...
Click to collapse
Sounds like you're in official 4.2 bootloader, which apparently has no USB icon. When you hit RCK on official loader, if you don't have an official rom loaded somewhere, you'd end up with an android on its belly. Out of caution you should verify with an "elder", or elderly for that matter, if there's a way to ascertain, from where you are, what bootloader you presently have.
On my part, I'd say if you hold down volume - and power, and the tab gets into fastboot mode automatically, this indicates official bootloader 4.2. Then you can use ADB to push or flash TWRP recovery, I think. When in Windows with ADB drivers installed, check when you connect your tab to your PC to ensure it shows up as "fastboot device." And you need to flash the correct version (4.2.1). Read this thread first. Good luck.
transformer pad tf300t
graphdarnell said:
Sounds like you're in official 4.2 bootloader, which apparently has no USB icon. When you hit RCK on official loader, if you don't have an official rom loaded somewhere, you'd end up with an android on its belly. Out of caution you should verify with an "elder", or elderly for that matter, if there's a way to ascertain, from where you are, what bootloader you presently have.
On my part, I'd say if you hold down volume - and power, and the tab gets into fastboot mode automatically, this indicates official bootloader 4.2. Then you can use ADB to push or flash TWRP recovery, I think. When in Windows with ADB drivers installed, check when you connect your tab to your PC to ensure it shows up as "fastboot device." And you need to flash the correct version (4.2.1). Read this thread first. Good luck.
Click to expand...
Click to collapse
Thank you for your reply.
Forgot to include the fact that the tab has not been unlocked or rooted.
The tab doesn't go into fastboot. My windows laptop recognizes it as a media mtp device and wants to synch with it every time I plug it in, but neither fastboot or adb see it.
n3tm0nk said:
Thank you for your reply.
Forgot to include the fact that the tab has not been unlocked or rooted.
The tab doesn't go into fastboot. My windows laptop recognizes it as a media mtp device and wants to synch with it every time I plug it in, but neither fastboot or adb see it.
Click to expand...
Click to collapse
What happens when you follow the directions here by Tobdaryl (reverting back to official 104220 where 4.2 is encrypted)? Short of returning the MB, ain't much you can do hanging on to it, right? I've done this with my tab on official 4.2, and it went back to official 104220 without problems. Must warn you though, it took quite a few minutes and at times, looked as if it's frozen. Just leave it on till it says it's done. Patience counts.
I have messed around with all my electronics in the passed, rooted them, put custom roms etc. with no trouble. So after getting frusterated with my Asus TF700T, I decided it was time to put Cyanogenmod on it. I read up on the forums and it recommended TWRP, I have always used clockwork mod but because TWRP was recommended I used that. I followed the directions and rebooted to the startup and it is stuck on the Cyanogenmod startup screen. So thinking that maybe it was just taking a long time because it was the first time, I waited and waited and waited. 24 hours later still stuck on the startup screen. I decided to try again, I pressed the power button and the volume down button and this is what I see:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.10-20130801" A03
Starting Fastboot USB Download Protocol
Than I have 3 choices to choose from: RCK, Android, and wipe data
When I press volume up once to select RCK I get a message stating:
Booting Recovery Kernel image
Booting Failed
Unrecoverable bootloader error <0x00000000>. (This part is in red)
After reading I decided to try tranformer tool kit. So I put the tablet into APX mode. Seems to work, tablet restarts with a blank screen, the computer makes the appropriate noises expected when it detects the tablet, but when I check ADB I get a message ADB is not working or communicating with your pad. Evidently I screwed things up somewhere but I don't know where to go from here... Please, If anyone can help, It would be so appreciated.
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
I sounds like the recovery flash failed. If you haven't already, I would try to re-flash TWRP through ADB and fastboot.
If you aren't sure how to do that through ADB use this post:
http://forum.xda-developers.com/showthread.php?t=2688891
Its the beginners guide in the general section.
I may be wrong here, but I've taken my TF700 from the brink of death and back again a few times.
What TWRP version did you flash and how???
The unrecoverable bootloader error is not good news. Usually you need a buster99 to get your tablet back - if you still can get into the bootloader and fastboot.
If you can, follow the instructions below to the letter (naturally you have to flash the TF700 system blob, not the TF300!), then flash a compatible recovery and a rom compatible with your recovery and bootloader. And if you're not sure ask first, then flash....
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
xellysiax said:
I have messed around with all my electronics in the passed, rooted them, put custom roms etc. with no trouble. So after getting frusterated with my Asus TF700T, I decided it was time to put Cyanogenmod on it. I read up on the forums and it recommended TWRP, I have always used clockwork mod but because TWRP was recommended I used that. I followed the directions and rebooted to the startup and it is stuck on the Cyanogenmod startup screen. So thinking that maybe it was just taking a long time because it was the first time, I waited and waited and waited. 24 hours later still stuck on the startup screen. I decided to try again, I pressed the power button and the volume down button and this is what I see:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.10-20130801" A03
Starting Fastboot USB Download Protocol
Than I have 3 choices to choose from: RCK, Android, and wipe data
When I press volume up once to select RCK I get a message stating:
Booting Recovery Kernel image
Booting Failed
Unrecoverable bootloader error <0x00000000>. (This part is in red)
After reading I decided to try tranformer tool kit. So I put the tablet into APX mode. Seems to work, tablet restarts with a blank screen, the computer makes the appropriate noises expected when it detects the tablet, but when I check ADB I get a message ADB is not working or communicating with your pad. Evidently I screwed things up somewhere but I don't know where to go from here... Please, If anyone can help, It would be so appreciated.
Click to expand...
Click to collapse
xellysiax - We are sorry to hear about your tablet and is this still an ongoing issue? Send us an email at [email protected] with this post and your serial number and we will be more than happy to assist you.
If you have any further questions, comments, or concerns please do not hesitate to let us know. We will be more than happy to assist you. Once again, thank you for choosing ASUS products and services.
Thank you,
-In Search of Incredible-
Technical Support Department
http://www.asus.com :: http://service.asus.com/
Ummmm let me take a wild guess what customer support will advise:
Sorry you unlocked so no warranty but send it in and for $300 we may repair it. If we can't we only charge you for shipping both ways.
Nice to see you, Asus! Where've you been the last 2 years?
berndblb said:
Ummmm let me take a wild guess what customer support will advise:
Sorry you unlocked so no warranty but send it in and for $300 we may repair it. If we can't we only charge you for shipping both ways.
Nice to see, Asus! Where've you been the last 2 years?
Click to expand...
Click to collapse
Hush! @Asus_USA wanted to anounce the roll-out of Android Lollipoop for ASUS Transformers. Or was it the source code of bootloader?
das chaos said:
Hush! @Asus_USA wanted to anounce the roll-out of Android Lollipoop for ASUS Transformers. Or was it the source code of bootloader?
Click to expand...
Click to collapse
Yeah - I had that dream too one time or another....
Hi all, I just encountered this same error message for the TF700T when going into fastboot mode
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.10-20130801" A03
Starting Fastboot USB Download Protocol
All I have done is unlock the tablet. I was on the "Practice/Background" step in berndblb's (awesome) custom ROM guide before starting to load up fastboot and adb, when I saw the message in the upper left corner. When I go into RCK, "booting recovery kernel image" then appears under the error message. After 3-4 seconds I get the dead android with "error!" screen. When I power off, the tablet goes into normal bootup and the stock ROM still works perfectly fine.
Since it does, is there something I should do to resolve this issue BEFORE trying to push TWRP to the tablet? Just trying to be prudent...
Many thanks,
MM
Every Asus tablet I have seen has the "key driver not found" on boot - ignore it.
The dead Droid also is perfectly normal. It's the stock recovery not finding a firmware file to flash. Just keep going
berndblb said:
Every Asus tablet I have seen has the "key driver not found" on boot - ignore it.
The dead Droid also is perfectly normal. It's the stock recovery not finding a firmware file to flash. Just keep going
Click to expand...
Click to collapse
Brilliant, thanks. Now, let's see how this goes...
Cheers
Hello.
I did something wrong while trying to flash TWRP on my pixel 2, I am now stuck at the bootloader, and I cannot boot System or Recovery. While at the bootloader screen, it says Device State : unlocked. If I try to get to download mode, it says "ERROR: Operation Denied". If I try to go into recovery, it says "ERROR: Slot Unbootable: Load Error". If I try "Start", I get the same error message.
Also, adb or fastboot don't seem to be able to "see" the pixel connected to the computer. I believe my cables are good since I was able to flash Magisk and reflash the whole system with them before bricking it.
Can anyone help?
Thanks!
stanelie said:
Hello.
I did something wrong while trying to flash TWRP on my pixel 2, I am now stuck at the bootloader, and I cannot boot System or Recovery. While at the bootloader screen, it says Device State : unlocked. If I try to get to download mode, it says "ERROR: Operation Denied". If I try to go into recovery, it says "ERROR: Slot Unbootable: Load Error". If I try "Start", I get the same error message.
Also, adb or fastboot don't seem to be able to "see" the pixel connected to the computer. I believe my cables are good since I was able to flash Magisk and reflash the whole system with them before bricking it.
Can anyone help?
Thanks!
Click to expand...
Click to collapse
happened to my walleye too , and managed to bring it back to life . check this thread for a possible solution. https://forum.xda-developers.com/pixel-2/help/december-factory-image-to-broken-t3875213
Thanks!
I missed that thread while researching this issue.
I will try these things when I get back from work next week.
Thanks again!
stanelie said:
Thanks!
I missed that thread while researching this issue.
I will try these things when I get back from work next week.
Thanks again!
Click to expand...
Click to collapse
Just as a reference for anyone else who needs the fix and can't be bothered opening another thread.
SOLUTION: At the menu where it is stuck and saying device fail etc, plug in your usb cable to the mobile, press and hold the POWER button for 10 seconds, it will now recognise your phone under fastboot.
Once that is cleared, it's pretty much straightforward flashing latest pixel 2 image via fastboot and problem solved.
sidenote: Issue came with anyone who tried to flash december security updates and above as of what I heard.
I will try that, thanks.
So, several things :
Holding down the power button had no effect other than restarting the boot menu, but Fastboot never became available.
Opening up the phone and disconnecting the battery and reconnecting it made Fastboot available again. This would be in line with other users that let the phone battery discharge completely before regaining fastboot access.
Sidenote : opening up this phone is not for the faint of heart. I managed to damage something on the motherboard doing so (probably a static electricity discharge), the screen ended up displaying gibberish. I was able to salvage my phone by replacing the motherboard. I had ordered a replacement motherboard when I thought all was lost with no fastboot, and I had it on hand. Expensive little sucker...
stanelie said:
Hello.
I did something wrong while trying to flash TWRP on my pixel 2, I am now stuck at the bootloader, and I cannot boot System or Recovery. While at the bootloader screen, it says Device State : unlocked. If I try to get to download mode, it says "ERROR: Operation Denied". If I try to go into recovery, it says "ERROR: Slot Unbootable: Load Error". If I try "Start", I get the same error message.
Also, adb or fastboot don't seem to be able to "see" the pixel connected to the computer. I believe my cables are good since I was able to flash Magisk and reflash the whole system with them before bricking it.
Can anyone help?
Thanks!
Click to expand...
Click to collapse
Same thing happened to me except I never even tried to root. Just pulled the phone out of my pocket, and the little Android dude was belly up. It's showing device locked - and although I had it in Dev. mode from weeks back (thought USB Debugging was enabled) it fails to respond to adb commands, boot-loader mode, etc.
...Looks like Google laid an egg with this one.
Pixel 2 - "ERROR: Slot Unbootable: Load Error"
If you get the above error you will find that you cannot boot into recovery and the phone stays in the bootloader screen each time you try to start the phone. If your bootloader is unlocked you might be able to recover your phone to flash a stock image and revive. My problem started when I tried to restore a nandroid backup after trying out Android Q beta 1. I got the error mentioned above.
Most of the people recommended that I get a replacement from Google support as they had tried everything but it didn't work. Well right here in XDA Pixel 2 forum there is a solution waiting to be used. I am reproducing it from the post titled
"December factory image seems to have broken fastboot enumeration"
Quote
A possible way to resurrect a bricked Pixel 2...
Hey guys, I have just been able to get mine alive. The device started to be recognized (USB/fastboot) after about 10 unsuccessful attempts to start the system: "Start", from bootloader.
So what exactly happened and what I did:
1. Bricked a Pixel 2.
2. It started into bootloader and showed the "slot unbootable" error.
3. The device was not recognized by any of my machines at all, lsusb did not show anything new in the system, and, respectively, fastboot did not see the device.
4. The default option in the bootloader is "Start" if I remember correctly. So I just pressed the power button and did not release it until I noticed a vibration. It were about 10 unsuccessful attempts of system loading before that vibration.
5. Right after that vibration I connected a generic (NONAME) USB-C <-> USB-A cable to both the device and my Linux machine, and fortunately the device was recognized by the system and fastboot was able to detect the device correctly. So I flashed the a factory image, and it went just fine.
Unquote
Let me confirm that this works. I kept the power button down while the phone was connected via USB to the PC for at least 5 mins. During several reboots suddenly I got a beep from the PC which indicated that ADB was working. I flashed a stock image and voila the pixel 2 is back in operation.
Hope this helps several other people who might have this problem.
ashokabs said:
If you get the above error you will find that you cannot boot into recovery and the phone stays in the bootloader screen each time you try to start the phone. If your bootloader is unlocked you might be able to recover your phone to flash a stock image and revive. My problem started when I tried to restore a nandroid backup after trying out Android Q beta 1. I got the error mentioned above.
Most of the people recommended that I get a replacement from Google support as they had tried everything but it didn't work. Well right here in XDA Pixel 2 forum there is a solution waiting to be used. I am reproducing it from the post titled
"December factory image seems to have broken fastboot enumeration"
Quote
A possible way to resurrect a bricked Pixel 2...
Hey guys, I have just been able to get mine alive. The device started to be recognized (USB/fastboot) after about 10 unsuccessful attempts to start the system: "Start", from bootloader.
So what exactly happened and what I did:
1. Bricked a Pixel 2.
2. It started into bootloader and showed the "slot unbootable" error.
3. The device was not recognized by any of my machines at all, lsusb did not show anything new in the system, and, respectively, fastboot did not see the device.
4. The default option in the bootloader is "Start" if I remember correctly. So I just pressed the power button and did not release it until I noticed a vibration. It were about 10 unsuccessful attempts of system loading before that vibration.
5. Right after that vibration I connected a generic (NONAME) USB-C <-> USB-A cable to both the device and my Linux machine, and fortunately the device was recognized by the system and fastboot was able to detect the device correctly. So I flashed the a factory image, and it went just fine.
Unquote
Let me confirm that this works. I kept the power button down while the phone was connected via USB to the PC for at least 5 mins. During several reboots suddenly I got a beep from the PC which indicated that ADB was working. I flashed a stock image and voila the pixel 2 is back in operation.
Hope this helps several other people who might have this problem.
Click to expand...
Click to collapse
I don't even know how to thank you. I almost had a heart attack watching my Pixel bricked. Thanks man!
Save my day! I just keep pressing power button and fastboot response finally!
Can this be done if the device is locked?
_Kalyan said:
I don't even know how to thank you. I almost had a heart attack watching my Pixel bricked. Thanks man!
Click to expand...
Click to collapse
Does ur bootloader locked or unlocked?
---------- Post added at 11:36 AM ---------- Previous post was at 11:36 AM ----------
ashokabs said:
If you get the above error you will find that you cannot boot into recovery and the phone stays in the bootloader screen each time you try to start the phone. If your bootloader is unlocked you might be able to recover your phone to flash a stock image and revive. My problem started when I tried to restore a nandroid backup after trying out Android Q beta 1. I got the error mentioned above.
Most of the people recommended that I get a replacement from Google support as they had tried everything but it didn't work. Well right here in XDA Pixel 2 forum there is a solution waiting to be used. I am reproducing it from the post titled
"December factory image seems to have broken fastboot enumeration"
Quote
A possible way to resurrect a bricked Pixel 2...
Hey guys, I have just been able to get mine alive. The device started to be recognized (USB/fastboot) after about 10 unsuccessful attempts to start the system: "Start", from bootloader.
So what exactly happened and what I did:
1. Bricked a Pixel 2.
2. It started into bootloader and showed the "slot unbootable" error.
3. The device was not recognized by any of my machines at all, lsusb did not show anything new in the system, and, respectively, fastboot did not see the device.
4. The default option in the bootloader is "Start" if I remember correctly. So I just pressed the power button and did not release it until I noticed a vibration. It were about 10 unsuccessful attempts of system loading before that vibration.
5. Right after that vibration I connected a generic (NONAME) USB-C <-> USB-A cable to both the device and my Linux machine, and fortunately the device was recognized by the system and fastboot was able to detect the device correctly. So I flashed the a factory image, and it went just fine.
Unquote
Let me confirm that this works. I kept the power button down while the phone was connected via USB to the PC for at least 5 mins. During several reboots suddenly I got a beep from the PC which indicated that ADB was working. I flashed a stock image and voila the pixel 2 is back in operation.
Hope this helps several other people who might have this problem.
Click to expand...
Click to collapse
Works on bootloader state locked or not?
SoKa1993 said:
Does ur bootloader locked or unlocked?
---------- Post added at 11:36 AM ---------- Previous post was at 11:36 AM ----------
Works on bootloader state locked or not?
Click to expand...
Click to collapse
If the boot loader is locked look for a script for unlocking the bootloader from recovery or bootloader state. I did find it but cannot remember. My bootloader was unlocked so I did not have to use it.
ashokabs said:
Pixel 2 - "ERROR: Slot Unbootable: Load Error"
If you get the above error you will find that you cannot boot into recovery and the phone stays in the bootloader screen each time you try to start the phone. If your bootloader is unlocked you might be able to recover your phone to flash a stock image and revive. My problem started when I tried to restore a nandroid backup after trying out Android Q beta 1. I got the error mentioned above.
Most of the people recommended that I get a replacement from Google support as they had tried everything but it didn't work. Well right here in XDA Pixel 2 forum there is a solution waiting to be used. I am reproducing it from the post titled
"December factory image seems to have broken fastboot enumeration"
Quote
A possible way to resurrect a bricked Pixel 2...
Hey guys, I have just been able to get mine alive. The device started to be recognized (USB/fastboot) after about 10 unsuccessful attempts to start the system: "Start", from bootloader.
So what exactly happened and what I did:
1. Bricked a Pixel 2.
2. It started into bootloader and showed the "slot unbootable" error.
3. The device was not recognized by any of my machines at all, lsusb did not show anything new in the system, and, respectively, fastboot did not see the device.
4. The default option in the bootloader is "Start" if I remember correctly. So I just pressed the power button and did not release it until I noticed a vibration. It were about 10 unsuccessful attempts of system loading before that vibration.
5. Right after that vibration I connected a generic (NONAME) USB-C <-> USB-A cable to both the device and my Linux machine, and fortunately the device was recognized by the system and fastboot was able to detect the device correctly. So I flashed the a factory image, and it went just fine.
Unquote
Let me confirm that this works. I kept the power button down while the phone was connected via USB to the PC for at least 5 mins. During several reboots suddenly I got a beep from the PC which indicated that ADB was working. I flashed a stock image and voila the pixel 2 is back in operation.
Hope this helps several other people who might have this problem.
Click to expand...
Click to collapse
I have same problem. I use Pixel 2 and Fedora. My question is, what i exactly should do? I mean the steps. I didn't get that beep from my laptop. But I got the vibration when I hold the power button when it's not connected to USB. Please Help me.
Sorry my english isn't that good.