Database Info

Root? Kingroot?

What's going on with kingroot for Xperia z3 lolipop 5.1.1? There is a date for available kingroot for this version?

No there isn't. Kingroot only supports 5.0 not 5.1 You could always flash 5.0.2, root with kingroot then flash a pre-rooted 5.1.1

heywheelie said:
No there isn't. Kingroot only supports 5.0 not 5.1 You could always flash 5.0.2, root with kingroot then flash a pre-rooted 5.1.1
Click to expand...
Click to collapse
I did it but when I updated to 5.1.1 the Root was deleted

DANIELTZ19 said:
What's going on with kingroot for Xperia z3 lolipop 5.1.1? There is a date for available kingroot for this version?
Click to expand...
Click to collapse
No date available...
I'm waiting for it too :crying:

DANIELTZ19 said:
I did it but when I updated to 5.1.1 the Root was deleted
Click to expand...
Click to collapse
Did you flash a stock 5.0.2, then root with kingroot, install the latest dual recovery from PC, boot to recovery, do a complete wipe then flash a pre-rooted 5.1.1 from recovery. It should work. I tried it here, worked perfectly.
BTW make sure you put the pre-rooted 5.1.1 on your sdcard before you start so once you go into recovery to do a full wipe you don't reboot until you flash the pre-rooted 5.1..1

heywheelie said:
Did you flash a stock 5.0.2, then root with kingroot, install the latest dual recovery from PC, boot to recovery, do a complete wipe then flash a pre-rooted 5.1.1 from recovery. It should work. I tried it here, worked perfectly.
BTW make sure you put the pre-rooted 5.1.1 on your sdcard before you start so once you go into recovery to do a full wipe you don't reboot until you flash the pre-rooted 5.1..1
Click to expand...
Click to collapse
I don't install pre-rooted 5.1.1 because it needs to Recovery .. and I don't want to do a recovery in my device .... i just Burning a normal version of 5.1.1

DANIELTZ19 said:
I don't install pre-rooted 5.1.1 because it needs to Recovery .. and I don't want to do a recovery in my device .... i just Burning a normal version of 5.1.1
Click to expand...
Click to collapse
Then just delete the recovery after you have flashed the pre rooted 5.1.1. The ramdisks are in the system partition.

gregbradley said:
Then just delete the recovery after you have flashed the pre rooted 5.1.1. The ramdisks are in the system partition.
Click to expand...
Click to collapse
If I do now Recovery then it deletes all my stuff in the cell phone .. other than that it will lose my warranty and it might make my cell phone issues

DANIELTZ19 said:
If I do now Recovery then it deletes all my stuff in the cell phone
Click to expand...
Click to collapse
It should not do that if you do it properly. You only lose stuff in your phone if you unlock the bootloader and you do not need to do that. Also, making a backup of things you want to keep is always a good idea.
DANIELTZ19 said:
.. other than that it will lose my warranty and it might make my cell phone issues
Click to expand...
Click to collapse
No you will not lose warranty if you follow the locked bootloader tutorial. You do not need to unlock the bootloader to install recovery and flash a pre-rooted 5.1.1
Please take a moment to look through any of the multiple guides in the general section to see how to do this

gregbradley said:
It should not do that if you do it properly. You only lose stuff in your phone if you unlock the bootloader and you do not need to do that. Also, making a backup of things you want to keep is always a good idea.
No you will not lose warranty if you follow the locked bootloader tutorial. You do not need to unlock the bootloader to install recovery and flash a pre-rooted 5.1.1
Please take a moment to look through any of the multiple guides in the general section to see how to do this
Click to expand...
Click to collapse
Okay, thank you very much, but there will be no hacking with "Kingroot"? This is the most easy and simple ..

DANIELTZ19 said:
Okay, thank you very much, but there will be no hacking with "Kingroot"? This is the most easy and simple ..
Click to expand...
Click to collapse
Kingroot will send your IMEI to an IP address in china, I do not recommend it. Downgrade and use giefroot, install dual recovery, flash a pre rooted 5.1.1, then delete the recovery if you want, but I do not see why you would do this.

