Related
Hi guys, i recently bought an lg g3 and i would like to install CloudyG3, looking on this forum i saw different methods to root the device, and bootloader unlock. my question is how do i ahve to preceed? root the device and unlock the bootloader and then install cloudyg3 rom or i can simply root device, install a custom kernel like twrp and then flash the custom rom? thanks in advance.
JulianMarku97 said:
Hi guys, i recently bought an lg g3 and i would like to install CloudyG3, looking on this forum i saw different methods to root the device, and bootloader unlock. my question is how do i ahve to preceed? root the device and unlock the bootloader and then install cloudyg3 rom or i can simply root device, install a custom kernel like twrp and then flash the custom rom? thanks in advance.
Click to expand...
Click to collapse
First you should do some reading just to brush up on flashing. TWRP is a recovery, not a kernel. I think there is a how to guide in forumland somewhere. You have to root first using purpledrake, towelroot, uproot, etc. Then you need to get the latest twrp .img for your appropriate model phone. Flashify that. Pick ROM of your choice and voila. Backup your stock just to have it. But seriously I would definitely read up before you break your phone.
Sent from my LG-D850 using XDA Free mobile app
I have a note 4 which I froze at 5.0.1 BOAF version using the debloater utility.
I would like to do the conversion to the DE unlock and flash CM13.
I keep seeing people needing to flash a 5.1.1 kernel in order to avoid bootloops. As I am not on 5.1.1, am I free to do the unlock, flash TWRP and then flash CM13/Gapps?
I really don't want to update to 5.1.1 and would like some input from those with BOAF who have done this. Any issues you had and solutions?
My fear is getting to the point of flashing TWRP and then not being able to flash SU and CM13 because of the TWRP SD card issue.
I am familiar with ADB and have been flashing roms since the DroidX.
Place all the files you need on your internal storage. Then root with Kingroot and unlock the BL. Then go into DL mode and flash recovery. Then you can access you internal SD to flash the Emotion kernel or you will get kernel panic and bootloop. Then flash Super SU 2.67. If you install Xposed you can remedy the TWRP ext SD issue with Wanam Xpose module. I know because I've done been down this road and figured it out today lol. Hope this helps shed a lil light on it for ya.
?If someone helps you, plz thank them?
Sent from my Tab S SM-T700
stajam said:
Place all the files you need on your internal storage. Then root with Kingroot and unlock the BL. Then go into DL mode and flash recovery. Then you can access you internal SD to flash the Emotion kernel or you will get kernel panic and bootloop. Then flash Super SU 2.67. If you install Xposed you can remedy the TWRP ext SD issue with Wanam Xpose module. I know because I've done been down this road and figured it out today lol. Hope this helps shed a lil light on it for ya.
?If someone helps you, plz thank them?
Sent from my Tab S SM-T700
Click to expand...
Click to collapse
So you say to flash a 5.1.1 kernel on a 5.0.1 system? Sounds weird...
Sent from my SM-N910V using Tapatalk
gcodori said:
So you say to flash a 5.1.1 kernel on a 5.0.1 system? Sounds weird...
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Well I understand what you are saying but if you're going to unlock the bootloader anyways and flash a 6.0 ROM what does it really matter. If you're worried about being able to downgrade, there is a safe upgrade method to do that so you can be able to downgrade if you want.
?If someone helps you, plz thank them?
stajam said:
Well I understand what you are saying but if you're going to unlock the bootloader anyways and flash a 6.0 ROM what does it really matter. If you're worried about being able to downgrade, there is a safe upgrade method to do that so you can be able to downgrade if you want.
?If someone helps you, plz thank them?
Click to expand...
Click to collapse
I'm concerned with soft bricking by flashing the wrong version kernel.
And I was asking how to NOT soft brick.
Has anyone done this with 5.0.1 (as the title states) without issue?
Sent from my SM-N910V using Tapatalk
gcodori said:
I'm concerned with soft bricking by flashing the wrong version kernel.
And I was asking how to NOT soft brick.
Has anyone done this with 5.0.1 (as the title states) without issue?
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
If you are on 5.0.1, you can do the DE conversion. You don't need to flash a kernel. Once you're done, you can flash the 5.1.1 through odin, install TWRP, and then flash the kernel and superSU again. Don't use the evolution kernel. Use the one from here: http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
https://www.androidfilehost.com/?fid=24415232478676428
gcodori said:
I'm concerned with soft bricking by flashing the wrong version kernel.
And I was asking how to NOT soft brick.
Has anyone done this with 5.0.1 (as the title states) without issue?
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
No, you do not have to flash a 5.1.1 kernel if you intend to stay on 5.0.1. However, if you decide to flash anything 5.1.1+, AND WANT ROOT, a 5.1.1+ permissive kernel is required to prevent boot loop.
livinxtreme2114 said:
No, you do not have to flash a 5.1.1 kernel if you intend to stay on 5.0.1. However, if you decide to flash anything 5.1.1+, AND WANT ROOT, a 5.1.1+ permissive kernel is required to prevent boot loop.
Click to expand...
Click to collapse
My confusion was that I had thought that roms included a kernel already, and you only needed to flash a kernel if you wanted a custom one other than what is included with the rom. In the past I have flashed roms that had tweaked kernels included, no need to flash a separate kernel.
So it sounds like if I want to go to CM13 I have to unlock, update to 5.1.1 then do all of the other steps listed.
I was just hoping to skip right over 5.1.1 and go right to CM13 with TWRP using the included CM13 kernel. That is what I was asking, if those of us on 5.0.1 could skip over updating to 5.1.1.
Another question...If I unlock the BL and then update to 5.1.1 as sizzle suggested, won't that lock the BL again?
gcodori said:
Another question...If I unlock the BL and then update to 5.1.1 as sizzle suggested, won't that lock the BL again?
Click to expand...
Click to collapse
This. Glad I found this thread, this question has been hauting me..
I did the bootloader unlock exploit recently and saw I was on 5.0.1. I know that if I want to flash to a 5.1.1 rom I need to update to 5.1.1 prior to get the kernel and modem and what not. My only worry about doing so is whether or not it will re-lock my bootloader in the process. I'm not worried about downgrading, just about losing my bootloader unlock and root.
Hello, has passed a lot of time since my last thread. This time, I'm requesting your help about something that every time I read a related thread turns more complicated.
I just want to know if I can flash CyanogenMod 13 or another custom ROM if I have an LG G4 with official Android Marshmallow V20c (not rooted and with locked bootloader, because I don't know if I can take the risk), because I learned how to root and unlock the bootloader, but for example, CM13 needs a V20a stock ROM and when I flashed that version with LGUP I didn't have signal and com.android.process wasn't working.
I hope you can give me a vision, very easy to understand, because the threads are not very explicit.
Thanks and regards!
chrisdlc119 said:
Hello, has passed a lot of time since my last thread. This time, I'm requesting your help about something that every time I read a related thread turns more complicated.
I just want to know if I can flash CyanogenMod 13 or another custom ROM if I have an LG G4 with official Android Marshmallow V20c (not rooted and with locked bootloader, because I don't know if I can take the risk), because I learned how to root and unlock the bootloader, but for example, CM13 needs a V20a stock ROM and when I flashed that version with LGUP I didn't have signal and com.android.process wasn't working.
I hope you can give me a vision, very easy to understand, because the threads are not very explicit.
Thanks and regards!
Click to expand...
Click to collapse
As simple as possible: no!
With MM and locked BL you can't get root and you can't install any custom Rom.
Jens1969 said:
As simple as possible: no!
With MM and locked BL you can't get root and you can't install any custom Rom.
Click to expand...
Click to collapse
You don't understand me. I know how to unlock my bootloader and after that root my phone, but I'm not taking the risk because I flashed the V20A stock ROM to install CM13, but I didn't have cellular signal and because that I didn't try to unlock and root my phone.
Maybe this question is more useful: Can I install CM13 when I have a V20C stock ROM and not the V20A one?
Thanks and regards.
You can flash any custom rom if you have unlocked bootloader and custom recovery e.g. TWRP. Without that things you can't flash anything, because custom roms needs unlocked bootloader.
adamz667 said:
You can flash any custom rom if you have unlocked bootloader and custom recovery e.g. TWRP. Without that things you can't flash anything, because custom roms needs unlocked bootloader.
Click to expand...
Click to collapse
OK, now I understand that I can flash CM13 over V20C and not necessarily over V20A.
Enviado desde mi LG-H815 mediante Tapatalk
You can flash CM13 on any V20... (V10 being LP, V20 MM) as long as you have a MM base you can flash. However, as said above, you MUST unlock bootloader to flash CM, don't try and flash custom ROM without unlocked bootloader. You can unlock bootloader on any version as long as yours is one of the models with the ability.
It may be a stupid question but I found 1 thing, about the bootloader, confusing:
When the M beta was released in the dedicated thread was written that the updating process to M locks the bootloader.
Now that M is released to root it we have to update from L to M and then fastboot boot twrp.img and apparently this command requires an unlocked bootloader (I've read this in a nexus thread).
The question is: if the update locks the bootloader how comes we need to unlock it in L?
What is the difference between a locked phone updated from L to M and a phone unlocked in L and then updated to M? Shouldn't both the phones have a locked bootloader?
TiA
Sent from my ASUS_Z008D
Fastboot FLASH twrp requires an unlocked bootloader (that's installing permanent twrp) fastboot BOOT twrp (tethered twrp) does not.
Sent from my ASUS_Z00A using Tapatalk
I know that, but the command doesn't say flash, it says boot, so it's like (or at least it looks like) the tethered recovery we're using for L. Yet they say to unlock before updating, or downgrade + unlock + upgrade.
Sent from my ASUS_Z008D
Ah, I misread your post. That actually is a good question!
Sent from my ASUS_Z00A using Tapatalk
Yes i also wondered why too(unlocked bootloader in L) but that was in description to have unlocked bootloader in L before flashing beta 6 MM to gain root or the script wouldnt work.
Not too sure if this is the same with new official MM maybe someone can explain more ?
I was about to ask the exact same question. Shakalaca method for rooting (Unlocked L > MM upgrade > root + xposed through tethered TWRP) ends up with a LOCKED bootloader (he say so in OP). This method works for OFFICIAL BETA (4.21.40.61).
Quang Boom's rooting video ends up with MM root and UNLOCKED bootloader.
Do Shakalaca's method works with OFFICIAL FINAL MM (i.e. 4.21.40.134)? Some say yes, others say no. I'm confused.
And a lot of people are saying they succeeded with a locked bl
Sent from my ASUS_Z008D
distant_thunder_89 said:
Quang Boom's rooting video ends up with MM root and UNLOCKED bootloader.
Click to expand...
Click to collapse
Can you post the link for this video? Thanks.
I unlocked the official mm with quang booms files he linked in YouTube, rooting is then possible with his signed twrp...
https://youtu.be/fDls4gLyusY
Guys, after some research I came to the conclusion that is not possible in MM to have both root and a locked BL.
I decided to upgrade nonetheless, if some issue arise which would require RMA we can always downgrade and use the LP relock to get warranty back (the LP relock is in the asus forum).
TheSSJ said:
I unlocked the official mm with quang booms files he linked in YouTube, rooting is then possible with his signed twrp...
Click to expand...
Click to collapse
Well this dude just made a video of himself using shakalaka's method for the beta (unlock android beta by shakalaka, 3d by samcjtsai), I just confronted the hashes for the files you can download from the YouTube page with those for the files from that 3d and they are the same, same method, same files.
But let's not make this a "how to root post", there's plenty of informations on here.
I'm just interested in the bootloader thing, if someone can explain.
Sent from my ASUS_Z008D
I've done a little bit of digging and haven't been able to find much, or at least haven't found a lot of details that are "newer" But my question is simple, Is the n910v version, stock, 6.0.1 able to be just simply rooted?
I don't want a custom rom or anything, all i'm needing is root access to remove bloatware and freeze some apps.
any help, direction, or keywords to search for would be greatly appreciated.
mrkrowely said:
I've done a little bit of digging and haven't been able to find much, or at least haven't found a lot of details that are "newer" But my question is simple, Is the n910v version, stock, 6.0.1 able to be just simply rooted?
I don't want a custom rom or anything, all i'm needing is root access to remove bloatware and freeze some apps.
any help, direction, or keywords to search for would be greatly appreciated.
Click to expand...
Click to collapse
Yes, I used these instructions. Then after I was unlocked with TWRP installed I flashed this with Odin, rooted in TWRP and then debloated. After all this you will be on the newest update rooted and unlocked.
so I have to flash down to 5.1.1, then unlock bootloader, gain root, then flash back to stock, then update back to 6.0.1, and then It'll still be unlocked and rooted?
mrkrowely said:
so I have to flash down to 5.1.1, then unlock bootloader, gain root, then flash back to stock, then update back to 6.0.1, and then It'll still be unlocked and rooted?
Click to expand...
Click to collapse
Pretty much but after you go back to 5.1.1, unlock, TWRP and root you are safe to go to update to 6.0.1 with this file. After you flash that flash TWRP again and install root again. After you unlock you are going to be unlocked unless you install the retail firmware and overwrite your aboot. The file I linked says stock restore but it is safe to flash when you are unlocked because I removed aboot.
I'm going to use the guide you posted to try unlock booyloader as and root. If successful, I can flash cm and gapps or do I need the deblosted romyou posted first? Thanks for your help
Sent from my Moto X using XDA-Developers mobile app
flyers00 said:
I'm going to use the guide you posted to try unlock booyloader as and root. If successful, I can flash cm and gapps or do I need the deblosted romyou posted first? Thanks for your help
Sent from my Moto X using XDA-Developers mobile app
Click to expand...
Click to collapse
Of you are going to install other rom, you don't need to de bloated. Just debloat the one you're going to use as default rom..
I'm having issue with kingroot ,after it attempts to root,the phone reboots a couple times. Then I have to restart the process
Sent from my Moto X using XDA-Developers mobile app
Finally got it to work. Only thing I did different I did was use Kongo root. Thanks for the info
Sent from my SM-N910V using XDA-Developers mobile app