[ROOT][RECOVERY][Xposed] worked/confirmed Blu Vivo XL. No need unlock bootloader. - Blu Vivo XL

First I want to thanks emowing for his finding the brother of this Blu Vivo XL, it is Gionee Elife S Plus.
Whole thing: https://blog.hovatek.com/how-to-root-gionee-elife-s-plus/
Step1: Install Vcom Driver manually. This intend to use for the SP Flash tool to work.
https://forum.hovatek.com/thread-440.html
Step2: Run SP Flash tool to install CWM recovery.
*** When read from scatter file, choose RECOVERY ONLY.
https://forum.hovatek.com/thread-159.html
Step3: please do backup to excard (sdcard1) before install superSU.zip
Step4: root, by installing superSU using CWM.
*** Xposed:
Download the latest version of Xposed for sdk22 and arm64 from here.
As of this writing it is xposed-v80-sdk22-arm64.zip.
Also download XposedInstaller_3.0_alpha4.apk and xposed-uninstaller-20150831-arm64.zip (just in case).
Reboot into CWM or TWRP and do a full backup
Install framework xposed-v80-sdk22-arm64.zip and then reboot
Cross your fingers and hopefully your phone will start properly. Initial boot would take longer than normal, plus rebooted like five times during the "Android is starting" (orange color on white background) step but finally finished.
Once your phone boots up install app XposedInstaller_3.0_alpha4.apk
Now you are ready for your favorite modules.

quyvinh said:
First I want to thanks emowing for his finding the brother of this Blu Vivo XL, it is Gionee Elife S Plus.
Whole thing: https://blog.hovatek.com/how-to-root-gionee-elife-s-plus/
Step1: Install Vcom Driver manually. This intend to use for the SP Flash tool to work.
https://forum.hovatek.com/thread-440.html
Step2: Run SP Flash tool to install CWM recovery.
https://forum.hovatek.com/thread-159.html
Step3: please do backup to excard (sdcard1) before install superSU.zip
Step4: root, by installing superSU using CWM.
*** Xposed:
Download the latest version of Xposed for sdk22 and arm64 from here. As of this writing it is xposed-v79-sdk22-arm64.zip. Also download XposedInstaller_3.0_alpha4.apk and xposed-uninstaller-20150831-arm64.zip (just in case).
Reboot into CWM or TWRP and do a full backup
Install xposed-v79-sdk22-arm64.zip and then reboot
Cross your fingers and hopefully your phone will start properly. Initial boot would take longer than normal, plus rebooted like five times during the "Android is starting" (orange color on white background) step but finally finished.
Once your phone boots up install XposedInstaller_3.0_alpha4.apk
Click to expand...
Click to collapse
I gave Xposed a try yesterday so that I could use Amplify. I started getting reboots when I started setting up Amplify. Did basically everything you said in this post. I think it had something to do with the 3.0 installer. Not sure though.
Sent from my VIVO XL using Tapatalk

ItGuyJax8430 said:
I gave Xposed a try yesterday so that I could use Amplify. I started getting reboots when I started setting up Amplify. Did basically everything you said in this post. I think it had something to do with the 3.0 installer. Not sure though.
Sent from my VIVO XL using Tapatalk
Click to expand...
Click to collapse
1. Make sure you have correct file of framework install in recovery.
2. Restart into android, then install xposed app
3. install amplify module.
Mine is running well. Tested and work with: Lucky Patcher, Greenify w/experiment.
However, not working: GravityBox.
*** Not all module is working for Android 5.1 ***
Sorry, my knowledge is limited, as I am still learning. 'Just want to share what I have. Thanks.

quyvinh said:
1. Make sure you have correct file of framework install in recovery.
2. Restart into android, then install xposed app
3. install amplify module.
Mine is running well. Tested and work with: Lucky Patcher, Greenify w/experiment.
However, not working: GravityBox.
*** Not all module is working for Android 5.1 ***
Sorry, my knowledge is limited, as I am still learning. 'Just want to share what I have. Thanks.
Click to expand...
Click to collapse
I used v80, maybe that was the issue. I'll give v79 a go and see if that fixes it.
Sent from my VIVO XL using Tapatalk

ItGuyJax8430 said:
I used v80, maybe that was the issue. I'll give v79 a go and see if that fixes it.
Sent from my VIVO XL using Tapatalk
Click to expand...
Click to collapse
make sure it is sdk22 arm64

quyvinh said:
make sure it is sdk22 arm64
Click to expand...
Click to collapse
Just installed, I'll keep you posted if I get reboots. I have Amplify installed as well with the default wakelock recommendations.
Sent from my VIVO XL using Tapatalk

Is Gionee Elife S Plus recovery fully working on Blu Vivo XL? need any modification on MT6753_Android_scatter.txt?
Saw a few people bricked Vivo XL, a little scared.

