so just got a replacement for my v10 that won't turn on. Unfortunately it came with H90120l unlike my nice old Lollipop V10, which was tweaked with all my root features, xposed, xprivacy running good, etc. I have checked the forums and it looks like rolling this replacement back to an original 5.1.1 ROM is impossible (too bad - I still have TWRP backups of my old phone) but is there a way to still root this ROM? I can't seem to find how the 20l can be rooted, I found how to root 20j but not 20l. Any help to links would be appreciated because I'm already very depressed about my lovely phone which was running a week ago, with long battery life and everything that was personalized sweetly, is now officially RIP.
webfrm said:
so just got a replacement for my v10 that won't turn on. Unfortunately it came with H90120l unlike my nice old Lollipop V10, which was tweaked with all my root features, xposed, xprivacy running good, etc. I have checked the forums and it looks like rolling this replacement back to an original 5.1.1 ROM is impossible (too bad - I still have TWRP backups of my old phone) but is there a way to still root this ROM? I can't seem to find how the 20l can be rooted, I found how to root 20j but not 20l. Any help to links would be appreciated because I'm already very depressed about my lovely phone which was running a week ago, with long battery life and everything that was personalized sweetly, is now officially RIP.
Click to expand...
Click to collapse
20l can roll back to 20j, then use the dirty cow exploit to install TWRP. You were very lucky to not get anything newer.
Sent from my Moto Z (2) using XDA Labs
Awesome
skywalker-live said:
20l can roll back to 20j, then use the dirty cow exploit to install TWRP. You were very lucky to not get anything newer.
Sent from my Moto Z (2) using XDA Labs
Click to expand...
Click to collapse
That is good news so I will research how to roll back to 20j, I am guessing with LGUP or something like that. By any chance do you have a link to the dirty cow exploit post? Oh and can you confirm that I'm correct that 5.1.1 is gone for sure?
webfrm said:
That is good news so I will research how to roll back to 20j, I am guessing with LGUP or something like that. By any chance do you have a link to the dirty cow exploit post? Oh and can you confirm that I'm correct that 5.1.1 is gone for sure?
Click to expand...
Click to collapse
I do know that lgup will flash the 20j kdz for you, and that 20j+ is anti-rollback 2 so no going further back. (Although going past 20l into 30b+ has something else that blocks downgradeing) The dirty cow exploit is better explained in the v20 forums where it originated, it should be the same files as the v10 and v20 are both 64 bit phones, just don't use the easy recowvery thread as it only worked for the original v20 firmware. The original dirty cow thread is the most informative. https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Make sure to NOT use the v20 TWRP as I think it will be included in the downloads from that thread. It is a long thread but I believe there are some posts from v10 users.
The most important thing is to read the process and any comments about the variations of the process many times, and that your definitely on 20j otherwise you'll get hung up on one of the steps if still on 20l.
I've never updated past 20l since I found out I have a vs990 motherboard and there were some reports of being bricked by the 30b+ updates if not on a true h901 board.
Sent from my Moto Z (2) using XDA Labs
Thanks
skywalker-live said:
I do know that lgup will flash the 20j kdz for you, and that 20j+ is anti-rollback 2 so no going further back. (Although going past 20l into 30b+ has something else that blocks downgradeing) The dirty cow exploit is better explained in the v20 forums where it originated, it should be the same files as the v10 and v20 are both 64 bit phones, just don't use the easy recowvery thread as it only worked for the original v20 firmware. The original dirty cow thread is the most informative. https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Make sure to NOT use the v20 TWRP as I think it will be included in the downloads from that thread. It is a long thread but I believe there are some posts from v10 users.
The most important thing is to read the process and any comments about the variations of the process many times, and that your definitely on 20j otherwise you'll get hung up on one of the steps if still on 20l.
I've never updated past 20l since I found out I have a vs990 motherboard and there were some reports of being bricked by the 30b+ updates if not on a true h901 board.
Sent from my Moto Z (2) using XDA Labs
Click to expand...
Click to collapse
Thanks Bro I will start with those 151 pages of posts on the dirty cow and see if I can roll back to a ROM I can root and put TWRP on. Still sad about not being on LP ROM but I will get used to MM as long as I can backup and root the phone again. Right now not having root means most of my paid apps are useless and that's just not sitting well with me.
Motherboard question and ADB
Hey,
I was wondering how you would know what motherboard you have. I found this post https://forum.xda-developers.com/tm...step-step-guide-rooting-lg-v10-using-t3382631 for the 20l and the only issue I have is the link to get ADB is dead. Since I have ADB from my previous rooting of the V10 do I need a different ADB? I put all the old files in the D_Cow folder and it seems all the stuff run adb start-server and basic stuff without an issue. I don't want to proceed without knowing if this motherboard or ADB version could be an issue and end up bricking the phone.
skywalker-live said:
I do know that lgup will flash the 20j kdz for you, and that 20j+ is anti-rollback 2 so no going further back. (Although going past 20l into 30b+ has something else that blocks downgradeing) The dirty cow exploit is better explained in the v20 forums where it originated, it should be the same files as the v10 and v20 are both 64 bit phones, just don't use the easy recowvery thread as it only worked for the original v20 firmware. The original dirty cow thread is the most informative. https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Make sure to NOT use the v20 TWRP as I think it will be included in the downloads from that thread. It is a long thread but I believe there are some posts from v10 users.
The most important thing is to read the process and any comments about the variations of the process many times, and that your definitely on 20j otherwise you'll get hung up on one of the steps if still on 20l.
I've never updated past 20l since I found out I have a vs990 motherboard and there were some reports of being bricked by the 30b+ updates if not on a true h901 board.
Sent from my Moto Z (2) using XDA Labs
Click to expand...
Click to collapse
webfrm said:
Hey,
I was wondering how you would know what motherboard you have. I found this post https://forum.xda-developers.com/tm...step-step-guide-rooting-lg-v10-using-t3382631 for the 20l and the only issue I have is the link to get ADB is dead. Since I have ADB from my previous rooting of the V10 do I need a different ADB? I put all the old files in the D_Cow folder and it seems all the stuff run adb start-server and basic stuff without an issue. I don't want to proceed without knowing if this motherboard or ADB version could be an issue and end up bricking the phone.
Click to expand...
Click to collapse
I have since found out that there are solderable links that actually depict what board you have, which means fully dismantling the phone to locate. I have not had the time to do that yet but as I purchased my phone directly from TMobile I think I will find the T link soldered. As for 20l you still have to downgrade to 20j for dirty cow to work. I have the Android sdk installed on my computer and when that is updated adb and fastboot are also made current, there is also a minimal adb/fastboot found here on xda that the links are kept up to date. I didn't need dirty cow since I rooted my v10 with the lollipop builds that still had full fastboot commands. The adb you used before with your v10 should be good enough, mine also helped me root my sons 'gpadx 8.0' running 6.0.
Sent from my Moto Z (2) using XDA Labs
Downgrade to 20J?
skywalker-live said:
I have since found out that there are solderable links that actually depict what board you have, which means fully dismantling the phone to locate. I have not had the time to do that yet but as I purchased my phone directly from TMobile I think I will find the T link soldered. As for 20l you still have to downgrade to 20j for dirty cow to work. I have the Android sdk installed on my computer and when that is updated adb and fastboot are also made current, there is also a minimal adb/fastboot found here on xda that the links are kept up to date. I didn't need dirty cow since I rooted my v10 with the lollipop builds that still had full fastboot commands. The adb you used before with your v10 should be good enough, mine also helped me root my sons 'gpadx 8.0' running 6.0.
Sent from my Moto Z (2) using XDA Labs
Click to expand...
Click to collapse
Glad that no change is needed for my fastboot and ADB since you got it to work with the gpadx . In the post I read he rooted with TWRP a 20l build without referencing a downgrade to 20j, so I am still looking how to downgrade to 20j; what else was the reason to have installed the LGUP and LGbridge files. I will keep looking since you mentioned that step is highly necessary, yet I can't find a post on rooting the 20l and 20j on the forums and for the one I read there lacks a reason for downloading those two files. At least I have gone though steps 1-2 and I'm just trying to decide how to locate a 20j rom and how to do that next step from the forum or should I follow step 3 even though it never references using lgup or lgbridge. I will need to try something soon so wish me luck!
webfrm said:
Glad that no change is needed for my fastboot and ADB since you got it to work with the gpadx . In the post I read he rooted with TWRP a 20l build without referencing a downgrade to 20j, so I am still looking how to downgrade to 20j; what else was the reason to have installed the LGUP and LGbridge files. I will keep looking since you mentioned that step is highly necessary, yet I can't find a post on rooting the 20l and 20j on the forums and for the one I read there lacks a reason for downloading those two files. At least I have gone though steps 1-2 and I'm just trying to decide how to locate a 20j rom and how to do that next step from the forum or should I follow step 3 even though it never references using lgup or lgbridge. I will need to try something soon so wish me luck!
Click to expand...
Click to collapse
I just re-read that guide, and it must be followed and read to a T. Steps 1 and 2 get your computer and phone ready, step 3 (I suggest rooted stock to start with) is the downgade to 20j with twrp process. Once TWRP is installed go here https://forum.xda-developers.com/tmobile-lg-v10/development/rom-v10h901v20estock-customized-t3360240
and install '20l part1' and '20l part2 full sock'. Those 2 files will be flashed in TWRP and bring you back to 20l with twrp, then you can run any root you want. I'm running magisk with that 20l right now and it works great. I haven't inspected the nougat zips yet to see if they compare to these mm zips, there is speculation that if you don't have a true h901 that nougat will brick the phone so I stayed with 20l the last mm update. I don't suggest any custom roms because of lack of development for the second screen among other hardware. Please remember to read everything many times before doing anything.
Sent from my Moto Z (2) using XDA Labs
Related
From what i have figured out with trial and error, if you are rooted and try to take the OTA and receive the 0x1111002 error, you can use the .tot file and flash back to stock and then it will allow you to take the OTA.. I flashed back to stock 3 times using the .kdz file and each time trying to update it would receive the dreaded error. Also you can downgrade back to 10b using the .tot file after taking the latest OTA.
The kdz files do not take you back to stock 'new'. They are kdz files for a version that was never released, so yea the update is going to see the wrong version and fail. Tot for pure stock.
Thanks for the info. Id seen several people tell others that were getting the error to use the kdz file so just thought would pass on a solution for others that had the same issue.
Yea, the difference between the two method seems be missed by many people, I didn't know until a couple of days ago. Someone said something that made me ask specifically.
TonikJDK said:
Yea, the difference between the two method seems be missed by many people, I didn't know until a couple of days ago. Someone said something that made me ask specifically.
Click to expand...
Click to collapse
So what is the difference between the two then?
Sent from my Nexus 7 using Tapatalk
GillRigged said:
So what is the difference between the two then?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Second post in this thread.
A lot of people were having a real hard time using the .tot file to return to v10b from v11c, for a variety of reasons, so Autoprime and AnnoyingDuck made the purchase and distribution of a v10b pre-release .kdz version happen, bless them both. They did not know the kdz they bought was a step pre-release at first, but that did not matter since they never intended the .kdz to provide a path back onto OTA's. The goal was just to get folks back to a rootable stock, from which they could flash things like the v11c modem image, if they wanted to.
Flashing back via the v10b .tot method always was possible, and returns you to OTA-capable stock. Its just that the .kdz is easier for most folks, if all you want is to return to a rootable version.
I am currently on a galaxy s4, just started messing around with android a little. I am interested in switching to a slightly newer phone. Assuming I get a g3 that is on the latest OTA update, is it possible to unlock the bootloader or install any type of custom recovery? I am interested in flashing different roms, which I currently can't do on my verizon OF1 S4. If I can't on this phone, what about a g4? I am really only interested in phones with user replaceable batteries that I can swap out, so my options are somewhat limited. Thanks for any help.
James.
I got a G3 that was on 35B -- which I believe is the latest version. You pretty much have to TOT back to 10B (see the thread regarding flashing back to stock), and then you can root, install TWRP, etc from there. Once you've got that, you can pretty much do what you want.
Personally, I had some fussing about with USB device drivers and so on -- I think it took me more time to get the device properly recognized in windows than any other parts of the process!
You'll notice that there are various different ROMS, some based on stock and some that are AOSP, Cyanogen, etc...
jamesvmccann said:
I am currently on a galaxy s4, just started messing around with android a little. I am interested in switching to a slightly newer phone. Assuming I get a g3 that is on the latest OTA update, is it possible to unlock the bootloader or install any type of custom recovery? I am interested in flashing different roms, which I currently can't do on my verizon OF1 S4. If I can't on this phone, what about a g4? I am really only interested in phones with user replaceable batteries that I can swap out, so my options are somewhat limited. Thanks for any help.
James.
Click to expand...
Click to collapse
Hey, thanks for the quick reply. That is excellent news. Sealed the deal for me, I will be buying this phone sometime this weekend. Not familiar with any of the LG tools, or this TOT method you mentioned, so I will read through the threads carefully. Thanks again.
Sure thing!
back to stock, using TOT is this thread.
To get back to 10B from 35B you'll need the dll file in here
Once I was back at 10B, I used stumproot to get root and then used adb to push a bumped TWRP onto the device.
Other tip: Backup your phone's EFS partition before you do too much, you want to keep a copy of that around just in case...
jamesvmccann said:
Hey, thanks for the quick reply. That is excellent news. Sealed the deal for me, I will be buying this phone sometime this weekend. Not familiar with any of the LG tools, or this TOT method you mentioned, so I will read through the threads carefully. Thanks again.
Click to expand...
Click to collapse
just to clarify what was said,
there is NO way to unlock the bootloader
there is a bypass called Bump, similar to loki, but not. yes, you can do anything you would with a real unlock, but we also have no fastboot, and thats not fixable.
if this is ever effectively patched, and you take the update, flashing roms is over.
just wanted to make sure you understood, there was no true unlock.
I'm getting a new g3 this week. I know the first thing the phone will do when I activate it is to do the OTAs. I want to root my phone. I want to know at which point do I stop the OTAs so I don't get stuck with unroot able version. I know the latest version, 6.0 is not root able. I do want to accidentally go to far.
Thanks
Don't take any OTAs at all if you can help it. It could come with 47A already, some other user's have recently.
Usually you can downgrade to 10B via the TOT method using the .DLL that's extracted from the 35B KDZ (both available from my Android File Host link at the bottom of the first post of @annoyingduck 's stickied return to stock thread in the General section, or in my signature below.
Root is easiest with the Stump app on XDA with its brute force option and that only works on 10B, then use TWRP Manager to install TWRP, and that part is only that easy on 12B and below
@R-T-B has found evidence that if under your battery the model number has a K at the end like VS985WK, then you might not be able to downgrade at all, so no permanent root.
Kingroot works even on 47A but it's highly suspicious and deeply ingrains itself into your system even more than is necessary for root, and with it you have to reroot after every reboot, rooting requires Internet every time, and it might be sharing your private information in the background.
If you do try to downgrade and brick, especially if you have the "K" model number, @R-T-B has a new debrick thread in the General section with modifications to previously available methods to at least get the phone working back on 47A.
This my first lg phone so I'm not a noob when it comes to rooting, I'm unfamiliar with some of lg terms. I've had moto and Samsung in the past.
So when the phone arrives I am going to post the current versions of everything and see if someone can guide me through the bes way to root, get twrp and flash a rom if I had to.
And yes, I have two threads on here. I have a thread to try and figure out out to unbrick a somewhat bricked g3 and this thread to make sure I don't do the same thing to the new phone.
Thanks
simpson1190 said:
So when the phone arrives I am going to post the current versions of everything and see if someone can guide me through the bes way to root, get twrp and flash a rom if I had to.
Click to expand...
Click to collapse
The best way is the same (what I replied previous) no matter what version.
roirraW "edor" ehT said:
The best way is the same (what I replied previous) no matter what version.
Click to expand...
Click to collapse
So if I am on 10b, I can root with stump, flash twrp with twrp manager and I'm good to go? I can flash rooms even if they are based on new versions like MM?
So the only hard thing is if I'm past 10b and/or the device is already on MM.
simpson1190 said:
So if I am on 10b, I can root with stump, flash twrp with twrp manager and I'm good to go? I can flash rooms even if they are based on new versions like MM?
Click to expand...
Click to collapse
Yes to both. Highly unlikely it'll come with 10B, and very likely it'll come with 47A or at least 35B.
roirraW "edor" ehT said:
The best way is the same (what I replied previous) no matter what version.
Click to expand...
Click to collapse
so my new g3 had 35b on it.
i've followed the guide to flash down to 10 b, i get an error in the lg tool that says upgrade stopped due to an error. then it gives instructions on trying again..
simpson1190 said:
so my new g3 had 35b on it.
i've followed the guide to flash down to 10 b, i get an error in the lg tool that says upgrade stopped due to an error. then it gives instructions on trying again..
Click to expand...
Click to collapse
You're using the new .DLL I directed you to? If you downloaded the TOT and .DLL from my Android File Host link, did you use 7-Zip to extract the files out of .7z archives you downloaded? Are you using the original USB cable (hopefully it came with the OEM one)? Installed the latest drivers from LG's website for the VS985 and then rebooted with the phone disconnected from the PC? Connected the phone in Download mode to a USB 2.0 port that comes directly off the motherboard on the PC (not USB 3.x and not through a USB hub)?
You changed the port # of the correct device - the one in the Port section, not the one in the Modem section, right?
Once the TOT flashing software gets to certain point where you think it's just going to "continue" on it's own but it doesn't, did you try unplugging the cable from the phone, wait five seconds, and then plug it back in, and wait up to a minute or more while the software should then start the flash in earnest?
Lastly, sometimes trying a different PC does the trick.
roirraW "edor" ehT said:
You're using the new .DLL I directed you to? If you downloaded the TOT and .DLL from my Android File Host link, did you use 7-Zip to extract the files out of .7z archives you downloaded? Are you using the original USB cable (hopefully it came with the OEM one)? Installed the latest drivers from LG's website for the VS985 and then rebooted with the phone disconnected from the PC? Connected the phone in Download mode to a USB 2.0 port that comes directly off the motherboard on the PC (not USB 3.x and not through a USB hub)?
You changed the port # of the correct device - the one in the Port section, not the one in the Modem section, right?
Once the TOT flashing software gets to certain point where you think it's just going to "continue" on it's own but it doesn't, did you try unplugging the cable from the phone, wait five seconds, and then plug it back in, and wait up to a minute or more while the software should then start the flash in earnest?
Lastly, sometimes trying a different PC does the trick.
Click to expand...
Click to collapse
the post you pointed me to has the KDZ file not the TOT file. It does reference a thread to downgrade via TOT file but that thread doesn't have the download links on it anymore. http://forum.xda-developers.com/verizon-lg-g3/general/restore-verizon-to-stock-t2827878
simpson1190 said:
the post you pointed me to has the KDZ file not the TOT file. It does reference a thread to downgrade via TOT file but that thread doesn't have the download links on it anymore. [/QUOTE]
My Android File Host link...d has all the KDZs, and the TOT and the .DLL.
Click to expand...
Click to collapse
roirraW "edor" ehT said:
My Android File Host link at the bottom of the first post of that thread has all the KDZs, and the TOT and the .DLL.
Click to expand...
Click to collapse
ok i found your files and I"m downloading them now. I have downloaded the flash tool and it wants a username and password. found a work around that involves turning off the internet and resetting the date on the computer. Is this the best way to flash a tot or did i not download the correct tool?
i give up....i get an error when using the tot that it didn't load. i even looked into the LGup tool and it says i have an unknown model. maybe this tool is not for the g3
f it. i'm doing the ota to MM, i like the phone with stock unrooted. so it's not worth this headache. Maybe the problem is I am on windows 10. But it is the only computer I have. If I every have a chance to use a win 7 computer, maybe I will try. With what I read, I should be able to downgrade to 10b from MM using the same methods.
simpson1190 said:
i give up....i get an error when using the tot that it didn't load. i even looked into the LGup tool and it says i have an unknown model. maybe this tool is not for the g3
Click to expand...
Click to collapse
simpson1190 said:
f it. i'm doing the ota to MM, i like the phone with stock unrooted. so it's not worth this headache. Maybe the problem is I am on windows 10. But it is the only computer I have. If I every have a chance to use a win 7 computer, maybe I will try. With what I read, I should be able to downgrade to 10b from MM using the same methods.
Click to expand...
Click to collapse
LGUp doesn't work with the VS985. The second post of the LGUp thread details what to use for Verizon G3s.
Windows 10 works fine. As long as your PCB (printed circuit board) in your particular phone isn't v2 (you'd have to look in @R-T-B 's thread in the General section as far as where to look on the board to find the "2" or "1", etc), then yes the downgrade method is the same from 47A. If you happen to have a newer revision of the VS985 then putting Marshmallow on will keep it from being downgraded any longer. This is a fairly recent development (last week or two) that this has been noticed in such detail.
If it is revision 2 of the PCB, then you won't be able to downgrade from 47A at all.
What you mean with "unrooteable" ?
If we like rooteable devices, why still people stay paying these "unrooteable" devices?
Its time to IMPOSE for CHITTY GOGLE INC to create REAL LINUX ADM ROOTED devices or STOP BUYING THESE DAMN CHITS!
Sent from my XT687 using xda premium
Dethfull said:
What you mean with "unrooteable" ?
If we like rooteable devices, why still people stay paying these "unrooteable" devices?
Its time to IMPOSE for CHITTY GOGLE INC to create REAL LINUX ADM ROOTED devices or STOP BUYING THESE DAMN CHITS!
Sent from my XT687 using xda premium
Click to expand...
Click to collapse
Personally, I love my G3, but I'm with you. I won't buy another LG product until they lose their root/custom firmware unfriendly stance.
The Google in says "Google is your friend"
so, A friendly acceptable device, is being distributable by them?
We have years Forcing, imposing, root on all SIMPLY ALL these "friendly" devices.
How we believe on their phrase?
I only believe, the UNIX AND LINUX GPL ARE BEING PAID FOR THEIR "FRIENDISM".
Sent from my XT687 using xda premium
Dear XDA,
I've rooted my LG-H850 some months ago. After some time i decided to update my phone to a new rom and saw that Nougat finally came out for the LG G5.
Now i'm reading the topic from Fulmics 1.0 and saw the following : '''Just flash in TWRP recovery after performing necessary wipes. Be aware that you have to be on Nougat bootloader, so make sure to have installed official nougat KDZ first.'.
I did some reading around on XDA but is still leaves me with some questions and i hope i can get some information about it.
People are talking about LG Bridge.
I haven't checked this out so far. My phone has TWRP and a custom rom on it.
If it's possible to update my phone, is it safe to do it this way?
Also i've seen people talking about a KDZ file. It has been a while since i rooted my phone and if i remember correctly you needed to use the KDZ to get TWRP on it. Correct me if i'm wrong.
If i install this KDZ file, am i ready to go and flash the Fulmics rom?
And if this is so, where can i find this file?
Sorry for the noobish questions but i reallly want to safely update my phone.
Thank you for reading!
With kind regards,
MarshalSmit
MarshalSmit said:
Dear XDA,
I've rooted my LG5 some months ago. After some time i decided to update my phone to a new rom and saw that Nougat finally came out for the LG G5.
Now i'm reading the topic from Fulmics 1.0 and saw the following : '''Just flash in TWRP recovery after performing necessary wipes. Be aware that you have to be on Nougat bootloader, so make sure to have installed official nougat KDZ first.'.
I did some reading around on XDA but is still leaves me with some questions and i hope i can get some information about it.
People are talking about LG Bridge.
I haven't checked this out so far. My phone has TWRP and a custom rom on it.
If it's possible to update my phone, is it safe to do it this way?
Also i've seen people talking about a KDZ file. It has been a while since i rooted my phone and if i remember correctly you needed to use the KDZ to get TWRP on it. Correct me if i'm wrong.
If i install this KDZ file, am i ready to go and flash the Fulmics rom?
And if this is so, where can i find this file?
Sorry for the noobish questions but i reallly want to safely update my phone.
Thank you for reading!
With kind regards,
MarshalSmit
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=3523999
Try this.
Sent from my LG-H860 using Tapatalk
forbeisgunn said:
https://forum.xda-developers.com/showthread.php?t=3523999
Try this.
Sent from my LG-H860 using Tapatalk
Click to expand...
Click to collapse
Thank you for your reply. I totally forgot to mention i have an LG-H850. Does this works for the H850 as well?
Anyone that can help me ?
I also have H850. I was rooted on MM. All I did was flash N KDZ with LGUP. Then I falshed TWRP (N version). Then I Flashed SuperSU (N version) from TWRP. For now I'm using rooted LG stock (N). I honestly don't see the point of custom ROM for now...it works great, smooth, battery life is good (approx the same as on MM).
I've done everything you have said and the phone worked perfectly with SU and all.
After that i installed Fulmics on it. After i restarted my phone it gave me an message that the phone encription had failed and that i needed to reset the phone. With my stupid head i pressed on this button.
Currently i'm getting instantly booted to TWRP and that's it.
Did i just fully bricked my phone?
// Starting the phone connected to a charger fixed it for some reason .
MarshalSmit said:
I've done everything you have said and the phone worked perfectly with SU and all.
After that i installed Fulmics on it. After i restarted my phone it gave me an message that the phone encription had failed and that i needed to reset the phone. With my stupid head i pressed on this button.
Currently i'm getting instantly booted to TWRP and that's it.
Did i just fully bricked my phone?
// Starting the phone connected to a charger fixed it for some reason .
Click to expand...
Click to collapse
Is your problem totally solved now?
Bulkang U. Antibop said:
Is your problem totally solved now?
Click to expand...
Click to collapse
I believe it is. I'm honestly to scared to flash the rom that i want .
I had the LG V10 with Android 6 rooted and I upgraded it to Nougat by flashing the kdz version 30b with the already installed TWRP. For various reasons, I had to reinstall the stock version of the OS (30b), which removed TWRP from the phone. Now, I want to reinstall TWRP to root it again. Currently, I have the 30c version (updated from 30b with the false hope that the below problem would be fixed) with the bootloader unlocked. However, when I try to flash the TWRP image file (or any recovery images, even the stock recovery image), I always receive the following error:
Code:
fastboot flash recovery twrp-3.0.0-0-h901.img
target reported max download size of 536870912 bytes
sending 'recovery' (31748 KB)...
OKAY [ 1.194s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 1.212s
I tried also to restore the rooted Android 6 KDZ (which did not gave me the above problems) using LGUP but it tells me that there is an "antirollback" problem because the version I want to install is older than the one I have. Then I tried to install the TWRP TOT file with LGUP but it gives me a communication error when it starts upgrading.
I think the solution would be to rollback to Android 6, install TWRP with fastboot working, then flash the rooted Nougat again. However, I cannot find how to rollback to an older Android version without TWRP and I cannot install TWRP with the current Android version. In practice, I am in a loop...
I don't know what else to do. Any help on how can I root my phone now?
@brok85
The simple fastboot commands for installing custom recovery were patched out sometime in the later MM firmwares. Since you lost root on Nougat, there currently is no option to get TWRP since there is no way to downgrade to any version of MM even with a modified LGUP.
If and when such a downgrade is possible you'd probably have to roll-back to 30b first instead of going to straight to MM.
chin'ah.girl said:
@brok85
The simple fastboot commands for installing custom recovery were patched out sometime in the later MM firmwares. Since you lost root on Nougat, there currently is no option to get TWRP since there is no way to downgrade to any version of MM even with a modified LGUP.
If and when such a downgrade is possible you'd probably have to roll-back to 30b first instead of going to straight to MM.
Click to expand...
Click to collapse
I have already rolled back to 30b. Antirollback check passes successfully as long as you want to flash the same Android version, e.g., Android 7...
Wouldn't it be possible to modify the 30b so that we can get those fastboot commands back? that would fix the problem without need to roll back to MM...
Unfortunately we can't modify fastboot commands at the ROM level because we have no way of flashing a modified ROM to the device that would allow the commands to go through. If we were it would be even more simple to flash a pre-rooted ROM through LGUP, but that has already been confirmed not to work as well.
So basically it's either downgrade or exploit a security flaw that allows root on the current ROM, and since no one is currently working on this device (at least to my knowledge) both of those are starting to look less and less likely.
brok85 said:
I have already rolled back to 30b. Antirollback check passes successfully as long as you want to flash the same Android version, e.g., Android 7...
Wouldn't it be possible to modify the 30b so that we can get those fastboot commands back? that would fix the problem without need to roll back to MM...
Click to expand...
Click to collapse
If your on 30b then the dirty cow exploit works, search this forum for it.
Sent from my LG-H901 using XDA Labs
skywalker-live said:
If your on 30b then the dirty cow exploit works, search this forum for it.
Sent from my LG-H901 using XDA Labs
Click to expand...
Click to collapse
Thanks for the suggestion! Would you please link a reference for dirty cow? I found something in the forum but I also read that someone bricked their devices, so it would be better to have the correct procedure.
That information is incorrect, unfortunately. Dirty Cow was patched out in January 2017, the 30b ROM is on May 2017 security patch. I even tried to do it myself and the "adb logcat -s recowvery" command no longer works, hence the reason why we need to downgrade to v20l for the exploit.
chin'ah.girl said:
That information is incorrect, unfortunately. Dirty Cow was patched out in January 2017, the 30b ROM is on May 2017 security patch. I even tried to do it myself and the "adb logcat -s recowvery" command no longer works, hence the reason why we need to downgrade to v20l for the exploit.
Click to expand...
Click to collapse
Except for the fact that 30b increased the anti rollback and we can't go back to 20l.
Sent from my LG-H901 using XDA Labs
@skywalker-live
I'm not entirely certain that's the problem. Any time you flash a ROM with a lower anti-rollback count usually results in a hard brick/9008 mode, not a soft brick. The few times I was able to successfully flash the device that was what happened and the phone was easily recovered from a soft brick with LGUP or LG Bridge. That is unless LG developed away for the bootloader to not be so stringent for easier recovery and less phones needing to be sent back to the factory. Also I believe the G5 was able to downgrade between MM and N.
Either way for us users who intentionally/unintentionally upgraded and lost root we don't have any options at the moment.
@chin'ah.girl. That is the whole point of anti roll back, to prevent going backwards, in this case it closes the last exploit used for rooting. This phone started with full fastboot capability on android 5.1.1. (yay we did everything like normal dev phones) Then with 6.0 LG removed fastboot flashing commands (unlocked bootloader that can't do anything), the dirty cow exploit gave us temp root to install twrp. There were 3 updates for the h901 in 6.0. The first 2 were ARB 0, the 3rd ("security" update) increased ARB to 1. Then 7.0 came and ARB increased to 2, because LG patched dirty cow. In a way ARB is designed to brick your phone if you force it, sure our phones are recoverable but only with the same version you started with. On newer LGs (v20? and newer) it just warns you and won't let you downgrade. I've looked back at all the posts from when 7.0 (30b) was released and anyone on unrooted, untwrped software has been stuck there. The only way to have root/ twrp on 30b is to have flashed a safely created stock rom in twrp. Even the best devs for this phone are stuck on 30b. I'm even looking at different brands unless someone can root the latest LG firmwares ( I would like a v20 but all my local stores only have the latest firmwares in stock).
Sent from my LG-H901 using XDA Labs
Well I guess having a soft brick with anti-rollback is better than having 9008 (I know it's also possible to recover from this mode but much more work is involved). I definitely know that currently no one has made progress because I'm one of the people in those threads. Haha!
So I guess that leaves us with hoping someone finds an exploit in current firmware...or buying a new phone like you suggested.
OOOHHHHH NO.. i just got my v10 today hoping to root and all but it's in 30c already.. and from what i have been reading in this thread... sounds like i'm doomed.. i have never used a phone without root...... unlucky me... my love for v10 got me in trouble........
skywalker-live said:
@chin'ah.girl. That is the whole point of anti roll back, to prevent going backwards, in this case it closes the last exploit used for rooting. This phone started with full fastboot capability on android 5.1.1. (yay we did everything like normal dev phones) Then with 6.0 LG removed fastboot flashing commands (unlocked bootloader that can't do anything), the dirty cow exploit gave us temp root to install twrp. There were 3 updates for the h901 in 6.0. The first 2 were ARB 0, the 3rd ("security" update) increased ARB to 1. Then 7.0 came and ARB increased to 2, because LG patched dirty cow. In a way ARB is designed to brick your phone if you force it, sure our phones are recoverable but only with the same version you started with. On newer LGs (v20? and newer) it just warns you and won't let you downgrade. I've looked back at all the posts from when 7.0 (30b) was released and anyone on unrooted, untwrped software has been stuck there. The only way to have root/ twrp on 30b is to have flashed a safely created stock rom in twrp. Even the best devs for this phone are stuck on 30b. I'm even looking at different brands unless someone can root the latest LG firmwares ( I would like a v20 but all my local stores only have the latest firmwares in stock).
Sent from my LG-H901 using XDA Labs
Click to expand...
Click to collapse
What is the difference between a rooted .kdz and a rooted .img?
We can flash a .kdz with LGUP so we would not need the TWRP in the first place. Why is not possible to build a rooted version of the 30b and generate a .kdz to flash with LGUP?
It is probably a stupid question but I am kind of ignorant in this matter...sorry for any blasphemy I may have involuntarily said above
brok85 said:
What is the difference between a rooted .kdz and a rooted .img?
We can flash a .kdz with LGUP so we would not need the TWRP in the first place. Why is not possible to build a rooted version of the 30b and generate a .kdz to flash with LGUP?
It is probably a stupid question but I am kind of ignorant in this matter...sorry for any blasphemy I may have involuntarily said above
Click to expand...
Click to collapse
Unfortunately those that are working to patch lgup to flash rooted .kdz's are still unsuccessful. But that has been everyone's hope for quite a while. Injecting root into a .kdz changes its signature, and then lgup fails to flash it.
Sent from my LG-H901 using XDA Labs
@chin'ah.girl if @ PlayfulGod is working on this let me know. I helped back in the day getting the lg flex running twrp. Yall might want to look into flashing a modified bootloader from a phone that is equal. Like we used the G2 aboot to bypass lgup errors it and got loki working. But then lg wouldnt not rls the source so we could get a stable kernel. But we did end up having twrp and root. . Check the aboot file. I will see if @djrbliss or maybe @Dees_Troy will jump in here and see what happens. idk how close the aboot is to the v20 or sense there was a working aboot for this phone you might be able to force a older aboot. it might softbrick but then you should be able to use fastboot cmds. hope this helps. Inbox me if you need. If I can find the old aboot file that worked I will play around with it
Gotroot said:
@chin'ah.girl if @ PlayfulGod is working on this let me know. I helped back in the day getting the lg flex running twrp. Yall might want to look into flashing a modified bootloader from a phone that is equal. Like we used the G2 aboot to bypass lgup errors it and got loki working. But then lg wouldnt not rls the source so we could get a stable kernel. But we did end up having twrp and root. . Check the aboot file. I will see if @djrbliss or maybe @Dees_Troy will jump in here and see what happens. idk how close the aboot is to the v20 or sense there was a working aboot for this phone you might be able to force a older aboot. it might softbrick but then you should be able to use fastboot cmds. hope this helps. Inbox me if you need. If I can find the old aboot file that worked I will play around with it
Click to expand...
Click to collapse
As far as I know no one is working on this as it seems most devs have given up and have moved onto the v20, or if they are working on it they haven't said so in the forums that I've seen. With that in mind help from anyone would be greatly appreciated, even if it is a long shot!
The aboot from the v20 might work.. It just need to be edited. I have played around with downgrading. Idk why lg seems to do this with certain models. The flex was a beast of a phone still is. But they wouldnt rls the scource kernel. Lg said they did but it wouldnt compile it was missing all kinds of drivers. Lg has lost all my respect
Any hope on rooting stock Nougat now? My V10 bootlooped and I sent it into LG and of course they flashed stock Nougat recovery so my TWRP is gone.
xxcmb3k3xx said:
Any hope on rooting stock Nougat now? My V10 bootlooped and I sent it into LG and of course they flashed stock Nougat recovery so my TWRP is gone.
Click to expand...
Click to collapse
Welcome to the train bro,..... None for now...
skywalker-live said:
@chin'ah.girl. That is the whole point of anti roll back, to prevent going backwards, in this case it closes the last exploit used for rooting. This phone started with full fastboot capability on android 5.1.1. (yay we did everything like normal dev phones) Then with 6.0 LG removed fastboot flashing commands (unlocked bootloader that can't do anything), the dirty cow exploit gave us temp root to install twrp. There were 3 updates for the h901 in 6.0. The first 2 were ARB 0, the 3rd ("security" update) increased ARB to 1. Then 7.0 came and ARB increased to 2, because LG patched dirty cow. In a way ARB is designed to brick your phone if you force it, sure our phones are recoverable but only with the same version you started with. On newer LGs (v20? and newer) it just warns you and won't let you downgrade. I've looked back at all the posts from when 7.0 (30b) was released and anyone on unrooted, untwrped software has been stuck there. The only way to have root/ twrp on 30b is to have flashed a safely created stock rom in twrp. Even the best devs for this phone are stuck on 30b. I'm even looking at different brands unless someone can root the latest LG firmwares ( I would like a v20 but all my local stores only have the latest firmwares in stock).
Click to expand...
Click to collapse
Among the marshmallows for H901, I have seen 20e, 20j and 20l here. And I have myself seen that 20e is on ARBv1 while 20j and 20l are on ARBv2 just like 30b and 30c. So 30b and 30c must be downgradable to 20j or 20l via LGUP due to having the same ARB version i.e. 2.
You can yourself verify the ARB versions by extracting the KDZ, then DZ and then searching for SW_ID in either ABOOT or SBL1 partition images. They both contain the same string whose 8th-last digit shows the ARB version of that KDZ.
I have tried flashing 20j and 20l on my h901 30b via LGUP. All checks pass as well as many partitions including modem, boot, laf, factory, recovery, aboot etc. are flashed but on 23% while flashing system partition the 0x2000 Invalid Command Response is shown by LGUP. Can anyone please try this downgrade and let me know what they get?
Would it be due to the reason that I am flashing H901BK files over H901?