Related
Please refer to this post before upgrading Your DHD
http://forum.xda-developers.com/showthread.php?t=879525
If You update to latest version You will NOT be able to boot custom HBOOT!!!
Here is guide how to downgrade Your DHD if You updated to latest version by mistake
http://forum.xda-developers.com/showthread.php?t=905003
This is complete guide for all HTC Desire HD owners who want's to root their devices and install custom recovery image.
FLASH THIS AT YOUR OWN RISK, I AM NOT RESPONSIBLE IF ANYTHING GOES WRONG
I have collected and summarize few guides on this forum in order to collect all informations on one place.
Check following threads for additional informations.
Please post all bug's and issues related to DHD scripts to sfjuocekr thread below.
http://forum.xda-developers.com/showthread.php?t=835746
http://forum.xda-developers.com/showthread.php?p=9183483
Summary:
1) Download Paul's Visionary+ tool (I have used version r12) (google removed this app from market) so You will have to download it from Paul's website.
This tools enables root and removes new HTC protection.
2) Install engineering version of HBOOT to get S-Off (HTC bootloader, something like BIOS for Your PC)
This step is optional and it's not required in order to flash custom ROM's on Your DHD but gives You more freedom with Your device.
3) Install custom recovery image (recovery is special program which is invoked from HBOOT
in order to flash ROM onto Your device.
Detailed description:
1) Download Paul's Visionary+ tool
1.1) Click here to download http://android.modaco.com/content/h...722/10-nov-r12-test-visionary-one-click-root/ or download it from here http://forum.xda-developers.com/attachment.php?attachmentid=447543&d=1290501865
1.2) Install Visionary+ on Your DHD
1.3) Run it, enable "Set system r/w after root
1.4) Click "Temproot Now!" - Wait until it's finished
1.5) Click Attempt Permroot Now!
1.6) DHD automatically reboot's
To test that everything went fine download from market application "terminal emulator"
run it, type su
If You get after that sign # it mean's that everything went fine.
Time for next step!
2) Install engineering version of HBOOT to get S-Off
2.1) Download sfjuocekr DHD script for flashing HBOOT from here
http://forum.xda-developers.com/showthread.php?t=835746
2.2) Unzip it and copy it to Your SDCard (It's important that You have on Your SDCard root directory with name DHD and all files inside this directory. Rename DHD-smart folder on Your SDCARD to DHD.
2.3) Run Terminal Emulator
2.4) Type su
2.5) Type "sh /sdcard/DHD/check
(Please be aware that You have to type "sh" in front of command)
2.6) If everything went OK type
sh /sdcard/DHD/backup
2.7) If this also went OK proceed with
sh /sdcard/DHD/hboot
This command will install engineering hboot which have S-Off turned off.
3) Install custom recovery image
3.1) Since ROM manager now officially support's Desire HD, we will use it to download and install custom clockwork image.
3.2) Run android market app on Your DHD and download and install ROM Manager app from market.
3.3) Download and install ROM manager.
3.4) Run ROM manager and select first option (Flash ClockWorkMod Recovery).
3.5) Wait until ROM Manager say's that installation went successfully (Current version of ClockWorkMod is 2.5.1.3)
3.6) After installation tap in Rom manager option Reboot into Recovery to test that everything went well.
3.7) DHD should reboot in clockwork recovery manager.
Enjoy.
This afternoon I've done what you describe in your guide and can say that everything works fine on my DHD !
Another Desire HD free from chains
Alright this probably sounds disgustingly noob but my phone isn't going into bootloader mode x_x. I've rooted the phone and followed the S-OFF procedure and no luck... Any ideas?
EDIT: Don't worry issue resolved. I had to end up using adb shell reboot bootloader. It's still a bit weird though, as to why I can't do this without adb...
Did You manage to install clockwork successfully?
zexbig said:
This is complete guide for all HTC Desire HD owners who want's to root their devices and install custom recovery image.
(I hade run into the strange problem for which I'm not sure is it problem with my PC or DHD, each time when I connected my DHD via USB cable my SDCard was automatically mounted as Disk Drive instead of just being in "Charge only" mode. I resolved this by removing back cover and ejecting SDCard and inserting it again while phone was operational, which is very unsafe thing to do!).
Enjoy.
Click to expand...
Click to collapse
known issue : can't remember the app, double-twist I think, it auto mounts SD card. Do you have that? Deselect or uninstall.
Yup looks like it. It's saying ClockworkMod Recovery v2.5.1.2. The only issue is, I can't select any of the options lol
EDIT: don't worry also solved that
Just another question though, using NANDROID am I able to backup my current ROM? I'm with Vodafone australia and I want to be able to restore this ROM (for warranty purposes).
crypticc said:
known issue : can't remember the app, double-twist I think, it auto mounts SD card. Do you have that? Deselect or uninstall.
Click to expand...
Click to collapse
Hmm probably something which come with original HTC ROM, I didn't install anything similar to that. But will double check..
Sylpher said:
Yup looks like it. It's saying ClockworkMod Recovery v2.5.1.2. The only issue is, I can't select any of the options lol
EDIT: don't worry also solved that
Just another question though, using NANDROID am I able to backup my current ROM? I'm with Vodafone australia and I want to be able to restore this ROM (for warranty purposes).
Click to expand...
Click to collapse
Backing up current ROM and restoring is primary function of nanodroid
zexbig said:
Backing up current ROM and restoring is primary function of nanodroid
Click to expand...
Click to collapse
Haha just making sure . I didn't want to lose my current ROM because Vodafone doesn't honour warranties on phones that have been modified in this manner.
Also I forgot altogether to say thanks lol! Thanks for the simple and straightforward guide
Hi, Does anyone have 10/Nov r12 test: VISIONary + one click root and can send it to me? I can't seem to be able to download it anywhere! Pages are down
clockwork installed can't select
HUGE thanks for writing these instructions. They worked perfectly.
rolphez said:
Hi, Does anyone have 10/Nov r12 test: VISIONary + one click root and can send it to me? I can't seem to be able to download it anywhere! Pages are down
Click to expand...
Click to collapse
Here you have the VISIONary r13, I've rootet successfully with this version.
just followed the guide and im backing up my phone now. Thanks very much.
help
3.5) Download test clockwork image from
and put it in C:\android-sdk-windows\tools\ directory.
3.6) Reboot Your phone into bootloader (Turn off phone, and press VOLUME DOWN and HOLD IT, and it the same time PRESS POWER and hold it until You get bootloader screen.
Then scroll with Volume down button on to fastboot and press power, connect USB cable and wait until android fastboot interface is installed.
3.7) Run cmd and cd to C:\android-sdk-windows\tools\
3.8) type
fastboot flash recovery clockwork.img
3.9) If everything went OK You will get following message:
C:\android-sdk-windows\tools>fastboot.exe flash recovery clockwork.img
sending 'recovery' (4914 KB)... OKAY
writing 'recovery'... OKAY
3.10)This means that You are almost finished. Type
C:\android-sdk-windows\tools\fastboot.exe reboot-bootloader
to reboot Your phone in bootloader mode.
When You are back in bootloader mode select recovery and phone will reboot in Clockwork recovery mode, since DHD does not have optical trackball just scroll 3 times trough menu (just press volume down button until You get message "back menu button enabled".
Enjoy.[/QUOTE]
hi
thanks for the guide.
done all the steps upto 2 everything good
cant get the step 3 , can you explain more deeply.
downloaded all the files , kept on my pc . do i need to move andriod -sk folder to sd and then rebot my phone . as you said to boot in bootloader but wen i press and hold power and volume down nothing happens
need help plz
another question how can i keep my original rom backed up , with which app?
I also cant get into the bootloader by pressing volume down when powering on. Also tried through shell (I think?, is the commands 'su' and then 'reboot bootloader'?) and got a 'not permitted'.
solved
I had to end up using adb shell reboot bootloader
its backing up my phone now
than everybody
where the backup will be saved , name of the files , so i can save them . and i f anything go wrong how to restore the original files?
help
after doing step one can i remove Visionary+ from phone?
any pros of keeping it?
You can remove visionary, only cons is that visionary have unroot option if You want to revert back this maybe usefull.
Sent from my Desire HD using Tapatalk
OP
please help me out here:
i always get this from cmd:fastboot not recognized as an internal or external command and nothing happens! any ideas please.
thank you
This is a port of the ClockworkMod Recovery V3.0.0.5 for Folio100.
Almost everything is functional except some minors issues.
Known issues :
boot part is not backup when using Backup / Restore.
Update 1 : Cache is mounted at start
Installation instructions :
Download : update.zip
- Copy the update.zip to a sdcard
- Follow the same procedure as explain in this post for the FolioMod
- Don't need to wipe.
- After reboot, enter recovery again to see the change
Click to expand...
Click to collapse
Usage :
- ( VOL + ) and ( VOL - ) key to highlight the menu
- ( HOME ) key to select
Click to expand...
Click to collapse
THANKS to:
Koush : the original creator of ClockworkMod
Dexter_nlb : for the great work he makes with the FolioMod
All the peoples who help me on cyanogenmod irc channel
wolfx said:
This is a port of the ClockworkMod Recovery V3.0.0.5 for Folio100.
Almost everything is functional except some minors issues.
Known issues :
partitions do not mount automatically at startup
boot part is not backup when using Backup / Restore.
Installation instructions :
Usage :
THANKS to:
Koush : the original creator of ClockworkMod
Dexter_nlb : for the great work he makes with the FolioMod
All the peoples who help me on cyanogenmod irc channel
Click to expand...
Click to collapse
this will be so great, good joob and keep em comming. Next stop Gingerbread
Installed it just aminute ago worked great. I played around a bit, i formated system, data, cache and dalvik cache. I also tryed format boot but that was a no go. In the first clockwork 3 releases there was also this problem with boot. i cant remember if it was the same error, but its fixed now so that it works correct. I also flashed FolioMod from clockwork iwth out any problems. Really nice work
Great Job!! Now we just need some AOSP/CM7 love
Can I use it with stock rom too? Tnx
Great work thanks alot for taking the time to do this
girello71 said:
Can I use it with stock rom too? Tnx
Click to expand...
Click to collapse
I don't try backup / restore (nandroid) with stock rom maybe it work, but when i try to flash stock rom it skip the different part and don't write anything.
However, what could be interesting if backup / restore work is to make a backup of a fresh install stock rom with the last update include.
boqonx said:
Great Job!! Now we just need some AOSP/CM7 love
Click to expand...
Click to collapse
I currently work on the CM7, but be patient, it's more complicated than for recovery.
Of course dude, take your time and slowly churn that tasty gingerbread dough
wolfx said:
I currently work on the CM7, but be patient, it's more complicated than for recovery.
Click to expand...
Click to collapse
Finaly, one more rom builder. We need some options to choose from. Wish you the best of luck. And if you dont mind, maybe from time to time post progress on your work. If you need some beta testing, im there
Back to square 0
Hi,
Based on the positive response i started to install the ClockworkMod recovery. As i got the error message that there was no space on the device i did a factory reset (i have 1.3c). Now the installation of the ClockworkMod looked ok. But after i rebooted the device nothing happened (blank screen). Only the initial screen shows (with pressing the on/off-vol+ buttons) after this just a blank screen. Also if i press within the 3 sec the on/off and vol+ the screen goes blank. So i guess i have now a bricked folio and i will start to read up how to unbrick.
BTW i do not know if i did something wrong or there is/was some particularities with my configuartion or that the clockworkmod still needs some work..
Butchi said:
Hi,
Based on the positive response i started to install the ClockworkMod recovery. As i got the error message that there was no space on the device i did a factory reset (i have 1.3c). Now the installation of the ClockworkMod looked ok. But after i rebooted the device nothing happened (blank screen). Only the initial screen shows (with pressing the on/off-vol+ buttons) after this just a blank screen. Also if i press within the 3 sec the on/off and vol+ the screen goes blank. So i guess i have now a bricked folio and i will start to read up how to unbrick.
BTW i do not know if i did something wrong or there is/was some particularities with my configuartion or that the clockworkmod still needs some work..
Click to expand...
Click to collapse
If you delete the update.zip for clockwork recovery you will have normal recovery. When installing clocwork you pu the zzip to root of exterenal sd card boot to recovery do system update, device reboots, now you have to do the system update again, your now in clockwork recovery
Butchi said:
Hi,
Based on the positive response i started to install the ClockworkMod recovery. As i got the error message that there was no space on the device i did a factory reset (i have 1.3c). Now the installation of the ClockworkMod looked ok. But after i rebooted the device nothing happened (blank screen). Only the initial screen shows (with pressing the on/off-vol+ buttons) after this just a blank screen. Also if i press within the 3 sec the on/off and vol+ the screen goes blank. So i guess i have now a bricked folio and i will start to read up how to unbrick.
BTW i do not know if i did something wrong or there is/was some particularities with my configuartion or that the clockworkmod still needs some work..
Click to expand...
Click to collapse
Not sure you bricked it, you can use the fastboot method to flash the recovery again, then you can use the recovery to flash a full rom.
Btw, where do we have fastboot access? I thought what we have is the tegra bootloader which is quite risky to enter? (heard of the story of ppl getting stuck in the bootloader with no way to get out)
boqonx said:
Btw, where do we have fastboot access? I thought what we have is the tegra bootloader which is quite risky to enter? (heard of the story of ppl getting stuck in the bootloader with no way to get out)
Click to expand...
Click to collapse
you can access fastboot by pressing POWER x 3 ( attention : 3 times only not 4) then VOL UP when the folio start. I use it everyday to flash recovery.img or boot.img with no problems.
Usage :
place the recovery.img or boot.img in the same directory as fastboot then from a shell navigate to your fastboot directory and us the following command :
for recovery:
Code:
./fastboot flash recovery recovery.img
for boot:
Code:
./fastboot flash linux boot.img
you can use the -w option to wipe data and cache
for reboot :
Code:
./fastboot reboot
wolfx said:
you can access fastboot by pressing POWER x 3 ( attention : 3 times only not 4) then VOL UP when the folio start. I use it everyday to flash recovery.img or boot.img with no problems.
Usage :
place the recovery.img or boot.img in the same directory as fastboot then from a shell navigate to your fastboot directory and us the following command :
for recovery:
Code:
./fastboot flash recovery recovery.img
for boot:
Code:
./fastboot flash linux boot.img
you can use the -w option to wipe data and cache
for reboot :
Code:
./fastboot reboot
Click to expand...
Click to collapse
So if we flash recovery.img thru fastboot we should be able to boot in to clockwork recovery via rom manager?
wolfx said:
Usage :
place the recovery.img or boot.img in the same directory as fastboot then from a shell navigate to your fastboot directory and us the following command :
Click to expand...
Click to collapse
Thanks for all the responses but i go step by step (hopefully "unbricking" my folio).
I was able to get to the display of the line "Starting Fastboot USB download protocol, please execute 'fastboot' command" (by pressing 3times the power button).
I connected the folio with USB to my PC (Win7) but the needed driver could not be found in the PC.
So i have a couple questions.
-Is the PC-driver part of the SDK? or how can i get the driver?
-I guess that with the PC i can copy via USB the recovery image to the fastboot directory. Is this correct? How else can i get the recovery image to the fastboot directory?
-Is the recovery image the "Folio stock image for full restore to stock rom" Dexters thread
Hope i can get some more help with restoring my system.
nickwarn said:
So if we flash recovery.img thru fastboot we should be able to boot in to clockwork recovery via rom manager?
Click to expand...
Click to collapse
Rom manager don't work with this recovery for now, official support must be added by Koush in rom manager before. I will commit the source to him when recovery is finalized.
Butchi said:
Thanks for all the responses but i go step by step (hopefully "unbricking" my folio).
I was able to get to the display of the line "Starting Fastboot USB download protocol, please execute 'fastboot' command" (by pressing 3times the power button).
I connected the folio with USB to my PC (Win7) but the needed driver could not be found in the PC.
So i have a couple questions.
-Is the PC-driver part of the SDK? or how can i get the driver?
-I guess that with the PC i can copy via USB the recovery image to the fastboot directory. Is this correct? How else can i get the recovery image to the fastboot directory?
-Is the recovery image the "Folio stock image for full restore to stock rom" Dexters thread
Hope i can get some more help with restoring my system.
Click to expand...
Click to collapse
For driver :
- Download the android SDK here
- Edit "<your-android-sdk-folder>/usb_driver/android_winusb.inf"
- Add the following after [Google.NTx86] (or [Google.NTamd64] if 64 bits windows)
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
- start your folio in fastboot mode and plug in. Win will not find the right driver to use
- Force driver installation : click update driver -> have disk -> point to "<your-android-sdk-folder>/usb_driver/android_winusb.inf"
- Choose bootloader driver
After this you normally can use fastboot place in : <your-android-sdk-folder>/tools
For the recovery.img you can use the one include in the update.zip or one from FolioMod.
Hope it can help you
I am still not there...
Again thanks for all the help and support
OK I installed the SDK (and the JRE as it was also a requirement). But i did not find the USB driver so far (which is strange because i had connected the folio with the PC earlier).
While doing all that i discovered that somehow the ClockworkMod Recovery was installed correct. I could get the expanded ClockworkMod menu. (Using the power button and simulteaneous the Vol+ button within the 3 sec. And whatever i selected update or recovery, i got to the ClockworkMod menu.) This looked promissing.
So i put an update.zip on the sdcard (dextermod 1.3b).
In the menu i selected 'apply sdcard:update.zip'. After this i got the screen (white text) Confirm install? THIS CAN NOT BE UNDONE and (yellow text) 7 lines with '-No', one line with '-Yes - install /sdcard/update.zip' and 3 more lines with '-No'.
After selecting the 'Yes' line i got the following messages:
--Install from sdcard...
Finding update package...
Opening update package...
Installing update...
Installation aborted
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Strange enough, even after the update was aborted, the system started again after i selected to reboot in the ClockworkMod menu. Wow. Who knows what happened may explain this. But nice for me the system works again (till the next time).
Looking very nice. Just flashed it and made a backup
Edit: February 2012: please disregard ALL information below this red text. ROM Manager now supports the Huawei U8160, and will flash the official recovery build from the app. See the Getting Started with ROM Manager & ClockworkMod section in this post.
ClockworkMod Recovery for Vodafone Smart (Huawei U8160)
Current release - v0.1 - 12 September 2011 [CWM Ver. 4.0.1.5]
What is ClockworkMod Recovery? From AddictiveTips:
ClockworkMod – also known as Clockwork and CWM – is a custom recovery for Android phones and tablets that allows you to perform several advanced recovery, restoration, installation and maintenance operations on your Android device that aren’t possible with the stock recovery.
Click to expand...
Click to collapse
Installation - Fastboot Method:
Use this method if you have never installed a build of ClockworkMod before.
Download the Android SDK for your operating system [Windows users are recommended to download the .zip version].
Extract the fastboot / fastboot.exe file from the tools folder of the Android SDK zip file to a folder on your computer.
Download the latest zip release of ClockworkMod using the link(s) below.
Open the ClockworkMod .zip file and extract the recovery.img file to the same folder as the fastboot / fastboot.exe binary.
Reboot (or turn your phone one) whilst holding the power and volume down keys. Your phone will now be in "fastboot" mode.
Open a terminal or command prompt, and run the following commands:
Note: these are example instructions for a Windows user who has extracted the fastboot.exe and recovery.img to C:\VodafoneSmart. Adjust the folder path to wherever you extracted these files.
Code:
cd C:\VodafoneSmart
fastboot flash recovery recovery.img
fastboot reboot
Installation - ClockworkMod Method (zip):
Use this method if you already have ClockworkMod installed, and you wish to update the version that already exists on your phone.
Download the latest zip release using the link(s) below.
Transfer the .zip file to your SD card. Do not extract the .zip file - only copy it.
Reboot into ClockworkMod, choose the option Install zip from sdcard -> choose zip from sdcard. Select the current release, and confirm the update by selecting Yes. Reboot and enjoy!
Usage:
To access ClockworkMod recovery, any one of the follow methods will work:
If you are running a build of CyanogenMod, choose the Recovery option from the reboot menu;
Run "adb shell reboot recovery" on any rooted ROM;
Reboot your device whilst holding the power and volume up keys.[/li]
Once you've entered ClockworkMod Recovery, you will be presented with several options (some familiar, some not). I won't try to explain all of the options, as there are better guides on the internet (example: the AddictiveTips site above). However, these are the ones you should really know about:
Wipe data/factory reset - same as before
Wipe cache partition - same as before
Install zip from sdcard -> choose zip from sdcard - this is the new method you will be using to flash ROMs and update packages
Backup & restore - this menu lets you perform a full backup or restore of your boot, /cache, /data/ & app2sd partition (which is compatible with mad2sd)
Mounts & storage -> mount USB storage - this lets you enable UMS mode to copy update packages (if you forgot to transfer before rebooting into recovery)
Advanced -> partition SD card - this lets you easily partition your SD card for use with mad2sd or any third-party app2sd solutions. It lets you select the size for the EXT4 partition as well as swap. MAKE SURE TO BACKUP ALL DATA ON YOUR CARD BEFORE USING THIS OPTION.
Changelog:
[CWM Ver. 4.0.1.5] v0.1 zip - 12 September 2011
First release.
Hi, I've been trying this guide and am having trouble with both methods.
Fastboot Method
I get into fastboot mode (where it's just at the hourglass screen), and type in "fastboot flash recovery recovery.img". The command prompt just says "Waiting for device", and never updates.
ClockworkMod Method
I installed the CWM I got off the Android Market, and then tried to reboot into recovery mode (both by rebooting through CWM and by pressing Volume+Up & Power). I just end up waiting at the hourglass screen like when it's in fastboot mode.
Any idea what I'm doing wrong?
for fastboot try without battery inside (only usb) works for me
if fastboot wont work try methode 3. http://www.addictivetips.com/mobile/how-to-install-a-custom-recovery-to-an-android-phone-device/
with extractet recovery.img from zip (http://forum.xda-developers.com/showthread.php?p=17496869)
jajajim said:
for fast boot try without battery inside (only usb) works for me
Click to expand...
Click to collapse
Tried that too; didn't work.
Thanks, worked for me with fastboot on u8180
zodac01 said:
Fastboot Method
I get into fastboot mode (where it's just at the hourglass screen), and type in "fastboot flash recovery recovery.img". The command prompt just says "Waiting for device", and never updates.
Click to expand...
Click to collapse
That happens to me too... I also noticed that in device manager is missing driver for Android 1.0? I don't know what to do next. Someone knows? Thanks
EDIT: It works ... download Pulse_Drivers_xp_w7_w764.zip from dc-unlocker (sry can't post link).
EDIT: It works ... download Pulse_Drivers_xp_w7_w764.zip from dc-unlocker (sry can't post link).
Click to expand...
Click to collapse
for linux users??
just a note, the U8160 has a different USB hardware ID when in fastboot mode, and so inside 70.android.rules you need to add "12d1" and "18d1"
18d1 is the fastboot USB id and 12d1 is the adb USB id
This is for linux btw.
i've two questions for subpsyke:
it's planned update to cwm recovery 5?
Why don't knowledge Rom Manager cwm recovery in your cyano release for U8160?
p.s
sorry for my bad english, i'm italian's users ...
thanks, needed this!
renegade_82 said:
i've two questions for subpsyke:
it's planned update to cwm recovery 5?
Why don't knowledge Rom Manager cwm recovery in your cyano release for U8160?
p.s
sorry for my bad english, i'm italian's users ...
Click to expand...
Click to collapse
Yea i got this problem too, in ROM manager, this recovery isnt detected, any ideas on how to get it?
EDIT: I flashed the IDEOS recovery through rom manager then flashed back this recovery, and now it works like it should.
EDIT: done, thanks a lot
for pulse driver, turn on phone, then press power + volume down, then plug usb, PC will search for a driver
fastboot is just: power button + volume down (and then it sticks on logo or hourglass) then open command prompt on pc
pulse driver:
http://www.mediafire.com/?l9zoonl8kygcejm
Hi there
Download the Android SDK for your operating system [Windows users are recommended to download the .zip version].
Extract the fastboot / fastboot.exe file from the tools folder of the Android SDK zip file to a folder on your computer.
Click to expand...
Click to collapse
I'm a windows user and i've downloaded the Sdk zip and there's no fastboot.exe on any of the folders... :|
Any suggestions?
Thanks in advance
jpcoke said:
I'm a windows user and i've downloaded the Sdk zip and there's no fastboot.exe on any of the folders... :|
Click to expand...
Click to collapse
Download android-sdk-windows-1.6_r1
The latest sdk doesn't have it
fastboot and recovery
http://www.wuala.com/freegroup/cyanogen/VodafoneSmart.zip/
u8160 cwm
iam havving problems around here
i need more instruction , i have the folder with recovery and fastbot ,but how to put tham on the phone ? i have rooted my device sucesfully iam stuck rebooting on recovery mode , i cant reboot as you show us , or enter in fastboot , please help me do it
aripelx said:
Download android-sdk-windows-1.6_r1
The latest sdk doesn't have it
Click to expand...
Click to collapse
cant seem to find this version of the sdk to download, anyone got a link?
thanks
I have a branded Vodafone Smart (U8160) and it stucks everytime at the hourglass screen. It won't get into recovery mode.
How do I fix this?
Edit: I haven't rooted it yet. Have I to do it before I could install CMW?
mcpossity said:
I have a branded Vodafone Smart (U8160) and it stucks everytime at the hourglass screen. It won't get into recovery mode.
How do I fix this?
Edit: I haven't rooted it yet. Have I to do it before I could install CMW?
Click to expand...
Click to collapse
for cwm it's power button+volume UP
fastboot power button+volume DOWN
it's easy to root with gingerbreak v1.2
---------- Post added at 01:54 PM ---------- Previous post was at 01:54 PM ----------
asidhowz said:
cant seem to find this version of the sdk to download, anyone got a link?
thanks
Click to expand...
Click to collapse
man, I have posted the link just up
Thanks, worked like a charm
I just bought a second hands xoom , I really had bad luck because my device reboots itself automaticaly too often
it's about a MZ601 3G 32g. of course I can't find the seller back in my life ...
OS 3.2
build number H.6.5-17-3
Kernel 2.6.36.3
I don't know my xoom belongs to which country . I would like to root it
Becasue I've heard it might be helpfull .
I 'm really an newbie !
Can someone help me out ?
Best Regards
Kevin
The MZ601 is the MOTO/EU/umts_everest 3G: 3.2/H.6.5-17-1 GSM (means you can use any SIM card in your device, you can send and receive SMS)
You first need to install Android SDK, Here is a link to the ADB Tutorial.
http://www.xda-developers.com/android/adb-easy-tutorial/
Instructions assuming that you have successfully installed the Android SDk -
(solarnz)
1. Downloading the rooting-update zip file.
Download the zip file from here - http://goo.gl/Om9aP
Now place this on your external sdcard. - Sorry this is a requirement at the moment, like I said this is a bit rushed.
2. Flashing recovery
1. Download this Recovery image. http://bit.ly/iLRAIV (place this image in you SDK PlatformTools Folder, or which ever folder that contains your adb.exe)
2. If your device is locked, now is a good time to unlock it.
Code:
adb reboot bootloader
fastboot oem unlock
fastboot reboot
3. Flash recovery
Code:
adb reboot bootloader
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.
4. Flashing the Xoom-Universal-Root.zip file.
If you're in clockwork mod recovery you can continue (This recovery image will say it is clockwork mod) . If you're not looking at clockwork mod, then you need to repeat step 3 again.
In cwm, go into "install zip from sdcard" -> "Choose zip from sdcard", then select the Xoom-Universal-Root.zip file you downloaded.
Note: use the volume buttons to navigate and the power button to select
Reboot your device and then welcome to your rooted device!
AS Always, If This Was Helpful - Hit The Thanks!
Mjamocha said:
The MZ601 is the MOTO/EU/umts_everest 3G: 3.2/H.6.5-17-1 GSM (means you can use any SIM card in your device, you can send and receive SMS)
You first need to install Android SDK, Here is a link to the ADB Tutorial.
http://www.xda-developers.com/android/adb-easy-tutorial/
Instructions assuming that you have successfully installed the Android SDk -
(solarnz)
1. Downloading the rooting-update zip file.
Download the zip file from here - http://goo.gl/Om9aP
Now place this on your external sdcard. - Sorry this is a requirement at the moment, like I said this is a bit rushed.
2. Flashing recovery
1. Download this Recovery image. http://bit.ly/iLRAIV (place this image in you SDK PlatformTools Folder, or which ever folder that contains your adb.exe)
2. If your device is locked, now is a good time to unlock it.
Code:
adb reboot bootloader
fastboot oem unlock
fastboot reboot
3. Flash recovery
Code:
adb reboot bootloader
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.
4. Flashing the Xoom-Universal-Root.zip file.
If you're in clockwork mod recovery you can continue (This recovery image will say it is clockwork mod) . If you're not looking at clockwork mod, then you need to repeat step 3 again.
In cwm, go into "install zip from sdcard" -> "Choose zip from sdcard", then select the Xoom-Universal-Root.zip file you downloaded.
Note: use the volume buttons to navigate and the power button to select
Reboot your device and then welcome to your rooted device!
AS Always, If This Was Helpful - Hit The Thanks!
Click to expand...
Click to collapse
Thx so much I've root my device now .
I've one extra icon calls superuser ??? What can i do with it ?
What is now difference between a normal and an root device ?
What do I have more possiblilitie with rooted device ?
best regards
Kevin
Is this method workable in 4.0.3 or even freshly released 4.0.4?
@Kevin
superuser gives you access to your device settings and all files.
Install root explorer, and you can browse your system files, but be very careful.
With root you can customize you xoom.
To find out more on what root access can do for you, use google to search,
this would not be the place for that. After you get a better understanding of the
root process, browse this forum for Modifications and what not.
Now you gotta find a ROM that fits your taste. You can start here:
http://forum.xda-developers.com/showthread.php?t=1459641
Make sure you Flash the GAPPS directly after you flash your new ROM, then reboot. There are many ROMS to choose from in this forum. Find the one that fits your device and your needs. Welcome to the Dark Side my Friend!
---------- Post added at 10:48 PM ---------- Previous post was at 10:38 PM ----------
Ftnjohn said:
Is this method workable in 4.0.3 or even freshly released 4.0.4?
Click to expand...
Click to collapse
Yes you can root your device on stock 4.0.3 using this method. From there find a 4.0.4 ROM to your taste and flash it in CWM recovery. (If you are using a XOOM) I prefer the EOS 4.0.4 ROM which is their Nighty Builds. You can find the Xoom EOS Nightly ROMs that fits you device by searching the Forum.
If This Was Helpful Hit The Thanks!
Hi all.
I have an Spanish wifi-only Xoom (MZ604) and I'm tired of waiting for motorola's updates (still in Honeycomb 3.2!!!).
I want to test either EOS3 (Android 4.1.1) or EOS2 (Android 4.0.4) custom roms. I've read almost all tutoriales but I still have some doubts about the procedures... could anybody check this message and warn me if I'm going to do something wrong?
DOUBT 1.- Key shortcuts in Xoom
Can anybody tell me the existing key combinations in Xoom? I only know about POWER+VOL_UP key to enter bootloader mode.
DOUBT 2.- How to install CWM.
If I understand it correctly, both EOS2 and EOS3 should be installed from CWM recovery...
Is the following procedure OK?
- Some tutorials say that you have to be root first to install CWM ... is it really needed? Can't be done directly with ADB?
- Install Android SDK in the PC.
- Download eos-recovery-r6.img or eos-recovery-r6-softkeys.img
- Connect XOOM to PC with the original USB cable.
- Reboot XOOM in bootloader mode (Power + VolUp)
- Exec adb and then:
fastboot oem unlock <---- is this a requirement?
fastboot flash recovery eos-recovery-r6.img
fastboot reboot
DOUBT 3.- How to install or upgrade EOS 2 or 3 ROM?
Is the following procedure OK?
- Download ROM and gapps zip files.
- Start XOOM in recovery mode (CWM) -> How to do this?
- Do a nandroid backup.
- Wipe everything (data, cache, dalvik, etc)
- Install ROM zip.
- Install gapps zip.
- No need to do anything to root it, the rom is already rooted <-- is that right?
- Reboot
Is everything OK? Did I miss anything? Do I need to root my 3.2 install before any other step? Do I have to do the "oen unlock"?
Thanks.
All you need to do is unlock your boot loader and get into flashing eos3. Will give you details how to soon
Sent from my MZ601 using Tapatalk 2
wesamothman said:
All you need to do is unlock your boot loader and get into flashing eos3. Will give you details how to soon
Click to expand...
Click to collapse
Thanks for answering. If I'm understanding you correctly, you say that I don't need CWM and I can just flash the EOS ROM directly to my xoom without "applying" it as a zip in CWM...
I would really like to install CWM, I appreciate a lot the possibility to do "nandroid" backups to be able to go back before installing kernels, updates or so ...
NoP_Compiler said:
Thanks for answering. If I'm understanding you correctly, you say that I don't need CWM and I can just flash the EOS ROM directly to my xoom without "applying" it as a zip in CWM...
I would really like to install CWM, I appreciate a lot the possibility to do "nandroid" backups to be able to go back before installing kernels, updates or so ...
Click to expand...
Click to collapse
Since you are going to install EOS Jellybean, I don't advise you with CWM. A different recovery made by EOS team is better through which you can do nandroid backup and other stuff...
Here is what you need to do step by step...
Note: please read this procedure carefully more than once until you are fully aware of it. If you have any doubts or concerns, just ask to avoid confusion before you apply. This should be followed step by step.
To summarize:
First, download the above ROM and GAPPs and put them onto your xoom internal and external SD card. Put them under /mnt/sdcard for internal sd or somewhere accessible, and under the root of your external sd card.
To download:
• Get the Motorola USB drivers to your laptop: http://developer.motorola.com/docstools/USB_Drivers/
• Get the Android SDK to your laptop: http://developer.android.com/sdk/index.html
• Recovery Image: http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.img
• GAPPS: http://goo.im/devs/teameos/roms/eos3/gapps/gapps-jb-20120726-eos-signed.zip
• ROM: http://goo.im/devs/teameos/roms/eos3/nightlies/wingray/ ; get the latest one...
Steps:
1. Power off your XOOM device.
2. Press and hold the volume down button while pressing the power button at the same time. Note: Even if your xoom starts again, just keep the button pressed until you see "Starting fastboot protocol" on the screen.
3. Connect Xoom to your computer via USB.
4. Open a ‘Command Prompt’ or ‘Terminal’ window on your computer in your sdk/tools folder. This is the sdk you downloaded above.
5. unlock your xoom and flash the recovery image. The recovery image should be in your current working directory where you have command line navigated to: Type:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery eos-recovery-r6.img
fastboot reboot
adb reboot recovery
Now, you have your device unlocked and recovery installed.
Reboot your xoom by selecting the option "reboot system now" from recovery. you can navigate up and down using the volume buttons. Once an option is highlighted, press the power button to select, you will still have your old ROM.
To flash the other ROM downloaded above,
1. Boot into recovery by:
i. As soon as you hit the reboot command above, you should see a Motorola logo appear. Wait 3 seconds and tap the Volume down button and the words Android Recovery should appear on the screen. When you see that, tap the Volume up button and you’ll boot into recovery.
2. From within Recovery, perform wipe data, wipe cache, and go to advanced, wipe dalvik cache and battery stats. Don't worry, if the ROM and GAPPs are deleted, which should not be the case, you will have them on your external sd card
Note: wipe data will delete your stuff on the xoom. It would be great if you backup your files that you need to your external sd card before you start any of this procedure.
3. In recovery, navigate to install zip from sdcard > choose zip from sd card and select the EOS ROM you copied to the root of the SD card. Once the files are flashed, DO NOT reboot afterwards. Hold on.
4. Again, from Recovery, choose install zip from sdcard > choose zip from sd card and select the GAPPs you copied to the root of the SD card.
Then hit reboot system now. It will take 2 - 3 minutes for the first reboot. Setup your google account. and you are good to go.
Later reboots will be much faster (around 30 - 45 seconds). The more apps you install, the slower it boots...
That is pretty much it. Enjoy, I hope this helps you
Of course it helps! In fact, a lot.
When I was talking about CRW I really meant EOS recovery (which is based in CRW itself IIRC).
The only that I can't understand is why some tutorials ask me to root the tablet before doing all this process...
Anyway, I think I'm finally going with EOS3 + EOS recovery if nobody here advices me to flash EOS 2 instead...
Sent from my Samsung Galaxy S2 using Tapatalk Pro.
So, before flashing:
- Do you think EOS3 (JB in Xoom) is mature enough to use it, or I should go with EOS2 final (ICS)?
- Do you know of anything not working in a wifi xoom with EOS3 rel.127?
- I've downloaded eos6-recovery.img ... do you think I should flash the "soft-keys" or the rogue-recovery instead?
- I don't have Microsoft Windows in my laptop: I work under Linux, so I haven't downloaded Motorola's USB drivers... I imagine that they are not needed under Linux, and It will work just with SDK's "adb" and "fastboot", right?
- Can the device be bricked with this procedure, or there is always a "Power+VolKey" way to flash a stock image? (like galaxys2 that its almost unbrickable).
PS: Thanks for informing me in the other thread that the EOS rom comes already rooted
I will be away for couple of hours, will answer your questions all as soon as I get back...
Sent from my MZ601 using Tapatalk 2
NoP_Compiler said:
So, before flashing:
- Do you think EOS3 (JB in Xoom) is mature enough to use it, or I should go with EOS2 final (ICS)?
- Do you know of anything not working in a wifi xoom with EOS3 rel.127?
- I've downloaded eos6-recovery.img ... do you think I should flash the "soft-keys" or the rogue-recovery instead?
- I don't have Microsoft Windows in my laptop: I work under Linux, so I haven't downloaded Motorola's USB drivers... I imagine that they are not needed under Linux, and It will work just with SDK's "adb" and "fastboot", right?
- Can the device be bricked with this procedure, or there is always a "Power+VolKey" way to flash a stock image? (like galaxys2 that its almost unbrickable).
PS: Thanks for informing me in the other thread that the EOS rom comes already rooted
Click to expand...
Click to collapse
Alright, eos jelly bean is fully stable, ,such faster and smoother than ICS. You want feel the difference until you try it... however, eos ICS is stable too and has more features and addons by eos because it has been there under dev for longer time, jellybean is new, one month old only... I recommend you to go for jellybean, and try and see for yourself. At anytime you can flash ICS since your Xoom booloader is already unlooked and recovery installed, you can do that by just wiping data and flash ICS zip. That is as simple as that...
For Motorola drivers on Linux, I think it is not needed, adb is built in with Linux, but I am not sure as I haven't tried that yet.
For eos recovery, don't use the soft key version, use the normal one...
with this recovery, you will be safe, because at all times, your external SD is accessible in emergencies...
Hope that helps...
Sent from my MZ601 using Tapatalk 2
You have it down perfectly. Just to recap.
1. Set up android sdk. Download recovery image and store in sdk folder. Download rom/gapps and store on tablet.
2. Boot into fastboot (power + volume up).
3. fastboot oem unlock (required). This will wipe all data.
4. fastboot flash recovery recovery.img (whatever recovery you decide to go with, I recommend eos soft key).
5. boot into recovery, make nandroid backup, flash rom of your choice + gapps if necessary.
People tie rooting to flashing custom roms because many people have become so reliant on apps like rom manager that flash the recovery for you, an app that requires root access. I never rooted my galaxy nexus or xoom. I simply flashed recoveries in fastboot and proceeded to flash roms in recovery.
It actually bothers me how some have become so reliant on root access to flash roms. It has gotten to a point where many people genuinely don't know the difference and that, to me, says they don't really understand what it is they're doing, which will lead to issues should they ever need to troubleshoot.
You seem to have it down well though. Good luck.
Thanks a lot to both.
I'm still waiting for JDK to download for Android SDK to work (I'm on hollydays in a small house in the middle of the forest and Im connecting with GPRS via tethering...).
I'll inform about the results...
Sent from my Samsung Galaxy S2 using Tapatalk Pro.
Good luck...
Sent from my MZ601 using Tapatalk 2
Ok. EOS6-RECOVERY installed correctly. There are a couple of mistakes and some missing info in the "tutorial", so I'm going to change it to help future users:
I finally did it under Windows because almost all tutorials in Internet explain all the possible problems that you can find in Windows, and it's a "too risky" task for me to "experiment" by myself.
PART 1 .- HOW TO INSTALL EOS6 RECOVERY:
Originally quoted from wesamothman:
First, download the above ROM and GAPPs and put them onto your xoom external SD card. Put them in a folder called /sources/ of your external sd card.
- Get the Motorola USB drivers to your laptop: http://developer.motorola.com/docstools/USB_Drivers/
- Get the Android SDK to your laptop: http://developer.android.com/sdk/index.html
- GAPPS: http://goo.im/devs/teameos/roms/eos3/gapps/gapps-jb-20120726-eos-signed.zip
- ROM: http://goo.im/devs/teameos/roms/eos3/nightlies/wingray/ ; get the latest one...
And the most important:
- Recovery Image: http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.img
Check that the md5sum of this file is correct and matches with the one provided in the download page. This is the most important file because it will allow to install the CWM recovery system and it's CRITICAL that the file is not corrupted.
Steps:
a.- Install in your PC the lastest JavaSE JDK from Oracle's website.
b.- Install in yout PC Android SDK, open Windows' cmd, enter the android-sdk folder and run:
Code:
tools\android.bat update sdk
Now select "Android SDK Tools", "Android SDK platform-tools", and Extras/"Google USB Driver". Click on "Install packages".
c.- Enable USB debugging in the XOOM (in settings, development).
d.- Install the Motorola USB drivers for your laptop (32 or 64 bits, check it in the Windows system properties).
e.- Plug the Xoom to your laptop.
f.- Execute cmd and enter the android-sdk/platform-tools folder.
Run "adb devices", if you get an empty "List of devices attached", then you must enter the control-panel -> devices and "Fix problem with device" over the MZ60x device. After a While, Windows will fix it and "adb devices" will show a message like:
Code:
List of devices attached
037887sda897xz device
(the digits string will vary according to your device)
NO NEED TO DO THIS:
NO -> 1. Power off your XOOM device.
NO -> 2. Press and hold the volume down button while pressing the power button at the same time. Note: Even if your xoom starts again, just keep the button pressed until you see "Starting fastboot protocol" on the screen.
Because the first command show after this lines: (adb reboot bootloader) won't work while in fastboot. Only "fastboot" commands work in fastboot mode. If you try that command in fastboot mode, it will say "Error: device not found".
So just, with your xoom working under the Android OS, do:
Code:
adb reboot bootloader
With the above, you'll enter fastboot mode without needing to press any key in the startup.
Now your Xoom will show the Motorola logo and the words "Fastboot protocol...". If you need to stop now for any reason, you can abandon this mode safely and reboot the tablet with "Power+VolUP+VolDown" for a few seconds.
But let's continue.... If you now do:
Code:
fastboot devices
You should get a string like
Code:
List of devices attached
037887sda897xz fastboot
If you don't see that string (and you see and error about device not found), you have to "fix/repair" the usb drivers again in the Windows ControlPanel / Devices. Now you'll see a "FASTBOOT" device instead of the MZ60x you repaired before (that's why we have to repair/fix again the device, because WIndows see it as a different device while in fastboot mode).
After repairing it, unplug and plug the USB cable (still in fastboot mode) and repeat the command:
Code:
fastboot devices
Now it will work and you'll see the device recognized by "fastboot"
Issue the following command to unlock the Xoom (you'll void the warranty):
Code:
fastboot oem unlock
Follow the Xoom's onscreen instructions to unlock the bootloader. You have to use VolDown to move through options and VolUP to accept an option.
The xoom will reboot and your old android OS will show, but now with a factory reset. Select language, time, etc and enable again USB debugging and execute in the PC:
Code:
adb reboot bootloader
(to start again the tablet in fastboot mode)
Now copy the file eos-recovery-r6.img to the android-sdk/platform-tools/ folder and execute:
Code:
fastboot flash recovery eos-recovery-r6.img
You will see something like:
Code:
C:\Users\sromero\Desktop\android-sdk-windows\platform-tools>
fastboot flash recovery eos-recovery-r6.img
sending 'recovery' (4114 KB)...
OKAY [ 0.499s]
writing 'recovery'...
OKAY [ 1.014s]
finished. total time: 1.529s
Check in the xoom's screen that the file was correctly written and execute:
Code:
fastboot reboot
You xoom will start again in Android OS mode. Execute:
Code:
adb reboot recovery
And you'll start the nice EOS Recovery (based on Clockworld Mod) recovery system.
You can also do it manually by powering on the Xoom and when the motorola logo appears, wait 3 seconds and press VolUp.
Now, you have your device unlocked and recovery installed. Now, you are SAFE because you can do nandroid backups and restores and can put any ROM in your system and go back with a backup or flash another different rom.
PART 2 .- HOW TO USE CWM / EOS RECOVERY
Code:
Up -> VolumeUp button
Down -> VolumeDown button
Select -> POWER button
PART 3 .- HOW TO INSTALL EOS3 ROM:
Under recovery mode (abd reboot recovery), do:
- Backup/restore -> backup to external SD.
- Wipe data/factory reset
- Wipe cache
- Advanced -> Wipe Dalvik Cache
- Advanced -> Wipe Battery Stats
- Install ZIP from SDCARD -> /sources/ -> the eos3 rom .zip file.
- Install ZIP from SDCARD -> /sources/ -> the gapps .zip file.
- Reboot
- Enjoy your new rom!
Very well detailed... great...thx.
Sent from my MZ601 using Tapatalk 2
wesamothman said:
Very well detailed... great...thx.
Click to expand...
Click to collapse
No... thank you for the initial info
After restarting, I have a notification about a ROM update (128). The ROM-management app allows me to download it or apply a incremental update...
Do you know if that second option (incremental update) is safe?
Anyway, I can just always do a Nandroid and test it ... having CWM I can't loose never anything, right?
Of course it is safe, I use it a lot. Just boot into recovery now by long press on power menu, select reboot, recovery,
First download build128. It will be under /storage/sdcard0/goo manager.
From recovery, wipe cache, dalvik, flash build 128, and reboot,
FYI, this latest build has theme engine now
Sent from my MZ601 using Tapatalk 2
wesamothman said:
First download build128. It will be under /storage/sdcard0/goo manager.
From recovery, wipe cache, dalvik, flash build 128, and reboot,
FYI, this latest build has theme engine now
Click to expand...
Click to collapse
So, the incremental update has to be flashed from recovery too?
I'll try it after a few days, when people confirms that it has not any major bug...
Thanks.
NoP_Compiler said:
Thanks a lot to both.
I'm still waiting for JDK to download for Android SDK to work (I'm on hollydays in a small house in the middle of the forest and Im connecting with GPRS via tethering...).
I'll inform about the results...
Sent from my Samsung Galaxy S2 using Tapatalk Pro.
Click to expand...
Click to collapse
Worth noting that to use fastboot and stuff, you only really need to install the Android SDK Platform-tools, maybe the regular SDK tools as well, I can't remember.
You don't need to install all the other stuff.
---------- Post added at 08:02 AM ---------- Previous post was at 08:01 AM ----------
NoP_Compiler said:
So, the incremental update has to be flashed from recovery too?
I'll try it after a few days, when people confirms that it has not any major bug...
Thanks.
Click to expand...
Click to collapse
Yes, any updates/mods/gapps updates need to be flashed in recovery.
Unless specified that its necessary by devs though, you don't need to wipe anything. I've been on JB nightlies from day 1 and I haven't wiped cache or anything since the initial wipe.
Is it possible to...
a.- change the system font (too 'light' in my xoom).
b.- disable jellybean UI animations...
?
I don't know about question a, though I'm sure its possible.
As for question b, try a different launcher. Apex launcher and nova launcher are both popular Android 4.0+ launchers (check play store for them).
Eos ROM,m settings, developer options, disable animations and transitions
Sent from my MZ601 using Tapatalk 2