Long story. I downloaded the Nexus rootkit and unlocked my bootloader in an attempt to root my device. I installed TWRP and erased all my device information without making a backup. During intallation something happened with the toolkit(I believe the program froze or I just got too impatient, so I disconnected the USB). Mind you at this point I had not installed any third party roms yet resides TWRP which I don't even know if it installed completely because after I disconnected the screen turned into bright static.
So after mindlessly disconnecting my phone the entire screen went blank or was static. I could not see anything, so I sent it to LG for repair. They fixed the screen, but the phone is still without an operating system because I wiped it when I had TWRP and I now see this after it loads https://goo.gl/photos/pNZz2XgpQ2oA3SMN6 I don't know what else they did over there because I no longer have TWRP. I also have a locked bootloader now. I attached some screen shots of what options I get when I turn on the phone and the other options I see. which include the bootloader and recovery screen.
https://goo.gl/photos/w7QnfuqtbNGirQuE9
https://goo.gl/photos/58XmdAiMwmdvGfr29
I have tried using the rootkit to install stock rom, but that requires an unlocked bootloader which I don't have. I also tried fastboot oem unlock, but it says failed. Also, I have tried installing the right drivers... It's hard to tell whether or not I have the correct drivers. Under device manager. I am seeing; Android Device--- LG Android Interface. I don't think these drivers work though because I can't pull up my device details in ADB (I am now able to do this thanks to some help in the forum)
EDIT: I fixed the driver issues, This involved manually assigning drivers TWICE through device manager. I had to assign them when I was in the bootloader and again when I went into recovery on my android device. Windows 8.1 recognized the device as 2 different devices based on what screen (bootloader vs recovery). Thus make sure to manually update your drivers twice. Once in bootloader and again in recovery. I am also using the latest android SDK platform tools.
I am now having trouble doing "adb sideload file.zip"... My device keeps rejecting googles OTA files saying signature verification failed https://goo.gl/photos/9UURn9To33YdZM7B7
I also get this error in CMD https://goo.gl/photos/dRvUS3bB5saGehX1A
EDIT: added more details
Last edit: Solved!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
So none of the OTA roms from google worked in ADB sideload etc, but for whatever reason when I sideloaded a custom ROM it installed just fine... No sig verifications errors in recovery mode... I used http://forum.xda-developers.com/nexus-5x/development/rom-pure-nexus-layers-fi-wifi-calling-t3244601 <---- After downloading this custom rom file, I moved it over to my SDK platform tools folder (you could also use the adb folder in your C drive if you went about installing those adb drivers)
Next, I started bootloader on my android device by pressing power and volume down buttons. I then navigated to recovery by using the volume keys. once in recovery, I selected apply update from ADB. I am now done with the phone.
I opened up command prompt from my PC using shift/right click from the appropriate folder (c/adb or platform tools folder). further, I opened command prompt and typed in "adb sideload pure_nexus_bullhead-6.0-20151109.zip" the flash was successful.
The first boot was not perfect. I recieved a error in regards to something about a manufacture error, but it was enough for me to get into the OS and enable OEM unlocking. I am now able to move forward and unlock the bootloader with rootkit or fastboot. After unlocking the boot loader I went back to a factory ROM which now installed with no problem.
Holly crap. Anyways huge thanks to everyone on this thread you guys are awesome I could not have done it without you.
XDA 4 life
Can you be a little more specific? what were you flashing and what steps did you follow?
Bootloader
metpage said:
Can you be a little more specific? what were you flashing and what steps did you follow?
Click to expand...
Click to collapse
ideaman924 said:
Please include:
Details of what you were doing
A screenshot (or a camera shot from another phone)
What things you flashed
What the phone was running prior to flashing
Your device model (just in case we need to recommend tot files)
If possible, a recent backup from TWRP
We cannot help without these things. Thanks!
Click to expand...
Click to collapse
Ok so here is the long story. I downloaded the Nexus rootkit and unlocked my bootloader in an attempt to root my device. I got half way through installing TWRP and erasing all my device information when my computer froze or something happened with the toolkit(I believe the program froze, so I disconnected). Mind you at this point I had not installed any third party roms or etc besides TWRP.
So after disconnecting my phone the entire screen went blank and was static. I could not see anything, so I sent it to LG for repair. They fixed the screen, but the phone is still without a operating system. I don't know what else they did over there because I no longer have TWRP. I have a locked bootloader now and no OS. I attached some screen shots of what options I get when I turn on the phone and the other options I see.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have tried using the rootkit to install stock rom, but that requires an unlocked bootloader which I don't have. Also, I have tried installing the right drivers... It's hard to tell whether or not I have the correct drivers. Under device manager. I am Android Device--- LG Android Interface. I don't think these drivers work though because I can't pull up my device details in ADB, but that could also be because everything is wiped on the device...
I also have the latest SDK installed from google.
For the most part I am a noob, I know, but I ain't going down without a fight.
more pics
Nebula666 said:
Ok so here is the long story. I downloaded the Nexus rootkit and unlocked my bootloader in an attempt to root my device. I got half way through installing TWRP and erasing all my device information when my computer froze or something happened with the toolkit(I believe the program froze, so I disconnected). Mind you at this point I had not installed any third party roms or etc besides TWRP.
So after disconnecting my phone the entire screen went blank and was static. I could not see anything, so I sent it to LG for repair. They fixed the screen, but the phone is still without a operating system. I don't know what else they did over there because I no longer have TWRP. I have a locked bootloader now and no OS. I attached some screen shots of what options I get when I turn on the phone and the other options I see.
I have tried using the rootkit to install stock rom, but that requires an unlocked bootloader which I don't have. Also, I have tried installing the right drivers... It's hard to tell whether or not I have the correct drivers. Under device manager. I am Android Device--- LG Android Interface. I don't think these drivers work though because I can't pull up my device details in ADB, but that could also be because everything is wiped on the device...
I also have the latest SDK installed from google.
For the most part I am a noob, I know, but I ain't going down without a fight.
Click to expand...
Click to collapse
I do get these options by holding down the power key and volume down
Nebula666 said:
I do get these options by holding down the power key and volume down
Click to expand...
Click to collapse
You're booting into the bootloader which is a good start. Using the vol keys can you go to recovery? Is it the stock recovery. Also,I think your drivers are correct. When booted into the boot loader you need to use fastboot commands, not adb, i.e. fastboot devices
Edit, I see from your second image it's the stock recovery. Try loading the ota from here, https://developers.google.com/android/nexus/ota#bullhead
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You're booting into the bootloader which is a good start. Using the vol keys can you go to recovery? Is it the stock recovery. Also,I think your drivers are correct. When booted into the boot loader you need to use fastboot commands, not adb, i.e. fastboot devices
Edit, I see from your second image it's the stock recovery. Try loading the ota from here, https://developers.google.com/android/nexus/ota#bullhead
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
So I tried using fastboot devices and nothing comes up.. I am going to try reinstalling all the SDK/drivers on a different computer. Maybe that will help.
Are you booted into the bootloader when you run fastboot devices? Power and vol down keys then stay on the screen with Start on it.
Sent from my Nexus 9 using XDA Free mobile app
Ok I think I am connected now...
Device manager is showing my device as
Android Devices
---Android Bootloader Interface
It is also now recognized in CMD.. before it would not show up.
jd1639 said:
Are you booted into the bootloader when you run fastboot devices? Power and vol down keys then stay on the screen with Start on it.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Ok I am not sure what to do now as the google directions advise me to use ADB reboot recovery and that doesnt work...
Just boot into the bootloader then use the vol keys to go to recovery
It's the same screen as the second image you posted.
Sent from my Nexus 5X using XDA Free mobile app
Ok so I tried running in recovery mode... I selected apply update from from ADB.... Than I ran the following command adb sideload (ota file.zip) from CMD and I got this error
"ERROR: DEVICE '(NULL)' NOT FOUND"
jd1639 said:
Just boot into the bootloader then use the vol keys to go to recovery
It's the same screen as the second image you posted.
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
See above, I get this message "ERROR: DEVICE '(NULL)' NOT FOUND"
You get that error on your pc? I'm not sure what to tell you.
You got the device back from being repaired in this condition?
Sent from my Nexus 5X using XDA Free mobile app
jd1639 said:
You get that error on your pc? I'm not sure what to tell you.
You got the device back from being repaired in this condition?
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
I get that error message from cmd after imputing adb sideload "ota file"
Nebula666 said:
I get that error message from cmd after imputing adb sideload "ota file"
Click to expand...
Click to collapse
You can't side load the ota if you don't have an OS installed. Download the the stock image from Android site and flash those images to get your device working. You need to be on the bootloader to flash them.
Sent from my Nexus 5X using Tapatalk
Nebula666 said:
I get that error message from cmd after imputing adb sideload "ota file"
Click to expand...
Click to collapse
While your phone is in the stock recovery and plugged into your computer type:
adb devices
What is the output?
Sent from my SM-G930V using Tapatalk
---------- Post added at 06:01 PM ---------- Previous post was at 05:43 PM ----------
metpage said:
You can't side load the ota if you don't have an OS installed. Download the the stock image from Android site and flash those images to get your device working. You need to be on the bootloader to flash them.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
The OTA updates Google is supplying us are not simply delta updates. They are the full package. Google is doing it this way because the developer preview OTA was borking locked devices. The OP indicated that he is still locked. Oddly since he was flashing TWRP when this ****uation started. But that's the info we were given.
Sent from my SM-G930V using Tapatalk
Half way solved
metpage said:
You can't side load the ota if you don't have an OS installed. Download the the stock image from Android site and flash those images to get your device working. You need to be on the bootloader to flash them.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
PiousInquisitor said:
While your phone is in the stock recovery and plugged into your computer type:
adb devices
What is the output?
Sent from my SM-G930V using Tapatalk
Click to expand...
Click to collapse
Ok here is what is going on.... It was definitely a driver issue. I had the drivers successfully installed when I was in bootloader, but as soon as I went to recovery mode on android my computer would no longer recognize the drivers, so I had to manually reinstall them again for recovery mode. Now I have access... I did another attempt at adb sideload "ota.zip" that I downloaded from googles OTA site , but I am getting a signature error on my android and abort message on android here
Am i suppose to unzip this file or leave it zip? When I unzip all I see is a bunch of .img files not zny zips so maybe I am missing something here.
So google has two download links for the OTA, I am trying the other one now without unzipping it.
Alright so the second file I downloaded is giving me the same verification errors in recovery... I am going to try one last thing before I try blending the phone.
There is hope ahead! i think I downloaded the wrong OTA from the google website. The nexus 5x and 6p have the same descriptions. Hopefully this solves the problem. I am literally ready to throw this phone in the blender and call it a day
Related
been looking around on here. im stuck now
Ok iv unlocked and have root and can load into Clockwork 5.5.0.2
But when in Clockwork i get
E:can't mount /sdcard/
When i reboot the nexus now all i get is the Google Logo with the unlock Padlock.
Once it did load back into OS and then rebooted it self now stuck on Google logo and Unlock padlock... i Didnt copy over my ROM too the SDCard....
How do i get back into the OS
Flash the factory Google images via fastboot. Search the forum. There a quite a few threads with step by step instructions.
Sent from my Galaxy Nexus using xda premium
Try pressing the volume down button and power button until you reach recovery. When you a red triangle, press Vol+/Vol-/Power at the same time, you will now see a menu, select factory data reset.
I've been in your shoes, and I doubt a factory reset will help. If I were you, I would download the stock images first (lte or GSM nexus?). After that, try seeing if your drivers are configured and that tour phone is being recognized by your computer when it is plugged in with the USB cable. The drivers will need to be configured for when the phone is showing the Google logo, but also configured again when the phone is in the boot loader. (Ask if you need more instructions for this).
OK, what worked for me was locking and then unlocking my phone again. Type fast boot OEM lock, and if the drivers are good then the boot loader will lock. Then type fast boot OEM unlock and it will wipe everything--even Android backups. It shoud also delete the problem. After that you can push files to it from the computer but you might have to configure your drivers again (I did). Hope this helps, it worked for me.
??
throwbot said:
I've been in your shoes, and I doubt a factory reset will help. If I were you, I would download the stock images first (lte or GSM nexus?). After that, try seeing if your drivers are configured and that tour phone is being recognized by your computer when it is plugged in with the USB cable. The drivers will need to be configured for when the phone is showing the Google logo, but also configured again when the phone is in the boot loader. (Ask if you need more instructions for this).
OK, what worked for me was locking and then unlocking my phone again. Type fast boot OEM lock, and if the drivers are good then the boot loader will lock. Then type fast boot OEM unlock and it will wipe everything--even Android backups. It shoud also delete the problem. After that you can push files to it from the computer but you might have to configure your drivers again (I did). Hope this helps, it worked for me.
Click to expand...
Click to collapse
I can connect the phone and lock n unlock the bootloader. so the USB drivers ar working. but iv got no way of pushing the files onto it
NxsLS said:
I can connect the phone and lock n unlock the bootloader. so the USB drivers ar working. but iv got no way of pushing the files onto it
Click to expand...
Click to collapse
Have you tried flashing via fastboot? I would assume if fastboot oem unlock/lock works, then flashing using fastboot/android sdk should work.
...though, as a non dev, i have been wrong before
what do you mean by "pushing the files"? What are you trying to push?
Sent from my Galaxy Nexus using XDA App
Good, make sure you boot loader has been unlocked. You can use a program like the root toolkit (I don't think I can put a link to a different website) but he root toolkit for the nexus should help you push the stock image to your phone. Go to droid-life (.com, cough cough) and there is a set of instructions for returning back to stock. You can also use those same instructions to try and get her back up and running. Try the root toolkit they have on there, too. The only problem you might run into is having your phone set to USB debugging after unlocking the boot loader, bit it should still accept fast boot commands while I'm the bootloader
---------- Post added at 09:48 PM ---------- Previous post was at 09:42 PM ----------
sorry, by pushing the files I mean pushing the stock image file (the stock software, including the stock operating system, stock bootloader, and stock radios). A rom is a custom tweaked version of the stock software. When you unlock the bootloader, if you don't have stock software on there (which you wont if you were running a rom when it crashed) then it might erase everything, including the from you were running. You will have to push that stock software (stock image file) back to your phone using commands from your computer
no worrys o2 just sending me a new nexus :x
report lost n stolen :x only £30 ex
NxsLS said:
report lost n stolen :x only £30 ex
Click to expand...
Click to collapse
I hate that.. because you didn't know what you were doing and screwed up your phone someone is supposed to provide you with a new one? As a few posters have already said, it should be a fairly easy fix. You didn't even acknowledge that you tried any of the suggested fixes. If you're going to mess around with your phone make sure you know what you're doing, or at the very least exhaust all potential options to get yourself out of a soft brick. I'm sure an experienced Android user could have you up and running in 10 minutes. It's no wonder providers don't want to unlock bootloaders on some phones.. Jesus...
i tryed all i got it too boot back into the OS but reset itself and locked in google with unlocked padlock. so gave up and will not make the same mistake of not copying over the rom after the root n unlock.. i have flashed/unlocked my samsung s2 with ODIN which was easy but the Nexus i used Galaxy Nexus ToolKit
Hey
I know this is a greatly discussed topic but I have been through countless threads and tried everything so please bear with me! Long story short, my phone is in a massive rut at the moment and nothing seems to get it out of bootloop (tried fastboot, odin etc; yes I'm not an expert at all but I'm not exactly a noob). Odin is/was my last hope and for some reason Windows XP seems to keep crashing it the minute I hit start. I read through numerous posts on the Galaxy Nexus forum and have also tried numerous other methods including trying to go back to stock via fastboot and toolkits, trying to flash .img files individually etc etc etc and I basically need all the help I can get if someone wouldn't mind? The phone does turn on to fastboot and is detected on toolkits and drivers are fine.
For those who need the info its a i9250 GSM maguro (UK version i.e. without google wallet) running JB 4.1.1. I did try to flash maguro ICS 4.0.4 and when I go into fastboot, the bootloader version has changed to PRIMELA03 whereas I'm sure JB isn't that but I may be wrong! The phone crashed 2 nights ago and ever since then it gets stuck in bootloop when switched on, the images are noisy and fuzzy as if the phone has some kind of virus and nothing flashes on it! Fastboot just crashes requiring a battery removal all the time. Odin crashes too so I cannot flash any other firmware. The phone is not rooted but the bootloader is unlocked and I have no SD card (obviously).
Sorry if I have posted in the wrong thread or done anything I shouldn't have -_- I just need help so someone PLEASE guide me in the right direction!
Thank you in advance!!
Update: I just tried to flash JB back over the bootloader version and it changed from PRIMELA03 to PRIMELC03 so the bootloader version does change however nothing else seems to flash!
Update 2: Think i finally managed to mess my phone up. Got the yellow exclamation mark triangle between a phone and pc -__- anyone have any insight on how to go around this? Everything I have read up has more or less got to do with all other variants of Gnex other than GSM!
Read this thread
http://forum.xda-developers.com/showthread.php?t=1925468
Sent from my i9250
bk201doesntexist said:
Read this thread
http://forum.xda-developers.com/showthread.php?t=1925468
Sent from my i9250
Click to expand...
Click to collapse
Tried this last night, even now, OMAP works when the phone is connected and runs the .bat file perfectly however it has NO effect on the phone, as soon as I try to boot it just comes up with the > phone!PC < screen, however ODIN does detect the phone so I am convinced it isn't a full brick! Odin however doesn't go through the process of flashing it just says FAIL in red on top once I start the process because I cannot get the phone into download mode or fastboot.
Devzz said:
Tried this last night, even now, OMAP works when the phone is connected and runs the .bat file perfectly however it has NO effect on the phone, as soon as I try to boot it just comes up with the > phone!PC < screen, however ODIN does detect the phone so I am convinced it isn't a full brick! Odin however doesn't go through the process of flashing it just says FAIL in red on top once I start the process because I cannot get the phone into download mode or fastboot.
Click to expand...
Click to collapse
Question from me, how did you get fastboot to work on your windows xp?
Keeps crashing as soon as I want to open it on mine
Sent from my R800i using xda premium
slim207rc said:
Question from me, how did you get fastboot to work on your windows xp?
Keeps crashing as soon as I want to open it on mine
Sent from my R800i using xda premium
Click to expand...
Click to collapse
Well I didn't use the conventional way; I had a the Wugs nexus toolkit (Yes I know xda doesn't take kindly to toolkits but I only use it to launch the ADB command prompt cos I don't really know how to use the SDK toolkit method) from which I launched the command prompt and used fastboot commands through that to try flash .img files to the phone. Unfortunately it all failed even when I could access fastboot. Now Odin doesn't let me flash anything either; It just says failed.
Sorry if this doesn't answer your question but that's how I went about doing the whole fastboot bit If you mean it crashes when you open cmd maybe try launch cmd through Wugs?
Devzz said:
Well I didn't use the conventional way; I had a the Wugs nexus toolkit (Yes I know xda doesn't take kindly to toolkits but I only use it to launch the ADB command prompt cos I don't really know how to use the SDK toolkit method) from which I launched the command prompt and used fastboot commands through that to try flash .img files to the phone. Unfortunately it all failed even when I could access fastboot. Now Odin doesn't let me flash anything either; It just says failed.
Sorry if this doesn't answer your question but that's how I went about doing the whole fastboot bit If you mean it crashes when you open cmd maybe try launch cmd through Wugs?
Click to expand...
Click to collapse
I'll just have to give it a shot. Thanks anyways though:thumbup:
Sent from my R800i using xda premium
slim207rc said:
I'll just have to give it a shot. Thanks anyways though:thumbup:
Sent from my R800i using xda premium
Click to expand...
Click to collapse
No problem
I will send you $50 via paypal if you can either instruct me how to fix it, or if i can mail you the phone and you return it back to me in working order.
I just got the phone. And i have spent the whole weekend reading and following what others have suggested in this forum to no avail.
I wanted to install TWRP onto it. I followed the instruction to unlock the bootloader first int the dev settings, then in the fastboot screen. When i unlocked it i got the yellow triangle, telling me to relock it, that the system cannot check for corruption, etc. It would not move past this screen. I had to reboot. It would not enter any recovery.
I tried flashing back the stock recovery from fastboot, from the stock images, i would not go past this screen. It would not boot into the system.
I then went to try to get back to stock with the instructions from this thread:
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Phone will not boot, it hangs at the "google" start screen. I can not unlock bootloader from fastboot now. It gives a "DENIED" message, unable to oem unlock bootloader.
In a windows machine, the phone will not be recognized. Under device manager, its listed under 'other devices' as 'android' and the driver fails to load. Under download mode, the LG drivers will work. I can only get in download mode on a Windows machine. I can only get to fastboot on a MacOS machine through terminal.
Please help, i am going to throw this phone in the trash otherwise. I will answer any questions you may have that will help solve this.
Turn on your windows machine
Download the tool in this link http://forum.xda-developers.com/nexus-5x/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258492
Put your phone in download mode
Open the tool, click on the home button "Flash stock + unroot" and check the box under it that says "bricked"
Problem solved
since you have installed TWRP do as written HERE.
It is confirmed that is working for nexus 5x too, read the whole thread anyway!
Caligula36 said:
In a windows machine, the phone will not be recognized. Under device manager, its listed under 'other devices' as 'android' and the driver fails to load.
Click to expand...
Click to collapse
Wug's may work for you. It may not. I've used it since its inception but have found issues with it off and on. As far as drivers go, my Windows 10 machine seems to have issues since last few updates. So far, (I have a rooted N5, N9, and complete stock 5X) updating the drivers through device manager has worked every time. Choose update from on drivers on PC then run through update on both drivers shown under android interface (or similar). Be sure the device is awake and connected when updating, of course.
Sent from my Nexus 9 using Tapatalk
ritchea said:
Wug's may work for you. It may not. I've used it since its inception but have found issues with it off and on. As far as drivers go, my Windows 10 machine seems to have issues since last few updates. So far, (I have a rooted N5, N9, and complete stock 5X) updating the drivers through device manager has worked every time. Choose update from on drivers on PC then run through update on both drivers shown under android interface (or similar). Be sure the device is awake and connected when updating, of course.
Click to expand...
Click to collapse
First of all, no need to pay anything, at least to me. Where are you from? We can try with TeamViewer but i don't have pc right now so if you don't find a solution, i can help you from Wednesday evening onwards.
Sent from my Nexus 5X using XDA Labs
Matt__BB said:
Turn on your windows machine
Download the tool in this link http://forum.xda-developers.com/nexus-5x/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258492
Put your phone in download mode
Open the tool, click on the home button "Flash stock + unroot" and check the box under it that says "bricked"
Problem solved
Click to expand...
Click to collapse
Which stock image should i be using? The .tot file? The OTA or factory image?
Matt__BB said:
Turn on your windows machine
Download the tool in this link http://forum.xda-developers.com/nexus-5x/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258492
Put your phone in download mode
Open the tool, click on the home button "Flash stock + unroot" and check the box under it that says "bricked"
Problem solved
Click to expand...
Click to collapse
NO PROBLEM NOT SOLVED.
I cannot get a connection to fastboot on Windows. Only on Mac through terminal. I can only get into download mode on windows. When i try to unlock bootloader on my Mac, it give a DENIED error.
Stevica Smederevac said:
First of all, no need to pay anything, at least to me. Where are you from? We can try with TeamViewer but i don't have pc right now so if you don't find a solution, i can help you from Wednesday evening onwards.
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
Thank you, i will take you up on that offer.
This is the only thing that comes up when i connect via fastboot, this and a drivers not installed alert. I CAN NOT install them manually, the dialog just says the Windows could not find the drivers.
Issue resolved. Mods can remove this thread.
Caligula36 said:
Issue resolved. Mods can remove this thread.
Click to expand...
Click to collapse
Nice:good:
Sent from my Nexus 5X using XDA Labs
Great!
Sent from my Nexus 9 using Tapatalk
What did you do to fix this?
Sent from my Nexus 5X using Tapatalk
Hey guys,
I've got a Oneplus 3 that freezes every time it tries to boot. Fastboot and recovery are still working, factory reset makes no difference. After sideloading the latest OxygenOs the screen just goes blank after the Oneplus splash screen and recovery doesn't work anymore. The MsmDownloadTool only gets me where I started, back at the bootloop. So the old OOS gives me bootloop with recovery and fastboot while the new OOS only gives me fastboot and a blank screen.
New system with old working boot and recovery gives "md5 checksum failed".
The bootloader is locked and as long as I can't get in the settings there is no way to unlock it, so my options are pretty limited here.
I've contacted Oneplus but they aren't really helping either.
Is there any way to get this thing back to life?
Robert1852 said:
Hey guys,
I've got a Oneplus 3 that freezes every time it tries to boot. Fastboot and recovery are still working, factory reset makes no difference. After sideloading the latest OxygenOs the screen just goes blank after the Oneplus splash screen and recovery doesn't work anymore. The MsmDownloadTool only gets me where I started, back at the bootloop. So the old OOS gives me bootloop with recovery and fastboot while the new OOS only gives me fastboot and a blank screen.
New system with old working boot and recovery gives "md5 checksum failed".
The bootloader is locked and as long as I can't get in the settings there is no way to unlock it, so my options are pretty limited here.
I've contacted Oneplus but they aren't really helping either.
Is there any way to get this thing back to life?
Click to expand...
Click to collapse
https://forum.xda-developers.com/on...mega-unbrick-guide-hard-bricked-t3405700/amp/
That always works.. use method 2
dmilz said:
https://forum.xda-developers.com/on...mega-unbrick-guide-hard-bricked-t3405700/amp/
That always works.. use method 2
Click to expand...
Click to collapse
Not this time... That is the tool I mentioned, only gets me back to the bootloop
Robert1852 said:
Not this time... That is the tool I mentioned, only gets me back to the bootloop
Click to expand...
Click to collapse
I know what you talking about.. Went through that too when i used method one.. use method 2..it will flash stock OOS and you will boot successfully
If you already did..try once more..download the tools over again
dmilz said:
I know what you talking about.. Went through that too when i used method one.. use method 2..it will flash stock OOS and you will boot successfully
If you already did..try once more..download the tools over again
Click to expand...
Click to collapse
Yeah already tried method 2 multiple times, downloaded the tools again but it still doesn't work on this phone..
Robert1852 said:
Yeah already tried method 2 multiple times, downloaded the tools again but it still doesn't work on this phone..
Click to expand...
Click to collapse
Ooh ok.. i see.. hope you will find a way out
Robert1852 said:
Yeah already tried method 2 multiple times, downloaded the tools again but it still doesn't work on this phone..
Click to expand...
Click to collapse
Probably a stupid question but have you tried flashing oxygen os recovery and then tried to flash stock ROM?
Xceeder said:
Probably a stupid question but have you tried flashing oxygen os recovery and then tried to flash stock ROM?
Click to expand...
Click to collapse
That unbrick tool also flashes the stock recovery. I cant flash anything using fastboot because the bootloader is locked
Robert1852 said:
That unbrick tool also flashes the stock recovery. I cant flash anything using fastboot because the bootloader is locked
Click to expand...
Click to collapse
And why is it locked then? Why would you ever relock your bootloader? You should be able to unlock it anyway without going in to settings. Are you sure you are using the correct drivers? Windows installs the wrong once by default.
Puddi_Puddin said:
And why is it locked then? Why would you ever relock your bootloader? You should be able to unlock it anyway without going in to settings. Are you sure you are using the correct drivers? Windows installs the wrong once by default.
Click to expand...
Click to collapse
It has never been unlocked. In the settings is the "Allow OEM Unlock" option which you should check before you can unlock the bootloader. As long as I can't boot the phone I can't check this option, or someone must know a workaround. Yes I'm pretty sure I'm using the correct drivers
Robert1852 said:
It has never been unlocked. In the settings is the "Allow OEM Unlock" option which you should check before you can unlock the bootloader. As long as I can't boot the phone I can't check this option, or someone must know a workaround. Yes I'm pretty sure I'm using the correct drivers
Click to expand...
Click to collapse
If you plug your phone in how does it show up under Device Manager? Have you also tried "fastboot OEM Unlock"?
Puddi_Puddin said:
If you plug your phone in how does it show up under Device Manager? Have you also tried "fastboot OEM Unlock"?
Click to expand...
Click to collapse
When it's in the bootloader menu it shows up as "Android Bootloader Interface", when it's in EDL mode it shows up as "Qualcomm HS-USB QDLoader 9008 (COM3)". It connects fine with the pc and flashes everything without problems as far as I can see. Yeah it says "FAILED (remote: oem unlock is not allowed)" probably because the allow oem unlock option in the settings isn't checked.
Most likely won't do anything, but have you tried a different computer? Seems like it would make no difference but tiny things like that have saved me in the past.
ZVNexus said:
Most likely won't do anything, but have you tried a different computer? Seems like it would make no difference but tiny things like that have saved me in the past.
Click to expand...
Click to collapse
Yea I know what you mean I tried it on a few different computers, even with different cables but it doesn't make a difference...
Robert1852 said:
Yea I know what you mean I tried it on a few different computers, even with different cables but it doesn't make a difference...
Click to expand...
Click to collapse
Pretty sure you are using wrong drivers. You should be able to unlock the bootloader even tho it is remote. When I first bricked my phone I forgot about the drivers aswell. My phone booted up and showed. System: Failed, Userdata:Failed. This means it failed to detect those partitions which you can find in unbrick program itself called system.img, userdata.img. You can actually flash these manually with fastboot flash system system.img but I also got the "Remote is not allowed error". After booting into disabled Driver Signature Enforcement mode and changing the drivers from on the guide I could actually flash these partitions. Your phone has to show up as Qualcomm 9008 or something close and not as Android Interfere Device. I have helped multiple people fixing their phone with this guide and they also had a locked bootloader and they also did not have the correct drivers.
Boot into https://www.google.com/amp/s/www.ho...so-that-you-can-install-unsigned-drivers/amp/ then install the driver linked on the Unbrick Guide. Your phone should show up correctly. Then run the unbrick guide as admin and it should go through flawless.
Puddi_Puddin said:
Pretty sure you are using wrong drivers. You should be able to unlock the bootloader even tho it is remote. When I first bricked my phone I forgot about the drivers aswell. My phone booted up and showed. System: Failed, Userdata:Failed. This means it failed to detect those partitions which you can find in unbrick program itself called system.img, userdata.img. You can actually flash these manually with fastboot flash system system.img but I also got the "Remote is not allowed error". After booting into disabled Driver Signature Enforcement mode and changing the drivers from on the guide I could actually flash these partitions. Your phone has to show up as Qualcomm 9008 or something close and not as Android Interfere Device. I have helped multiple people fixing their phone with this guide and they also had a locked bootloader and they also did not have the correct drivers.
Boot into https://www.google.com/amp/s/www.ho...so-that-you-can-install-unsigned-drivers/amp/ then install the driver linked on the Unbrick Guide. Your phone should show up correctly. Then run the unbrick guide as admin and it should go through flawless.
Click to expand...
Click to collapse
Tried everything it says in the guide about the drivers (even the last part about installing the certificates) but it just keeps showing up as qualcomm hs-usb qdloader 9008, even though I'm pretty sure they are installed correctly. It just won't show up as Qualcomm 9008, as it is supposed to, whatever I try. But it looks like these drivers are only for the EDL mode, and as far as I know it is normal for the phone to show up as Android Bootloader Interface when it's in the bootloader menu. And you can't use fastboot from EDL mode... Will try it later again on a different pc though, really hope you are right about the drivers after all
Hi Robert,
I am having same problem with my oneplus3. I also tried both unbrick methods and tried different oxygen ROMs.
Are you able to fix your phone?
Thanks in Advance,
Anil
Have you tried this http://www.androidbrick.com/oneplus-one-two-3-3t-5-mega-unbrick-guide-twrp-flashing/
Robert1852 said:
Hey guys,
I've got a Oneplus 3 that freezes every time it tries to boot. Fastboot and recovery are still working, factory reset makes no difference. After sideloading the latest OxygenOs the screen just goes blank after the Oneplus splash screen and recovery doesn't work anymore. The MsmDownloadTool only gets me where I started, back at the bootloop. So the old OOS gives me bootloop with recovery and fastboot while the new OOS only gives me fastboot and a blank screen.
New system with old working boot and recovery gives "md5 checksum failed".
The bootloader is locked and as long as I can't get in the settings there is no way to unlock it, so my options are pretty limited here.
I've contacted Oneplus but they aren't really helping either.
Is there any way to get this thing back to life?
Click to expand...
Click to collapse
Hi
Go back to an older Version...3.xx
worked for me
be warned ..3.xxx formats internal memory
I also have the same problem, I'll try to restore to old version too.
Do you also have artifacts on the screen?
I've tried everything in my power to unlock this bootloader, and nothing is working. I've tried several different drivers by using device manager and selecting them, and all of them seem to allow my device to be recognized until I boot into fastboot. Then I get <waiting for any device> and nothing happens. I've updated my Android SDK to 8.0, as 8.1.0 won't install due to a mismatch of file sizes. My Pixel C is on 8.0. Any help would be much appreciated! Thank you
sabrdawg said:
I've tried everything in my power to unlock this bootloader, and nothing is working. I've tried several different drivers by using device manager and selecting them, and all of them seem to allow my device to be recognized until I boot into fastboot. Then I get <waiting for any device> and nothing happens. I've updated my Android SDK to 8.0, as 8.1.0 won't install due to a mismatch of file sizes. My Pixel C is on 8.0. Any help would be much appreciated! Thank you
Click to expand...
Click to collapse
Try the procedure by TheeWolf, https://forum.xda-developers.com/showthread.php?t=3236946
It worked for me on an N5 when every other nexus device I had worked in Fastboot.
Sent from my [device_name] using XDA-Developers Legacy app
Thank you for your reply! I actually just figured it out in the meantime. What I did was update the drivers WHILE in fastboot, and ADB finally recognized my device. I was then able to unlock my bootloader!