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

[Q] Unable to boot into recovery mode

I've tried using ROM manager and booting back into recovery mode but it stalls at the Google unlock screen. I've also tried installing the stock version of 2.3.2 version from Rom manager but got the same results.
I've also flashed the clockworkMod recovery to 3.0.0.5 then rebooted into Bootloader where i selected the "Recovery" option but again I only reach the Google unlock icon screen. It's been sitting at that screen for the past 20mins. Only way past it is to boot normally (after i reinsert the battery).
I have tried restoring from a previous backup but that too fails because it cant reach the recovery portion of the process after rebooting.
About Phone
Version: 2.3.2
Baseband Version: I9020XXJK8
Kernel Version: 2.6.35.7-g81433b [[email protected]#1]
CPU INFO: ARMv7 Processor Rev 2 (v7l)
Mod Version: CyanogenMod-7-02102011-NIGHTLY-NS
Build #: GRH78C
Click to expand...
Click to collapse
any help is greatly appreciated.

reflash recovery

thejron said:
reflash recovery
Click to expand...
Click to collapse
try reflashing the recovery from within the bootloader with "fastboot flash recovery recovery.img" or something like that. you should find something about this here on XDA i think.

floomat said:
try reflashing the recovery from within the bootloader with "fastboot flash recovery recovery.img" or something like that. you should find something about this here on XDA i think.
Click to expand...
Click to collapse
thx. i'll try that now.

thx for the reply, this page worked:
http://forum.xda-developers.com/sho...ighlight=fastboot+flash+recovery+recovery.img
i was able to update the ROM to 2.3.3, while in recovery mode. I rebooted the device but now when i go to Reboot>Recovery it still hangs at the google unlock screen. I think the only way for me to successfully access the recovery screen would be to connect my phone to the pc and run the fastboot boot-recovery-clockwork-3.0.0.5-crespo.img file.

headsh0tshurt said:
I think the only way for me to successfully access the recovery screen would be to connect my phone to the pc and run the fastboot boot-recovery-clockwork-3.0.0.5-crespo.img file.
Click to expand...
Click to collapse
What's happening is that Android is overwriting your custom recovery whenever it reboots.
To fix it, you first have to go back to the stock rom. Then, using either root explorer or adb, you have to rename /etc/install-recovery.sh
That way, when you flash your custom recovery, it doesn't rewrite the stock one when you reboot.
Check out this link:
http://forum.xda-developers.com/showthread.php?t=740748
edit: Also, in case someone else reads your post about using fastboot to get into recovery... the command is actually: "fastboot boot recovery-clockwork-3.0.0.5-crespo.img"
Note the space, not hyphen, between boot and the recovery image
Edit2: Ugh, the link I gave is pretty unclear (very shoddy google work). Anyway, the idea in the link is right, the command to remount your system in adb is:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
The full list of commands would be:
adb shell
su [you have to allow root access on your phone at this point - superuser will give you a popup]
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /
cd etc
mv ./install-recovery.sh ./install-recovery.sh.old

kaimyn said:
What's happening is that Android is overwriting your custom recovery whenever it reboots.
To fix it, you first have to go back to the stock rom. Then, using either root explorer or adb, you have to rename /etc/install-recovery.sh
That way, when you flash your custom recovery, it doesn't rewrite the stock one when you reboot.
Check out this link:
http://forum.xda-developers.com/showthread.php?t=740748
edit: Also, in case someone else reads your post about using fastboot to get into recovery... the command is actually: "fastboot boot recovery-clockwork-3.0.0.5-crespo.img"
Note the space, not hyphen, between boot and the recovery image
Edit2: Ugh, the link I gave is pretty unclear (very shoddy google work). Anyway, the idea in the link is right, the command to remount your system in adb is:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
The full list of commands would be:
adb shell
su [you have to allow root access on your phone at this point - superuser will give you a popup]
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /
cd etc
mv ./install-recovery.sh ./install-recovery.sh.old
Click to expand...
Click to collapse
i ran adb shell and entered the commands listed above. Below is a screenshot of what was entered.
{
"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 after I entered the mv ./install-recovery.sh ./install-recovery.sh.old
command it says that i can't rename the .install-recovery.sh because it doesn't exist. do i have to manually create a folder on the root with this name?

Did you go back to stock first? I think the files get deleted on a new rom, but for some reason you still have to rename the files while in stock. I had the same issue the first time I went to a custom rom.
I'm about to head to bed (asia) but I'll double check the directory in the morning.
You should also be able to Google the answer... I may have told you the wrong directory for the file. Look for something along the lines of android mount install-recovery.sh
Sent from my Nexus S using XDA App

No i didn't go back to stock prior to running the earlier cmd lines.
while in USB Debug mode, i transferred over the GRI40-2.3.3-rooted.zip into the phones' clockworkmod/backup folder. i then rebooted it into the bootloader and:
ran fastboot boot recovery-clockwork-3.0.0.5-crespo.img
Click to expand...
Click to collapse
I then chose the Backup & Restore option and selected to Restore the GRI40-2.3.3-rooted.
Once it was done i then selected reboot, it powered back on with full stock image. i rebooted it once more to confirm it had the stock image of 2.3.3. then from the bootloader screen i selected the recovery option and it took me to the screen with the android icon and the exclamation mark above it.

headsh0tshurt said:
No i didn't go back to stock prior to running the earlier cmd lines.
while in USB Debug mode, i transferred over the GRI40-2.3.3-rooted.zip into the phones' clockworkmod/backup folder. i then rebooted it into the bootloader and:
I then chose the Backup & Restore option and selected to Restore the GRI40-2.3.3-rooted.
Once it was done i then selected reboot, it powered back on with full stock image. i rebooted it once more to confirm it had the stock image of 2.3.3. then from the bootloader screen i selected the recovery option and it took me to the screen with the android icon and the exclamation mark above it.
Click to expand...
Click to collapse
So now if you delete or rename install-recovery.sh you should be good. For future reference
Code:
fastboot boot
Doesn't flash anything so you're literally just booting into an image so no matter what you wouldn't boot back into that image without the command again. If you want to flash a new recovery without using ROM Manager you can use the following command:
Code:
fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5.img

kenvan19 said:
So now if you delete or rename install-recovery.sh you should be good. For future reference
Click to expand...
Click to collapse
Okay I was not able to locate the file "install-recovery.sh" file on the SD, so from bootloader, I ran the code:
Code:
fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5.img
and went into recovery mode where i ran the latest nightly (cm_crespo_full-12.zip) and rebooted it more than once and each time it gets stuck @ the cyanogen mod7 boot screen....progress :/

headsh0tshurt said:
Okay I was not able to locate the file "install-recovery.sh" file on the SD, so from bootloader, I ran the code:
Code:
fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5.img
and went into recovery mode where i ran the latest nightly (cm_crespo_full-12.zip) and rebooted it more than once and each time it gets stuck @ the cyanogen mod7 boot screen....progress :/
Click to expand...
Click to collapse
interesting...Firstly because I wasn't paying close enough attention and mistyped the command (it should be fastboot flash recovery recovery-clockwork-crespo-3.0.0.5 not fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5) and it worked nonetheless.
There is a reason, however, you most likely weren't able to find the file etc/install-recovery.sh and that is because it isn't on the SD card. Unless you're using Root Explorer (paid app on the market, link here: https://market.android.com/details?id=com.speedsoftware.rootexplorer&feature=search_result) you're not going to see it.

Suggest you try the instructions at the bottom of this page > http://jaxov.com/2011/02/how-to-root-android-2-3-3-gingerbread-on-nexus-s/
7-step process that will help you go to CMR instead of stock recovery. Worked perfectly for me.

kenvan19 said:
interesting...Firstly because I wasn't paying close enough attention and mistyped the command (it should be fastboot flash recovery recovery-clockwork-crespo-3.0.0.5 not fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5) and it worked nonetheless.
There is a reason, however, you most likely weren't able to find the file etc/install-recovery.sh and that is because it isn't on the SD card. Unless you're using Root Explorer (paid app on the market, link here: https://market.android.com/details?id=com.speedsoftware.rootexplorer&feature=search_result) you're not going to see it.
Click to expand...
Click to collapse
yeah i copy/pasted what you wrote in my response but in actuality i wrote the correct file name into the the CMD and it went through. IF/when i get past the CM7 boot screen i'll look into the root explorer app. thx for the assist

kenvan19 said:
interesting...Firstly because I wasn't paying close enough attention and mistyped the command (it should be fastboot flash recovery recovery-clockwork-crespo-3.0.0.5 not fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5) and it worked nonetheless.
There is a reason, however, you most likely weren't able to find the file etc/install-recovery.sh and that is because it isn't on the SD card. Unless you're using Root Explorer (paid app on the market, link here: https://market.android.com/details?id=com.speedsoftware.rootexplorer&feature=search_result) you're not going to see it.
Click to expand...
Click to collapse
.cruiser said:
Suggest you try the instructions at the bottom of this page > http://jaxov.com/2011/02/how-to-root-android-2-3-3-gingerbread-on-nexus-s/
7-step process that will help you go to CMR instead of stock recovery. Worked perfectly for me.
Click to expand...
Click to collapse
Thanks for the link. I went through the instructions and the results were the same. the end of the instructions mentions to get the Root explorer on the phone but that doesnt work b/c i cant bypass the CM7 boot screen. so i just restored it to GRI40-2.3.3-rooted.zip via the clockwork recovery

The install-recovery.sh file is missing in CM7 - you have to do this process from a stock rom.
Personally, this is exactly how I did it. You may try it this way if you like... you should have instructions for all the individual pieces.
1. Go back to stock 2.3.2
2. Get the OTA update to 2.3.3
3. Unlock your bootloader
4. Using the fastboot boot recovery method, install SU
5. Boot in to Android and then rename install-recovery.sh
6. Install rom manager
7. Flash CWM 3.0.0.5
Good luck! Who knows, maybe you have to have an unlocked bootloader to get CWM to stick.

kaimyn said:
The install-recovery.sh file is missing in CM7 - you have to do this process from a stock rom.
Personally, this is exactly how I did it. You may try it this way if you like... you should have instructions for all the individual pieces.
1. Go back to stock 2.3.2
2. Get the OTA update to 2.3.3
3. Unlock your bootloader
4. Using the fastboot boot recovery method, install SU
5. Boot in to Android and then rename install-recovery.sh
6. Install rom manager
7. Flash CWM 3.0.0.5
Good luck! Who knows, maybe you have to have an unlocked bootloader to get CWM to stick.
Click to expand...
Click to collapse
my impatience got the best of me. after restoring it to the stock 2.3.3. i just reinstalled all the applications. none of my downloaded files (music/wallpapers) were lost.
[sarcasm]just have to go through the joy of reorganizing each screen [/sarcasm]. Mostly i am pisssed that i'd have to start from scratch in Angry birds .

This happened to me with gingercollab. I did fastboot flash then booted straight to recovery and installed cm7. Everything was working fine until I restored my nandroid of gingercollab by mistake.
Sent from my Nexus S using XDA Premium App

the issue was never resolved. and i get the system update for 2.3.4 about twice a week and i cant install it b/c after it restarts it bombs out at the android icon w/ the excalamtion mark.
i've tried the factory wipe/reset thinking that would start me off clean but that didnt work.

Unless you RENAME the stock recovery it WILL NEVER STICK. Unlocked bootloader or not. I just reflash recovery from fastboot if/when I need it.
Sent from a bird cage, with a swing!

[BOOT] Root for S-Off with unsecured Boot Image

Hey Guys,
so if you have the same problem like me, that superoneklick tool hangs at "Running psneuter" than you should give this a try.
this works only on s-off devices.
{
"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"
}
all you s-on´s you have to wait for other options or find someone with a xtc clip.
DISCLAIMER: i´m not responsible for bricking your device. do everything in this guide at your own risk.
- download the PG88IMG-unsecured_bootimg.zip
- rename it to "PG88IMG.zip"
- put it on the root of your SD card
- reboot into hboot and wait.
bootloader will automaticly chack this file (ignore the security flag ;-) ) and flash this unsecured boot.img.
reboot your phone and use superoneklick tool the normal way.
rename the PG88IMG.zip to something else or the bootloader will try to flash it every time when the phone starts in bootloader.
hope this will help those who could root even with s-off.
source: New Sense ROM from Desire Forum
and thx to BRONSON29 who give me the right direction: Single Post
happy modding and rooting.
now we need someone who can compile a custom recovery for the desire s
kind regards
stephan

i started to build clockworkmod recovery for the device...
hope to finish a working beta the next days...
so stay tuned ;-)

