Database Info

Lost LTE signal after rooting. Please help!

Hi, I recently decided to root my Nexus 5 using this guide on youtube: /watch?v=J1AKqrrf-5o
But after I'm all done with the rooting process, I noticed that my Nexus 5 has lost its LTE signal. Now it onlyy uses 3G. I managed to put it back on LTE by doing: *#*#4636#*#* and changed my prefered network, but by doing so, I lost my service with T-Mobile. Can't call or send messege with LTE on.
Please help me! I'm very new to Android and rooting but this first experience is not so good. Can you tell me what went wrong? Also, I rooted using the Linux guide.

Rooting alone won't mess up Wi-Fi. Don't use you tube use this http://forum.xda-developers.com/showthread.php?p=47025283
You might need this first. http://forum.xda-developers.com/showthread.php?p=47156064

jd1639 said:
Rooting alone won't mess up Wi-Fi. Don't use you tube use this http://forum.xda-developers.com/showthread.php?p=47025283
Click to expand...
Click to collapse
Many thanks, but I what can I do now? I don't want to sound like a jerk but what can the link do if I already rooted using the youtube guide (sorry again if that does sound jerkish).

danny2146 said:
Many thanks, but I what can I do now? I don't want to sound like a jerk but what can the link do if I already rooted using the youtube guide (sorry again if that does sound jerkish).
Click to expand...
Click to collapse
That's why I have you the second link

If all else fails flash the google stock images

Agreed. A root alone should not have caused an issue with your radio unless something went incorrectly. I would ( personally ) flash Google's stock nexus images and then possibly try again. Gaining root access can be done different ways, you may need to read into other alternatives...

I don't know. I use the ChainFIre CF Auto root on Ubuntu. I did unrooted the device earlier and was able to get LTE and service to work. Though after I use this samw method again, LTE stopped working properly, so I guess something is wrong with this method. Will try the "standard" method later though, if I can get a hold of a windows computer.

Let's back track a bit. What is the goal with root? Are you wanting to keep a custom recovery? What network are you using?
If you are going to just root stock and not go for a custom rom, I'd just flash a custom recovery via fastboot then boot to recovery and flash the SuperSU zip from Chainfire. At that point, you're rooted stock. If you decide to take an OTA update then you'll just need to make sure that you have the stock recovery installed. However, it's just as easy to flash the update when one of our devs packages it as a rom zip to flash via custom recovery, if not easier really.

Frankly, at this point my knowledge about android phone is still very hazy as this is acually my first ever phone, let along rooting, but I am eager to learn. So what's wrong if I didn't get a custom recovery? I just followed the instruction that they (chainfire autoroot) have for Linux and got this. Dunno if it was something in my phone nor the root. I am on T-Mobile BTW.

Yea, I'm baffled by that method affecting anything to do with service. It should be one of the least intrusive ways to root. However, weird things happen. So where are we now? Are you still rooted with the service issues? Which update / baseband are you on? You have the correct T-Mobile APNs? Have LTE(Recommended) selected under Preferred Network Mode in Settings / More... /Mobile Networks? Shouldn't really be necessary to mess with changing stuff in the Hidden Menu in this instance.

I'm on T-mobile Nexus 5 KitKat 4.4.2, with LTE in prefered mobile data. I rooted, the problem happened, unrooted this morning, the problem gone, rooted again with same method, the problem came back. I think I have the right APN since there are two with T-mobile options and I have tried both of them. As of now, I am still on root, but thinking of unroot it again...

danny2146 said:
I'm on T-mobile Nexus 5 KitKat 4.4.2, with LTE in prefered mobile data. I rooted, the problem happened, unrooted this morning, the problem gone, rooted again with same method, the problem came back. I think I have the right APN since there are two with T-mobile options and I have tried both of them. As of now, I am still on root, but thinking of unroot it again...
Click to expand...
Click to collapse
Still scratching my head over that, as the whole idea of Chainfire's auto root just literally is only supposed to install the SuperSU app and the binary and make no other changes. Obviously that isn't the case for you though. Are you unrooting via the settings in the SU app or via reflashing the stock img files?

