Can't find info on this anywher but bought a phone off ebay and just boots into recovery mode. Can't get into bootloader mode to dreaming.nbh the thing. Is this considered bricked? i can get to recovery mode. i hit alt + L and i have the factory recovery system. at the bottom it does say E:Can't open /cache/recovery/command ... HELP PLEASE
I'm having the same EXACT issue. Haven't found a solution yet.
I'm going to bump this.
I've researched the last 4 hours about how to restore the G1 and all of them require the phone to enter into the bootloader (gray screen). I can not for the life of me get my G1 into the boot loader. It has no water damage that i know of. If I hold Home + Back + power I can get to the HTC erase phone thing but nothing responds.
Camera + Power does nothing other than turn the phone on and it goes into recovery mode.
Maybe an official bootloader in an update.zip format?
Tried all 3 here:
http://forum.xda-developers.com/showthread.php?t=455860
They all get verified and installation starts but then it aborts installation immediately.
Bumpage for some answers. I have an ADP1 phone. I've tried all the images from http://developer.htc.com/adp.html#s3.
1.1 and 1.5 all verify and start the installation but they immediately stop and I get a message saying "Installation aborted". I've tried flashing the radio image first but I get the same result.
I have a rooted Nexus 10. I recently received a popup that an update was ready to install (4.4.2). Somewhere during the install process it crashed. I can't remember exactly what it said but something about e:\ and invalid files. Now when I boot the tablet it loads the Google logo and then it displays the 4 color ball animation until the battery dies. I don't mind wiping everything so I downloaded the 4.4.2 rom from google and figured I could wipe and flash a fresh copy. The problem is I can't get ODIN to see my tablet. I plug in the USB and I hear the normal chirp that windows has found new hardware and it installs some strange driver (SAMSUNG CDC?) but ODIN never loads a com port.
Any thoughts on what's wrong, or other ways to try to fix the tablet?
Thanks.
I'm afraid I don't know much about ODIN....but:
I think there's hope yet! First things first, download the (dl.google.com/android/installer_r22.3-windows.exe) Android SDK Tools and install them - you'll need at least the Tools and the USB drivers.
Once those are installed, launch a command prompt (windows key + r on the keyboard, type in cmd and preess enter). Use cd and the tab key to get to the directory where you installed the SDK tools (e.g. cd "Documents\SDK Tools\platform-tools").
Now, on your Nexus 10, go into recovery by pressing the power button, volume up, and volume down buttons at the same time until you see a little Android with a red exclamation mark (I believe). Then, to show the menu hold the power button and volume up. Choose "Apply update from ADB"
Back on the computer, on the command prompt, type "adb sideload C:\Users\Where\You\Downloaded\The\Rom" without the quotes. It should transfer the rom to the nexus 10 and reflash it.
Please, let me know if you have any questions, I'm happy to help!
Have you tried doing a factory reset/ cache wipe in the recovery? (hold vol up+down and power from tablet off , then select Recovery Mode in fastboot)
You flash the factory image in fastboot NOT Odin .. you dont flash anything in Odin for Nexus you do everything thru the bootloader/fastboot
bjschafer said:
Back on the computer, on the command prompt, type "adb sideload C:\Users\Where\You\Downloaded\The\Rom" without the quotes. It should transfer the rom to the nexus 10 and reflash it.
Click to expand...
Click to collapse
First off tried just doing a wipe/factory reset and that didn't solve it (but thanks for the suggestion NewMagnus).
I was able to get into recovery and sideload the rom over. After it copied this is what came up on the Recovery (which by the way appears to be ClockWorkMod 6.0.1.6, which I don't actually remember installing but oh well):
Restarting adbd...
Finding update package...
Opening update package...
E:Can't open .temp/update.zip
(bad)
Installation aborted.
So, small progress but still no joy.
And an update...
I ran the Nexus Root Toolkit again but restarted the bootloader first. This time it somehow found FASTBOOT and installed the image no problem. I'm back up and running now. Wahoo!
Thanks for the help to get me here.
e2p219 said:
And an update...
I ran the Nexus Root Toolkit again but restarted the bootloader first. This time it somehow found FASTBOOT and installed the image no problem. I'm back up and running now. Wahoo!
Thanks for the help to get me here.
Click to expand...
Click to collapse
Well, as bad as it is to say, I'm glad I'm not the only one who had this problem. Thanks for the advice, hopefully I can pull a Lazarus on mine, its been dead and buried in a drawer for months. Unfortunately my SIII just bit the dust (permanently) so its time to try to resurrect this one again.
Hi,
Last night google pushed out the Lolllipoop update to my phone. I have stock android, nothing is rooted or changed.
It downloaded the update, installed it and rebooted into a forever lasting startup animation.
After a night of this i tried to restart the phone, same situation as above.
I resorted to go into recovery mode and wipe the phone, get image of dead droid stating command not find.
Atleast bootloader works.
I use mac, im a bit geeky, but i have troubles find a good guide that lets me completely flash the phine back to 4.4 when you are in the situation of a halfass os on your phone.
HELP or at point to where i can complain to google
ropapa84 said:
Hi,
Last night google pushed out the Lolllipoop update to my phone. I have stock android, nothing is rooted or changed.
It downloaded the update, installed it and rebooted into a forever lasting startup animation.
After a night of this i tried to restart the phone, same situation as above.
I resorted to go into recovery mode and wipe the phone, get image of dead droid stating command not find.
Atleast bootloader works.
I use mac, im a bit geeky, but i have troubles find a good guide that lets me completely flash the phine back to 4.4 when you are in the situation of a halfass os on your phone.
HELP or at point to where i can complain to google
Click to expand...
Click to collapse
Long lasting boot animation means, it is call boot-loop. It happens to some people (including me) who upgraded to Lollipop. Try factory data reset using stock/custom recovery and see it is booting or not. It worked for me and some other people.
Factory data reset will erase all your data.
steps to boot in to stock recovery
1.Power off the Nexus 4.
2.Press and hold at the same time Volume Up, Volume Down and Power buttons.
3.When you’re at the Bootloader / Fastboot main screen press Volume Up until the Start text turns to Recovery mode.
4.Press Power to boot the Recovery Mode.
> shortly you will see a green Android laid on its back with a red exclamation mark.
5.Press and hold Power button and immediately press the Volume UP.
This will open the Stock Recovery mode of your Nexus 4.
You can download factory images for Kitkat 4.4 and Lollipop 5 from google website. Extract that file and you will find a file with the name Flash-All. Simply running the Flash-all script will erase all the contents in the phone. To avoid that, just remove the -w from the line
fastboot -w update ....zip
I hope this helps you!:good:
[resolved] Thanks
Thank you,
This should help people in the same situation. I did not manage to test your solution but the logic is there.
I found a toolkit for mac that rooted and installed kitkat 4.4.4. for me.
When google pushes lollipop again and if a boot-loop happens again, i will definitely give your method a go!
Thanks,
R
So this was I have done to create and to try and solve this issue.
I was running stock CM12 and wanted to flash a different ROMs, so I tried to unlock the bootloader and using "fastboot -i 0x1ebf oem unlock" and without restarting the phone, tried to flash 64bit TWRP recovery, after this the phone no longer booted, but TWRP was booting, with a lot of errors of not being able to mount "/data" and other partitions. So I downloaded the CM12 offical ZIP file to try and do a factory reset, flashed using "fastboot" with the file "flash-all.bat" and here is where the problem started, this process failed, I think because there is a "flash-radio.sh" file where the "fastboot" lines do no have the "-i 0x1ebf" and because of this (I assume it's this lol), this process failed and the phone no longer starts, nothing works, tried in windows, ubuntu and a MAC at work, nothing is able to see the phone any more, the only sign of life I get, is when I remove the battery and connect the usb cable, the red LED from the phone turns on, but the PC still does not detect the phone, followed a recommendation I found, to remove the battery, pressing and holding the volume UP button + connecting the USB cable + connecting the battery, all this whilst the volume UP button is still being pressed and also did not work, no signs at all of life =(
Not sure what to do more, any idea guys?
Can't return because I bought on eBay UK =(
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.