Database Users

How to root LG D802 with 220H firmware ?

Hi,
Is there any reasonably safe way to root LG D802 (international ANEUBK version) with latest 220H update installed ? The phone was never rooted before. I know how to use ADB, etc.
Thanks !

Cst79 said:
Hi,
Is there any reasonably safe way to root LG D802 (international ANEUBK version) with latest 220H update installed ? The phone was never rooted before. I know how to use ADB, etc.
Thanks !
Click to expand...
Click to collapse
Towelroot

azher98 said:
Towelroot
Click to expand...
Click to collapse
Doesn't work, it sais "phone is not supported". I understand that towelroot exploits a Linux kernel loophole that was patched around June 3.

Ioroot by side loading in stock recovery, or stump root, the only two ways for rooting 20h, powered by codefire team members (those who made Bump! )
http://forum.xda-developers.com/showthread.php?t=2448887
http://forum.xda-developers.com/showthread.php?t=2850906

6ril1 said:
Ioroot by side loading in stock recovery, or stump root, the only two ways for rooting 20h, powered by codefire team members (those who made Bump! )
http://forum.xda-developers.com/showthread.php?t=2448887
http://forum.xda-developers.com/showthread.php?t=2850906
Click to expand...
Click to collapse
Sorry, but I just gave up on it. Everything is such a mess regarding tools, versions, download locations...I will probably just wait for the official Lollipop update (the reason why I wanted to root was to install CM12 eventually).

Cst79 said:
Sorry, but I just gave up on it. Everything is such a mess regarding tools, versions, download locations...I will probably just wait for the official Lollipop update (the reason why I wanted to root was to install CM12 eventually).
Click to expand...
Click to collapse
It's very simple:
1) download ioroot:
http://downloads.codefi.re/autoprime/LG/ioroot/ioroot.zip
2) extract datroot.zip from the archive just downloaded (from bts folder)
3) on the G2 enable dev option (Settings - About Phone. Then go to the bottom and you should see Build Number. This needs to be pressed a total of seven times. You should get a message at the fourth press. On the seventh, you'll get another message saying that Developer Options are unlocked.)
4) enable usb debug on the phone (Development Settings Enable USB Debugging)
5) plug the phone in usb with the pc and accept yhe RSA Fingerprint message.
6) reboot your phone in recovery with adb cmd (tape cmd: adb reboot recovery)
7) choose 'apply update from adb' in the phone recovery menu (navigate with vol down and valid with power)
8) in the pc tape cmd: adb sideload c:\datroot.zip
9) reboot et enjoy
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

6ril1 said:
It's very simple:
Click to expand...
Click to collapse
Thank you, I figured these steps but:
- On one ioroot post (old post - first in thread I think) , they say that I cannot easily install custom recovery without some modified kernel ?? Are you sure I can install TWRP after rooting in order to ensure a way to flash images ?
- Also, can I revert to 100% stock after this (including baseband, bootloader, etc.), if I want to ? If so, with what tools and steps ? This information is very valuable to me.
- Right now I cannot enter recovery mode pressing the Vol Down + power then waiting for LG logo then pressing them again or power button 3 times, no matter what. I can only do this with "adb reboot recovery". Why is this ?
Thanks !

Cst79 said:
Thank you, I figured these steps but:
- On one ioroot post (old post - first in thread I think) , they say that I cannot easily install custom recovery without some modified kernel ?? Are you sure I can install TWRP after rooting in order to ensure a way to flash images ?
- Also, can I revert to 100% stock after this (including baseband, bootloader, etc.), if I want to ? If so, with what tools and steps ? This information is very valuable to me.
- Right now I cannot enter recovery mode pressing the Vol Down + power then waiting for LG logo then pressing them again or power button 3 times, no matter what. I can only do this with "adb reboot recovery". Why is this ?
Thanks !
Click to expand...
Click to collapse
The bootloader is locked. Untill recently, there was only one way to work around it, loki patch.
Only JB bootloader was lokiable, LG patched the KK one and loki doesn't work on it.
So, with loki, you had to downgrade bootloader for being able to apply loki. KK kernel must be patched too for being able to boot behind the downgraded bootloader. All the method for installing a custom recovery with this system was automated by the app autorec.
Recently, Bump was made. it permits to stay with kk booloader. It inject in the kernel (custom recovery and custom kernel) LG authentic Key.
You can easily revert to stock by flashing kdz, or even flashing zip that contains original partition.
I don't understand you last question.

