[Q] Phone "stuck" on Motorola Logo - Droid X General

I'm having a problem with my Droid X using the 2.2 Froyo update. My phone was rooted using 2.1 when I updated to 2.2 and I started getting this problem. If my phone turns off then when it tries to turn back on it will get "stuck" at the Motorola logo screen. I say "stuck" because I discovered I can still use my phone, I can unlock it, open things, turn it off, it works except it only shows the boot up screen. I can get around this by leaving my battery out for several minutes, then it will boot up fine. I've already tried several things to fix my phone but nothing has worked. What I've tried so far:
Unrooting my phone
Rerooting my phone
flashing a "stock" 2.2 SBF
reset to factory defaults
I'm out of ideas except for trying to get my phone replaced by Verizon. So my question is what's left for me to try? Otherwise, will I be able to return my phone to verizon despite it being rooted at one point? Thanks in advance if anyone can help me out here.
EDIT: I noticed my phone didn't have this problem if my SD card was removed, so I tried reformatting it but that hasn't solved anything either...

Have you tried the 2.2.1 leak? This gives you a new kernel and bootloader.

Stoogie said:
I'm having a problem with my Droid X using the 2.2 Froyo update. My phone was rooted using 2.1 when I updated to 2.2 and I started getting this problem. If my phone turns off then when it tries to turn back on it will get "stuck" at the Motorola logo screen. I say "stuck" because I discovered I can still use my phone, I can unlock it, open things, turn it off, it works except it only shows the boot up screen. I can get around this by leaving my battery out for several minutes, then it will boot up fine. I've already tried several things to fix my phone but nothing has worked. What I've tried so far:
Unrooting my phone
Rerooting my phone
flashing a "stock" 2.2 SBF
reset to factory defaults
I'm out of ideas except for trying to get my phone replaced by Verizon. So my question is what's left for me to try? Otherwise, will I be able to return my phone to verizon despite it being rooted at one point? Thanks in advance if anyone can help me out here.
EDIT: I noticed my phone didn't have this problem if my SD card was removed, so I tried reformatting it but that hasn't solved anything either...
Click to expand...
Click to collapse
If the phone is not rooted when you take it into the Verizon store then you will be fine. I would ensure that any traces of root have been removed from the SD card (apps that require root, etc). As long as the phone is stock when they see it then it will be fine. I have had to do this several times with roms and root access.

Can't you just SBF it? I'm fairly new to the X but I've had to SBF rescue my D1 and D2 multiple times.
OOOPS didn't read the SBF part...
If it is still hosed after an SBF install I would guess that you have a hardware issue and need to replace the phone.