gregbradley said:
Kingroot will send your IMEI to an IP address in china, I do not recommend it. Downgrade and use giefroot, install dual recovery, flash a pre rooted 5.1.1, then delete the recovery if you want, but I do not see why you would do this.
Click to expand...
Click to collapse
Because that everyone I know who did Recovery then it's destroyed a lot of things on the device ..

DANIELTZ19 said:
Because that everyone I know who did Recovery then it's destroyed a lot of things on the device ..
Click to expand...
Click to collapse
You are confusing recovery with losing drm keys when unlocking the bootloader.
I have never come across anyone who has recovery installed correctly and used correctly who has had problems like that

@DANIELTZ19
If you're worried and want another opinion then my advice is that everything GregBradley has stated is correct. His method is also the safest and reliable with an excellent tutorial in the General forum. Read it http://forum.xda-developers.com/z3/general/guide-rootrecovery-how-to-root-install-t3017056
cheers

[Q] Is it possible to Flash .ZIP without root?

I have Galaxy S6 (920F) with Android Nougat.
I have managed to install TWRP Recovery on my device and it is allowing me to install .zip files. But my phone is Not ROOTED.
So my question is,
If I flash .zip(s) now that are made for my device, will it be installed successfully?
or my device will stuck on bootloop?

Well, if you are flashing some files into directories that don't require root to access, it will work.
But lets say you want to flash ported system app (like message app). It will not work, since it requires flashing into \system and that directory requires root to be accessed and modified. :good:

Ragazzza said:
Well, if you are flashing some files into directories that don't require root to access, it will work.
But lets say you want to flash ported system app (like message app). It will not work, since it requires flashing into \system and that directory requires root to be accessed and modified. :good:
Click to expand...
Click to collapse
so if I'd want to install a custom rom i need to have twrp installed and also the phone needs to be rooted, right?(kind of a stupid question, I know)
also, are these tutorials good to install twrp and root my g920f with the xef 7.0 android?
/watch?v=oDX8OT0jWw0&t=4s
/watch?v=sHXvuRRlNnI

ciprian97pop said:
so if I'd want to install a custom rom i need to have twrp installed and also the phone needs to be rooted, right?(kind of a stupid question, I know)
also, are these tutorials good to install twrp and root my g920f with the xef 7.0 android?
/watch?v=oDX8OT0jWw0&t=4s
/watch?v=sHXvuRRlNnI
Click to expand...
Click to collapse
Yup, you need root for rom. Hm i would like to guide you by writting here, but just watch on youtube how to root galaxy s6 nougat, about a week ago i have rooted my friends s6 flat g920f, everything went smooth! :good:

Ragazzza said:
Yup, you need root for rom. Hm i would like to guide you by writting here, but just watch on youtube how to root galaxy s6 nougat, about a week ago i have rooted my friends s6 flat g920f, everything went smooth! :good:
Click to expand...
Click to collapse
ok then
basically, boot into recovery, flash twrp, reboot, boot again into recovery which now is twrp then flash another zip and in the end you have a custom recovery and root, righr?

ciprian97pop said:
ok then
basically, boot into recovery, flash twrp, reboot, boot again into recovery which now is twrp then flash another zip and in the end you have a custom recovery and root, righr?
Click to expand...
Click to collapse
Nah man, you flash twrp with odin
here you go

How did u manage to install twrp on sm-g920f ??

On H83010i, bootloader unlocked not rooted. Want H83020f rooted

I have successfully unlocked the bootloader my H83010i version.
I started down the path to root my device using H83010d tot file but stopped because I didn't know if when I upgrade to android 7.0 versions if I would lose root?
Therefore what is the easiest way to get to H83020f rooted?
How do I go from H83010i to H83020f and be rooted?
I have rooted a lot of samsung galaxy phones but this is my first LG so I am struggling a bit to understand how to upgrade. I assume if I do an OTA update it will install the latest version? I checked for system updates and it just said there is an update and to start downloading it but I don't know which update version that is?
Please advise.
Thanks in advance.

