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?
Related
My apologies if this has already been posted. I've been looking all morning but haven't seen anyone with the same issue.
Unlock bootloader: no problem.
Flash TWRP: I downloaded from http://teamw.in/project/twrp2/275, and I got an error about partition size mismatch, but that's ok, right?
But when I try to enter recovery, all I get is the warning screen that my phone is unlocked. The drivers are certainly installed correctly, and fastboot is working fine. I just can't get into recovery to flash a ROM!
Restoring to 4.4.4 stock worked like a charm.
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
I've re-enabled USB debugging. Do I dare try to flash a custom recovery again?
Pandae said:
Do I dare try to flash a custom recovery again?
Click to expand...
Click to collapse
You can use Flashify to make a backup of your current recovery and to flash TWRP.img. should work like a charm.
But Flashify requires root, I see? The reason I'm trying to flash a custom recovery is so I can root in the first place.
Pandae said:
But Flashify requires root, I see? The reason I'm trying to flash a custom recovery is so I can root in the first place.
Click to expand...
Click to collapse
You're right. Latest motorola driver and [TOOL]Minimal ADB and Fastboot will do the trick.
Sorry, I should have clarified that when flashing TWRP, I've already been using fastboot.exe from a command line (and administrator level), with the drivers correctly installed. That's how I was able to unlock in the first place.
I did try it with the version of Fastboot you linked to (what I have works peachy for my Nexus 7), still the same thing. I can't boot into recovery and only get stuck at the Motorola unlocked warning.
Pandae said:
I can't boot into recovery and only get stuck at the Motorola unlocked warning.
Click to expand...
Click to collapse
Oh. Sorry. Can you post the output (terminal & device) of
Code:
fastboot devices
fastboot flash recovery NAME_OF_RECOVERY.img
I'd done "fastboot devices" already to verify, and it returns the serial number, though as I said it's clearly working since I was able to unlock as well as flash recovery. I'm flashing "TWRP2801-titan-motog-2014.img" that I downloaded from the TWRP site, and fastboot gives the standard messages about size and success (and my phone gives the size mismatch error).
It's so strange to me. I've flashed a custom recovery dozens of times on both generations of my Nexus 7s, but I've never seen this.
Pandae said:
It's so strange to me.
Click to expand...
Click to collapse
Yeah......have to meditate about that problem....... is your battery low? Fastboot mode of the device gives me all sorts of problems if it detects low battery
I had been using fastboot at 100% (literally finished a full charge) and 84%, but thanks for the continued attempts at explanation.
Oh, did you check the md5 checksum of your download?
Ah, good thought! I rarely do, but I did just now...and they're the same. It's crazy, isn't it?
Pandae said:
Ah, good thought! I rarely do, but I did just now...and they're the same. It's crazy, isn't it?
Click to expand...
Click to collapse
If you are willing to risk it, try a fresh download and try again. I've flashed TWRP more than 20 times by now and never recieved an error whatsoever. It basically the easiest thing to do.
Incase you are stuck again, don't reflash the entire stock rom. Just flash the recovery.img from the stock rom files.
OR
Try this:
HOW TO ROOT MOTO G 2014 with Temporary Custom Recovery
Cheers
I've flashed a custom recovery many a time and have helped people through it, though on Nexus 7s.
Now shall I compound the mystery? I didn't think yet to use ADB to make my phone reboot to recovery. I had assumed recovery wasn't working. So here we go, after booting into Android:
adb reboot devices: my phone's there.
adb reboot recovery: TWRP's working?! And now root is complete!
It doesn't make sense to me why I can't get into recovery from the bootloader, but I can get into it with the simple ADB command. But I appreciate all the help, thanks!
Pandae said:
It doesn't make sense to me why I can't get into recovery from the bootloader
Click to expand...
Click to collapse
A little workaround:
Install Android Terminal Emulator
Add "Term shortcut" widget.
In "Arguments" enter
Code:
su -c reboot recovery
I made a mistake and did not turn on the debug mode. So when trying to unlock the bootloader using the tool here:
http://forum.xda-developers.com/moto-g-2014/development/ultimate-moto-g-2014-toolkit-t2979862
it dint work. Now I keep getting "UTAG "flashfail" configured as fastboot" error. I have searched the forums and it seems I need to reflash the motorola boot img to get it to work.
Someone please help me out with it. I am on the latest 5.0.2 update for XT1068 - Indian version.
vicky_ag said:
I made a mistake and did not turn on the debug mode. So when trying to unlock the bootloader using the tool here:
http://forum.xda-developers.com/moto-g-2014/development/ultimate-moto-g-2014-toolkit-t2979862
it dint work. Now I keep getting "UTAG "flashfail" configured as fastboot" error. I have searched the forums and it seems I need to reflash the motorola boot img to get it to work.
Someone please help me out with it. I am on the latest 5.0.2 update for XT1068 - Indian version.
Click to expand...
Click to collapse
ok download the boot.img and use mfastboot to flash
reefuge said:
ok download the boot.img and use mfastboot to flash
Click to expand...
Click to collapse
Links to the boot image please
vicky_ag said:
Links to the boot image please
Click to expand...
Click to collapse
heres a flashable zip if you have custom recovery, or just use the boot.img (5.0.2) from unzipped file
Code:
mfastboot.exe flash boot boot.img
That worked. But now having another issue
I have rooted a lot of phones but this is the first I am stumbling my way through it. I unlocked the bootloader by going to Motorola's site and then went ahead and tried to root the phone using the tool mentioned in original post.
So the tool pushes the boot.img and reboots the phone. Then even when the phones boots in TWRP, the computer keeps saying waiting for device.
Now when I try to do a normal boot, I get the warning from Motorola but then phone wont bootup. No matter how much I wait or even try to re-flash the above image.
vicky_ag said:
That worked. But now having another issue
I have rooted a lot of phones but this is the first I am stumbling my way through it. I unlocked the bootloader by going to Motorola's site and then went ahead and tried to root the phone using the tool mentioned in original post.
So the tool pushes the boot.img and reboots the phone. Then even when the phones boots in TWRP, the computer keeps saying waiting for device.
Now when I try to do a normal boot, I get the warning from Motorola but then phone wont bootup. No matter how much I wait or even try to re-flash the above image.
Click to expand...
Click to collapse
Please don't use mfastboot. It is known for having problems with latest Android versions. You can use Minimal adb and fastboot or the the latest Android SDK.
Next make sure you have flashed the latest TWRP 2.8.4.0.
Wipe everything in twrp. Cache, dalvik and data.
MTP is a bit messed up (not just on our devices). Go to mount, disable mtp, unmount everything, connect usb and enable MTP. Now your device should appear on your computers file manager.
One last thing. Unless you flash the latest SuperSU 2.4.5, stock Lollipop will automatically remove twrp and reinstall stock recovery on the next boot (Actually there is another way. But why would you want to install TWRP without rooting the phone).
doppelhelix said:
Please don't use mfastboot. It is known for having problems with latest Android versions. You can use Minimal adb and fastboot or the the latest Android SDK.
Next make sure you have flashed the latest TWRP 2.8.4.0.
Wipe everything in twrp. Cache, dalvik and data.
MTP is a bit messed up (not just on our devices). Go to mount, disable mtp, unmount everything, connect usb and enable MTP. Now your device should appear on your computers file manager.
One last thing. Unless you flash the latest SuperSU 2.4.5, stock Lollipop will automatically remove twrp and reinstall stock recovery on the next boot.
Click to expand...
Click to collapse
Oh. After many tries now I am stuck in a bootloop. The phones goes to the "warning" then reboots for 5-6 times before it actually starts up. So I am wondering what will be the correct way to go about rooting and clearing this mess. And I see only SuperSu 2.4.0 in play store. has there been a latest version?
vicky_ag said:
The phones goes to the "warning" then reboots for 5-6 times
Click to expand...
Click to collapse
That's because off the outdated SuperSU. Get the latest .zip here http://forum.xda-developers.com/showthread.php?p=23427715
doppelhelix said:
That's because off the outdated SuperSU. Get the latest .zip here http://forum.xda-developers.com/showthread.php?p=23427715
Click to expand...
Click to collapse
So I went this way. I installed the recovery using the tool mentioned in the op. Installed SuperSU latest. Still when I go to bootloader and try recovery, nothing happens. I booted up the phone to see if SuperSU is installed and it appears fine in the apps. But the recovery wont load no matter what.
Another strange thing even when I am connected on 3G, I am not getting the icon.
vicky_ag said:
So I went this way. I installed the recovery using the tool mentioned in the op. Installed SuperSU latest. Still when I go to bootloader and try recovery, nothing happens. I re-tried installing recovery, still no go.
Click to expand...
Click to collapse
Then how did you install SuperSU if you can't get into recovery?
doppelhelix said:
Then how did you install SuperSU if you can't get into recovery?
Click to expand...
Click to collapse
I got in the first time using the tool mentioned in the op. I checked and it uses the command:
fastboot.exe boot twrp.img
This causes the phone to boot into twrp and I can copy the SuperSU to install. But the recovery still doesn't work.
vicky_ag said:
I got in the first time using the tool mentioned in the op. I checked and it uses the command:
fastboot.exe boot twrp.img
This causes the phone to boot into twrp and I can copy the SuperSU to install. But the recovery still doesn't work.
Click to expand...
Click to collapse
What are you talking about. TWRP is the recovery.
---------- Post added at 10:08 ---------- Previous post was at 10:06 ----------
Oh sorry. Now I understand. Please use this commands:
Code:
fastboot flash boot boot.img
fastboot flash recovery twrp.img
doppelhelix said:
What are you talking about. TWRP is the recovery.
Click to expand...
Click to collapse
Ok so this is what has happened:
1. I use the tool mentioned which uses the command:
fastboot.exe boot twrp.img
2. This causes the phone to boot into TWRP recovery. Then I installed SuperSU.
3. Rebooted the phone completely and checked the version of SuperSU.
4. Again went to the bootloader menu, selected TWRP. Nothing happens at this setup. phone doesn't boot at all. on clicking the power button it goes into normal boot
5. I tried going to the bootloader menu and running.
fastboot.exe flash recovery twrp.img
still no luck. Again trying to go from the bootloader menu to recoery yields no boot up.
vicky_ag said:
Ok so this is what has happened:
1. I use the tool mentioned which uses the command:
fastboot.exe boot twrp.img
2. This causes the phone to boot into TWRP recovery. Then I installed SuperSU.
3. Rebooted the phone completely and checked the version of SuperSU.
4. Again went to the bootloader menu, selected TWRP. Nothing happens at this setup. phone doesn't boot at all. on clicking the power button it goes into normal boot
5. I tried going to the bootloader menu and running.
fastboot.exe flash recovery twrp.img
still no luck. Again trying to go from the bootloader menu to recoery yields no boot up.
Click to expand...
Click to collapse
You are overriding the boot image with the recovery. The correct commands are
Code:
fastboot flash boot boot.img
fastboot flash recovery twrp.img
doppelhelix said:
You are overriding the boot image with the recovery. The correct commands are
Code:
fastboot flash boot boot.img
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
Just tried that:
C:\fastboot>fastboot.exe flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10200 KB)...
OKAY [ 0.496s]
writing 'boot'...
OKAY [ 0.438s]
finished. total time: 0.944s
C:\fastboot>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (9696 KB)...
OKAY [ 0.463s]
writing 'recovery'...
OKAY [ 0.433s]
finished. total time: 0.903s
Click to expand...
Click to collapse
Still when I go to the bootloader and select recovery, phone doesn't boot up at all.
vicky_ag said:
Just tried that:
Still when I go to the bootloader and select recovery, phone doesn't boot up at all.
Click to expand...
Click to collapse
Ok. Let's try this.
Can you boot normally into android? If so, please look if SuperSU is installed. If so, go to play store and install Android Terminal Emulator.
Open it and type
Code:
su
Supersu should pop up. Allow root.
Next type
Code:
reboot recovery
The device should boot into recovery. ( some people have this problem)
doppelhelix said:
Ok. Let's try this.
Can you boot normally into android? If so, please look if SuperSU is installed. If so, go to play store and install Android Terminal Emulator.
Open it and type
Code:
su
Supersu should pop up. Allow root.
Next type
Code:
reboot recovery
The device should boot into recovery. ( some people have this problem)
Click to expand...
Click to collapse
Thanks that works
vicky_ag said:
Thanks that works
Click to expand...
Click to collapse
Nice. Until you can go directly to the recovery, be very carefull not to leave the recovery without having flashed a rom and SuperSU. Also make sure that you grant adb access by accepting the RSA key when connecting the device with your computer. Just in case.
doppelhelix said:
Nice. Until you can go directly to the recovery, be very carefull not to leave the recovery without having flashed a rom and SuperSU. Also make sure that you grant adb access by accepting the RSA key when connecting the device with your computer. Just in case.
Click to expand...
Click to collapse
I am actually fine with a stock ROM on Motorola for now. They have lesser fluff than samsung et al. The major reason for trying to root the phone was to get TitanBackup working, I have been preserving some apps at a particular version in my last phone. The only way I found to restore the app and data was to use TitanBackup. The whole unlock the bootloader was because of Motorola adding a step to do this.
Adding recovery was an addition just in case Motorola forgets about us 1 year down the line. Then might flash to CM or something
TWRP Recovery v.3.0 for BLU_VIVO_XL (gionee6753_65u_l1)
based on firmware version BLU_V0030UU_V07_GENERIC_5.1_20160126-1033 / Tue Jan 26 10:33:33 CST 2016 / Android 5.1
How do we go about to install this
jemmini said:
TWRP Recovery v.3.0 for BLU_VIVO_XL (gionee6753_65u_l1)
based on firmware version BLU_V0030UU_V07_GENERIC_5.1_20160126-1033 / Tue Jan 26 10:33:33 CST 2016 / Android 5.1
Click to expand...
Click to collapse
Is this confirmed to work? I tried flashing the TWRP for the Blu Pure XL and the phone boot looped. I was able to unlock the bootloader ADB but after flashing TWRP the phone bootlooped.
ItGuyJax8430 said:
Is this confirmed to work? I tried flashing the TWRP for the Blu Pure XL and the phone boot looped. I was able to unlock the bootloader ADB but after flashing TWRP the phone bootlooped.
Click to expand...
Click to collapse
flash the original recovery (from fastboot mode).
loading recovery and system loading - are two different things...
p.s. recovery was tested.
jemmini said:
flash the original recovery (from fastboot mode).
loading recovery and system loading - are two different things...
p.s. recovery was tested.
Click to expand...
Click to collapse
10-4 ill give the recovery a go. I knew there was a difference, I was just giving extra info on my situation. I just got my replacement phone in today, ill give the recovery a go.
ItGuyJax8430 said:
10-4 ill give the recovery a go. I knew there was a difference, I was just giving extra info on my situation. I just got my replacement phone in today, ill give the recovery a go.
Click to expand...
Click to collapse
give me the boot.img and recovery.img files from your firmware. and the file /proc/emmc from the system
and I'll make TWRP for you...
It works. Thank you jemmini!
Edit: It appears I spoke too soon. Recovery works, but now the phone is in a constant boot loop.
2nd update: By some miracle, I got the phone to stop looping and just stay on recovery by randomly pressing buttons.
During the loop, I get this message.
after unlocking the bootloader you need for the first time to boot the system with the original recovery. and only after that to flash the TWRP...
jemmini, do you have a backup of the stock rom? If so, can you upload it? Thank you.
jemmini said:
after unlocking the bootloader you need for the first time to boot the system with the original recovery. and only after that to flash the TWRP...
Click to expand...
Click to collapse
Can you provide step by step instructions?
I imagine it would be something like this.
1. Developer Options > Enable OEM Unlock
2. Enable USB Debugging
3. Reboot to bootloader
4. fastboot oem unlock
5. fastboot reboot? (boot back into system) << i think this is where people are getting boot loop
6. reboot to bootloader
7. fastboot flash recovery (twrp recovery.img)
8. reboot to recovery
9. profit?
---------- Post added at 07:50 AM ---------- Previous post was at 07:46 AM ----------
xdadev_user11 said:
jemmini, do you have a backup of the stock rom? If so, can you upload it? Thank you.
Click to expand...
Click to collapse
If you have no other option, you can try this.. http:// firmwarefile.com/gionee-s-plus
emowing said:
Can you provide step by step instructions?
Click to expand...
Click to collapse
1. Developer Options > Enable OEM Unlock
2. Enable USB Debugging
3. Reboot to bootloader
4. fastboot oem unlock
4.1. fastboot oem unlock confirm
5. fastboot reboot? (boot back into system) << i think this is where people are getting boot loop
6. reboot to bootloader
7. fastboot flash recovery (twrp recovery.img)
8. reboot to recovery
9. profit.
jemmini said:
give me the boot.img and recovery.img files from your firmware. and the file /proc/emmc from the system
and I'll make TWRP for you...
Click to expand...
Click to collapse
I'm planning on trying out TWRP later today. Before I do that, what files should I grab (as a backup) and from where should I grab them? I'm happy to upload them for others, too.
So I will be able to root the phone with this? After unlocking bootloader and flashing twrp I flash supersu?
jemmini said:
1. Developer Options > Enable OEM Unlock
2. Enable USB Debugging
3. Reboot to bootloader
4. fastboot oem unlock
4.1. fastboot oem unlock confirm
5. fastboot reboot? (boot back into system) << i think this is where people are getting boot loop
6. reboot to bootloader
7. fastboot flash recovery (twrp recovery.img)
8. reboot to recovery
9. profit.
Click to expand...
Click to collapse
@jemmini I've never heard of the command fastboot oem unlock confirm before. Is this a command to run or do you mean we should do a fastboot getvar all and check the bootloader unlock status for a yes? Sorry for the newbie question. I've never needed to do this with a nexus.
emowing said:
@jemmini I've never heard of the command fastboot oem unlock confirm before. Is this a command to run or do you mean we should do a fastboot getvar all and check the bootloader unlock status for a yes? Sorry for the newbie question. I've never needed to do this with a nexus.
Click to expand...
Click to collapse
The confirmation he means is after you execute the unlock command, on the phone screen asks you to confirm by press volume up. That all.
[del]
xdadev_user11 said:
It works. Thank you jemmini!
Edit: It appears I spoke too soon. Recovery works, but now the phone is in a constant boot loop.
2nd update: By some miracle, I got the phone to stop looping and just stay on recovery by randomly pressing buttons.
Click to expand...
Click to collapse
The same thing happened to me.
After I was able to get into recovery using your steps, I formated ONLY the /data partition and rebooted. The phone then booted up properly after that.
I then downloaded the SuperSU ZIP file and rooted my phone through recovery .
I hope this helps someone.
acotto said:
The same thing happened to me.
After I was able to get into recovery using your steps, I formated ONLY the /data partition and rebooted. The phone then booted up properly after that.
I then downloaded the SuperSU ZIP file and rooted my phone through recovery .
I hope this helps someone.
Click to expand...
Click to collapse
Nice find :good:. I'll try it when I get my phone.. it will be delivered today.
emowing said:
If you have no other option, you can try this.. http:// firmwarefile.com/gionee-s-plus
Click to expand...
Click to collapse
So I unlocked bootloader and also got the bootloop. I flashed this firmware to fix it, but I found out the radio included is not the same as the US version, so now the sim cards don't work.
The firmware image have a file called "MT6753_Android_scatter.txt" which determine what partition to flash. Base on this guide http://www.mtkroms.com/2015/03/how-to-restore-lost-imei-on-any.html, the "secro" partition being replaced may be what caused the issue, so looked like that's what I have unchecked before flashing.
jemmini said:
..
Click to expand...
Click to collapse
I just discovered that you can back the secro and many other partition within TWRP. I don't know if that alone will fix the sim problem. WRONG
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
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