es0tericcha0s said:
Still scratching my head over that, as the whole idea of Chainfire's auto root just literally is only supposed to install the SuperSU app and the binary and make no other changes. Obviously that isn't the case for you though. Are you unrooting via the settings in the SU app or via reflashing the stock img files?
Click to expand...
Click to collapse
I used the stock flashing method. I only unrooted it though, not lock the boot loader.

danny2146 said:
I used the stock flashing method. I only unrooted it though, not lock the boot loader.
Click to expand...
Click to collapse
Ok. So at this point, I would have the SuperSU zip (contains the SuperSU app and su binary) http://download.chainfire.eu/381/SuperSU/UPDATE-SuperSU-v1.91.zip on your phone, then fastboot a custom recovery like TWRP http://techerrata.com/browse/twrp2/hammerhead (fastboot flash recovery nameofrecovery.img), boot into recovery, and flash the zip. No need to wipe anything. Should just be able to flash and go. Then open SuperSU and make sure the binary is updated.

I'm sorry but how does one flash a custom recovery? Do I need a PC alondside or I can just do it entirely on my phone?

danny2146 said:
I'm sorry but how does one flash a custom recovery? Do I need a PC alondside or I can just do it entirely on my phone?
Click to expand...
Click to collapse
I included the command in the parenthesis in the last post.
In bootloader mode on the phone, of course, flash from PC, with the file in your fastboot folder:
fastboot flash recovery nameofrecovery.img (note - you can change the name of the file you download to whatever, as long as you leave the extension .img alone. ex: twrp.img)
If you are rooted already or still, you can flash from the phone either via the GooManager app https://play.google.com/store/apps/details?id=com.s0up.goomanager like this:
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will install the recovery automatically.
or
(Rooted only) You can also use the app Flashify to flash the .img file directly from the phone. https://play.google.com/store/apps/details?id=com.cgollner.flashify
So yea, to solve your issue, I think it would be best to just start clean/stock, then go with the custom recovery flashed from PC + SuperSU zip method. If you can fastboot the other files to return to stock, this is no different and very quick. Should not take more than 5-10 seconds to flash the recovery. The whole operation, starting from scratch should take make 3-5 minutes to flash recovery, boot to it, flash the SuperSU zip then reboot, assuming you have fastboot set up properly and the 2 files you need downloaded already.

es0tericcha0s said:
I included the command in the parenthesis in the last post.
In bootloader mode on the phone, of course, flash from PC, with the file in your fastboot folder:
fastboot flash recovery nameofrecovery.img (note - you can change the name of the file you download to whatever, as long as you leave the extension .img alone. ex: twrp.img)
If you are rooted already or still, you can flash from the phone either via the GooManager app https://play.google.com/store/apps/details?id=com.s0up.goomanager like this:
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will install the recovery automatically.
or
(Rooted only) You can also use the app Flashify to flash the .img file directly from the phone. https://play.google.com/store/apps/details?id=com.cgollner.flashify
So yea, to solve your issue, I think it would be best to just start clean/stock, then go with the custom recovery flashed from PC + SuperSU zip method. If you can fastboot the other files to return to stock, this is no different and very quick. Should not take more than 5-10 seconds to flash the recovery. The whole operation, starting from scratch should take make 3-5 minutes to flash recovery, boot to it, flash the SuperSU zip then reboot, assuming you have fastboot set up properly and the 2 files you need downloaded already.
Click to expand...
Click to collapse
I don't know , but this is very interesting. I now suspect that the problem is from T-Mobile's end, not mine, nor the root. I just dug into my mom,dad's phone and what did I find? 3 goddamn G! Not LTE. But when I tried to force the thing to get LTE, it disconnected from the service. However, when I moved to another location this evening, both the LTE and service came back. I think something odd is happening either in my neighborhood or T-Mobile service. Anyways, seems like nothing of major, might have to have a talk to T-Mobile about this.
But last question, with my CF root now, how can I know if I already have a custom recovery yet? And which one? You know for if I want to flash a ROM in the future. And thank you for your help!

