Related
Dear all,
When looking at the recent HTC Hero update firmware released from HTC i was curious to why they had included adb.exe and fastboot.exe in the upgrade program, so I started looking into this. Basicly I made replacement tools for adb.exe and fastboot.exe that simulated the behavior of a phone to be on the safe side.
From this session I learned two things. First of all we can upgrade the rom.zip via both OSX, Linux and Windoze. Secondly there is a special boot mode called oem-78 which enabled RUU bootloader mode.
Some other notes also is that my bootloader was delivered with factory hboot version 1.76.0007, but even with this bootloader while in RUU mode the bootloader does not seem to check signature when trying to boot cm-hero-recovery.img. It crashes on boot tought, but this seems to be another way in for booting unsigned images...
Another interesting note is that my device was factory programmed with firmware 2.73.751.4, while the upgrade released yesterday is 2.73.405.5.
This is the resulting log from what the ARUWizard is actually doing.
I did not investigate futher after fastboot flash zip rom.zip, so there might be more needed to do after this, so proceed with caution if you want to try this.
Code:
# Get list of attached devices
$ adb devices
# Check battery power for detected device.
$ adb -s <SN> shell cat /sys/class/power_supply/battery/capacity
# Get current firmware version.
$ adb -s <SN> shell getprop ro.build.description
# Reboot into bootloader with RUU mode enabled.
$ adb -s <SN> shell reboot oem-78
# Check if device is is disconnected from usermode
$ adb devices
# If not present any more, check via fastboot
$ fastboot devices
# If detected, check if in RUU mode
$ fastboot -s <SN> getvar boot-mode
# If mode returns RUU, start the upgrade by erasing cache
$ fastboot -s <SN> erase cache
# Upload rom.zip file and flash
$ fastboot -s <SN> flash zip rom.zip
Best regards,
Exion
Diator said:
I am in Taiwan, i bought the Hero 1 week ago and the default firmware is 2.73.751.4
Click to expand...
Click to collapse
Same here. I bought mine a few days ago in Taiwan. This is the new version where they ship 1 extra microSD that is 8GB class 6 (as well as the old 2GB card). The handset itself is standard HTC Hero white, but the firmware is Chunghwa telecom branded.
I have attached my build.prop file which should give most info regarding this firmware for those interested.
Best regards,
Exion
This is a super simple method taken from Arcadia 310 on another thread.
This is assuming you have The Android SDK already installed and updated.
Download these files XoomRoot.zip HERE
and FASTBOOT for MAC - HERE
Unzip both archives into your ~/sdk/platform-tools folder.
I AM NOT RESPONSIBLE FOR YOU SCREWING UP YOUR DEVICE, THIS IS VOIDING YOUR WARRANTY ANYWAYS. HIT ME UP ON TWITTER OR HERE IF YOU NEED HELP OR HAVE QUESTION. ON TO DIRECTIONS.
Follow these steps: (After you have unzipped into your folder)
1. Follow the pre requisites above.
2. Open a terminal (located in the utilities folder)
3. Navigate to your sdk/platform-tools folder
Example: "cd /home/b16/Desktop/sdk/platform-tools" (no quotes)
4. Type "./adb devices" and make sure your Xoom shows up on the list.
This command will show you if your device is connected to the Android Debug Bridge.
5. Now type in "./adb reboot bootloader" (You can skip the next 3 steps if you’ve unlocked with fastboot previously)
This will reboot your device into bootloader mode accepting fastboot commands.
6. I had to type "chmod 755 fastboot" first to get it to execute.
This will change the permissions of the FASTBOOT BINARY so it can execute.
7. Now type in "./fastboot oem unlock" and choose to unlock it. (wait for reboot)
This will make your device "Hackable" and will VOID your warranty, you can re-lock it later if you like using another guide on this forum. Located HERE.
8. Once it has rebooted type "adb reboot bootloader" and hit enter.
Now you are going back into bootloader mode to finish the job.
9. Once in bootloader mode type "./fastboot flash boot rootboot.img"
This is going to flash the boot image needed to have root working properly within the system.
10. Type "./fastboot reboot" (wait for reboot)
command wil now boot you back into Android.
11. Type "./adb remount"
We are now mounting the system partition in order to push the Super User binary.
12. Type "./adb push su /system/bin"
Does what it says. Pushes binary to system folder.
13. Type "./adb shell" You should now see a "#" sign.
This will put you into a root shell to change the permissions of files in the next step.
14. Type "chmod 4755 /system/bin/su"
You just changed the permissions of the super user binary to run properly.
15. Type "exit".
You will now be back in your home terminal ready to push the Super User Apk.
16. Type "./adb push Superuser.apk /system/app"
You should now have root acces! Enjoy!
Thanks for posting this. Another thing I did, because I use ADB quite frequently, was add the SDK tools to my path. For those that need help, it looks something like this:
Open Terminal and type echo 'export PATH=~/Downloads/android-sdk-mac_x86/tools:$PATH' >> ~/.profile
This only works if your SDK folder is in your Downloads folder inside your Home folder.
The next time you open a Terminal window, you can simply type adb remount or whatever you need without having to add the ./
Another bonus is this makes it much easier to keep kernels, ROMs, and modules out of your SDK tools folder, where they do not belong.
First off thanks for doing this... I figured out my n1 and I can do this too... I'm stuck at the chmod 775 line... I enter that command and its like I didn't enter it... after I proceed to fast boot OEM unlock it tells me that it can't be executed .. what am I doing wrong... God I hate being noobed out... I'm so close!!!
Sent from my Nexus One using XDA App
EDIT: got past that with the help of using fastboot-mac from htc's website... but now I'm stuck on getting the rootboot.img over
Morgan-Brants-Mac-minilatform-tools Chongo$ ./fastboot-mac flash boot rootboot.img
sending 'boot' (2902 KB)... OKAY
writing 'boot'... FAILED (remote: (0000000f))
Morgan-Brants-Mac-minilatform-tools Chongo$
EDIT2: Well it was due to my xoom being almost dead (not enough juice to flash)
on the other hand this was a refresher course and I now understand ADB a whole lot more... thank you for this educational piece I am now a tiger blood enfused SUPER USER
I am glad I could help, I have this tutorial on my website along with many other devices, http://rootzwiki.com if there is any other devices you would like to see
b16a2smith said:
I am glad I could help, I have this tutorial on my website along with many other devices, http://rootzwiki.com if there is any other devices you would like to see
Click to expand...
Click to collapse
Thanks.. ill let you know when I get a new phone.. should be soon
Sent from my Nexus One using XDA App
thanks for this. Cant wait to get mine on the 27th
wheeeler said:
Thanks for posting this. Another thing I did, because I use ADB quite frequently, was add the SDK tools to my path. For those that need help, it looks something like this:
Open Terminal and type echo 'export PATH=~/Downloads/android-sdk-mac_x86/tools:$PATH' >> ~/.profile
This only works if your SDK folder is in your Downloads folder inside your Home folder.
The next time you open a Terminal window, you can simply type adb remount or whatever you need without having to add the ./
Another bonus is this makes it much easier to keep kernels, ROMs, and modules out of your SDK tools folder, where they do not belong.
Click to expand...
Click to collapse
Well the default shell in a mac is bash so wouldn't be:
Code:
echo "export PATH=$HOME/bin/android-sdk-mac_x86/tools:$HOME/bin/android-sdk-mac_x86/platform-tools:$PATH" > .bash_profile
This is a video walkthru of rooting that happens to be on a Mac but the process is the same for Windows:
http://www.youtube.com/watch?v=4YkIw0y_Os4
im not sure if it is just me or not, but i get stuck at step 5 for some reason?
i type ./adb reboot bootloader it shuts down then turns on and i get stuck at "starting fastboot protocal support" it sits forever then i have to hold volume up and power to reboot and its fine, but cant ever get past that.
it no longer shows as attached device at that point either
Magenta you say.
chevyman46933 said:
im not sure if it is just me or not, but i get stuck at step 5 for some reason?
i type ./adb reboot bootloader it shuts down then turns on and i get stuck at "starting fastboot protocal support" it sits forever then i have to hold volume up and power to reboot and its fine, but cant ever get past that.
it no longer shows as attached device at that point either
Click to expand...
Click to collapse
can anyone help me?
OK, thanks for the initial post and outstanding directions. I've updated what you listed based on what I have seen on my mac. I've just been through this process now and everything is working great. I hope this helps.
1. Follow the pre requisites above.
* I also had to download the fastboot-mac file from the HTC site- http://developer.htc.com/adp.html
2. Open a terminal (located in the utilities folder)
3. Navigate to your sdk/platform-tools folder
Example: "cd /home/b16/Desktop/sdk/platform-tools" (no quotes)
4. Type "./adb devices" and make sure your Xoom shows up on the list.
This command will show you if your device is connected to the Android Debug Bridge.
goonmac-2: platform-tools goon$ ./adb devices
List of devices attached
028040c743e111d7 device
5. Now type in "./adb reboot bootloader" (You can skip the next 3 steps if you’ve unlocked with fastboot previously)
This will reboot your device into bootloader mode accepting fastboot commands.
FYI - your xoom will just say "Starting..." but it is ready to accept the next step.
6. I had to type "chmod 755 fastboot" first to get it to execute.
This will change the permissions of the FASTBOOT BINARY so it can execute.
7. Now type in "./fastboot oem unlock" and choose to unlock it. (wait for reboot)
This will make your device "Hackable" and will VOID your warranty, you can re-lock it later if you like using another guide on this forum. Located HERE.
goonmac-2: platform-tools goon$ ./fastboot-mac oem unlock
... INFO To continue, follow instructions on the device's display...
OKAY
8. Once it has rebooted type "adb reboot bootloader" and hit enter.
Now you are going back into bootloader mode to finish the job.
*after the reboot, initially, I got this error:
goonmac-2: platform-tools goon$ ./adb reboot bootloader
error: device not found
when the reboot completes, you will come to the original setup screen. it is worth noting that you need to select the language and follow the on screen directions. Re-enter your account information etc. When you get to the desktop, your device will then be re-seen by your mac.
9. Once in bootloader mode type "./fastboot flash boot rootboot.img"
This is going to flash the boot image needed to have root working properly within the system.
* Again, need to use the fastboot-mac:
goonmac-2: platform-tools goon$ ./fastboot-mac flash boot rootboot.img
sending 'boot' (2902 KB)... OKAY
writing 'boot'... OKAY
10. Type "./fastboot reboot" (wait for reboot)
command wil now boot you back into Android.
* Again, need to use the fastboot-mac:
goonmac-2: platform-tools goon$ ./fastboot-mac reboot
rebooting...
11. Type "./adb remount"
We are now mounting the system partition in order to push the Super User binary.
no issues
goonmac-2: platform-tools goon$ ./adb remount
remount succeeded
12. Type "./adb push su /system/bin"
Does what it says. Pushes binary to system folder.
no issue
goonmac-2: platform-tools goon$ ./adb push su /system/bin
701 KB/s (26336 bytes in 0.036s)
13. Type "./adb shell" You should now see a "#" sign.
This will put you into a root shell to change the permissions of files in the next step.
no issue
goonmac-2: platform-tools goon$ ./adb shell
14. Type "chmod 4755 /system/bin/su"
You just changed the permissions of the super user binary to run properly.
no issue
# chmod 4755 /system/bin/su
15. Type "exit".
You will now be back in your home terminal ready to push the Super User Apk.
16. Type "./adb push Superuser.apk /system/app"
no issue
goonmac-2: platform-tools goon$ ./adb push Superuser.apk /system/app
1137 KB/s (196521 bytes in 0.168s)
still stuck at same step, after ./adb reboot fastboot i cant go any farther, the xoom just isnt connected to recieve and additional commands, heres a copy n paste from my terminal...
Mac-Users-Mac-mini:tools Home$ pwd
/Users/Home/desktop/sdk/platform-tools
Mac-Users-Mac-minilatform-tools Home$ ./adb devices
List of devices attached
161c10c94180d557 device
Mac-Users-Mac-minilatform-tools Home$ ./adb reboot bootloader
Mac-Users-Mac-minilatform-tools Home$ chmod 755 fastboot
Mac-Users-Mac-minilatform-tools Home$ ./fastboot oem unlock
-bash: ./fastboot: cannot execute binary file
Mac-Users-Mac-minilatform-tools Home$ ./adb devices
List of devices attached
Mac-Users-Mac-minilatform-tools Home$
any help/suggestions?
Are you using the Mac fastboot binary? I'm not by my computer right now, but I believe the Mac version is called fastboot-mac by default. Download it, make sure it's executable (chmod 755 fastboot-mac), then try fastboot-mac oem unlock. After you run adb reboot bootloader, you will lose your ADB connection, and your Xoom won't display anything but the boot logo and something about starting fastboot. This is your cue to unlock. Hope this helps.
Sent from my Xoom using XDA Premium App
wheeeler said:
Are you using the Mac fastboot binary? I'm not by my computer right now, but I believe the Mac version is called fastboot-mac by default. Download it, make sure it's executable (chmod 755 fastboot-mac), then try fastboot-mac oem unlock. After you run adb reboot bootloader, you will lose your ADB connection, and your Xoom won't display anything but the boot logo and something about starting fastboot. This is your cue to unlock. Hope this helps.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
that was exactly it, i was using the fastboot from another post, got the fastboot-mac from the website adn it works perfect!! thanks!!!
xoom unlocked, finally
thats why I amended the steps
1. Follow the pre requisites above.
* I also had to download the fastboot-mac file from the HTC site- http://developer.htc.com/adp.html
goon55 said:
thats why I amended the steps
1. Follow the pre requisites above.
* I also had to download the fastboot-mac file from the HTC site- http://developer.htc.com/adp.html
Click to expand...
Click to collapse
For some respason I didnt realize the difference between the two fastboots until he mentioned that and thankfully your ad was right above with the link to htc thanks to you guys im now have rooted and unlocked and overclocked my xoom and its incredible now! Thanks for the patience with me
I did a video that was done on my MAC in the MAC OS. If anyone wants a more visual way to see how this is performed. I follow all these steps exactly. I show how I set my environment PATH, and this actually is what tripped me up, because my user profile wasn't looking at the PATHs I originally setup, but all that is required is entering
echo 'export PATH=xyz:$PATH' >> ~/.bash_profile (this whole line )
Where 'xyz' is your path to the android-sdk/platform-tools/ from the root of your Hard Drive, for most Macs it should be ' /Users/[Ur User Name]/android-sdk/platform-tools '
http://www.youtube.com/watch?v=26EhGGOGUus
Hope this helps
I also have a WiFi Xoom Video Tutorial available available as well. Check it out.
http://www.youtube.com/watch?v=zC6J-hV6SM4
I try to go over common hiccups that I have seen some users have come across as well in the video.
I'm getting the following error:
./fastboot-mac flash boot rootboot.img
sending 'boot' (2902 KB)... ERROR: usb_write failed with status e00002ed
FAILED (data transfer failure (No such file or directory))
fastboot-mac is chmod 755, rootboot.img is there, alongside it, I'm in as root and it's still failing for me.
Edit: Nevermind. Right after pulling the reboot before the rootboot.img - or boot.img for wifi users - immediately go into the aforesaid command and it should work just fine.
Took me a couple of times.
Can you unroot on mac?
1. How can I root my phone?
1.1 General information/Basic adb-commands
Rooting a phone enables you to do things, which normally aren't possible for the average user like:
- Removing apps which were preinstalled by the provider (like Orange, Vodafone, etc.). My Tattoo had Vodafone apps for buying music and other sh*t, which was installed on the system partition (to which a "normal" user has no rights to write to, including deleting).
The Tattoo was successfully rooted by a bunch of guys here, namely -bm-, mainfram3 and Coburn64 (maybe, I don't remember quite correctly ). Also the Tattoo was the first phone having a security mechanism hindering a user to mount the filesystems as read/write, which had to be overridden by remapping the read only memory region to a read/write one. This is done by the module Tattoo-hack.ko, also made by mainfram3. He also created the first boot.img, which enabled su directly from adb and loading Tattoo-hack directly from boot on.
A few words about adb:
ADB is a tool for communicating from the PC with the mobile phone. For this a service is running on the phone enabling the communication via Terminal Emulator. Here are the most useful adb-commands:
Code:
adb push localFileFromPC /path/on/mobilephone
-> pushes a file "localFileFromPC" to a specified location on the phone
adb pull /path/to/file pathFromPC
-> receives a file from the phone and stores it to "pathFromPC"
adb remount
-> This is only possible in custom ROMs, remounts the file system to r/w automatically
adb shell "command"
-> executes "command" and returns to the computer shell
adb shell
-> opens a shell session on the phone (from here on you have to be very careful! Also you can execute now normal linux commands like rm, mv, ls, chmod and so on, but not cp (this can done through busybox)). You will have to use this more often, so get used to it
1.2 Do I have to create a goldcard?
I read this question quite often. For rooting, you don't need it, but for SIM-locked phones you can't flash custom unbranded ROMs (I think).
A guide to create a goldcard follow this link: http://forum.xda-developers.com/show...88&postcount=1 (thanks to MiSSigNNo to this point)
1.3 Tools you need
A complete set of tools can be found here Feel free to mirror it:
http://rapidshare.com/files/403766494/Tattoo.rar.html
Mirror(s):
http://www.bild-ton.net/Tattoo.rar
http://www.megaupload.com/?d=CI9AW83F
This package contains:
- adb binaries for Windows (sorry Linux users )
- su (Please note: use the su-binary attached in this post, not the one in the archive!!!!!)
- m7 exploit
- Amon_RA recovery.img
- mainfram3 boot.img
- flash_image binary
- tattoo-hack.ko
1.4 The automated way
This method was created by maverixx and can be found here. This basically consists of a package doing everything you need by itself. It roots the phone and flashes maverixx recovery.img, which (no offense) I don't like as much as I like Amon_RA's one!). Just click the batchfile and it does the rest (you have to connect your phone via USB to your PC though ).
If you want to use the automated way, but flashing Amon_RA's recovery, just replace the recovery.img from maverixx' package with the recovery.img provided in my archive file (see 1.3 for the link).
In my time here I noticed quite a few users experiencing problems either with a fully functional su or with the recovery image not flashing certain update.zip packages. It seems to be a matter of luck.
1.5 The manual way (recommended by the author)
I personally like what is done when and how, that's why I recommend the manual way. So let's get down to business Let's see if you know all the adb-commands I wrote here:
1. Let's say you have everything unpacked into C:\Tattoo
2. In your terminal (on your PC) type:
- adb shell "mkdir /data/local/bin" (if it returns an error it means that the directory already exists, just proceed)
- adb push m7 /data/local/bin/
- adb push su /data/local/bin/
- adb push flash_image /data/local/bin/
- adb push tattoo-hack.ko /data/local/bin/
- adb push recovery.img /sdcard
- adb push boot.img /sdcard
3. We have every needed file on the phone now. Type now (we are still in your terminal):
- adb shell
$ cd /data/local/bin
$ chmod 766 m7 (I don't retain this step as mandatory, so if this process fails, just proceed)
$ while ./m7 ; do : ; done
lots of text until you see something like "wrote shell code", press enter 2 or 3 times enter to see:
#
4. Then perform this:
- # export LD_LIBRARY_PATH=/system/lib
- # export PATH=/system/bin
- # insmod ./tattoo-hack.ko
- # mount -o rw,remount /dev/block/mtdblock5 /data
- # mount -o rw,remount /dev/block/mtdblock3 /system
- # cat ./su > /system/bin/su
- # chmod 4755 /system/bin/su
- # chmod 755 ./flash_image
Questions?
1.6 Problems and (hopefully good) solutions
Q: How do I execute my command line tool?
A: On your Windows host, go to Start->Run...->type "cmd"
Q: Where is my adb? When I type it in my shell it says that it was not found!
A: The adb binary is found in the archive I supplied above or in the Google SDK. As my archive-file is quite smaller than the Google SDK you should take mine. Let's suppose your adb binary is unpacked in C:\Tattoo, then type:
Code:
Your\Current\Location> cd C:\Tattoo
C:\Tattoo> adb <command>Q: adb says "error: device not found" when I try to launch the shell on the phone!
A: Connect the phone with the usb cable and make sure the sd card is not mounted as drive on your PC!!!
Q: When I want to copy something the phone returns that "cp" is not found! Also when I try to move a file, it says "cross-link device".
A: Well, copying from one partition to another is only possible either via busybox or via
Code:
cat file > /location/filename
Example:
cp /data/su /system/bin
is realized by typing
cat /data/su > /system/bin/suAlso make sure that system is r/w!!!
Q: flash_image returns write errors when flashing recovery/boot image!
A:
For boot: Try to redo the flash procedure
For recovery: Note that you can't flash the same recovery.img as the one already installed, so install another recovery.img first (like maverixx) and then Amon_RA's again. If it still doesn't work reboot, remount the partitions r/w, insmod tattoo-hack.ko and retry flashing.
Q: How can I unroot my device?
A: Just delete su from /system/xbin and restore the old boot.img. Alternatively see here for retrieving a stock ROM to flash it on your phone.
i hope someone try this i don't have time
Okay, here's what happened,
2 days ago, i installed ARHD ROM, works perfectly fine,
next day, i saw a kernel by franco. installed it, then after rebooting.... baamm! my unit is not working anymore, stuck in boot screen,
i tried different ways, followed different forums, like Tutorial Disaster. still to no avail,
the sad thing is, i forgot to back it up before doing the upgrades, i know its my fault..
i tried to erase everything via recovery, still not working,
Just today, went to HTC service center, i'm from the Philippines, but i bought my unit from online selling. as per HTC service center its from indonesia, they tried to re-flash something but they said its not working, so they said that they will need to change the mother board, and it will cost me 14,000 pesos or $350.. i don't want to spend that much, feels like i bought a new one..
can someone please enlighten me?
?!
You can erase everything in recovery, but you have to flash something afterwards, maybe like ARHD.
There's nothing wrong with your device, don't panic. Just do a wipe, then flash the ROM as the directions are given.
if you can still get into recovery
relock it
flash stock recovery
flash stock RUU
done
Download ARHD and CWM Recovery
Rename ARHD to update.zip and CWM to recovery.img
Place update.zip and recovery.img into a folder with fastboot and adb
Extract boot.img from update.zip and place in your fastboot folder
Put your phone into fastboot mode with unlocked bootloader
Flash boot with command 'fastboot flash boot boot.img'
Boot recovery using 'fastboot boot recovery.img' command
Use command 'adb push update.zip /sdcard/update.zip' to send ARHD to phone
Then install rom from update.zip in recovery
It's nothing serious with your phone. It is easily can be recovered. Just don't run here and there so the XDA community can assist you.
There are two ways to recover your phone.
1) flash RUU
2) push xxx_rom.zip to your device.
Already tell you about flashing RUU in the disaster thread.
well, i would like to give thanks to all of you, who answered my questions, helped a lot. trying to read more here before doing another run in fixing my device.
where can i get stock RUU? my device is from indonesia. and one more thing, how to flash RUU?
djpoe said:
Download ARHD and CWM Recovery
Rename ARHD to update.zip and CWM to recovery.img
Place update.zip and recovery.img into a folder with fastboot and adb
Extract boot.img from update.zip and place in your fastboot folder
Put your phone into fastboot mode with unlocked bootloader
Flash boot with command 'fastboot flash boot boot.img'
Boot recovery using 'fastboot boot recovery.img' command
Use command 'adb push update.zip /sdcard/update.zip' to send ARHD to phone
Then install rom from update.zip in recovery
Click to expand...
Click to collapse
very detailed instruction here
where can i get adb BTW?
wintermute000 said:
if you can still get into recovery
relock it
flash stock recovery
flash stock RUU
done
Click to expand...
Click to collapse
This and finish with: fastboot erase cache
Sent from my HTC One X using XDA
wolfraim said:
This and finish with: fastboot erase cache
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
thanks man.. where can i get the stock RUU and stock recovery? and also why do we have to re lock the device?
EDIT: i almost forgot, because this problem started after installing a new kernel by franco, so i guess i need to install a stock kernel? where can i get it?
mikey0105 said:
thanks man.. where can i get the stock RUU and stock recovery? and also why do we have to re lock the device?
EDIT: i almost forgot, because this problem started after installing a new kernel by franco, so i guess i need to install a stock kernel? where can i get it?
Click to expand...
Click to collapse
I had the same problem with franco's kernel, what I did was, go to recovery and re-flash my xx_rom.zip, then it boots ok. You should try the same, provided you still have the ARHD.zip in your sdcard.
Your device from Indonesia ? I believe this is the RUU for you (same for me too):http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.103.14_release_257076_signed.exe
ckpv5 said:
I had the same problem with franco's kernel, what I did was, go to recovery and re-flash my xx_rom.zip, then it boots ok. You should try the same, provided you still have the ARHD.zip in your sdcard.
Your device from Indonesia ? I believe this is the RUU for you (same for me too):http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.103.14_release_257076_signed.exe
Click to expand...
Click to collapse
thanks ill try it later.. i don't have it on my sdcard, as i've said i erased everything already..
but i guess i'll try the step on top provided by "djpoe" to put the ARHD inside my SD card. hope everything will work..
1 Download ARHD and CWM Recovery
2 Rename ARHD to update.zip and CWM to recovery.img
3 Place update.zip and recovery.img into a folder with fastboot and adb
4 Extract boot.img from update.zip and place in your fastboot folder
5 Put your phone into fastboot mode with unlocked bootloader
6 Flash boot with command 'fastboot flash boot boot.img'
7 Boot recovery using 'fastboot boot recovery.img' command
8 Use command 'adb push update.zip /sdcard/update.zip' to send ARHD to phone
9 Then install rom from update.zip in recovery
For item 7 & 8, maybe you like a safe-proof guide that I posted here
Just replace "D:\HTC\One X\HTC Dev.com unlock\android-sdk\platform-tools>" to your own fastboot/adb folder path
and "recovery-clockwork-touch-5.8.3.1-endeavoru.img" to "recovery.img" if you renamed it.
and "xxx.zip" to "update.zip"
thanks, i'm downloading the files now...
quick question, if i erased all data/cache, the kernel that i installed? will it be deleted as well? because i need to have a stock kernel and i can't see one?
erase all data/system/cache will not delete the installed kernel.
As you said you will follow djpoe's guide, see no. 4 & no. 6 regarding kernel flashing.
Remember the ROM.zip that you have earlier (see Disaster thread), inside the ROM.zip there is a boot_signed.img, that is the stock kernel. But you don't really need the stock kernel, what you need is the AHRD's kernel (see. no.4).
ohhh i see! now that good to know thanks... waiting for the files to be downloaded.. will give you feedback later... fingers cross...
additional question, just wondering, why is it important to re-lock the device before flashing ruu?
i tried to copy the update.zip by doing this
adb push update.zip/sdcard/update.zip
then there are lots of command on the CMD.. see below
C:\fastboot>adb push update.zip/sdcard/update.zip
Android Debug Bridge version 1.0.29
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
-------------------------------
then tried to install it via CWM, apply /sdcard/update.zip
it says
finding update
opening update
E: Can't open sdcard/update.zip
(No such file or directory)
Installation aborted
It should be C:\fastboot>adb push update.zip /sdcard not C:\fastboot>adb push update.zip/sdcard/update.zip
where is your adb files ? In the fastboot folder too ? If yes, try this:
1. C:\fastboot>fastboot boot recovery-clockwork-touch-5.8.3.1-endeavoru.img
2. C:\fastboot>adb devices
enter
C:\fastboot>adb shell
enter then type after ~ # mount sdcard
3. don't close anything, open another cmd prompt
C:\fastboot>adb push update.zip /sdcard
then enter
once completed, choose install from sdcard - choose zip from sdcard, the update.zip should be there
here whats happening. see attachment
mikey0105 said:
here whats happening. see attachment
Click to expand...
Click to collapse
There is no AdbWinUsb.dll in your folder ?
GUYS!!! AT LAST!!!! I'm so happy!!! its all okay now! oh man! this is crazy! hahaha! thank you so much to all!. the feeling is really great! WOOOOOWWWWW!!!!
A link for all the necessary files in a platform-tools folder.zip:
Sorry, this forum doesn’t allow me to submit direct links.
h.t.t.p.w.w.w. dropbox.com/s/tk0v3aogwqhp5qn/platform-tools.zip?dl=0
Unzip and put the platform-tools folder on your C drive.
A part of this guide was made by steven-liesenborgs I have used that to make an all in one guide.
1. Create Temproot:
Go to start – windows accessories – open the command prompt. Connect the USB cable to your phone and connect to your pc (!! Make sure USB debugging is turned on your HTC and if asked for only charging or mass storage choose only charging!!) Now go back to the command prompt and type: (press enter after each line,)
cd c:\platform-tools
adb devices
Normally you will now see numbers and letters meaning your device is connected and recognized.
Type: (in windows 10 you can select and use ctrl-c ctrl-v)
adb push fre3vo /data/local/tmp
adb shell
chmod 777 /data/local/tmp/fre3vo
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
Now you get normally something like the following lines (this may take 2 min)
Buffer offset: 00000000
Buffer size: 8192
Scanning region fb7b0000…
Scanning region fb8a0000…
Scanning region fb990000…
Scanning region fba90000…
Potential exploit area found at address fbb4d600:a00.
Exploiting device…
I f it Works you will see that $ has dissapeared, otherwise try one of the next lines below (!!restart your mobile for each attempt!!)
/data/local/tmp/fre3vo -debug -start 10000000 -end 1FFFFFFFF
/data/local/tmp/fre3vo -debug -start 20000000 -end 2FFFFFFF
/data/local/tmp/fre3vo -debug -start 30000000 -end 3FFFFFFF
/data/local/tmp/fre3vo -debug -start F0000000 -end FFFFFFFF
/data/local/tmp/fre3vo -debug -start E0000000 -end EFFFFFFF
When $ has dissapeared type:
adb shell
Now you will see # instead off $ which means succes. Now type:
exit
2. Change version to downgrade and get superCID and Goldcard
Type:
adb push misc_version /data/local/tmp/misc_version
adb push flashgc /data/local/tmp/flashgc
adb shell chmod 777 /data/local/tmp/*
adb shell
cd /data/local/tmp
./misc_version -s 1.00.000.0
Now you get:
–set_version set. VERSION will be changed to:1.00.000.0
Patching and backing up partition 17…
Then type:
./flashgc
(!! In case of an error message like below, check if you did select charge only in settings menu !!)
Error opening backup file.
If everything worked type:
sync
You can check if everything is fine, type:
dd if=/dev/block/mmcblk0p17 bs=1 skip=160count=10
1.00.000.010+0 records in
10+0 records out
10 bytes transferred in 0.001 secs (10000 bytes/sec)
BACK-UP everything now
3. Temp root and backup
Type:
Exit
adb push su /data/local/tmp/
adb push busybox /data/local/tmp/
adb push fixsu.sh /data/local/tmp/
adb install SuperUser.apk
adb shell chmod 755 /data/local/tmp/fixsu.sh
adb shell/data/local/tmp/fixsu.sh
Backup your data with a backup program on your phone, Rom Manager, Titanium Backup of My backup root for instance.
4. Downgrade to Froyo:
You will need a Rom which you can find following link below :
(There is a rom included the platform-tools.zip from Dropbox, renamed to PC10IMG.zip ready to use, continue to 4a at once) Remember, this is a shipped EU rom, if you need another you can download and find it at same domain from link below or h.t.t..p androidruu.com
h.t.t.p shipped-roms.com/index.php?catcegory=android&model;=Vision
RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e_26.03.02.26_M_release_155556_signed.exe
Download this .exe and activate it as administrator wait till you the first screen, don’t do anything just leave it there.
Click on Start>Run and type %temp%. Then click OK. Look for the newest folder in the temp folder. Double-click on it. (Appdata/local files/temp from user administrator) Open the last folder made (organize!) it will have a name like {4AD69632-45A1-41DE-} Search in that directory for a rom which the update utility did create there. Copy the rom to the platform-tools folder. Close the HTC Android Rom Update Utility, you don’t need it anymore. Change the name of the rom in PC10IMG.zip. Be aware if you can see extensions or not and you didn’t create a .zip.zip file. Check it with right click on it and see properties.
4a
Now copy the PC10IMG.zip to the root of SD card. Take off the USB cable and check in phone your settings, charge only, USB and accept software 3thparty. Restart the Desire. For some reason this goes smoother as turning power off. When the screen goes dark push volume down and power button at same time till you get in the boot menu. Click power button one time and the HTC will search for a file, and start to check the PC10IMG.zip. This will take 1 or two minutes . Now you get a choice to upgrade yes or no select yes with the Volume up or down button and activate the choice with the power button. You HTC will now downgrade to Froyo Android 2.2 firmware 1.34.405.5.
5. Root and Superuser to upgrade
Every file you need is already included in the platform-tools.zip from Dropbox
Source: .h.t.t.p.w.w.w. desire.tode.cz/how-to-root-htc-desire-z-g2-vision
Connect the HTC Desire Z to the computer via USB.
Make sure USB debugging is enabled on the HTC Desire Z by checking Settings » Applications » Development » USB debugging.
On the computer, go back to command prompt an type:
adb push busybox /data/local/tmp/
adb push gfree /data/local/tmp/
adb push hboot-eng.img /data/local/tmp/
adb push psneuter /data/local/tmp/
adb push recovery-clockwork-3.0.2.4-vision.img /data/local/tmp/recovery.img
adb push root_psn /data/local/tmp/
adb push su /sdcard/
adb push Superuser.apk /sdcard/
adb shell
chmod 755 /data/local/tmp/*
/data/local/tmp/psneuter
NOTE: You will drop out of the shell after this command to platform-tools folder, type:
adb shell
cd /data/local/tmp
./gfree -f -b hboot-eng.img -y recovery.img
As it is very important that the hboot was installed correctly gfree calculates md5sums of the partition. It will calculate the following 3 checksums
md5sum #1 - checksum of partition 18 before the installation
md5sum #2 - checksum of the hboot image that should be installed
md5sum #3 - checksum of partition 18 after the installation
The messages that you what to see are either/or
md5sum #1 == md5sum #2 – the hboot image is already installed -> skipping installation
md5sum #3 == md5sum #2 – the hboot image was successfully installed -> OK!
If you get a different error message then DO NOT REBOOT. Check everything again and try again
If gfree worked correctly continue with, type:
./root_psn
sync
reboot
The HTC Desire Z is now rooted with S-OFF, the Engineering HBoot & the ClockworkMod Recovery.
6. Install a new Rom
This is a tricky part since most roms will just fail to install, at least on shipped models, the roms from Guhl99 (XDA Forums)do the job. There is an interesting part to these roms also, which I Like. You really should check his work out.
In case you prefer a Cyanogenmod version 10.1 Guhl99 made one also you can find it via XDA forums, in the platform-tools folder there is a working Cyanogenmod 10.1 cm-10.1-20140309-UNOFFICIAL-vision.zip in case you don’t like spoofing. If you do like it, check out Guhl99 his work which you should do anyway in case of HTC Desire 7.
In your platform-tools folder select AndromadusAOSP4.2-vision-pff-16062013.zip an AOS Android4.2.2 and gapps-jb-20130301-signed.zip (they are already present in the platform-tools.zip from Dropbox)
Copy them to the root of your SD card, download Rom Manager from link below and install it:
If you can’t download it because your SD is occupied release the USB cable from your phone.
h.t.t.p.w.w.w. apk4fun.com/apk/2119/
Open Rom Manager, select Recovery Setup and activate the 2th ClockworkMod option, select as option the 3x version. Go back and select now the 1th ClockworkMod option and activate it to flash, it will ask for permission which you grant. Now Clockworkmod has root acces as Superuser. Go back to main menu from Rom Manager and select Fix Permissions. Now, check if everything in your Phone settings is still correct. Charge only, USB debugging, allow unknow installs etc. Take the USB cable out of your Phone. In Rom Manager menu select Reboot to Recovery and activate it, no need to push buttons this time the HTC wil go to Rom Manager bootmenu automatic by restart after showing the HTC start screen first.
7. Rom Manager Bootmenu
Another part which need some attention to proceed. In this menu the Volume up and down button are used to scroll. The power button is used to get to out of a submenu. The Photo button, on right lower side is used to activate the selection. With this knowledge in mind it is easy to navigate and delete Factory Settings, then Cache and under advanced menu the Dalvik Cache. Return to main menu pressing the Power button and select install zip from SD. Select ROMAndromadusAOSP4.2-vision-pff-16062013.zip and activate it with Photo button. The Desire will now install AOS Android 4.2.2. When it is finished select Install a zip from SD again and this time select gapps-jb-20130301-signed.zip and install it. When ready select reboot in Rom Manager and the HTC will restart, which will take some minutes, and it will run now on Android 4.2.2. Connect the HTC to USB Cable and copy the 3 files from platform-tools/PFF folder to your SD. Use a file manager on your HTC to search and install them to play with spoofing.
Now you are ready: This rare quality phone with qwerty keyboard will be at your service for some years more.
Still works! Thanks!