Database Develop

How To: Get back to stock 2.1, stock recovery and S-ON for an RMA

The other day my phone's touchscreen developed a dead spot. Verizon was kind enough to send me a "Like-New" replacement and requested that I return the old phone. The only problem with that was I had hacked the hell out of it and didn't want them to see what I did and charge me.
I had rooted the phone, installed Clockwork Recovery, set S-OFF with Unrevoked Forever, updated to the latest radio and installed all kinds of different ROMs before finally settling on CM6. Now I had to find a way to install either stock 2.1 or stock 2.2 with the correct radio for either one, flash back the stock recovery, and finally set the phone back to S-ON. If you find yourself in a similar situation, you'll probably want to read this instead of spending 6 hours pulling your hair out, like I did. Here's what I finally came up with:
STEP 1: Get ADB Running.
Make sure you have ADB up and running. If you're rooted with a custom ROM and you don't have ADB running you have more problems than I can help you with. If you use a Mac, see Step 1A below to make things a little easier when using ADB.
Step 1A: (Mac Users Only) Make Your Life Easier.
Let's add the android SDK tools folder to your .bash_profile. What does this do, you ask? It makes it so that you can run any ADB commands without having to be in your SDK Tools directory. How do we do this?
Open a terminal window. Type
Code:
nano ~/.bash_profile
This will open a text editor in the terminal and create a new text file in your home directory called .bash_profile, which will be invisible in the Finder.
Enter the following:
Code:
PATH=$PATH:/Applications/Utilities/android-sdk-mac_86/tools
export PATH
!!IMPORTANT!! I have my "android-sdk-mac_86/tools" folder inside my "Utilities" folder, which is inside the "Applications" folder. If you have your android sdk folder somewhere else you will have to change the above text to reflect the proper path to your folder.
Hit ctrl-x. Not cmd-x, ctrl-x.
The editor will ask you if you want to save changes. Press "Y".
It will ask you what you want the file name to be. Just press enter, as we've already named it .bash_profile.
Quit and re-open terminal.
You can now use any command in the SDK tools folder from any directory.
STEP 2: Install Fastboot.
Make sure you have the HTC Fastboot tool installed. If you don't, you can get it here: http://developer.htc.com/adp.html
Download it for your particular operating system.
Another tip for Mac users: Once you download and unzip it, rename it from "fastboot-mac" to just "fastboot", then place it in your SDK Tools directory.
STEP 3: Downgrade To 2.1 With Old Radio.
We now need to downgrade our radio and get back to stock 2.1. The best way I found to do this was explained in this thread: http://forum.xda-developers.com/showthread.php?t=757927
Download the zip and follow the instructions.
Hat tip to Berzerker7 for the write-up, and aiccucs for putting together the zip file in that thread.
The next step will be a little bit of backtracking, but it's mostly painless, and it still seems to be the easiest way to do this.
STEP 4: Set NAND To S-ON.
We now need to set the NAND to S-ON. Problem is, in step 3 we flashed the stock recovery back onto the phone. Not a huge issue.
First, go to unrevoked.com and download unrevoked3. Run it. This will re-root the phone and install Clockwork recovery. Once this is done, go here: http://unrevoked.com/rootwiki/doku.php/public/forever and download the unrevoked-forever S-ON Tool.
Copy this file to your SD card and rename it "update.zip"
You can do that with adb like this:
Code:
adb push /path/to/unrevoked-forever-son.zip /sdcard/update.zip
Reboot into recovery and use Clockwork to apply the patch, which will set the NAND back to S-ON.
STEP 5: Get The Phone To Accept Stock Recovery With S-ON
This was the biggest problem that I ran into. The phone would regurgitate every zip I found which contained a stock recovery when the phone was set S-ON. I finally found a way around that.
First, download this PB31IMG.zip file: http://d01.megashares.com/index.php?d01=CHoQD3B
This IMG file was posted by Diego Mejia, on a youtube video he uploaded. Thanks to Diego, his work was very helpful in this process.
Here's the catch: in order to apply this PB31IMG.zip, we need to downgrade HBOOT or we'll get an error, due to the fact that we had set S-ON in the previous step.
Here is a link to a post on androidforums.com with an attached zip file called "revert.zip": http://androidforums.com/incredible-all-things-root/123816-how-revert-back-earlier-version-hboot.html
Credit is due to adrynalyne for coming up with this process and posting the files, I just tweaked his instructions a bit to make them work for me.
Once the "revert.zip" file has been downloaded, follow adrynalyne's instructions on what to do with the files. Reposted below:
Boot the phone into Clockwork Recovery.
Go to partitions, and mount data.
Type the following commands in a terminal window:
Code:
adb push flash_image /data
adb push mtd0.img /data
adb shell
chmod 777 /data/flash_image
cd /data
flash_image misc mtd0.img
exit
adb reboot oem-78
Watch for your phone to reboot to a silver HTC logo.
Then type:
Code:
fastboot devices
Verify your device shows up/responds/etc.
Click to expand...
Click to collapse
If the "fastboot" command works you should see an "H" followed by a string of random numbers and letters. So far, so good.
STEP 6: Reapply Stock 2.1 With Stock Recovery.
Once you've run the "fastboot" command successfully, go ahead and pull the battery. Leave the phone off. Go back to the PB31IMG.zip you downloaded in step 5, and copy it to the root of your SD card. Put the SD card back in the phone and boot it into recovery. If you've done all this correctly, the phone should recognize the PB31IMG.zip as valid and ask if you want to apply it. Do so. This will reflash the stock 2.1 ROM with the stock recovery while the phone is set S-ON. You can now send your phone back to Verizon.
STEP 7: Profit.
--B

Hey Mods, any chance of a sticky?
--B

There's a much easier/faster way to do this:
Just S-ON before you downgrade a first time, and then flash_image misc right away. The PB31IMG will take and you'll be at 2.1 with a single RUU flash.