danny2146 said:
I don't know , but this is very interesting. I now suspect that the problem is from T-Mobile's end, not mine, nor the root. I just dug into my mom,dad's phone and what did I find? 3 goddamn G! Not LTE. But when I tried to force the thing to get LTE, it disconnected from the service. However, when I moved to another location this evening, both the LTE and service came back. I think something odd is happening either in my neighborhood or T-Mobile service. Anyways, seems like nothing of major, might have to have a talk to T-Mobile about this.
But last question, with my CF root now, how can I know if I already have a custom recovery yet? And which one? You know for if I want to flash a ROM in the future. And thank you for your help!
Click to expand...
Click to collapse
Just boot into recovery and see what you have.

If you used CF-Root, then it would not have installed a custom recovery. This is something that you would have done on your own and not likely to have forgotten. If you root access is working properly, I'd suggest installing TWRP from the GooManager app as it's pretty easy and no PC required.
http://teamw.in/project/twrp2/205
Then make a nandroid back up of your phone and make sure to back up the EFS folder too and save them to a safe place. You can back that up in TWRP or from the method described here:
http://forum.xda-developers.com/showthread.php?t=2514095

Let's back up here. Why do you think you need root if you have no idea what you are doing? Are you just rooting because you can or do you have a real purpose?
Sent from my Nexus 5

Custom Recovery

Hey all. Just wanted to let anyone know that doesn't already that the recovery installer for the F400 and D855 works on our variant. Just used the apk and have functional custom recovery. I was able to flash the volume boost mod I had on my G2 and it worked flawlessly. If you use it, when you click reboot system it will come up with a message saying "Potential loss of root, would you like to fix?" Just click no. Clicking no reboots system and root isn't lost. Clicking yes boots into stock recovery and gives an error message but you can still reboot system normally without loss of root. I did both options to check before I posted this .
This isn't a total traditional recovery flash. It's an apk that flashes a temporary custom recovery while leaving stock recovery intact. When you click the apk you'll have the option to install recovery. Once you do it will allow selection of rebooting into recovery. You have to go into the apk to reboot into custom recovery each time but its a temporary solution until we get fully functioning perm custom rec. You can make nandroid and restore nandroid. Tested both and they are working.

BreakingVZW said:
Hey all. Just wanted to let anyone know that doesn't already that the recovery installer for the F400 and D855 works on our variant. Just used the apk and have functional custom recovery. I was able to flash the volume boost mod I had on my G2 and it worked flawlessly. If you use it, when you click reboot system it will come up with a message saying "Potential loss of root, would you like to fix?" Just click no. Clicking no reboots system and root isn't lost. Clicking yes boots into stock recovery and gives an error message but you can still reboot system normally without loss of root. I did both options to check before I posted this .
This isn't a total traditional recovery flash. It's an apk that flashes a temporary custom recovery while leaving stock recovery intact. When you click the apk you'll have the option to install recovery. Once you do it will allow selection of rebooting into recovery. You have to go into the apk to reboot into custom recovery each time but its a temporary solution until we get fully functioning perm custom rec. You can make nandroid and restore nandroid. Tested both and they are working.
Click to expand...
Click to collapse
good to know, thanks... but it doesn't have the full abilities of custom recovery, eg: flashing kernels/roms. correct? we still need to unlock the bootloader for that, yes?

screwyluie said:
good to know, thanks... but it doesn't have the full abilities of custom recovery, eg: flashing kernels/roms. correct? we still need to unlock the bootloader for that, yes?
Click to expand...
Click to collapse
Yes you are correct. I believe that the Chinese recovery doesn't allow writing to the system partition of the phone so you won't be able to restore a backup. People say you can make one though. It may be able to flash a ROM bit that is untested due to the lack of something to flash and test. But if you needed to flash a small mod then this should work. Although be careful because I think I've read that the partitions may not be correct so use at your own risk.
Sent from my LG-D850 using XDA Premium 4 mobile app

roughneckboren said:
Yes you are correct. I believe that the Chinese recovery doesn't allow writing to the system partition of the phone so you won't be able to restore a backup. People say you can make one though. It may be able to flash a ROM bit that is untested due to the lack of something to flash and test. But if you needed to flash a small mod then this should work. Although be careful because I think I've read that the partitions may not be correct so use at your own risk.
Sent from my LG-D850 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah I should have included that in my OP. It works well enough for minor mods and you can make backups. Thanks for adding that.

