Related
Using the terminal in Linux Mint 12, I unlocked, rooted, and flashed a custom recovery to my Nexus 7. The first time I did this, I neglected to use the OEM cable, and the recovery that I flashed did not take, bricking my Nexus. I reflashed the recovery, with the OEM cable, and from CWM recovery I installed the latest cm10 with gapps. The first time I booted it, I went through the setup procedures and logged in. After about a tenth of a second of the homescreen being visible, my Nexus crashed. And by crashed, I do not mean it went black and showed my the Google screen, I mean that it went black, then he screen fuzzed with visual artifacts, and was unresponsive until the battery drained completely.
I then, using the terminal, reflashed the recovery, went in and reflashed the cm10 ROM, then the gapps, and booted. Now, it works fine.
However! Upon rebooting to the bootloader, either through the on device menu, or through ADB, fastboot is dead. It displays the device information, the little android man, and the arrows pointing to the Power button and volume rocker. When I press either of these buttons, nothing happens. If I am connected to ADB, I cannot see the device, even after restarting the server.
Has anyone had similar issues? Does anyone have any advice?
Yes, I am running everything as root, and yes, I have checked that USB debugging is on.
Hi there,
I was able to boot the Q fine. I enabled USB debugging, used ADB to reboot into bootloader ran the oem unlock/unlock_accept command successfully. I rebooted and flashed CWM recovery v 6.0.2.7 steelhead. Once this was done, I rebooted into recovery and used adb to push the latest stable release of CM 10.1 to the sdcard. I then flashed this via CWM recovery, and performed a factory reset.
Now that I have rebooted system, it just sits on the cyanogenmod loading splash screen. I left it for over 2 hours at first, then I power cycled device and left it over night. I attempted to go back into recovery, but covering the LED on the top does not seem to result it anything. I power cycled the Q again, and held my hand over the LED from boot to attempt to get into recovery but I am not able to. I also powered device up and waited until the ring LED began to light up, then covered the top LED to see if this allowed to boot into recovery but still no change.
I let the Q boot up once more, and after sitting on the splash screen loading for about 10 minutes, I connected the device back to my PC, and found that adb can see the device. However now that it is running CM 10.1, adb security is enabled and my PC is unauthorized. I am unsure how to proceed at this point. Do I need to try a different PC than the one that was originally used to flash to see if it works (I doubt it will as that wont be authorized either, right?) or am I doing something wrong while trying to get into recovery?
If anyone can shed some light, or assist even getting into recovery, or providing a way to get around the adb authority requirement it would be greatly appreciated.
Ok scratch the above.. I managed to tap on the top LED about 50 times during boot, at which point it turned to red solid LED ring and loaded enough for me to get in using fastboot. I flashed the recovery again, ran a factory reset/wipe cache on it twice, and rebooted. it is now sitting at the home screen ready for me to purchase an OTG USB cable tomorrow and set up cyanogen mod!
After a whole 24 hours of using Lollipop and found the phone was unusable (phone would ring, but not give any other indication of an incoming call) in some ways, and lacking in other features, I decided it was time to go back to 4.4.4.
So I followed the instructions from Google(/android/nexus/images) , downloaded the 4.4.4 Occam factory image, and installed Minimal ADB and Fastboot. It took a while playing with drivers to get the device to show properly with the adb devices command, but it finally did, and was able to command it to reboot bootloader.
Everything still looking good. Still following the instructions, did the oem unlock, wiping it to factory settings, and then ran flash-all.bat. It went through that, the phone restarted into the bootloader, this time showing the Kitkat loading images instead of Lollipop, I think I'm home free.
I'm in the bootloader again now and notice adb devices is no longer showing the phone, so I try oem lock, and the phone screen updates to show locked. Odd, but it worked. I now used the volume buttons to select power off, and power off the device.
Powering on, the phone shows the Kitkat white "Google" on the screen, but that's it. I try powering it off again, and it restarts itself. I try getting it to display in adb devices, and nothing. The phone has been sitting at this screen for half an hour now with no change.
Using volume down+power I'm able to get it back into fastboot mode, but nothing will work from there. Start, recovery mode, and power off all result in the same thing: phone looks like it's turning on, but sits forever just showing the white "Google" on the screen. Abd devices still shows no devices attached, yet the phone still accepts oem lock and unlock commands, so I tried to run flash-all.bat again, but it just gives a 'command write failed(unknown error)'.
I'm kinda stumped now, and I haven't been able to find anything on this kind of issue. I'm hoping someone might have some experience or be able to suggest something my limited experience hasn't exposed me to before.
EyebrowZing said:
After a whole 24 hours of using Lollipop and found the phone was unusable (phone would ring, but not give any other indication of an incoming call) in some ways, and lacking in other features, I decided it was time to go back to 4.4.4.
So I followed the instructions from Google(/android/nexus/images) , downloaded the 4.4.4 Occam factory image, and installed Minimal ADB and Fastboot. It took a while playing with drivers to get the device to show properly with the adb devices command, but it finally did, and was able to command it to reboot bootloader.
Everything still looking good. Still following the instructions, did the oem unlock, wiping it to factory settings, and then ran flash-all.bat. It went through that, the phone restarted into the bootloader, this time showing the Kitkat loading images instead of Lollipop, I think I'm home free.
I'm in the bootloader again now and notice adb devices is no longer showing the phone, so I try oem lock, and the phone screen updates to show locked. Odd, but it worked. I now used the volume buttons to select power off, and power off the device.
Powering on, the phone shows the Kitkat white "Google" on the screen, but that's it. I try powering it off again, and it restarts itself. I try getting it to display in adb devices, and nothing. The phone has been sitting at this screen for half an hour now with no change.
Using volume down+power I'm able to get it back into fastboot mode, but nothing will work from there. Start, recovery mode, and power off all result in the same thing: phone looks like it's turning on, but sits forever just showing the white "Google" on the screen. Abd devices still shows no devices attached, yet the phone still accepts oem lock and unlock commands, so I tried to run flash-all.bat again, but it just gives a 'command write failed(unknown error)'.
I'm kinda stumped now, and I haven't been able to find anything on this kind of issue. I'm hoping someone might have some experience or be able to suggest something my limited experience hasn't exposed me to before.
Click to expand...
Click to collapse
ADB needs a booted up android to work, it wont work in bootloader mode. Another requirement is that usb debugging must be enabled in dev options. Fastboot works only in bootloader mode and doesnt need usb debugging.
Download wugfresh toolkit.. Use it to restore your device and DISABLE FORCE FLASH
Sent from my Nexus 4 using XDA Free mobile app
Hello all,
Any help with this would be seriously appreciated. I rooted my Nexus 10 a while back, maybe two years ago. I'm not very proficient with this stuff. Anyhow I decided to do the OTA upgrade to 5.0...I was concerned something would go wrong unless I went to stock first, but I read that the only thing that would happen is root would be removed.
Anyhow, the tablet appears stuck while booting. I see the Google screen first with the unlocked indicator on the bottom. A few seconds later is the Android logo on its back, a red triangle over it with an exclamation point and "no command" written below". It stays that way for a minute or so, tries to reboot and goes back to the no command screen. I can't even power off, when I try to do so it just powers back on by itself and ends up at the no command screen again.
I tried booting into recovery (power, volume up, volume down). My options from here are either Start, Restart Bootloader, Recovery Mode or Power Off. Every option I choose leads to the No Command Screen (except power off, which powers off). No idea what to do from here.
Any help at all would be appreciated. As you can probably tell I don't have much experience with this and just wanted to go back to unrooted stock. If you have advice, please be clear. I can follow directions well enough, just don't have much experience here. Thanks in advance.
Same here, bootloop.
Same thing here. A seemingly short download of Lollipop (even though I have 50Mbs internet). Installation, reboot, and now it loops endlessly. I can get to the bootloader or into Download mode, but that's all. Recovery mode just reboots. I was rooted and had TWRP installed. Other than that, I was running stock 4.4.4.
I've rooted all my devices, and installed various ROM's on several devices. I have the full ADB installation. I have the Nexus Root Toolkit installed. The problem is, the device will not show up under "Devices" on the computer itself. I've installed every USB driver there is (and uninstalled each one after it does not work, so no I do not have several USB drivers installed). Of course nothing shows up using "adb devices" either. Nexus Root Toolkit also cannot find any devices. I've read everything on this subject I can find, and there are no answers out there. Anyone have ANY ideas??
Thanks
Guys, if your device is connected in fastboot (try "fastboot devices") then you can flash roms or recovery (and then flash rom) from there. There are multiple threads with the same problems out there which were fixed. E.g: http://forum.xda-developers.com/nexus-10/help/bricked-t2948546
In my example, I flashed TWRP recovery from fastboot, then installed custom ROM from recovery (official ROM failed to install for some reason). Try this, it might help.
danweis said:
Same thing here. A seemingly short download of Lollipop (even though I have 50Mbs internet). Installation, reboot, and now it loops endlessly. I can get to the bootloader or into Download mode, but that's all. Recovery mode just reboots. I was rooted and had TWRP installed. Other than that, I was running stock 4.4.4.
I've rooted all my devices, and installed various ROM's on several devices. I have the full ADB installation. I have the Nexus Root Toolkit installed. The problem is, the device will not show up under "Devices" on the computer itself. I've installed every USB driver there is (and uninstalled each one after it does not work, so no I do not have several USB drivers installed). Of course nothing shows up using "adb devices" either. Nexus Root Toolkit also cannot find any devices. I've read everything on this subject I can find, and there are no answers out there. Anyone have ANY ideas??
Thanks
Click to expand...
Click to collapse
Go to Fastboot mode (pwr+both volumes), Than select recovery after a while an android with Exclamation mark appears which is a stock recovery screen. To access the stock recovery menu press and hold power than press one of the volume keys so the menu will appear. Than do a factory reset and clear caches. You can than reboot and wait for boot animation to finish (it wont take long this time) and you will boot.
If this doesnt work you can flash a stock factory image easily from fastboot again.
Aresmar said:
Go to Fastboot mode (pwr+both volumes), Than select recovery after a while an android with Exclamation mark appears which is a stock recovery screen. To access the stock recovery menu press and hold power than press one of the volume keys so the menu will appear. Than do a factory reset and clear caches. You can than reboot and wait for boot animation to finish (it wont take long this time) and you will boot.
If this doesnt work you can flash a stock factory image easily from fastboot again.
Click to expand...
Click to collapse
I also had the same problem... I followed these instructions and now my Nexus 10 can boot normally (it took a long time to boot).
Only problem is all my data was deleted.... stup*d f*cking sh*t!!!!!!!
I've successfully rooted my T-Mobile LG Leon, and I've successfully installed TWRP, but for the life of me, I can't get the phone to boot into recovery. I can RE-boot into recovery from TWRP manager, but I can't actually boot into it from a fully powered-down state. I've tried every combination of the power and volume buttons I can think of, and nothing ever works. Download Mode works, the factory restore menu works, but I CANNOT get into recovery. Is there a very specific set of instructions anywhere that I can follow?
EDIT: Okay, I finally figured it out: You need to actually select to do a factory reset, and it throws you into the recovery menu.
Yeah, it was because the stock recovery doesn't exist as a menu, when you're running stock and enter the adb command "adb reboot recovery" it will reboot to the "factory reset mode" and the actual file of this mode is stored on partition named "recovery". Choosing the factory reset option boots the custom recovery because it replaces the said " factory reset mode" and that's the trick.
You can access recovery from the powered off state by holding volume down and power on until you see the lg sign. Without letting go of volume down, depress on the power button before clicking it back in and holding both buttons in until you see twrp pop up.
If you reboot to recovery now, it''ll probally say secure booting error. Simply go to the Developer options and enable OEM Unlock and that'll make you boot to it
You boot in the download mode by holding the vol up 10 seconds and during this 10 seconds you insert the usb. The LG Leon brand screen will come on a minute then it will go into download mode. It says not to unplug until firmware is done updating. So I guess you should have your custom recovery or whatever before you do this. I have only got this far, and thusly it sits. All Dressd up with no where to go...haha
kruc Ire said:
You boot in the download mode by holding the vol up 10 seconds and during this 10 seconds you insert the usb. The LG Leon brand screen will come on a minute then it will go into download mode. It says not to unplug until firmware is done updating. So I guess you should have your custom recovery or whatever before you do this. I have only got this far, and thusly it sits. All Dressd up with no where to go...haha
Click to expand...
Click to collapse
can't find "enable OEM" at all in developer options. have phone hooked computer, and on, it's sending and receiving. No OEM. Isn't there.
See, I'm trying to root this without using KingUser. Since I found that it was pretty easy to do from the very beginning with Samsung, and I just don't see any way to do it here. I can't get ADB Devices command to see the phone.
kruc Ire said:
can't find "enable OEM" at all in developer options. have phone hooked computer, and on, it's sending and receiving. No OEM. Isn't there.
See, I'm trying to root this without using KingUser. Since I found that it was pretty easy to do from the very beginning with Samsung, and I just don't see any way to do it here. I can't get ADB Devices command to see the phone.
Click to expand...
Click to collapse
I think I have the same issue, but I rooted my phone using kingroot, I haven't tested the adb commands, I just want to use twrp but no luck, it says Secure booting error and I can't find OEM Unlock option in Developer Menu.
duffycop said:
I think I have the same issue, but I rooted my phone using kingroot, I haven't tested the adb commands, I just want to use twrp but no luck, it says Secure booting error and I can't find OEM Unlock option in Developer Menu.
Click to expand...
Click to collapse
I got a good way to get it rooted with SuperSU. Ran a command window script I found out there. It worked and now I have SuperSU root. I also figured out how to get into recovery. It looks as though my phone is not the standard LEON that people are talking about here. It's got a few designations, and the T Mobile site advertises a Leon that seems very similar and is called by the name most are using..
Anyhow my LG Leon is designated as a H320. It also carries a v10 desiganation, v10b. The v10 is variable from a-h or a-i. It would seem that once it is updated to 5.1.1 android it gets upped, and becomes unrootable. Mine being a v10b was rootable, but it took me a while to get used to it, and make the command window work.
Unfortunately for me one of many things I tried before getting it rooted, was ADB fastboot. And since this told me to wait for too long, I pulled the plug on it and pulled the battery to get back into "normal" operations. Perhaps I should have waited, because after finding out a few things about the phone, I discovered the true way to get it into recovery:
The real way into recovery for my phone, is to (from power off state) hold the volume up, a few seconds, then plug the USB cable which is going to the computer into the phone. While holding the volume up until it comes to recovery. This will activate the recovery, (Now for me it activates that fastboot command line...and does nothing else). This was the bit of information I could have used from the beginning, that no one knows. All these places tell you to hold the power and volume up, and then let off power when the screen changes, but that never worked even once. You just hold the volume, and plug the USB from computer. This works.
For me it goes into a "FASTBOOT" header at the bottom of the screen that never changes.
I believe it does this because of my unsuccessful attempt to fastboot it before. And it does not have the right driver to get recognized in the computer. So I'm screwed as far as the recovery goes now.
It is rooted though. And it doesn't seem to have any alternate ROMS available anyways. so we're dealing with the loss of the recovery.
When I do try to use an app such as TWRP manager or CWM (ROM) Manager to reboot into recovery, I get a "boot certification verification -1" error instead of the fastboot line at the bottom of the startup screen and it boots normally from there. So many people asked about this "boot certification verification -1" and NO answers are available anywhere online. So that's where it stands for this phone right now.
Anyone know what driver I should use to get the thing recognized in the computer? I have downloaded a zipped fastboot tools, and it won't get recognized inside the driver manager as "android" only as "unknown device" so I can't use that route....I'm thinking about doing a factory reset to try to erase the fastboot attempt. That may not help though. Anyone?
kruc Ire said:
I got a good way to get it rooted with SuperSU. Ran a command window script I found out there. It worked and now I have SuperSU root. I also figured out how to get into recovery. It looks as though my phone is not the standard LEON that people are talking about here. It's got a few designations, and the T Mobile site advertises a Leon that seems very similar and is called by the name most are using..
Anyhow my LG Leon is designated as a H320. It also carries a v10 desiganation, v10b. The v10 is variable from a-h or a-i. It would seem that once it is updated to 5.1.1 android it gets upped, and becomes unrootable. Mine being a v10b was rootable, but it took me a while to get used to it, and make the command window work.
Unfortunately for me one of many things I tried before getting it rooted, was ADB fastboot. And since this told me to wait for too long, I pulled the plug on it and pulled the battery to get back into "normal" operations. Perhaps I should have waited, because after finding out a few things about the phone, I discovered the true way to get it into recovery:
The real way into recovery for my phone, is to (from power off state) hold the volume up, a few seconds, then plug the USB cable which is going to the computer into the phone. While holding the volume up until it comes to recovery. This will activate the recovery, (Now for me it activates that fastboot command line...and does nothing else). This was the bit of information I could have used from the beginning, that no one knows. All these places tell you to hold the power and volume up, and then let off power when the screen changes, but that never worked even once. You just hold the volume, and plug the USB from computer. This works.
For me it goes into a "FASTBOOT" header at the bottom of the screen that never changes.
I believe it does this because of my unsuccessful attempt to fastboot it before. And it does not have the right driver to get recognized in the computer. So I'm screwed as far as the recovery goes now.
It is rooted though. And it doesn't seem to have any alternate ROMS available anyways. so we're dealing with the loss of the recovery.
When I do try to use an app such as TWRP manager or CWM (ROM) Manager to reboot into recovery, I get a "boot certification verification -1" error instead of the fastboot line at the bottom of the startup screen and it boots normally from there. So many people asked about this "boot certification verification -1" and NO answers are available anywhere online. So that's where it stands for this phone right now.
Anyone know what driver I should use to get the thing recognized in the computer? I have downloaded a zipped fastboot tools, and it won't get recognized inside the driver manager as "android" only as "unknown device" so I can't use that route....I'm thinking about doing a factory reset to try to erase the fastboot attempt. That may not help though. Anyone?
Click to expand...
Click to collapse
I dunno, I have the H340AR, with this phones happens the same that with the Samsung Galaxy Ace 3, there are, 3G versions, 4G versions, regional versions, etc.. GA3 have 7275R, 7275B, 7272L, 7272T, I dunno, maybe if we could get a device tree for a H340 and an H320 we could make some TWRP and CM compiling, but I just can't figure it out how to make a device tree or even where to begin..
I successfully rooted my H340AR with Kingroot, it works like a charm. I haven't tried fastboot and I tried to install TWRP in this link https://dl.twrp.me/c50/ but I get that F error "Secure booting error". I guess I have my bootloader locked, so I'm trying to figure out how to unlock my bootloader.
I'm trying to contact with some developers and see if anyone can help me build a device tree.
]
Hi, I have that same phone H340AR LTE. I rooted it with Kingroot and also tried to use TWRP to gen into recovery and got that Security error. I only pulled out the baterry and turn it on again so it booted normally. I made a factory reset because I read that it could be a problem of OTA firmware update. Then I installed TWRP and BusyBox again and tried to get into recovery from TWRP option. When I did that, it showed up the Android lying in his back with a red triangle. I pulled a out the battery again and yes, it seems very dumb and simple but it worked and could reboot the phone.
However, I can't get into recovery from TWRP yet. I read that the problem with us not being able to unlock the bootloader(we don't have the OEM option) is because Leon has Lollipop 5.0.1 and OEM is for 5.1.1
pedrovay2003 said:
I've successfully rooted my T-Mobile LG Leon, and I've successfully installed TWRP, but for the life of me, I can't get the phone to boot into recovery. I can RE-boot into recovery from TWRP manager, but I can't actually boot into it from a fully powered-down state. I've tried every combination of the power and volume buttons I can think of, and nothing ever works. Download Mode works, the factory restore menu works, but I CANNOT get into recovery. Is there a very specific set of instructions anywhere that I can follow?
EDIT: Okay, I finally figured it out: You need to actually select to do a factory reset, and it throws you into the recovery menu.
Click to expand...
Click to collapse
when i pressed factory reset all it did was to a factory reset even though i flashed twrp.img successfully... help?
lg leon h345 lollipop 5.1.1
This device has a locked bootloader. If you flash a custom recovery on it, it will not boot into recovery, but will report a security issue. You will lose all recovery functionality, including factory reset, adb, fastboot. If your phone fails to boot, you have a brick.