Database Info

[GUIDE] Rooting and flashing your patched Hero. (Windows) [Updated: 12/19]

Constructive criticism is welcome.
This is my first guide and it's quite late here so I'm going to go through this lightly first, and more in detail later.
Note: I am NOT responsible for any damage your phone may or may not receive. It is your fault for following this guide, not my fault for writing it. Just for the sake of saving you from a headache, I would recommend backing up your contacts before starting this guide.
Phase 1: Prepping your CDMA Hero for rooting/flashing.
1. Ensure that USB debugging and installing apps from unknown sources is enabled. You can do this by going into Settings> Applications Check unknown sources. From there go into Development and ensure that "Enable USB debugging" is checked.
2. Mount your SD card on your computer by plugging in the USB cable, and dragging down the notification area. BACKUP YOUR DATA! ALWAYS!
3. After your data is backed up, Safely remove hardware (I find it annoying to get the "this disk may contains errors" every time i plug it in) your Hero. Using your notification area, unmount your SD card.
4. On your hero, navigate to Settings> SD card and phone storage> unmount SD card. Then format your card. It should Auto re-mount after this.
5. Download FlashRec (great tool!) and Amon-RA's recovery image. Place them onto the root of your SD card (not in any folders, just drag and drop them.) Unmount your SDcard.
6. I used Linda File manager (from the market), but you can use one of your choice. Navigate to the root of your SDcard (you'll probably start there, if you dont just click sdcard.) Open flashrec with the installer, and wait until it's finished.
7. Open FlashRec, and attempt to make a backup (i simply named mine "/sdcard/backup"). If it success proceed to the next step. if not, refer to post 2.
8. In FlashRec, type "/sdcard/recovery-RA-heroc-v1.5.2.img" without the quotes. Linux is Case-sensitive, so the capital letters have to be included. tap "download recovery image". Wait for it to finish, when it does reboot into recovery mode by powering off your phone. After it's off, hold HOME and the power button. You should see some green text on a black background.
9. First things first, Make a nandroid backup. It can, and will save your ass at some point in time. Before you flash ANYTHING to your phone, ALWAYS do a nandroid backup. Congratulations, you can now flash a custom ROM!
Phase 2:Flashing your custom ROM
Since I love Flipz and his work so much I'll be using his ROM in my guide (let me know if you have a problem with it Flipz).
0. Do a nandroid backup before you even think about downloading a ROM
1. Download Fresh 1.0.
2. Do not unzip it, leave it as it is and copy it to the root of your SD card. You can do this either from recovery mode (by enabling usb mode) or through the notification bar. Proceed to recovery mode by holding HOME+END CALL (or just disable USB mode) and select "flash update from .zip" Select the Fresh ROM and wait. It should automatically reboot after it finishes installing.
3. Be patient while it's booting, it took me about 5 minutes for the first boot, after that it gets much faster. Once it loads, everything should be all fine and dandy. If it's not, well aren't you glad you made your backup? Just proceed back into recovery and do a nandroid restore.
4. You can now delete all those .apks and .zips and whatnot. Mount your SD card on the computer, and move your backed up files back onto your card.
5: Enjoy! If you don't like the clear lock, Flipz has a patch on his website (geekfor.me) to replace it with a clear screen. This should keep all of your contacts and settings in place, but I make no promises.
Sources:
The Unlockr

How to unpatch your Sprint CDMA Hero.
Phase 1: Installing the SDK/Drivers
1. Download the SDK from Google. Create a folder at the root of your C:\ drive called android (it doesn't have to be your C:\, you can put it anywhere, but this guide will use "C:\android" as it's path.)
2. If using Windows Vista or earlier, proceed to the next step.
3. Download the driver for your system.
Windows 7 32Bit
Windows 7 64bit
To find out which drivers are right for your system, go into your control panel, and change the view type to small icons. Click on system, and check and see if it says 64-bit Operating System or 32-bit Operating System. Extract the contents into:
C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Vista_x64 (for the Windows 7 64-bit)
or
C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Vista_x86 (for the Windows 7 32-bit)
4. If you have not plugged your Hero into the computer yet, it's as simple as navigating to where you extracted the contents of the archive, and right clicking androidusb.INF (should be the second from the top) and clicking install.
5. Ensure that USB debugging is enabled by navigating to Settings>Applications>Devolopment. If it does not have a check next to it, tap it. Plug your phone in and wait for the drivers to install.
6. In Windows, navigate to the command prompt.
XP: Start>run type "cmd" and press enter.
Vista or later: Start/"orb" in the search box right above it, type "cmd" and press enter.
if you see a window pop up with "C:\Windows\system32\cmd.exe" if you have done this correctly.
7. type "cd \android\tools" and press enter. now type "adb devices". It should start a daemon, and show you a series of numbers. If it does, then congratulations! your drivers are installed properly! I'll come back and add later how to reinstall the drivers if they do not install correctly.
Phase 2: Unpatching your Hero
Ensure that you have an adaptor to plug your SDcard into your computer. I didn't use an adaptor when i did this, but I highly recomend it just to make things easier. If your phone or SDcard or computer or toaster blows up, catches fire, shoots lazer beams and burns your curtains, or causes any damage to your or anything else I take no responsibility.
1. Backup all of the data from your memory card onto your computer. Navigate to Settings> SD and phone storage. Unmount your SD card and format it.
2. Go to Settings> Applications> Devolopment and ensure USB debugging is enabled.
3. Open command prompt, as you did in Phase 1, and navigate to "C:\android\tools". Type "adb shell" and press enter. Now you're in your phones console. Type "cat /sys/class/mmc_host/mmc1/mmc1:*/cid"
4. Copy down the code you get EXACTLY. Double, triple, and qraduple check. If the code is wrong, you may destroy your SD card.
5. Reverse the code.
Example:
123456789
Would become
987654321
6. replace the first two numbers/letters with zero zero. (007654321). Now on your PC, navigate to Here. Copy the number (with the zeros in place!) to the box that says CID. Click continue and wait for the email with your goldcard key. Save it to your computer.
7. Download this hex editor and install it. run it (requires administrative priveledges), and put your SDcard into your computer, or mount your SDcard.
8. In the hex editor, click on the extra tab, and open both your SDcard and the Goldcard you downloaded earlier. Ensure that "Open as read only" is unchecked when you open your SDcard. Sector size should be at "512 (Hard Disks/Floppy Disks)".
9. Go to the Goldcard tab, and press Ctrl+A to highlight all of it, then press Ctrl+C to copy it. Go to your SDcard tab, and select from 00000000 to 00000170. Now click on the edit>paste write.
10. click File>save. Remove and replace your SDcard, or unmount and remount your phone. If you can navigate into the drive, congratulations you have a Goldcard.
Phase 3: Downgrading your Hero.
1. Download the1.29 RUU. Plug your phone into the USB port with your goldcard inserted. Have your phone powered on when you do this, and ensure that it is not locked.
2. Ensure that you have HTC Sync installed, and that it connects to your phone.
3. Run the RUU and wait for it to finish. After it is finished, proceed to post 1.

If we simply want to upgrade to a different ROM or the new 1.5.2 recovery.img then can we simply pick up on your instructions from that point??
Thanks for your post. The only thing I think you are missing (for a totally new user doing this) is explaining how to boot into recovery mode when you are ready to flash the new ROM.
There is one other thing that I think would be great to have added to a post like this and that is an explanation of how to restore your programs after flashing a new ROM. Do you just reinstall them or is there a way to restore files and be able to keep your screen looking mostly the same?

Whats up with the Moto Droid? When are ROMS going to be pushed? and are you going to wright and Guide for Droid like this one?

saintirish said:
If we simply want to upgrade to a different ROM or the new 1.5.2 recovery.img then can we simply pick up on your instructions from that point??
Thanks for your post. The only thing I think you are missing (for a totally new user doing this) is explaining how to boot into recovery mode when you are ready to flash the new ROM.
There is one other thing that I think would be great to have added to a post like this and that is an explanation of how to restore your programs after flashing a new ROM. Do you just reinstall them or is there a way to restore files and be able to keep your screen looking mostly the same?
Click to expand...
Click to collapse
As far as I know, you just have to reinstall your programs. This guide will also work for loading ROMs other then Freshhh, but some ROMs require you to do a wipe before you install them. Check to see if that specific ROM requires a wipe before doing an install. Yes, I have used this method to upgrade from RA's 1.2.3 to 1.5.2 with no problems.
@_Chris_Kirkland said:
Whats up with the Moto Droid? When are ROMS going to be pushed? and are you going to wright and Guide for Droid like this one?
Click to expand...
Click to collapse
I have no idea about Droid modding, as I don't have a Droid. I'm not to fond of the idea of writing a guide for a phone I don't have because I wouldn't be able to verify that it works with minimal problems.

Alright, I've completed the basics of how to do this. I'll add a problems and solutions section once people start having problems.

great job, this should help folks out a good deal.

That's my intention. Just trying to make things easier for those who aren't so good with the console. I think I'm gonna go ahead and do the Win7 driver workaround now.

In step 8 of the guide I can follow along up to step 8 but when I type in the text I don't see the download option.

jfoster38122 said:
In step 8 of the guide I can follow along up to step 8 but when I type in the text I don't see the download option.
Click to expand...
Click to collapse
You're talking about the FlashRec step right?
Could you tell me exactly what you can see?

So this is probably an obvious question, but I apparently not to me, but is the guide to perform a downgrade for people who have not rooted and flashed their phone? Because I was able to downgrade to 1.29 ruu after having flashed my phone with Fresh 1.0, is it because I flashed a custom rom that I could downgrade to 1.29 or is there something different now?

mark920 said:
So this is probably an obvious question, but I apparently not to me, but is the guide to perform a downgrade for people who have not rooted and flashed their phone? Because I was able to downgrade to 1.29 ruu after having flashed my phone with Fresh 1.0, is it because I flashed a customer rom that I could downgrade to 1.29 or is there something different now?
Click to expand...
Click to collapse
This is a guide to try and simplify patching, but it also covers a section on how to downgrade a phone that Sprint/HTC patched so that the 1.29 RUU method wouldn't work.

How does someone get a phone that was patched by sprint/htc to not allow the 1.29ruu to work on the phone?

mark920 said:
How does someone get a phone that was patched by sprint/htc to not allow the 1.29ruu to work on the phone?
Click to expand...
Click to collapse
Ether get a newer Hero, or run the software update in the phone. I ran the software update >_>

abcdfv said:
You're talking about the FlashRec step right?
Could you tell me exactly what you can see?
Click to expand...
Click to collapse
Once I enter the recovery image in, the 2 options are "Flash Recovery Image" and "Restore Backup Image"
There's no download recovery image option.
- JustPyro

It may have been updated since I used it... I'll look into it
EDIT: Click on FlashRecovery image.

Excellent work! I just want to let you know that the link for the RUU 1.29 does not work (at least for me). Great guide though.

Link updated.

[GUIDE] How to root Android 2.2 on the EVO 4G Outdated

The rooting method for the EVO 4G is close to the same as the Droid 2, just recently created by Sebastian Krahmer at http://c-skills.blogspot.com/, but with a little variation.
Here is the step-by-step I just did on my brother's (dwizzy130) EVO 4G that came with 2.2 from Sprint.
I am NOT responsible for any damages (bricking, not working, basically anything that goes wrong) This has been tested and works. Over the next few days, I will be cleaning this post up and making the steps more clear.
Special thanks to:
Sebastian Krahmer for the exploit
dwizzy130 (my brother) for letting me test on his EVO (since I don't have one)
The unrevoked team for their methods
Toastcfh for his mtd-eng.img
Topgun966 over at evo4g.me for hosting the files
djR3Z over at TheDroidDemos.com just made a GREAT video walkthrough that should make this MUCH easier for all of you. He spent a TON of time making it yesterday, so please give him lots of thanks!
VIDEO WALKTHROUGH (2 parts)
Make sure your phone is unplugged from your computer until I tell you to plug it in!
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 here
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.40 here
Run the installer. Move on once installed. If reboot is required, do so and then move on.
Windows 7 Users:
Go to your start menu, then control panel. When that is open, (if you are in category view mode) click on "Uninstall a program" and then choose HTC Sync to uninstall. If you are in Icon view mode choose "Programs and Features" and then click on HTC Sync to uninstall. This will load the proper drivers needed for unrevoked3.
Other Windows Version Users:
Go to your start menu, then control panel. When that is open, select Add/Remove Programs, and then choose HTC Sync to uninstall. This will load the proper drivers needed for unrevoked3.
Next,
Download my evo-root.zip.
It contains a few files necessary to root the EVO.
Unzip the contents of the zip to your android sdk tools folder.
Download the unrevoked-forever.zip
Place this zip in your tools folder as well, as a zip, not extracted.
Download this PC36IMG.zip || Mirror(This is the same as running an RUU, so it will delete all of your user data when we use it later in the guide, so backup everything you want to save on your phone first)
MD5: e52f6ec4f8f5fd6dc251ef19ee19750b
Put this zip in your sdk tools folder as well, as a zip, not extracted.
After unzipping the contents of evo-root.zip to your android sdk tools folder and placing the PC36IMG.zip and unrevoked-forever.zip in the folder, move on.
Step 4: Make sure USB Debugging is ON (checked) on your EVO. Go to Settings > Applications > Development > and make sure it is checked.
Step 5: 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.
If your computer asks you to restart after the new drivers were installed, do that now.
Step 6: Open up a command promt from your android-sdk/tools folder.
Windows 7 users:
Open up the android sdk folder and hold shift and right click on the tools folder. You will see an option that says "Open command window here" Choose that one and you will be set. the command prompt should read something like C:\android-sdk-windows\tools>
Other Windows Version Users:
Go to the start menu, go to All Programs, then Accessories, and click on command prompt. Once open type
Code:
cd C:\android-sdk-windows\tools
Once ready, type these commands in cmd prompt from your adb tools directory. After every line press enter.
Code:
adb push unrevoked-forever.zip /sdcard/
adb push flash_image /data/local/
adb push rageagainstthecage-arm5.bin /data/local/tmp/
adb push mtd-eng.img /sdcard/
adb push PC36IMG.zip /sdcard/
Note: the PC36IMG.zip will take longer than expected to transfer to the sdcard. It is a BIG file.
Now we chmod a few things. After every line press enter. It should repeat what you typed in and then return you to a blank line with an $ for everything in adb shell
Code:
adb shell
chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
chmod 0755 /data/local/flash_image
Ok now for the root shell.
*
(still in adb shell)
Code:
cd /data/local/tmp
Code:
./rageagainstthecage-arm5.bin
You will now see some text on your cmd prompt screen explaining the exploit.
Wait for the adb shell to go away, and it will dump you into your windows command prompt again (no shell) should look something like this:
C:\android-sdk-windows\tools>
Once that dumps you out of the shell, type
Code:
adb shell
and you will see you now have a
Code:
#
instead of
Code:
$
now type
Code:
cd /data/local
./flash_image misc /sdcard/mtd-eng.img
that will flash your misc partition with Toast's mtd-eng.img.
This should return you to a blank line with #.
If you get an "Out of memory error" with a huge list of weird lines, here's how to fix it.
Reboot your phone normally.
Open a command prompt and go backwards in this guide until you see the big red * and start from there.
Once it is flashed correctly, move on:
Type
Code:
reboot bootloader
Remember how you pushed that huge PC36IMG.zip to your sdcard earlier? This is where that comes in handy. Once you booted into hboot, Select "bootloader" with your volume up/down buttons and hit the power button. Let it sit for a little bit while it loads the PC36IMG.zip. This can take up to 5 minutes. When it finally asks if you want to apply this zip, choose YES. (Remember, this is the same as running an RUU, so it will delete all of your user data).
If this doesn't work (ie the PC36IMG.zip does NOT load) backup all of your sdcard contents onto your computer, reformat your sdcard to FAT32, redownload the PC36IMG.zip, and drag and drop it onto the sdcard, then reboot into the bootloader and try again. This should fix the issue.
Once it is finished, select restart. You now are on the stock 2.1 build of Android.
Next step, mount your sdcard on your computer, and delete the PC36IMG.zip from it. This is because the next step requires using hboot, and you don't want to sit and wait while it loads up again, just for you to say "no" to the install. Please follow this step, for it saves 5-10 minutes of waiting ahead.
I worked extensively with Matt Mastracci, so this rooting guide will use the unrevoked method to root 2.1. This is what worked for me testing on my brother's EVO, so if you do end up trying something else to root 2.1 with, PLEASE do not post it here or ask questions, for I will only support the unrevoked team.
Now open up your web browser on your computer and navigate to Unrevoked
Choose the correct operating system to download for.
*
Make sure you install the modified android usb driver that comes with the unrevoked3 install (see the html file included when you extract the exe)
Once downloaded and extracted, run the program on your computer.
Make sure your EVO is plugged in with USB DEBUGGING ON!
It will reboot to the bootloader, and it will wait for you to use volume down to select HBOOT USB. (the last option)
After you have selected it (by pressing the power button) let the unrevoked3 program handle the rest of the flashing.
If you have had any trouble with the bootloader freezing or not moving for over 3 minutes, you most likely forgot to uninstall HTC Sync (as directed at the beginning of this guide), or you need to install the modified hboot drivers that come with the unrevoked3 program, OR a nasty combination of the both.
For the modified drivers and explanation on how to install them, open the "hboot driver.htm" file that gets extracted when you extract the reflash_package.exe. It will explain everything. You will have to reboot your phone after you install the drivers. Once you have repaired this go back to the big blue *
As soon as it is booted into recovery, you are done with that.
Next in recovery go to
Code:
install zip from sdcard
then
Code:
choose zip from sdcard
and choose the
Code:
unrevoked-forever.zip
This will flash the unrevoked forever hboot unlock.
_____________________________________________________________________
Part 2
Note: This section would not have been possible without the amazing testing and help of cilio87. He earns a gold star *
Now it's time to finish up the process and flash the stock 2.2 build of Android. You need to do this before any custom ROM in order to re-update the partitions we downgraded in the rooting process.
Step 1: Download either the update zip with
ClockWorkMod recovery included
or
Amon_RA's recovery included
This is the most up-to-date version of Amon_RA recovery that allows you to back up WiMAX partition.
(Either zip contains the final touches to the root process, one flashes clockworkmod recovery, and the other respectively, Amon_RA's recovery)
Extract the 3 files inside the zip to your desktop.
If you are still in recovery (from part one or the guide) go back to the main menu of recovery on your phone (if you aren't already at the main menu, hit vol up & down at the same time) Select
Code:
Reboot System Now
Let the Rom load, and when it gets to the sign in screen for Google, just skip everything and let the ROM boot.
If you are already on a custom rom, boot into it and follow from here.
Once It is fully booted, mount your sdcard onto your computer, and copy the 3 files you extracted from the zip to the sdcard.
Once copied, Unmount your sdcard from the computer.
Step 2: Unplug your phone from the computer. Power it off completely. Now while holding VOLUME DOWN turn on the phone with the power button, continuing to hold volume down. This will boot into hboot. You can release the buttons once you get to the hboot menu. Then use the power button to click on bootloader. This will scan the sdcard for the new PC36IMG.zip you just copied to the sdcard. When it asks "Do you want to start update?" Hit Volume Up for Yes. It will reload the zip and then start the flash. Once the flash is complete (may take 5 or so minutes) Choose NO when it asks you to reboot.
Step 3: After choosing NO to the reboot, you will see a menu again. Select Bootloader from the menu, then use the Volume Down button to hover over "Recovery" and press Power to click on it.
If your phone gets stuck at the White EVO 4G screen, pull your battery, and then power on while holding volume down again. It should boot to the bootloader again, where you can select recovery.
Once you are booted into this custom recovery, go to
Code:
Install Zip from sdcard / Flash zip from sdcard (Amon_RA)
and then (clockworkmod only)
Code:
choose zip from sdcard
You will then see the 2.2-root.zip. Click on that and accept the flash.
Once that flash is complete, return to the main menu of recovery and Select
Code:
Reboot System Now
You now have stock Android 2.2 with root and all updated partitions!
If you would like the flash_image binanry so you can flash new recovery images quickly from adb shell, flash the zip that is attached below as a normal zip in recovery AFTER you have completed this entire guide.
IN ORDER TO FLASH CM6 OR DAMAGE CONTROL, YOU NOW NEED TO FLASH THE ENG SPL. LOOK FOR IT IN THE EVO 4G ANDROID DEVELOPMENT FORUM.
Here is the ENG SPL
Good Luck!
Dan Wager

Awesome! Good job on everyone that worked on it. Finally no more people asking about it

Yes! I look forward to the rest of your post
Sent from my PC36100 using XDA App

Great news everyone!
Eagerly awaiting.

Awesome xD
Sent from my HTC Evo 4G using XDA app.

Oh thanks! Gonna be watching this all night! This is gonna be AWESOME!!

Vandam500 said:
Finally no more people asking about it
Click to expand...
Click to collapse
if only you were right...

I love the xda forums, good job to everyone involved, another reason I love my evo.
Sent from my PC36100 using XDA App

I wish I didn't just take my xanax. Ughhhh

Vandam500 said:
Awesome! Good job on everyone that worked on it. Finally no more people asking about it
Click to expand...
Click to collapse
I'll add with another question that will "end"
Will this allow me to have PRI 1.40?

Stop with the irrelevant posts! We don't need a hundred pages of nothing! Start a thank you thread if you want! Leave this one for the op and instructions and the files! Makes things easier for everyone so we don't have to go thru hundreds of posts to piece together relevant information!
NOTICE THE TITLE OF THE THREAD IT SAYS GUIDE LET IT BE JUST THAT!

Details---
I've heard the process is more than a simple click like simple root or unrevoked... But at least we have root.
It will be nice to see the detailed failsafe guide so I don't go around bricking phones and hopefully an automated prog is made to make it a breeze.

A great help!
Having a B-day tomorrow, and have searched the month of August for a complete method to root my froyo 2.2
Thank you in advance for your expertise and assistance..

well, i followed the droid2 guide and it worked all the way up to giving me the # sign... but the cp commands are failing. but since i have #, can i just run unrevoked 3.1 at this point? or do i need to succeed in the entire driod2 tutorial?

Thank you
OMG you guys are the best devs ever ill be stuck to this like glue once again XDA is the best forum on the planet.

edufur said:
well, i followed the droid2 guide and it worked all the way up to giving me the # sign... but the cp commands are failing. but since i have #, can i just run unrevoked 3.1 at this point? or do i need to succeed in the entire driod2 tutorial?
Click to expand...
Click to collapse
no, once you get to that point you have other stuff to do.
just wait til the guide comes out... We've waited how long for this thing? an extra hour or so won't kill you. (hopefully)

Yeah, almost done writing the guide. Try not to give out anymore details yet, I should be posting the full guide shortly.

sprink0281 said:
Stop with the irrelevant posts! We don't need a hundred pages of nothing! Start a thank you thread if you want! Leave this one for the op and instructions and the files! Makes things easier for everyone so we don't have to go thru hundreds of posts to piece together relevant information!
NOTICE THE TITLE OF THE THREAD IT SAYS GUIDE LET IT BE JUST THAT!
Click to expand...
Click to collapse
And your message is wholly important? Yes, the title says "guide" but that means that the original post will contain the guide. This is a forum, not a wiki. (I know my message doesn't help at all either)
Hooray, root on 2.2!

please make it easy for us newbies too please

Greenfieldan said:
please make it easy for us newbies too please
Click to expand...
Click to collapse
I'm getting the basics out tonight and will make it an easy read like my Hero rooting guide tomorrow sometime, because I am exhausted tonight.

[ROOT][GUIDE] HBoot 2.02/2.10 SOFF - Goodbye Stranger - Upd. 02.25.11

I am sad to say the time has come to retire this post....Now before you get all panicky and ****, just sit your **** down, take your adderall and relax, damn antsy ass people. Anywho, with people our there like xHausx and others that have automated all of this there really isnt a need for me to keep this updated. I will keep the post here for archival purposes but, I will not be updating it, any further. I may pop into the thread here and there but probably not. I would like to thank all those that helped and supported me during this threads run. With out you we would still be stuck.
In the mean time if your looking to root your phone, check out xHausx's thread
here: http://forum.xda-developers.com/showthread.php?t=838448
And no I still dont recommend Clockwork or Unrevoked.
Till next time...Super Tramp - Goodbye Stranger
Archive of the guide as of 2/14/11
READ THIS GUIDE CAREFULLY SEE POST TWO FOR FAQ OR SEARCH THE THREAD.
Presenting the ONE AND ONLY surefire root method that backs up your RSA KEYS prior to rooting !!!!
Also I am aware that unrevoked has out their new tool. However while I was sitting in IRC, I saw many that it wasnt working for. So Until there is a surefire, easy method, I will keep this thread updated.
Credit goes to:
amoamare (Initial method)
toast (fake recovery and script)
unrevoked (thanks for your app)
amon_ra (fixed custom recovery)
chris1683 (thanks for the rom) (sprintlovers)
ryanza (z4root)
illogos, epicroot, xHausx, TrevE, Chubbzlou (Testing)
BooDaddy (RSA Backup Info)
and who ever else I missed
Help me finance my Vette!
zikronix
Disclaimer and well a little fun:
This has been tested on many phones and it worked fine...but if it breaks your **** dont come cry to me about it...you knew the risks! No one here is responsible if you break, brick, set fire, punch, smash, stab, destroy, your self, computer or your phone. The only person responsible is you! Just because it worked for me and others does not mean it will for you. Anytime you flash something its a risk.
Ladies and gentlemen... I've traveled over half our forum to be here tonight. I couldn't get away sooner because I had a POST coming in and I had to see about it. That phone is now rooted at and running well. I have two others comming in and this method has rooted many on the board. So, ladies and gentlemen... if I say my guide works you will agree. You have a great chance here, but bear in mind, you can lose it all if you're not careful.
Out of all methods that beg for a chance to root your phone, maybe one in twenty will work; the rest will be trolls-that's posters trying to get between you and the guide-to get some of the root action that ought by rights come to you. Even if you find one that has a simpler guide, and means to root, he'll maybe know nothing about helping. This is... the way that this works. This method is reliable like no other in this field and that's because its been tested and tested time and time again. I assure you, whatever the others promise to do, when it comes to the showdown, they won't be there...
Downloads
================================================== ====
STOP HERE READ THIS
This Method soley uses Amon_RA Recoveries....Period. A poor soul that lost his RSA keys (broken 4g forever) by recent clock work shenanaigans here
VX - Updated Amon Ra Recovery. Download Here: hboot_2.xx_soff-VX.zip
MD5: 27eb4a36ba01078193975fc93723dd60 <---VERIFY YOUR MD5, IF ITS NOT THIS REDOWNLOAD
Lets Get Rooted!
======================================================
Prerequsites:
Extract only the main zip file to a folder of your choice. I recommend the root of C:\ into a folder of your choice or on the desktop. Make sure you have the drivers installed for your phone (recommended: SDK Drivers or unrevoked hboot drivers) and USB debugging is on. This was setup for people running windows, if you have access to it do it on a 32bit version. I can't stress this enough you must use the adb.exe included with the package This is command line based do NOT double click the exe. Assume nothing, and cut and paste or type the commands EXACTLY as listed, they are case sensitive and each line is a seperate command. Oh and Read the FAQ and Warnings for f-sakes
1) Connect your phone to the computer (Rear USB Port Perferred) make sure the computer detects the phone (DO NOT MOUNT USB) If it doesnt install the drivers. Now master Reset your Phone (Menu>settings>Sd & Phone Storage>Factory Data Reset). Your phone will reboot. While your phone is rebooting it ctrl+alt+delete on your computer and open up task manager and click the processes tab look for anything that says adb.exe click it and hit end process.
2) Your phone should be booted and in the rom. You can skip the setup. On your phone enable install applications from unknown sources.(menu>settings>applications>unknown sources) and turn on usb debugging.
3) Open a command prompt (do NOT click adb.exe) and change to where ever you extracted the files to.
4)Type the following (this must be excuted from the folder you extracted to)
adb push root/unrevoked-forever.zip /sdcard/
adb push root/mtd-eng.img /sdcard/
adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip
adb push pc36img/PC36IMG-MR.zip /sdcard/PC36IMG-MR.zip
adb push root/flash_image /data/local/
Click to expand...
Click to collapse
5) Now were gonna install z4root. When its done look at your phone z4root should be running. Select temporary root... It will go thru the process will eventually come to a white screen *Wait* after a sec or so screen will come up saying temp root was a success. Ok so now type the following
adb -d install -r root/z4root.apk
adb shell am start -a android.intent.action.MAIN -n com.z4mod.z4root/com.z4mod.z4root.z4root
Click to expand...
Click to collapse
6) Your command should still be open and you should be in the directory where you extracted the files. Once you have typed "su" command below look at your phone and click allow for SuperUser...Ok so now type the following from the command prompt
adb shell
su
Click to expand...
Click to collapse
6A) REQUIRED RSA BACKUP This will back up your RSA keys just in case something goes wrong in that department. You should still be in your command window inside the shell with a #. (The following came from this thread)
mkdir -p /sdcard/nandroid/RSA-PR-BACKUP
cat /dev/mtd/mtd0 > /sdcard/nandroid/RSA-PR-BACKUP/wimax.img
This saves it in a file that can actually be restored. This next step is another type of backup just for good measure
busybox sed -n '/BEGIN CERTIFICATE/,$p' /dev/mtd/mtd0 > /sdcard/rsa_OEM.key
This will dump the RSA keys to a text file on your SD Card named rsa_OEM.key
Mine was about 4575 KB in size, but the size could vary. Go ahead and switch the phone's USB connection over to "Disk Drive" and then browse to your SD Card and verify that the file rsa_OEM.key is indeed on the card.
Proceed to Step 7
Click to expand...
Click to collapse
7) You Should still be at a "#". This means you have root if you see a "$" or some other error message. Reboot your phone, check your drivers, usb debugging and cable and start over. If you got a "#" You can Proceed. You should still be in the shell at a "#" If not start over...Otherwise
chmod 0755 /data/local/flash_image
./data/local/flash_image misc /sdcard/mtd-eng.img
sync
Click to expand...
Click to collapse
8) Now we are going to reboot your phone into the boot loader to flash the first PC36IMG.zip. You should still be in the shell So Type:
reboot bootloader
Click to expand...
Click to collapse
9) Once your phone is in the boot loader highlight bootloader, and press the power button. It will load the PC36IMG File...When it ask you to flash press VOL-UP. You will notice that it says bootloader bypassed and maybe some other errors. Dont worry this is normal. Once the flash of the file is done it will ask to reboot, Select NO by Pressing VOL-DOWN. Now some people have gotten some errors here and there during the flashing just continue as normal.
10) You should still be in the boot loader at this point. Scroll down to recovery and press the power button. It Should take you to a red triangle. If not and you get stuck at a white htc screen pull the battery and then repower the phone with power + vol down and select recovery. When you see the red triangle. Type the following (IF YOU GET STUCK HERE CHECK THE FAQ):
adb push recovery /
adb shell busybox --install /sbin
adb shell nohup /sbin/recovery &
Click to expand...
Click to collapse
With any luck you should be at a recovery (green screen with text)
11) Select enable USB-MS. This will mount your sdcard. Look in the root of your sdcard and you should have two files. One named PC36IMG.zip and one named PC36IMG-MR.zip. Rename the file named PC36IMG.zip to PC36IMG-ENG.zip and then rename PC36IMG-MR.zip to PC36IMG.zip when your done follow the instructions on your phone to disable usb (press power) then proceed to step 12
12) Now Select flash zip from the menu and choose unrevoked-forever.zip. Wait for it to complete. Select Reboot from the menu.
Now pay attention. It might kick you back into:
BOOT LOADER: See 12A
ROM: See 12B
WHITE HTC SCREEN: See 12C
12A) Ok so you got kicked to the boot loader. It should scan your card and find the PC36IMG.zip chose yes to flash this file and when it ask you to reboot....reboot by pressing vol-up....Proceed to step 13
12B) Ok so the phone booted into a rom. Power the phone off. Then repower the phone on pressing power and vol-down at the same time. It should take you into the bootloader and scan your card and find the PC36IMG.zip chose yes to flash this file and when it ask you to reboot....reboot by pressing vol-up....Proceed to step 13
12C) Ok so the phone is stuck at a white htc screen. Power the phone off by pulling the battery. Then repower the phone on pressing power and vol-down at the same time. It should take you into the bootloader and scan your card and find the PC36IMG.zip chose yes to flash this file and when it ask you to reboot....reboot by pressing vol-up....Proceed to step 13
13) Ok your phone is rooted now, and you should be inside the rom. The rom you just flashed is Sprint Lovers rom with the modified recovery. Download a rom of your choice copy it to the root of your sd card and flash it. But type the following first
adb shell mv /sdcard/PC36IMG.zip /sdcard/PC36IMG-MR.zip
adb reboot recovery
Click to expand...
Click to collapse
14) You Should be in the recovery menu now (green text screen). Do a backup by navigating to backup/restore press power to select then do a Nand backup in the next menu. Once thats done, select return, then reboot or flash a rom of your choice. If you flashed a different custom rom than the one thats included in the package cool. If not no big deal eitherway. Do a PRL/Profile update while in the rom after the phone is done rebooting. Your Done.
15) Read the FAQ for questions
==========================================
FIX BROKEN RECOVERY
This is really only needed if you rooted with one of the previos guides version 6 or lower or if you installed a different recovery like I told you not to. It installs amon_ra 2.2.1
1) Download File PC36IMG_Recovery.zip and Rename to PC36IMG.zip.
copy to the root of your SDCard and power off phone
2) Power your phone back on into the boot loader by holding power and vol-down until your presented with a white screen. It will read the pc36img.zip and as you if you want to flash. Say yes. Then it will ask if you want to reboot, VOL+UP for yes.
3) If your rom gets tossed in the process. Reboot your phone into bootloader select recovery, and reflash your rom....DONE
================================================
UNROOT GUIDE
NOTE: This will erase all data on the phone. (Will not erase data on the SDCard)
1) If your on Hboot 2.10 Download the PC36IMG.zip Here. If your on Hboot 2.02 Download the PC36IMG.zip here then Unrevoked s-on here rename the pc36img file to pc36img.zip copy that and the unrevoked s-on tool to the root of your sd
2) Power your off. Power the Phone back on into the boot loader by holding power and vol-down until your presented with a white screen.
3) It will scan for the pc36img.zip. Select no to flash. Select recovery from the menu. Once in recovery choose flash zip from the menu, and select unrevoked forever s-on.
4) When its done flashing select reboot from the menu.
5) From here either run the official ruu or boot back into the boot loader (see step 2). When it scans and ask you to flash the pc36img.zip select yes then yes to reboot.
Click to expand...
Click to collapse

