Related
Hi, im in the process of selling my phone and am following the tutorial on here about turning the phone back onto stock. The flash with flashtool was successful but im forever stuck on the boot screen? with now no way to go into custom recovery? i installed the correct rom for the phone so why hasnt it worked? thanks in advance.
dav08094194 said:
Hi, im in the process of selling my phone and am following the tutorial on here about turning the phone back onto stock. The flash with flashtool was successful but im forever stuck on the boot screen? with now no way to go into custom recovery? i installed the correct rom for the phone so why hasnt it worked? thanks in advance.
Click to expand...
Click to collapse
The only way I could get it to work was the following; however there is one thing to try before you try my way because mine did this also - after the wipe and flash with flashtool etc. The only way I found to get out the bootloop was to do a factory restore after when its looping. So from the boot screen loop hold the power button until it goes off then on then off again.
Then do the process to get into the recovery so hold down and power then release power as soon as the lg logo appears (first one) then press it again immediately that SHOULD get ya to the grey factory reset screen. Press the power button 3 x and it should do a factory restore and boot up this time. First boot may take a minute it should eventually start up.
Failing that try this - Open the lg mobile support tool and connect the phone in download mode (volume up and power with plugged in usb on mine) then go to options and upgrade recovery. it will download a file usually about 2GB then install it, the phone will reboot at 100% on the phone and 80ish% on the lg tool it will then start into the setup feature,
DO NOT disconnect the phone until it gets to 100% and finishes. This way you shouldn't need to do an extra factory reset.
I understand for this the phone needs to be seen on com 4 (it shows on the phone screen) so if necessary go into device manager with the phone still plugged in in download mode and select com ports then select the phone com port then right click >properties> advanced and change the com port to 4. It may tell u its already being used but don't worry it is fine. Save and exit device manager.
please bare in mind these are just my experiences on MY LG D802 however its worked every single time for me without fail and ive done it a good few lol.
HTH:good:
Hi,
Have a weird situation, but try as much as I may, I'm unable to resolve it.
My phone is rooted (international D802) and was running fine. Had a screen issue and got it replaced at the service center but their system identified my phone as a rooted device, and a couple of days later the problems started.
The issues I'm facing right now:
1. The phone doesn't charge when switched on, at all.
2. The phone doesn't reboot either.. not instantly anyways. If powered off, or rebooted, the phone doesn't turn back on, it just goes dead. It does boot again though if tried after a couple of hrs.
3. The phone charges when its off (shows no light or indicator though, like its bricked)
4. Cannot go into either recovery or download mode. Coz the phone doesn't boot when restarted or when i try to reboot into recovery.
5. When it does magically start after a few hrs (upon long pressing the power button), even if I try to go into download or recovery via the vol keys, it just boots to android.
6. The phone is recognized properly as LG G2 under windows and all the drivers install too.
7. The phone isn't recognized under Linux... tried both Ubuntu and Knoppix.
Travelling out of the country in a few days, really need to sort this out.
Any and all help/suggestions will be greatly appreciated.
Thanks in advance
Somebody... Anybody? :'(
When your phone rebooted I would recommend you firstly to activate USB Debugging in the developer settings. You said your device is rooted? So try to install the Auto Rec recovery here
https://www.androidfilehost.com/?w=files&flid=13763 - but make sure you are on Kitkat. Now, install the app normal and let the app install all things. After installation, the app asks you to reboot to recovery, now press reboot to recovery.
Maybe you have luck and the phone reboots to TWRP. In TWRP you can go to Reboot and then Reboot to Download mode.
Now (if all worked) you can flash the stock rom .kdz file of the d802 via the FlashTool 2014.
Hope you have luck, please keep me up to date if everything worked.
Yours, Flo
Good luck!!
Thanks a lot for the response Flo, but the problem is that i never got around to updating to a Kitkat rom... the rom i was never got updated and I was kinda happy with how things were working so didn't jump on to any other rom.
Anything I can do in my current situation?
Go back to stock via lg flash tool
_____________________________________Read more write less and be smart
siggey said:
Go back to stock via lg flash tool
Click to expand...
Click to collapse
As mentioned in my first post, can't get into download mode.
Try this
http://forum.xda-developers.com/showthread.php?p=56000637
LG G2 is UNBRICKABLE NOW! [FIX REAL HARD BRICK]
_____________________________________Read more write less and be smart
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.
I had to reboot my device due to problems with my speaker. Now i'm not able to boot anymore.
I'm only able to get into ODIN Mode, and flashing new FW or TWRP does nothing. It'll flash correctly, but as soon as it sends the reboot command the device powers off and does not boot, and no, it does not reach the "Galaxy s8, powered by android screen".
It does not want to power on, and only responds to the odin button combo, can't boot into recovery either since nothing works.
I was running the latest version of Renovate Ice if that matters.
I've searched trough some other threads, but it seems like i'm the only one that's having this problem.
Any help or thoughts would be greatly appreciated!
Edit 1: I've tried flashing both AQK7 and AQG5. Both flash fine, but as soon as odin sends the reboot command to my phone, it turns off and does not turn on.
Auto Reboot is ticked. Same goes for any version of TWRP, it will flash, but when it has to reboot the device turns off and does not turn on. There's nothing on the screen, its completely black and the only thing that does work is Download Mode. I've also tried ereasing nand, and repartitioning storage. Both seem to have 0 effect. As stated in one of my replies, i was running the latest build of renovate-ice with magisk, no other mods, or themes installed.
Im a bit confused - you can only boot into download mode (not into twrp?) and the phone is in bootloop? Have you flashed anything (mod?) before or activated a substratum theme which could cause this?
The only thing I can think of is a) you delete in twrp file manager the corrupted file, if there is something like this or b) a twrp restore from a backup. Boot into download mode and then do not press vol up to go into odin mode but press vol down to reboot - then immediately press the combo for twrp and you will get to the recovery. This helped my s8 many times when I was in a bootloop and couldnt boot up twrp
FloM94 said:
Im a bit confused - you can only boot into download mode (not into twrp?) and the phone is in bootloop? Have you flashed anything (mod?) before or activated a substratum theme which could cause this?
The only thing I can think of is a) you delete in twrp file manager the corrupted file, if there is something like this or b) a twrp restore from a backup. Boot into download mode and then do not press vol up to go into odin mode but press vol down to reboot - then immediately press the combo for twrp and you will get to the recovery. This helped my s8 many times when I was in a bootloop and couldnt boot up twrp
Click to expand...
Click to collapse
Thanks for the reply! Other than using the Renovate-Ice rom, and running magisk the thing was pretty much stock. wasn't messing around in twrp either. Its not stuck in a bootloop either, it just refuses to do anything other than go in and out of DL mode. The phone does not respond to any button imputs other than DL mode. As stated in the OP it does not boot at all, just a black screen. i've already tried to reflash a stock FW and TWRP, but that does not seem to work...
try the method I did - this is the last thing I could think of, before reflash the whole phone with odin
More info about your speaker problem
popmpopm said:
More info about your speaker problem
Click to expand...
Click to collapse
There isn't much to say about the problem ,it just stopped working, hence why i rebooted the phone, and ran in to the problem i'm having right now.
FloM94 said:
try the method I did - this is the last thing I could think of, before reflash the whole phone with odin
Click to expand...
Click to collapse
Doesn't work sadly, but thanks for the help anyways!
but you havent installed Viper4Arise or anything like that?
Because of this my speaker also stopped working a few weeks ago
if you can get into download mode then get into download mode and leave phone, then download samsung smart switch for your pc (older version like 4.1.17022_20 from here http://www.filehorse.com/download-samsung-smart-switch/29268/ that allows phone based recovery), once installed open it, then click on more at top right, (do not update the software if you get a prompt) select emergency device recovery...., then click on right tab (device initialisation) and fill in your phone details etc., connect your phone (in download mode) and follow the process, maybe it works, you'll need to root and install TWRP again but thats no big issue.
Jostian said:
if you can get into download mode then get into download mode and leave phone, then download samsung smart switch for your pc (older version like 4.1.17022_20 from here http://www.filehorse.com/download-samsung-smart-switch/29268/ that allows phone based recovery), once installed open it, then click on more at top right, (do not update the software if you get a prompt) select emergency device recovery...., then click on right tab (device initialisation) and fill in your phone details etc., connect your phone (in download mode) and follow the process, maybe it works, you'll need to root and install TWRP again but thats no big issue.
Click to expand...
Click to collapse
I've tried this just now, and it still gives me the same result, it goes trough the process, but as soon as it has to reboot it doesn't boot anymore.
Thanks for the suggestion though!
FloM94 said:
but you havent installed Viper4Arise or anything like that?
Because of this my speaker also stopped working a few weeks ago
Click to expand...
Click to collapse
i think phone is damaged by water or dropped s8 so fragile phone ! its happen to me with s5 the phone dead after speaker problem !!
popmpopm said:
i think phone is damaged by water or dropped s8 so fragile phone ! its happen to me with s5 the phone dead after speaker problem !!
Click to expand...
Click to collapse
I've had a case on the phone since day one, and I've checked for water damage, but there is non. The tab that is supposed to indicate it is untouched. But thanks for your input! I appreciate it
I have the same problem. Its look like is bootloader issue. try flash this soft :
G950FOWA1AQCC_Recovery
But if you are on newest rom it wont work.
Hello, you can solve this problem?
I was going along ok until I made the fatal error of transferring the Magisk patched file to PC via MTP instead of taking the time to re-learn adb, which must have corrupted it. Thus predictably Odin hung and I am in trouble.
Where I am stuck is being unable to turn the phone off to come back in download mode to start over with stock firmware. I have been unable to find any secret button presses, and the battery doesn't seem to want to die leaving me with an $800 paperweight.
I did search around for this first and didn't find any real answers. Has anyone found an effective solution to this problem? Thanks.
fastzombies said:
I was going along ok until I made the fatal error of transferring the Magisk patched file to PC via MTP instead of taking the time to re-learn adb, which must have corrupted it. Thus predictably Odin hung and I am in trouble.
Where I am stuck is being unable to turn the phone off to come back in download mode to start over with stock firmware. I have been unable to find any secret button presses, and the battery doesn't seem to want to die leaving me with an $800 paperweight.
I did search around for this first and didn't find any real answers. Has anyone found an effective solution to this problem? Thanks.
Click to expand...
Click to collapse
If Odin recognizes you device, you can flash firmware in emergency recovery.
Cindysmith0994 said:
If Odin recognizes you device, you can flash firmware in emergency recovery.
Click to expand...
Click to collapse
Thank you, but the PC won't recognize the device. What does happen is the emergency recorevy screen tries to come up. I tried starting in download mode with bixby+vol down then USB. I did get the battery low enough where I don't get the teal screen of death anymore, perhaps it is too low for USB to work? What I was hoping for was the charging animation but no luck. Surely this is just a software problem and there is a way out.
fastzombies said:
Thank you, but the PC won't recognize the device. What does happen is the emergency recorevy screen tries to come up. I tried starting in download mode with bixby+vol down then USB. I did get the battery low enough where I don't get the teal screen of death anymore, perhaps it is too low for USB to work? What I was hoping for was the charging animation but no luck. Surely this is just a software problem and there is a way out.
Click to expand...
Click to collapse
Did you try getting into recovery and perform a data factory reset and then see what happens?
Just load the stock firmware BL, Ap, cp and home csc into Odin if you see emergency teal screen. The emergency screen will start loading
Black screen ....Perhaps your battery is dead?
Thank you all for the replies. I had let the battery get low in a misguided attempt (based on advice elsewhere) to get it to shut off. I had to let it charge a while for it to wake up enough for PC to see it. Then I was able to flash in Emergency Recovery mode.
Thank you for the help.
fastzombies said:
Thank you all for the replies. I had let the battery get low in a misguided attempt (based on advice elsewhere) to get it to shut off. I had to let it charge a while for it to wake up enough for PC to see it. Then I was able to flash in Emergency Recovery mode.
Thank you for the help.
Click to expand...
Click to collapse
Glad you got your device up and running ?
Maybe someone can help me. I seemed to have borked my phone. I kept getting "Google is Stopping" with no way to fix it, so I tried reflashing my firmware in odin. After I loaded all the files and hit start, I realized I didn't untick auto reboot, so I tried aborting the installation and ended up with screen (I've had it before and got out of it by still flashing in Odin, but now, if I try to reflash firmware while in this screen, it's stuck on SYSTEM in odin.
Any help appreciated!
Try this
That is where I got stuck. Are you trying to flash stock or patched firmware? I had to start over with stock as I copied the patched via MTP instead of adb and it got corrupted.
I think what I did was unplug and reset Odin. Wait for screen to turn off, then make sure it is at least 80% charged. Then Bixby + Vol Down + plug in and you will go back to this screen. Then I was able to flash stock. I had to go so far as to re-lock bootloader and flash stock again since my "OEM Unlocking" was not just greyed out but missing. Since then I've had no time to try again, but at least I have a working phone.
This is my anecdotal procedure, can't say if it is the right or best one.
Hi All,
I was trying to flash the latest firmware for my device (G9750ZCU2ASG4) and during the odin process, my computer restarted which failed the update halfway through. I rebooted the computer, tried again, and it was trying to establish a connection for a really long time, so I disconnected my phone from the USB port on my computer, and held Power and Volume Down to try and force reboot the phone. I was going to try and go back into download mode to restart the process. My phone mentioned something about needing to do an emergency recovery, but I continued to hold down the power and volume down keys and then everything went black on the phone.
I've tried multiple USB cords, all of the button commands known for the device, and have even tried to perform the emergency mode recovery on my device, but it seems like it's in some sort of locked state; What I mean is the phone is stuck on a black screen. I can't "boot" into recovery or into download mode. The phone doesn't even vibrate when I hold the power button or power and down to try and force reboot it. Odin doesn't recognize the phone when I plug it into the computer nor does the device manager on my windows computer.
Does anyone have any experience with this sort of issue or any idea of what else I can do to try and get into download mode to flash my firmware again? All help, suggestions, or comments regarding this are much appreciated.
Sounds like the battery is dead
Hi Dude, I am struggling with the same problem, read this post and it came to me, had to come back and give you the solution.
Press bixby+volume down, IMMEDIATELY after the screen goes off, hold volume up and down while connecting the USB cable super fast.
You have got like 10ms to do it
Otherwise it just goes back to the AVB FAIL screen
Ran into this issue, none of the above worked for me.
This is how I resolved:
1) Placed phone on wireless charging mat and let it boot to emergency recovery screen
2) Load TWRP into AP slot of Odin and leave the window open on your computer ready to flash
3) Connect phone to computer whilst it's on the mat and press start in Odin as soon as your device appears
It may fail a few times but if your quick you can install TWRP.
4) Now boot into recovery and let your phone charge to a reasonable level (above 20%)
5) Boot into Download mode and flash your desired rim via Odin