Stoogie said:
I'm having a problem with my Droid X using the 2.2 Froyo update. My phone was rooted using 2.1 when I updated to 2.2 and I started getting this problem. If my phone turns off then when it tries to turn back on it will get "stuck" at the Motorola logo screen. I say "stuck" because I discovered I can still use my phone, I can unlock it, open things, turn it off, it works except it only shows the boot up screen. I can get around this by leaving my battery out for several minutes, then it will boot up fine. I've already tried several things to fix my phone but nothing has worked. What I've tried so far:
Unrooting my phone
Rerooting my phone
flashing a "stock" 2.2 SBF
reset to factory defaults
I'm out of ideas except for trying to get my phone replaced by Verizon. So my question is what's left for me to try? Otherwise, will I be able to return my phone to verizon despite it being rooted at one point? Thanks in advance if anyone can help me out here.
EDIT: I noticed my phone didn't have this problem if my SD card was removed, so I tried reformatting it but that hasn't solved anything either...
Click to expand...
Click to collapse
It's a known issue with 2.3.15. gmanapps, the guy that created the hdmi app in the market said it was the video driver not loading up in time because of some code changes Motorola made; but supposedly it's fixed in 2.2.1. I suggest you don't upgrade to 2.2.1 until there is a full sbf.
I get stuck on the "M" logo 7 times out of 10 after every reboot; I just hold the power button down until the pop-up window comes up (of course I can't see it) and guess where the shutdown press is on the screen to power off the phone, and then power on again after a minute or two. This trick usually works.
Check it out here:
https://supportforums.motorola.com/message/256095#256095

Related

Need help with refurbished X

Problem: Phone wont turn on, at all. Completely unresponsive
Now for the lengthy story.
My original x had liberty aosp running nicely with an OC set on boot at 1200. A nice clump of pixels died randomly one day, so I called verizon for a replacement. I got my replacment refurbished X in the mail, and sbf'd to froyo, for rooted gingerbread upgrade.
I nandroid backed up my old X. I then installed liberty aosp to my new X, and then immediately restored the nandroid from the old X.
My new phone was running great for about a day, then I went and added some changes from the UOT Kitchen, and installed the app that makes the logcat the boot animation.
Again, the phone worked fine for a day or so, then while I was running google maps, it rebooted randomly.
It went through the boot logo, to recovery, so I just hit reboot. It went all through the boot animation, then back to the boot logo, then back through the boot animation.
I made it back to the home screen, then left it alone. After a while it rebooted again on its own. Sometimes the screen would black out, and be completely unresponsive. I pulled the battery, then put it back in, and it wouldn't turn on.
Sometimes, it would take the battery being out for 5 minutes for the phone to accept it, and turn on.
Now, just repeat the two previous paragraphs a few times, and you will get what happened to me.
After a while, I just restored my old working nandroid from the old X. It too had the same problem. I figured it might be my OC, so I set the settings back to stock. Same thing still..
I was then going to wipe data, and install liberty aosp again. The phone was in the recovery menu, so I went to mount usb storage, plugged it in to the computer, and nothing happened.
So, I unmounted usb storage, and hit reboot. The phone booted to the bootloader menu. I unplugged the computer, then tried to power off the phone, but the power button didn't work. So I pulled the battery......
Now the phone wont turn on at all. The battery was at a 70 percent charge at the final time it worked.
Once, I got the phone to boot to the bootloader menu, but once I got my sbf ready to go, the bootloader menu had frozen. Phone was unresponsive to inserting usb, and the sbf program didn't read my phone as being connected.
Again, im now back to a for real bricked phone, that when I hold the power button, it wont turn on. I did leave the phone plugged in, and later today, im going to try using a friends battery...
My dilemma, is now I can't send the phone back for another replacement, for fear it will work at the shop, and they will see my rootedness, then charge me for a new phone, even though im 99% percent sure nothing I did caused this crap.
Anybody have any ideas?
Sent from my DROID2 using Tapatalk
Sent from my DROID2 using Tapatalk
Refurbs not rootable??
I am having similar problems with a refurb X. I have SBF'd several times. The latest was using the Linux mehtod. Then I do the data and cache wiping and install CM7 Nightly 42 and Gapps.
Most of the time when the screen times out and goes to sleep it doesn't come back. When it does, it is by rebooting itself.
Other times it will just randomly reboot.
A few times I have had to remove the battery.
I am going to try a different ROM today and see if that changes things.
Use the linux too found here, has worked on many bricked phones, will work if you can get phone into bootloader mode for sure
www.droidxforums.com/forum/droid-x-sbf/23638-linux-solution-your-windows-rsd-lite-problems.html
DROID X running liberty GB V.8
STAYFROSTY777 said:
Use the linux too found here, has worked on many bricked phones, will work if you can get phone into bootloader mode for sure
www.droidxforums.com/forum/droid-x-sbf/23638-linux-solution-your-windows-rsd-lite-problems.html
DROID X running liberty GB V.8
Click to expand...
Click to collapse
That is exactly what I used to SBF. It works to SBF but when I load CM7 the device starts the random reboot and freezing stuff.
Does it only reboot with CM or does it do it when you sbf as well? If it does it when after you sbf, that is a legit problem. I would suggest if it does it in sbf, leave it unrooted and return it, they wont be able to tell it was rooted because sbf takes you back to stock froyo.
Sent from my NookColor using XDA Premium App
Mine continued to reboot after I SBF'd back to 2.2.1. I went ahead and did the upgrade that was pushed over the Verizon network and now it doesn't reboot.
Could it be something with the newer released Droid X devices and the kernel used in the OTA upgrade by Verizon?

Droid X Willn't Activate.

So.... I was stuck at the M logo after trying to update to a newer version of MIUI. I successfully SBF'd back to stock froyo and my phone won't activate. When the activation call tells me to press "1", it simply goes silent.
Now I somehow bypassed the activation screen, I don't think that was a good idea because it forced me to connect via wifi. I just said "screw it anyway" and went ahain to reroot. Then I installed CM7 (since I current don't have the MIUI zip I was previously running on my phone). Now I am stuck at the CM7 logo. Not sure if I should SBF again or what I should do. I'm kinda freaked.
Also, I have never had a problem SBFing before. This seems more serious than before.
Update: Wiping data allowed me to boot up in CM7. Still cannot activate my phone. Whenever it prompts me to press "1", all I get is complete silence.
I'm currently at UT Dallas, so I don't think location is a problem is it? Actually it shouldn't be because I bricked my phone here before. Had to reactivate it and it worked great.
Man, this is the first time my phone won't activate.
Yes I know I am posting a lot, but since no one is here to help currently I'm trying things out on my own.
I tried restoring a nandroid I had of CM7 previously. Man I thought this was always a failsafe....
Just thinking of things I did since the last time I activated my phone. I updated something (radio version, I don't really know much about it), it was supposed to make my 3G faster or whatever. But I mean I've SBF'd, factory reset and everything, so that shouldn't be an issue?
Gosh dang, I just want my phone back the way it was 2 hours ago.
One of the reasons nandroid might not be working is that I might have a different version of clockwork on my phone. I remember before having a version where the test was blue, but I forgot the version number. Now the one I get with rom manager is green (like the one I had before I got the blue one).
Man I am sooo confused here. I am completely at a loss. I am out of ideas. I need help.
So I realized I did not have the second init version of clockwork. I just flashed that, and I'm waiting to see if I will get any errors. If I get this to work I am going to flash the version of MIUI I had and try to restore my more recent nandroid (since Ive gotten MIUI).
Yup problem solved. Not sure what was causing the problem, but at least its solved. I'm gonna be extra careful next time I flash something.

Phone bricked after Orange UK Gingerbread OTA update?

Hi,
Ive already looked around the forum but cannot find an answer to my question.
I know my phone is not totally bricked, I understand there are probably ways of plugging it into a PC to force an update but i downloaded the OTA update that popped up on my phone last night. As I understand it is meant to update and keep all of your apps and saved data, which I chose to do instead of wiping anything with a manual update to save all the hassle.
The phone was rooted on froyo 2.2.2 orange uk rom but apart from that there were no other mods to the OS.
The phone came up with the "power off" message and now sticks on the black Motorola screen showing
"Failed to boot 2
starting rsd mode"
I can pull the battery out and the phone turns on for about 20 seconds, and I can use the OS in this time but then the "powering off" message comes back up
and it goes back to the error message on the splash screen.
Is there a way I can stop this OTA update from powering off my phone and getting stuck in this loop or do i have to wipe the phone and flash an sbf file?
Can you point me to the sbf file for the new orange gingerbread rom?
Thanks
ryan
Anyone?
When i turn phone on it works for about 20-30 seconds, before it restarts into the splash screen. It seems as if the phone is running some sort of script to continue with the upgrade but when it reboots it cant continue or something...
The OTA update didnt even start flashing, it just downloaded, then i clicked "install now" and it just rebooted to the error.
If i cant fix it easily, can I use RSDLite and an SBF file to go back to stock? Or can you only do this on an unlocked bootloader?
My bootloader is still stock. The only thing I did when I got the phone was root it so that I could install certain apps.
PLEASE HELP!
Link to Orange UK GB SBF is in Atrix 4G Android Dev forum in the Atrix Firmwares Superthread..page 25ish.
I RSDLited this SBF onto my Atrix (unlocked bootloader running Alien #4) with no problems.
This same route may be your only option...not sure about recovery of your apps etc..I have everything backed up via Blur, Google account and Titanium Pro, so no concern for me there.
FYI, this new rom seems to have little Orange bloat and runs great for me in stock form...just rooted...and battery life is very respectable.

[Q] Boot loop issue - at&t Android 2.3.6

Hi,
I have dropped my phone few weeks back and cracked the screen. Still it was in working condition and every thing seemed working fine. But during the last few weeks my phone has received the OTA updates and now it is on Android 2.3.6. Now my phone is rebooting on it own. If I try to reboot it never reboots. When I try to reboot in 'Android Reboot with No BP' option, it reboots and every thing seems working fine but in few minutes it starts rebooting again on its own. Not sure when I dropped the phone it got some hardware damage or the OTA updates causing this reboot issue.
When I tried to boot up using 'Boot Android (no BP)' option it at least boots up and shows me Motoblur log in screen but again with in few seconds it goes back to boot up mode. Some times it stays for 5 to 10 minutes but never stays there more than 10 minutes and it goes back to boot loop.
I have unlocked my Atrix using Automatic boot loader tool. Did not help. Tried to flash with Motorola .SBF files both 2.3.4 and 2.3.6, no luck either. Did the factory reset, wipe out the cache etc....no luck.
I have even tried to install custom ROM (NottachTrix 4G), that didn't help either.
I am thinking it might have caused by Android 2.3.6 updates. So I want to try to flash it with a custom ROM which is built on 2.3.4 or lower but afraid to do that thinking I might hard brick my phone.
Any help is greatly appreciated.
Thanks,
GPR789GPR
Well, unfortunately with the screen cracked, you can't return to Motorola. I had a goof with my Atrix when I first got it because I accidentally did a SBF flash to the wrong version and it bricked the phone and fried the motherboard and Motorola replaced it because I said the Gingerbread update messed it up. Ha.
Anyways, since returning to Moto is not an option for you, I would just go ahead and try to install a custom ROM, maybe try Neutrino ROM 2.2 or 2.5?
Do you have ROMRacer Recovery or CWM Recovery installed? Will it let you get into it? If so, put a custom ROM on your SD card, do a wipe data and cache and install it.
I'm no expert, but I have noticed no one else replied and just trying to help.
Hope all works out for you!
Boot loop issue - at&t Android 2.3.6
Thanks andreww88 for your reply. I read in one of the forums that once the phone is updated with 2.3.6 don't try to go back to older versions especially lower than 2.3.4. That would make the phone to be hard bricked. That is why I didn't try any other ROM other than NottachTrix 4G because it is built on 2.3.6. I could be wrong. That is why I need some guidance to try any other custom ROM.
i had the same issue. What i did was get the Atrix Fastool and whipe the phone. Then i extracted the sbf for 141 and then flashed 59 60 and 61 smg files from fastboot. After that everything worked properly. To then unlock my bootloader i used the flashing script and i was set. This is recoverable not easy but you can recover.
Thanks Moneyman1978 for your reply. Can you be more detail what you did to resolve this issue. Can you send me the links or point me to Fastool and 141 .SBF file also SMG files. Thanks again.
gpr789gpr said:
Hi,
I have dropped my phone few weeks back and cracked the screen. Still it was in working condition and every thing seemed working fine. But during the last few weeks my phone has received the OTA updates and now it is on Android 2.3.6. Now my phone is rebooting on it own. If I try to reboot it never reboots. When I try to reboot in 'Android Reboot with No BP' option, it reboots and every thing seems working fine but in few minutes it starts rebooting again on its own. Not sure when I dropped the phone it got some hardware damage or the OTA updates causing this reboot issue.
When I tried to boot up using 'Boot Android (no BP)' option it at least boots up and shows me Motoblur log in screen but again with in few seconds it goes back to boot up mode. Some times it stays for 5 to 10 minutes but never stays there more than 10 minutes and it goes back to boot loop.
I have unlocked my Atrix using Automatic boot loader tool. Did not help. Tried to flash with Motorola .SBF files both 2.3.4 and 2.3.6, no luck either. Did the factory reset, wipe out the cache etc....no luck.
I have even tried to install custom ROM (NottachTrix 4G), that didn't help either.
I am thinking it might have caused by Android 2.3.6 updates. So I want to try to flash it with a custom ROM which is built on 2.3.4 or lower but afraid to do that thinking I might hard brick my phone.
Any help is greatly appreciated.
Thanks,
GPR789GPR
Click to expand...
Click to collapse
Well, I had a similar issue. I did the 4.5.141 (OS 2.3.6) OTA update and then it would just bootloop. I'm on stock, rooted, locked BL. I then ran the OTA update again via recovery and that didn't help. I then did a full factory reset, then update via recovery and still didn't fix anything (good thing I had TiBu backup). After calling AT&T they finally admitted that Moto recalled the 4.5.141 build update since there was WIDESPREAD boot-loop issues with many Atrix users. Great.
They're sending me a new phone. Luckily, mine is in good condition.
Any one please have any suggestions for me. Do you think it is a hardware issue or can it be fixed by fixing the software??? Any help is appreciated.
If any of you has any ideas about how to fix this issue I would appreciate if you can share it here.

[q] stuck in bootloop sprint ls980 please help!!!!

OK to start off i am not a noob at this, i have read though the forms and cant seem to find out why my phone will not come out of this bootloop. This started happening 2 days ago when I went to install a new rom on my phone. I powered down my phone, put it in recovery (Twrp), I wiped everything but internal storage. I then processed to flash the new rom. Everything went great. My phone rebooted and worked fine for the first 1 min, when i tried to pull down the notification bar the phone stuck off and went into a bootloop. I then tried to go back to my old rom and had the same problem (notification bar would not pull down). So i went to plan B and used the Back To Stock Form to restore the phone back to stock. The process went smooth as well not a problem at all. When the phone started up it allowed me to set up the voice navigation and name of the phone, as i went to update the prl and profile the phone shut off again, when it turned back on it starts normally and the goes to the lock screen where i am unable to make any iterations with the screen at all besides when it turns the blacklight off, as i try to use the knock on the LED light turns white but the screen will not turn back on (not even with the power button). Then it reboots to the lockscreen again and continues to do it until i manually force it off. I have tried everything from redownloading the firmware files, tried back to stock 3 times, hard factory reset, and reset in recovery mode. My phone is back to stock but i am unable to do anything with it unless i factory reset and go though the set up again, but even then i cant get a connection (even with wifi) without the phone shutting off and rebooting. Everytime the phone reboots the time reads 12:00am and switches to 12:01 really quick. I cant get a connection at ALL (I EVEN TRIED REMOVING THE SIMS AND AND PUT IT BACK IN AFTER BACK TO STOCK PROCESS.)
Im not sure if the application Dr.Web could possibly be making my phone do this. I did have it installed and did not remove before I tried to switch to the new rom. The anti-theft part was active.
SOMEONE PLEASE BE MY HERO AND HELP........I REALLY WOULD HATE TO DEAL WITH LG ON THIS ISSUE IF I CAN FIX IT MYSELF
THANKS TO EVEYONE THAT SUPPORTS AN ANSWER
Sshaffer1992 said:
OK to start off i am not a noob at this, i have read though the forms and cant seem to find out why my phone will not come out of this bootloop. This started happening 2 days ago when I went to install a new rom on my phone. I powered down my phone, put it in recovery (Twrp), I wiped everything but internal storage. I then processed to flash the new rom. Everything went great. My phone rebooted and worked fine for the first 1 min, when i tried to pull down the notification bar the phone stuck off and went into a bootloop. I then tried to go back to my old rom and had the same problem (notification bar would not pull down). So i went to plan B and used the Back To Stock Form to restore the phone back to stock. The process went smooth as well not a problem at all. When the phone started up it allowed me to set up the voice navigation and name of the phone, as i went to update the prl and profile the phone shut off again, when it turned back on it starts normally and the goes to the lock screen where i am unable to make any iterations with the screen at all besides when it turns the blacklight off, as i try to use the knock on the LED light turns white but the screen will not turn back on (not even with the power button). Then it reboots to the lockscreen again and continues to do it until i manually force it off. I have tried everything from redownloading the firmware files, tried back to stock 3 times, hard factory reset, and reset in recovery mode. My phone is back to stock but i am unable to do anything with it unless i factory reset and go though the set up again, but even then i cant get a connection (even with wifi) without the phone shutting off and rebooting. Everytime the phone reboots the time reads 12:00am and switches to 12:01 really quick. I cant get a connection at ALL (I EVEN TRIED REMOVING THE SIMS AND AND PUT IT BACK IN AFTER BACK TO STOCK PROCESS.)
Im not sure if the application Dr.Web could possibly be making my phone do this. I did have it installed and did not remove before I tried to switch to the new rom. The anti-theft part was active.
SOMEONE PLEASE BE MY HERO AND HELP........I REALLY WOULD HATE TO DEAL WITH LG ON THIS ISSUE IF I CAN FIX IT MYSELF
THANKS TO EVEYONE THAT SUPPORTS AN ANSWER
Click to expand...
Click to collapse
god that is really hard to read...did you make a back up before you do installation? if so do a restore, if you dint, download another rom, kernel, put it in your phone, wipe everything except internal storage via TWRP then flash rom then kernel.
G1_enthusiast said:
god that is really hard to read...did you make a back up before you do installation? if so do a restore, if you dint, download another rom, kernel, put it in your phone, wipe everything except internal storage via TWRP then flash rom then kernel.
Click to expand...
Click to collapse
lol sorry i wanted to be as pacific as possible. I did make a backup before flashing the rom. when i tried to go back to it i had the same problem with it rebooting after a few mins. i tried flashing furnace 0.0.8 kernel after installing a fresh rom but same problem. I am back on factory recovery atm is there anyway to flash twrp back to the phone without it being rooted? i tried to get the computer to communicate with the phone when it turns on but it wont seem to connect unless im in download mode or recovery.
Sshaffer1992 said:
lol sorry i wanted to be as pacific as possible. I did make a backup before flashing the rom. when i tried to go back to it i had the same problem with it rebooting after a few mins. i tried flashing furnace 0.0.8 kernel after installing a fresh rom but same problem. I am back on factory recovery atm is there anyway to flash twrp back to the phone without it being rooted? i tried to get the computer to communicate with the phone when it turns on but it wont seem to connect unless im in download mode or recovery.
Click to expand...
Click to collapse
so the phone turn on? try enable debugging in developer option, sometimes that works for me, not sure why.
Solution?
Sshaffer1992 said:
OK to start off i am not a noob at this, i have read though the forms and cant seem to find out why my phone will not come out of this bootloop. This started happening 2 days ago when I went to install a new rom on my phone. I powered down my phone, put it in recovery (Twrp), I wiped everything but internal storage. I then processed to flash the new rom. Everything went great. My phone rebooted and worked fine for the first 1 min, when i tried to pull down the notification bar the phone stuck off and went into a bootloop. I then tried to go back to my old rom and had the same problem (notification bar would not pull down). So i went to plan B and used the Back To Stock Form to restore the phone back to stock. The process went smooth as well not a problem at all. When the phone started up it allowed me to set up the voice navigation and name of the phone, as i went to update the prl and profile the phone shut off again, when it turned back on it starts normally and the goes to the lock screen where i am unable to make any iterations with the screen at all besides when it turns the blacklight off, as i try to use the knock on the LED light turns white but the screen will not turn back on (not even with the power button). Then it reboots to the lockscreen again and continues to do it until i manually force it off. I have tried everything from redownloading the firmware files, tried back to stock 3 times, hard factory reset, and reset in recovery mode. My phone is back to stock but i am unable to do anything with it unless i factory reset and go though the set up again, but even then i cant get a connection (even with wifi) without the phone shutting off and rebooting. Everytime the phone reboots the time reads 12:00am and switches to 12:01 really quick. I cant get a connection at ALL (I EVEN TRIED REMOVING THE SIMS AND AND PUT IT BACK IN AFTER BACK TO STOCK PROCESS.)
Im not sure if the application Dr.Web could possibly be making my phone do this. I did have it installed and did not remove before I tried to switch to the new rom. The anti-theft part was active.
SOMEONE PLEASE BE MY HERO AND HELP........I REALLY WOULD HATE TO DEAL WITH LG ON THIS ISSUE IF I CAN FIX IT MYSELF
THANKS TO EVEYONE THAT SUPPORTS AN ANSWER
Click to expand...
Click to collapse
I had the same problem except with me, i was just trying to change fonts manually. It went into a bootloop and i stressed dover it for hours until finally i found out that you have to use the lg mobile support tool (you can find it in one of these threads on the lg g2) and revert it back to stock. That fixed it perfectly fine. Its a lengthy process but simple. If that doesn't work you have to do what the lg mobile support tool does semi-manually with another program lg flash tool which is longer but just as simple if you follow the directions given in the thread to the letter.
androidfantic32 said:
I had the same problem except with me, i was just trying to change fonts manually. It went into a bootloop and i stressed dover it for hours until finally i found out that you have to use the lg mobile support tool (you can find it in one of these threads on the lg g2) and revert it back to stock. That fixed it perfectly fine. Its a lengthy process but simple. If that doesn't work you have to do what the lg mobile support tool does semi-manually with another program lg flash tool which is longer but just as simple if you follow the directions given in the thread to the letter.
Click to expand...
Click to collapse
I tried the lg flash tool and it put my phone back to stock but still have the same problem. I also tried lg mobile support tool but it will not recongize my phone. I did happen to get into settings and seen that both my imei and baseband are unknown. Could this be causeing the proble m? is there any way to fix it?
G1_enthusiast said:
so the phone turn on? try enable debugging in developer option, sometimes that works for me, not sure why.
Click to expand...
Click to collapse
Yes my phone turns on but doesnt stay on for long it will freeze and reboot i noticed my imei and baseband are unknown. Any idea what can be causeing that to happen? Could it cause the phone to reboot like it is? I am back on stock firmware again,. I did try debugging but still no luck, i was even luck enough to root it again before it rebooted but still didnt help.
Sshaffer1992 said:
Yes my phone turns on but doesnt stay on for long it will freeze and reboot i noticed my imei and baseband are unknown. Any idea what can be causeing that to happen? Could it cause the phone to reboot like it is? I am back on stock firmware again,. I did try debugging but still no luck, i was even luck enough to root it again before it rebooted but still didnt help.
Click to expand...
Click to collapse
**** thats not good at all. This happen when I was using my S3, if IMEI is gone then you could not use the phone at all, theres no way you can get it back unless you made a back up. you have to sent it in man, sorry this is as good as hard brick.
G1_enthusiast said:
**** thats not good at all. This happen when I was using my S3, if IMEI is gone then you could not use the phone at all, theres no way you can get it back unless you made a back up. you have to sent it in man, sorry this is as good as hard brick.
Click to expand...
Click to collapse
My friend also has a lg g2 that i rooted for him would i be able to use a backup from his phone. Also when i turn the phone conpletely off and hold down all 3 bottons it brings me to a hardware key settings it does shows my imei number there. If i sent it into lg would they know the phone was once rooted or does the back to stock method cover it up? Thanks for your help btw
Sshaffer1992 said:
My friend also has a lg g2 that i rooted for him would i be able to use a backup from his phone. Also when i turn the phone conpletely off and hold down all 3 bottons it brings me to a hardware key settings it does shows my imei number there. If i sent it into lg would they know the phone was once rooted or does the back to stock method cover it up? Thanks for your help btw
Click to expand...
Click to collapse
they have coders there, I'm sure if they really want to know they can figure it out. If you send it in to get it fix out of your own pockets (meaning you pay them) then i'm sure they dont care, but if you want a replacement due to warranty then it may be a different story.
Sshaffer1992 said:
Yes my phone turns on but doesnt stay on for long it will freeze and reboot i noticed my imei and baseband are unknown. Any idea what can be causeing that to happen? Could it cause the phone to reboot like it is? I am back on stock firmware again,. I did try debugging but still no luck, i was even luck enough to root it again before it rebooted but still didnt help.
Click to expand...
Click to collapse
That suck bro I'm facing the same issue right now hope you got it repaired if so feel free to share the process lol
Nba2kgod said:
That suck bro I'm facing the same issue right now hope you got it repaired if so feel free to share the process lol
Click to expand...
Click to collapse
I eneded up restoreing my phone back to stock and took it into my local sprint store it cost ne 75 dollars to replace the phone not under warranty (if u have sprint protection its free) i told them i took and ota update and it started rebooting itself. If you do get a replacement make sure u back up your efs files to a safe place on your phone. Theses files can become corrupted by flashing roms and kernals.
Sshaffer1992 said:
I eneded up restoreing my phone back to stock and took it into my local sprint store it cost ne 75 dollars to replace the phone not under warranty (if u have sprint protection its free) i told them i took and ota update and it started rebooting itself. If you do get a replacement make sure u back up your efs files to a safe place on your phone. Theses files can become corrupted by flashing roms and kernals.
Click to expand...
Click to collapse
Not under warranty? Doesn't it have a 1 year manufacturer warranty? The G2 wasn't released on Sprint until November last year so it should have been covered.
Sent from my LG-LS980 using Tapatalk
Yes its still under manufacturer warranty but when i made a repair order with lg it said it would take 2 to 3 weeks to get my phone back and if they found out it was due to being rooted and flashing roms im sure lg would of charged a arm a leg to repair it. With sprint i got a new phone in 2 days or ordering it.

Categories

Resources