Related
ok here's the story i was flashing a new rom to my evo and after i rebooted it it gave me an icon of a little android man with an arrow coming out of a box and when it went away the phone would not come back on, it still gets power and when connected to a computer it tries to install a "Qualcomm CDMA Technologies MSM" but nothing on the screen of the evo, i can't boot into recovery or anything the screen just stays blank, is it dead or can i fix it somehow?
take the battery out, put it back in, then reboot
*not liable for this advice, but has worked for me.
Tried that no luck tried with just the power cord no luck tried both no cigar it just doesn't do anything
Sent from my SPH-M900 using XDA App
i think there might be possible for you to put your SD card in your computer, copy over the PC136img zip, then reboot into recovery and flash it so you can get back to working.
cabbieBot said:
i think there might be possible for you to put your SD card in your computer, copy over the PC136img zip, then reboot into recovery and flash it so you can get back to working.
Click to expand...
Click to collapse
But he/she said he/she can't reboot into recovery...
marvelouswonder8 said:
ok here's the story i was flashing a new rom to my evo and after i rebooted it it gave me an icon of a little android man with an arrow coming out of a box and when it went away the phone would not come back on, it still gets power and when connected to a computer it tries to install a "Qualcomm CDMA Technologies MSM" but nothing on the screen of the evo, i can't boot into recovery or anything the screen just stays blank, is it dead or can i fix it somehow?
Click to expand...
Click to collapse
What ROM were you flashing? What root method did you use? Are you fully unlocked (+NAND)? These are all questions we need answers to before we can help.
Yes I was fully rooted nand and all, I used the latest clockwork recovery to flash the new cm6 and followed all the install instructions on the forum exactly (wipe data wipe cache flash latest radio etc) after I flashed the rom I hit the reboot to system button and it showed me the box with the android guy coming out of it when that went away I couldn't get the unit to start up at all
Sent from my SPH-M900 using XDA App
Can you connect it to your compter? Will adb recognize the device? If so, it may be possible to issue the 'adb reboot recovery' command and restore your NAND backup. If not, I don't know what you can do.
when i hook it to the computer the only device that it recognizes is the "qualcomm CDMA technologies MSM" which i haven't been able to find a driver for i had the adb driver installed on my computer and it doesn't recognize when plugged in
Ok so I did some digging and found a driver that loaded up no problem for the qualcomm device, it was an adb device and in device manager it said it was running fine but when I went to issue the adb reboot recovery command adb returns that there's no device connected I tried several other drivers as well with the same results best I can figure somehow the only portion of the phone that's receiving power is this one device as my battery was completely dead when we tested it in my friends evo (charging it then transplanting to my evo didn't work either) so it looks to be dead
Sent from my SPH-M900 using XDA App
I had a similar issue when I installed CM6. Hung at the boot screen. I was able to boot into recovery using ADB. I don't think the computer showed that the phone was connected...I don't remember though. Try to run reboot recovery from ADB again. My second install attempt worked perfectly...loving CM6!
Try to instal the original ruu from your computer.
Sent from my PC36100 using Tapatalk
This is an older thread but just happened to me (updated radios) so I googled it. I tried rebooting many times with the volume down but would not go into recovery. Same qualcomm thing while I was reading this thread it magically booted. All I had to do was wait a couple of minutes (no more than 5). I panicked because of the screen but its all good.
Searched all over and google yada yada yada. So i end up opening a thread here.
Hello guys/babes/kids/oldfags/ifags in disguise . I have a galaxy nexus here that will only boot into
-download mode,
- fastboot (not working at all, pc wont detect its fastboot and buttons all dead when in recovey/fastboot)
- safe mode - will boot into safe mode if i did combo buttons when attached to charger/pc
The story :
When i booted it from batt pull via only power button press, it will go into download mode straight and if i power off or factory reset in safe mode, it will reboot back into safe mode.
I cant flash anything since fastboot is broken. Ive tried Odin back to factory image of Galaxy Nexus GSM ICS and Jellybean but the prob isnt solved and fastboot is still broken. Tried repartition and bootloader update in ODIN yet still fail. And after every successful flash of repackaged stock, it will directly boot into safe mode (for both ICS and JB factory image). Why i didnt flash using fastboot? Fastboot is broken that is. Lets continue...
Other hardwares are still fine as in safe boot, ive tested all the buttons, display, calls, speaker etc. This is fastboot relate i believe as no matter what pc ive tried and all types of gnex drivers i tried. It wont even fart when connecting to pc(win7 x86). ADB works fine though when i booted into the safe mode. Im able to do adb stuffs but whenever i query it to reboot to fastboot or recovery, a dead end again. OMAPflash the tuna edition for omap4460? Tried yet still the same.
Additional facts : The phone was not unlocked and tempered by any way before the prob happened but now the bootloader is unlocked after i flashed the repackaged ODIN (chainfire posted it)
So XDA Gnex'ers, LET THE HUNT BEGIN!
Sent from my GT-I9100 using xda premium
Reserved for updates
Have you stumbled across this yet?
http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/
iowabowtech said:
Have you stumbled across this yet?
http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/
Click to expand...
Click to collapse
thats omapflash, to be more precise.
op, try that. also, might want to read something more, efrant has a link on it on one of his threads.
sent from my i9250
bk201doesntexist said:
thats omapflash, to be more precise.
op, try that. also, might want to read something more, efrant has a link on it on one of his threads.
sent from my i9250
Click to expand...
Click to collapse
Yup, tried it but its still the same. Fastboot still dosent work and relashing packaged factory images in odin dosent fix the fastboot
Sent from my GT-I9100 using xda premium
Saw a Jtag service nearby and thinking of sending it in. Its roughly after conversion from RM(Malaysian Ringgit) around USD$90. Possible recovery from the issue?
Sent from my GT-I9100 using xda premium
does it try to create an error log? or are you able to pull bug report?
it boots into download mode and safemode so, there's hope.
override182 said:
Searched all over and google yada yada yada. So i end up opening a thread here.
Hello guys/babes/kids/oldfags/ifags in disguise . I have a galaxy nexus here that will only boot into
-download mode,
- fastboot (not working at all, pc wont detect its fastboot and buttons all dead when in recovey/fastboot)
- safe mode - will boot into safe mode if i did combo buttons when attached to charger/pc
The story :
When i booted it from batt pull via only power button press, it will go into download mode straight and if i power off or factory reset in safe mode, it will reboot back into safe mode.
I cant flash anything since fastboot is broken. Ive tried Odin back to factory image of Galaxy Nexus GSM ICS and Jellybean but the prob isnt solved and fastboot is still broken. Tried repartition and bootloader update in ODIN yet still fail. And after every successful flash of repackaged stock, it will directly boot into safe mode (for both ICS and JB factory image). Why i didnt flash using fastboot? Fastboot is broken that is. Lets continue...
Other hardwares are still fine as in safe boot, ive tested all the buttons, display, calls, speaker etc. This is fastboot relate i believe as no matter what pc ive tried and all types of gnex drivers i tried. It wont even fart when connecting to pc(win7 x86). ADB works fine though when i booted into the safe mode. Im able to do adb stuffs but whenever i query it to reboot to fastboot or recovery, a dead end again. OMAPflash the tuna edition for omap4460? Tried yet still the same.
Additional facts : The phone was not unlocked and tempered by any way before the prob happened but now the bootloader is unlocked after i flashed the repackaged ODIN (chainfire posted it)
So XDA Gnex'ers, LET THE HUNT BEGIN!
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
First of all, bricked mean there is nothing beside a black screen. Nowaday device are hard to brick. second, One does not simply flash a gnex with odin. It's simply a big wtf that is shining through my head. 3rd, if fastboot is not working, it's because it need a special driver that i suppose you didnt install. If you can boot your phone in fastboot but can connect to it, it's because you have a broken USB port, which is not the case since you can access adb. 4th, i'm still trying to know how you achieved this. It look to me you were following some instruction and it either ended, tl;dr i will skip a few step, hope it will work which didnt or you missed electricity. Install Kies, get your phone in download and recover your phone from it. Never attempt again to play on custom rom. Man, how can someone derp a galaxy nexus, it is like the easiest device to work with.
chadouming said:
First of all, bricked mean there is nothing beside a black screen. Nowaday device are hard to brick. second, One does not simply flash a gnex with odin. It's simply a big wtf that is shining through my head. 3rd, if fastboot is not working, it's because it need a special driver that i suppose you didnt install. If you can boot your phone in fastboot but can connect to it, it's because you have a broken USB port, which is not the case since you can access adb. 4th, i'm still trying to know how you achieved this. It look to me you were following some instruction and it either ended, tl;dr i will skip a few step, hope it will work which didnt or you missed electricity. Install Kies, get your phone in download and recover your phone from it. Never attempt again to play on custom rom. Man, how can someone derp a galaxy nexus, it is like the easiest device to work with.
Click to expand...
Click to collapse
Thx for the reply.
Some clarification here, im not the owner of this phone. Im using 9100 and im just helping a friend to recovery. Ive tried few pcs and it wont even fart when i plugged in during fastboot or recovery (i read someone that in recovery you can do some commands) but the pc(s) wont even detect a hardware being plugged in.
Plus, in fastboot, i cant press any of the hardware keys. No vol up or vol down and the power button dosent work in recovery. I only got to the 3e stock recovery via 'adb reboot recovery' during in fast mode where it booted into the relaxing chillin android with the triangle + red exclamation mark on its tummy. Pressed all buttons and it went to the 3e recovery.
At the 3e, only power button works. I cant toggle a bit using the vol keys. Note that the vol buttons work to boot the phone into fastboot and download mode and also during safe mode, all the keys works flawlessly.
So, i tried the odin method to recovery this living Gnex but with a faulty heart and kidney but it will still boot to safe mode regardless of ICS or Jellybean.
How did this happen?
I have no idea. The owner of the phone claimed that he has never rooted or tempered it in any way. Plus it was still on ICS when i first got the phone (all data was still intact but it was in safe mode at that time).
Regarding drivers, ive attempted many pcs with almost every drivers available. Shall i list em here:
- KIES
- Naked Nexus drivers
- PDA.net
- the 'official' gnex verizon driver set which is said working on GSM devices etc.
Tried those and adb+download mode works fine. Pcs detect em and tried to install the hardware n search for the drivers but not in fastboot. Its just dead.
killersloth said:
does it try to create an error log? or are you able to pull bug report?
it boots into download mode and safemode so, there's hope.
Click to expand...
Click to collapse
Adb works fine so im able to pull anything when its booted. Im not sure if we can pull anything in download mode. Adb/fastboot didnt work in download mode. Am i correct? Mind to share some light here on this. And in fastboot, none. No vol keys to operate and the 4-5 pc ive tried wont even fart a sound or hint anything saying a hardware connected. Its like its a dead circuit plugged only in fastboot.
This is quite a super rare case here. Most of the dead gnex i found on the next and also in XDA has a working fastboot that only needs drivers to make it working but on this unit, even the vol keys is dead. Awkwarddddd
Sent from my GT-I9100 using xda premium
override182 said:
Thx for the reply.
Some clarification here, im not the owner of this phone. Im using 9100 and im just helping a friend to recovery. Ive tried few pcs and it wont even fart when i plugged in during fastboot or recovery (i read someone that in recovery you can do some commands) but the pc(s) wont even detect a hardware being plugged in.
Plus, in fastboot, i cant press any of the hardware keys. No vol up or vol down and the power button dosent work in recovery. I only got to the 3e stock recovery via 'adb reboot recovery' during in fast mode where it booted into the relaxing chillin android with the triangle + red exclamation mark on its tummy. Pressed all buttons and it went to the 3e recovery.
At the 3e, only power button works. I cant toggle a bit using the vol keys. Note that the vol buttons work to boot the phone into fastboot and download mode and also during safe mode, all the keys works flawlessly.
So, i tried the odin method to recovery this living Gnex but with a faulty heart and kidney but it will still boot to safe mode regardless of ICS or Jellybean.
How did this happen?
I have no idea. The owner of the phone claimed that he has never rooted or tempered it in any way. Plus it was still on ICS when i first got the phone (all data was still intact but it was in safe mode at that time).
Regarding drivers, ive attempted many pcs with almost every drivers available. Shall i list em here:
- KIES
- Naked Nexus drivers
- PDA.net
- the 'official' gnex verizon driver set which is said working on GSM devices etc.
Tried those and adb+download mode works fine. Pcs detect em and tried to install the hardware n search for the drivers but not in fastboot. Its just dead.
Adb works fine so im able to pull anything when its booted. Im not sure if we can pull anything in download mode. Adb/fastboot didnt work in download mode. Am i correct? Mind to share some light here on this. And in fastboot, none. No vol keys to operate and the 4-5 pc ive tried wont even fart a sound or hint anything saying a hardware connected. Its like its a dead circuit plugged only in fastboot.
This is quite a super rare case here. Most of the dead gnex i found on the next and also in XDA has a working fastboot that only needs drivers to make it working but on this unit, even the vol keys is dead. Awkwarddddd
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Great to know you are not the one who did that . So if i understand correctly, you say download mode work ? If yes, flash another stock rom from chainfire using odin. No one wan't to flash with odin, but if fastboot is not working, you shall at least try it. Also, when you are putting the phone in download mode and connecting it to kies, it should detect it has to be restored. i would say the main reason for it to not work is that android debugging is not ticked in developer options. But that would be strange that adb work on safe mode. There is probably a way to that with adb but you will have to google it. Tell your friend to follow instruction next time. And ffs, do not use odin ! (Little idea too, try to get in fastboot not connected on PC and wait a few minutes then see if you can move with the volume button, then try to connect it on pc)
chadouming said:
Great to know you are not the one who did that . So if i understand correctly, you say download mode work ? If yes, flash another stock rom from chainfire using odin. No one wan't to flash with odin, but if fastboot is not working, you shall at least try it.
Click to expand...
Click to collapse
Yes i have already did that few times. Few times of ICS factory image and few with JB. All are repacked version provided by chainfire. Its the full package not the software only with stripped bootloader n recovery. Its still the same
Sent from my GT-I9100 using xda premium
http://forum.xda-developers.com/showthread.php?t=1392310
download and install toolkit from that thread ^^^^^^
uninstall all gnex drivers you installed
reboot pc, open gnex toolkit, with phone unplugged install the drivers
fastboot should work
killersloth said:
http://forum.xda-developers.com/showthread.php?t=1392310
download and install toolkit from that thread ^^^^^^
uninstall all gnex drivers you installed
reboot pc, open gnex toolkit, with phone unplugged install the drivers
fastboot should work
Click to expand...
Click to collapse
Thx, tried it on a few pcs but it still wont work. Even the volkeys in fastboot didnt work :8
Sent from my GT-I9100 using xda premium
override182 said:
Thx, tried it on a few pcs but it still wont work. Even the volkeys in fastboot didnt work :8
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
did you try flashing google's factory image in odin??
my fastboot once was unresponsive, but rebooting into it fixed it
from safemode, if you adb reboot bootloader it is unresponsive?
killersloth said:
did you try flashing google's factory image in odin??
my fastboot once was unresponsive, but rebooting into it fixed it
from safemode, if you adb reboot bootloader it is unresponsive?
Click to expand...
Click to collapse
Yes i had, still boots to safe mode and the fastboot is still dead. Yes ive tried adb reboot bootloader but its dead in fastboot, again.
Sent from my GT-I9100 using xda premium
only suggestion left is to just boot into fastboot, leave it alone for awhile (5-10 mins), then try and plug it in and mess with it.
Try doing the whole driver thing mentioned above but instead of flashing a Google image just do the boot loader portion, what settings are you using to flash in Odin?
Sparx639
killersloth said:
only suggestion left is to just boot into fastboot, leave it alone for awhile (5-10 mins), then try and plug it in and mess with it.
Click to expand...
Click to collapse
Tried yesterday, nothing happened
Sparx639 said:
Try doing the whole driver thing mentioned above but instead of flashing a Google image just do the boot loader portion, what settings are you using to flash in Odin?
Sparx639
Click to expand...
Click to collapse
First tried pda only with auto reboot, no gooding. The i tried with booloader, no good. Then bootloader only, still no good. Then i tested all including pit file, still no good.
Update, sent in for Jtagging few min ago. The phone is not with me now and ill get it back in 3days working or not. I shall report in back after 3 days. Thanks to all by giving suggestion and ideas. See u guys again in 3 days
Sent from my GT-I9100 using xda premium
chadouming said:
Also, when you are putting the phone in download mode and connecting it to kies, it should detect it has to be restored. i would say the main reason for it to not work is that android debugging is not ticked in developer options.
Click to expand...
Click to collapse
adb does not work in download mode/bootloader. adb only works when adbd (adb service) is started, and that happens in android boot process. it means android debug bridge.
sent from my i9250
Sorry for the long delay to anyone waiting for the answer/status.
Jtag cant fix it. Returned the device to a friend. Prolly a mobo replacement is the solution but its damn pricy here in Malaysia. It costs 80% of the price to get a new Gnex.
Hell yeah and thx to everyone supporting this.
Sent from my GT-I9100 using xda premium
I am new at all this stuff but i think I'm starting to somehow get a hang of it. I rooted my phone this week running .587 by downgrading the kernel etc, you know. Today I wanted to try another rom so I followed this guide: http://forum.xda-developers.com/showthread.php?t=1955248 To install Xperia Ultimate HD on my phone with a locked bootloader.
However during step 8 CWM shut down and started to boot. But it doesn't start and I'm unable to get back into CWM My computer won't recognise the phone so I can't flash the kernel or do a complete reset using SUS. What do I do? is it save:able?
Been doing flashtool ftf recoveries whenever this occured. Do not power on arc s with it stuck. let flashtool self boot to flash mode and you will be back in buisness again.
Sent from my GT-P6800 using xda app-developers app
if you could tell me what to do a bit more precise I'd really love you! like a small guide
I assumed you have flashtool since you mention about kernel downgrade. if no get it installed
the step actually same as flashing the kernel with phone power off.
reference link to a online guide
http://www.thespicygadgematics.com/2012/06/how-to-fix-bricked-sony-xperia-android.html
Sent from my GT-P6800 using xda app-developers app
Sparfen said:
if you could tell me what to do a bit more precise I'd really love you! like a small guide
Click to expand...
Click to collapse
1. Flash ready to rood ics 562 with flashtool. Here's a youtube tutorial.
2. Root your phone
3. get cwm and follow these steps to install custom rom with locked bootloader
make sure in cwm before installation
1. Wipe data/factory reset
2. wipe cache partition
3. go to mounts and storage menu and\
4. format /system
5. format/data
6. format cache
7. exit mounts and storage menu
6. go to advance
7. wipe dalvik cache
8. wipe battery stats
9. exit advance
10. install custom rom from sd card without rebooting
works every time for me
TRY THIS!
Sparfen said:
I am new at all this stuff but i think I'm starting to somehow get a hang of it. I rooted my phone this week running .587 by downgrading the kernel etc, you know. Today I wanted to try another rom so I followed this guide: http://forum.xda-developers.com/showthread.php?t=1955248 To install Xperia Ultimate HD on my phone with a locked bootloader.
However during step 8 CWM shut down and started to boot. But it doesn't start and I'm unable to get back into CWM My computer won't recognise the phone so I can't flash the kernel or do a complete reset using SUS. What do I do? is it save:able?
Click to expand...
Click to collapse
ok first since ur stuck flash back to stock using flash tools n then follow the procedure.. i had a similar problem n i fixed it.. it was a very simple prob.. for installing these custom roms u ve to format system/ , so if ur using the cwm app by pvyparts ul loose the cwm after wiping it.. all u ve to do is after flashing the custom rom ul ve to install CWM back (use cwm version 5 available in the thread by pvyparts.. not the latest one..)
here's the thread for CWM
n post back if it works..
Thanks guys, really appreciate it, will try these methods out.
Still won't work
I tried doing all the different things you said but the phone won't boot holding in the back button and inserting the datacable. The light on the side turns green but nothing else happens.
Sparfen said:
I tried doing all the different things you said but the phone won't boot holding in the back button and inserting the datacable. The light on the side turns green but nothing else happens.
Click to expand...
Click to collapse
Mate, press the back button while you connect to PC and flashtool will show "device connected in flashmode" than select a firmware to FLASH and FLASH it. After the process is done disconnect and power it on... =)
jader13254 said:
Mate, press the back button while you connect to PC and flashtool will show "device connected in flashmode" than select a firmware to FLASH and FLASH it. After the process is done disconnect and power it on... =)
Click to expand...
Click to collapse
Yeah, that I know and that's what I'm doing. When I hold down the back key and connect to the pc all that happens is that the green led lights up. Flashtool won't recognise it and it still says that I should hold down the back key and then connect to the PC...
http://forum.xda-developers.com/showthread.php?t=1126358
XperienceD said:
http://forum.xda-developers.com/showthread.php?t=1126358
Click to expand...
Click to collapse
Thanks but flashtool won't recognise it and i have a locked bootloader.
Sparfen said:
I am new at all this stuff but i think I'm starting to somehow get a hang of it. I rooted my phone this week running .587 by downgrading the kernel etc, you know. Today I wanted to try another rom so I followed this guide: http://forum.xda-developers.com/showthread.php?t=1955248 To install Xperia Ultimate HD on my phone with a locked bootloader.
However during step 8 CWM shut down and started to boot. But it doesn't start and I'm unable to get back into CWM My computer won't recognise the phone so I can't flash the kernel or do a complete reset using SUS. What do I do? is it save:able?
Click to expand...
Click to collapse
This happened to me once, if i remember right, i've used the repair phone option in sus ( since my phone cannot be recognized i did the click your phone option) it did not repair my phone since sus said i have the latest version installed BUT then i pulled out my battery, reinsert it; open flashtoool, clicked flashmode and entered it successfully
Sparfen said:
Thanks but flashtool won't recognise it and i have a locked bootloader.
Click to expand...
Click to collapse
Odd, because flashtool skills recognise it. Try pulling out the battery and reinserting it and connecting
Sent from Xperia Arc S
THANK YOU!
jman2131 said:
Odd, because flashtool skills recognise it. Try pulling out the battery and reinserting it and connecting
Sent from Xperia Arc S
Click to expand...
Click to collapse
OMG! I pulled out the battery and left it out for a while and then flashtool noticed it and i was able to flash in a generic rom! Thank you!
Which rom u flashed??
Sparfen said:
OMG! I pulled out the battery and left it out for a while and then flashtool noticed it and i was able to flash in a generic rom! Thank you!
Click to expand...
Click to collapse
I was also stuck at Sony logo and it reboots every time just after sony logo. Then i used flashtool, flashed using "LT15i_4.1.B.0.587_Kernel.ftf".....
Now it boot further, but only to XPERIA logo, and then reboots....but certain times i have seen it getting past the logo, like it shows a display asking for pc companion, even the taskbar too with time and blutooth icon on it....but all of a sudden it reboots. i have tried rebooting more than a 100 times, while taking out battery everytime.
Also, I'm not able to get into recovery mode. I tried this using the combination of power on, and when sony logo appears, pressing and releasing volume down repeatedly. I hope i'm doing right.
So what should I do?? am not able to use this phone for a week...
Please help me out.
Ok got it working. I just unlocked the boot loader from sony bootloader site(sorry couldn't post the link, because of low post count)
So, it booted up but show error as soon as put a sim, that "Unfortunately keypad has stopped working".
I figured out the culprit, it is the build version with i flash it. I reflashed it with LT15i_4.1.B.0.431_kernel.ftf, now it working fine like a charm.
So much relief...!!
Hope this may help someone too...so i shared!!!
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?
i installed cm14.1 today from the cyanogenmod website i had everything running fine until i reboot into recovery. i got a black screen and it didnt bot into recovery at all so i held my power button and volume down and nothing happens. i cant even boot up into fast boot or anything. nothing is turning my phone on. when i connect it to my pc nothing happens. is there anything i can do?
There's a mega unbrick guide for the OnePlus 3, use that then install the correct firmware and install the custom TWRP and re flash the ROM
i tried that method but the device doesnt even show up on my pc
envious86 said:
i tried that method but the device doesnt even show up on my pc
Click to expand...
Click to collapse
Get this sorted yet? You'll need a modified TWRP recovery for the newest CM based builds. I went through the same thing yesterday or the day before. Try holding volume down and power for like 30 seconds until you feel it vibrate that it is rebooting. Then hold volume *UP* while it reboots or if you see the "your device is not safe..." flash screen hurry and press volume down and go into fastboot. From there you can fastboot flash a new recovery.
I had the same problem as well, in device manager go to ports (com & LPT) and it will show up there under qualcum device. Don't forget to go and turn off certificate verification
Thanks guys I'll try this after work. Hopefully it works. If not sure oneplus are hopefully releasing a new phone soon
No it didn't work. I have a feeling I deleted something I shouldn't have because I was clearing out my files before I restarted and that was that.
you gotta use special twrp recovery for cm14.1...
https://www.androidfilehost.com/?fid=385035244224394867
Just use the recovery rahditzz provided you with a link, if your phone is stuck on black screen with white led hold your power button until it turns off, then boot to fastboot and flash the recovery and you will boot...
rahditzz said:
you gotta use special twrp recovery for cm14.1...
https://www.androidfilehost.com/?fid=385035244224394867
Click to expand...
Click to collapse
thanks didnt work. when i fastboot flash recovery and boot again it just goes into a black screen again
Then use unbrick method 2..
rahditzz said:
Then use unbrick method 2..
Click to expand...
Click to collapse
neither method works. all i can do is get into fastboot mode thats it. it wont show up on my pc at all
Method 2 workshop 100%, unless its a hardware fault..
Are you pushing volume up while plugging in cable?
I am. To be honest its very complex too me. I'm new to android and all this is so hard. I follow steps but I'm not 100% sure what I doing. Also my computer isn't great. Do these methods work on vista? Is there a video tutorial or anything? Sorry for annoying you and you don't understand how thankful i am for your help.
I jeep getting the sahara communication failed error
envious86 said:
I am. To be honest its very complex too me. I'm new to android and all this is so hard. I follow steps but I'm not 100% sure what I doing. Also my computer isn't great. Do these methods work on vista? Is there a video tutorial or anything? Sorry for annoying you and you don't understand how thankful i am for your help.
Click to expand...
Click to collapse
Your running vista???? Good god update your OS!!
Maybe your fastboot drivers got updated? There were some reports around this. You could try reinstalling the drivers and following the unbrick guide without an internet connection.
Sent from my ONEPLUS A3003 using Tapatalk
Cool u can boot into Fastboot, what error do you get when you type Fastboot devices? Nothing shows up?