Got a link to download the apk?

http://forum.xda-developers.com/showthread.php?t=2825865
Be aware of the faults in this.
Sent from my LG-D850 using XDA Premium 4 mobile app

ReggieSmith said:
Got a link to download the apk?
Click to expand...
Click to collapse
If you're only flashing minor mods you'll be fine. Don't expect to be able to flash kernels or ROMs though.

Could you check the qfuse, see if it tripped?

mrhaley30705 said:
Could you check the qfuse, see if it tripped?
Click to expand...
Click to collapse
Mine didn't.

BreakingVZW said:
Hey all. Just wanted to let anyone know that doesn't already that the recovery installer for the F400 and D855 works on our variant. Just used the apk and have functional custom recovery. I was able to flash the volume boost mod I had on my G2 and it worked flawlessly. If you use it, when you click reboot system it will come up with a message saying "Potential loss of root, would you like to fix?" Just click no. Clicking no reboots system and root isn't lost. Clicking yes boots into stock recovery and gives an error message but you can still reboot system normally without loss of root. I did both options to check before I posted this .
This isn't a total traditional recovery flash. It's an apk that flashes a temporary custom recovery while leaving stock recovery intact. When you click the apk you'll have the option to install recovery. Once you do it will allow selection of rebooting into recovery. You have to go into the apk to reboot into custom recovery each time but its a temporary solution until we get fully functioning perm custom rec. You can make nandroid and restore nandroid. Tested both and they are working.
Click to expand...
Click to collapse
By chance, do you have a screenshot of this recovery? We can all enter the built in recovery quickly using the Quick Boot app found in GPlay. I would like to see what this recovery offers, different from the stock recovery.
Thanks

TonyStark said:
By chance, do you have a screenshot of this recovery? We can all enter the built in recovery quickly using the Quick Boot app found in GPlay. I would like to see what this recovery offers, different from the stock recovery.
Thanks
Click to expand...
Click to collapse
How would I go about getting you a screen shot? I can't use the screenshot method bc the recovery isn't touch and if you press the traditional hardware key method it makes selections in the recovery bc of the use of the power key.

BreakingVZW said:
How would I go about getting you a screen shot? I can't use the screenshot method bc the recovery isn't touch and if you press the traditional hardware key method it makes selections in the recovery bc of the use of the power key.
Click to expand...
Click to collapse
A webcam, camera etc. If you are unable to do this, no worries.

TonyStark said:
A webcam, camera etc. If you are unable to do this, no worries.
Click to expand...
Click to collapse
I can do that for you when I get off work.

About Root in 05Q

Hello guys!!!, Today I get the new OTA with the firmware 05Q and I install it. I see in the forum a version of 05Q rooted LINK HERE
I only want to ask if anyone know another way of get root actually or if I should wait until our amazing toolkits for 1+1 get updated.
Thanks i nadvance!!! :cyclops:

You can gain root following, This thread. If you already have a custom recovery install, might be easier to install the pre-rooted 05QA. I went the second route.
P.S. That toolkit will root 05QA, just does not have the new firmware to go back to stock.

I have a custom recovery installed ofc, if I install the pre-rooted 05Q I lost all my data and apps? Should I do a factory reset? Thanks for your fast answer mate!!

Istvan_86 said:
I have a custom recovery installed ofc, if I install the pre-rooted 05Q I lost all my data and apps? Should I do a factory reset? Thanks for your fast answer mate!!
Click to expand...
Click to collapse
If you have custom recovery installed. Do a back up first. You should not have to wipe or lose anything.

rraquib said:
If you have custom recovery installed. Do a back up first. You should not have to wipe or lose anything.
Click to expand...
Click to collapse
Really thanks again mate!! I do it, like you, as soon as possible.

Wait guys, all you need to do is flash SuperSU from your custom recovery. That's it, nothing more.
@rraquib, why on earth would you tell him to flash the entire ROM again??