6ril1 said:
The bootloader is locked. Untill recently, there was only one way to work around it, loki patch.
Only JB bootloader was lokiable, LG patched the KK one and loki doesn't work on it.
So, with loki, you had to downgrade bootloader for being able to apply loki. KK kernel must be patched too for being able to boot behind the downgraded bootloader. All the method for installing a custom recovery with this system was automated by the app autorec.
Recently, Bump was made. it permits to stay with kk booloader. It inject in the kernel (custom recovery and custom kernel) LG authentic Key.
You can easily revert to stock by flashing kdz, or even flashing zip that contains original partition.
I don't understand you last question.
Click to expand...
Click to collapse
Sorry, but you lost me here. I can't map your answers to my simple questions. My simple questions are:
- Can I revert to 100% factory stock, if I mess with rooting and install CyanogenMod 12 ? If yes, how ?
- After rooting with ioroot (what's the difference between ioroot and ioroot25 ??) what is the simplest way to install CyanogenMod 12 ? I don't really care about TWRP and such if I don't need to.
I'm really not a noobie, but not living in this world of phone hacking I can't figure out the names, versions, etc.
Thanks !

Cst79 said:
Sorry, but you lost me here. I can't map your answers to my simple questions. My simple questions are:
- Can I revert to 100% factory stock, if I mess with rooting and install CyanogenMod 12 ? If yes, how ?
- After rooting with ioroot (what's the difference between ioroot and ioroot25 ??) what is the simplest way to install CyanogenMod 12 ? I don't really care about TWRP and such if I don't need to.
I'm really not a noobie, but not living in this world of phone hacking I can't figure out the names, versions, etc.
Thanks !
Click to expand...
Click to collapse
No offense, but I tried to answer you on technical aspects, but I perceive me that your questions are more general order.
it takes time to explain what is custom recovery, and there are already tons of readings that relate to this topic.
I answered to your principal question, how to root 80220H.
As i said in my previous edited answer, you can go back to stock if you need.
I also realize that this thread should instead be placed in question/answer section, not in a dev section.

6ril1 said:
No offense, but I tried to answer you on technical aspects, but I perceive me that your questions are more general order.
it takes time to explain what is custom recovery, and there are already tons of readings that relate to this topic.
I answered to your principal question, how to root 80220H.
As i said in my previous edited answer, you can go back to stock if you need.
I also realize that this thread should instead be placed in question/answer section, not in a dev section.
Click to expand...
Click to collapse
Hello,
No, my questions are not generic, I want to find out:
- How do I install CyanogenMod 12 after I root the phone.
- What are the steps to revert to 100% stock after I root the phone and install CM12; Can I just use the LG flash tool and flash the kdz with no complains from the LG software if I have CM12 installed ?
Thanks.

Do you loss data with this metod?
Thanks

LG Spirit H440n general thread

Welcome to the general thread for LG Spirit H440n/H420 and it's other variants.
Feel free to share any information you have about this device. I will include everything important at the op.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Specifications
You can find LG Spirit specs here.
USB Drivers:
You can find drivers for your device through LG mobile support tool.
Also, there are the universal LG USB drivers.
Stock kdz files
You can find the stock firmware for LG Spirit variants here.
Root
You can root any Lollipop version with KingRoot.
Here is how to replace KingRoot with SuperSU.
You can root any version (Lollipop or Marshmallow) by unlocking the bootloader and installing a custom recovery first.
Bootloader Unlock
You can unlock the H440n bootloader with the method provided here.
For unlocking the H420/H422 bootloader (patched uboot) refer to the Notes section of this post.
Custom Recoveries
CWM H440n
TWRP H440n thread, maintained by @Fobos531
Refer to the Notes section of this post for H420/H422 custom recovery flashing.
Notes
Note1: You can install the Lollipop kdz files with LG Flash Tool. Also, here are some details on how to install the Marshmallow kdz.
Note2: LG Spirit source code can be found here.
Note3: It seems that in order to use ADB you have to set the USB connection type to:
1. MTP in windows
2. PTP in linux
Note4: LG H422 users, find everything about your device in detail here (4pda thread) and here (xda thread). You can find infromation on how to unlock the bootloader (uboot patch), root, flash a custom recovery and stock or custom roms.

screen on
hello there, just bought this phone. It's fine. But why doesn't it switch the screen on when a notification arrive? do you have any solution or suggestion? thanks!

giamanto said:
hello there, just bought this phone. It's fine. But why doesn't it switch the screen on when a notification arrive? do you have any solution or suggestion? thanks!
Click to expand...
Click to collapse
Hello. You' re right I notice it too. I think you can try the app "Screen notifications" from the Play Store but I haven't tested it yet.

polfrank said:
Note 4: It seems like our device's source code can be found here: http://opensource.lge.com/osSch/list?types=ALL&search=h440 (Correct me if I'm wrong). I wish I knew how to build Cyanogenmod..
Click to expand...
Click to collapse
I'll check it out when I get to my work computer. No linux at home...
At least CWM Recovery would be nice to have.
Edit:
http://pastebin.com/06QGsZgh

polfrank said:
Hello. You' re right I notice it too. I think you can try the app "Screen notifications" from the Play Store but I haven't tested it yet.
Click to expand...
Click to collapse
thank you! it works PERFECTLY!

If I have done everything right, I have extracted the kdz file (T-mobile Croatia) and here we have recovery.img and boot.img attached to this post!
I post them because someone may be able to build CWM recovery for us, so I would like to make his life easier if he decides to do so.

polfrank said:
If I have done everything right, I have extracted the kdz file (T-mobile Croatia) and here we have recovery.img and boot.img attached to this post!
I post them because someone may be able to build CWM recovery for us, so I would like to make his life easier if he decides to do so.
Click to expand...
Click to collapse
Buddy you are my hero! Now I can get some stuff done with syncing CM12 sources to build CWM and after that hopefully TWRP with one buddy from BUG Forums. For now on, priority is CWM and hopefully CM12(.1 is optional). I tested out with extracting boot.img and recovery.img directly from phone and didn't had success with it (failed to do some stuff with creating .mk files for phone).
Also thanks to OP for .kdz file, it shall work on any other network because it is very much clean ROM (Croatian T-Mobile, only have few apps which can be uninstalled without root).
Peace from owner which had this phone rooted.

midzan21 said:
Buddy you are my hero! Now I can get some stuff done with syncing CM12 sources to build CWM and after that hopefully TWRP with one buddy from BUG Forums. For now on, priority is CWM and hopefully CM12(.1 is optional). I tested out with extracting boot.img and recovery.img directly from phone and didn't had success with it (failed to do some stuff with creating .mk files for phone).
Also thanks to OP for .kdz file, it shall work on any other network because it is very much clean ROM (Croatian T-Mobile, only have few apps which can be uninstalled without root).
Peace from owner which had this phone rooted.
Click to expand...
Click to collapse
Nice! If you compile a working cwm for a start, YOU are a hero! Feel free to ask for anything else I can do to help you with (but I know only little stuff).
I just want to mention that the thanks for the .kdz file goes to the guys I mention at the credits!

Seems that bootloader is locked. Fastboot oem unlock didn't work and didn't have luck with loki or bump either.

manakeri said:
Seems that bootloader is locked. Fastboot oem unlock didn't work and didn't have luck with loki or bump either.
Click to expand...
Click to collapse
You mean you wanted to flash recovery and the locked bootloader prevented you? If this is the case try the app "flashify" from Play Store.
If you just mention it, well, it's good to know. :good:

I flashed the recovery, that's not the problem, booting into it is.
Someone else with more experience about unlocking bootloaders (and time) could have a try.
I'll upload the CM device files to the github tomorrow.

manakeri said:
I flashed the recovery, that's not the problem, booting into it is.
Someone else with more experience about unlocking bootloaders (and time) could have a try.
I'll upload the CM device files to the github tomorrow.
Click to expand...
Click to collapse
Actually there isn't problem with booting in recovery you just need to do this button combination
Power + vol down and when lg logo apears press combination again
This is how LG G3 goes to recovery and it should work here too
Edit: I should upload also CM device files and kernel to my github next week at collège so we should have all files on one github

You can reboot to recovery with apps that offer an advanceed reboot menu, too. Like Link2sd.
Though, I don't know if @manakeri is talking about something else like: try boot to recovery but the locked bootloader prevents you..

polfrank said:
Though, I don't know if @manakeri is talking about something else like: try boot to recovery but the locked bootloader prevents you..
Click to expand...
Click to collapse
Exactly that. There is verification that the recovery's certificate matches original or something like that.

Here is new firmwares
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW79RCO032ESAYF6BB4BMEM/H440n10e_00.kdz - LG H440N 10E HUNGARY
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW48UI40323XARJB234BLAO/H440n10b_00.kdz - LG H440N 10B Poland PLUS

Well seems that our bootloader isn't locked if I look via this app. Would give a try with CWM (currently building up from stratch, need some time to compile it) and see would it boot up somehow (key combo and this app)

http://www.mediafire.com/download/51nnmacvkqm5df9/recovery.img

manakeri said:
http://www.mediafire.com/download/51nnmacvkqm5df9/recovery.img
Click to expand...
Click to collapse
That is CWM you built or it is TWRP?

CWM

Working? How instaled this?

TWRP for Z3 compact ; Unlocked Bootloader - GUIDE

Hey guys! Here is how to get recovery for your Z3 Compact without losing any files or flashing any kernels, as this could usually be a pain in the butt if you need a kernel for a custom rom...
I do not take credit for any of the resources in this guide and neither do i take any responsibility for bricked phones,dead SD cards or death
Click to expand...
Click to collapse
Prerequisites
1. Unlocked Bootloader (Its fairly easy to do, a simple google would suffice)
2. TWRP image- Get it Here
3. Flashtool installed with all required drivers
4. ADB and Fastboot (Here)
5. Patience
How to Install
1. Make sure you have an unlocked bootloader or this will, and shall not work.
2. Make sure you are running the latest firmware (.291). If not, use flashtool to update to the latest firmware.
3. Copy the downloaded TWRP image to your adb/fastboot folder and rename it recovery.img for ease.
4. Click shift+right click in any empty space in your adb/fastboot folder and click open command window here.
5. switch off your z3c. press the vol up button and insert USB cable to boot into fastboot mode
6. Make sure everything is working by typing
Code:
fastboot devices
in the cmd window. If all is well, then it should show your device's serial along with fastboot written beside it.
7. Time to flash the recovery:
Type in this command
Code:
fastboot flash recovery recovery.img
Congrats! You now have a recovery
8. To enter recovery mode, power off your phone, and press and hold Vol-down and Power button together until you see the sony logo.
You can now flash any rom or zips you want with this recovery, for root, flash the latest SuperSu Zip from chainfire.
I would also recommend flashing DRM fix zip.
If you want a better version of the stock rom, i will recommend installing SliMM Rom by Wajk
Note: This TWRP can get uninstalled in some cases, for example flashing a rom with twrp built in. But repeat the same process to get TWRP back without losing any data!
Thanks!

Hi, I'm from Brazil and I just bought a used D5833.
As usual, as soon as I bought the device, I did the procedure to unlock Bootloader without knowing that it was not necessary to get root and neither of the side effects of the unlock (about the quality of the camera and etc).
However the whole procedure worked well to install RECOVERY but I still could not get root.
I am using a MM 6.0.1 and TWRP 3.0.2-1 and the problem is always the same at the time of doing the FLASH in Supersu:
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
I tried with the following versions of SUPERSU:
UPDATE-SuperSU-v2.65-20151226141550.zip
BETA-SuperSU-v2.68-20160228150503.zip
UPDATE-SuperSU-v2.76-20160630161323.zip
SR4-SuperSU-v2.78-SR4-20161115184928.zip
Older versions cause a bootloop
I keep looking but I can not do ROOT
I would even like to install the SliMM ROM but you need root first.
Could you help me ??

dansan691 said:
Hi, I'm from Brazil and I just bought a used D5833.
As usual, as soon as I bought the device, I did the procedure to unlock Bootloader without knowing that it was not necessary to get root and neither of the side effects of the unlock (about the quality of the camera and etc).
However the whole procedure worked well to install RECOVERY but I still could not get root.
I am using a MM 6.0.1 and TWRP 3.0.2-1 and the problem is always the same at the time of doing the FLASH in Supersu:
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
I tried with the following versions of SUPERSU:
UPDATE-SuperSU-v2.65-20151226141550.zip
BETA-SuperSU-v2.68-20160228150503.zip
UPDATE-SuperSU-v2.76-20160630161323.zip
SR4-SuperSU-v2.78-SR4-20161115184928.zip
Older versions cause a bootloop
I keep looking but I can not do ROOT
I would even like to install the SliMM ROM but you need root first.
Could you help me ??
Click to expand...
Click to collapse
No, you can install SliMM directly. To get root, you should be using armv23 version... Try this. Also, you should use a DRM restore zip to get back camera quality

Clarification
Should I have to flash DRM Fix every time I flash TWRP?

andry360 said:
Should I have to flash DRM Fix every time I flash TWRP?
Click to expand...
Click to collapse
No need. But if you change reflash ROM, you might need to

i was able to flash to recovery but ive tried tons of version of supersu but still cant get root access, can you give a step by step instructions on how to? thank you so much.

epiii_nephrine said:
i was able to flash to recovery but ive tried tons of version of supersu but still cant get root access, can you give a step by step instructions on how to? thank you so much.
Click to expand...
Click to collapse
Can you please give me the error you get?

panzerox123 said:
Can you please give me the error you get?
Click to expand...
Click to collapse
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
ive tried almost all versions of supersu.
im running the latest stockfirware.
i hope you could help, i really need to get root access on my d5833. thanks

epiii_nephrine said:
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
ive tried almost all versions of supersu.
im running the latest stockfirware.
i hope you could help, i really need to get root access on my d5833. thanks
Click to expand...
Click to collapse
Alright... I know what's up. If you can wait till 9PM IST today, I will create another guide. Thanks!

To Get Root
As I can see, many people are having trouble getting root on their devices. You cannot directly get root on .291 as far as I know.
But since I do not use the stock firmware, there is no way for me to test. I will be using you people as testers now. I know of two methods. First , the shorter one. I got the supersu from Xperience ROM.
Please try this and let me know. Otherwise, the other method is pretty hard and requires flashing kernels.
Download the file from the attachment down.
 @epiii_nephrine

panzerox123 said:
As I can see, many people are having trouble getting root on their devices. You cannot directly get root on .291 as far as I know.
But since I do not use the stock firmware, there is no way for me to test. I will be using you people as testers now. I know of two methods. First , the shorter one. I got the supersu from Xperience ROM.
Please try this and let me know. Otherwise, the other method is pretty hard and requires flashing kernels.
Download the file from the attachment down.
@epiii_nephrine
Click to expand...
Click to collapse
Thank you so much sir! will be testing this version.. i'll let you know :good:

epiii_nephrine said:
Thank you so much sir! will be testing this version.. i'll let you know :good:
Click to expand...
Click to collapse
Sure! If this does not work, I have another method.

After installing the recovery. Every time i reboot my mobile. It goes to TWRP directly.

smahio said:
After installing the recovery. Every time i reboot my mobile. It goes to TWRP directly.
Click to expand...
Click to collapse
Doesn't make any sense... It would so that only if you flashed to boot partition. Download EliteKernel V3 , extract the zip, keep the boot.img in your minimal adb folder and do
Fastboot flash boot boot.img
Then try again

I am having issue with TWRP 3.0.2-1 on my D5833. 3.0.2-0 and other previous versions ran without problem on my Z3C but the display problem occurred in TWRP 3.0.2-1 and the situation is similar with the photo below. (It was running an AOSP 7.1 ROM for Z3C D5803, the bottom of the screen could not display correctly, and the entire screen was flashing)
According to my observations, when my D5833 was running TWRP 3.0.2-1, the color temperature of the interface was colder than that of 3.0.2-0, I guess that's due to a change in the graphics mode or something similar, and once I set the color temperature to warmer (i.e. change the display mode), it will display everything correctly. However, I just can't figure out how to do that, maybe editing some codes? Can anyone please help me?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ewjy said:
I am having issue with TWRP 3.0.2-1 on my D5833. 3.0.2-0 and other previous versions ran without problem on my Z3C but the display problem occurred in TWRP 3.0.2-1 and the situation is similar with the photo below. (It was running an AOSP 7.1 ROM for Z3C D5803, the bottom of the screen could not display correctly, and the entire screen was flashing)
According to my observations, when my D5833 was running TWRP 3.0.2-1, the color temperature of the interface was colder than that of 3.0.2-0, I guess that's due to a change in the graphics mode or something similar, and once I set the color temperature to warmer (i.e. change the display mode), it will display everything correctly. However, I just can't figure out how to do that, maybe editing some codes? Can anyone please help me?
Click to expand...
Click to collapse
Sh*t this is bad. I dont think it has anything to do with twrp. Try reinstalling stock android marshmallow.
If that doesnt work, than it is a definite problem with hardware.

panzerox123 said:
Sh*t this is bad. I dont think it has anything to do with twrp. Try reinstalling stock android marshmallow.
If that doesnt work, than it is a definite problem with hardware.
Click to expand...
Click to collapse
Thanks for the reply. I have tried to reinstall the stock ROM and many other methods but no one would fix the display problem of TWRP 3.0.2-1 and most third-party ROMs. There are only three types of ROMs can run without display problems on my D5833: stock Sony Xperia ROM, official CyanogenMod 12.1 builds and any third-party ROMs mainly based on stock Xperia ROM and / or CM. CM builds higher than 12.1 will occur the display problems too.
I remember there is another characteristic: the boot screen can indicate the situation - when the boot screen shows "SONY" logo at the center with "XPERIA" logo at the bottom, there is NO display problem. When the boot screen only shows "SONY" logo and the bottom is empty, there WILL BE display problem. It's quite weird.

ewjy said:
Thanks for the reply. I have tried to reinstall the stock ROM and many other methods but no one would fix the display problem of TWRP 3.0.2-1 and most third-party ROMs. There are only three types of ROMs can run without display problems on my D5833: stock Sony Xperia ROM, official CyanogenMod 12.1 builds and any third-party ROMs mainly based on stock Xperia ROM and / or CM. CM builds higher than 12.1 will occur the display problems too.
I remember there is another characteristic: the boot screen can indicate the situation - when the boot screen shows "SONY" logo at the center with "XPERIA" logo at the bottom, there is NO display problem. When the boot screen only shows "SONY" logo and the bottom is empty, there WILL BE display problem. It's quite weird.
Click to expand...
Click to collapse
oh OK. If this problem did not exist on older version of TWRP, then using the same method, roll back to twrp 3.0.2-0. you just need to download that file. All the best!

panzerox123 said:
oh OK. If this problem did not exist on older version of TWRP, then using the same method, roll back to twrp 3.0.2-0. you just need to download that file. All the best!
Click to expand...
Click to collapse
Indeed there will be no problem for older versions. However, I am still unable to install and run many third-party ROMs smoothly, that means the number of ROMs I can try out is limited. Anyway, that is alright, thanks for your reply.

ewjy said:
Indeed there will be no problem for older versions. However, I am still unable to install and run many third-party ROMs smoothly, that means the number of ROMs I can try out is limited. Anyway, that is alright, thanks for your reply.
Click to expand...
Click to collapse
Funny... It works very well for me... In fact it's much more stable than previous versions

[TWRP][P9+][3.1.1-1][EMUI 5.x ONLY][DECRYPTION SUPPORT]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is only for Huawei P9 Plus (VIE)
Code:
OpenKirin presents unofficial TWRP for stock EMUI 5.x with decryption support.
Intended for usage on stock emui 5.x in combination with unlocked bootloader and
modded boot image with disabled dm-verity (depending on what you want to do).
Code:
[COLOR="red"][B]WARNING:[/B] since 3.1.0-2 update we've enabled image flashing to special partitions -
not just /recovery or /boot partition.
That means your device could be bricked in a few seconds if you do not pay attention
or don't know what you're doing. (Noobs please stay away out of this section!)[/COLOR]
Installation Instructions
Code:
1. Enter fastboot mode on unlocked device
2. flash recovery using the following command: fastboot flash recovery twrp-3.1.1-1-vie.img
3. reboot to recovery!
Rooting Methods
Code:
[B][U]1. Official SuperSU (not just 2.82+)[/U][/B]
1. Ensure you are running stock kernel from b380+
2. Tick the option "Keep vendor partition mounted" inside OpenKirin Settings
3. download and install [URL="www.supersu.com/download"]official SuperSU[/URL]
4. Enjoy!
[B][U]2. Custom SuperSU[/U][/B]
1. Make sure the device running stock EMUI 5.x boot.img
2. flash this modded SuperSU 2.79: [URL="https://drive.google.com/open?id=0BxWP2gF_0Bd_UmQ2Zm9ZRGxBTUE"]download here[/URL]
3. enjoy root :)
[COLOR="red"][B]NOTE:[/B][/COLOR] this is for every device (except kirin 960 based) running emui 5.x without loop support.
[B][U]3. Magisk[/U][/B]
1. ensure you are running a kernel from b380 or later
2. flash magisk
3. enjoy root & safetynet (read note)
[B][COLOR="red"]NOTE:[/COLOR][/B] Magisk Hide is a known problem on Huawei/Honor devices.
Make sure you are not rebooting/turning off your device with Magisk Hide enabled!
You may face a broken fingerprint scanner, do not worry,
simply disable magisk hide and reboot - fps works again!
Downloads
Code:
[LIST]
[URL="https://github.com/OpenKirin/android_device_huawei_vie/releases/download/3.1.1-1/twrp-3.1.1-1-vie.img"][U]download twrp-3.1.1-1-vie.img[/U][/URL]
[/LIST]
FAQ
Code:
Q: What's the code status?
A: 10. June 2017
Q: which P9+ models are supported?
A: every model should be supported.
Q: Can i use this TWRP with decrypted /data?
yes, you can! (have a look at the instructions in FAQ)
Q: Can i install LOS or AOSP based roms with this TWRP?
yes, you can! (please follow the installing procedure in the corresponding rom thread)
Q: Can i install Magisk?
A: Every ROM based upon b380+ kernel should now include proper loop support.
Since 3.1.0-3 you are able to flash Magisk through TWRP (recovery kernel has been updated)
Q: Does official SuperSU work?
A: Yes, even though chainfire included a fix in his upcomming version,
you can use every version of it, just check the "Rooting Instructions" section.
Q: ETAs?
A: No.
Going back from decrypted -> encrypted?
Code:
1. Format /data inside of TWRP
2. Flash eRecovery & Kernel from your currently installed Stock ROM Build
3. Do a factory reset inside of eRecovery
5. Let device boot up
6. Install your current firmware hw_data package & SuperSU using TWRP again
Want to decrypt? No problem.
Code:
1. Format /data inside of TWRP
2. Flash a kernel with forceencrypt disabled
3. bootup your device
Special Thanks
Code:
* [URL="https://forum.xda-developers.com/member.php?u=2335078"]surdu_petru[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=7354786"]XePeleato[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=220328"]paulobrien[/URL]
XDA:DevDB Information
TWRP, Tool/Utility for the Huawei P9 Plus
Contributors
OldDroid, surdu_petru, xepeleato
Version Information
Status: Stable
Created 2017-04-04
Last Updated 2017-06-11

