Database Info

[Q] USB Not Working in Bootloader

I have an old Nexus S that runs painfully slow. No amount of factory resetting helps so I want to perform a full wipe with a clean factory image install and unlock the bootloader while I am at it. I am using the Nexus Root Toolkit and the drivers have installed and are working correctly. However, once my phone reboots into the bootloader USB does not seem to be detected and the operation fails. Starting with my phone on with USB debugging enabled, I have no problem using the ADB quick tools in the Nexus Toolkit to list devices and reboot via ADB. Performing a full driver test runs fine until the phone reboots to the bootloader, then I get a fastboot error. Also, in the bootloader beneath the boot options near the bottom of the screen is this text:
Code:
USB Control Init
USB Control Init end
Another stranger thing is that the volume buttons also don't work in the bootloader, but they work fine when the phone is on. It is weird that these two hardware functions don't work in the bootloader but work fine in the OS. Could this be a software problem in the bootloader itself?

red_skittles said:
I have an old Nexus S that runs painfully slow. No amount of factory resetting helps so I want to perform a full wipe with a clean factory image install and unlock the bootloader while I am at it. I am using the Nexus Root Toolkit and the drivers have installed and are working correctly. However, once my phone reboots into the bootloader USB does not seem to be detected and the operation fails. Starting with my phone on with USB debugging enabled, I have no problem using the ADB quick tools in the Nexus Toolkit to list devices and reboot via ADB. Performing a full driver test runs fine until the phone reboots to the bootloader, then I get a fastboot error. Also, in the bootloader beneath the boot options near the bottom of the screen is this text:
Code:
USB Control Init
USB Control Init end
Another stranger thing is that the volume buttons also don't work in the bootloader, but they work fine when the phone is on. It is weird that these two hardware functions don't work in the bootloader but work fine in the OS. Could this be a software problem in the bootloader itself?
Click to expand...
Click to collapse
(These are only suggestions)
Try another cable, another usb point on the computer, unplugging and replugging the usb into the phone while in bootloader, try pressing the power button to reload the bootloader, try installing another driver from NRTK, try booting into the bootloader from a powered off state while connected to the computer.. Good luck

Setting.Out said:
(These are only suggestions)
Try another cable, another usb point on the computer, unplugging and replugging the usb into the phone while in bootloader, try pressing the power button to reload the bootloader, try installing another driver from NRTK, try booting into the bootloader from a powered off state while connected to the computer.. Good luck
Click to expand...
Click to collapse
No luck with any of these suggestions. As a test I booted my Nexus 7 into the bootloader plugged in the USB. My PC immediately made the chime noise to let me know a USB device had been plugged in. This is not the case when the Nexus S is plugged in while in the bootloader. Windows Device Manager also doesn't recognize the NExus S when it is in the bootloader.
The fact that USB isn't a problem in the OS leads me to believe this isn't hardware related. Is there a way to update/reflash the bootloader from on the device without using fastboot?

red_skittles said:
No luck with any of these suggestions. As a test I booted my Nexus 7 into the bootloader plugged in the USB. My PC immediately made the chime noise to let me know a USB device had been plugged in. This is not the case when the Nexus S is plugged in while in the bootloader. Windows Device Manager also doesn't recognize the NExus S when it is in the bootloader.
The fact that USB isn't a problem in the OS leads me to believe this isn't hardware related. Is there a way to update/reflash the bootloader from on the device without using fastboot?
Click to expand...
Click to collapse
I don't know if there is a phone bootloader update..?? Have you tried the "bricked" option?.. I am sure that you have already backed upp all your data, as unlocking the phone wipes it..

Phone Off, Battery Indicator Screen

Does anyone know how to enable the charging screen that appears when you're phone is charging while off? For some reason it doesn't want to turn on, on my phone and instead comes up with the OnePlus logo with "Powered by Android" screen while charging.
Thanks.

Do you have the Chinese model? What result do you get from this command?
Code:
fastboot oem device-info
Transmitted via Bacon