Berzerker7 said:
There's a much easier/faster way to do this:
Just S-ON before you downgrade a first time, and then flash_image misc right away. The PB31IMG will take and you'll be at 2.1 with a single RUU flash.
Click to expand...
Click to collapse
Interesting. I couldn't get RUU to jive for some reason and didn't happen upon the bit about the flash_image until I'd already gone around in circles for several hours. Cool if the shortcut works, though! Where was your info at one o'clock this afternoon when I needed it?
--B

xraystyle said:
Interesting. I couldn't get RUU to jive for some reason and didn't happen upon the bit about the flash_image until I'd already gone around in circles for several hours. Cool if the shortcut works, though! Where was your info at one o'clock this afternoon when I needed it?
--B
Click to expand...
Click to collapse
Not reading your topic. lol

I found it easier, to just since your rooted already, just put it to S-on, then run the stock RUU for 2.2. and your done in two steps. no need for all the codes.... I just did it, got my refurb yesterday,...

Thanks for the informative post! This will help a lot of people in the future.

beginners guide for new members"NooBs"

i chose to start this thread as an educational and informative way of answering simple question so new questions arent repeatedly asked.
first off try to use the search window as much as possible before you post a question, chances aer your question has been asked before, so you will find the answer somewhere.when you do have to post a question be patient, the answer will come either in the form of an informative response or with a link to an informative response.
in every thread or be it for a rom ,a mod a theme etc. there are instructions. follow them to the letter and you shouldnt have any problem.
most importantly, be grateful to the devs or members which might assist you , at least say thank you and hit the thanks button, and donate if you can. these individuals work very hard at what they do here to provide you with the information and freedom you need to do what you want to do with your HEROC.
say thanks,,,its not that difficult.
Root your HTC HERO200 CDMA...
there are many different methods of rooting your device, it depends on your particular device.
they all work you simply have to find the one that works for you. for instance myself i use the regawmod one click method. (thanks regaw) when
i tried to use it on an associates device it didnt work...you have to find the method that works for your device.
youll find the files and programs you need to perform whatever procedure you choose to try on the developers page.
make sure you read the instruction completly before you begin. when you do begin follow the instruction to the letter and you shouldnt have any problem.once again, dont get piussed at the dev because it didnt work, its not that the procedure doesnt work, it just didnt work for you...simply search for another method and try again.and you will succeed.
i was going to post some of the methods but dont have permission from the devs to do so, so for now youll have to search for the precedures yourself. if or when i do get permission ill edit this thread or post the link in order to help yo on your way,,,ehhh for now itll be good practice for using the search window.
method 1.
hhttp://www.gadgetsdna.com/how-to-root-htc-hero-cdma-stock-android-2-1/3628/
The HTC Hero 2.1 exploit is based on the EVO rooting method. Rooting HTC Hero Android phone provides full access to its system files allowing you to modify the phone’s firmware and install third party apps, themes and custom ROMs. You can then spruce up your HTC Hero handset with number of third party applications.
How to Root Sprint’s 2.27.651.5 Release for CDMA Hero (Stock Android 2.1)
Note: If you already have the Android SDK and HTC Sync set up on your computer, skip to Step 4 now
Step 1: Download the Android SDK.
Step 2: Extract the Android SDK zip. Move the contents of the extracted zip to C:\
Your Android tools folder path should now be C:\android-sdk-windows\tools
Step 3: Download HTC Sync 2.0.33 here. Run the installer, and reboot your computer when it is finished. Skip to step 4 once rebooted.
Step 4: Download the hero-root.zip. This zip contains everything you need to root your Hero.
(md5: c6e5058ed14f71c68fb099e10be142fb)
Step 5: Extract the 3 files inside hero-root.zip to the C:\android-sdk-windows\tools folder on your computer.
Step 6: Make sure USB Debugging is ON (checked) on your Hero. Navigate to Settings > Applications > Development > and make sure it is checked
Step 7: Plug your phone into the computer via USB, Make sure that the connection type in the Notification Pull-Down Bar is “Charge Only”, not “Disk Drive” or else this won’t work. You may restart your comuter when prompted to do so.
Step 8: Open a Command Prompt window by clicking the Start button and typing cmd into the search box and pressing enter. Alternatively, navigate to Start Menu > All Programs > Accessories > Command Prompt
Step 9: You enter the commands followed by pressing ENTER, one code at a time.
1 cd C:\android-sdk-windows\tools
You should now see C:\android-sdk-windows\tools>
Now type
adb devices
You will now notice your HTC Hero phone’s serial number. If you get “device not found” error, you either need to make sure you the drivers were properly installed or make sure you enable USB debugging on your phone. Continue on once you get the proper phone serial output.
You will now push the files needed to gain root to your sdcard in your phone with these following commands one by one:
adb push unrevoked /sdcard
adb push recovery.img /sdcard
adb push boot-patched.zip /sdcard
Now we run the exploit. Be patient, this may take up to 40 seconds.
adb shell
sh /sdcard/unrevoked
You should now see output that says this:
UNREVOKED
============================================================ unrEVOked: root for HTC evo and hero (http://unrevoked.com)
Now, on your phone, go to your app tray, and you will see that the Superuser Permissions app is in it, which is only possible on rooted devices.
Open the Superuser Permissions app. You will see a blank screen.
In the Command Prompt on your computer, type:
A prompt will appear on your Hero asking you to give /system/bin/sh privileges. Click Allow.
Go back to your command prompt, and you should see
$ su su #
Now Type
flash_image recovery /sdcard/recovery.img
Flashing the recovery may take many seconds to complete. Wait until the # symbol returns to proceed.
You should now see
# flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
#
This means it was a successful flash.
Now type
reboot recovery
Your phone will now boot to the custom recovery image you just flashed. In the Recovery Menu on your phone, choose the option:
Flash zip from sdcard
Then Select
boot-patched.zip
and press the Home button to apply. Once Recovery says “Install from sdcard complete” select “Reboot system now” from the menu.
Voila!! You now have full root access on HTC Hero 2.1!
Thanks to the guys at xda-developers and gadgetsdna
or, you can try regaw's one click root method. you can find it here on Xda, just use the search window,,,it's easy
both of these methods have worked well for me in the past, im sure one of them WILL work for you
-----------------------------------------------------------------------------
Flashing a ROM (from clockworkMod)
this is the method i use and i "never" have any problems
download the ROM of your choosing and move to the root of your sdcard
follow the devs instruction for installation which should be something like this;
1. do a nandroid backup
2. reboot into recovery
3. wipe data
4. wipe cashe
5. choose advanced, wipe dalvik
***OPTIONAL***
6. choose mounts and storage
7. format system
8. format data
9. formatcashe
10. go back. and choose install zip from sd card
11. choose, choose zip from sd card
12. find the rom you want to flash and choose yes
13. when its through flashing choose install zip from sd card
14. find the gapps you want to flash and choose yes
when its through with the flash the screen will return to the main menu and choose reboot system
the first boot will take a little longer than usual this is normal. setup your google s#@ts as usual and enjoy your new ROM.
follow these instructions and you shouldnt have any problems, if you do, go back to the thread you downloaded from post a reply to report it to the dev so they know theres a problem and they can determine if its a problem with the rom, a problem with the way you flashed or a problem with your system.
15. "ONCE AGAIN" most importantly, be grateful to the devs, at least say thank you and hit the thanks button, and donate if you can.
these individuals work very hard at what they do here to provide you with the information you need to do what you want to do with your HEROC.
say thanks,,,its not that difficult.
-----------------------------------------------------------------------------
themeing your new ROM
1. make sure the theme you choose is compatable with the rom you have flashed
2. since alot of the themes have a different procedure for installation,"READ AND FOLLOW THE DEVS INSTRUCTIONS"(sorry for the caps)
they are there for a reason.
-----------------------------------------------------------------------------
boot animations
1. Put the zip file in your tools folder from the android-sdk-windows
2. Load up Command Prompt (cmd) and go to your tools directory inside the android-sdk-windows folder
3. Load up your phone into recovery and mount /system
4. Type in command prompt
adb remount
adb push bootanimation.zip /system/media
adb reboot
or (compliments of user7618)
Boot animations are easier to change by sliding the .zip into /system/media or /data/local. That way, there is no need for adb commands, just a file explorer like root explorer. Make sure that it is named bootanimation.zip.
-----------------------------------------------------------------------------
Flashing a different recovery image
cd C:\android-sdk-windows\tools...got
cd C:\android-sdk-windows\tools>adb devices...got
(recognized phone)>>>>>
cd C:\android-sdk-windows\tools>adb shell
#flash_recovery image /sdcard/recovery-clockwork-4.0.0.2-heroc-20110611.img (enter)
mtd: successfully bla bla bla
#reboot....
or,,,
[edit] Method I
Flash recovery using: ADB
NOTE: This method will work while you are booting into the current recovery on the phone.
1.Download the ClockworkMod Recovery: HeroC Download Optimus V Download.
2.Copy the recovery.img to root of the SD card.
3.Boot the phone into recovery.
4.Open command prompt, cd to the Android SDK directory & type the following commands:
adb shell
mount /sdcard
flash_image recovery /sdcard/"name of recovery".img
reboot recovery
5.Your phone should now reboot into the ClockworkMod Recovery (orange text for 3.0+).
[edit] Method II
Flash recovery using: RomManager
1.Download the ClockworkMod Recovery: HeroC Download Optimus V Download.
2.On the SD card, go to /clockworkmod/download/koush.tandtgaming.com/recoveries.
3.Rename the old image there named recovery-clockwork-2.5.0.1-heroc.img to recovery-clockwork-2.5.0.1-xxx.img.
4.Move, then rename, the recovery.img you downloaded to recovery-clockwork-2.5.0.1-heroc.img.
5.Open RomManager and press Flash ClockworkMod Recovery and reboot the phone to recovery, you should see the orange text.
[edit] Method III
Flash recovery using: Terminal Emulator Note: Requires s-off, otherwise you'll recieve "out of memory" errors.
1.Download the ClockworkMod Recovery: HeroC Download Optimus V Download.
2.Move recovery.img to root of the SD card.
3.Open the Terminal Emulator on the phone & type the following commands:
4.:
su
flash_image recovery /sdcard/"name of recovery".img
reboot recovery
5.The phone should now reboot into the ClockworkMod Recovery (orange text for 3.0+).
[edit] Method IV
Flash recovery using: H-Boot/S-Off Only HeroC Only
See S-Off for CDMA Hero if you are unsure what S-OFF is.
1.Download HERCIMG.zip
Newest Download: (version 3.0.5) HERCIMG.zip <--Updated 01212011
md5: 6dcd265a51cc7090824d7f9f889b370b
Alternate Download: (version 2.5.0.7) HERCIMG_clockwork-2.5.0.7 <--Updated 02-07-2011
md5: 0a367eb1d4445c72f8022769f7edc9dd
2.Move HERCIMG.zip to root of the SD card. Make sure the file is named HERCIMG.zip or H-Boot will not recognize it.
3.Power off the phone.
4.Hold the Volume Down & Power' button until the phone boots into the bootloader.
5.Wait for bootloader to scan and find HERCIMG.zip.
6.Press action to install.
7.The phone should now reboot into the ClockworkMod Recovery (orange text for 3.0+).
Retrieved from "http://romrepo.info/wiki/index.php?title=Flash_the_ClockworkMod_Recovery"
-----------------------------------------------------------------------------
Change sprint insignia (ON AOSP) to whatever you want
1. Download eri.zip
2. Unzip the file to wherever you please.
3. Right click on eri.xml and choose "Open with Notepad"
4. Once you open the file you will see "Sprint" in the 5th line.
5. Delete Sprint and place whatever you would like in it's place. I believe you have up to 16 spaces to work with if need be.
6. Save the file with an .xml extension. Important: Make sure it is eri.xml and not eri.xml.txt. This will cause issues.
7. Place the eri.xml in your /androidsdk/tools directory.
8. Pull up your Command Promt/Terminal/Etc
9. CD to your /androidsdk/tools directory and:
adb remount
adb push eri.xml /data/eri.xml
adb reboot
or, (thanks to user 7618 )
I threw together a simple app to change the Carrier Name in the status bar/lockscreen to whatever you want since my alot of people seem to ask how to change it. Feel free to use it. Tested on Incredible and Eris. Dev's feel free to thow it your roms if you want. No ads and free just a simple tool to change the text. Thanks to the great Eris community.
Currently only works for AOSP roms such as cyanogenmod.
V1.3
While trouble shooting some radio issues on a rom I realized there's no need to reboot the phone to apply the new carrier name. I only needed to cycle the radio so I changed the app to toggle airplane mode on and then back off after you input your text so the change should take place immediately. This should make it a little easier to test and try different things or just change it more often.
I also added some shortcut buttons at the bottom to quickly add the text for the ", < and > signs so you don't have to type it all out. Only tested this with cm7 but should still work with any rom's it worked with before. Again thanks to Psiphon for pointing these symbol fixes out.
http://www.multiupload.com/RO6RZUUL16
V1.2
Fix for phones that don't already have an eri.xml file there
Added version number to bottom of screen so people can be sure what version they are running.
http://www.androidphiles.com/files/g.../ccname1.2.apk
V1.1
Fixed force closes when using symbols.
You can now use symbols except for double quotes. Apostrophe (single quote) seems to work fine.
Some usefull info if you want to use quotes....
Originally Posted by Psiphon
You can use special characters like the quotation marks and greater/less than signs by using entity references (either using an entity name or number):
" (quotation mark) use "
< (less than sign) use either < or <
> (greater than sign) use either > or >
I hope this helps!
Added Toast popup to let you know the name has been set.
If reboot button does not reboot phone just reboot the phone manually
http://www.androidphiles.com/files/g.../ccname1.1.apk
This app does one thing. It takes the input text you type and creates and eri.xml file and puts it in data/ folder on your phone. Then you can reboot for change to take effect. You can uninstall the app after you change it if you want or you can leave it on there(it's pretty small) in case you like to switch it every now and then. If you flash a new rom you will have to rerun the app.
-----------------------------------------------------------------------------
hopefully there will be more info in the future to add to this thread that will make things easier for everyone all around.
-----------------------------------------------------------------------------
***TO ALL DEVS AND OTHER MEMBERS*** i myself cant thank you enough for the help and advice ive recieved in the past, if you might hace any information you feel would be helpful to this thread please feel free to PM it to me and ill see that i edit this post with your procedures. and ofcourse your names will be added to a list of thanks at the bottom of the post,,,Thanks again,
THANX FOR THEIR HELP TO ME IN THE PAST;
flipz
coffeehandle
MattCrystal
laie1472
user7618
PMGRANDS
kushdeck
bierce22
conap
psiphon
kifno(aspentree)
-----------------------------------------------------------------------------
all of the information i have provided here has been compiled from Devs and other membes in order to assist new memberslike myself , and to help the devs and senior members so they dont have to keep answering the same questions again and again.
*** i f you want to thank someone, thank them for passing on their knowlege to me as im passing it on to you***
enjoy,,,

please dont double post

Nice beginners guide.
-----
3vo. That is all that needs be said.

Nice beginners guide.
Also, an easier way to change the carrier banner:
http://forum.xda-developers.com/showthread.php?t=960099
Instead of all that goofy crap with files and whatnot.
Boot animations are easier to change by sliding the .zip into /system/media or /data/local. That way, there is no need for adb commands, just a file explorer like root explorer. Make sure that it is named bootanimation.zip.
-----
3vo. That is all that needs be said.

Thanks man ill keerp adding, i really hope this helps some folks

Kudos. Good guide.
#Root/Hack-Mod_Always*

Also we dont talk about "he who must not be named" around here so you might want to take that out of the credits.
lai and user know who im talking about lol.

Uhhhhh,,,Ooops. My bad....sorry bout that guys.

ha lol i was just kidding but seriously that guy went bannanas and had a severe case of schizophrenia lmao.

lol, i hear ya man, i feel credits given where credits due, but on the other hand,,,,aw well you know what i was gonna say

Yeah, dude was crackers, but if he helped you, then he helped you. I'd leave him in there, personally.
-----
3vo. That is all that needs be said.

Yup agreed. A if he helped he helped that's just how it is. Like the guy or not.
#Root/Hack-Mod_Always*

cool guys i do feel the same way, but dont wanna stir any bees nests either, ill put it back in but we'll just overlook it. thanx for understanding

Tools to take OTA for Sprint M8/Get Back to Stock

FOR SPRINT M8 NON-H/K MODELS ONLY​
Well everyone I'm here to bring you a little tool set i use to take official OTAs.I am not a dev nor do I take credit for the work. This is mainly just a collection of things I used to get OFFICIAL OTA updates. I've used this on 2 Sprint m8's with STOCK Hboots so I am sure this will work. Please feel free to share this with others JUST GIVE CREDIT WHERE IT IS DUE.
To start off there are some requirements...
S-OFF is needed
STOCK HBOOT
HTC One M8 (Sprint non-Harmon Kardon)
UNLOCKED Bootloader (If you are LOCKED and rooted PLEASE use UNLOCK Bootloader method included in zip. DO NOT use HTCDEV to unlock... Your internal storage will be wiped if you do. YOU HAVE BEEN WARNED
MAKE SURE TO UNLOCK BOOTLOADER before doing any of this (instructions are included in zip)
1. Copy the stock nand to backup folder in twrp
2. Make a backup of your setup
3. Restore the stock nand provided
4. Flash stock recovery provided
5. Boot up and do all otas up to latest
6. Flash custom recovery
7. Restore your backup
8. Flash modified firmware
9. Lock bootloader
10. Flash asdp for hk mod.zip in ruu mode (same as flashing FIRMWARE) if audio is not working in htc music
Locking-Unlocking & Remove Tampered flag
***NEED TO BE S-OFF!!***
TO LOCK BOOTLOADER
1. Phone on with adb debugging enabled to confirm this open cmd prompt type adb devices should show device serial number
2.Type adb shell
3.Type su to get # prompt
4. Copy paste exactly as is
Code:
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
5.Type exit you may need to enter that command 2x to get out of adb shell
6.Type adb reboot bootloader You should be ***LOCKED***
TO UNLOCK BOOTLOADER
1. Phone on with adb debugging enabled to confirm this open cmd prompt type adb devices should show device serial number
2.Type adb shell
3.Type su to get # prompt
4. Copy paste exactly as is
Code:
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
5.Type exit you may need to enter that command 2x to get out of adb shell
6.Type adb reboot bootloader You should be ***UNLOCKED***
TO REMOVE ***TAMPERED*** text
1. Phone on with adb debugging enabled to confirm this open cmd prompt type adb devices should show device serial number
2.Type adb shell
3.Type su to get # prompt
4. Copy paste exactly as is
Code:
echo -ne '\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564
5.Type exit you may need to enter that command 2x to get out of adb shell
6.Type adb reboot bootloader You should not see ***TAMPERED***
Flashing Firmware
IN HBOOT MODE
1. Label the file to exactly 0P6BIMG.zip
2. Put zip in root of external SD card
3. Boot into HBOOT to flash (bootloader should detect zip automatically and prompt you to flash)
IN FASTBOOT MODE
1. Boot device into FASTBOOT mode (device should show FASTBOOT USB)
2. Put the firmware file to be flashed in the folder with fastboot.
3. Open a command prompt from the folder where fastboot is located.
4. Run the following commands:
fastboot oem rebootRUU (this will reboot the device into RUU mode in preparation for zip flashing)
fastboot flash zip 0P6BIMG_M8WHL_x.xx.xxx.x_firmware.zip (the name of the zip should match the name of the file you're flashing)
5. Once complete, you can fastboot reboot or fastboot reboot-bootloader depending on what you want to do next. If you choose bootloader, you can confirm that your radio is now updated to the one from the file you flashed
Links needed ...
For Locking and Unlocking bootloader (ONLY WORKS WITH ROOTED ROM AND S-OFF!!)
For Removing Tampered Flag (ONLY WORKS WITH ROOTED ROM AND S-OFF!!)
For Modified Firmware
I'd like to give thanks to the people that have made this possible
if i forget someone I'm sorry send me a pm I'll add you to the list
Team420 for taking me in showing me the basics
BADSEED for allowing me to break so many test roms lol
BD619 for hooking me up with adb files
scotty1223 for making those awesome guides
Captain_Throwback for providing the collection of firmware ... Oh yeah and the TWRP recovery
TEAMWIN for making TWRP in the 1st place
HTC for making such an awesome phone
DISCLAIMER: I AM IN NO WAY HELD LIABLE FOR DAMAGES MADE TO YOUR PHONE OR IF YOUR DEVICE TRANSFORMS INTO A DECEPTICON CAUSING WORLD DESTRUCTION...YOU ARE FOLLOWING AND FLASHING THIS AT YOUR OWN RISK

DOWNLOADS​
Main Link on Mega HERE
Mirror Link on AFH HERE

And this as well

Hi,
Added to FAQ Guide Q15

Nice work Miggs:thumbup:
Sent from my HTC M8

Great work Bro, very helpful. Thank you

Just one thought on your thread title. You might change it to "How to Return to Stock" since most of those steps aren't needed to take a OTA. Very useful for those who need to go back to a stock device though.
Sent from my HTC M8

Magnum_Enforcer said:
Just one thought on your thread title. You might change it to "How to Return to Stock" since most of those steps aren't needed to take a OTA. Very useful for those who need to go back to a stock device though.
Sent from my HTC M8
Click to expand...
Click to collapse
GOOD CATCH!! THANKS ... That was actually how this idea came about lol

Good work Miggsr!

Need stock apps to take OTA
I'm in need of a list of the stock apps so I can figure out what ones I'm missing so I can take the OTA. Also has someone made a zip of the stock apps. Any help would be great.

Piroman024 said:
I'm in need of a list of the stock apps so I can figure out what ones I'm missing so I can take the OTA. Also has someone made a zip of the stock apps. Any help would be great.
Click to expand...
Click to collapse
Why not just keep a backup of the latest stock rom on your sdcard?

BD619 said:
Why not just keep a backup of the latest stock rom on your sdcard?
Click to expand...
Click to collapse
Or look in the first post of this thread for stock backups:
http://forum.xda-developers.com/showthread.php?t=2736048
Sent from my HTC M8

Piroman024 said:
I'm in need of a list of the stock apps so I can figure out what ones I'm missing so I can take the OTA. Also has someone made a zip of the stock apps. Any help would be great.
Click to expand...
Click to collapse
in my zip i have included a STOCK backup made with TWRP that is also included in the zip it has ALL stock apps that you may be looking for to make things easier just copy that folder to your TWRP backup folder whether its on your internal sd or external sd restore that and boot up

Tring to upgrade "dirty"
I do keep a copy of the stock rom for when stuff hits the fan. I also have a backup i made before I went S-off. I deleted a few of the system apps that were bugging me before I learned that OTA also checks apps.
I'm trying to get the OTA without wiping my phone and all the setup time I have so far spent on it.
I just try to install the OTA again this time i checked the log. I get "/system/app/Plusone.apk" has unexpected contents. I guessing this is caused from my removing apps. I'm thinking i can use this to find what the installer thinks is missing.
My last question, is there a way to extract .apk and .odex files from the ruu?

Piroman024 said:
I do keep a copy of the stock rom for when stuff hits the fan. I also have a backup i made before I went S-off. I deleted a few of the system apps that were bugging me before I learned that OTA also checks apps.
I'm trying to get the OTA without wiping my phone and all the setup time I have so far spent on it.
I just try to install the OTA again this time i checked the log. I get "/system/app/Plusone.apk" has unexpected contents. I guessing this is caused from my removing apps. I'm thinking i can use this to find what the installer thinks is missing.
My last question, is there a way to extract .apk and .odex files from the ruu?
Click to expand...
Click to collapse
okay with the first half of what you said... i have not had an ota check for apps... when removing google plus you probably left a second apk that works with it hence your error message. if you are looking to be able to take an official ota you should NOT be rooted. honesty if you meet ALL REQUIREMENTS i listed then just follow the guide you should be fine. the backup i have there is based on initial rom that came with the device. so you will have to do 3 ota updates to be exact. i made it that way out of personal preference. now for the second half of your post ... as i mentioned i am not a dev unfortunately i can not answer that question for you... slightly above my pay grade. not to put you on the spot either i'd like to keep thread on topic in OP.

so Harmon Kardon edition can not be unroot?

hhhstonehhh said:
so Harmon Kardon edition can not be unroot?
Click to expand...
Click to collapse
Sure it can...same steps just use HK files

BD619 said:
Sure it can...same steps just use HK files
Click to expand...
Click to collapse
I could not have said it any better lol

Great Tut Miggs !!!

cbrown245 said:
Great Tut Miggs !!!
Click to expand...
Click to collapse
thanks CB i just making things easier for others

[Tutorial] How to install Android Loliipop+Root

Note:​I'm going to assume you have the Fastboot and ADB Drivers installed and the boot loader is unlocked! ​
Why is this here?
This thread is made to help new users install the developers preview through what I think is the fastest way and safest way too through the command prompt on Windows.
Responsibility!
If your device becomes bricked, makes toast for you, and anything else I did not mention its simply not my fault since you took it upon your self to do this method.​
Credits!​​Thanks Google for this lovely Operating System. Thank you Chain Fire for providing this method to root Android Lollipop and for your app and boot.img too! Thanks to LG for manufacturing this great device to use and enjoy stock Android. Finally, big thanks to TWRP for providing us with this recovery!​​​​​
The Steps!​​​​​Step 1: Download the Lollipop preview HERE, extract it and open the folder with all the image files along with the radio and bootloader image too.
Step 2: Drop all the images to your folder that contains the ADB and Fastboot files
Step 3: Open the folder that contains the ADB and Fastboot files
Step 4: Hold the shift key and right click and click "Open command window here"
Caution! Make sure you back up everything before you begin the process if not its not my fault you forgot to back up.
Step 5: Make sure your device is in fastboot and connected. We are going to replace the boot loader for a newer one. Please make sure the boot loader image name first before we began because i'm just going to use boot loader as a example the real file name will be different. Type the command shown below.
Code:
fastboot flash bootloader bootloader.img
Step 6: Now we are going to flash the Radio as also stated above be sure to check the image name before we flash.
Code:
fastboot flash radio radio.img
Step 7: Now we are going to flash userdata. This part you don't have to worry about the file name you can just copy and paste the command but, I would double check.
Code:
fastboot flash userdata userdata.img
Step 8: Now going to flash boot or the kernel just as step 8 and here from out I will let you know when you have to worry about the file name again.
Code:
fastboot flash boot boot.img
Step 9: Now were flashing the system files.
Code:
fastboot flash system system.img
Step 10: Now were flashing the a custom recovery (twrp for this example) so we can install the SuperSU files later. You can get the recovery image HERE and rename it "Trecovery" and place it to the same folder. After flashing it go to the recovery and from there reboot it.
Code:
fastboot flash recovery Trecovey.img
Yay! We got Android Lollipop now we have to root it.​​​​​Step 1: Let Andriod Lollipop boot up and go download SuperSu on your device by going to Chainfire SuperSU thread and click on his installable zip link and download SuperSU 2.14 or above. On your computer download his modified boot image HERE and rename it Rboot.img and move it your folder where the ADB and Fastboot files are.
Step 2: On your computer go to fastboot again on your phone and type the code in below.
Code:
fastboot flash boot Rboot.img
Step 3: Go to recovery and install the SuperSU zip as usual, reboot, and that's it. Enjoy!

reserved

Trecovery.img

Thanks for your work. Unfortunately, we already have a sticky thread on flashing images and rooting: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
The method to flash and root lollipop is no different than any other version.
Because we don't want multiple threads with the some information I will close this thread
Thanks.

axon7tool: Flash and backup boot/recovery using EDL mode

Note: This is an inherently dangerous tool. I have made every effort to make it as safe as possible. But there is always a risk of bricking your device. You assume all responsibility for the consequences. Proceed with caution.
Warning: To avoid bricking your device, NEVER write both boot and recovery in one session. ALWAYS write one partition, test, then write the other. This is why the tool will only write one partition at a time.
Warning: There are versions of TWRP for the Axon 7 that are known to erase your IMEI when doing a restore. Do NOT do a TWRP restore unless your are SURE that you have a good version of TWRP!
This tool will allow you to:
Backup your boot and recovery partitions.
Flash a boot or recovery image (including the signed TWRP image).
See following posts for operating system specific setup instructions.
Once your setup is complete, enter EDL mode:
1. Power off phone.
2. Hold both volume buttons.
3. Plug phone into computer.
4. For G models, you must "adb reboot edl" (see other threads).
Usage:
axon7tool <mode> <partition(s)>
Note: The tool name will vary depending on your operating system.
<mode> is -r for read, -w for write.
For read mode, <partition> is one or more of gpt, boot, recovery. Files will be created as <partition>-backup.bin
For write mode, <partition> is boot or recovery. File will be read from <partition>.bin
Examples:
To backup everything on Linux:
./axon7tool-1.5-linux -r gpt boot recovery
To write recovery on Win64:
Place file as recovery.bin
axon7tool-1.5-win64 -w recovery
Links to axon7tool:
axon7tool-1.5-linux (main)
axon7tool-1.5-linux (alternate)
axon7tool-1.5-win64.exe (main)
axon7tool-1.5-win64.exe (alternate)
Link to signed TWRP removed.
FAQ:
Q: Can you provide a signed boot image with root?
A: No. I do not have the ZTE signing key, and tenfar's images are not current.
Q: Can I have the source code for the tool?
A: No.
Q: Can you provide the programmer?
A: No.
Q: Do you accept donations?
A: No, all work is provided freely for community use.

Setup instructions for Linux:
1. Ensure your login user is in the "plugdev" group.
$ id
You should see plugdev in the list. If not, add yourself to the group and logout/login to take effect.
2. Ensure your udev rules are setup.
Create a file eg. /etc/udev/rules.d/qcom.rules that contains:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", GROUP="plugdev"
3. All done!

Setup instructions for Win64:
1. Download zadig from http://zadig.akeo.ie/
2. Put device in EDL mode.
3. Run zadig. Select the WinUSB driver. If you have installed the Qualcomm EDL driver, you may need to tick "Edit" and find the device in the list.
4. All done!

Reserved for Mac instructions.

Questions:
1) Does the backup of boot and recovery partitions work like backing up through TWRP (if the recovery is already flashed to TWRP)
2) The signed TWRP image is by... ZTE?

kgptzac said:
Questions:
1) Does the backup of boot and recovery partitions work like backing up through TWRP (if the recovery is already flashed to TWRP)
2) The signed TWRP image is by... ZTE?
Click to expand...
Click to collapse
1- No this doesn't work like backing up with TWRP, This tool is more powerful than Custom Recovery (TWRP), and you should be very careful on how to use it.
Like @tennear mention about try first by using -r (read) then just flash the sign TWRP.
I personally recommend just flash TWRP and DON'T mess with Boot image.
2- the Sign TWRP is not provided by ZTE, ZTE will NEVER release a Custom Recovery for us users.