buyslake said:
I have successfully unlocked the bootloader my H83010i version.
I started down the path to root my device using H83010d tot file but stopped because I didn't know if when I upgrade to android 7.0 versions if I would lose root?
Therefore what is the easiest way to get to H83020f rooted?
How do I go from H83010i to H83020f and be rooted?
I have rooted a lot of samsung galaxy phones but this is my first LG so I am struggling a bit to understand how to upgrade. I assume if I do an OTA update it will install the latest version? I checked for system updates and it just said there is an update and to start downloading it but I don't know which update version that is?
Please advise.
Thanks in advance.
Click to expand...
Click to collapse
First of all, no need to use 10D tot file anymore. Download and install 20A kdz front autoprime located here:
https://forum.xda-developers.com/tmobile-lg-g5/development/stock-h830-20a-rom-flashable-zips-imgs-t3511294
Once that's installed, set up your system and then follow the following guide to get TWRP an root:
https://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-running-30a-nougat-t3524322
After you have TWRP and root download the flashable 20F zip and install from TWRP (make sure to delete recovery from boot.p file after installing and also flash root). Here's the link to 20F:
https://forum.xda-developers.com/tmobile-lg-g5/development/stock-h830-20f-rom-flashable-zips-imgs-t3592855
If you follow all of that, you will be on stock 20F, rooted and with TWRP. After that, I recommend checking out the following custom kernel and installing that and using magisk instead of SuperSU. Kernel located here:
https://forum.xda-developers.com/tmobile-lg-g5/development/jan-17-2017-20c-deodexed-kernels-t3539611
Hopefully that helps, if you need more help just ask.

Thanks so much for taking the time to write me this great information. I have a question about the (make sure to delete recovery from boot.p file after installing and also flash root). ???????? Is this explained clearly somewhere? I don't know what I should do.

buyslake said:
Thanks so much for taking the time to write me this great information. I have a question about the (make sure to delete recovery from boot.p file after installing and also flash root). ???????? Is this explained clearly somewhere? I don't know what I should do.
Click to expand...
Click to collapse
After flashing the 20F version from TWRP, it creates a recovery from boot.p file in the system directory. If you don't delete this file before rebooting, you will lose TWRP. So, after doing the recowvery method to get root and TWRP and then after you flash the 20F from TWRP, after it's done flashing go to main menu of TWRP, click on mount, check system, go back to main menu, click advanced, click file manager and go-to system directory and click on the recovery from boot.p file and then delete. Now you can reboot without losing TWRP. Then you can flash SuperSU or magisk for root

Your Device software cannot be checked for corruption. Lock the bootloader
Thanks for the fast responses. After many hours of studying the posts and I finally got my LG G5 running on H830_20F_DeOdexed rom withh Asgard version 4.5 kernal and rooted with SuperSU v2.74.
However I keep getting the "your device software cannot be checked for corruption. lock the bootloader message upon starting up. see attachment
Does everyone get that message? Or is there a way to remove it?
I thought the Asgard kernal said it got rid of that?

buyslake said:
Thanks for the fast responses. After many hours of studying the posts and I finally got my LG G5 running on H830_20F_DeOdexed rom withh Asgard version 4.5 kernal and rooted with SuperSU v2.74.
However I keep getting the "your device software cannot be checked for corruption. lock the bootloader message upon starting up. see attachment
Does everyone get that message? Or is there a way to remove it?
I thought the Asgard kernal said it got rid of that?
Click to expand...
Click to collapse
You'll always have that message, no current way around it. Asgard kennel will allow you to pass safety net if you use magisk instead of SuperSU for root as it hides that the bootloader is unlocked from the system.

Where is Magisk?
jeffsga88 said:
You'll always have that message, no current way around it. Asgard kennel will allow you to pass safety net if you use magisk instead of SuperSU for root as it hides that the bootloader is unlocked from the system.
Click to expand...
Click to collapse
Are you saying that boot up message will not be there if I switch to Magisk?
I tried to find magisk but I was unable to locate the install file and instructions on how to change from SuperSU to magisk. Do you know the link to it?

