Hello, I've been using my old x2 as my PDA/MP3 player. I also have put custom ROM on it because... It's fun!!
What's not fun is my locked up phone, here's what occurred... I tried to sbf my phone and received an error flashing (had all correct Motorola drivers/rsd lite. So as it failed and never even cleared out my phone I decided to use my iso boot disk instead. The disk came up, ran normal, said flashing was complete..... nightmare began....
Now I cannot boot into recovery New/old. I can't boot the phone. I can't do anything. The phone starts, I get the Motorola dual core screen (can't hold volume keys to get to rsd/fastboot/etc. The phone will get to the point of booting but will come up with screen which says...
"Failed to boot number 4"
"Starting rsd....."
Then when I go into try anything rsd (iso disk or rsd lite) the phone will either shut off right away and loop sometimes to same screen. Or it will come back when plugged into pc saying battery (which is fully charged) is to low to flash....
I'm going crazy...
Are there any other restore tactics?
I can't erase battery stats because I have no recovery... I've always followed instructions and flash roms for nearly every manufacturer of phones over the years. I am stumped....
Sent from my Galaxy Nexus using xda premium
Disention said:
Hello, I've been using my old x2 as my PDA/MP3 player. I also have put custom ROM on it because... It's fun!!
What's not fun is my locked up phone, here's what occurred... I tried to sbf my phone and received an error flashing (had all correct Motorola drivers/rsd lite. So as it failed and never even cleared out my phone I decided to use my iso boot disk instead. The disk came up, ran normal, said flashing was complete..... nightmare began....
Now I cannot boot into recovery New/old. I can't boot the phone. I can't do anything. The phone starts, I get the Motorola dual core screen (can't hold volume keys to get to rsd/fastboot/etc. The phone will get to the point of booting but will come up with screen which says...
"Failed to boot number 4"
"Starting rsd....."
Then when I go into try anything rsd (iso disk or rsd lite) the phone will either shut off right away and loop sometimes to same screen. Or it will come back when plugged into pc saying battery (which is fully charged) is to low to flash....
I'm going crazy...
Are there any other restore tactics?
I can't erase battery stats because I have no recovery... I've always followed instructions and flash roms for nearly every manufacturer of phones over the years. I am stumped....
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
First, make sure the battery is charged up. You can't RSD without at least 20% battery. Simply plug it in and let it charge, then try again after about an hour.
Also, make sure you are using the correct SBF file. It could've been a bad download, or worse you flashed one for another phone.
I've had nothing but trouble RSDLite and personally only use sbf_flash. So using the iso boot disk is recommended by me.
Yes, I agree that rsd lite will never again be the way I go. The disk had been much handier. Only problem is that I was out of disks, I was also without my CD in the office. I have done plenty of rsd reboot/reflash. Didn't expect this which is why I then went, got my CD, tried again.
Strange thing is the disk is what brought the issue I have at hand to light. So...
I really appreciate the insight for future occurrence avoidance.
How would you suggest fixing problem at hand?
The battery is full charge... It's that 2.3.5 battery glitch still coming back to light. The battery should be full. Now I end up in that strange loop, I don't even know if my battery is now charging or not...
Ugh... I really wish I could figure out exactly where I went wrong as well.
Thanks again for the response!
Sent from my Galaxy Nexus using xda premium
Disention said:
Yes, I agree that rsd lite will never again be the way I go. The disk had been much handier. Only problem is that I was out of disks, I was also without my CD in the office. I have done plenty of rsd reboot/reflash. Didn't expect this which is why I then went, got my CD, tried again.
Strange thing is the disk is what brought the issue I have at hand to light. So...
I really appreciate the insight for future occurrence avoidance.
How would you suggest fixing problem at hand?
The battery is full charge... It's that 2.3.5 battery glitch still coming back to light. The battery should be full. Now I end up in that strange loop, I don't even know if my battery is now charging or not...
Ugh... I really wish I could figure out exactly where I went wrong as well.
Thanks again for the response!
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
So you still only have access to RSD on the phone? Or did it accept the SBF? I'm thinking that you flashed another phone's sbf file.
Sent from my Nexus 7 using xda app-developers app
Yes, if you could re-read my first post for sake of my key stroke would be great. The phone does not boot I'll try and snap a quick pic with other phone and show what happens. This is only thing which happens in a complete loop... can't get into new or old restore/bootstrap. Can't get it to load any of the basic rsd menu options. If I plug into pc it tells me battery is not charged enough. Or just shuts down with disk or boot CD. It's insane!
It's most definitely the RIGHT folder. All of my phone have their own nearly organized files. None of them flash the same way. Droid X2, HTC EVO 4G, Galaxy Nexus..... Yeah, I know the files ok but good thought!
Sent from my Galaxy Nexus using xda premium
Sent from my Galaxy Nexus using xda premium
Have you tried to turn the phone off, put it directly into RSD mode then run RSD program with the correct SBF file?
That's the problem, I never can "put" it in to rsd mode. I start the phone simply by plugging it in it automatically boot into that loop. Nothing I've found will load such as restore, boot loader, etc.
When it says it's going into rsd, it either turns itself off when in that phase and I start rsd. Or it will give me an error stating battery is not charged enough (it's got a full charge, already tested with multimeter)
Sent from my Galaxy Nexus using xda premium
If you got a spare charger around can jerry rig it. If you know what im talking about. If that don't work with the battery issue then if your under contract I'd go get a replacement. Do it by phone as they will not check your device once you send it back.
I've got plenty of spare charger...
What do you mean "Jerry rig" though?
Sent from my Galaxy Nexus using xda premium
Cut the end off that plugs into your phone, then use the ground and hot wire inside the power cord. Put them on the correct ends of the battery without touching the others, can tape them to it then put the battery back in the phone making sure the wires don't move or touch anything else. Then have the one with wires on your battery plugged into the wall, the usb from your phone to your computer then turn RSD on your phone, then try to SBF it. If you still get that arrow do the other option and call and get a replacement. Ive saved a many of phones doing the jerry rigging of the charge. But if it works and you can SBF then when the steps are complete undo the wires and walla.
I like it!
Let me get some stuff together and put this to the test!
I'll post my results!
Thanks!
Sent from my Galaxy Nexus using xda premium
This is the EXACT thing that happened to me about to weeks ago when trying to SBF back to 2.3.4, a task that I've done many times.
I got the "failed to boot" etc screen that you have. Basically I kept trying to SBF (it still wasn't working) and eventually I got the "battery too low to flash" screen.
Since the battery wasn't actually charging at all because of this weird boot screen, I had to drive down to my local RadioShack where they had some device that would charge ANY battery. It was sweet, AND they let me use it for free at their store. So they popped my X2 battery in and I went to the nearest bookstore to get some work done. Came back two hours later and my battery was charged.
But that's all besides the point. Basically what I did to fix it was I kept trying to SBF and eventually it worked. I downloaded another 2.3.4 sbf file to make sure (even though I've used the same file many times) and I even downloaded a 2.3.5 sbf file and began "alternating" between the three in rsd lite, hoping that one of them would "catch". Eventually I believe my original 2.3.4 file caught and my droid was back to normal.
Sorry for your troubles! This problem sucked and it freaked me out a lot when it happened. But I think you'll be fine. Don't worry too much about it like I did!
Disention said:
Then when I go into try anything rsd (iso disk or rsd lite) the phone will either shut off right away and loop sometimes to same screen. Or it will come back when plugged into pc saying battery (which is fully charged) is to low to flash.
Click to expand...
Click to collapse
I have had problems with my DroidX2 not staying charged while being plugged-in to the a usb port on the computer ... I had to use a usb wall-wart for consistent chargeing.
So, if your battery is haveing trouble staying charged (or not) try connecting it to a usb wall-wart and let it charge for at least a couple (~2) hours.
Also, how old is the battery? (I'm pretty sure this has nothing to do with you issue, but it could affect chargeing and battery-life)
Disention said:
That's the problem, I never can "put" it in to rsd mode. I start the phone simply by plugging it in it automatically boot into that loop. Nothing I've found will load such as restore, boot loader, etc.
When it says it's going into rsd, it either turns itself off when in that phase and I start rsd. Or it will give me an error stating battery is not charged enough (it's got a full charge, already tested with multimeter)
Click to expand...
Click to collapse
The following steps can also be seen here -or- see the original sbf/rsd instructions (note: the sbf files are not available at this time)
key instructions at step #10:
With the X2 in a completely POWERED DOWN state, press and hold the volume up button on the top right hand side of the phone. While still holding the volume up press and hold the power button until the screen turns on. At the top of the screen you should see "Starting RSD protocol support" once this text appears you may release the volume up button.
Click to expand...
Click to collapse
Related
I installed a script onto the atrix rom that I was running and apparently the 2 did not play well together. After I installed the script with script manager and rebooted the phone would not get past the motorola boot screen. I proceeded to download the GB SBF and try to sbf back to original. during the course of this the sbf failed and i had to download a different copy. the phone was still in RSD Lite mode and I didnt know how to get out of it so I figured i'd just remove the battery. I know, not the best thing to do, but I did it.
now the phone will not even turn on when the power button is pushed. I have it plugged to a wall charger right now to see if the battery is dead. but it just sits at the motorola screen so I have to wait to see if the battery will charge and let me get back to rsd lite.
Any Idea what pulling the battery when the screen said RSD Lite caused to go wrong?
My phone did that when the battery completely died. Let it sit for a bit then pull the battery. Plug it into the wall without the battery and see what happens. Hopefully you boot into recovery.
Sent from my DROID X2 using xda premium
booked said:
I installed a script onto the atrix rom that I was running and apparently the 2 did not play well together. After I installed the script with script manager and rebooted the phone would not get past the motorola boot screen. I proceeded to download the GB SBF and try to sbf back to original. during the course of this the sbf failed and i had to download a different copy. the phone was still in RSD Lite mode and I didnt know how to get out of it so I figured i'd just remove the battery. I know, not the best thing to do, but I did it.
now the phone will not even turn on when the power button is pushed. I have it plugged to a wall charger right now to see if the battery is dead. but it just sits at the motorola screen so I have to wait to see if the battery will charge and let me get back to rsd lite.
Any Idea what pulling the battery when the screen said RSD Lite caused to go wrong?
Click to expand...
Click to collapse
i did the same thing. i am downloading sbf ginger bread now. if you pull the battery and plug into ac charger it should bring back rsd mode. per mistawolfes instructions. it did for me.
booked said:
I installed a script onto the atrix rom that I was running and apparently the 2 did not play well together. After I installed the script with script manager and rebooted the phone would not get past the motorola boot screen. I proceeded to download the GB SBF and try to sbf back to original. during the course of this the sbf failed and i had to download a different copy. the phone was still in RSD Lite mode and I didnt know how to get out of it so I figured i'd just remove the battery. I know, not the best thing to do, but I did it.
now the phone will not even turn on when the power button is pushed. I have it plugged to a wall charger right now to see if the battery is dead. but it just sits at the motorola screen so I have to wait to see if the battery will charge and let me get back to rsd lite.
Any Idea what pulling the battery when the screen said RSD Lite caused to go wrong?
Click to expand...
Click to collapse
i've done that with droid x before and got code corrupt in the bootloader..
can't sbf no more.. i had to use the assurion inssurance and got a new phone..
might be differ for the x2..
Removed the battery, plugged it into the ac charger and it still bootloops. Any other ideas? I may have to just call Asurion in the morning and get another one on the way.
booked said:
Removed the battery, plugged it into the ac charger and it still bootloops. Any other ideas? I may have to just call Asurion in the morning and get another one on the way.
Click to expand...
Click to collapse
if its bootlooping you should be able to pull batt and get into recovery.
homephysician said:
if its bootlooping you should be able to pull batt and get into recovery.
Click to expand...
Click to collapse
it wont get into recovery. like it said it wouldnt get past the motorola boot screen. I did get into RSD lite mode again. I plugged the phone into the charger with the battery in so it would charge. before the screen automatically comes on i held down the volume key and the power button and it went into fastboot.
it also says that the battery is low, so that may be my whole problem.
booked said:
it wont get into recovery. like it said it wouldnt get past the motorola boot screen. I did get into RSD lite mode again. I plugged the phone into the charger with the battery in so it would charge. before the screen automatically comes on i held down the volume key and the power button and it went into fastboot.
it also says that the battery is low, so that may be my whole problem.
Click to expand...
Click to collapse
I bet that is your problem. Let it sit plugged in for an hour, then try everything again.
Sent from my DROID X2 using xda premium
mistawolfe said:
I bet that is your problem. Let it sit plugged in for an hour, then try everything again.
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
just playing the waiting game right now. i feel lost without my phone.
thanks for the help everyone.
booked said:
just playing the waiting game right now. i feel lost without my phone.
thanks for the help everyone.
Click to expand...
Click to collapse
I had a similar issue and the battery will not charge when in that state. I took a $30 hit and bought a battery at VZW store... Went home, put in new battery, SBF'ed and was good to go.... If my dog hadnt chewed up the box while I wasnt looking, I would have taken the battery back.... But at least now I have a spare battery and anytime I am going to flash or try anything a little squirrelly I just charge one battery all the way, take it out and make sure I have atleast 50% on the one in the phone.... It gives me a kinda warm, fuzzy, sense of security....
They DO sell external battery chargers for this battery type. You can get one of those at walmart or grab a new battery like dag
Sent from my DROID X2 using XDA App
EvilTim said:
They DO sell external battery chargers for this battery type. You can get one of those at walmart or grab a new battery like dag
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
I did actually try a friends generic/fit all external battery charger and it really didnt work to well and thats why I bought the extra battery... Now I am looking at getting a dock that has a external battery charger....
DAG425 said:
I had a similar issue and the battery will not charge when in that state. I took a $30 hit and bought a battery at VZW store... Went home, put in new battery, SBF'ed and was good to go.... If my dog hadnt chewed up the box while I wasnt looking, I would have taken the battery back.... But at least now I have a spare battery and anytime I am going to flash or try anything a little squirrelly I just charge one battery all the way, take it out and make sure I have atleast 50% on the one in the phone.... It gives me a kinda warm, fuzzy, sense of security....
Click to expand...
Click to collapse
SON OF A *****! ur right, it didnt charge the entire night!!! I may have to make a stop at the verizon store and pick up a new battery with some charge.
So after loading the gingerbread sbf it gets to the droid red eye boot screen and just boot loops from there. im coming from a the atrix gb rom so i should be using the GB sbf, right?
error 4 PHONE ONLY BOOTS IN RSD
I was trying to sbf to 2.3.4 and it failed after reboot phone says error 4 and is in rsd mode any ideas how to get phone to boot I have tried sveral times to sbf 2.3.3 and it fails just like 2.3.4 ? Stumped PLEASE HELP
booked said:
So after loading the gingerbread sbf it gets to the droid red eye boot screen and just boot loops from there. im coming from a the atrix gb rom so i should be using the GB sbf, right?
Click to expand...
Click to collapse
When it sits and spins @ the eye, pull the batt.. then hold vol down+pwr to start it back up , let go when ya see fastboot, press vdown till ya see recovery, press both v+v- when ya see the adroid press v+v- again. Do a factory reset. Then reboot youll be fine.
brossma1 said:
I was trying to sbf to 2.3.4 and it failed after reboot phone says error 4 and is in rsd mode any ideas how to get phone to boot I have tried sveral times to sbf 2.3.3 and it fails just like 2.3.4 ? Stumped PLEASE HELP
Click to expand...
Click to collapse
Make sure you have the latest version of RSDLite.
http://forum.xda-developers.com/showthread.php?t=1254879
Thanks I got it and reloaded drivers and it now seems to have worked twice
Sent from my DROID X2 using XDA App
mastafunk said:
When it sits and spins @ the eye, pull the batt.. then hold vol down+pwr to start it back up , let go when ya see fastboot, press vdown till ya see recovery, press both v+v- when ya see the adroid press v+v- again. Do a factory reset. Then reboot youll be fine.
Click to expand...
Click to collapse
When unseen recovery u only need to press volume up to enter.
YES DO THIS IF U MADE IT TO DROID EYE!
No need for crazy stuff if u can factory reset from stock recovery u should be just fine.
I tried to find the answer without posting a new thread. I honestly did. But I'm stuck and it's 6am and I thought I'd ask while I'm still semi-literate.
I soft bricked the **** out of my atrix. I was flashing an sbf to it using rsdlite. All was going smoothly BUT I am a jackass and my phone battery was like... 20% so it died halfway through and now, all I get is:
SVF: 105:1:2
Failed to boot 0x1000
NO OS Detected, Going to RSD mode,
a menu of options,
etc.
Now I made a factory dev cable by connecting the 5v to pin 4. So I can get this far without the stupid battery message. My problem is that I can't do anything else?! While before (when it was working) it came up in RSDlite when it was in RSD, now it doesn't
I reinstalled drivers and RSDlite, rebooted, tried different computers and tried differed USB ports...
I'm not sure what the problem is? I just cant get my computer to see it, even though it turns on and gives me the menu as soon as I plug it in. If I press the up volume key when I plug it in I get
SCF:105:1:2
Failed to boot 0x1000
PwrReason: Factory_Cable
PwrReason: Power_Cut
Starting Fastboot protocol support.
That's all I've got. Please guys, I really need my phone and I need to find a way to get that sbf on there!
Thanks
Edit: Just like to add that I'm running Windows 7, 32 bit with the latest drivers and rsd lite 5.3.1
Is there any chance the second time you are starting RSD you haven't opened the application using administrative privileges?
I'm assuming he knows you can't flash with a certain battery percentage. You've tried charging it and trying again right?
Thanks for the replies guys,
Admin privileges isn't the problem I'm sure of that.
I ran around the last few days trying to find somewhere to charge the battery (motorola phones are pretty much nonexistent in Australia) and try again, I just assumed the factory/dev cable would circumvent that problem. Anyway I had no luck so I bought a standalone charger off ebay which should come on monday.
I'll try when I get the battery charged and post the results in case anyone has a similar problem.
Fingers crossed!
Mine did that too cause I did the same thing and didn't fully charge my battery. Everything worked out when I let it charge for a little while.
Sent from my Atrix
Im curious my ATRIX came with gingerbread 4.5.91 if I messed something up how would I return it to stock what sbf should I use?
Sent from my MB860 using XDA App
How did you let it charge? Just plug it in and leave it at that bootup menu where it tries to go into RSD?
Nas939 said:
How did you let it charge? Just plug it in and leave it at that bootup menu where it tries to go into RSD?
Click to expand...
Click to collapse
you can pull out the battery and plug it into a wall charger, and it should boot into a charging mode.
if that doesn't work, you could also rip apart an old USB cable and connect the positive and negative wires to the positive and negative contacts of the battery while it's plugged into the phone - this will force a current into the battery and charge it up. you can look for a video on youtube that shows you how to do it if you just search 'charge any phone without a charger'
Can't you just do a factory reset?
In any case this should help you without having to flash any sbfs
http://www.technipages.com/2-ways-to-factory-hard-reset-motorola-atrix.html
If not then the sbf should be here:
http://forum.xda-developers.com/showthread.php?t=1125944
If you're on AT&T in the US I think you'd need the first one.
i had flashed CM10 by dragonkiller and all was working fine. i was getting annoyed by minor bugs, so i decided to go to ecplise 2.3 (which was an upgrade from my last rom, eclipse 2.1). ive had it on the phone before and know what im doing.. started by SBFing to 2.3.4, but there was a problem right away. after RSD rebooted my phone i got stuck on the M screen with an error saying "modem failed to power up". since then i have not found a solution and nothing i have tried on my own has fixed the problem. trying to get the stock system recovery to run will display the error "battery is too low to flash" no matter how long i leave the phone charging.. please help! 2 days with no phone already, i cant afford a new one and i rely on this for work!
I've gotten that error message before and gotten out of it fine. First thing you will need to do is charge your battery. Find another Droid X2 or X user and swap batteries, buy an external charger, or take it to the store and *see* if they will charge it for you. After that replace the battery in the phone. With it off, hold volume up and power. When the screen turns on release power and continue holding volume up untill "starting RSD Protocol" appears... plug in and SBF as normal. You could also try the EzSBF but that did not work for me when i got the modem error. RSD should work assuming you have the proper drivers installed.
Likely what happened is your battery died mid flash or you had a bad SBF file and it failed the flash causing the phone to not be able to boot.
Happened to me before. As the software that charges your phone no longer exists, you can't charge the phone to SBF properly. I wound up stripping an old USB cable I had and made a "suicide cord" that I electrical taped to the battery for a few hours. (Red, +; black, -) Worked fine afterwards.
Sent from my MB870 using xda app-developers app
Moral of the story...charge your phone before you SBF.
And post questions in the Q&A thread.
Thread moved to proper section.
jsgraphicart said:
Moral of the story...charge your phone before you SBF.
Click to expand...
Click to collapse
buy a Team BlackHat cable
or
Spare Battery Charger for Motorola Droid X/X2
Yup charge your battery this happened to me as well,even though it was at 50 percent when I tried still wasn't enough to finish.
Sent from my MB870 using xda premium
After trying to sbf with the RSD program back to stock 2.3.4 from the Daytona CM 10 rom the RSD program failed and now i'm stuck at the RSD prompt on my phone. The worst part is I can't try again because my battery is to low and.won't charge in this mode. Is their still hope when I receive my charger?
Greedy Greed said:
After trying to sbf with the RSD program back to stock 2.3.4 from the Daytona CM 10 rom the RSD program failed and now i'm stuck at the RSD prompt on my phone. The worst part is I can't try again because my battery is to low and.won't charge in this mode. Is their still hope when I receive my charger?
Click to expand...
Click to collapse
unfortunately the phone can not charge in the boot loader and it will always default to rsd mode after a bad flash, so no charging. ways around this is to make a factory cable (hard, not recomended), hack together a stripped down charge cable(connects directly to the battery, not hard but not the safest way), find someone with the same phone and use their battery, find an external battery charger, or go to verizon(probably not a good idea)
That's weird, when my phone would not get pass the M Logo and my battery was too low to RSD it would still charge, maybe I got lucky
Lrs121 said:
unfortunately the phone can not charge in the boot loader and it will always default to rsd mode after a bad flash, so no charging. ways around this is to make a factory cable (hard, not recomended), hack together a stripped down charge cable(connects directly to the battery, not hard but not the safest way), find someone with the same phone and use their battery, find an external battery charger, or go to verizon(probably not a good idea)
Click to expand...
Click to collapse
Well I ordered an extended battery before this happened so hopefully it comes charged and I can try again. If not not I will get the external charger hopefully it's not fully soft bricked. I was worried this might happen since this was my first time going back from Jellybean to gingerbread.
TheTechnicalBoss said:
That's weird, when my phone would not get pass the M Logo and my battery was too low to RSD it would still charge, maybe I got lucky
Click to expand...
Click to collapse
Ive never had any luck with that. I guess it was a lucky flash.
Greedy Greed said:
Well I ordered an extended battery before this happened so hopefully it comes charged and I can try again. If not not I will get the external charger hopefully it's not fully soft bricked. I was worried this might happen since this was my first time going back from Jellybean to gingerbread.
Click to expand...
Click to collapse
It is incredibly hard to brick any Motorola phone. And it even harder to not be able to recover from a boot loop or a soft brick as long as you can run sbf flash or rsd lite.
Sent from my MB870 using xda premium
I have no idea what went wrong or where. One day a few apps starting force closing. Then I got weird unlocking problems. Now google play crashed consistently on any search, as well as ****ing settings. I ****ing hate this phone.
-Rooted and unlocked via freegee.
-Installed clockwork over adb(everything was fine at this point)
-Flashed a few different ROMS
-Flashd beanstalk, and then the problems started.
-Can't get ****ing adb to connect no matter what so I can't flash a new recovery
-Considering beating in my phone with a bat.
Anyone have any suggestions for getting recovery working again? Clockworks app doesn't work, similar to what this fellow went through (and apparently solved) http://forum.xda-developers.com/showthread.php?t=2258671&highlight=can+t+boot+recovery
Haven't tried LGNPST because I have no idea what the acronym stands for and no one says what it is.
Refer to tinybin thread in android development
Sent from my Optimus G using Tapatalk 2
drwario said:
Refer to tinybin thread in android development
Sent from my Optimus G using Tapatalk 2
Click to expand...
Click to collapse
I've exhausted everything I could find through the teenybin thread. LGNPST and teenybin gave me back fastboot, but I still have no recovery.
Oh yeah, and a sweet bonus: My phone refuses to go past the boot screen when booting and adb on both my desktops refuses to recognize my device! Anyone want a free phone before I smash it to bits against my face?
Update: For all you poor fools who are following the same path, heres what happened.
Left it plugged in all night and it continued to flash red for a while, and then show a full charge screen, then turn off. Repeated this throughout the whole night.
Come morning I perform a hard battery pull via this thread: http://forum.xda-developers.com/showthread.php?p=45849420#post45849420
I wait a minute with the motherboard connector disengaged. Hold power button for 10 seconds. Plug back in, absolutely no change in my situation. I tried again for about 5 minutes, ditto.
So in conclusion, I broke my phone because I installed a custom rom and LG didn't want me to. I hope whatever team was in charge of developing this phone burns in hell like they so sweetly deserve.
**** you LG. ****. YOU. I want my ****ING money back. You make **** PRODUCTS.
Dude you are aware it's YOUR fault if any thing bad happens when you are playing around with a rooted phone. U installed it and its your own bad....
Sent from my LG-E975 using xda app-developers app
steffenbakke said:
Dude you are aware it's YOUR fault if any thing bad happens when you are playing around with a rooted phone. U installed it and its your own bad....
Sent from my LG-E975 using xda app-developers app
Click to expand...
Click to collapse
Yeah its my fault for installing a custom ROM. You wouldnt be saying this if a desktop or laptop magically stopped working after reinstalling windows or linux. If those were as randomly, stupidly risky, people would be ****ing in arms at microsoft, as they rightfully should be at carriers. Whatever man.
If you can't access recovery or the phone will not boot then adb won't work. You said that you do have the ability to use fastboot though. Have you tried flash twrp from fastboot?
Sent from my LG-E970 using xda app-developers app
Why you install recovery over adb? I mean, when you unlock with freegee it installs the recovery you want (cwm or twrp), so no need for adb.
Have you tried to KDZ a stock rom and do a hard reset?
putsometrebleinit said:
If you can't access recovery or the phone will not boot then adb won't work. You said that you do have the ability to use fastboot though. Have you tried flash twrp from fastboot?
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
I tried LGNPSTING a lot of things and now the battery is ****ed. Hard battery disconnect did nothing. It'll flash its light and maybe show the lg logo when plugged in.. but other than that its frustratingly dead.
Just sell the ****ng phone man...
You got frustrated due to a lack of patience. You can flash recoveries via fastboot. If you actually searched well you would have seen that.
Sent from my Optimus G using XDA Premium 4 mobile app
DeathmonkeyGTX said:
You got frustrated due to a lack of patience. You can flash recoveries via fastboot. If you actually searched well you would have seen that.
Sent from my Optimus G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Doesnt work, and never did. The ****ing phone drivers are so ****ty and proprietary, no computer I used would recognize my phone. I actually managed to flash the stock AT&T rom to my phone through LGNPST, along with a recovery, or so LGNPST said, but of course another problem had to come up. Fantastic ****ing phone here.
swashy said:
Doesnt work, and never did. The ****ing phone drivers are so ****ty and proprietary, no computer I used would recognize my phone. I actually managed to flash the stock AT&T rom to my phone through LGNPST, along with a recovery, or so LGNPST said, but of course another problem had to come up. Fantastic ****ing phone here.
Click to expand...
Click to collapse
Then it sounds likely that you're doing something wrong, have an antivirus conflict, or genuinely do not have access to one well-maintained windows machine.
swashy said:
I tried LGNPSTING a lot of things and now the battery is ****ed. Hard battery disconnect did nothing. It'll flash its light and maybe show the lg logo when plugged in.. but other than that its frustratingly dead.
Click to expand...
Click to collapse
You can melt the software side of these phones so badly and still recover with the Qualcomm tools after the fact, it's not even funny how bad things can go before no return. Flashing a rom didn't do this, period. I want to believe you just suffered from a fluke hardware failure. Even more so it sounds like the USB connector went ape and continued wigging out from there.
The universal drivers also work perfectly. Considering in every way this is the nexus 4 with an SD card slot and a better LTE amplifier, everything you're ranting about is invalid.
The phone is a sanctioned, flash to hell and back model. You need to do some soul searching and find out where YOU went wrong. Or at least get an el cheapo multimeter out and start checking continuity. If it turns out you broke the charging connector or the battery connector off of the board you can STILL be saved. Just put in some effort and try to find the root cause. Screaming and cursing on a random corner of the internet isn't solving your problem
Making up crazed excuses isn't doing any service to you or the other forum users either. Especially the driver ranting. They work flawlessly. Hell even the generic Google provided SDK abd driver works.
If you figure anything out we're here to try and get you back to good.
Sent from my Optimus G using xda app-developers app
-edit- and leave the battery disconnected for awhile. The reason I suggest holding the power button while battery disconnected is in the hope that it will drain any remaining current out of the phone. There's no documentation to say it does or doesn't. So let the thing sit and be absolutely sure it's got a chance to reset. And check the battery voltage to confirm if it's dead or not. Since the contacts will be right there when it's disconnected...
That red light flashing / lg logo when plugged in is exactly where my phone and others was when needing a battery pull. It's fixed every phone I've heard of in that state. Try it again?
The same thing happened to me twice before. Both times I was able to recover my LG you get back into my recovery screen. What works for me is using Lgnpst back to stock jb. Next I flashed both teeny bins. Immediately after flashing the teeny bins, I open my LG up and pulled the battery. I waited about 10 minutes attach the battery back into the LG. Booted to the device and a factory reset my holding the power button in the volume down button. After the the device finished the reset I was good to go and my LG back to normal. This is what works for me give it a try... And good luck.
Sent from my Optimus G using Tapatalk 2
Well, another free day off, guess I'll give it a go again.
The connection of the battery to the mobo is most definitely intact. Pulled the plug to the mobo for ten minutes, plugged back in.
It still just steadily flashes red whenever I charge it. Nothing.
I'll try holding the power button while its disconnected, but I don't have a multimeter to check voltage.
Edit: Something changed. After sitting with the battery disconnected and a rubber band around the power button for 20 minutes, it showed a battery with a charge icon, then nothing. Havent had a screen for awhile. Pressing the power button, nothing. Holding it for awhile gets the full-charge battery, and if I keep holding it, the google symbol, and then nothing. I guess I'll try pulled the battery for 20 minutes again, Maybe it didn't fully discharge?
Edit 2: I've been informed that after a hundred battery pulls, the battery probably has something physically wrong with it. ****ing phenomenal goddamned phone here!! Why do I pay tech companies money for **** again?
swashy said:
Well, another free day off, guess I'll give it a go again.
The connection of the battery to the mobo is most definitely intact. Pulled the plug to the mobo for ten minutes, plugged back in.
It still just steadily flashes red whenever I charge it. Nothing.
I'll try holding the power button while its disconnected, but I don't have a multimeter to check voltage.
Edit: Something changed. After sitting with the battery disconnected and a rubber band around the power button for 20 minutes, it showed a battery with a charge icon, then nothing. Havent had a screen for awhile. Pressing the power button, nothing. Holding it for awhile gets the full-charge battery, and if I keep holding it, the google symbol, and then nothing. I guess I'll try pulled the battery for 20 minutes again, Maybe it didn't fully discharge?
Edit 2: I've been informed that after a hundred battery pulls, the battery probably has something physically wrong with it. ****ing phenomenal goddamned phone here!! Why do I pay tech companies money for **** again?
Click to expand...
Click to collapse
go to a service, ask them if it can be repaired, if they say yes go home and wait for an idea
if they say no dont lose the hope
its a great phone, and as you see you are the only one with this problem
and with that angriness you will do nothing, remember you and only you are the responsable for any damage your phone suffers, not the developer of that rom