min1968 said:
Is Gionee Elife S Plus recovery fully working on Blu Vivo XL? need any modification on MT6753_Android_scatter.txt?
Saw a few people bricked Vivo XL, a little scared.
Click to expand...
Click to collapse
Please do not modify anything. To make it easy, Blu Vivo XL is the same Gionee Elife S Plus.
Tested. Worked. No need unlock bootloader.

In this linek: https://forum.hovatek.com/thread-159.html
it shows example selected checkboxs of recovery and android. Should we only select "recovery"?
quyvinh said:
Please do not modify anything. To make it easy, Blu Vivo XL is the same Gionee Elife S Plus.
Tested. Worked. No need unlock bootloader.
Click to expand...
Click to collapse

Recovery ONLY

quyvinh said:
Recovery ONLY
Click to expand...
Click to collapse
I flashed CWM recovery, enter it flashed supersu, and reboot, now it stopped at white screen with back "BLU Android" text.
Tried enter CWM recovery again, wipe data or cache, but always stay at "wipe cache...." screen. Have to remove battery to enter CWM recovery again...
What should I do now?
Can anybody upload CWM backup-ed ROM so I can restore?
---------- Post added at 03:46 PM ---------- Previous post was at 03:02 PM ----------
I wonder if this CWM recovery has something wrong. I tried to backup to builtin ROM, it says cannot backup; then I tried to back to MicroSD, after about 10 min it still says cannot backup, and also, my MicroSD cannot be recognized by any device (my PC, camera, and This phone itself anymore.

*** You are in soft brick now. As long as you can get into recovery, you are OK. Please find out how to change to TWRP, and flash the backup rom from this post. http://forum.xda-developers.com/vivo-xl/how-to/rom-warning-please-read-unlock-t3313857***
It sad to hear you are in problem. Did you do the step#3? Do nand backup before flashing superSU?
If you did, then you should have your own a ROM back up.
Moreover, I do not know how could you end up in this situation. Any one have the same problem? I need to gather all popular problem into one place and try to figure out the safeway.
I feel bad if more people have problem with this method. Honesty, I succeeded with this method. Then come here and share with all of you. Please do at your own risk. If I see more problem then I will turn my thread down.
min1968 said:
I flashed CWM recovery, enter it flashed supersu, and reboot, now it stopped at white screen with back "BLU Android" text.
Tried enter CWM recovery again, wipe data or cache, but always stay at "wipe cache...." screen. Have to remove battery to enter CWM recovery again...
What should I do now?
Can anybody upload CWM backup-ed ROM so I can restore?
---------- Post added at 03:46 PM ---------- Previous post was at 03:02 PM ----------
I wonder if this CWM recovery has something wrong. I tried to backup to builtin ROM, it says cannot backup; then I tried to back to MicroSD, after about 10 min it still says cannot backup, and also, my MicroSD cannot be recognized by any device (my PC, camera, and This phone itself anymore.
Click to expand...
Click to collapse

I have tWRP Recovery now.
There are 4 files in ROM backup folder, I merged two win.000 and win,001 files into one file as .win, how to deal with another win000.md5?
Putting 2 files(boot.emmc.win and merged system.ext4.win) in new SD card and restored, now always boot to tWPR recovery, cannot see "Blu Android " screen... and idea?
Thanks.
quyvinh said:
*** You are in soft brick now. As long as you can get into recovery, you are OK. Please find out how to change to TWRP, and flash the backup rom from this post. http://forum.xda-developers.com/vivo-xl/how-to/rom-warning-please-read-unlock-t3313857***
It sad to hear you are in problem. Did you do the step#3? Do nand backup before flashing superSU?
If you did, then you should have your own a ROM back up.
Moreover, I do not know how could you end up in this situation. Any one have the same problem? I need to gather all popular problem into one place and try to figure out the safeway.
I feel bad if more people have problem with this method. Honesty, I succeeded with this method. Then come here and share with all of you. Please do at your own risk. If I see more problem then I will turn my thread down.
Click to expand...
Click to collapse

can you redo with out merged?

Finally got my phone up.
I used tWRP restored without merge files, but still always boot to recovery. Then I flashed back to original recovery ; powered on, it went to factory recovery, from there I selected boot, it boot clean.
quyvinh said:
can you redo with out merged?
Click to expand...
Click to collapse

I am glad to know your phone is good now. Thanks for sharing.

I challenged again, now I get my Vivo XL rooted.
Basically I re-do OP's steps, except:
1, Use TWRP recovery image instead of CWM
(from this thread: http://forum.xda-developers.com/vivo-xl/how-to/rom-warning-please-read-unlock-t3313857)
2, after flashing recovery, enter TWRP to clear data.
No need unlock boot loader.
And I found it's actually had to really brick this phone, since you can easily switch recovery (TWRP, CWM and original), and fact is, original recovery + stock rom restore is always working.

This could work for the Blu Vivo 5? (Most of the specs are the same)

I can't for the life of me get any of my 3 computers (2 are Windows 10, one is Windows 7, all 3 are 64-bit) to recognize the phone using the VCOM drivers. I installed them as I believe I'm supposed to, prior to connecting it to the computer:
1.) Open Device Manager
2.) Right-click PC name
3.) Select "Add legacy hardware"
4.) Manually install drivers (I used /MediaTek USB VCOM drivers/USB VCOM Driver/Win7/usb2ser_Win764.inf)
5.) Select "MediaTek PreLoader USB VCOM Port" (it's been assigned to COM 8)
I get a notice that it's been installed correctly, but may not work (I assume because it's legacy / not verified) and it shows up in my list, but it has a yellow exclamation point. When plugging in the phone, it comes up as either MTP (also with a yellow exclamation point) or under Android Devices (or similar)...which one depends on the computer. And yes, I've tried restarting the computer before plugging it in.
In any case, I can almost always use ADB to get into the phone, but when running MTK Droid Tool Kit, it's never recognized. And when I run ADB using the Kit's included install, it never starts the ADB server (even after running kill-server / start-server / list devices).
Thoughts? The fact that y'all haven't had trouble makes me think I'm missing something obvious. Not sure what it is, though. Wrong driver?