buyslake said:
Are you saying that boot up message will not be there if I switch to Magisk?
I tried to find magisk but I was unable to locate the install file and instructions on how to change from SuperSU to magisk. Do you know the link to it?
Click to expand...
Click to collapse
No. I said currently there is no way to get rid of that message unless you lock the bootloader and you can't do that after modifying the system (i.e. installing TWRP and root). I said magisk will allow you to pass safety net. All that does is allow you to use apps that won't work with root / unlocked bootloader. If you don't use apps like Android pay or other apps that don't work when rooted, it really isn't necessary to switch from SuperSU to magisk. Anyways, if you're interested in magisk use Google (or XDA search) and search magisk XDA.

OneUi Android Pie (9.0) (without Root , With Root, With Root + Xposed ) For A8 plus.

Backup First I am not responsible for anything. Backup your NVRAM NVDATA EFS to restore ur iemi .
I have Made a TWRP backup for Pie so everybody can move from Oreo to pie by Restoring Backup.
first install BL and CP of pie throw odin and then restore backup uncheck efs while restoring.
Pie (9.0) with root:
https://mega.nz/#!8BJ30IBS!Ho6iy07O3NZLyKI-A1-yWWI3qqBLH4Cix92s6fyAw_Y
Pie (9.0) with root+xposed:
https://mega.nz/#!cBYnwYDL!Sc2QuTOLi257erZfKtX3aBZltSAtqfXxxvG06EFlxr8
CP and BL for Pie and Odin:
https://mega.nz/#!FEZhmATR!xb1LLR5npE4EwpZCBZhpP0jrBy0fgctKKIJsgtMHG9k

ajnajao1 said:
Removed
Click to expand...
Click to collapse
Why did you remove this?

Where link without root?

freemod said:
Where link without root?
Click to expand...
Click to collapse
Use file with Root and use magisk uninstaller to remove root.

ajnajao1 said:
Backup First I am not responsible for anything. Backup your NVRAM NVDATA .
I have Made a TWRP backup for Pie so everybody can move from Oreo to pie by Restoring Backup.
first install BL and CP throw odin and then restore backup
Pie (9.0) with root:
https://mega.nz/#!8BJ30IBS!Ho6iy07O3NZLyKI-A1-yWWI3qqBLH4Cix92s6fyAw_Y
Pie (9.0) with root+xposed:
https://mega.nz/#!cBYnwYDL!Sc2QuTOLi257erZfKtX3aBZltSAtqfXxxvG06EFlxr8
CP and BL for Pie and Odin:
https://mega.nz/#!FEZhmATR!xb1LLR5npE4EwpZCBZhpP0jrBy0fgctKKIJsgtMHG9k
Click to expand...
Click to collapse
How did you root pie?

I have decided to share screenshots
I'm a us user as you can see I have volte working and I got Dolby working .
Make sure you have the latest Oreo bootloader installed this so can down grade to Oreo if I want to.
Do not flash pie modems if you do you will have to flash pie bootloader.
If you have a bootloader example
Xxu3 you need flash ap system and bootloader xxs4.
This not for flashing this build but for flashing pie on Odin

Restore.
Restoring with selected EFS damaged original IMEI.... Without is it ok. Thanks!

when I went to install the stock gave error of dm-verify
Help me!!

RuizLenatoh said:
when I went to install the stock gave error of dm-verify
Help me!!
Click to expand...
Click to collapse
Specify your question. what are you asking>?

ajnajao1 said:
Specify your question. what are you asking>?
Click to expand...
Click to collapse
Do you have a telegram? so I can talk to you better

mchlbenner said:
I have decided to share screenshots
I'm a us user as you can see I have volte working and I got Dolby working .
Make sure you have the latest Oreo bootloader installed this so can down grade to Oreo if I want to.
Do not flash pie modems if you do you will have to flash pie bootloader.
If you have a bootloader example
Xxu3 you need flash ap system and bootloader xxs4.
This not for flashing this build but for flashing pie on Odin
Click to expand...
Click to collapse
How do I flash and does this work for my country?

Bad.Server said:
How do I flash and does this work for my country?
Click to expand...
Click to collapse
Depends on which country.
I'm using Canada csc it works on USA and Canada.