same here
timmaaa said:
Do you have the Chinese model? What result do you get from this command?
Code:
fastboot oem device-info
Transmitted via Bacon
Click to expand...
Click to collapse
I have an international 64gb opo but I have got the same issue any idea?

I have the same issue as stated in this thread.
Battery charging icon gone pls help
Didn't find any solution thought..

b.dut said:
I have an international 64gb opo but I have got the same issue any idea?
Click to expand...
Click to collapse
One idea would be to post the results of the command.
Transmitted via Bacon

timmaaa said:
Do you have the Chinese model? What result do you get from this command?
Code:
fastboot oem device-info
Transmitted via Bacon
Click to expand...
Click to collapse
Nah, the International Model.
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
But I have to add, I noticed that the "Charger screen enabled: false" was on when I first saw the screen and during that time the charging screen would appear so I ignored it. I have a feeling it could be due to Franco Kernel somehow or TWRP because those are the only 2 things I've flashed since I recall the charger screen working.

Kerjifire said:
Nah, the International Model.
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
But I have to add, I noticed that the "Charger screen enabled: false" was on when I first saw the screen and during that time the charging screen would appear so I ignored it. I have a feeling it could be due to Franco Kernel somehow or TWRP because those are the only 2 things I've flashed since I recall the charger screen working.
Click to expand...
Click to collapse
Just flash the stock kernel and see if it works again. The battery images are in the stock kernel ramdisk. You can check the /res directory where they should be.
I have a worse problem with no-one helping :
https://forums.oneplus.net/threads/no-charging-animation-while-powered-off.101980/#post-5402277
Someone ?
Thomas

not seen that issue yet, but will keep an eye out for it.

Stuck on Google logo, no recovery mode, bootloader is locked