FAQ
FAQ:
Your here cause something went wrong right? Ok thats fine. This list isnt extensive but its here to provide quick answers to some weird or common questions. New questions and problems are added to the bottom.
Q: Will this downgrade my hboot
A: No. I used to have an hboot downgrade but it was bricking peoples phones. However is you want to risk bricking your device, visit this thread here. I I advise against this. This bricked alot of phones which is why I pulled it.
Q: How do I install the Hboot Drivers
A: Check this here
Q: I get "error: more than one device and emulator"
A: kill the adb.exe tasks in task manager or reboot your computer
Q: Step #9 my phone does read the PC36IMg.zip
A: If you renamed the zip file make sure it doesn't say PC36IMG.zip in the name remember that xp and up on windows doesn't show the file ext by default so if you see PC36IMG.zip chances are its named PC36IMG.zip.zip
Q: Why cant I use Clockwork Recovery
A: At the moment its not coded for the new partitions. Just read the first few pages of this thread or check this here
Q: What Hardware does this work for
A: All currently known hardware 0001-0004
Q: What Hboot's does this work for
A: It was built for 2.02 and 2.10 however it will work for all version its just there are easier ways for those
Q: I think I messed up can I just start over.
A: Yes. Its recommended if you want to start over run the official ruu.
Q: This is very complicated
A: It is...thats why there is instructions
Q: Will this erase my data
A: Yes but not from the SDCARD
Q: Can I deleted the files off my SDCARD when done
A: Yes, except for RSA_OEM.KEY and WIMAX.IMG
Q: I get permission denied or device offline when trying to step 10
A: Check here or here or here this might work for you
Q: I used clockwork it seems to work fine.
A: It might but considering the partition information is not correct. You may have just over wrote your wimax keys and broke 4G. Have fun with that like this poor guy here
Q: This uses unrevoked in one of its steps? Explain?
A: There have been some concerns that this uses unrevoked-forever in one of its steps. As far as we know that Unrevoked 3 (not to be conufused with unrevoked-forever) is causing some radio issues with hardware in general and new hardware. Unrevoked-forever does not appear to bork the radio like unrevoked 3 does. This is apparent by the many success stories. However Unrevoked3 could very well possibly destroy your radio/wimax/brick if used.
Q: I get device not found
A: Install the drivers for your phone, (Unrevoked, ADB)
Q: Camera doesnt work after doing this
A: Flash a new rom thats current. Like SteelRom, Fresh, Stock Rooted. The issue here is the Hardware is different. NO CUSTOM KERNELS
A2: Reports say they changed the camera provider/hardware. And the drivers are different! Using a rom based off the latest release and kernel should fix it As Discussed here and here and here
Q: When I go to recovery. I get a red triangle.
A: See Step 10
Q: This doesnt work!
A: Yes it does if you follow the directions, Unless some other bull**** decided to popup!
Q: CM6.x doesnt work
A: See Question 7....Nothing I can do about that if the kernel doesnt support your camera/device.
Q: My phone boot loops now...You broke my ****!
A: I didnt break your ****. You broke your own ****! Its not broken so chill out (well it might be but probably not). What rom did you flash? Did you flash a custom kernel? Did your rom come with a custom kernel? I bet your using a custom kernel. Try a rom like Steel Rom, Sprint Lovers
Q: How do I back up my RSA Keys
A: Check here for the latest up to date information. Or run this command from the shell
cat /dev/mtd/mtd0 > /sdcard/wimax.img
Click to expand...
Click to collapse
Q: My 4g Doesnt work
A: Was it broken prior to the s-off, what steps did you take. Are you running AOSP ROM or Another kernel?, Did you try a different rom? What version is your phone? Do you have SwitchPro Widget installed? (uninstall it), Did you try to run unrevoked3 prior to this? After flashing the radios and stock kernel based rom did you do a data and prl update? Does the mac behind your battery match whats in about phone (4g has to be on to see mac) Also try the tree.xml fix posted
adb shell
ls /data/misc/wimax/
look for a file with your macaddress ending in .tree.xml. you want to move that to another location so it gets regenerated. (the following command basically renames it.)
mv /data/misc/wimax/(Your-mac-address).tree.xml /data/misc/wimax/(Your-mac-address).tree.xml.old
4. Start 4G may not connect
5. Do a prl/profile update
6. Power off the phone and power it back on. Try it
7. PRL/Profile. Try it
Click to expand...
Click to collapse
Q: 4G is still broke.
A: Check your RSA keys
adb shell
cat /dev/mtd/mtd0 | grep RSA
returned output show appear as this:
# cat /dev/mtd/mtd0 | busybox grep RSA
cat mtd0 | busybox grep RSA
RSA-REQUEST
RSA-REPLY
RSA-REJECT
RSA-ACK
RSA-1024
RSA-REQUEST
RSA-REPLY
RSA-REJECT
RSA-ACK
RSA-1024
RSA
ReRSA
RSA requests
RSA replies
-----BEGIN RSA PRIVATE KEY-----
-----END RSA PRIVATE KEY-----
#
It should look just like the above
the important lines are BEGIN RSA PRIVATE KEY and END RSA PRIVATE KEY.
If you have those two lines, your keys are still likely to be intact.
If those two lines are missing, your keys are likely missing.
/dev/mtd/mtd0 is where the wimax image is stored.
Click to expand...
Click to collapse
Q: OK I think My Keys are tossed. We made a backup right? So how do I restore it?
A: This post or post should do it for you
Q: My Phone says its not rooted.
A: If you have s-off your rooted. Simple as that. Try a different rom if you want. The second pc36img.zip file you flashed is Sprint Lovers and is a very nice rooted rom.
Q: When I try to get into Fastboot by pressing VOLUME UP and booting the phone, my phone instead buzzes three times and acts dead. What happened?
A: The S-OFF update also enables Qualcomm Diagnostics mode on your phone, which is entered by doing what you just did. You can exit this mode (and boot normally) by removing the battery and USB cable.
Q: Can you tell me what this does?
A: Read the guide? Basically your downgrading the phone, so you can flash unrevoked because htc "comically fixed" the phone. Then your re upgrading the phone back to shipping radios, system, pri, nv, kernel...all the while with keeping s-off
Q: How did you get to be so cool
A: If you have it, you don’t need it. If you need it, you don’t have it. If you have it, you need more of it. If you have more of it, you don’t need less of it. You need it to get it. And you certainly need it to get more of it. But if you already don’t have any of it to begin with, you can’t get any of it to get started. Which means you really have no idea how to get it in the first place, do you? You can share it, sure. You can even stockpile it if you like. But you can’t fake it. Wanting it, needing it, wishing for it. The point is, if you’ve never had any of it, ever, people just seem to know.
Q: Do you really own a vette?
A: Yes, and a backpack with jets!
Q: Whats with you and the dots ...
A: ...
Q: Your Kind of an Cocky Asshole
A: Yea...I Get that. Oh well. I cant fix stupid or ignorant.

