Related
There are quite a few threads that have all the information but for new Z3TC owners, it can be challenging to know where to start and to understand the process.
How I started here is recently purchasing a Rogers Z3TC and to my surprise, the bootloader cannot be unlocked. I shouldn't have been surprised since carriers do tend to lock the bootloaders and if I did my research, I would have found out that Sony offers unlockable and non-unlockable versions of the same hardware. I have never had to worry about having a recovery to root the device or install custom ROMs with root. For anyone new to Android, the recovery is probably the single most important mode to setting up your device the way you want. A prerequisite for that is of course an unlocked bootloader so you can install the recovery of your choice - ClockworkMod (CWM) or TeamWin Recovery Project (TWRP).
So what makes the process confusing for some new Z3TC owners, such as myself, is that the process is somewhat backward. For most of my previous devices, it is:
1. Unlock bootloader
2. Install recovery
3. Gain root through flashing SuperSU or a rooted custom ROM
Because for my Rogers Z3TC cannot be bootloader unlocked, the process now looks like this:
1. Obtain root
2. Install recovery
3. Flash a pre-rooted Lollipop ROM
The only way we can get root on Lollipop is on a pre-rooted ROM because there is no exploit yet to do it directly. The only way we can install a pre-rooted ROM is through a custom recovery. The only way we can get a custom recovery is to be rooted. For unlocked bootloaders, they can get recovery through flashing the img of the recovery. The only way we can obtain root is through an exploit on a Z3 ROM, which thankfully works on the Z3TC due to the similar hardware.
So without quoting all the instructions of each step, I will provide the links and you just have to follow the instructions for each part.
Before you begin, you will need Flashtool and install the drivers for Flashmode and your device. You will not need Fastboot because unfortunately, you wont be doing anything with it on a locked bootloader. You may install it if you want.
If you are on Windows 8.1/10, you will need to to disable driver signature.
1. Obtain root by first flashing SGP621_23.0.1.A.0.167_CE.ftf and the system partition of D6603_23.0.A.2.93_Generic_20GLOBAL.ftf. Then use giefroot to root.
2. Prepare prerooted flashable zip of 23.1.A.0.690 NOBA on your internal storage or external SD.
3. Install XZDualRecovery and now you will have TWRP to install 23.1.A.0.690 NOBA on your SD card.
I would finish off by running SGP621-RICDefeat.zip to get R/W system access.
This is the simple template that I would imagine be the way those of us with locked bootloaders will install custom ROMs, obtain root or upgrade Android.
Thank you @lowtraxx for the root instructions and @[NUT] for the XZDualRecovery.
I am running stock Lollipop now.
If I take above mentioned steps,
do I lose the data with apps and settings I am using now?
ux50jp said:
I am running stock Lollipop now.
If I take above mentioned steps,
do I lose the data with apps and settings I am using now?
Click to expand...
Click to collapse
I have tried downgrading from Lollipop back to step one without wipe in Flashtool but I think the system data are incompatible and caused bootloop.
Once I flashed a fresh SGP621_23.0.1.A.0.167_CE.ftf, I did not bother setting up any apps until I did a fresh install of the pre-rooted Lollipop ROM. If you can back up everything first, that would be best. If you cannot, try Flashtool without wipe and worst case scenario if you bootloop, there is a shut off button beside the SIM card tray and you can still get back into Flashmode.
hellocng said:
I have tried downgrading from Lollipop back to step one without wipe in Flashtool but I think the system data are incompatible and caused bootloop.
Once I flashed a fresh SGP621_23.0.1.A.0.167_CE.ftf, I did not bother setting up any apps until I did a fresh install of the pre-rooted Lollipop ROM. If you can back up everything first, that would be best. If you cannot, try Flashtool without wipe and worst case scenario if you bootloop, there is a shut off button beside the SIM card tray and you can still get back into Flashmode.
Click to expand...
Click to collapse
If someone could do a tutorial video, I think a lot of people along with myself would highly appreciate it. I tried doing root on locked bootloader prior to Lollipop, but it just wasn't happening for me. So I decided to give up and just update it since it was too much of a hassle.
Thanks for the post.
Has anyone else tried this?
I am wondering why the root method previously need to unlock the bootloader to get the 621 firmware back on an rooted.
What has changed for this to work without unlocking the bootloader?
Thanks in advance
hellocng said:
1. Obtain root by first flashing SGP621_23.0.1.A.0.167_CE.ftf and the system partition of D6603_23.0.A.2.93_Generic_20GLOBAL.ftf. Then use giefroot to root.
2. Prepare prerooted flashable zip of 23.1.A.0.690 NOBA on your internal storage or external SD.
3. Install XZDualRecovery and now you will have TWRP to install 23.1.A.0.690 NOBA on your SD card.
I would finish off by running SGP621-RICDefeat.zip to get R/W system access.
This is the simple template that I would imagine be the way those of us with locked bootloaders will install custom ROMs, obtain root or upgrade Android.
Thank you @lowtraxx for the root instructions and @[NUT] for the XZDualRecovery.
Click to expand...
Click to collapse
Will I lose my drm keys by doing this? I want to get root but dont wanna unlock my bootloader
Jiyeon90 said:
Will I lose my drm keys by doing this? I want to get root but dont wanna unlock my bootloader
Click to expand...
Click to collapse
yes if you don't follow this steps
1- flash stock 4.4.4 with flashtool
2-flash the 4.4.4 Z3 system only" with flastool
3-factory reset in settings enable usb debuging etc,etc
4-obtain root with giefroot
5-backup TA partition
6-unlock boot loader
7-install dual recovery
8-flash prerooted 5.0.2 with custom recovery
9- gain get system R/W access with ricdefeat
10-relock boot loader restoring TA
good luck
Jiyeon90 said:
Will I lose my drm keys by doing this? I want to get root but dont wanna unlock my bootloader
Click to expand...
Click to collapse
No, we cannot unlock our bootloader so we will not lose DRM.
Speedy Gonzalez said:
yes if you don't follow this steps
1- flash stock 4.4.4 with flashtool
2-flash the 4.4.4 Z3 system only" with flastool
3-factory reset in settings enable usb debuging etc,etc
4-obtain root with giefroot
5-backup TA partition
6-unlock boot loader
7-install dual recovery
8-flash prerooted 5.0.2 with custom recovery
9- gain get system R/W access with ricdefeat
10-relock boot loader restoring TA
good luck
Click to expand...
Click to collapse
Step 3 and 5 is not necessary because we cant do step 6.
hellocng said:
No, we cannot unlock our bootloader so we will not lose DRM.
Step 3 and 5 is not necessary because we cant do step 6.
Click to expand...
Click to collapse
what do you mean with we can't ? you don't want to ?
Never mind I didn't knew you CAN'T unlock the bootloader at all
1. Obtain root by first flashing SGP621_23.0.1.A.0.167_CE.ftf and the system partition of D6603_23.0.A.2.93_Generic_20GLOBAL.ftf. Then use giefroot to root.
2. Prepare prerooted flashable zip of 23.1.A.0.690 NOBA on your internal storage or external SD.
3. Install XZDualRecovery and now you will have TWRP to install 23.1.A.0.690 NOBA on your SD card.
I would finish off by running SGP621-RICDefeat.zip to get R/W system access.
Click to expand...
Click to collapse
These steps don't unlock bootloader. So DRM stays intact. No need to backup/restore TA!!!
hellocng said:
No, we cannot unlock our bootloader so we will not lose DRM.
Step 3 and 5 is not necessary because we cant do step 6.
Click to expand...
Click to collapse
So I can get root even if I skip step 3, 5, and 6?
Jiyeon90 said:
So I can get root even if I skip step 3, 5, and 6?
Click to expand...
Click to collapse
Yes.
Thank you, its working now, yeah no need to backup TA, unlock bootloader, etc.
It was a bit tricky but not as hard as in the other threads.
I did one mistake, I flashed the SGP621 pre-rooted zip on my SGP611, it wouldnt turn on obviously, so I created a pre-rooted file for the SGP611 and now I'm on lollipop with root and dual recovery
Flashing the ricdefeat file fails everytime though but thats a very minor issue.
Here's the pre-rooted file for the SGP611 users
https://drive.google.com/file/d/0Bz4ANHmLVuVTR2FqWHEzemxORjg/view?usp=sharing
It seems really hard to brick the device too, I ran out of space on my pc while flashing 4.4.4 with flashtool so the processes was aborted at about 50% but I was still able to get into flash mode again.
Jiyeon90 said:
Thank you, its working now, yeah no need to backup TA, unlock bootloader, etc.
It was a bit tricky but not as hard as in the other threads.
I did one mistake, I flashed the SGP621 pre-rooted zip on my SGP611, it wouldnt turn on obviously, so I created a pre-rooted file for the SGP611 and now I'm on lollipop with root and dual recovery
Flashing the ricdefeat file fails everytime though but thats a very minor issue.
Here's the pre-rooted file for the SGP611 users
https://drive.google.com/file/d/0Bz4ANHmLVuVTR2FqWHEzemxORjg/view?usp=sharing
It seems really hard to brick the device too, I ran out of space on my pc while flashing 4.4.4 with flashtool so the processes was aborted at about 50% but I was still able to get into flash mode again.
Click to expand...
Click to collapse
Could that prerooted 611 file work on my lollipop 612? Or would it need 612 specifically to work?
Thanks
GigaSPX said:
Could that prerooted 611 file work on my lollipop 612? Or would it need 612 specifically to work?
Thanks
Click to expand...
Click to collapse
I'm not sure, you could give it a try.
Or just make a pre-rooted file yourself, it's quite easy, just remember to use the right lollipop .FTF file for your 612 device.
Jiyeon90 said:
I'm not sure, you could give it a try.
Or just make a pre-rooted file yourself, it's quite easy, just remember to use the right lollipop .FTF file for your 612 device.
Click to expand...
Click to collapse
Just follow the same instructions from the first post?
GigaSPX said:
Just follow the same instructions from the first post?
Click to expand...
Click to collapse
Yes, what I did was.
Downgrade to 4.4.4 using flashtool, if you are on 611 or 612 dont use the ftf file in the first post as your device wont turn on, use the correct ftf file for your device.
Flash z3 compact system using flashtool (dont wipe anything and exclude everything but system, you will end up with with the z3 system and you will get error messages when you turn it on, thats fine)
Root using giefrrot (it took me 3 tries to get it rooted)
Install double recovery.
Put the pre-rooted file in your phone memory or sd card.
Flash the pre-rooted lollipop file and reboot, thats all.
But as you have the 612 device I would recommend you to make your own pre-rooted file, just follow these instructions
http://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904
Jiyeon90 said:
Flashing the ricdefeat file fails everytime though but thats a very minor issue.
It seems really hard to brick the device too, I ran out of space on my pc while flashing 4.4.4 with flashtool so the processes was aborted at about 50% but I was still able to get into flash mode again.
Click to expand...
Click to collapse
The RICDefeat is quite important if you want to remove bloatware or alter the system in anyway, which is one of my prime reasons for rooting. What was the error or message?
Flash mode is intact as long as the bootloader is locked as we cannot modify any of the kernel or boot partitions.
Jiyeon90 said:
Yes, what I did was.
Downgrade to 4.4.4 using flashtool, if you are on 611 or 612 dont use the ftf file in the first post as your device wont turn on, use the correct ftf file for your device.
Flash z3 compact system using flashtool (dont wipe anything and exclude everything but system, you will end up with with the z3 system and you will get error messages when you turn it on, thats fine)
Root using giefrrot (it took me 3 tries to get it rooted)
Install double recovery.
Put the pre-rooted file in your phone memory or sd card.
Flash the pre-rooted lollipop file and reboot, thats all.
But as you have the 612 device I would recommend you to make your own pre-rooted file, just follow these instructions
http://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904
Click to expand...
Click to collapse
I want to personally thank you for the instructions. I'm now running perfectly as is prerooted Lollipop SGP612. It took me several tries too with the rooting with giefroot because each time I run it, I can't get it connected to USB anymore, which I had to constantly restart to get.
hellocng said:
The RICDefeat is quite important if you want to remove bloatware or alter the system in anyway, which is one of my prime reasons for rooting. What was the error or message?
Flash mode is intact as long as the bootloader is locked as we cannot modify any of the kernel or boot partitions.
Click to expand...
Click to collapse
I don't remember what error message I got, all I remember is seeing the word 'aborted' with the green Android guy laying down.
I have removed several apps that came pre-installed using titanium backup, I also installed the SD card fix so I can use the SD card freely. I haven't had a single issue so far.
---------- Post added at 12:03 AM ---------- Previous post was at 12:03 AM ----------
GigaSPX said:
I want to personally thank you for the instructions. I'm now running perfectly as is prerooted Lollipop SGP612. It took me several tries too with the rooting with giefroot because each time I run it, I can't get it connected to USB anymore, which I had to constantly restart to get.
Click to expand...
Click to collapse
No problem, glad I could help [emoji2]
Hi!
I recently updated my LG G4 from V20A (I think) to V20G. My bootloader is unlocked and I had TWRP/root prior. Now, my TWRP and root seem to be gone. I've tried a number of things, but nothing seems to work. All root solutions seem to involve a pre-rooted kernel V20A. I presume I need V20G to match the software version - is that correct?
Where do I start?
Thank you! :good:
Lisali said:
Hi!
I recently updated my LG G4 from V20A (I think) to V20G. My bootloader is unlocked and I had TWRP/root prior. Now, my TWRP and root seem to be gone. I've tried a number of things, but nothing seems to work. All root solutions seem to involve a pre-rooted kernel V20A. I presume I need V20G to match the software version - is that correct?
Where do I start?
Thank you! :good:
Click to expand...
Click to collapse
Which version of TWRP and SuperSU have you used?
I assume you updated to V20G with LGUp or some other tool by flashing a KDZ. You cannot root any MarshMallow version, you must downgrade to a Lollipop version and root it.
tmihai20 said:
I assume you updated to V20G with LGUp or some other tool by flashing a KDZ. You cannot root any MarshMallow version, you must downgrade to a Lollipop version and root it.
Click to expand...
Click to collapse
You're wrong. In MarshMallow, if you have bootloader unlock, you can flash a Custom Recovery and then, from this recovery install SuperSU. But you must use some lastest version of SuperSU (it can autopatch BOOT before install).
lept_2014 said:
You're wrong. In MarshMallow, if you have bootloader unlock, you can flash a Custom Recovery and then, from this recovery install SuperSU. But you must use some lastest version of SuperSU (it can autopatch BOOT before install).
Click to expand...
Click to collapse
My bad then. I do not know why everybody kept saying that you cannot root a Marshmallow stock Rom. I guess they were talking about all G4s. It makes sense that unlocking the bootloader could allow writing a custom recovery.
Sent from my LG-H815 using Tapatalk
lept_2014 said:
Which version of TWRP and SuperSU have you used?
Click to expand...
Click to collapse
I used the latest versions I could find of both. Should I not have done that?
lept_2014 said:
You're wrong. In MarshMallow, if you have bootloader unlock, you can flash a Custom Recovery and then, from this recovery install SuperSU. But you must use some lastest version of SuperSU (it can autopatch BOOT before install).
Click to expand...
Click to collapse
Yes, that's what I understand as well - but there's so much conflicting information out there, and not a clear step-by-step guide on what to do. My bootloader is unlocked. How do I proceed? It seems that flashing TWRP only works by first loading it from fastboot and then flashing it - but I'm not sure. I'd really appreciate some guidance. Thank you! :good:
Lisali said:
I used the latest versions I could find of both. Should I not have done that?
Yes, that's what I understand as well - but there's so much conflicting information out there, and not a clear step-by-step guide on what to do. My bootloader is unlocked. How do I proceed? It seems that flashing TWRP only works by first loading it from fastboot and then flashing it - but I'm not sure. I'd really appreciate some guidance. Thank you! :good:
Click to expand...
Click to collapse
I've a LG G4 (H815), but I use TWRP Recovery for LG G4 T-Mobile USA (H811) because for some reason, the first don't let me boot with it. Anyway, with the smartphone ON:
Connect it to Computer
Copy to internal memory a SuperSU
Reboot in bootloader/fastboot mode:
Code:
adb reboot bootloader
Boot with TWRP Recovery:
Code:
fastboot boot twrp-3.0.2-0-h811.img
From TWRP Recovery, accept to allow it make changes, and 'install' the SuperSU
Reboot smatphone normally, and that is all.
Lisali said:
Hi!
I recently updated my LG G4 from V20A (I think) to V20G. My bootloader is unlocked and I had TWRP/root prior. Now, my TWRP and root seem to be gone. I've tried a number of things, but nothing seems to work. All root solutions seem to involve a pre-rooted kernel V20A. I presume I need V20G to match the software version - is that correct?
Where do I start?
Thank you! :good:
Click to expand...
Click to collapse
http://www.androidrootguide.com/2015/06/how-to-install-twrp-recovery-and-root-lg-g4-h815.html
I used this guide with latest twrp
lept_2014 said:
I've a LG G4 (H815), but I use TWRP Recovery for LG G4 T-Mobile USA (H811) because for some reason, the first don't let me boot with it. Anyway, with the smartphone ON:
Connect it to Computer
Copy to internal memory a SuperSU
Reboot in bootloader/fastboot mode:
Code:
adb reboot bootloader
Boot with TWRP Recovery:
Code:
fastboot boot twrp-3.0.2-0-h811.img
From TWRP Recovery, accept to allow it make changes, and 'install' the SuperSU
Reboot smatphone normally, and that is all.
Click to expand...
Click to collapse
YES! This worked and was so easy. Thank you, THANK YOU! You're a genius! This should be a sticky. It's so much easier than so many other guides out there. Also - weird that one has to use a different version of TWRP for it to work.
A big thank you once again! :good::good::good::good::good:
Did the update (...or root) wipe the device or does it do an in-place upgrade? Also, did you do the V20G upgrade from the notification that came up on the phone? Thanks for your help
Latz said:
Did the update (...or root) wipe the device or does it do an in-place upgrade? Also, did you do the V20G upgrade from the notification that came up on the phone? Thanks for your help
Click to expand...
Click to collapse
Hi!
If you're rooted, the OTA update does not work and won't install. I'm not sure if it works via LG Bridge - I think it won't wipe anything. My device was wiped because of incorrect TWRP installation. Good luck!
Lisali said:
Hi!
If you're rooted, the OTA update does not work and won't install. I'm not sure if it works via LG Bridge - I think it won't wipe anything. My device was wiped because of incorrect TWRP installation. Good luck!
Click to expand...
Click to collapse
Cheers Thanks for the reply
Lisali said:
YES! This worked and was so easy. Thank you, THANK YOU! You're a genius! This should be a sticky. It's so much easier than so many other guides out there. Also - weird that one has to use a different version of TWRP for it to work.
A big thank you once again! :good::good::good::good::good:
Click to expand...
Click to collapse
Hi ! So have you used the twrp for h815 or the twrp for h811 ?
shinmegami said:
Hi ! So have you used the twrp for h815 or the twrp for h811 ?
Click to expand...
Click to collapse
He should have used H815 one... Using H811 on H815 can make you a lot of problems like system partition might be on bootloader or so, so it's risky to do anything in recovery not designed for your specific model
Wysłane z mojego LG-H815 przy użyciu Tapatalka
Minto107 said:
He should have used H815 one... Using H811 on H815 can make you a lot of problems like system partition might be on bootloader or so, so it's risky to do anything in recovery not designed for your specific model
Wysłane z mojego LG-H815 przy użyciu Tapatalka
Click to expand...
Click to collapse
Ok thank you.
Have a nice day.
I have a H815P version, so what is the best way to root? I'm in Marshmallow.
Enviado desde mi LG-H815 mediante Tapatalk
Hello all!
I'm having problems with Windows 10 and all the programs to deal with my P880... Yesterday I tried
to unlock the bootloader on my new G4 H515 but didn't worked.
The original software was verizon (at least it looked like), I downgraded to lollipop (V10b and V10d, both euro open) but, using the LG official method to unlock the bootloader didn't worked.
In adb the first command didn't do nothing, the second one reboot the phone but only shows a guide and how to reboot the phone, when I tried to go for the third one nothing happens.
The device is detected only for a few seconds, even by the original LGMobile Support Tool, after force the detection by disconnecting and connecting the cable the phone reboot in software upgrade
and its not detected anymore...
Anyone have the same problems and/or any solution?
Install Win7 is not an option, processor is not supported by Win7.
Thank you
RuedasLocas said:
Hello all!
I'm having problems with Windows 10 and all the programs to deal with my P880... Yesterday I tried
to unlock the bootloader on my new G4 H515 but didn't worked.
The original software was verizon (at least it looked like), I downgraded to lollipop (V10b and V10d, both euro open) but, using the LG official method to unlock the bootloader didn't worked.
In adb the first command didn't do nothing, the second one reboot the phone but only shows a guide and how to reboot the phone, when I tried to go for the third one nothing happens.
The device is detected only for a few seconds, even by the original LGMobile Support Tool, after force the detection by disconnecting and connecting the cable the phone reboot in software upgrade
and its not detected anymore...
Anyone have the same problems and/or any solution?
Install Win7 is not an option, processor is not supported by Win7.
Thank you
Click to expand...
Click to collapse
Solved!
Everytime we need to reboot the bootloader (or give another command in cmd) we need to uninstal the standard "kedacom usb device" driver and install manually the LG adb drivers.
BTW, was UNLOCKED running V20G-EUR-XX
I have an LG G4 815 which never rooted and I am not sure about bootloader (probably locked). I am on latest MM v20g. Is there anyway to root my phone so I can install apps require root? Without of course wiping my data?
dinko1 said:
I have an LG G4 815 which never rooted and I am not sure about bootloader (probably locked). I am on latest MM v20g. Is there anyway to root my phone so I can install apps require root? Without of course wiping my data?
Click to expand...
Click to collapse
Do you have an unlocked bootloader?
When you reboot do you see any white writing on the top left hand corner of the screen?
As usual, I am not responsible for any damages done to your device after trying this little guide.
1.-You need to unlock your bootloader first, which means this doesn't work on the Verizon variant. You also need to be sure you have your system image available in case something goes wrong.
2.-Then flash the chinese TWRP found here. Thanks to @hjk23 for providing the link.
3.- Flash SuperSU-v2.78-SYSTEMMODE.zip from here.
4.-BOOM, you're rooted. You need to have in mind that this is using the System mode and it works without modifying the boot.img. This means you will NOT be able to flash OTAs the usual way. I haven't tried using Flashfire since I have not received any OTAs so far.
If this didn't work you can also try flashing this modified boot.img, it has only been tested with the Mexican AT&T variant, so I don't know if it will work properly with other variants.
Thanks!
I would try this if I was certain Flashfire would work...(don't want to reflash for an OTA)
diegochiva95 said:
where? I want to see him
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-z-play/help/unlocked-bootloader-t3459976/page4
Post number 34
I take it back, sadly it is stuck at boot for me I tried it yes. No other SuperSu? I think I had the 03 version and you have 02... I think?
EDIT: not true, I had 02 too, but it just wouldn't work.
EDIT: It forced somewhat of a factory reset on me when I tried the same SuperSU but no systemless, I didn't lose any media but I had to relog in my account and download and update all apps again.
I will just wait for nougat...
several people commented that password is required to enter the recovery......
Enviado desde mi XT1635-02 mediante Tapatalk
diegochiva95 said:
several people commented that password is required to enter the recovery......
Enviado desde mi XT1635-02 mediante Tapatalk
Click to expand...
Click to collapse
The same password that you used to encrypt the phone while setting it up. If you're using a pattern you can use the numbers equivalent to the pattern you used.
FreedFromDeath said:
As usual, I am not responsible for any damages done to your device after trying this little guide.
1.-You need to unlock your bootloader first, which means this doesn't work on the Verizon variant. You also need to be sure you have your system image available in case something goes wrong.
2.-Then flash the chinese TWRP found here. Thanks to @hjk23 for providing the link.
3.- Flash SuperSU-v2.78-SYSTEMMODE.zip from here.
4.-BOOM, you're rooted. You need to have in mind that this is using the System mode and it works without modifying the boot.img. This means you will NOT be able to flash OTAs the usual way. I haven't tried using Flashfire since I have not received any OTAs so far.
Click to expand...
Click to collapse
Thanks for the tutorial. But was inquisitive to know why one cannot use systemless root on our Vertex??
Thanks!
great
just pick up my phone
btw 7 is not released yet right
hmnk said:
Thanks for the tutorial. But was inquisitive to know why one cannot use systemless root on our Vertex??
Thanks!
Click to expand...
Click to collapse
This isn't the Vertex though, this is the Addison.
FreedFromDeath said:
This isn't the Vertex though, this is the Addison.
Click to expand...
Click to collapse
http://www.gsmarena.com/moto_z_play...r_testing_55inch_screen_in_tow-news-19195.php
Anyways, coming back to the topic, why can't we use systemless root on our device?
Thanks,
Regards.
FreedFromDeath said:
As usual, I am not responsible for any damages done to your device after trying this little guide.
1.-You need to unlock your bootloader first, which means this doesn't work on the Verizon variant. You also need to be sure you have your system image available in case something goes wrong.
2.-Then flash the chinese TWRP found here. Thanks to @hjk23 for providing the link.
3.- Flash SuperSU-v2.78-SYSTEMMODE.zip from here.
4.-BOOM, you're rooted. You need to have in mind that this is using the System mode and it works without modifying the boot.img. This means you will NOT be able to flash OTAs the usual way. I haven't tried using Flashfire since I have not received any OTAs so far.
Click to expand...
Click to collapse
says it is not necessary to flash the .zip SuperSU only accept the root for the TWRP own. It is true?
diegochiva95 said:
says it is not necessary to flash the .zip SuperSU only accept the root for the TWRP own. It is true?
Click to expand...
Click to collapse
Isn't there a warning to never accept the root from the recovery?
Another thing, if deencryption doesn't work you can sideload the SuperSU zip using adb through TWRP.
Updated OP with a possible workaround.
FreedFromDeath said:
Updated OP with a possible workaround.
Click to expand...
Click to collapse
If you dont mind, could you provide the details of your device?
So I see there is a Chinese twrp for moto z play but is anyone working on a north American version? Same question for SuperSU? Will there be official versions with systemless root? I guess what I'm asking is should I wait a bit or go this route? I like otas. I also reeeeally like a rooted phone (exchange server BS needs to be bypassed for piece of mind).
Not enitrely sure what happened, but my phone wouldnt boot after flashing SuperSU, even after i restored stock system,boot, and EFS. The boot.img got me booting again though and now rooted. (US variant)
Edit: Can someone upload a stock boot.img for the US variant? I think my backup boot.img might be corrupt, as it causes my phone not to boot.
jon7701 said:
Not enitrely sure what happened, but my phone wouldnt boot after flashing SuperSU, even after i restored stock system,boot, and EFS. The boot.img got me booting again though and now rooted. (US variant)
Edit: Can someone upload a stock boot.img for the US variant? I think my backup boot.img might be corrupt, as it causes my phone not to boot.
Click to expand...
Click to collapse
My phone got frozen at boot, dual sim in the EU version.
I tried to flash the non-systemless SuperSU and that made it factory reset, still not rooted.
I will wait....
hmnk said:
Anyways, coming back to the topic, why can't we use systemless root on our device?
Thanks,
Regards.
Click to expand...
Click to collapse
Anyone??
Thanks
hmnk said:
Anyone??
Thanks
Click to expand...
Click to collapse
I tried to do systemless and it was unable to patch the boot image.
Also if someone could upload a US variant boot.img that would be very appreciated. On the mexican boot.img I cant get data or recieve calls. I can only make outgoing calls for some reason.
Yesterday i've unlocked the bootloader and try AOSP.
Then i go back to stock rom and relocked the bootloader.
Now camera app always say, another application uses the camera and won't start.
alternative camera apps also don't work.
don't backup any drm keys.
is there any chance to get it working?
[-silver-] said:
is there any chance to get it working?
Click to expand...
Click to collapse
You'll need to flash a stock rom and wipe everything in the process.
I had the same problem and flashing using the flashtool with all wipe options checked didn't fix the problem. Any other ideas?
mistarose said:
I had the same problem and flashing using the flashtool with all wipe options checked didn't fix the problem. Any other ideas?
Click to expand...
Click to collapse
I would assume that relocking it without the DRM keys has broken it. To rewrite the TA backup img to the phone you have to use flashtool version 922.3 If I was in your position with or without a drm backup I would try using that version of the flashtool to flash a FW and try the relock procedure again to see if it makes a difference. Have you unlocked it again to see if it brings the camera back?
XperienceD said:
I would assume that relocking it without the DRM keys has broken it. To rewrite the TA backup img to the phone you have to use flashtool version 922.3 If I was in your position with or without a drm backup I would try using that version of the flashtool to flash a FW and try the relock procedure again to see if it makes a difference. Have you unlocked it again to see if it brings the camera back?
Click to expand...
Click to collapse
Ok I unlocked the device again using Sony Mobile Flasher. I'm now flashing an Android 6 ftf file from the UK. I have the TA backup img but am not sure how to restore it. Apparently the Backup TA version 1 had a restore option in the CMD menu. But all the 2nd version does is backup a TA partition key from what I can tell.
Any help restoring the key would be greatly appreciated.
Edit: Ok now I've booted up without locking the boot loader and the camera is working. So now I should be able to lock the bootloader and have it stay working right? But how do I do that?
mistarose said:
So now I should be able to lock the bootloader and have it stay working right? But how do I do that?
Click to expand...
Click to collapse
Lets see. Download Flashtool version 9.22.3 and download Rootkernel, use RK to create a DK.ftf from your TA.img then flash that using the 9.22.3 version of the flashtool. To create a DK.ftf open a cmd window in the Rootkernel folder and enter flash_dk TA.img DK.ftf.
Thank you for the help.
I was using a higher version of the Flashtool so I found the 9.22.3 version and got that installed. I found the Rootkernel and used it to create a DK.ftf successfully from my TA.img.
I flashed that successfully and rebooted the phone but it didn't work. This also didn't automatically relock the device like I read it should of.
I then started over by flashing the Android 6.0 ftf file again. Then I used the flashtool to relock the device. Finally, I flashed the DK.ftf file one more time.
I just booted up the phone and now the camera isn't working with the same error I had before. I also checked the security menu of the phone and it still says the DRM files are not there.
I'm really not sure why it's not working.
EDIT: See below.
mistarose said:
I then started over by flashing the Android 6.0 ftf file again. Then I used the flashtool to relock the device. Finally, I flashed the DK.ftf file one more time.
Click to expand...
Click to collapse
Lets try one last thing. From reading the threads here apparently flashing the DK.ftf is only for those with an unlocked BL wanting to keep DRM functions so places the TA in a location that DRM-fix kernels can pickup. To rewrite the original partition you have to do the following...
shoey63 said:
CONFIRMATION OF TA RESTORE!
- Unlocked bootloader
- Flashed TWRP
- Pushed TAbackup.img (I renamed it) to /data/local/tmp
- Did
Code:
adb shell dd if=/data/local/tmp/TAbackup.img of=/dev/block/bootdevice/by-name/TA
- Rebooted
- Everything back as it was. Original TA restored and DRM keys all active:victory:
shoey63 said:
Then flash a stock ftf.
Click to expand...
Click to collapse
NOTE/EDIT: Due to dm-verity, you cannot restore TA on a rooted phone (Z3+ onwards). It won't boot up. Boot and system have to be pure untouched stock.
Click to expand...
Click to collapse
...if this way fails then it's time to talk to Sony or just run an unlocked BL permanently.
Flashing DK.ftf isn't enough. You need to make a boot.img with DRM fix as well using rootkernel.
shoey63 said:
Flashing DK.ftf isn't enough. You need to make a boot.img with DRM fix as well using rootkernel.
Click to expand...
Click to collapse
They're trying to relock but the camera stops working when they do so just trying any method at this point.
While using the v29a ROM, @kessaras said it should be possible to lock the bootloader using "fastboot oem lock", which didn't work for me on any ROM. I decided to give it a try anyways and it actually worked! It wiped my data, and after restoring and all that I rebooted the phone to see if it was actually locked. "fastboot getvar unlocked" gave me a result of "no". Try it out, but beware, your data will be lost. Proof video: https://youtu.be/Tr6E9LaGWRs Before doing this make sure EVERYTHING is stock! This includes custom recoveries. I do not claim any responsibility if anything goes wrong!
Steps (assuming you already have v29 rom installed):
1. Download ADB and fastboot, along with LG drivers (if you don't have them). Connect your phone and start CMD. CD to the folder where your adb and fastboot files are. (pretty obvious isn't it? )
2. Type "adb reboot bootloader".
3. Type "fastboot oem lock". This WILL wipe your data, and I'm NOT responsible for it!
4. Enjoy your locked phone.
Interesting to say the least, is there any drm locked content that you now can use? (not sure if g4 has any)
Tbh you can relock even without loosing data (at least on LL and MM).
Just reflash the misc partition from either a previous backup (recommended) or from a extracted stock kdz partition will do so.
You should backup misc and the persistent partition before doing so just for the case.
Never written it down because I thought its something no one would like to do but that's verified to work...
.
Sent from my LG-H815 using XDA Labs
OsiBasi said:
Interesting to say the least, is there any drm locked content that you now can use? (not sure if g4 has any)
Click to expand...
Click to collapse
I didn't use any drm content while it was unlocked, so I can't tell. Sorry
steadfasterX said:
Tbh you can relock even without loosing data (at least on LL and MM).
Just reflash the misc partition from either a previous backup (recommended) or from a extracted stock kdz partition will do so.
You should backup misc and the persistent partition before doing so just for the case.
Never written it down because I thought its something no one would like to do but that's verified to work...
.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Yes, it's totally possible but this method doesn't need any backups. I understand it might be hard to believe it worked, even for me it was hard to believe having tried this method on previous ROMs to no avail
alex2000robert said:
Yes, it's totally possible but this method doesn't need any backups. I understand it might be hard to believe it worked, even for me it was hard to believe having tried this method on previous ROMs to no avail
Click to expand...
Click to collapse
yes using fastboot command is new (for OUR device) coming with that modified N release.
btw my described method does not necessarily need a backup. you can do even without..
.
steadfasterX said:
yes using fastboot command is new (for OUR device) coming with that modified N release.
btw my described method does not necessarily need a backup. you can do even without..
.
Click to expand...
Click to collapse
Didn't see you mention flashing misc partition. But if I don't remember wrong it gets flashed everytime we install a KDZ with LGUP anyways this method should be somewhat safer as it doesn't involve flashing anything.
alex2000robert said:
Didn't see you mention flashing misc partition. But if I don't remember wrong it gets flashed everytime we install a KDZ with LGUP anyways this method should be somewhat safer as it doesn't involve flashing anything.
Click to expand...
Click to collapse
no - not every partition u see in a KDZ will be flashed.
Especially when you have an unlocked bootloader.
well the fastboot command will erase all data. flashing misc not nvm i don't care about which is better just wanted to add that there is a method which works on LL and MM (fastboot command will not work there).
btw you should consider to add a [N only] or similar in the thread title
.
steadfasterX said:
no - not every partition u see in a KDZ will be flashed.
Especially when you have an unlocked bootloader.
well the fastboot command will erase all data. flashing misc not nvm i don't care about which is better just wanted to add that there is a method which works on LL and MM (fastboot command will not work there).
.
Click to expand...
Click to collapse
I don't care either, now the good thing is that we suddenly got from 1 method involving backups to 3 methods of which 2 don't involve backups. Hurray :highfive:
I just included [V29a only], just in case. Maybe on V30a/b/c from Korea this won't work.
alex2000robert said:
I don't care either, now the good thing is that we suddenly got from 1 method involving backups to 3 methods of which 2 don't involve backups. Hurray :highfive:
I just included [V29a only], just in case. Maybe on V30a/b/c from Korea this won't work.
Click to expand...
Click to collapse
lol yes true so true :highfive: :victory:
title is perfect now
"Your device is corrupt. It cannot be trusted and may not work properly". Using that resulted on this.. Can't even access recovery
---------- Post added at 02:05 PM ---------- Previous post was at 01:54 PM ----------
Also cant access download mode. So i think this **** ruined my phone lol
pedrogcsb said:
"Your device is corrupt. It cannot be trusted and may not work properly". Using that resulted on this.. Can't even access recovery
Click to expand...
Click to collapse
Go to my Q&A, Help & Troubleshooting thread ---> https://forum.xda-developers.com/g4/help/help-imei-0-t3660318/page2
All the info you need is there. Your IMEI probably got corrupted.
Edit: Oh I just saw your added post about not being able to boot into the Download mode, I can't help you at the moment. Haven't figured out why some devices refuse to boot into the Download mode...
Mr.FREE_Bird said:
Go to my Q&A, Help & Troubleshooting thread ---> https://forum.xda-developers.com/g4/help/help-imei-0-t3660318/page2
All the info you need is there. Your IMEI probably got corrupted.
Click to expand...
Click to collapse
What do you mean? I can't even turn on my phone, or acces TWRP or Download mode. Nothing is working
alex2000robert said:
While using the v29a ROM, @kessaras said it should be possible to lock the bootloader using "fastboot oem lock", which didn't work for me on any ROM. I decided to give it a try anyways and it actually worked! It wiped my data, and after restoring and all that I rebooted the phone to see if it was actually locked. "fastboot getvar unlocked" gave me a result of "no". Try it out, but beware, your data will be lost. Proof video: https://youtu.be/Tr6E9LaGWRs
Steps (assuming you already have v29 rom installed):
1. Download ADB and fastboot, along with LG drivers (if you don't have them). Connect your phone and start CMD. CD to the folder where your adb and fastboot files are. (pretty obvious isn't it? )
2. Type "adb reboot bootloader".
3. Type "fastboot oem lock". This WILL wipe your data, and I'm NOT responsible for it!
4. Enjoy your locked phone.
Click to expand...
Click to collapse
you should add a big warning that re-locking the bootloader will lock the bootloader
yea I know.. just make it clear that this means:
BEFORE you do so you have to ensure that everything is completely STOCK! Even no TWRP flashed etc.
.
steadfasterX said:
you should add a big warning that re-locking the bootloader will lock the bootloader
yea I know.. just make it clear that this means:
BEFORE you do so you have to ensure that everything is completely STOCK! Even no TWRP flashed etc.
.
Click to expand...
Click to collapse
Thanks, just added that.
pedrogcsb said:
"Your device is corrupt. It cannot be trusted and may not work properly". Using that resulted on this.. Can't even access recovery
---------- Post added at 02:05 PM ---------- Previous post was at 01:54 PM ----------
Also cant access download mode. So i think this **** ruined my phone lol
Click to expand...
Click to collapse
Sorry, don't know how to help you here. I read about this error snd supposedly after 10 seconds this message should go away by its own... Try to boot it and wait a little. Then unlock back the bootloader with the unlock.bin and flash the stock recovery from the ZIP file of V29a (which should've flashed by itself, did you remove it?) and only then lock the bootloader. Make sure everything is stock.
pedrogcsb said:
What do you mean? I can't even turn on my phone, or acces TWRP or Download mode. Nothing is working
Click to expand...
Click to collapse
Well, I guess you hard bricked your phone. You had modified firmware(TWRP, kernel) and relocked. Not even surprised you're phone is bricked. Only shot would be send it to LG but they will 99% know you messed with firmware
Wysłane z mojego LG-H815 przy użyciu Tapatalka
Hello,
Is it still possible to unlock the boot loader of an LG G4? Their site is not working.
Minto107 said:
Well, I guess you hard bricked your phone. You had modified firmware(TWRP, kernel) and relocked. Not even surprised you're phone is bricked. Only shot would be send it to LG but they will 99% know you messed with firmware
Wysłane z mojego LG-H815 przy użyciu Tapatalka
Click to expand...
Click to collapse
https://forum.xda-developers.com/g4/development/unbrick-lg-g4-h815-9008-qualcomm-t3452853 I think I will try this next in the morning
Did anyone try unlocking the bootloader as well?
Sent from my iPhone using Tapatalk