Database Info

Omfg i did it!!! Omfg i dit it!!! Rogers htc magic superhero rom!!!!

WOW AFTER AGES>>>>>>> FINALLY!!!! YAY!!!
First i would like to thank every one who made this possible , im sorry i dont know ur names..
This is what i did i dont know if itll work for every one but fingers crossed....
1. its like the normal rooting procedure except with the boot.img that i have!!! U need the sdk for this to work!!
2. Download superhero rom v2: http://www.megaupload.com/?d=3Y02RZAT
3. rename as update.zip and place on sdcard.
4. Shutdown phone.
5. Download: http://rapidshare.com/files/248983573/recovery-RAv1.0H.img
6. place this img in the tools folder of the sdk.
7. Start phone in fastboot mode (power+voulme)
8. from the fastboot menu in cmd restart phone with the boot image provided above. (c:\sdk\tools fastboot boot recovery-RAv1.0H.img).
UPDATE:: DO A NANDROID BACKUP THEN USE THE BOOT.IMG THAT WAS BACKED UP BY NANDROID (ON YOUR SD CARD) FOR STEP NUMBER 12/13/14..
9. wipe data and update .
10. reset phone but remove battery when the rogers sign comes on.
11. go to flashboot mode again.
12. .......... use backed up boot.img
13. place this in the tools directory of the sdk
14. in cmd again flash the boot image (c:\sdk\tools fastboot flash boot boot.img)
15. Now reboot and thats it ur done!!!!
NO WIFI!!!! NO BLUETOOTH IN THE SUPER HERO ROM AM TRYING OTHER ROMS... I THINK THIS METHORD SHOULD WORK AN ALL ROMS NOW... maybe not....
after trying for a while only superhero works not the hero by haykuro... dunno why it keeps restarting at the htc splash screen....

waiting nice

Thanks for using my recovery! lol

reply: like i said in the begenning thnx to all tht helped....
ps the daldroid should work as well

good job man, very interested in this but gotta wait till wifi works.

i think wifi dosent work becase superhero was for dream not magic... but the ui is sweet!
can someone help to enable wifi and bluetooth??

Oh wow, thanks. I will shortly follow your instructions.

lol to fix wifi find out whos boot.img you stole rolleyes and take the wlan.ko from /system/lib/modules and throw it over the one in the build.
sign, package, fly.
EDIT:
also, in default.prop (within the boot.img) change it ro.secure to 0 if you want rooted adb shell
Code:
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
heh.. this is why sometimes you should wait before just throwing an incomplete build out

haykuro said:
lol to fix wifi find out whos boot.img you stole rolleyes and take the wlan.ko from /system/lib/modules and throw it over the one in the build.
sign, package, fly.
EDIT:
also, in default.prop (within the boot.img) change it ro.secure to 0 if you want rooted adb shell
Code:
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
heh.. this is why sometimes you should wait before just throwing an incomplete build out
Click to expand...
Click to collapse
That is exactly why I am waiting for a proper release to come out.......hint
LOL

it was the boot image i backed up myself... so what do i do exactly??? I kinda got the first part, used adb pull and push to copy over the file, but the edit just flew way oover my head.....
ps haykuro can you use this to make a biuld?? alsoo can u pls show me how to sign a package searched everywhere couldnt find out how...
re: TRIED THE wlan.ko file transfer still it says failed to start wlan!!!