ت

mchlbenner said:
Depends on which country.
I'm using Canada csc it works on USA and Canada.
Click to expand...
Click to collapse
I'm from the Philippines and I don't know how this would work.... should flash the Philippine csc from the 8.0 update er. Sorry I'm completely clueless on how this works, all I know is flashing them.

Bad.Server said:
I'm from the Philippines and I don't know how this would work.... should flash the Philippine csc from the 8.0 update er. Sorry I'm completely clueless on how this works, all I know is flashing them.
Click to expand...
Click to collapse
Depends on what you want to get out of your phone.
I'm rooted so I had to use this canda csc.
For ab+ their no USA build I want have volte.
This csc I flash is done through twrp.
If your stock no root ect and you get what the services you want then go a head and do it.
If you are rooted and want to keep root then I would not.

mchlbenner said:
Depends on what you want to get out of your phone.
I'm rooted so I had to use this canda csc.
For ab+ their no USA build I want have volte.
This csc I flash is done through twrp.
If your stock no root ect and you get what the services you want then go a head and do it.
If you are rooted and want to keep root then I would not.
Click to expand...
Click to collapse
How do flash it though? I extracted the .zip file but it doesnt have the files to be flashed through Odin. Also I think I should tell you that my phone or rather knoxs tells's me that my phone is rooted but I've already flashed the non-rooted stock rom years ago because I failed when I tried to root my phone before and I don't know how to fix my mistake and gain root. If its not too much to ask, I would like to ask for your help, I would greatly appreciate it.

Bad.Server said:
How do flash it though? I extracted the .zip file but it doesnt have the files to be flashed through Odin. Also I think I should tell you that my phone or rather knoxs tells's me that my phone is rooted but I've already flashed the non-rooted stock rom years ago because I failed when I tried to root my phone before and I don't know how to fix my mistake and gain root. If its not too much to ask, I would like to ask for your help, I would greatly appreciate it.
Click to expand...
Click to collapse
It is a twrp back so it has to be flash with twrp.

Unsupported/Unknown image format when patching via Magisk pls help

Hi,
I have very awkward problem, when trying to root my xperia xz. I was trying almost everything to fix it, but nothing helped. I used different Magisk version, downloading different stock roms from Xperifirm that fits mine fw, extracting kernel.sin, dumping with flashtool to kernel.elf, and renaming to boot.img, but still the problem occured. I was also trying to root via twrp, but still the same problem. I read tons of guides, but found nothing useful, searched in google and nothing. It seems like the problem is quite rare. I also noticed, that every boot.img, which Magisk can patch, has size below 20MB, for example, boot.img from ROMs downloaded by Xperifirm, have around 35MB, and boot.img transferred from my phone has 65MB. And second thing, when i was trying to modify boot.img via rootkernel, only kernels that rootkernel could modify, were the kernels patchable by Magisk. Rootkernel was getting stuck with kernels from Xperifirm and from my phone. When flashed kernel, that Magisk could patch, bootloop occurred. My stock rom is oreo 8.0.0 41.3.A.2.192-R2E, bootloader is unlocked. Maybe my phone is just unrootable? Or kernels from stock roms are encrypted somehow, and i just don't know how to decrypt them? Every help is really appreciated, thanks.

try to root with twrp

Raghaov said:
try to root with twrp
Click to expand...
Click to collapse
I tried, but it didnt work, i wrote that earlier

Blaska122 said:
Or kernels from stock roms are encrypted somehow, and i just don't know how to decrypt them?
Click to expand...
Click to collapse
Here is what you need to extract your kernel (boot.img) from offical firmware. You will also need to repack it (very simple, just unpack ~ repack) with AIK in order for it to boot properly rooted.

&(*) said:
Here is what you need to extract your kernel (boot.img) from offical firmware. You will also need to repack it (very simple, just unpack ~ repack) with AIK in order for it to boot properly rooted.
Click to expand...
Click to collapse
Thanks for answer!

Thank you all for help, but I recently change my phone, so the thread can be archived.