I was finally able to install custom recovery (I used TWRP instead of CWM) and get the phone rooted using SuperSU, but the included instructions weren't clear enough for me. I'm not new to rooting and flashing, but I am new to Mediatek and maybe that's the problem. Or maybe it's just a reading comprehension fail on my part. Anyway, I uninstalled everything via USB Deview, restarted, installed VCOM drivers manually, restarted, removed battery and plugged phone in. Waited a few moments before running the SP Flash Tool.
One thing I didn't pick up on that this tutorial (http://www.guruswizard.com/2016/01/root-gionee-elife-s-plus-and-install-cwm-recovery.html) made clear was the location of the scatter file. I thought I was supposed to generate it myself. I replaced the CWM "recovery.img" with the TWRP one (kept the same name) so that when I loaded the scatter file, it would use TWRP instead of CWM.
I figure we're stuck with the stock ROM for now? Anyone aware of CM development for the Vivo XL or Elife S Plus?

Related

[Q] I managed to remove my os on my phone. Help please!

I want to start this off with that i really don't know anything about ROMs and flashing and stuff like that, so just hold that in mind. I am pretty sure that I have the international version of the HTC One since I live in Sweden.
Ok, so here is what happened: I rooted my phone bu using TWRP 2.6.3.3 and SuperSU 1.91. The reason i wanted to root my phone was to be able to use an app that you can only use if you have rooted your phone. When i rooted my phone and downloaded the app it said that i needed to uppdate my busybox so i downloaded a busybox installer from the appstore. When i tried to uppdate my busybox to the latest version it wouldnt work for some reason so i was going to re-root my phone with Superuser instead. However when I couldnt drag the Superuser folder into my sd card i started messing around in twerp recovery and being an idiot as i am i did a "Format data" in TWRP, when i did that obviusly everything got removed and now i don't have an os the only things i can do is booting into bootloader and TWRP otherwise my device is stuck on the HTC bootscreen. Also when i connect my phone to my computer nothing pops up so im guessing that my computer can't recognise it anymore.
I have using google but i couln't find anything. I will be monitoring this thread like a hawk so please help me.
Edit: Here is more information: I have S-on, it also says ***tampered*** and ***unlocked***
Edit2:If you need any more information for helping me please let me know and ill get it.
TL;DR: Rooted HTC One with SuperSU, Formatted data, no os, need help.
Cyanisyde said:
I want to start this off with that i really don't know anything about ROMs and flashing and stuff like that, so just hold that in mind. I am pretty sure that I have the international version of the HTC One since I live in Sweden.
Ok, so here is what happened: I rooted my phone bu using TWRP 2.6.3.3 and SuperSU 1.91. The reason i wanted to root my phone was to be able to use an app that you can only use if you have rooted your phone. When i rooted my phone and downloaded the app it said that i needed to uppdate my busybox so i downloaded a busybox installer from the appstore. When i tried to uppdate my busybox to the latest version it wouldnt work for some reason so i was going to re-root my phone with Superuser instead. However when I couldnt drag the Superuser folder into my sd card i started messing around in twerp recovery and being an idiot as i am i did a "Format data" in TWRP, when i did that obviusly everything got removed and now i don't have an os the only things i can do is booting into bootloader and TWRP otherwise my device is stuck on the HTC bootscreen. Also when i connect my phone to my computer nothing pops up so im guessing that my computer can't recognise it anymore.
I have using google but i couln't find anything. I will be monitoring this thread like a hawk so please help me.
Edit: Here is more information: I have S-on, it also says ***tampered*** and ***unlocked***
TL;DR: Rooted HTC One with SuperSU, Formatted data, no os, need help.
Click to expand...
Click to collapse
Don't panic mate, it's ok you didn't break anything.
Ok, so you can go into twrp. That's enough
All you have to do is installing a custom ROM and you will have your phone back.
Follow this guide: http://forum.xda-developers.com/showthread.php?t=2183023 to install Android revolution HD 51 (4.4.2 android)
Since you can't access the internal SD from your computer, you will have to Sideload it. Don't worry nothing so difficult:
Here is the guide: http://forum.xda-developers.com/showthread.php?t=2318497
So: -Download the file from the first link.
- sideload it into your TWRP
- install it from twrp
- Done!!
Uxepro said:
Don't panic mate, it's ok you didn't break anything.
Ok, so you can go into twrp. That's enough
All you have to do is installing a custom ROM and you will have your phone back.
Follow this guide: http://forum.xda-developers.com/showthread.php?t=2183023 to install Android revolution HD 51 (4.4.2 android)
Since you can't access the internal SD from your computer, you will have to Sideload it. Don't worry nothing so difficult:
Here is the guide: http://forum.xda-developers.com/showthread.php?t=2318497
So: -Download the file from the first link.
- sideload it into your TWRP
- install it from twrp
- Done!!
Click to expand...
Click to collapse
THANK YOU SO MUCH FOR THIS! I will be trying this right now!
Uxepro said:
Don't panic mate, it's ok you didn't break anything.
Ok, so you can go into twrp. That's enough
All you have to do is installing a custom ROM and you will have your phone back.
Follow this guide: http://forum.xda-developers.com/showthread.php?t=2183023 to install Android revolution HD 51 (4.4.2 android)
Since you can't access the internal SD from your computer, you will have to Sideload it. Don't worry nothing so difficult:
Here is the guide: http://forum.xda-developers.com/showthread.php?t=2318497
So: -Download the file from the first link.
- sideload it into your TWRP
- install it from twrp
- Done!!
Click to expand...
Click to collapse
I just have one question: Do i download the HD 31.6 or do i download HD 51.0 version of the ROM?
Cyanisyde said:
I just have one question: Do i download the HD 31.6 or do i download HD 51.0 version of the ROM?
Click to expand...
Click to collapse
51.0!
Uxepro said:
51.0!
Click to expand...
Click to collapse
Thank you once again!
Cyanisyde said:
Thank you once again!
Click to expand...
Click to collapse
You are welcome! Last raccomandations, when you flash Android rev. remember to select the wipe option in Aroma installer.
Also at the end of the installation press on "wipe davilk cache"
If you encounter bootloop do a "fastboot erase cache".
Also, remember that the first boot after flashing it takes long time (even 10 mins) and it's seems stuck on the htc logo but it's not
Good luck!