Reserved

any working twrp for emui 4,1 with decryption support?

Thx bro

Thx for this nice work @OldDroid
This twrp works fine and root too....

VIE-L29C185 does it work?
I think model device is convenient. is it correct? I will be happy if you give me information.

goksemozkan said:
I think model device is convenient. is it correct? I will be happy if you give me information.
Click to expand...
Click to collapse
It is working good on my VIE-L29C185B360! Go ahead, use it and enjoy....

Addymore said:
It is working good on my VIE-L29C185B360! Go ahead, use it and enjoy....
Click to expand...
Click to collapse
my friend. What supersu have you uploaded, give a link.
https://forum.xda-developers.com/p9/...t3565703/page4
DL: http://filestore.to/?d=B9J55H6X9F link empty

goksemozkan said:
my friend. What supersu have you uploaded, give a link.
https://forum.xda-developers.com/p9/...t3565703/page4
DL: http://filestore.to/?d=B9J55H6X9F link empty
Click to expand...
Click to collapse
For root, I flashed this supersu for emui5....in twrp provided up! Working like a charm...! Thx to @OldDroid

Addymore said:
For root, I flashed this supersu for emui5....in twrp provided up! Working like a charm...! Thx to @OldDroid
Click to expand...
Click to collapse
Thanks to all my friends, now root and supersu are working perfectly.
And I will definitely enjoy :good::good::good:

Now, start nel custom rom

Works perfectly on VIE-L29C636 , thank you!

Thank you so much man
successfully got TWRP and root on VIE-L29C185
Good job my friend

Hi,
How can I flash twrp in emui 7? I've tryed several tutorials but I can't do it.
Best Regards

SuperTamagochi said:
How can I flash twrp in emui 7? I've tryed several tutorials but I can't do it.
Click to expand...
Click to collapse
Have you unlocked the bootloader?

Hi guys. Sombody help me. How can i flash magisk on my p9 plus, i try many twrp, but everytime i see loop?

New release is up - TWRP 3.1.1-0 for P9 Plus.
Kernel should now support loop from b381 onwards.
Check OP for download link and github for more information!
P9 Plus Releases + Changelog
Regards

I'm sorry for the inconvenience but i forgot to exclude the special directory inside the /data partition during wipe/factory reset.
I've re-uploaded the fixed release, so everyone who had already installed 3.1.1-0 should now re-download and re-install.
Best regards

I'm sorry if this question has been asked somewhere else before, but can I flash an OTA update (extracted .zip) using TWRP, while keeping TWRP and SU?
It's quite bothersome to go back to full-stock, lock the bootloader, run the update, unlock the bootloader and root again, just for a minor update like B360 to B370.
I'm currently on B360 with TWRP 3.1.0 and SuperSU (rooted).