kgptzac said:
Questions:
1) Does the backup of boot and recovery partitions work like backing up through TWRP (if the recovery is already flashed to TWRP)
2) The signed TWRP image is by... ZTE?
Click to expand...
Click to collapse
1. The tool writes the raw partitions to your PC. Whatever you have in the partition is written out, whether it is stock recovery or TWRP or whatever.
2. The signed TWRP image is copied from the zip that tenfar provided in his post. I did not create it, and I cannot create signed images.

Forgive me my noobiness, but here’s a step-by-step-instruction list. Am I thinking right? I want to minimise the risk when I try your tool tomorrow.
Step 1: Enable Developer options in phone by tapping the build number
Step 2: Enable OEM Unlock in phone (is this needed?)
Step 3: Enable debugging (for adb)
Step 4: Connect phone to PC
Step 5: Download Zadig
Step 6: Install Zadig
Step 7: Open command in the folder in which you downloaded adb.exe (and the rest of the files that come with it) (Richt click while holding shift to get the option to open CMD in a folder)
Step 8: Enter the command “Adb Devices” to reassure your device is detected
Step 9: Enter the command “Adb reboot edl” to reboot the phone to EDL mode
Step 10: After phone has rebooted to EDL mode, run Zadig, select WInUSB driver and install it for your device
Step 11: Rename “axon7tool-1.5-win64.exe” to “axon7tool.exe”
Step 12: Download “axon7-2017u-twrp-signed.img” to the folder where axon7tool.exe is located
Step 13: Open command in the folder in which you have downloaded axon7tool-1.5-win64.exe (renamed to axon7tool.exe)
Step 14: Enter command “axon7tool -r gpt”.
Step 15: Enter command “axon7tool -r boot”
Step 16: Enter command “axon7tool -r recovery”
Step 17: Verify if the tool has created “gpt-backup.bin”, “boot-backup.bin”, “recovery-backup.bin”.
Step 18 (unsure): rename “axon7-2017u-twrp-signed.img” to “recovery.bin” ?
Step 19: enter “axon7tool -w recovery recovery.bin
Step 20: Wait for the command to finish
Step 21: Place the .zip file for Z.A.D. Mix7 or CM13 on your SD card via your PC or Axon 7. Also download Gapps.zip of your choice and place on SD card.
Step 22: Boot your Axon 7 to TWRP Recovery by holding the power button simultaneously with volume down (or is it volume up?)
Step 23: Perform a full wipe of Dalvik, Cache and Data in TWRP
Step 24: Flash the .zip of your custom ROM of choice in TWRP
Step 25: Flash the .zip of your Google Apps of choice in TWRP
Step 26: Perform a full wipe of Dalvik, Cache and Data in TWRP
Step 27: Reboot your phone, enjoy the custom ROM of your choice.
Is this the correct procedure?
I’m a bit unsure of step 18. Am I doing it right? Or do you need to unzip that .img somehow to find a recovery.bin file? Or do you need to get that file from somewhere else? Or do you need to rename “axon7-2017u-twrp-signed.zip” to “recovery.img”?
For Z.A.D. MIX7, I suppose you still need to flash a SuperSU version seperately? I heard in CM it's baked-in.
Thanks for the help.
Jan

