Request to backup the Recovery partition before flashing it - P8lite Q&A, Help & Troubleshooting

Hi there,
before I flash my recovery partition, I want to secure it, is there any way?
"dd" is not possible without root permission. Is there any way with adb, or do I have to go the way about rooting through Kingroot/SuperSu first? (obsolete)
My Build-Number is
ALE-L21C432B194
The device is unlocked.
//Edit 1:
Kingroot cannot root my system, a request is running, but I think i will not wait for it.

i got something from cellebrite. it use "fastboot ome backdoor get" and "fastboot flash slock xxx",but i don't known what xxx is .

Related

How do you keep up with the updates after rooting your P8?

Afaik you loose the OTA updates after rooting (because of twrp) so how do you keep your system up to date? or is this somthing that you risk in order to root your phone
You can try to flash the stock recovery back and install the firmware manually or using the updater, or you find the firmware in flashible zip format and flash it through twrp. I personally rooted without keeping Twrp so i can still update.
Thanks for answering! And yeah the problemas is that I cant find the firmware updates anywhere, so how do I root without a custom recovery? Can you tell me some hints to find the solution or a link? Thanks again
EDIT: Oh, just found a way, and in case someone is also wondering heres how its done: You have to boot to twrp through adb, and then you can flash super su without flashing the custom recovery . This is the generic way to do it, have not tested im my P8 yet, will report later.
fede011 said:
Thanks for answering! And yeah the problemas is that I cant find the firmware updates anywhere, so how do I root without a custom recovery? Can you tell me some hints to find the solution or a link? Thanks again
EDIT: Oh, just found a way, and in case someone is also wondering heres how its done: You have to boot to twrp through adb, and then you can flash super su without flashing the custom recovery . This is the generic way to do it, have not tested im my P8 yet, will report later.
Click to expand...
Click to collapse
*No need to go through all the hassle there is an automated script which i used it myself if you are still on stock recovery, it installs Twrp to flash superSu and then restores the original recovery.
http://forum.xda-developers.com/p8l...otloader-root-p8-p8lite-t3164956#post62851688
*If you are on Twrp, you can download "Huawei update extractor" http://forum.xda-developers.com/showthread.php?t=2433454 use it to extract your firmware (update.app) and take from it the 'recovery.img'. Then go to platform-tools where you open the CMD from, place the recovery.img in it you can rename it to "stockrecovery.img"
then "shift+right click" open the command line.
type: adb reboot bootloader
type: adb devices ----->to see your device
type: fastboot flash recovery 'type hear the name of recovery'
example: flastboot flash recovery stockrecovery.img
type: fastboot reboot ----->reboot device
some tutorial i found on youtube:
https://www.youtube.com/watch?v=YfWYKREeQeQ
By the way the method for Twrp i haven't tested but that's the theory, so please do it on your own risk and do the required research. Goodluck:good:
Edit: Another method in theory if you have Twrp could be to use 'flashify' app https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en to flash the stock 'recovery.img' which you extracted from the stock firmware. No need to use adb.
Rashad83 said:
*No need to go through all the hassle there is an automated script which i used it myself if you are still on stock recovery, it installs Twrp to flash superSu and then restores the original recovery.
http://forum.xda-developers.com/p8l...otloader-root-p8-p8lite-t3164956#post62851688
*If you are on Twrp, you can download "Huawei update extractor" http://forum.xda-developers.com/showthread.php?t=2433454 use it to extract your firmware (update.app) and take from it the 'recovery.img'. Then go to platform-tools where you open the CMD from, place the recovery.img in it you can rename it to "stockrecovery.img"
then "shift+right click" open the command line.
type: adb reboot bootloader
type: adb devices ----->to see your device
type: fastboot flash recovery 'type hear the name of recovery'
example: flastboot flash recovery stockrecovery.img
type: fastboot reboot ----->reboot device
some tutorial i found on youtube:
https://www.youtube.com/watch?v=YfWYKREeQeQ
By the way the method for Twrp i haven't tested but that's the theory, so please do it on your own risk and do the required research. Goodluck:good:
Edit: Another method in theory if you have Twrp could be to use 'flashify' app https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en to flash the stock 'recovery.img' which you extracted from the stock firmware. No need to use adb.
Click to expand...
Click to collapse
I still haven't changed the bootloader so it will be easier, I was waiting for the email from huawei but never received, but with the link you provided I was able to get the code instantly (since my model GRA-UL10 isn't on the list) its late here so will try it tomorrow. But I have a final question, will be possible to flash SuperSU without flashing twrp? There is a command that lets you boot twrp without flashing I just don't want to reflash my bootloader unnecessarily, thanks in advance. After this I will probably post a guide since it is not easy to find everything in one place.
fede011 said:
I still haven't changed the bootloader so it will be easier, I was waiting for the email from huawei but never received, but with the link you provided I was able to get the code instantly (since my model GRA-UL10 isn't on the list) its late here so will try it tomorrow. But I have a final question, will be possible to flash SuperSU without flashing twrp? There is a command that lets you boot twrp without flashing I just don't want to reflash my bootloader unnecessarily, thanks in advance. After this I will probably post a guide since it is not easy to find everything in one place.
Click to expand...
Click to collapse
In order to root your device you need a custom recovery which gives you the ability to push files which is not possible with the stock recovery that's how i understand it. The script in the link i gave u automates the steps you have to do manually, if you are going to root the device using the command line you will need a su.zip to flash using twrp, and a twrp recovery image through which you will access the file system, and finally knowing the command lines to do it all which is all in all is a hassle. So booting into or flashing twrp isn't really a big deal (at least for me) as long as you have the stock recovery by the end of it all.

