I have a Verizon LG G3, updated to lollipop, everything working fine for a day, then re-rooted, still working fine til I noticed xposed wasnt running. When I attempted to uninstall it before reinstalling the trouble began.... the reboot in the uninstall never finished, and still hasnt finished almost a day later. I have already tried every option in the bootloader (safe mode, usb debug, clear cache, factory reset) they all just hang at the LG splash screen forever. Please help! Ive tried everything I can think of, cant reflash via USB, cant factory reset via bootloader or adb.
You have a functioning custom recovery (TWRP, philz, cwm)? Restore the backup you should've made before messing around with things! Or, if you haven't learned that lesson yet, you could re-flash a Rom back onto your phone.
Tyoryn said:
I have a Verizon LG G3, updated to lollipop, everything working fine for a day, then re-rooted, still working fine til I noticed xposed wasnt running. When I attempted to uninstall it before reinstalling the trouble began.... the reboot in the uninstall never finished, and still hasnt finished almost a day later. I have already tried every option in the bootloader (safe mode, usb debug, clear cache, factory reset) they all just hang at the LG splash screen forever. Please help! Ive tried everything I can think of, cant reflash via USB, cant factory reset via bootloader or adb.
Click to expand...
Click to collapse
use the kdz method to restore stock.
you dont use the same method for exposed on kk as lollipop. check the exposed thread for details on that.
Related
I used the 1 click toot method and thought I may return my fascinate. I decided against it and tried to root again with no luck. The root always has a bunch of FC's and eventually gets stuck. The generic ringer also starts with no way to stop it. Only a battery pull will restart the phone afterward. I have also already really installed the Samsung drivers for the phone. Anybody have any thoughts?
Did you go back to stock via odin...if not do so...and push root manually...instead of an app.
I did through Odin. Tried to push root manually last night. The phone froze right after the push and never recovered. Had to battery pull. I had all of the files pushed and got to the chmod and wait stage when it froze.
Hmm, maybe re push to stock in odin...make sure you are doing the correct files...though it sounds like you did...a second time around sometimes seems to hit the spot...droid used to give me the same issues with sbf.
Do a factory data reset after you redo the odin recovery. Make sure you are using the verizon file when pushing each flash and doing it in the proper order. Then manually root, dont use one click or an app.
Also remember to push the files one at a time and let the phone restart between each one booting back into download mode.
Sent from my SCH-I500 using XDA App
I've been working all weekend so I havent had too much time to deal with it. I wiped data and cache in the recovery menu initially and then the phone wouldn't allow me to sign back into my Google account. It kept telling me that I didn't have a data connection on 3g OR wifi. I finally did a factory reset through the privacy menu (not in recovery) and all seems to finally be working and completely stock. Now off to root and flash voodoo...
hey i had the same problem i made a post on how to fix it though.. go to the 0.00 internal storage issue mine was doing what u said plus more but i fixed it just follow the steps i set
http://forum.xda-developers.com/showthread.php?t=804457
Got it. Just for the record: Rooted, Flashed all three files with Odin to get "back to stock". Re-OTA'd. Somehow Busybox and Su were still there so I manually removed. Then changed my mind about returning the phone and attempted to root again with no luck. Re-flashed through Odin ok, then attempted root but errors prevented finish. Cleared data and wiped cache through recovery. Then my google account wouldn't resync b/c of network connection error, even though I had a working data connection the entire time. Tried booting into recovery and clear and wipe data again. No luck. Finally decided to use factory data reset from within settings. Now all clear, rooted again, re-synced my google account and all good. You guys rock. Thanks for the help.
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Thanks for the reply!
I didn't check the MD5 last night but I did just now and it matches.
I did a cache wipe the first time but not a system wipe. Then I started getting more desperate and tried reinstalling w/ system wipes and factory resets, but it didn't change anything.
No, I didn't change the ROM. Doing the Bootloader unlock exploit was about the absolute maximum of my technical abilities! The only thing I know I did wrong was that I didn't downgrade to the old boot version the first time (mainly because the wifi thing sounded inconsequential and I didn't want to learn the procedure if I didn't have to).
Anyway, I just tried Ultimate KangBang and it seems to work--no error messages so far. I don't know what I did wrong, but hopefully this keeps working!
IceDragon59 said:
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
Click to expand...
Click to collapse
andybones said:
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Click to expand...
Click to collapse
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
franklin411 said:
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
Click to expand...
Click to collapse
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
in the future it is always good practice to backup(nandroid) your current ROM. I have been burned too many times, always do a nandroid before you do anything in recovery.
your photos are normally saved to the SD, flashing ROMs or wiping the system will not delete them
andybones said:
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
Click to expand...
Click to collapse
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
franklin411 said:
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
Click to expand...
Click to collapse
na the name has nothing to do with it. it can be named whatever.
im guessing the wipe worked.
franklin411 said:
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Click to expand...
Click to collapse
weird, i was having the same problem with the same processes stopped working. i wiped cache dalvik and system but not factory reset. once i factory reset, it worked fine. i figured a system wipe would have been enough....
Hey all.
So just a few hours ago, I was running rooted stock, as per the guide in the development section. I then installed twrp, and attempted to flash a ROM, which resulted in my phone not booting.
Since then, I got into recovery, attempted a factory reset (which didn't work), and ended up using Odin to restore to stock.
So now I'm sitting on the stock image, unsure if I have root. Everything seems to work fine, but is slow. Also, I cannot enable wifi (the switch goes on for a split second, then back to off).
Is there a way I can uninstall twrp, and go back to complete and total stock?
If it's relevant, I get a constant "This device has detected an application attempting unpermitted actions..." error.
Thanks guys!!!
UPDATE: It still has root access.
UPDATE 2: I'm finding some similar issues people were having with the T-Mobile version (http://androidforums.com/t-mobile-g...connect-wifi-prevention-information-help.html) though I'm not sure whether I can follow those solutions. I will wait until someone can advise me on this.
It sounds like you didn't installed the complete stock image, that the stocked rooted image is installed. Have you done factory reset?
wolfgrrl said:
It sounds like you didn't installed the complete stock image, that the stocked rooted image is installed. Have you done factory reset?
Click to expand...
Click to collapse
I tried the factory reset option from within twrp recovery, which doesn't fix any of these issues I'm having with constant security alerts or Wifi.
Got it fixed by doing this:
http://forum.xda-developers.com/showthread.php?t=2301259
I recently tried to re-install root on my device. I used the link below to root:
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
Everything worked fine, my phone rebooted normally, said it was rooted and I went on my day. Later that day I rebooted my phone and now it wont start up. It just pauses at the verizon logo and never gets past that. I can get into the default LG recovery, but I don't know how much I can really do there.
I really need to recover some of my files, contacts, etc. If I could just fix the issue without losing data that would be better, but at the very least I need to save some files from my phone. Any ideas?
EDIT: I have done some research and found I can fix my issue if I'm able to get my phone to be recognized by my computer. For some reason the MTP USB Device driver fails the install...
Have you gotten into recovery and tried to wipe the cache?
If you can get into the stock recovery you should be able to choose wipe cache and it will take you to twrp if you have it flashed onto your phone. From there you can restore or wipe the cache and see if that helps.
Exact problem
My s3 is soft bricked and i need all my information back, would pay for help
Majnuel said:
My s3 is soft bricked and i need all my information back, would pay for help
Click to expand...
Click to collapse
Your hit there's no way to recover information from a soft/hard brick requires a factory flash
Hey guys, I was running stock ZVC (with stock recovery and bootloader) until just a few minutes ago, when I finally gave in and told the phone to apply the OTA update that was pushed out last week (the "ZVE" one). It started doing its thing, but next time I looked back at the device it was in recovery mode, just sitting there at the menu prompt...
I've since tried rebooting and powering off about half a dozen times, but it just keeps looping back to recovery mode. I also tried wiping the cache and rebooting, with no luck... It still loops back to recovery mode. I don't know what went wrong, but I'm assuming it could be related to one of two things that I didn't think about until afterwards:
1) The phone was rooted via Kingoroot, and root was still active when I tried to apply the update.
2) Just a FEW programs were frozen via TitaniumBackup (as well as Android's own app management system, using the "disable" feature), but these weren't system- or kernel-critical apps. They were things like LG Health, Sprint Money, etc...
Can anyone suggest a fix? Right now it just keeps rebooting into stock recovery and I've never had to deal with an issue like this, so I'm not sure what to do. I was obviously running the stock ROM, so I'm not set up to flash stuff. Although if it can be done with the default recovery, I suppose I could obviously do that... Once again, everything was stock on the phone except for Kingoroot, which was still enabled during the update.
I'm in a pickle here, guys. It's not like I'm any different than everyone who "needs their phone for work," but yeah, I need my phone for work... If I have to wipe data/factory reset, there's probably no way to pull some data off of the phone via PC first, is there? I suppose it's not that big of a deal, but I have some data and some program data that I hadn't gotten around to backing up yet, because I didn't think I'd need to until before I attempted to flash a new ROM or custom recovery.
Any help would be HUGE. Thanks...
EDIT: I took it into the Sprint store today a couple hours after I posted this, and they said I'd have to send it in to LG for warranty service. I don't know if the Sprint tech person knew what she was doing or not (because she had to use Google to figure out how to put the phone into download mode, even though she owns the same model), but she said that she couldn't establish a connection between the PC and the phone...
Now I'm not sure if that's the case, or if she just didn't have the right drivers installed, or if she was even in the right mode (I think she was using some Sprint-made flashing tool, but she did get it into download mode). She also seemed bored and like she just didn't wanna deal with it, so I don't know...
Assuming I can flash back to an earlier build like ZVB (and assuming I can even find it online), is that done from download mode or from recovery? By the way, we also tried just doing a factory reset and that didn't work either; just keeps rebooting to recovery...
Thanks...
EDIT 2: Fixed by flashing to stock via these instructions. Had to select Board DL and use a different key sequence as described here.