Related
Hi XDA,
I've searched in many threads but i can't find an anwser.
I've bricked my Galaxy Gio when i flashed a custom kernel. It was the kernel in this thread http://forum.xda-developers.com/showthread.php?t=1319816
Now it does nothing, I can't boot in any mode, not in download mode, not in recovery mode...
I have android 2.3.3 Gingerbread.
Is there any way to unbrick or is my phone just an expensive decoration now.
Thanks in Advance.
Hi !!!
same new here
This ll work in some cases
Hope this will work in your device as well
Pull the battery to kill the boot loop (or whatever is hosed up), put the phone into downloading mode and re-flash the stock ROM.
Free to try...
Thanks for quick reply but i can't go into download mode as i said. Also my phone is just totally off and won't boot at all. My pc also doesn't detect it when it is plugged in.
SuperUub said:
Thanks for quick reply but i can't go into download mode as i said. Also my phone is just totally off and won't boot at all. My pc also doesn't detect it when it is plugged in.
Click to expand...
Click to collapse
If not even adb detects it, i'm pretty sure you're buggered, mate.
did you try and leave the battery out for some 10 min or more?
If adb does not detect the phone after that, then it seems to be a brick for real.
Is your phone stop at the "samsung" when you turn on your phone?
If is this,it's very easy to unbrick
One easy procedure which you might want to try with no guarantee it'll work:
-Remove the battery, microSD and SIM from the phone.
-Prepare the Odin software and your ROM on a known working system
-Connect the phone to the computer with the USB cable.
-With one hand, simultaneously hold Volume down, home and power.
-With your other hand, put the battery in the phone.
I was able to get Odin to detect an otherwise bricked phone this way. I was however unable to get further than the "setup connection" step. Maybe your outcome will be better.
Regards,
Darkshado
+
Yes this way usually works. I've tested this way.
that worked for me to on a brick when it didnt even went on, no recovery, download mode etc, after waiting 2 weeks and trying to repair it myself I nearly throw it away, and then suddenly it went into download mode for about 1 or 2 seconds, wich told me the battery whasn't working.. so I started to charge the battery, and hoped it would boot, but it didn't.. using that method given above, I could get into download mode again, and flashes a new stock ROM. now I still have my phone, working.
Odin to detect
Darkshado said:
One easy procedure which you might want to try with no guarantee it'll work:
-Remove the battery, microSD and SIM from the phone.
-Prepare the Odin software and your ROM on a known working system
-Connect the phone to the computer with the USB cable.
-With one hand, simultaneously hold Volume down, home and power.
-With your other hand, put the battery in the phone.
I was able to get Odin to detect an otherwise bricked phone this way. I was however unable to get further than the "setup connection" step. Maybe your outcome will be better.
Regards,
Darkshado
Click to expand...
Click to collapse
i i need help, odin detects my phone but dont pass from -"setup connection", did you have news?
I had my mainboard replaced at a service center... Probably not the news you would have liked, but I'm afraid that's your next step as well.
Darkshado said:
One easy procedure which you might want to try with no guarantee it'll work:
-Remove the battery, microSD and SIM from the phone.
-Prepare the Odin software and your ROM on a known working system
-Connect the phone to the computer with the USB cable.
-With one hand, simultaneously hold Volume down, home and power.
-With your other hand, put the battery in the phone.
I was able to get Odin to detect an otherwise bricked phone this way. I was however unable to get further than the "setup connection" step. Maybe your outcome will be better.
Regards,
Darkshado
Click to expand...
Click to collapse
This worked for me too, try to charge your battery in another phone if possible
bobcota said:
i i need help, odin detects my phone but dont pass from -"setup connection", did you have news?
Click to expand...
Click to collapse
same problem
same problem here
voetbalremco said:
that worked for me to on a brick when it didnt even went on, no recovery, download mode etc, after waiting 2 weeks and trying to repair it myself I nearly throw it away, and then suddenly it went into download mode for about 1 or 2 seconds, wich told me the battery whasn't working.. so I started to charge the battery, and hoped it would boot, but it didn't.. using that method given above, I could get into download mode again, and flashes a new stock ROM. now I still have my phone, working.
Click to expand...
Click to collapse
i also have the same prblem here just now , i tried to flash this ROM but i forgot to wipe data/factory reset the phne and i unintentionally flashed the rom without wiping it :'( and now, dont boot at all but can still turned on and ended up just "samsung" appearing on the screen . please help :crying::crying:
I've bricked my Galaxy Gio when i flashed a custom kernel.
Hi There I also have the same problem. I installed Galaxy Ace's Kernel onto my Galaxi Gio, Now it does nothing, I can't boot in any mode, not in download mode, not in recovery mode...
S[B said:
[/B]uperUub;20668671]Hi XDA!
I've searched in many threads but i can't find an anwser.
I've bricked my Galaxy Gio when i flashed a custom kernel. It was the kernel in this thread http://forum.xda-developers.com/showthread.php?t=1319816
Now it does nothing, I can't boot in any mode, not in download mode, not in recovery mode...
I have android 2.3.3 Gingerbread.
Is there any way to unbrick or is my phone just an expensive decoration now.
Thanks in Advance.
Click to expand...
Click to collapse
Not either going to Download Mode
trackIDtracker said:
Hi !!!
same new here
This ll work in some cases
Hope this will work in your device as well
Pull the battery to kill the boot loop (or whatever is hosed up), put the phone into downloading mode and re-flash the stock ROM.
Free to try...
Click to expand...
Click to collapse
When I finish restore my back up, I reboot my phone and it get brick (JUGG 5.0)!!! I cannot even press any button to turn the screen on!! Already try with different charger, battery and sim card also!! Does someone have any idea please!!
Try the long power button press. Press the power button and hold it for like 10 seconds (Maybe more, it always feels more then 10 seconds). The phone should vibrate 3 times and then you release.
If that doesn't work, then see if you can get into download mode and get Odin to recognize your phone.
I already try, I press it nearly 1 minute, but the screen doesn't turn on!
what exactly are you doing? you were making a backup in cwm, it finished and then you rebooted?
I flash a new Rom, but I don't like it. So I use Darkside Superwipe to wipe all cache and data of that Rom so that I can do the back up. After the back up process is finished,(I see everything runs well). I reboot the phone and it gets brick.
gunbreak said:
I flash a new Rom, but I don't like it. So I use Darkside Superwipe to wipe all cache and data of that Rom so that I can do the back up. After the back up process is finished,(I see everything runs well). I reboot the phone and it gets brick.
Click to expand...
Click to collapse
I am not quite understanding. You made backup, or did you restore a backup that you previously made? Anyways, If the phone wont boot try to put in in dl mode and odin it back to stock.
xcrazydx said:
I am not quite understanding. You made backup, or did you restore a backup that you previously made? Anyways, If the phone wont boot try to put in in dl mode and odin it back to stock.
Click to expand...
Click to collapse
Oh I understand u, I restore my back up. How can I put it in the mode that you say? I can't even turn the screen on can you please help me!
gunbreak said:
Oh I understand u, I restore my back up. How can I put it in the mode that you say? I can't even turn the screen on can you please help me!
Click to expand...
Click to collapse
Before you try to odin it, can you get into cwm by holding the volume up, down, and power. Release power when first samsung logo appears. stay holding vol buttons until cwm pops up. can you get into this?
xcrazydx said:
Before you try to odin it, can you get into cwm by holding the volume up, down, and power. Release power when first samsung logo appears. stay holding vol buttons until cwm pops up. can you get into this?
Click to expand...
Click to collapse
No, it doesn't work. All the buttons freeze now
You most likely are hard bricked, but you still have a slight chance to get into download mode. Not sure how you managed a brick by restoring a backup, but I'll try to help.
Ok, you are going to need the drivers for your phone. http://www.mediafire.com/file/6onrjbyd46j4lhj/T-Mobile_t989_GSII_ADB_Drivers.zip
You need odin as well, download it. http://www.mediafire.com/?u868rqz4qn0ta34
These links were provided by KonstantinKeller
Go here http://www.sammobile.com/firmware/ and make an account. I use sammobile because it contains everything in one shot. No need to get radio and crap from other places. After you make an account go to firmware section and type t989 in the search box. download the t989uvkid. ASSUMING YOU HAVE AMERICAN T989
After you have completed the download you are going to need to unzip it with 7zip to extract the tar.
Plug the USB cable into your computer, without plugging it into your phone.
Hold VOL UP + VOL DOWN while plugging in the USB cable to your phone. Stop holding buttons when the ''Warning'' appears.
Press Volume UP and start ODIN (Run as Admin on Vista and 7, just to be safe)
Click PDA and locate the MD5 file you extracted earlier.
WAIT FOR ODIN TO RECOGNIZE YOUR PHONE. THE COM PORT WILL TURN YELLOW AND HAVE A NUMBER
MAKE SURE NOTHING BUT AUTO REBOOT IS CHECKED!!!!!!!
Press 'Start' and be patient. It will take a few minutes because it is a large file.
phone will reboot automatically.
If you can't get the phone to be recognized try different usb ports or a different computer if you have another. This may not work at all, considering it sounds like you are hard bricked. Good luck!
I should download T989UVKID or T989UVKL1? I think my phone get android 2.3.6
gunbreak said:
I should download T989UVKID or T989UVKL1? I think my phone get android 2.3.6
Click to expand...
Click to collapse
it won't matter. if you want the newest grab kL1
Window told me "no driver found" after I already installed the samsung driver!
gunbreak said:
Window told me "no driver found" after I already installed the samsung driver!
Click to expand...
Click to collapse
Delete that driver setup and use kies. http://www.samsung.com/us/kies/
I think it already died, no driver found again. I try in device manager, it appears as Samsung Android ADB interface, but nothing appears on my screen it's such a hard brick....
gunbreak said:
I think it already died, no driver found again. I try in device manager, it appears as Samsung Android ADB interface, but nothing appears on my screen it's such a hard brick....
Click to expand...
Click to collapse
Just do this and see if it goes into DL mode.
Plug the USB cable into your computer, without plugging it into your phone.
Hold VOL UP + VOL DOWN while plugging in the USB cable to your phone. Stop holding buttons when the ''Warning'' appears.
If not, you have 2 options
Send to this guy for jtag repair for $50 http://mobiletechvideos.mybigcommerce.com/
OR warranty it through samsung
I should warranty it through Samsung or ask for replacement phone through Tmobile? (I have insurance in my plan). I wonder if Tmobile find out my phone is rooted and I have to pay for the replacement phone. Do you have any idea?
gunbreak said:
I should warranty it through Samsung or ask for replacement phone through Tmobile? (I have insurance in my plan). I wonder if Tmobile find out my phone is rooted and I have to pay for the replacement phone. Do you have any idea?
Click to expand...
Click to collapse
You can go to the tmobile store and tell them it wont turn on. you wont need your insurance plan, the phone carries a warranty against defects for 1 year. Just play dumb and say it wont turn on and demand a new phone.
Do u have any idea if Tmobile check the phone or not?
gunbreak said:
Do u have any idea if Tmobile check the phone or not?
Click to expand...
Click to collapse
They can't tell anything if it's hard bricked. You're fine man, Get a new one.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
So by the heading you guys must know I have messed up pretty badly.
Let me tell you first, I have done my research. Tried each and every thing possible (AFAIK) but it just wont boot into recovery.
FLASHBACK: ( I have Sff) (Volume button is broken).
1) Did a clean wipe ( Cache, Dalvik, System),
2) Installed Ignorance V4, ( I thought the kernel must be in the zip, so didnt flash the kernel)
3) Phone booted and stuck in splashscreen. ( Ignorance)
4) Connected it to Laptop via USB. Checked ADB. Device not found.
5) Switched off device, connected to laptop, checked ADB, Device not found.
6) Checked through device manager, and device manager recognizes the phone. All drivers are installed and updated. Windows Vista.
Now, what to do? Is there any way I can get into recovery or even Hboot so that I can flash kernel?.
Need help
Owner of a messed up V.
Vickrant.
myhtconeV said:
So by the heading you guys must know I have messed up pretty badly.
Let me tell you first, I have done my research. Tried each and every thing possible (AFAIK) but it just wont boot into recovery.
FLASHBACK: ( I have Sff) (Volume button is broken).
1) Did a clean wipe ( Cache, Dalvik, System),
2) Installed Ignorance V4, ( I thought the kernel must be in the zip, so didnt flash the kernel)
3) Phone booted and stuck in splashscreen. ( Ignorance)
4) Connected it to Laptop via USB. Checked ADB. Device not found.
5) Switched off device, connected to laptop, checked ADB, Device not found.
6) Checked through device manager, and device manager recognizes the phone. All drivers are installed and updated. Windows Vista.
Now, what to do? Is there any way I can get into recovery or even Hboot so that I can flash kernel?.
Need help
Owner of a messed up V.
Vickrant.
Click to expand...
Click to collapse
Which recovery u have ??
If you have Cwm...Let ua battery drain completely and then put in on charge, it will boot into cwm directly. That's the only option.
If you have TWRP, lol..I'd Suggest you torepair your Vol Buttons
red de0392 said:
Which recovery u have ??
If you have Cwm...Let ua battery drain completely and then put in on charge, it will boot into cwm directly. That's the only option.
If you have TWRP, lol..I'd Suggest you torepair your Vol Buttons
Click to expand...
Click to collapse
Thanks for replying ya
Unfortunately I have TWRP. So my one v is going for repairs :crying::crying:. Still not given up...trying it on my other lappy, lets see if adb picks it up there.
myhtconeV said:
Thanks for replying ya
Unfortunately I have TWRP. So my one v is going for repairs :crying::crying:. Still not given up...trying it on my other lappy, lets see if adb picks it up there.
Click to expand...
Click to collapse
Don't Sweat too Much Mate. It Won't boot into recovery.
Well My Vol Buttons are Dying As well...Will flash CWM Now
We should Learn from other
red de0392 said:
Don't Sweat too Much Mate. It Won't boot into recovery.
Well My Vol Buttons are Dying As well...Will flash CWM Now
We should Learn from other
Click to expand...
Click to collapse
:good: what if i try that with mine?
Downloading HTC Sync Manager. Hope the updated drivers work. Called up my IT guy. He is giving me a quote on repairs tomorrow. Come to think of it, my one v was bound to end like this. Screen broken and shattered at 2 places, headphone jack socket gone, volume buttons gone.
Now upgrading to...........................wait for it............................ Nokia 1100.
myhtconeV said:
:good: what if i try that with mine?
Downloading HTC Sync Manager. Hope the updated drivers work. Called up my IT guy. He is giving me a quote on repairs tomorrow. Come to think of it, my one v was bound to end like this. Screen broken and shattered at 2 places, headphone jack socket gone, volume buttons gone.
Now upgrading to...........................wait for it............................ Nokia 1100.
Click to expand...
Click to collapse
Hahahah...That's a Beast
myhtconeV said:
So by the heading you guys must know I have messed up pretty badly.
Let me tell you first, I have done my research. Tried each and every thing possible (AFAIK) but it just wont boot into recovery.
FLASHBACK: ( I have Sff) (Volume button is broken).
1) Did a clean wipe ( Cache, Dalvik, System),
2) Installed Ignorance V4, ( I thought the kernel must be in the zip, so didnt flash the kernel)
3) Phone booted and stuck in splashscreen. ( Ignorance)
4) Connected it to Laptop via USB. Checked ADB. Device not found.
5) Switched off device, connected to laptop, checked ADB, Device not found.
6) Checked through device manager, and device manager recognizes the phone. All drivers are installed and updated. Windows Vista.
Now, what to do? Is there any way I can get into recovery or even Hboot so that I can flash kernel?.
Need help
Owner of a messed up V.
Vickrant.
Click to expand...
Click to collapse
Recently I have seen one interesting issue that might appear like solution to your problem. According to the description you may try turning off your phone and plugging in a charger. If you will have the same behaviour your phone should start into recovery mode. =)
Edited: Doh! TWRP...
You may try All-In-One-Kit as well. It has high level interface to run adb commands (including Boot into Recovery). Yeah yeah, I've seen your note that adb does not recognize your device, anyway...
Stupid answer from me....... Op are both your volume buttons broken?
Sent from my Nexus 7 using Tapatalk
heavy_metal_man said:
Stupid answer from me....... Op are both your volume buttons broken?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yes.
I have given it for repairs.I have decided not to sell or dispose it.
Its only sometime before I buy a moto g or xperia device. Waiting for my new credit card :fingers-crossed:
which phone would you suggest?
Vickrant.
If you are good with 16gb storage better buy Moto G if not there are a few options like Xperia M , Canvas series and all..
Sorry to be so late to the party, but in case other people get this issue. ADB will often work just after the kernel finishes loading, before it gets shut off. So between the htc boot screen and when the boot anim starts you have a window to commit abd commands. I often use this to save time when flashing kernels etc, notably because my WIP roms rarely make it past bootanim!
red de0392 said:
Which recovery u have ??
If you have Cwm...Let ua battery drain completely and then put in on charge, it will boot into cwm directly. That's the only option.
If you have TWRP, lol..I'd Suggest you torepair your Vol Buttons
Click to expand...
Click to collapse
You sure about this?i am stuck there and i have cwm recovery installed,will it switch itself straight to recovery after the battery is dried up?i am using sony xperia c
Every time i try to boot up my phone, the logo screen shows up, and then it immediately gets redirected to ClockWorkMod.
I'm able to do everything in ClockWorkMod, but that's about it. All of Clockworkmod's features seem to work though.
I'm also able to enter into bootloader by holding the power button and the volume down button.
I tried doing a clean factory reset, but all it did was redirect me to ClockWorkMod.
Any suggestions on how to get out of this loop?
Cinestra said:
Every time i try to boot up my phone, the logo screen shows up, and then it immediately gets redirected to ClockWorkMod.
I'm able to do everything in ClockWorkMod, but that's about it. All of Clockworkmod's features seem to work though.
I'm also able to enter into bootloader by holding the power button and the volume down button.
I tried doing a clean factory reset, but all it did was redirect me to ClockWorkMod.
Any suggestions on how to get out of this loop?
Click to expand...
Click to collapse
Install a rom.
Unable to install a rom
Chilidog said:
Install a rom.
Click to expand...
Click to collapse
I originally got into this spot when I was trying to install ViperOne onto my phone. Unfortunately, I don't have any other roms on my phone right now, and my computer doesn't recognize my phone while it's in ClockWorkMod or while it's in Bootloader (although I do here a ding sound whenever I connect my HTC One to the computer, I just can't see where the driver is at. And I'm not quite sure if I can do anything with it anyways).
Because my computer is unable to recognize my phone, I can't put on any roms onto my phone. So I can't install any new ones.
Go buy a usb-otg cable and a usb flash drive. You can get them both for under 20 bucks. Even cheaper if you already have a usb flash drive 5 bucks.
That seems like a viable solution
cmlusco said:
Go buy a usb-otg cable and a usb flash drive. You can get them both for under 20 bucks. Even cheaper if you already have a usb flash drive 5 bucks.
Click to expand...
Click to collapse
Thank you for the advice, that seems like a viable solution. However, are there any other solutions that wouldn't require me buying external hardware? I don't understand how I really even got into this recovery loop in the first place...
Would you just download a rom onto the card, plug that into the USB-otg cable, and then install it on the phone?
I'm just wondering... is it certain that the rom is the problem though?
What if it's the Clockworkmod?
If possible, I would just like to revert back to TWRP so i could just load its backups.
Resolved
I was able to revert from ClockWorkMod recovery to TWRP using this tutorial: https://www.youtube.com/watch?v=jnESTcH2ioA and then i was able to recover my system to its original point. Thank you all for the advice!
Apparently my phone is bricked..
I rooted my phone a long time ago when I first got it, never installed any roms or anything.
I get this message on the LG Screen:
"Secure Booting Error problem
Device UnLock!!, so Boot Success!!"
I've tried multiple ways to fix my phone and I can't get any of them working.
I'd be happy to pay the person in a steam game of your choice!!!!
Thank you
AustinBobDox said:
Apparently my phone is bricked..
I rooted my phone a long time ago when I first got it, never installed any roms or anything.
I get this message on the LG Screen:
"Secure Booting Error problem
Device UnLock!!, so Boot Success!!"
I've tried multiple ways to fix my phone and I can't get any of them working.
I'd be happy to pay the person in a steam game of your choice!!!!
Thank you
Click to expand...
Click to collapse
If you use lg flash tool to go back to stock it should work.
2SHAYNEZ
shayneflashindaily said:
If you use lg flash tool to go back to stock it should work.
2SHAYNEZ
Click to expand...
Click to collapse
I tried but the drivers won't install correctly. They did once, but it just said something along the lines of "Ready", and never did anything even after plugging and unplugging.
AustinBobDox said:
I tried but the drivers won't install correctly. They did once, but it just said something along the lines of "Ready", and never did anything even after plugging and unplugging.
Click to expand...
Click to collapse
Uninstall and reinstall drivers ... Try different computer. Lg flash tools should fix your problem . goodluck
2SHAYNEZ
AustinBobDox said:
I tried but the drivers won't install correctly. They did once, but it just said something along the lines of "Ready", and never did anything even after plugging and unplugging.
Click to expand...
Click to collapse
That message upon boot is normal if your phone has been modified. Mine says it too and my phone is booting up perfectly fine. In fact, it always has said that from the day I first modified it.
Most likely your software is just bricked. First of all, BE HAPPY YOUR PHONE IS JUST SOFT BRICKED! :laugh:
(I recently hard bricked my phone by accidentally flashing a file for a completely different phone... phone was completely dead!)
You need to provide more info for anyone to help you, whether it's me or someone else:
1) What phone are you using? E980, E988, E986, F240, etc etc.
2) Do you have a custom recovery, like CWM or TWRP? (I'm hoping you are because getting software back will be easier).
2.1) Can you boot into this recovery? (hold volume up and power button at the same time. The boot animation will begin and the screen will then shut off again. Once it does, let go of the power button, but keep holding the volume up key. The phone should reboot into recovery. It's tricky to do, and if any other readers notice that I described it wrong, please correct me!)
3) Do you ever see the LG boot animation? (The animated LG logo)
4) Once you see that message upon boot, do you wait for it to pass and hope the phone boots, or do you panic and force the phone off?
5) To get the drivers to install for using LG FlashTool, have you done the following?
- First download and install the drivers from the LG site (I'd link you to it, but I only know the link to the E980 drivers. I don't know what phone you have).
- Once installed, plug your usb cable into your computer, but not the phone.
- Hold the volume up and volume down buttons at the same time while plugging the usb cable into the phone
- Phone should now boot into Download mode and your computer will start installing more drivers. Let them install.
- Change the Com port of the phone to Com41 (ask if you don't know how to do this)
- Continue using the LG Flash Tool.
I apologize if any of this sounds like I'm insulting your Android phone intelligence. I don't know how much of this stuff you know.
spexwood said:
That message upon boot is normal if your phone has been modified. Mine says it too and my phone is booting up perfectly fine. In fact, it always has said that from the day I first modified it.
Most likely your software is just bricked. First of all, BE HAPPY YOUR PHONE IS JUST SOFT BRICKED! :laugh:
(I recently hard bricked my phone by accidentally flashing a file for a completely different phone... phone was completely dead!)
You need to provide more info for anyone to help you, whether it's me or someone else:
1) What phone are you using? E980, E988, E986, F240, etc etc.
2) Do you have a custom recovery, like CWM or TWRP? (I'm hoping you are because getting software back will be easier).
2.1) Can you boot into this recovery? (hold volume up and power button at the same time. The boot animation will begin and the screen will then shut off again. Once it does, let go of the power button, but keep holding the volume up key. The phone should reboot into recovery. It's tricky to do, and if any other readers notice that I described it wrong, please correct me!)
3) Do you ever see the LG boot animation? (The animated LG logo)
4) Once you see that message upon boot, do you wait for it to pass and hope the phone boots, or do you panic and force the phone off?
5) To get the drivers to install for using LG FlashTool, have you done the following?
- First download and install the drivers from the LG site (I'd link you to it, but I only know the link to the E980 drivers. I don't know what phone you have).
- Once installed, plug your usb cable into your computer, but not the phone.
- Hold the volume up and volume down buttons at the same time while plugging the usb cable into the phone
- Phone should now boot into Download mode and your computer will start installing more drivers. Let them install.
- Change the Com port of the phone to Com41 (ask if you don't know how to do this)
- Continue using the LG Flash Tool.
I apologize if any of this sounds like I'm insulting your Android phone intelligence. I don't know how much of this stuff you know.
Click to expand...
Click to collapse
No, no I understand!
1)E980
2)I have TWRP.
3)I only see the LG Logo, the error message and that's it, it goes right to TWRP after that.
4)I wait for it to pass, and it goes to TWRP.
5)I will try this on a different PC, because when I boot into download mode and plug in the phone, the drivers attempt to install but fail. I have attempted to re-install them multiple times, but I'll give it a shot on my laptop tonight, and let you know if that works.
Thanks for the help, and I may PM you later!
AustinBobDox said:
No, no I understand!
1)E980
2)I have TWRP.
3)I only see the LG Logo, the error message and that's it, it goes right to TWRP after that.
4)I wait for it to pass, and it goes to TWRP.
5)I will try this on a different PC, because when I boot into download mode and plug in the phone, the drivers attempt to install but fail. I have attempted to re-install them multiple times, but I'll give it a shot on my laptop tonight, and let you know if that works.
Thanks for the help, and I may PM you later!
Click to expand...
Click to collapse
Have to tried install cwm through twrp then wiping clean and installing a ROM ...
2SHAYNEZ
Me thinks his botloop is due to a bad rom flash, flash a rom(EZ kat is a good choice if you want the AT&T stock experience). follow shayne's instructions.
@AustinBobDox:
I know EXACTLY what the problem is. You ran into the notorious recovery bootloop, which seems to be happening to many Kitkat users running recoveries incompatible with KK.
I had it a few times myself while using CWM, PhilZ Touch, and TWRP (Yeah, I got them on all 3!)
Unfortunately, the TWRP and CWM recoveries posted in this forum cause this bootloop randomly if you have the stock Kitkat rom installed (whether rooted or not). Personally, I have not been able to get out of it. I ended up flashing a "fix" that was supposed to get me out of it, but... it was for a completely different phone (an HTC) and it hard bricked my phone.
SO DON'T FLASH ANY "FIXES"!!!!!!!!!
Technically, the ROM is perfectly fine. I read that this bootloop is caused by the phone setting a flag that tells it to boot straight into recovery. Basically, when you initiate the recovery boot, it sets this flag, and when you reboot the phone, it's supposed to clear the flag. In the case of this bootloop, it doesn't get cleared for some reason.
Luckily, since you are on TWRP, you can try this:
Open the TWRP command console thing (I think it's under Advanced or something).
Type this command EXACTLY:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
DOUBLE CHECK YOUR SPELLING, SPACES, ETC!!
EDIT: I put a part in bold because it's .1
The decimal could easily have been missed if reading on a smaller screen or something.
Submit the command and try to reboot to system via the TWRP menu.
If this doesn't work, then you have no choice but to use the tot method once you get it working.
EDIT: Oh and before getting the drivers to install by plugging in the phone, install these drivers:
http://www.lg.com/us/support-mobile/lg-E980
(Look under Software Update tab)
Whether the command works or not, once you get the phone up and running again, install this recovery:
http://forum.xda-developers.com/showthread.php?t=2760895
It's the only recovery right now that's definitely working on Kitkat without the bootloop issue. The only downside is that it can't mount the external_SD, so anything you flash must be on the internal storage.
EDIT: Oh and in case you can't tell, don't flash this recovery! You install the APK in Android and then open the app and install recovery from there. You need to root first though.
---------- Post added at 03:48 AM ---------- Previous post was at 03:38 AM ----------
luisoman2000 said:
Me thinks his botloop is due to a bad rom flash, flash a rom(EZ kat is a good choice if you want the AT&T stock experience). follow shayne's instructions.
Click to expand...
Click to collapse
With this recovery bootloop, even if you flash a new rom, the bootloop could remain. I wasn't able to try a whole new flash, but I did try restoring a backup (different things, I know) and I still kept booting into recovery.
Oddly enough, this has happened to me on all cwm versions, flashing the hacked twrp was the only way i could get out of it. I use cwm to flash roms, twrp i only use when in bootloop or to flash mods.
Sent from my LG-E980 using Tapatalk
AustinBobDox said:
I tried but the drivers won't install correctly. They did once, but it just said something along the lines of "Ready", and never did anything even after plugging and unplugging.
Click to expand...
Click to collapse
Did you make sure under, device manager, your port is set to com 41 for your device?