Just got my LG G Pad 8,.3 and when I try to boot into the bootloader (adb reboot bootloader) the devices reboots but comes right back into the OS.
Any ideas?
Same here... totally bone stock.
Similar issues when trying to get to stick recovery. I get the "dead" Android on his back with the red exclamation mark, but no key combo will get me to recovery
ej, did you ever solve this?
Cheers,
Su
ej_424 said:
Just got my LG G Pad 8,.3 and when I try to boot into the bootloader (adb reboot bootloader) the devices reboots but comes right back into the OS.
Any ideas?
Click to expand...
Click to collapse
do you have the developer options enabled? Do you have mtp enabled? Do you have debugging on?
when you type in adb devices, does your tablet show up, and have you enabled your computer to have access to your tablet?
go into settings and tap on build seven times to enable the developer options. Also, look at the thread for rooting your gpad in the general section.
Yes to all the above from me
Sumanji said:
Yes to all the above from me
Click to expand...
Click to collapse
Are you using windows or Linux? If Linux, check to see if you can access the bootloader through adb using root.
If using Linux, did you remember to set up the /etc/udev/rules.d folder for permissions on your computer?
I have the exact same problem here 'adb reboot recovery' works, but 'adb reboot bootloader' just does a regular reboot.
Anyone solve this?
sirianni said:
I have the exact same problem here 'adb reboot recovery' works, but 'adb reboot bootloader' just does a regular reboot.
Anyone solve this?
Click to expand...
Click to collapse
That's because to all intents we have no bootloader. It's locked. We are just fooling the tablet with the loki patch.
At least that's my understanding (and let's face it my understanding isn't much )
Sent from my LG-V500 using XDA Premium HD app
OK now I see that the thread I was reading was regarding the Google play edition. I guess the loki method is the only way of accessing the bootloader on the LG v500.
Sent from my LG-V500 using xda app-developers app
Related
My volume keys aren't working, and my phone is bootlooping after I tried to unroot it. The volume keys not working is a hardware issue. Is there anything I can do on the computer end to boot into the bootloader?
Thanks
Alec
Try to get adb to work for you.
If the system bootloops after adb service is brought up, you can try using 'adb reboot recovery' or 'adb reboot bootloader'.
If you made it, get back to stock and turn it in for the killing.
alec534 said:
My volume keys aren't working, and my phone is bootlooping after I tried to unroot it. The volume keys not working is a hardware issue. Is there anything I can do on the computer end to boot into the bootloader?
Thanks
Alec
Click to expand...
Click to collapse
bk201doesntexist said:
Try to get adb to work for you.
If the system bootloops after adb service is brought up, you can try using 'adb reboot recovery' or 'adb reboot bootloader'.
If you made it, get back to stock and turn it in for the killing.
Click to expand...
Click to collapse
It's bootlooping at the Google logo, and so adb isn't recognizing it. Frown. Thanks for your idea though.
alec534 said:
My volume keys aren't working, and my phone is bootlooping after I tried to unroot it. The volume keys not working is a hardware issue. Is there anything I can do on the computer end to boot into the bootloader?
Thanks
Alec
Click to expand...
Click to collapse
You can type adb reboot-bootloader in a command prompt. You can also download Quick Boot from the market, and you can reboot into the bootloader from your device.
EDIT: Oops, I took to long in replying... didn't see that it was already suggested.
EDIT 2: Mis-read your post. Think you are out of luck.
Sent from my Galaxy Nexus using Tapatalk
efrant said:
You can type adb reboot-bootloader in a command prompt. You can also download Quick Boot from the market, and you can reboot into the bootloader from your device.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
All I get is a "device not found" error. Adb doesn't seem to recognize the phone while it's bootlooping.
You can buy a jig for it to force it into boot loader. I also used it on mine to force it into boot loader download. Purchased one just in case something bad happened.
http://www.amazon.com/gp/aw/d/B0053...ile?redirect=true&ref_=oh_o00_s00_i00_details
Sent from my Galaxy Nexus using Tapatalk
purelife82 said:
You can buy a jig for it to force it into boot loader. I also used it on mine to force it into boot loader download. Purchased one just in case something bad happened.
http://www.amazon.com/gp/aw/d/B0053...ile?redirect=true&ref_=oh_o00_s00_i00_details
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
You are a life-saver if this works on the Nexus too. Thanks so much.
its works on my nexus.
Sent from my Galaxy Nexus using Tapatalk
My side buttons is not working for me.(the volume keys)
Any one know any way to boot to recovery?
i have a logo loop now.so i can't enter to the system.
help:crying:
ilia333 said:
My side buttons is not working for me.(the volume keys)
Any one know any way to boot to recovery?
i have a logo loop now.so i can't enter to the system.
help:crying:
Click to expand...
Click to collapse
Use adb from bootlooping screen. The command is "adb reboot recovery". Adb is part of android SDK. There are plenty of guides on how to set up adb out there and its easy.
Sent from my Inspire 4G using xda premium
Gizmoe said:
Use adb from bootlooping screen. The command is "adb reboot recovery". Adb is part of android SDK. There are plenty of guides on how to set up adb out there and its easy.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
"device not found"
i hjave to enter to fastboot mod but i can't.
ilia333 said:
My side buttons is not working for me.(the volume keys)
Any one know any way to boot to recovery?
i have a logo loop now.so i can't enter to the system.
help:crying:
Click to expand...
Click to collapse
As Gizmoe told you..use adb commands to achive that. Use the guide in my signature to see how that is done. :good:
---------- Post added at 11:53 AM ---------- Previous post was at 11:52 AM ----------
ilia333 said:
"device not found"
i hjave to enter to fastboot mod but i can't.
Click to expand...
Click to collapse
Make sure that you have usb debugging enabled and the driver is installed correctly (with the phone unplugged)
glevitan said:
Make sure that you have usb debugging enabled and the driver is installed correctly (with the phone unplugged)
Click to expand...
Click to collapse
It is but i have to be in Hboot to apply the adb commands
ilia333 said:
It is but i have to be in Hboot to apply the adb commands
Click to expand...
Click to collapse
You can run adb from pretty much anywhere. Even if you were stuck in the splashscreen or in the rom.
Sent from a dream.
Teichopsia said:
You can run adb from pretty much anywhere. Even if you were stuck in the splashscreen or in the rom.
Sent from a dream.
Click to expand...
Click to collapse
but how can i check that usb debugging enabled?
if i cant accese the system?
ilia333 said:
but how can i check that usb debugging enabled?
if i cant accese the system?
Click to expand...
Click to collapse
You don´t to have be in hboot to use adb. You have to be with the phone on normally or from the splash screen itself. If you are in hboot then choose fastboot and try from there but using fastboot devices command instead.
As long as you have not factory reseted the phone the usb debugging drivers will stay in the phone.
ilia333 said:
but how can i check that usb debugging enabled?
if i cant accese the system?
Click to expand...
Click to collapse
USB debugging should always be enabled by default in any custom Rom. The thing that will disable it is doing factory reset from hboot screen. But you can't get there anyways so it should be enabled. Start the phone as normal and let it go to splash screen. Plug into pc and be sure to check that pc sees the phone. If not, unplug phone. Uninstall drivers. Re install drivers and then plug phone back in. From adb type "adb devices". You should see your device. After that run the "adb reboot recovery". If it still doesn't see it plug phone into different port. Preferably one that goes straight into mother board and remove any other USB devices that are plugged in.
Sent from my Inspire 4G using xda premium
glevitan said:
You don´t to have be in hboot to use adb. You have to be with the phone on normally or from the splash screen itself. If you are in hboot then choose fastboot and try from there but using fastboot devices command instead.
As long as you have not factory reseted the phone the usb debugging drivers will stay in the phone.
Click to expand...
Click to collapse
any other way to enable it ?
I did a factory reset.
i just installed a new rom.
thank you for trying to help any way/
Go to settings>Applications>development and check USB debugging.
If you're still getting device not recognized, you should reinstall HTC drivers by reinstalling HTC sync. ( if you haven't installed those in the first place, then you won't be able to use adb unless you do)
ilia333 said:
any other way to enable it ?
I did a factory reset.
i just installed a new rom.
thank you for trying to help any way/
Click to expand...
Click to collapse
When you say "factory reset," do you mean that you ran a RUU? Or that you chose "factory reset" in recovery, so you still have a custom ROM installed? If the answer is the latter, you probably have USB Debugging enabled. Just give ADB a try.
bananagranola said:
When you say "factory reset," do you mean that you ran a RUU? Or that you chose "factory reset" in recovery, so you still have a custom ROM installed? If the answer is the latter, you probably have USB Debugging enabled. Just give ADB a try.
Click to expand...
Click to collapse
I have a custom ROM.i did a factory reset from the recovery.
But i have message that "device not found".
ilia333 said:
I have a custom ROM.i did a factory reset from the recovery.
But i have message that "device not found".
Click to expand...
Click to collapse
Do you have the HTC sync drivers installed? If not, you should be able to find guides for it, like glevitan said.
bananagranola said:
Do you have the HTC sync drivers installed? If not, you should be able to find guides for it, like glevitan said.
Click to expand...
Click to collapse
Thank You guys !!!!
I did it.
From fuly turned off phone.
Weird, but hey. Whatever works. Glad you got it.
Sent from my Inspire 4G using xda premium
Bump Bump Bump!!!
I have the same problem with HTC Desire HD!
And guess what? It belongs to my wife!!! And I have to give it back to her or I should stay several nights
in the street.... and instead of a pillow I should put a cat or something under my head!
Problem.... Stuck at htc boot screen... not able to enter recovery
I installed 4ext recovery ages ago....
the main problem is that the volume keys ( both up and down ) are broken and neither of them work!
adb restart recovery doesn't work
no device find!
yes I installed all the drivers, and I can boot other phones into recovery
What should I do?
Please help!
tanx!
hrkh83 said:
Bump Bump Bump!!!
I have the same problem with HTC Desire HD!
And guess what? It belongs to my wife!!! And I have to give it back to her or I should stay several nights
in the street.... and instead of a pillow I should put a cat or something under my head!
Problem.... Stuck at htc boot screen... not able to enter recovery
I installed 4ext recovery ages ago....
adb restart recovery doesn't work
no device find!
yes I installed all the drivers, and I can boot other phones into recovery
What should I do?
Please help!
tanx!
Click to expand...
Click to collapse
How did you end like this? can you access hboot?
glevitan said:
How did you end like this? can you access hboot?
Click to expand...
Click to collapse
How?
I installed the R26.2 successfully, the JB Rom I mean..
Then installed all the tweaks in PIMP my ride successfully again ( I am not a noob.... )
That didn't triggered it...
At the end I was trying to install Int2ext+ and it happened....! I don't know why!
I had done this before on various phones.... I don't know what happened!
The only thing I was able to access so far was HTC BOOT SCREEN! :laugh: and I also
can access a choke hold from my wife soon I guess!
I don't know why these things always happen to her phone... other friends phones are fine when
I change their roms bla bla bla!
hrkh83 said:
How?
I installed the R26.2 successfully, the JB Rom I mean..
Then installed all the tweaks in PIMP my ride successfully again ( I am not a noob.... )
That didn't triggered it...
At the end I was trying to install Int2ext+ and it happened....! I don't know why!
I had done this before on various phones.... I don't know what happened!
The only thing I was able to access so far was HTC BOOT SCREEN! :laugh: and I also
can access a choke hold from my wife soon I guess!
I don't know why these things always happen to her phone... other friends phones are fine when
I change their roms bla bla bla!
Click to expand...
Click to collapse
Pull the battery and then put it back. And try to boot, pressing power + volume down until you get hboot.
Sent from my GT-N7000 using xda app-developers app
I have a GSM galaxy nexus and I have a big problem. My android keyboard stopped working and my device is encrypted so when I restarted it today I couldn't get past the screen to decrypt my phone.
I would normally try to get into recovery and flash a new keyboard or something of that nature but my volume down button no longer works and I can't fix it (i've tried).
I really just want to get my data off of the phone but I can't think of anything at this point.
Suggestions?
Adb reboot recovery or a USB jig to get you into download mode.
Sent from my Nexus 7 using xda app-developers app
Adb won't work and i ordered a jig but if i use Odin. I lose all my data. Any other ideas?
Is fastboot/bootloader available through 'adb reboot bootloader' by any chance? If not, you'll loose all your data.
Sent from my i9250
bk201doesntexist said:
Is fastboot/bootloader available through 'adb reboot bootloader' by any chance? If not, you'll loose all your data.
Sent from my i9250
Click to expand...
Click to collapse
No i cant get to adb because of the encryption lock screen. Fudge, i was hoping there was another way.
Hi guys,
I have an huge issue! Last week I flashed 4.3 slim rom and, at the beginning everything was good, but, later on I used Titanium Back to restore apps and settings and, from there on, my problems started! In fact, after that, my Gnex was not able to start and remains on the bootanimation all the time. I already had this problem when I passed from 4.1 to 4.2 but now I have a further issue that is that vol - button doesn't work! So I cannot start the phone in fastboot mode with the procedure vol+/vol-/power buttons.
I tried to follow this guide:
http://forum.xda-developers.com/showthread.php?t=2400171
but it doesn't work for my problem, so I ask you if you know any alternative mode to start fastboot mode by using PC with some toolkit.
Very thank you, I hope you will be able to help me!:laugh:
Go toolkits go
adb reboot-bootloader
Guys, can you explaine me better, please?
Connect your phone to the laptop, and then type the command I posted earlier in the command prompt.
Hoping you have the drivers set up properly.
Sent from my Galaxy Nexus using Tapatalk 4
Unfortunatly it didn't work
gebedias said:
Unfortunatly it didn't work
Click to expand...
Click to collapse
If it didn't work, likely there would be an error message.
cupfulloflol said:
If it didn't work, likely there would be an error message.
Click to expand...
Click to collapse
I am using Win XP and it says that "it is impossible to find adb file" (this is a my translation from italian...)
gebedias said:
I am using Win XP and it says that "it is impossible to find adb file" (this is a my translation from italian...)
Click to expand...
Click to collapse
Do you have adb installed? If not, that is your problem.
gebedias said:
I am using Win XP and it says that "it is impossible to find adb file" (this is a my translation from italian...)
Click to expand...
Click to collapse
You don't have adb tools installed. Download them.
Sent from my Galaxy Nexus using Tapatalk 4
I have a new Nexus 7 2013 Wifi (4.4.0 build KRT16S) that I'm trying to root. I'm new at this, but I've been reading posts for a couple of days.
I'm using the SkipSoft Android Toolkit. I've unlocked ok. I've enabled USB debugging okay. I've selected Superuser by Clockworkmod, it detects ADB mode, reboots to Fastboot mode okay, then asks if I'm unlocked and have enabled USB debugging- I have.
Then it says that it's booting into Android using an Insecure Boot Image... downloading "boot.img." Reports "OKAY [ 0.228s]" then reports:
"booting..."
And that's where it sits forever. The Nexus is in Fastbook Mode with the Android guy on his back. I can power off the Nexus 7 and it comes up okay. I tried the alternative root method with the same results.
Thoughts?
kennybellew said:
I have a new Nexus 7 2013 Wifi (4.4.0 build KRT16S) that I'm trying to root. I'm new at this, but I've been reading posts for a couple of days.
I'm using the SkipSoft Android Toolkit. I've unlocked ok. I've enabled USB debugging okay. I've selected Superuser by Clockworkmod, it detects ADB mode, reboots to Fastboot mode okay, then asks if I'm unlocked and have enabled USB debugging- I have.
Then it says that it's booting into Android using an Insecure Boot Image... downloading "boot.img." Reports "OKAY [ 0.228s]" then reports:
"booting..."
And that's where it sits forever. The Nexus is in Fastbook Mode with the Android guy on his back. I can power off the Nexus 7 and it comes up okay. I tried the alternative root method with the same results.
Thoughts?
Click to expand...
Click to collapse
I tried on a different PC, thinking it might be the USB driver, as I did have some initial problems getting that to work. It also hung at the same spot reporting that it was "booting..."
I tried going through the process with Nexus Root Toolkit and finally got it to work on the second PC with that.
So, my issue is resolved (in that I got it rooted another way); however, someone else may have this issue, so any suggestions might still help someone else.
HELP please!
kennybellew said:
I have a new Nexus 7 2013 Wifi (4.4.0 build KRT16S) that I'm trying to root. I'm new at this, but I've been reading posts for a couple of days.
I'm using the SkipSoft Android Toolkit. I've unlocked ok. I've enabled USB debugging okay. I've selected Superuser by Clockworkmod, it detects ADB mode, reboots to Fastboot mode okay, then asks if I'm unlocked and have enabled USB debugging- I have.
Then it says that it's booting into Android using an Insecure Boot Image... downloading "boot.img." Reports "OKAY [ 0.228s]" then reports:
"booting..."
And that's where it sits forever. The Nexus is in Fastbook Mode with the Android guy on his back. I can power off the Nexus 7 and it comes up okay. I tried the alternative root method with the same results.
Thoughts?
Click to expand...
Click to collapse
Hi Kenny,
My Nexus 4 is doing EXACTLY the same thing. Is it safe to quit and reboot? I don't want to damage the bootloader!!
Thanks in advance.
Kurt
I recommend flashing superuser using twrp
Sent from my Nexus 7 using XDA Premium 4 mobile app