I was on a stock based ROM (my phone would not boot a cm based one for some reason) but can't remember which one. So I backed everything up including a backup of my nandroid and put it all on my sd card so I can downgrade to KK. I followed the instructions (from where I can't remember because I've been to so many threads and sites for a fix) using LG Flash Tool and downloaded the 10d .tot file along with the .dll file. All went fine until the 89% mark and came up the error "can't communicate with device". Well ok I did it again... same thing. Started my massive search online to find a fix. I tried a mod.dll, an LGUP_8974.dll and found another .dll I can't find right now. But I can get up to 94% with the mod and LGup ones. Once the error was "unable to get miniOS confirmation boot" or something like that but that only happens when doing an upgrade dl. I've tried the board DL and upgrade DL. Now on the modded .dlls on upgrade dl, when it tries to boot the led will flash like normal when booting but I'm just stuck in a boot loop. So in short...
No custom recovery,
Boot loop at LG logo
uninstalled/reinstalled drivers
used every combination of .dlls and action mode in flashtools there is. Even tried older versions.
I do have download mode.
I can get to stock recovery and do a reset but that does nothing.
If I can get twrp on it I can restore my nandroid on my sd card. Any help would be appreciated.
yogi-4 said:
I was on a stock based ROM (my phone would not boot a cm based one for some reason) but can't remember which one. So I backed everything up including a backup of my nandroid and put it all on my sd card so I can downgrade to KK. I followed the instructions (from where I can't remember because I've been to so many threads and sites for a fix) using LG Flash Tool and downloaded the 10d .tot file along with the .dll file. All went fine until the 89% mark and came up the error "can't communicate with device". Well ok I did it again... same thing. Started my massive search online to find a fix. I tried a mod.dll, an LGUP_8974.dll and found another .dll I can't find right now. But I can get up to 94% with the mod and LGup ones. Once the error was "unable to get miniOS confirmation boot" or something like that but that only happens when doing an upgrade dl. I've tried the board DL and upgrade DL. Now on the modded .dlls on upgrade dl, when it tries to boot the led will flash like normal when booting but I'm just stuck in a boot loop. So in short...
No custom recovery,
Boot loop at LG logo
uninstalled/reinstalled drivers
used every combination of .dlls and action mode in flashtools there is. Even tried older versions.
I do have download mode.
I can get to stock recovery and do a reset but that does nothing.
If I can get twrp on it I can restore my nandroid on my sd card. Any help would be appreciated.
Click to expand...
Click to collapse
If you boot into download mode and delete the laf partition (download mode) you will get fastboot next time that you enter download mode and you can use fastboot to flash and/or boot TWRP. Note make sure that you have a backup of laf first if you ever want download mode back. The following is for another LG phone but it should work. http://forum.xda-developers.com/showpost.php?p=60699787&postcount=1932 the backed up laf in the post wont work but you can always extract it from a tot file for your device.
Hope that this helps.
That worked!! I flashed a rom that had an aroma installer and it didn't boot, same boot loop. Flashed another aroma rom and it booted perfectly!! Thanks again.
Edit: A beer is on it's way!
yogi-4 said:
That worked!! I flashed a rom that had an aroma installer and it didn't boot, same boot loop. Flashed another aroma rom and it booted perfectly!! Thanks again.
Edit: A beer is on it's way!
Click to expand...
Click to collapse
Thanks for the donation.
Related
edit: on a whim I looked at the heimdall command line options and saw "close pc screen" as one of the arguments and tried that and it booted up perfectly!!!!! So relieved it was something that simple!
I got my S4 last night and immediately tried to root it after I got it, I read up on some stuff (not new to rooting, I've rooted multiple devices in the past) and attempted to flash TWRP via Odin but then it said it failed for some reason, I tried again and it failed. I figured everything was fine until I rebooted and got "Firmware upgrade encountered an issue. Please select recovery mode in kies and try again." I tried to connect it to my old Windows XP pc (my main pc runs Arch Linux) and kies kept saying "connecting" no matter how many times I tried to make it connect or reinstall the drivers.
I can get to download mode and I'm trying to flash the stock firmware via heimdall but it's taking forever to uncompress the image. I got the images from here: http://forum.xda-developers.com/showthread.php?t=2258628
I tried to flash cf-autoroot with heimdall in hopes that it would restore my bootloader but it wouldn't flash because it said it was missing an XML file.
I think I'm just missing the bootloader/recovery image but I'm not sure. Am I heading in the right direction?
If you have root and still have access to the phone when u turn it on flash cwm recovery via Odin or if Ur phone turns on nd have root then download goomanager nd you can install twrp with that app with no problems
Sent from my SGH-M919 using xda premium
im having the same issue...
i am flashing Modem_UVUAMDL.tar and philz touch 5.08.5-jfltetmo as recovery, OUDHS jfltetmo also, but nothing is working
i was running infamous 4.0 ROM, flashed the cyanogenmod nightly and somehow everything exploded and now the only thing on my screen is the SGS4 stock image... it wont boot into recovery mode only download.
i am on an OSX using heimdall and i do not ever have access to a PC!
icecreamwithyou said:
im having the same issue...
i am flashing Modem_UVUAMDL.tar and philz touch 5.08.5-jfltetmo as recovery, OUDHS jfltetmo also, but nothing is working
i was running infamous 4.0 ROM, flashed the cyanogenmod nightly and somehow everything exploded and now the only thing on my screen is the SGS4 stock image... it wont boot into recovery mode only download.
i am on an OSX using heimdall and i do not ever have access to a PC!
Click to expand...
Click to collapse
Did you find a fix I have the same issue but I do have a pc?
brando56894 said:
edit: on a whim I looked at the heimdall command line options and saw "close pc screen" as one of the arguments and tried that and it booted up perfectly!!!!! So relieved it was something that simple!
I got my S4 last night and immediately tried to root it after I got it, I read up on some stuff (not new to rooting, I've rooted multiple devices in the past) and attempted to flash TWRP via Odin but then it said it failed for some reason, I tried again and it failed. I figured everything was fine until I rebooted and got "Firmware upgrade encountered an issue. Please select recovery mode in kies and try again." I tried to connect it to my old Windows XP pc (my main pc runs Arch Linux) and kies kept saying "connecting" no matter how many times I tried to make it connect or reinstall the drivers.
I can get to download mode and I'm trying to flash the stock firmware via heimdall but it's taking forever to uncompress the image. I got the images from here: http://forum.xda-developers.com/showthread.php?t=2258628
I tried to flash cf-autoroot with heimdall in hopes that it would restore my bootloader but it wouldn't flash because it said it was missing an XML file.
I think I'm just missing the bootloader/recovery image but I'm not sure. Am I heading in the right direction?
Click to expand...
Click to collapse
I just recently purchased a rooted S4 and I downloaded a ROM from this site that wasn't compatible with my S4 and flashed it (BIG mistake I know now). So now I can't start up my phone. I read here that I should wipe out the divalk cache/cache and restart (didn't work). Reset to factory settings and reboot (didn't work). Download the TWRP flashable zip and flash it from the Recovery memory then reboot (didn't work). Now I'm really worried. Can you please help me?
Warrior1016 said:
I just recently purchased a rooted S4 and I downloaded a ROM from this site that wasn't compatible with my S4 and flashed it (BIG mistake I know now). So now I can't start up my phone. I read here that I should wipe out the divalk cache/cache and restart (didn't work). Reset to factory settings and reboot (didn't work). Download the TWRP flashable zip and flash it from the Recovery memory then reboot (didn't work). Now I'm really worried. Can you please help me?
Click to expand...
Click to collapse
What does it do when you boot up?
I went through the normal procedure of installing a new ROM, I wiped w/factory reset, got hit with a "status 7" error. I looked it up and it's apparently a problem with conflicting recovery manager files. That makes sense because I have CWM recovery and it asked me to install TWRP. I guess you can't have both?
I followed a tutorial explaining how to edit the userscript file to bypass the error and it seemed like it was going to install at first but I still got hit with it. Now my computer doesn't recognize my s3 (d2spr) so I have to put the files on an external microSD. I tried to restore from CWM but it wouldn't let me. I'm pretty new to this stuff so I'm not sure how to proceed from here.
Your best option is Odin back to stock and start over again.
Sent from my SPH-L710
Im having the same issue. Can someone please help. I tried flashing the stock sprint rom using ODIN but i'm also stuck in recovery boot loop. Would some one direct me where i can maybe find the correct .tar to flash with ODIN
this is the one i used: L710VPUCMK3_L710SPRCMK3_L710VPUCMK3_HOME
Thanks
Hi everyone.
I'm so frustrated for a week to get get back to Stock Recovery Menu from CWM Recovery. The problem is, I want to restore Stock Firmware for my LG Optimus G E973 but it won't work unless I role back to Stock Recovery Menu. I've been searching around for it but no luck. Now the only hope is to get Stock Recovery image and push it into the phone and I think the only ways to get it is, someone backup Stock Recovery from the same phone model or extract it from original Stock ROM image. I failed to do so. For the convenience to download the KDZ file, I uploaded it to Google Drive with the link below. I bag you, PLEASE, help me get Stock Recovery image from the .kdz file I uploaded for you. I will wait for your response every seconds and thank in advance.
https://drive.google.com/file/d/0B8G245x5wYw2a1VhTjVZQXdqOTQ
Why not just flash back the official kdz? The download mode works regardless you have stock recovery or CWM.
I did. it won't work. I used KDZ_FW_UPD_EN with .kdz file while putting my phone in Download Mode. Then the program restart the phone to proceed the installation but CWM recovery appear instead of stock recovery and nothing happen.
Read this
http://forum.xda-developers.com/showthread.php?t=2388440
[GUIDE] Flashing Original Firmwares >1GB / Unbrick Procedure (UPDATED 07/12/13)
this is all you need, back your data up then firstly you need " hard reset procedure " then flash kdz i used this too many time but dont forget it will erase all your data (sd card too)
Sent from my LG-E975 using xda app-developers app
Rexkh said:
I did. it won't work. I used KDZ_FW_UPD_EN with .kdz file while putting my phone in Download Mode. Then the program restart the phone to proceed the installation but CWM recovery appear instead of stock recovery and nothing happen.
Click to expand...
Click to collapse
You need to flash official full KDZ upgrade. What phone you have originally? F180 or E975? or some other? Wipe + Factory reset in recovery before putting into download mode. (The major nuisance with this set is all you can do is power button thingi and no battery pullouts.
TELLUS: http://tny.cz/98a22ec6
BELL/BWA: http://tny.cz/a0b914fc
BELL Mobility: http://tny.cz/dce80a93
I finally found the solution accidentally, Just manually set the phone in Download Mode for 2nd time when it stuck in fastboot mode. Bingo!
Hi hoping someone can help, I accidentally wrote the wrong file to my system partition and am stuck at smartwatch 3 logo.
i tried pc companion and it tells be there "no software available for my device" all i can get to is fastboot mode stock recovery is gone too
I wrote twrp to it but as of yet have not been able to launch it. its running 5.1.1 os and i cant remember build number other than it began with an L
Please help
ZR1
if you read this and know i have no hope please let me know that too please
seems like if i had stock partitions images i could flash using adb i"d be good yes?? no?
I do not have time to help right now, but since you can get to fastboot, you are probably fine. Find the stock 5.1.1 recovery and boot to it. Then sideload the latest update. You will be good to go.
The command in a terminal window is...
Code:
Fastboot boot <stock recovery.img>
Alternatively, you can boot to twrp and install a twrp flushable zip.
Good luck.
Lekofraggle thank you for your help.
I did what you said with img file from this thread http://forum.xda-developers.com/sma...50-version-t2988087/post62897403#post62897403
it wrote the img file but still just hangs at boot image, and i still cant get twrp to work after holding power button and choosing recovery option screen goes blank and then starts to boot and hangs at smartwatch 3 image
all the things i"ve rooted before in my life i"ve never screwed up this bad.
zr1 said:
Lekofraggle thank you for your help.
I did what you said with img file from this thread http://forum.xda-developers.com/sma...50-version-t2988087/post62897403#post62897403
it wrote the img file but still just hangs at boot image, and i still cant get twrp to work after holding power button and choosing recovery option screen goes blank and then starts to boot and hangs at smartwatch 3 image
all the things i"ve rooted before in my life i"ve never screwed up this bad.
Click to expand...
Click to collapse
Have you tried Sony Companion to repair your watch?
If you were running 5.1.1, then the recovery you mention is for 5.0.1, so that might be the reason why you can not boot into it. See if you can find the stock recovery for 5.1.1
I have used the following method a couple of times now to get me out of trouble after playing around with my SW3
http://forum.xda-developers.com/smartwatch-3/general/guide-roll-watch-to-previous-software-t3176801
You can then use the stock recovery you already have and update via OTA files to get it back to the latest firmware or via Sony Companion.
I had the exact same issue after I did fastboot flash using corrupt system.img (which wasn't a snapshot that could be flashed but rather a tarball). Since you have TWRP installed you can confirm this by trying to mount system partition in recovery mode. After it fails, connect to recovery via adb and view latest kernel messages (dmesg). It should show something like "failed to locate ext4 filesystem".
If this is your case, you can use TWRP restore function to restore system from your TWRP backup. It will then erase the partition, mkfs.ext4 and write the files from tarball. This did the trick for me.
(If you don't have backup, try looking for downloads in other threads here)
Edit: Re-read your post. Since your TWRP is broken, try hotbooting it using fastboot boot new_boot.img (you can take it here)
ebones thank you thank you thank you
I had downloaded new_boot img already so im not sure what i was doing wrong but i did what you said and she booted right into TWRP i now have to sideload the right update.zip file and run it in twrp correct?
edit; having trouble sideloading wear-supersu.zip what is the correct command?
GOT IT!!! I installed stock rom from this thread http://forum.xda-developers.com/sma...rom-repacked-stock-rom-swr50-version-t2988087 through TWRP and it works cant thank you guys enough
Thanks ZR1
I have flashed many phones before my G4 and this is the first time I'm having to ask for help.
The firmware installed was AICP CM13, then the screen went green with a DemiGod message. I held the vol down button to reboot and it came back up. After a few restarts and green screens i figured I needed to reflash the firmware. I booted into Recovery and while wiping the device to flash a new firmware, TWRP crashed. After leaving it for half hour or so, I took the battery out to enter into TWRP so I can flash the new firmware. TWRP is no there to be seen. I hold down the vol down and power button, releasing power for second or two and choose to go into recovery. Every time the phone just gets stuck on the LG screen displaying "Bootloader state :Bootlader unlocked!".
In short, I have no firmware, the device has been wiped and TWRP doesn't seem to be working.
I have tried to flash a KDZ file (H81520A_00.kdz) using the flash guide here. This comes back as unsuccessful saying "connection to server failed". As shown below.
View attachment 3605673
The method to flash an .img file using cmd on the pc includes moving the 4gb .img file to the parent folder of the phone storage. I can't get to move any files whatsoever to my device so figured this method would not work.
Seems if I can somehow flash TWRP, then I should be able to install a new firmware.
Any help much appreciated.
Hi, Can you get an ADB connection to your phone, or get your phone into bootloader somehow. From there you could try 'fastboot boot recovery.img'?
If so, then from within TWRP you can flash twrp recovery so the recovery is then sorted. Then you could flash click here (the full version). This will then allow LG UP to find a connection. From there if you really wanted to can flash any KDZ as a proper reset. Hope it works buddy!!
rav101 said:
Hi, Can you get an ADB connection to your phone, or get your phone into bootloader somehow. From there you could try 'fastboot boot recovery.img'?
If so, then from within TWRP you can flash twrp recovery so the recovery is then sorted. Then you could flash click here (the full version). This will then allow LG UP to find a connection. From there if you really wanted to can flash any KDZ as a proper reset. Hope it works buddy!!
Click to expand...
Click to collapse
I can get into recovery but I am unsure as to how I could try 'fastboot boot recovery.img'. Would that be the same as flashing an img when the root method first came out?
AndHD2 said:
I can get into recovery but I am unsure as to how I could try 'fastboot boot recovery.img'. Would that be the same as flashing an img when the root method first came out?
Click to expand...
Click to collapse
Just to make sure you know. TWRP is your recovery. Your last message said you did not have TWRP?
When I first rooted my phone (and subsequently when I install a .kdz), I have to go into the bootloader and install TWRP. I personally do this by using the above command "fastboot boot recovery.img" with the recovery.img being placed on my computer in the same location as my adb installation. This command only boots up TWRP but does not flash it. I then flash twrp by having a copy of it on my external sd card. Within twrp you can select to flash zip, or there is an option to flash an image. I use this to flash twrp (from twrp... its a little inception like but it works). Once you have twrp up and running, you can install a rom. If you want to do flash a .kdz, I have found you need to be on a stock based rom in the first place hence why i referenced the v20a full system zip.
Hope that made sense.
Regards,
Ravi
It is late here and with me being tired I said recovery instead of download. I can boot into download mode but when I try to boot into recovery then it just goes straight to the LG splash screen and it will either remain in that screen or the green Demigod screen would come up.
I'm off to sleep and away from my laptop as I have to be up in 5 hours. Luckily I still have my Note 4 so at least I'm not without a phone in the morning. I will try the steps what you have suggested just as soon as I get back from work.
Many thanks
rav101 said:
Just to make sure you know. TWRP is your recovery. Your last message said you did not have TWRP?
When I first rooted my phone (and subsequently when I install a .kdz), I have to go into the bootloader and install TWRP. I personally do this by using the above command "fastboot boot recovery.img" with the recovery.img being placed on my computer in the same location as my adb installation. This command only boots up TWRP but does not flash it. I then flash twrp by having a copy of it on my external sd card. Within twrp you can select to flash zip, or there is an option to flash an image. I use this to flash twrp (from twrp... its a little inception like but it works). Once you have twrp up and running, you can install a rom. If you want to do flash a .kdz, I have found you need to be on a stock based rom in the first place hence why i referenced the v20a full system zip.
Hope that made sense.
Regards,
Ravi
Click to expand...
Click to collapse
I have finally got chance to sit down and have a go at performing the procedure listed above. I downloaded the adb and fastboot installation as outline here. It is the minimum to what this thread says I will need for my device. I moved the recovery.img to the installation location which were in Windows/programs files (x86)/Minimal adb and fastboot. I launched the program and typed in 'fastboot boot recovery.img'. I tried this in download mode, charging mode (phone off) and while on the LG flash screen where TWRP didnt load but in all cases I have had no response at all.
If someone can help the much appreciated.
AndHD2 said:
I have finally got chance to sit down and have a go at performing the procedure listed above. I downloaded the adb and fastboot installation as outline here. It is the minimum to what this thread says I will need for my device. I moved the recovery.img to the installation location which were in Windows/programs files (x86)/Minimal adb and fastboot. I launched the program and typed in 'fastboot boot recovery.img'. I tried this in download mode, charging mode (phone off) and while on the LG flash screen where TWRP didnt load but in all cases I have had no response at all.
If someone can help the much appreciated.
Click to expand...
Click to collapse
Hi @AndHD2, I'm sorry but I can't think of anything else
rav101 said:
Hi @AndHD2, I'm sorry but I can't think of anything else
Click to expand...
Click to collapse
I had another demigod type screen but this was grey and not green with less detail. However it did say it were a kernel error.
Is the handset still under warrenty with the bootloader unlocked. I have a feeling its not