Hello there!
Following these steps, you'll be able to root your freshly marshmallowed P8 Lite.
The method was tested by several other users, with not just this model.
Requirements:
Huawei P8 Lite with the Chinese 6.0 Firmware
Unlocked bootloader
TWRP Recovery (Kirin Chipset)
Do you have everything above?
Good, here are the steps:
Go to THIS post, and download the attachment of it. (BETA-SuperSU-v2.67-SYSTEMMODE.zip)
Put this zip on your SD Card.
Boot into recovery and flash it.
That is all what you need to do.
Credits goes to: aufarxda for making the working zip, zirangua for trying and successfully rooting our device with this, and of course Chainfire for making rooting phones possible and easy.
Note:
If you tried with the official zips from Chainfire's thread, you should rooted your phone as well, but the root was lost after a few reboots.
At least it was like that for me.
The reason for this, Chainfire introduced a new way of rooting the phone, which called "systemless" root. It means, no modification is made to your /system partition, only to your boot image.
The install script of this zip checks for compatibility to do "systemless" root, and if it can do that, it'll do that.
However, with our device, something must be messed up with the boot image, because it seems to be resetting after few (or the first) reboots.
The downloaded zip was modified in a way, that the script only root your phone via the old method, modifying your /system partition.
The whole point to have a "systemless" root is not rerooting after every update, or system reset, however, it seems like it's not working well with our phone, so only the old method remains.
Twrp needed?
slimbullet said:
Twrp needed?
Click to expand...
Click to collapse
Yes, it's needed, and thanks for pointing this out.
How are flash in Recovery Mode? He gives 3 options: Reboot - Download new Version and Recovery - Shutdown!?
You have to flash TWRP by fastboot adb before.
TWRP is needed for flashing the zip files
daviddosa said:
Yes, it's needed, and thanks for pointing this out.
Click to expand...
Click to collapse
I did all of those steps and now i have blackscreen and my phone wont turn on....
I have twrt,unlockedbloader,beta 6.0,debugging etc and it dont work...
and the second boot animation missing
Surdyn said:
I did all of those steps and now i have blackscreen and my phone wont turn on....
I have twrt,unlockedbloader,beta 6.0,debugging etc and it dont work...
and the second boot animation missing
Click to expand...
Click to collapse
the same problem here
daviddosa said:
Hello there!
Following these steps, you'll be able to root your freshly marshmallowed P8 Lite.
The method was tested by several other users, with not just this model.
Requirements:
Huawei P8 Lite
Unlocked bootloader
TWRP Recovery (Kirin Chipset)
Do you have everything above?
Good, here are the steps:
Go to THIS post, and download the attachment of it. (BETA-SuperSU-v2.67-SYSTEMMODE.zip)
Put this zip on your SD Card.
Boot into recovery and flash it.
That is all what you need to do.
Credits goes to: aufarxda for making the working zip, zirangua for trying and successfully rooting our device with this, and of course Chainfire for making rooting phones possible and easy.
Note:
If you tried with the official zips from Chainfire's thread, you should rooted your phone as well, but the root was lost after a few reboots.
At least it was like that for me.
The reason for this, Chainfire introduced a new way of rooting the phone, which called "systemless" root. It means, no modification is made to your /system partition, only to your boot image.
The install script of this zip checks for compatibility to do "systemless" root, and if it can do that, it'll do that.
However, with our device, something must be messed up with the boot image, because it seems to be resetting after few (or the first) reboots.
The downloaded zip was modified in a way, that the script only root your phone via the old method, modifying your /system partition.
The whole point to have a "systemless" root is not rerooting after every update, or system reset, however, it seems like it's not working well with our phone, so only the old method remains.[/QUDo wee
Do wee need an sd card or it can be done witch the main storage?
Click to expand...
Click to collapse
not work stop Screen Takeoff and not star and restart
---------- Post added at 03:05 AM ---------- Previous post was at 02:52 AM ----------
blackscreen and my phone restart how fixed
daviddosa said:
Hello there!
Following these steps, you'll be able to root your freshly marshmallowed P8 Lite.
The method was tested by several other users, with not just this model.
Requirements:
Huawei P8 Lite
Unlocked bootloader
TWRP Recovery (Kirin Chipset)
Do you have everything above?
Good, here are the steps:
Go to THIS post, and download the attachment of it. (BETA-SuperSU-v2.67-SYSTEMMODE.zip)
Put this zip on your SD Card.
Boot into recovery and flash it.
That is all what you need to do.
Credits goes to: aufarxda for making the working zip, zirangua for trying and successfully rooting our device with this, and of course Chainfire for making rooting phones possible and easy.
Note:
If you tried with the official zips from Chainfire's thread, you should rooted your phone as well, but the root was lost after a few reboots.
At least it was like that for me.
The reason for this, Chainfire introduced a new way of rooting the phone, which called "systemless" root. It means, no modification is made to your /system partition, only to your boot image.
The install script of this zip checks for compatibility to do "systemless" root, and if it can do that, it'll do that.
However, with our device, something must be messed up with the boot image, because it seems to be resetting after few (or the first) reboots.
The downloaded zip was modified in a way, that the script only root your phone via the old method, modifying your /system partition.
The whole point to have a "systemless" root is not rerooting after every update, or system reset, however, it seems like it's not working well with our phone, so only the old method remains.
Click to expand...
Click to collapse
Hi this method work only with the chinese version (B535) on european version (B524) i got a bootloop ...
This happen to me
xander33 said:
Hi this method work only with the chinese version (B535) on european version (B524) i got a bootloop ...
This happen to me
Click to expand...
Click to collapse
so how do we root B524 now?
omid.quist said:
so how do we root B524 now?
Click to expand...
Click to collapse
Follow the tutorial on generale section provided by sokkoban the thead it s called [TUTORIAL] ...
how to recover after the boot loop ?? i tried this on the EU marshmallow and now im stuck !!
daviddosa said:
Hello there!
Following these steps, you'll be able to root your freshly marshmallowed P8 Lite.
The method was tested by several other users, with not just this model.
Requirements:
Huawei P8 Lite with the Chinese 6.0 Firmware
Unlocked bootloader
TWRP Recovery (Kirin Chipset)
Do you have everything above?
Good, here are the steps:
Go to THIS post, and download the attachment of it. (BETA-SuperSU-v2.67-SYSTEMMODE.zip)
Put this zip on your SD Card.
Boot into recovery and flash it.
That is all what you need to do.
Credits goes to: aufarxda for making the working zip, zirangua for trying and successfully rooting our device with this, and of course Chainfire for making rooting phones possible and easy.
Note:
If you tried with the official zips from Chainfire's thread, you should rooted your phone as well, but the root was lost after a few reboots.
At least it was like that for me.
The reason for this, Chainfire introduced a new way of rooting the phone, which called "systemless" root. It means, no modification is made to your /system partition, only to your boot image.
The install script of this zip checks for compatibility to do "systemless" root, and if it can do that, it'll do that.
However, with our device, something must be messed up with the boot image, because it seems to be resetting after few (or the first) reboots.
The downloaded zip was modified in a way, that the script only root your phone via the old method, modifying your /system partition.
The whole point to have a "systemless" root is not rerooting after every update, or system reset, however, it seems like it's not working well with our phone, so only the old method remains.
Click to expand...
Click to collapse
Hi Daviddosa you have installed chinese beta android 6 fw? On that firmware is camera with special light effects.. Can you make backup of that camera, and get it here, or copy complete camera sw? Thanks a lot!
Here is HwCamera.apk on Chinese version of MM 6.0
sokkoban said:
Here is HwCamera.apk on Chinese version of MM 6.0
Click to expand...
Click to collapse
thx. just put it in system apps? and replace the old one? because update wont work
sokkoban said:
Here is HwCamera.apk on Chinese version of MM 6.0
Click to expand...
Click to collapse
Thanks.. sadly it is not working. Just wondering why on chinese ROMs there is working light painting, but on EU ROMS no.
danvo01 said:
Thanks.. sadly it is not working. Just wondering why on chinese ROMs there is working light painting, but on EU ROMS no.
Click to expand...
Click to collapse
I'm wonderin too. But this is not only difference in Chinese ROM. On B524 not feature like Touch Plus, Smart Care, Mobile data traffic counter, HiCloud and many others
So my opinion is Chinese firmware is much better that European. For that I change my ALE-L21 to ALE-UL00
sokkoban said:
I'm wonderin too. But this is not only difference in Chinese ROM. On B524 not feature like Touch Plus, Smart Care, Mobile data traffic counter, HiCloud and many others
So my opinion is Chinese firmware is much better that European. For that I change my ALE-L21 to ALE-UL00
Click to expand...
Click to collapse
so.. do you think it is better to flash back chinese beta v 311 (?) instead of 524? I looked for more stable bluetooth connection, and now i see differences...
I never use Bluetooth. But Chinese version of 6.0 is B535
Related
Hi everyone
I recently updated to B609 and (as expected) my phone was un-rooted.
I decided it would be better for me to just install a ROM instead of waiting for a new way to ROOT every time a new OTA comes out. (I have seen some very interesting ones that include Xposed)
This would be the first time i install a ROM on one of my phones but i do know how to use custom recovery's and i will always keep a copy of a backup close so i can flash back when something goes wrong.
A problem i have with starting all of this: I can't seem to find a way to unlock the Bootloader on my phone.
I have looked online but i always get links for older versions/other phones/German stuff.
Second problem: The recovery. As far as i understand, there is no working TWRP for EMUI3.0. BUT there should be a working CMW recovery. Should i go fot CMW?
Third problem: Which ROM? There are 3 that grabbed my attention. Se7en-Rom (But it seems like it hasn't been updated in a while), My-RoM (which seems the most interesting for me at the moment) and Miui (which i just found out about). Which should i go with or should i use another one? I can already say that i want my phone Rooted and Xposed is something i would love to have back (since i used to have it on my previous phone).
Any advice and help would be appreciated
JellyFox said:
Hi everyone
I recently updated to B609 and (as expected) my phone was un-rooted.
I decided it would be better for me to just install a ROM instead of waiting for a new way to ROOT every time a new OTA comes out. (I have seen some very interesting ones that include Xposed)
This would be the first time i install a ROM on one of my phones but i do know how to use custom recovery's and i will always keep a copy of a backup close so i can flash back when something goes wrong.
A problem i have with starting all of this: I can't seem to find a way to unlock the Bootloader on my phone.
I have looked online but i always get links for older versions/other phones/German stuff.
Second problem: The recovery. As far as i understand, there is no working TWRP for EMUI3.0. BUT there should be a working CMW recovery. Should i go fot CMW?
Third problem: Which ROM? There are 3 that grabbed my attention. Se7en-Rom (But it seems like it hasn't been updated in a while), My-RoM (which seems the most interesting for me at the moment) and Miui (which i just found out about). Which should i go with or should i use another one? I can already say that i want my phone Rooted and Xposed is something i would love to have back (since i used to have it on my previous phone).
Any advice and help would be appreciated
Click to expand...
Click to collapse
I have a P7-L10 with B609. I was able to successfully root it with RootGenius. When you root it, the bootloader is unlocked at the same time. As far as I can tell, the root is 100%. As for CWM, you can get it from here:
http://forum.xda-developers.com/ascend-p7/development/mods-tweaks-kernels-recoverys-emui-2-3-t2966670
TWRP doesn't work with B609/emui3.0.
My L10 has faulty flash memory and won't accept a custom recovery, so I can't test CWM or any custom ROMs. Perhaps others can advise. Good luck!
arthios said:
I have a P7-L10 with B609. I was able to successfully root it with RootGenius. When you root it, the bootloader is unlocked at the same time. As far as I can tell, the root is 100%. As for CWM, you can get it from here:
http://forum.xda-developers.com/ascend-p7/development/mods-tweaks-kernels-recoverys-emui-2-3-t2966670
TWRP doesn't work with B609/emui3.0.
My L10 has faulty flash memory and won't accept a custom recovery, so I can't test CWM or any custom ROMs. Perhaps others can advise. Good luck!
Click to expand...
Click to collapse
RootGenius was the first thing i tried. It went up to 66% then i got an error but that was a fully Chinese version.
I just tried it again with the one i found by using Google and it goes up to 72%, then tells me that the root has failed.
Which version did you use?
This is what I used and it worked fine (root genius): http://forum.xda-developers.com/showthread.php?t=2789337
As for bootloader, as far as I know from, starting with firmware 133 (Emui 2.3) all devices have unlocked bootloader
CWM is the only custom recovery for the moment;
Did not try any custom ROM (I'm happy with stock ROM for the moment).
Cheers
ibeqa said:
This is what I used and it worked fine (root genius): http://forum.xda-developers.com/showthread.php?t=2789337
As for bootloader, as far as I know from, starting with firmware 133 (Emui 2.3) all devices have unlocked bootloader
CWM is the only custom recovery for the moment;
Did not try any custom ROM (I'm happy with stock ROM for the moment).
Cheers
Click to expand...
Click to collapse
That's the first one i tried out. The first few times it ended in an Error. I tried it again today and when my phone reboots during the process, RootGenius loses contact with my phone.
And there is a bootloader-ish thing, but the only options i have is reboot, factory reset and cache wipe.
JellyFox said:
That's the first one i tried out. The first few times it ended in an Error. I tried it again today and when my phone reboots during the process, RootGenius loses contact with my phone.
And there is a bootloader-ish thing, but the only options i have is reboot, factory reset and cache wipe.
Click to expand...
Click to collapse
Hmmm, strange problem. Assuming you have the latest version of HiSuite installed and your drivers are current, all I can suggest is trying again with RootGenius (I used version 1.8.7) with your firewall and antivirus disabled or perhaps trying with Vroot. If you do decide to try Vroot it probably won't work unless you disable your firewall and antivirus.
arthios said:
Hmmm, strange problem. Assuming you have the latest version of HiSuite installed and your drivers are current, all I can suggest is trying again with RootGenius (I used version 1.8.7) with your firewall and antivirus disabled or perhaps trying with Vroot. If you do decide to try Vroot it probably won't work unless you disable your firewall and antivirus.
Click to expand...
Click to collapse
I disabled my firewall and antivirus and gave RootGenius another try. Normally it goes up to 71% and gives me the error. Now it went to 71%, rebooted and then it gave me the error. The weird part is that right before i get the error, it says the installation is complete.
Moved on to Vroot (which is called Iroot now apparently) . It took a while longer but it wasn't able to do it either.
JellyFox said:
And there is a bootloader-ish thing, but the only options i have is reboot, factory reset and cache wipe.
Click to expand...
Click to collapse
Get in bootloader mode, if your bootloader is unlocked, it will be written and highlighted with red color. I will point out again, starting with firmware B133 (Emui 2.3) all bootloaders for L10 version (I don't know for Chinese versions) are unlocked
Cheers.
update to b615 and flash or just flash this >> http://forum.xda-developers.com/ascend-p7/development/b615-unlocked-boot-img-t3050926 and use rootgenius remove inmutable etc...
btw there is twrp for emui 3 which mostly work fine http://forum.xda-developers.com/showpost.php?p=59340975&postcount=208
Z!L0G80 said:
update to b615 and flash or just flash this >> http://forum.xda-developers.com/ascend-p7/development/b615-unlocked-boot-img-t3050926 and use rootgenius remove inmutable etc...
btw there is twrp for emui 3 which mostly work fine http://forum.xda-developers.com/showpost.php?p=59340975&postcount=208
Click to expand...
Click to collapse
I still didn't get the OTA for B615 yet but thank you for the recovery.
ibeqa said:
Get in bootloader mode, if your bootloader is unlocked, it will be written and highlighted with red color. I will point out again, starting with firmware B133 (Emui 2.3) all bootloaders for L10 version (I don't know for Chinese versions) are unlocked
Cheers.
Click to expand...
Click to collapse
You were right! (not that i every doubted you). I found the problem i had: For some reason, i couldn't boot in bootloader trough my phone BUT i was able to do it with 'adb reboot bootloader'. After making some idiotic mistakes and having to re-flash the stock ROM, I finally was able to install My-RoM v3.3, its rooted, i have Xposed so i am happy
So thank everyone for the help!
I've got a PRA-LX1 here, P8 lite 2017
I wanted to give Magisk (and then MagiskSU) a try, but it says it requires a stock boot image dump.
How to make one reliably for this model? I tried with twrp first, but it says it requires root to do so. Since I wanted to try if MagiskSU can root it, I am wondering now how to dump it without having root in the first place?
First of all, this is general for P8 Lite not 2017; after that magisk require the boot image dump only if you don't have a custom recovery.
you can flash the magisk zip from twrp.
ItalianWolf said:
First of all, this is general for P8 Lite not 2017; after that magisk require the boot image dump only if you don't have a custom recovery.
you can flash the magisk zip from twrp.
Click to expand...
Click to collapse
I'm sorry, I didn't see there is a different section for the 2017.
Yet, this doesn't answer the question at all - if I had a custom recovery installed I wouldn't have the need to ask that- obviously
Smirftsch said:
I'm sorry, I didn't see there is a different section for the 2017.
Yet, this doesn't answer the question at all - if I had a custom recovery installed I wouldn't have the need to ask that- obviously
Click to expand...
Click to collapse
You said that, from your first post:
Smirftsch said:
I've got a PRA-LX1 here, P8 lite 2017
...omississ... I tried with twrp first. ...
Click to expand...
Click to collapse
twrp it's a custom recovery.
Did you mean that you tried to install twrp and you failed? you have to unlock bootloader (i think the procedure it's like P8 Lite) than flash it.
I don't know if it's working, but you can give a try: download a full firmware then use huawei update extractor to extract the boot image and you're almost done.
ah, now I get the misunderstanding. Guess I was a bit unclear. On this phone I only have the twrp app so far, which refuses to do the backup without having root.
Thanks for the hint with the update extractor, will dig it and give it a try.
If there are other ways yet, always open for suggestions.
Smirftsch said:
ah, now I get the misunderstanding. Guess I was a bit unclear. On this phone I only have the twrp app so far, which refuses to do the backup without having root.
Thanks for the hint with the update extractor, will dig it and give it a try.
If there are other ways yet, always open for suggestions.
Click to expand...
Click to collapse
Did it work?
Hi
I have been following the thread for the linage os in the View 10 forum.
Several people have reported it working on Honor 9 Lite which is treble compatible, before I try it out however I wanted to be sure I could go back to my current rom which is the official LLD-L31 for the UK honor 9 lite.
My current build number is LLD-L31 8.0.0.121(C432)
What options do I have to restore if I don't like the rom I flash?
So far I have managed to pull the System & ODM folders to my pc. all except the Vendor file due to a permissions error.
Is this enough? Can I simply push these folders back? and at which point do I attempt the push? When booted/in recovery etc?
Otherwise, Is there an official or unofficial Huawei/Honor restore tool? or maybe a full rom I can flash? HiSuite says it has this function, but my device isn't listed.
Sorry for all the questions, it's been a while since I flashed a rom & it was always via TWRP I understand treble roms are flashed via the stock recovery though
jusumgeezer said:
Hi
I have been following the thread for the linage os in the View 10 forum.
Several people have reported it working on Honor 9 Lite which is treble compatible, before I try it out however I wanted to be sure I could go back to my current rom which is the official LLD-L31 for the UK honor 9 lite.
My current build number is LLD-L31 8.0.0.121(C432)
What options do I have to restore if I don't like the rom I flash?
So far I have managed to pull the System & ODM folders to my pc. all except the Vendor file due to a permissions error.
Is this enough? Can I simply push these folders back? and at which point do I attempt the push? When booted/in recovery etc?
Otherwise, Is there an official or unofficial Huawei/Honor restore tool? or maybe a full rom I can flash? HiSuite says it has this function, but my device isn't listed.
Sorry for all the questions, it's been a while since I flashed a rom & it was always via TWRP I understand treble roms are flashed via the stock recovery though
Click to expand...
Click to collapse
Search for Huawei ERecovery you may find something useful..
jusumgeezer said:
Hi
I have been following the thread for the linage os in the View 10 forum.
Several people have reported it working on Honor 9 Lite which is treble compatible, before I try it out however I wanted to be sure I could go back to my current rom which is the official LLD-L31 for the UK honor 9 lite.
My current build number is LLD-L31 8.0.0.121(C432)
What options do I have to restore if I don't like the rom I flash?
So far I have managed to pull the System & ODM folders to my pc. all except the Vendor file due to a permissions error.
Is this enough? Can I simply push these folders back? and at which point do I attempt the push? When booted/in recovery etc?
Otherwise, Is there an official or unofficial Huawei/Honor restore tool? or maybe a full rom I can flash? HiSuite says it has this function, but my device isn't listed.
Sorry for all the questions, it's been a while since I flashed a rom & it was always via TWRP I understand treble roms are flashed via the stock recovery though
Click to expand...
Click to collapse
I have the same model and have also been following the thread. My understanding, and hopefully someone will correct if wrong, is that with project treble GSI you're only overwriting, via fastboot, system.img partition, therefore if you want to return to your original I suspect you can do the same thing again and fastboot original.img with a factory reset.
There is a utility called huawei firmware finder which allows you to look for firmware. I tried it but can only find the LLD-AL10 8.0.0.100(C675CUSTC675D4) which i think is for the 4/64GB veresion or may even be for the huawei P smart. Until honor make the firmware available not sure what other options exist.
BTW it would help if you report back with any success/failures if you try it. Also interested in what this version Lineage OS is missing/not working, I think the camera still has some issues last i checked the thread.
xzyk said:
I have the same model and have also been following the thread. My understanding, and hopefully someone will correct if wrong, is that with project treble GSI you're only overwriting, via fastboot, system.img partition, therefore if you want to return to your original I suspect you can do the same thing again and fastboot original.img with a factory reset.
There is a utility called huawei firmware finder which allows you to look for firmware. I tried it but can only find the LLD-AL10 8.0.0.100(C675CUSTC675D4) which i think is for the 4/64GB veresion or may even be for the huawei P smart. Until honor make the firmware available not sure what other options exist.
BTW it would help if you report back with any success/failures if you try it. Also interested in what this version Lineage OS is missing/not working, I think the camera still has some issues last i checked the thread.
Click to expand...
Click to collapse
Thanks for the reply, I suspected that's how it worked, just flash back the original system image.
I think I'm gonna hang fire for the time being until I know I have the correct firmware to go back if needed, hopefully the camera will be sorted by then too.
I flashed a firmware today and couldn't revert to stock because can't find it. Any ideas?
evolucja said:
I flashed a firmware today and couldn't revert to stock because can't find it. Any ideas?
Click to expand...
Click to collapse
When you unlocked your bootloader and before you overwrote your system partition you should have taken a backup of your stock system partition so you can restore it. Honor has not made the firmware available yet as far as I know.
xzyk said:
When you unlocked your bootloader and before you overwrote your system partition you should have taken a backup of your stock system partition so you can restore it. Honor has not made the firmware available yet as far as I know.
Click to expand...
Click to collapse
Just in case I decide to try this, how do I get a flashable file?
I pulled the contents of system + odm via ADB but just ended up with 2.3GB of folders.
Can I convert this to a flashable .img file? Or should I have done this another way?
jusumgeezer said:
Just in case I decide to try this, how do I get a flashable file?
I pulled the contents of system + odm via ADB but just ended up with 2.3GB of folders.
Can I convert this to a flashable .img file? Or should I have done this another way?
Click to expand...
Click to collapse
found description for how to do it for v10 on another site:
adb shell
su
dd if=/dev/block/bootdevice/by-name/system of=/storage/emulated/0/system.img
this implies root is required so I guess you would:
1. unlock bootloader
2. load TWRP.
3. load root (su).
4. reboot back into TWRP and save system.img.
However, you make it work you need to make sure system.img is saved before any changes are made.
xzyk said:
found description for how to do it for v10 on another site:
adb shell
su
dd if=/dev/block/bootdevice/by-name/system of=/storage/emulated/0/system.img
this implies root is required so I guess you would:
1. unlock bootloader
2. load TWRP.
3. load root (su).
4. reboot back into TWRP and save system.img.
However, you make it work you need to make sure system.img is saved before any changes are made.
Click to expand...
Click to collapse
I was thinking about this today & came to the same conclusion.
The idea is to pull a clean unmodified system image, but the only way to do that is by using root privileges SU, then via TWRP - Does that not make it a modified image?
Maybe I'm thinking about it too much:silly:
What Root method & TWRP versions have Honor 9 Lite users had success with? I'm keen to give this a go
jusumgeezer said:
I was thinking about this today & came to the same conclusion.
The idea is to pull a clean unmodified system image, but the only way to do that is by using root privileges SU, then via TWRP - Does that not make it a modified image?
Maybe I'm thinking about it too much:silly:
What Root method & TWRP versions have Honor 9 Lite users had success with? I'm keen to give this a go
Click to expand...
Click to collapse
Not TWRP as that is the recovery partition (recovery.img) not the system partition (system. Img). Not sure about root though as i believe that does add stuff in one, or more, of the system sub folders, maybe someone else can confirm, but if you're using superuser then unzipping that should tell you what's being added and where. However, if you think about it, this has always been a bit of an issue with any android. You cannot take a nandroid backup without some kind of custom recovery so how can you ever take a snapshot of the stock rom. Specialised tools can do it as they can dump the entire rom but how can any android be dumped in full straight out of the box without first changing something.?
You could try this:
https://9to5google.com/2017/11/04/how-to-backup-restore-android-device-data-android-basics/
but it never really worked properly for me.
jusumgeezer said:
I was thinking about this today & came to the same conclusion.
The idea is to pull a clean unmodified system image, but the only way to do that is by using root privileges SU, then via TWRP - Does that not make it a modified image?
Maybe I'm thinking about it too much:silly:
What Root method & TWRP versions have Honor 9 Lite users had success with? I'm keen to give this a go
Click to expand...
Click to collapse
xzyk said:
Not TWRP as that is the recovery partition (recovery.img) not the system partition (system. Img). Not sure about root though as i believe that does add stuff in one, or more, of the system sub folders, maybe someone else can confirm, but if you're using superuser then unzipping that should tell you what's being added and where. However, if you think about it, this has always been a bit of an issue with any android. You cannot take a nandroid backup without some kind of custom recovery so how can you ever take a snapshot of the stock rom. Specialised tools can do it as they can dump the entire rom but how can any android be dumped in full straight out of the box without first changing something.?
You could try this:
https://9to5google.com/2017/11/04/how-to-backup-restore-android-device-data-android-basics/
but it never really worked properly for me.
Click to expand...
Click to collapse
Guys TWRP Test Alpha build booted in Honor 9 Lite.
Tonight Stable build with all TWRP features is going to release in XDA i hope so.
Credits to @XePeleato - Team OpenKirin
VigneshS007 said:
Guys TWRP Test Alpha build booted in Honor 9 Lite.
Tonight Stable build with all TWRP features is going to release in XDA i hope so.
Credits to @XePeleato - Team OpenKirin
Click to expand...
Click to collapse
Great, that's good news. Please report back with a link so we can all share. Thanks.
Thanks for the replies everyone.
Great news about TWRP too, I look forward to trying it out.
Hi,
I am very new to this android world so my queries might feel stupid. Actually i m here after 3 years and that is very long period in this world. I know about rooting(super Su), bootloader and recovery (stock,CM and TWRP) . Recently read about Magisk and got some queries. Hope you will help me out. These are not device specific but need to learn.
What i read/study i found these readings...
1. Magisk roots device systemlessly (does not touch system partition) so one can get OTA updates easily.
2.To install and run Magisk one needs to unlock the bootloader .
3.(Device Specific) My redmi MI Flash tool says,If you unlock the bootloader , you wont get OTA updates.
4.I have previously rooted my galaxy Y and uninstalled system apps. If i delete sys apps from magisk,still can we say that we are not touching system.
So all statements are true? or some? or none ?
Here my device is redmi 3s (6.0.1- MIUI 9.6.1.0 Global Stable).All these queries are just in relation to OTA system updates. Nothing related to warranty.
Thanking You
Yes.
Yes.
Don't know about Xiaomi, but I've never had issues with OTA on a device with an unlocked bootloader (I've mainly used different Google and Oneplus devices). Someone with a Xiaomi is gonna have to chime in on this one.
As long as you use Magisk's debloating feature of replacing files or directories with empty ones, you're good. The actual /system partition won't be touched. Use a module like the Debloater module by @veez21, or make a debloater module yourself.
Didgeridoohan said:
Don't know about Xiaomi, but I've never had issues with OTA on a device with an unlocked bootloader (I've mainly used different Google and Oneplus devices). Someone with a Xiaomi is gonna have to chime in on this one.
Click to expand...
Click to collapse
Ahh, Thank You.
You get OTA system updates for your STOCK ROM ?
inwell said:
Ahh, Thank You.
You get OTA system updates for your STOCK ROM ?
Click to expand...
Click to collapse
Yes. But, having both Magisk and a custom recovery (an OTA won't install with a modified boot image and a custom recovery installed) I always find it easier to download the update and flash it manually. But, like I said, I have no idea if this is true for Xiaomi.
1. Ok. i also heared that when you update your device,you lose root...not true ? Or you need to root again ?
2.In normal stock device,we get update notification and we downlaod then restart (as per convenience)device to update.
If i remove some system apps from my rooted device and unroot the device,manage to get stock recovery back ,will the OTA update system treat my device as Stock-untouched? And install updates just as stock device will do ?
3. Is boot.img and bootloader are same things? Coz i read that for re locking boot loader you need to flash boot.img from stock software. (But Some procedures just use fastboot and relock oem command-they wont use boot.img,dont know why )
I read that unrooting,restoring stock recovery and locking bootloader again is more difficult/complicated than the rooting procedure
Some one should come up with solution just like Windows Restore .If you want to go back to everything STOCK,just use that feature same as done to Restore Windows in its previous state.
Any update that also updates the boot image (which means pretty much all) will remove root. But, that's just a simple case of reflashing Magisk right after applying the update.
If you've touched /system in any way, removing system apps or even just mounting the /system partition read-write, an OTA will fail. To be able update with an OTA your /system and /vendor partitions need to be untouched and you need to have the stock boot image and stock recovery installed. If your device doesn't conform to this the OTA will fail.
Boot image and bootloader are not the same thing. That you can read up on all over the internet, so I won't go into details. If you have done any kind of modifications on your device, I suggest you leave your bootloader unlocked. It's to easy to mess things up otherwise.
Going back to full stock is usually just a matter of flashing a full factory image/firmware package/stock ROM. Quite easy... Of course, some manufacturers make it harder than others.
Didgeridoohan said:
Boot image and bootloader are not the same thing. That you can read up on all over the internet, so I won't go into details. If you have done any kind of modifications on your device, I suggest you leave your bootloader unlocked. It's to easy to mess things up otherwise.
Click to expand...
Click to collapse
Ok. As you say the two are different , but can you explain in simple words (terms) that how they both are related/linked/connected? Coz as i read some forums/posts i get to read
1. To relock/lock bootloader you need to flash boot.img which suggests these (terms) are linked/connected.
2. but same time some forums/post suggest no img file flashing but just a fastboot command(s) to relock bootloader. In this case it seems they are not linked/connected.
And if the above 2 statements are true and device specific then how the bootloader and boot image are linked and not linked in diff devices? what changes are made so that in some cases these are linked and in some not
Sorry for asking too much. But you were really very kind to help me out.Thank you once again
I'm not 100% accurate (and someone will hopefully come I'm and correct me if needed), but basically the bootloader checks that everything is alright and then starts up your device. After that the boot image (ramdisk and kernel) takes over. Ramdisk basically makes sure all the partitions are mounted, and the kernel is exactly what it sounds like. The core of the OS, making sure that everything is working as it should.
This is of course a huge over-simplification, so if you want more you'll have to search around (and there are tons of resources around the web).
The main reason I can think of right at the moment for wanting to flash a boot image before locking the bootloader is that it's generally a good idea to have your device fully stock and functional before doing so. After you've locked the bootloader there might not be any going back if things start acting up and you could end up with a nice paperweight.
Questions are good. That's how you learn. I do believe that you'd be much better of searching around the internet for your answers. They've been put out there many, many times.
Ok.Thank you very much.I will learn more ...
I rooted the e5 plus using this method: https://forum.xda-developers.com/mo...o-e5-plus-rhannah-backup-magisk-root-t3822702
This was different from what I'm used to as normally TWRP replaces the stock recovery and then root is applied. Here, TWRP is only used in fastboot and not applied permanently.
A couple of questions:
Since recovery is not replaced, can this device receive OTA updates with no issues?
Can a normal factory reset be done without soft bricking the device?
If I want to install zip files for mods etc, can I use the fastboot temp TWRP to do this and it will still work?
Are there any actions/caveats that should be done or avoided with this TWRP method?
Excuse my ignorance but I'm sure someone else may have the same question and I'd rather not brick my device.
Thank you.
shezzy83 said:
I rooted the e5 plus using this method: https://forum.xda-developers.com/mo...o-e5-plus-rhannah-backup-magisk-root-t3822702
This was different from what I'm used to as normally TWRP replaces the stock recovery and then root is applied. Here, TWRP is only used in fastboot and not applied permanently.
A couple of questions:
Since recovery is not replaced, can this device receive OTA updates with no issues?
Can a normal factory reset be done without soft bricking the device?
If I want to install zip files for mods etc, can I use the fastboot temp TWRP to do this and it will still work?
Are there any actions/caveats that should be done or avoided with this TWRP method?
Excuse my ignorance but I'm sure someone else may have the same question and I'd rather not brick my device.
Thank you.
Click to expand...
Click to collapse
OTA won't work if rooted, you'll have to flash stock boot or flash full stock ROM.
Flashing twrp causes issues because of avb and dm-verity
TWRP won't have access to data because of encryption and won't be able to write to system.
Basically you're only booting twrp to make a backup and then use Magisk to patch your boot.img for root. From there you can install magisk modules and Xposed as well as any apps you use that need root.
You might use the TWRP installer within Android to install TWRP but it didn't boot for me on my E5 Plus.
reaper-death said:
Basically you're only booting twrp to make a backup and then using Magisk to patch your boot.img for root.
.
Click to expand...
Click to collapse
Ok so that's the answer I was looking for. TWRP is ONLY for backing up in our case since it doesn't have access. Therefore, none of what I asked about will work.
shezzy83 said:
Ok so that's the answer I was looking for. TWRP is ONLY for backing up in our case since it doesn't have access. Therefore, none of what I asked about will work.
Click to expand...
Click to collapse
These Moto e5 + posts have become pointless.
No method works and if root does work it will have issues. The original poster can't fix the issue because they don't know what they are talking about half the time.
We need better people on here who can make a video or explain how to do this without ****ing with our heads ?
Like a person who knows what they are doing with that exact phone model and are not just saying **** for a post ?
Contact me if you need real help fixing these people's mistakes [not root] "fix a bricked phone"!