Guest Bruno Ferreira Posted May 12, 2010 Report Posted May 12, 2010 (edited) Hi everyone!! I'm new here and totally newb in Android OS, so i have some questions about the root process! #1 - My phone has a generic ROM, since i bought it at expansys, do i need to create a "goldcard"?? #2 - If don't have to create the "goldcard" where do i start to begin (what step) rooting the phone? #3 - what about app2sd, can i install it, and how can i do it?? If i have more doubts i'll call back again :) Thanx Bruno Edited May 12, 2010 by Bruno Ferreira
Guest Sandman83 Posted May 12, 2010 Report Posted May 12, 2010 When step1 is executing, i see the "radio" word, someone can explain what is it?
Guest NarutoDKz Posted May 12, 2010 Report Posted May 12, 2010 I'm about to do this. (In Linux Mint) But I got three BIG questions: First and most important. Is there a good reason to root? Second: Will you be able to tell that it is rooted, (Any special apps or Icons) And third: Will memory decrease/increase. Please answer.
Guest freeborn Posted May 12, 2010 Report Posted May 12, 2010 I can not connect VPN after rooting, Anyone has the same problem?
Guest judgey2k10 Posted May 12, 2010 Report Posted May 12, 2010 Without repeating step 1 i'm going straight to step 2 (recovery)? Yep :)
Guest pina Posted May 12, 2010 Report Posted May 12, 2010 I tested my A2SD using Gscript, but I came across this: Should I be worried about the error at the beginning of the script? I just tried to install Navigon and before the installation, I got 125MB fre space, after the installation 111MB... So I guess A2SD isn't working? But Gscript tells me it's ok...? I'm pretty confused now...
Guest Phil65 Posted May 12, 2010 Report Posted May 12, 2010 Hi everybody ! I hope you will be able to help me with a strange issue when trying to root using R4 I could execute (on Windows XP) step1-windows.bat and step2-windows.bat without problems. Now I'm blocked at the "Android system recovery" green menu : I cannot move down to the menu items. My Desire seems to be blocked. Nothing happens... I tried using the volume buttons, the power button, ... nothing works. So I cannot execute the "Wipe" and "apply update zip" steps. What am I doing wrong ? How can I solve this issue ? Thanks for your help ! Phil65
Guest RealUnknown Posted May 12, 2010 Report Posted May 12, 2010 I rooted My Desire Succesfully but now i cant copy fonts with RootEXplorer and it told" there was not enough free disk space to complete the paste operation " what can i do ?
Guest Pyr0x64 Posted May 12, 2010 Report Posted May 12, 2010 Hi everybody ! I hope you will be able to help me with a strange issue when trying to root using R4 I could execute (on Windows XP) step1-windows.bat and step2-windows.bat without problems. Now I'm blocked at the "Android system recovery" green menu : I cannot move down to the menu items. My Desire seems to be blocked. Nothing happens... I tried using the volume buttons, the power button, ... nothing works. So I cannot execute the "Wipe" and "apply update zip" steps. What am I doing wrong ? How can I solve this issue ? Thanks for your help ! Phil65 use the optical trackball
Guest Kushan Posted May 12, 2010 Report Posted May 12, 2010 (edited) I'd just like to say that I managed to get r4 to work on Windows 7 64bit. Twice, now. There were some instructions a few pages back and someone posted a modified .bat file that seemed to fix the issue (or rather, FOUND the issue and attempted to fix it) by putting a sleep command after "fastboot-windows.exe oem rebootRUU" in step1.bat. This is perfect, all the problem seems to be is Win7 takes a bit longer to recognise the device, so "sleeping" for a few seconds fixes it, the only problem is the "sleep" command has been removed from windows for a while now, so the modified .bat didn't actually work. If you manually enter the two commands, then it's fine. Anyway, I digress, try this step1.bat for Windows 7 x64 - note, you might need to install HTCSync before it'll work. Note: I'm not taking any credit for this, whoever it was that figured out the delay was all that was wrong deserves the credit, all I did was replace "sleep" with something that would actually work. YMMV.step1_windows.rar Edited May 12, 2010 by Kushan
Guest Phil65 Posted May 12, 2010 Report Posted May 12, 2010 (edited) use the optical trackball Thanks... Edited May 12, 2010 by Phil65
Guest freddy87 Posted May 12, 2010 Report Posted May 12, 2010 i got this message at step 1 - maybe any1 could help me :) ;) ? FAILED (remote: 90 hboot pre-update! please flush image again immediately) sending 'zip' (137446 KB)... FAILED (command write failed (No such file or direc tory)) Rebooting to bootloader... rebooting into bootloader... FAILED (command write failed (No such file or direc tory)) Step 1 complete - now use the bootloader menu to enter recovery mode. To do this, press the power button, wait a few seconds, then use the volume keys and power button to select the RECOVERY option. D:\Downloads\desire root\r4-desire-root>
Guest 42turkeys Posted May 12, 2010 Report Posted May 12, 2010 (edited) i got this message at step 1 - maybe any1 could help me :) ;) ? FAILED (remote: 90 hboot pre-update! please flush image again immediately) sending 'zip' (137446 KB)... FAILED (command write failed (No such file or direc tory)) Rebooting to bootloader... rebooting into bootloader... FAILED (command write failed (No such file or direc tory)) Step 1 complete - now use the bootloader menu to enter recovery mode. To do this, press the power button, wait a few seconds, then use the volume keys and power button to select the RECOVERY option. D:\Downloads\desire root\r4-desire-root> This seems to be that it can't see the files. Try using the r3 TinyCoreLinux method and see if that helps as some strange things happen with Windows. Edited May 12, 2010 by 42turkeys
Guest freddy87 Posted May 12, 2010 Report Posted May 12, 2010 thx - it works now for me with the windows batch file using command "pause" and wait 20seconds then press a key (instead of choice) thanks
Guest mortazavi Posted May 13, 2010 Report Posted May 13, 2010 My bootloader version is 0.75 and my ROM ver is 1.15 and I have rooted my Desire with r3 method, Can I root again my device with new method (r4) for installing ROM Ver 1.21? What is differences between these two ROM ver?
Guest burst Posted May 13, 2010 Report Posted May 13, 2010 My bootloader version is 0.75 and my ROM ver is 1.15 and I have rooted my Desire with r3 method, Can I root again my device with new method (r4) for installing ROM Ver 1.21? What is differences between these two ROM ver? use the MCR Kitchen Roms to get they are all based of 1.21
Guest ElDiablo77 Posted May 13, 2010 Report Posted May 13, 2010 @ 42turkeys, thanx for help m8 but it kept failing so I did it a different way. Now got a rooted desire by using the recover windows through batch file method which worked fine 1st time. Downloaded MCR through kitchen & sitting on my parted SD card 4 later on but just now gonna make sure everything is working before I go jumping ahead. Well done to all those who help out on here. Thanx again.
Guest Posted May 13, 2010 Report Posted May 13, 2010 Hello! I have questions :) (sorry I am a lil bit noob about rooting it will be the 1st time) If I want to make a goldcard, where should I have to unzip the SDK? Do I have to unzip it to the SD card? Where can I read the version of Desire's bootloader and current rom? I am looking forward to having answers ;) Best Regards from Hungary!
Guest Julian1984 Posted May 13, 2010 Report Posted May 13, 2010 Should I upgrade ext3 to ext4? Thanks!!
Guest mrtran Posted May 13, 2010 Report Posted May 13, 2010 (edited) Desire Root Step 1 Erasing cache and rebooting in RUU mode... erasing 'cache'... OKAY ... OKAY About to start flash... < waiting for device > sending 'zip' (137446 KB)... OKAY writing 'zip'... INFOadopting the signature contained in this image... INFOsignature checking... INFOzip header checking... INFOzip info parsing... INFOchecking model ID... INFOchecking custom ID... FAILED (remote: 42 custom id check fail) sending 'zip' (137446 KB)... OKAY writing 'zip'... INFOadopting the signature contained in this image... INFOsignature checking... INFOzip header checking... INFOzip info parsing... INFOchecking model ID... INFOchecking custom ID... FAILED (remote: 42 custom id check fail) Desire Root Step 1 Erasing cache and rebooting in RUU mode... erasing 'cache'... OKAY ... OKAY About to start flash... < waiting for device > sending 'zip' (137446 KB)... OKAY writing 'zip'... INFOadopting the signature contained in this image... INFOsignature checking... INFOzip header checking... INFOzip info parsing... INFOchecking model ID... INFOchecking custom ID... INFOchecking main version... INFOstart image[hboot] unzipping for pre-update check... INFOstart image[hboot] flushing... INFO[RUU]WP,hboot,0 INFO[RUU]WP,hboot,100 INFOstart image[radio] unzipping for pre-update... INFOstart image[radio] flushing... INFO[RUU]WP,radio,0 INFO[RUU]WP,radio,6 INFO[RUU]WP,radio,14 INFO[RUU]WP,radio,19 INFO[RUU]WP,radio,27 INFO[RUU]WP,radio,36 INFO[RUU]WP,radio,44 INFO[RUU]WP,radio,51 INFO[RUU]WP,radio,59 INFO[RUU]WP,radio,100 FAILED (remote: 90 hboot pre-update! please flush image again immediately) sending 'zip' (137446 KB)... FAILED (command write failed (No such file or direc tory)) Rebooting to bootloader... < waiting for device > rebooting into bootloader... OKAY Step 1 complete - now use the bootloader menu to enter recovery mode. To do this, press the power button, wait a few seconds, then use the volume keys and power button to select the RECOVERY option. I run step 1 many time. The first I meet the report in code 1 and now I have report in code 2. After step 1, I run step 2 and not successful. Desire Root Step 2 Pushing required files to device... * daemon not running. starting it now on port 5037 * * daemon started successfully * error: device not found adb server is out of date. killing... ADB server didn't ACK * failed to start daemon * error: Pushing update file to device sdcard - this may take a few minutes... adb server is out of date. killing... * daemon started successfully * error: device not found adb server is out of date. killing... ADB server didn't ACK * failed to start daemon * error: Now wipe and apply rootedupdate.zip from the recovery image menu. adb server is out of date. killing... ADB server didn't ACK * failed to start daemon * error: Can any body help me??? Edited May 13, 2010 by mrtran
Guest Julian1984 Posted May 13, 2010 Report Posted May 13, 2010 Desire Root Step 1 Erasing cache and rebooting in RUU mode... erasing 'cache'... OKAY ... OKAY About to start flash... < waiting for device > sending 'zip' (137446 KB)... OKAY writing 'zip'... INFOadopting the signature contained in this image... INFOsignature checking... INFOzip header checking... INFOzip info parsing... INFOchecking model ID... INFOchecking custom ID... FAILED (remote: 42 custom id check fail) sending 'zip' (137446 KB)... OKAY writing 'zip'... INFOadopting the signature contained in this image... INFOsignature checking... INFOzip header checking... INFOzip info parsing... INFOchecking model ID... INFOchecking custom ID... FAILED (remote: 42 custom id check fail) Desire Root Step 1 Erasing cache and rebooting in RUU mode... erasing 'cache'... OKAY ... OKAY About to start flash... < waiting for device > sending 'zip' (137446 KB)... OKAY writing 'zip'... INFOadopting the signature contained in this image... INFOsignature checking... INFOzip header checking... INFOzip info parsing... INFOchecking model ID... INFOchecking custom ID... INFOchecking main version... INFOstart image[hboot] unzipping for pre-update check... INFOstart image[hboot] flushing... INFO[RUU]WP,hboot,0 INFO[RUU]WP,hboot,100 INFOstart image[radio] unzipping for pre-update... INFOstart image[radio] flushing... INFO[RUU]WP,radio,0 INFO[RUU]WP,radio,6 INFO[RUU]WP,radio,14 INFO[RUU]WP,radio,19 INFO[RUU]WP,radio,27 INFO[RUU]WP,radio,36 INFO[RUU]WP,radio,44 INFO[RUU]WP,radio,51 INFO[RUU]WP,radio,59 INFO[RUU]WP,radio,100 FAILED (remote: 90 hboot pre-update! please flush image again immediately) sending 'zip' (137446 KB)... FAILED (command write failed (No such file or direc tory)) Rebooting to bootloader... < waiting for device > rebooting into bootloader... OKAY Step 1 complete - now use the bootloader menu to enter recovery mode. To do this, press the power button, wait a few seconds, then use the volume keys and power button to select the RECOVERY option. I run step 1 many time. The first I meet the report in code 1 and now I have report in code 2. After step 1, I run step 2 and not successful. Desire Root Step 2 Pushing required files to device... * daemon not running. starting it now on port 5037 * * daemon started successfully * error: device not found adb server is out of date. killing... ADB server didn't ACK * failed to start daemon * error: Pushing update file to device sdcard - this may take a few minutes... adb server is out of date. killing... * daemon started successfully * error: device not found adb server is out of date. killing... ADB server didn't ACK * failed to start daemon * error: Now wipe and apply rootedupdate.zip from the recovery image menu. adb server is out of date. killing... ADB server didn't ACK * failed to start daemon * error: Can any body help me??? Try in a non x64 bits computer... (I got the same error and that works...)
Guest Sandman83 Posted May 13, 2010 Report Posted May 13, 2010 Hi to all. I have succeeded to root the device yesterday. I want to thank to everyone who helped me in this. I had problems with drivers.
Guest bossbodo Posted May 13, 2010 Report Posted May 13, 2010 hail! I have a problem ... I made the wrong root. Version 0.75 hboot I was then I made the root with hboot 0.80. you can go back to 0.75? :)
Guest andy76q Posted May 13, 2010 Report Posted May 13, 2010 i'm in real panic.. My phone is rooted and i've flash the device sevral times, so far so good but now just when i wiped it clean and was in usb mode for copying new rom to sd card, then something happend and the recovery screen froze so i rebooted and tried a new recovery but now it cant find the device. Tried the ./step1-linux.sh and there everthing works fine, but when trying step2 or the recovery and it just says cant find device.. I have linux 32bit and everthing has worked so far. Is it bricked?
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now