Related
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?
I bought this tablet and I want to install a custom rom. I am not interested in dual booting. I found a thread titled
"[GUIDE]A500/501/G100W-Installing ICS V8 UNL-BL & CWM Or back to HC BL(24-6-2012) "
Information there is a little confusing to me. On my A200, the steps were simple, unlock boot loader, install CWM and then root/install rom. Then I was done. Seems like I have to do more steps on theA500, which I don't mind I just want to do it right. Is it my understanding that the thread is for dual booting, it also talks about CPU ID.
I found another thread that talks about Afterota v1.09, do I only need to just do this for what I want to do or do I need to do more? Why would I need to install a ICS bootloader, I have ICS now, stock, doesn't it already have it? I tried looking at the Q/A but I just ended up more confuse.
Could someone just give point me in the right direction so I can go about unlocking bootloader and installing CWM so I can install a custom rom.
I have Android 4.0.3 Kernel Version 2.6.39.4+ Stock
Side question, my unit is a 16gb model but its only reading about 12.71gb, does anyone know why?
A500 works differently: the stock ICS BL is locked and cannot be unlocked from fastboot. What we can do however, is to flash custom BL, since we know the device "Secure Boot Key". In general the term "ICS BL" means my patched BL, which you can find in my signature. There is a bunch of guides to get it flashed on the forum, and blackthunder made a tool to simplify the process.
Skrilax_CZ said:
A500 works differently: the stock ICS BL is locked and cannot be unlocked from fastboot. What we can do however, is to flash custom BL, since we know the device "Secure Boot Key". In general the term "ICS BL" means my patched BL, which you can find in my signature. There is a bunch of guides to get it flashed on the forum, and blackthunder made a tool to simplify the process.
Click to expand...
Click to collapse
Alright, so I do not need to do
Option 1 use Afterota for A500/G100W IF YOU ARE ON OTA ICS and follow this thread
or
Option 2 , keep reading.... don't be a chicken , just do it !!.
then I just need to use blackthun3r tool? I tried it but when I launch A500APXFLASH.EXE it ask me for a SBK and the guide said this "the v0.4 APX flash tool will give your SBK automaticly !!" but its blank it has not given me SBK automatically. So I was directed to this thread
http://forum.xda-developers.com/showthread.php?t=1810618
which has the "SBCalc "
which then directed me to
http://forum.xda-developers.com/showthread.php?t=1624645
which reads
GET ME MY CPUID!!!
There are 2 different cpuid
ICS CPUID has only 13 digits/characters and is your "serial no." as reported in settings, on your sdcard cover and on the box
we are only interested in the 15 digit HC CPUID this can only be got:
(1) From a PC using Blackthund3rs A500 manager
(2) From your device using Terminal Emulator App
(3) From USBDeview must have previously used the Tab under HC with the PC you're using
(4) From a uid.txt in any Honeycomb-cwm backup in external_sd/clockworkmod/backup/"your_HC_backup" folder
(5) From adb devices if you're running honeycomb
(6) From cwm 1.7.2 via on screen display and a text file - great if you are on ICS already
(7) Master_Ellis has posted that he found the HC cpuid in /sys/firmware/fuse/acer_cpuid - add a zero to the front!!!
please if anyone uses this let us know if this is correct!!!
thanks Master for the heads Up!!!
(8) Gersma's most excellent OTA Toolmakes most of this thread obsolete!!!! Thankyou Gersma for all you've done OTA Tool is all anyone ever needs....
Features :
I don't get it though, I thought you said all I needed was the blackthund3r apx flash utility. I'm really confuse, can you specify what I need to do?
I went back to the original thread where the blackthund3r flash tool is and it clearly says
"3-When it askes for your SBK you need to type it in , the v0.4 APX flash tool will give your SBK automaticly !!"
But I do not see the SBK come up automatically. Man all I want is to be able to flash roms ;/ Can you specify what I need to do please I do not want to jump the gun here and brick my device. I see two files in the zip file, a500 Manager v1.0.2 and Apx Flash Utility v0.4
Alright I figured out what I was missing and manage to go through the whole process easily. I have Apex now but how do I install CWM or TWRP? WHen I go into recovery I get a dead android.
Lots of trials and errors lol so I figured out Recovery only works the first time, is there any way to have CWM on there permanently?
Update
Recovery always works now, wasn't sure if that was a glitch or what. Anyways, thanks Skrilax, that little piece was enough for me to get going. I understood the guide once I knew what I needed which required me reading a few threads. Guide kinda needs to be tweaked a little.
F9zSlavik said:
Lots of trials and errors lol so I figured out Recovery only works the first time, is there any way to have CWM on there permanently?
Update
Recovery always works now, wasn't sure if that was a glitch or what. Anyways, thanks Skrilax, that little piece was enough for me to get going. I understood the guide once I knew what I needed which required me reading a few threads. Guide kinda needs to be tweaked a little.
Click to expand...
Click to collapse
Recovery not sticking is due to having a stock rom. Rooting with ICS Root 7.1.1 stops this
Sent from my Iconia A500 using Tapatalk 2
Just noting: stock recovery won't work, and if you ever applied OTA, booting Android will overwrite recovery, unless you remove the updater. And for the guides, all will work, some are more automated, some less.
Orrite guys,
This is my first thread post on xda so i hope that - 1: i get it in the right place... and 2: i hope it helps
OK, so i wanted to root/flash away on my GS3 GT-I9300 but i'm a linux user (peppermint - variation of ubuntu 12.04) and i had a hard time finding the information i needed to be confident enough to attempt using a terminal with heimdall to flash a recovery image onto my fone so i could install .zips like the awesome supersu
I'll keep it short and simple, because it is... its just not a common way as most people are windows or mac and personally i loathe both
Attached is a .zip with everything you need and a copy of these instructions.
Here we go:
I have done this on my own GS3 GT-I9300 a couple of times, as well as one other GS3 GT-I9300
Put fone into download mode - Volume Down, Home and Power buttons together till it responds and connect to your pc
FAQ
Q: Does this root method erase my settings and apps?
A: No, it doesn’t touch a thing, very safe to do.
Q: I ended up in Kernel panic mode, what do I do?
A: Relax, that’s same as ODIN download mode, simply run Heimdall again and flash the files again, it will work.
Q: I don’t get ClockworkMod Recovery like you do, just get Android with belly open.
A: If you’ve updated to newer software update, the stock OS will over-write ClockworkMod Recovery on reboot. To fix this, make sure “auto-reboot” is checked off in ODIN, then take the battery out when it’s done flashing in ODIN. Then enter ClockworkMod Recovery right away
Note: below is the 'no reboot' command line for linux (make sure you specify the correct file path to the recovery image) - once flashing is finished, unplug the phone and remove the battery. Replace the battery and now boot straight to recovery and flash supersu.zip
Command line for flashing recovery image
sudo heimdall flash –recovery recovery.img –no-reboot
It really is that simple.
Humanspida
Credits to everyone on xda (too many to list but you know who you are) with threads providing help on this, as well as:
galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3-on-linuxubuntu
which was the other place i eventually used
hope this helps.
.
thx for that man
also, if you're on a i64 based computer, do not use the last version of heimdall, but the 1.3.1 instead
github/Benjamin-Dobell/Heimdall/issues/43 (I'm not allowed to post links here...)
jobano said:
also, if you're on a i64 based computer, do not use the last version of heimdall, but the 1.3.1 instead
github/Benjamin-Dobell/Heimdall/issues/43 (I'm not allowed to post links here...)
Click to expand...
Click to collapse
This should be sorted now. As of November 2013 I've been successfully using the heimdall from ubuntu repositories (v1.4.0) on x86_64.
After almost a full day of flashing I now have a 100% successful method of flashing any stock JB Firmware
With this method I have been able to successfully flash any stock JB Firmware from 10.4.2.9 all the way through to 10.6.1.27.5 without issue.
unfortunately you can not go back to ICS bootloader or firmware (there is a signature mismatch issue here).
Try this at your own risk, I will not be responsible for a bricked device.
Recommend doing NVFlash first so your tablet is Unbrickable
NVFlash for ICS bootloader
NVFlash for JB bootloader
Warning:
If you flash an incorrect recovery to a 4.2 bootloader there is about a 90% chance that fastboot flash commands will now just freeze the tablet - When you attempt to flash via fastboot everything will seem to go ok on the command prompt but you will not see the blue progress bar on the tablet when flashing & the reboot command will not reboot the tablet after the flash command & nothing will have flashed to the tablet.
If this is the case try this solution.
Please read below for how to check your bootloader version and confirm your flashing the correct recovery.
Requirements:
Must be unlocked (Method 1 seems to work fine for locked devices but must be unlocked for Method 2 to flash custom recovery).
Must have working fastboot
Working adb in recovery (optional). I use adb in this method for rebooting but this can be done manually with vol- & power.
Always make a backup first.
Files Needed:
Download the stock JB firmware you wish to flash from either the Asus website or from the Index thread here, be sure to download the correct SKU version you wish to use On your tablet you can check what SKU your using by going to settings>about tablet, scroll down to build number and you can see SKU version..
If using method 2 download the TWRP recovery you require, Here is a link to the TWRP thread. When you download a version of TWRP it will have a name like "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob" - You can rename to something shorter for flashing if you like, I rename like so "twrp-2.5.0.0-4.2.blob".
What recovery to flash for bootloader version: example for TF300T model:
Check & confirm what bootloader your on - boot to bootloader menu (vol- & power) and look at the text in top left, your bootloader version number is there.
JB 4.1 firmwares
If current bootloader = 10.4.2.9 - JB 4.1 - recovery to flash = TWRP "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" or CWM
If current bootloader = 10.4.2.13 - JB 4.1 - recovery to flash = TWRP "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" or CWM
If current bootloader = 10.4.2.17 - JB 4.1 - recovery to flash = TWRP "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" or CWM
If current bootloader = 10.4.2.18 - JB 4.1 - recovery to flash = TWRP "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" or CWM
If current bootloader = 10.4.2.20 - JB 4.1 - recovery to flash = TWRP "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" or CWM
JB 4.2 Firmwares
If current bootloader = 10.6.1.8 - JB 4.2 - recovery to flash = ONLY TWRP "openrecovery-twrp-2.4.4.0-tf300t-4.2.blob" - flashing a non-4.2 version of TWRP or any version of CWM will brick device. Also flashing 2.5.0.0-tf300t-4.2 on the 10.6.1.8 bootloader results in a split-screen issue.
If current bootloader = 10.6.1.15.3 - JB 4.2 - recovery to flash = ONLY TWRP "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob" - flashing a non-4.2 version of TWRP or any version of CWM will brick device.
If current bootloader = 10.6.1.27.1 - JB 4.2 - recovery to flash = ONLY TWRP "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob" - flashing a non-4.2 version of TWRP or any version of CWM will brick device.
If current bootloader = 10.6.1.27.5 - JB 4.2 - recovery to flash = ONLY TWRP "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob" - flashing a non-4.2 version of TWRP or any version of CWM will brick device.
My Notes about TWRP 2.4.4.0-4.2:
TWRP 2.4.4.0-4.2 will not mount my sandisk 64gb micro SDXC UHS-1 class 10 card, but previous versions of TWRP have no issue. I believe this is a UHS-1 issue. TWRP 2.5.0.0-4.2 has fixed this bug and and can now mount 64gb micro SDXC UHS-1 class 10 card again.
Method 1
Unzip the firmware zip you downloaded, there will be another zip file inside.
Example:
Lets say you choose WW 10.4.2.20 firmware. (same method apply's for any firmware version and SKU you choose - US, WW, JP, TW, CN)
[*]Unzip "WW_epaduser_10_4_2_20_UpdateLauncher.zip"and you will find another zip inside "WW_epad-user-10.4.2.20.zip".
[*]Now unzip the WW_epad-user-10.4.2.20.zip and you will find a "blob" file.
[*]Now copy the blob file to your android-sdk\platform-tools folder.
Now to the flashing:
With your device loaded in android go to settings, developer options and make sure they are on & usb debugging is on.
[*]Plug device into PC with usb cable & boot to fastboot.
Using adb commands
Open command prompt (run as admin) & cd to you android-sdk\platform-tools folder.
Check your PC can see your device
Code:
adb devices
You should get a list with you device s/n, if not then adb is not setup.
Next
Code:
adb reboot-bootloader
or
Manually boot to fastboot
Hold vol- & power button to boot to bootloader then connect to PC.
Fastboot will start automatically when connected to PC on the 4.2 bootloaders. On 4.1 bootloaders you will need to select the usb icon using vol- to highlight the usb icon and vol+ to select.
Note:
In bootloader NEVER select the Wipe Data icon or you will brick.
Once in fastboot open command prompt & cd to you android-sdk\platform-tools folder and type command
Code:
fastboot devices
and again here you should get a list with you device s/n, if not then fastboot is not setup.
[*]If OK we can now flash the system blob we put in the platform-tools folder
Code:
fastboot -i 0x0b05 flash staging blob
This will take about 10 minutes to send & write system, you will see a progress bar on device when system is writing.
[*]When complete
Code:
fastboot reboot
This method should work fine but have found that sometimes the device will get stuck at the boot animation, if this happens method 2 works fine every time.
Method 2
Unzip the firmware zip you downloaded, there will be another zip file inside.
Example:
Lets say you choose WW 10.4.2.20 firmware. (same method applys for any firmware version and SKU you choose - US, WW, JP, TW, CN)
[*]Unzip "WW_epaduser_10_4_2_20_UpdateLauncher.zip"and you will find another zip inside "WW_epad-user-10.4.2.20.zip".
[*]Place a copy of the WW_epad-user-10.4.2.20.zip on your microSD card.
[*]Now on PC unzip the WW_epad-user-10.4.2.20.zip and you will find a "blob" file.
[*]Now copy the blob file to your android-sdk\platform-tools folder.
[*]Now copy the "twrp-version.blob" file you downloaded to your android-sdk\platform-tools folder.
--Make sure you have the correct twrp version for the firmware your flashing.
Now to the flashing:
With your device loaded in android go to settings, developer options and make sure they are on & usb debugging is on.
[*]Plug device into PC with usb cable & boot to fastboot.
Using adb commands
Open command prompt (run as admin) & cd to you android-sdk\platform-tools folder.
Check your PC can see your device
Code:
adb devices
You should get a list with you device s/n, if not then adb is not setup.
Next
Code:
adb reboot-bootloader
Manually boot to fastboot
Hold vol- & power button to boot to bootloader then connect to PC
Fastboot will start automatically when connected to PC on the 4.2 bootloaders. On 4.1 bootloaders you will need to select the usb icon using vol- to highlight usb icon and vol+ to select.
Note:
In bootloader NEVER select the Wipe Data icon or you will brick.
Once in fastboot open command prompt & cd to you android-sdk\platform-tools folder and type command.
Code:
fastboot devices
and again here you should get a list with you device s/n, if not then fastboot is not setup.
[*]If OK we can now flash the system blob we put in the platform-tools folder.
Code:
fastboot -i 0x0b05 flash staging blob
This will take about 10 minutes to send & write system, you will see a progress bar on device when system is writing.
[*]Once this has completed type in the command prompt.
Code:
fastboot reboot-bootloader
You can now check that your bootloader has upgraded/downgraded, look at the text in the top left of the bootloader screen and make sure it's changed to the firmware version you just flashed.
[*]Now again depending on the bootloader version go to fastboot.
Next
[*]In the below command I am using "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" for JB firmware 10.4.2.20, and shortened the name "twrp-JB.blob" so just change command according to TWRP version needed.
Code:
fastboot -i 0x0b05 flash recovery twrp-JB.blob
[*]Once this has completed type in the command prompt.
Code:
fastboot reboot-bootloader
[*]Now this time in bootloader select the "RCK" icon to enter twrp recovery.
[*]In twrp recovery select "Wipe".
[*]Here I do a complete wipe (cache, Dalvik cache, Factory Reset, System, Internal Storage & Format Data) I don't believe Internal Storage & Data Format are necessary but I like a full clean flash.
[*]Once you have done full wipe type in command prompt.
Code:
adb reboot-bootloader
or manually reboot to bootloader, hold vol- and power button.
[*]Now again in bootloader select the "RCK" icon to enter twrp recovery.
[*]In twrp recovery disconnect your device usb cable from PC.
[*]Select "Install" & select the firmware zip you copied to your external sd card and slide to flash/install.
[*]Once completed reboot, you will get message at top of recovery saying there is no OS installed are you sure you want to reboot - slide to confirm yes, another message will popup asking if you want root permissions installed - I select NO "Do not install" you can probably select yes here if you want twrp to root.
The device will reboot, you'll see a progress bar as the signature is being matched, it will reboot again when done.
Now device will boot with the stock JB bootloader & firmware you have chosen.
Done.
You can now flash twrp, then flash any custom rom for that firmware.
As I have said I have done this with all stock WW JB firmware available and can confirm that the bootloader does change and system will boot and run without any issues. But try at own risk.
Firmware I have done this with: Only tried with WW SKU
10.6.1.27.5
10.6.1.27.1
10.6.1.15.3
10.6.1.8
10.4.2.20
10.4.2.18
10.4.2.17
10.4.2.13
10.4.2.9
More Info:
Downgrading from CROMi-X back to CROMi-3.4.6
Upgrading from ICS to JB
If you this information is helpful please hit the thanks button.
Nice work and thanks for sharing it PJC21. Looks like you've got quite a bit of time invested in this info. :thumbup:
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
Thank you for the detailed information. Couldn't one just flash the stock .zip file from TWRP, reboot, reinstall TWRP recovery from fastboot and then wipe in TWRP as you would do when upgrading? I have done that between JB releases before, but I guess the bootloader didn't change.
jimpmc said:
Thank you for the detailed information. Couldn't one just flash the stock .zip file from TWRP, reboot, reinstall TWRP recovery from fastboot and then wipe in TWRP as you would do when upgrading? I have done that between JB releases before, but I guess the bootloader didn't change.
Click to expand...
Click to collapse
Yeah quite possibly, I didn't even think to try it that way :laugh:
However if just flashing the system blob via fastboot then rebooting, my devices will get to the boot animation screen and just sit there.
I do prefer being on the correct bootloader before flashing the firmware though and this way allows for that.
Maybe consider making this two parts.
1. with twrp recovery installed
2. with stock recovery installed
Good info and needed!
Note: I should have added with twrp, fastboot, or adb to flash I always loose root and data. With stock if I am using the same version or anything numerically higher I keep root and data but going to a lower numeric I loose root and data.
I hope this is understandable.
I can confirm that this method 101 % works. :good:
I have migrated from custom ROM 4.2.1 to factory 4.2.1.
After final reboot I lost root, but rooting afterwards gave me rooted factory 4.2.1. No problems at all.
Thanks for this.
Q-Logic said:
I can confirm that this method 101 % works. :good:
I have migrated from custom ROM 4.2.1 to factory 4.2.1.
After final reboot I lost root, but rooting afterwards gave me rooted factory 4.2.1. No problems at all.
Thanks for this.
Click to expand...
Click to collapse
+1 works
Sent from my GT-I9100 using xda app-developers app
OK, I have a question. I see this works with full ROMs from Asus, good. What about TWRP backups?
So, before I upgraded to 4.2.1, I took a TWRP backup of 4.1.1 latest v20 build. If I restored that backup via TWRP, would it work? Would the bootloader revert to the older one (with the USB icon)? My backup did include the boot partition, but I didn't know if this would brick the device.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Just to make sure ...
Have you actually downgraded from 4.2.1 to 4.1.1?
I'm on 4.2.1 (10.6.1.8; Energy Rom) at the moment and eager to browse all those nice custom roms that are based on 10.4.x.x. like cm 10.1 & co.
Since the 4.2 upgrade rearranged the file system i'm afraid of messing it up when reverting to pre-multiuser-versions ...
Also i'd love to have this nvflash brickproof thingie ...
You think I could give this a go?
MrsColumbo said:
Have you actually downgraded from 4.2.1 to 4.1.1?
I'm on 4.2.1 (10.6.1.8; Energy Rom) at the moment and eager to browse all those nice custom roms that are based on 10.4.x.x. like cm 10.1 & co.
Since the 4.2 upgrade rearranged the file system i'm afraid of messing it up when reverting to pre-multiuser-versions ...
Also i'd love to have this nvflash brickproof thingie ...
You think I could give this a go?
Click to expand...
Click to collapse
To be honest - I'm not sure, I didn't downgrade, let pjc21 say did he. I would be afraid to do mess with file system just like you.
But I would be interested to try this if his downgrading method works.
funnel71 said:
OK, I have a question. I see this works with full ROMs from Asus, good. What about TWRP backups?
So, before I upgraded to 4.2.1, I took a TWRP backup of 4.1.1 latest v20 build. If I restored that backup via TWRP, would it work? Would the bootloader revert to the older one (with the USB icon)? My backup did include the boot partition, but I didn't know if this would brick the device.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
I'm not sure here, but would think no as the new update has a different file system arrangement. I myself would not try this as I really have no idea what would happen.
MrsColumbo said:
Have you actually downgraded from 4.2.1 to 4.1.1?
I'm on 4.2.1 (10.6.1.8; Energy Rom) at the moment and eager to browse all those nice custom roms that are based on 10.4.x.x. like cm 10.1 & co.
Since the 4.2 upgrade rearranged the file system i'm afraid of messing it up when reverting to pre-multiuser-versions ...
Also i'd love to have this nvflash brickproof thingie ...
You think I could give this a go?
Click to expand...
Click to collapse
Yes I have downgraded from 4.2.1 (10.6.1.8) to 4.1.1 (10.4.2.20) and I have also downgraded through all the JB firmware back to the first JB firmware that came out 10.2.4.9 -28/08/2012- not that many people would want to go back that far but I was attempting to go all the way back to an ICS bootloader & firmware so I could access NVflash and become brickproof as my tab came with JB pre-loaded. When attempting to go from a JB bootloader & firmware to an ICS one there is a signature mismatch which I have not looked into as yet and am not sure it would even be possible to modify this to get a match. I will have a look when I get the time and look at the differences between the JB & ICS signatures to see if it might be possible to modify these.
Works fine
pjc21 said:
Yes I have downgraded from 4.2.1 (10.6.1.8) to 4.1.1 (10.4.2.20) and I have also downgraded through all the JB firmware back to the first JB firmware that came out 10.2.4.9 -28/08/2012- not that many people would want to go back that far but I was attempting to go all the way back to an ICS bootloader & firmware so I could access NVflash and become brickproof as my tab came with JB pre-loaded. When attempting to go from a JB bootloader & firmware to an ICS one there is a signature mismatch which I have not looked into as yet and am not sure it would even be possible to modify this to get a match. I will have a look when I get the time and look at the differences between the JB & ICS signatures to see if it might be possible to modify these.
Click to expand...
Click to collapse
Witch much satisfaction I can confirm this working. Had to sideload the update zip, though, 'cause I forgot to copy it to my external micro sd card. in the course I ****ed up the update (progress indicator not progressing, so i did a vol-+power-reset, subsequently rom did not load), but adb-d recovery again, inserted micro sd and did the update (downdate) to 10.4.2.20. running cm 10.1 nightly now.
Yeah, this brickproof mod sounds really good. I wouldn't want to miss up on jb's smoothness, though. IMHO JB and ICS are worlds apart. Maybe those guys give it a go with a 4.2-brickproof-mod one fine day
Thanks pjc21 for this outstandig work. This is what Android OS is about: being able to explore all possibilities of a fine piece of hardware you actually own instead of being led on a leash by a corporation. :good::good::good:
This worked pretty easy, returning from 4.2.1 ( 10.6.1.8) I flashed the 4.1.1 (10.4.2.20) blob through fast boot,then flashed twrp 2.3.3.0 in fast boot, rebooted into recovery restored my 4.1.1 backup and all is well.
pjc21 said:
Yes I have downgraded from 4.2.1 (10.6.1.8) to 4.1.1 (10.4.2.20) and I have also downgraded through all the JB firmware back to the first JB firmware that came out 10.2.4.9 -28/08/2012- not that many people would want to go back that far but I was attempting to go all the way back to an ICS bootloader & firmware so I could access NVflash and become brickproof as my tab came with JB pre-loaded. When attempting to go from a JB bootloader & firmware to an ICS one there is a signature mismatch which I have not looked into as yet and am not sure it would even be possible to modify this to get a match. I will have a look when I get the time and look at the differences between the JB & ICS signatures to see if it might be possible to modify these.
Click to expand...
Click to collapse
Please update us on your progress. Everything I've read says that going back to ICS for NVFlash cannot be done if the tablet came with JB. Thanks.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
wetbiker7 said:
Please update us on your progress. Everything I've read says that going back to ICS for NVFlash cannot be done if the tablet came with JB. Thanks.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
He stated you cannot go back to ICS in the first post,, but you can switch JB firmware pretty easy.
treo4life said:
He stated you cannot go back to ICS in the first post,, but you can switch JB firmware pretty easy.
Click to expand...
Click to collapse
Exactly. But........ he also said he was going to try and modify the signatures to see if he can get them to match. If he can succeed, it will be a huge breakthrough.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
That's true, don't know if he is going to try to tackle that one though.. would be nice to have the option...
Sent from my EVO using xda premium
treo4life said:
That's true, don't know if he is going to try to tackle that one though.. would be nice to have the option...
Sent from my EVO using xda premium
Click to expand...
Click to collapse
No doubt. Hopefully he'll continue working on it.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
I just received my new tablet ... Need to downgrade to 4.1.1 to be able to run AOSP Rom.
Thanks for the procedure. I will give it a try.
Dummy friendly guide how to upgrade, flash and install the latest Marshmallow Firmware and the latest ROM’s such as the ViperOne ROM 4.x.x, this guide is intended for those who are already slightly familiar with the flashing process and have previously managed to flash a ROM on their HTC One M9 device…
CHECKLIST BEFORE STARTING:
1) Phone is S-OFF
2) Unlocked Bootloader
3) Rooted
4) Latest TWRP recovery
5) SUPER CID changed to 11111111
6) External SD Card
7) NANDROID Backup and any or every other form of backup
8) Device drivers, Android SDK Platform Tools including ADB & FASTBOOT.
9) USB Debugging enabled.
10) BACK UP OF ALL YOUR DATA !!!
Before we begin make sure you back up all your data on both the internal and external SD card.
For the purpose of this tutorial we will be installing the latest ViperOneM9 ROM…
a) Downloaded and place the latest ViperOne ROM - ViperOneM9_4.x.x.zip on your External SD card,
Main Thread by j to the 4n is found here:
http://forum.xda-developers.com/one-m9/development/rom-viperonem9-1-0-0-tweaks-hub-t3072773
Latest ViperOne ROM for download is here:
http://venomroms.com/htc-one-m9/
b) If you are currently on ViperOneM9 3.5.0 or older and wish to upgrade to the latest 4.x.x than the latest Marshmallow firmware is required (3.35.401.12 or 3.35.617.12 firmware)… This can be found here and within Sneakyghost original thread.
https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
Now download the latest version of either:
NO WIPE ZIP
or
FULL STOCK WIPE ZIP
For this tutorial we will use the FULL STOCK WIPE ZIP (to archive a clean install – this will wipe everything on your phone excluding the External SD card)
c) Place the downloaded M9_3.35.401.12_FullStock_wipe.zip into your Android SDK Platform Tools Folder (for example C:\Android\ if this is where all your tools are found)
d) Download the latest version of TWRP recovery from
http://www.teamw.in/devices/htconem9.html
Place the downloaded twrp-2.8.7.0-hima.img in your Android SDK Platform Tools Folder
e) Once you are 101% ready to begin the process start by connecting your device and launching the command window (hold shift, right click in window with all the required ADB/FASTBOOT aps and select "open command window here) once the black terminal window appears start by typing in
adb devices
if your phone appears in the list we can continue by typing:
adb reboot download
wait a few seconds for the screen to appear and type:
fastboot oem rebootRUU
your phone should now be in the RUU mode with a silver HTC logo, now type
(if you renamed the original file type its current name, by default it is as follows)
fastboot flash zip M9_3.35.401.12_FullStock_wipe.zip
f) you will most likely receive something like this towards the end after running the above command...
FAIL90 hboot pre-update! please flush image again immediate
FAILED (remote: FAIL90 hboot pre-update! please flush image again immediate)
For "hboot-preupdate" response, restart the same procedure for device...
just type the above command again and phone will flash the update again and hopefully it will take at least a minute or more to complete, hopefully there will be no more errors, just in case repeat the above command... Just in case you do see errors try looking them on Sneakyghost's thread found here
g) Once this is done and everything passed than we have successfully upgraded our firmware to Marshmallow... Since we selected the FULL STOCK WIPE option we need to flash TWRP once again (as it was wiped) and don't bother resetting or hoping for the phone to boot normally as it won’t...
(if you renamed the original file type its current name, by default it is as follows)
Type:
fastboot flash recovery twrp-2.8.7.0-hima.img
and once it’s done
adb reboot-bootloader
*if for any reason you need to reset your phone and gain access to the bootloader menu, download mode, recovery etc. you can always do this manually by holding vol up, vol down and power buttons at the same time for a few seconds to reset the device, to get into the bootloader, recovery, download mode etc. After the phone resets continue holding the vol down and power button until you reach the bootloader menu.
*if you type adb devices and you see multiple devices or emulators that prevent the commands from working I suggest running the following:
adb kill-server
adb devices
Now only your connected device should appear…
h) It is now time to enter our recently flashed recovery to finally install our latest ROM.
Enter the recovery manually or by typing
adb reboot recovery
From there you may select the wipe option (swipe to factory Reset) and proceed to the Install section, browse for your ROM file and select it.
i) Within Aroma installer select all your preferred options and begin to install, once the flashing completes your device should reboot and now you keep your fingers crossed and wait (will take several minutes so just be patient…. And DONE!!! You now have the latest Marshmallow firmware and ViperOneM9 ROM installed.
#Please note that I’m no expert when it comes to these matters, this guide is here to help anyone who is unsure what to do, I tried to write it up the best way possible (sorry that there are no fancy pictures) if there any errors or issues with my methods please feel free to correct them but so far they worked for me and hopefully will also work for you. (This guide will also help you flash other ROM's) If you need more help please feel free to ask, there is always someone here on xda who knows the answers
Excellent write up !!
Many thanks !!!....g
glad i could help
GODSPD said:
glad i could help
Click to expand...
Click to collapse
Very nice writeup. Just got an M9 for the wife. I've been around the block so I get everything, but I've been away from HTC since the One X...well, there's the N9 but it's a nexus. What are the RUU mode and Download mode. If I remember correctly there was only the bootloader to go to on the One X. If it's complicated is there somewhere I can read about the modes?
Can you write instructions for s-on and unlocked boatloader? Thanks.
Sent from my HTC One M9 using Tapatalk
Excellent write-up! For extra-completeness, could you please cover changing the mid in android-info and dealing with error 22 (stuff about headers). I'm still fighting that one...
Thanks for your time.
CrazyRom said:
Excellent write-up! For extra-completeness, could you please cover changing the mid in android-info and dealing with error 22 (stuff about headers). I'm still fighting that one...
Thanks for your time.
Click to expand...
Click to collapse
PM sent, hope it helps.
zrzhu said:
Can you write instructions for s-on and unlocked boatloader? Thanks.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Have you received the official Marshmallow OTA yet on your device? the S-OFF method is available for those who don't want to wait for official updates, I will gladly write up a S-ON method once more people receive the official update...
GODSPD said:
PM sent, hope it helps.
Click to expand...
Click to collapse
Also try the following as error 22 was not covered in the error handling section...
http://forum.xda-developers.com/showpost.php?p=59783531&postcount=3
Download 7zip, open the zip inside of the program, right click on the Android text file and open within. Change the mid to yours hit save. It will ask if you want to update the zip, hit yes. Then try and flash.
SneakyGhosts post explains this:
Error 22 is new to me too but the string is kind of self explanatory: every archive has a header where the archive-program finds info about what type of archive and what compression. If the error says anything about this header, the logical conclusion is either a corrupted, broken archive or an unsupported archive type.
I suspect the latter simply due to the fact that the zip was unpacked and repacked, which then easily creates an incompatible zip.
GODSPD said:
Have you received the official Marshmallow OTA yet on your device? the S-OFF method is available for those who don't want to wait for official updates, I will gladly write up a S-ON method once more people receive the official update...
Click to expand...
Click to collapse
No, I've att m9. I'm still I viperone 3.5. Why do we need to wait for the official update?
Sent from my HTC One M9 using Tapatalk
zrzhu said:
No, I've att m9. I'm still I viperone 3.5. Why do we need to wait for the official update?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
because you need the latest firmware in order to install 4.x.x and the only way to get the latest firmware is via the OTA or by flashing it with the s-off method.
GODSPD said:
because you need the latest firmware in order to install 4.x.x and the only way to get the latest firmware is via the OTA or by flashing it with the s-off method.
Click to expand...
Click to collapse
Thanks. Hopefully ATT will release Marshmallow soon then.
Hi guys i dont have anymore pc. Can i flash new firmware without pc? Plz help
Can you put here your all c:\android folder in .zip file? Of course you can't put here all venom rom zip, but only all your files in that folder
BLEK0TA said:
Can you put here your all c:\android folder in .zip file? Of course you can't put here all venom rom zip, but only all your files in that folder
Click to expand...
Click to collapse
which exact files are you after, the android sdk?
thanks bro!! nice collection!
zrzhu said:
Thanks. Hopefully ATT will release Marshmallow soon then.
Click to expand...
Click to collapse
I'm still kind of "fuzzy" on this whole firmware thing.... IF I don't want to wait (on ATT) and IF I go S-OFF, which firmware can I/should I use for Marshmallow?
Delete
HI, can you please tel me how long does the firmware flash take as mine has been at it for over 2 hours? Not sure if it is stuck?
I am on sprint. How do i get the new firmware? It isnt on the list. Thank you