Related
Hello to everyone.
I'm using Lenovo A560 and want to root it to delete all those junk, built-in apps so that my RAM usage will decrease. I have tried many times using various root software (rootgenius, kingo, framaroot) yet didn't successful to root my a560. I have already installed usb driver for lenovo a560. Anyone can help me? I already have tried to root my phone like in the http://forum.xda-developers.com/showthread.php?t=2769260 thread but still the same problem occurred.
When i used rootgenius, my phone just reboot and reboot until 86% and the process failed. same on the kingo (except my phone did not reboot like before, it just failed after a reboot). In framaroot, the #error 6 message pop out.
Anyone can help me how to root my phone please? My phone system:
Android 4.3
Baseband ver : A560_A_0001_140330
Kernel Ver: 3.4.0-g80ec9c8-01182-gb30d6a7-dirty [email protected] #6
Build Num : A560_S010_143330
#just put every details for that i'm a newbie in these things. Any help would be very appreciated. (manual root not recommended, but still can try~)
Thanks!
Same problem here. Anyone can help please? Android 4.3 running on Lenovo A560.
problem solved.
I finally managed to root my a560 by installing the driver from the phone into the PC . Then I used iRoot to root my phone. It works! I followed the methods provided by a Russian blog (cannot post outside link because I'm a new user,credit to the blog)
Here's the methods (translated, contains grammar errors).
Remember, you're doing it at your own risk. The site administrator can not be held liable for the actions that you make.
1. Download and install the program on your computer VRoot
2. Disable antivirus (as needed).
3. Run the program, connect the device to your computer (if it is not defined, then try to install the drivers from the official site of your device). On the phone should be included: Debugging via USB, install from unknown sources in the USB connection must be uncheck MTP and Camera (RTR).
4. Once the device is determined, press the bottom right button green "ROOT", and wait.
5. Then, after the last window, the device will reboot (And it can be disconnected from the computer).
6. Root entitled to receive!
Russification (Thanks to Timur):
- Set on the PC this Chinese VRoot
- Put on sotik "Chinese" root-rights
- Then go to the Play Store, we set out SuperSU
- Run it, he will offer to update binary.
- Click to continue, and then click "OK". Pops request of the Chinese root.
- Press the right button zelёnenkuyu. After SuperSU say that the installation is successful, it will prompt you to delete other applications control root-access.
- Click "Yes" forward (SuperSU remove our "Chinese" and replace it with a more simply). Writes again about the successful installation.
Note : The phone will ask you something in Chinese after you root the phone. Just click the right button when the phone pop-up something after you root. This is because right button is the 'YES' and left one is 'NO' and i think that is the phone is asking for root permission.
P/s : for some reason I cannot delete the pre-installed software on my phone, even using root explorer. Anyway, the softwares that need the phone rooted can be installed.
Hi everyone! I've used this forum for help rather often, but never made an account until just now.
Recently, I decided to get a new phone. Specifically, an Asus Zenfone 3 Laser(Model number ZC551KL / Z01BDC). However, there's no subforum for this device, and only one mention of this model across all of XDA, which is odd considering it's been out for about 2 weeks in most places, and was announced months ago. The same goes for it's brother the Zenfone 3 Max...even odder when 3/5 Zenfone 3 models have their own forums.
I'd like to know if anyone has set out to root this model of phone, as well as if it has a locked bootloader(as I'm not entirely sure about this, though I doubt it.)
As a sidenote...is there any way to try to get a subforum for this device? I'm fairly certain that it'll be a decent enough device to play around with, much like the Zenfone 2 laser. And I apologize if I placed this in the wrong forum.
z01bdc root
did you even find a method for this? can't find anything for z01bdc
zenfone 3 laser zcrr1kl managing
i 'm looking for to root too.
I'm not an expert, so i had found this but i'm not to decide to used still.
i left the link
http :// android-os .xyz /2016/11/ asus- zenfone -3-laser-zc551kl-8206. html
if somebody knows about this software, please tell me about this tool if its useful for root the smartphone.
thanks
Official ASUS Bootloader Unlock Tool Released
Check it out here:
asus.com/Phone/ZenFone-3-Laser-ZC551KL/HelpDesk_Download/
Root and ROMs will follow...
My phone Asus Zenfone 3 laser ZC551kl Z01BDB
Thanks for the link, I already unlock my phone bootloader. Anynews for spesific twrp and root for this phone ? I'm going crazy when Twrp and root release for this baby
https://forum.xda-developers.com/zenfone-3/help/how-to-root-zenfone-3-laser-zc551kl-t3502606
idiots guide, how to root zenfone 3 laser for dummies
my zenfone 3 POS! (laser) is now rooted. here is how i did it
1-in phone settings, go to security and turn on "unknown sources". then, also from settings, go to "about phone" then "software info", once there, tap build number several times until the phone gives you a message that your a developer. then go back to settings, and find "developer options" here you will see a "usb debugging" setting. turn this on.
2-with your zenfone, go to: asus.com/Phone/ZenFone-3-Laser-ZC551KL/HelpDesk_Download/ under utility, find and download/install the bootloader unlocking tool.
3-run the unlocker tool, keep in mind that it will do a factory reset, and all data will be lost. (backup files/pics/etc as needed) during the process, you will get a message that says " You do not have pin password to verify device, do you still want to unlock your device" tap yes
4-once completed, you will need to download a couple files. the twrp: https://depositfiles.com/files/ux8w5thp6 and *i now recomend magisk,
Not supersu* superdu: https://download.chainfire.eu/696/supersu/ move both files to the phones internal storage so they can be easily found.
5- with a pc, go to: https://forum.xda-developers.com/sho....php?t=2588979 just follow the steps on that thread and then after it is installed, the location where you have saved your twrp.img file you need to go to that folder and hold shift+right click on any empty space inside that folder of which you have saved twrp img and a context menu will come up with various options so select 'open command window here' then all you have to do is enable debugging on your asus zenphone 3 laser and then connect it to your pc and allow debugging on the device a menu will pop up, then inside the command window type "adb reboot bootloader" (remove quotations) then hit enter your phone will reboot to bootloader.
Next step is to type "fastboot flash recovery twrp-3.1.1.unofficial.img" (remove quotations) hit enter
6- now, using volume rockers to navigate and lock button as select, select recovery and wait
7- once the twrp loads, put in you devices lock pin, and continue to main menu. once there, select install, then look for the supersu .zip file *update, use magisk instead, see avove*(if you dont see it, look for a button that says "zip file" at botton right
8- done, please follow the instructions above at your own risk, im a nube.
Gt5228 said:
my zenfone 3 POS! (laser) is now rooted. here is how i did it
1-in phone settings, go to security and turn on "unknown sources". then, also from settings, go to "about phone" then "software info", once there, tap build number several times until the phone gives you a message that your a developer. then go back to settings, and find "developer options" here you will see a "usb debugging" setting. turn this on.
2-with your zenfone, go to: asus.com/Phone/ZenFone-3-Laser-ZC551KL/HelpDesk_Download/ under utility, find and download/install the bootloader unlocking tool.
3-run the unlocker tool, keep in mind that it will do a factory reset, and all data will be lost. (backup files/pics/etc as needed) during the process, you will get a message that says " You do not have pin password to verify device, do you still want to unlock your device" tap yes
4-once completed, you will need to download a couple files. the twrp: https://depositfiles.com/files/ux8w5thp6 and superdu: https://download.chainfire.eu/696/supersu/ move both files to the phones internal storage so they can be easily found.
5- with a pc, go to: https://forum.xda-developers.com/sho....php?t=2588979 just follow the steps on that thread and then after it is installed, the location where you have saved your twrp.img file you need to go to that folder and hold shift+right click on any empty space inside that folder of which you have saved twrp img and a context menu will come up with various options so select 'open command window here' then all you have to do is enable debugging on your asus zenphone 3 laser and then connect it to your pc and allow debugging on the device a menu will pop up, then inside the command window type "adb reboot bootloader" (remove quotations) then hit enter your phone will reboot to bootloader.
Next step is to type "fastboot flash recovery twrp-3.1.1.unofficial.img" (remove quotations) hit enter
6- now, using volume rockers to navigate and lock button as select, select recovery and wait
7- once the twrp loads, put in you devices lock pin, and continue to main menu. once there, select install, then look for the supersu .zip file (if you dont see it, look for a button that says "zip file" at botton right
8- done, please follow the instructions above at your own risk, im a nube.
Click to expand...
Click to collapse
The link in step 5 is broken. It should be
https://forum.xda-developers.com/showthread.php?t=2588979
sunblade7 said:
The link in step 5 is broken. It should be
https://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
For everyone thinking about this. Unlocking your device works but the twrp is broken for some or maybe many devices. My phone bricks everytime i try to either fastboot boot or fastboot flash the twrp image.
I
KingRoot?
I used KingRoot to root my old HTC Desire 626g+, and it worked fine, no issues. Does anyone know if this is also the case for the Asus ZenFone Laser 3 (ZC551KL)? I would certainly prefer using KingRoot if it is safe. If you think I should root it another way, why is that method any better?
MY BAD
I meant to make this a new thread, I clearly messed up. Still new here
Could an admin please delete this reply for me.
Kelvinkellner123 said:
I used KingRoot to root my old HTC Desire 626g+, and it worked fine, no issues. Does anyone know if this is also the case for the Asus ZenFone Laser 3 (ZC551KL)? I would certainly prefer using KingRoot if it is safe. If you think I should root it another way, why is that method any better?
MY BAD
I meant to make this a new thread, I clearly messed up. Still new here
Could an admin please delete this reply for me.
Click to expand...
Click to collapse
I tried all method to root Asus Zenfone 3 Laser ZC551KL and all failed, And the last i try to Root it I got bootloop. Yeah.... Is this a Joke ?
Maul_Lallana said:
I tried all method to root Asus Zenfone 3 Laser ZC551KL and all failed, And the last i try to Root it I got bootloop. Yeah.... Is this a Joke ?
Click to expand...
Click to collapse
Can you get into the recovery? If you can, try flashing the ASUS official image from their website. If you want to keep root, flash supersu right after it. Or... which method are you talking about?
It isn't a joke, if you visit the other forum on here with a lot more support, and success, that will be a better place to receive help, since a lot of us that have our phones rooted with that method are on the other forum only. Here's the link.
https://forum.xda-developers.com/zenfone-3/help/how-to-root-zenfone-3-laser-zc551kl-t3502606/page9
I'm running the latest 7.1.1 update with no issues whatsoever, on my phone.
---------- Post added at 04:03 PM ---------- Previous post was at 04:01 PM ----------
Maul_Lallana said:
I tried all method to root Asus Zenfone 3 Laser ZC551KL and all failed, And the last i try to Root it I got bootloop. Yeah.... Is this a Joke ?
Click to expand...
Click to collapse
Some people have more success with Magisk than SU, some have more success with SU than Magisk. you'll want to try both, as i had to.
50percentsuccessrate said:
It isn't a joke, if you visit the other forum on here with a lot more support, and success, that will be a better place to receive help, since a lot of us that have our phones rooted with that method are on the other forum only. Here's the link.
https://forum.xda-developers.com/zenfone-3/help/how-to-root-zenfone-3-laser-zc551kl-t3502606/page9
I'm running the latest 7.1.1 update with no issues whatsoever, on my phone.
---------- Post added at 04:03 PM ---------- Previous post was at 04:01 PM ----------
Some people have more success with Magisk than SU, some have more success with SU than Magisk. you'll want to try both, as i had to.
Click to expand...
Click to collapse
supersu worked for me, but i have zo1bdc. Seems like magisk is tge way to go for most people.
Gt5228 said:
supersu worked for me, but i have zo1bdc. Seems like magisk is tge way to go for most people.
Click to expand...
Click to collapse
I have the same phone, are you on 7.1.1? I'm curious to know what is making it work for some and not others
50percentsuccessrate said:
I have the same phone, are you on 7.1.1? I'm curious to know what is making it work for some and not others
Click to expand...
Click to collapse
no, android 7.0.
Hello guys, i also have a ZenFone 3 Laser Droid 7.1.1 and i'm thinking not to root it yet... Even if right now with 7.1.1. Installed is very buggy and slow, Asus announced that in mid 2018 we'll get the new update for Droid 8, which they say will include more awesome features and way less preinstalled garbage apps, so must be a cleaner, faster experience... can't wait for it
Iv'e got a guide but I need 10 posts to post it properly.
Gt5228 said:
my zenfone 3 POS! (laser) is now rooted. here is how i did it
1-in phone settings, go to security and turn on "unknown sources". then, also from settings, go to "about phone" then "software info", once there, tap build number several times until the phone gives you a message that your a developer. then go back to settings, and find "developer options" here you will see a "usb debugging" setting. turn this on.
2-with your zenfone, go to: asus.com/Phone/ZenFone-3-Laser-ZC551KL/HelpDesk_Download/ under utility, find and download/install the bootloader unlocking tool.
3-run the unlocker tool, keep in mind that it will do a factory reset, and all data will be lost. (backup files/pics/etc as needed) during the process, you will get a message that says " You do not have pin password to verify device, do you still want to unlock your device" tap yes
4-once completed, you will need to download a couple files. the twrp: https://depositfiles.com/files/ux8w5thp6 and *i now recomend magisk,
Not supersu* superdu: https://download.chainfire.eu/696/supersu/ move both files to the phones internal storage so they can be easily found.
5- with a pc, go to: https://forum.xda-developers.com/sho....php?t=2588979 just follow the steps on that thread and then after it is installed, the location where you have saved your twrp.img file you need to go to that folder and hold shift+right click on any empty space inside that folder of which you have saved twrp img and a context menu will come up with various options so select 'open command window here' then all you have to do is enable debugging on your asus zenphone 3 laser and then connect it to your pc and allow debugging on the device a menu will pop up, then inside the command window type "adb reboot bootloader" (remove quotations) then hit enter your phone will reboot to bootloader.
Next step is to type "fastboot flash recovery twrp-3.1.1.unofficial.img" (remove quotations) hit enter
6- now, using volume rockers to navigate and lock button as select, select recovery and wait
7- once the twrp loads, put in you devices lock pin, and continue to main menu. once there, select install, then look for the supersu .zip file *update, use magisk instead, see avove*(if you dont see it, look for a button that says "zip file" at botton right
8- done, please follow the instructions above at your own risk, im a nube.
Click to expand...
Click to collapse
Thank you. Did really helped a lot. Beside the fact that the link at point 5 is broken, we don't really need it, as everything is greatly explained, ant the fact that for me Magisk worked when SU bricked my phone, everything else is a GO. Thanks to this guide, i have a ZC551KL rooted, with TWRP. kEEP IT UP :good:
This how you unlock bootloader.
Read all before doing anything!
Yes.
Backup all your ect unlocking bootloader will erase all your data.
1 first you will need to USB drivers including adb usb driver.
After that download minimal adb and fastboot.
Make sure you enable debuging and oem unlock in developer's settings.
Download inteladroiddrv.setup.
After you set this up test run "adb devices"
2. Download the twrp that I link in thread.
3.extract recovery .img to minimal directory.
4.open minimal app and run adb reboot bootloader.
5. Run fastboot oem unlock.
6.follow instructions and unlock bootloader.
7.next wait until process is over then it will reboot.
8. After reboot go settings about device go to build tap a bunch of times to reable
Developer's setting enable debugging.
9. Next go to minimal app run adb reboot bootloader your know in fastboot run fastboot boot recovery.img.
10 this will boot recovery then flash root.zip.
11. After that I recommend you do backup and yes it is big after done you can move it to your PC.
Do flash recovery permit touch doesn't work.
https://www.mediafire.com/file/d3h8cnouw8fih6s/android_cdc_driver.zip
Sent from my Studio XL 2 using xda premium
https://www.mediafire.com/file/s4aidnkyacpidjq/latest_usb_driver_windows.zip
https://www.mediafire.com/file/q7nt7xko0f653o4/IntelAndroidDrvSetup1.10.0.zip
skritch said:
I am very interested in rooting the Blu Studio XL2. Can you let me know how you accomplished it?
Click to expand...
Click to collapse
You need to get adb drivers.
Go to settings about device then tap many times on build then go to development settings enable debugging.
You need to unlock bootloader.
Make sure you backup your apps etc.
Unlocking bootloader will wipe user data.
After all USB stuff is in installed.
Adb reboot bootloader this will take you to fastboot next put fastboot oem unlock.
On your phone it will give a choice to unlock bootloader volume up unlocks volume down will keep it locked.
Just pressure you this is not hard to do.
I have two work able recoveries at the time they can bootloop you if you install I was told so here is my solution to this.
Adb reboot bootloader then do this fastboot boot recovery img.
Works like a charm after recovery boots up do a backup.
I will try to drop some links to recoveries for you.
You will likely need to install USB drivers manually local disc c/ programs go into like Intel Android Device USB driver.
This should take care of adb and fastboot problems.
https://www.mediafire.com/file/zy47tm55qr76fc4/SR3-SuperSU-v2.79-SR3-20170114223742.zip
https://www.mediafire.com/file/0ckf...XL+2+-+S0270UU_V08+-+MT6737+-+by+lopestom.zip
https://www.mediafire.com/file/jgpx...XL+2+-+S0270UU_V08+-+MT6737+-+by+lopestom.zip
https://www.mediafire.com/file/do0v472pgcxu3s0/minimal_adb_fastboot_v1.4_setup.exe
I f you need help pm me
I will being posting proof of root also.
Update twrp can be flashed on but no touch.
The garlic touch recovery can be flashed and it works.
Twrp can used only temporary by fastboot boot recovery.img.
Update the other recovery can't find SD card don't use it.
Sent from my Studio XL 2 using xda premium
Sent from my Studio XL 2 using xda premium
This works and is easy as hell. You can also install Magisk 14 install zip if so inclined. Instead of the SR3 SuperSU zip. I did because I wanted a properly working for all modules (mainly luckypatcher) Xposed. Normal Xposed v87 SDK 23 doesn't work. All modules report they are not activated when they are. I, after a couple hours dining and trying many things found out that the SR3 SuperSU zip I flashed coupled with BusyBox install on this phone, which has toybox caused and will cause many apps needing root and BusyBox to not work, re, adaway, Xposed official, Rom Toolbox, Luckypatcher and more. So I used my untouched, Ie, non rooted nandroid backup to restore too, rebooted and installed the Xposed Installer that the Magisk module recommend (been through the Magisk/Xposed rodeo many times) and back to fastboot for the cmd "fastboot boot recovery.img"
Flashed the downloaded Magisk v14 zip, reboot again and fastboot twrp boot to lastly install Xposed.v87.3_Sdk23_sytemless.zip.......
Every time I tried installing within Magisk Manager. I could not get it to work even though Magisk Manager reported all was ok and no errors. But zip Flash Xposed via TWRP does. Safteynet will fail but the Xposed Installer has a toggle for on off as well as a recovery disabler zip so one can toggle reboot and it passes or flash the disabler zip instead of uninstalling the framework.
im reading all this info but im still confused. is it possible for someone to make a video tutorial on how this is all done please??
Things are not going real great with this install. First of all I used a package called MTK USB Driver2014 which had an exe file named DPInst64.exe which I assumed was a good idea for my Win 7 64 bit. I got a message screen saying Google and two different groups of Media Tek usbser drivers with various ports defined are ready to use. I went through the routine then as was outlined in the first post. First I got USB debugging enabled on the phone after going through the initial user setup (this is a new phone). Then I set on the unlock option to on as well as usbdebuggin. Then I ran "adb devices" and got nothing. A couple of unplugs and replugs of the USB to the phone showed a USB driver installing. One stated it installed OK and the Media Tek failed. I ran another "adb devices" and saw the device listed, so I decided to continue.
The "fastboot oem unlock" went well and finished in a few seconds. Then the XL 2 screen showed text in tiny, tiny white on black with 3 options to choose. the default was on the reboot option and said to push volume up to select another or volume down to select the one defaulted. I pushed volume down and nothing happened. The device appeared locked. Would not respond to volume + power button or any other controls. I waited a half hour. So I looked online and it said this happens but to reboot it. I couldn't figure out how. So after more research I found that entering "fastboot reboot-bootloader" followed by "fastboot continue" would cause the phone to go back into normal mode where I once again reconfigured the phone from scratch and enabled Developer tool USB debugging.
Now I finished configuring again and the USB drivers started auto installing again and I got the MTK error on the driver install. I had to unplug the USB and replug and enter "adb devices" and at this point the phone asked for approval and I selected always from this computer. All is well so with the TWRP renamed to recovery.img in the adb program directory I entered "fastboot boot recovery.img" and the TWRP menu came up. I didn't back up because I don't have a SD card large enough and since I can't see any files from when I connect the USB cable, I wasn't sure how to download the backup image once it is stored on the phone. So at this point I selected the TWRP menu option to acomplete the install where future use of TWRP would not be read-only (forgot the exact wording, there was a slide to the right on the bottom of the screen to accept write mode).
Now I rebooted the phone by pressing the up button of the volume and the power button at once and I am still taken to the same green on black text that I saw before on the BLU "recovery menu" (without an obvious method to select TWRP). Is this something to be expected, that the TWRP menu is only available to boot via the PC using adb and fastboot or should the TWRP image somehow remained on my phone?
Thanks!
---------- Post added at 08:21 PM ---------- Previous post was at 08:07 PM ----------
Flex_or_fleece said:
This works and is easy as hell. .
Click to expand...
Click to collapse
Not so much for me LOL.
Can you tell me just how to install root, xposed and xprivacyLua on my phone? Would really be appreciative.
See above for how far I have gotten into the process. Not looking for a different image. This is only the second time I have working on this depth of changes. Again, thank you.
I have been working on this now for 2 full days. I managed to install Magisk 16.0 using TWRP, then without understanding or thinking this was old information, I selected Xposed from Magisk (installed from Magisk before I ready about needing to install it from TWRP) and all appeared to be well. I enabled Xposed and added XprivacyLua and enabled it via the Xposed module page. Everything appeared to be setup properly but Xprivacy said it wasn't installed and a log sent to the developer proved that it was not installed (even though the check box in Xposed said so.)
So after reading the posts above, I elected to remove Xposed via Magisk and install the Magisk version of Xposed (xposed-v89.2-sdk23-topjohnwu.zip) via TWRP. Got everything installed again and same results, everything showed the check boxes marked and therefore active but XprivacyLua would not work).
Now reading above about problems with Busybox, I decided to install Busybox and then the busybox binaries via TWRP, downloaded from this location. https://forum.xda-developers.com/an...zip-busybox-v1-26-2-flashable-binary-t3581875
Now after doing that, I am hung up when trying to open Magisk. It is a solid green screen now. Tired re-installing both the zip via TWRP and the apk and have the same results. I assume I am going to have to restore. This is all new to me and I did not make a backup image because I don't have a SD card where I am working on this. All I can find is a factrory image on Needrom website: BLU_S0270UU_V6.0.04.02_GENERIC_20180203.rar
Can anyone point me to a guide that explains in elementary (as possible) terms how to get this ROM onto my phone and with it restored with the factory image? THANK YOU!!!!!
Flex_or_fleece;73955523 my untouched said:
Hi, is there anyway you would be willing to share this backup? Thank you!. I live in a small town with no computer shops and I did not have a SD card to back up to. Thank you.
Click to expand...
Click to collapse
I am struggling with everything including lack of mini SD card while residing at the moment far away from a computer store, a USB cord that is flaky as the snow, and a bricked phone because I wrongly read in a prior post that installing Busybox was a way to resolve the issue of Xposed showing it was installed and working when it was not.
Now can anyone suggest a link that shows how to flash the ROM I found online at NeedROM: BLU_S0270UU_V6.0.04.02_GENERIC_20180203.rar to this phone? I am not an expert at this, having rooted only a few phones over the years where I wanted Xprivacy and mostly just entered a few commands to make it happen. Today its getting too complicated.
I don't know if this phone even works with the SP flash tool, and if it does the drivers I have found to attempt it are not working.
Any help would be appreciated. THANKS!
Donphillipe said:
I am struggling with everything including lack of mini SD card while residing at the moment far away from a computer store, a USB cord that is flaky as the snow, and a bricked phone because I wrongly read in a prior post that installing Busybox was a way to resolve the issue of Xposed showing it was installed and working when it was not.
Now can anyone suggest a link that shows how to flash the ROM I found online at NeedROM: BLU_S0270UU_V6.0.04.02_GENERIC_20180203.rar to this phone? I am not an expert at this, having rooted only a few phones over the years where I wanted Xprivacy and mostly just entered a few commands to make it happen. Today its getting too complicated.
I don't know if this phone even works with the SP flash tool, and if it does the drivers I have found to attempt it are not working.
Any help would be appreciated. THANKS!
Click to expand...
Click to collapse
Hello! Been through the same thing.
It is compatible with SP flash tool. Think about it: in the factory all phones come empty so there must be something to flash them. In case of Mediatek-based devices, it's SP Flash Tool.
And yeah, your drivers are broken. First of all, uninstall them. Can't tell exactly how because I don't know what you installed but you can try the programs list and the device manager.
After removing them, download mediatek-drivers.zip and extract it.
Now follow this carefully:
1) Go to device manager and click on Universal Serial Bus controllers.
2) Then go to Action >> Add legacy hardware.
3) Select Install the hardware that I manually select from a list (Advanced).
4) In the hardware types, select Show All Devices.
5) Click on Have Disk... >> Browse, browse to where you extracted the drivers, go to mediatek-drivers/Win7/ and select usb2ser_Win764.inf or usb2ser_Win7.inf if your system is 64 or 32 bits arch respectivelly.
6) Click Open and OK.
7) Select MediaTek DA USB VCOM PORT, then just Next everything.
Now repeat every step above but in step 7 select MediaTek PreLoader USB VCOM Port.
Your drivers should be installed by now.
Now if you haven't done it yet, download it here. Run it, go to Download and in Scatter-loading File, choose the MT6737M_Android_scatter.txt file that (hopefully) came with your ROM. If it didn't download it here and place it in the same folder as the .img files that came with your ROM.
If it shows all checkboxes marked, just mark system, boot and recovery. It's a soft brick, you don't need a full reflash. If it doesn't but has system boot and recovery it's fine too. Hit download. Now, with your phone turned off, hold the VolDown key and plug it in. It will start flashing.
A popup will appear when it's done. That's it! Unplug and restart it. Should be back from the dead now.
The TWRP build you are using can only be booted via fastboot but not installed. If you flash it, the touchscreen will not work nor power buttons so you can't select anything. However I found a working flashable TWRP build: TWRP 3.1.1 built by Vampirefo
This one has the touchscreen working so you can permanently flash it on your device. It's very important to have a working recovery on your device that can reboot to bootloader because Power+VolDown actually boots in some kind of hardware test mode on this phone. Basically, if you softbricked your system, no working recovery=no bootloader=no temp recovery. And it's way easier to just restore your backup if you brick your phone.
Also, you can flash it througt SP Flash Tool. Rename it to recovery.img and go for it.
Can you reply or PM me with the rom you found? Mine is really old and I always have to wait for OTA...
Also, if you have any progress with Xposed, please share couldn't get it working properly here. Not a single module works...
Tried installing it the regular way with SuperSU and Magisk and tried the systemless install within and out of Magisk. None worked so far.
Thank you!
Mark42XLII said:
Hello! Been through the same thing.
Can you reply or PM me with the rom you found? Mine is really old and I always have to wait for OTA...
Also, if you have any progress with Xposed, please share couldn't get it working properly here. Not a single module works...
Tried installing it the regular way with SuperSU and Magisk and tried the systemless install within and out of Magisk. None worked so far.
Thank you!
Click to expand...
Click to collapse
I got the ROM from needrom.com you have to create an account, then just search on Blu studio xl and scroll down to pull the 2 version. Restored using SP Flash tool with non problem.
This whole thing is really frustrating. Get Magisk installed via TWRP, then to load Xposed Framework, you have to load Xposed via TWRP and then if you follow comments here from Flex_or_fleeceand his mini guide for downloading from Magisk with download only and not an install, you get the universal Xposed Systemless zip that is supposed to be able to choose which OS version you need during the install but that doesn't work installing via TWRM installing the universal version of Xpozed seamless zip so you have to download from the XDA site the latest Xposed with the SDK of your OS, in my case SDK23 latest version for Android 6.0. Now once you get Xposed installed via TWRP, then everything appears to work but trying to load XprivacyLua says it is not installed when the Xposed Module list says it is installed and the module is checked as being active. Yet the XprivacyLua menu still says you need to fix the issue.
Flex_or_fleece who claimed to get this working in a prior post said he resolved his problem by going to the link for BusyBox XDA pages for a solution, well I tried that, first installing BusyBox free from playstore, made sure that it said it was installed, then I loaded the libraries they talk about that is supposed to fix the BusyBox with toybox and after installing and testing the free version of BusyBox, then booting to TWRP and installing the Busybox library zip, once you boot up, the Magisk Manager will never open up again, just a blank green screen.
Time for a restore and try something else next time but unfortunately (unless the guy I asked about what exactly he did regarding BusyBox will respond, which he hasn't yet, ) then it's anyone's guess and I am all fresh out of guesses
Donphillipe said:
This whole thing is really frustrating. Get Magisk installed via TWRP, then to load Xposed Framework, you have to load Xposed via TWRP and then if you follow comments here from Flex_or_fleeceand his mini guide for downloading from Magisk with download only and not an install, you get the universal Xposed Systemless zip that is supposed to be able to choose which OS version you need during the install but that doesn't work installing via TWRM installing the universal version of Xpozed seamless zip so you have to download from the XDA site the latest Xposed with the SDK of your OS, in my case SDK23 latest version for Android 6.0. Now once you get Xposed installed via TWRP, then everything appears to work but trying to load XprivacyLua says it is not installed when the Xposed Module list says it is installed and the module is checked as being active. Yet the XprivacyLua menu still says you need to fix the issue.
Click to expand...
Click to collapse
I already did the BusyBox thing you talked about before and it went the same way. The difference is that my first attempt was by downloading from XDA so I didn't went through the universal zip problem. Actually there is now inside Magisk both the universal zip and the targeted sdk version numbers ones. Also I installed GravityBox and it said that couldn't communicate to the framework or something like that. Basically same problem. But I noticed something: when you install Xposed and reboot for the first time, it says that the Xposed framework is installed but not active and tells you to check the logs. If you go there you can see that the log file apparently doesn't even exist. In the second reboot it tells you it's active and running but if you check the logs it still couldn't open it because it doesn't exist. So maybe the problem is that Xposed isn't even starting up.
Mark42XLII said:
I already did the BusyBox thing you talked about before and it went the same way. The difference is that my first attempt was by downloading from XDA so I didn't went through the universal zip problem. Actually there is now inside Magisk both the universal zip and the targeted sdk version numbers ones. Also I installed GravityBox and it said that couldn't communicate to the framework or something like that. Basically same problem. But I noticed something: when you install Xposed and reboot for the first time, it says that the Xposed framework is installed but not active and tells you to check the logs. If you go there you can see that the log file apparently doesn't even exist. In the second reboot it tells you it's active and running but if you check the logs it still couldn't open it because it doesn't exist. So maybe the problem is that Xposed isn't even starting up.
Click to expand...
Click to collapse
On one of my iterations I installed a playstore app Marshmellow SD fix which fixed my problem with Xposed saying it couldn't read the log file. https://forum.xda-developers.com/xposed/modules/xposed-marshmallow-sd-fix-write-t3403263 But then once I installed this, slide the slider for Xposed to "authorize to sdcard" and then Xposed no longer had the error saying it couldn't read the log file but then simply always said "log file empty".
I'm just trying for Xposed and XprivacyLua only. When if I don't install BusyBox or the follow up install of the BusyBox binary zip file (that locks up the Magisk screen) and when I only start with a full ROM restore, install Magisk with TWRP, bring up Magisk and install Magisk Manager, install Xposed Systemless via TWRP, bring it up then it says Xposed is active. In Xposed I download and install the latest XprivacyLua and click the box in the Xposed module listo enable XprivacyLua, the check box remain checked and show active but the XprivacyLua menu says it is not installed. I sent a trace to the developer of XPrivacyLua and he said that Xposed was never loading it, and this is to repeat with all the respective check box checked and everything but the actual app saying all are active.
Adding "BLU STUDIO XL 2" so maybe Google can find this thread when people don't append the 2 to the XL"
Xposed still not working
I won't use a phone without these tools so at the moment I am still using my old Blu Studio with Android 5 that has the cracked screen and it is getting more and more cracked and harder to read. From time to time I pull my new unused BLU STUDIO XL 2 out of the closet and go a few more rounds with it. I've searched high and dry for the FlexorFliece fellow who claims to have it working and can't find him on any other blog or forum and he doesn't respond to messages but I just don't see how he got the Xposed suite working on this phone. I just spent three 14 hour days working on it as of today and got so frustrated that I reflashed the stock ROM on it and set it back in the closet again to try again another day, perhaps waiting like last time for a few more releases of the respective apps and modules to try again.
Now with several iterations of installing Xposed I've gotten the "green light" from Xposed Installer menu saying that it's installed and working and with the latest release which I think I recall is Magisk 17.1 and Xposed seamless SKD23 at release 89.3. This is actually quite funny that the light is green with Xposed Framework indicated as active from the Xposed Installer menu. You can then start searching for and downloading modules from the Xposed Manager and eventually the "green light" will go red while none of the Xposed modules will ever work, green or red light. At least the red light finally gives you a real indication.
I've loaded versions of Magisk all the way back to V14 and Xposed seamless (SDK23) back to 87.3 and the results are always the same. I'm either in a boot loop on a bad try or on a good try I'm showing the green light on Xposed but with no module working and reaching a threshold of about 6 Xposed modules loaded, then the light finally turns to a red one saying it's not installed or working.
I tried Flex or Fleece's technique of adding the Magisk version (from its repository of Magisk modules), the busybox and the ADB/Flashboot modules as a prerequisite but that didn't do a thing.
Now here's some odd things about this phone and even getting it to a good point to experiment with it.
I've found if I start with a fresh flash of the stock ROM or the phone in any condition without USB Debugging on, for example if I start with a powered down phone and hold the VOL-UP and POWER button at the same time, I can go to the stock recovery to select boot to bootloader option. (Release the POWER button slightly before the VOL UP or you'll boot the phone instead.)
Next I move to the PC and begin fastboot commands:
- get the ADB command window up by bringing up Windows file explorer with the name of the ADB folder visible and while holding SHIFT I then right click on the ADB folder and select "Open command window here" which opens a "DOS prompt" with the adb files in the directory. It's assumed I have pre-copied the new recovery image recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img to the same directory (folder) as hosts the adb.exe and fastboot.exe. Here I go back up to Windows File Explorer open the folder containing ADB/fastboot and rename this image to a shorter name. (Could use the DOS rename command but the syntax is too long and too easy to make a mistake.) Here I have renamed it to simply recoveryTWRP.img
Now then on the PC command window I enter ....
fastboot devices (to check that my USB is working OK)
fastboot oem unlock (to unlock the bootloader)
fastboot flash recovery recoveryTWRP.img (recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img that's been renamed)
fastboot reboot (to reboot the phone)
The phone may not boot after a flash or after and adb/fastboot interaction if the USB cable is not unplugged when done, so be aware of that.
Now if you are fast, you can go ahead and hold VOL UP at the moment the phone begins to boot and at the moment you have completed the fastboot series of commands. As soon as you see the TWRP recover manager you can release the VOL UP and be patient while the TWRP Menu appears.
Note now that you won't be able to use the SD card you may have randomly installedwith TWRP unless you have initialized it via Settings on the phone where you have under Storage option, set the SD card type to be "portable storage". If it's not formated and initialized by this phone, TWRP won't let you select it.
Quirks seen here include a failed install with unable to mount errors on the TWRP console trying to root, that is unless you have actually initialized the phone and set on Developer Tools and turned on USB debugging. (Sounds crazy but that's what I am seeing.) So basically that's what you'll find. ALso this verion of TWRP on this phone will not mount USB storage as with TWRP on other BLU devices I've tested, so copy all l your potential zip files to install as well as your apks you plan to side load (e.g. Xposed Installer and Magisk Installer apk files to the SD card prior to loading TWRP and finding that the files are not on the card or in the phone storage yet.
Other caveats are, with USB debugging off, each time you plug in the USB cable and want to upload files to the phone, when you go looking for the files in Windows device manager you will see a blank white screen appearing like there are no files on the deivce. What you have to do is slide the phone messages up and down a few times (perhaps dragging down from the top if it's not on the main screen) and finally the small window will appear on the phone where it asks for USB Charging only which you can tap and change it to USB Media and at that point you can see the SD card and Internal Storage for the phone in the respective Pc window where you can drag files into the phone's folders from the Windows PC. Otherwise with the phone having USB Debugging on you are supposed to be able to set it permanently to USB Media but you actually can't set it permanently. If you do research you will see online articles claiming that with Developer Options enabled and USB Debugging on, that setting the option just above the green "input" word on the Developer options screen allows you to set USB Charging to USB Media and it should stay permanently. Well stay it does on the menu but the function itself does not stay. Here each time you plug the phone in with the USB cable you will be curious why you cannot access the phone's storage because you believe the menu in Developer options that says it has been set to USB Media. Yes, it shows that way but you still can't see the storage on the PC. What you have to do each time you attache the phone with a USB cable then is go to Developer Options (shortcut would be to click on the info bar stating USB Debugging is enabled and when you arrive at Developer options, page down to just above the green "input" word and then temporarily set the option from USB Media to one of the other options, then set it back again to USB Media and you once again can see the phone's storage on your Windows computer.
And all this work and dealing with quirks is required before you even try to root by using SU or Magisk zip files and attempting to install then via the new TWRP recovery image you installed and gain access to by rebooting and holding in the VOL UP button to access the TWRP menu.
Otherwise the best performing ROM I have found is BLU_S0270UU_V6.0.04.02_GENERIC but when I went looking for it just now, the only place I can find it is now with the new toll-booth controlled need.rom repository. Yes I now see that needrom.com has now started charging to download the zip recovery modules we all uploaded there for free. What a sneaky bunch of #$#R)!!! Also, the spamming of Google has made searching for ROMs and any information about rooting a phone all but worthless. For example when I searched for BLU_S0270UU_V6.0.04.02_GENERIC which I believe is the latest ROM. I know there is a V8 floating around out there that I loaded but just in setting it up, the layout of the screen first went crazy and then the wireless log-in gave problems and then and finally the turning point was that the camera or video wouldn't work, so I gave up that version of the ROM. Anyway, searching for the ROM resulted in 5 full pages of search results with every website on every page saying they had the rom to download but in fact none of them did. I got directed from everything from purchasing female teen clothes, to sports gambling sites to unending surveys to you name it. What a vast wasteland it is out there these days. Unless Google does something to stop this technique where every website says they have a hit on your phone model when all they do is to stuff your search argument into a page of generic randomly generic diatribe, one day we will no longer be able to use the Internet to find things, or certainly it will take more time while weeding through all the disinformation.
Now
Yes, but that is not the challenging part. The challenging part is to get Xposed installed and the Xposed apps working with your root that you can obtain by several methods.
TWRP and this phone is easy, as you said and as I agreed. You will not be able to get Xposed apps running if that is the goal - even with root.
What is the main interest in this phone rooted? No one has gotten Xposed working so far or if they do get the green banner saying it is installed, it doesn't work with any of the apps. (Reported as due to toybox.) The phone has been rootable for nearly a year now, it's just that you can't do much with the root once you get it.
I have had my phone rooted for over a year now. Every few months I try again installing the latest version of Xposed via SuperSU or Magisk. Xposed apps will not work with either.
Last week I rooted my J7 2016 without problem. I installed TRRP 3.1.1-0 (j7xelte) with ODIN 3.12.3 and flashed the latest SuperSU v2.82 Zip. I then reflashed a stock ROM because I needed an official system for my banking app. After I installed the app on my old Xperia E1 I tried to root my J7 again but it doesn't work anymore. Stock rom used: https://www.sammobile.com/firmwares/ssp/SM-J710FN/XEF/download/J710FXXU3AQF8/187083/ (updated to Android 7.0 with system update)
The problem is that I'm getting a black screen after the boot logo with the message "Verification Failed. Unable to restart your device. The Integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data." on it with a "Reset" option below it. In TWRP I also often get the errors "Unable to mount '/data' " or "Unable to mount '/storage' ", but I've seen YouTube videos where peoples phones restart no problem with the same mount errors appearing.
USB Debugging and OEM Unlock were enabled and FRP Protection disabled.
I tried the following but it doesn't work no matter what I do, and this is annoying me big time because last week it worked no problem:
- Rooting on Android 6.0.1 and 7.0
- Wipe complete system (TWRP with the "type: Yes" confirmation), TWRP factory reset wipe and individual folder wipes to remove possible Samsung encryptions.
- Reformat "data" to ext3, exFat, ext4 ... but the unable to mount option reappears.
ROOT METHODS:
1. Root guide by jcadduono (this worked last week, now it shows the "Verification Failed" error on startup)
https://forum.xda-developers.com/ga...ecovery-official-twrp-j7xelte-galaxy-t3437659
2. Root package from: https://desktop.firmware.mobi
Flashing the image only results in a red one-line "Recovery is not Seandroid Enforcing" message on startup and the phone boots to unrooted OS
3. Root with Magisk-v14.0 (results in TWRP error that zip flash failed)
4. Package and tutorial by The Phone Skipping: https://www.youtube.com/watch?v=bkT8kZ8hb28
5. Flashing no-verity-opt-encrypt-5.1.zip and samsung-sm-j710f-6.0.1-nodmv.tar after the "Verification Failed" error appears
6. KingRoot app rooting (Xperia E1 no problem, J7 not supported)
I'm running out of solutions and I've already spent at least 10 hours on this including an all-nighter.
Nevermind, I followed the YouTube tutorial "How To Install TWRP & Root Galaxy S7|S7 Edge" by Shark Jungle for installing everything without my external SD card and it works now.
Hello Ollion9,
I have recently bought a j710-fn (I want a removable battery). I first installed a stock rom 6.0.1 from SamMobile https://www.sammobile.com/firmwares/ssp/SM-J710FN/XEF/download/J710FXXU3AQF8/187083/
and I did not root it yet. A few days later I have the 7.0 system update which of course I install.
And now I want to root my phone.
Which of the "root methods" you propose is the simplest ?
I want to root my phone with my stock Samsung rom for installing AdAway & Xposed Framework.
On my previous phones I used CF Auto Root, which was great and easy to install but is not available for the j710fn.
So which method can I use knowing that my technical knowledge is very limited ?
I think I should not be using the following method because the 710fn is not in the list : https://forum.xda-developers.com/galaxy-j7/how-to/how-to-root-twrp-install-xposed-t3328580
Thanking you in advance for your kind answer
1382 said:
Hello Ollion9,
I have recently bought a j710-fn (I want a removable battery). I first installed a stock rom 6.0.1 from SamMobile https://www.sammobile.com/firmwares/ssp/SM-J710FN/XEF/download/J710FXXU3AQF8/187083/
and I did not root it yet. A few days later I have the 7.0 system update which of course I install.
And now I want to root my phone.
Which of the "root methods" you propose is the simplest ?
I want to root my phone with my stock Samsung rom for installing AdAway & Xposed Framework.
On my previous phones I used CF Auto Root, which was great and easy to install but is not available for the j710fn.
So which method can I use knowing that my technical knowledge is very limited ?
I think I should not be using the following method because the 710fn is not in the list : https://forum.xda-developers.com/galaxy-j7/how-to/how-to-root-twrp-install-xposed-t3328580
Thanking you in advance for your kind answer
Click to expand...
Click to collapse
The video I mentioned in my second post works perfectly, however the video doesn't include how to install TWRP though so here is a step by step tutorial that I've written down for myself in case I ever forget and I have to root again in the future:
1. Install ODIN and Samsung USB Drivers on PC
ODIN: https://www.odindownload.com
Drivers: http://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
2. On phone, enable developer options (Settings -> About device -> Software Info -> Tap 7 times on Build number)
3. Settings -> Developer options -> OEM unlock (enable) + USB debugging (enable)
[Without OEM unlock Factory Reset Protection (FRP) will be active and the device will not (re-)boot when rooted and prevents installation of recovery software]
4. Turn off device
5. Boot into Download Mode (Volume Down + Home + Power)
6. Press Volume Up to confirm
7. Plug USB cable into phone
8. Open ODIN on PC and disable "Auto Reboot" in Options tab
[When phone is recognized the Log window should say "Added!"
9. Add "twrp-3.1.1-0-j7xelte.img.tar" to AP section of ODIN
Download here: https://eu.dl.twrp.me/j7xelte/
10. Click "Start" and wait until ODIN has finished
11. Turn off phone (remove and reinsert battery) and unplug USB cable
12. Boot into Recovery Mode (Volume Up + Home + Power)
13. In TWRP swipe "Swipe to Allow Modification" to the right
14. Tap "Wipe" and then "Format Data" (confirm by typing "yes")
15. Click TWRP Home button (house)
16. Plug USB cable into phone
17. On PC copy and paste the "No Verify" and "SuperSU" zip files onto the "Internal Storage" of the phone
Downloads:
SuperSU: https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
No Verify: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
18. In TWRP tap "Install" and find the previously copied zip files
19. Tap "SR5-SuperSU-v2.82-SR5-20171001224502.zip" and swipe to flash the file (wait until the process is done)
20. Click TWRP Home button (house)
21. Tap "no-verity-opt-encrypt-5.1.zip" and swipe to flash the file (wait until the process is done)
22. Tap "Reboot System" (if the phone doesn't reboot with the button swipe the "Install TWRP App" button to the right to reboot)
23. Wait for the phone to boot and go through the first installation process
24. The device is now rooted
Thank you very much for posting your step by step tutorial.
I will try it this week.
Hello Ollion9.
This method works on a Samsung Galaxy J7 2016 (SM-J710FN) right?
I'm asking because I've tried a similar procedure on my phone, but with a diferent version of SuperSU and my camera and flashlight crashed imediatly... So I guess I should try your method to see if it works....
Thank you very much in advance.
PS: sorry for my english but I'm Portuguese and English it's really not my strong suite.
Ollion9 said:
Nevermind, I followed the YouTube tutorial "How To Install TWRP & Root Galaxy S7|S7 Edge" by Shark Jungle for installing everything without my external SD card and it works now.
Click to expand...
Click to collapse
thank you it work very good man:good::good:
Will i be able to install the stock Android Oreo Official Rom?
Will i be able to install the stock Android Oreo Official Rom again?
If yes please help me with the steps.
I was trying to root with another method,my device didn't root but my knox is void and I'm not receiving any updates.
Please help me out.
samsung j7 sm-j710mn cant flash supersu... and why do i have only 3 options when boot in twrp
Only 3 options when I boot to twrp.?
Many of us are using 6.0.1 with this device. And we can tell you would want to root this device... otherwise you wouldn't be here.
To root the device you are required to downgrade to 5.1.1. Recently ZTE has removed all the official ROMs for this device that contain 5.1.1 files. This was the most common way to downgrade, by downloading these files and side loading them with ADB. However, I have found a Romanian version of the 5.1.1 ROM that is suitable for the root process.
You will need:
Vodafone Smart Ultra 6
A computer
ADB Platform tools
Micro-USB Cable
Firstly, download the platform-tools.zip from: https://developer.android.com/studio/releases/platform-tools
-extract the platform-tools.zip and place the folder anywhere on your computer.
Secondly, download the Romanian stock ROM from: https://bit.ly/2IwkUCT
-extract it and move the update.zip folder into the platform-tools folder.
Lastly, download the TWRP recovery from: https://androidfilehost.com/?fid=24591000424952165
Now, make sure you have the Android USB Drivers installed. You can download from here: https://developer.android.com/studio/run/win-usb
Now that is out of the way, lets flash the ROM onto your phone.
Reboot the phone into recovery. (Power button + VOL up (release the power button 2 seconds after "powered by android" logo, otherwise it will reboot)) Also plug in the phone to PC.
Now, select 'Apply update from adb'.
On the computer, head to the platform-tools folder and open CMD with that directory. (you know, the cd C:blah\blah\blah)
Type in
Code:
adb devices
to check if your device is detected by the computer. If it shows the device name along with sideload, then it is fine.
Then, type in
Code:
adb sideload update.zip
Wait until the process is complete and the phone says 'Install from ADB was complete.' in the bottom left of the screen on the phone.
Reboot the phone and you should see Android 5.1.1 setup screen in the Romanian language. Set it to the language you desire and connect to Wi-Fi. Log into your Google Account and do not set up a lock on the phone.
Now, head to Google Chrome and download KingRoot apk: https://kingroot.net/
Install the APK and try to root. It should work.
Now, go into Google Play Store, and install Rashr Flash Tool: https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools&hl=en_GB
Move the TWRP recovery img file from the PC to the phone, and then open the Rashr Flash App and grant root permissions.
Scroll down till you see the 'Recovery from Storage' option. Select that and flash the recovery img.
Now, that should work. When it is complete, find and download the custom ROM you would like to flash. In my case, I will be using the MIUI 7 ROM. (links of other ROMs below.)
Transfer it to the phone and reboot to recovery. Once you are in recovery, wipe everything except internal storage and flash the ROM. After flashing, then you can wipe internal storage and reboot. You can also root if you desire.
You have now installed a custom recovery and a custom ROM to your phone. Give ya self a pat on the back.:good:
List of ROMs you can install on this device:
MIUI 7: https://www.modaco.com/forums/topic/377403-port-rom-miui-v7-beta-for-vsu6/
Flyme 5.1.5.13 LP: https://www.modaco.com/forums/topic/377296-port-rom-flyme-os-51513-lp/
Lineage 14.1: https://www.modaco.com/forums/topic/379655-lineageos-141-for-vodafone-smart-ultra-6/
Lineage 13.0: https://www.modaco.com/forums/topic/379075-lineageos-130-for-vodafone-smart-ultra-6/
GIPSY V5: https://www.modaco.com/forums/topic...-lollipop-511-deodexedmore-performanceonline/
Outstanding guide
Thank you
I don't understand this bit, sorry
"On the computer, head to the platform-tools folder and open CMD with that directory. (you know, the cd C:blah\blah\blah)"
Does any 5.1.1 stock ROM works? the link for the Romanian is no longer available.
Thanks.
Link is down, i am betting zte or vodafone did a dmca takedown on it
Is it possible to get a new link?
Thanks in advance
Notice about link
Hey everyone, it just occurred to me that the link is broken, thanks to the person who contacted me about this via PM. I'm not active with this thread as i forgot to subscribe to it since the start of this thread (heheh, sorry). I still have the file on my PC and I re-uploaded it to mediafire; which you can find here: http://www.mediafire.com/file/mr2mdg3oi7whw3c/update.zip/file
Feel free to contact me on my Telegram: t.me/yomarshmellow
silversid2 said:
I don't understand this bit, sorry
"On the computer, head to the platform-tools folder and open CMD with that directory. (you know, the cd C:blah\blah\blah)"
Click to expand...
Click to collapse
Hey, happy to help!
Open Command Prompt (CMD) on your computer and browse to the directory of your platform-tools folder.
command example: cd C:\platform-tools
- I suggest keeping your platform-tools in the root directory of your C: Drive to access it quickly
Alternatively, go to the platform-tools folder with Windows Explorer, and SHIFT+RIGHT CLICK inside the folder. Then select "Open powershell window here" After that, type in cmd for the first command and continue with the guide.
If you have "open command prompt window here" then that is fine, you don't have to type in cmd.
I'm sorry for replying late, but if you need more direct help, contact me on Telegram: t.me/yomarshmellow
Good luck!
obvious said:
Outstanding guide
Thank you
Click to expand...
Click to collapse
I agree, the guy definitely has an eye for writing manuals )
Hello,
I must have done something wrong since I can't do anything.
I tried to install again by sideload the ROM provided but it is giving an error.
The message is:
"This package is for "P839V55" product; this is a "omni_p839v55".
Updater process ended with ERROR: 7
Can someone help?
YoMarshMellow said:
Hey everyone, it just occurred to me that the link is broken, thanks to the person who contacted me about this via PM. I'm not active with this thread as i forgot to subscribe to it since the start of this thread (heheh, sorry). I still have the file on my PC and I re-uploaded it to mediafire; which you can find here: http://www.mediafire.com/file/mr2mdg3oi7whw3c/update.zip/file
Feel free to contact me on my Telegram: t.me/yomarshmellow
Click to expand...
Click to collapse
Thanks for the link. The rom has Google FRP enabled, so to bypass it, I followed this vid:
https://www.youtube.com/watch?v=qFd33_kiEzo
I'm not sure how safe this guys APK is, but it did work. If there's an easier / better way to bypass FRP, please let us know.
thanks bro:fingers-crossed::fingers-crossed::fingers-crossed:
Kingroot not installing
Followed all the instructions - adb and installing Romanian ROM... but they get stuck on the Kingroot bit - "app not installed".
Done some searching on the 'net for a solution; even tried this FRP bypass (although I don't fully understand it and all it did was ask for my Google password - worrying - and then did feck all else!).
Any ideas, please?
RedSnowDonkey said:
Followed all the instructions - adb and installing Romanian ROM... but they get stuck on the Kingroot bit - "app not installed".
Done some searching on the 'net for a solution; even tried this FRP bypass (although I don't fully understand it and all it did was ask for my Google password - worrying - and then did feck all else!).
Any ideas, please?
Click to expand...
Click to collapse
Sorry for late reply, I assume you may have already fixed the issue. If not, try install a different kingroot APK with a different package. You might also get the warning telling you that this app may do permanent damage to your device, allow it and install.
Also, FRP stands for Factory Reset Protection. It is Google way of iCloud Lock, where if your phone is erased without authentication then it will lock itself on the Android Setup screen. Asking you to log in to the Google Account that was previously on the device before it was erased. There are services that fix this, or you can even bypass this yourself with some methods. But if a site asked you for your password for FRP then that is definitely a scam.
Sadly, I do not have the phone anymore so I cannot go in-depth the errors no more. But I will try and help as much as possible. ?
Also contact me on my Telegram for faster replies, it's a lot more easier for me: t.me/yomarshmellow
hey
((sorry for my bad english)) Hello, i have Vodafone Smartphone Ultra 6 (6.0.1) i tried downgrade but i couldn't. i downloaded everything and when i try "adb sideload update.zip" it gives an error (Total xfer: 0.01x) and it gives an error from phone (E: footer is wrong) (E: signature verification failed). I researched this error on internet they told me "Install TWRP for your model" and i also researched this. Wants root for instal TWRP and i cant root 6.0.1 android. What should i do?
EpsilonN said:
((sorry for my bad english)) Hello, i have Vodafone Smartphone Ultra 6 (6.0.1) i tried downgrade but i couldn't. i downloaded everything and when i try "adb sideload update.zip" it gives an error (Total xfer: 0.01x) and it gives an error from phone (E: footer is wrong) (E: signature verification failed). I researched this error on internet they told me "Install TWRP for your model" and i also researched this. Wants root for instal TWRP and i cant root 6.0.1 android. What should i do?
Click to expand...
Click to collapse
Try using super su, it worked fine for me
Hello! How to Russify Vodafone Smart Ultra 6??
I was trying to KIngRoot on a stock ROM with instruction from Modaco and it was not working either.
Hi, I have followed the steps above and downgrade the VSU6 to 5.1.1 but unfortunately the phone goes to a loop when booting (optimizing applications 1 to 14). I have been able to enter in recovery mode and switch it off. Is there anything I can do to fix the mobile? I appreciate if somebody could advise me what to do.
Update; I did a factory reset and telephone boot in version 5.1.1. (Turkish Edition)
The problem now is that I can not root the phone; I have tried KingrRoot and at third attempt it rooted the phone for a few minutes. Now KingRoot does not even try to root. I have tried kingo ROOT and it took ages, it indicated the phone as Rooted but it wasn't. Anybody knows how to root this mobile successfully?
Latest update: Finally installed Magisk throw TWRP and this automatically ROOT the mobile so it could be that it was not necessary to downgrade phone to 5.1.1. After this I used TWRP to install nutsda modified LineageOS 14.1 and gappss; everything is working.