I was having really bad force close issues and I did a factory reset and it didn't make it better. They were system up and home force closes. They came up constantly so I couldn't even get into settings to turn on debugging mode to do any of the methods to go back to stock. I called and got a replacement but will T-Mobile know my phone was rooted and will they even care.?
Sent from my LG-D801 using Tapatalk
em2drvr03 said:
I was having really bad force close issues and I did a factory reset and it didn't make it better. They were system up and home force closes. They came up constantly so I couldn't even get into settings to turn on debugging mode to do any of the methods to go back to stock. I called and got a replacement but will T-Mobile know my phone was rooted and will they even care.?
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
Rooting does void your warranty and supposedly there is a root detection mechanism that they use that's on the stock ROM. I've only seen it mentioned but I don't know anything about it.
On the other hand people have sent in LG G2's for screen repair that are rooted and they've just received a new phone back. Since your problem is software and not hardware I imagine there could be extra grief in trying to repair a phone that's rooted since they will use different tools. I'd say it would depend on how they repair/replace your phone.
You can remove the ROOTED indication in download mode. See http://forum.xda-developers.com/showthread.php?t=2700992
diamond12 said:
You can remove the ROOTED indication in download mode. See http://forum.xda-developers.com/showthread.php?t=2700992
Click to expand...
Click to collapse
The problem is that bc of the fc's it won't me do anything on the phone. It's completely unresponsive.
Sent from my LG-D801 using Tapatalk
Have you tried a hardware factory reset using the poweron key sequence? (power+vol-, let go when LG logo comes up, press again immediately)
Also, maybe try to reflash 4.2.2 kdz.
Related
When I turn the phone off as soon as it vibrate before turning off it just freeze on the screen with the phone saying shutting down and I have to pull the battery out for it to finish turning off. Anyone know how to fix this or has experience this issue before? Just started happening today.
Are you rooted? What rom if so? What kernel? What recovery? What model phone?
Sent from my Nexus S 4G using XDA App
I'm rooted stock rom stock kernal stock recovery model # is GT-i9020T
It just sounds like something is running and doesn't want yo shut down. Got any less quality apps on it?
I would start uninstalling one at a time and trying to shut it down.
Sent from my Nexus S 4G using XDA App
I don't think is that I did a factory reset and data wipe thinking it would fix the problem but it didn't! Also now when I connect the phone to the computer it won't recognize it all just gives me a code 43 any solution for this? I had it working before so I know the drivers were install correct since I use fastboot and adb.
If that's the case it sounds like it may be a hardware issue. See if you could use your warranty for a replacement.
Sent from my Nexus S 4G using XDA App
I guess it is phone just die can't send to Samsung cause bootloader was unlock and the voids the warranty
Hi, completely lost with what to do so hoping you guys can help me out. I am relatively clueless (but hopefully able to follow direction).
Heres the story:
Bought a Nexus S second hand for Rogers here in Canada. Been working great for 3 months or so.
The phone, to my knowledge, has never been rooted in anyway, hacked, etc.
So I have had Go Launcher and its associated widgets installed for some time. No issues. About a week ago I got an update notification for 2.3.6 (I was previously on 2.3.4, and even though I checked it never did find 2.3.5)
Now I heard about issues with tethering, and since I never had the search pop up issue I kept ignoring this.
Well today, the Go Launcher got 'stuck' while I was switching orientation( horizontal to verticle) and once it got unstuck recevied a ton of force close notices. I decided to power it off. It got stuck in the power off animation. I pulled the battery.
Since then, it gets stuck in the boot animation (rainbow x?). I have pulled battery numerous times, one time it sat in the animation for 20 min or so, only to restart itself and do it again.
I went to fastboot, and rebooting that way does nothing. Also, I can't go to recovery, when I do it restarts, and then the Android pops up, but eventually I get an Exclamation mark and Android and need to pull battery.
I don't think I can hook it up to the pc because I don't think I enabled usb debugging.
What are my options, any help would be greatly appreciated!
You need to flash the clock work recovery to put a new rom, first install the usb drivers for the nexus and the using dos flash the clock work recovery
Sent from my Nexus S using XDA App
Sent from my Nexus S using XDA App
Is that possible even though I'm pretty sure usb debugging is not enabled?
Any idea what caused this?
Surely there is a way to reset?
OK so did the rooting procedure but stopped before actually hitting the rooting stage.
Any ideas what happened?
Could it have been Go Launcher? Or maybe enabling orientation switching caused it to freak out...
Sent from my Nexus S using XDA App
Follow up to step 7 in the nexusshacks how to root guide and goto recovery mode now, select mounts and thrmen mount usb storage and copy a downloaded rom like cyanogen mode and goto install from zip and fromsd sdcard to install and then advance>clear delvik cache and clear cache partition before installing the rom
Sent from my Nexus S using XDA App
brad2332 said:
OK so did the rooting procedure but stopped before actually hitting the rooting stage.
Any ideas what happened?
Could it have been Go Launcher? Or maybe enabling orientation switching caused it to freak out...
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
If you don't tick the prevent force close, a month ago mine were stuck on home screen and keep forceclosing, all i do is just install another launcher press home screen and voila
The android ! Is the recovery. Stock recovery.
You can try a factory reset from in there.
Or do the entire unlock bootloader and root thing. Unlocking will wipe the phone anyways so just try a factory reset from recovery.
At the ! There is a button press that brings you to the options. I can't recall for sure what it is though. I think it is volume up and press power but I am not certain. If you can't figure it out on your own just look it up.
You probably corrupted your sdcard partition while pulling the battery while it was trying to unmount. If that's the case your sdcard is now bad and the only way to fix is to send it in to service.
Sent from my Nexus S 4G using xda premium
So just went ahead and rooted and now running cm7.
Unfortunately lost everything on the phone but had no choice. It was not possible to get into fastboot and use recovery. It hung at the exclamation mark.
Oh well. First time using CM7.... pretty good... mostly just seems to be stock android?
Sent from my Nexus S using XDA App
Again the exclamation mark IS the stock recovery.
phone is on infused v2 and is now just looping after i restarted it, samsung samsung samsung.... how to fix this?
aviationmech406 said:
phone is on infused v2 and is now just looping after i restarted it, samsung samsung samsung.... how to fix this?
Click to expand...
Click to collapse
Have you tried anything to fix this......??
if not just pull batt, hold power and both volume up/down at the same time....when the first samsung logo appears let go of power and continue to hold till you get into recovery. should be like 10 sec maybe 15
wipe data factory reset and you should boot past the loop....if not you most likely have to reflash or use the ultimate unbrick.
mine did this when i deleted the lagfix folder by accident (trying to fee up space) i ended up booting into red recovery and disabling voodo lagfix, rebooted then went back in to recovery and re enabled it.
Im not able to get the recovery to come up, everything is jacked, im trying to track down instructions for that ultimate unbrick..
Ok found this http://forum.xda-developers.com/showthread.php?t=1116251&highlight=unbrick but the part where it says make sure your phone is com## in the odin, mine isnt showing up with that?
aviationmech406 said:
Im not able to get the recovery to come up, everything is jacked, im trying to track down instructions for that ultimate unbrick..
Ok found this http://forum.xda-developers.com/showthread.php?t=1116251&highlight=unbrick but the part where it says make sure your phone is com## in the odin, mine isnt showing up with that?
Click to expand...
Click to collapse
Did you get this working? When I was running Infused I had to repeatedly do battery pulls and the three button meth. to get the recovery. Should seriously try to get recovery to start before doing a back to stock.
As for Odin recognizing the phone, did you make sure you have the kies with the drivers installed, did you try different usb ports and/or computers caus sometimes the drivers act funky. Have seen other people have problems with Odin and the drivers.
Got odin to work and its back to stock, only problem i have now is when the date/time is set to automatic it sends it completely off the grid, i have to manually set it which i dont like to do, any quick fix to this?
I'm having a similar problem. My phone is bootlooping and my pc and odin are recognizing it, however the issue is that the phone only turns on for half a second before shutting back off, not allowing me to do anything with it. Anyone know of a way to fix this?
aviationmech406 said:
Got odin to work and its back to stock, only problem i have now is when the date/time is set to automatic it sends it completely off the grid, i have to manually set it which i dont like to do, any quick fix to this?
Click to expand...
Click to collapse
Even on stock? Ive seen this problem with custom roms like dlevrom 5.0 but not on stock? Cruise over there and see what he did to fix it. I believe there is a program called fastfix to force the locales to show up with North America. Nevertheless, check your locale and text in settings to make sure if the correct locale for your area is shown. If not there is a program in the market to force the correct one. Sorry, dont recall the programs name. Maybe the fastfix or fasterfix.
Sent from my SAMSUNG-SGH-I997 using XDA App
Astirnon said:
I'm having a similar problem. My phone is bootlooping and my pc and odin are recognizing it, however the issue is that the phone only turns on for half a second before shutting back off, not allowing me to do anything with it. Anyone know of a way to fix this?
Click to expand...
Click to collapse
Go to either the thread on the Heimdall one click back to stock or the thread on the Unbrickable mod, read up on your download mode access problem and figure which direction to go. Sounds like a soft brick but anything other than a black screen period is salvagable so your all good.
Sent from my SAMSUNG-SGH-I997 using XDA App
Pull battery plug in USB cable hold volume s power buttons insert battery should put you at download screen to odin to stock.
Sent from my SAMSUNG-SGH-I997 using XDA App
JLR9914 said:
Go to either the thread on the Heimdall one click back to stock or the thread on the Unbrickable mod, read up on your download mode access problem and figure which direction to go. Sounds like a soft brick but anything other than a black screen period is salvagable so your all good.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
Ok I did both, Odin had a different "modem" I guess so my time was off, I tried the heimdall one and it gave me the gingerbread update which is nice but im having a problem I turn on phone after and after the Samsung comes on it does this sketchy screen with a lot of colors then boots into "atts rethink possible" not sure if anyone can help with that.
aviationmech406 said:
Ok I did both, Odin had a different "modem" I guess so my time was off, I tried the heimdall one and it gave me the gingerbread update which is nice but im having a problem I turn on phone after and after the Samsung comes on it does this sketchy screen with a lot of colors then boots into "atts rethink possible" not sure if anyone can help with that.
Click to expand...
Click to collapse
Sounds like the rainbow thing peeps were getting when they used gb leaks with the froyo bootloaders? You are still booting up fine so that is good. Head over to one of the leaks like UCKJ2 or 4 and study first because the gb bootloaders might solve your rainbow but they are to be used with caution, you could brick your phone real quick.
Sent from my SAMSUNG-SGH-I997 using XDA App
While I was flashing a ROM (Synergy1.3), my wife decided to move my phone to another table. When i looked at it a few minutes later,the screen was blank. Now it wont turn on at all. I had used that particular ROM before without any problems. My battery was at 90% when i started to flash. I have a terrible feeling i am bricked. Any ideas?
goralla said:
While I was flashing a ROM (Synergy1.3), my wife decided to move my phone to another table. When i looked at it a few minutes later,the screen was blank. Now it wont turn on at all. I had used that particular ROM before without any problems. My battery was at 90% when i started to flash. I have a terrible feeling i am bricked. Any ideas?
Click to expand...
Click to collapse
You take out the battery..then try it?
Dominazn said:
You take out the battery..then try it?
Click to expand...
Click to collapse
yes,also tried charging it from wall charger ans USB. I get this error when plugging into USB (QHSUSB_DLOAD)
It's hard to brick a phone. Worst case, boot into download mode and Odin up the stock image.
If you can't access Download mode, you've most likely bricked as any research I've done points to it. If you've got insurance you can pay the premium, or send it to one of the JTAG services for repair (such as MobileTechVideos).
Just don't leave or touch the phone next time when you're flashing!
With my case it's hard to hit the buttons for recovery and download. I created across to get to them. Not what you're wanting to here. But here's a tip: if you can get adb to recognize your phone but can't use buttons to get into download mode you can "adb shell" and then "reboot download". That will cause the phone to boot download/Odin mode. Hopefully that will work and you can flash back to stock.
Sent from my SCH-I535 using xda app-developers app
The phone will not power up in any way at all. I am in the 5th stage of the grieving process. Back to my Tbolt and hope Samsung honors the warranty.
goralla said:
The phone will not power up in any way at all. I am in the 5th stage of the grieving process. Back to my Tbolt and hope Samsung honors the warranty.
Click to expand...
Click to collapse
They won't honor it with a rooted phone or flash count pass 0
Sent from my Verizon Samsung Galaxy S3 4G LTE
If you cant get to download mode or get adb to recognize when properly set up you do probably have a brick. What's happening to you with the warning happened to my friend on Sprint while accidentally flashing a ROM for a different phone. What he had to do was send it in to MobileTechVideos and got it repaired for around 60$. Samsung/Verizon wont likely fix them under warranty.
My only question is if you indeed were flashing synergy, how did a system ROM brick a device. o_0 And hell even if it was another phones ROM wouldn't our locked bootloader deny overwriting?
enomele said:
If you cant get to download mode or get adb to recognize when properly set up you do probably have a brick. What's happening to you with the warning happened to my friend on Sprint while accidentally flashing a ROM for a different phone. What he had to do was send it in to MobileTechVideos and got it repaired for around 60$. Samsung/Verizon wont likely fix them under warranty.
My only question is if you indeed were flashing synergy, how did a system ROM brick a device. o_0 And hell even if it was another phones ROM wouldn't our locked bootloader deny overwriting?
Click to expand...
Click to collapse
I also accidentally flashed a rom for a different phone and am considering sending it to MobileTechVideos. Your friend had good success with them fixing his phone?
-Purk
I think this might also work for you, if the battery charging icon comes on while your charging it then this might work. When you have it connected and the charging icon comes on put it in download mode(do not unplug it until your in download mode). Then use odin to flash it back to stock. It happen to me ones and when i did this it work for me, so i don't know if this will work for you. (Sorry for my grammar)
Bought this phone and didn't like it. Felt like my G3 was a better phone, so I went and bought myself the Note 5. Anyways....
I backed up everything from my G4 and did Factory reset. Now when I try to setup the phone, I complete the last step and I'm greeted with the "Unfortunately, LGSetupWizard has stopped" Message and then it returns to the first setup (choose language) screen. Just happens over and over. I just have this phone and don't know what to do. I really don't want to flash the PR stock file to my phone. Does anyone know of a solution or some sort of setup bypass?
Thanks in advance
do a hard reset, turn off the device, then hold volume down and press the power button until the lg logo comes up, release the power button and immediately press it again until you boot into the factory reset. Keep the volume down button pressed continuously until the factory reset screen comes up.
Yea, I tried that a while back but still the same problem...
tyiphius said:
Yea, I tried that a while back but still the same problem...
Click to expand...
Click to collapse
Did you root before? replaced some app to system? I have this problem before cause of deodex home..but still can access it..
If you can reach wifi setting after start screen, try to pull status bar down...then go to setting>home screen>select home..
My advice is you have to reflash stock image but the problem will be MTP mode..
download sg usb mass storage enabler for access storage via pc..
Yes the phone was rooted.
I don't think I debloated by removing system apps. I think my problem might have came from using the debloated tool by gatesjunior. Though nothing of it when I reset the phone. If disabling the apps wasn't the problem then I guess I did go delete system apps.
But if I deleted Setupwizard, I wouldn't have the setup at all correct?
tyiphius said:
Yes the phone was rooted.
I don't think I debloated by removing system apps. I think my problem might have came from using the debloated tool by gatesjunior. Though nothing of it when I reset the phone. If disabling the apps wasn't the problem then I guess I did go delete system apps.
But if I deleted Setupwizard, I wouldn't have the setup at all correct?
Click to expand...
Click to collapse
Its still has setup UI, because before this i've froze those app ..
try go to setting and select home 1st...from my previous comment
faizalotai said:
Its still has setup UI, because before this i've froze those app ..
try go to setting and select home 1st...from my previous comment
Click to expand...
Click to collapse
Still nothing. I brought it to a ATT device support center and they'd replace it but there was non in stock, so ATT will send me one in 4 bussiness days.
The device center will swap out the phone if they can't fix it and once its under its 1yr manufacture warranty. You don't ATT mobile insurance either. I had my Note 4 swapped out by them in store before.
You should just have to reflash the system img and it would work.
Sent from my LG-H810 using XDA Free mobile app
I had this problem too.. Couldn't find an answer short of flashing it to PR... After a loooooong time on the phone with AT&T tech support, finally did an RMA... Send the other one back this morning, I hope it doesn't come back and bite me later bc it was rooted.
I had serious thoughts of flashing an international system image to it so it could brick. But couldn't bring myself to do it...
I would however like to know what I did to get that.. I did just like the OP and did a simple factory reset. I did delete a few things from system manually, but that was mainly att stuff and Google books, magazines etc. I haven't rooted the new one yet bc now I'm skeptical on doing anything with this damn phone.
Sent from my LG-H810 using XDA Free mobile app
It happened because system cannot access lg setup wizard apk, either its been delete or froze.
What do l do when my LG70 is showing unfortunately LGSetupWizard has stopped