Hi guys,
So here is the problem I've encountered, -
During the routine news reading on my phone (Nexus 5 32Gb), I've got the warning message from Clean Master app saying that "Your phone is too hot", and afterwards the phone made a self reboot. Now it is stuck on "Google" logo and doesn't go past it.
I feel obligated to mention that this is not the first time I have received this warning message, but it is indeed the first time my phone made a self-reboot since I started using it (almost 10 month).
Since my phone's bootloader has never been unlocked and device isn't rooted, I tried to perform factory reset via stock Recovery mode. But it appears that this option is not available for me since when I am trying to go to Recovery via the Bootloader menu options - all I get is a black screen with no indications whatsoever.
Additional info and problems I've encountered:
- I am running stock firmware (4.4.4) - KTU84P
- I cannot connect to the device via ADB (probably because USB debugging is off or due to the fact that I cannot boot to android.)
Next course of actions:
- I've decided to flash the factory firmware image via fastboot.
- In order to do that I need to unlock bootloader first (or so I've been told during my research).
- I used the "fastboot oem unlock" command and I've got the following result:
OKAY [ 47.189s]
finished. total time: 47.191s
At this point phone is in Bootloader mode and the Lock State is "unlocked"
- Phone wasn't automatically rebooted, so I've entered "fastboot reboot" command - phone switched off
- Since phone is turned off, I turn it back on --> same situation with being stuck on the "Google" logo.
- Booting device into Bootloader mode --> "Lock State - locked" once again. Meaning - I didn't actually unlock the bootloader.
I've found only one thread on XDA which mentions the same problem as mine with 95% similarity of the "symptoms", but it is unresolved.
At this point I am frustrated, because I cannot really go anywhere without unlocked bootloader. No custom recovery, no flashing images, etc. Since I am a basically a noob, there is a huge chance I am missing something, - I am actually crossing fingers on that one.
Guys,
I would really appreciate any help, idea or/and advice on this issue.
Cheers.

OK. Adb only works in android or custom recovery so that's never going to work. USB debugging is only for within Android itself but this is irrelevant.
If you unlocked the BL and rebooted and its locked again, that means usually that the internal NAND is fried.
You can try and flash stock using the LG flash tool method (you can get to it via signature) however since the device was also overheating, I wouldn't expect it to work and need to be RMA'd / repaired
Sent from my Nexus 5 using Tapatalk

Get it repaired under warranty. Seems like a hardware issue to me.
Or As said by rootsu... Rma it

OK. Adb only works in android or custom recovery so that's never going to work. USB debugging is only for within Android itself but this is irrelevant. <br />
<br />
If you unlocked the BL and rebooted and its locked again, that means usually that the internal NAND is fried. <br />
<br />
You can try and flash stock using the LG flash tool method (you can get to it via signature) however since the device was also overheating, I wouldn't expect it to work and need to be RMA'd / repaired <br />
<br />
Sent from my Nexus 5 using Tapatalk<br/>
Thank you,
I'll definitely try LG flash tool, just for the sake of last resort option before turning to RMA/repair procedures.
Get it repaired under warranty. Seems like a hardware issue to me. <br />
Or As said by rootsu... Rma it<br/>
Thanks man,
Any issue that is hardware related is bad news unfortunately...
Thanks again for your input.
I'll update the status after trying LG flash tool.

Arc reactor ....... This exact same issue happened to me on Saturday night. Everything you described. I don't know if master cleaner had something to do with it, like taking out the recovery or what not. I know there are options on there to go in depth and cleaning recovery files. I have been racking my brain since Saturday trying to figure this out. Like you said, you boot up the phone, it gets stuck at google splash screen, so you go into bootloader moder then to recovery and there is NO RECOVERY. The screen is black.
My USB debugging was not on before this issue happened and I cannot get the phone to power past the boot screen in order to enable it. I also tried using fastboot to push files to the device, but it keeps saying failed .
Then I can use fastboot oem lock command to lock the bootloader and when you reboot into bootloader mode the device remains unlocked after just locking it.

As previously mentioned, USB debugging has nothing to do with any of this.
Sent from my Nexus 5 using Tapatalk

rootSU said:
As previously mentioned, USB debugging has nothing to do with any of this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Just giving my exact symptoms of what state my phone was is in. Sorry I posted....

xBigMikex said:
Just giving my exact symptoms of what state my phone was is in. Sorry I posted....
Click to expand...
Click to collapse
I'm just trying to help you and anyone else reading that the USB debugging setting is a red herring and you shouldn't pay any attention to it of you can't boot. I'm trying to help you, no need to throw it back in my face.
Jeez, why do I waste my time helping, teaching and writing guides for the ungrateful?!
Sent from my Nexus 5 using Tapatalk

rootSU said:
I'm just trying to help you and anyone else reading that the USB debugging setting is a red herring and you shouldn't pay any attention to it of you can't boot. I'm trying to help you, no need to throw it back in my face.
Jeez, why do I waste my time helping, teaching and writing guides for the ungrateful?!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I am not going to go there with you... thanks for your help. I just came on here to see if I could find a solution to a problem.

If your bootloader remains unlocked, try lg flash tool. If that doesn't resolve it, it needs sending for repair.
Sent from my Nexus 5 using Tapatalk

Nvidia shield boot on charge carputer

Hello guys, I have looked for days and days for a solution... Could only find a solution if the tablet was a Nexus 7 or a Samsung device. I looked into the system files for anything remotely similar but unfortunately could not.
So do the great minds that are here able to help me ? So that the tablet will boot on a power input? Booting down is achieved by using an app so all I need is to boot the tablet. The tablet is a 2014 shield, rooted with cwm on 5.1.1
I am not a developer so will need a little hand holding but can usually achieve things, I would of thought somebody would have tryed this before considering the price of the tablet...
Can this be achieved by modifying a system file or does it have to be done on the bootloader ? If so can you please help.
I use the tablet mainly for in car diagnostics, and also media so want it to auto boot on power. All wiring is done just need a final little help. Regards BT

I doubt you will get your tablet to boot on charge, as it would require modifying the bootloader (wich is, AFAIK, not open-source).
But you can try some alternative, for example, don't shut it down, just let it sleep instead of powering it off. With the right settings you can get almost 0% discharge (Wifi off when screen off, turn bluetooth off, disable syncing, airplane mode, ...)
By default, the tablet screen turn on when on charge.

Cheers I will give that a try, I will see if I can get it working as you described above, what would you advise using tasker?
To anybody else;
I have tried running the : fastboot oem off-mode-charge 0 command through Minimal ADB. But unfortunately it comes back saying;
(bootloader) Unknown Command!
OKAY [ 0.029s]
finished. total time: 0.033s
When I test some other commands such as 'fastboot devices' it comes back with the correct serial so I am communicating with the device, and when I do 'fastboot oem unlock' It comes back saying unlocked too. But running 'fastboot oem device-info' again returns an unknown command... So is this a problem with what I am doing or the shield tablet not being compatible?

I've tried everything but my phone just won't turn on

Yesterday I tried to update my phone to android 6.0 but something must have gone wrong during the process because now my phone is stuck in a bootloop, I've tried as hard as i can to fix it but nothing is working. I tried to do a hard factory reset and wiped my phones memory but it won't turn on, I really don't know what to do because I cannot afford to get a new phone.

ineedhelplz said:
Yesterday I tried to update my phone to android 6.0 but something must have gone wrong during the process because now my phone is stuck in a bootloop, I've tried as hard as i can to fix it but nothing is working. I tried to do a hard factory reset and wiped my phones memory but it won't turn on, I really don't know what to do because I cannot afford to get a new phone.
Click to expand...
Click to collapse
If you can get into the bootloader, reflash your firmware to get it back to working condition.

damianx5 said:
If you can get into the bootloader, reflash your firmware to get it back to working condition.
Click to expand...
Click to collapse
Yes I can get into the bootloader but my computer isn't recognizing that my phone is plugged in, it just says charging

ineedhelplz said:
Yes I can get into the bootloader but my computer isn't recognizing that my phone is plugged in, it just says charging
Click to expand...
Click to collapse
Make sure you have all the drivers installed and that you have adb and fastboot files as well.

If you still cant access to transfer files, search for "adb push and pull" commands at google to directly send files to and from your devices.

I am having the same issue!
Here is the difference:
Updated phone to the new OS and my phone went into a boot loop. Booted my phone in Fastboot to try to Factory Reset, it won't reset, it just goes back into Boot Loop... *sobs* I've looked everywhere to find a solution to the following problem, and I'm posting here in order to avoid making unnecessary forums.
My Issue:
As stated above, I updated my phone and it went into boot loop. I am trying to flash it to the previous version, but because I can not factory reset my phone I can not flash my phone. I can not unlock the Bootloader because my USB Debugging is disabled and can not be enabled because my phone is bricked.
I've tried clearing the cache - wipe_data | wipe_cache | fastboot format userdata
I've tried
C:\Users\Name\AppData\Local\Android\android-sdk\platform-tools>fastboot devices
********** fastboot (serial number)
C:\Users\Name\AppData\Local\Android\android-sdk\platform-tools>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.546s]
writing 'recovery'...
OKAY [ 2.699s]
finished. total time: 3.245s
C:\Users\Name\AppData\Local\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Users\Name\AppData\Local\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
Only to later find it did not work due to my Bootloader being Locked...
Here's what I'd like to know: How do I Factory Reset my phone OR Unlock my Bootloader from my computer? Heck, why not tell me both, I can really use the help as this is my only phone and Motorola REFUSED to fix my phone due to some magical liquid damage... to a water resistant phone... that was never once touched by liquid of any kind... but I digress... [...vents on]
About my Phone:
Model XT1548
Rooted: No
Bootlader: Locked
Flashed: No (I believe)
Cause of Problem: Update to Marshmallow
_________________________________________________________
BTW: I made a new thread for this because I wasn't sure if posting here would get any help. HERE

Could you get it working?