This method doesn't rely on any root exploits & will work with any Android version on the ZTE Blade (and all variants). It should work on any phone with an unlocked bootloader (all zte android devices are sold with unlocked bootloaders).
Software needed:
adb (windows/linux/mac versions available as part of the android sdk - http://developer.android.com/sdk/index.html You will find adb in the tools directory.)
fastboot (windows/linux/mac versions available here: http://koushikdutta.blurryfox.com/G1/ )
windows drivers for the phone (if you use windows: http://support.zte.com.cn/support/news/NewsDetail.aspx?newsId=1000442 )
ClockworkMod (http://clockworkmod.com/rommanager - download zte blade clockwork recovery image)
SuperUser ( http://androidsu.com/superuser/ Download Eclair/Froyo/Gingerbread/Honeycomb (2.1 – 3.2) version) - Alternatively you can use any rooted custom rom
If your phone is running Android 2.1, then it is probably a 'gen1' device, search for "Mr Pigfish" on Android market if you're unsure. Gen1 blades will need an older version of clockworkmod, 3.0.1.4 - http://download.clockworkmod.com/recoveries/recovery-clockwork-3.0.1.4-blade.img
Method:
Download/install adb & fastboot. Install drivers for the phone if needed (on Windows).
Plug your phone into your pc using the usb cable, mount usb storage, then copy the Superuser or custom rom zip onto it & unmount usb storage.
Make sure that usb debugging is enabled on your phone, there should be an icon in the status bar, you can enable it in settings (settings -> applications -> development -> usb debugging).
Open a command terminal window & change to the directory that you downloaded recovery-clockwork-[version]-blade.img to. Type...
Code:
adb reboot bootloader
This will make the phone reboot, wait for the android logo (or custom splash screen) on the phone then type...
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-blade.img
fastboot reboot
You have just installed ClockworkMod recovery. Your phone will reboot back into android, when it has done that turn it off, then turn it on with the vol- button held to start clockworkmod. Use vol+/- to navigate, home button to select an option, back button to go back. You should create a backup now before you flash anything, when that backup is complete use 'install zip from sdcard' to either install superuser to root your stock rom, or install a custom rom. If you're installing a custom rom then you'll need to wipe data/factory reset too (you will lose all data). reboot, you're done.
I'm not sure if this is the right section for the thread, it'd probably be better in blade general. I forgot that newbies can't reply here.
Anyway, for those that can reply, can you suggest any improvements? I'll find links for adb, fastboot & windows drivers later.
Everything is clear except where to find adb and fastboot for noob users... (like me).
I did a little search and found out that adb is installed with the Android SDK... so, i installed it, installed the android platform-tools package, the usb driver but i am stuck with fastboot...
There is no fastboot in the Android SDK installation directory... and i can't find it on the web... so, i can't install clockworkmod recovery and i'm stuck...
Can u help me plz ?
Yeah, as I said, I'm still looking for links. you get fastboot when you compile android from source, but that is a bit of a long & complicated way.
Here is a pre-compiled version of fastboot for windows, linux & macos http://koushikdutta.blurryfox.com/G1/
adb works without the sdk too, I'll see if I can find links for that.
The windows driver is on zte's site somewhere, but that's a pain to find anything on. I'm not sure if the Google driver works. I don't even run windows, so if anybody can help write that part...
Probably best to for XP use the exe driver installer (Thats in the pcsuite.iso in the official 2.3.5 rom)
Windows 7 just works (gets drivers from windows update).
Does the superboot apk deal with changing default.prop (to allow adb remount etc).
If not could do that (use the same thing the CM7 universal converter uses to split the boot.img).
unrandomsam said:
Probably best to for XP use the exe driver installer (Thats in the pcsuite.iso in the official 2.3.5 rom)
Windows 7 just works (gets drivers from windows update).
Click to expand...
Click to collapse
Not everybody is running the official 2.3.5 rom, it's probably a tiny fraction of users. 2.1 roms don't have the driver iso. I found the drivers & updated the first post. The drivers on the phone should work fine, if you are running an unmodified 2.2 or 2.3 stock rom, just plug the phone in & it should mount a driver cd image over usb to install the drivers.
Does the superboot apk deal with changing default.prop (to allow adb remount etc).
Click to expand...
Click to collapse
It's superuser, it's a clockworkmod zip file & no, it doesn't change default.prop. It installs superuser & su.
If not could do that (use the same thing the CM7 universal converter uses to split the boot.img).
Click to expand...
Click to collapse
Tell ChainsDD, it isn't my software, I just wrote a quick idiot's guide.
Hi wbaw....
nice to see you posting helpful stuff here....
Can I ask what is perhaps a silly question, about the rooting process for ZTE devices, without relying on root exploits?
How is this different, or better, than using the z4Root modified by kallt_kaffe App, which I have linked (MoDaCo).
Is it just the use of the exploit, or is there another reason?
I have used it on my OSF/Blade, and never lost root or had any other problem, AFAIK.
Also, I see you are not showing your previous GEN1/Gen2 all-in-one TPT for GSF any more...is it available any more for ppl who may want to try it?
Thanks in advance
The exploit that z4root uses doesn't work on newer versions of Android (2.2.2 & above), ZTE are selling some phones with these newer versions of Android.
If z4root works for you, then that's fine, there's nothing wrong with it. It just doesn't work for everybody.
If you are using a version of Android that z4root (or other root exploits) do work on, then you should update Android asap. Otherwise a malicious app could use the same exploit to take over your phone. Root exploits themselves aren't bad (as long as you're doing it to your own device, or with permission of the owner) - the fact that root exploits work is bad & a sign that you need to update the software asap.
GSF has it's own thread. You can get the same effect by using the gen1 to gen2 tpt & then installing gsf. It is buggy & old, I think there is a nasty remote root exploit out there for 2.3.4 too. Just use CyanogenMod, it's much better, less buggy, more secure, they keep up with the latest Android fixes & it has more customisation options.
Thank you for the explanation...I will go ahead and do what you have advised.
I am just continuing to use good old Swedish Spring RLS5, which I think was kallt_kaffe (Cold Coffee) also......GEN 2 thanks to your Gen 1>Gen 2 TPT.
I think t is 2.2.
If I want to proceed to permanently root as you describe, should I use z4root to unroot first?
I will probably move to CyanogenMod, so I should use your exploit-free root instructions first.
BTW, I will be sad to move on from SS, as it does seem to be as near a perfect fit as I have found for the Blade.
I did put on GSF ,some time ago, and to be very honest, I just lasted a night with it, then restored the SS Nandroid.......it didn't feel at all as satisfactory a UI experience as SS.
Perhaps it was me, you know, you get used to an old pair of sneakers, etc.
As you said, it was and is always beta...it was an early version!!!
Thanks again, and keep up the good work in these calm(er) waters
Custom roms are already rooted. You don't need to root a custom rom, you just install it with clockworkmod.
If you already have a custom rom installed then you don't need any of this guide, you've already got clockworkmod. All this guide does is tell you how to install clockworkmod.
This is for people with phones on a stock rom who want to be able to install clockworkmod to root their stock rom or install a custom rom.
You shouldn't still be using Android 2.2 because the root exploit in z4root works on it, therefore other more malicious apps could use a similar exploit without asking you first.
Hi..... does this work on any Android phone?
I have in mind the new Samsung W i 8150.
Getting one for Xmas.... AFAIK
Sent from my ZTE-BLADE using Tapatalk
It should work on some other android phones, but they'll need adb & an unlocked bootloader, so it wont work with every phone. It should work on any ZTE android phone or tablet (except maybe the tureis?).
Hi!I have a Zte Blade with 2.3.5 OS. I tried to root my phone using this tutorial, but when i write : "fastboot flash recovery recovery-clockwork-5.0.2.0-blade.img" in Comand Prompt program, i get this message : "error: cannot load : recovery-clockwork-5.0.2.0-blade.img".
Can anyone help me, please?
Thanks!
stanangel said:
Hi!I have a Zte Blade with 2.3.5 OS. I tried to root my phone using this tutorial, but when i write : "fastboot flash recovery recovery-clockwork-5.0.2.0-blade.img" in Comand Prompt program, i get this message : "error: cannot load : recovery-clockwork-5.0.2.0-blade.img".
Can anyone help me, please?
Thanks!
Click to expand...
Click to collapse
You need to download clockwork recovery & be in the directory that you downloaded it to, to run that command.
Thank you!It works. Now, can I put Cyanogenmod 7.1 on 2.3.5 OS with this root and clocworckmod ?
stanangel said:
Thank you!It works. Now, can I put Cyanogenmod 7.1 on 2.3.5 OS with this root and clocworckmod ?
Click to expand...
Click to collapse
You can put clockworkmod on, but cm7 might not work without a bit of fixing, it is designed for 2.2 blades, zte's 2.3.5 has a different radio firmware.
Is this a 2.3.5 blade? where did you buy it?
Well, first time i had 2.1 update-1.After that I updated the version to 2.2 Boygues (or something like this) and then i found on this forum the official image.bin (2.3.5) and I decided to update.But now, i want to try CM.
stanangel said:
Well, first time i had 2.1 update-1.After that I updated the version to 2.2 Boygues (or something like this) and then i found on this forum the official image.bin (2.3.5) and I decided to update.But now, i want to try CM.
Click to expand...
Click to collapse
I see, you'll need to use another image.bin to go back to 'gen2' - the zte froyo radio firmware. Otherwise you wont get any phone signal, 3g or gps on CM7 because the 2.3.5 image.bin that you installed contained new radio firmware.
You don't need to root it first, you can install clockworkmod with a gen2 radio firmware using a custom image.bin like this one that http://www.mediafire.com/?jb4crw3em2m4r4x Amphoras made.
The 2.3.5 image.bin contained another new version of the radio firmware, which isn't compatible with CM7.
Uhuuu, it works.Thank you a lot! CM7.1 is awsome.This forum is awsome.
Hey I cant acess adb after doing adb reboot bootloader. When I come to the chinese letter I cant do nothing. So i cant fastboot flash recovery recovery-xxx.img.
What im i doing wrong?
Related
ummmm...hello xda devs and members. i am a noob on these forums regarding development of the android OS. i managed to installed racht's floyo v0.30 after a lot of difficulties.
i have root explorer v2.15 installed on the custom rom. before yesterday everything was alright, i could browse and change the permissions of files easily. how ever yesterday in the evening i found out that my gallery wasnt displaying any of my cam pics. so via root explorer i browsed to the DCIM folder and saw that Owner r/w/e permission wasnt enabled. i tried to enable but i got a message saying that permission change was unsuccessful as sd card does not allow it, or something similar. so i updated and installed the official android 2.1 eclair via SEUS. the problem still persists. please help me
um, did you wipe the userdata in xrec/cwm ?
if not, try that.
if you did, all i can suggest is back up the content and format the card.
(that said i'm no expert so maybe someone else will have better solutions.)
before installing rom i performed factory reset through xrecovery and i also tried formatting the sd card. but no use. are u saying that i should try factory reset in phone settings. please reply ASAP
oh, no, just in recovery , but if you've done that, and you've tried formatting the sdcard, idk, perhaps try reinstalling the rom now that you've formatted the sdcard?
if that doesn't do it, y'need someone with more experience than me, heh.
hmmmm...maybe i should try again. and i was wondering if i can use a different sd card(not the one that came with my phone) but if i do so on my custom rom will i brick my phone or something
no, switching sd card won't brick the phone.
also, you could try a more recent version of root explorer and see if that helps.
thanks for the replies. i will try root explorer v2.17 and give updates. please subscribe to this thread so if i face any further problems with this you can help me out.
If can help....
you should explorer more on the forum
anyway, get latest flash tool, adb shell, baseband 015, unlock bootloader, custom kernel, custom Rom which is compatible with your custom Rom.
NOTE: USE THE SEARCH BUTTON ON TOP RIGHT OF THIS PAGE.
flash 015 baseband using flash tool, reboot, install busybox, xrecovery, #unlock bootloader (CAREFUL), reboot, flash custom kernel#, install custom rom. done.
NOTE: CAN SKIP STEP WITH ## QUOTE IF YOU ARE UNEASY WHAT YOU ARE DOING, PHONE WILL NOT BE SMOOTH AS PHONE WITH UNLOCKED BOOTLOADER AND WITH CUSTOM KERNEL, SAFETY FIRST .
IF GOT PROBLEM, REFLASH/UPDATE USING SEUS(GOOGLE), USING FLASHTOOL INSTALL BUSYBOX, XRECOVERY. REBOOT INTO RECOVERY, MOUNT SYSTEM, PLUG IN ADB CABLE TO PC (ENABLE USE DEBUG FIRST ADB AND INSTALL DRIVER), CMD, ADB SHELL, TYPE IN:
1. SU
2. BUSYBOX
3. DMESG
(SEARCH FORUM FIRST IF DON'T UNDERSTAND)
1. FLASHTOOL, SU IMPROPER INSTALLED
2. FLASHTOOL, BUSYBOX IMPROPER INSTALLED
3. KERNEL, SEUS AGAIN
IF ANY IF THE COMMAND YOU HAVE ENTERED SHOW ERROR, BLANKS(ENABLE USB DEBUG OR DRIVER ERROR) PLEASE CHECK INSTRUCTION CAREFULLY AND TRY AGAIN. THIS IS ULTIMATE FIX THAT I KNOW TO ME, OUT THERE MAYBE SOME PEOPLE WHOSE ARE MORE ADVANCE THAN ME CAN COMMENT/POINT OUT ERROR ABOUT MY POST AND WORK TOGETHER TO TEACH NEWBI A BETTER UNDERSTANDING
Thanks button are there ====>
ok guys thanks for all your replies (though i did not get many). i think i fixed the problem. you see with racht's floyo v0.30 comes a file manager. what i did was browse to the sd card directory. then i first excluded it from media scan and then reverted the process. i checked to see if my pictures were still in the gallery. i rebooted the phone and to my relief they were there...thank god. anyways thanks for your prompt replies. if you need any help be sure that i will help you
CKKnot said:
you should explorer more on the forum
anyway, get latest flash tool, adb shell, baseband 015, unlock bootloader, custom kernel, custom Rom which is compatible with your custom Rom.
NOTE: USE THE SEARCH BUTTON ON TOP RIGHT OF THIS PAGE.
flash 015 baseband using flash tool, reboot, install busybox, xrecovery, #unlock bootloader (CAREFUL), reboot, flash custom kernel#, install custom rom. done.
NOTE: CAN SKIP STEP WITH ## QUOTE IF YOU ARE UNEASY WHAT YOU ARE DOING, PHONE WILL NOT BE SMOOTH AS PHONE WITH UNLOCKED BOOTLOADER AND WITH CUSTOM KERNEL, SAFETY FIRST .
IF GOT PROBLEM, REFLASH/UPDATE USING SEUS(GOOGLE), USING FLASHTOOL INSTALL BUSYBOX, XRECOVERY. REBOOT INTO RECOVERY, MOUNT SYSTEM, PLUG IN ADB CABLE TO PC (ENABLE USE DEBUG FIRST ADB AND INSTALL DRIVER), CMD, ADB SHELL, TYPE IN:
1. SU
2. BUSYBOX
3. DMESG
(SEARCH FORUM FIRST IF DON'T UNDERSTAND)
1. FLASHTOOL, SU IMPROPER INSTALLED
2. FLASHTOOL, BUSYBOX IMPROPER INSTALLED
3. KERNEL, SEUS AGAIN
IF ANY IF THE COMMAND YOU HAVE ENTERED SHOW ERROR, BLANKS(ENABLE USB DEBUG OR DRIVER ERROR) PLEASE CHECK INSTRUCTION CAREFULLY AND TRY AGAIN. THIS IS ULTIMATE FIX THAT I KNOW TO ME, OUT THERE MAYBE SOME PEOPLE WHOSE ARE MORE ADVANCE THAN ME CAN COMMENT/POINT OUT ERROR ABOUT MY POST AND WORK TOGETHER TO TEACH NEWBI A BETTER UNDERSTANDING
Thanks button are there ====>
Click to expand...
Click to collapse
ummmm...you just taught how to install a custom rom which is already in my knowledge but anyways you tried to help so i appreciate it and thanks.
As i understand - there is no more upgrade to the operation system.
mine is the newest (4 )and i'm not satisfied with it.
Can someone tell me how to root it and what os to install and how. there are some guides but i do not know if they actual and good for os4 ver.
thanks.
libal said:
As i understand - there is no more upgrade to the operation system.
mine is the newest (4 )and i'm not satisfied with it.
Can someone tell me how to root it and what os to install and how. there are some guides but i do not know if they actual and good for os4 ver.
thanks.
Click to expand...
Click to collapse
Please don't start another *how do I root* thread there are dozens if not hundreds of postings on here explaining in great detail how to achieve root.
sorry but....
1. I ask for the best and easy way to root android 4
2.also for the best firmware.
thank you anyway...
To get root & custom recovery, the following methods are reported to be working with the latest Asus ROM:
http://forum.xda-developers.com/show....php?t=1689193
http://forum.xda-developers.com/show....php?t=1681155
http://forum.xda-developers.com/show....php?t=1688012
The first method ( [TOOL]PERI-0.4 One click root+recovery/fix-bootloops+soft-bricks ALL Devices V0.4) works well for me on TF101G with latest ICS . Just install it on the PC, run the .BAT file and follow the instructions to root and install Custom Recovery and Root / SU on the Transformer.
The only issue I've had is that this custom Recovery won't seem flash the ASUS stock ROM for some reason. So what I do now is use the above tool to get root and Custom Recovery, then use that to flash ClockWorkMod Recovery v6.0.1.4 NoTouch Hybrid from http://forum.xda-developers.com/show....php?t=1855686 - click the Download link and get the cwm-6.0.1.4-notouch-hybrid.zip file (apparently the Touch version is currently broken).
From CWM recovery you should be able to flash any custom ROM and kernel etc., and also return to stock by flashing the ASUS stock ROM from their download site (make sure you select the right one for your model and unzip it first - for some reason they put the zip ROM inside another zip).
If you do return to stock, don't forget you'll also lose root and custom recovery so you'll need to start over.
I'm using Android Revolution HD 3.4.3 3G which seems pretty stable. I've also heard good things about Revolver, but I couldn't get 3G working on the 3G version.
Good luck.
1 click root
http://forum.xda-developers.com/showthread.php?t=1689193
This worked for me. Just make sure you download version for your transformer.
well thank you all ...
thank you all...
Now here's the situation:
I'm still on an older ROM version (4.2.1 - see attachment)
A while ago my tablet told me there was an update. I wanted to get it, it downloads but it always fail to apply the update.
What I've done to the device so far is that I've used motochopper to root the device and got rid of some ASUS apps.
So since it refuses to update, I've decided to unlock it, flash a custom recovery and get myself a custom rom.
But I've read a lot about people bricking their devices and I doubt it'll be as easy as it was on Nexus 4 and Nexus 7 - so I need some advice on how exactly to do it.
Recently I found the thread that enables us some sort of nvflash although being on JellyBean. They were talking about a specific version of bootloader and I'm not certain if I have this bootloader since I'm on an older JellyBean version. Of course I would like to use this bricksafe as well - just in case
Can someone lead me to a guide or instruct me how to do it? I don't want to brick this device
Thx in advance
l33ch0r said:
Now here's the situation:
I'm still on an older ROM version (4.2.1 - see attachment)
A while ago my tablet told me there was an update. I wanted to get it, it downloads but it always fail to apply the update.
What I've done to the device so far is that I've used motochopper to root the device and got rid of some ASUS apps.
So since it refuses to update, I've decided to unlock it, flash a custom recovery and get myself a custom rom.
But I've read a lot about people bricking their devices and I doubt it'll be as easy as it was on Nexus 4 and Nexus 7 - so I need some advice on how exactly to do it.
Recently I found the thread that enables us some sort of nvflash although being on JellyBean. They were talking about a specific version of bootloader and I'm not certain if I have this bootloader since I'm on an older JellyBean version. Of course I would like to use this bricksafe as well - just in case
Can someone lead me to a guide or instruct me how to do it? I don't want to brick this device
Thx in advance
Click to expand...
Click to collapse
This THREAD has all the info you need to do NVFlash. It's based on 10.6.1.15 something bootloader which I believe is the same as the latest Asus official. If you're on 4.2 rom, you can flash the flatline img. and generate the necessary files from there. Once that done, you can use either the provided CWM or the latest 4.2 TWRP to flash any compatible custom rom (4.3). Have fun.
graphdarnell said:
This THREAD has all the info you need to do NVFlash. It's based on 10.6.1.15 something bootloader which I believe is the same as the latest Asus official. If you're on 4.2 rom, you can flash the flatline img. and generate the necessary files from there. Once that done, you can use either the provided CWM or the latest 4.2 TWRP to flash any compatible custom rom (4.3). Have fun.
Click to expand...
Click to collapse
First of: thanks for your reply
Guide says something about bootloader 10.6.1.15.3 - I still have an even older one (10.6.1.8...) - will it still work?
l33ch0r said:
First of: thanks for your reply
Guide says something about bootloader 10.6.1.15.3 - I still have an even older one (10.6.1.8...) - will it still work?
Click to expand...
Click to collapse
Yes, that version will work because it is on the 4.2 bootloader.
Sent from my TF300T using xda app-developers app
Only works on unlocked device?
Ok I'll try like this
These are the steps I would do: (I pray someone to look over these steps and correct me if I'm wrong )
1.) Go to asus site and download unlock_v8 and run it so to unlock my tablet.
2.) I go to androidroot.mobi and download flatline_tf300.img and nvflash-tools-win32.zip (win32? Hope that does not stand for 32-bit and hope it will work on 64-bit)
3.) I reboot my device into Fastboot (don't know exactly what that means "Please note that for transformer tablets the fastboot command might require the option "-i 0x0b05"" - at this stage the device is already connected to the pc and just in case it's not in fastboot I should run this command?)
4.) I use cmd.exe to type in these commands. In which directory? In the directory where I unzip the files from nvflash-tools-win32.zip? The guide is not too specific on that.
5.) I type in "$ fastboot flash recovery flatline_device.img" (I know for device I use tf300) which will flash the recovery.
6.) I reboot my device (let android boot?) and reboot again into recovery. (power + vol down?)
7.) I select "Advanced - Wheelie" and Step 1: Flash AndroidRoot BL and find myself with a custom bootloader.
8.) It says the device will power off. Automatically? However, I boot into android and after that reboot again into recovery mode.
9.) I choose Step 2 which will generate wheelie blobs
10.) I follow the on screen prompt to retrieve my blobs (anyone has a screenshot of that? Or is it self-expalantory?)
All this time the device is connected to pc via usb?
11.) Now I reboot my tablet into APX mode - after Step 10: am I still in recovery or booted to Android?
12.) If my tablet is recognized I type "$ wheelie --blob blob.bin" into cmd
13.) Then I will type in the commands to obtain the backups
Still got a few questions though. The device is connected to PC throughout this whole procedure, right? Where to start cmd (do I have to put the files from nvflash-tools into a specific folder from where I start cmd.exe?)
And after this procedure is done do I need to flash anything else? Or will I be then equipped with a working recovery that allows me to flash custom roms?
Thanks in advance for anyone who's taking time to answer my maybe uninformed questions but I'm kind of having troubles following the guide
How to root Lenovo TAB A7-40 A3500-FL?
[Solved] See the guide below!
Device info:
Model number: Lenovo A3500-FL
Android version: 4.4.2
Kernel version: 3.4.67
Build number: A3500FL_A442_01_25_140823_SE
BB Chip: MT6582
MS Board. A3500FL
Bar code: this was my device's serial number
SW Ver.: ALPS.KK1.MP1.V2.10
Custom Build Verno.: 1408775889
Managed to get cwm and root with this guide: http://forum.xda-developers.com/and...vo-a3500-h-t2879208/post55491817#post55491817
Modified the guide for Lenovo A3500-FL!
EDIT: Also some users have reported that this guide doesn't do the trick or is out-dated, so copypasted the guide from this post here.
Guide
1. Download attachment cwmRecovery.zip and download latest Flash_tool (version 5.1352.0) can be downloaded from here)
1.1. Enable USB-debugging. (How to do this)
2. Manually install the drivers from the attachment a7_40_drivers.zip for the LenovoTablet before plugin it to computer (win7 dirvers work for win8 too).
2.1. To install unsigned/uncertified drivers on Windows 7: http://en.kioskea.net/faq/3914-windows-7-how-to-install-unsigned-drivers
2.2. To install unsigned/uncertified drivers on Windows 8: http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
2.3. After you have disabled the driver signature verification, you can install the drivers like this: Right click My computer, Manage, Device Manager, right click your computer at the top, Add Legacy hardware, next, Install plapla manually, next, Show all Devices, Have a Disk.., Browse to the driver folder where you unzip them, choose example windows7 and the 64 version (win7 drivers work for win8.x too), install every device. Then follow the guide.
(Note: Otherwise Windows only installs the normal automatic drivers and its more difficult to install the other drivers.)
2.4. Plug your device to PC.
3. Download the latest supersu zip file (version 2.46) from attachments or from https://download.chainfire.eu/696/SuperSU/
3.1. Move the zip.-file to the Sdcard.
4. Turn off your device.
5. Unpack cwmRecovery.zip
6. Run Flash_tool.exe with Admin Rights.
7. Chose Scatter-Loading and choose MT6582_Android_scatter.txt (in Recovery folder).
7.1. Now you will see checekd only one checkbox - recovery, if not click on it and choose recovery.img
7.2. Press Download.
7.3. Connect your device.
7.4. Wait few seconds.
8. Have CWM on your device .
9. Unplug your device.
10. . Boot to cmw recovery by turning off your device. Then press and hold VOL DOWN + VOL UP and then also press and hold POWER for about 7 seconds.
10.1. Choose " Install zip from sdcard." (To confrim always use the Power Button)
10.2. Choose "zip from sdcard".
10.3. Select SuperSU-v2.46.zip from sdcard and apply.
10.4. Have a rooted tablet.
It might be necessary to always flash the CWM with the Flashtool directly before you startup the device. Otherwise it will start the original AndroidRecovery again.
It might also be necessary to use different drivers from here.
If the supersu zip doesn't install, try toggling the signature verification to disabled from cwm->install zip from sdcard->toggle signature verification.
Tested and working on Levono A7-40 3500-FL with kitkat update, build number A3500FL_A442_01_25_140823_SE, from ota. Attached screenshot for proof. Also other people have reported that this works for later updates too, for example A3500FL_A442_01_27_141127_SE.
You can update to the latest OTA firmware by first going back to stock recovery. See the second post for the guide.
Thanks and credits go to: @Koli96 and @bobais
How to go back to stock rom/recovery and update to latest Lenovo OTA firmware update
So, it's pretty simple, you take the stock_recovery.zip from the first post, extract it, and replace recovery.img in the recovery folder with the stock one.
Then :
Quote:
4. Turn off your device.
6. Run Flash_tool.exe with Admin Rights
7. Chose Scatter-Loading and choose MT6582_Android_scatter.txt (in Recovery folder)
7.1. Now you will see checekd only one checkbox - recovery, if not click on it and choose recovery.img
7.2.. Press Download
7.3. Connect your device
7.4. Wait few seconds.
And that's it !
On a side note, if it seems stuck on a black screen with a loading circle after factory reset, you have to put the tablet in landscape mode and restart (the shutdown menu appears without any problem) - this issue doesn't seem related to recovery, but a bug within lenovo firmware and the first configuration screen.
Side note 2: The first boot after flashing new update might take 15mins.
Side note 3: After updating to the latest OTA you can go back to cwm recovery with the guide from the first post.
Credits @tenuis
I got the same tablet and I also am looking for a root. :/
Another waiting for rooting lenovo owner.
Same here, i was looking for a root guide and i couldn't find anything.
Does anyone else has a problem with long charging times?
Well it charges long and the charge stays long, so no issue here.
Seems that not that many lenovos root easily, but of course this is a pretty new device(?).
leripe said:
Well it charges long and the charge stays long, so no issue here.
Seems that not that many lenovos root easily, but of course this is a pretty new device(?).
Click to expand...
Click to collapse
OK let's try this
Install mtk drivers
Install USB and adb drivers
Install v root 1.7.8
Now tick adb debugging and connect your device to PC run v root and click root button after device get connected to v root
Let me know if you have any issues
All the best ?
Sent from my x604 using Tapatalk
The-Immortal said:
OK let's try this
Install mtk drivers
Install USB and adb drivers
Install v root 1.7.8
Now tick adb debugging and connect your device to PC run v root and click root button after device get connected to v root
Let me know if you have any issues
All the best ?
Sent from my x604 using Tapatalk
Click to expand...
Click to collapse
Can you link all the drivers?
Edit: Vroot link here: http://vrootdownload.info/vroot1.7.8/
leripe said:
Can you link all the drivers?
Edit: Vroot link here: http://vrootdownload.info/vroot1.7.8/
Click to expand...
Click to collapse
If you have win7 or win8/8.1 USB drivers will automatically installed when you connect device
Adb driver I hope this will work
http://adbdriver.com/downloads/
If it fails make a google search am sure you will find it
Sent from my x604 using Tapatalk
The-Immortal said:
If you have win7 or win8/8.1 USB drivers will automatically installed when you connect device
Adb driver I hope this will work
http://adbdriver.com/downloads/
If it fails make a google search am sure you will find it
Sent from my x604 using Tapatalk
Click to expand...
Click to collapse
Installed everything and tried vroot once again (I have tried it before).
Still not rooted. And btw that vroot at least tries to install bunch of bloatware crap on the pc.
Edit:
I would suggest for anyone who installed Vroot to your pc to scan the whole pc after you uninstall the vroot.
Here are the scanning tools:
Malwarebytes
adwcleaner
superantispyware
hitmanpro
leripe said:
Installed everything and tried vroot once again (I have tried it before).
Still not rooted. And btw that vroot at least tries to install bunch of bloatware crap on the pc.
Edit:
I would suggest for anyone who installed Vroot to your pc to scan the whole pc after you uninstall the vroot.
Here are the scanning tools:
Malwarebytes
adwcleaner
superantispyware
hitmanpro
Click to expand...
Click to collapse
I got a successful root by flashing Recovery.rar from lenovo-forums.ru, (it's easy to google, I'm not allowed to post links) with the included SPFlash Tool and afterwards flashing the needed SU binaryies and apk. However, this will mess up the OTA updates, and I can't find the stock recovery again.
Therefore, I really beg anyone having the stock recovery to post it, enabling us to switch between them, whenever we want to apply any OTAs.
Thanks a lot!
nkr said:
I got a successful root by flashing Recovery.rar from lenovo-forums.ru, (it's easy to google, I'm not allowed to post links) with the included SPFlash Tool and afterwards flashing the needed SU binaryies and apk. However, this will mess up the OTA updates, and I can't find the stock recovery again.
Therefore, I really beg anyone having the stock recovery to post it, enabling us to switch between them, whenever we want to apply any OTAs.
Thanks a lot!
Click to expand...
Click to collapse
Well I very highly doubt that there will be any more updates for a device with this price range. And since the next android version is the L version, which requires more work than before.
Edit2: http://forum.xda-developers.com/android/development/guide-lenovo-a3500-h-t2879208 found this. Tested and it works. Will edit it to the first post.
The same as me
i cant flash update.zip from cwm recovery and need to restore the stock recovery ...
I think flashing the stock rom can solve the problem..
.by using the sp flash tool we can select to flash recovery only ....unticking the others except recovery.img ....you just try to download the stock rom and flash the recovery
Same problem
Heya guys!
I have the same problem here.. I can't run the .zip file from the SD card, it get interrupted every time. Any ideas?
drabuaiad said:
The same as me
i cant flash update.zip from cwm recovery and need to restore the stock recovery ...
I think flashing the stock rom can solve the problem..
.by using the sp flash tool we can select to flash recovery only ....unticking the others except recovery.img ....you just try to download the stock rom and flash the recovery
Click to expand...
Click to collapse
I dont know what you two are trying to do but this thread is about rooting the lenovo A3500-FL not about lenovo stock rom.
Rooting..
Yes indeed, that's what I'm trying to do. Rooting the A3500-FL. According to the instructions you need to install the SuperSU from a zip on your SD card. When I try do that it gets interrupted every time. Installing recovery went well. So I'm not getting what I do wrong? Any ideas?
leripe said:
I dont know what you two are trying to do but this thread is about rooting the lenovo A3500-FL not about lenovo stock rom.
Click to expand...
Click to collapse
Mrosenho said:
Yes indeed, that's what I'm trying to do. Rooting the A3500-FL. According to the instructions you need to install the SuperSU from a zip on your SD card. When I try do that it gets interrupted every time. Installing recovery went well. So I'm not getting what I do wrong? Any ideas?
Click to expand...
Click to collapse
http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip and y ou mean this when you talk about update.zip?
And I hope you are using the install zip from sdcard option and the choose zip from sdcard option?
Boot to cmw.
Install zip from sdcard.
Choose zip from sdcard.
browse to your supersu zip and apply.
Now I also update the first post's guide, so you can check that out too.
Thanks for the help so far. But now I'm starting to doubt that the CWM install went successfully. Let me show you a picture of my screen after a failed install of the UPDATE-SuperSU-v2.02.zip -file. (ht_tps://ww_w.dropb_ox.com/s/1wrnatzjk2gn42h/2014-10-09%2008.50.40.png?dl=0) (slightly modified link because of forum rules, just take out the _) I'm using the "apply update from sdcard" option, then I browse to the SuperSU.zip -file and apply it. Then it starts installation, but aborts it in a few seconds. So am I booting to just a normal recovery mode and not CWM? (Sorry if all this seems totally ignorant, I have only flashed roms before, never rooted a new device)
leripe said:
UPDATE-SuperSU-v2.02.zip and you mean this when you talk about update.zip?
And I hope you are using the install zip from sdcard option and the choose zip from sdcard option?
Boot to cmw.
Install zip from sdcard.
Choose zip from sdcard.
browse to your supersu zip and apply.
Now I also update the first post's guide, so you can check that out too.
Click to expand...
Click to collapse
Yup.. This is the problem. The recovery runs fine from Flash Tool and claims it installs it. (Download ok) But I still don't seem to have CWM on the device. It's just normal recovery mode. So any ideas about the CWM-installation? What could possibly go wrong? I get no error messages. Cheers.
//Mike
Mrosenho said:
Thanks for the help so far. But now I'm starting to doubt that the CWM install went successfully. Let me show you a picture of my screen after a failed install of the UPDATE-SuperSU-v2.02.zip -file. (ht_tps://ww_w.dropb_ox.com/s/1wrnatzjk2gn42h/2014-10-09%2008.50.40.png?dl=0) (slightly modified link because of forum rules, just take out the _) I'm using the "apply update from sdcard" option, then I browse to the SuperSU.zip -file and apply it. Then it starts installation, but aborts it in a few seconds. So am I booting to just a normal recovery mode and not CWM? (Sorry if all this seems totally ignorant, I have only flashed roms before, never rooted a new device)
Click to expand...
Click to collapse
thanks ...
It is work fine for me on a3500 fl with 4.4.2 ver a442_01_26_140911_se
Mrosenho said:
Yup.. This is the problem. The recovery runs fine from Flash Tool and claims it installs it. (Download ok) But I still don't seem to have CWM on the device. It's just normal recovery mode. So any ideas about the CWM-installation? What could possibly go wrong? I get no error messages. Cheers.
//Mike
Click to expand...
Click to collapse
Same for me, what about this @leripe ?
EDIT// Oh, It's working now, tried to flash it one more time, then I held a power button until Lenovo logo appeared and then I pressed Vol UP and Vol DOWN and the CWM came in, thank you! Now my tablet is finally rooted
Hi, i have from a couple of day the ubuntu edition of pro 5, for various reason i want to run android on it and also make an image of system to give the opportunity for android users to get the ubuntu experience... any help?
- i have flashed the recovery from canonical (recovery-turbo) with unlocked ADB
- i can access to fastboot and to adb trough recovery
- i have make a map of partitions (ls -al /dev/block/platform/*/by-name)
- i have try to copy the system to sd card ( dd if=/dev/block/sda41 <--- system partition of=/media/F49C-xxxx <--- my sdcard) but it not find the sd
- on the side of android flash i think that the procedure on this post maybe ok http://forum.xda-developers.com/show...53&postcount=3 but the software (MultiUpgrade 4.8.5) fail to start
- ever for android flash, i have also think to put a complete update.zip to the root of device but the / folder is read only system.
Any help for both purpose are welcome
some news...
some news... i have successfuly install TWRP and maked a backup of system/data/boot if anyone want to play with backup or try to flash it i can upload it (it's a 5gb folder, tell me wich file hosting you want)
i have try after backup to flash the CM rom and some Flyme but i have always the same error: "could not find 'meta-inf/com/google/android/update-binary' in the zip file"
Any suggestion?
ps: if anyone has a TWRP backup of his pro 5 i can try to restore on my...
Hi,
I also got my Meizu Pro 5 Ubuntu Edition a couple of days ago, and even I expected it to be not-so-polished, I couldn't believe the number of features missing and the number of unresolved bugs. Being a long-term Linux/Ubuntu user I will (from now on) closely watch the development process, but meanwhile I would like to use my new phone.
If you make it to flash Flyme, please share the full process.
It would be great if we could go back-and-forth Android/Ubuntu to check the progress from time to time (as Nexus can)
Toroman said:
Hi,
I also got my Meizu Pro 5 Ubuntu Edition a couple of days ago, and even I expected it to be not-so-polished, I couldn't believe the number of features missing and the number of unresolved bugs. Being a long-term Linux/Ubuntu user I will (from now on) closely watch the development process, but meanwhile I would like to use my new phone.
If you make it to flash Flyme, please share the full process.
It would be great if we could go back-and-forth Android/Ubuntu to check the progress from time to time (as Nexus can)
Click to expand...
Click to collapse
As we find someone that want share his TWRP backup, i think that a deep wipe and a restore from backup work...
mobilezonerm said:
As we find someone that want share his TWRP backup, i think that a deep wipe and a restore from backup work...
Click to expand...
Click to collapse
In this thread there is a link:
http :// forum.xda-developers. com/meizu-pro-5/development/rom-cyanogenmod12-1-temasek-unofficial-t3358744
http :// xep.8800.org/ pro5/
But also on the Canonical site:
https ://wiki.ubuntu. com/Touch/ Devices
(Sorry for the spaces the policy doesn't allow me to post urls yet.)
I somehow thought that we can use official Flyme download from the Meizu website and the official Ubuntu turbo image without the need of installing TWRP or anything - and flash both via USB.
Functionality with TWRP would be a plus.
Well I think you can. Press both Volume up + power button, that's the stock recovery where you can flash images from meizu. So you probably can get Flyme when you have Ubuntu, but when you want to go back I think you'll have to flash the ubuntu turbo recovery back through fastboot. I think you can go without TWRP.
Pleytos said:
Well I think you can. Press both Volume up + power button, that's the stock recovery where you can flash images from meizu. So you probably can get Flyme when you have Ubuntu, but when you want to go back I think you'll have to flash the ubuntu turbo recovery back through fastboot. I think you can go without TWRP.
Click to expand...
Click to collapse
Well the power + up gives (a kind of) recovery that shows a screen with the Ubuntu logo in the center - nothing else. I believe the android version has a different recovery?
Ah I never saw that screen. Yes Android/Flyme has a different screen: like this
You can try to to use the Ubuntu recovery to flash a Flyme Rom. I did it with TWRP, but never tried it with the Ubuntu recovery.
The Flyme Rom replaces the recovery and boots with both TWRP and the Flyme recovery, maybe even with a Ubuntu recovery (I can't image it to be that different.).
Edit:
You might want to back up your current recovery. I just flashed the recovery from Canonicals website, and its just the English/Chinese Flyme one.
just a moment... thank's Pleytos, but we need the TWRP backup folder... on yours link there are the CM rom and on the Canonica site there are only the update.zip....
Keep in mind, also the partitons are different on Pro 5 Ubuntu, for this the best is to have the entire backup of an android phone, both CM rom and Update.zip are not flashable by TWRP (i have try)
and Toroman the recovery that you see is the original recovery, if you flash the recovery on Canonical website you have the screen posted by Pleytos BUT with this recovery you obtain only the unlock of ADB in recovery and, as you can read from the screenshoot to make an update you have to put a "update.zip" on root directory of the phone that, unfortunally in ubuntu edition, is read-only file system... i have just unlock it from linux terminal with a "remount,rw" but if you try to copy update.zip (many versions) to root fonder there aren't space enough...
I've make lot of try in this day and i have find two possible solutions:
- flash a rom with MultiUpgrade 4.8.5 (official software used by Meizu, that not start because some token is missing)
as reported in a big russian forum
- make a total erase of internal memory and rewrite it with a image from android Pro 5 phone (TWRP Backup)
Pleytos, one answer, wich room have you flash via TWRP? (both Ciano and Flyme, wich version)
All done... guide in details:
- on windows install driver: Samsung_USB_Drivers_for_Mobile_Phones_1.5.9.0
- on linux: run from terminal "$ sudo add-apt-repository ppa:ubuntu-sdk-team/ppa" and "$ sudo apt-get install phablet-tools"
- download from here (http://people.canonical.com/~plars/touch/recovery-turbo.img) the recovery image with unlocked ADB
- turn off the phone and turn on with volume down pressed to enter in fastboot mode
- in windows go to the folder where you have fastboot / in linux open the terminal and give "sudo -s"
- make a flash of recovery (fastboot flash recovery recovery-turbo.img)
- now download the TWRP recovery (i've used the 3.0.0 on this forum) and from terminal flash it (fastboot flash recovery "nomerecovery")
- now you have to copy first a CM rom on the phone or sd, before flash the CM rom erase completely the system partition, flash it whit TWRP and only after you are able to flash Flyme rom
keep in mind to make a full backup by TWRP and save it on external archive before operate. (it's less complicate for future restore and help you if something goes wrong)
if someone need the backup of Ubuntu for his phone, ask me...
Ubuntu Dump
mobilezonerm said:
if someone need the backup of Ubuntu for his phone, ask me...
Click to expand...
Click to collapse
Hello, can you provide me full Ubuntu dump? Im very interesting to install native Ubuntu touch on Meizu Pro 5. Share the link, for example, on Mega or Google Drive
Need you help
mobilezonerm said:
Hi, i have from a couple of day the ubuntu edition of pro 5, for various reason i want to run android on it and also make an image of system to give the opportunity for android users to get the ubuntu experience... any help?
- i have flashed the recovery from canonical (recovery-turbo) with unlocked ADB
- i can access to fastboot and to adb trough recovery
- i have make a map of partitions (ls -al /dev/block/platform/*/by-name)
- i have try to copy the system to sd card ( dd if=/dev/block/sda41 <--- system partition of=/media/F49C-xxxx <--- my sdcard) but it not find the sd
- on the side of android flash i think that the procedure on this post maybe ok http://forum.xda-developers.com/show...53&postcount=3 but the software (MultiUpgrade 4.8.5) fail to start
- ever for android flash, i have also think to put a complete update.zip to the root of device but the / folder is read only system.
Any help for both purpose are welcome
Click to expand...
Click to collapse
can any one help me remotely to install android on miuze pro 5 which coming with Ubuntu , i download every thing but lost with steps, or can you provide clear steps so i can follow
mobilezonerm said:
Pleytos, one answer, wich room have you flash via TWRP? (both Ciano and Flyme, wich version)
Click to expand...
Click to collapse
Hi! I flashed CyanogenMod 12.1 from Faust93, AICP 12.1 Rom from Faust93, and Flyme 5.1.6.0G & Flyme 5.1.5.0G via TWRP, It worked for me. I haven't been able to go back to Ubuntu though. Ubuntu-device flash doesn't work for me.
I can also flash Flyme with the standard recovery/ Canonical recovery by putting it on /sdcard/
tamyou2020 said:
can any one help me remotely to install android on miuze pro 5 which coming with Ubuntu , i download every thing but lost with steps, or can you provide clear steps so i can follow
Click to expand...
Click to collapse
Yes I can help you, are you running Ubuntu on your PC or Windows?
Before flashing Android, could you maybe help me with getting some Ubuntu files back? I can also help you through a chat or something if that is easier. Never mind I finally did it!I can still help you though, if you need me
Hi , Am running Ubuntu over windows ( virtual box ) we can go with team viewer , or if you want i can install Ubuntu in separate machine , Please let me know how we can communicate
Pleytos said:
Hi! I flashed CyanogenMod 12.1 from Faust93, AICP 12.1 Rom from Faust93, and Flyme 5.1.6.0G & Flyme 5.1.5.0G via TWRP, It worked for me. I haven't been able to go back to Ubuntu though. Ubuntu-device flash doesn't work for me.
I can also flash Flyme with the standard recovery/ Canonical recovery by putting it on /sdcard/
Yes I can help you, are you running Ubuntu on your PC or Windows?
Before flashing Android, could you maybe help me with getting some Ubuntu files back? I can also help you through a chat or something if that is easier. Never mind I finally did it!I can still help you though, if you need me
Click to expand...
Click to collapse
Hi,
I've been away for some time, and I can see some nice progress in making Android work on the Ubuntu edition.
I might be repeating myself but it would be ideal if we (who own the Ubuntu edition) can go back and forth seamlessly. Unfortunately my flashing skills are buried in the ancient time of the HTC HD2 so I need some assistance (as probably more of us do). Here are some questions, I appreciate the effort and the help (assume I'm using Ubuntu on the desktop) (if something is easier in windows - please note). This would be a full circle:
1 Is it possible and how to make a COMPLETE backup of the Ubuntu edition phone (including the recovery and everything) to be able to get back to the factory condition (and using what tools/steps). I think I have read somewhere that OTA updates does not work with custom recovery or something similar.
2 after making the backup from question 1 - assume flashing official flyme to make it like a factory android device. (orig.recovery, OTA and so)
3 flash ubuntu back using backup provided with one.
I guess the ubuntu edition has the bootloader unlocked factory default.
Info on flashing CM or similar can than be like flashing it on original android - assuming (2) is working
As already said, just a remainder - Ubuntu recovery screen that came with the original phone is just ubuntu logo on the center on the screen - I don't know if it is important for any feature (OTA or something)
Best regards!
Also, looking around I have found this - seems interesting also
https://wiki.ubuntu.com/Touch/DualBootInstallation
Toroman said:
Also, looking around I have found this - seems interesting also
https://wiki.ubuntu.com/Touch/DualBootInstallation
Click to expand...
Click to collapse
Actually this is most interesting! I would love to buy this phone, ubuntu edition. But since it would be my primary device and ubuntu touch not quite there yet, I'm not. That page about dual boot seems outdated though. And it is about nexus devices
Being able to have dual boot with android or even as someone said above have a back up and every 2 months restore ubuntu and check the progress would be great.