What is the point of getting the new HBoot?

sorry, wrong question

abiezer said:
What is the point of getting the new HBoot?
Click to expand...
Click to collapse
there is no point in getting a new hboot....this tool is for those that have phones with the new hboot....that unrevoked wont work on.
this is not the new hboot

Oh I see so this is basically for people who couldn't root to be able to root. Got it. Thanks.

Dumb question, sorry trying to keep up with this while at work. Once I do this, then I still need to run Unrevoked, correct?

shepkc said:
Dumb question, sorry trying to keep up with this while at work. Once I do this, then I still need to run Unrevoked, correct?
Click to expand...
Click to collapse
its included in the script it tells you how to do it.

update failed, said main version is older...

its working for some but not others...i dont know why the main version is older thing...

i think we have ironed out the mainversion deal...
looking into it now.

Should be fixed now...so try it I guess.

v2
Looks like your V2 is working, I didn't run into the main version failure. Flashing as I type, I hope slyder got this to work.

Confirmed, V2 works
alright brotha your v2 of the batch file works like a charm. S-OFF confirmed on HBOOT 2.02. Thanks to everyone involved in making this happen.

Outstanding
Sent from my PC36100 using XDA App

On a brand new fresh 2.2 out of the box running HBOOT 2.02 I got "Main version is older". Are there any prerequisites i have to run to get this to work? I just reinstalled 2.2 and ran the script and got main version is older.