@Controllerboy close, but not quite. I'll attempt to provide detailed feedback on your step by step list tomorrow. Time for sleep now.

Controllerboy said:
Step 1: Enable Developer options in phone by tapping the build number
Step 2: Enable OEM Unlock in phone (is this needed?)
Step 3: Enable debugging (for adb)
Click to expand...
Click to collapse
None of these steps should be necessary.
Controllerboy said:
Step 4: Connect phone to PC
Step 5: Download Zadig
Step 6: Install Zadig
Click to expand...
Click to collapse
I believe you just run zadig, I don't remember an installer.
Controllerboy said:
Step 7: Open command in the folder in which you downloaded adb.exe (and the rest of the files that come with it) (Richt click while holding shift to get the option to open CMD in a folder)
Step 8: Enter the command “Adb Devices” to reassure your device is detected
Step 9: Enter the command “Adb reboot edl” to reboot the phone to EDL mode
Step 10: After phone has rebooted to EDL mode, run Zadig, select WInUSB driver and install it for your device
Step 11: Rename “axon7tool-1.5-win64.exe” to “axon7tool.exe”
Click to expand...
Click to collapse
Renaming the tool is optional.
Controllerboy said:
Step 12: Download “axon7-2017u-twrp-signed.img” to the folder where axon7tool.exe is located
Step 13: Open command in the folder in which you have downloaded axon7tool-1.5-win64.exe (renamed to axon7tool.exe)
Step 14: Enter command “axon7tool -r gpt”.
Step 15: Enter command “axon7tool -r boot”
Step 16: Enter command “axon7tool -r recovery”
Click to expand...
Click to collapse
The tool is "one shot". You can read any combination of gpt, boot, and recovery in one session, then the tool will restart the phone.
Controllerboy said:
Step 17: Verify if the tool has created “gpt-backup.bin”, “boot-backup.bin”, “recovery-backup.bin”.
Step 18 (unsure): rename “axon7-2017u-twrp-signed.img” to “recovery.bin” ?
Click to expand...
Click to collapse
Yes, this is correct.
Controllerboy said:
Step 19: enter “axon7tool -w recovery recovery.bin
Step 20: Wait for the command to finish
Click to expand...
Click to collapse
Yes, this is correct. Writing boot or recovery takes about 30 seconds. Then the tool will reboot your phone. Be sure to hold the Vol+Up button to reboot into recovery.
Controllerboy said:
Step 21: Place the .zip file for Z.A.D. Mix7 or CM13 on your SD card via your PC or Axon 7. Also download Gapps.zip of your choice and place on SD card.
Step 22: Boot your Axon 7 to TWRP Recovery by holding the power button simultaneously with volume down (or is it volume up?)
Step 23: Perform a full wipe of Dalvik, Cache and Data in TWRP
Step 24: Flash the .zip of your custom ROM of choice in TWRP
Step 25: Flash the .zip of your Google Apps of choice in TWRP
Step 26: Perform a full wipe of Dalvik, Cache and Data in TWRP
Step 27: Reboot your phone, enjoy the custom ROM of your choice.
Click to expand...
Click to collapse
Everything past step 20 is up to you.
Controllerboy said:
Is this the correct procedure?
I’m a bit unsure of step 18. Am I doing it right? Or do you need to unzip that .img somehow to find a recovery.bin file? Or do you need to get that file from somewhere else? Or do you need to rename “axon7-2017u-twrp-signed.zip” to “recovery.img”?
For Z.A.D. MIX7, I suppose you still need to flash a SuperSU version seperately? I heard in CM it's baked-in.
Thanks for the help.
Jan
Click to expand...
Click to collapse
You cannot unzip an img file.
The TWRP image provided is just as tenfar provided for 2017u users. You only need to rename it to recovery.img for using the tool.
If someone has the 2017g TWRP file, I can upload and link it. The links in the tenfar post have been removed.

