[FIXED]
After installing CWM via FreeGee on my G Pro F240L, the device became softbricked (booting only into CWM). I tried various methods to unbrick. including the R&DTool flashing method, but encountered various errors, including the infamous battery error. When I looked at the device this morning, however, it had rebooted itself overnight and was now stuck on the LG boot logo, with the following small text in the top left corner:
Secure booting Error!
Cause: boot certification verify
The device no longer appears to be recognized in adb from my PC, and though it is still capable of booting into download mode I have had no luck with the methods posted by others for bypassing the battery-level error in the Support Tool/flasher. If anyone could help, that would be immensely appreciated.
Can you still get into recovery? And when in recovery does adb then detect the device?
chdrummerdude said:
Can you still get into recovery? And when in recovery does adb then detect the device?
Click to expand...
Click to collapse
No, I can't enter recovery, the only method of modifying firmware available to me seems to be Download Mode.
NuclearWynter said:
No, I can't enter recovery, the only method of modifying firmware available to me seems to be Download Mode.
Click to expand...
Click to collapse
So you have tried flashing back to stock using the flash tools? It's not ideal but it get the phone back up and running. I own a e980 so im not familiar with the battery error you speak of.
chdrummerdude said:
So you have tried flashing back to stock using the flash tools? It's not ideal but it get the phone back up and running. I own a e980 so im not familiar with the battery error you speak of.
Click to expand...
Click to collapse
Yep, tried several variations of the flashtool method. The battery error: at about 50% through the flashing process, it throws an error essentially saying the phone's battery needs to be at 100% in order to continue, problem being that the error comes up even when the battery is at 100% - and also comes up if I try with the battery removed from the phone.
Has anyone experienced a similar issue? I'm getting quite desperate.
Man if you could just get adb enabled.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
chdrummerdude said:
Man if you could just get adb enabled.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
That would certainly make things easier, but it seems impossible to do seeing as the phone either can't boot past the logo, or only into Download Mode.
NuclearWynter said:
That would certainly make things easier, but it seems impossible to do seeing as the phone either can't boot past the logo, or only into Download Mode.
Click to expand...
Click to collapse
Add my e980 to the list =/ just hit this problem as well. I have it worse though since I don't have a windows PC. Can't even get into recovery. All I get is the Boot up screen with the same message you received.
chdrummerdude said:
Man if you could just get adb enabled.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
hello
i have f240l i returned back to stock backup which i made CWM i received an OTA i accepted the phone restarted and after that its stuck in recovery mode only. what can i do to make this work again
I also used Freegee and it messed up my device. I don't think this tool works correctly for the OGP (e980).
Can anyone tell me if I can get back to the AT&T stock ROM using TWRP ? If so, how?
Sent from my LG-E980 using xda app-developers app
Related
So I bought myself a Galaxy Nexus from Ebay and it arrived today.
The problem with it is, that the seller told me he did an OTA Update that in the end causes endless Bootloops.
I thought to myself that this should be easy to solve by just flashing a custom rom but I don't even get to the Bootloader.
Whenever I press Volume Up + Down + Power the Google logo appears without vibrating or anything.
Then it goes on to the Nexus Bootscreen till it just restarts.
Any Ideas?
Does adb recognizes your de vice?
Sent from my Galaxy Nexus using xda app-developers app
Isn't it necessary to be able to boot to check that?
So it looks like my phone is soft bricked.
There's still the problem that I'm unable to get into the bootloader aswell as into download mode.
I also already tried the OMAP flash tool.
domimatik said:
Isn't it necessary to be able to boot to check that?
Click to expand...
Click to collapse
I got into a bootloop once and i could access adb.... maybe you can try...
Sent from my Galaxy Nexus using xda app-developers app
I sadly can't access ADB either. Bought myself a USB-Jig.
Anyone got experience in these kinda things?
domimatik said:
I sadly can't access ADB either. Bought myself a USB-Jig.
Anyone got experience in these kinda things?
Click to expand...
Click to collapse
It will get you into Odin mode similar to pressing Vol down + Power, then you can use Odin to flash a new firmware which is very dangerous and could brick your device if done wrong
DynamicRam said:
It will get you into Odin mode similar to pressing Vol down + Power, then you can use Odin to flash a new firmware which is very dangerous and could brick your device if done wrong
Click to expand...
Click to collapse
Yes... USB jig should do the trick.
Sent from my Galaxy Nexus using xda app-developers app
Successfully flashed a new rom on my nexus via Odin but I'm still unable to get into fastboot/bootloader.
Bootloop also occures whenever I start the device
I was doing a lot websurfing and the phone got hot but didn't think much of it. Then my screen imagine became distorted and a loud noise came out of the speaker. I had never seen it before. I figured the phone crashed. The power button didn't work, so I removed the battery and put it back in. Now the phone can't get past the "Google" screen (which blurs after a few moments). My phone is unlocked and rooted. It's been so long since I've flashed my phone that I don't know if the usb debugging is turned on and here's where my problem lays. I can't get the phone to be recognized by any of my computers. I've tried a bunch of tools, installing different drivers, and Odin. All of them can't see my phone. I can boot into Fastboot and Odin. I can sometimes boot into CWM, and if I do, all I see is "ClockworkMod recovery v5.8.0.2" and no other options. After 15 seconds, the phone will exit CWM and reboot.
Anyone have any ideas on how to fix this?
Can you boot into recovery and maybe full wipe and re flash? Have you tried a backup? Have you tried mounting in recovery? Should be SD or USB mount try that maybe. I'm not a Dev. But I would try all those first. Post back if possible.
Sent from my Galaxy Nexus using xda app-developers app
Man_Utd said:
I've tried a bunch of tools, installing different drivers, and Odin. All of them can't see my phone. I can boot into Fastboot and Odin. I can sometimes boot into CWM, and if I do, all I see is "ClockworkMod recovery v5.8.0.2" and no other options. After 15 seconds, the phone will exit CWM and reboot.
Click to expand...
Click to collapse
Since you can boot into fastboot, then follow this if you want to return to stock immediately and start fresh, or keep this method for later if you want to try some other solutions first. It is your choice
ahmadallica said:
Since you can boot into fastboot, then follow this if you want to return to stock immediately and start fresh, or keep this method for later if you want to try some other solutions first. It is your choice
Click to expand...
Click to collapse
I can boot into fastboot, but it does me no good if I can't get my computer and phone to communicate. This is where my problem lies. I've tried different USB drivers and none of them work.
savagehax said:
Can you boot into recovery and maybe full wipe and re flash? Have you tried a backup? Have you tried mounting in recovery? Should be SD or USB mount try that maybe. I'm not a Dev. But I would try all those first. Post back if possible.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I can boot into CWM, but there is no option to flash or wipe. All I see is one line of text. That's it.
ahmadallica said:
Since you can boot into fastboot, then follow this if you want to return to stock immediately and start fresh, or keep this method for later if you want to try some other solutions first. It is your choice
Click to expand...
Click to collapse
Man_Utd said:
I can boot into fastboot, but it does me no good if I can't get my computer and phone to communicate. This is where my problem lies. I've tried different USB drivers and none of them work.
Click to expand...
Click to collapse
Did you try the "Universal Naked Drivers" linked in ahmadallica's post?
Sent from my Nexus 4 using Tapatalk 2
Man_Utd said:
I can boot into fastboot, but it does me no good if I can't get my computer and phone to communicate. This is where my problem lies. I've tried different USB drivers and none of them work.
Click to expand...
Click to collapse
I think it is bettER to uninstall the drivers you have already, and try another USB port. Did you try that as well?
Download the galaxy Nexus toolkit and that will apply the stock image vai google. You can restore your phone from scratch back to stock.
Sent from my Galaxy Nexus using Tapatalk 2
3rdstring said:
Did you try the "Universal Naked Drivers" linked in ahmadallica's post?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
3rdstring said:
Did you try the "Universal Naked Drivers" linked in ahmadallica's post?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Okay, I figured out why my computer couldn't see the phone. The USB cable was bad. It charged the phone, so I assumed it worked. Tried another cable and now the computer sees the device. Stupid cable!
So, I got going using fastboot but now I have another problem. I can connect to the phone and my computer sees it, but when I try a flash command like "fastboot flash bootloader bootloader.img", I get "Failed (status read failed (Too many links))". I've been doing some reading and see this is not a good thing.
I haven't tried Odin, because I read in another post by efrant, not to use Odin if I'm getting the "Failed (status..."
I probably have a hardware issue, right? Any suggestions?
Thanks to everyone for their input!!!
I tried using fastboot to boot into the latest recovery .img file. Again, all I got was the title "ClockworkMod Recovery Mod 6.0.1.9"
Man_Utd said:
I tried using fastboot to boot into the latest recovery .img file. Again, all I got was the title "ClockworkMod Recovery Mod 6.0.1.9"
Click to expand...
Click to collapse
Try using fastboot to flash TWRP recovery image not CWM.
Download it from here if you have GSM GNex (Maguro), otherwise, just choose your device from the same website
And what about returning to stock using fastboot? You changed the USB cable so seems this should work with you now.
ahmadallica said:
Try using fastboot to flash TWRP recovery image not CWM.
Download it from here if you have GSM GNex (Maguro), otherwise, just choose your device from the same website
And what about returning to stock using fastboot? You changed the USB cable so seems this should work with you now.
Click to expand...
Click to collapse
I just tried TWRP recovery and got "Failed (status read failed (Too many links))".
I also tried using fastboot to return to Android stock rom. That didn't work either.
I think I'm screwed. Man, I didn't even overclock the cpu. :crying:
Man_Utd said:
I just tried TWRP recovery and got "Failed (status read failed (Too many links))".
I also tried using fastboot to return to Android stock rom. That didn't work either.
I think I'm screwed. Man, I didn't even overclock the cpu. :crying:
Click to expand...
Click to collapse
Well, I searched for that error and found this thread. I checked it quickly and there are many suggestions up there to solve the issue like changing the cable, ports, and so on. So please take some time to read through it and try the various solutions so hopefully this error will be solved
I too have had issues with cables. Never that same error but I've had read and write errors. I've resorted to using a 3yr old Motorola Droid power cable because it seems to be built the best. I've also had success using different ports and computers.
Also instead of updating the drivers to the newest try deleting the device out if device manager and rebooting and then installing the device new. That has fixed a "hardware component ID" error I had
Sent from my Nexus 7 using Tapatalk HD
Today my Gnex randomly rebooted, then got stuck rebooting. it now starts gets all the way to the home screen then reboots, then the cycle starts over. I am rooted runny shiney rom. nothing new installed recently and as stated before the phone was running normal the rebooted out of the the blue.
I have cleared cache, davik and done factory wipe, all to no avail.
the text on bottom of my bootloader reads:
Product name-tuna
variant- toro 32gb
hw version-10
bootloader version primemd04
baseband version-i515.fk02 cdma-unknown
carrier info-none
i cant flash the factory image because the phone doesn't stay powered on long enough to stay connected to the computer. apparently when i re flashed and root i forgot to make a back up so i can not restore that way either.
You could try pulling battery put back in and hold volume buttons and power to get into fastboot mode and flash factory image. Maybe you already tried this but maybe not so thought I'd throw my thoughts your way.
Sent from my Galaxy Nexus using xda app-developers app
tshelby73 said:
You could try pulling battery put back in and hold volume buttons and power to get into fastboot mode and flash factory image. Maybe you already tried this but maybe not so thought I'd throw my thoughts your way.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I have tried that but I cant get the factory image save to my phone to flash it. Now is the only time i have missed removable memory
jj69chev said:
I have tried that but I cant get the factory image save to my phone to flash it. Now is the only time i have missed removable memory
Click to expand...
Click to collapse
the phone reboot itself even when it is on bootloader mode? thats really rarely if not impossible
jj69chev said:
I have tried that but I cant get the factory image save to my phone to flash it. Now is the only time i have missed removable memory
Click to expand...
Click to collapse
So you neef help flashing the Factory image? Pm me if you do. I will help
Sent from my Galaxy Nexus using XDA Premium HD app
jj69chev said:
I have tried that but I cant get the factory image save to my phone to flash it. Now is the only time i have missed removable memory
Click to expand...
Click to collapse
You don't put image on phone you flash it using fastboot command from computer.
If you don't know how get with previous poster.
Sent from my Galaxy Nexus using xda app-developers app
andQlimax said:
the phone reboot itself even when it is on bootloader mode? thats really rarely if not impossible
Click to expand...
Click to collapse
No it doesnt reboot when in recovery, but i dont have the factory image save on the device.
tshelby73 said:
You don't put image on phone you flash it using fastboot command from computer.
If you don't know how get with previous poster.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Fastboot gives me the device not found error, I will get with previous poster as well
jj69chev said:
Fastboot gives me the device not found error, I will get with previous poster as well
Click to expand...
Click to collapse
You might not have the right drivers. Have you used fastboot before?
Sent from my Galaxy Nexus using xda app-developers app
tshelby73 said:
You might not have the right drivers. Have you used fastboot before?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I Have the correct drivers, and have used fast boot before. i think i get the error because when i factory reset it, that turns off the debugging mode.
jj69chev said:
I Have the correct drivers, and have used fast boot before. i think i get the error because when i factory reset it, that turns off the debugging mode.
Click to expand...
Click to collapse
Debugging mode is only important when you are trying to use adb while booted into Android. In the bootloader, debugging being on or off doesn't matter. It also doesn't matter in recovery either.
Something is wrong somewhere, drivers are usually the best place to start as it is probably the most common reason why the device doesn't communicate with fastboot. Other things to try are different USB cables and USB ports.
jj69chev said:
I Have the correct drivers, and have used fast boot before. i think i get the error because when i factory reset it, that turns off the debugging mode.
Click to expand...
Click to collapse
Well looks like you know what your doing so looks like you have a major issue beyond my skill level. Sorry i couldn't help. Never tried it but Odin may be a thought. If you can get into recovery you could side load using adb also.
Sent from my Galaxy Nexus using xda app-developers app
cupfulloflol said:
Debugging mode is only important when you are trying to use adb while booted into Android. In the bootloader, debugging being on or off doesn't matter. It also doesn't matter in recovery either.
Something is wrong somewhere, drivers are usually the best place to start as it is probably the most common reason why the device doesn't communicate with fastboot. Other things to try are different USB cables and USB ports.
Click to expand...
Click to collapse
When Fast booting i can not flash radio-cdma... i get an "unknown error" does this mean my cdma radio is shot?
jj69chev said:
When Fast booting i can not flash radio-cdma... i get an "unknown error" does this mean my cdma radio is shot?
Click to expand...
Click to collapse
Have you tried the flash-all it seems to do some formatting that may help but I think it does that later after the radios. Warning it will wipe your phone including sdcard.
Sent from my Galaxy Nexus using xda app-developers app
Have you tried connecting it into download mode, and then flash an odin image through odin? with that method you wont need to actually put the image onto the device but rather odin just copies it over for you while flashing the phone at the same time.
Same issue
My phone started randomly rebooting, and wont stop, it can't get past the lock screen without crashing on me. However i went into recovery, wiped everything, and flashed back to the stock rom ( i was running the shiny 4.3 rom) and the issue is still persistng, anyone know what can be done, or is something possibly wrong with the hardware?
Fahull said:
My phone started randomly rebooting, and wont stop, it can't get past the lock screen without crashing on me. However i went into recovery, wiped everything, and flashed back to the stock rom ( i was running the shiny 4.3 rom) and the issue is still persistng, anyone know what can be done, or is something possibly wrong with the hardware?
Click to expand...
Click to collapse
You found this thread but didn't read it? Seriously? This isn't 1000+ pages.... As suggested: use fastboot to flash the Factory image with the flash-all.bat.
Sent from my Galaxy Nexus using XDA Premium HD app
Fahull said:
My phone started randomly rebooting, and wont stop, it can't get past the lock screen without crashing on me. However i went into recovery, wiped everything, and flashed back to the stock rom ( i was running the shiny 4.3 rom) and the issue is still persistng, anyone know what can be done, or is something possibly wrong with the hardware?
Click to expand...
Click to collapse
I was also running shiney 4.3. I had to get a new phone because nothing I tried helped. I'm no expert but it seems to me that the CDMA radio is toast in mine/
Please does anyone knows a workaround on the battery low error while flashing kdz file on flashtools..please help me on this matter..i really need it badly..thanks in advance..
help
help please..update on this problem
Doesnt anybody experience thia kind of problem?please if anyone is having the same problem,please share your experience here.coz i read that a lot of people experience this..
Sent from my Q360 using xda app-developers app
Have you tried this link?
http://forum.xda-developers.com/showthread.php?t=2559828
Sent from my Nexus 7 using xda app-developers app
luenboy said:
Please does anyone knows a workaround on the battery low error while flashing kdz file on flashtools..please help me on this matter..i really need it badly..thanks in advance..
Click to expand...
Click to collapse
Workaround:
Make use of your installed/reinstalled recovery system to restore a rom or better nandroid-backup that is already as close as possible to your stock firmware. From there the kdz flasher should work (at least according to my own experience).
This backup worked for me(E986)
http://storagecow.eu/Xda/Users/Anirudhks-OptimusGPro/Stock.rar
xifizurk said:
Workaround:
Make use of your installed/reinstalled recovery system to restore a rom or better nandroid-backup that is already as close as possible to your stock firmware. From there the kdz flasher should work (at least according to my own experience).
This backup worked for me(E986)
http://storagecow.eu/Xda/Users/Anirudhks-OptimusGPro/Stock.rar
Click to expand...
Click to collapse
I would love to see that my phone is at recovery mode..but i cant access it no matter what i do..i've tried the button combination but it fails to load cwm.i already have backup of my entire system on cwm,if only there is a way to install cwm or twrp on this to access recovery.or if there is a way to force this to boot recovery,there will be no problem
Sent from my Q360 using xda app-developers app
jimi_pooh said:
Have you tried this link?
http://forum.xda-developers.com/showthread.php?t=2559828
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Ive already tried that but keeps on getting an error after extracting the kdz file..
Sent from my Q360 using xda app-developers app
luenboy said:
I would love to see that my phone is at recovery mode..but i cant access it no matter what i do..i've tried the button combination but it fails to load cwm.i already have backup of my entire system on cwm,if only there is a way to install cwm or twrp on this to access recovery.or if there is a way to force this to boot recovery,there will be no problem
Sent from my Q360 using xda app-developers app
Click to expand...
Click to collapse
As far i understand yiu wont to go back to stock with kdz flashing. What is the reason? You say u cant get in recovery mode, so u havent the recovery bootloop after installing freegee. Why u wont to flash back to stock? Doesnt your g pro starts?
lg-user45 said:
As far i understand yiu wont to go back to stock with kdz flashing. What is the reason? You say u cant get in recovery mode, so u havent the recovery bootloop after installing freegee. Why u wont to flash back to stock? Doesnt your g pro starts?
Click to expand...
Click to collapse
No,my phone is stuck at lg logo.it wont pass that..and the reason why it is stuck is i flashed a custom kernel for lg e988..after flashing,it wont boot up..i can only access download mode..if i flash it using kdz updater,i kept on getting error extracting file..if i use lg online support,i kept getting battery level low error.if i use the tutorial how to bypass the battery low issue,im getting error after extracting kdz file..
Sent from my Q360 using xda app-developers app
I had 2 times problems with low battery issue. I passed it only changing from Diag mode to emergency.
And also it seems to me that the kdz flashing procedure passes only randomly without battery issue. But only on emergency.
I also reinstalled all drivers to reactivate usb ports. With some patience it should pass through
lg-user45 said:
I had 2 times problems with low battery issue. I passed it only changing from Diag mode to emergency.
And also it seems to me that the kdz flashing procedure passes only randomly without battery issue. But only on emergency.
I also reinstalled all drivers to reactivate usb ports. With some patience it should pass through
Click to expand...
Click to collapse
Still no luck..doe anyone here knows where i can download tot file or anyone knows how to convert .kdz to .oct?
Sent from my Q360 using xda app-developers app
Hi!
A few days ago I flashed Gohma rom and smart me, pressed reset device at the settings. after that there was bootloop. I tried to flash stock image through fastboot, it flashed succesfully but now I cannot get out of that bootloader screen. I have tried every stock images but no luck... Whenever I power on the device it vibrates three times immediately and boots to bootloader.
So, do you have any advice here?
In the gohma ROM zip, there's a return to stock script. Try to remove the two adb commands from that script and run it to flash your watch.
It's helped some other people.
Sent from my GT-N7100 using XDA Free mobile app
dproldan said:
In the gohma ROM zip, there's a return to stock script. Try to remove the two adb commands from that script and run it to flash your watch.
It's helped some other people.
Sent from my GT-N7100 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the advice, but didnt work... still stuck on the bootloader screen :/ guess I'll send it back and hope to get replacement...
Memmpf said:
Thanks for the advice, but didnt work... still stuck on the bootloader screen :/ guess I'll send it back and hope to get replacement...
Click to expand...
Click to collapse
I had the same and I put my watch in boot loader mode and used the Super Tool found in developer area and pushed the boot loader and system to the phone and was able to get it to boot...give that a try