I have a LG stylo 4 and i was trying to root it, well i saw here that some had problems doing so, but i gave it a shot, i was able to enable OEM unlock, and usb debugging, i found boot.img file and i was about to root.
But when i plugged in the phone to my pc and opened adb and entered the command "adb reboot fastboot" the phone just restarted normally. i tried "adb reboot recovery" i the screen saying "no command".
Now the only thing i got to work with adb was to use sideload, when i did this, i got adb to be able to talk to the device.
im wondering if i can use sideload to root the phone?
Related
I cant seem to ADB from the bootloader. It works fine when the Xoom is on but when i enter "adb reboot bootloader" it reboots in to boot loader and stops working.
I have the necessary drivers as its showing "Mot Single ADB Interface" under device manager.
When i enter adb devices its saying "list of devices attached" but there is no device under it.
When i enter "adb get-state" it comes back with "UNKNOWN"
Please help
When you say that it stops working, are you trying to enter other ADB commands or are you using fastboot? I've just tried all of the same commands as you have entered and I get the exact same results. It seems to me (and I'm by no means an expert in adb having just learnt the basics so far) that in bootloader the standard ADB commands do not work. Once in bootloader it seems that you need to use the fastboot commands to flash an img file.
Also, in bootloader mode the xoom is no longer recognised by the pc, just press vol up + popwer and it should reboot, or I guess you could also enter fastboot reboot to do the same thing.
Hello.
Earlier today I wanted to try a new JB rom to replace ICS so I transfered it into SD card and tried to reboot into recovery.
Instead of getting to recovery, I got stuck in fastboot mode, so I'm assuming recovery has been damaged.
After a whole afternoon of researching this forum I tried for several times this tutorial in order to install a recovery and afterwards a ROM (http://forum.xda-developers.com/showthread.php?t=1088046) and similar ones in both Mac OS X and Windows 7 (tried both USB 2.0 and USB 3.0 so its not a problem from USB) and I didn't succeed at all.
When I am using Windows 7, when I use "fastboot erase recovery", I keep receiving this message "waiting device". If I write "fastboot devices", I don't get results.
When using Mac OS X, I can get via command line to the folder "platform-tools" where fastboot is located but if I write "fastboot erase recovery" or something, it says "command not found". I've read it could be because I have to set fastboot as an environmental variable, but I having trouble setting it (Mac OS Lion).
Thank you so much for reading. Please help me!!! Any clues would be really appreciated!
-----
UPDATE: I finally managed to communicate with the device.
I used the following commands from this tutorial http://androidforums.com/optimus-m-all-things-root/382525-guide-get-out-fastboot-mode-2.html
fastboot erase boot
fastboot erase recovery
fastboot erase system
fastboot flash recovery
The problem is, now I'm stuck at LG Logo, can't access fastboot... Please help, I think it's even worse now.
boot rom, pull out battery and boot normal, it does or not? if it does use terminal emulator or adb push to install custom recovery, adb will work in fastboot if you had checked android debugging
http://forum.xda-developers.com/showthread.php?t=1007244
http://forum.xda-developers.com/showthread.php?t=1146566
grigtm said:
boot rom, pull out battery and boot normal, it does or not? if it does use terminal emulator or adb push to install custom recovery, adb will work in fastboot if you had checked android debugging
http://forum.xda-developers.com/showthread.php?t=1007244
http://forum.xda-developers.com/showthread.php?t=1146566
Click to expand...
Click to collapse
I don't understand what you mean by boot rom. Every time I turn on the phone, (normal or as POWER+HOME+VOL DOWN) it goes into fastboot. When I pull out the battery, and power again it goes again into fastboot...
techdani said:
I don't understand what you mean by boot rom. Every time I turn on the phone, (normal or as POWER+HOME+VOL DOWN) it goes into fastboot. When I pull out the battery, and power again it goes again into fastboot...
Click to expand...
Click to collapse
ok, read here http://forum.xda-developers.com/showthread.php?t=1088046 do exactly what says in this thread
So my LG G2 popped up a message telling me there was an update available (yay lollipop). Having TWRP installed I didn't take the update at first. However, I found an app that allows you to switch between a custom recovery and a stock recovery. When I switched to stock, I booted into the recovery to test it and it worked. So I went ahead with the OTA. Instantly, my phone was stuck in fastboot mode and I cannot get into download mode or anything else at all. Any options anyone?
I'm trying to use fastboot with adb to re-flash the stock firmware now. When I open command prompt in the platform-tools folder and type in "adb devices" it shows none. When I type in "fastboot devices" it shows a question mark. If I type in "fastboot reboot" it will communicate with the device and reboot it. I can't tell if I have a driver issue or what the problem really is.
I have a stock N5 that has a broken screen. You can see some parts of it but doesn't respond to touch at all. I saw there was an app on here that let's you see and remotely control the screen using your PC with adb. It looks like I might have the usb debugging turn on, however my adb shell is not authorized but does see the device. I have tried booting into stock recovery, but adb is not running at that time to allow me to push access keys.
What options do I have to be able to remotely use this phone. I want to use it as a camera for tinycam pro
Sent from my Pixel using Tapatalk
If your bootloader is unlocked, you can boot TWRP without flashing anything. From TWRP you'll get adb access.
If your bootloader is locked, you're doomed. :-/
Bootloader is locked. Is there anything I can flash to get it to work.
Sent from my Pixel using Tapatalk
I was able to use fastboot and unlock the bootloader. The phone restarted and went to a welcome screen. I was then able to flash twrp in recovery and load that up. I got into adb shell and ran some echo commands to put things into the default.props file in an attempt to enable us debugging when it rebooted. Well I guess the commands we're not correct or something but it didn't work. So then I went back into the bootloader and I thought I had to reflash twrp again, so I ran the same fastboot command I did before to load twrp. Says it wrote fine but now when I select recovery the phone just reboots back to the welcome screen. Since most of the screen is messed up o can't make out why that happens. Any help would be appreciated
Sent from my Pixel using Tapatalk
In case anyone else has the similar problem, once back into TWRP by using 'fastboot boot <img>', i used this post to mount the file system under system2 folder - https://forum.xda-developers.com/showpost.php?p=63829295&postcount=27
I then pushed my adb key onto the device so when the OS boots back up, it would allow adb to connect
Code:
adb push C:\Users\<username>\.android\adbkey.pub /data/misc/adb/adb_keys
Hello. I can't get my phone rooted in any way.
I want to Root so I can use TWRP app to flash TWRP recovery .img, and after that I can boot into TWRP recovery and flash new ROM. Correct????
What I've tried so far. OppoTools 1.6.5 = One key root gets hard stuck on Oppo logo at start-up and then I have to flash Coloros ROM again from recovery. Also KingRoot says app not installed. On windows version of KingRoot it gets to some percentage and then it Fails.
I have downloaded "unlocked bootloader" Coloros from this forum that was mentioned before ( Dropbox link )
I have also tried two different ColorOs versions.
I have installed 15sec ADB installer.
I plug my phone into PC and run CMD.
I type adb devices into command prompt and it detects my R7 plus.
then I try to command " adb reboot bootloader "
Phone restarts normally and doesnt go to bootloader. Tell me if im stupid, but isn't Bootloader different than Recovery? Because I can get to recovery command "adb reboot recovery"
I tried some weird button combination Vol+ Vol- + Power and phone semibricked for awhile and PC didnt even react USB driver correctly and almost waved the white flag on this case.
I've enabled USB-debuggin and OEM unlock from devices dev-options.
When I to type command "fastboot oem unlock" on command prompt is says Waiting for device. Nothing pops-up on device and nothing happens.
So now Im stuck on situation that my phone doesnt launch into bootloader where presumably "fastboot oem unlock" would work?
If you have flashed the version of Color OS that has bootloader enabled, you should simply need to go into the settings, enable USB debugging and OEM unlocking, then shutdown the phone before holding the power and volume+ buttons and waiting the ADB bootloader screen. After that, just plug it into the computer and follow the guide on flashing twrp with ADB.