Rupert van da Cow said:
I'm sorry if this question has been asked somewhere else before, but can I flash an OTA update (extracted .zip) using TWRP, while keeping TWRP and SU?
It's quite bothersome to go back to full-stock, lock the bootloader, run the update, unlock the bootloader and root again, just for a minor update like B360 to B370.
I'm currently on B360 with TWRP 3.1.0 and SuperSU (rooted).
Click to expand...
Click to collapse
Hi, I can tell you in advance that NO, at least with an earlier version and that in principle it is only for normal P9.
Actually, you could only install that recovery, but with that I do not know what to tell you.
Anyway, due to the internal form of Huawei updates, they can not be installed since twrp, at least I have not been able to, nor anyone I know.
Sorry for my bad English, I do not know, and I use a translator.
Enviado desde mi VIE-L09 mediante Tapatalk

Stable Oxygen OS/Android 11 fastboot boot twrp.img lead to Qualcomm Crashdump

Hello,
My goal is to get an Android 11 Stable version with TWRP recovery and magisk root.
I cannot achieve this goal cause of an error - "Qualcomm crashdump" - i get when trying to boot into TWRP.IMG
Does anyone managed to install twrp recovery and root with Android 11 stable?
Thanks

BenoMosko said:
Hi!
First Thanks for the reply.
Second, I opened a thread just for that, maybe you can share your wisdom with us over there
Stable Oxygen OS/Android 11 fastboot boot twrp.img lead to Qualcomm Crashdump
Hello, My goal is to get an Android 11 Stable version with TWRP recovery and magisk root. I cannot achieve this goal cause of an error - "Qualcomm crashdump" - i get when trying to boot into TWRP.IMG Does anyone managed to install twrp...
forum.xda-developers.com
I dont have a T-Mobile OP6T i have a global device.
"it could work to set up a rooted OOS 10 (which should give you less trouble) and then use the method I described above to upgrade."
Can you share and give us step by step instruction please?
Which version should i be on with installing twrp recovery and root using magisk?
10.3.8?
10.3.12?
cant i do it straight from 11?
thanks.
Click to expand...
Click to collapse
I believe there's a rollback zip which could help you out. It's at the bottom of this article. Not sure if it works on stable. Note that it wipes everything!
scorpio76r said:
Yes, I have the T-Mobile which is internationally converted
Click to expand...
Click to collapse
TMO has not been very kind to development in any way. It may just take some time for modding to catch up or you may find a way. Much luck finding the answer I personally stay as far away from provider branded devices as I can

