Related
I used this method http://forum.xda-developers.com/showthread.php?t=710842 to root without unlocking bootloader.
I want to flash the new amonra recovery 1.8.0.1
Fastboot flash recovery filename.img does not work (this is probably the limitation of this method of rooting without unlocking bootloader).
What's the best way/easier way to do this rather than going through steps 17-24
Thanks.
Besides using the one-click root? http://forum.xda-developers.com/showthread.php?t=747598
Also, what's wrong with 17-24? You *have* to do this regardless in order to install stuff into /system, although actually not 100% sure if you have to do it in order to install a recovery.
I guess the point is you don't want to set up adb?
khaytsus said:
Besides using the one-click root? http://forum.xda-developers.com/showthread.php?t=747598
Also, what's wrong with 17-24? You *have* to do this regardless in order to install stuff into /system, although actually not 100% sure if you have to do it in order to install a recovery.
I guess the point is you don't want to set up adb?
Click to expand...
Click to collapse
The one click root for nexus one didn't exist when I did mine using the tutorial i did.
everything works except you can't do a "fastboot flash recovery" command.
So using the One Click Root, lets you use the fastboot flash recovery command and keeps the bootloader locked?
Maybe I'll redo my phone.
You need to use flash_image command from the Terminal. Fastboot works only for original images when bootloader is locked.
So far all the methods i've read require me to rsdlite or adb the factory fxz which I believe causes me to lose data.
nvertigo said:
So far all the methods i've read require me to rsdlite or adb the factory fxz which I believe causes me to lose data.
Click to expand...
Click to collapse
As far as I can figure, the only way would to use an app to backup the data, flash back to factory, re-root and restore the data. The OTA update will remove root access. I would do a backup with CWM first if possible.
nvertigo said:
So far all the methods i've read require me to rsdlite or adb the factory fxz which I believe causes me to lose data.
Click to expand...
Click to collapse
if you know what you actually changed with root permissions then you can just flash stock recovery onto the phone then remove all things root and put everything back to normal stock (like unfreezing things out of tibu or whatever) then take the ota. if you are not sure what you changed, you can flash recovery and system then take the ota (assuming you didn't flash new kernals or anything else major).
And if you just want to keep data then you can flash stock ota with rsdlite and remove the two entries that erase data and cache in the xml file. Then take the ota. or flash the fxz and remove the same data erasing entries in the xml
If you have an unlocked bootloader, just mfastboot stock recovery and stock system and take the OTA. You won't lose data. Then just reflash TWRP and root. Good to go.
If your bootloader is locked, then I have no idea.
Sent from my Dev Edition Moto X
Schaweet said:
If you have an unlocked bootloader, just mfastboot stock recovery and stock system and take the OTA. You won't lose data. Then just reflash TWRP and root. Good to go.
If your bootloader is locked, then I have no idea.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I am on a vzw dev edition. I have rooted and have twrp installed. I changed the boot animation and installed xposed. If I undo those 2 things does some have a step by step process for getting back to stock and taking the ota and then re installing twrp and rooting. I would greatly appreciate it.
robwege said:
I am on a vzw dev edition. I have rooted and have twrp installed. I changed the boot animation and installed xposed. If I undo those 2 things does some have a step by step process for getting back to stock and taking the ota and then re installing twrp and rooting. I would greatly appreciate it.
Click to expand...
Click to collapse
This is what I did.
1. Download 4.4 stock files from Motorola (you need to request access and they will email you the link)
2. Extract recovery.img and system.img from the stock image and place them in your platform tools folder ( or where fastboot and adb are located)
3. Update your SDK if it is out of date.
4. Download and put mfastboot in your platform tools folder (or where fastboot and adb are within your sdk directory)
5. Boot phone into fastboot mode
6. open a command prompt and change directory to your platform-tools folder and type the following (7 & 8)
7. fastboot flash recovery recovery.img
8. mfastboot flash system system.img
9. Reboot
10. Accept and install OTA
11. Reboot into fastboot mode
12. Reflash TWRP and root phone.
13. Reboot
14. Open Xposed and reinstall framework
15. Reboot
You would be good to go at that point. You would still need to reinstall your logo as it would be reset
If you already unlocked your phone and didn't change anything, you shouldn't have much trouble with the commands
Schaweet said:
This is what I did.
1. Download 4.4 stock files from Motorola (you need to request access and they will email you the link)
2. Extract recovery.img and system.img from the stock image and place them in your platform tools folder ( or where fastboot and adb are located)
3. Update your SDK if it is out of date.
4. Download and put mfastboot in your platform tools folder (or where fastboot and adb are within your sdk directory)
5. Boot phone into fastboot mode
6. open a command prompt and change directory to your platform-tools folder and type the following (7 & 8)
7. fastboot flash recovery recovery.img
8. mfastboot flash system system.img
9. Reboot
10. Accept and install OTA
11. Reboot into fastboot mode
12. Reflash TWRP and root phone.
13. Reboot
14. Open Xposed and reinstall framework
15. Reboot
You would be good to go at that point. You would still need to reinstall your logo as it would be reset
If you already unlocked your phone and didn't change anything, you shouldn't have much trouble with the commands
Click to expand...
Click to collapse
Thank you for your help. The only things I changed were and boot logo and xposed. I also freezer some apps but that is an easy fix. You di this on a vzw Dev edition as well?
Sent from my XT1060 using XDA Premium 4 mobile app
robwege said:
I am on a vzw dev edition. I have rooted and have twrp installed. I changed the boot animation and installed xposed. If I undo those 2 things does some have a step by step process for getting back to stock and taking the ota and then re installing twrp and rooting. I would greatly appreciate it.
Click to expand...
Click to collapse
robwege said:
Thank you for your help. The only things I changed were and boot logo and xposed. I also freezer some apps but that is an easy fix. You di this on a vzw Dev edition as well?
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you froze the OTA application, you need to unfreeze that first as you won't have root until after you take the OTA and then reinstall TWRP.
I have a VZW DE as well.
I'm not sure how the changed boot animation will affect the OTA.
Your safest bet is to just follow the process I wrote to ensure the OTA doesn't fail and create other problems. It really only takes like 5 minutes. It leaves your data intact, so you won't have to set it up again. It also leaves the Xposed app on your phone and you just need to open it and install it. All your modules will still be there and will work as they did before after a reboot.
Schaweet said:
If you froze the OTA application, you need to unfreeze that first as you won't have root until after you take the OTA and then reinstall TWRP.
I have a VZW DE as well.
I'm not sure how the changed boot animation will affect the OTA.
Your safest bet is to just follow the process I wrote to ensure the OTA doesn't fail and create other problems. It really only takes like 5 minutes. It leaves your data intact, so you won't have to set it up again. It also leaves the Xposed app on your phone and you just need to open it and install it. All your modules will still be there and will work as they did before after a reboot.
Click to expand...
Click to collapse
I kept the old boot animation file so I can just move it back.
Sent from my XT1060 using XDA Premium 4 mobile app
OK so then technically you can reinstall the old boot Ani, unfreeze all apps, disable xposed using the Xposed disabler zip that should be in your SD card root directory, and then flash stock recovery.
That should allow you to take the OTA as you would technically be stock at that point. I chose the other method to ensure I was 100% stock. This should get you to stock as well, but I guess I like to be certain.
Sent from my Dev Edition Moto X
Schaweet said:
OK so then technically you can reinstall the old boot Ani, unfreeze all apps, disable xposed using the Xposed disabler zip that should be in your SD card root directory, and then flash stock recovery.
That should allow you to take the OTA as you would technically be stock at that point. I chose the other method to ensure I was 100% stock. This should get you to stock as well, but I guess I like to be certain.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
OK. I think I will do your method instead. I will unfreeze the apps, install old boot logo and disable xposed just to be safe. Then I will do your method. Wish me luck.
Sent from my XT1060 using XDA Premium 4 mobile app
If you do my method with all the numbered steps, you don't have to mess with all the unfreezing and stuff. Flashing system.img overwrites all those changes for you.
Sent from my Dev Edition Moto X
Schaweet said:
If you have an unlocked bootloader, just mfastboot stock recovery and stock system and take the OTA. You won't lose data. Then just reflash TWRP and root. Good to go.
If your bootloader is locked, then I have no idea.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
You don't even need an unlocked bootloader, you can still flash stock images on a locked bootloader. Also the person obviously unlock the bootloader since TWRP is installed, unless I'm not aware of a way to install it without.
eksasol said:
Also the person obviously unlock the bootloader since TWRP is installed, unless I'm not aware of a way to install it without.
Click to expand...
Click to collapse
You are correct. You can only flash a custom recovery if your bootloader is unlocked. That is what unlocking your bootloader allows you to do - flash unsigned recovery files (i.e., custom recoveries) and obviously, TWRP is not signed by motorola. Then once you have a custom recovery, the custom recovery allows you to flash unsigned operating systems.
If your bootloader is locked, you cannot flash an unsigned recovery.
Schaweet said:
If you do my method with all the numbered steps, you don't have to mess with all the unfreezing and stuff. Flashing system.img overwrites all those changes for you.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I am looking at your steps. Number 8 says fastboot and not mfastboot. Is this a typo or the correct command? I entered it in a cmd prompt and it just said waiting for device. I checked and adb was seeing my device.
Sent from my XT1060 using XDA Premium 4 mobile app
---------- Post added at 01:40 PM ---------- Previous post was at 01:40 PM ----------
robwege said:
I am looking at your steps. Number 8 says fastboot and not mfastboot. Is this a typo or the correct command? I entered it in a cmd prompt and it just said waiting for device. I checked and adb was seeing my device.
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I meant step 7.
Sent from my XT1060 using XDA Premium 4 mobile app
robwege said:
I am looking at your steps. Number 8 says fastboot and not mfastboot. Is this a typo or the correct command? I entered it in a cmd prompt and it just said waiting for device. I checked and adb was seeing my device.
Click to expand...
Click to collapse
fastboot is fine to flash recovery but you need to be in bootloader mode to use fastboot. You need mfastboot to flash system since it is so large. But mfastboot will work to flash recovery, too.
adb doesn't work in bootloader mode and fastboot doesn't work when you are booted into system. So if adb is working for you, you aren't in bootloader mode (note: bootloader mode is also called fastboot mode since for fastboot to work, you need to be in bootloader mode).
Go back to step 5 - boot into bootloader mode. Just type adb reboot bootloader. That will put you in bootloader mode.
NightThyme said:
fastboot is fine to flash recovery but you need to be in bootloader mode to use fastboot. You need mfastboot to flash system since it is so large. But mfastboot will work to flash recovery, too.
adb doesn't work in bootloader mode and fastboot doesn't work when you are booted into system. So if adb is working for you, you aren't in bootloader mode (note: bootloader mode is also called fastboot mode since for fastboot to work, you need to be in bootloader mode).
Go back to step 5 - boot into bootloader mode. Just type adb reboot bootloader. That will put you in bootloader mode.
Click to expand...
Click to collapse
OK. So if I am understanding you correctly. I boot the phone into fast boot. Then type your reboot bootloader cmd. Then from there I can do step 7 and 8 as typed above I. The thread where 7 uses fastboot and 8 uses mfastboot?
Sent from my XT1060 using XDA Premium 4 mobile app
robwege said:
OK. So if I am understanding you correctly. I boot the phone into fast boot. Then type your reboot bootloader cmd. Then from there I can do step 7 and 8 as typed above I. The thread where 7 uses fastboot and 8 uses mfastboot?
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The commands are written correctly. You have to be in bootloader/fastboot mode. I thought I said that.
Edit. I did see step 5.
Follow every step you don't want a brick.
Sent from my Dev Edition Moto X
Schaweet said:
The commands are written correctly. You have to be in bootloader/fastboot mode. I thought I said that.
Edit. I did see step 5.
Follow every step you don't want a brick.
Click to expand...
Click to collapse
This.
If I wanted to go back to stock from an aosp based ROM could I use the mfastboot recovery and system method or do I ha e to rsd.... I'm unlocked btw
Sent from my Moto X using Tapatalk
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?
Installing magisk_patched is unnecessary.
download ADB here
download TWRP here
download magisk here
first ,we must unlock bootloader.
Settings->About phone->tap at Build number 7 times.Now,we unlocked the "Developer options". open it and turn the OEM unlocking on.
Reboot to bootloader&Run this command on your computer with ADB:
fastboot oem unlock
Use Volume key to select&Power key to enter.
(Ensure you have fully backed up all your files first because the device will be wiped back to default factory state but with an unlocked bootloader)
reboot to bootloder&connect us phone to computer.
Run this command on your computer with ADB:
fastboot boot twrp-3.3.1-2-guacamole.img
then,the phone will reboot to TWRP,but this not end for install, it will be broke after you reboot again, we must install the twrp-installer-3.3.1-2-guacamole.zip In this TWRP.
after this step we got the TWRP installed.
then use TWRP to install the last release magisk.
now we got magisk installed & SafetyNet-pass.
you can install xposed or not .
thanks all&enjoy.
This guide completely misses unlocking the bootloader, changing the option in developer settings to OEM unlock is NOT unlocking the bootloader. Please amend your guide to show the missing steps:
Running the following in the bootloader is how to correctly unlock the bootloader :
fastboot devices
Make sure your device is reported correctly
fastboot oem unlock
(Ensure you have fully backed up all your files first because the device will be wiped back to default factory state but with an unlocked bootloader)
djsubterrain said:
This guide completely misses unlocking the bootloader, changing the option in developer settings to OEM unlock is NOT unlocking the bootloader. Please amend your guide to show the missing steps:
Running the following in the bootloader is how to correctly unlock the bootloader :
fastboot devices
Make sure your device is reported correctly
fastboot oem unlock
(Ensure you have fully backed up all your files first because the device will be wiped back to default factory state but with an unlocked bootloader)
Click to expand...
Click to collapse
reedit now，thx
May want to fix Ture to True and after flashing the TWRP-installer reboot back to TWRP to make sure it sticks(Recovery Installed) before you flash Magisk zip.
Don't forget to flash to both slots to get everything to stick.
Its pretty hard to fail safetynet. I've flashed many different things on this phone and never failed it.
JeSUS! FINALLY! After trying out that other method of rooting, installing twrp and magisk (by using patched images) THIS worked. I updated to 9.5.6 (back to stock, but still bootloader unlocked) and then followed this guide to rooting this phone. Finally! Whew! Wish I had done this from the start. I'm able to go get some sleep now! Thanks OP!
So many great minds here! Best community for a specified device that ive ever had the pleasure of being a part of. Can't wait to try this when my unlock token comes in ?
roaduardo said:
JeSUS! FINALLY! After trying out that other method of rooting, installing twrp and magisk (by using patched images) THIS worked. I updated to 9.5.6 (back to stock, but still bootloader unlocked) and then followed this guide to rooting this phone. Finally! Whew! Wish I had done this from the start. I'm able to go get some sleep now! Thanks OP!
Click to expand...
Click to collapse
This is the classic way to get root,happy to help you
Purest said:
Don't forget to flash to both slots to get everything to stick.
Click to expand...
Click to collapse
I am waiting for the gsi of resurrection remix, curing twrp now is unnecessary
just making sure:
adb devices
adb reboot bootloader
fastboot devices
fastboot oem unlock (have it checked in dev options first)
reboot into bootloader after phone setup
fastboot boot twrp ................img
install twrp..............zip
install magisk
reboot?
equlizer said:
just making sure:
adb devices
adb reboot bootloader
fastboot devices
fastboot oem unlock (have it checked in dev options first)
reboot into bootloader after phone setup
fastboot boot twrp ................zip
install twrp..............zip
install magisk
reboot?
Click to expand...
Click to collapse
Did u try it ? Im waiting on confirmation as well
This is the method that I have been doing all along and it works everytime without any issues.
equlizer said:
just making sure:
adb devices
adb reboot bootloader
fastboot devices
fastboot oem unlock (have it checked in dev options first)
reboot into bootloader after phone setup
fastboot boot twrp ................zip
install twrp..............zip
install magisk
reboot?
Click to expand...
Click to collapse
Should be fastboot boot TWRP.img then install either twrp.zip if there's an installer or twrp.img if not
JTruj1ll0923 said:
Should be fastboot boot TWRP.img then install either twrp.zip if there's an installer or twrp.img if not
Click to expand...
Click to collapse
fixed my post so this method i dont have to worry about slots a and b right? Then what about when an update comes. Do i flash the full update or can i do an OTA? If i flash a full .zip will i loose my data? I'm coming from a pixel 2 xl.
Can someone please clarify. If I do this on slot A, how do I change over to Slot B to do it?
BlueMemory said:
Installing magisk_patched is unnecessary.
download ADB here
download TWRP here
download magisk here
first ,we must unlock bootloader.
Settings->About phone->tap at Build number 7 times.Now,we unlocked the "Developer options". open it and turn the OEM unlocking on.
Reboot to bootloader&Run this command on your computer with ADB:
fastboot oem unlock
Use Volume key to select&Power key to enter.
(Ensure you have fully backed up all your files first because the device will be wiped back to default factory state but with an unlocked bootloader)
reboot to bootloder&connect us phone to computer.
Run this command on your computer with ADB:
fastboot boot twrp-3.3.1-2-guacamole.img
then,the phone will reboot to TWRP,but this not end for install, it will be broke after you reboot again, we must install the twrp-installer-3.3.1-2-guacamole.zip In this TWRP.
after this step we got the TWRP installed.
then use TWRP to install the last release magisk.
now we got magisk installed & SafetyNet-pass.
you can install xposed or not .
thanks all&enjoy.
Click to expand...
Click to collapse
Flashing twrp Breaks wifi.
ashokmor007 said:
Flashing twrp Breaks wifi.
Click to expand...
Click to collapse
Does it really? I just ordered a 7 Pro yesterday so I don't have mine yet.
Hi everyone its not working for me i wonder why i am on gm1915
H4X0R46 said:
Does it really? I just ordered a 7 Pro yesterday so I don't have mine yet.
Click to expand...
Click to collapse
No it doesn't. I flashed the twrp installer zip with magisk and my wifi is working just fine.
---------- Post added at 09:24 PM ---------- Previous post was at 09:21 PM ----------
schmeggy929 said:
May want to fix Ture to True and after flashing the TWRP-installer reboot back to TWRP to make sure it sticks(Recovery Installed) before you flash Magisk zip.
Click to expand...
Click to collapse
schmeggy what up. I see you're still rockin the Bad BoyZ siggy