timmaaa said:
Wait guys, all you need to do is flash SuperSU from your custom recovery. That's it, nothing more.
@rraquib, why on earth would you tell him to flash the entire ROM again??
Click to expand...
Click to collapse
@timmaaa Read carefully I mentioned both option and he was wondering about the pre-rooted version.

rraquib said:
@timmaaa Read carefully I mentioned both option and he was wondering about the pre-rooted version.
Click to expand...
Click to collapse
You said that flashing entire ROM would be easier, it isn't. All that's need to get root is to flash the SuperSU zip. He's already on 05Q so flashing the ROM zip is completely and utterly pointless. It's like telling someone who's run out of petrol to install a entirely new petrol tank that's full of petrol (when all that's actually needed is the fuel).
It doesn't matter what someone thinks might be the solution, if you're going to answer in the q&a section you need to give the best and easiest solution.

The thing is flashing update-supersu is not working... for me at least. I updated OTA.. After installation finished, rebooted to TWRP and tried to install update-supersuv2.37.zip...
It doesn't show any error, but when I reboot my phone there is no supersu installed ( actually there is one but it's greyed out with android icon and not showing up on application list )

timmaaa said:
Wait guys, all you need to do is flash SuperSU from your custom recovery. That's it, nothing more.
@rraquib, why on earth would you tell him to flash the entire ROM again??
Click to expand...
Click to collapse
+1
only SU from TWRP

plato79 said:
The thing is flashing update-supersu is not working... for me at least. I updated OTA.. After installation finished, rebooted to TWRP and tried to install update-supersuv2.37.zip...
It doesn't show any error, but when I reboot my phone there is no supersu installed ( actually there is one but it's greyed out with android icon and not showing up on application list )
Click to expand...
Click to collapse
Install a newer version
#stayparanoid

Sorry guys for don´t answer your comments, I have been working out of my country for a couple of weeks.
I get root on 05Q with just flashing SuperSU 2.46 from recovery. Easy and fast, just that.
Anyway you have my thanks in your respective buttons.
EDIT: If moe people with doubts read this. I use the info on this post. http://forum.xda-developers.com/showthread.php?t=2788632

6.0.1 ota with stock rooted 6.0

My v10 downloaded an OTA , which im assuming is 6.0
1. Im rooted on stock 6.0 and unlocked boot loader. Will the OTA work without messing up anything ? Ill have to root again im sure, just want some info before i pull the trigger.

I don't think the update will even proceed being that you're on a rooted ROM. I have that notification too, and i just don't know how to turn it off.

I to am rooted,unlockboot and stock rom. I don't feel like taking a chance. So I used titanium backup to freeze the software update and in the drop down notification if you press it, it's a notification from Google play services if you block it in apps it will disappear from your drop down. I also deleted the update zip in the cache folder.I used es file explorer ,device/cache/update

popwar said:
My v10 downloaded an OTA , which im assuming is 6.0
1. Im rooted on stock 6.0 and unlocked boot loader. Will the OTA work without messing up anything ? Ill have to root again im sure, just want some info before i pull the trigger.
Click to expand...
Click to collapse
Okay, I'm assuming you are on H90120e (system version). There is a root exploit for the H90120j update. You just do the following:
Make a backup of your apps and settings
Flash your phone to the new update (H90120j)?
Take a look at either one of these threads to root your device again:
http://forum.xda-developers.com/tmobile-lg-v10/general/step-step-guide-rooting-lg-v10-using-t3382631
OR
http://forum.xda-developers.com/tmobile-lg-v10/general/root-android-6-0-h901-t3382819

You can't flash the phone that is already rooted and has TWRP.
I am in this same situation. On stock rom with root and twrp. I want to update to the new update, but do not want to loose all my apps, settings, etc.
Question is, how to do the initial update before having to re-root again?
How do we flash the phone with the new update?