did you download version 2
do you have gtalk

I did download v2, and I do have gtalk.

b0r0b said:
I did download v2, and I do have gtalk.
Click to expand...
Click to collapse
you got PM....i want to know exactly whats happening.

Main version is older
I have also tried with V2 and get the "Main version is older".
Baseband
2.15.00.09.01
Software
3.30.651.2
PRL
60671

[SD CARD][HOW TO] Cant Mount SD Card or SD Card Corrupted

For those who may be flashing ROMs, cannot mount the SD Card any more, and may have accidentally corrupted their SD Card, here are some helpful steps.
Preliminary Review - Check to see if you can mount in recovery or bootloader
First, go back to your bootloader screen and click on fastboot (reset your phone and hold the power and vol down button). Once in bootloader check your computer drives to see if the sd card is recognized
Your computer may be able to recognize the drive even if it cant open it. If thats the case, you may be able to format it from your computer (use FAT32 formatting).
Second, If you cannot see your SD Card in your ROM or from the PC, and you are using Clockwork Recovery (CW), try flashing TWRP recovery first. Do this by going through the following steps:
Step #1
Download TWRP recovery from http://teamw.in/project/twrp2/100 Make sure to download the correct version for your device
Step #2
Place the recovery file into a folder with fastboot.exe
Step #3
Reboot your phone and hold down the Vol Down Button and Power Button until your bootloader screen appears, then enter fastboot. Then connect to your computer. I find this method works best by holding down the buttons right away. If your phone is off, press the power button then immediately press and hold the power and vol off buttons again until bootloader screen shows up. Dont let go until the screen shows.
Step #4
Type
Code:
fastboot flash recovery twrp.img
but replace the twrp.img wording with the exact name of your downloaded TWRP recovery
Step #5
Enter TWRP recovery by selecting it from your bootloader screen. Then ensure the device is connected to your computer and select the Mount option and then mount your sd card.
IF you still cant see your SD Card from TWRP recovery or you get an error, proceed to the next steps. Your computer may be able to recognize the drive, even if it cant open it (if your lucky).
If your computer recognizes the drive but cant open it, you can try formatting it from your computer (make sure to format as FAT32)
If you really cant see your SD Card, and your fairly sure its corrupted, and you have no way formatting it from your computer, continue on below:
Basic Solution
Reflashing Stock Recovery to your device using fasboot, then doing a full factory reset. This would be using the method in post http://forum.xda-developers.com/showthread.php?t=1630459
PLEASE NOTE THIS METHOD WILL WIPE THE DATA FROM YOUR DEVICE AS WELL AS FROM YOUR SD CARD
This method works because custom recoveries cannot re format SD Cards on the HTC One S, only wipe data from them. However, the stock recovery does have a proprietary feature that will reformat the internal sd card if it has been corrupted.
Inotherwords:
Step #1
Download the stock recovery from: http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img
*******Note that this file is a stock recovery for S4 devices, not S3.
Place the file into the same folder as your fastboot.exe
Step #2
On your device, go into bootloader and fastboot mode, connect your computer to the device, and type
Code:
fastboot flash recovery ville_recovery_signed.img
Step #3
Reboot into the bootloader and then choose to "clear storage" from the main screen and afterwards reset to factory defaults.
Step #4
Go back into the bootloader once step #3 is done and enter fastboot, connect your device and reflash your original custom recovery again. Your SD Card should be visible
Advanced Solution - If you do not want to wipe the data from your device
This method does not require reflashing the original recovery and factory reseting the whole phone. However, it still means that the info on your sd card will be lost. It also needs a rooted device.
This method does not require you to access your bootloader or use fastboot. You can do this while having your phone in custom recovery.
DO NOT ATTEMPT UNLESS YOU FEEL COMFORTABLE WITH THE INSTRUCTIONS. THERE ARE ALWAYS RISKS WITH FORMATTING. DO NOT HOLD ME RESPONSIBLE FOR BRICKED DEVICES. YOUR DEVICE IS LIKELY OUTSIDE OF WARRANTY ALREADY SINCE YOU WOULD HAVE UNLOCKED THE BOOTLOADER.
I have taken this solution from HTC One X forums namely from post 17 at http://forum.xda-developers.com/showthread.php?t=1647806&page=2
However, I have also confirmed (SneakyGhost's partition list for HTC One S) that the correct mmcblk0p for the HTC One S sd card is mmcblk0p36.
Step #1: Download the version of busybox listed below, unzip it and also put this in the folder with ADB before you get started. You only need to do this if you dont already have busybox installed on your HTC One S. Sometimes this busybox file can be found under /system/bin or /system/xbin if youve previously installed it. If so, replace the paths in the instructions below for that of your busybox. If you have busy box already installed in /system/bin , then you do not need to type in the paths since the adb shell automatically picks up programs in that folder
Step #2: Go to your command prompt in the folder with adb.exe . Connect your HTC One S to your computer and type
Code:
adb devices
and ensure your computer sees your HTC One S. This command should work even if you are in a custom recovery like TWRP or CW (but for gods sake, if your on CW, the first thing you should do is flash TWRP, but thats just an editorial opinion, lol).
Step #3: Type
Code:
adb push busybox /data/local/tmp
This pushes busybox to a temp folder on your HTC One S. Make sure you are pushing the busybox file and not the zip file. If you already have busy box installed you do not need to do this step. (you can delete it from this folder later if you like)
Step #4: Type
Code:
adb shell
to get into your linux shell. Then type
Code:
su
to get root access. Your command prompt should now be a # and not $.
Step #5: Type
Code:
chmod 755 /data/local/tmp/busybox
to fix permissions for busybox. You may not need to do this if you already have busy box installed with the correct permissions. If these instructions dont work with your version of busy box, try setting the permissions with this code but replace the path with the location of your busybox.
Step #6: Type
Code:
cat /proc/partitions
and just ensure you see mmcblk0p36. This is the sdcard partition for HTC One S
Step #7:Type
Code:
/data/local/tmp/busybox mkfs.vfat /dev/block/mmcblk0p36
Make sure you type this correctly. You dont want to format the wrong partition accidentally.
That should work. Pls let me know if it doesnt. If it doesnt work with your version of busybox just try using the one in the zip file below. Also remember, dont just push the zip file. Extract the busybox file from the zip and push that to your device instead.
Also, it may help to use adb through a custom recovery instead of being in your ROM (ie if it doesnt work when your phone is booted normally, try doing the steps with recovery loaded).
There are other methods to try too They would be:
Other Solutions
Other Method #1: Relocking your bootloader and using a compatible RUU with your phone. This will fully wipe your device
Other Method #2: If your computer sees your sdcard even if it cant open it when your device is connected, you can try formatting it that way (ie the way you would format any other drive on your computer)
Only use the busybox method if you are comfortable with it and if other methods have failed. You can learn more about the formatting command (ie mkfs.vfat) by googling it.

So if I got this right if I have busybox already I only have to do is step 7.

Almost, but yes, that is the key step. Although you would still want to open a terminal Window, either an adb shell or from the phone, and type su to get root, and double check to ensure the shell sees the partition. Also, I did hear in the one X forums that not every version of busy box worked. I would imagine an updated version would likely work though.
Sent from my HTC One S using xda premium

Step 4, a quicker way: adb shell su , get you into shell as root right away

AKToronto said:
Almost, but yes, that is the key step. Although you would still want to open a terminal Window, either an adb shell or from the phone, and type su to get root, and double check to ensure the shell sees the partition. Also, I did hear in the one X forums that not every version of busy box worked. I would imagine an updated version would likely work though.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Oh right hope I don't need it lol.
I think this should be moved to Q&A and replace the other sticky that's there.

Darknites said:
Oh right hope I don't need it lol.
I think this should be moved to Q&A and replace the other sticky that's there.
Click to expand...
Click to collapse
Im thinking it would be helpful to have this post there. Im not sure how I request to do that though. Should I PM a moderator?

AKToronto said:
Im thinking it would be helpful to have this post there. Im not sure how I request to do that though. Should I PM a moderator?
Click to expand...
Click to collapse
No idea but does sounds like a good start lol.

Darknites said:
No idea but does sounds like a good start lol.
Click to expand...
Click to collapse
I asked a moderater to review by clicking on the ! in the post, but I havent heard back yet. I also updated the post to be more n00b friendly too, and tried to cover off all sd card related issues.

AKToronto said:
I asked a moderater to review by clicking on the ! in the post, but I havent heard back yet. I also updated the post to be more n00b friendly too, and tried to cover off all sd card related issues.
Click to expand...
Click to collapse
Nice update. Ya I wish they hurry up with sorting it, the other one is a load of crap and this really should replace it.

Updated with a link to another good tutorial about pushing ROMs to the phone

Its like they don't care about stickys any more, come mods its about time this replaced the crappy one.

Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.

Steveh8204 said:
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Click to expand...
Click to collapse
Does your bootloaderscreen say "fastboot usb" anywhere? There is an option that you have to select in your bootloader called fastboot... If it says fastboot usb then you are connected, and you shouldnt get a waiting for device error.

AKToronto said:
Does your bootloaderscreen say "fastboot usb" anywhere? There is an option that you have to select in your bootloader called fastboot... If it says fastboot usb then you are connected, and you shouldnt get a waiting for device error.
Click to expand...
Click to collapse
yea I got into the bootloader and then fast boot. ive managed to sort it now, for some reason my pc was the problem, I had to reboot my computer after a command window prompt otherwise I just got the waiting for device screen.
typical really, my laptop and phone both conspiring against me.
eventually managed to flash another recovery which did see my sdcard so all is good now.
thanks for your reply though!

AKToronto said:
For those who may be flashing ROMs, cannot mount the SD Card any more, and may have accidentally corrupted their SD Card, here are some helpful steps.
Click to expand...
Click to collapse
Dude, this works flawless!
Thought I had a soft-brick, but your instructions bring back my sd-card!
I choose the "advanced Option", it works fine....
Typing su-command generated an error message, but the other steps still functioned....
I will place link in section "helpfull links" in my signatur
Big THX to you good sir, ...

Steveh8204 said:
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Click to expand...
Click to collapse
Just format your phone using your PC... That's all you need to do...all those steps are overkill... Bootloader on phone... Connect to pc .. Navigate to devices on PC and format your phone...then flash recovery like stated above..
Sent from my One S using xda premium

$droyd$ said:
Just format your phone using your PC... That's all you need to do...all those steps are overkill... Bootloader on phone... Connect to pc .. Navigate to devices on PC and format your phone...then flash recovery like stated above..
Sent from my One S using xda premium
Click to expand...
Click to collapse
Some people had reported not being able to see their phone from their PC no matter what they tried... Hence the advanced steps

Dude add S3 stock recovery please.

Darknites said:
Dude add S3 stock recovery please.
Click to expand...
Click to collapse
Good point Darknites. Thank you. Do you have a link to S3 stock recovery? I dont seem to have one handy... But I did edit the OP to make that point a bit clearer (that the link is for S4 devices). Thanks again bud. Good catch.

AKToronto said:
Good point Darknites. Thank you. Do you have a link to S3 stock recovery? I dont seem to have one handy... But I did edit the OP to make that point a bit clearer (that the link is for S4 devices). Thanks again bud. Good catch.
Click to expand...
Click to collapse
Nope but a RUU will have it.

[Super Guide] Alcatel ideal (4060A)

Code:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DISCLAIMER
I am not responsible for bricks, cats being both alive and dead, heat death of the universe, etc. I've attempted to minimize the chance of damage, but you will use this guide at your own risk.
Thanks to [mention]ejwith9953[/mention] for getting TWRP working correctly
Thanks to [mention]forgottonhacker[/mention] for proofreading and formatting
ABOUT
WINDOWS ONLY GUIDE
THIS GUIDE IS FOR THE PEOPLE SEEKING TO INSTALL TWRP AND OBTAIN A FIX FOR SOFT-BRICKED DEVICES
STEP 1
On a DESKTOP:
Download CURE_4 and extract to desktop (or a folder to your preference).
[Download Links at Bottom of Post]
On your PHONE:
Go to Settings > About phone > tap build number, till it says your a developer.
Go to Settings > Developer Options and enable OEM unlock, and USB debugging
Reboot Device
STEP 2
Connect Device to PC
Open your extracted folder and run START_HERE.bat
Let it run, it will copy files, execute temp root exploit, and open a new CMD window.
In the new window, copy/paste commands individually.
Code:
adb shell
run-as -s1
su
dd if=/data/local/tmp/twrp.img of=/dev/block/mmcblk0p25
When you see the following:
Code:
26404+0 records in
26404+0 records out
Get ready to pull out the battery ( reboot recovery does NOT work )
Put the battery back in and hold the PWR and VOL UP at the same time, when you see Alcatel splash let go of power but continue to hold volume up.
Say hello to TWRP!
STEP 3
Now we are going to install SuperSU it’s easy from here don’t fret!
IMPORTANT
BACKUP /SYSTEM PARTITION IN TWRP AND MAKE A COPY ON YOUR PC
Now that you have a backup go back and tap install. Tap on "up a level" then sdcard.
Find SuperSu.zip and swipe to install!
Reboot system! (this may take a few minutes so don’t freak out)
Verify that SuperSu got installed.
Go back to the extracted folder on your computer and run CLEANUP.bat
SOFT FIX
Boot up to custom recovery tap wipe > advanced wipe
Select Dalvik cache and Cache, then SWIPE to wipe
Go back to the Home Screen
Tap Advanced > fix permissions and Swipe
REBOOT AND ENJOY
If this fix did not work for you please do contact me as I have another method, I will be putting up a debloated version of the ROM soon.
I will be adding more to the guide, so make sure to turn on your notifications!
DOWNLOADS
Stock-ish ROM EXTRACT FROM ZIP FIRST! then flash as /system
password: fax
Dropbox  Google  Box.net  Mega
​EDIT: On payday going to buy another one of these phones for stock firmware.

Reserved

Broken Download Link
The Link to download the Code-4 package is broken, and it makes me oh-so-sad!!! Help!

WowTheDog said:
The Link to download the Code-4 package is broken, and it makes me oh-so-sad!!! Help!
Click to expand...
Click to collapse
try now. also "cure-4" XD

Cure-4 download link not working.
I tried to say...
faxanidu said:
try now. also "cure-4" XD
Click to expand...
Click to collapse

The cure-4 thing is missing again, can we get a hold of that?

Omg everyone flagging as malware give me a bit

Hey, it all worked, I had a soft bricked phone, and its booting now. I did the commands in OSX, I just opened the START_HERE.bat and saw your adb commands. The only hangup was that I couldn't push Supersu.zip to /sdcard/ because it wasn't writable for some reason, but I just pushed it to the tmp path from the other commands instead.
Thanks so much!

Good brother my problem is that I have my soft brick phone and I do not know what to do to revive it, do you have any idea how to repair it?

ericcorp said:
Hey, it all worked, I had a soft bricked phone, and its booting now. I did the commands in OSX, I just opened the START_HERE.bat and saw your adb commands. The only hangup was that I couldn't push Supersu.zip to /sdcard/ because it wasn't writable for some reason, but I just pushed it to the tmp path from the other commands instead.
Thanks so much!
Click to expand...
Click to collapse
Odd it pushes supersu automatically. Might had something to do with the soft brick. Your welcome though! Spread the word!

sanpuyon said:
Good brother my problem is that I have my soft brick phone and I do not know what to do to revive it, do you have any idea how to repair it?
Click to expand...
Click to collapse
Follow guide fixes soft brick also just reboot it. let it sit awhile then plug it in. Should be a able to get ADB shell

faxanidu, I just tried on my dead device and I got twrp :good: but won't complete boot after fixing permission tho. Hey that's good enough for me, congrats on what you did! Just gonna wait till a rom gets put up.
To get started I did have to do some steps in oem recovery like I said from the other thread, otherwise my device shows as unauthorized tho, enable adb, then rock volume back and forth till I get mounted /system, then hit reboot. It seems I've tried just doing one or the other but it would still be unauthorized. Just sayin, and again like I told you I don't really know what I'm doing
Thanks again, and if you have any further advice or tips, I'm all ears
edit: I didn't have supersu show up either but I put it on an sdcard and installed it that way.

i am too afraid to try this, is this safe? if i brick my phone, how do i flash stock firmware
---------- Post added at 03:24 AM ---------- Previous post was at 02:59 AM ----------
faxanidu said:

Good news everyone! I have built a massive guide for the alcatel ideal! install custom recovery and more now! also fix for soft bricked phones! just follow this guide.
WIndows only
Thanks to ejwith9953 with getting TWRP working correctly, he is the bomb!
So dont forget to thank him!
STEP 0
DISCLAIMER! I am not responsible for bricks, cats being both alive and dead, heat death of the universe, etc. Ive minimized the chance of damage as much as possible, but still use this guide at your own risk.
​
STEP 1​​Goto settings > about phone > tap build number, till it says your a developer.
Goto settings > developer Options. slide on OEM unlock, and USB debugging
Download CURE_4 to your computer and extract folder to desktop (or somewhere).
Reboot phone.
Links are at bottom!
STEP 2​​Open your extracted folder, run START_HERE.bat
Let it run, it will copy files, execute temp root exploit, and open a new CMD window.
In the new window type in these codes from top to bottom letting each one finish. ( or copy/paste )
Code:
adb shell
run-as -s1
su
dd if=/data/local/tmp/twrp.img of=/dev/block/mmcblk0p25
When you see:
26404+0 records in
26404+0 records out
your ready to pull out the battery ( reboot recovery does NOT work )
Put the battery back in and hold the PWR and VOL UP at the same time, when you see alcatel let go of power but continue to hold volume up.
Welcome to custom recovery my friends!
STEP 3​​Now we are going to install SuperSU its easy from here dont fret! but first!
click backup, under partitions uncheck everything EXCEPT system. Now swype to backup.
Now that you have a backup go back and click install. click "up a level" then sdcard.
scroll down and click SuperSu.zip. Swipe to install! Now Reboot system! (this may take a few minutes so dont freak)
check that SuperSu installed, did it? great! go back to the extracted folder on your computer and run CLEANUP.bat
STEP 4 -SOFTFIX ONLY​​Boot up to custom recovery click wipe > advanced wipe
checkmark Dalvik cache and Cache, the SWIPE to wipe ( sounds dirty )
now click BACK all the way to main screen. now click advanced.
click fix permissions And Swipe. Now REBOOT. hopefully that will boot your phone if not let me know. i dont
have an extra one to purposfully softbrick to test. but ill have a debloated pre rooted ROM for you
to use soon regardless
More to the guide will be coming, for now this is the basics. im going to bed see you all later!
LINKS!
password: fax
Dropbox  Google  Box.net  Mega
​
EDIT: 4 links encrypted
Click to expand...
Click to collapse
faxanidu said:
Click to expand...
Click to collapse
Thank you! i am now happily running twrp, though with some mods, i rooted with kingroot first then ran the commands
Now we wait for lineage os or cm13

For some reason I can't do this on my working phone. when it comes to the "getting uid" screen, everything that runs says "missing second argument" then I try entering the commands it says "run-as: Package '-s1' is unknown"?

scohut said:
For some reason I can't do this on my working phone. when it comes to the "getting uid" screen, everything that runs says "missing second argument" then I try entering the commands it says "run-as: Package '-s1' is unknown"?
Click to expand...
Click to collapse
What the? Never had that problem can't reproduce plz send screenshot

faxanidu said:
Good news everyone! I have built a massive guide for the alcatel ideal!
Click to expand...
Click to collapse
Thank you so much for this.
I started and misread the text as a lowercase "L" instead of the number one for the "run-as -s1" part of the code. I wasn't sure how to correct it when I got an error, so I started over and ran the START_HERE.bat again. When the new cmd window opens, I can't type anything. It reads:
# Device:Alcatel_4060A
-Getting uid 0->Ok.
-Checking permissive run-as.->Ok
# turn off/on the bluetooth.....................................................
..............←[s←[0;34m
[email protected]:/data/local/tmp #
Click to expand...
Click to collapse
I'm not sure how to start over to get back on track for the adb shell code.
I know, it's pretty bad that I didn't get past the first part of Step 2. Any help is appreciated.

faxanidu said:
What the? Never had that problem can't reproduce plz send screenshot
Click to expand...
Click to collapse
this..

Rush-O-Matic said:
Thank you so much for this.
I started and misread the text as a lowercase "L" instead of the number one for the "run-as -s1" part of the code. I wasn't sure how to correct it when I got an error, so I started over and ran the START_HERE.bat again. When the new cmd window opens, I can't type anything. It reads:
I'm not sure how to start over to get back on track for the adb shell code.
I know, it's pretty bad that I didn't get past the first part of Step 2. Any help is appreciated.
Click to expand...
Click to collapse
That happens rarely just reboot and start again

faxanidu said:
That happens rarely just reboot and start again
Click to expand...
Click to collapse
And it reads what?

scohut said:
this..
Click to expand...
Click to collapse
Looks like exploit.sh for corrupted or something plus if you have any mods like exposed might interfere with it. The script dumps info it need to patch see policy then creates run-as with info.
Edit: I'm basically using dirty cow exploit. Works on everything