Hi guys,
My XT910 ran Cyanogenmod 11, Kitkat Nightly. Tonight an OTA update appeared (something called snapshot or something). Thought it might fix some thing that were not quite right in my version so decided to update. At some point during this process the screen went black then the M logo appeared than the android recovery menu (i can load it). And nothing else. I tried rebooting, wiping cache, reset to factory, nothing works. Copied several ROM on the sd card because i have the option to update from sd. Nada. I gotta tell you i'm on a Mac and i cant change that this week, no Windows till next week. And probably the battery is draining...
What to do?
This is how it goes:
I can not power down the device
It restarts periodically if no action taken
at first the M logo appears
instead of CM logo there is a robot with an exclamation mark inside a red triangle
i can get into recovery menu by pressing the volume keys
i can choose one of the options but nothing else
when applying updates from sd card (stock 4.1.2, nightly rom or snapshot rom) it goes up to "verifying update" then it abandons
Later edit:if i reboot from recovery menu and when it powers off i press pwr and vol- it goes to boot menu. No windows means no adb hence power off from that menu. when i plug in the charger, the M logo appears andstays there. Question: if it does actually charge the battery and i dont fix it before getting a windows, what kind of rom should i flash? Stock?
OK, I tried updating the M10 snapshot today over my current M9 snapshot that I had installed.
As it was updating, the screen went off and then I couldn't get anywhere past the M Logo, pressing the volume keys I'm also able to navigate to recovery etc.. but that's it.
I was not able to boot the phone off and even though the screen was off, I don't believe the phone was off. When I got home, the only thing I knew to do was to flash a stock JB rom using RSD Lite. But when I tried flashing it a few moments ago, it failed - the battery is low apparently. Putting it on charge I can now see a charging logo on the screen that is not centered, but I believe it is charging. Once I've got some juice I will try flashing it again, and then I think it's a whole process of rooting it, installing SafeStrap again, and then starting over with CM11.
I don't know if you can even get RSD Lite for MAC, but it's the only way I know that should work to get the phone back up and running.
Thanks for sharing.
There is no RSD for Mac, nor something similar. But i've managed to set up a virtual xp machine (modern.ie), installed everything, captured the usb port with the phone stating "usb connected". Unfortunately i just couldnt connect the phone to rsd, no matter what i did.
Oh gosh.
I managed to get my phone back by flashing the stock JB rom and then working from there.
Try going to the boot menu thing (hold down all keys) and then navigate to AP fastboot. RSD lite should see the phone in this mode.
But make sure the battery is OK first. I did manage to charge it to 40% and it then flashed after it had some charge. Seemed to flash it a little differently than other times. Also the phone said "Device is LOCKED", but thankfully it all worked out fine. Now I'm on CM11 09/15 Nightly.
Have you installed the Motorola drivers?
Maybe you can't do it through a VM.
Generated on a RAZR Maxx (XT910) using XDA's free mobile app.
d.casper.b said:
Oh gosh.
I managed to get my phone back by flashing the stock JB rom and then working from there.
Try going to the boot menu thing (hold down all keys) and then navigate to AP fastboot. RSD lite should see the phone in this mode.
But make sure the battery is OK first. I did manage to charge it to 40% and it then flashed after it had some charge. Seemed to flash it a little differently than other times. Also the phone said "Device is LOCKED", but thankfully it all worked out fine. Now I'm on CM11 09/15 Nightly.
Have you installed the Motorola drivers?
Maybe you can't do it through a VM.
Generated on a RAZR Maxx (XT910) using XDA's free mobile app.
Click to expand...
Click to collapse
"Device is locked" means that bootloader is locked in our phones,except those few developer edition models.
Sent from my Razr XT910
I'm glad you could do it. Mine seems to charge as well, it's now close to 24h since it bricked and i assume it would just die if it wouldnt charge in that particular state. Fortunately the keys on the Mac keyboard started working again after drinking beer two nights ago so i dont need to trick the virtual machine anymore, but unfortunately i just cannot get the rsd to see the phone on this VM. Probably should try a VM with windows 7 - i guess ill just do that. I have installed the drivers, the VM recognizes the phone (moto spyder adb...) but rsd wont see it, nor the adb driver installer (it needs to identify the device in order to install the proper drivers). I know that rsd is picky when it comes to usb cables, it might just not work with the original cable, but after trying 4 different cables i tend to think this is not the problem
P.S. I'm very upset on Google about killing Motorola and being disrespectful with its own customers (i mean i would have been expecting to be the first to get Android updates, not to wait one year to be able to update from 2.3 and i couldnt imagine they will not roll out RAZR updates after 4.1.2) so my next phone will be a Nokia Lumia. The coolest one, like my StarTac, my V70, my V3, my RAZR...
You maybe successful with a Windows machine
Indeed i was. It was fast and sound, no problems at all flashing stock rom. Though the phone didn't actually charged when plugged in and displaying the M logo. I had to actually sacrifice a usb cable and charge the battery directly.
I have the same problem - I updated to the last snapshot, and did a wipe in safestrap - and got bricked.
Only difference is I can't flash nothing! and in AP Fastboot mode the computer doesn't recognize anything.
Related
Hey folks,
I'm having some issues with my ATT Atrix. The phone keeps rebooting at the "Rethink Possible" screen. I bought this phone off of somebody on CL. I actually had the phone make it past the att screen a couple times. It made it to the setup up Motoblur screen but when I clicked start it just skipped it and takes me to the "Emergency Calls Only" screen. However the phone would just restart eventually at this screen as well. When the screen timed out I could not get the screen to turn back on at this point unless I unplugged the USB cord and plugged it back in. When the phone was on the Emergency Calls screen, my computer did recognize the phone and it did launch the motorola website. While I had the phone at this screen it did say that it had to force close android.process.com. I am coming from a captivate with rooting and flashing roms so I am familiar with Android. I am just trying to figure out where the problem could be with my Atrix. I am hoping somebody can point me in the right direction. Thanks for your time!
Your best bet will be to SBF that back to stock. Have you tried that yet? If not search for RSD Lite and SBF in the forums. There are several links and guides.
Is it unlocked?
I am not sure if it is unlocked as I cannot get past the emergency call screen. However, I will search SBF and research that option of setting it back to stock. I know when I flashed roms on the Captivate I would enter into recovery mode. I see in the Atrix that I would have to use Fastboot? The only reason I am worried about flashing a rom is that the phone reboots on its own so I would not want to hard brick it if it rebooted during a flash.
If it's unlocked you should see the word "unlocked" in the upper left corner of the boot logo screen, unless it was unlocked then flashed back or fruitcake in which case it will not say unlocked.
You should not have issues flashing from recovery if you have enough juice in your battery, which you maybe don't if you have been letting it sit rebooting. The rebooting is more than likely caused by an issue with a kernel, ROM, etc. Think of recovery as being similar to the BIOS on a PC. You enter into BIOS before the OS boots, etc., and this is before all the hardware has initialized and drivers have loaded, so the problem causing the reboots should not exist at that time. I would definitely try flashing a different ROM, and also a stock kernel.
It never said unlocked when I got the phone to turn on. I am having trouble getting the phone to turn on this time. I have downloaded RSD Lite and the 4.5.91 .sbf file to flash. I am just having trouble getting the phone started. Are there any ways to force the phone on. When I press the power button the green LED stays lit but nothing comes on the screen. When I plug into the charger it shows the moto symbol then goes to the Battery charging screen. Im not sure if the battery is correct because it says BHX5 1500mAh on the battery. Thanks for your help guys!
Update: I can get the phone into Fastboot and then Android Recovery Mode when the phone is plugged into the wall charger. However when I connect the phone to the computer via USB it just shows the green led when the phone is powered on. Anyway I can get the phone to boot into Fastboot while connected to the computer via USB?
Bump. Any way to get the phone to turn on when plugged into the computer or anyone know why there would be an issue of the phone turning on when plugged into the wall charger but only showing the green led when plugged into the computer? The battery shows 100% charged. Thanks
Update: I got the phone into RSD mode and flashed the 4.5.91 sbf but the phone only goes to the Emergency Call Screen. Is there anything else that can be done?
nishith611 said:
Update: I got the phone into RSD mode and flashed the 4.5.91 sbf but the phone only goes to the Emergency Call Screen. Is there anything else that can be done?
Click to expand...
Click to collapse
Did you fastboot -w before flashing the sbf? (Guess you don't really need to when flashing a sbf)
What may also help is flashing the boot.img file from whatever ROM you are using via fastboot.
Don't know if this will help, but it solves an issue when flashing to a different ROM from CM7, so maybe will help for you.
I know this might sound dumb, but do you have a sim card installed? Also, try to boot into recovery and just do a factory reset. @CaelanT already pointed out that this should be unnecessary since you flashed an sbf but it wouldn't hurt to try.
nishith611 said:
Update: I got the phone into RSD mode and flashed the 4.5.91 sbf but the phone only goes to the Emergency Call Screen. Is there anything else that can be done?
Click to expand...
Click to collapse
EDIT: I reread the OP and realized he had already tried to bypass the start screen.
That is not the correct battery. That is actually a battery used for the Droid X/X2. It seems they have pulled a switch-a-roo on you. (Probably because the Atrix battery could be used as an "Extended" battery in the DX/DX2) Anyways, it should still work but you can find the correct battery online, it should be a BH6X and should have a capacity of 1880/1930mAH.
nishith611 said:
...Im not sure if the battery is correct because it says BHX5 1500mAh on the battery. Thanks for your help guys!
Click to expand...
Click to collapse
Thanks for the reply. I tried to get the phone into recovery mode. I get to the Exclamation Point screen but it gives me no options for a factory reset. I saw that you have to touch the lower right hand side of the screen, but this doesn't do anything for me.
As far as flashing the boot.img file for the rom that I used. I flashed the stock 4.5.91 motorola rom. How can I find boot.img and would I flash it using RSD?
Also would it help if I flashed a custom rom instead of the stock Motorola 2.3.4 rom?
Could the battery not being the BH6X rom be the issue for it not getting enough power to stay on by itself?
Thanks for the help guys, I really appreciate it!
No, the sim card was not installed during the flash. However, I did install the sim card afterwards but the phone boots up and goes to the big green battery charging screen and does not go any further. However when the sim card is not plugged in I can get the phone to go to the Emergency Call screen.
nishith611 said:
As far as flashing the boot.img file for the rom that I used. I flashed the stock 4.5.91 motorola rom. How can I find boot.img and would I flash it using RSD?
Click to expand...
Click to collapse
The following are the instructions for flashing the boot.img. this was the solution to bootloops when trying to restore to a different ROM after CM7, but as I said previously, you never know if it will help or not:
1.Open up the Zip file of your current Blur ROM (Ninja, CherryBlur, Alien, etc.)
2.extract the boot.img file and copy to the directory where your fastboot is.
3.Pull phone battery & reinsert
4.Power on phone and go straight to Fastboot mode (Power + Vol Down)
5.Type "fastboot flash boot boot.img" (exclude quotation marks)
6.Once flashed, reboot phone using "fastboot reboot"
Sorry, don't know how to extract the boot.img from a sbf. Did a quick search and couldn't find instructions. Not something I have done before. Maybe someone else can help with this. I don't even know if this will work, but anything is worth a shot when you are stuck.
<edit> Which CWM are you using?
You can flash Romracers via fastboot if you are not using it. This may help you get into recovery.
Update: I got the phone to recognize the sim card and make phone calls and get wifi active. But the phone still reboots by itself. I can use all the functions of the phone except it just reboots by itself. I got into the About phone section and it says
Android: 2.3.4
Kernel: [email protected] # 2
I can get into the Android Market as well as everything else. Could this be a hardware issue that causes the phone to reboot by itself within a minute or so?
Edit: I can get the vol up and down buttons to work while the phone is working but the power button is not responsive to let me power the phone off. Could a hardware issue with the power button be causing the constant reboot loop?
Update: I got the phone to function with the OS working just fine (phone calls, texts, emails, etc..) but it keeps restarting on its own. The power button still does not work however, could this be a hardware issue? Thanks
I'm pretty sure i have attempted every solution on here (XDA) and elsewhere to troubleshoot my problem. I am hoping it is obvious, but i've put hours into this and i could really use some help!
My tablet is (or was) a Verizon 4G LTE Galaxy 10.1
I had successfully rooted it when i first got it using Odin...i flashed a ROM...can;t remember which one (obviously a wrong one) and ever since it has been rather temperamental.
Over the course of the past week i have been to APX and back... Heimdall (which i am pretty sure i am not doing correctly) to attempting to flash firmware..stock roms etc...
I don;t know whether it is a driver issue, or if i need a stock rom or to flash firmware....but here is where i am at now.
If i try to power up normally...the Samsung galaxy tab logo bootlader flashes for a sec or two...the screen then either goes black...and repeats a few times...or sometimes it flashes the logo and the backlight stays on until i turn it off.
(Seems to be a fairly common problem)
If i hold the volume up and power together...i can get to the Odin download screen with the flashing droid and the midget droid that appears to be walking away from a trash can.
HOWEVER, when i plug the tab into my laptop (windows 7 x64) (i also have access to a (windows 7 x86) and my girlfriends xp machine. I've tried on all mostly on my x64 machine.
Heres the thing.
When i power down...sometimes just pressing the power button once or twice...sometimes, while off i hold the volume down button for a few sec..and all of a sudden the comp reads the device and i can get open ODIN...get the yellow COM thing...but never seem i always get the same error message...can not open/find com/port...
so i can get into odin on my comp with a black screen on my device...or i can get to download mode on my device and my machine wont recognize it.
I seem to have inherited a little bit of everyones problems on here...
Please tell me that there is hope for my tablet...please help? I'm sure you can imagine my frustration. TY.
joshualectric said:
I'm pretty sure i have attempted every solution on here (XDA) and elsewhere to troubleshoot my problem. I am hoping it is obvious, but i've put hours into this and i could really use some help!
My tablet is (or was) a Verizon 4G LTE Galaxy 10.1
I had successfully rooted it when i first got it using Odin...i flashed a ROM...can;t remember which one (obviously a wrong one) and ever since it has been rather temperamental.
Over the course of the past week i have been to APX and back... Heimdall (which i am pretty sure i am not doing correctly) to attempting to flash firmware..stock roms etc...
I don;t know whether it is a driver issue, or if i need a stock rom or to flash firmware....but here is where i am at now.
If i try to power up normally...the Samsung galaxy tab logo bootlader flashes for a sec or two...the screen then either goes black...and repeats a few times...or sometimes it flashes the logo and the backlight stays on until i turn it off.
(Seems to be a fairly common problem)
If i hold the volume up and power together...i can get to the Odin download screen with the flashing droid and the midget droid that appears to be walking away from a trash can.
HOWEVER, when i plug the tab into my laptop (windows 7 x64) (i also have access to a (windows 7 x86) and my girlfriends xp machine. I've tried on all mostly on my x64 machine.
Heres the thing.
When i power down...sometimes just pressing the power button once or twice...sometimes, while off i hold the volume down button for a few sec..and all of a sudden the comp reads the device and i can get open ODIN...get the yellow COM thing...but never seem i always get the same error message...can not open/find com/port...
so i can get into odin on my comp with a black screen on my device...or i can get to download mode on my device and my machine wont recognize it.
I seem to have inherited a little bit of everyones problems on here...
Please tell me that there is hope for my tablet...please help? I'm sure you can imagine my frustration. TY.
Click to expand...
Click to collapse
Have you tried rhis method
http://rootzwiki.com/topic/7718-romleakodineg01-factory-stock-odin-image-vzw-lte-tab-101/
Sent from my GT-P7510 using Tapatalk
...
Thanks for the quick reply. I think i did try this at one point...the problem still stands...when i am in odin dl mode on my tab...the com tab wont turn yellow and comp wont read my device.
If i do it the other way....with a black screen...it wont be able to communicate or find the port. ...but ill try again right now.
Nope....epic fail. There has to be a solution, right?
As long as you can get into download mode you should be able to fix it. Most likely the issue is not your tab but the drivers on your computer.
I spent the better part of a day frustrated trying to go from the leaked 3.2 to official 3.2 having issues similar to you with Odin. Funny thing is for me the PC somehow ended up not recognizing the tab on the USB port I used to flash on but would on others so I simply swapped Ports and continued. Little did I realize that although things seemed okay that issue was a symptom and Odin was now flashing corrupted info onto the tablet.
A simple reboot of the PC fixed things for me. That you have tried other machines though is worrisome. Still there's a chance it still is a driver issue so I would check drivers on the PC and perhaps install kies if you don't have it to see if the drivers with kies help.
Since you're on the Verizon tab flash back to stock 3.1 and flash stock recovery. Then let all the OTA updates run. After that all you need to do is flash cwm and Pershoots kernel along with superuser to be rooted. There is no better ROM for our Verizon tab than this and all wifi ROMs are incompatible with it.
Still, no luck. When i am in download mode on my tab....my computer doesn't recognize it. When I just power up and and plus it in, the screen goes black but the computer sees the device as well as ODIN. However sometimes it is recognized as APX and sometimes it is recognized as a Samsung android device... usually with one or two driver errors.
So, it seems obvious that it would be a driver issue... i've tries kies, and as many variations of drivers i can find.,.. when in APX mode i try to flash using the nvflash method in cmd or heimdall, otherwise i try ODIN and it seems to be successful until the "setup connection" point.
Is there a way (if it is even something i should do ) to get drivers on my device in its current state?
Im at a loss...i know this thing can be resurrected...everything just seems so backwards. Any thoughts?
I know that this is a very basic question, but do you have USB Debugging enabled?
George
No way to check now, as he says the tablet doesn't boot any more.
It sounds like a driver issue for sure, and to be clear here the ONLY requirement that I know of when flashing with odin on the TABLET end is for it to be in download mode waiting for usb BEFORE being plugged in. So when I say driver issue Im talking about on the PC side here. Have kies installed just to get the drivers, fire up odin and get the tab into download mode while unplugged. Plug it in and watch odin to see if the com port status lights up. If not swap usb port and repeat. Do not use a hub and ypu may want to remove unnecessary usb devices too just to see.
I just recently joined the rooting community a few days ago. I started by rooting my phone with petes rooting tool, and then sbf'd the phone back to android 2.3.4 before installing boot strap recovery on the phone. I was able to successfully flash the cyanogen 10 mod, with many exceptions. The first of these exceptions is that the phones keyboard did not work at all (unable to active phone, unable to do anything really), so I decided to look this up. I tried almost everything except installing a new gapps which I was in the process of doing when I hit a major roadblock. The problem I ran into was that when I re-installed the bootstrap recovery on the cyanogen 10 rom to get to the recovery mode in order to flash the gapps file, the phone became stuck on the M (dual core) boot screen. I was however able to access the boot menu (power+volume down), and tried to sbf the phone back to android 2.3.4 so that it would hopefully fix all of my stupidity. Little did I know that this would just increase my unluckiness with the rooting process, and the phone now will not boot into the boot screen. When I hold down (volume down+power) the phone simply flahes a screen and then will do nothing until I pop the battery out. After that, i tried simply turing the hone on by holding down just the power button, and it boot to a screen which displays "failed to boot 2" and then below that "starting RSD mode". From this screen I have tried to sbf to android 2.3.4, and also to android 2.3.5 multiple times, and every time it pops up with either an error on the computer, or "sec_exception: febe, 4e, 4e" and then an error on the computer. ANY HELP WOULD BE GREATLY APPRECIATED!!!! I AM OUT OF OPTIONS AT THIS POINT, AND AM STARTING TO PANIC! HELP ME!
Failed to boot, sounds like hardware failure
but you can try ezSBF, link in my list, might work.
sd_shadow's [Collection] of Links for Droid X2
Sent from my Clear using xda premium
vernon428 said:
I just recently joined the rooting community a few days ago. I started by rooting my phone with petes rooting tool, and then sbf'd the phone back to android 2.3.4 before installing boot strap recovery on the phone. I was able to successfully flash the cyanogen 10 mod, with many exceptions. The first of these exceptions is that the phones keyboard did not work at all (unable to active phone, unable to do anything really), so I decided to look this up. I tried almost everything except installing a new gapps which I was in the process of doing when I hit a major roadblock. The problem I ran into was that when I re-installed the bootstrap recovery on the cyanogen 10 rom to get to the recovery mode in order to flash the gapps file, the phone became stuck on the M (dual core) boot screen. I was however able to access the boot menu (power+volume down), and tried to sbf the phone back to android 2.3.4 so that it would hopefully fix all of my stupidity. Little did I know that this would just increase my unluckiness with the rooting process, and the phone now will not boot into the boot screen. When I hold down (volume down+power) the phone simply flahes a screen and then will do nothing until I pop the battery out. After that, i tried simply turing the hone on by holding down just the power button, and it boot to a screen which displays "failed to boot 2" and then below that "starting RSD mode". From this screen I have tried to sbf to android 2.3.4, and also to android 2.3.5 multiple times, and every time it pops up with either an error on the computer, or "sec_exception: febe, 4e, 4e" and then an error on the computer. ANY HELP WOULD BE GREATLY APPRECIATED!!!! I AM OUT OF OPTIONS AT THIS POINT, AND AM STARTING TO PANIC! HELP ME!
Click to expand...
Click to collapse
im not completely sure why you sbf'd after rooting the first time? no need for that. i would read up a bit more if you do get it working, watch tomsgt123 's videos on youtube so you know what youre doing. and you used the Gapps for cm10.1 not our version. that is why keyboard didnt work. read read read.
after reading abain, i guess you were on 2.3.5. and thats why you sbf'd. but rooting was not needed before sbf. hope you have better luck next time .
flash will fail if battery is too low, should be a low battery error though, but maybe not every time.
if it is low battery, you will need a charged battery or a tbh programing adapter
link to TBH adapter and dx2 external charger in my list
Sent from my XT862 using xda premium
Lorenzo VonMatterhorn said:
im not completely sure why you sbf'd after rooting the first time? no need for that. i would read up a bit more if you do get it working, watch tomsgt123 's videos on youtube so you know what youre doing. and you used the Gapps for cm10.1 not our version. that is why keyboard didnt work. read read read.
after reading abain, i guess you were on 2.3.5. and thats why you sbf'd. but rooting was not needed before sbf. hope you have better luck next time .
Click to expand...
Click to collapse
Do you have any advice on where I should go from here then? My phone is basically a useless hunk of technology until i can get it to boot back into cyanogen 10, or sbf it back to an android operating system. The RSD mode always fails when I try to normally sfd, but i have not tried EZ sbf yet..... any other suggestions?
vernon428 said:
I just recently joined the rooting community a few days ago. I started by rooting my phone with petes rooting tool, and then sbf'd the phone back to android 2.3.4 before installing boot strap recovery on the phone. I was able to successfully flash the cyanogen 10 mod, with many exceptions. The first of these exceptions is that the phones keyboard did not work at all (unable to active phone, unable to do anything really), so I decided to look this up. I tried almost everything except installing a new gapps which I was in the process of doing when I hit a major roadblock. The problem I ran into was that when I re-installed the bootstrap recovery on the cyanogen 10 rom to get to the recovery mode in order to flash the gapps file, the phone became stuck on the M (dual core) boot screen. I was however able to access the boot menu (power+volume down), and tried to sbf the phone back to android 2.3.4 so that it would hopefully fix all of my stupidity. Little did I know that this would just increase my unluckiness with the rooting process, and the phone now will not boot into the boot screen. When I hold down (volume down+power) the phone simply flahes a screen and then will do nothing until I pop the battery out. After that, i tried simply turing the hone on by holding down just the power button, and it boot to a screen which displays "failed to boot 2" and then below that "starting RSD mode". From this screen I have tried to sbf to android 2.3.4, and also to android 2.3.5 multiple times, and every time it pops up with either an error on the computer, or "sec_exception: febe, 4e, 4e" and then an error on the computer. ANY HELP WOULD BE GREATLY APPRECIATED!!!! I AM OUT OF OPTIONS AT THIS POINT, AND AM STARTING TO PANIC! HELP ME!
Click to expand...
Click to collapse
mine did the fail to boot thing back in september, i have to get a new x2. Try using a different computer, good luck
vernon428 said:
Do you have any advice on where I should go from here then? My phone is basically a useless hunk of technology until i can get it to boot back into cyanogen 10, or sbf it back to an android operating system. The RSD mode always fails when I try to normally sfd, but i have not tried EZ sbf yet..... any other suggestions?
Click to expand...
Click to collapse
With it powered off, hold power and volume up . See if you can get it into rsd mode . If so, sbf from there . Hope it works .
Lorenzo VonMatterhorn said:
With it powered off, hold power and volume up . See if you can get it into rsd mode . If so, sbf from there . Hope it works .
Click to expand...
Click to collapse
I can get into RSD mode, and the phone seems to SBF okay, until the SBF on the computer displays "failed", and the phone displays an error message. I am also using a fully charged battery during the whole process (my friend has the same phone so i swap batteries out with him to charge).
vernon428 said:
I can get into RSD mode, and the phone seems to SBF okay, until the SBF on the computer displays "failed", and the phone displays an error message. I am also using a fully charged battery during the whole process (my friend has the same phone so i swap batteries out with him to charge).
Click to expand...
Click to collapse
and you tried EZsbf?
try ezSBF
if you can't get it to work, you can go back, try using rsd lite, and look for Driver issues
Hello. I'm new to the forum, and the issue that brought me here as had me fulling my hair out of the last three days.
I'll try my best to make this short as possible. I have (obviously) AT&T Lg Optimus G (E970) that was running 4.0.4. i rooted and unlocked it and flashed a cm 10.1 using TWRP. Yesterday tried to flash a zip for a transparent status bar mod. But the flash resulted in CM getting stuck on the splash screen. So i booted in TWRP recovery mode to restore from a recent backup. In the midst of wiping my rom and going to restore, i guess my phone died (which was weird because it had a substantial charge). Then it would no longer power on, and the only was i could get ANY response was by plugging it on the charger. All i get it the red indicator light. my phone will only turn on when plugged into the computer. from there the only two thing i can do is enter download mode and boot. and when i try to boot, i will get the lg logo for a moment and the the screen cuts out and goes back the the flashing red light.
so I trien the LGNPST method.
i downloaded the auto LGNPST and installed just fine. downloaded teenybin and lg stock bin. i've tried to flash both (put phone into download mode, select the dll and select the bin file). what happens is everything starts off fine, then when it gets to 67% the phone reboots, then goes back to the flashing red indicator light, and a message on LGNPST will pop up saying the phone has been disconnected, and to reconnect to continue. so i'll unplug the phone, plug it back in, and put it in download mode, and hit continue. LGNPST will say complete but the phone will still be just sitting in download mode. and if i unplug it, it's goes back to square one (red flashing indicator light)
EDIT: i was flashing the v11c stock bin. i just flashed the v20j bin and now we're boot looping while plugged in (lg logo for about 2 seconds, shut off, repeat) progress???
SO SO SORRY FOR THE LONG READ. Just trying to give as much info as possible hoping it helps.
My question is, is this a hard or a soft brick, and do i have any options left? after researching on here i'm hoping JTAG isn't my only option (I don't have the time or funds to go that route) and i saw someone mention taking it back to at&t, butIi don't think that would help me any since rooting the phone voids the warranty, correct?
I'd be eternally grateful for ANY advice. i'm at my wits end, and i've been google researching this for so long i'm starting not to even comprehend what i'm reading. PLEASE HELP!! And thank you so much in advance.
goplatinum said:
Hello. I'm new to the forum, and the issue that brought me here as had me fulling my hair out of the last three days.
I'll try my best to make this short as possible. I have (obviously) AT&T Lg Optimus G (E970) that was running 4.0.4. i rooted and unlocked it and flashed a cm 10.1 using TWRP. Yesterday tried to flash a zip for a transparent status bar mod. But the flash resulted in CM getting stuck on the splash screen. So i booted in TWRP recovery mode to restore from a recent backup. In the midst of wiping my rom and going to restore, i guess my phone died (which was weird because it had a substantial charge). Then it would no longer power on, and the only was i could get ANY response was by plugging it on the charger. All i get it the red indicator light. my phone will only turn on when plugged into the computer. from there the only two thing i can do is enter download mode and boot. and when i try to boot, i will get the lg logo for a moment and the the screen cuts out and goes back the the flashing red light.
so I trien the LGNPST method.
i downloaded the auto LGNPST and installed just fine. downloaded teenybin and lg stock bin. i've tried to flash both (put phone into download mode, select the dll and select the bin file). what happens is everything starts off fine, then when it gets to 67% the phone reboots, then goes back to the flashing red indicator light, and a message on LGNPST will pop up saying the phone has been disconnected, and to reconnect to continue. so i'll unplug the phone, plug it back in, and put it in download mode, and hit continue. LGNPST will say complete but the phone will still be just sitting in download mode. and if i unplug it, it's goes back to square one (red flashing indicator light)
EDIT: i was flashing the v11c stock bin. i just flashed the v20j bin and now we're boot looping while plugged in (lg logo for about 2 seconds, shut off, repeat) progress???
SO SO SORRY FOR THE LONG READ. Just trying to give as much info as possible hoping it helps.
My question is, is this a hard or a soft brick, and do i have any options left? after researching on here i'm hoping JTAG isn't my only option (I don't have the time or funds to go that route) and i saw someone mention taking it back to at&t, butIi don't think that would help me any since rooting the phone voids the warranty, correct?
I'd be eternally grateful for ANY advice. i'm at my wits end, and i've been google researching this for so long i'm starting not to even comprehend what i'm reading. PLEASE HELP!! And thank you so much in advance.
Click to expand...
Click to collapse
If it is hard bricked when connected to computer it will show up in device manager as QDUSB Device or something similar. You could try to do a factory reset with button combo, be sure phone is powered off then hold power and volume down until menu shows up.
You Can Also Try TeenyBin If Factory Reset Does Not Work
Regards,
acervenky,
XPT
thanks for the reply guys. it looks like my phone is showing up in the device manager under ports as "LGE AndroidNet USB Serial Port (COM3)" is that a good sign? i'm going to try flashing teenybin again.
goplatinum said:
thanks for the reply guys. it looks like my phone is showing up in the device manager under ports as "LGE AndroidNet USB Serial Port (COM3)" is that a good sign? i'm going to try flashing teenybin again.
Click to expand...
Click to collapse
Yes, you are not dead in the water. Proceed, young grasshopper.
Sent from my Optimus G using xda app-developers app
All the custom, unofficial 4.2.2 roms I found on XDA require that you be on the latest LG 4.1.2 OTA.
There are also links to stock rom and kernel so you don't have to mess with LGPT whatever. No need to do OTA etc, if you flash this.
http://forum.xda-developers.com/showthread.php?t=2219953
I also found TWRP to be far easier to install, which is installed by default I think with FreeGee. But you can find thread for the latest TWRP 2.6. TWRP makes flashing and wiping cache/dalvik super easy.
Ok, so i'm starting to think this is a battery issue as opposed to a hardware issue. i could still be wrong. I've flashed the stcok rom after stock rom. When i plug my phone into a computer usb port it LG logo boot loops (and this is the only way i can get to download mode), but when i plug it into the usb wall charger, i just get the red flashing light and no other response. when it's not plugged in i get nothing.It's still showing up as "LGE AndroidNet USB Serial Port" in my device manager and i can still get to dpownload mode just fine, so i know all isn't "according to what i've read and been told". So i'm running out of fixes. I did come accross a thread on here suggesting i unplug the battery and plug it back up. So i'll be getting the tools and praying that works.
I did also come across an interesting thread on another forum. They were saying how id you allowed your battery to drain all the way to true zero (which i think might be possible because my phone died in recovery mode), it wouldn't have enough juice to initiate and monitor the charging process. If this is the case, can the batter be brought back to life? a jump start or something (lol)? or will i have to just replace the battery?
THANK YOU SO MUCH FOR THE HELP SO FAR GUYS.
When you used lgnpst to go to 11c it boot looped because you tried to go backwards from cm. If you did a factory reset afterwards with button combo it should boot. Also can you get into recovery after flashing teenybin to do a reset and flash a ROM?
adfurgerson said:
When you used lgnpst to go to 11c it boot looped because you tried to go backwards from cm. If you did a factory reset afterwards with button combo it should boot. Also can you get into recovery after flashing teenybin to do a reset and flash a ROM?
Click to expand...
Click to collapse
i did a factory reset a few times, but it still never booted. and whenever i LGNPST, when it hits 67% the phone reboots and just starts bootlooping (if i flash a stock rom) if i LGNPST teenybin, at 67% the phone will shut off and the flashing red light will just come up. and after each a message will say phone was unplugged or lost connection. after both instances ill plug it back up and put it in download mode again to finish and it will complete, but the phone will just be sitting there in download mode. and if i reboot.... bootloop city.
i cam across this thread that seems to detail my issue perfectly. so i'm going to attempt a teenybin flash one more time to tryt to get recovery mode (havent been able to get it at all), and if that doesn't work i'm going to do a battery pull..
http://forum.xda-developers.com/showthread.php?t=2261803&highlight=battery
BATTERY UNPLUG WORK LIKE A CHARM. again, i followed the method [r.]GimP laid out here http://forum.xda-developers.com/showthread.php?p=43732147#post43732147
i was nervous because i've never opened my (or any other) phone before.
and thanks to the tot link provided by zymphad above, i'm now running jb 4.1.2
THANK YOU GUYS :highfive:
I found LG's camera lacking, but 4.2 has an update for that, plus the camera mod, much improved I think.
Running RootBox great now with 124mhz idle, GPU downclocked to 200 and CPU undervolted to 85, stable and cool. I don't 3d game on phones.
Glad you fixed it, I just hope someone makes a high capacity internal battery for us since taking it apart isn't that difficult.
Sent from my Optimus G using Tapatalk 4 Beta
Hello there. Since I'm new here I'd like to say hello to everyone
Today I got my RAZR and wanted to play with it. It was already rooted and it had a 4.1.2 android for it, but I didn't liked it at all so I tried to install MIUI. After creating a new partition (1) i had installed miui, but after reboot phone died - Motorola logo appears and it reboots. I looked for some info in the internet and I found about installing new, clean rom via fastboot. I downloaded SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTCEE_HWp2b_Service1FF_fastboot archive and tried to install it with Eternity Project, but after rebooting system does not start and android with red triangle appears.
Right now I am stuck and I don't know what to do. Could you guys tell me what should I do? The phone is RAZR XT910 from European distribution. Also, my Phone is being recognized as Spyder S.
Thank's in advance
Maciek
maciekk600 said:
Hello there. Since I'm new here I'd like to say hello to everyone
Today I got my RAZR and wanted to play with it. It was already rooted and it had a 4.1.2 android for it, but I didn't liked it at all so I tried to install MIUI. After creating a new partition (1) i had installed miui, but after reboot phone died - Motorola logo appears and it reboots. I looked for some info in the internet and I found about installing new, clean rom via fastboot. I downloaded SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTCEE_HWp2b_Service1FF_fastboot archive and tried to install it with Eternity Project, but after rebooting system does not start and android with red triangle appears.
Right now I am stuck and I don't know what to do. Could you guys tell me what should I do? The phone is RAZR XT910 from European distribution. Also, my Phone is being recognized as Spyder S.
Thank's in advance
Maciek
Click to expand...
Click to collapse
When you see android with red triangle just press vol- and vol+ and find the option factory reset.
From your post I see that you flashed ICS Fastboot file,right?
Were you on ICS or JB before brick?
Sent from my Razr XT910
Well, as far as I remember it was JellyBean. I tried to flash it, but it didn't work at all. When I tried to flash the newest available soft for my RAZR it didn't want to flash (it was stopping at 1st step - when using RSD Lite, but when I used EPRJ flashing method, after reboot phone couldn't find any files copied to it's cache or something). Right now my battery is too low and I guess the only option is to make a factory cable, because it won't even charge.
And factory reset doesn't change anything: still the Motorola logo appears and then the phone turns off and sometimes reboots.
Is there any way I could install system via install update from sd card option? Or the only thing I can do is to try to install clean Android via RSD or EPRJ?
maciekk600 said:
Well, as far as I remember it was JellyBean. I tried to flash it, but it didn't work at all. When I tried to flash the newest available soft for my RAZR it didn't want to flash (it was stopping at 1st step - when using RSD Lite, but when I used EPRJ flashing method, after reboot phone couldn't find any files copied to it's cache or something). Right now my battery is too low and I guess the only option is to make a factory cable, because it won't even charge.
And factory reset doesn't change anything: still the Motorola logo appears and then the phone turns off and sometimes reboots.
Is there any way I could install system via install update from sd card option? Or the only thing I can do is to try to install clean Android via RSD or EPRJ?
Click to expand...
Click to collapse
The only way is to flash it with RSD Lite.
Here http://forum.xda-developers.com/showthread.php?t=2231289 are all JB Fastboot files.
Sent from my Razr XT910
Okay. I downloaded the british retail soft, we'll see if it works. But will this soft have Polish language?
And the second thing: is there any way to charge the phone when in my situation? When I plug in the charger, white led only flashes for a while and then the bootloop starts - motorola logo appears and that is all. I have also tried the method with pressing vol + and - for 10 seconds and again, but this didn't work either. The only exit here is to make factory cable, right?
maciekk600 said:
Okay. I downloaded the british retail soft, we'll see if it works. But will this soft have Polish language?
And the second thing: is there any way to charge the phone when in my situation? When I plug in the charger, white led only flashes for a while and then the bootloop starts - motorola logo appears and that is all. I have also tried the method with pressing vol + and - for 10 seconds and again, but this didn't work either. The only exit here is to make factory cable, right?
Click to expand...
Click to collapse
Right,with factory cable you can't charge the phone but you can flash fastboot file,that's what it's for.
Sent from my Razr XT910
It worked, thank God. Thanks for the advice, next time I'll be more careful with my RAZR
Greets!
But another problem suddenly appears - my battery won't charge over 40%. Tried turning it off, but it didn't work.
Edit: I have had 50%, now I have 60. It looks like it's going up and changes after 10%. We'll see if it manage to charge up 100% battery.
Edit2: Okay, it fully charged. Thank's again mate for tips