Timmmmaaahh! said:
I believe there's a rollback zip which could help you out. It's at the bottom of this article. Not sure if it works on stable. Note that it wipes everything!
TMO has not been very kind to development in any way. It may just take some time for modding to catch up or you may find a way. Much luck finding the answer I personally stay as far away from provider branded devices as I can
Click to expand...
Click to collapse
You are so correct. I will never purchase a carrier branded device again.

Timmmmaaahh! said:
I believe there's a rollback zip which could help you out. It's at the bottom of this article. Not sure if it works on stable. Note that it wipes everything!
TMO has not been very kind to development in any way. It may just take some time for modding to catch up or you may find a way. Much luck finding the answer I personally stay as far away from provider branded devices as I can
Click to expand...
Click to collapse
Hi,
I have the rollbacks and i can use mstool to do rollbacks to 10.3.8
that's not my issue.
Lets organize it.
I have a goal - OnePlus 6T with OOS11+TWRP+ROOT
can i achieve this goal?
if yes,
can u please give me details on how to achieve?
thanks.

BenoMosko said:
Hi,
I have the rollbacks and i can use mstool to do rollbacks to 10.3.8
that's not my issue.
Lets organize it.
I have a goal - OnePlus 6T with OOS11+TWRP+ROOT
can i achieve this goal?
if yes,
can u please give me details on how to achieve?
thanks.
Click to expand...
Click to collapse
This would also be helpful to people who are just purchasing this device which most likely will have the 11 update already

