I rooted my LG G3 with StumpRoot. Everything went fine and I had successful root. Checked it and all. Then I flashed the new Barren ROM (v1) and I lost root. I tried re-running StumpRoot and StumpRoot is claiming I already have my device is already rooted. However, any application that requires root or Superuser, it says that root is not detected. I have Superuser on my phone.
Did you flash through TWRP?
Can you still boot into recovery, and does TWRP come up as your recovery?
This ^^^^^
I have no idea how you can lose root when it's built into it.
Now if you took the OTA update then you will lose root.
Then you have to revert back to zv4 via Flashtool if you want root again.
The FAQ, and the ZV6 threads have all to info you need.
engine95 said:
This ^^^^^
I have no idea how you can lose root when it's built into it.
Now if you took the OTA update then you will lose root.
Then you have to revert back to zv4 via Flashtool if you want root again.
The FAQ, and the ZV6 threads have all to info you need.
Click to expand...
Click to collapse
I don't know how I lost root either. I did not do any OTA updates. All I did was "Update Profile" to get my data working again. I've rooted and flashed roms on many phones, never had this issue until the G3.
CodeCompile said:
I don't know how I lost root either. I did not do any OTA updates. All I did was "Update Profile" to get my data working again. I've rooted and flashed roms on many phones, never had this issue until the G3.
Click to expand...
Click to collapse
Did you unlock the bootloader with "Bump", so you have TWRP?
Then just flash the Rom again. Or any Rom for that matter
engine95 said:
Did you unlock the bootloader with "Bump", so you have TWRP?
Then just flash the Rom again. Or any Rom for that matter
Click to expand...
Click to collapse
I downloaded the TWRP listed on some thread on Sprint LG G3 then used flashify on my rooted G3 to flash it, after that I flashed the custom ROM using TWRP.
Since then, I tried to boot into recovery (power+volume down) and it just booted into safe mode.
Also, if/when I do boot it into recovery, should I also try flashing a SuperSU rom too?
CodeCompile said:
I downloaded the TWRP listed on some thread on Sprint LG G3 then used flashify on my rooted G3 to flash it, after that I flashed the custom ROM using TWRP.
Since then, I tried to boot into recovery (power+volume down) and it just booted into safe mode.
Also, if/when I do boot it into recovery, should I also try flashing a SuperSU rom too?
Click to expand...
Click to collapse
The only thing I can think of is that the download was corrupt. I would try flashing TWRP with Flashify again. If that works, then reinstall SuperSU. That should get you root back. Then download a ROM again, verify the MD5, and flash in TWRP.
If Flashify won't run, then try reinstalling SuperSU, and see if that helps. If not, I think you'll have to revert to the stock ZV4 ROM with LG's Flashtool.
I suggest the Barrin V2 ROM. It's the latest version of Barren, built on the ZV6 ROM instead of ZV4: http://forum.xda-developers.com/sprint-lg-g3/development/rom-barrin-odexed-deodexed-t2950747
I tried using flashify and it gave me an error saying I needed root. I tried booting intorecovery husing the instructions and it either just boots up regularly or goes into safe mmode. Have I bricked my phone to this Rom?
Revert to stock as explained here:http://forum.xda-developers.com/spr...de-how-to-restore-sprint-lg-g3-ls990-t2852042
Then reroot, and start over.
Related
So after rooting and taking the android 4.3 update, my phone worked just fine with root. Then I tried to install a custom recovery (TWRP, using the ADB method) and ever since then, the recovery is just gone. Whenever I try to boot into it, the phone boots into download mode with an error message saying, "Could not do normal boot". After that, I tried installing TWRP from the Goo Manager app. Nothing changes. I also can't find a stock restore for 4.3 or a downgrade to 4.2. Is there any way for me to get back stock recovery or a custom recovery?
m634 said:
So after rooting and taking the android 4.3 update, my phone worked just fine with root. Then I tried to install a custom recovery (TWRP, using the ADB method) and ever since then, the recovery is just gone. Whenever I try to boot into it, the phone boots into download mode with an error message saying, "Could not do normal boot". After that, I tried installing TWRP from the Goo Manager app. Nothing changes. I also can't find a stock restore for 4.3 or a downgrade to 4.2. Is there any way for me to get back stock recovery or a custom recovery?
Click to expand...
Click to collapse
First, you should have done more research. You can't install a custom recovery on 4.3 (or MJ7). The only thing available is a "questionable" root method. No custom ROMs and no Safestrap.
Second, once an update has been applied, there is no way of going back.
You should check this thread out. http://forum.xda-developers.com/showthread.php?t=2507217.
If that doesn't work, try this one. http://forum.xda-developers.com/showthread.php?t=2507253.
Make sure you read ALL instructions first.
Good luck.
m634 said:
So after rooting and taking the android 4.3 update, my phone worked just fine with root. Then I tried to install a custom recovery (TWRP, using the ADB method) and ever since then, the recovery is just gone. Whenever I try to boot into it, the phone boots into download mode with an error message saying, "Could not do normal boot". After that, I tried installing TWRP from the Goo Manager app. Nothing changes. I also can't find a stock restore for 4.3 or a downgrade to 4.2. Is there any way for me to get back stock recovery or a custom recovery?
Click to expand...
Click to collapse
You can't install a custom recovery on 4.3/MJ7.
The only way to recover this is for you to flash the full-wipe MJ7 image that you'll find here in the development forum.
Then, consider reading before flashing. The I545 has a locked bootloader and can't support a custom recovery or custom kernels.
k1mu said:
You can't install a custom recovery on 4.3/MJ7.
The only way to recover this is for you to flash the full-wipe MJ7 image that you'll find here in the development forum.
Then, consider reading before flashing. The I545 has a locked bootloader and can't support a custom recovery or custom kernels.
Click to expand...
Click to collapse
Thanks! Knowing this, I think I will just stick with root but no recovery...hopefully, something will change and allow me to unstick myself from this situation in the future.
riker147 said:
You should check this thread out. http://forum.xda-developers.com/showthread.php?t=2507217.
Click to expand...
Click to collapse
This worked well when I had the same issue. I did lose root even with Survival Mode enabled on SuperSU, but otherwise no issues. Thank you.
So a while back I decided to start my phone fresh. remove root. full factory reset. of course the plan was to re root install a recovery and get back to flashing far too many roms. but ive hit a snag and I cant find my fix.
Starting off, to return to stock I odin flashed the official mdk firmware from back in the day. And then did a factory restore to completely remove everything.
Once done with that I odin flashed the md2 prelease firmware to get root with the motochopper method. updated su binaries and then flashed the mdk kernel back.
And all of that seemed to work fine. Apps requiring root seemed to work fine. But when it came time to flash cwm with rom manager the **** started. after flashing the latest cwm and rebooting into recovery I was greeted with the regular android recovery. So I tried flashing it from rom recovery. That seemed to work. But no roms will flash. Making and restoring a backup kind of worked. But cwn was mainly useless.
So I started over and over with the reverting to stock, factory reseting, and rerooting. ive tried the loki versions of cwm flashing with no luck and have just hit a highly frustrating wall. After near 12 hours trying to figure this out I'm asking for assistance. ive done this before. what the hell is the problem. Help me XDA people. You're my only hope.
Cwm from rom manager hasn't worked in awhile. Use philz touch if you really want cwm. Or use flashify to get twrp
hydeburns said:
So a while back I decided to start my phone fresh. remove root. full factory reset. of course the plan was to re root install a recovery and get back to flashing far too many roms. but ive hit a snag and I cant find my fix.
Starting off, to return to stock I odin flashed the official mdk firmware from back in the day. And then did a factory restore to completely remove everything.
Once done with that I odin flashed the md2 prelease firmware to get root with the motochopper method. updated su binaries and then flashed the mdk kernel back.
And all of that seemed to work fine. Apps requiring root seemed to work fine. But when it came time to flash cwm with rom manager the **** started. after flashing the latest cwm and rebooting into recovery I was greeted with the regular android recovery. So I tried flashing it from rom recovery. That seemed to work. But no roms will flash. Making and restoring a backup kind of worked. But cwn was mainly useless.
So I started over and over with the reverting to stock, factory reseting, and rerooting. ive tried the loki versions of cwm flashing with no luck and have just hit a highly frustrating wall. After near 12 hours trying to figure this out I'm asking for assistance. ive done this before. what the hell is the problem. Help me XDA people. You're my only hope.
Click to expand...
Click to collapse
Like Josh said just use Flashify https://play.google.com/store/apps/details?id=com.cgollner.flashify
It's still updated and works great. To many have had issues with ROM manager or Goo.
Sent from my SCH-I545 using Tapatalk
hydeburns said:
So a while back I decided to start my phone fresh. remove root. full factory reset. of course the plan was to re root install a recovery and get back to flashing far too many roms. but ive hit a snag and I cant find my fix.
Starting off, to return to stock I odin flashed the official mdk firmware from back in the day. And then did a factory restore to completely remove everything.
Once done with that I odin flashed the md2 prelease firmware to get root with the motochopper method. updated su binaries and then flashed the mdk kernel back.
And all of that seemed to work fine. Apps requiring root seemed to work fine. But when it came time to flash cwm with rom manager the **** started. after flashing the latest cwm and rebooting into recovery I was greeted with the regular android recovery. So I tried flashing it from rom recovery. That seemed to work. But no roms will flash. Making and restoring a backup kind of worked. But cwn was mainly useless.
So I started over and over with the reverting to stock, factory reseting, and rerooting. ive tried the loki versions of cwm flashing with no luck and have just hit a highly frustrating wall. After near 12 hours trying to figure this out I'm asking for assistance. ive done this before. what the hell is the problem. Help me XDA people. You're my only hope.
Click to expand...
Click to collapse
I was in the same boat all day yesterday - reset to stock using the MDK No wipe tar via Odin, factory restored, flashed MD2, motochopped, flashed MDK, but then could not get any new recoveries to take. Using Flashify I was just able to install CWM 6.0.4.7 (which I had tried doing using ROM Manager, and paid $1.99 for, which didn't work) - halle-frickin-luyah!
sdsurferbob said:
I was in the same boat all day yesterday - reset to stock using the MDK No wipe tar via Odin, factory restored, flashed MD2, motochopped, flashed MDK, but then could not get any new recoveries to take. Using Flashify I was just able to install CWM 6.0.4.7 (which I had tried doing using ROM Manager, and paid $1.99 for, which didn't work) - halle-frickin-luyah!
Click to expand...
Click to collapse
Thanks guys. I tried all of this with the flashify. Even started off freshly reinstalling stock Mdk and then rerooting with the same method I mentioned earlier. Installing cwm through flashify. And though I can make and restore a backup of my stock rooted Rom. I get the same errors I've been getting trying to flash a custom Rom. I'll try to post a screenshot of the error I get in can when flashing.
Hi everyone. First time posting on the forums and unfortunately it's because of a major problem . So here's my situation:
A couple days ago I decided i would try to update my phone to 5.0 because the update was pushed OTA for the ls990. It supposedly installed with no error, but when it went to reboot it took me straight into my custom recovery. Now when i try to restore from backup, flash a new rom, or wipe the system it will say it was successful, but nothing will change and each time i reboot it takes me right back into recovery. I've tried booting into system or bootloader, but both of those options take me right back into recovery. If i pull the battery and wait then repower the phone it takes me right back into recovery. I need some help here because my phone is practically bricked, yet i still have access to ONLY recovery mode. During each reboot the LG logo does flash on the screen (not sure if that info is useful though). Here's what i'm running:
Specs:
Rooted and Bumped Sprint LG G3 (ls990)
Stock ROM
TWRP Recovery
Maybe this happened because it was a stock update and i didn't have stock android recovery for it to complete the upgrade? My /boot folder appears to be empty in TWRP, but im not sure if that's just because its not even mounting it or if im actually missing a kernel, bootloader, or something else. ANY help or advice will be greatly appreciated. Thank you for your time.
Your gonna have to restore using this guide. It did happen because you were on custom recovery, anytime you want stock upgrade, you must unroot it and put stock recovery back on 1st. It's not bricked if it comes on, only softbricked, which can be fixed with download mode. That guide is well written.
sent from my LG G3
also it was not the android 5.0 update..
Try this first before using the LG Flash tool
http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
It should hopefully save you from wiping the phone completely.
Thanks
joeyhdownsouth said:
Your gonna have to restore using this guide. It did happen because you were on custom recovery, anytime you want stock upgrade, you must unroot it and put stock recovery back on 1st. It's not bricked if it comes on, only softbricked, which can be fixed with download mode. That guide is well written.
sent from my LG G3
Click to expand...
Click to collapse
I reverted to stock firmware using the instructions on that thread and now everything is working! Thank you very much.
Now the only problem is that it seems the new sprint update patched the stump root exploit. Guess ill have to do the firmware flash again lol.
TheInfamousWrong said:
I reverted to stock firmware using the instructions on that thread and now everything is working! Thank you very much.
Now the only problem is that it seems the new sprint update patched the stump root exploit. Guess ill have to do the firmware flash again lol.
Click to expand...
Click to collapse
I think you need zv4 firmware to avoid this problem.
sent from my LG G3
im0rtalz said:
Try this first before using the LG Flash tool
http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
It should hopefully save you from wiping the phone completely.
Click to expand...
Click to collapse
Thank you very much, It works like a chime
I have this problem in yunique i only instaled twrp and it is rebooted into recovery menu but i can't restart my phone it is always going to recovery menu when trying to restart
Select reboot --> Boot to bootloader
When in fastboot
type
fastboot devices
then type
fastboot continue
This will fix the twrp loop issue.
Is there a way to install the d003 ota update from TWRP on a rooted 5x KIW-L24 running B331? The updater pops up every time I boot up, but that method fails. Could it be because I used that script to remove stuff preinstalled on my phone?
bigman1 said:
Is there a way to install the d003 ota update from TWRP on a rooted 5x KIW-L24 running B331? The updater pops up every time I boot up, but that method fails. Could it be because I used that script to remove stuff preinstalled on my phone?
Click to expand...
Click to collapse
It would not update on mine with stock rom and twrp recovery. I think you need to go stock recovery and then update. You can reflash custom recovery and root once it's done. The D003 update definitely took care of my horrible GPS accuracy and fix.
cheers
I flashed the stock b331 recovery. Restored a b331 nandroid. Tried to ota, failed. Dowloaded the full image and did the dload folder reboot to stock recovery method. Fails out at 5%. Tried flashing the update.zip through twrp, fails. tried the newest b331 recovery from the repo, tried to dload folder again. fails... HELP!!!!! please?
bircky311 said:
I flashed the stock b331 recovery. Restored a b331 nandroid. Tried to ota, failed. Dowloaded the full image and did the dload folder reboot to stock recovery method. Fails out at 5%. Tried flashing the update.zip through twrp, fails. tried the newest b331 recovery from the repo, tried to dload folder again. fails... HELP!!!!! please?
Click to expand...
Click to collapse
I used the stock b331 plus stock recovery zip (July 31?) provided in the how to return to stock thread and did a factory reset before boot. It sounds like you still had a custom recovery. That will not work.
You need to be complete stock to be able to install an OTA. It's because it's a file patcher, if files are missing, or modified, it will fail.
That worked !!! Thanks a bunch. Nandroiding a fresh reset for future flubs.
Good !
bircky311 said:
That worked mooms! Thanks a bunch. Nandroiding a fresh reset for future flubs.
Click to expand...
Click to collapse
You are welcome
My SM-G900T is running Lollipop 5.1.1 rooted by installed twrp-3.0.2-2-klte + SuperSU using odin.
I am planning to update it to Marshmallow 6.0.1 (G900TUVS1GPK3) using odin. After the update, I believe the phone will be unrooted. Should I install twrp-3.0.2-2-klte + SuperSU again in order to bring back the root?
Yes, is the short answer. It's a pretty simple process, just flash the update, boot back to Download, flash TWRP, boot to recovery, then flash SU. However, after some experimentation, I'd recommend an extra step, especially if you're planning to run Xposed. After flashing the update, boot into the stock recovery and let the phone boot normally after the stock recovery does its thing. Without this step, Xposed breaks Wifi Calling, and my guess is there are other things which also break, since I get force-closed messages for a couple of T-Mobile processes if I don't let the stock recovery run. Once the phone has booted, just boot back to Download & then flash TWRP & install SU, and Xposed if you want it.
I'm not sure if you'll also need to wipe or not, all the updates I've done have been MM->MM. You can flash those without any wiping or restoring because they don't touch /data. I've found that switching between stock & modified MM roms without wiping appears to work but later causes severe performance problems. Between stock updates, I've had no problems even without wiping.
invisiblewave said:
Yes, is the short answer.
Click to expand...
Click to collapse
Thank you Invisiblewave. I understand that I need to reflash twrp, but since I installed SuperSU already and I think the update would not delete/uninstall it, if I flash SuperSu again, will there be a problem?
The update will remove your previous SuperSU install, so yes, you have to flash it again if you want root.
invisiblewave said:
After flashing the update, boot into the stock recovery and let the phone boot normally after the stock recovery does its thing. Without this step, Xposed breaks Wifi Calling, and my guess is there are other things which also break, since I get force-closed messages for a couple of T-Mobile processes if I don't let the stock recovery run. Once the phone has booted, just boot back to Download & then flash TWRP & install SU, and Xposed if you want it.
Click to expand...
Click to collapse
Thanks for the tips! I just did the same upgrade and wanted to make sure everything worked afterwards.
use this guide
https://forum.xda-developers.com/tm...l/root-how-to-root-sm-g900t-firmware-t3358190
That guide is incomplete. It needs an additional step after flashing the update to let the phone boot once normally, otherwise WiFi calling doesn't work. Flash update, reboot (stock recovery runs and does stuff), reboot to Download, then flash TWRP, SU, Xposed, etc.