Folks who are able to use this new tool/method successfully, please report back with your variant. I can't test this myself, so I'm relying on some verification before I update the newbie guide to point here instead of tenfar's thread (which is outdated and no longer updated as tenfar is now inactive).

tennear said:
<-- SNIP -->
If someone has the 2017g TWRP file, I can upload and link it. The links in the tenfar post have been removed.
Click to expand...
Click to collapse
I found this on the 65th page of Tenfar's thread (http://forum.xda-developers.com/showpost.php?p=69215285&postcount=642)
khaino said:
Step 1: Download the zip file and extract to your local disk. a2017 for Chinese model,and a2017u for US model,a2017g for HK & EU model
a2017u :B20_blunlockedhttp://d-h.st/KaaQ
a2017u B20 http://d-h.st/LqR5 (modified from @rczrider�s backup real stock b20 boot.img)
a2017u B27 http://d-h.st/kRgq
a2017 B06:http://d-h.st/ztXw
a2017 B07:http://d-h.st/VVlf
a2017 B08: http://d-h.st/bT6r
a2017 B09:http://d-h.st/sBjo
a2017 B10:http://d-h.st/cBOE(wifi not working) http://d-h.st/aceq (from official update.zip)
a2017g B02 :http://d-h.st/aPiC
a2017g B03:http://d-h.st/r3Z4
TWRP recovery 3.0.2-2 : http://d-h.st/dgWW
latest tools:http://d-h.st/Ienb with dump function
Click to expand...
Click to collapse
So I just use the file from http://d-h.st/r3Z4 (axon7root-a2017g-b03.zip), unzip and rename the .img file to recovery.img?
The issue here is that the hosting used is so crappy I can't even download the file...