BenoMosko said:
Hi,
I have the rollbacks and i can use mstool to do rollbacks to 10.3.8
that's not my issue.
Lets organize it.
I have a goal - OnePlus 6T with OOS11+TWRP+ROOT
can i achieve this goal?
if yes,
can u please give me details on how to achieve?
thanks.
Click to expand...
Click to collapse
With an international version, I don't see any reason why it wouldn't work. After MSM'ing (whichever version) I'd first make sure it gets a working TWRP and Magisk root, then upgrade to latest 10 keeping the method I described in mind (to keep TWRP and root alive), then take the same step towards 11. I don't think it even matters which 10 is present, the full stable 11 zip will upgrade it either way. I was one (security) update behind.

Timmmmaaahh! said:
With an international version, I don't see any reason why it wouldn't work. After MSM'ing (whichever version) I'd first make sure it gets a working TWRP and Magisk root, then upgrade to latest 10 keeping the method I described in mind (to keep TWRP and root alive), then take the same step towards 11. I don't think it even matters which 10 is present, the full stable 11 zip will upgrade it either way. I was one (security) update behind.
Click to expand...
Click to collapse
Thank you so much for the support
"keeping the method I described in mind"
can you please copy paste it here?
and maybe do a little
1.
2.
3.
steps instructions please????????
thanks.

BenoMosko said:
Thank you so much for the support
"keeping the method I described in mind"
can you please copy paste it here?
and maybe do a little
1.
2.
3.
steps instructions please????????
thanks.
Click to expand...
Click to collapse
I already did
Timmmmaaahh! said:
That makes SafetyNet pass? I did the classic routine:
Install full zip (OnePlus6TOxygen_34.J.60) via 'Local upgrade' - no rebooting
Flash TWRP installer (I had 3.4.0-11) via Magisk - no rebooting
Flash Magisk via Magisk to other slot
Reboot! All done.
Click to expand...
Click to collapse