bhagiratha said:
You can't flash the phone that is already rooted and has TWRP.
I am in this same situation. On stock rom with root and twrp. I want to update to the new update, but do not want to loose all my apps, settings, etc.
Question is, how to do the initial update before having to re-root again?
How do we flash the phone with the new update?
Click to expand...
Click to collapse
Why can't you flash the phone that is already rooted and has TWRP?
All you are doing is opening the LGUP tool and flashing the new H90120j .kdz file using the "refurbish" option then flashing the H90120j .tot file that has TWRP using the "update" option which will flash the phone regardless of what is running on your phone. The guides on the first link explain that. I believe your concern is keeping all of your settings and apps. Look up Titanium backup, it works for me.

Thank you. I only flash the LGH901AT-01-V20j-310-260-JUL-12-2016-ARB02+0ROOTTWRP tot file and all is good.
Well except that I lost Dolby audio.
I will look for a fix.

jun19inf said:
Okay, I'm assuming you are on H90120e (system version). There is a root exploit for the H90120j update. You just do the following:
Make a backup of your apps and settings
Flash your phone to the new update (H90120j)?
Take a look at either one of these threads to root your device again:
http://forum.xda-developers.com/tmobile-lg-v10/general/step-step-guide-rooting-lg-v10-using-t3382631
OR
http://forum.xda-developers.com/tmobile-lg-v10/general/root-android-6-0-h901-t3382819
Click to expand...
Click to collapse
Hi,
Do I have to use LGUP to install the update or can I click install on the dropdown of my phone?
I'm on stock MM 6.0 (H90120e) Rooted and I will not have access to my main PC for another week as I'm traveling.
Thanks,
-NJ

Anyone?

bhagiratha said:
You can't flash the phone that is already rooted and has TWRP.
I am in this same situation. On stock rom with root and twrp. I want to update to the new update, but do not want to loose all my apps, settings, etc.
Question is, how to do the initial update before having to re-root again?
How do we flash the phone with the new update?
Click to expand...
Click to collapse
There's a guide in general that tells how to do all this. In fact jun19inf WROTE it.
In a nutshell, do a twrp backup.
Upgrade to 20j by flashing the stock 20j kbz.
Enable usb debugging and oem unlock
flash tot that has twrp in it.
Now you can go into twrp and 1) root via supersu 2) restore ONLY data from your twrp backup taken previously to get your apps etc back. Alternatively Titanium Backup will also do just fine.

njdevils28 said:
Hi,
Do I have to use LGUP to install the update or can I click install on the dropdown of my phone?
I'm on stock MM 6.0 (H90120e) Rooted and I will not have access to my main PC for another week as I'm traveling.
Thanks,
-NJ
Click to expand...
Click to collapse
If all is you have is root, you should be able to unroot in the SuperSU settings, and then let the update install. But if you have TWRP, then I can't see any way to do the update without using a PC to flash your phone back to stock ROM and recovery. Although you may check the dev. section to see if Eliminator has a flashable ROM to bring you up to date.
Sent from my LG-H901 using XDA-Developers mobile app

YrrchSebor said:
If all is you have is root, you should be able to unroot in the SuperSU settings, and then let the update install. But if you have TWRP, then I can't see any way to do the update without using a PC to flash your phone back to stock ROM and recovery. Although you may check the dev. section to see if Eliminator has a flashable ROM to bring you up to date.
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
Ah. Thank you very much!
-NJ