Need some help - Cant access TWRP and lost root while doing updating

Hey guys, with the release of the Android M update for OP2, i had flashed the new rom on my device. However, during the process of flashing the rom, i looked over a step, and didnt flash SuperSU in the process. Hence right now, i have no root nor SuperSU access on my OP2 running Android M.
Everything else seems to be working nicely, although i would really like to reobtain my root access. i have looked online for some options, but i thought the devs and members here could help me out as to what to do. should i undergo and do the entire root process again? Or will the process below be enough to help me regain root access :
"Download the TWRP or CWMR image for your device and save it into the same directory as the ADB / fastboot drivers
Boot into the bootloader. Key-combinations can be found here.
Open the Windows command or Mac terminal and navigate to the direction where the ADB / fastboot drivers are located
Execute the following command: fastboot flash recovery filename.img (with filename.img being the name of the recovery image you downloaded earlier)"
I'd really appreciate much help, as I'm pretty new to this stuff. Thanks!

Help Me Root This Thing! XT1575

I've done a lot of research on a reliable way to root my Moto X Pure Edition XT1575 and want someone to check my plan before I pursue this. I'm gonna download TWRP for Clark and superSU 2.78 and put them in the same folder and open up the command prompt in that folder. Then hook up to the PC and enter the following command "fastboot boot twrp.img" then I'm gonna replace the twrp.img with the name of the twrp file and backup to the SD. Then reboot into the bootloader again and flash twrp with fastboot "fastboot flash recovery twrp.img" then start recovery and go to reboot into recovery again to lock it in. Then I'm booting back into twrp and going to Advanced & Terminal and entering the following command "echo SYSTEMLESS=true>>/data/.superSU then back home then flash superSU 2.78.
Please correct me on everything that may be wrong. If there's a better way to root, tell me how to do it your way.
My device info:
Moto X Pure Edition XT1575 (clark)
Build# MPH24.49-18
Kernel version 3.10.84
Android version 6.0
Bootloader OxAo48
Sent from my Moto X Pure Edition
ElectroJoe said:
I've done a lot of research on a reliable way to root my Moto X Pure Edition XT1575 and want someone to check my plan before I pursue this. I'm gonna download TWRP for Clark and superSU 2.78 and put them in the same folder and open up the command prompt in that folder. Then hook up to the PC and enter the following command "fastboot boot twrp.img" then I'm gonna replace the twrp.img with the name of the twrp file and backup to the SD. Then reboot into the bootloader again and flash twrp with fastboot "fastboot flash recovery twrp.img" then start recovery and go to reboot into recovery again to lock it in. Then I'm booting back into twrp and going to Advanced & Terminal and entering the following command "echo SYSTEMLESS=true>>/data/.superSU then back home then flash superSU 2.78.
Please correct me on everything that may be wrong. If there's a better way to root, tell me how to do it your way.
My device info:
Moto X Pure Edition XT1575 (clark)
Build# MPH24.49-18
Kernel version 3.10.84
Android version 6.0
Bootloader OxAo48
Sent from my Moto X Pure Edition
Click to expand...
Click to collapse
You've researched well. Couple things: The command is "echo SYSTEMLESS=true>>/data/.supersu", you added capitols on supersu. Next your first command of "fastboot boot twrp.img (or whatever you rename the TWRP recovery image to)" will live boot TWRP, which for our device is not necessary. Live booting is essentially booting into a custom recovery environment without actually installing the recovery. This is useful for devices that DO NOT have factory images available, which allows you to make a backup in the live environment prior to altering your device. We have factory images and factory recovery images, so you can skip this step and go right into "fastboot flash recovery twrp.img (or again, whatever you rename the recovery image to). Then after the recovery flash from within fastboot, you must reboot into recovery using the button select options within fastboot or your recovery will be overwritten by the stock recovery. Upon first boot of TWRP you'll have an option to keep your device read only or read/write. I personally choose NOT to keep it read only, rather read/write, because I don't care about taking OTA's with a custom recovery, but this is up to you. Then you'll want the supersu.zip on your device already (you want the regular standard current version, not a modded one from here: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703), either on your internal or external sd. And yes, prior to flashing supersu enter the command in TWRP without quotes "echo SYSTEMLESS=true>>/data/.supersu" (this prevents the bootloop that our device gets when flashing supersu in systemless mode). And your good to go. I just did this a few weeks ago from clean fastboot flashing the latest factory image, works perfectly.
Now for some clarity, I'd like someone else to chime in on the TWRP command "echo SYSTEMLESS=true>>/data/.supersu" that has to be entered. I know for sure entering the command prior works, and roots properly, but I have also read that the latest 2.78 version of supersu does not require this. I'd really like someone that KNOWS FOR SURE (no opinions) if this step can now be bi-passed, or if our device requires and will always require this step now and in the future. This will help solve a ton of questions about this issue that are spread throughout the forums so users don't have to dig to get a simple answer.
Thanks for taking the time to educate me on this. I'm gonna give it a try in a few minutes. Will I be a developer if I get it right? Hahaha I'll let you know how it goes
Sent from my Moto X Pure Edition
annoyingduck said:
You've researched well. Couple things: The command is "echo SYSTEMLESS=true>>/data/.supersu", you added capitols on supersu. Next your first command of "fastboot boot twrp.img (or whatever you rename the TWRP recovery image to)" will live boot TWRP, which for our device is not necessary. Live booting is essentially booting into a custom recovery environment without actually installing the recovery. This is useful for devices that DO NOT have factory images available, which allows you to make a backup in the live environment prior to altering your device. We have factory images and factory recovery images, so you can skip this step and go right into "fastboot flash recovery twrp.img (or again, whatever you rename the recovery image to). Then after the recovery flash from within fastboot, you must reboot into recovery using the button select options within fastboot or your recovery will be overwritten by the stock recovery. Upon first boot of TWRP you'll have an option to keep your device read only or read/write. I personally choose NOT to keep it read only, rather read/write, because I don't care about taking OTA's with a custom recovery, but this is up to you. Then you'll want the supersu.zip on your device already (you want the regular standard current version, not a modded one from here: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703), either on your internal or external sd. And yes, prior to flashing supersu enter the command in TWRP without quotes "echo SYSTEMLESS=true>>/data/.supersu" (this prevents the bootloop that our device gets when flashing supersu in systemless mode). And your good to go. I just did this a few weeks ago from clean fastboot flashing the latest factory image, works perfectly.
Now for some clarity, I'd like someone else to chime in on the TWRP command "echo SYSTEMLESS=true>>/data/.supersu" that has to be entered. I know for sure entering the command prior works, and roots properly, but I have also read that the latest 2.78 version of supersu does not require this. I'd really like someone that KNOWS FOR SURE (no opinions) if this step can now be bi-passed, or if our device requires and will always require this step now and in the future. This will help solve a ton of questions about this issue that are spread throughout the forums so users don't have to dig to get a simple answer.
Click to expand...
Click to collapse
It worked! I'm rooted and looking for a stable rom with a lot of features and customizations that works with Verizon LTE. I also want viper4android. I'm glad I backed up because I tried flashing a viper4android zip and it caused my phone not to boot. It just sat at the unlocked bootloader warning so I just restored it. Evidently, I was supposed to unzip the file in esfile Explorer and install the apk. I think I also needed the selinux mode changer app.
What would I gain by installing a custom Kernel to my rooted stock rom? Can I even do that?
Sent from my XT1575 using Tapatalk
ElectroJoe said:
It worked! I'm rooted and looking for a stable rom with a lot of features and customizations that works with Verizon LTE. I also want viper4android. I'm glad I backed up because I tried flashing a viper4android zip and it caused my phone not to boot. It just sat at the unlocked bootloader warning so I just restored it. Evidently, I was supposed to unzip the file in esfile Explorer and install the apk. I think I also needed the selinux mode changer app.
What would I gain by installing a custom Kernel to my rooted stock rom? Can I even do that?
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Flash ViPER4Android from here, no SELinux changing app needed: http://forum.xda-developers.com/android/software/viperaudio-viperatmos-3-8-sq-driver-t3289075
As for custom kernel, Frankenclark. Features available is in the post: http://forum.xda-developers.com/moto-x-style/development/kernel-frankenclark-t3289939
annoyingduck said:
Now for some clarity, I'd like someone else to chime in on the TWRP command "echo SYSTEMLESS=true>>/data/.supersu" that has to be entered. I know for sure entering the command prior works, and roots properly, but I have also read that the latest 2.78 version of supersu does not require this. I'd really like someone that KNOWS FOR SURE (no opinions) if this step can now be bi-passed, or if our device requires and will always require this step now and in the future. This will help solve a ton of questions about this issue that are spread throughout the forums so users don't have to dig to get a simple answer.
Click to expand...
Click to collapse
I literally did this to a fresh MXPE two weeks ago... misspelled the filename so it wasn't recognized (it isn't supersy apparently), and flashed SuperSU 2.78-SR1, rebooted and stuck at boot logo for 20 minutes. Rebooted into TWRP and entered the correct echo command to create the .supersu file and reboot, it looped twice quickly and then went to the lockscreen after a 2-3 minutes.