Timmmmaaahh! said:
I already did
Click to expand...
Click to collapse
Great, Thanks.
One more question...
when going back to 10.3.8 to install twrp, can i use the latest twrp version and not "3.4.0-11"?
thanks.

Timmmmaaahh! said:
I already did
Click to expand...
Click to collapse
Hi ..Will the twrp version 3.5.2-9 work too? Or do we have to use this version in your post?

Would flashing OOS 10 back clear all my data? Is there way to just install the TWRP and root it with magisk zip like we did earlier?

shreyas.kukde said:
Would flashing OOS 10 back clear all my data? Is there way to just install the TWRP and root it with magisk zip like we did earlier?
Click to expand...
Click to collapse
It has been a no go so far trying to get magisk and twrp on 11. I guess we will need to use the msm tool and,start from scratch

BenoMosko said:
Great, Thanks.
One more question...
when going back to 10.3.8 to install twrp, can i use the latest twrp version and not "3.4.0-11"?
thanks.
Click to expand...
Click to collapse
Libraplum76 said:
Hi ..Will the twrp version 3.5.2-9 work too? Or do we have to use this version in your post?
Click to expand...
Click to collapse
I really don't think versions are all that important. Try the latest one and work your way down from there? Best practice IMHO is just revisiting the TWRP thread when preparing to flash and check for any anomalies in OP and last 2 or 3 pages of the thread. Do the same for anything you need to flash (Magisk, OOS or custom ROM thread, etc.). More reading lowers the chances of failure.

Just use fastboot flash boot_a boot.img and preferably fastboot flash boot_b boot.img, instead of boot.img use beta3 prerooted and preinstalled with twrp boot image - you can find it somewhere on this forum in another section. Then just from fasboot boot to recovery and install oos11 again.

ppajdek said:
Just use fastboot flash boot_a boot.img and preferably fastboot flash boot_b boot.img, instead of boot.img use beta3 prerooted and preinstalled with twrp boot image - you can find it somewhere on this forum in another section. Then just from fasboot boot to recovery and install oos11 again.
Click to expand...
Click to collapse
You just brung hope, thank you. I will definitely go on the hunt for that recovery image*Edit, just found the link https://forum.xda-developers.com/t/...1-open-beta-2-and-open-beta-3-latest.4316563/

This has been solved for the oneplus 6t international converted on Oxygen 11 stable. Using the PRO3 file from the link I posted earlier (shout out to member KizuYuna who made and, provided the PRO3 file, also shout out to ppajdek for pointing me in the right direction ) I fastboot flash boot the file (simple drag and drop) it brought me to a twrp called pitch black( yaay! I had some form of twrp) while in there I flashed the 3.5.1_9-0 fajita installer zip. Next, I hit the power button in the pitch black twrp that gave me a option to reboot to recovery. Yaay, I rebooted to twrp 3,5.1_9-0. Next I flashed the latest 11 oxygen stable. After that I flashed the twrp installer again. After that, I rebooted to recovery (was glad I hadn't bricked by now) Next, I flashed magisk 23.0 and, lastly rebooted to system. (shocked that I didn't get a crash dump screen, lol) went into magisk and, enabled magisk hide. Here are pictures of the result, yaay. I did not post a picture of twrp, but yes it works and is present.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

scorpio76r said:
This has been solved for the oneplus 6t international converted on Oxygen 11 stable. Using the PRO3 file from the link I posted earlier (shout out to member KizuYuna who made and, provided the PRO3 file, also shout out to ppajdek for pointing me in the right direction ) I fastboot flash boot the file (simple drag and drop) it brought me to a twrp called pitch black( yaay! I had some form of twrp) while in there I flashed the 3.5.1_9-0 fajita installer zip. Next, I hit the power button in the pitch black twrp that gave me a option to reboot to recovery. Yaay, I rebooted to twrp 3,5.1_9-0. Next I flashed the latest 11 oxygen stable. After that I flashed the twrp installer again. After that, I rebooted to recovery (was glad I hadn't bricked by now) Next, I flashed magisk 23.0 and, lastly rebooted to system. (shocked that I didn't get a crash dump screen, lol) went into magisk and, enabled magisk hide. Here are pictures of the result, yaay. I did not post a picture of twrp, but yes it works and is present. View attachment 5384313View attachment 5384315
Click to expand...
Click to collapse
Great! Worked for me too. Thought I could never get Root or Twrp again.

scorpio76r said:
It has been a no go so far trying to get magisk and twrp on 11. I guess we will need to use the msm tool and,start from scratch
Click to expand...
Click to collapse
A telegram group titled OnePlus 6T Chat has a user who said he flashed latest TWRP and Latest Magisk and it worked for him. Strange..

shreyas.kukde said:
A telegram group titled OnePlus 6T Chat has a user who said he flashed latest TWRP and Latest Magisk and it worked for him. Strange..
Click to expand...
Click to collapse
Shocking, lol

scorpio76r said:
Shocking, lol
Click to expand...
Click to collapse
Can you provide the TWRP zip that you flashed?