Related
Hi. I just received my Xoom back after the 4G upgrade and now I'm unable to root. I've followed all the steps, but when I type fastboot oem unlock, the command prompt just says <Waiting for Device> (I've confirmed that ADB can see the device), and that's it....it just sits there. Can anyone help me?
Did you boot up the xoom? And do a DB reboot bootloader? Then fastboot OEM unlock?
Sent from my Xoom using xda premium
Yes I did...
Was it unlocked when you sent in? If so it may still be unlocked.
Sent from my Xoom using xda premium
It was unlocked, but they've upgraded the software to 3.2.2 and it's locked again.
It might not be. They don't have to lock it to flash it. And they probly didn't check either.
Sent from my Xoom using xda premium
Ok....pardon the ignorance but how can I tell? I no longer have Superuser. I can't even flash a custom image. Should I downgrade it to 3.0, Root, and then flash it with the Custom 3.2.2 found here on XDA?...
No not that way it screws it up! Use this and only this! Skip the unlock and see if the files work, then you know you were still unlocked.
http://forum.xda-developers.com/showthread.php?t=1242241
Sent from my Xoom using xda premium
Hammer....tried that....no matter what, once the Xoom bootloader reboots, all I get is: Starting Fastboot Protocol Support. Nothing else happens and my adb windows just sits there and says Waiting for Devices.
tdetroit said:
Hammer....tried that....no matter what, once the Xoom bootloader reboots, all I get is: Starting Fastboot Protocol Support. Nothing else happens and my adb windows just sits there and says Waiting for Devices.
Click to expand...
Click to collapse
That's because your timing is slightly off, and you're letting the stock recovery overwrite your custom recovery. You have to "catch the boot"
You can follow these steps:4. Install recovery image (CWM)
If you haven't done it already, download the recovery image file and save it to your computer in the Platform Tools folder.
(Download the recovery image from this link: http://forum.xda-developers.com/show....php?t=1074979 only the img file flashed through fastboot Remember, never try to flash a zip file through fastboot!)
4.1 Boot into flash mode with 'adb reboot bootloader.'
4.2 Install your downloaded recovery image: 'fastboot flash recovery recovery-solarnz-100611-1150.img' or whatever is the exact name of the recovery img file you are flashing.
4.3 Enter CWM recovery with the procedure below.
4.4 Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo section 4.
4.5 Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work (if you see Starting Fastboot Protocol), experiment with the timing (see below).
4.6 When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for getting this far!
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. Just repeat steps 4.1 through 4.6 if that happens.
tdetroit said:
Hi. I just received my Xoom back after the 4G upgrade and now I'm unable to root. I've followed all the steps, but when I type fastboot oem unlock, the command prompt just says <Waiting for Device> (I've confirmed that ADB can see the device), and that's it....it just sits there. Can anyone help me?
Click to expand...
Click to collapse
I got mine back yesterday morning then used the Universal Xoom Root instructions and files to root it yesterday afternoon. Perfect!
-ts
I've tried that...won't work. As far as my timing being off....I'm literally watching the Screen the whole time...I never even get anything except the Fastboot Protocol screen...nothing changes. I simply can't go further. I've tried loading the img file (Step 4), but can't even get that far. I've spent an hour on the phone with Motorola yesterday and after being bounced to 5 different techs, they told me to contact the developer.....which I've done, with no success. I'm almost tempted to send this damn thing back and ask them to revert my device and install an older OS onto it.
Let the device boot all the way and make sure debugging is checked.
Sent from my ADR6400L using xda premium
hammer4203 said:
Let the device boot all the way and make sure debugging is checked.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
It is. That was the first thing I've checked.
Then androidsdk may be fubar. Reload your sdk and try again. Make sure to use the newest and download all the files it needs. Redownload the root files too. Then see what happens. My sdk had to be updated when I bought my xoom.
Sent from my ADR6400L using xda premium
hammer4203 said:
Then androidsdk may be fubar. Reload your sdk and try again. Make sure to use the newest and download all the files it needs. Redownload the root files too. Then see what happens. My sdk had to be updated when I bought my xoom.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Ah, I will do that. Matter of fact, I'll download it to my other laptop...which never had any sort of anything SDK related on it, give it a fresh start. Thanks....will do this when I get home this evening.
No such luck. Step two: Fastboot oem unlock....window says: < waiting for device > and my xoom just sits there and says: Starting Fastboot Protocol Support.
I've tried this on a totally different laptop, brand new SDK installed, fastboot, and the motorola drivers for the xoom. I'm at my wits end.
tdetroit said:
No such luck. Step two: Fastboot oem unlock....window says: < waiting for device > and my xoom just sits there and says: Starting Fastboot Protocol Support.
I've tried this on a totally different laptop, brand new SDK installed, fastboot, and the motorola drivers for the xoom. I'm at my wits end.
Click to expand...
Click to collapse
Nevermind. IT WORKED. I ended up using my work laptop. Something's wonky with both of my personal laptops....either way, it's now unlocked. Thanks for everyone's help and patience.
Ur welcome! Also remember your mouse on a desktop? Took me weeks to figure out the damn thing was causing the bsod errors, and it seemed to work perfectly fine. I would back up your computers you have issues with and do a fresh install on them. I do every 6mo or so.
Sent from my Xoom using xda premium
i may be up a creek now. i've tried everything i can.
here's the whole situation, maybe someone can offer some guidance on how i can get my phone back.
i installed this rom, http://forum.xda-developers.com/showthread.php?t=1835478, but did not see that there was a problem with people getting stuck at the initial google boot logo. i wouldn't have tried it if i did.
but it's too late now. so i too have that problem. in addition, i also have that problem with the nexus s in that the power button is busted, works only to boot the phone.
so i boot the phone normally, i get to that boot logo indefinitely.
i press up and power button i get to fastboot screen. for some reason the volume buttons don't work on that screen so i can't pick recovery there. only thing that works is hitting the power button and reboots the bootloader.
i plug the phone into my pc and i can't access it through adb, fastboot... does not recognize a device is connected.
so in summary, all i can do is access the fastboot screen or the boot logo screen.
if someone can help me figure out how to do one of the following: boot into recovery instead of fastboot, figure out how to use the volume buttons in fastboot, or get the phone recognized by my pc so i can use adb, that would be awesome.
i feel like i just bricked it for good....
thanks
Install the SDK. Launch it. Find the drivers to download in the SDK. Install them. Boot the phone into fastboot and connect it to pc. Open up a command prompt IN the directory that has fastboot in it. Type in the command prompt fastboot devices.
If your serial number shoes your good to go. Get the .img of your custom recovery and type fastboot flash recovery nameofile.img. with that being the exact file name ( hint type the first letter of the recovery and hit tab)
Yep, you gotta get fastboot working again. It's pretty important.
Sent from my Nexus S 4G using xda premium
i've had the sdk/driver installed already.
like i said, the phone when it boots is not being recognized by the laptop at all, as if it's not even plugged in. so when i do fastboot devices, nothing shows up.
Was it recognized prior?
Sent from my Nexus 7 using Tapatalk 2
in the prior rom it was recognized by the laptop, before i tried to flash the rom i linked above that created this mess...
albundy2010 said:
Install the SDK. Launch it. Find the drivers to download in the SDK. Install them. Boot the phone into fastboot and connect it to pc. Open up a command prompt IN the directory that has fastboot in it. Type in the command prompt fastboot devices.
If your serial number shoes your good to go. Get the .img of your custom recovery and type fastboot flash recovery nameofile.img. with that being the exact file name ( hint type the first letter of the recovery and hit tab)
Click to expand...
Click to collapse
AlphaEchoViktorSierra said:
Yep, you gotta get fastboot working again. It's pretty important.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Yep fastboot is a great tool, if you have a nexus s then you MUST get it working!
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
wookietv said:
i've had the sdk/driver installed already.
like i said, the phone when it boots is not being recognized by the laptop at all, as if it's not even plugged in. so when i do fastboot devices, nothing shows up.
Click to expand...
Click to collapse
Seems like your nexus s drivers are not installed in your laptop
google the nexus s usb drivers download them and put in the respective folder
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
albundy2010 said:
Was it recognized prior?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
was gonna ask the same question
like i said, i already had the sdk and drivers installed.
they worked fine before i installed that rom.
this definitely seems like it's on the fault of the phone, not the laptop.
looks like you got busted like a SIR!!
Just kidding man dont take it seriously...
I might sound silly but i hope you have tried this but if you have not then do try
Go here and try changing the usb plugs
http://forum.xda-developers.com/showthread.php?t=1785672
IT shows flashboot steps, you need to connect phone in bootloader mode which you are achieving atm, and see if it works
and if it doesnt then let me know i will try to help out more if i could
P.S I am also new in android so pardon my noobnes
i went another route...
i figured i had nothing to lose at this point... so i ripped the phone apart and attempted to fix the power button, which i believed in turn would fix not being able to use the volume keys in the fastboot screen.
i was correct. i jiggled with the power button inside and it seemed to work. the volume keys now reacted in the fastboot screen.
i was able to then get into recovery, wipe the phone, connect the phone to the laptop and put a new rom on it.
i'm not sure if its fixed the button completely, but at least i can get into the new rom :laugh:
well thats a relief and i am glad that you problem is solved
a little advice, get repaired that power button for good so that you have no hassle in near future
converse5 said:
well thats a relief and i am glad that you problem is solved
a little advice, get repaired that power button for good so that you have no hassle in near future
Click to expand...
Click to collapse
+1, I agree with you. It does not cost much as well. I had this problem and was managing with apps. But finally got it replaced for good.
Today I bought the HTC One X
I immediately jumped on xda looking to root, I've rooted in the past with Samsung Infuse and Motorola Backflip, and I'm very discouraged right now
I installed the One_X_ATT_All-In-One_Kit_v2.1 and everything was going well, until I tried to flash the TWRP recovery, and it ran, but didn't at the same time it was very odd
Anyway, in Fastboot I can't flash a recovery because the cmd promt says "error: device not found"
also, there is no OS installed so I'm in a constant bootloop
Main Issues:
- device not found
- boot loop
- recovery won't work because the SD card won't mount, something along those lines
- also day of the super bowl...
Not sure why this is all happening, who can help me out? Willing to donate...
***** TAMPERED *****
***** UNLOCKED *****
EVITA PVT SHIP S-ON RL
HBOOT - 1.14.0002
RADIO - 0.19as.32.09.11_2
OpenDSP - v29 1.0.45.0622
eMMC - boot
Jun 11 2012 14:26:28
You probably factory reset in bootloader by accident... You'll have to plug the phone in and right click on removable storage and format. Even though it doesn't recognize it should still format.
When in fastboot, type in --> fastboot devices
See if it sees anything
Sent from my One X using Tapatalk 2
It also sounds maybe drivers aren't working? I have no idea. Just throwing an idea out there.
Sent from my One X using xda app-developers app
InflatedTitan said:
You probably factory reset in bootloader by accident... You'll have to plug the phone in and right click on removable storage and format. Even though it doesn't recognize it should still format.
When in fastboot, type in --> fastboot devices
See if it sees anything
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I ended up relocking my device, and below **** RELOCKED **** it says **** Security Warning ****
also, typing in fastboot devices worked at first, it showed up, then i relocked device and now it doesn't show up.
Plugged into computer, doesn't show up though, it's charging can't format
Since your relocked (you shouldn't have but its cool lol) download the RUU matching the firmware your phone is using... Run that and it should get you back to stock
Sent from my One X using Tapatalk 2
InflatedTitan said:
Since your relocked (you shouldn't have but its cool lol) download the RUU matching the firmware your phone is using... Run that and it should get you back to stock
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
How am I gonna be able to do any of this if the device can't be found in order to try and flash it?
Can you take the SD card out,and use external SD card to USB to format
Sent from my Dell Streak using xda app-developers app
Reinstall HTC drivers.. Restart computer, and plug USB into back of comp if on desktop, main USB if laptop and try again. Make sure when in bootloader if says fastboot USB in red.
Once again type fastboot devices
See what happens...
Also... Try to right click on your adb/fastboot folder and choose "open command prompt here"... Run CND from that path and see if it helps... Just a thought....
Sent from my One X using Tapatalk 2
GREATTT!!! for some reason now, on my HOX the fastboot usb is only available for one second...
I can't find anything anywhere on this problem, when i boot into bootloader, it's for less than a second... Unbelievable
Relax, then try a different port and cord combo. Then if possible try a different pc
Sent from my HTC One XL
swagglikerichie said:
GREATTT!!! for some reason now, on my HOX the fastboot usb is only available for one second...
I can't find anything anywhere on this problem, when i boot into bootloader, it's for less than a second... Unbelievable
Click to expand...
Click to collapse
ok I fixed this problem, so now I am still stuck on the error: device not found issue
that's my main concern, I can't flash because it can't find the device
Man there's some funny business going on... Try to right click on your adb/fastboot folder and "open command prompt here".... See if that does anything better
It should find it if your in fastboot. You at least sound fairly knowledgeable about most of it.. So I can't say user error... As wrecker said try different ports, try reinstalling HTC drivers and restart computer... Try unplugging and plug back in
Sent from my One X using Tapatalk 2
you can always try with linux then you dont have to mess up with additional drivers
InflatedTitan said:
Man there's some funny business going on... Try to right click on your adb/fastboot folder and "open command prompt here".... See if that does anything better
It should find it if your in fastboot. You at least sound fairly knowledgeable about most of it.. So I can't say user error... As wrecker said try different ports, try reinstalling HTC drivers and restart computer... Try unplugging and plug back in
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
fastboot can find it now, and I was able to read the CID, just 11111111
going to try and flash from fastboot command prompt, how long does it take usually to download boot.img through DOS?
swagglikerichie said:
fastboot can find it now, and I was able to read the CID, just 11111111
going to try and flash from fastboot command prompt, how long does it take usually to download boot.img through DOS?
Click to expand...
Click to collapse
Have no clue, why would you do that? Why not just download a recovery image and fastboot it
Sent from my One X using Tapatalk 2
InflatedTitan said:
Have no clue, why would you do that? Why not just download a recovery image and fastboot it
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
What are other methods of flashing not through the AIO Kit Hansen2000 or something like that?
Also, I tried this http://www.androidauthority. com /one-x-revert-stock-recovery-76854/
and it seemed like it worked, but still no OS installed, constant boot loop
swagglikerichie said:
What are other methods of flashing not through the AIO Kit Hansen2000 or something like that?
Also, I tried this http://www.androidauthority. com /one-x-revert-stock-recovery-76854/
and it seemed like it worked, but still no OS installed, constant boot loop
Click to expand...
Click to collapse
Don't use anything that's not from xda. OS stands for OPERATING SYSTEM! you need to install a recovery first. The toolkit should have contained the recovery image. It should be like open recovery.twrp.2.3.3.img or something like that. Download that file, and drop it in your adb/fastboot folder. Enter fastboot, right click on adb/fastboot folder and choose open command prompt here. Type this --> fastboot flash openrecoveryname.img
^^^ of course replace the end with the exact name if the recovery script you downloaded. Easy peasy right? If you manage to become successful, reboot bootloader and now you can boot into your "custom" recovery (twrp) . if you manage to be inside twrp, High five yourself.
Back on your computer, download cleanrom 5.1.. I'll explain why later once you have a working phone again.
"Mount" in twrp. Watch for your computer to prompt you if what you want to do. Choose "open to view files" or something like that. Next window is your sdcard. Drag cleanrom5.1.zip anywhere on your SD card, just remember where.
In twrp, unmount. Choose install, find the cleanrom5.1.zip. Flash that biootch. Let it boot and report back with any questions
Sent from my One X using Tapatalk 2
So if you run into any more device not found stuff, put the folder of the one x toolkit directly in the root of your C drive. That worked for me.
Edit: I think this actually solves a different issue that I may have confused with yours, but worth a try.
Sent from my HTC One X using xda app-developers app
you should of just run a ruu when phone said fastboot usb and left it stock for life until you learn something
you should also stop using the toolkit and learn to do it all manually first, i haven't yet used the toolkit since this phone is super easy once you learn the basic android stuff and read. flashimagegui is ok since it allows for flashing roms on fly without using pc.
InflatedTitan said:
Don't use anything that's not from xda.
Click to expand...
Click to collapse
Agreed. This webpage the OP mentioned is not even for our phone, its for the quad core version (code named ENDEAVORU). Which is often the case if you go to other websites. They don't clearly delineate between the dual core and quad core versions, which can lead to a real brick.
Particularly in this case, if the file had flashed properly, you would have bricked. Installing the recovery from the wrong device is a bad idea. And recovery is not the same as the OS or ROM.
As others have suggested, it seems the OP needs to read and learn a lot more before doing anything more with the phone, or else permanent damage is going to happen.
I have nexus 5 and its bricked, But I cant unlock the bootloader using fastboot ( I think its because I have no rom ). Is there an another way to unlock the bootloader?
The fastboot oem unblock solution is the only way to unlock the bootloader without root.
If you can't do it then you may have hardware issues.
The phone is recognized when you run the command "fastboot devices"? If not, you'll need to get it recognized before issuing fastboot commands to the phone.
If you have no ROM, and the bootloader is locked, you've gotten yourself into quite the predicament. What error does fastboot oem unlock give you?
Sent from my Nexus 5X using Tapatalk
drsn0w said:
If you have no ROM, and the bootloader is locked, you've gotten yourself into quite the predicament. What error does fastboot oem unlock give you?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I get the devices to oem unlock, but when i try and flash a bootloader.img I get this
Owners-iMac:image-hammerhead-mob31e EmilyHaugen$ ./fastboot flash bootloader /Users/owner/Desktop/android/hammerhead-mob31e/bootloader-hammerhead-hhz20h.img
target reported max download size of 1073741824 bytes
sending 'bootloader' (3124 KB)...
OKAY [ 0.308s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.488s
Strange
Sent from my Nexus 5X using Tapatalk
After unlocking the bootloader, reboot the phone into fastboot and see if the bootloader is still unlocked.
Try relocking the bootloader and then unlock it. If the phone performs a factory wipe in a few seconds, the emmc chip may be damaged.
Primokorn said:
The fastboot oem unblock solution is the only way to unlock the bootloader without root.
If you can't do it then you may have hardware issues.
Click to expand...
Click to collapse
I think that has a root.
My friend rooted it and than remove kingroot (without unroot).
What the way to unlock bootloader with root?
Thenx
matan10 said:
I think that has a root.
My friend rooted it and than remove kingroot (without unroot).
What the way to unlock bootloader with root?
Thenx
Click to expand...
Click to collapse
BootUnlocker app
Primokorn said:
BootUnlocker app
Click to expand...
Click to collapse
But I have no rom. And I cant install rom because my bootloader is locked
matan10 said:
But I have no rom. And I cant install rom because my bootloader is locked
Click to expand...
Click to collapse
I know but you asked. No other solution mate except going to a repair shop.
Hello,
First some background and credits:
There are a few ways to brick a phone. Sometimes it's lack of experience, sometimes it's an accidental thing, sometimes there just isn't an explanation for what went wrong... (share your experience here, if you wish). For me, I owned my OPO for about 4 hours before things went wrong. First thing I did was I rooted it and installed TWRP. After creating a nandroid backup of the stock image I installed my favorite custom ROM and restored all my apps with TiBu. Everything was great and configured just the way I wanted it. I then wiped my old phone (Nexus 4), installed a new ROM and got it all ready for my wife. She was so excited to get rid of her GNex and move up to the N4. But then, for whatever reason, I opened an app on my OPO that I used to manage, download, and install kernels with. It came up with "there is a new kernel update!" and I instinctively clicked on "Install". 10 seconds later my phone was bricked. Nothing came on the screen, no fastboot, no recovery, nothing to boot to, no way to send data to and from it. The second the screen went black and the phone became lifeless I got that wretched feeling in my gut as I realized I just flashed a N4 kernel on my new OPO. Restoring the kernel management app with TiBu made it act like it's still running on my old phone, and in my excitement I didn't take a second to think things through...
I received a bit of consolation when a quick XDA search revealed that I am not the only dumbass to brick his phone this very way. I joined forces with some pretty smart and desperate people and tried different things, all described in the following thread: http://forum.xda-developers.com/oneplus-one/help/wrong-kernel-black-screen-fastboot-adb-t2835696. Unfortunately it took us what seemed like many long weeks to figure it all out. Well, in the end a solution was found and I documented it in the the following post: http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136.
This was a few months ago, but I recently noticed many people continue to search for these directions and have problems finding them hidden among many pages and other threads, so I've decided to put this stand alone thread with these, now updated, directions.
Let me get one more thing straight, for the record. I did not find the way to unbrick the OPO. In fact I wasn't even the very first one to do it. It was a collective effort of few people who tried many different approaches and ideas, and I eventually documented these steps for others to follow. Being said, the following people deserve credit as well: @os_man, @rezor92, @Mnt-XDA. If I am forgetting other significant names and efforts, I apologize.
***CAUTION***
The following instructions are for hardware bricked devices ONLY and will not work on soft bricked devices. To determine whether your device is soft or hard bricked, click the button below:
Hardware brick
A hardware bricked OPO has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition. The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OPO should be detected as QHSUSB_BULK USB. You might have a bricked OPO as a result of flashing a kernel meant for a different device (or a ROM meant for another device that included a kernel), tinkering with the boot logo or bootloader, or your attempt of unlocking the bootloader resulted in corrupting the boot partition.
Software brick
Please do not attempt to use these directions if your phone is soft bricked. A software bricked OPO is one that might be stuck in a bootloop, but has a working bootloader, recovery partition, fastboot, or adb. If you press the power button and images appear on the screen and you are able to enter fastboot mode (Power + VolUP) or recovery (Power + VolDOWN) then your device is soft bricked. This thread does not encompass soft brick recovery, the instructions below do not apply and will not work on these phones. Consult other threads for help on soft bricked devices.
If based on the above explanation of differences between soft and hard bricks you determined your device is hard bricked, here's what you will need to do...
1:
Download Color.zip from https://goo.gl/iDby26
After downloading, unzip the archive on your computer.
2:
Next, you need proper Windows drivers. There are architectural differences between Windows XP and Windows 7/8, so follow the directions below that pertain to you. One quick note about the drivers: the installation and process is very simple and straightforward on Windows XP (I also tested successfully on Windows 2003), but proves to be quite a challenge when running on Windows 7 or 8. Over and over people report issues when attempting the unbrick procedure on Windows 7/8, some have more luck than others. Being said, if you have access to a Windows XP computer, I highly recommend that you use that. If you have no choice but to use a Windows 7 or 8 computer and have problems, please share them here and read others' experiences.
So first, by now you probably tried a few different things to fix your phone and you've already installed some drivers, including Qualcomm USB drivers for 9006 and 9008. My best advice is to uninstall the drivers you tried so far and use the ones listed below. Go to Device Manager, right click on the bricked USB device (QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008) and go to Properties, click on Driver, then select Uninstall. Check the box to remove driver files, if prompted. Then:
2a:
Windows XP users:
You are in luck, driver installation is straightforward. Go to the extracted Color.zip folder and find Driver.iso. Extract Driver.iso. Inside the extracted folder find Setup.exe. Run Setup.exe to install the drivers. The installer is Chinese, but all you need to do is click through the prompts.
2b:
Windows 7 and Windows 8:
These operating systems block unsigned driver installations by default. Follow these steps (thanks @nag4pl for testing these):
Download and extract these Qualcomm 2012 drivers: https://goo.gl/cIKnFZ. Connect your bricked phone and let Windows do its thing.
Now something very essential you need to do here is to execute two commands to allow you to install unsigned drivers for QHUSB_BULK. Click on Start Menu > Type cmd.exe > Right Click and Run as Administrator.
In the CMD window type in the following commands (hit enter after each):
Code:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
Code:
bcdedit.exe -set TESTSIGNING ON
After both the commands should run successfully, restart your computer.
You can now proceed to install unsigned drivers from the file you downloaded. Open Device Manager, you should be seeing ugly yellow warning under other devices for QHUSB_BULK. Right click on the name and select Update Driver Software > Browse my Computer for driver software. For driver software location provide the path where you have extracted Qualcomm 2012 drivers you downloaded and make sure 'Include Subfolders' is checked. Proceed through all the installation prompts ignoring any warnings.
3:
Once you have the drivers straightened out, connect your bricked phone to the computer and start it up by holding VolUp + Power to about 10 seconds, and let the computer do its thing. Don't install drivers if they are not installed by itself. Instead launch Msm8974DownloadTool.exe as Administrator (right click on Msm8974DownloadTool.exe and select "Run as administrator") from the extracted Color.zip archive. It will scan all the COM ports and find the phone. That's the one line that looks different in the list. The list is just a list of your com ports and devices. If you unplug the phone and move it to another port, it will show your bricked phone on a different line.
Clicking on "Enum" just rescans the busses. Clicking the big square button in upper right corner scans the phone and reports what's good and what's not. It takes a minute for the scan to finish.
If you don't see your phone in the list of com devices, try unplugging/plugging in your phone a couple times, and rebooting it with VolUP + Power (hold 10 seconds). You will see it in Device Manager as well.
Once you see the phone in the list, click Start. You should see the programs start writing different files to the phone. Each time it writes a file you'll see a progress bar. Once you see this process happening, smile, you know you will be good to go... After all files are written, the com line with your device will turn green. You're good, unplug and reboot your phone. It will boot to ColorOS, the Chinese OS that comes on OPO.
4:
Optional Steps:
Your phone is no longer bricked. You now have a few options to get back to stock. The easiest way is to use a toolkit from http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418, or you can flash an image manually by following directions from: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541. Download the proper image zip and after extracting it, run the following commands in fastboot mode:
Code:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
Make sure you have the proper image. I accidentally installed the 16GB version on my 64GB OPO first time and obviously didn't get 64GB of space.
That's about it. I think if people are still having problems then it's likely due to drivers, or Windows 7/8 issue.
Good luck! Share your experience here and let me know if I can improve this thread.
Please click the Thanks button if you found the above guide useful.
Click to expand...
Click to collapse
I saw this guide but its for one plus one.
Its any way to do this guide for nexus 5?
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732/page40
This is the link
Can you boot into fastboot mode? If you can, connect the phone, run the fast boot command "fastboot oem unlock".
audit13 said:
Can you boot into fastboot mode? If you can, connect the phone, run the fast boot command "fastboot oem unlock".
Click to expand...
Click to collapse
I ran this command but it still locked. I think because its need to reboot after run the unlock command, but I cant reboot because I have no rom.
After you type "fastboot oem unlock", you should get a prompt on the phone to say "yes".
audit13 said:
After you type "fastboot oem unlock", you should get a prompt on the phone to say "yes".
Click to expand...
Click to collapse
Right. I did it and its looks like its unlocked, but after reboot to bootloader it was back seems locked.
If the bootloader relocks itself on reboot, the Emmc chip is damaged and needs to be replaced.
audit13 said:
If the bootloader relocks itself on reboot, the Emmc chip is damaged and needs to be replaced.
Click to expand...
Click to collapse
How much does a repair for switch emmc chip?
If I buy this chip, can I switch it alone?
It's the memory chip on the motherboard that needs to be replaced. Unless you have specialized soldering equipment, the best solution would be to find a nexus 5 with a smashed screen and working internal components.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the "Deuces" script or to flash a new system image.
I have tried all of the basic stuff to get to my device to be recognized. I downloaded and installed the latest ADB & Fastboot and I have tried different cables and USB ports and still have no luck. I'm really worried and not sure what to do if I cannot get my device to accept fastboot commands so I can recover.
Please let me know if you have any ideas that may help me.
Jason
EDIT:
I still have no idea what I did, but I decided to use the Skipsoft Tool to see if it would work. Lucky for me it did and I was able to restore the factory image. Sorry for the fire-drill, I should have tried this before I posted. Thank you for the replies!!
Grab the latest Google platform tools and USB drivers. When your device is plugged in, do you see any unknown devices in your device manager? Or anything that looks like it could be your phone?
jascolli said:
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the "Deuces" script or to flash a new system image.
I have tried all of the basic stuff to get to my device to be recognized. I downloaded and installed the latest ADB & Fastboot and I have tried different cables and USB ports and still have no luck. I'm really worried and not sure what to do if I cannot get my device to accept fastboot commands so I can recover.
Please let me know if you have any ideas that may help me.
Jason
Click to expand...
Click to collapse
I've seen that before.
When you select reboot bootloader does that message go away?
Try it without the cable plugged in does it go away then?
I just want to know if you can actually get that message to go away or not at this point.
Also can you link the tools you are downloading
jascolli said:
I still have no idea what I did, but I decided to use the Skipsoft Tool to see if it would work. Lucky for me it did and I was able to restore the factory image. Sorry for the fire-drill, I should have tried this before I posted. Thank you for the replies!!
Click to expand...
Click to collapse
For future learning, I'd recommend you familiarize yourself with how to do this without toolkits. A toolkit is nice, but it really helps to understand what the toolkit is doing so that if you have an issue you know what to do next.
Telperion said:
For future learning, I'd recommend you familiarize yourself with how to do this without toolkits. A toolkit is nice, but it really helps to understand what the toolkit is doing so that if you have an issue you know what to do next.
Click to expand...
Click to collapse
Solid advice, thank you.
I did this same thing and solved it the same way. I think things just get funky and the tool you mentioned to fix it.
nolimit78 said:
I did this same thing and solved it the same way. I think things just get funky and the tool you mentioned to fix it.
Click to expand...
Click to collapse
Yeah I'm baffled. I could not for the life of me get fastboot to work. That Skipsoft tool is pretty impressive.
HELP!!!!
I have same problem, so which functions you use to fix it????
jascolli said:
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the "Deuces" script or to flash a new system image.
I have tried all of the basic stuff to get to my device to be recognized. I downloaded and installed the latest ADB & Fastboot and I have tried different cables and USB ports and still have no luck. I'm really worried and not sure what to do if I cannot get my device to accept fastboot commands so I can recover.
Please let me know if you have any ideas that may help me.
Jason
EDIT:
I still have no idea what I did, but I decided to use the Skipsoft Tool to see if it would work. Lucky for me it did and I was able to restore the factory image. Sorry for the fire-drill, I should have tried this before I posted. Thank you for the replies!!
Click to expand...
Click to collapse
Same thing happened to me. I need help. Please tell me how you unbricked your phone
same problem
i have the same problem already download skipsoft program but dont have results can you tell me the steps what you do please
---------- Post added at 07:48 AM ---------- Previous post was at 07:43 AM ----------
yuva_cool said:
Same thing happened to me. I need help. Please tell me how you unbricked your phone
Click to expand...
Click to collapse
do you already unbricked your phone?
my pixel still cant be detected by that toolkit, can u list the step by step procedure what u did to unbrick the device?
I was having the exact same issue as OP. I wound up fixing it by entering fastboot and making it display barcodes until the battery died. Then I put a rubber band over the power button so the red led would blink (I wanted to completely drain the battery). When it stopped blinking, I hooked my dead phone up to my PC via a USB 3 port and held Power + vol down to boot into fastboot (the battery was still too low for the phone to boot normally -- it would just show the battery icon). Surprisingly, my PC recognized my phone (made the little USB sound) and I was able to fastboot flash-all the newest factory image on it!! No toolkits required!
I'm so happy because this was a last ditch effort before I sent my original phone back to google and would have to live with the RMA they sent me which could not be bootloader unlocked (this is a whole other issue!)
I hope this helps!
EDIT: Info I provided in a PM
Unfortunately I didn't take any photos of the process... I didn't want to push my luck and things are working now. But The photo I've attached was exactly what I was seeing except I was on the December update (Now I'm on the January update) ... and:
UFS: 128 GB Hynix
DRAM: 4096MB Micron LPDDR4
Device State: unlocked (I had been unlocked since April 2018)
Until I had entirely drained my battery, I couldn't do anything. Download mode and recovery mode were impossible to access. I forgot the specific error, but it was the same as a lot of other people who have been having this problem.
The only thing I could do was to restart bootloader, which removed the error message until I tried to do anything. I couldn't boot at all or do anything conducive to fixing my phone until I drained the battery entirely. I couldn't get any PCs to even acknowledge the existance of my phone until after the battery was drained.
Keep in mind, I NEVER got my RMA phone to work. I was only able to fix my original NEW phone that I had purchased directly from google.
Until I had entirely drained my battery, I couldn't do anything. Download mode and recovery mode were impossible to access. I forgot the specific error, but it was the same as a lot of other people who have been having this problem.
The only thing I could do was to restart bootloader, which removed the error message until I tried to do anything. I couldn't boot at all or do anything conducive to fixing my phone until I drained the battery entirely. I couldn't get any PCs to even acknowledge the existance of my phone until after the battery was drained.
Click to expand...
Click to collapse
This is the correct resolution to this issue.
I had the same issue, no usb in bootloader. I drained the phone and rebooted into the Bootloader flash A and B side bootloader the Aug 2018 (previously working for me) and A and B side Radio, as well as the System image. After that everything booted fine.
Attempted to install the January update the same way and it worked as well.
Seems like they messed up A and B side flashing
My steps::: For Lurkers having this issue.
1. Drain battery DEAD!
2. Boot Bootloader (Vol Down + Power)
3. fastboot flash bootloader bootloader-walleye-mw8998-002.0073.02.img (or whatever image)
3. fastboot set_active b (opposite of the one on screen)
4. fastboot reboot-bootloader
5. fastboot flash bootloader bootloader-walleye-mw8998-002.0073.02.img (or whatever image) (Again)
6. fastboot reboot-bootloader
7. fastboot flash radio radio-walleye-g8998-00253-1809191716.img (or whatever image)
8. fastboot set_active a (opposite of the one on screen)
9. fastboot reboot-bootloader
10. fastboot flash radio radio-walleye-g8998-00253-1809191716.img (or whatever image)
11. fastboot reboot-bootloader
12. fastboot update image-walleye-pq1a.190105.004.zip (or whatever image)
Phone boots properly, and is updated.
thedude9821 said:
I was having the exact same issue as OP. I wound up fixing it by entering fastboot and making it display barcodes until the battery died. Then I put a rubber band over the power button so the red led would blink (I wanted to completely drain the battery). When it stopped blinking, I hooked my dead phone up to my PC via a USB 3 port and held Power + vol down to boot into fastboot (the battery was still too low for the phone to boot normally -- it would just show the battery icon). Surprisingly, my PC recognized my phone (made the little USB sound) and I was able to fastboot flash-all the newest factory image on it!! No toolkits required!
I'm so happy because this was a last ditch effort before I sent my original phone back to google and would have to live with the RMA they sent me which could not be bootloader unlocked (this is a whole other issue!)
I hope this helps!
EDIT: Info I provided in a PM
Unfortunately I didn't take any photos of the process... I didn't want to push my luck and things are working now. But The photo I've attached was exactly what I was seeing except I was on the December update (Now I'm on the January update) ... and:
UFS: 128 GB Hynix
DRAM: 4096MB Micron LPDDR4
Device State: unlocked (I had been unlocked since April 2018)
Until I had entirely drained my battery, I couldn't do anything. Download mode and recovery mode were impossible to access. I forgot the specific error, but it was the same as a lot of other people who have been having this problem.
The only thing I could do was to restart bootloader, which removed the error message until I tried to do anything. I couldn't boot at all or do anything conducive to fixing my phone until I drained the battery entirely. I couldn't get any PCs to even acknowledge the existance of my phone until after the battery was drained.
Keep in mind, I NEVER got my RMA phone to work. I was only able to fix my original NEW phone that I had purchased directly from google.
Click to expand...
Click to collapse
omg after months of figuring it out ,and almost opt for warranty,finally my pixel is aliveeeee, thanks alot for the fix im so glad.. and whats more important for me is the data is still intact! i cant thank you enough.. google messed up december update pretty bad.
I just received my 4th RMA and the bootloader wasn't able to unlock. So to my surprise Google is giving me a full refund? I purchased my Pixel 2 back in Nov 2017 ?
Dajax2 said:
3. fastboot flash bootloader bootloader-walleye-mw8998-002.0073.02.img (or whatever image)
Click to expand...
Click to collapse
@Dajax2 Super new to this and it may be a total waste since my bootloader screen says "Device State: locked" but in trying to flash or even sideload ota, the command returns "error: cannot load (file location/name): no such file or directory found". Again, total noob and I don't even know if I'm supposed to unzip the folder or not but have tried both ways with the same error.
It returns the serial number for fastboot devices but nothing for adb devices. I obviously didn't have OEM or USB debugging enabled prior. Hoping I can at least get in to retrieve data before giving up all hope :/
Solved. Enter barcode mode. In this screen, check for devices from adb or fastboot. It should be there. You are now able to switch slots and do all the fastboot things.
Great workaround that I would never have thought - good info here, thanks everyone!
dianea said:
Solved. Enter barcode mode. In this screen, check for devices from adb or fastboot. It should be there. You are now able to switch slots and do all the fastboot things.
Click to expand...
Click to collapse
Edit - My phone wasn't detected when on the barcode screen, just like from the main bootloader screen.
HOWEVER... to my surprise.. the above method of draining the battery completely to 0% actually worked. I'm a little dumbfounded why this allowed the bootloader to connect via fastboot again, but it did. I was able to flash the latest factory image (without wipe) and boot back up like nothing ever happened. Thank you so much for the tip. I passed this along to Google support and they also said they appreciate the troubleshooting and asked me to just send back the replacement phone with the RMA package/label.
---------- Post added at 06:36 PM ---------- Previous post was at 06:18 PM ----------
thedude9821 said:
Keep in mind, I NEVER got my RMA phone to work. I was only able to fix my original NEW phone that I had purchased directly from google.
Click to expand...
Click to collapse
Did they accept the RMA phone back and remove the temp auth on your card?
thedude9821 said:
I was having the exact same issue as OP. I wound up fixing it by entering fastboot and making it display barcodes until the battery died. Then I put a rubber band over the power button so the red led would blink (I wanted to completely drain the battery). When it stopped blinking, I hooked my dead phone up to my PC via a USB 3 port and held Power + vol down to boot into fastboot (the battery was still too low for the phone to boot normally -- it would just show the battery icon). Surprisingly, my PC recognized my phone (made the little USB sound) and I was able to fastboot flash-all the newest factory image on it!! No toolkits required!
I'm so happy because this was a last ditch effort before I sent my original phone back to google and would have to live with the RMA they sent me which could not be bootloader unlocked (this is a whole other issue!)
I hope this helps!
EDIT: Info I provided in a PM
Unfortunately I didn't take any photos of the process... I didn't want to push my luck and things are working now. But The photo I've attached was exactly what I was seeing except I was on the December update (Now I'm on the January update) ... and:
UFS: 128 GB Hynix
DRAM: 4096MB Micron LPDDR4
Device State: unlocked (I had been unlocked since April 2018)
Until I had entirely drained my battery, I couldn't do anything. Download mode and recovery mode were impossible to access. I forgot the specific error, but it was the same as a lot of other people who have been having this problem.
The only thing I could do was to restart bootloader, which removed the error message until I tried to do anything. I couldn't boot at all or do anything conducive to fixing my phone until I drained the battery entirely. I couldn't get any PCs to even acknowledge the existance of my phone until after the battery was drained.
Keep in mind, I NEVER got my RMA phone to work. I was only able to fix my original NEW phone that I had purchased directly from google.
Click to expand...
Click to collapse
Dajax2 said:
This is the correct resolution to this issue.
I had the same issue, no usb in bootloader. I drained the phone and rebooted into the Bootloader flash A and B side bootloader the Aug 2018 (previously working for me) and A and B side Radio, as well as the System image. After that everything booted fine.
Attempted to install the January update the same way and it worked as well.
Seems like they messed up A and B side flashing
My steps::: For Lurkers having this issue.
1. Drain battery DEAD!
2. Boot Bootloader (Vol Down + Power)
3. fastboot flash bootloader bootloader-walleye-mw8998-002.0073.02.img (or whatever image)
3. fastboot set_active b (opposite of the one on screen)
4. fastboot reboot-bootloader
5. fastboot flash bootloader bootloader-walleye-mw8998-002.0073.02.img (or whatever image) (Again)
6. fastboot reboot-bootloader
7. fastboot flash radio radio-walleye-g8998-00253-1809191716.img (or whatever image)
8. fastboot set_active a (opposite of the one on screen)
9. fastboot reboot-bootloader
10. fastboot flash radio radio-walleye-g8998-00253-1809191716.img (or whatever image)
11. fastboot reboot-bootloader
12. fastboot update image-walleye-pq1a.190105.004.zip (or whatever image)
Phone boots properly, and is updated.
Click to expand...
Click to collapse
Gifted both of you Ad-Free for this.
You saved me $300 and the annoyance of having to wait for shipping for either RMA or another phone on Swappa.