first custom rom is in the kitchen too ;-)
will be based on RUU_Saga_HTC_Europe_1.28.401.1
at first only a basement.... nothing big
only deodexed, zipaligned, prerooted, busybox and some little tweaks
removed some apps, cause they could be downloaded in market (like facebook, twitter etc)
let´s see what else i can do.
regards

loveboatcaptain said:
first custom rom is in the kitchen too ;-)
Click to expand...
Click to collapse
I would suggest to remove route66 and amazonmp3 in custom..
Question about removing route66 - I failed to push the native carhome (from asop 2.3) instead of the htc one - anyone suceeded? (where to push which apk exactly?)

dont know said:
I would suggest to remove route66 and amazonmp3 in custom..
Question about removing route66 - I failed to push the native carhome (from asop 2.3) instead of the htc one - anyone suceeded? (where to push which apk exactly?)
Click to expand...
Click to collapse
i have added the google car home in my rom and it´s working well. you can choose in app drawer which car launcher should be loaded. you can checkbox the question and it will run that one on default.
route66 isn´t in my rom, but that htc locations app. don´t know if it´s the same what you mean. you can disable htc locations with the integrated titaniumbackup. after that google maps, if installed, is the default app for clicking on contacts adresses and for navigation.
regards

Which apk (where from?) did you push in which directory? Perhaps you can upload the apk?
EDIT: pushed it again to system/app - now works (perhaps I didn't set permissions first time); only litlle issues (settings-> android settings -> FC because of wrong path)
Where to download your ROM? What did you change
HTC locations IS Route66 - which you have to buy after 30 days. So its adware - I deleted the 3 files (locations*) - no problems after that.
Tomorrow (when at home) I will try Android music3 from my NexuS instead of HTC music2.apk. hoping the lockscreen will work with aosp musicplayer...
EDIT: Tried music3.apk - does work as normal BUT does NOT work in lockscreen
If anyone want try out the leaked music3 (from android 3.0) http://dl.dropbox.com/u/7354082/goog...echfrom10c.zip [thanks to mortzz]
Sent from my HTC Desire S using Tapatalk

Thx!
After S-OFFed my phone with the XTC Clip i finally rooted my Desire S.
Thanks again for this great tutorial .

i am s-on !
i did this :
i put clockworkmods recovery on my SD root.
then temp root with gingerbreak1.2.
then in a adb shell i type su klik allow, and get temproot
#
then i backup my ori recovery just incase we overwrite it ..
dont worry about phone saying SD not mounted its cached.
dd if=/dev/block/mmcblk0p21 of=/mnt/sdcard/part21.img
now i flash clockworkmods recovery
dd if=/mnt/sdcard/recovery.img of=/dev/block/mmcblk0p21
it finish without errors
but when i reboot its not been flashed, allthoe it have made a backup of ori recovery on sdcard.
this migth work on boot.img partition 22 allso ,i have not tested it..
hope someone can use this info
THX
marsdroid

brokenworm said:
i am s-on !
i did this :
i put clockworkmods recovery on my SD root.
then temp root with gingerbreak1.2.
then in a adb shell i type su klik allow, and get temproot
#
then i backup my ori recovery just incase we overwrite it ..
dont worry about phone saying SD not mounted its cached.
dd if=/dev/block/mmcblk0p21 of=/mnt/sdcard/part21.img
now i flash clockworkmods recovery
dd if=/mnt/sdcard/recovery.img of=/dev/block/mmcblk0p21
it finish without errors
but when i reboot its not been flashed, allthoe it have made a backup of ori recovery on sdcard.
this migth work on boot.img partition 22 allso ,i have not tested it..
hope someone can use this info
THX
marsdroid
Click to expand...
Click to collapse
like in your other post i think this is a possible way. if it is possible to change the boot.img after temp-rooting you will be able to get root with adb to mount system r/w to push su files.
than you have permanent root but with S-On. but i think there will be a way to flash recovery too. than it is like the thing with the HTC wildfire. possible root but with s-on. you can only flash things in recovery mode and you can´t mount system r/w when the devices is booted.

loveboatcaptain said:
like in your other post i think this is a possible way. if it is possible to change the boot.img after temp-rooting you will be able to get root with adb to mount system r/w to push su files.
than you have permanent root but with S-On. but i think there will be a way to flash recovery too. than it is like the thing with the HTC wildfire. possible root but with s-on. you can only flash things in recovery mode and you can´t mount system r/w when the devices is booted.
Click to expand...
Click to collapse
G:\adb>adb shell
$ su
su
# dd if=/dev/block/mmcblk0p22 of=/mnt/sdcard/22.img
dd if=/dev/block/mmcblk0p22 of=/mnt/sdcard/22.img
8192+0 records in
8192+0 records out
4194304 bytes transferred in 0.452 secs (9279433 bytes/sec)
# dd if=/mnt/sdcard/boot.img of=/dev/block/mmcblk0p22
dd if=/mnt/sdcard/boot.img of=/dev/block/mmcblk0p22
5676+0 records in
5676+0 records out
2906112 bytes transferred in 0.906 secs (3207629 bytes/sec)
# sync
sync
#
i did not brick
can you plz post some adb mounting commands.. im rusty

loveboatcaptain said:
like in your other post i think this is a possible way. if it is possible to change the boot.img after temp-rooting you will be able to get root with adb to mount system r/w to push su files.
than you have permanent root but with S-On. but i think there will be a way to flash recovery too. than it is like the thing with the HTC wildfire. possible root but with s-on. you can only flash things in recovery mode and you can´t mount system r/w when the devices is booted.
Click to expand...
Click to collapse
we need something faking the nand lock open... like wpthis did.. OR
i can live with s-on and R/O on /system , IF only i got the recovery or boot installed...
marsdroid

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

I need help rooting my zte quest 5

Ok so i got a zte quest 5 (z3351s) though qlink. Not the phone i wanted but it was one i could afford. And it works very well just can't run amazon music and other apps at the same time.
But the bloatware is unreal. Used to in my galaxy s3&s4 days i could root and delete all apps i didn't need. I know i can disable them but i want them gone completely.
Majisk didnt work
Kingoroot same even used pc.
I am hoping someone knows of a way i can root this phone or at least delete all the un needed apps for example i have Google maps go (came stock) i put the org google maps which is better plus offers sat view.
Edit i did some math and converting and the useless apps 11 out of 58 come out to 349.72mb which is a lot if your phone only has 16gb of space. Also note i don't have hardly anything.
Worst case i can Hotspot to my note10+ for multitasking but not sure of data limit.

@TexasPride
a phone's Android can get considered "rooted" as soon as in Android the SU-binary is present. Hence you at any time at your own can install the appropriate SU-binary onto your phone's Android by means of ADB.

I heard about adb methods but i haven't messed with it in forever since apk/ios apps came out

jwoegerbauer said:
@TexasPride
a phone's Android can get considered "rooted" as soon as in Android the SU-binary is present. Hence you at any time at your own can install the appropriate SU-binary onto your phone's Android by means of ADB.
Click to expand...
Click to collapse
Are you sure it will always work?
I tried this method of installing supersu: https://github.com/spff/install-supersu-via-adb
As a result, I got my phone eternally showing the boot logo and not booting.
Not a problem to re-flash stock ROM but it is an example that there in no universal way to install SU (or SuperSU) via adb.
If you could give a link to some other method how SU could be installed, I'll give it a try of course.

vp1117 said:
Are you sure it will always work?
I tried this method of installing supersu: https://github.com/spff/install-supersu-via-adb
As a result, I got my phone eternally showing the boot logo and not booting.
Not a problem to re-flash stock ROM but it is an example that there in no universal way to install SU (or SuperSU) via adb.
If you could give a link to some other method how SU could be installed, I'll give it a try of course.
Click to expand...
Click to collapse
I spoke of SU-binary and NOT of SuperSU installer package
Example:
Code:
adb devices
adb push <location-of-matching-su-binary-on-computer> /sdcard/Downloads/ 2>nul
adb shell "chmod 0777 /sdcard/Downloads/su"
Of course you can install SuperSU package by means of ADB and this even when device is booted into Stock Recovery: but this requires to make some mods to SuperSU zip.

TexasPride, sorry I stepped in your thread.​
jwoegerbauer said:
I spoke of SU-binary and NOT of SuperSU installer package
Click to expand...
Click to collapse
I see. It is often mixed in numerous materials one can find in the net. Subject is SU-binary update, but the ultimate goal is to install supersu.
jwoegerbauer said:
Example:
Code:
adb devices
adb push <location-of-matching-su-binary-on-computer> /sdcard/Downloads/ 2>nul
adb shell "chmod 0777 /sdcard/Downloads/su"
Click to expand...
Click to collapse
What should be result of running this code? SU-binary located in Downloads with 777 permission? What is the practical sense/use of it?
What software/application would use SU in that location?
Sorry for my questions. I'm not arguing. I try to understand the idea.
jwoegerbauer said:
Of course you can install SuperSU package by means of ADB and this even when device is booted into Stock Recovery: but this requires to make some mods to SuperSU zip.
Click to expand...
Click to collapse
Somehow, with my almost zero knowledge of edify and linux command line I got the same conclusion: SuperSU zip has to be modified in order to install it via adb on devices that do not have TWRP for sideload. I failed to find any examples of SuperSU modding...

@vp1117
Answering your questions from last to first:
Installing SuperSU.zip via ADB
The SuperSU.zip doesn't come with an EDIFY coded script, but with an Android SHELL script - everyone who has knowledge of LINUX scripting can read / modify it.
Android comes with TAR-binary, but not ZIP-binary. Hence the SuperSu.zip must get repacked into SuperSU.tar thus it can get extracted on Phone. The contents of such a TAR-file would look as shown here
{
"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"
}
Making use of SU-binary
The SU-binary ( ~110KB ) is nothing else then the root user, as known from LINUX.
Running in Android via ADB a command that requires super-user ( root ) rights is done as follows
Example:
Code:
adb devices
adb shell "/sdard/Downloads/su -c '<ommand-that-requires-root-here>'"

jwoegerbauer said:
Answering your questions from last to first:
Installing SuperSU.zip via ADB
The SuperSU.zip doesn't come with an EDIFY coded script, but with an Android SHELL script - everyone who has knowledge of LINUX scripting can read / modify it.
Android comes with TAR-binary, but not ZIP-binary. Hence the SuperSu.zip must get repacked into SuperSU.tar thus it can get extracted on Phone. The contents of such a TAR-file would look as shown here
Click to expand...
Click to collapse
OK. I guess, I can repack zip to tar.
Sorry for my silly question but why should I need to keep superSU as an archive? Could not I just upload all folders + update-binary.sh to the phone? I'm sure I can do it.
Am I right my next step would be running update-binary.sh (~60 KB) from <adb shell> command line?
jwoegerbauer said:
Making use of SU-binary
The SU-binary ( ~110KB ) is nothing else then the root user, as known from LINUX.
Running in Android via ADB a command that requires super-user ( root ) rights is done as follows
Example:
Code:
adb devices
adb shell "/sdard/Downloads/su -c '<ommand-that-requires-root-here>'"
Click to expand...
Click to collapse
Interestingly, I can execute all commands I need without having su-binary (~100 KB) uploaded to my phone. It is strange but I see #-prompt after I ran <adb shell>. This happens on my UNrooted phone, running stock ROM. I guess, it's a specifics of my phone, no need to try explain it.

I done failed trying to read i dont really understand linux all that well. But if anyone has any links so i can download it and try it

vp1117 said:
Sorry for my silly question but why should I need to keep superSU as an archive? Could not I just upload all folders + update-binary.sh to the phone? I'm sure I can do it.
Am I right my next step would be running update-binary.sh (~60 KB) from <adb shell> command line?
Click to expand...
Click to collapse
Of course it's your decision how you transfer the SuperSU package onto phone: many ways lead to Rome.
My decision was to push SuperSU package repacked as TAR-file onto phone, extract it there, and finally run the modified update-binary.sh when phone is booted into recovery mode:
Code:
adb shell "$(cat < %supersu_dir%/update-binary.sh); echo $?"

So I rebooted to stock recovery and then uploaded following from UPDATE-SuperSU-v2.82-20170528234214.zip package to my phone's folder /tmp:
/arm64
/common
/META-INF
update-binary.sh
Here is what I got:
Z:\android\adb>adb shell "$(cat < /tmp/update-binary.sh); echo $?"
127
/system/bin/sh: #!/sbin/sh: not found
And here's what I got running same command from # command line:
# $(cat < /tmp/update-binary.sh); echo $?
/system/bin/sh: #!/sbin/sh: not found
127
In response to # ls -al /sbin I get lots of lines one of them is as follows:
lrwxrwxrwx 1 root root 7 1970-01-01 00:00 sh -> busybox
I feel that I'm doing something wrong, but what exactly?
In attached txt-file I put some more details I got in command line.

jwoegerbauer said:
... and finally run the modified update-binary.sh when phone is booted into recovery mode:
Click to expand...
Click to collapse
Am I right the only modification needed is to rename update-binary to update-binary.sh ?

@vp1117
NO.
When I said modified then I didn't mean simply rename it: The contents of original update-binary file must be rewritten / deleted in some parts. Also, believe me, it makes sense to repack original SuperSU.zip to SuperSu.tar as I demonstrated above. Take also note that, if device's Android isn't rooted yet, the location for unpacked SuperSU mandatory must be /data/local/tmp.
BTW:
I can see BusyBox is installed on your device's Android. Take note that BusyBox by default comes with the SU-binary. Hence your device's Android is rooted! Wondering why you waste your time with trying to completely install SuperSU from scratch?

jwoegerbauer said:
Wondering why you waste your time with trying to completely install SuperSU from scratch?
Click to expand...
Click to collapse
Good question.
Probably, because I see this when phone restarts from recovery to normal android:

jwoegerbauer said:
Also, believe me, it makes sense to repack original SuperSU.zip to SuperSu.tar as I demonstrated above.
Click to expand...
Click to collapse
OK, no problem, I can re-pack zip into tar.
However, what you demonstrated above was a screenshot showing update-binary.sh being inside the tar. At the same time you don't tell how update-binary.sh must be amended. Is it OK?

TexasPride​
I'm very sorry I put so much spam in your thread. Please forgive me. If I knew how to delete my posts here I would deleted them.

vp1117 said:
TexasPride​
I'm very sorry I put so much spam in your thread. Please forgive me. If I knew how to delete my posts here I would deleted them.
Click to expand...
Click to collapse
Its ok, i dont mind at all.

@TexasPride
FYI: I no longer participate this hijacked thread.