Related
Cant root my evo keeps giving me the main Version is older! Update Fail!” error!
ive tried
http://myevo4g.net/simple/?page_id=13
http://forum.xda-developers.com/showthread.php?t=706411&highlight=1.47.651.1
http://forum.xda-developers.com/showthread.php?t=701004&highlight=1.47.651.1
http://forum.xda-developers.com/showthread.php?t=720565
any help thanks
phone info
firmware
2.1-update1
basband
2.05.00.06.10
kernal
2.69-789bf291
[email protected]#1
build
1.47.651.1 cl195459 release-keys
software
1.47.651.1
you also can't read forum rules
Search for simple root...since your still 2.1
ive done the simple root gives me the same error
Just redo step 2...If you can't root with Simple root then maybe you shouldn't be rooting your phone at all
ive tried several time everytime it checks the PC36IMG.zip on the evo it gives me that older version error. and to just reboot
are you in charge only mode, also did you download Dot Net Framework 4
i do have the dot 4 and im in htc sync mode with debug enabled
the img gets pushed its just on the evo when its checking the img it gives me the older version error.
You need to use the SimpleRoot version for 1.47. You're most likely using the first SimpleRoot he developed.
Sent from my PC36100 using XDA App
EyeslikeOlives said:
You need to use the SimpleRoot version for 1.47. You're most likely using the first SimpleRoot he developed.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yes, there are two simpleroots.
i downloaded the version thats on this site myevo4g.net its the 1.47.651.1. edition
and simple root is updated
o and on the comad prompt on the pc it gives me one error
/sdcard/flash_image: Permission denied
is that normal
This root method is laughably easy...the hardest thing is downloading SDK...
http://forum.xda-developers.com/showthread.php?t=741294
http://www.youtube.com/watch?v=GAqTEAWxh7U
hecklbrg said:
This root method is laughably easy...the hardest thing is downloading SDK...
http://forum.xda-developers.com/showthread.php?t=741294
Click to expand...
Click to collapse
ok will try
foresure84 said:
http://www.youtube.com/watch?v=GAqTEAWxh7U
Click to expand...
Click to collapse
seen it and tried it gave me same error thanks tho
okay step by step what did you do
ok i cleared all the memory and formated the sd card
i made sure that he evo was in sync mode and debuging enabled
after it conected to pc i opend up simple root the latest one it updated and instaled the update.
after restarting pc just to make sure everthing was good stated simple root again
checked phone for sync and debuging
cliked root comand prompt came up everything got pushed
only error that i saw was that /sdcard/flash_image: Permission denied
after that evo bootoed to the dancing green men
evo was checking the PC36IMG.zip theb it say main Version is older! Update Fail
then ask to reboot and i push up volume to reboot
flash image or recovery image also send me your email i think i have something that may help
foresure84 said:
flash image or recovery image also send me your email i think i have something that may help
Click to expand...
Click to collapse
u talking about step 2 on simple root?
if so i dont even click on it cause step one fails.
found this but dont understand how to do it.
im in a comand promt now and ive navigated to the simple folder.
http://forum.xda-developers.com/showpost.php?p=7524114&postcount=1461
after each command hit enter
cd C:\android-sdk-windows\tools or where ever you installed the sdk folder
adb shell "cat /sdcard/flash_image > /data/local/flash_image"
adb shell "chmod 755 /data/local/flash_image"
adb shell "/data/local/flash_image misc /sdcard/mtd-eng.img
adb reboot bootloader
Ok guys, first of all Scotty2 gets all the credit for the program R&D. I used my device as a test bed and have tried a couple different kernels (Gr8Gorilla's O/C Kernel and the stock kernel).
Now for the boring stuff ...
This is a very invasive way of rooting your device but the benefit is TRUE S=Off and root privileges throughout the system. As such, you do this at your own risk and if you brick your device neither Scotty2 nor myself are responsible, YOU ARE!!! Do this at your own risk!!!
This is not for the faint of heart and if you have any reservations about doing things like this do not do it.
This process will do three things for your device. I will explain them here:
1. It will set up Super CID on your device allowing you to flash any carriers rom (not just tmobile). Giving you more freedom with your choice of software. The software still needs to be device specific to the glacier for compatability reasons though. Like vodafone glacier roms etc.
2. It will subsidy unlock your device. In other words, it will SIMUNLOCK your phone allowing you to use an AT&T sim card and so on in your device without needing the unlock code from HTC.
3. Most important of all it will turn the RADIO S=Off. This is the ultimate S=Off because the radio is what controls the security flag in the first place. Once you turn it off here it is off everywhere and will allow you pure unadulterated access to your device.
This process will not change your bootloader (unless your on 0.86.0000 and you follow the optional steps).
Now, you may be asking "Why do this? I already have root from your other guide and it has given me r/w access to system and recovery. I thought this meant we had permanent S=Off." This is only partially true. We have had an engineering bootloader and "Label" s=off not radio s=off. When you turn the security off in radio it is off permanently no matter what hboot you have installed engineering or otherwise. However, it is optional but you can still copy the engineering hboot over and it will allow you to flash whatever you like without (as much) fear of bricking your device.
This guide assumes you know how to use ADB. If you do not there are guides all over XDA to show you how. There is even a really good one in this forum. Also here is a video on how to setup adb discovered by topgun303: http://www.youtube.com/watch?v=1UF5w1dKe2U
*NOTE*
For some reason this process can bork your recovery. If you notice after following the steps below that in order to reboot from recovery you have to uninstall/reinstall the battery and hit the power button, just install/reinstall clockwork recovery through Rom Manager in the android market and it will fix your problem.
CONFIRMED: Guide does work for pre-OTA devices!!! Thanks xanz!
Here we go:
If you are already permarooted per the other guide just follow the first 11 steps.
Make sure you have visionary installed on your device. (If you were already permarooted w/s=off ignore this step.)
Download this file:
http://www.mediafire.com/?s7afymwe2wb3x60 New version of gfree with more options! See below.
md5sum: b73c56ca0e21664c5756d4ad295063c5
1. Now unzip the file into your SDK tools directory.
2. Plug your device into your computer.
3. Now open explorer and hold down shift at same time you right mouse click on your SDK tools directory (platform-tools if you have the R8 version of the SDK). Select open command window here. If you are in linux (ubuntu) right mouse click on your SDK tools folder, choose actions, and choose open command window(or whatever it's called). Otherwise, open a command prompt and cd your way to your SDK tools directory.
4. Type "adb push gfree /data/local" and hit enter.
Optionally, you could dl the file to your phone use androzip or something like it to unzip the file and then use root explorer to move the file named gfree to /data/local. Not the gfree.h file. All the other files are source code inlcuded for the gnu license. This would skip the first 4 steps.
5. Now unplug your device from the computer.
6. Run visionary to gain temp root. (If you were already permarooted w/s=off ignore this step.)
7. Open terminal emulator on your device, type "su", and hit enter to gain root privileges.
8. Type "cd /data/local" and hit enter.
9. Now type "chmod 777 gfree" and hit enter to make the program executable.
10. Type "./gfree -f" and hit enter.
New features in gfree.
gfree usage:
gfree [-h|-?|--help] [-v|--version] [-s|--secu_flag on|off]
-h | -? | --help: display this message
-v | --version: display program version
-s | --secu_flag on|off: turn secu_flag on or off
-c | --cid <CID>: set the CID to the 8-char long CID
-S | --sim_unlock: remove the SIMLOCK
With the new features you can turn off one thing at a time. You can also turn security back on and set the CID back to stock if you wish. To turn simlock back on you still have to follow the revert procedures on this page as the information that is patched to turn the lock off is encrypted and we can't write back to it other than restoring the entire image.
So, if you wanted to leave simlock on but turn security off and set super CID the command would be "./gfree --secu_flag off --cid 11111111" + enter. The -f switch after ./gfree that is now in the above step (./gfree -f) just tells gfree to patch everything.
11. Wait for the program to finish and then reboot into HBoot to see if S=Off. Also, check your bootloader version. If it says s=off and has bootloader version 0.86.0000 it worked.
If you already had hboot 0.85.2007 you can check it through the hboot menu. It gives you an option for "system info" in the hboot menu. Highlight it and hit power. It should say CID = 11111111 or something like that. If it does your golden.
Congratulations!
12. If this is the first time you have rooted your device you will need to run visionary again (temproot w/set system r/w after root checked and then attempt permroot) to make root privileges permanent and then reboot again. Now "su" should work properly for you.
Gfree writes a backup of the file that it patches named Part7backup-numbers.bin on your sdcard. I suggest putting this file in a safe place as it is the only way to revert if you need to.
[Optional] Steps to flash engineering bootloader.
1. Restart your phone and plug it back into your computer.
2. Download this file: http://www.megaupload.com/?d=NN5726Z8
md5sum: df4fd77f44993eb05a4732210d2eddc6
3. Copy the file to your SDK tools directory.
4. Open a command prompt again and cd into your SDK tools directoty (platform-tools if your on the new R8 SDK).
5. Type "adb push hboot_dhd.nb0 /data/local" and hit enter.
6. Now open terminal on your device and type "su" and enter to gain root priviliges.
7. Type "cd /data/local" and enter.
8. Now type "dd if=hboot_dhd.nb0 of=/dev/block/mmcblk0p18" and hit enter.
9. You should see something like: 2048 bytes in 2048 bytes out 1048576 bytes copied blah blah blah.
10. Now restart the device into hboot and check if your bootloader version is 0.85.2007. That is what you want to see.
Congratulations, you now have a TRUE root and engineering bootloader on your shiny MT4G!!!
Procedure to revert
1. Rename the part7backup file that you already have to something just so you know that it is the original backup.
2. Open up terminal emulator or adb shell and type "su" + enter to get root privileges.
3. Type "cd /data/local" and hit enter.
4. Now type "./gfree -f" + enter to run gfree again. It will disable wp on the emmc and remove the brq filter in the kernel. (as well as make another backup, which you can delete if you wish)
5. Now run the "dd if=/where/your/part7backup-numbers.bin of=/dev/block/mmcblk0p7" and it should show the output:
xxxx bytes in
xxxxbytes out
xxxxxxxxxx copied in blah blah blah
6. Run "sync" and then reboot. (I didn't do this and it worked fine but it won't hurt either. )
If you have the engineering hboot 0.85.2007 installed you will still be showing s=off when you do the above revert steps. Follow these steps to reflash the stock hboot and turn s=on:
Download this file and unzip it to /sdcard on your device.
unroot.rar
http://www.mediafire.com/?12oi5elu7v2y8og
md5sum: aad4e64126cf8d92d7e8b5abb48fdadd
Terminal Emulator Method
1. Open up terminal editor on your device.(I prefer this method b/c you can see the output.)
a. Type "su" + enter to gain root privileges.
b. Type "cd /sdcard/unroot" + enter.
c. Type "sh unroot.sh" + enter.
d. Follow the onscreen prompts.
File Explorer Method
2. Open root explorer, sufbs, or some other file browser with root access.
a. Navigate to /sdcard/unroot.
b. Click on unroot.sh and allow it to run. Some file browsers ask permission before they execute scripts.
c. Wait 18 to 20 seconds and reboot your phone into the bootloader to check if S=on.
You now have S=ON again.
Here is a pic of the stock HBoot 0.86.0000 with S=Off to prove it.
If already on ENG bootloader, S-OFF, and perm rooted via your other guide would we be able to just run gfree for the "radio/sim" unlock?
Genocaust said:
If already on ENG bootloader, S-OFF, and perm rooted via your other guide would we be able to just run gfree for the "radio/sim" unlock?
Click to expand...
Click to collapse
Yes, that's what I did. Good call btw! I wrote the guide in a hurry just before heading to work and knew I would miss something.
My MyGlacier 4G MINE!!!
u could use root explorer to place the gfree file in data local couldn't u?
Yes you could use root explorer. I am going to revise this as soon as I get time. I'm at work right now.
As for the optional steps, you wouldn't need to do them if you already followed the other permroot guides successfully b/c you should alread have hboot 0.85.2007 installed.
My MyGlacier 4G MINE!!!
so is the 0.85.2007 is the one we want to be on?
mrpanic7 said:
my bootloader is 0.85.2007 is this the sweet one i want or the stock one?
Click to expand...
Click to collapse
Good to go. You have the engineering hboot.
Should work from either one as long as you have some kind of root access.
But ... Keep that one.
My MyGlacier 4G MINE!!!
sweet thanks, and the whole talk about subsidy unlock and flashing other device roms, is that part of the hboot im running, or the gfree file ?
Hey grankin01 this is what i have on my screen. Bec i just got this phone from warranty claim.
GLACIER PVT ENG S -OFF
HBOOT-0.85.2007 (PD1510000)
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
oct 11 2010, 12:44:14
@mrpanic7, no its part of the gfree patch.
@topgun303, what kernel version are you running? Stock?
My MyGlacier 4G MINE!!!
sweet thanks will test tonight and comment when everything is done! how do we know if hte gfile goes thru successfully? since im already permarooted
grankin01 said:
@mrpanic7, no its part of the gfree patch.
@topgun303, what kernel version are you running? Stock?
My MyGlacier 4G MINE!!!
Click to expand...
Click to collapse
Kernal version: I have not flashed anything other kernal yet. This is what came with my phone.
2.6.32.21-g899d047
[email protected] #1
tue oct 26 16:10:01 CST 2010
Hey grankin01 I dont have adb steup, can you provide workaround for that. Meaning without adb.
Awesome man. Great job. Just to be clear. After unzipping the file, all of them need to go in the data/local folder yes?
So we can use root explorer to oaste the file, then the termunal steps?
Sent from my rooted w/s=off HTC Glacier on Iced Glacier Dark Froyo Themed 1.1.1 using XDA App
You should be able to use root explorer and yes put all files in /data/local including the hboot_dhd.nb0 file if you are going to do the optional steps.
Edit: Added mention of root explorer method between steps 4 and 5.
My MyGlacier 4G MINE!!!
hey grankin01 my phone is on engineer bootloader right now. what are the advantages of engineer bootloader vs bootloader version 0.86.0000?
Also if i flash bootloader version 0.86.0000, can i go back to engineer bootloader.
u r the maaan
after trying everything i got s=off thanx to you...but 1 lil isue the root did not stick for me after checking hboot to see if i got s=off
topgun303 said:
hey grankin01 my phone is on engineer bootloader right now. what are the advantages of engineer bootloader vs bootloader version 0.86.0000?
Also if i flash bootloader version 0.86.0000, can i go back to engineer bootloader.
Click to expand...
Click to collapse
Eng hboot will let you flash anything you want. Stock hboot will still limit your choices.
Yes you can just do the optional steps from the OP to go back to eng hboot. Actually having stock hboot will let you see if it worked without having to do anything special.
My MyGlacier 4G MINE!!!
wadie said:
after trying everything i got s=off thanx to you...but 1 lil isue the root did not stick for me after checking hboot to see if i got s=off
Click to expand...
Click to collapse
So this did work w/stock device and kernel?
Try running visionary r14 and doing permroot option. Being a stock rom you may still have to fiddle with it a little. Not quite an exact science.
My MyGlacier 4G MINE!!!
So the bootloader version 0.86.0000 provides simunlock correct? If i read correct from the first page of op. For now i think i will stay on engineer hbootloader.
Also one more thing op, I found a great video on how to setup adb. I have already got my adb setup using this. If u like you can post it in the op section. http://www.youtube.com/watch?v=1UF5w1dKe2U
Okay, so i received my G2 today, and trying to root it. I have two rooted phones with CM6 on them (Nexus One, and MyTouch3g), I rooted the nexus back in the day before the one click root applications, so i am not new to rooting.
Before we flame, i DID Google, and search the XDA threads here. But I'm still getting some problems, ill try to explain.
I'm using the CyanogenMod Wiki tutorial.
Code:
If the HTC Desire Z is already running 1.34.707.3 or lower you can skip to the Gaining Temporary Root Access section.
My firmware is a 1.22.###.# wich leads me to believe that i am below the required firmware.
I attempted root per the rest of the tutorial, got to the gfree script and got an error stating it could not power cycle the something.
Ive been reading and to my understanding, this is caused by not having the proper firmware.
Okay, so i started over. and started at the top with Downgrade to 1.34.707.3
I got to step 8
This is step 6-8 for reference
Code:
# Copy the 1.34.707.3 firmware to the root of the SD card (NOT in any folders).
# On the computer, open terminal and run the following command:
adb reboot bootloader
# Follow the on screen directions, on the HTC Desire Z, on flashing the 1.34.707.3 firmware.
# Once finished you can can continue to the next section.
so i adb reboot bootloader, [email protected] reboots to HBOOT
however i have a standard HBOOT screen. I can go to Fastboot, and back to HBOOT.... when i try to go to recover i get the phone/exclamation triangle icon (as expected, as i don't have a custom recovery yet).
So where it says "Follow the on screen directions, on the HTC Desire Z, on flashing the 1.34.707.3 firmware. ", i am not getting any such directions, just the basic HBOOT screen.
ANY help would be appreciated.
stshannon said:
Okay, so i received my G2 today, and trying to root it. I have two rooted phones with CM6 on them (Nexus One, and MyTouch3g), I rooted the nexus back in the day before the one click root applications, so i am not new to rooting.
Before we flame, i DID Google, and search the XDA threads here. But I'm still getting some problems, ill try to explain.
I'm using the CyanogenMod Wiki tutorial.
Code:
If the HTC Desire Z is already running 1.34.707.3 or lower you can skip to the Gaining Temporary Root Access section.
My firmware is a 1.22.###.# wich leads me to believe that i am below the required firmware.
I attempted root per the rest of the tutorial, got to the gfree script and got an error stating it could not power cycle the something.
Ive been reading and to my understanding, this is caused by not having the proper firmware.
Okay, so i started over. and started at the top with Downgrade to 1.34.707.3
I got to step 8
This is step 6-8 for reference
Code:
# Copy the 1.34.707.3 firmware to the root of the SD card (NOT in any folders).
# On the computer, open terminal and run the following command:
adb reboot bootloader
# Follow the on screen directions, on the HTC Desire Z, on flashing the 1.34.707.3 firmware.
# Once finished you can can continue to the next section.
so i adb reboot bootloader, [email protected] reboots to HBOOT
however i have a standard HBOOT screen. I can go to Fastboot, and back to HBOOT.... when i try to go to recover i get the phone/exclamation triangle icon (as expected, as i don't have a custom recovery yet).
So where it says "Follow the on screen directions, on the HTC Desire Z, on flashing the 1.34.707.3 firmware. ", i am not getting any such directions, just the basic HBOOT screen.
ANY help would be appreciated.
Click to expand...
Click to collapse
Which phone do you have? You stated that you have a G2 (which is an HTC Vision) but you're referencing a guide for a Desire Z
Sent from my T-Mobile G2 using XDA App
OriginalGabriel said:
Which phone do you have? You stated that you have a G2 (which is an HTC Vision) but you're referencing a guide for a Desire Z
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Hmmmmmm.... if its as simple as im using the wrong guide, im going to feel really dumb.
Im clicking through the CyanogenMod wiki again, and yes i see after i click HTC Vision form the main page, theres two options, and apparently, i am using the Desire Z (which i thought was the codename for my us version of the HTC device).... i will make another attempt using the proper (hopefully) tutorial.
God i feel like such a newb.
Thanks for getting me pointed in the right direction tho.
stshannon said:
Hmmmmmm.... if its as simple as im using the wrong guide, im going to feel really dumb.
Im clicking through the CyanogenMod wiki again, and yes i see after i click HTC Vision form the main page, theres two options, and apparently, i am using the Desire Z (which i thought was the codename for my us version of the HTC device).... i will make another attempt using the proper (hopefully) tutorial.
God i feel like such a newb.
Thanks for getting me pointed in the right direction tho.
Click to expand...
Click to collapse
Damn kids these days!
Here you go: http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
Sent from my T-Mobile G2 using XDA App
I'll be up for a bit, post back if you run into any problems; I'll try to take a peek back here often.
Sent from my T-Mobile G2 using XDA App
okay, still fail, same power cycle emmc (or whatever) failure.
Got MSN we can keep the thread fairly clean?
I sent you a PM with my contact info, if you are up for helping via MSN or phone.
Well, OriginalGabriel must have gone AFK, or to sleep or something.
Anyone else with advice would be appreciated.
Im using the correct Wiki Guide for Tmobile G2
I get to the enter "/data/local/gfree -f" in the terminal emulator, and it fails. It fails power cycling the eMMC (or something similar), and the next 3 commands do not work either (assumably because the eMMC did not power cycle properly.)
Baseband Version 12.28b.60.14eU_26.03.02.26_M
Kernel Version 2.6.32.17-g9ab3677 [email protected]#1
Build number 1.22.531.8 CL277427 release-keys
im running into the same problem as well. as soon as i get to step where i enter in
/data/local/gfree -f
in the terminal emulator, i get the same eMMC failure message and the remaining 3 commands don't work
stshannon said:
Well, OriginalGabriel must have gone AFK, or to sleep or something.
Anyone else with advice would be appreciated.
Im using the correct Wiki Guide for Tmobile G2
I get to the enter "/data/local/gfree -f" in the terminal emulator, and it fails. It fails power cycling the eMMC (or something similar), and the next 3 commands do not work either (assumably because the eMMC did not power cycle properly.)
Baseband Version 12.28b.60.14eU_26.03.02.26_M
Kernel Version 2.6.32.17-g9ab3677 [email protected]#1
Build number 1.22.531.8 CL277427 release-keys
Click to expand...
Click to collapse
Shut down adb.exe by using ctrl alt del and then try again. It should start up again all by itself for the perm root process.
EdKeys said:
Shut down adb.exe by using ctrl alt del and then try again. It should start up again all by itself for the perm root process.
Click to expand...
Click to collapse
Tried that, end processed the adb.exe after i (in cmd window on computer)
Code:
adb push gfree /data/local
adb shell chmod 777 /data/local/gfree
but before i (in terminal emulator on G2)
Code:
/data/local/gfree -f
Still get same power cycle fail on the eMMC.... should i unplug it from the computer when i run gfree? think power from USB is keeping the eMMC powered and wont let it cycle? <shrug>
stshannon said:
Well, OriginalGabriel must have gone AFK, or to sleep or something.
Anyone else with advice would be appreciated.
Im using the correct Wiki Guide for Tmobile G2
I get to the enter "/data/local/gfree -f" in the terminal emulator, and it fails. It fails power cycling the eMMC (or something similar), and the next 3 commands do not work either (assumably because the eMMC did not power cycle properly.)
Baseband Version 12.28b.60.14eU_26.03.02.26_M
Kernel Version 2.6.32.17-g9ab3677 [email protected]#1
Build number 1.22.531.8 CL277427 release-keys
Click to expand...
Click to collapse
stshannon said:
Tried that, end processed the adb.exe after i (in cmd window on computer)
Code:
adb push gfree /data/local
adb shell chmod 777 /data/local/gfree
but before i (in terminal emulator on G2)
Code:
/data/local/gfree -f
Still get same power cycle fail on the eMMC.... should i unplug it from the computer when i run gfree? think power from USB is keeping the eMMC powered and wont let it cycle? <shrug>
Click to expand...
Click to collapse
are you sure all the files were pushed to the g2? pm me with your phone number and i'll call you to help, if I can.....
kimchi29 said:
im running into the same problem as well. as soon as i get to step where i enter in
/data/local/gfree -f
in the terminal emulator, i get the same eMMC failure message and the remaining 3 commands don't work
Click to expand...
Click to collapse
What step is that ^^^^^ command in????
Heres the commands:
Keep in mind these are the commands after you temp root with Rage in the WIKI.
This command on the computer:
Code:
adb push gfree /data/local
Then on phone terminal emulator:
Code:
# cd /data/local
# chmod 777 gfree
# ./gfree -f
# sync
Then lock in root;
Code:
# /data/local/tmp/root
# sync
Are you guys following the Wiki HERE.
By the way as soon as a MOD see this thread its either gonna get locked or moved for being posted in the wrong section.
EdKeys said:
are you sure all the files were pushed to the g2? pm me with your phone number and i'll call you to help, if I can.....
Click to expand...
Click to collapse
PM Sent
joemm said:
What step is that ^^^^^ command in????
Heres the commands:
Keep in mind these are the commands after you temp root with Rage in the WIKI.
This command on the computer:
Code:
adb push gfree /data/local
Then on phone terminal emulator:
Code:
# cd /data/local
# chmod 777 gfree
# ./gfree -f
# sync
Then lock in root;
Code:
# /data/local/tmp/root
# sync
Are you guys following the Wiki HERE.
By the way as soon as a MOD see this thread its either gonna get locked or moved for being posted in the wrong section.
Click to expand...
Click to collapse
No, im using the one on the CyanogenMod Wiki page.
stshannon said:
No, im using the one on the CyanogenMod Wiki page.
Click to expand...
Click to collapse
Why not use the XDA Wiki? Known to work time and time again.
Hi All,
The details of the issue are given below, but it's a long-ish post, so to summarise:
-Stuck on USB-Bricked Froyo RUU, hboot 0.93.
-Need root in order to flash misc fix for unbricking, but need unbricked device in order to either:
--root (unrevoked) or
--downgrade to use modaco root method (r6-desire-root-alt).
->I'm out of ideas/search terms and in dire need of a solution.
Full details below:
After spending all day yesterday and all morning today scouring the internet, researching, downloading, attempting solutions etc etc I am at my wit's end with this problem. I am no major n00b but I do not have the level of understanding that some people on this forum possess, hence why I am posting this.
The starting point was a rooted (unrevoked method) s-off Desire running MIUI. After doing a routine backup from ROM manager, the device failed to boot (got stuck at splash screen)
Upon trying to restore a backup I discovered to my horror that my recovery (Amon-RA) was unable to access the SD card, and ADB was also unable to see the device.
In my web-voyages since then I have incidentally discovered the method for re-enabling SD card access, but at the time I could not understand what was happening, and after several tests (different SD cards, formatting, data wipe, reflashing AlphaRev spl) came to the (catastrophically incorrect) conclusion that there must be something wrong with my hboot, and that the only hope was to apply an RUU by PB99IMG method.
Soo... applied a WWE Froyo RUU: "RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed". The plan was then to re-root the phone and restore my backup, to return to its original state.
The RUU put my hboot to 0.93, and USB-bricked the phone.
Hence, Unrevoked3 is out of the question, as the computer does not acknowledge the phone whatsoever when booted into the ROM, which is the required starting point for unrevoked.
So obviously I went in search of anti-USB-Brick medicine, only to discover that the misc-fixing methods available require a rooted ROM (to flash the update.zip)
Further searching uncovered a suggestion of using the step1 part of r6-desire-root-alt Modaco rooting method, since it requires only fastboot to work, then applying the misc fix to un-USB-brick and hence proceed with unrevoked.
Sadly this did not work, presumably because of my 0.93 hboot situation (the method states compatibility only with 0.80 and below). After the processing of the test image stage, android system recovery gave the response "could not verify whole-file signature" to any update.zip flashing attempts.
So I went for another swim in the RUU sea to obtain "RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed" in the hope of jiggling hboot back to 0.80 and hence enabling r6-desire-root-alt etc. This failed because it is an earlier version, and hboot would not allow the update.
So I looked to the downgrade utility, accessible from the Desire Index in the Desire Android Development forum, but this again requires PC connectivity when booted into a ROM, and is hence unusable.
So I am truly, enormously stuck. I can't root without unbricking, and I can't unbrick without root.
I'm sure there must be a way round it, and it's possible that the veterans on this forum will see the solution immediately, but I am totally out of ideas and on the point of desperation, as I rely heavily on my phone for organisation, email and music functions, all of which are very important to me.
Any and all suggestions would be very much appreciated
Many thanks
Mike
RESOLVED
For anyone else who is suffering a similar problem, I eventually discovered a solution (in all likelihood the ONLY solution to an unrooted, 0.93 hboot, USB-bricked device) at this thread:
http://forum.xda-developers.com/archive/index.php/t-813476.html
I quote the post in this thread by quanchi on 6th November 2010, 10:30 PM:
I have added clarification points in bold where possible, to maximise the usefulness to others. This method is a life-saver for people in this most tricky of situations, and could potentially be useful for other scenarios, although perhaps less likely to be the only option.
"This is a specific situation - usb brick and totally stock rom, recovery and hboot. It's not required for people who have a modified recovery and a rooted rom. It's easy like 1-2-3.
Before doing anything else enable the Debug Mode in the Applications / Dev menu
1. Download the rageagainstthecage exploit from the authors site:
http://c-skills.blogspot.com/2010/08/please-hold-line.html
NOTE: The link is in the first paragraph (the word 'these'), directly linked to:
http://stealth.openwall.net/xSports/RageAgainstTheCage.tgz
at this moment in time
2. Download the flash_image and misc (mtd0.img) partition image from this thread.
http://forum.xda-developers.com/showthread.php?t=691639&highlight=usb+brick
Modify the mtd0.img according to your phones CID (how to get the CID also explained in the thread)
NOTE: I'd recommend using the CID generator provided, to better ensure the chances of success, particularly if inexperienced with hex editing (as I was)
2. Download Android Terminal Emulator from the Market
NOTE: This is the one by Jack Palevich. For the specific file paths given here to work, you must use this emulator. However, the method could be adapted to work with any emulator, as long as it creates a folder in internal memory that it has access to like 'shared_prefs' in this case
3. Copy the exploit binary (rageagainstthecage-arm5.bin), the flash_image and modifed mtd0.img to the sdcard via an external card reader
4. Start the Terminal
5. Copy the files to the Terminal app data directory (the only place on the data partition you will have write access while running the Terminal), and make the binaries executable
cat /sdcard/rageagainstthecage-arm5.bin > /data/data/jackpal.androidterm/shared_prefs/rageagainstthecage-arm5.bin
cat /sdcard/flash_image > /data/data/jackpal.androidterm/shared_prefs/flash_image
cat /sdcard/mtd0.img > /data/data/jackpal.androidterm/shared_prefs/mtd0.img
cd /data/data/jackpal.androidterm/shared_prefs/
chmod 755 rageagainstthecage-arm5.bin flash_image
IMPORTANT: The shared_prefs folder only exists after you change the preferences in the terminal emulator. So before commencing, change the text colour or something. Secondly, the '>' (right-facing angle bracket) characters are NOT just side effects of a copy-and-paste process, they are in fact NECESSARY for the cat function to operate as intended (I imagine experienced folks and linux users would already know this, but I didn't)
6. Run the exploit
/data/data/jackpal.androidterm/shared_prefs/rageagainstthecage-arm5.bin
After the exploit exits/finishes there should be a short system freeze, followed by inablity to issue any command from the terminal (don't worry). Exit the Terminal by long pressing HOME and force close the Terminal app from the Application Manager
NOTE: You can tell when it's finished because its final statement is 'forked #number# childs' (in my case it was 'forked 3303 childs')
7. Start the terminal again, a root prompt should be visible
NOTE: What this means is the $ character at the beginning of the line becomes a # character
8. Flash the misc partition
cd /data/data/jackpal.androidterm/shared_prefs
./flash_image misc mtd0.img
9. Reboot
Done and done
Enjoy"
Hi! Does your problem involve being stuck in an htc screen with 4 warning signs on each side and i connect to Computer and disconnect show a bootloader version and just one option - RUU?
This has been very interesting read.
im not good at hex editing and my cid is 02__001 which comes up as invalid with the generator.
im wondering what to do ? i want to keep a mtd0 file handy from before.
hi
i've a desire usb bricked with hboot 0.93 s-off
now i follow the instruction and i have the modified image and all the rest of the file but when i execute the exploit from the terminal emulator and i try to restart the emulator it doesn't restart (i've force close it after the forked 3302 number child message)
can you help me?
wooow i solved by myself
1. move the flash_image and mtd0.img to data
2. open the android terminal emulator
3. su logcat (root permission)
4. cd /data
5. ./flash_image misc mtd0.img
6. reboot
fireblade84 said:
wooow i solved by myself
1. move the flash_image and mtd0.img to data
2. open the android terminal emulator
3. su logcat (root permission)
4. cd /data
5. ./flash_image misc mtd0.img
6. reboot
Click to expand...
Click to collapse
many lovely thanks for SU LOGCAT
brick?
cellular south samsung galaxy showcase. need help. debugging not working. external sd will not mount on reboot. cannot flash. cannot root. system path not found. how do i get a working kernel? had dj20 with a universal kernel 2.1, was going froyo but didnt get the build right (bad file) and crossed kernel platfrorms. how do i get back to 2.1? or stock?
my question
just terminal emulator and logcat should work?
As you see in this post : http://forum.xda-developers.com/showthread.php?t=1162971 , a method to downgrade (or update) when having the error ... so the thing is Gingerbreak was patched in 2.3.5 , or other older versions so the only simple thing is to use another exploit , lets cut through into it , and please post your feedback :
For whoever wants temproot for the use of superuser , Option 1 is the only option for Locked BL+S-ON , but after finishing option 1 , your sdcard will be unmounted (mount it from settings) , and bluetooth won't work unless the phone is rebooted , which means when the root is gone , Option 1 can't allow you to flash CWM , or generally edit /system by any way , but stuff more like SetCPU , Titanium Backup , and similar root apps work ...
OPTION 1
IF you aren't seeing the # in the command prompt that is because you aren't rooted , so you have to use zergRush or Tacoroot , but zergrush is easier :
1. download the temproot.zip and extract it somewhere
2. enable USB debugging on your Wildfire S
3. go to market and download superuser ( doesn't root your phone but it may help )
4. plug your phone and run temproot
5. just watch it , if you see between the lines overseer found a path ,then it worked
6. now to make sure you gained root , try turning on bluetooth , if it did then you are not rooted , also when you open the command prompt , if you type in "adb shell" and seen # , then it worked , if you saw $ , type in the cmd "su" , it should change to # , if it didn't check your phone (superuser will ask to allow or not , just allow it)
This is what i got , please tell if it worked , because it worked for me so it should for you !
I am new to xda in posting and replying stuff , but i know how forums work , so if i asked a question of how this forum works , plz answer .
OPTION 2
I've Got feedback earlier that zergRush didn't work , then this method will state the second root option which is kinda harder and picky-er , so let's cut through into it ...
This exploit is called Tacoroot , and it is mostly used for adb shell root purposes , not for superuser purposes
1. Extract the Tacoroot simple.zip somewhere and enable USB Debugging at settings >applications>development
2. Enable USB debugging from Settings> Applications > Development
3. Now run Step1
4. After the phone reboots to recovery , press both vol + and power button in the same time until a menu of four shows up , then make sure you got reboot system is highlighted (it may not be called reboot system , but something similar) and press the power button
5. when the phone boots , run Step2
6. Redo step 4
7. Now after it boots run step3
8. That's It ! you got root ! now open up a cmd , cd to the adb directory , and type in adb shell , then su , and it should show # , which confirms the root
!
WARNING : you will have a bootloop now while you have the adb root , and if you have finished what you need with the root , to get unrooted and boot normally just run Undo .
does not work for me: (
i have problem, look:
***************************************
*** HTC Wildfire S Temporary root ****
******** by wiseminosse 2011 **********
running step 1...
adb server is out of date. killing...
* daemon started successfully *
rm failed for /data/local/tmp/boomsh, No such file or directory
running step 2...
rm failed for /data/local/tmp/sh, No such file or directory
running step 3...
397 KB/s (23056 bytes in 0.056s)
running step 4...
running step 5...
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00016118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
running step 6...
rm failed for -f, Read-only file system
mount: Operation not permitted
running step 7...
Unable to chmod /sbin: Read-only file system
running step 8...
Click to expand...
Click to collapse
PeMo19946 said:
does not work for me: (
i have problem, look:
Click to expand...
Click to collapse
did you enable usb debugging ??
yes.. maybe i have problems with computer..
for me it worked like a charm , give me your software specifications please (s-on/s-off , unlocked/locked bootloader ... )
s-off
bootloader locked ;/
i can't unlock bootloader but i have bad software
I must try tomorrow in Windows XP
well done ,so useful
Permanent root for S-off and unlocked bootloader WFS
PeMo19946 said:
s-off
bootloader locked ;/
i can't unlock bootloader but i have bad software
I must try tomorrow in Windows XP
Click to expand...
Click to collapse
hey , try removing the usb debugging and then re-enable it , it might help , also don't run temproot in cmd , just go to the folder and run it !
more over , you are s-off , meaning you can get permananet root ! go to shortfuse.org and download superoneclick ,extract it somewhere , and run superoneclick , all you have to do just click root ! and answer anything it asks you , then reboot the phone , you'll have perm root !!
EDIT : it is downloaded from http://depositfiles.com/files/n0dcxce3t
Make More internal storage !!
Check out my new tutorial , thanks to Jikantaru ! Make a lots of storage on your picky Wildfire S !
http://forum.xda-developers.com/showthread.php?p=22520350#post22520350
This is an expanded version of Jikantaru's tutorial and more precise !
PeMo19946 said:
s-off
bootloader locked ;/
i can't unlock bootloader but i have bad software
I must try tomorrow in Windows XP
Click to expand...
Click to collapse
maybe i got your problem , look , when first choosing HTC sync , it might open HTC sync on the PC , so open up task manager(on PC) , and go to the processes tab , end every process that carries htc on it , then try redoing the thing !
Sorry, i have S-ON, sorry. I must try all steep in XP, maybe help
I give know ..
well please post your feedback here please
Does not work on XP, still the same error with the lack of access to files.
are you following the instructions correctly
cuz it is a temproot that should work on any wildfire s , give your software info please , go to settings about and there find and tell me your software specifications
Android version 2.3.5
HTC Sense version 2.1
Software number 2.17.531.1
More:
Kernel version
2.6.35.10-g8409c43
[email protected] #1
Wed Nov 16 17:52:43 CST 2011
Baseband version
47.23b.35_3035H_7.53.39.11M
Build number
2.17.531.1 CL214145 release-keys
Tacoroot , option 2
What on earth ?! 2.17 ?! Then you only have tacoroot to work , I will be updating my main post for the use of tacoroot then , it may take time ...
Oh, this is a way to give me all this work?
PeMo19946 said:
Oh, this is a way to give me all this work?
Click to expand...
Click to collapse
Tacoroot Gives you temproot access to any HTC phone , although you might not access the phone directly from the touchscreen , but you will only see a bootloop , while this loop is looooopppiinggg , you have root access through the adb shell , which will give you what is required "ROOT ACCESS" !
PeMo19946 said:
Oh, this is a way to give me all this work?
Click to expand...
Click to collapse
Post Updated , check it for the tacoroot ...
still error, driving me crazy! want to smash the phone right now
how to remove a wrong post?