Killadude said:
reply: like i said in the begenning thnx to all tht helped....
ps the daldroid should work as well
Click to expand...
Click to collapse
Yes, it works. Since June 8th ;-)
But daldroid-recovery is really a quick-mod of haykuro's one, so thank him (and others, I only mentioned him and a few others in a readme file in the ramdisk image)
I'm happy to see that someone else started releasing roms for pvt 32A board, because I was really busy and used all of my sparetime to try to rebuild a working kernel (Hero is running on my phone since 3 weeks, untested-bluetooth-fix, wlan fix, but still no working kernel, no iptables, so no release).
Going abroad for a few days, I'm sure I'll come back and be able to download your (or Haykuro's) new rom with a new built-from-sources-working-kernel for pvt32A ;-)
Greetings
Daldroid

Killadude said:
it was the boot image i backed up myself... so what do i do exactly??? I kinda got the first part but the edit just flew way oover my head.....
ps haykuro can you use this to make a biuld??
Click to expand...
Click to collapse
Im pretty sure he has
http://www.getyourdroidon.com/root/hero-sapphire-signed.zip
or did you mean a rogers specific one?

- Wifi and BT cannot start in this rom

yup one specific for rogers cuz our is the only goddam magic that couldnt until today be rooted!!

I just followed your instructions for the superherov2 rom and I ran into some problems.
I cannot upload the boot.img
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now my phone is stuck with the Rogers logo. Any ideas on how about I can go on fixing this problem.

First u could try in fastboot mode re booting to the recovery img boot..... once in there wait for a minute, connect usb to computer and in cmd go to tools folder and type
adb devices, if u see a serial underneath then type
adb push boot.img /data/local/boot.img
with the image you downloaded if this fails then, ill redriect u to a link Thanks to daldroid itll help you run the origanal magic rom, without the rogers crap installed on it. Just not you have to set the api settings in the menu to:
name: rogers
address: internet.com
to acess the rogers edge/3g internet.
http://www.arbitraryuser.com/blog/2...-south-africa-to-get-android-market-and-more/
just skip to instruction number 8 in the step by step instructions
PS IF U DID DO A NANDROID BACKUP JUST PLACE THE BOOT.IMG & SYSTEM.IMG THAT WERE BACKED UP INTO THE TOOLS FOLDER AND TYPE IN CMD
FASTBOOT FLASH BOOT BOOT.IMG
FASTBOOT FLASH SYSTEM SYSTEM.IMG
I had to do that many a times because most of the roms failed to install...
tell me if any of that helps...
PS thanks for the test i have now changed the instructions on the main page..

Killadude said:
First u could try in fastboot mode re booting to the recovery img boot..... once in there wait for a minute, connect usb to computer and in cmd go to tools folder and type
adb devices, if u see a serial underneath then type
adb push boot.img /data/local/boot.img
with the image you downloaded if this fails then, ill redriect u to a link Thanks to daldroid itll help you run the origanal magic rom, without the rogers crap installed on it. Just not you have to set the api settings in the menu to:
name: rogers
address: internet.com
to acess the rogers edge/3g internet.
http://www.arbitraryuser.com/blog/2...-south-africa-to-get-android-market-and-more/
just skip to instruction number 8 in the step by step instructions
PS IF U DID DO A NANDROID BACKUP JUST PLACE THE BOOT.IMG & SYSTEM.IMG THAT WERE BACKED UP INTO THE TOOLS FOLDER AND TYPE IN CMD
FASTBOOT FLASH BOOT BOOT.IMG
FASTBOOT FLASH SYSTEM SYSTEM.IMG
I had to do that many a times because most of the roms failed to install...
tell me if any of that helps...
PS thanks for the test i have now changed the instructions on the main page..
Click to expand...
Click to collapse
OK, if I try to use adb, it gives me an error stating that the device cannot be found.
I tried using my own boot.img, but I got the same error. Any ideas?

hotweiss said:
OK, if I try to use adb, it gives me an error stating that the device cannot be found.
I tried using my own boot.img, but I got the same error. Any ideas?
Click to expand...
Click to collapse
When you are in fastboot mode, "adb devices" won't show it. I THINK he meant "fastboot devices". It should show your devices in fastboot mode

OK, I used Ubuntu to fastboot my boot.img and that has now worked. I have one question now, how do you enter your Rogers data information. The ROM doesn't make a data connection with Rogers.

hotweiss said:
OK, I used Ubuntu to fastboot my boot.img and that has now worked. I have one question now, how do you enter your Rogers data information. The ROM doesn't make a data connection with Rogers.
Click to expand...
Click to collapse
Settings -> Wireless Controls -> Mobile networks -> Access Point Names
EDIT: read the NEXT post for the correct settings to put into the fields

[Recovery]cwm-5.0.2.3-liberty-agse and stock cwm-5.0.2.3-liberty

Liberty still has something no other device has - ARIA!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
..........
Downloads:
cwm-5.0.2.3-liberty-agse.zip AGSE (ARIA) Edition - with cap key lights enabled
cwm-5.0.2.3-liberty.zip Stock Clockworkmod 5.0.2.3 - with cap key lights enabled

attn1 said:
Liberty still has something no other device has - ARIA!
Download: cwm-5.0.2.3-liberty-agse.zip
Click to expand...
Click to collapse
and apparently , interesting background images
*****
I am still on v2.5.0.1 - and help on how to install this img?

Thanks so much attn1!
Edit: found this for instructions, would this do?.....
HTML:
http://forum.xda-developers.com/showthread.php?t=1122694

here's 2 ways to do it:
if you have s-off:
boot phone into fastboot mode
hook phone to computer with usb cable
ON COMPUTER:
unzip cwm-5.0.2.3-liberty-agse.zip
command prompt
fastboot flash recovery cwm-5.0.2.3-liberty-agse.img
without s-off: (this is what I did, didn't have a USB cable handy)
terminal emulator
su
cd /sdcard/download
unzip cwm-5.0.2.3-liberty-agse.zip
flash_image recovery cwm-5.0.2.3-liberty-agse.img

tommyguns818 said:
Thanks so much attn1!
Edit: found this for instructions, would this do?.....
HTML:
http://forum.xda-developers.com/showthread.php?t=1122694
Click to expand...
Click to collapse
yep, if you are s-off with Revolutionary or AlpharevX.
Nutshell69 said:
and apparently , interesting background images
Click to expand...
Click to collapse
that's Aria herself.

Looking forward to the HTC Jenna
Sent from my Liberty using XDA App

i was wondering.....i've got s-off but no computer around me at the moment. is there a way to install this through the terminal app? I see sObe did it via terminal way but im not sure if he's s-off or not.
EDIT: I went for it and did it through terminal just like sObe and I have s-off. Worked like a charm. Thanks guys!!!

When I chose internal card I get
E:Can't mount /emc/
???

s0be said:
here's 2 ways to do it:
without s-off: (this is what I did, didn't have a USB cable handy)
terminal emulator
su
cd /sdcard/download
unzip cwm-5.0.2.3-liberty-agse.zip
flash_image recovery cwm-5.0.2.3-liberty-agse.img
Click to expand...
Click to collapse
tried this twice still failing :S
do i need to be running a certain rom?
I get through su just fine, i cd to the /sdcard/download (where my img is)
type in the flash_image .....
getting sh: flash_image: command not found
so looks like the terminal emulator isnt getting the PATH correctly
echo $PATH returns
/data/local/bin:/sbin:/system/sbin:/system/bin:/system/xbin
ug.

If your doing it through terminal, you need to make sure that your doing it exactly as shown in s0bes post. Also make sure that you have your new cwm 5.0.2.3 download in the download folder on your sd card.

Nutshell69 said:
tried this twice still failing :S
do i need to be running a certain rom?
I get through su just fine, i cd to the /sdcard/download (where my img is)
type in the flash_image .....
getting sh: flash_image: command not found
so looks like the terminal emulator isnt getting the PATH correctly
echo $PATH returns
/data/local/bin:/sbin:/system/sbin:/system/bin:/system/xbin
ug.
Click to expand...
Click to collapse
probably any aosp or cm based rom would work. the stock cleaned up roms, not so much.

Aside from the background thing, what advantages does this recovery have over 2.5.1.7? Is it faster? are the backups compatible?
T

s0be said:
probably any aosp or cm based rom would work. the stock cleaned up roms, not so much.
Click to expand...
Click to collapse
yea - i think thats the problem - not running a cm rom - will install 209 and try
thanks
***EDIT***
Installed CM 211 ROM
did these steps
terminal emulator
su
cd /sdcard/download
unzip cwm-5.0.2.3-liberty-agse.zip
flash_image recovery cwm-5.0.2.3-liberty-agse.img
getting errors :
mtd: erase failure at 0x00000000 (I/O error)
.......
thoughts?

Also curious of the benifit vs backward or forward compatibility gotchas. Anyone?
Edit. Tried to instal and get the same errors as above. S-on
Sent from my Liberty using XDA App

Nutshell69 said:
yea - i think thats the problem - not running a cm rom - will install 209 and try
thanks
***EDIT***
Installed CM 211 ROM
did these steps
terminal emulator
su
cd /sdcard/download
unzip cwm-5.0.2.3-liberty-agse.zip
flash_image recovery cwm-5.0.2.3-liberty-agse.img
getting errors :
mtd: erase failure at 0x00000000 (I/O error)
.......
thoughts?
Click to expand...
Click to collapse
Perhaps you can't flash a recovery from the rom without s-off? I'm not an expert to say that's the case... If so, you have to go through the whole unroot and re-flash procedure, which I forgot the steps to LONG ago. You might try rebooting into recovery, and using adb shell to do those steps. If you don't have ADB available, this may be beyond an easy upgrade.
I know of no advantages of this recovery over 2.5, btw.

SoCalHTCFuze said:
Also curious of the benifit vs backward or forward compatibility gotchas. Anyone?
Edit. Tried to instal and get the same errors as above. S-on
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
s0be said:
Perhaps you can't flash a recovery from the rom without s-off? I'm not an expert to say that's the case... If so, you have to go through the whole unroot and re-flash procedure, which I forgot the steps to LONG ago. You might try rebooting into recovery, and using adb shell to do those steps. If you don't have ADB available, this may be beyond an easy upgrade.
I know of no advantages of this recovery over 2.5, btw.
Click to expand...
Click to collapse
In fact, you cannot flash a recovery without S-OFF, unless you use the original unrevoked tool and select custom recovery (the original unrevoked only managed to install a custom recovery which was good enough at the time).

The whole point of S-OFF is that you can flash the system partition. Like Gene said, if you don't have S-OFF, you'd need to unroot and use unrevoked again.
If you do have S-OFF, it's easy:
(OS X)
md5 /path/to/cwm-5.0.2.3-liberty-agse.img (confirm md5 sum)
./adb devices (confirm you're connected)
./adb reboot bootloader
./fastboot-mac devices
./fastboot-mac flash recovery /path/to/cwm-5.0.2.3-liberty-agse.img
./fastboot-mac reboot
./adb reboot recovery (wait to hit enter until the boot animation starts)
I haven't used it yet but I hear the backups are faster in 5.x

^^^ 5.0.2.3 is a little faster. I saw the new option to fix permissions in the recovery and tried it. Man it took like 30 min to run and chewed about 60 percent of battery. From now on I'll just use ROM manager. It never failed me and is way quicker. On further note....I like it. Go miss aria!

s0be said:
If so, you have to go through the whole unroot and re-flash procedure, which I forgot the steps to LONG ago.
Click to expand...
Click to collapse
Just so people in this situation are aware, you do not have to "unroot" your phone first. Just run Unrevoked a second time on your device and it will overwrite the recovery with the one you select.

drumist said:
Just so people in this situation are aware, you do not have to "unroot" your phone first. Just run Unrevoked a second time on your device and it will overwrite the recovery with the one you select.
Click to expand...
Click to collapse
egads - got this error
Error: failed to get root. Is your firmware too new?

[Guide] How to Downgrade Latest Hboot 2.00.0002>> without using HTC Dev V2

This method works for software version 2.11 and above and doesn't work for version 2.10 below.. Please use zegRush if this doesn't work for you.
FOR PHONES THAT ARE NOT ROOTED
Note: For locked bootloaders only. Do not use Htc dev prior to using this guide.
First thanks to:
1. mtothearkus
2.petarpLab..
3.jcase for TacoRoot..
4. amidabuddha
5.zryvffn (misc_version_universal)
I AM NOT RESPONSIBLE FOR ANYTHING THAT MAY HAPPEN TO YOUR DEVICE..
This was tested on latest OTA ASIA 2.15.xx with latest Hboot 2.00.0002.
Latest 2.15 cannot be rooted with zegRush so did some research..
Things Needed:
1.tacoroot
2.misc_version (download attachments below)
3.OLDEST RUU for your "REGION/ BRAND".. i repeat, specific region to avoid customer ID error.
4. adb (you know how it works)
5. phone in USB debugging mode.
STEPS:
1. download tacoroot and misc and put all files in your desired directory.
2. Run terminal and change location to where you files are.
3. now type:
Code:
adb push tacoroot.bin /data/local/tmp/tacoroot
adb push misc_version /data/local/tmp/
4.After pushing all the files, run tacoroot by typing:
Code:
adb shell
chmod 777 /data/local/tmp/*
/data/local/tmp/tacoroot --setup
5. After this commands your phone "REBOOT" the phone to recovery. Now press vol up then power then REBOOT to boot the phone normally. Wait till it boots completely and then type:
Code:
adb shell
/data/local/tmp/tacoroot --root
6.This command will gets you out of adb shell.. so we need to get back to adb shell and you will see "#" sign..meaning you are temp rooted and we can then proceed to changing MISC_VERSION:
Code:
adb shell
cd /data/local/tmp
./misc_version -s 1.27.405.6
7. After its done you can now flash your "REGION/ BRAND specific RUU".
8. After your done with RUU. Proceed to http://revolutionary.io..
Happy Flashing
FOR ROOTED PHONES
*Proceed with:
STEP 3
STEP 6
STEP 7
STEP 8
-Done
*Added misc_version_universal thanks to zryvffn

Thx you are marvelous! I will try it later
Sent from my HTC Desire S using XDA App

scan6 said:
Thx you are marvelous! I will try it later
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
Say if you did it by this procedure.

Yes! it works very wellwith my version 2.13 to1.47
It's quite easy to do it
Thx a lot!
Sent from my HTC Desire S using XDA App

Thx for the guide. Worked great. I downgraded from 2.15 to 1.31 asia wwe.
From my Desire S Using XDAP

Hey man, I've added your guide to my thread http://forum.xda-developers.com/showthread.php?t=1186401
Just to let you know. Thanks for the great guide.

nodeffect said:
Hey man, I've added your guide to my thread http://forum.xda-developers.com/showthread.php?t=1186401
Just to let you know. Thanks for the great guide.
Click to expand...
Click to collapse
hey dude thanks.. btw this guide is for those who can't downgrade using mtothearkus method.. those recent 2.15.x versions..its just the same but it uses different root methods.. all credits to mtothearkus..appreciate it dude..thanks..

Thanks, noted.

After rebooting phone from recovery, typing
adb shell
/data/local/tmp/tacoroot --root
Answer:
Rebooting into root.
cannot create /data/local.prop: permission denied
and phone restart...
Desire S, Android 2.3.5, Hboot 2.00.0002

qpkqkma said:
After rebooting phone from recovery, typing
adb shell
/data/local/tmp/tacoroot --root
Answer:
Rebooting into root.
cannot create /data/local.prop: permission denied
and phone restart...
Desire S, Android 2.3.5, Hboot 2.00.0002
Click to expand...
Click to collapse
Dude what your software version number? brand if any?.. if this root doesnt work.. try zegRush method..
or try this
Update to latest available firmware, then try.
If that fails, do a factory reset and try.

Software : 2.10.401.8
Kernel: 2.6.35.10
Non-branded, lastest firmware.
Late I´ll try factory reset.

qpkqkma said:
Software : 2.10.401.8
Kernel: 2.6.35.10
Non-branded, lastest firmware.
Late I´ll try factory reset.
Click to expand...
Click to collapse
Zergrush method from mtothearkus's thread should work for you

qpkqkma said:
Software : 2.10.401.8
Kernel: 2.6.35.10
Non-branded, lastest firmware.
Late I´ll try factory reset.
Click to expand...
Click to collapse
That's it.. hehe. 2.10 is an old firmware.. ASIAN OTA is 2.15.. so try the zegrush method.. this tut was developed for those who can't root using the zegRush..thanks amidabuddha..=)

Signed up here at xda just to say that this worked nicely on my Desire S.
I had difficulty making the ADB code given by shadi22 work at first, but after redoing them and just copy pasting them in terminal, they worked. My Desire S also had an Asia 2.15 ROM and 2.00.0002 Hboot. Used the Asia WWE 1.48.707.1 RUU to downgrade the HBOOT after changing the misc-version and tacorooting, then Revolutionary all the way
At first, I thought that I made a mistake choosing this phone (My Desire's display got borked and SISPH's repair quote was way too expensive for a nearly two year old device ) because of the need to downgrade the hboot before getting S-OFF, but shadi22's method is probably the most elegant of all the S-OFF methods on 2.00.0002 devices

HAHAHA.. thanks dude.. Anyway.. SISPH are full of dumb people.. i had problem with my device too.. a green dot on an LCD screen. my phones on warranty but never had it repaired since they have no replacement part yet. so give up on the idea for that damn SISPH.. They had the worst customer service.. they should never have been contracted with HTC on the first place.. No HTC on my next phone. The reason to go with HTC was mainly for the developers in this beloved site.. But now im seeing great dev from other phone section..=)

Try to do a zergRush method. Everything run fine, i do steps 1-5, do a step 6 (run RUU etc etc.) but RUU say me error updating, phone stuck on HTC logowhen i pull out cable it load in HBOOT and say "RUU Security Fail ! Update Fail!".
Sucks.....im downloading RUU with SW 2.10.401.8 to recover phone.....
Any other method ?

Hey guys,
So I tried this method but encountered the following issue as shown in the image below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does anyone have any ideas as to where I have went wrong?
Kind regards,
DJM.

dontjudgemekk said:
Hey guys,
So I tried this method but encountered the following issue as shown in the image below:
Does anyone have any ideas as to where I have went wrong?
Kind regards,
DJM.
Click to expand...
Click to collapse
Off hand I would say that /data/local/tmp was not empty before you started and contains more than just the 2 files you copied there, thus the command chmod 777 /data/local/tmp/* is failing.
Why not just do 2 chmod commands for the 2 files you copied?

tpbklake said:
Off hand I would say that /data/local/tmp was not empty before you started and contains more than just the 2 files you copied there, thus the command chmod 777 /data/local/tmp/* is failing.
Why not just do 2 chmod commands for the 2 files you copied?
Click to expand...
Click to collapse
How would I clear the /data/local/tmp directory?
Can you phrase what you mean by performing 2 chmod commands for the 2 files better? I dont understand what you mean unfortunately. Are you referring to the tacoroot.bin and misc_version files?

dontjudgemekk said:
How would I clear the /data/local/tmp directory?
Can you phrase what you mean by performing 2 chmod commands for the 2 files better? I dont understand what you mean unfortunately. Are you referring to the tacoroot.bin and misc_version files?
Click to expand...
Click to collapse
Yes after you create the adb shell and get the $ prompt type:
chmod 777 /data/local/tmp/misc_version
chmod 777 /data/local/tmp/taco root.bin

How-To flash your boot.img on Mac OSX

First of all, I think this tutorial is needed since I see this question pop up everywhere and most flashing/rooting tutorials are for Windows. I found myself struggling a lot with flashing on mac since it so much easier on Windows and there are plenty of tutorials on the net for windows but not so much or very poorly for Mac . So I hope this clears out much of your questions on how to flash for a mac.
Download the mac version of the Android SDK from the website.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Unzip it and place it on your harddrive where you will never delete it. For example:
Code:
Users/your_username/Documents/Android/android-sdk-macosx
Go to the unzipped folder and then navigate to tools. Double click android and let it run. It will open terminal windows and the android sdk itself. Let it load
It will look like this:
Now install the tools, platform tools and I also installed the sdk since 4.0.
Click to expand...
Click to collapse
Download the fastboot files (boot.img and fastboot-mac) here.
Unzip them and place them in the platform-tools in your android-sdk directory for example:
Code:
Users/your_username/Documents/Android/android-sdk-macosx/platform-tools/
Now you download the ROM you want. Here are the most of them located for the HTC One S and you copy it to your phone.
Boot into recovery. If you don't know how to do it, here is a short guide:
Power Off while holding the down volume button
You are into bootloader now if it restarted
Navigate to recovery with your volume buttons
Press the power button to select recovery
Click to expand...
Click to collapse
Then you do the following steps:
Wipe data/factory reset
Wipe cache partition
Install zip from sdcard
choose zip from sdcard
Then you choose the zip you downloaded and where you put it on your phone
Let it install
Click to expand...
Click to collapse
If it is installed:
Turn your phone off while holding the down volume button
Let it boot into bootloader
Connect your phone to your Mac
Select fastboot in bootloader
It will change to fastbootusb
Click to expand...
Click to collapse
Open up Terminal on your mac and type following commands:
cd /Users/your_username/Documents/Android/android-sdk-macosx/platform-tools
chmod +x fastboot-mac
/Users/your_username/Documents/Android/android-sdk-macosx/platform-tool/fastboot-mac flash boot boot.img
You could replace "/Users/your_username/" with "~/" (Option + N). (Thanks to m1schi)
Click to expand...
Click to collapse
let it run and it should show you something like this:
Now reboot and enjoy your flashed ROM!
Note: if this helped you in any means: please leave a thanks.

You could replace "/Users/your_username/" with "~/" (Option + N). This always links to your home directory.

m1schi said:
You could replace "/Users/your_username/" with "~/" (Option + N). This always links to your home directory.
Click to expand...
Click to collapse
Oh thank you! will put it in there.
Sent from my HTC One S using XDA

Nice tutorial, but there is a shorter way.
You don't need to install the Android SDK (unless you want to get involved with android development) you just need a working copy of Fastboot for mac and run it from terminal
That's how I have always done it. Not only on my One S, but also on all the others HTC phones I've Owned
https://dl.dropbox.com/u/1012262/fastboot-mac

solracarevir said:
Nice tutorial, but there is a shorter way.
You don't need to install the Android SDK (unless you want to get involved with android development) you just need a working copy of Fastboot for mac and run it from terminal
That's how I have always done it. Not only on my One S, but also on all the others HTC phones I've Owned
https://dl.dropbox.com/u/1012262/fastboot-mac
Click to expand...
Click to collapse
Well, if they want to work with adb and such they need to download the sdk. So yeah, I know it was a shorter way but i thought: give it the full on way for people so they are sure.

ive done this 14 times and every single time it says no such file or directory this does not work

chuuw33 said:
ive done this 14 times and every single time it says no such file or directory this does not work
Click to expand...
Click to collapse
You can use the Boot Flash Script from my TrickDroid thread which has MacOS support

You can also add the path of the folder in which the fastboot binary is located in ~/.bash_profile
In your guide that would be /Users/your_username/Documents/Android/android-sdk-macosx/platform-tool/ so with a command:
Code:
echo /Users/your_username/Documents/Android/android-sdk-macosx/platform-tool/ >> ~/.bash_profile
This will make you able to use the fastboot binary from any directory without having to type the path to the binary. In other words if your boot.img is located on your desktop you could just navigate to your desktop in terminal and execute
Code:
fastboot flash boot boot.img
without the path to the binary

torxx said:
You can use the Boot Flash Script from my TrickDroid thread which has MacOS support
Click to expand...
Click to collapse
thanks i'll give it a go
---------- Post added at 12:54 PM ---------- Previous post was at 12:53 PM ----------
C0mpu13rFr34k said:
You can also add the path of the folder in which the fastboot binary is located in ~/.bash_profile
In your guide that would be /Users/your_username/Documents/Android/android-sdk-macosx/platform-tool/ so with a command:
Code:
echo /Users/your_username/Documents/Android/android-sdk-macosx/platform-tool/ >> ~/.bash_profile
This will make you able to use the fastboot binary from any directory without having to type the path to the binary. In other words if your boot.img is located on your desktop you could just navigate to your desktop in terminal and execute
Code:
fastboot flash boot boot.img
without the path to the binary
Click to expand...
Click to collapse
thanks i'll try this out

I, like the other guy have tried and tried this formula a ton of times. I always get the error "fastboot-mac: command not found"
Also, I cannot find that Flash Boot Script anywhere? Where do I get it?

sanders858 said:
I, like the other guy have tried and tried this formula a ton of times. I always get the error "fastboot-mac: command not found"
Also, I cannot find that Flash Boot Script anywhere? Where do I get it?
Click to expand...
Click to collapse
The op of trickdroid thread. You may need to change boot may need to edit scripts boot.IMG depending on what ROM your running.
Sent from my Nexus 7 using Tapatalk 2

sanders858 said:
I, like the other guy have tried and tried this formula a ton of times. I always get the error "fastboot-mac: command not found"
Also, I cannot find that Flash Boot Script anywhere? Where do I get it?
Click to expand...
Click to collapse
Try this: cd to folder where your fast boot is, then type:
./fastboot-mac flash boot boot.img
Sent from my HTC One S using xda premium

copy file to phone
Hi,
So i unlocked my bootloader yesterday and flashed a custom rom and my phone was working fine. after this though i wanted to use cyanogen mod, so, using rom-manager i downloaded a stable build of cyanogen mod... since then when the phone starts up, it starts up in cyanogen but there are lots of problems...1.it doesnt recognise my sim.2wifi doesnt work.3 my htc one x now isnt being being recognised as a driver on my mac...so this means i can't easily download a new rom and try to flash that, nor can i connect it to a pc and move a new rom file into my phones storage....
i have been told i need to fastboot the phone and flash a new boot.img... so ive downloaded sdk now, and gone through all of the steps up until the instruction *copy rom file to phone*....any ways to work around this, as i cant simply just copy the file to my phone, i think ill need to use terminal or sdk, but im not proficient enough with either of these
thanks for any help u can give

Hex edit HTC One XL Evita CID

This is intended for non AT&T One XL phones, as they do not require SuperCID to unlock bootloader and the SuperCID exploit does not work for non AT&T phones.
So you can use this method if you:
Have a non AT&T One XL and have unlocked the bootloader and need SuperCID to S-OFF
Or have already unlocked your bootloader (>2.14hboot) or acquired S-OFF(<2.14hboot) and need to change your CID for whatever reason. If this is the case be sure to replace 11111111 with the CID you wish to change it to. (MUST BE 8 CHARACTERS)
I have simplified this post. Rather than extract the mmcblk0p5 partition file and hex edit the cid, you can just write directly to mmcblk0p5.
I assume you have ADB working. If you do not, you will want to make sure you have the HTC drivers installed and HTC Sync not installed.
Open your command prompt and navigate to your fastboot/adb folder or shift right click within your fastboot/adb folder and click on "open command prompt here". Connect your phone to your PC.
Type:
Code:
adb shell
Then:
Code:
su
echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
Your CID should now be changed to Super CID... or whatever CID you wanted to change it to.
Congrats! To verify reboot to bootloader and type fastboot getvar cid or fastboot oem readcid

exad said:
Being someone with a non AT&T Phone and knowing the plight of not being able to use SuperCID one click, and with S-OFF being so popular, I decided to make a guide to hex editing your CID as I found it difficult to locate one myself to share a link with others. I'm positive someone else has posted how to do this before but this should be easily searchable or at the very least very redundant.
I am not in any way responsible for what happens to your phone while doing this. This can be pretty dangerous.
Onward.
You will need:
Rooted HTC One XL evita with USB Debugging turned ON!
Working ADB
HTC Drivers
I assume you have these if you're reading this. If you do not, see the mega everything thread Resource Compilation courtesy of redpoint73 here
o- Plug in your phone.
o- Open Command Prompt.
o- In command prompt type:
>adb shell
>su
>dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4
o- A file named mmcblk0p4 will now be on the SD card of your phone. *It's a good idea to make note of the file size to cross check with after you've edited and save a copy of this file as a backup*
o- Using your favourite hex editor, look for and hex edit your CID, in my case, TELUS001 to 22222222 *Hex editors can be downloaded for free search google if you need one* Note: USE 11111111 for S-OFF or 22222222 for HTCDEV as HTC Dev no longer accepts 11111111 for unlock.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
o- After you've hex edited, save the file with the same name in the same spot (root of SDcard if following my directions) *After you save the file, it's a good time to make sure the file size matches up*
o- Return to the command prompt and type:
>dd if=/sdcard/mmcblk0p4 of=/dev/block/mmcblk0p4
>reboot bootloader
*Wait till phone is in bootloader/fastboot*
>fastboot oem readcid
o- Admire your new CID. Should Display as "22222222" or "11111111" or whatever else you may have changed it to.
If it helps you, good!
Click to expand...
Click to collapse
I am pretty certain this is the only way I can SuperCid my phone. My current CID is ORANG001 (or similar) and I would really like SuperCid.
I have never used hexedit, though as far as I can see the hexedit here is about as simple as hexeditting can be.
What I would really like would be a screen shots of the CMD feedback, I have no idea what I should be seeing in the CMD window and it's frightening me. I am not a complete beginner to all this, I have been rooting android and messing around for years. I am swimming deeper and deeper at a very steady pace and this would be a good thing to learn to do.
any help appreciated.

I dont believe there is anything returned when entering those commands.
Sent from my Sony Tablet S using xda app-developers app

exad said:
I dont believe there is anything returned when entering those commands.
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
Okay, apart from the adb push one I guess.
I'll give it a go later.
Sent from my HTC One X using xda app-developers app

archie winnington-ingram said:
Okay, apart from the adb push one I guess.
I'll give it a go later.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
When i open cmd, and type first line:
adb shell
the screen display: [email protected]:/ # ........................
So what i need to type in this .........................???????????? I am using MIUIv5

thinhletien said:
When i open cmd, and type first line:
adb shell
the screen display: [email protected]:/ # ........................
So what i need to type in this .........................???????????? I am using MIUIv5
Click to expand...
Click to collapse
The guide tells you what to type. I made it simpler.

exad said:
The guide tells you what to type. I made it simpler.
Click to expand...
Click to collapse
But my problem is when i type the first line, it asking me:
[email protected]:/ # ................
And i have to type something in "............" maybe because of my rom? I am using MIUIv5 sense base. Do i need to install superuser first before do that step?

You should already have super user installed on miui. Does it prompt you on your phone for root access?
Sent from my HTC One X using xda app-developers app

Can´t get SuperCID
Hello,
i need help to get SuperCID on a german Vodafone (VODAP102) HOXL. It´s on hboot 2.14 and it seems that the partition is write protected. I´ve also tried to delete the original mmcblk0p4 by twrp 2.6 and paste in a modified mmcblk0p4.
Is there any way to disable the write protection to get a SuperCid and then S-Off? Even tried:
- Jet
- Jet -k
- Modified the oneXChopper (changed CWS__001 to VODAP102 in the ownage file) -> Error at Line "adb shell ln -s /data/local/tmp/busybox /data/local/tmp/sed
" It always says "Can´t link, file exist.
Thanks for help and sorry for my bad english
Additional information:
- Current ROM ViperXL 3.28
- Bootloader unlocked
- Recovery TWRP 2.6
fastboot var all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 1.27a.32.45.15_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.162.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HTxxxxxxx
(bootloader) imei: xxxxxxxxx
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8311000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4161mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Downgrading hboot with Jet tool is the only way.
Sent from my HTC One X using xda app-developers app

Thanks for the advise but i´m doing something wrong. How do i downgrade the hboot with jet? I thought Jet would do it itself?
The script is running, but instead of booting in Qualcomm Mode it boots normal?
Also tried ./jet -k doesn´t worked. What could i try? Do I need other files in the jet folder?
[email protected]:/home/ubuntu/Desktop/jet# ./jet
JET - Jewel/Evita Toolkit v0.3.3beta
This tool will put backup critical partition data and then put your phone
into QHSUSB mode, where it will then downgrade your HBOOT.
Before running this script, you should have TWRP loaded onto your phone.
Plug your phone in via USB and ensure USB debugging is enabled.
Press Enter to continue...
Preparing...
This phase backs up /dev/block/mmcblk0p4 from your phone to this machine. In
addition, we will fetch your IMEI from the phone and use it to create an
additional partition 4 replacement to use as a failsafe. In the
event something goes wrong, you'll have a way to unbrick manually.
Please stand by...
Backing up mmcblk0p4 to /sdcard/bak4
Rebooting to bootloader...
Getting IMEI value...
Building failsafe P4 file...
Success. Rebooting phone.
Rebooting to recovery...
Waiting 45s for recovery...
Pulling /dev/block/mmcblk0p4 backup from phone...
Applying SuperCID mod to backup P4.
Success.
Phase 2
Now that we have backups, we're going to intentionally corrupt the
data on /dev/block/mmcblk0p4. This will cause the phone to enter
Qualcomm download mode (or QHSUSB if you prefer).
The process can't be stopped after this. Continue?
[Y]es or [N]o?y
Do NOT interrupt this process or reboot your computer.
Corrupting /dev/block/mmcblk0p4...
23 KB/s (1024 bytes in 0.042s)
Rebooting...
Success.
Your phone should now appear to be off, with no charging light on.
Press Enter to continue...
Device detection started...
Waking Device...

I'm on the step where you type
dd if=/sdcard/mmcblk0p4 of=/dev/block/mmcblk0p4
but it says "cannot open for read: No such file or directory"
I put the replaced the file in the same spot it was initially created.
Edit: Nevermind, I still had phone in USB storage mode from copying the file in the first place

When doing adb shell it says "device not found"

Being that you're on cm10.2 you said you've enabled usb debugging in developer options but gave you granted it root access also?
Sent from my Evita

timmaaa said:
Being that you're on cm10.2 you said you've enabled usb debugging in developer options but gave you granted it root access also?
Sent from my Evita
Click to expand...
Click to collapse
Uhm, no. I enabled it but it didn't ask for root.
Edit: just checked superuser, and set it from "only apps" to "apps & ADB"

fusk said:
Uhm, no. I enabled it but it didn't ask for root.
Edit: just checked superuser, and set it from "only apps" to "apps & ADB"
Click to expand...
Click to collapse
Yeah that's the option I meant, hopefully it'll work now. There is also the option located in developer options, just above usb debugging, "root access". They might achieve the same result though.
Sent from my Evita

timmaaa said:
Yeah that's the option I meant, hopefully it'll work now.
Sent from my Evita
Click to expand...
Click to collapse
It didn't, still says device not found.
I open cmd by shift+rightclick and launch cmd from where adb.exe is located.

I've edited my previous post, try that too.
Sent from my Evita

timmaaa said:
I've edited my previous post, try that too.
Sent from my Evita
Click to expand...
Click to collapse
It already says "apps & ADB"

fusk said:
It already says "apps & ADB"
Click to expand...
Click to collapse
Ok, it looks to me like we're definitely dealing with a driver issue then. If you put your phone in fastboot mode, does the command "fastboot devices" return your serial number?