Hi all. I just got my factory warranty back and I attempted to root it. Everything went as it should, until just after the install finished. Instead of rebooting normally, it now will only reboot into TWRP. Once there, when I try to flash a custom ROM (in this case, Bliss, but I don't think it matters, I get an error message that says the zip file is corrupt. Then, while still in recovery, when I tried to wipe everything except the sd card, it says mkfs.fat process ended with error. I then powered down and attempted the factory reset. I scrolled down on both screens and it did not say anything about any errors, so I assumed it took. However, it reboots right back into TWRP recovery. It also boots right to TWRP recovery when I try to boot normally. Of course, adb does not recognize the phone in any mode that I can get into (fastboot/recovery/download), so, I can't use LG Bridge to reflash the original firmware. Does anybody have any ideas for a fix? I know that this replacement phone had 6.0 on it. I thought I did everything to a t? TIA...
OK, not sure how I got there, but when I attempt to reboot from TWRP it says No OS Installed! Are you sure you want to reboot? That at least says what the problem is. Does anybody know how to fix this?

Where can I download the update file?

wbexpress said:
Hi all. I just got my factory warranty back and I attempted to root it. Everything went as it should, until just after the install finished. Instead of rebooting normally, it now will only reboot into TWRP. Once there, when I try to flash a custom ROM (in this case, Bliss, but I don't think it matters, I get an error message that says the zip file is corrupt. Then, while still in recovery, when I tried to wipe everything except the sd card, it says mkfs.fat process ended with error. I then powered down and attempted the factory reset. I scrolled down on both screens and it did not say anything about any errors, so I assumed it took. However, it reboots right back into TWRP recovery. It also boots right to TWRP recovery when I try to boot normally. Of course, adb does not recognize the phone in any mode that I can get into (fastboot/recovery/download), so, I can't use LG Bridge to reflash the original firmware. Does anybody have any ideas for a fix? I know that this replacement phone had 6.0 on it. I thought I did everything to a t? TIA...
OK, not sure how I got there, but when I attempt to reboot from TWRP it says No OS Installed! Are you sure you want to reboot? That at least says what the problem is. Does anybody know how to fix this?
Click to expand...
Click to collapse
Did you select refurbish or upgrade?
I believe you need to select upgrade when flashing or you get stuck in TWRP
Sent from my LG-H901 using XDA-Developers mobile app

How to root V10 T-mobile M.M ver V20L
How to root V10 T-mobile M.M ver V20L
Can some one guide me on the following:
1. Can I flash back and downgrade to Software version V20J from V20L.
2. Is there any root method for V10 t-mobile MM ver V20L.

1. It is well explained in this forum, you CANNOT go back without facing a software brick.
2. You can root your phone through Dirty_Cow method or by flash Eliminater74 ROM (Part1 & Part2).
Again, search for that in this section and in development one...

jonsat said:
1. It is well explained in this forum, you CANNOT go back without facing a software brick.
2. You can root your phone through Dirty_Cow method or by flash Eliminater74 ROM (Part1 & Part2).
Again, search for that in this section and in development one...
Click to expand...
Click to collapse
Thanks so much for your reply, I was about to flash it to downgrade my V10 from V20L to V20J i even downloaded the files for it Phew....
Okay, I have searched most of the rootings are V20J i have not found a method for rooting and twrp for V20L software update.
Please if u can share the link, that would be helpful...
thanks regards,

I wonder how people perform searches... by the way, few lines under this very thread, there is:
https://forum.xda-developers.com/tmobile-lg-v10/general/root-20l-dirty-cow-t3498722

jonsat said:
I wonder how people perform searches... by the way, few lines under this very thread, there is:
https://forum.xda-developers.com/tmobile-lg-v10/general/root-20l-dirty-cow-t3498722
Click to expand...
Click to collapse
Awwhh GOD!!! big thanks for your help, u r truly an awesome person. Peace and blessing upon u.
regards,

Stuck in bootloop after flashing xposed

Hello, I got Samsung J-7108 and I got stuck in bootloop after flashing Xposed Framework with flashfire... I am sure I downloaded the right version for my CPU, the latest one. I flashed the original firmware, but it doesn't work. I don't have a custom recovery, what can I do? Help, please.

Speeder12321 said:
Hello, I got Samsung J-7108 and I got stuck in bootloop after flashing Xposed Framework with flashfire... I am sure I downloaded the right version for my CPU, the latest one. I flashed the original firmware, but it doesn't work. I don't have a custom recovery, what can I do? Help, please.
Click to expand...
Click to collapse
Did you ever figure out how to fix this issue? Was very curious about this Flashfire.
Paul R

try to flash boot.bin for your phone ,, extract it from stock room and convert ti from bin to tar and flash it

Thank you for your replies. I had to do a factory reset, nothing else helped. So I tried it again, I flashed the Xposed V86 with flashfire, worked fine for two days, than the phone went to bootloop again. I guess I will not deal with xposed anymore, it is a good thing, but doesn't really work as it should.

Okay, so I have a update: Phone works fine for two days. I turn it on and everything seems fine, but... after two days of using it goes to bootloop again no matter what I do. I tried flashing original firmware, works fine for two days, than bootloop again, tried factory resetting, wiping cache and so on, still the same, works, but goes to bootloop every two days when I try to turn it on. Help, please.

Any ideas?

Try to flash the xposed uninstaller zip

messi2050 said:
Try to flash the xposed uninstaller zip
Click to expand...
Click to collapse
I did many times, never helped

Speeder12321 said:
I did many times, never helped
Click to expand...
Click to collapse
I think that u will need to flash twrp then wipe the system/data partitions and reflash stock rom ( note that this may break your phone )

I found out, that stock firmware works fine, but whenever I give it a root access, it stucks in bootloop after 2 days of using the phone... is there anything else I can try before wiping data partitions?

Speeder12321 said:
I found out, that stock firmware works fine, but whenever I give it a root access, it stucks in bootloop after 2 days of using the phone... is there anything else I can try before wiping data partitions?
Click to expand...
Click to collapse
which root method u are using

messi2050 said:
which root method u are using
Click to expand...
Click to collapse
I am using a pre-rooted firmware.

I guess that XPosed changed the values of some System files and uninstaller does no job in changing them back to how they were before. Question is: There's no custom recovery availible for Chinese model of J7, so is there a possibility to delete System using a Root file explorer? Which has access to System partition?

messi2050 said:
which root method u are using
Click to expand...
Click to collapse
When I do factory reset in recovery on rooted firmware, it works again, but like I said, just for two days? How is that even possible? Factory reset should delete everything including changes that xposed made, shouldn't it?

Speeder12321 said:
When I do factory reset in recovery on rooted firmware, it works again, but like I said, just for two days? How is that even possible? Factory reset should delete everything including changes that xposed made, shouldn't it?
Click to expand...
Click to collapse
Xposed modifies System, Factory reset does not affect system only Data.
Your issue isn't xposed.
You are probably receiving a security policy update. The policy update breaks earlier versions of supersu causing bootloops.
You need to flash supersu v2.78 SR1 with Flashfire then the correct Xposed version.
Supersu v2.78 will block the policy up date.

ashyx said:
Xposed modifies System, Factory reset does not affect system only Data.
Your issue isn't xposed.
You are probably receiving a security policy update. The policy update breaks earlier versions of supersu causing bootloops.
You need to flash supersu v2.78 SR1 with Flashfire then the correct Xposed version.
Supersu v2.78 will block the policy up date.
Click to expand...
Click to collapse
I don't think so, I used prerooted firmware for months and never had a single problem... everything started to go wrong after flashing xposed.. So how can be SuperSU a problem if it used to work fine before?
EDIT: And no, I didn't receive security policy update.
EDIT2: But thanks a lot for your advice, I will try to update SuperSU... Is it okay if I flash newer superSU with flashfire, when my current one is installed as a system app or do I need to do something before flashing the new one?

Speeder12321 said:
I don't think so, I used prerooted firmware for months and never had a single problem... everything started to go wrong after flashing xposed.. So how can be SuperSU a problem if it used to work fine before?
EDIT: And no, I didn't receive security policy update.
EDIT2: But thanks a lot for your advice, I will try to update SuperSU... Is it okay if I flash newer superSU with flashfire, when my current one is installed as a system app or do I need to do something before flashing the new one?
Click to expand...
Click to collapse
Use the uninstaller in SuperSU settings.

ashyx said:
Use the uninstaller in SuperSU settings.
Click to expand...
Click to collapse
It is installed as a system app, so I will need to do a full unroot. And if I do full unroot, I won't be able to flash the new one with flashfire, because it needs root access, what now ?
EDIT: Okay, I managed to update SuperSU to version 2.78 SR1, I will post an update if it fixed my issue, thanks

ashyx said:
Xposed modifies System, Factory reset does not affect system only Data.
Your issue isn't xposed.
You are probably receiving a security policy update. The policy update breaks earlier versions of supersu causing bootloops.
You need to flash supersu v2.78 SR1 with Flashfire then the correct Xposed version.
Supersu v2.78 will block the policy up date.
Click to expand...
Click to collapse
Thank you sooooooo so much, it fixed my issue