I've read some other posts on how to root this phone, but in my mind, it doesn't seem specific enough. Even though this phone was $90, I really don't want to screw up the process.
If it's still too complicated to root the device, I'd be happy with being able to get TWRP going.
You may lose all data, pictures, etc. Back up what you need first.
Step by step guide:
1) Unlock your bootloader. See https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a for instructions, If your bootloader cannot be unlocked, then STOP. If it can be unlocked, you will now have an unlock code.
2) You will need ADB for the next step. You can Google Minimal ADB and use that. Use "fastboot oem unlock CODE" where you use the code obtained above.
3) You now have an unlocked phone, without these steps you cannot proceed further. The TWRP variation that you use depends on the type of phone processor you have. There are TWRP variants for both Qualcomm (https://forum.xda-developers.com/moto-e4-plus/development/twrp-twrp-moto-e4-plus-qualcomm-t3697154) and for Mediatek (https://forum.xda-developers.com/mo...rp-ported-twrp-recovery-moto-e4-plus-t3667559) Be sure to use the right one. Download to your ADB directory.
4) I put the Magisk.zip (for Root) and the Magisk Manager on my phone first. Links are here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
5) Back to ADB. Command is "fastboot flash recovery YOURIMAGENAME.IMG" The name of the Recovery image will vary depending on which one you downloaded.
6) TWRP should now be installed. Use the ADB command "ADB reboot recovery" and you should be at the TWRP screen. Flash the Magisk zip. Reboot the phone (and that will take a bit.)
7) You are basically done, but install the Magisk Manager APK to get updates.
You should now have an unlocked and rooted phone.
I believe that the Amazon E4 Plus phones already are unlocked because the bootloader was already unlocked in developer options
CarLover014 said:
I believe that the Amazon E4 Plus phones already are unlocked because the bootloader was already unlocked in developer options
Click to expand...
Click to collapse
I have never seen a new phone come with Developer options enabled, let alone OEM unlocked. Also, when you say an "Amazon phone" if you mean one with Amazon ads enabled, those have a locked bootloader.
But no point in debating. Go to ADB and type "fastboot oem device-info" and that will give you the status.
Everything goes seemingly well until I do "adb reboot recovery". Then I get "error: device not found". What am I doing wrong here?
Zexter said:
Everything goes seemingly well until I do "adb reboot recovery". Then I get "error: device not found". What am I doing wrong here?
Click to expand...
Click to collapse
If you haven't done so, try installing these drivers: http://drivers.softpedia.com/get/MO...a-Device-Manager-Android-USB-Driver-254.shtml
koop1955 said:
If you haven't done so, try installing these drivers: http://drivers.softpedia.com/get/MO...a-Device-Manager-Android-USB-Driver-254.shtml
Click to expand...
Click to collapse
I've installed the drivers. I can can transfer files n what not. Twrp also runs when booting it but not when flashing it. I get the "device not found" error message. I did end up rooting by just running twrp instead of flashing it, but would like to get it flashed.
Zexter said:
I've installed the drivers. I can can transfer files n what not. Twrp also runs when booting it but not when flashing it. I get the "device not found" error message. I did end up rooting by just running twrp instead of flashing it, but would like to get it flashed.
Click to expand...
Click to collapse
1) You can have your phone recognized by your computer as an MTP (letting you transfer files), but not under ADB. Those are two different things. The drivers that I linked to, along with Minimal ADB, should get your phone recognized under both.
2) If your phone is rooted and you have TWRP installed, then you don't need to do more. But if you follow the steps above, you will get ADB to recognize your phone.
koop1955 said:
1) You can have your phone recognized by your computer as an MTP (letting you transfer files), but not under ADB. Those are two different things. The drivers that I linked to, along with Minimal ADB, should get your phone recognized under both.
2) If your phone is rooted and you have TWRP installed, then you don't need to do more. But if you follow the steps above, you will get ADB to recognize your phone.
Click to expand...
Click to collapse
I was able to get root by just booting into twrp but couldnt get twrp flasdhed. However, I did a repair install of the drivers from the link u provided and was able to get it flashed.
Ty much!
Zexter said:
I was able to get root by just booting into twrp but couldnt get twrp flasdhed. However, I did a repair install of the drivers from the link u provided and was able to get it flashed.
Ty much!
Click to expand...
Click to collapse
You are welcome! Cheers!
koop1955 said:
You may lose all data, pictures, etc. Back up what you need first.
Step by step guide:
1) Unlock your bootloader. See https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a for instructions, If your bootloader cannot be unlocked, then STOP. If it can be unlocked, you will now have an unlock code.
2) You will need ADB for the next step. You can Google Minimal ADB and use that. Use "fastboot oem unlock CODE" where you use the code obtained above.
3) You now have an unlocked phone, without these steps you cannot proceed further. The TWRP variation that you use depends on the type of phone processor you have. There are TWRP variants for both Qualcomm (https://forum.xda-developers.com/moto-e4-plus/development/twrp-twrp-moto-e4-plus-qualcomm-t3697154) and for Mediatek (https://forum.xda-developers.com/mo...rp-ported-twrp-recovery-moto-e4-plus-t3667559) Be sure to use the right one. Download to your ADB directory.
4) I put the Magisk.zip (for Root) and the Magisk Manager on my phone first. Links are here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
5) Back to ADB. Command is "fastboot flash recovery YOURIMAGENAME.IMG" The name of the Recovery image will vary depending on which one you downloaded.
6) TWRP should now be installed. Use the ADB command "ADB reboot recovery" and you should be at the TWRP screen. Flash the Magisk zip. Reboot the phone (and that will take a bit.)
7) You are basically done, but install the Magisk Manager APK to get updates.
You should now have an unlocked and rooted phone.
Click to expand...
Click to collapse
never mind i am an idiot... i downloaded the source code... i found the downloads tab... *face palm*
can ya root it without installing twrp?? i dont want nor need it. I just want it rooted.
thanks for the guide. So the "no-verity-opt-encrypt" file is not needed no matter what kind of moto e plus it is right? also what happens if I let the motorola update by mistake (the motorola update service that always wants to run system update)? will that unroot the phone?
---------- Post added at 04:33 AM ---------- Previous post was at 04:01 AM ----------
koop1955 said:
You may lose all data, pictures, etc. Back up what you need first.
Step by step guide:
You should now have an unlocked and rooted phone.
Click to expand...
Click to collapse
thanks for the guide. So the "no-verity-opt-encrypt" file is not needed no matter what kind of moto e plus it is right? also what happens if I let the motorola update by mistake (the motorola update service that always wants to run system update)? will that unroot the phone?
and do I need to update Magisk Manager all the time? what does the updates do (I think Magisk Manager houses supersu which is the thing that grants root access to apps that require it?_
hello, I don't know what to do when im trying to know if my device is unlockable like I installed everything but im stuck on step 2 like I open a command prompt and type in the command but it says unknown command
I have Motorola MOTO E4 PLUS(XT1770).
I don't know how to go back default setting in engineering mode?
Actually i modified the mtk engineering settings(telephony) and in result i get my volte is not working.
Can anyone have Motorola MOTO E4 Plus default setting of engineering mode. If anyone have please post ss of full engineering mode settings (telephony).
Sorry my english is weak!
Please guys!!!!!!
HELP ME
Sent from my Moto E4 Plus using XDA Labs
MrCelcol said:
im stuck on step 2 like I open a command prompt and type in the command but it says unknown command
Click to expand...
Click to collapse
Did you install fastboot?
Are you running in the right directory?
Any app so we can root without twrp or other rom's??
Edit:Kingroot and Kingoroot both show root failed
Sent from my Moto E (4) Plus using Tapatalk
SpeedFreak905 said:
Any app so we can root without twrp or other rom's??
Edit:Kingroot and Kingoroot both show root failed
Sent from my Moto E (4) Plus using Tapatalk
Click to expand...
Click to collapse
Not happening. At all. Need TWRP..
Thanks buddy
bcrichster said:
Not happening. At all. Need TWRP..
Click to expand...
Click to collapse
Sent from my Moto E (4) Plus using Tapatalk
Related
Hi,
I managed to unlock the Bootloader on my Moto G 2nd dual sim. Now I'm looking for a step to step how to to root my phone.
There are so many (confusing) how to's out there
I'm using Marshmallow.
Took me a while to find instructions for non Windows user to unlock bootloader ...so a step by step Linux how to would be appreciated.
thanks in advance,
Best, Martin
da.cappo said:
Hi,
I managed to unlock the Bootloader on my Moto G 2nd dual sim. Now I'm looking for a step to step how to to root my phone.
There are so many (confusing) how to's out there
I'm using Marshmallow.
Took me a while to find instructions for non Windows user to unlock bootloader ...so a step by step Linux how to would be appreciated.
thanks in advance,
Best, Martin
Click to expand...
Click to collapse
As long as you have your adb and fastboot tools installed on your computer, as well as the drivers you need for the moto g2, the steps are the same for both windows and Linux. To root:
1. Flash twrp version 3.0.0.0
Download the file, place in your fastboot folder, and then open a command window in that folder. Type : fastboot flash recovery twrp.img
2. Using TWRP, install SuperSU v2.62 only.
3. (Optional)Boot your rom up and update SuperSU to version 2.65 using the play store.
That's all you need to get root access.
Viren said:
As long as you have your adb and fastboot tools installed on your computer, as well as the drivers you need for the moto g2, the steps are the same for both windows and Linux. To root:
1. Flash twrp version 3.0.0.0
Download the file, place in your fastboot folder, and then open a command window in that folder. Type : fastboot flash recovery twrp.img
2. Using TWRP, install SuperSU v2.62 only.
3. (Optional)Boot your rom up and update SuperSU to version 2.65 using the play store.
That's all you need to get root access.
Click to expand...
Click to collapse
that doesnt work, you ned a modified boot.img or it gets stuck in a bootloop. why attempt to answer a question you clearly dont know the answer to?
dcroz said:
that doesnt work, you ned a modified boot.img or it gets stuck in a bootloop. why attempt to answer a question you clearly dont know the answer to?
Click to expand...
Click to collapse
1. You do not need a modified boot image, SuperSU will modify the boot image for you.
2. I answered your question because I've done the above hundreds of times before.
3. I do realise that I'm replying many months later than when you posted, but XDA only informed me of your reply just now.
So, I have decided on rooting my Xperia Z3 Compact so that I can finally move OBB to SD card, however I have no knowledge of how roots work (not a programmer much), or which one to pick. I have seen quite a few options for different roots, and previously used Kingo root, but seeing the post about it I am avoiding it like a forest fire. Anyone got good suggestions on which one to pick for my Xperia z3 compact?
In modern Android the phone's security systems prevent rooting via one click apps unless the device is unlocked. The best/safest way to root is to flash custom recovery such as TWRP and then install SuperSU.zip from TWRP. Make sure you make a backup first just in case.
You will most likely have to unlock your bootloader before you can flash TWRP. SONY devices are usually pretty Dev friendly, so you shouldn't have too much trouble finding everything you need. Good luck.
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
In modern Android the phone's security systems prevent rooting via one click apps unless the device is unlocked. The best/safest way to root is to flash custom recovery such as TWRP and then install SuperSU.zip from TWRP. Make sure you make a backup first just in case.
You will most likely have to unlock your bootloader before you can flash TWRP. SONY devices are usually pretty Dev friendly, so you shouldn't have too much trouble finding everything you need. Good luck.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Erm can you explain it so that I will understand it? XD
I kind of understand what you mean but I am still confused here and there....
GarrusN7 said:
Erm can you explain it so that I will understand it? XD
I kind of understand what you mean but I am still confused here and there....
Click to expand...
Click to collapse
Your phone has a recovery. When you bought it, it came with the factory (or stock) recovery. Stock recoveries will only let you flash certain signed zip files and not all (for example - your ota updates). So you need to shift to a custom recovery that will let you flash any file you want. Custom recoveries are device specific. Search how to flash it in your phone. Common ones are - TWRP, cwm, philz.
Once you have your new recovery set up, you are ready to root it. All you have to do is use the recovery to flash the supersu file (i recommend chainfire). If you have twrp installed, the flashable su file is a part of it, and it will guide you.
Reboot after done, and supersu will prompt you to update your su binaries, done. you are all set. Dont forget to unlock the bootloader.
Your warranty will be void unless you revert all changes. Not at all complicated, you do it once and get the hang of it.
A short note on flashing: Flashing is replacing (or installing) certain system files. You can tweak your system in any way you like (overclocking, changing animations, installing apps or scripts, changing the os, etcetera ). Just make sure the zips you flash are compatible.
RealWelder said:
In modern Android the phone's security systems prevent rooting via one click apps unless the device is unlocked. The best/safest way to root is to flash custom recovery such as TWRP and then install SuperSU.zip from TWRP. Make sure you make a backup first just in case.
You will most likely have to unlock your bootloader before you can flash TWRP. SONY devices are usually pretty Dev friendly, so you shouldn't have too much trouble finding everything you need. Good luck.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
dev.kasibhatla said:
Your phone has a recovery. When you bought it, it came with the factory (or stock) recovery. Stock recoveries will only let you flash certain signed zip files and not all (for example - your ota updates). So you need to shift to a custom recovery that will let you flash any file you want. Custom recoveries are device specific. Search how to flash it in your phone. Common ones are - TWRP, cwm, philz.
Once you have your new recovery set up, you are ready to root it. All you have to do is use the recovery to flash the supersu file (i recommend chainfire). If you have twrp installed, the flashable su file is a part of it, and it will guide you.
Reboot after done, and supersu will prompt you to update your su binaries, done. you are all set. Dont forget to unlock the bootloader.
Your warranty will be void unless you revert all changes. Not at all complicated, you do it once and get the hang of it.
A short note on flashing: Flashing is replacing (or installing) certain system files. You can tweak your system in any way you like (overclocking, changing animations, installing apps or scripts, changing the os, etcetera ). Just make sure the zips you flash are compatible.
Click to expand...
Click to collapse
Is chain fire part of Super Su or do you mean instead of it? And what do you mean unlock bootloader???
GarrusN7 said:
Is chain fire part of Super Su or do you mean instead of it? And what do you mean unlock bootloader???
Click to expand...
Click to collapse
Chainfire made the root strategy. There are various strategies. Supersu is by chainfire. To change your recovery from stock to custom, you need to unlock the bootloader. It protects the current system by not letting unauthorized files overwrite or execute their scripts.
Not unlocking bootloader and flashing may lead to a brick. So
download platform-tools by google. (adb)
Extract it. Say at C:\
Now install drivers for your phone
open cmd and navigate to the folder where you extracted platform tools. Follow the code.
Enable usb debugging from developer options
Code:
cd C:\platform-tools
adb devices
a device and some number should show up with an online status
Code:
adb reboot bootloader
fastboot devices
again, a device and number should show
Code:
fastboot oem unlock
fastboot reboot
if it says success,bootloader is unlocked.
download a recovery.img specific to your phone. rename it to say twrp.img and place it in the same folder as platform tools.
Code:
adb reboot bootloader
fastboot boot twrp.img
the recovery will boot. this is a temporary boot and will wipe off on a reboot. Flash your supersu zip to root.
That's all. You have a rooted phone with an unlocked bootloader.
That is the maximum anyone would describe for you. Still confused, please do some research.
Hit thanks if i helped.
dev.kasibhatla said:
Chainfire made the root strategy. There are various strategies. Supersu is by chainfire. To change your recovery from stock to custom, you need to unlock the bootloader. It protects the current system by not letting unauthorized files overwrite or execute their scripts.
Not unlocking bootloader and flashing may lead to a brick. So
download platform-tools by google. (adb)
Extract it. Say at C:\
Now install drivers for your phone
open cmd and navigate to the folder where you extracted platform tools. Follow the code.
Enable usb debugging from developer options
Code:
cd C:\platform-tools
adb devices
a device and some number should show up with an online status
Code:
adb reboot bootloader
fastboot devices
again, a device and number should show
Code:
fastboot oem unlock
fastboot reboot
if it says success,bootloader is unlocked.
download a recovery.img specific to your phone. rename it to say twrp.img and place it in the same folder as platform tools.
Code:
adb reboot bootloader
fastboot boot twrp.img
the recovery will boot. this is a temporary boot and will wipe off on a reboot. Flash your supersu zip to root.
That's all. You have a rooted phone with an unlocked bootloader.
That is the mazimum anyone would describe for you. Still confused, please do some research.
Hit thanks if i helped.
Click to expand...
Click to collapse
Thanks. Tho I am sure once I get hands on to it, I will know what to do. Can't wait to move those damned OBB Xd
Just be aware that by unlocking the bootloader you are going to lose camera quality. That's because the keys for image processing are deleted. I think it's only noticeable in low light situations, but still important to know, because once lost those keys will never come back. Therefore I'd rather recommend this rooting method:
https://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
fab_ben said:
Just be aware that by unlocking the bootloader you are going to lose camera quality. That's because the keys for image processing are deleted. I think it's only noticeable in low light situations, but still important to know, because once lost those keys will never come back. Therefore I'd rather recommend this rooting method:
https://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
Click to expand...
Click to collapse
I woundn't recommend this anymore...
Use this one from russel5 - this is for stock rom and locked bootloader - and for staying at looked bootloader...
https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
This is an noob-save tut which uses russel5's way...
https://forum.xda-developers.com/z3-compact/general/guide-newbshow-to-291-mm-z3clocked-t3536395
fluffi444 said:
I woundn't recommend this anymore...
Use this one from russel5 - this is for stock rom and locked bootloader - and for staying at looked bootloader...
https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
This is an noob-save tut which uses russel5's way...
https://forum.xda-developers.com/z3-compact/general/guide-newbshow-to-291-mm-z3clocked-t3536395
Click to expand...
Click to collapse
What he/she says. Sorry, I totally forgot about that method, it's much easier, thank you!
dev.kasibhatla said:
Chainfire made the root strategy. There are various strategies. Supersu is by chainfire. To change your recovery from stock to custom, you need to unlock the bootloader. It protects the current system by not letting unauthorized files overwrite or execute their scripts.
Not unlocking bootloader and flashing may lead to a brick. So
download platform-tools by google. (adb)
Extract it. Say at C:\
Now install drivers for your phone
open cmd and navigate to the folder where you extracted platform tools. Follow the code.
Enable usb debugging from developer options
Code:
cd C:\platform-tools
adb devices
a device and some number should show up with an online status
Code:
adb reboot bootloader
fastboot devices
again, a device and number should show
Code:
fastboot oem unlock
fastboot reboot
if it says success,bootloader is unlocked.
download a recovery.img specific to your phone. rename it to say twrp.img and place it in the same folder as platform tools.
Code:
adb reboot bootloader
fastboot boot twrp.img
the recovery will boot. this is a temporary boot and will wipe off on a reboot. Flash your supersu zip to root.
That's all. You have a rooted phone with an unlocked bootloader.
That is the maximum anyone would describe for you. Still confused, please do some research.
Hit thanks if i helped.
Click to expand...
Click to collapse
Well ****....my root doesn't work. I am using SuperSu and TWRP but for some reason a ram disk extraction fails and no install...is it because I have systemless version of my phone or whatever keeps popping up???? And how do I fix that crap???
dev.kasibhatla said:
Chainfire made the root strategy. There are various strategies. Supersu is by chainfire. To change your recovery from stock to custom, you need to unlock the bootloader. It protects the current system by not letting unauthorized files overwrite or execute their scripts.
Not unlocking bootloader and flashing may lead to a brick. So
download platform-tools by google. (adb)
Extract it. Say at C:\
Now install drivers for your phone
open cmd and navigate to the folder where you extracted platform tools. Follow the code.
Enable usb debugging from developer options
Code:
cd C:\platform-tools
adb devices
a device and some number should show up with an online status
Code:
adb reboot bootloader
fastboot devices
again, a device and number should show
Code:
fastboot oem unlock
fastboot reboot
if it says success,bootloader is unlocked.
download a recovery.img specific to your phone. rename it to say twrp.img and place it in the same folder as platform tools.
Code:
adb reboot bootloader
fastboot boot twrp.img
the recovery will boot. this is a temporary boot and will wipe off on a reboot. Flash your supersu zip to root.
That's all. You have a rooted phone with an unlocked bootloader.
That is the maximum anyone would describe for you. Still confused, please do some research.
Hit thanks if i helped.
Click to expand...
Click to collapse
fluffi444 said:
I woundn't recommend this anymore...
Use this one from russel5 - this is for stock rom and locked bootloader - and for staying at looked bootloader...
https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
This is an noob-save tut which uses russel5's way...
https://forum.xda-developers.com/z3-compact/general/guide-newbshow-to-291-mm-z3clocked-t3536395
Click to expand...
Click to collapse
I unlocked the boot loader the official way (Sony guide and ****). I didn't want to brick my phone accidently.
GarrusN7 said:
I unlocked the boot loader the official way (Sony guide and ****). I didn't want to brick my phone accidently.
Click to expand...
Click to collapse
You wouldn't have bricked your phone
If you followed instructions on their site and contacted them, like unlocking htc bootloader, congratulations, your warranty is officially void.
If you didn't contact them in any wau or uploaded your phone's mac/imei, if you re lock, warranty valid again.
dev.kasibhatla said:
You wouldn't have bricked your phone
If you followed instructions on their site and contacted them, like unlocking htc bootloader, congratulations, your warranty is officially void.
If you didn't contact them in any wau or uploaded your phone's mac/imei, if you re lock, warranty valid again.
Click to expand...
Click to collapse
At least I did this the safe way. Oh well, I never send my phones for repairs as the repairs are always overpriced, my dad fixes everything himself if actually fixable XD.
But my root issue still remains!
GarrusN7 said:
At least I did this the safe way. Oh well, I never send my phones for repairs as the repairs are always overpriced, my dad fixes everything himself if actually fixable XD.
But my root issue still remains!
Click to expand...
Click to collapse
Here's a link from another post. Follow it and check. It should work.
(you've already performed a few of those steps)
link
This is a short guide on rooting for thous who are new to this stuff
Steps:
1: download adb platform tools from here
2: Unlock bootloader. follow the guide on htcdev.
make sure you have htc drivers installed so that you can use oem command in fastboot mode for unlocking
3: Download TWRP
4: Download SuperSU and copy it to your phone's internal memory
5: Enable USB debugging and type "adb reboot-bootloader" from pc
6: Type: "fastboot boot twrp-3.1.1-0-alpine.img"
make sure you have twrp image in same folder as adb.
7: Wait for sometime you will boot into twrp recovery from there select install and select the SuperSU zip file
8: reboot and check for root
Links:
http://www.supersu.com/download
https://developer.android.com/studio/releases/platform-tools.html
has anybody tried this? I'm a bit scared to be the first one
javnostra said:
has anybody tried this? I'm a bit scared to be the first one
Click to expand...
Click to collapse
You should make sure you get a pristine backup at hand, or a RUU appropriate to your device. Otherwise you'll never be able toreturn to a full stock system.
On the U11 it is possible to boot TWRP from fastboot, without flashing it and thus without touching stock recovery. That way I've been able to flash Magisk what's coming with MagiskSU and the possibility to use some Modules. And all without altering the system or replacing stock recovery in the first place.
Sent from my HTC U11 using XDA Labs
javnostra said:
has anybody tried this? I'm a bit scared to be the first one
Click to expand...
Click to collapse
Yes its working without flaws, i have tested it myself. also your not installing recovery this time your booting directly
dranzer006 said:
Yes its working without flaws, i have tested it myself. also your not installing recovery this time your booting directly
Click to expand...
Click to collapse
Thanks, I will try it then.
javnostra said:
Thanks, I will try it then.
Click to expand...
Click to collapse
It works. Thanks a lot. My phone is rooted
5m4r7ph0n36uru said:
You should make sure you get a pristine backup at hand, or a RUU appropriate to your device. Otherwise you'll never be able toreturn to a full stock system.
Click to expand...
Click to collapse
for anyone asking themselves how to backup
https://forum.xda-developers.com/showpost.php?p=53767160&postcount=2
or https://forum.xda-developers.com/showpost.php?p=53770286&postcount=4
or is there a different way these days? @5m4r7ph0n36uru
BerndM14 said:
Connect phone to PC, boot into bootloader mode and type fastboot boot name_of_recovery.img that'll just boot the custom recovery as opposed to flashing it, that way you can make a nandroid backup of all partitions including stock recovery.
Click to expand...
Click to collapse
an0ther said:
The guys method of using recovery to backup recovery will only work on Philz… Not twrp as it does not always backup stock recovery properly. The proper way to backup stock recovery is..
1. Root your phone, which can be done by towel root or by just booting a recovery like he said,
fastboot boot twrporwhatever.img, then flash supersu
2. Boot phone that has stock recovery
3. adb shell
4. su "watch your phone to grant root adb access if you haven't ever done it"
5. dd if=/dev/block/mmcblk0p43 of=/sdcard/recovery.img
6. This will put flashable recovery.img on your internal sd card. Copy this and save it for later
7. "fastboot flash recovery recovery.img" will get you back to stock recovery, "fastboot flash recovery twrporwhatever.img" to flash custom recovery.
Click to expand...
Click to collapse
If possible and a TWRP recovery is available one should boot to bootloader and try if the command fastboot boot name_of_twrp.img works. Make sure to NOT grant r/w at first boot and leave it ro. Now you can perform a backup of stock recovery, boot and system image (not system partition!) to obtain a pristine backup.
All else will alter system partitions md5 and the backup won't be pristine any longer. Due to block based OTA policy introduced by Google you won't be able to OTA without a pristine system image.
Sent from my HTC U11 using XDA Labs
Bro My Boot Loader is Locked.
Htc dev Not Relised Htc u play Boot loader.
I think these are the instructions. You need to register to access the link
https://www.htcdev.com/bootloader/unlock-instructions
or use my login:
lizba
ALJSDBf234LJABSf
edit: dont use my login. you have to register. you'll get a mail with another page plus a .bin file
https://www.htcdev.com/bootloader/unlock-instructions/page-4/
I have two questions.
1. If I fastboot to TWPR will it stay (flash for good) or after disconnecting my phone it will be gone ?
2. Can I flash Magisk instead of SuperSU ?
Code:
fastboot oem get_identifier_token
FAILED (remote: unknown command)
how i can solve it?
ex71 said:
Code:
fastboot oem get_identifier_token
FAILED (remote: unknown command)
how i can solve it?
Click to expand...
Click to collapse
need enable "OEM unlock" in developers menu, reboot into bootloader and select "download mode". Next steps from original guide.
ex71 said:
need enable "OEM unlock" in developers menu, reboot into bootloader and select "download mode". Next steps from original guide.
Click to expand...
Click to collapse
But in download mode there is no fastboot active ?! Until you installed the correct drivers
no "fastboot" (like a "one s", etc) on this phone. no fastboot usb
"fastboot" command work in "bootloader menu" and "download mode"
fastboot oem only in download mode
Hello. Please explain what I am doing wrong. I will download what is in points. I download this adb something, but it does not work. Nothing starts. Does not communicate with the phone. OCB. Could anyone write this guide so that he could understand and act?
hello everyone
Buy a Chinese mi8, unlock it waiting for the days that xiaomi tells you.
I installed the global version, and everything works correctly, but I want to change the rom.
I've tried to install TWRP with adb and it's impossible, it tells me the ADB template that OKEY, but never restarts in recovery mode with TWRP, so I can not install magisk, or any rom that is not official.
Is there any way to install a ROM (.zip) without TWRP?, how do I do Root without magisk? Has it happened to anyone?
thanks!
First of all, you're in the wrong section.
Second you should install via fastboot as described a thousand times AND reboot directly to your TWRP image via fastboot command.
The you can flash another from and root it.
Third, I'd like to strongly advice you to do some research about android, flashing etc to make sure that you know what you are doing.... So many people are moaning about bricked devices....
trahzebuck said:
First of all, you're in the wrong section.
Second you should install via fastboot as described a thousand times AND reboot directly to your TWRP image via fastboot command.
The you can flash another from and root it.
Third, I'd like to strongly advice you to do some research about android, flashing etc to make sure that you know what you are doing.... So many people are moaning about bricked devices....
Click to expand...
Click to collapse
Thanks for your help
It's not the first cell phone I've flashed that you're not smart.
I have followed the steps as they are, and as you can see in the image, everything seems to be installed correctly. But whenever I restart in recovery mode, I get the xiaomi no twrp.
Do you know why?
cheteuk said:
Thanks for your help
It's not the first cell phone I've flashed that you're not smart.
I have followed the steps as they are, and as you can see in the image, everything seems to be installed correctly. But whenever I restart in recovery mode, I get the xiaomi no twrp.
Do you know why?
Click to expand...
Click to collapse
You are trying to be smart? Well...
Why didn't you post your exact steps with fastboot in the first post?
Now it's clear what you did wrong. I already expected it. And you did NOT read what I wrote:
You are rebooting your device with fastboot reboot. In this case your twrp is wiped out by the XIAOMI recovery. Use: fastboot boot yourimagename.
btw, why are you using such an old TWRP? You won't be able to flash actual roms.
So I'd like to come back to my advice in the first answer....
cheteuk said:
Thanks for your help
It's not the first cell phone I've flashed that you're not smart.
I have followed the steps as they are, and as you can see in the image, everything seems to be installed correctly. But whenever I restart in recovery mode, I get the xiaomi no twrp.
Do you know why?
Click to expand...
Click to collapse
fastboot boot recovery.img
not fastboot reboot
Sent from my MI 8 using Tapatalk
Vuska said:
fastboot boot recovery.img
not fastboot reboot
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
I've tried twrp-3.3.1-0-dipper too, and fastboot boot xxxx.img.
And it hasn't been restarted either.
cheteuk said:
I've tried twrp-3.3.1-0-dipper too, and fastboot boot xxxx.img.
And it hasn't been restarted either.
Click to expand...
Click to collapse
Use the all in one tool, to remove encryption and flash a compatible TWRP.
tsongming said:
Use the all in one tool, to remove encryption and flash a compatible TWRP.
Click to expand...
Click to collapse
What is the all in one tool?
cheteuk said:
What is the all in one tool?
Click to expand...
Click to collapse
Try this. There is all you need.
https://tradingshenzhen.com/de/cont...sh-tutorial-global-firmware-xiaomieu-firmware
Upps, in German. You can choose English.
Goalach said:
Try this. There is all you need.
https://tradingshenzhen.com/de/cont...sh-tutorial-global-firmware-xiaomieu-firmware
Upps, in German. You can choose English.
Click to expand...
Click to collapse
Thanks for the help.
But all the steps that indicate, I have passed them and I never install the TWRP correctly.
1. my mobile phone is unlocked (with the padlock open)
2. I have the official rom installed
3. I try to install twrp with all the commands you have told me, and I never restart the mobile with twrp. I've tried new, intermediate and older versions. and nothing
Is there any way to install an unofficial rom without TWRP?
cheteuk said:
Thanks for the help.
But all the steps that indicate, I have passed them and I never install the TWRP correctly.
1. my mobile phone is unlocked (with the padlock open)
2. I have the official rom installed
3. I try to install twrp with all the commands you have told me, and I never restart the mobile with twrp. I've tried new, intermediate and older versions. and nothing
Is there any way to install an unofficial rom without TWRP?
Click to expand...
Click to collapse
You can't flash a ROM without TWRP and Magisk is the only way you can root your phone that I know of. If you don't even know these simple things/haven't done simple research you might risk to softbrick or even hardbrick your new and shiny phone. There are many guides on how to flash TWRP but you can PM me if you want more help.
Also you don't install TWRP with adb, you need to use fastboot...
cheteuk said:
What is the all in one tool?
Click to expand...
Click to collapse
The number 1 result
http://bfy.tw/Nvtb
You can try this
Make sure you have activated the usb debugging in developer options.
1. Download the tools from here: bit.ly/FlashToolMi8
2. Install the minimal_adb_fastboot_v1.3.1_setup
3. Copy the twrp-3.2.3-0-dipper.img to Minimal ADB and Fastboot Folder
4. Turn off your phone completely. then press power button + volume down to boot in fastboot mode.
5. Run CMD as Administrator then cd to the installed Minimal ADB and Fastboot folder. (Ex: cd C:\Program Files (x86)\Minimal ADB and Fastboot)
6. Use this command on your cmd: fastboot flash recovery twrp-3.2.3-0-dipper.img
7. Then: fastboot boot twrp-3.2.3-0-dipper
8. And: fastboot reboot recovery
9. You're now in twrp recovery mode
10. Copy Disable_Dm-Verity_FEC_v1.1 and Magisk-v18.1 to your phone
11. Install Disable_Dm-Verity_FEC_v1.1 from twrp
12. Then install Magisk-v18.1
13. Reboot, Your phone now rooted
I've tried multiple rooting programs to try to root the phone, but none of them seem to work. So my question is, has anyone figured out a working method to get root? (I've unlocked the boot loader already)
TheRedPandaSSN said:
I've tried multiple rooting programs to try to root the phone, but none of them seem to work. So my question is, has anyone figured out a working method to get root? (I've unlocked the boot loader already)
Click to expand...
Click to collapse
I haven't been able to root it either. How'd u unlock the bootloader ?
greeneyez15o said:
I haven't been able to root it either. How'd u unlock the bootloader ?
Click to expand...
Click to collapse
If you go into developer options it allows you to unlock the bootloader.
TheRedPandaSSN said:
If you go into developer options it allows you to unlock the bootloader.
Click to expand...
Click to collapse
I don't think that completely unlocks the bootloader
TheRedPandaSSN said:
If you go into developer options it allows you to unlock the bootloader.
Click to expand...
Click to collapse
All that does is ALLOW the bootloader to be unlocked - it doesn't unlock it.
I just unlocked the bootloader
Used adb
"Fastboot flashing unlock"
Next im gonna try to apply root
Wish me luck
I have just ordered this phone. Will hopefully be able to share backup copies of ramdisk(boot) to be used with magisk to give root
Well if anyone is Interested in trying out mtk-su to get system-less, boot-less root it should work. It worked with my umidigi phone that also has mtk p70 soc. And running pie.
https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
Here is device back up script project I had done based on that mtk-su.
https://github.com/mrmazakblu/Root-Backup-Helper
My test of using mtk-su did not work out.
But i do have backup copy of the stock boot.img , install magisk manager (currently i used V 7.3.4, after magisk update, V20 caused device trouble. Recommend stay with mahisk v19.3) and patch the boot.img from link below, then flash with "fastboot flash boot /file.name" to have full root.
here is stock boot file
https://androidfilehost.com/?fid=1899786940962604580
:::UPDATE::10-27
Successfully flashed magisk with twrp. But because the current twrp has no working touchscreen. It was done with ADB commands.
mrmazak said:
My test of using mtk-su did not work out.
But i do have backup copy of the stock boot.img , install magisk manager (use most recent version, currently i used V 7.3.4) and patch the boot.img from link below, then flash with "fastboot flash boot /file.name" to have full root.
here is stock boot file
https://androidfilehost.com/?fid=1899786940962604580
Click to expand...
Click to collapse
How'd u patch the boot.img ?
Thanks !!!
greeneyez15o said:
How'd u patch the boot.img ?
Thanks !!!
Click to expand...
Click to collapse
You can follow full guide found on magisk thread.
Here is general steps.
1. Install magisk manager app
2. Select install. Choose option to patch local file.
3. When complete, copy that patched_boot.img to PC
4. Fastboot flash boot patched_boot.img
I did not share the patched boot.img. you need to do this step on your own. Is better that way.
mrmazak said:
You can follow full guide found on magisk thread.
Here is general steps.
1. Install magisk manager app
2. Select install. Choose option to patch local file.
3. When complete, copy that patched_boot.img to PC
4. Fastboot flash boot patched_boot.img
I did not share the patched boot.img. you need to do this step on your own. Is better that way.
Click to expand...
Click to collapse
Sorry for the question, but wheres the option to patch local file?
---------- Post added at 01:25 PM ---------- Previous post was at 01:01 PM ----------
greeneyez15o said:
Sorry for the question, but wheres the option to patch local file?
Click to expand...
Click to collapse
I followed instructions, I keep getting error cannnot load 'patched_boot.img'
greeneyez15o said:
Sorry for the question, but wheres the option to patch local file?
---------- Post added at 01:25 PM ---------- Previous post was at 01:01 PM ----------
I followed instructions, I keep getting error cannnot load 'patched_boot.img'
Click to expand...
Click to collapse
I feel maybe I was too general in the steps. (not enough detail) sorry.
If you got to the part when it is loading patched_boot
then you got past the patching part.
so, you need to find the patched_boot.img . It should be in the download folder on device
copy this to your PC.
reboot phone to bootloader mode.
then open terminal in same window as the copied patched_boot.img file, or use the full path name in the command.
In the following example, the patched_boot.img file is saved in c:\adb
Code:
adb pull /sdcard/Download/patched_boot.img c:\adb\
adb reboot bootloader
fastboot flash boot c:\adb\patched_boot.img
fastboot reboot
mrmazak said:
I feel maybe I was too general in the steps. (not enough detail) sorry.
If you got to the part when it is loading patched_boot
then you got past the patching part.
so, you need to find the patched_boot.img . It should be in the download folder on device
copy this to your PC.
reboot phone to bootloader mode.
then open terminal in same window as the copied patched_boot.img file, or use the full path name in the command.
In the following example, the patched_boot.img file is saved in c:\adb
Click to expand...
Click to collapse
Got it !!! Had to reboot my computer ?
mrmazak said:
You can follow full guide found on magisk thread.
Here is general steps.
1. Install magisk manager app
2. Select install. Choose option to patch local file.
3. When complete, copy that patched_boot.img to PC
4. Fastboot flash boot patched_boot.img
I did not share the patched boot.img. you need to do this step on your own. Is better that way.
Click to expand...
Click to collapse
Does anyone manage to change the system file? when you try the phone freezes helps reboot
fafanakatr said:
Does anyone manage to change the system file? when you try the phone freezes helps reboot
Click to expand...
Click to collapse
Do you mean, flashing gsi image, or editing things on stock system. I have been focussed on tarp, and my tried either case.
I can do that soon and confirm if system is freeze.
OK, first time i tried to flash GSI here it is failed.
used fastboot flash system **gsi.img**
(phh v119)
it flashed without error, but will not go past bootloader splash screen. --ODD
will try again later
mrmazak said:
Do you mean, flashing gsi image, or editing things on stock system. I have been focussed on tarp, and my tried either case.
I can do that soon and confirm if system is freeze.
OK, first time i tried to flash GSI here it is failed.
used fastboot flash system **gsi.img**
(phh v119)
it flashed without error, but will not go past bootloader splash screen. --ODD
will try again later
Click to expand...
Click to collapse
I did everything according to the instructions that you suggested, and everything worked out for me, I got a root, but when I try to change the system files, the phone freezes, maybe the root is not full? Thanks for your work)
fafanakatr said:
I did everything according to the instructions that you suggested, and everything worked out for me, I got a root, but when I try to change the system files, the phone freezes, maybe the root is not full? Thanks for your work)
Click to expand...
Click to collapse
Well all depends on what system files you have changed.
I was able to delete the system private-app file "blu-ignite" (an unauthorized app installed program) without freezing system.
I was on magisk 19.3. when I try to update to magisk v20 then I have issues. Freezes, wifi not turn on, ect. So try to restore stock, and Will have to use custom update Chanel with magisk to force it to use the older version.
I am also trying to see if twrp can be used tethered, to install magisk. By using "adb shell twrp sideload" command. And sideloading the magisk file.
If, when I see it works I can write the the whole process.
mrmazak said:
Well all depends on what system files you have changed.
I was able to delete the system private-app file "blu-ignite" (an unauthorized app installed program) without freezing system.
I was on magisk 19.3. when I try to update to magisk v20 then I have issues. Freezes, wifi not turn on, ect. So try to restore stock, and Will have to use custom update Chanel with magisk to force it to use the older version.
I am also trying to see if twrp can be used tethered, to install magisk. By using "adb shell twrp sideload" command. And sideloading the magisk file.
If, when I see it works I can write the the whole process.
Click to expand...
Click to collapse
I will try to do as you suggested and let you know) I will be well waiting for your success
mrmazak said:
Well all depends on what system files you have changed.
I was able to delete the system private-app file "blu-ignite" (an unauthorized app installed program) without freezing system.
I was on magisk 19.3. when I try to update to magisk v20 then I have issues. Freezes, wifi not turn on, ect. So try to restore stock, and Will have to use custom update Chanel with magisk to force it to use the older version.
I am also trying to see if twrp can be used tethered, to install magisk. By using "adb shell twrp sideload" command. And sideloading the magisk file.
If, when I see it works I can write the the whole process.
Click to expand...
Click to collapse
thank you very much I did everything according to the instructions and everything worked out for me,I tried to turn on the camera2api but so far without success,
can you understand this?