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.
Related
My XOOM is bricked and show RSD Mode 2 when power on, I can go into the fastboot mode by press VOL UP + Power button, and plan to do fastboot process to restore the system.
However, my problem is the Computer cannot detect XOOM, when I input "fastboot oem unlock", then the command stopped at a "Waiting for device" reply, so I cannot go to next step.
I have installed all of the needed software I see in this forum. Moto USB driver, Android SDK, Java, fastboot.
I have tried the RSDlite 5.0 but with the same reason, the RSDlite cannot detect device so it cannot work out.
anyone with the same problem and how to solve it? Do I need to send back it to Motorola for restore?
Thanks a lot for your help, It is too bad to stay with a bricked XOOM.
Xoom stuck in RSD mode 2
I'm having the same issue. I'm at the boot screen with the Moto symbol and I have an error in the top right that says "Failed image SOS 0x0002" and below that "Starting RSD mode 2". My computer does not see my xoom. I've tried other links to this problem but they are not the same. They all mention RSD mode 3. Damn my stupidity . Someone please help
Unbrick RSD Mode 2
I don't know what version xoom you are using, or under what circumstances you bricked your xoom under, but I managed to get mine (3g, USA) out of RSD 2 this way after it wouldn't boot coming out of a botched automated unroot/relock procedure. You may want to try this to get back to stock and working again, and then redo all the rooting and tweaks. I am going to go on the notion that you use windows (I use windows 7 64bit, but the steps should be the same or similar for other versions), have android sdk installed, and know what fastboot is.
... but first a few disclaimers!
1) If everything is fine now, disregard this reply!
2) I am in no way an expert in unbricking xooms, this is just how I figured it out for my situation.
3) Again, this is how I unbricked MY xoom, it may or may not work for you. If something here doesn't work for you, I really can't help.
4) I am not as big of a douche bag as I sound like in the last couple of disclaimers. If you are stuck and there is something I forgot to mention, I'll try to help.
4) You are probably having the same problem as someone else. As much as I hate to say it... GOOGLE IT! Just make sure you have all the error codes and include how you bricked your device. Horrible example: " R2D2 mode after I tried to turn my xoom into an autonomous killing machine by feeding my device crepes error code xx42" Bad example, yet it's very (odd) specific.
5) Don't be offended if I go into details that seem way below you. Someone else may need to read this, and may not understand everything you or I do. I try to break everything down as much as I can. Also, if I didn't go far enough into detail, let me know.
6) I inserted two 4's to see if you are really taking the time to read the entire post so the first 4 may not be true!
7) Once you get fastboot working, and the bootloader unlocked, the brick may be undone. I have you get the stock images just in case. Following the last part of the post will wipe your data.
Now back to our regularly scheduled programming...
1) Download the correct stock system software (wifi/3g) from motodev.
motorola.com/products/software/?utm_campaign=xoomsoftware&utm_medium=motorolacom&utm_source=supportforums&utm_term=unlockboard&pubid=987654
You have to register on the site. I would attach the files, but I agreed to a nice end user agreement saying I will not redistribute them. Also, I can't post links yet since I am still new so the beginning of the url is missing. There are posts in the xoom development forum that link to the file.
2) Unzip the contents to the folder where fastboot is located. Usually located in C:/program files/android/android-sdk/tools, or C:/program files (x86)/android/android-sdk/tools if you use a 64bit version of windows.
3) Power on the xoom and get into fastboot by holding the volume down button as soon the moto logo shows. I noticed it took a little while longer than usual for fastboot to show up. I noticed in the original post that the user said Volume up + Power. That is how you hard reboot... or do a dragon punch...I forget.
4) Once the device shows fastboot is running, Open a command prompt ( start, all programs, accessories, command prompt, or type cmd in the search bar ). Next type/copy these commands minus any comments marked by "<---". Note that every new line is a new command:
ON THE PC:
cd c:/program files/android/android-sdk/tools <---May be different depending upon what version of windows you are using. Replace 'programs files' with 'program files (x64)' if using 64 bit windows. If all else fails, type cd then copy one of the paths from step 2.
fastboot oem unlock <---This MAY solve your problem right here
should say check your device for instruction. On the xoom, hit volume down, then volume up, voulme down again, and volume up again to confirm the unlock.
When I did that my xoom rebooted, and I was back in business; however, if the unlock worked and you are still not able to boot, let's get back to stock. Get the xoom back into fastboot again by holding the volume down button while it starts.
ON THE PC:
You should still be in the same command prompt from earlier.
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot oem lock
This will wipe your xoom completely, but your nice shiny paperweight should be less paperweight like. I do the relock for good measure just because I think I left it unlocked, then I received an OTA update, and got good RSD Mode 2 again for some reason. If you want, try it without the fastboot oem lock command in case you want to get right back into rooting, flashing recoveries, etc... Well, hope all this helped. Again if clarification is needed, let me know and I will try to help. Hope this works. Take it easy!
zanzebar said:
I'm having the same issue. I'm at the boot screen with the Moto symbol and I have an error in the top right that says "Failed image SOS 0x0002" and below that "Starting RSD mode 2". My computer does not see my xoom. I've tried other links to this problem but they are not the same. They all mention RSD mode 3. Damn my stupidity . Someone please help
Click to expand...
Click to collapse
I have the same issue. Looks like I now own a brick!
zanzebar said:
I'm having the same issue. I'm at the boot screen with the Moto symbol and I have an error in the top right that says "Failed image SOS 0x0002" and below that "Starting RSD mode 2". My computer does not see my xoom. I've tried other links to this problem but they are not the same. They all mention RSD mode 3. Damn my stupidity . Someone please help
Click to expand...
Click to collapse
1) Turn the xoom on and leave it plugged into USB.
2) When it says Starting RSD Mode 2, type the following in your command prompt in windows "fastboot oem unlock"
*Make sure you are typing these commands within the directory where your fastboot and .img's are located. ( I dropped mine in C:\Android-sdk\platform-tools\
*The Xoom will not respond initially and your command prompt will say "waiting for device".
3) Hold the power button and volume up to reset the xoom. The fastboot command should intercept the xoom booting and take you to the unlock prompt again. Follow the on screen instruction.
*This will wipe the device again, which I'm assuming you did when you locked
it with a custom kernel (boot.img)
After it is completed, type "fastboot reboot" in windows command prompt or just reboot however you can.
This doesn't work!
i have two motorola xoom, one of them have the failed image sos 0x0002 starting rs mode 2.
When i plug in the bricked motorola xoom nothing respons in the computer. i have the fastboot on with the waiting for device activated with fastboot oem unlock and RSD Lite v4.9 or 5.0 doesn't detect it too..
What can we do? i'm from spain and i bought the tablet in new york. Can i send it to the garanty?
The only way to do this is as follows:
Download rsdlite 4.9 or earlier only and install it on your computer.
Downlaod the latest moto drivers and install them.
Search for and download the stock SBF file for your Xoom wifi or 3g.
Get your Xoom to the rsd mode 2 screen and plug it in your computer
Use rsdlite to push the SBF file to the Xoom.
It will probably say it failed after a long wait. Its OK. Just restart your Xoom and your back to factory.
Good luck
csseale said:
The only way to do this is as follows:
Download rsdlite 4.9 or earlier only and install it on your computer.
Downlaod the latest moto drivers and install them.
Search for and download the stock SBF file for your Xoom wifi or 3g.
Get your Xoom to the rsd mode 2 screen and plug it in your computer
Use rsdlite to push the SBF file to the Xoom.
It will probably say it failed after a long wait. Its OK. Just restart your Xoom and your back to factory.
Good luck
Click to expand...
Click to collapse
i believe there is no SBF file for wifi xoom right now.
So I haven't had a chance to try anything you all have said since I've been at work all night. I have to agree with the last post though. I have looked everywhere and cannot find the.sbf I hope it leaks soon though so I dont have to deal with the shame of sending it to moto.
I still can't get the xoom to receive commands. I need that .sbf. I'll definitely be checking every minute for the wifi version leak.
The above means does not work.
I end up with a RSD re-enumaration failed error.
I'm on wifi xoom and can make it into "Starting Fastboot protocol support" but when i attempt to flash any of the images posted above or do a fastboot oem unlock I simply get <waiting for device> and nothing responds. Help?
Your Xoom is completely Bricked
At this point there is nothing you can do. You can A. wait patiently for .SBF for wifi only xoom or B. explain to motorola what happened and if it is under warranty they will replace or repair your xoom in 1 week.
Mayday
I am having the same problem, will someone be kind enough to find get the sbf out... aint android open source?
BlueEditionE6 said:
I am having the same problem, will someone be kind enough to find get the sbf out... aint android open source?
Click to expand...
Click to collapse
Android is open source but google is not releasing the source code for honeycomb yet.not exactly the same thing. You might be ****ed...
rockhumper said:
Android is open source but google is not releasing the source code for honeycomb yet.not exactly the same thing. You might be ****ed...
Click to expand...
Click to collapse
As long as you didn't reformat your internal sdcard you're probably not really bricked. It's not impossible but is really hard to brick the Xoom. I would suggest you go to the IRC #[email protected] freenode and see if any of those guys can help you. If anyone can, they can.
Good luck!
Greetings! First of all, I would like to thank anyone who takes the time to help me diagnose and resolve this issues, let alone anyone who takes the time to read this thread.
I've been having issues with my Xoom (ICS 4.0.0) for about 3 weeks now.
A brief history of the issue's occurrence:
-I unrooted the device and returned it to stock.
-Everything was fine and dandy until one day it spontaneously said something along the lines of 'Android is upgrading..', and then performed a reset.
-Since resetting, it bootloops.
The device only turns on when plugged into a charger and hard reset.
The device only turns off when allowed to boot loop for minutes and then hard reset (it simply does not reset, and just turns off).
I'm not the most technically-savvy person with android devices but here are some things I've done/noted.
When trying to use adb commands, it does not recognize the device or properly issue commands.
I've tried wiping data/clearing cache to no avail.
EDIT: I've tried fastbooting, but the bootloader will not unlock. When trying to unlock, it simply resets and then acts as though it was never unlocked.
I have no idea how to return it to a stock image. All I know is that I have a micro-SD and some spare time.
Could anyone help me understand what exactly is going on with my Xoom?
If I can provide you with any more information, please let me know.
Thanks again. (=
If it was stock and spontaneously upgraded it sounds like a bad OTA upgrade. I've been rooted from the start so never have taken an OTA upgrade...don't you need to accept it or can it just upgrade on it's own?
Anyway, can you get it into fastboot mode?
Volume up and power, then at dual core screen, press volume down...if you see something like "entering fastboot mode" you're not bricked. You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
If you haven't done so, just google 'recovering Xoom using fastboot' and you should get some good information.
Good luck!
Remember to grab the MZ604 files if you have the Wifi only version of the Xoom.
http://developer.motorola.com/products/software/ <------ Grab the files here. The files are for the US version of the Wifi Xoom only.
Instructions to return it to stock
1) First you need the Moto Drivers - Read this thread to START you - http://forum.xda-developers.com/showthread.php?t=981578
Should have these drivers installed if you have rooted your Xoom before.
2) Make sure you have the latest SDK - adb and fastboot should be in /platform-tools -
http://developer.android.com/sdk/index.html
Should have the android SDK if you have rooted your Xoom before.
3) Place all the downloaded stock image files into the SDK Tools folder.
4) If you are booting up from scratch, you can get the Xoom in fastboot mode by doing the following. Use command prompt to perform the rest of the steps
Hold VolDown and Power button will boot unit for fastboot mode
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
If you Xoom is booted up already follow the commands below using command prompt to perform the steps
adb reboot bootloader <---- reboots the Xoom into fastboot mode.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
As Always If This Was Helpful Hit the Thanks!
Yeah, what Mjamocha said...
okantomi said:
Yeah, what Mjamocha said...
Click to expand...
Click to collapse
LOL Thanks.
okantomi said:
Anyway, can you get it into fastboot mode?
Click to expand...
Click to collapse
Yes, I can. But so far nothing has been successful in terms of fastboot commands.
okantomi said:
You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
Click to expand...
Click to collapse
When I try to execute fastboot commands such as 'fastboot flash boot boot.img'.. it says the following:
Device still locked. Device must be unlocked first. Failed to process command error(0x8)
Whenever I try to unlock the bootloader, it appears to be successful at first and then the device reboots. But it just reboots to a bootloop, and the bootloader still says its locked. Perhaps I made a mistake in communication. The bootloader is currently locked and will not unlock, as just described.
When I try to unlock it and it reboots, even if I access the fastboot menu right away, it still says the device is still locked.
Thoughts?
Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.
slacka-vt said:
Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.
Click to expand...
Click to collapse
Yes, I can get into android recovery. However, within a second of switching into recovery mode, the robot falls down and there appears to be a red triangle caution sign containing an exclamation point.
When trying to do a factory reset, it says all data is wiped (as normal). Upon rebooting, it continues to bootloop. So essentially the factory reset and cache clear options in the Android Recovery menu do not produce the expected results.
Pretty odd. I didn't mess with the Xoom at all prior to this issue.
Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.
slacka-vt said:
Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.
Click to expand...
Click to collapse
Yeah, just tried it to no avail. Thanks so much for your help anyway. (=
I'm not sure what to do now.
I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.
slacka-vt said:
I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.
Click to expand...
Click to collapse
I hear ya. I've tried 2 different cords and 3 different computers. I'm using a Mac (10.6.8) right now, but have used 2 PCs (Vista + 7).
Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?
slacka-vt said:
Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?
Click to expand...
Click to collapse
I got the 'device still locked' error. Weird, huh?
How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.
slacka-vt said:
How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.
Click to expand...
Click to collapse
Yeah I tried that. Won't lock or unlock successfully. Locking produces no difference, and unlocking produces the same 'device still locked' error. This is getting out of hand! Thanks so much for your advice. You think I should open it up?
I hate to be so persistently annoying about this, but could anyone possibly suggest a method of working around the locked bootloader?
Is there anything I can do with an SD card to remedy the device's stubborn foolery?
I think you should give it a try, I have bricked my xoom a few times and have always been able to flash the stock imagine to recover. You really have nothing to lose by pulling the battery pin just be careful.
Sent from my Xoom using xda premium
I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?
cherlamperter said:
I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?
Click to expand...
Click to collapse
I have looking for a utube how to guide but no luck, I just might make one for you so you will know what to expect. Give me a few and I will get back to ya.
Sent from my Xoom using xda premium
Hey guys, how are you?
Well, I wished to root my Moto G, so I (tryed?) to unlock the bootloader. Alright, done it, but then I ran into some trouble...
After the booting up, everything started forceclosing and since then, when I try to boot it, I get a black screen after the Motorola logo.
Now, I am really really worried about my phone. I got it a month ago. I'm so afraid I really f****d up my phone right now that my hands are shaking.
I'm new to Android, so sorry if the solution is pretty obvious. And if it's not, could explain it very carefully to me? I don't know what to do.
My best wishes to you, guys.
I'm assuming you used superboot if so that would happen.
The logo sort of blured out right just press volume down and power and it would work
Or did this happen when you were just trying to unlock bootloader?
TomGlass1 said:
I'm assuming you used superboot if so that would happen.
The logo sort of blured out right just press volume down and power and it would work
Or did this happen when you were just trying to unlock bootloader?
Click to expand...
Click to collapse
Yeah, that happenned when I was trying to unlcok bootloader.
And well, my computer now doesn't even recognizes my phone.
EDIT: It appears as "Fastboot falcon S" in the Device Manager. Tried installing some drivers I found in the Internet, but it didn't work.
Explain exactly what happened please. Was the unlock successful and did you just bootup normally after or did u do anything else in fastboot mode? Why are you trying to install fastboot drivers again, as you already wouldve had them to unlock the bootloader. Did you try installing recovery or some root img from fastboot? You said its forceclosing, but it isnt starting at all now?
Some things you can do right now (if your bootloader is unlocked) is to flash a recovery (twrp,cwm) through fastboot and if you think most system files (or settings) are beyond repair, flash your firmware version though fastboot. Will point you to the guides for them, but post more info if you want help.
hemanthmahesh said:
Explain exactly what happened please. Was the unlock successful and did you just bootup normally after or did u do anything else in fastboot mode? Why are you trying to install fastboot drivers again, as you already wouldve had them to unlock the bootloader. Did you try installing recovery or some root img from fastboot? You said its forceclosing, but it isnt starting at all now?
Some things you can do right now (if your bootloader is unlocked) is to flash a recovery (twrp,cwm) through fastboot and if you think most system files (or settings) are beyond repair, flash your firmware version though fastboot. Will point you to the guides for them, but post more info if you want help.
Click to expand...
Click to collapse
Alright, just after I unlocked, when I was booting, I got a message saying that "xxxx has stopped working/failed to initialize/something like that". And then, when I rebooted, I got the usual message of the "bootlocker has been unlocked". After that, the Motorola logo started animating, but then I just got a black screen. I can't turn it off and the battery just got depleted (I'm charging right now).
When I try to connect it in my computer, the PC recognizes it as "MTP Device" or "Fastboot falcon S" when fastbooted. I can't install any drivers and the Motorola Device Manager doesn't recognizes it either.
Well, if there is some missing information, just ask me. I tried to describe my problem the best I could. Anyway, sorry for my bad English and thanks in advance for any effort trying to discover what's wrong.
Motorola Device Manager isn't helpful in this state as it doesn't handle things in fastboot. You already have all the required drivers (fastboot falcon S is the right driver afaik, falcon being motog codename) for flashing your stock firmware.
1. First, you can try the "Factory" option in bootloader (the third one, use volume down to move selector, volume up to select), though this might not really work for major issues.
2. When in fastboot mode, use "fastboot getvar all" to get the firmware details if you already didn't know about it.
3. Otherwise if yours is a standard gsm (non dualsim/non cdma), just download Blur_Version.174.44.9.falcon_umts.Retail.en.GB (UK stock for gsm, 4.4.2)
Download the mfastboot files to use rather than fastboot for flashing. You might need to modify your commands a bit for various firmwares.
http://forum.xda-developers.com/showthread.php?p=47820707 (refer this thread for flashing your stock firmware)
All the firmwares are in either of the links below (all around 400mb):
http://sbf.droid-developers.org/phone.php?device=14
(or)
http://www.filefactory.com/folder/c6cdedc45a775d27
I still don't get why many ppl are getting these errors after unlocking, very bad unlock method of moto if so ( I didnt get any such issues though).
When I use the "fastboot getvar all" command, it says "waiting for device". The phone is already connected, but the Moto G doesn't recognizes it's connected either.
I'm getting more and more afraid I really hardbricked it.
http://www.mymotocast.com/download/MDM?platform=windows
Tried installing these drivers? Your fastboot doesn't seem to be setup properly. How did you unlock without a working fastboot driver? You are trying that command in bootloader mode right?
Already installed it from the start. The message I got is always this:
"There aren't any updates for your device at the moment
Current Version: N/A"
My fastboot: Doesn't matter the operation I do, I always get this <waiting for device> and the phone is already connected into the computer. And the phone doesn't recognizes it is connected too.
And greeeeat news: my phone now doesn't charges either. I get stuck on a screen with a battery logo and 0%, when connected to the charger. Still, I still can access the fastboot mode. Well, am I lucky or not?
I'm pretty confused with this. How exactly did you unlock without a working fastboot (no waiting for device issue)? Did you change your pc drivers after unlock or trying this from a different pc? When you say "phone doesn't recognizes it is connected" you mean it says "Connect USB data cable" below "Device is UNLOCKED"? If so, maybe try another usb port cause it should normally say "Transfer Mode: USB Connected" regardless of proper drivers.
Your phone will chrarge no matter what though, no worry about that. It needs to say "Battery OK (Charging)" when connected to PC
No, as long as you have working your device isn't technically bricked in any sense. Don't worry, get that fastboot working again and anything can be fixed.
Also you didnt say whether or not you tried that "Factory" option in bootloader!
hemanthmahesh said:
I'm pretty confused with this. How exactly did you unlock without a working fastboot (no waiting for device issue)? Did you change your pc drivers after unlock or trying this from a different pc? When you say "phone doesn't recognizes it is connected" you mean it says "Connect USB data cable" below "Device is UNLOCKED"? If so, maybe try another usb port cause it should normally say "Transfer Mode: USB Connected" regardless of proper drivers.
Your phone will chrarge no matter what though, no worry about that. It needs to say "Battery OK (Charging)" when connected to PC
No, as long as you have working your device isn't technically bricked in any sense. Don't worry, get that fastboot working again and anything can be fixed.
Also you didnt say whether or not you tried that "Factory" option in bootloader!
Click to expand...
Click to collapse
OMG. I tried that "Factory" option before but it didn't work. Now I tried a second time and it worked. Thanks a lot! Really :laugh:
Anyway, now my phone is back again and rooted. Thanks for the help, guys!
Thaiane said:
Already installed it from the start. The message I got is always this:
"There aren't any updates for your device at the moment
Current Version: N/A"
My fastboot: Doesn't matter the operation I do, I always get this <waiting for device> and the phone is already connected into the computer. And the phone doesn't recognizes it is connected too.
And greeeeat news: my phone now doesn't charges either. I get stuck on a screen with a battery logo and 0%, when connected to the charger. Still, I still can access the fastboot mode. Well, am I lucky or not?
Click to expand...
Click to collapse
Guys the problem occurs due to corruption of /data folder. Even I had the same issue.
What you can do is
1. Connect your phone to PC in fastboot mode.
2. In fastboot, enter the command "adb erase userdata" and "adb erase cache" without quotes and reboot you phone. It will work for most of the devices, if it doesn't I have some other workaround too.
help
forgotter said:
Guys the problem occurs due to corruption of /data folder. Even I had the same issue.
What you can do is
1. Connect your phone to PC in fastboot mode.
2. In fastboot, enter the command "adb erase userdata" and "adb erase cache" without quotes and reboot you phone. It will work for most of the devices, if it doesn't I have some other workaround too.
Click to expand...
Click to collapse
I have the same problem. my phone stuck in blank screen after Unlock Bootloader. and then I try to do "adb erase userdata" and "adb erase cache". but my phone has no chenge, still stuck in.
I attach log when enter command adb above.
I'm sorry before. I can't spech English well
jidurrr said:
I have the same problem. my phone stuck in blank screen after Unlock Bootloader. and then I try to do "adb erase userdata" and "adb erase cache". but my phone has no chenge, still stuck in.
I attach log when enter command adb above.
I'm sorry before. I can't spech English well
Click to expand...
Click to collapse
The log you have posted contains only the help commands of adb and not the actual commands you gave.
Give a try to factory reset from fastboot mode on your phone. And do you a custom recovery installed in your phone?
forgotter said:
The log you have posted contains only the help commands of adb and not the actual commands you gave.
Give a try to factory reset from fastboot mode on your phone. And do you a custom recovery installed in your phone?
Click to expand...
Click to collapse
I've tried factory reset for several times, but no change as well.
yes, I get a CWM in my phone. and then, what have I do?
jidurrr said:
I've tried factory reset for several times, but no change as well.
yes, I get a CWM in my phone. and then, what have I do?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2704207
Go to the above forum.
Sorry for late reply was busy with studies.
I had flash stock firmware
through PC
After a bad root-attempt it seems that my bootloader is damaged. It happens when I used Oneplus One toolkit 1.6. I need help!
The phone is stuck I a startup loop. I can’t enter recovery mode but I can come in to fastboot mode. When I use the command “fastboot oem device-info” I can see that the bootloader is tempered but not unlocked. It seems that I cant unlock it. Because when I use the command “fastboot oem unluck” the phone just reboot into a new loop. Under “Unlocking the device” stage 7 is says “A disclaimer will display on the device that must be accepted.” That never happens with my phone.
wiki.cyanogenmod.org/w/Install_CM_for_bacon
What can I do!?
gunvald89 said:
After a bad root-attempt it seems that my bootloader is damaged. It happens when I used Oneplus One toolkit 1.6. I need help!
The phone is stuck I a startup loop. I can’t enter recovery mode but I can come in to fastboot mode. When I use the command “fastboot oem device-info” I can see that the bootloader is tempered but not unlocked. It seems that I cant unlock it. Because when I use the command “fastboot oem unluck” the phone just reboot into a new loop. Under “Unlocking the device” stage 7 is says “A disclaimer will display on the device that must be accepted.” That never happens with my phone.
wiki.cyanogenmod.org/w/Install_CM_for_bacon
What can I do!?
Click to expand...
Click to collapse
I see this is you first post here in xda and wish it was a better one than this but there are threads on how to fix your issue. May I suggest in the future you do a little more research prior to doing anything with your expensive phones. Sorry to sound like an ass but I see this happen so often. Now to help you out
1 Download all the fastboot images for your phone and flash each other to restore your phone to stock http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
2 Here is the thread you should of read and used prior to doing anything http://forum.xda-developers.com/showthread.php?t=2788632
Good luck and be careful
playya said:
I see this is you first post here in xda and wish it was a better one than this but there are threads on how to fix your issue. May I suggest in the future you do a little more research prior to doing anything with your expensive phones. Sorry to sound like an ass but I see this happen so often. Now to help you out
1 Download all the fastboot images for your phone and flash each other to restore your phone to stock http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
2 Here is the thread you should of read and used prior to doing anything http://forum.xda-developers.com/showthread.php?t=2788632
Good luck and be careful
Click to expand...
Click to collapse
Yes you are absolutely right. I should have read more before trying to root it. What is done is done and now I try to learn from my misstates and save my phone from the garbage can. All help is very appreciated!
Regarding your links, they were unfortunately not helpful in my case. As every other guide I have read they all assume that the bootloader is unlocked or that is possible to unlock it with the “fastboot oem unluck” command. Which in my case seems impossible/hard to do. The question is why I can’t unlock the bootloader or/and how can it be done?
gunvald89 said:
After a bad root-attempt it seems that my bootloader is damaged. It happens when I used Oneplus One toolkit 1.6. I need help!
Click to expand...
Click to collapse
This is what happens when you use "toolkits".
It's much easier to learn what you should do vs clicking a button or hitting "1" on your keyboard.
mbudden said:
This is what happens when you use "toolkits".
It's much easier to learn what you should do vs clicking a button or hitting "1" on your keyboard.
Click to expand...
Click to collapse
^^^This
While toolkits may seem like they make things easier, they're not always reliable, and they allow the user to skip over some really crucial learning experience from doing things manually.
Transmitted via Bacon
http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909 is a good read.
timmaaa said:
^^^This
While toolkits may seem like they make things easier, they're not always reliable, and they allow the user to skip over some really crucial learning experience from doing things manually.
Transmitted via Bacon
Click to expand...
Click to collapse
To replay to the several message that is wrong to use toolkit. I understand you all and obviously now with results to hand it is obvious that it wasn’t the best thing to do. With my prior phone SGS3 I first did everything the manual way and then I was spoiled with a wonderful toolkit from the xda moderator, mskip, that did everything I did but faster.
Please don’t kick a man when he’s down. If someone have any idea to fix this then please write here.
gunvald89 said:
To replay to the several message that is wrong to use toolkit. I understand you all and obviously now with results to hand it is obvious that it wasn’t the best thing to do. With my prior phone SGS3 I first did everything the manual way and then I was spoiled with a wonderful toolkit from the xda moderator, mskip, that did everything I did but faster.
Please don’t kick a man when he’s down. If someone have any idea to fix this then please write here.
Click to expand...
Click to collapse
Try reading this thread http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
I'm not entirely sure what is going on in the thread. It says toggle, so maybe you could toggle the tamper bit closes and try to unlock again.
It would also be possible to boot the recovery without loading it on the phone.
This uses the command "fastboot boot recovery.img" rather than flash. Then from there you could use TWRP's recover to to play with stuff.
abcarter said:
Try reading this thread http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
I'm not entirely sure what is going on in the thread. It says toggle, so maybe you could toggle the tamper bit closes and try to unlock again.
It would also be possible to boot the recovery without loading it on the phone.
This uses the command "fastboot boot recovery.img" rather than flash. Then from there you could use TWRP's recover to to play with stuff.
Click to expand...
Click to collapse
Thanks for your replay! I’m looking in to this now
gunvald89 said:
To replay to the several message that is wrong to use toolkit. I understand you all and obviously now with results to hand it is obvious that it wasn’t the best thing to do. With my prior phone SGS3 I first did everything the manual way and then I was spoiled with a wonderful toolkit from the xda moderator, mskip, that did everything I did but faster.
Please don’t kick a man when he’s down. If someone have any idea to fix this then please write here.
Click to expand...
Click to collapse
On further reading, It seems you'd push the zip to reset the tamper flag:
adb push FILENAME.zip /sdcard/
Then you'd boot TWRP
"fastboot boot recover.img"
Then you'd flash the file.
I've not used this personally, I have booted a recovery through adb, which is how I rooted my phone without unlocking the bootloader.
I'm sure it is just a typo, but as you spelled it several times in this thread like this I just have to ask.
You're not actually typing "fastboot oem unluck" when trying to unlock your phone, are you? :silly:
Cause that would kinda explain why you're so unlocky with it.
gunvald89 said:
To replay to the several message that is wrong to use toolkit. I understand you all and obviously now with results to hand it is obvious that it wasn’t the best thing to do. With my prior phone SGS3 I first did everything the manual way and then I was spoiled with a wonderful toolkit from the xda moderator, mskip, that did everything I did but faster.
Please don’t kick a man when he’s down. If someone have any idea to fix this then please write here.
Click to expand...
Click to collapse
Nobody is kicking you when you're down, just providing good information for people to learn from.
Transmitted via Bacon
I really hope that you will find your solution mate...Just read here and there and be confident.
Anyways, this is my second experience with phone rooting (prior my OPO i had a SGS4) and at the moment of rooting the phone i did not trust all these toolkits, i just dont feel safe using commands written by other people.
I guess i was right...
Best of luck!
gunvald89 said:
Please don’t kick a man when he’s down. If someone have any idea to fix this then please write here.
Click to expand...
Click to collapse
Who's kicking you when you're down?
We're just replying just in case someone else comes by this thread and doesn't understand the risks of "toolkits".
Just because something is faster, doesn't mean it's the best route.
Just like the toll on the highway. Faster but gonna cost you in the end.
[armitage] said:
I'm sure it is just a typo, but as you spelled it several times in this thread like this I just have to ask.
You're not actually typing "fastboot oem unluck" when trying to unlock your phone, are you? :silly:
Cause that would kinda explain why you're so unlocky with it.
Click to expand...
Click to collapse
Hehe that right my spelling is quite bad. Unfortunately that was not the problem here even if my spelling in this thread is really bad… Have to start reading more books or something
Following this guide right now
https://forums.oneplus.net/threads/install-adb-drivers-for-windows-8-1-64-bits.51264/
abcarter said:
On further reading, It seems you'd push the zip to reset the tamper flag:
adb push FILENAME.zip /sdcard/
Then you'd boot TWRP
"fastboot boot recover.img"
Then you'd flash the file.
I've not used this personally, I have booted a recovery through adb, which is how I rooted my phone without unlocking the bootloader.
Click to expand...
Click to collapse
Fist of. Thanks for all your help!
I am trying to push it but now it seems that my mobile isn’t correctly connected. When I run adb devices my phone doesn’t come up the list. It has been there before but I believe I have to fix this before anything else
gunvald89 said:
Fist of. Thanks for all your help!
I am trying to push it but now it seems that my mobile isn’t correctly connected. When I run adb devices my phone doesn’t come up the list. It has been there before but I believe I have to fix this before anything else
Click to expand...
Click to collapse
Download this: theyre the drivers for USB from Google.
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Then unpack the file and go into Hardware manager. Right click on your android device connected with USB and select upgrade drivers. Select the folder that you previously unpacked and select ADB drivers.
Do the same but in this case for Fastboot-bootloader driver version if you cant find your fastboot device after rebooting into bootloader via ADB.
It's not fully detailed as a guide but if you're at least a minimum used to manage peripherals in windows you will not have any problem in using the drivers.
Well done....
The first person who bricked the Opo, writing three lines of code...
Dont know how is that possible
gunvald89 said:
Yes you are absolutely right. I should have read more before trying to root it. What is done is done and now I try to learn from my misstates and save my phone from the garbage can. All help is very appreciated!
Regarding your links, they were unfortunately not helpful in my case. As every other guide I have read they all assume that the bootloader is unlocked or that is possible to unlock it with the “fastboot oem unluck” command. Which in my case seems impossible/hard to do. The question is why I can’t unlock the bootloader or/and how can it be done?
Click to expand...
Click to collapse
The guide I provided does not require you to have a unlocked bootloader. This is to restore phone to 100% stock and is done in fastboot with fastboot commands. Are you sure you read it right
Straight from Cyanogen themselves right here
Code:
Instructions:
First time flashing CyanogenMod 11S on your device, or coming from another ROM (e.g. ColorOS)?
Download the file cm-11.0-XNPH25R-bacon-signed-fastboot.zip to your PC from the links below
Reboot your device into Fastboot mode by holding PWR+VOL-UP
Connect your device via USB to your PC
Unpack the downloaded zip
Open a command prompt (Windows) or terminal (Linux/Mac) and perform the following fastboot commands:
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
fastboot update cm-11.0-XNPH25R-bacon-signed-fastboot.zip
DuckMcQUack said:
Download this: theyre the drivers for USB from Google.
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Then unpack the file and go into Hardware manager. Right click on your android device connected with USB and select upgrade drivers. Select the folder that you previously unpacked and select ADB drivers.
Do the same but in this case for Fastboot-bootloader driver version if you cant find your fastboot device after rebooting into bootloader via ADB.
It's not fully detailed as a guide but if you're at least a minimum used to manage peripherals in windows you will not have any problem in using the drivers.
Click to expand...
Click to collapse
Thanks your suggestion. I tried that and is just says that I have the same driver installed. Also tried to uninstall every driver that has anything to do with google android and phones and then reinstall. I also tied to install from my Android SDK folder but I got the same message.
playya said:
The guide I provided does not require you to have a unlocked bootloader. This is to restore phone to 100% stock and is done in fastboot with fastboot commands. Are you sure you read it right
Straight from Cyanogen themselves right here
Code:
Instructions:
First time flashing CyanogenMod 11S on your device, or coming from another ROM (e.g. ColorOS)?
Download the file cm-11.0-XNPH25R-bacon-signed-fastboot.zip to your PC from the links below
Reboot your device into Fastboot mode by holding PWR+VOL-UP
Connect your device via USB to your PC
Unpack the downloaded zip
Open a command prompt (Windows) or terminal (Linux/Mac) and perform the following fastboot commands:
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
fastboot update cm-11.0-XNPH25R-bacon-signed-fastboot.zip
Click to expand...
Click to collapse
Oh nice. I will try that after i get the drivers up and running!
This may be a simple solution, but I am completely puzzled on how to fix this.
SO i recently rooted my phone & used the twrp "twrp-3.3.1-4-guacamole". Installed magisk via that twrp and continued with my day.
I accidentally got a virus by trying to get a full free vpn, me being a terrible pirate, i accidentally got a virus! Silly me.
It was annoying me and I decided to factory reset my phone... not via twrp. I remembered after I clicked "Reset all" on oxygenos that it's not the way how to do it with a root device, and well.. it didn't exactly work.
Every time I power/reboot the phone it just brings me to the fastboot menu of "START", "POWER OFF", "RECOVERY MODE", & "RESTART BOOT LOADER". I thought since TWP is recovery mode I try to access that... no luck, it just brings me back to that fastboot menu. I tried going on CMD via adb by saying "fastboot flash boot twrp-3.3.1-4-guacamole.img". It will say it's finished and successful, but when i reboot and try to access recovery mode it just does not work.
TL;DR: Think I bricked my phone, there is no OS installed and I can only access the fastboot.
Any help? Much appreciated
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
trapcoder666 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Click to expand...
Click to collapse
Thank you for the guap recovery as i didn't know it existed. However, what are the steps? when i go on the MSM download tool it doesn't detect my phone.
that being said, i can't access any of my files through my pc using fast boot. on MSM it's just saying "waiting for device" even when plugged in so thats annoying.
trapcoder666 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Click to expand...
Click to collapse
I downloaded the one you sent, and after a while as my internet is bad. It still does not work.
Whenever I try to install the qualcomm drivers it never shows up, and when i try and boot it up so the gual recover detects my phone it never works. It's still saying "waiting for device".
Does anyone know how to fix this? it's doing my head in that it's not as easy as it should be.
MOweenSalah said:
I downloaded the one you sent, and after a while as my internet is bad. It still does not work.
Whenever I try to install the qualcomm drivers it never shows up, and when i try and boot it up so the gual recover detects my phone it never works. It's still saying "waiting for device".
Does anyone know how to fix this? it's doing my head in that it's not as easy as it should be.
Click to expand...
Click to collapse
Pretty sure that your phone will not be accessible via adb/fastboot during the msm process. Did you follow the directions in the link above to a T?
A few things to note:
- Works perfectly fine for unbricking GM1917 modeled OnePlus 7 Pros.
- Use the original cable and try to plug it into a USB 2.0 port. I've found that this is the most ideal condition.
- Make sure your device is charged up. If you can't see how much charge it has, leave it charged via the 30W warp charger for 40 minutes and that should be good enough.
- In the L2 drivers folder found in the archive, navigate to the 32 or 64 folder depending on your system's architecture, and click on the file that ends in the extension ".cat". Then, click "view signature", then "View certificate", then "Install." This is IMPORTANT.
- Then, make sure your device is powered OFF, then, plug in the USB-A side of the cable (big head) into your computer and do NOT connect the USB-C (small head) into your phone yet.
- Hold down Volume up AND volume down for five seconds, and while you're continuing to hold, plug the USB-C side into your phone. The drivers should automatically download, and you should see a "Qualcomm QD loader" device in Device Manager. If you see an exclamation mark or you don't see this, you are doing it wrong and you need to repeat the above steps.
- Open up MSMTool.exe as an administrator and click 'start' only. Should take a few minutes, but you will have a good-as-new OnePlus 7 Pro.
Click to expand...
Click to collapse
Krsmqn said:
Pretty sure that your phone will not be accessible via adb/fastboot during the msm process. Did you follow the directions in the link above to a T?
Click to expand...
Click to collapse
I did yes, i pressed all buttons and the power button for 5 seconds and plugged my charger in. Then after that went on the MSM tool and it went straight to the fastboot. I really don't know but it loves this fastboot tool haha
Krsmqn said:
Pretty sure that your phone will not be accessible via adb/fastboot during the msm process. Did you follow the directions in the link above to a T?
Click to expand...
Click to collapse
Add: I made a video showing what I mean with the fastboot. Basically if i do anything with the phone fastboot it will just go back to the menu (sorry for bad quality)
https://www.youtube.com/watch?v=jU8a6kDXNNs&feature=youtu.be
MOweenSalah said:
Add: I made a video showing what I mean with the fastboot. Basically if i do anything with the phone fastboot it will just go back to the menu (sorry for bad quality)
&feature=youtu.be
Click to expand...
Click to collapse
It's one of those things where if someone was there with you, it'd likely get figured out. I've seen this kind of situation hundreds of times on XDA, and with all due respect, the problem is most always at the hands of the user. These phones are cookie cutter made, so there's nothing different (besides individual variants) that would make thee tools not function correctly, unless it's operator error. But that's not set in stone. Just don't give up. Try setting up your camera for an overhead view. I couldn't tell if you were plugging in your cord. And it seemed to reboot, instead of power off. Repeat the steps carefully, and see if you can achieve better results.
Don't give up! We're here for you ?
Make sure phone is powered off before plugging it in. Launch msm tool, Press the vol up and down key for a few seconds then plug in.
Edit : make sure your drivers are up to date too.
I don't know about msm tools never tried it but I know your situation.
Don't do fastboot flash boot twrp-3.3.1-4-guacamole.img
Remove the word flash. You are supposed to boot into twrp then flash the zip file to the phone.
look at this
Command in Fastboot mode is:
Fastboot boot "name of the recovery".img. Phone should boot to twrp. Then flash twrp.zip
or try Fastboot roms:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Choose the one for youre phone (region)
MSM tool it's the last option.
Can't you just switch slots from fastboot or did you mess up both?
trapcoder666 said:
Make sure phone is powered off before plugging it in. Launch msm tool, Press the vol up and down key for a few seconds then plug in.
Edit : make sure your drivers are up to date too.
Click to expand...
Click to collapse
Firstly I'm terribly sorry for no response (same goes to everyone else looking into this matter for me. THANK YOU!)
However, I have done this multiple times in the past and it instantly goes back to boot menu. it sucks :/
IronSingh said:
I don't know about msm tools never tried it but I know your situation.
Don't do fastboot flash boot twrp-3.3.1-4-guacamole.img
Remove the word flash. You are supposed to boot into twrp then flash the zip file to the phone.
look at this
Click to expand...
Click to collapse
Okay. I shall go and look into this situation when I receive my phone back (going to explain that in a later quote)
larsdennert said:
Can't you just switch slots from fastboot or did you mess up both?
Click to expand...
Click to collapse
If i'm honest with you.. i'm not sure in the slightest. My only assumption is no because the only thing I can access is only the fastboot. if i attempt to go into recovery mode it will go back to fastboot. when I flash twrp it will flash but it won't boot into it. It's confusing as hell.
Just to add to this whole situation:
Since I have no idea and just wanted it fixed in the day; i was willingly to give money for this phone to be fixed, but thanks to the person, he just made it a slower process by doing things i've already done.. going to pick the phone back up in an hour of this message.
I haven't used the fastboot boot twrp cmd yet, but from how everything else has been so far i feel like that won't work, but i will update everyone on that situation.
Just to add additional things that I may have not mentioned in the past will be below:
- Whenever i type in "ADB Devices" in cmd, it will not show up with anything. However, when I type in "fastboot devices" it shows it's serial and in "fastboot". It will only show as fastboot and i can't access the phone via file explorer in windows.
When i say "ADB Devices" it says *devices attached* and will show none of my phones details, but when i say fastboot devices it will then show the devices.
^ what i said above means I can't use the guap recover, or anything which means the phone has to be detected in windows, because other than fastboot, it won't work at all.
- So far I can't access twrp as a whole, so if anyone knows how to give me a guide on how to install it from where I am at, that would be amazing (if not, i'll try and reiterate what to do with the one given from a previous comment, so thank you )
- There was one time I was allowed in TWRP but i completely forgot how i entered it (so i can't explain), So i feel like there is hope in that aspect. I feel like i entered something via cmd so maybe there's a way?
In terms of hardware my phone is completely fine, there's not a single problem other than the software being a pain in the ***!!
if anyone can just spew out a bunch of help in different explanations it means the world because so far all I can see is that I wasted about £600 on an amazing phone because of dumb *** haha.
Thank you to everyone who has helped, and is helping
From your comments, you are not familiar with how Android functions. Not knowing the difference between adb and fastboot is an indicator that you should just endeavour to have a stock phone until you understand whats going one. It's also hard for people to help as no one has hands on and can see what is broken. Everyone here will be working blind like trying to fix your car for you from across the country.
Start the phone into fastboot and connect it to a pc. From a pc command prompt in your fastboot directory enter the command:
fastboot getvar current-slot
If the current slot is A then:
fastboot --set_active=b
or vice versa
fastboot --set_active=a
then fastboot reboot and see if you boot into the other slot.
Not knowing what phone you have makes it even tougher but I suspect you will have to reflash a clean complete rom via fastboot.
https://forum.xda-developers.com/on...fastboot-roms-oneplus-7-pro-t3931424#poststop
larsdennert said:
From your comments, you are not familiar with how Android functions. Not knowing the difference between adb and fastboot is an indicator that you should just endeavour to have a stock phone until you understand whats going one. It's also hard for people to help as no one has hands on and can see what is broken. Everyone here will be working blind like trying to fix your car for you from across the country.
Start the phone into fastboot and connect it to a pc. From a pc command prompt in your fastboot directory enter the command:
fastboot getvar current-slot
If the current slot is A then:
fastboot --set_active=b
or vice versa
fastboot --set_active=a
then fastboot reboot and see if you boot into the other slot.
Not knowing what phone you have makes it even tougher but I suspect you will have to reflash a clean complete rom via fastboot.
https://forum.xda-developers.com/on...fastboot-roms-oneplus-7-pro-t3931424#poststop
Click to expand...
Click to collapse
I do appreciate the help. If i'm honest with you the only reason I did this is to increase my data speeds (which from look of things is outdated now), and a longer battery life. I don't know much about rooting/jailbreaking but believe me that I have been in the scene for years, but not even knowing everything haha!
that being said.. i'm in twrp! thank you so much mate, i'll try and go and install the rom now. thank you!
Now install the zip twrp
Thankfully.. IT'S FIXED!
I didn't have to install twrp again or any of that. I simply changed the slot from A to B and pressed all buttons when it was showing the "! Your decide is unlocked" orange/black screen.
I had msm tools up and it detected and instantly installed the OS to the latest one and boom. It works again!
I got to thank everyone for helping me because without you people I wouldn't of been able to fix it. I looked everywhere and no help anywhere as I feel like it's pretty dumb to do what I did haha!
Thank you again people!
Oh you gave up on root?
You are supposed to read the instructions and follow them to the letter. When I read your post I realized you tried to install twrp like you would pre Oreo but it changed you have to boot into twrp then install it via zip file.
Anyways just remember that for next time.