[A2017U - B29] "Fastboot Flashing Unlock" returns "Unknown Command" in ADB

[A2017U - B29] "Fastboot Flashing Unlock" returns "Unknown Command" in ADB
Hi !
Quick info: I am not a novice when it comes to rooting / unlocking bootloader / installing TWRP or CWM / installing Xposed Frameworks, etc
I will make this short and sweet.
My Info :
- Axon 7 Gold - A2107U (US variant) with Update B29 installed (A2017UV1.0.0B29)
- Minimal ADB and Fastboot
- Windows 7 x64 Home premium
Here are the steps I have done:
1-
I installed the ADB drivers and Qualcomm WWAN drivers on my computer.
2-
Under Developers settings, I have enabled "OEM Unlocking".
3-
Using Axon7backup.exe, I created 2 backup files: "stock_recovery_backup.img" and "stock_boot_backup.img"
4-
Rebooted in bootloader using "adb reboot bootloader", (my device was listed). I first tried "fastboot oem unlock" then tried "fastboot flashing unlock", both returning "Unknown Command".
HERE IS WHERE I AM CONFUSED:
Normally, anyone would Unlock to bootloader THEN install TWRP, but from what I've seen with Axon7, some people say that Installing TWRP is "required" to unlock the bootloader.
I've seen some say that they have successfully rooted / unlocked bootloader with the B29 update, but I don't see any zip files or threads for the B29.
Could anyone enlighten me on the steps that I (and many others) have to do in order to Unlock the Bootloader and be able to install TWRP and Xposed Framework (and root).
Thank you !
Could anyone enlighten me on the steps that I (and many others) have to do in order to Unlock the Bootloader and be able to install TWRP and Xposed Framework (and root).
Thank you ![/QUOTE]
Ok so the long story short is that the bootloader is not unlockable out of the box. When ZTE released the bootloader unlock, they released a separate ota for it called B20_boot from B20 which modified the fastboot image. It didn't make sense for a lot of people for ZTE to release a separate OTA since it would not allow them to recieve future otas (such as B29) so they are working on a new bootloader unlock. So since you are on B29 and the bootloader is not unlockable out of the box and you cannot update to B20_boot since you are not on B20 this is what you do:
1) I am assuming you already have the tool downloaded since you used it to create the backup files so just follow the same instructions to boot into edl mode, then open a command window where the tool is located. Then execute:
Code:
axon7backup.exe
to start the tool and then
Code:
axon7root.exe -p # -r
where # is your COM Port # in Device Manager. The tool will flash the signed version of TWRP with ZTE's signature from the leaked firehose onto your Axon 7.
2)Hold down volume up and power to exit download mode and boot into recovery which should now be TWRP.
3) Download the bootloader unlock zip from @DrakenFX: https://www.androidfilehost.com/?fid=529152257862665656. Flashing the zip will replace your fastboot image with the one from B20_boot.
4) After you have flashed the zip, reboot to bootloader and just execute
Code:
fastboot oem unlock
and you are good to go!
^^The stock fastboot does not support the unlocking command. There's another fastboot image in the bootloader unlock thread that gets flashed first. *THEN* you can issue the unlock command.
I've been messing with android at least since late 2009 and have seen many variants of unlocking processes. This one is new for me too.
bkores said:
Ok so the long story short is that the bootloader is not unlockable out of the box. When ZTE released the bootloader unlock, they released a separate ota for it called B20_boot from B20 which modified the fastboot image. It didn't make sense for a lot of people for ZTE to release a separate OTA since it would not allow them to recieve future otas (such as B29) so they are working on a new bootloader unlock. So since you are on B29 and the bootloader is not unlockable out of the box and you cannot update to B20_boot since you are not on B20 this is what you do:
1) Go to this thread: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204. Download @tenfar's tool for A2017U B20(axon7root.exe not axon7backup.exe). There is no tool for B27 or B29 because the OP is no longer active but it will still work(I have tested.)
Click to expand...
Click to collapse
I see that the release a "axon7root-us-b27.zip" here: http://d-h.st/kRgq
"Uploaded By: tenfar
Uploaded On: 2016-09-19 23:10:07"
Should I use the B27 or follow the B20 method ?
EDIT: Should I do following command ?: reboot disemmcwp (to remove protect write, or it's no longer necessary? )
Boutchoo said:
I see that the release a "axon7root-us-b27.zip" here: http://d-h.st/kRgq
"Uploaded By: tenfar
Uploaded On: 2016-09-19 23:10:07"
Should I use the B27 or follow the B20 method ?
Click to expand...
Click to collapse
I edited my original answer. Since you already have axon7backup.exe you don't have to download the tool. And yes you should do "reboot disemmcwp" if you want to be able to make changes to /system
bkores said:
I edited my original answer. Since you already have axon7backup.exe you don't have to download the tool.
Click to expand...
Click to collapse
Nice ! TWRP is now installed !
I was wondering, if I backup my DATA only using TWRP and restore them after doing "fastboot oem unlock", will I be able to get my apps back without breaking my system ?
EDIT: After doing "Fastboot oem unlock", TWRP gives me "Mount: Decrypt Data: Enter Password:"...
EDIT2: Ok now Android is locked... it's asking me to enter a password *NEVER MIND- FORMATED CELL, NOW WORKS*
Edit3: Do I need to flash SuperSU or is it pre-packaged ?
Boutchoo said:
Nice ! TWRP is now installed !
I was wondering, if I backup my DATA only using TWRP and restore them after doing "fastboot oem unlock", will I be able to get my apps back without breaking my system ?
EDIT: After doing "Fastboot oem unlock", TWRP gives me "Mount: Decrypt Data: Enter Password:"...
EDIT2: Ok now Android is locked... it's asking me to enter a password
Click to expand...
Click to collapse
Did you just flash TWRP using -r or flashed the boot image as well using -b? Because if you just flashed TWRP the data decryption thing should not have happened. For some reason ZTE screwed up encryption to the point where if you backup data in TWRP with a pin/password/pattern enabled and then restore from it you will get a data decryption prompt where no password would work, not even your own. If you get this you have no choice but to wipe your data and then do either a Google restore during setup or use Titanium Backup(after you flash SuperSU) if you have it. In the future if you want to backup your data and until ZTE fixes it, you have to disable your pin/password/pattern first.
bkores said:
Did you just flash TWRP using -r or flashed the boot image as well using -b? Because if you just flashed TWRP the data decryption thing should not have happened.
Click to expand...
Click to collapse
I copy pasted your line "axon7root.exe -p 8 -r" only, did nothing else.
Also, do I need to flash SuperSU for the root or is it pre-packaged ?
Boutchoo said:
I copy pasted your line "axon7root.exe -p 8 -r" only, did nothing else.
Also, do I need to flash SuperSU for the root or is it pre-packaged ?
Click to expand...
Click to collapse
Flash SuperSU
bkores said:
Flash SuperSU
Click to expand...
Click to collapse
When I flash SuperSU-v2.78-201609011115.zip from my SD Card, it crashes TWRP.
Boutchoo said:
When I flash SuperSU-v2.78-201609011115.zip from my SD Card, it crashes TWRP.
Click to expand...
Click to collapse
You need SuperSU v2.65 as any other version will crash TWRP(no one knows why)
bkores said:
You need SuperSU v2.65 as any other version will crash TWRP(no one knows why)
Click to expand...
Click to collapse
Ah, I see. It's weird !
Also, what does flashing the boot (-b) does with the Axon 7 ? It's weird that only recovery (-r) is necessary.
Boutchoo said:
Ah, I see. It's weird !
Also, what does flashing the boot (-b) does with the Axon 7 ? It's weird that only recovery (-r) is necessary.
Click to expand...
Click to collapse
The modified boot image allows people without an unlocked bootloader to have root however if your bootloader is unlocked you should not do it as you will have the data decryption issue.
Boutchoo said:
When I flash SuperSU-v2.78-201609011115.zip from my SD Card, it crashes TWRP.
Click to expand...
Click to collapse
Try 2.65

there is a root method for ZE550KL W/ MARSH.?

AS TITLE
Install all adb drivers properly on your PC.
If you're on Marshmallow, this might help you to unlock your bootloader https://www.asus.com/zentalk/in/thread-116376-1-1.html it's a simple APK you can install on your phone.
Connect your phone to PC and reach it with adb.
Go into fastboot mode (adb reboot bootloader) and type from your cmd "fastboot oem device-info" i think is still a must to check if it worked properly.
If you're sure it's unlocked now, then flash root .zip file with TWRP, I did not flash TWRP on my ze500kl, so I think on ze550kl you can try to boot TWRP rather than flashing it as well (fastboot boot TWRPname.img), try to boot TWRP, because if you flash it there are chances to brick your phone (for example if TWRP isn't right for it), but if you try to just boot it i don't think you can damage your rom.
If you flash a root .zip file, make sure you made a full nandroid backup with twrp first, or at least to have an uninstaller .zip for it as well.. I recommend you to make a stock nandroid backup anyway before any kind of modding (espacially FLASHING).
I personally use Magisk superuser (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445).
I don't own a ze550kl, i own a ze500kl and this method perfectly works for me. As long as you can unlock your bootloader, i think you can flash the root without problems if you manage to boot into the proper TWRP version for ze550kl.

Categories

Resources