Hey guys I really hope you can help me out because I have a bricked N5. So this is my first time attempting to flash anything to my phone and I decided to check out the android L preview. I watched a bunch of videos and got everything set up (SDK, unlocked bootloader). After I unlocked the bootloader, I forgot to enable usb debugging before I booted into fastboot and attempted to flash L. When I try to flash L I get "writing bootloader... FAILED (remote: invalid bootloader image)" every time. So I said screw it I'll just flash 4.4.4 and be done with it but I get the same FAILED msg in cmd. I'm assuming this is the issue that's preventing me from successfully flashing anything to my phone but not 100% sure. I've tried to get my phone into recovery mode but can't seem to make that work either. What can I do to fix this? keep in mind that just today was the first time I've ever used the command prompt =/ Thanks in advance for giving this a read and I really hope its just some simple fix *fingers crossed*
USB Debugging has NOTHING to do with bootloader or fastboot. The ONLY thing USB Debugging is related to is ADB while booted into Android.
You might want to read some more threads: [Resource] All Guides and Info Threads
Lethargy said:
USB Debugging has NOTHING to do with bootloader or fastboot. The ONLY thing USB Debugging is related to is ADB while booted into Android.
You might want to read some more threads: [Resource] All Guides and Info Threads
Click to expand...
Click to collapse
well turn's out all I had to do was restart my laptop and now everything has decided to work. Thanks for the response Lethargy
Related
I am trying recovery,but every time when i write fastboot oem unlock i gives me back with a message "waiting for devices",and just holds there....what should i do to make recovery....Thanks in fowards...
mimi12 said:
I am trying recovery,but every time when i write fastboot oem unlock i gives me back with a message "waiting for devices",and just holds there....what should i do to make recovery....Thanks in fowards...
Click to expand...
Click to collapse
Are you following any of the guides in the Development section?
Are you Mac or Windows or Linux?
Your post is a little hard to understand, but I think you're trying to push the clockwork recovery to your phone, is that correct, or are you just trying to get into normal recovery?
Assuming you're on the white screen that says fastboot mode at the top of it, then your problem is that you don't have the proper drivers on your computer to talk to the phone. You need to install the drivers from the SDK (or if on Windows you can use PDANet).
The best guide on there, AllGamer's, has full instructions on how to get the phone and the computer talking to each other properly.
May I ask why you want to oem unlock the phone? You're aware it's not necessary to do this to root the phone or flash clockwork recovery or even flash custom roms? There's nothing wrong with running unlocked (I do), but just be aware that the fastboot oem unlock command will totally WIPE ALL DATA off your phone, including your pics and music off the USB storage area.
My guide to rooting has you skip the oem unlock, but you can follow any guide and just skip that step to avoid wiping your phone.
Sorry for the short post.I run on Windows,i dont know what is clockwork recovery,i read something about it,but i didnt understand,i think that i need normal recovery.I installed sdk on my computer and i go to load drivers(browse....etc)and it cant "find" drivers,i installed pdanet also and i get the same message "waiting for devices",i installed some application and it started to freeze every 5-10min,i dont have that much data on him self,so its ok if recovery wipe all data,i will try that guides and will get back to you how it went,btw THANKS for everything....
This thread might help you out as well. http://forum.xda-developers.com/showthread.php?t=878786
Thank you for everything,i did it,i wipe out everything and now is working like new.......i had troubles with installing adb and fastboot drivers,but i managed to figure it out,and everything went smooth))One again thank you very,very,very,very,very,very,very,very,very,very much....
P.S -sorry if my english is bad...
Hello everyone
I've recently got an LG Q6 M700N, and I'm trying to root it, but I've came across a problem. Whenever I type in adb reboot bootloader, the phone simply reboots to the system. It won't go into bootloader. Have any of you encountered this issue? Can you give me a fix or a workaround? Developer options are ON, OEM Unlock is ON, drivers are installed, tried with multiple USB ports on my PC, adb sees the device in debug mode.
Thanks in advance!
If I've posted in the wrong thread: My bad! Sorry.
See thread in dev section
deleted
It was late and I was cleaning up my old OP5T, getting it ready to sell. I thought I had plugged in my OP5T, but I still had my OP6 plugged in when I ran "fastboot oem lock". Now it won't boot and I can't unlock it (I'm assuming because I can't get into the OS and "enable OEM unlocking" anymore).
Is there anything I can do?
try using search next time because its already been talked abput here https://forum.xda-developers.com/oneplus-6/help/relock-bootloader-t3798135
Actually, I DID read that. I didn't just roll off the cabbage truck. If you have time to post snippy replies (I also searched YOUR post history), then maybe you can point out where in that thread the answer to my question is. I could see if there was a thread where this specifically happened, or if it had been talked about over and over, but I couldn't find one. You do know this is a fairly new device, right? TBH, you're just being rude. To count on someone to hit the right search terms for a single thread where the info exists is just asinine.
1) I have not seen anyone with this situation on the OP6 yet
2) The OP5T had an unbrick tool
3) Most phones have a way to restore the OS to factory
If it can't be restored without calling OnePlus, then why not just say so? I'll answer for you, it's because you actually enjoy replying in such a manner. Grow up.
Have you tried the mega unbrick guide?
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Flapjack said:
It was late and I was cleaning up my old OP5T, getting it ready to sell. I thought I had plugged in my OP5T, but I still had my OP6 plugged in when I ran "fastboot oem lock". Now it won't boot and I can't unlock it (I'm assuming because I can't get into the OS and "enable OEM unlocking" anymore).
Is there anything I can do?
Click to expand...
Click to collapse
I don't think relocking your bootloader will disable the "enable OEM unlock" toggle in the OS. You may just be able to unlock your bootloader as normal again. You should be able to use the fastboot recovery method to restore your OS.
[email protected] said:
Have you tried the mega unbrick guide?
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Click to expand...
Click to collapse
I did, but I got the "software image does not exist" error. Does it matter whether I downloaded the 5.13 or 5.15 vesion?
mikex8593 said:
I don't think relocking your bootloader will disable the "enable OEM unlock" toggle in the OS. You may just be able to unlock your bootloader as normal again. You should be able to use the fastboot recovery method to restore your OS.
Click to expand...
Click to collapse
I tried several times. It throws the following error, which when searched for, always seemed to be someone forgetting to enable OEM unlocking in settings:
Code:
FAILED (remote: oem unlock is not allowed)
Success! I was able to get it to work with the drivers from this post. No other drivers worked. I also forced the COM port to the first available (in my case, COM1) vs the one it popped up on. Until I did that, I would just get a huge list of ports that had no device attached. Once I had it on COM1, it was the only device that showed up in the list. The first time after that, I got a "Sahara Communication Failed" error, but it went away after rebooting the phone back into EDL mode again.
Thanks for the help!
Flapjack said:
Success! I was able to get it to work with the drivers from this post. No other drivers worked. I also forced the COM port to the first available (in my case, COM1) vs the one it popped up on. Until I did that, I would just get a huge list of ports that had no device attached. Once I had it on COM1, it was the only device that showed up in the list. The first time after that, I got a "Sahara Communication Failed" error, but it went away after rebooting the phone back into EDL mode again.
Thanks for the help!
Click to expand...
Click to collapse
Hi buddy,
I tired to relock the bootloader and success in that but the phone stuck at fastboot mode, neither restarting to system nor to anything. Kindly help me if i can flash the stock rom in locked bootloader is so how.
THanks in adv
Did you try msm download tool ?
My OnePlus was bricked and it's bootloader is locked too, I have tried most of the steps like msm and those Bat files etc. But error is coming
"Remote : Flashing is not allowed in locked state"
Even tried that all in one tool that also can't unlock my bootloader
Now plz someone show me steps it will be a great help
Problem solved. Trying different USB cable (2.0) worked.
-----
Hi, I was trying to downgrade from Android 12 to 11. Following guide step by step, including
USB Debugging, Turn on OEM Unlocking, then used adb to boot into bootloader. Device state was locked. Ran fastboot flashing unlock but then stuck at Waiting for Device. Phone didn't go into warning to unlock bootloader.
I noticed that Boot slot is b, not sure if that matters.
Also tried to follow Google's own flash too, got stuck at the same phone screen.
Any help is appreciated.
Kenneth
kenship said:
Problem solved. Trying different USB cable (2.0) worked.
-----
Hi, I was trying to downgrade from Android 12 to 11. Following guide step by step, including
USB Debugging, Turn on OEM Unlocking, then used adb to boot into bootloader. Device state was locked. Ran fastboot flashing unlock but then stuck at Waiting for Device. Phone didn't go into warning to unlock bootloader.
I noticed that Boot slot is b, not sure if that matters.
Also tried to follow Google's own flash too, got stuck at the same phone screen.
Any help is appreciated.
Kenneth
Click to expand...
Click to collapse
Sounds like a driver issue. It's either the Google USB driver: https://developer.android.com/studio/run/win-usb
or the ADB driver: https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
Thks for the reply. Well I can't say for sure but switching USB ports and changing cable eventually solved my issue. I kept reinstalling Google USB driver as well so any one of them could be the problem. But I really don't worry now since I successfully flashed 11 back.
Just as the title says; I have the unlock token and I've tried everything I can think of to flash it and nothing's worked. I have OEM unlocking enabled, the phone is permanently carrier unlocked, USB debugging is enabled, I've made sure to download a new version of Platform Tools, I've moved the .bin file to the same directory as Platform Tools, the phone comes up in ADB and fastboot when I check, it just won't write and I can't figure out why... usually it just hangs at sending 'cust-unlock' etc. but never progresses past that. Can anyone help me figure this out?
EDIT: Resolved! Me being dumb, not realized I'd only tried USB 2.0 ports; using a 3.2 port did the trick instantly.
Have you tried other fastboot commands like - "fasboot reboot bootloader" to ensure your fastboot is working properly and the correct drivers are installed?
FoxyDrew said:
Have you tried other fastboot commands like - "fasboot reboot bootloader" to ensure your fastboot is working properly and the correct drivers are installed?
Click to expand...
Click to collapse
Yea, that's what's baffling; I can jump back and forth between adb and bootloader/fastboot pretty easily but I just can't send the unlock token. I have seen a couple weird errors though, like if I'm in bootloader and do 'fastboot OEM unlock' and it fails (since I can't get the token to flash) and afterward I try 'fastboot devices' sometimes fastboot crashes to the 'press any key to reboot' screen.
Could this just be an outdated driver issue? I thought they were up to date...
Have u try using other cable or even try on different PC?
hendavi said:
Have u try using other cable or even try on different PC?
Click to expand...
Click to collapse
I've tried multiple USB ports and the original cable as well as others; I've confirmed commands like 'ADB reboot bootloader' and 'fastboot reboot bootloader' work and I've even updated the ADB/fastboot drivers just in case... still nothing. I haven't tried a different PC yet but I suppose that's next
No matter what I try, this is what I get every time I try it from the bootloader. I've tried from bootloaderd/recovery, but it fails there too saying something like 'writing not allowed' or something... I have OEM unlock turned on and it's carrier unlocked, so I have no clue what's stopping this from working.
What's really weird is I actually got this to work once before on this same device, but had to reset the phone back to stock T-Mobile branded software using the MSM tool; the first time around, I was able to enter the unlock token and just unlock it like normal (fastboot OEM unlock). Now that I've reset the phone and I'm trying again, it just won't work... really perplexed on this one.
UPDATE
I had to pull up an image of my mobo's io panel because I couldn't remember and couldn't see which ports were which; once I moved the cable to a USB 3.2 port, it worked... I guess I'd only been trying it on USB 2.0s before so it didn't work.
Thanks for your help!
I had same issue on my OnePlus 8 TMobile. Have to disable driver signatures. This shows you how. Yes, the link is for a diff phone, but just follow the disable driver signatures part of it and it will then show up in fastboot
https://forum.xda-developers.com/t/...owing-up-in-fastboot-mode-windows-10.4194491/
EDIT: False alarm. I was sent an unlock code for an older device I have instead of the one I just bought. Should've double checked it first.