Stuck in boot up screen

ok, i am stuck on my boot up screen. i flashed a zip file xposed arm zip. after the reboot it will not pass the boot animation screen. now on my old Motorola phone, i would do the pwr + vol keys to boot back in to recovery. well this does no work on my X. any one have any ideas. I am rooted, unlocked, twrp was installed from play store, & i did do a back up. thanks
JWACK72 said:
ok, i am stuck on my boot up screen. i flashed a zip file xposed arm zip. after the reboot it will not pass the boot animation screen. now on my old Motorola phone, i would do the pwr + vol keys to boot back in to recovery. well this does no work on my X. any one have any ideas. I am rooted, unlocked, twrp was installed from play store, & i did do a back up. thanks
Click to expand...
Click to collapse
What device do you have, XT1095, XT1097, etc? And you are not able to boot into the bootloader using vol down + power correct?
It was a 1096, now its trash. it would go into fastboot, but could not get into twrp recovery. its done. RIP
JWACK72 said:
It was a 1096, now its trash. it would go into fastboot, but could not get into twrp recovery. its done. RIP
Click to expand...
Click to collapse
If it boots to fastboot, it's not dead. Just reflash the recovery and you're good to go.
Sent from my XT1095 using Tapatalk
Was there a resolution for this? I'm having a similar problem. I'm not sure how I got to this status, but here's what I'm dealing with:
Device: XT1095
Bootloader: Unlocked
Rooted, ROM - Resurrection Remix, TWRP
Turning on the phone reaches the RR bootsplash and proceeds to bootloop.
When holding down the power and volume down, it will enter fastboot.
When I try to open TWRP recovery, it'll show the blue TWRP screen and just sit there.
I have tried to reinstall TWRP, but that has no effect. I didn't want to manually flash another ROM or go back to stock because at least now it seems USB debugging is on and if I flashed a ROM I cant be sure I'd be able to turn it on. Do any of you pros have some ideas hove I can get back into my phone? Thanks
bibbin said:
I have tried to reinstall TWRP, but that has no effect. I didn't want to manually flash another ROM or go back to stock because at least now it seems USB debugging is on and if I flashed a ROM I cant be sure I'd be able to turn it on. Do any of you pros have some ideas hove I can get back into my phone? Thanks
Click to expand...
Click to collapse
Do you have a USB-OTG device plugged in while trying to start TWRP? If so remove it, you can mount it after TWRP starts if this helps.
Have you tried a different build of TWRP? I'm currently using the one built by invisiblek, one of the CM devs for the victara. It was built and posted on December 8th and is here: http://www.invisiblek.org/twrp/twrp_2.8.7.0-0624b8bd_victara.img
Have you tried flashing the stock recovery to see if that will start? If it does, you could use the factory reset option there and then try reinstalling TWRP. (TWRP has a settings directory in /sdcard and maybe that is corrupted.)
There have been a few people posting with this problem but I've not seen a definitive fix for it.
Thank for the quick response. No, I don't have USB-OTG inserted. It is using TWRP 2.8.7.1. No, I haven't tried installing the version you mentioned. What I did do was attempt to flash the pre-installed TWRP 2.8.1.0 via MOTO X TOOLKIT. It failed. I'm not very experienced at using ADB manually. As I mentioned, I've been reluctant to flash another ROM (custom or stock) because I don't want to get stuck with USB debugging inactive with no way to get in far enough to reactivate it.
---------- Post added at 04:32 PM ---------- Previous post was at 03:40 PM ----------
If I manage to install the invisiblek TWRP and it opens properly will I then be able to restore the backups created with TWRP 2.8.7.1?
If that's the case, I need to find a tutorial on installing TWRP manually via ADB, right? I usually install TWRP via TWRP Manager.
bibbin said:
Thank for the quick response. No, I don't have USB-OTG inserted. It is using TWRP 2.8.7.1. No, I haven't tried installing the version you mentioned. What I did do was attempt to flash the pre-installed TWRP 2.8.1.0 via MOTO X TOOLKIT. It failed. I'm not very experienced at using ADB manually. As I mentioned, I've been reluctant to flash another ROM (custom or stock) because I don't want to get stuck with USB debugging inactive with no way to get in far enough to reactivate it.
---------- Post added at 04:32 PM ---------- Previous post was at 03:40 PM ----------
If I manage to install the invisiblek TWRP and it opens properly will I then be able to restore the backups created with TWRP 2.8.7.1?
If that's the case, I need to find a tutorial on installing TWRP manually via ADB, right? I usually install TWRP via TWRP Manager.
Click to expand...
Click to collapse
That's interesting, the TWRP Manager has never worked correctly for me although it's been a long time since I've tried it.
To flash manually, you actually need fastboot which is usually installed along with adb. If you open a command window, and type in fastboot and it runs, the rest is pretty easy. If it doesn't run, this thread has the 15 second ADB/Fastboot installer, select to install it system-wide: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Download the recovery image, rename the file to twrp.img, then open a command window in the folder where you downloaded it (type cmd then Enter in the address line at the top of the folder window.)
When the command window is open and the phone is in bootloader mode and connected to the computer with the USB cable, enter the command "fastboot device" (without the quotes) If everything is working it will list the serial number of your phone.
Then enter "fastboot flash recovery twrp.img" (without the quotes) to start the flashing process, ignore the size mismatch message. It will only take a few seconds to complete.
Use the volume down key to highlight recovery, then volume up to select it. Hopefully TWRP will boot up and you'll be good to go!
Well, reinstalling TWRP didn't fix it. Thoughts? Anyone?
bibbin said:
Well, reinstalling TWRP didn't fix it. Thoughts? Anyone?
Click to expand...
Click to collapse
Reflash stock rom from fastboot.
Sent from my XT1095 using Tapatalk
UPDATE: Thanks all. Well, after fiddling around with various methods of reinstalling TWRP, I managed to get it reinstalled and all is back to normal now.