Controllerboy said:
So I just use the file from http://d-h.st/r3Z4 (axon7root-a2017g-b03.zip), unzip and rename the .img file to recovery.img?
The issue here is that the hosting used is so crappy I can't even download the file...
Click to expand...
Click to collapse
That is correct.
d-h.st seems to be down for the past few days. I guess it will come back at some point, and you can download the zip file to extract the recovery image. Or maybe someone else has a copy of it...

@tennear
As far as u know TWRP is the same for every A7, sign or not.

DrakenFX said:
@tennear
As far as u know TWRP is the same for every A7, sign or not.
Click to expand...
Click to collapse
Unpacking the TWRP image for A2017U, it says:
ro.product.model=A2017U
So this recovery seems to be specific to A2017U.
But unpacking the TWRP image for A2017 (China), it says:
ro.product.model=ZTE A2017U
Hmm, different but still A2017U.
I don't have the TWRP image for A2017G (yet), so I can't tell what it says. But given the above, and that the G and U models are almost identical, I am thinking the A2017U image will run on all devices.

tennear said:
Reserved for Mac instructions.
Click to expand...
Click to collapse
So can the Linux tool be used on Mac?

nuserame said:
So can the Linux tool be used on Mac?
Click to expand...
Click to collapse
No. I have not built the tool on Mac yet. I will try to do that soon.

I wouldnt say I was a newbie but how do you get the file to run. Even with Antivrus off, the computer just wont run it.
Thank you for the time and support.

The .exe file isn't meant to be ran on it's own. Double-clicking it won't do a thing. You need to use cmd (command) to execute commands to the file. If you look at my post on the first page of this thread, you'll get an idea of how the process works. But please don't follow my post as of now, since it's not detailed nor 100% correct yet.
It's my intention to try my luck tomorrow and I'll post a detailed and 100% correct step-by-step-process.

Excuse me for my ignorance, but how does this tool differ from tenfars tool? Beside not being able to write two partitions at the same time that is.
TIA,
Cheerz,
/Cacti