I am having so much trouble getting mytouch4gS to root. I am under the impression that the usb drivers aren't installed Though I could be wrong... I've downloaded HTC Sync (It doesn't recognize the device) Installed with anti-virus disabled, Fastboot is off, USB debug enabled. I've tried using the HTC Boot Unlocker, Revolutionary Method, and one of the Tool Kits here on XDA and none seem to be able to recognize my device... How the fok do I get this thing rooted?
HBOOT: 1.44.0007 (S-On)
This is the code that it throws
Code:
C:\Users\Admin>cd \Android
C:\Android>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.009s]
finished. total time: 0.009s
Go with Revolutionary. I had problems initially getting the token to work but I was substituting a zero for an "O" or something. I copied and pasted the token from Revolutionary and it worked like a champ.
Sent from my RubiX CubeD Extreme MT4GS using Tapatalk
Coug76 said:
Go with Revolutionary. I had problems initially getting the token to work but I was substituting a zero for an "O" or something. I copied and pasted the token from Revolutionary and it worked like a champ.
Sent from my RubiX CubeD Extreme MT4GS using Tapatalk
Click to expand...
Click to collapse
When I run Revolutionary nothing happens. The cmd prompt pops up then disappears immediately. I dont even get a chance to put in anything
run Mr Root...it'll work for sure
xmc wildchild22 said:
run Mr Root...it'll work for sure
Click to expand...
Click to collapse
I'm running 32 bit W7 Home Premium and it says The version of this file is not compatible with the version of Windows you are running....
My laptop runs Ubuntu, if anyone knows of a Linux based root?
Maybe the download link was corrupt or something, I'll try the 4shared mirror
Did you install the fastboot drivers?
They are seperate from htc sync.
You can find them on the revolutionary page.
Use rev to s-off it and then you can root your rom or install a new one after replacing your recovery.
Sent from my Bulletproof_Doubleshot using xda premium
Blue6IX said:
Did you install the fastboot drivers?
They are seperate from htc sync.
You can find them on the revolutionary page.
Use rev to s-off it and then you can root your rom or install a new one after replacing your recovery.
Sent from my Bulletproof_Doubleshot using xda premium
Click to expand...
Click to collapse
Thank you! Much Love & Respect
it should work...what happened when you clicked on it?
Keep getting invalid beta key? How do I paste into Revolutionary?
EDIT/SOLUTION: Betakey is strange... Paste into word pad and type out characters until they match exactly using a different font before entering key
xmc wildchild22 said:
it should work...what happened when you clicked on it?
Click to expand...
Click to collapse
This
{
"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"
}
hmm kk thank you
Fully Rooted. S-Off.
Attached is Fastboot.exe from Mr. Root and Signed Superuser.
This is the step by step I used for revolutionary for anyone in the future who is having issues with rooting their MyTouch 4g Slide /Doubleshot
http://theunlockr.com/2011/09/09/how-to-permanently-root-and-gain-s-off-on-the-t-mobile-mytouch-4g-slide-revolutionary-method/
II. Gain S-Off
1. Download the latest version of the tool from the developers here (the initial versions require you to generate a beta key for you to use the program, just follow the steps to do so. If it lets you download the program without a beta key, then it’s a newer version than at the time of writing this, just continue):
Revolutionary
2. Plug in your device.
3. Select charge only if the option exists on your device, or just do NOT mount the SD Card.
4. On your device, click on Settings > Applications > Development > Turn USB Debugging ON.
5. Find the Revolutionary program you downloaded and unzip it to the TempRoot folder inside the TempRoot folder you extracted in Section II.
6. Right click it and select Open as Administrator (if you do not have that option when you right click, simply select Open).
7. Input your beta key you received and wait for it to do it’s thing (if you are using a newer version of Revolutionary then it might not ask you for this. If that is the case, just continue).
III. Flash a Custom Recovery Image
1.. Once done gaining S-Off, it will ask you if you want to flash clockworkmod recovery, type in y and hit enter.
2. Once it is done flashing the recovery image it will close the command prompt window.
3. On your phone, you should see S-Off at the top.
4. Take out the battery and put it back in.
5. Turn on the device, by holding down volume down and power until the screen boots up.
6. Push volume down and then power to select recovery.
7. If the phone reboots to the clockworkmod recovery screen you are all set.
IV. Gain Permanent Root Access.
1. With the phone still in clockworkmod recovery from the last step, plug it in via USB cable.
2. Select Mounts and Storage by using the volume buttons to move and power to select.
3. Then select mount USB storage (the sd card directory should pop up on your computer screen)
4. Download the root .zip file and save it to your computer (do NOT extract it)
MyTouch Slide 4G Root .zip File
5. Copy the root .zip file to the root of your sdcard and wait for it to transfer (not in any folders, just on the sd card itself).
6. On your device, select unmount sdcard.
7. On your device, select go back.
8. Then select Install zip from sdcard and choose the root .zip file.
9. Wait for it to flash, once done, select reboot system now.
10. Once your device reboots, open the app drawer and you should see Superuser permissions there. If so, you are all set, you are rooted, have S-Off and a custom recovery image.
optimus x said:
This
Click to expand...
Click to collapse
I am getting the same error.
^ I also get the same error
Are you on 32 bit Windows?
xmc wildchild22 said:
Are you on 32 bit Windows?
Click to expand...
Click to collapse
Yes I am
Sent from my SGH-T959V using XDA
Yes, i'm also on 32 bit
Hi
The best way I found was here:
http://wiki.rootzwiki.com/HTC_myTouch_4G_Slide
It does have the Revolutionary Method, but for some reason, I found these directions easiest to follow.
Good luck.
Related
I know this the wrong forum but I need developers help my camera app keeps fc and says report to Google
Sent from my Nexus S using XDA App
can you be more specific?
custom rom, kernel or what have you
2.3 1, I902XXJK8, Kernal 2.6.35.7-g7f1638a, [email protected]#1
Sent from my Nexus S using XDA App
your running gingerbread yes, but who made the rom?
(cyanogen,modaco,etc)
or is it stock??
Its stock I'm not even rooted everything works but the camera
Sent from my Nexus S using XDA App
Thats strange dont know y ur camera would stop working running stock. Might be a software issue so u may wanna take it back an exchange it
The application camera (process com.Google.android camera) has stopped unexpectedly please try again
That's what it keeps saying
Sent from my Nexus S using XDA App
go to main settings, applications, manage applications, all, camera, clear data. then you should reboot.
I did that almost a hundred times
Sent from my Nexus S using XDA App
Bspence415 said:
I did that almost a hundred times
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
try moving all your camera pictures to your desktop. then clear your data in the camera app and the gallery app. you might have to factory reset to fix it, so consider backing up some of your data.
Bspence415 said:
I did that almost a hundred times
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
have you considered unlocking your bootloader(rooting your phone)?
That's what I'm going to try tonight is there a one click root like for the galaxy because I don't know how to root sns yet
Sent from my Nexus S using XDA App
Bspence415 said:
That's what I'm going to try tonight is there a one click root like for the galaxy because I don't know how to root sns yet
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
very easy, you dont need an app for it. very basically... install drivers to your desktop, download sdk, "fastboot oem unlock", flash clockwork recovery, flash a rom(and gapps if needed). read the threads here. shouldnt take you more than 30-60min.
How do I do the fastboot OEM unlock?
Sent from my Nexus S using XDA App
Bspence415 said:
How do I do the fastboot OEM unlock?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
taken from this thread... http://forum.xda-developers.com/showthread.php?p=10238318#post10238318
AllGamer said:
GRH78
Bootloader v.JK1
Baseband v.JK8
Yes, there are tons of guides out there, and even one click scripts that can ROOT the SNS (Samsung Nexus S) for you, but none of them go into enough detail for any of them to work properly.
Having many android devices working properly via ADB on your computer doesn't automatically guarantees it will see the SNS.
So, before jump to the exiting stuff of ROOTing the SNS, lets cover some basics to actually get you started and make sure you can actually ROOT the SNS, else all is in vain.
Part 1
Download Android SDK 2.3 or click the file name android-sdk_r08-windows.zip (32 MB) direct from Google, instead of wasting your time jumping through hoops and dodging pop up/flash ADs from those FileSharing places.
Turn Off your SNS
Make sure the SNS is connected to the PC via the USB cable
Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button
{
"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"
}
it reads LOCK STATE - LOCKED
open Device Manager (or run devmgmt.msc) make sure you don't see this problem (windows failed to identify the SNS and install the correct drivers)
Do a right click and select Update Driver Software
Select Brose my computer for driver software
point it to where you downloaded the Android SDK 2.3 (..\android-sdk-windows\google-usb_driver)
Make sure to CLICK "Let me pick from a list of device drivers on my computer"
Then from the list 3 choices select Android Bootloader Interface
If it's installed properly it should show up like this (reboot is not required)
NOTE: if you encounter problems like question marks, unknown drivers, or exclamation marks eve after you have installed the drivers, download and try the USBDeview 32/64 to remove and uninstall all the junk USB devices from your computer/registry
Now that the basic preparations are done, we can finally get to have fun with the SNS & hack away via ADB.exe / FASTBOOT.exe
Part 2
open a command prompt go to run & type CMD hit enter
switch to the directory where you downloaded & unzipped the ..\android-sdk-windows\tools
type fastboot oem unlock and hit enter
Then you will get this
Code:
fastboot oem unlock
...
meanwhile on the SNS you'll see this screen
selecting YES will wipe EVERYTHING from the SNS, so make sure you have backed up everything you needed to safe before you continue.
use the Volume up/down keys to select and Power key to apply
you should see something like this after it's done
Code:
... OKAY [435.433s]
finished. total time: 435.433s
now back on this screen you should read
LOCK STATE - UNLOCKED
Download the clockwork recovery recovery-clockwork-3.0.0.0-crespo.img image, and save it to the ..\android-sdk-windows\tools directory
renamed it to recovery.img
then type fastboot flash recovery recovery.img and hit enter
you should get something like this, if not your image is corrupted, download it again
Code:
sending 'recovery' (3980 KB)... OKAY [ 0.621s]
writing 'recovery'... OKAY [ 0.511s]
finished. total time: 1.132s
Then back on the SNS select Power Off (Reboot also works)
Power ON the SNS
...meanwhile the SNS is rebooting Download superuser from http://forum.xda-developers.com/showthread.php?t=682828
choose the Eclair/Froyo version
Mount the USB storage
drag/drop the su-version#-signed.zip file into the root of the internal SD of the SNS
Power Off the SNS
Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button
select Recovery
then it should boot into this screen, if not then repeat the steps to download the image
select install ZIP from sdcard (power button to apply)
select choose zip from sdcard (power button to apply)
select su-version#-signed.zip file you downloaded earlier, and apply it
select yes - install su-version#-signed.zip
confirm it says "Install from sdcard complete"
select go back
select reboot
done!
Enjoy your unlocked & rooted phone!
Click to expand...
Click to collapse
Seriously, you have a buggy phone before even rooting, I'm not sure rooting will fix it for you. What if your hardware for the camera is bad and that's what's causing the problem? Once rooted, you'll have to worry about un-rooting and relocking the bootloader to avoid any warranty hassles. I'd take it back and exchange it before rooting.
Make sure you have a solid working phone before rooting!
On another note, even though it's in red in the posted tutorial, let me reemphasize that the oem unlock step WILL WIPE EVERYTHING ON YOUR PHONE, INCLUDING THE SDCARD (internal one)...so if you have any pics or stuff on there you can't afford to lose, transfer them to the computer via USB before starting the root process.
I was unlocking the bootloader so i could root the phone. I was successful but now my phone is stuck on the google screen with the unlocked pad at the bottom.
Through the forum i found that i'm missing the boot image so i found that.
I pulled in my phone to the computer and typed "fastboot flash boot test_boot.img". it comes up with "error: cannot load test_boot"
The same thing happened when i tried to "fastboot flash recovery recovery.img" aswell to try and fix it that way but the same error came up.
I made sure the file names were correct.
Please help!!
bozo089 said:
I was unlocking the bootloader so i could root the phone. I was successful but now my phone is stuck on the google screen with the unlocked pad at the bottom.
Through the forum i found that i'm missing the boot image so i found that.
I pulled in my phone to the computer and typed "fastboot flash boot test_boot.img". it comes up with "error: cannot load test_boot"
The same thing happened when i tried to "fastboot flash recovery recovery.img" aswell to try and fix it that way but the same error came up.
I made sure the file names were correct.
Please help!!
Click to expand...
Click to collapse
fastboot clockwork recovery then flash a rom.
I would flash clockwork but when i put the file into my SDK tools folder and then use CMD to try and flash it but i got an error. Details are in my first post.
Please help!
bozo089 said:
I would flash clockwork but when i put the file into my SDK tools folder and then use CMD to try and flash it but i got an error. Details are in my first post.
Please help!
Click to expand...
Click to collapse
do you have the recovery.img file in the same folder as fastboot?
simms22 said:
do you have the recovery.img file in the same folder as fastboot?
Click to expand...
Click to collapse
Yeah its in there.
Also, when i typed adb devices it only says "see devices attached" not the serial number.
bozo089 said:
Yeah its in there.
Also, when i typed adb devices it only says "see devices attached" not the serial number.
Click to expand...
Click to collapse
do you have the proper drivers installed? if not, go directly to PdaNets website http://junefabrics.com/android/ and have it install the proper drivers onto your computer. this way is by far the easiest way to install the drivers. download and install the free program then just follow the directions on the screen.
simms22 said:
do you have the proper drivers installed? if not, go directly to PdaNets website http://junefabrics.com/android/ and have it install the proper drivers onto your computer. this way is by far the easiest way to install the drivers. download and install the free program then just follow the directions on the screen.
Click to expand...
Click to collapse
I do have that installed. I used it to unlock the bootloader. Im trying to reinstall it using the link you provided but the phone doesn't turn on so i dont think it will work. Now in the fastboot screen on my phone it says fastboot status -FAILinvalid command
bozo089 said:
I do have that installed. I used it to unlock the bootloader. Im trying to reinstall it using the link you provided but the phone doesn't turn on so i dont think it will work. Now in the fastboot screen on my phone it says fastboot status -FAILinvalid command
Click to expand...
Click to collapse
Update: the FAILinvalid part went away but i think i might have uninstalled the pdaNet when trying to reinstall it.
bozo089 said:
Update: the FAILinvalid part went away but i think i might have uninstalled the pdaNet when trying to reinstall it.
Click to expand...
Click to collapse
OK, i did a system restore and now i have pdaNet back. I have no idea how to use it or what to do next.
Please help!
EDIT: when i typed "fastboot devices" into CMD, it shows my device!
take a screenshot of your /sdk/tools folder.
(seriously do it).
OR if you don't want to.. does fastboot appear as "fastboot" or "fastboot.exe" ?
Uploaded with ImageShack.us
There you go
bozo089 said:
Uploaded with ImageShack.us
There you go
Click to expand...
Click to collapse
Okay, yeah. I see the problem, your extensions are hidden "recovery.img" is actually "recovery.img.img" so you're fastbooting a invalid file. What I want you to do is on the top left of a Windows explorer, it says Organize. Press that and go to folder options -> view -> hide extensions for known file types (UNCHECK THIS). Rename recovery.img.img so it appears as recovery.img not recovery.img.img
Put your phone in bootloader mode if it isn't already with USB plugged in.
The phone needs to be in bootloader mode in order for it to recognize the fastboot command.
{
"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"
}
^ appears as that.
through command prompt
cd C:\android-sdk-windows\tools\
(optional -- do this if your phone isnt in bootloader mode) adb reboot bootloader
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
and you're set. click on "thanks" if this helped you!
wow, ok so it says writing and sending went "OKAY". I assume that means it worked.
I really don't know what to do now. How do i access the clockwork menu and how do i install a ROM?
bozo089 said:
wow, ok so it says writing and sending went "OKAY". I assume that means it worked.
I really don't know what to do now. How do i access the clockwork menu and how do i install a ROM?
Click to expand...
Click to collapse
yeah that meant it worked. you can access clockwork menu by going down to RECOVERY in the menu or "adb reboot recovery"
you install a ROM by...
1. Shop around the Dev forums and look for what ROM you want to use. I personally use CM7.
2. Use netarchy's kernel (its worth it).
Steps:
1. Put ROM onto your sdcard
2. Boot into Clockwork Recovery (told you above on how to do it)
3. Wipe Factory, Dalvik, Cache
4. Flash ROM (Proceed to flash CM7 Gapps afterwards if you decide to go with CM7)
5. Flash Kernel (Optional)
6. Reboot!
Ahhh, i updated without looking at your post first. Can i put the kernal on now that ive rebooted?
thank you for your help and time
Hi everyone,
So this is my issue. Yesterday i tried to root my working nexus s i9020t with a one click root on my mac computer. Terminal said 'root ok' everything was ok then the phone didnt get past the google startup.
So i tried recovery... that didnt do anything.
Then i started with SDK on my windows 7 machine and with fastboot.
Basically i erased everything on the phone (boot and recovery)
Fastboot is unlocked. At the top it says no boot or recovery img.
When i do 'fastboot flash recovery recovery.img' with my recovery.img in the same folder on windows it says 'cannot load or mount recovery.img'
Fastboot is seeing the phone since it is listed when I write 'fastboot devices'.
Basically i think i ruined the recovery file, dont care about rooting right now, just want to load a recovery image or boot image.
If i go down to recovery on the phone in fastboot it will start fastboot again and say ' no boot or recovery img'
Any help?
THANK YOU!
AllGamer said:
GRH78
Bootloader v.JK1
Baseband v.JK8
Yes, there are tons of guides out there, and even one click scripts that can ROOT the SNS (Samsung Nexus S) for you, but none of them go into enough detail for any of them to work properly.
Having many android devices working properly via ADB on your computer doesn't automatically guarantees it will see the SNS.
So, before jump to the exiting stuff of ROOTing the SNS, lets cover some basics to actually get you started and make sure you can actually ROOT the SNS, else all is in vain.
MOD EDIT: This guide does not apply to the AT&T/Rogers/Telus variants of the Nexus S (i9020A). For those models, please refer to this guide.
Part 1
Download Android SDK 2.3 or click the file name android-sdk_r08-windows.zip (32 MB) direct from Google, instead of wasting your time jumping through hoops and dodging pop up/flash ADs from those FileSharing places.
Turn Off your SNS
Make sure the SNS is connected to the PC via the USB cable
Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button
{
"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"
}
it reads LOCK STATE - LOCKED
open Device Manager (or run devmgmt.msc) make sure you don't see this problem (windows failed to identify the SNS and install the correct drivers)
Do a right click and select Update Driver Software
Select Brose my computer for driver software
point it to where you downloaded the Android SDK 2.3 (..\android-sdk-windows\google-usb_driver)
Make sure to CLICK "Let me pick from a list of device drivers on my computer"
Then from the list 3 choices select Android Bootloader Interface
If it's installed properly it should show up like this (reboot is not required)
NOTE: if you encounter problems like question marks, unknown drivers, or exclamation marks eve after you have installed the drivers, download and try the USBDeview 32/64 to remove and uninstall all the junk USB devices from your computer/registry
Now that the basic preparations are done, we can finally get to have fun with the SNS & hack away via ADB.exe / FASTBOOT.exe
Part 2
open a command prompt go to run & type CMD hit enter
switch to the directory where you downloaded & unzipped the ..\android-sdk-windows\tools
type fastboot oem unlock and hit enter
Then you will get this
Code:
fastboot oem unlock
...
meanwhile on the SNS you'll see this screen
selecting YES will wipe EVERYTHING from the SNS, so make sure you have backed up everything you needed to safe before you continue.
use the Volume up/down keys to select and Power key to apply
you should see something like this after it's done
Code:
... OKAY [435.433s]
finished. total time: 435.433s
now back on this screen you should read
LOCK STATE - UNLOCKED
Download the clockwork recovery recovery-clockwork-5.0.2.0-crespo.img image, and save it to the ..\android-sdk-windows\tools directory
renamed it to recovery.img
then type fastboot flash recovery recovery.img and hit enter
you should get something like this, if not your image is corrupted, download it again
Code:
sending 'recovery' (3980 KB)... OKAY [ 0.621s]
writing 'recovery'... OKAY [ 0.511s]
finished. total time: 1.132s
Then back on the SNS select Power Off (Reboot also works)
Power ON the SNS
...meanwhile the SNS is rebooting Download superuser from http://forum.xda-developers.com/showthread.php?t=682828
choose the Eclair/Froyo version
Mount the USB storage
drag/drop the su-version#-signed.zip file into the root of the internal SD of the SNS
Power Off the SNS
Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button
select Recovery
then it should boot into this screen, if not then repeat the steps to download the image
select install ZIP from sdcard (power button to apply)
select choose zip from sdcard (power button to apply)
select su-version#-signed.zip file you downloaded earlier, and apply it
select yes - install su-version#-signed.zip
confirm it says "Install from sdcard complete"
select go back
select reboot
done!
Enjoy your unlocked & rooted phone!
Click to expand...
Click to collapse
Sent from my Nexus S using XDA Premium App
Sent from my Nexus S using XDA Premium App
Follow the recovery part,
Sent from my Nexus S using XDA Premium App
osugsxr,
Thanks for the reply, but that is the tutorial i tried and i get stuck at the part:
'Fastboot flash recovery recovery.img'
it says that the recovery.img cannot be loaded....
ever see something like that?
To me it sounds like fastboot can't find your recovery image.
Could you try doing fastboot with the absolute path?
On windows (path for example):
fastboot flash recovery C:\android\recovery.img
Make sure you get the backspaces right.
On linux (for example)
fastboot flash recovery /home/user/android/recovery.img
Good luck.
Greetz
michaeljameson1985 said:
osugsxr,
Thanks for the reply, but that is the tutorial i tried and i get stuck at the part:
'Fastboot flash recovery recovery.img'
it says that the recovery.img cannot be loaded....
ever see something like that?
Click to expand...
Click to collapse
Is it in the correct folder?
Sent from my Nexus S using XDA Premium App
osugsxr said:
Is it in the correct folder?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Progress report - So i now have clockworkmod recover v5.0.2.0 on my android nexus s 9020t and have tried everything from Stock rom to a different rom to update.zip the file.... nothing has worked.
I tried to install the update.zip from the recovery and get the error that there is an error in /sdcard/update.zip
is it possible clockworkmod recovery v5 wont work with my nexus s?
thanks!
Mike
You know that you have to copy the ROM zip file to the SDCard and then choose 'Install zip from sdcard' option in CWM, selecting the download ROM zip file, right?
Greetz
ClockworkMod Touch recovery 5.8.0.2 is now available for the HTC Desire
ALL CREDITS TO @Koush
{
"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"
}
Installing The Recovery
There are primarily three methods of installing a custom recovery to your phone. Please note that the first method is specific to ClockworkMod recovery only while the other two methods can be used for any custom recovery supported by your phone.
Using ROM Manager
Using Fastboot
Using flash_image
I still prefer the Fastboot method so these instructions are for Windows users, but the equivalent steps should work for mac and linux:
Open up a cmd window and go to your SDK tools folder. Now type
Code:
Code:
fastboot
and press enter. You should see a list of fastboot commands available. If you don't get that, you're probably not in the right folder. Check your path and where you installed the SDK and make sure you are in the /tools folder.
Once you've verified you can run fastboot, it's time to move the recovery image to the /tools folder (easier not to have to specify a path to the recovery file). I would also rename the recovery file to something short like recovery.img.
Once the recovery image is in the same /tools folder as fastboot, you'll need to put your phone in fastboot USB mode. To do this:
1) make sure the Fast Boot option is disabled. Note, this "Fast Boot" has nothing to do with the fastboot executable I've been talking about. This is a setting in Sense to allow the phone to boot up faster. To disable this setting, go to Settings > Power > Fast boot (uncheck the box).
2) Hold down the power button and select Power Off from the menu. Wait 1 minute for the phone to completely power off.
3) Boot into HBOOT. See this post for detailed instructions on how to boot into HBOOT:
How to boot into bootloader (HBOOT)
4) Once you're in HBOOT, you'll see it scan for a few files. This is normal. When it is done, you can make selections in the menu. Vol-UP and Vol-DOWN allows you to move up and down the menu list. POWER button acts as ENTER and selects whatever you're highlighted over.
By default, FASTBOOT is selected. So just press power.
5) now you should be in the FASTBOOT section of HBOOT. Plug the phone in via the USB cable to the computer where you installed the Android SDK. You should see the red FASTBOOT banner turn into FASTBOOT USB. If that doesn't happen, it means that your HBOOT drivers aren't working.
Your phone is now ready to accept commands from the fastboot executable that came with the Android SDK. Go back to that cmd window where we tested the fastboot command earlier. From there, issue the following command:
Code:
Code:
fastboot flash recovery recovery.img
Here's a quick explanation of the above command:
fastboot: that's the executable tool
flash: that's the function we want the fastboot tool to perform
recovery: this is the name of the partition we want to flash into. since we are flashing a recovery image, it needs to go to the recovery partition.
recovery.img: this is the name of the actual file to flash. Your filename may be different. Just make sure it matches the actual filename.
Fastboot will flash the image and give you a success/failure notification. If successful, you're all set. To check out the new recovery image, verify that BOOTLOADER is selected in the HBOOT menu (should be highlighted in blue). Press POWER button to select it. Now you should be back at the main HBOOT menu.
Use VOL-DOWN to highlight RECOVERY and press POWER button. The phone will now attempt to boot into the new recovery image.
You'll see the htc splash screen briefly and then the recovery image. That's it!
Nice....
Woow that is fast ....
I'm now running EXT4 touch. Lets give this a go.......
Nice work. Thanks.
Very Nice, ty
Thank you. Will try it tonight.
screenshots of recovery? what does this have over 4ext?
Anyone try it? the Ext4's lauching time is too long, whatever the touch version or classic version. I dont know why.
But the RMD 1. 034 is faster than that. I will try it this weekend.
Anyway, well done Yorzua!
Rastaman-FB said:
screenshots of recovery? what does this have over 4ext?
Click to expand...
Click to collapse
Reported by @koush himself as :
Currently, supported devices include (stay tuned, as I am updating this list as I build):
Samsung Nexus S
Samsung Nexus S 4G
Samsung Galaxy Nexus (CDMA and GSM)
HTC Desire
HTC Desire HD
HTC Evo
HTC Evo 3D (GSM and CDMA)
HTC Thunderbolt
Motorola Atrix 4G
But my thread here is for the HTC Desire only as i dont own the other devices.
The touch code is still beta, so please flash it, test it, report bugs and be patient
@yorsua, Where can I see the source code?
Did you just modify the recovery directory in the cm tree?
Rastaman-FB said:
screenshots of recovery? what does this have over 4ext?
Click to expand...
Click to collapse
Koush got this working just a couple of days ago. 4ext has the advantage of time and a fabulous dedicated developer
Was waiting for koush to get it working, so I can peep into the source.
If i install this recovery, can i still use my nandroid backups from an older version (4)
Cause I don't want to lose them.
"Backup may not be supported on this device. Skipping backup of sd-ext"
That's what I call useless. Interface itself is too plain. It has touch support, but that's it. It's not been tweaked to make use of its touch interface.
have an error while entering finale command, any ideas?
super_turbo said:
have an error while entering finale command, any ideas?
Click to expand...
Click to collapse
Are you s-off ?
nope its s-on
Sorry guys, i have been extremely busy at work and releasing my whatsapp mods
Droidzone said:
"Backup may not be supported on this device. Skipping backup of sd-ext"
That's what I call useless. Interface itself is too plain. It has touch support, but that's it. It's not been tweaked to make use of its touch interface.
Click to expand...
Click to collapse
As i wrote, the touch code on CWM is still a Beta.
So please flash it, test it, report bugs if you want.
Be patient
super_turbo said:
have an error while entering finale command, any ideas?
Click to expand...
Click to collapse
Must be S-OFF indeed !
Need s-off with patched hboot for fastboot commands.
I want to report a bug, not sure of the cause though
It's in my post
http://forum.xda-developers.com/showthread.php?t=1476978
ikidntu said:
I want to report a bug, not sure of the cause though
It's in my post
http://forum.xda-developers.com/showthread.php?t=1476978
Click to expand...
Click to collapse
Thanks for your testing and feedback.
Bug reported.
sjn01 said:
Anyone try it? the Ext4's lauching time is too long, whatever the touch version or classic version. I dont know why.
But the RMD 1. 034 is faster than that. I will try it this weekend.
Anyway, well done Yorzua!
Click to expand...
Click to collapse
Delete 4EXT Folder on SD and try it!
@OP, Did you notice that the official recovery build has been updated to 5.8.0.2? I wish you'd pull the faulty version you've attached here.
Someone was having trouble doing an RUU through his Virtualbox'd Windows.. So I figured.. why not. For the virtualbox tutorial, view JeepFreak's thread
NEW - Install wine on MAC http://wiki.winehq.org/MacOSX - you can compile yourself or download and install it
1.) Download fastboot and extract to your desktop, and place the RUU your desktop.
2.) install wine if you haven't already
{
"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"
}
3.) if you get stuck at this window, just press tab and hit enter
4.) run the RUU in wine
5.) the RUU should popup with a progress bar
6.) navigate to the wine C:\ drive (i am using gnome classic, so the process may differ here)
7.) Now search for "rom" or "rom.zip" in the folder
8.) QUICKLY drag it to your desktop BEFORE the RUU closes
9.) Now you should have this on your desktop
10.) Now you want to change into your fastboot directory and lock your bootloader
11.) If you are stuck on <waiting for device> hit Ctrl-C, and type sudo -s
12.) your phone should reboot and be stuck in your bootloader with a similar screen
13.) Now you want to get ready to RUU
14.) Your phone should now look like this
15.) Next we want to flash the zip (make sure to put it in the fastboot folder)
16.) the prompt should just do some crap..
17.) you will most likely get an error due to SuperCID, just reflash the zip.
18.) Now you may or may not get an error about hboot, if you do, reflash the zip again
19.) Finally, your phone should be like this
20.) During this time, it'll be writing the RUU
21.) After your phone turns off, hold volume down until you get into hboot, then boot into fastboot
22.) fastboot erase cache
23.) Now we need to re-unlock the bootloader, get your Unlock_code.bin and put it in the fastboot folder (you can get this from HTCDev again if you lost your old one)
23.) Unlock your bootloader
24.) flash your recovery!
and now you are done... FINALLY
Thanks to 18th.abn for showing me how to RUU a zip
Good job....:good: just one thing, think you should add fastboot for mac to OP as well, do you have it ? and while you're at it link to wine as well.
Crappyvate said:
Good job....:good: just one thing, think you should add fastboot for mac to OP as well, do you have it ? and while you're at it link to wine as well.
Click to expand...
Click to collapse
Right. I forgot you can't apt-get in mac can you?
Sent from my HTC One XL using xda app-developers app
absolutelygrim said:
Right. I forgot you can't apt-get in mac can you?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
no you can't natively but you can using macports:
port search <name of package>
port install <name of package> (this is what you would use to install wine for example)
port selfupdate
port help
Nice job!
I can flash the rom.zip successfully (according to the command line), but after that the phone never reboot or power down. Is it safe to turn it off anyway?
SB
Skickat från min ASUS Transformer Pad TF700T via Tapatalk 2
when i run wine in ubuntu 12.04 i get this issue here sorry for bringing up a old thread
[email protected]:/home/tigartist/Downloads/ruuextract# wine /home/tigartist/Downloads/dlxstock.exe
fixme:storage:create_storagefile Storage share mode not implemented.
fixme:apphelp:ApphelpCheckInstallShieldPackage stub: 0x33f1fc L"C:\\users\\root\\Temp\\{695E0798-C5C2-4E8C-9EAE-45159E1C9D88}\\Disk1\\data1.hdr"
fixme:ieframe:taskbar_list_SetProgressState iface 0x14b95c8, hwnd 0x30022, flags 2 stub!
fixme:ieframe:taskbar_list_SetProgressValue iface 0x14b95c8, hwnd 0x30022, ullCompleted 1, ullTotal 64 stub!
err:module:import_dll Library MFC42u.DLL (which is needed by L"C:\\users\\root\\Temp\\{3AA3566E-6871-4B43-8AA5-00E91AD85221}\\{50F2F878-636A-496F-A7CB-544C067E0C4B}\\ARUGlobal.dll") not found
err:module:import_dll Library ARUGlobal.dll (which is needed by L"C:\\users\\root\\Temp\\{3AA3566E-6871-4B43-8AA5-00E91AD85221}\\{50F2F878-636A-496F-A7CB-544C067E0C4B}\\ARUWizard.exe") not found
err:module:import_dll Library MFC42u.DLL (which is needed by L"C:\\users\\root\\Temp\\{3AA3566E-6871-4B43-8AA5-00E91AD85221}\\{50F2F878-636A-496F-A7CB-544C067E0C4B}\\ARUWizard.exe") not found
err:module:LdrInitializeThunk Main exe initialization for L"C:\\users\\root\\Temp\\{3AA3566E-6871-4B43-8AA5-00E91AD85221}\\{50F2F878-636A-496F-A7CB-544C067E0C4B}\\ARUWizard.exe" failed, status c0000135
[email protected]:/home/tigartist/Downloads/ruuextract#
The way I dealt with it was to cd in ~/.wine, then run the wine line in one tab, and this in another
Code:
while true; do find . -name rom.zip ; cp `find . -name rom.zip` /tmp/; sleep .5; done
(the first find is so I can see that the file was really created, the second is used for the source file for the cp)
Then at the end, rom.zip was in /tmp/ waiting for me.
t1gartist said:
when i run wine in ubuntu 12.04 i get this issue here sorry for bringing up a old thread
[email protected]:/home/tigartist/Downloads/ruuextract# wine /home/tigartist/Downloads/dlxstock.exe
fixme:storage:create_storagefile Storage share mode not implemented.
fixme:apphelp:ApphelpCheckInstallShieldPackage stub: 0x33f1fc L"C:\\users\\root\\Temp\\{695E0798-C5C2-4E8C-9EAE-45159E1C9D88}\\Disk1\\data1.hdr"
fixme:ieframe:taskbar_list_SetProgressState iface 0x14b95c8, hwnd 0x30022, flags 2 stub!
fixme:ieframe:taskbar_list_SetProgressValue iface 0x14b95c8, hwnd 0x30022, ullCompleted 1, ullTotal 64 stub!
err:module:import_dll Library MFC42u.DLL (which is needed by L"C:\\users\\root\\Temp\\{3AA3566E-6871-4B43-8AA5-00E91AD85221}\\{50F2F878-636A-496F-A7CB-544C067E0C4B}\\ARUGlobal.dll") not found
err:module:import_dll Library ARUGlobal.dll (which is needed by L"C:\\users\\root\\Temp\\{3AA3566E-6871-4B43-8AA5-00E91AD85221}\\{50F2F878-636A-496F-A7CB-544C067E0C4B}\\ARUWizard.exe") not found
err:module:import_dll Library MFC42u.DLL (which is needed by L"C:\\users\\root\\Temp\\{3AA3566E-6871-4B43-8AA5-00E91AD85221}\\{50F2F878-636A-496F-A7CB-544C067E0C4B}\\ARUWizard.exe") not found
err:module:LdrInitializeThunk Main exe initialization for L"C:\\users\\root\\Temp\\{3AA3566E-6871-4B43-8AA5-00E91AD85221}\\{50F2F878-636A-496F-A7CB-544C067E0C4B}\\ARUWizard.exe" failed, status c0000135
[email protected]:/home/tigartist/Downloads/ruuextract#
Click to expand...
Click to collapse
We can just use these steps to do the same on a windows right?
Sent from my One X using xda app-developers app
w0tha said:
We can just use these steps to do the same on a windows right?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I mean, you could... but there's far easier ways for windows since the RUU is actually built to run on it.
1. Re-lock bootloader
2. Flash stock recovery
3. Run RUU
4. Re-unlock using either HTC dev or another method of choice. Or if you have s-off you don't need to re-unlock.
I need to run one RUU_xxx.exe in order to lower HBOOT on my Desire S.
Would it change HBOOT if I flash rom.zip? It seems that this step (running RUU) is the only one that really requires Windows, in my way to S-OFF (even Revotionary has Linux version).
In Linux terminal run sudo apt-get install wine then run ruu with wine
Help?
When I run it, I get rom_01.zip and rom_02.zip. I try to grab them, but they disappear within the next split second. After that, I try to quit the wine process before it can delete the files. I successfully retrieve them and put them on the desktop. I can't open them and my zip unarchiver says the files are incomplete or damaged. Is this normal?
Using a VM and actually running the ruu is much easier in my opinion a d you get the full ruu.
The only thing is you have to watch for when the phone disconnects and then remount it in the VM while its ruuing. It disconnects a few times.
Sent from my One X using xda app-developers app
P645 said:
When I run it, I get rom_01.zip and rom_02.zip. I try to grab them, but they disappear within the next split second. After that, I try to quit the wine process before it can delete the files. I successfully retrieve them and put them on the desktop. I can't open them and my zip unarchiver says the files are incomplete or damaged. Is this normal?
Click to expand...
Click to collapse
Even if you can extract the rom.zip (it's actually 2 of them now rom01.zip and rom02.zip) they're encrypted, you would need to do this first http://forum.xda-developers.com/show....php?t=2084470
Tried it.
Entered this:
ruuveal --device evita rom_01.zip rom_d.zip
Got this:
ruuveal
-------
invalid htc aes encrypted zip file!
Edit: Used rom_02.zip instead of rom_01.zip. Works now. nvm.
Thanks for this! Any chance you could fix the images? They appear to be broken.