Order of things to be done - unlocking/flashing etc

I intend to create a post with how to do things on this phone.
Just bought the 64GB Black.
So, trying to pull the order of things to be done.
Please help, this is for newbies.
When you receive it. What should be done first? (and how did you do it???)
(EDIT : I will update this as I find things out.)
Bootloader
Follow the guide found here : http://xiaomitips.com/guide/unlock-mi-5-bootloader/
You should do this in advance of getting your phone.
Recovery - TWRP
Guide here : http://en.miui.com/thread-245756-1-1.html
Which ROM to install?
CM alternative?
Gapps?
If you own the Mi5, how did you go about it? Any tips? What went wrong? How did you fix?
First I unlocked my bootloader, which is essential to do first. Then I flashed TWRP using the ADB terminal thing on my computer via USB. After I had TWRP, I rooted my phone using SuperSU. But I was bored of MIUI so I flashed Cyanogenmod 13 in the thread in the MI 5 ROM forum. I have not changed anything since then really, I'm using the root that comes with CM now. It's all really good.
Edit: make sure you flash google apps at the SAME TIME as cyanogenmod! Without booting in between! Also the snapchat camera doesn't work right now for CM but if you use the app casper.io (not on play store, google it) you can use the phones camera app and then it works fine.
regnarox said:
First I unlocked my bootloader, which is essential to do first. Then I flashed TWRP using the ADB terminal thing on my computer via USB. After I had TWRP, I rooted my phone using SuperSU. But I was bored of MIUI so I flashed Cyanogenmod 13 in the thread in the MI 5 ROM forum. I have not changed anything since then really, I'm using the root that comes with CM now. It's all really good.
Edit: make sure you flash google apps at the SAME TIME as cyanogenmod! Without booting in between! Also the snapchat camera doesn't work right now for CM but if you use the app casper.io (not on play store, google it) you can use the phones camera app and then it works fine.
Click to expand...
Click to collapse
Which TWRP did you use (link?)
Which GApps did you use? (Nano, pico, stock etc) and presumably ARM64?
since there isn't a sdcard, are you able to do a full backup so you can revert back to if you have second thoughts. I guess you have to do a full wipe prior to flashing e.g CM13
Questions about rooting
Hey I got a Mi5 64GB with unlocked bt and twrp installed.
Now I want to root the device but when I boot to twrp I can't flash files because the device is encrypted by default and in order to decrypt it I need to perform a full wipe or enter a password, I don't know the password because it's not a password I decided on, I don't really have a problem doing a full wipe I don't have any important data.
But here are my questions:
1. If I'll do a full wipe will I have to install MiUi and twrp again?
2. Right now if I connect my phone to my PC using USB when it's in recovery mode I can't use MTP and if I'll perform a full wipe the SuperSU.zip will get deleted from my device and I will have to get it back to the device somehow and I can't because I can't use MTP when I'm in recovery mode. So I thought maybe after the full wipe I will be able to use MTP on recovery maybe I can't because it's encrypted at the moment?
Thanks
TWRP - https://www.androidfilehost.com/?fid=24533103863138514 (no touch screen issue which is present in other recoveries)
GApps - http://opengapps.org/ (ARM64) I used microG instead of gapps to save a lot of battery. (You can google it if you want)
It doesn't really matter what GApps do you use, although I'd go for nano/pico. I wouldn't want all the GApps to be my system apps.
---------- Post added at 11:11 AM ---------- Previous post was at 11:02 AM ----------
Sachuan said:
Hey I got a Mi5 64GB with unlocked bt and twrp installed.
Now I want to root the device but when I boot to twrp I can't flash files because the device is encrypted by default and in order to decrypt it I need to perform a full wipe or enter a password, I don't know the password because it's not a password I decided on, I don't really have a problem doing a full wipe I don't have any important data.
But here are my questions:
1. If I'll do a full wipe will I have to install MiUi and twrp again?
2. Right now if I connect my phone to my PC using USB when it's in recovery mode I can't use MTP and if I'll perform a full wipe the SuperSU.zip will get deleted from my device and I will have to get it back to the device somehow and I can't because I can't use MTP when I'm in recovery mode. So I thought maybe after the full wipe I will be able to use MTP on recovery maybe I can't because it's encrypted at the moment?
Thanks
Click to expand...
Click to collapse
1. You just need to format data, your system partition will not be wiped. You will just lose everything except the system.
2. You probably will be able to use MTP, although I'm not but other people are so you should too. If you don't, you'll need to go to advanced in TWRP, enter adb sideload and sideload the zip.
[I deleted your quote becasue it said I can't post outside links]
Ok, thank you!
(I don't need to install twrp again right?)
Sachuan said:
[I deleted your quote becasue it said I can't post outside links]
Ok, thank you!
(I don't need to install twrp again right?)
Click to expand...
Click to collapse
No, you don't
proag said:
No, you don't
Click to expand...
Click to collapse
Good thanks!
Sent from my MI 5 using XDA-Developers mobile app

New to Rooting: Huawei honour 4x Android 6.0. Need help.

Hi,
I'm working with a Huawei Honour 4x, Android 6.0, Stock Rom, Model: CHE-TL00, EMUI 4.1
I'm looking to root it but could not find anything specific on google or XDA. I've read about systemless root for Android 6.0 but the material largely concerns the nexus phones.
I've got quite an odd brand with a specific model make which differs from other models of the Honour 4x.
Simply put, i'd like to root the device. Can anyone point me towards more information to achieve this ?
I've searched and failed. I'm hoping someone else may know where to look.
#Update: I have twrp installed.
#Update 2: I used TWRP to flash SuperSU. My phone failed to boot afterwards and kept looping. So i recovered using the Nandroid backup.
Back to square one. Any help would really appreciated.
#Update 3: Problem Solved. For anyone who has the same device, here are the steps to take.
1. Flash TWRP using Minimal ADB Flash and Boot
2. Use TWRP to flash the updated version of SuperSU (2.71 Beta). (HAS TO BE THIS VERSION or the latest version!!!)
Used: [BETA-SuperSU-v2.74-2-20160519174328-forced-systemless] or [BETA-SuperSU-v2.71-20160331103524]
3. Reboot; wait for a few minutes for phone to load.
4. Job done. Your phone should be rooted.
TWRP source: https://twrp.me/huawei/huaweihonor4x.html
Thanks for your sharing.
Hi, I recently updated to the 6.0 Rom and am trying to root it (using your guide)
1. Flash TWRP using Minimal ADB Flash and Boot
2. Use TWRP to flash the updated version of SuperSU (2.71 Beta). (HAS TO BE THIS VERSION or the latest version!!!)
Used: [BETA-SuperSU-v2.74-2-20160519174328-forced-systemless] or [BETA-SuperSU-v2.71-20160331103524]
3. Reboot; wait for a few minutes for phone to load.
4. Job done. Your phone should be rooted.
Click to expand...
Click to collapse
I can get my device to reboot into fastboot but it doesn't recognise the device after that?
(Just says "Waiting for device", and nothing shows up if I type 'Fastboot Devices')
Could you tell me what drivers you used? I really want to root it to try and get some space back
follow the steps anyway, dont worry if it say conecting in hisuite, and be sure u have hisuite installed, i.e, u have an hisuite.exe in the folder C:\Program Files (x86)\HiSuite\ .... and for the space, in hi suite desktop app u can uninstall some, goodluck!
Coedy said:
Hi, I recently updated to the 6.0 Rom and am trying to root it (using your guide)
I can get my device to reboot into fastboot but it doesn't recognise the device after that?
(Just says "Waiting for device", and nothing shows up if I type 'Fastboot Devices')
Could you tell me what drivers you used? I really want to root it to try and get some space back
Click to expand...
Click to collapse
I had the same issue. There're a lot of bloatware apps pre-installed which take up crucial internal space. It seems like it is a driver issue.
My process of achieving root was essentially trial and error, so there was a lot of google searching and installing; without making note of everything i installed (when concerning drivers).
So i won't pretend to be an expert but I'll list the most useful places i checked out.
Firstly, i download the basic Android command line tools from the SDK webpage.
Secondly, i followed the steps on the TWRP webpage (can't link as i'm a new user) I download their recommended drivers too.
Thirdly, (Since Huawei do support modification to an extent, you can find a set of their recommended drivers on google or on their webpage). I googled a set of USB drivers for the Honor 4x and downloaded these too.
Following this, I was able to connect my device successfully.
(Failing this, Google has a lot of content on connecting the Honour to Minimal ADB Flash and Boot. Check it out.) :good:
sr993 said:
Hi,
#Update 2: I used TWRP to flash SuperSU. My phone failed to boot afterwards and kept looping. So i recovered using the Nandroid backup.
Click to expand...
Click to collapse
Hi, my model is Ch2-L11 and I'm very noob and very likely to mess up the whole phone, so I was wondering How did you created a nandroid backup?
I installed the minimal adb tool that you suggested in your post. should I use "adb backup all" in cmd? or creating a nandroid backup is different?
Why not sharing where you sourced the TWRP you used is a mystery and makes this correctly referenced thread rather worthless.
thanks for share..

TWRP 3.2.3-1 for Pixel Devices

TLDR: It's here and it may eat your data, and you will lose SuperSU root if currently installed. READ the install instructions carefully!
Pixel XL
Pixel
DO NOT RESTORE DATA FROM alpha builds of TWRP using RC1. You will probably lose all data including internal storage. If you need to restore a data backup from an alpha build, reinstall the alpha and restore using the alpha and make a new backup using RC1.
Note: Do not use if you have multiple users (including a guest user)
File Based Encryption (FBE) can be a bit tricky. If a restore doesn't work correctly, it can trigger an automatic wipe of your data. Sometimes TWRP will fail to prompt you to enter your password or otherwise fail to set up decrypt properly. If this happens, reboot TWRP. It seems to be some kind of timing issue and I haven't had time to track it down yet.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
NOTE about 3.2.1-0: This version will decrypt Android 8.1, however the new image is built in Android 8.1 and may not be compatible with SuperSU and/or Magisk until they update their stuff. I have not tested. Good luck.
3.2.1-1 has working decrypt with the February security patch!
3.2.1-2 fixes some zip install errors
3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set
How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.
Amazing work sir! I think this is what we've all been waiting for! I mean I know I've been checking here frequently, hoping for this
Wow and so it begins, great work thanks!
Thanks
Sent from my Pixel using XDA-Developers mobile app
has anyone got the zip installed? when i boot into twrp.img everything is encrypted? im 100% stock as well
Dees_Troy said:
Note: I am going to be very busy the next couple of weeks. I probably won't be able to answer your questions or fix things immediately.
Click to expand...
Click to collapse
the pixel installer.zip is corrupt. :crying:
Really looking forward to having this and SuperSU working together. After that, I just need things to flash. Been going crazy not being able to appeasey crack flashing addiction.
GeekMcLeod said:
Really looking forward to having this and SuperSU working together. After that, I just need things to flash. Been going crazy not being able to appeasey crack flashing addiction.
Click to expand...
Click to collapse
Do you happen to have a copy of the .zip? All the ones I download are corrupt...
zaksimmermon said:
Do you happen to have a copy of the .zip? All the ones I download are corrupt...
Click to expand...
Click to collapse
No I haven't downloaded anything yet. Not going to until I can have supersu alongside twrp.
Why does installation of this remove SuperSU?
Aren't they supposed to be used side-by-side?
And it also warns not to install if expecting important calls.
Does it prevent the phone apps from operating or what?
I understand everything else.
Snowby123 said:
Why does installation of this remove SuperSU?
Aren't they supposed to be used side-by-side?
And it also warns not to install if expecting important calls.
Does it prevent the phone apps from operating or what?
I understand everything else.
Click to expand...
Click to collapse
"In other words, Chainfire's systemless root method modifies the same binary that TWRP needs to modify in order to get data decryption working. Therefore, when you flash TWRP you are overwriting the changes made to the init binary by Chainfire's systemless root method. While this is a minor setback, thanks to the dual partition nature of the Pixel (and future devices shipping with Nougat), TWRP has some nifty new capabilities."
I'm pretty sure he's just saying dont chance something going wrong like it bootlooping or wiping data if you need your phone for something important like a phone call. Tough to answer said phonecall in a boot loop.
zaksimmermon said:
has anyone got the zip installed? when i boot into twrp.img everything is encrypted? im 100% stock as well
Click to expand...
Click to collapse
I get exactly the same. Even after several attempts at booting the img, i don't get prompted to enter the PIN / passphrase as stated in instructions hence why the data is encrypted i presume.
rtthane said:
I get exactly the same. Even after several attempts at booting the img, i don't get prompted to enter the PIN / passphrase as stated in instructions hence why the data is encrypted i presume.
Click to expand...
Click to collapse
I finally got passed that issue. I had to flash factory images and erase everything to the point of being at setup screen. I didn't set anything up, no network or wifi, skipped Google sign in, no password and also no Google functions activated. This led to an unencrypted setup, so after turning on dev settings and Android debugging I booted up the image. Now my issue is the zip to install twrp for sailfish is corrupt and if you try to unzip it there are no files in it....I downloaded the marline zip and there are files when unzipped....
Maybe I'm an asshole but I cNt for the life of me flash this I download the .IMG I even changed name to TWRP.img but it won't flash boot at all just an error hmmmmm maybe I'm just dumb?
ne0ns4l4m4nder said:
Maybe I'm an asshole but I cNt for the life of me flash this I download the .IMG I even changed name to TWRP.img but it won't flash boot at all just an error hmmmmm maybe I'm just dumb?
Click to expand...
Click to collapse
Are you trying to fastboot flash or fastboot boot?
Sent from my Pixel using Tapatalk
Guys, check out super su and root in xl thread. New Super su posted by chain fire to work with twrp.
fracman said:
Guys, check out super su and root in xl thread. New Super su posted by chain fire to work with twrp.
Click to expand...
Click to collapse
Posted on standard pixel SU thread as well. Now if only I could make sense on the steps I need to take. This dual partition issue is throwing me off
ej_424 said:
Posted on standard pixel SU thread as well. Now if only I could make sense on the steps I need to take. This dual partition issue is throwing me off
Click to expand...
Click to collapse
My phone won't be here till tomorrow but as I understand it you need to use these steps (someone correct me if I'm wrong)
Reboot bootloader
Fastboot boot (twrp).img
Reboot recovery
In recovery, flash the twrp flashable .zip file
Reboot recovery
Flash the SuperSU sr4.zip
Reboot
Profit????
BakedTator said:
My phone won't be here till tomorrow but as I understand it you need to use these steps (someone correct me if I'm wrong)
Reboot bootloader
Fastboot boot (twrp).img
Reboot recovery
In recovery, flash the twrp flashable .zip file
Reboot recovery
Flash the SuperSU sr4.zip
Reboot
Profit????
Click to expand...
Click to collapse
OK thanks, wondering if root will work with November update or of I need to roll back first. Prior to SU update today Nov update didn't work with the auto cf root

Categories

Resources