Related
My soft brick Verizon gnex is giving me a bit of trouble. It was stock, locked, and all those other things that you all probably frown upon, but worked fine for me and I had not reason to change this. It got stuck in a boot loop and a hard reset and wipe didn't do anything. I found efrant's guide and got everything set up. fastboot devices results in a correct read of my device and I can run fastboot reboot-bootloader, which I did as a check to make sure computer to phone commands were working fine.
The problem is that when I run fastboot oem unlock, I get the unlock bootloader?, can scroll to "Yes" and then my phone gets stuck there...indefinitely. I've let it go for up to two hours and don't get anywhere. If I terminate with a battery pull/ unplug, I get a "too many links" error. Running wug's toolkit does the same thing. Rebooting into fastboot works, but the phone is still locked. If I select "No" on the unlock screen, I get the Google splash forever. Any suggestions?
i hate to ask this question... but...
when you scrolled to yes, did you press the power button to accept the selection?
Zepius said:
i hate to ask this question... but...
when you scrolled to yes, did you press the power button to accept the selection?
Click to expand...
Click to collapse
I wish the solution were that easy (though if I were that stupid....yikes). I did hit the power button and cannot scroll to No. The device is really just stuck there. My cmd prompt is just hanging (...) too. I suppose it could be that the communication is only going one way (computer to phone) but somehow isn't going phone-to-computer. I've tried different drivers/cords/USB ports, but (right now) don't have another computer that I can play around on.
I may give it one last driver reinstall try, but it's looking like Odin is the way to go?
molgator24 said:
My soft brick Verizon gnex is giving me a bit of trouble. It was stock, locked, and all those other things that you all probably frown upon, but worked fine for me and I had not reason to change this. It got stuck in a boot loop and a hard reset and wipe didn't do anything. I found efrant's guide and got everything set up. fastboot devices results in a correct read of my device and I can run fastboot reboot-bootloader, which I did as a check to make sure computer to phone commands were working fine.
The problem is that when I run fastboot oem unlock, I get the unlock bootloader?, can scroll to "Yes" and then my phone gets stuck there...indefinitely. I've let it go for up to two hours and don't get anywhere. If I terminate with a battery pull/ unplug, I get a "too many links" error. Running wug's toolkit does the same thing. Rebooting into fastboot works, but the phone is still locked. If I select "No" on the unlock screen, I get the Google splash forever. Any suggestions?
Click to expand...
Click to collapse
I aint a grave digger , I can see the post date but Have you found Solution yet ?? I am myself stuck there ?
herecomesmaggi said:
I aint a grave digger , I can see the post date but Have you found Solution yet ?? I am myself stuck there ?
Click to expand...
Click to collapse
No dice. Samsung offered to let me send it back, but I never got around to it. If you send yours in and/or figure it out, let me know and I may turn my current paperweight into something usable. Best of luck, and sorry I don't have more to offer!
OK thanks for clearing that out. I have tried everything, it seems that memory is corrupted and that's why bootloader can't format it and is stuck at unlocking... I will update if I found anything.
Avoid Spells!!! "Auto correct : ON"
So I tried using the wugfresh toolkit last nigh to root since from what I've read all the nexus devices use the same method to unlock the bootloader and such. This was likely a mistake. After figuring out I had to change the device to PtP I managed to get to the unlock bootloader screen on the device, at which point it became unresponsive. I turned it off completely, and at that point it wouldn't boot at all, it would just sit on the nexus logo forever. I also couldn't fastboot, holding down the power, volume up and volume down buttons seemed to do nothing. So I let it run down last night in hopes of starting on a fresh charge. Now the device doesn't seem to want to charge at all. I plugged it into both my computer and wall charger through the usual usb cable, and the screen isn't showing any indication of charging. All I saw was the notification light blinking in short bursts after initially plugging it in, and now not even that is happening.
Ideas?
Reboot to recovery and wipe dalvik, cache and system and reboot
Sent from my Nexus 7 using xda premium
Simer03 said:
Reboot to recovery and wipe dalvik, cache and system and reboot
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
If you wipe system, what exactly are you expecting to reboot into???
je
Simer03 said:
Reboot to recovery and wipe dalvik, cache and system and reboot
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Exactly....I can't reboot into recovery because I can't fastboot into anything. I'm not sure how this helps.
destructobob said:
Exactly....I can't reboot into recovery because I can't fastboot into anything. I'm not sure how this helps.
Click to expand...
Click to collapse
A few points.
First, this is why I highly discourage 'toolkits', especially on Nexus devices. There simply is no reason to use them and many reasons not. It is much wiser to learn how to do things manually, as it makes troubleshooting problems much easier and is less likely to cause a problem. For example, to unlock the bootloader, you could have issued a single command to accomplish it.
Second, as I don't use toolkits, I can't say exactly how the one you used works, but it most likely automates that 'fastboot oem unlock' command, which IS the same for both N7 versions. If so, it shouldn't have caused you any issues.
Third, assuming all you did was attempt to unlock the bootloader - and not flash any custom stuff, root the device, etc. - you should not be running into this issue. If you did try something else, that could certainly explain some of the problems you have. There is certainly a possibility that your device is defective. It it truly won't charge or function at all, I would highly recommend you return it for a new one. If it's dead, there should be no reason why they won't take it back.
Next time, I would recommend doing things the old fashioned way .
phonic said:
A few points.
First, this is why I highly discourage 'toolkits', especially on Nexus devices. There simply is no reason to use them and many reasons not. It is much wiser to learn how to do things manually, as it makes troubleshooting problems much easier and is less likely to cause a problem. For example, to unlock the bootloader, you could have issued a single command to accomplish it.
Second, as I don't use toolkits, I can't say exactly how the one you used works, but it most likely automates that 'fastboot oem unlock' command, which IS the same for both N7 versions. If so, it shouldn't have caused you any issues.
Third, assuming all you did was attempt to unlock the bootloader - and not flash any custom stuff, root the device, etc. - you should not be running into this issue. If you did try something else, that could certainly explain some of the problems you have. There is certainly a possibility that your device is defective. It it truly won't charge or function at all, I would highly recommend you return it for a new one. If it's dead, there should be no reason why they won't take it back.
Next time, I would recommend doing things the old fashioned way .
Click to expand...
Click to collapse
It turns on, it's on at the moment actually. It's been sitting at the nexus logo for about ten minutes. And I still can't load into fastboot, holding down those three buttons does nothing. I'm not even sure why the device froze at the unlock screen. I'm trying to start up the old fashioned way right now, following this link http://forum.xda-developers.com/showthread.php?t=2379618
I've managed to make my way to the platform tools folder in a command line, but running the reboot bootloader command there does nothing. It simply says device not found. I don't think my computer is even seeing the n7 properly so it can't reboot it. I don't think its defective, but I don't know where to begin to fix this using the old fashioned way either....
phonic said:
A few points.
First, this is why I highly discourage 'toolkits', especially on Nexus devices. There simply is no reason to use them and many reasons not. It is much wiser to learn how to do things manually, as it makes troubleshooting problems much easier and is less likely to cause a problem. For example, to unlock the bootloader, you could have issued a single command to accomplish it.
Second, as I don't use toolkits, I can't say exactly how the one you used works, but it most likely automates that 'fastboot oem unlock' command, which IS the same for both N7 versions. If so, it shouldn't have caused you any issues.
Third, assuming all you did was attempt to unlock the bootloader - and not flash any custom stuff, root the device, etc. - you should not be running into this issue. If you did try something else, that could certainly explain some of the problems you have. There is certainly a possibility that your device is defective. It it truly won't charge or function at all, I would highly recommend you return it for a new one. If it's dead, there should be no reason why they won't take it back.
Next time, I would recommend doing things the old fashioned way .
Click to expand...
Click to collapse
I second all that's been said here. While toolkits can seem attractive, it's really quite simple, and much safer to do it manually once your take an hour to learn your way around the Android-SDK (way easier than it sounds, I promise).
I like toolkits, seriously, but they hardly ever work. I usually have to drop to a shell prompt and run the commands manually anyway.
Sent from Nexus 7 XHD using XDA Premium HD
destructobob said:
It turns on, it's on at the moment actually. It's been sitting at the nexus logo for about ten minutes. And I still can't load into fastboot, holding down those three buttons does nothing. I'm not even sure why the device froze at the unlock screen. I'm trying to start up the old fashioned way right now, following this link http://forum.xda-developers.com/showthread.php?t=2379618
I've managed to make my way to the platform tools folder in a command line, but running the reboot bootloader command there does nothing. It simply says device not found. I don't think my computer is even seeing the n7 properly so it can't reboot it. I don't think its defective, but I don't know where to begin to fix this using the old fashioned way either....
Click to expand...
Click to collapse
To get into bootloader mode, you hold down POWER+VOLDOWN - not all three buttons. Make sure you turn off your device first (hold down power until it shuts off), then hold down those two buttons.
If it gets to the nexus logo, that means your bootloader should be OK, which means you can probably recover.
The 'adb reboot bootloader' command will not work until the device is booted up, your turned on developer mode and USB debugging, and you allowed your computer to connect.
Assuming you can get into bootloader, look to see if you did successfully unlock it or not. If you didn't, try the 'fastboot oem unlock' command.
If you continue to be unable to boot normally, you will likely need to flash the system image. There is one floating around here (system.img). You can do this in the bootloader as well (fastboot flash system system.img).
hadisious said:
I second all that's been said here. While toolkits can seem attractive, it's really quite simple, and much safer to do it manually once your take an hour to learn your way around the Android-SDK (way easier than it sounds, I promise).
Click to expand...
Click to collapse
I understand that and have absolutely learned my lesson. What's confusing me at the moment is installing the drivers listed in the link I posted. All that's there is a zip file, no exe or anything which is what I'm used to for installers. I was able to reboot my nexus 7 into bootloader before with the toolkit, so I know I had the drivers installed properly at some point. The toolkit installed a universal ADB set which I'm thinking should work. I don't know what to do to get the device into bootloader to follow the instructions.
phonic said:
To get into bootloader mode, you hold down POWER+VOLDOWN - not all three buttons. Make sure you turn off your device first (hold down power until it shuts off), then hold down those two buttons.
If it gets to the nexus logo, that means your bootloader should be OK, which means you can probably recover.
The 'adb reboot bootloader' command will not work until the device is booted up, your turned on developer mode and USB debugging, and you allowed your computer to connect.
Assuming you can get into bootloader, look to see if you did successfully unlock it or not. If you didn't, try the 'fastboot oem unlock' command.
If you continue to be unable to boot normally, you will likely need to flash the system image. There is one floating around here (system.img). You can do this in the bootloader as well (fastboot flash system system.img).
Click to expand...
Click to collapse
So I'm able to get into the bootloader, but its not responding to the command line entries. My computer brings a popup anytime the nexus tries to do a regular boot, where it just sits at the logo. The popup explains that the device is unrecognized. I've uninstalled any devices that resemble the nexus in device manager, and have tried repeatedly to update the driver manually by pointing it to the usb driver folder within the sdk. Doing that simply says windows is unable to locate the correct driver. So I think my device is where it needs to be, I just can't connect to it from the command line at the moment.
First of all, what made you try the toolkit(effective as it is) on the new Nexus...? Couldn't you just sit down for a day or two enjoying stock experience(abominative as it is)...?
alicarbovader said:
First of all, what made you try the toolkit(effective as it is) on the new Nexus...? Couldn't you just sit down for a day or two enjoying stock experience(abominative as it is)...?
Click to expand...
Click to collapse
Unlocking the bootloader will always result in your device getting wiped.
So it makes sense that you do this first, this way you don't need to setup your device twice.
It also has nothing to do with stock vs custom. I have an unlocked bootloader, custom recovery and am rooted. But my device is still completely stock as far as the OS goes. The only thing I might change in the future is a custom kernel, as I am usually fine with things 'stock' from a user perspective on Nexus.
phonic said:
Unlocking the bootloader will always result in your device getting wiped.
So it makes sense that you do this first, this way you don't need to setup your device twice.
It also has nothing to do with stock vs custom. I have an unlocked bootloader, custom recovery and am rooted. But my device is still completely stock as far as the OS goes. The only thing I might change in the future is a custom kernel, as I am usually fine with things 'stock' from a user perspective on Nexus.
Click to expand...
Click to collapse
Honestly I had completely forgot that the initial unlocking does the factory reset. I got caught up in booting up the device and installing a few apps to try it out, to the point that I completely blanked on the reset haha.
I tried a bunch of different roms and verions on my gnexus and old N7, jumping between CM and PA mostly, and I got used to just having a backup ready and not worrying about a data wipe. I've mostly stuck with PA because the pie controls are fantastic on both devices and I've come to get used to the added screen space. I'm perfectly fine with the stock experience outside of pie controls, but I do love customizing my device and the custom roms allow for so much freedom in that regard.
destructobob said:
I understand that and have absolutely learned my lesson. What's confusing me at the moment is installing the drivers listed in the link I posted. All that's there is a zip file, no exe or anything which is what I'm used to for installers. I was able to reboot my nexus 7 into bootloader before with the toolkit, so I know I had the drivers installed properly at some point. The toolkit installed a universal ADB set which I'm thinking should work. I don't know what to do to get the device into bootloader to follow the instructions.
Click to expand...
Click to collapse
Okay... so its a zip file.... go to device manager and it should show you some android driver or nexus 7 or something.... right-click on that and choose update drivers... choose manual method and select the folder hat you unzipped...
then use fastboot to flash factory image...
Q: is factory image for nexus 4 2013 available
??
shengovind said:
Okay... so its a zip file.... go to device manager and it should show you some android driver or nexus 7 or something.... right-click on that and choose update drivers... choose manual method and select the folder hat you unzipped...
then use fastboot to flash factory image...
Q: is factory image for nexus 4 2013 available
??
Click to expand...
Click to collapse
I actually got it successfully up and running, unlocked and rooted and everything. The screen and dual speakers alone justify the price for sure, and the speed difference is noticeable. Riptide 2 seems to run alot smoother on this than my old N7. I'm also aware that in general a clean install runs better than something that's been used for a while, so perhaps that's part of my percieved performance gains. In any case I'm more than happy with my purchase, and am looking forward to getting my chromecast tomorrow!
destructobob said:
I actually got it successfully up and running, unlocked and rooted and everything. The screen and dual speakers alone justify the price for sure, and the speed difference is noticeable. Riptide 2 seems to run alot smoother on this than my old N7. I'm also aware that in general a clean install runs better than something that's been used for a while, so perhaps that's part of my percieved performance gains. In any case I'm more than happy with my purchase, and am looking forward to getting my chromecast tomorrow!
Click to expand...
Click to collapse
:good::good::good:
phonic said:
Unlocking the bootloader will always result in your device getting wiped.
So it makes sense that you do this first, this way you don't need to setup your device twice.
It also has nothing to do with stock vs custom. I have an unlocked bootloader, custom recovery and am rooted. But my device is still completely stock as far as the OS goes. The only thing I might change in the future is a custom kernel, as I am usually fine with things 'stock' from a user perspective on Nexus.
Click to expand...
Click to collapse
Yes but you should've waited for a suitable toolkit.
alicarbovader said:
Yes but you should've waited for a suitable toolkit.
Click to expand...
Click to collapse
Why would I wait for a toolkit?
This is a Nexus device. You don't need a toolkit. All you need is two brain cells and a willingness to learn. You can unlock, flash custom recovery and root in a matter of minutes with nothing other than the Android SDK. Toolkits cause more problems than they solve.
phonic said:
Why would I wait for a toolkit?
This is a Nexus device. You don't need a toolkit. All you need is two brain cells and a willingness to learn. You can unlock, flash custom recovery and root in a matter of minutes with nothing other than the Android SDK. Toolkits cause more problems than they solve.
Click to expand...
Click to collapse
ok, not a toolkit.. I give you that, but was the stock experience too intimidating...?
personally, i'd nuked htc sense when i got thoroughly bored with its great buttery ui. i like the aosp experience, rooted or not.
and i didn't know that we don:t need toolkits fpr nexus devices, cuz i've never happened to own one.
I have been looking for the past couple days and have not found an obvious answer for my issue. So hopefully this isn't an answered repeat but if so pleas link ^-^.
I received my HTC One M8 dev edition the other day and was hoping to get it unlocked with probably cynogenmod installed while it was fresh but I am having issues with the bootloader unlock. So far I am able to get my unlock code from HTC and when I flash it the command window shows success but I never receive the prompt on the phone to commit to the unlock. I found out the hard way that it didn't auto accept since I soft bricked installing twrp and no longer have access to the recovery even after reflashing a stock one (but at least I have phone access again).
Has anyone had and found a solution to this problem? I was really looking forward to having a nice custom rom but seem to be stuck with the factory dev edition which is still loads better than the carrier edition. I will consider a non HTC bootloader unlock if I have to but the dev unlock seems nice and easy.
Hopefully some one can just tell me I did something retarded and all will be good ^-^.
Also I have tried Squabbi's toolkit but it ends up the same way, but less command prompts.
Thanks
Dlome said:
I have been looking for the past couple days and have not found an obvious answer for my issue. So hopefully this isn't an answered repeat but if so pleas link ^-^.
I received my HTC One M8 dev edition the other day and was hoping to get it unlocked with probably cynogenmod installed while it was fresh but I am having issues with the bootloader unlock. So far I am able to get my unlock code from HTC and when I flash it the command window shows success but I never receive the prompt on the phone to commit to the unlock. I found out the hard way that it didn't auto accept since I soft bricked installing twrp and no longer have access to the recovery even after reflashing a stock one (but at least I have phone access again).
Has anyone had and found a solution to this problem? I was really looking forward to having a nice custom rom but seem to be stuck with the factory dev edition which is still loads better than the carrier edition. I will consider a non HTC bootloader unlock if I have to but the dev unlock seems nice and easy.
Hopefully some one can just tell me I did something retarded and all will be good ^-^.
Also I have tried Squabbi's toolkit but it ends up the same way, but less command prompts.
Thanks
Click to expand...
Click to collapse
You should be able to enter recovery by going to fastboot and using the volume keys to navigate to the recovery option, and picking it by pressing the power button.
To enter fastboot with your phone on, hold down the power button and vol. up until your phone turns off (20 seconds or so). AS SOON AS IT TURNS OFF, switch to power button and vol. down. Then go to the recovery option, and you are in.
And while you are in fastboot, you might as well try running the unlock key again. If it doesn't work, go back to HTCDev for another. I'm not sure how that works, but I think you could get another code if you can't get this one to work.
xunholyx said:
You should be able to enter recovery by going to fastboot and using the volume keys to navigate to the recovery option, and picking it by pressing the power button.
To enter fastboot with your phone on, hold down the power button and vol. up until your phone turns off (20 seconds or so). AS SOON AS IT TURNS OFF, switch to power button and vol. down. Then go to the recovery option, and you are in.
And while you are in fastboot, you might as well try running the unlock key again. If it doesn't work, go back to HTCDev for another. I'm not sure how that works, but I think you could get another code if you can't get this one to work.
Click to expand...
Click to collapse
Currently when I try to enter recovery it enters a boot loop and freezes on the HTC screen. From what I read this is from trying to install a custom recovery with a locked bootloader. That part I can live with for now since it does not seem to be an issue, just the outcome of my mistake. My biggest issues seems to be the bootloader unlock not working. unless the two are related which could be as I am fairly new to this process.
Dlome said:
Currently when I try to enter recovery it enters a boot loop and freezes on the HTC screen. From what I read this is from trying to install a custom recovery with a locked bootloader. That part I can live with for now since it does not seem to be an issue, just the outcome of my mistake. My biggest issues seems to be the bootloader unlock not working. unless the two are related which could be as I am fairly new to this process.
Click to expand...
Click to collapse
So, have you tried the code again? And/or have you gone back to the HTCDev site for a new unlock code?
I have tried two unlock tokens so far and tried both of them several times. It's almost like I'm submitting something wrong and don't know it. When I submit the token I am including both the start and end brackets which is what it appears to be asking for and not just the string between them.
Dlome said:
I have tried two unlock tokens so far and tried both of them several times. It's almost like I'm submitting something wrong and don't know it. When I submit the token I am including both the start and end brackets which is what it appears to be asking for and not just the string between them.
Click to expand...
Click to collapse
Are you copying and pasting the very first part of the code?
The part that looks like:
"(bootloader) < please cut following message >
(bootloader)" ?
IMMEDIATELY after that is what you copy and paste.
The copy should start when it says "<<<< identifier token start >>>>"
I am only copying the <<<< identifier token start >>>> and <<<< identifier token end >>>> along with the string between and leaving out the bootloader tag that is on each line.
I guess one question I should be asking is are there any settings on the phone that I need to set? I have developer options activated, usb debugging on, and the fastboot option unchecked in the power settings. Other than that the phone is stock settings. I remember my s4 needed to be in a specific usb connection mode but since they are completely different phones im not sure if that will apply here.
Dlome said:
I guess one question I should be asking is are there any settings on the phone that I need to set? I have developer options activated, usb debugging on, and the fastboot option unchecked in the power settings. Other than that the phone is stock settings. I remember my s4 needed to be in a specific usb connection mode but since they are completely different phones im not sure if that will apply here.
Click to expand...
Click to collapse
You seem to be doing everything right. I'm stumped. Hopefully someone else comes along with a solution. @redpoint73?
That's what I was afraid of haha. I don't know why but while I am no expert in this area I do not feel I'm ignorant either yet I always seem to have problems even when I follow the steps correctly >.<
I do appreciate the troubleshooting greatly thank you. I will keep trying things and see what I can find and if I figure it out you bet I will add it here because I can't be the only one getting stuck haha.
Can you please post the results of
fastboot getvar all
Make sure you remove your IMEI before posting.
xunholyx said:
Hopefully someone else comes along with a solution. @redpoint73?
Click to expand...
Click to collapse
Ummm, yeah . . . in fact I think I do:
Maybe I'm missing something here. But the Dev Edition comes already bootloader unlocked, and therefore should be no reason to do so.
I think the prompt to unlock never comes up on the phone, since its already unlocked.
---------- Post added at 10:20 AM ---------- Previous post was at 10:19 AM ----------
bloodhawk said:
Can you please post the results of
fastboot getvar all
Make sure you remove your IMEI before posting.
Click to expand...
Click to collapse
Yes, this will tell us a lot.
Or boot into bootloader and just see if it says LOCKED, RELOCKED or UNLOCKED.
I bet it says UNLOCKED.
Hello. I am having some issues with Nexus 5X and was hoping someone could help possibly fix it, if it's even fixable.
I bought the phone from a used store for pretty cheap On march 5th this year.
Tuesday night i was surfing on google chrome app and all of a sudden the entire thing froze up on screen couldn't get it to do anything what so ever so i tried powering it down and rebooting it. Well i got it to power down but then it went into a constant boot loop where it just kept rebooting to the "Google" screen and then it wouldnt get any further. Eventually it ceased doing that after about 5-10 minutes and then i was unable to get the device to do anything, couldn't even get into the bootloader menu. Battery was at 55% when this all started and phone had been working very good prior. Last night i tried to get it to turn on again and this time i noticed a red flashing light on the bottom speaker. I have seen this one before on other nexus devices so i plugged it in and got the charging screen to come up, i let it charge full and then went to try and start it with no luck of getting it to do anything. Today i have managed to get it to simple Boot to the Google screen but it remains their for a few momments then shuts off and does nothing else, sometimes it goes into a constant repeat of that, i hear it's called a boot loop.
I am not sure what the issue is. What i wanna know is if it's an easy fix or not.
Thanks
**Update***
i was able to get it to finally go into to the bootloader screen, but have no clue what to do here, clicking restart just goes back to the same problems.
If you haven't already tried you could try doing a search for Nexus 5x BLOD or Nexus 5x bootloop of death, this may not be the issue but it will give you something to compare the symptoms your device has. There should also be plenty of info on any workarounds there are available to try and get your device back up and running.
Hope that helps
Ok will do thank you
Following thread https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
installed 4Coreoreo fix, but am having issues getting to to flash boot
Command window stays stuck on < waiting for device > and the phone is doing nothing, just sitting in the Bootloader menu
says fastboot mode
secure boot enabled
device state locked
am i missing something? Am thinking the bootloader is locked
unable to do an oem unlock because i can't get it to boot into the os.
Yep your bootloader is locked and sounds like USB debugging needs to be enabled also if ADB is not finding your device using commands 'adb devices' or 'fastboot devices'.
Have another look through the BLOD threads as from what I remember you may need to cool the device right down to get it to boot to system fully to be able to enable OEM unlocking and USB debugging.
Keep searching, and good luck
Edit: I see you posted in the 4 core thread and got it to boot temporarily and OEM unlocked, just try again and enable usb debugging and you should be on to a winner.
junglism93 said:
Yep your bootloader is locked and sounds like USB debugging needs to be enabled also if ADB is not finding your device using commands 'adb devices' or 'fastboot devices'.
Have another look through the BLOD threads as from what I remember you may need to cool the device right down to get it to boot to system fully to be able to enable OEM unlocking and USB debugging.
Keep searching, and good luck
Edit: I see you posted in the 4 core thread and got it to boot temporarily and OEM unlocked, just try again and enable usb debugging and you should be on to a winner.
Click to expand...
Click to collapse
Ty for the reply, unfortunately even after enabling everything i still can't get fastboot to do anything but < waiting for device >
I think she done, sadly. My nexus 4 has lasted longer then this one, even that phone has its issues tho, like to randomally reboot itself sometimes, others the screen suddenly won't come on (lots of battery life) and it is hard to reboot but usually does. And it's 6 years old lol
Gibson295 said:
Ty for the reply, unfortunately even after enabling everything i still can't get fastboot to do anything but < waiting for device >
I think she done, sadly. My nexus 4 has lasted longer then this one, even that phone has its issues tho, like to randomally reboot itself sometimes, others the screen suddenly won't come on (lots of battery life) and it is hard to reboot but usually does. And it's 6 years old lol
Click to expand...
Click to collapse
No problem, other than trying a different usb port, cables or updating your ADB and fastboot if you haven't already it sounds like it's the end of the road for your 5x.
Leave it in a cupboard for a few days and give it a go another time, you never know. I've still got my Nexus 4, new battery time for mine but it still runs like a charm lol.
Hi, I'm new to XDA. I am trying to get a rooted device so I can play around with it and do cool things. After trying 4 different phones and weeks of nonstop research and attempts, I decided to an Amazon Fire 8 Plus (10th Generation). I know how to unlock bootloader using windows 10 and android sdk. The one problem is that I can't enable OEM unlocking. When I tried fastboot flashing unlock anyway, my tablet got stuck in fastboot mode. Basically, what happens is, I turn it on, nothing suspicious there, but after I confirm it when I get the warning message, it INSTANTLY turns back off. Tinkering around with date and time, software updates, rebooting, and toggle developer options did nothing. I even went as far as disabling the lock screen so it doesn't make me enter my pin when I try to turn it on - still nothing! I am very desperate and tired of all this rooting, it would be nice to get some help!
Also, I think I can use this video
to root if I figure out to get to that temp directory command thing the guy entered. I use windows ten, but can't find how to get to that place.
An answer to either question would be much appreciated, thanks!
Zeek347 said:
Hi, I'm new to XDA. I am trying to get a rooted device so I can play around with it and do cool things. After trying 4 different phones and weeks of nonstop research and attempts, I decided to an Amazon Fire 8 Plus (10th Generation). I know how to unlock bootloader using windows 10 and android sdk. The one problem is that I can't enable OEM unlocking. When I tried fastboot flashing unlock anyway, my tablet got stuck in fastboot mode. Basically, what happens is, I turn it on, nothing suspicious there, but after I confirm it when I get the warning message, it INSTANTLY turns back off. Tinkering around with date and time, software updates, rebooting, and toggle developer options did nothing. I even went as far as disabling the lock screen so it doesn't make me enter my pin when I try to turn it on - still nothing! I am very desperate and tired of all this rooting, it would be nice to get some help!
Also, I think I can use this video
to root if I figure out to get to that temp directory command thing the guy entered. I use windows ten, but can't find how to get to that place.
An answer to either question would be much appreciated, thanks!
Click to expand...
Click to collapse
You will find more accurate information about it in the specific device's forum https://forum.xda-developers.com/c/amazon-fire-hd-8-and-hd-10.4709/ I guess you choose the more problematic OEM to start tinkering with, Amazon is not such good for rooting and modding.