Hi alll,
I have a rooted (i think) HTC Legend. I have completed step 1 of the root but had errors with step 2. Now I want to install clockwork rom manager so I can install azure.
But when i download azure using the rom manager app (and after flashing clockwork) it asks me to press OK for a reboot but nothing happens. I have also checked the recovery that I have and it is the one installed as part of the root.
I have tried downgrading the recovery to an older clockwork version, which works and then I installed the latest clockwork again, but i still have the recovery from the step 1 root.
How do i get clockwork recovery installed?
You mentioned errors with step 2.
Did you stick a freshly formatted SD into phone instead of goldcard??
Sent from my Legend
did you downgrade before rooting?
Check your root.
Install a terminal emulator from the Market, if you don't already have one.
Fire it up, type su. If you don't get an error about permissions, then you should have root.
E.E.
chances are, if it did not reboot your system, your not rooted...
Hi all,
Seems if I am having nearly the same problem. The Clockwork Recovery is always freezing when I try to install. So I downloaded the Terminal Emulator from the Market, but when I try to run: "Applikation Terminal Emu (Process com.android.term) has been closed unexpected. Please try again."
SuperUser Permission Reuest also doesn't work, there is happening just nothing when I try to start. Btw thats the same headline what I am having when freezing while installing clockwork recovery.
What went wrong while rooting? Can someone help please
I had some Problems with step2 btw .. because my Legend is the only hardware to get access to the SD Card. So i restarted the phone between step1 and step2, used it as harddrive just to format the SD Card agaein. The I jumped back and started and finished step2 just fine (thats what I thought )
Related
1. I had a rooted phone with CyanogenMod 4.1.9999
2. I downloaded Original System Image (signed-dream_devphone_userdebug-img-14721.zip) from http://developer.htc.com/adp.html
3. I updated the phone with the zip file
Now I'm getting an exclamation screen when I try to get into recovery scree (Pressing Home button during boot)
I tried to downgraded using RC29 Image: http://android-roms.googlecode.com/files/DREAIMG-RC29.zip - Followed first 6 steps from http://forums.tmonews.com/index.php?topic=8970.0
I'm not able to update or do anything with the phone now.
PLEASE HELP!!!!
my guess would 2 be push alt+l and a list of options will come up! Also dont use the system image from htc.com use the recovery image 2 go back 2 whatever version you want it 2... make sure u wipe before you downgrade/upgrade
please move
sorry to be the one to point this out...but please ask these questions in the q&a section as it is not development related
garok89 said:
sorry to be the one to point this out...but please ask these questions in the q&a section as it is not development related
Click to expand...
Click to collapse
I'm sorry for posting it here. I'm not able to move it to Q&A section. If there is an option, please let me know how.
law_ren_ce said:
my guess would 2 be push alt+l and a list of options will come up! Also dont use the system image from htc.com use the recovery image 2 go back 2 whatever version you want it 2... make sure u wipe before you downgrade/upgrade
Click to expand...
Click to collapse
Thanks law_ren.
I get 3 options when i press Alt+L
1. Alt+L Toggle log text display
2. Alt+S apply sdcard:update.zip
3. Alt+W Wipe Data/factory reset
I renamed the android 1.6 system image to update.zip
[snap]
Verifying update package...
E:No signature (5 Files)
E:Verification failed
hifake said:
Thanks law_ren.
I get 3 options when i press Alt+L
1. Alt+L Toggle log text display
2. Alt+S apply sdcard:update.zip
3. Alt+W Wipe Data/factory reset
I renamed the android 1.6 system image to update.zip
[snap]
Verifying update package...
E:No signature (5 Files)
E:Verification failed
Click to expand...
Click to collapse
The same happens with recovery image signed-dream_devphone_userdebug-ota-14721.zip
I say flash another recovery.img via fastboot.
Hi I have a problem like you....my G1 load only in recovery mode(Hold power=recovery, hold home+power=recovery, camera+power=recovery)
Did you fix your G1??? Please help me fix it
EvGeNN2007 said:
Hi I have a problem like you....my G1 load only in recovery mode(Hold power=recovery, hold home+power=recovery, camera+power=recovery)
Did you fix your G1??? Please help me fix it
Click to expand...
Click to collapse
I haven't fixed it yet. Am not able to place the recovery image using fastboot - my phone is not recognized by the computer
Work around I've found for flashing the recovery image if you can't figure out fastboot (I've never got it to work) is like this:
1. Follow the root procedure.
2. Install the most recent CM rom without using the HTC image (reason I do this is he's got some linux commands built into his ROM that aren't installed in the vanilla android build).
3. Download the cm-recovery-1.4.img to your sd card (or whichever recovery image you like)
4. Run terminal commands like so:
$su root (the reason I do this is it gives you higher level access to the system than just su, and I've found it doesn't work with just su for some reason)
#flash recovery /sdcard/cm-recovery-1.4.img
#reboot
5. Hold your home key as it powers up, and you should have the new recovery image installed.
Of course, I'd say do a full wipe, then install the ROM, and go through the fix permissions and clear cache.
JonnyFlash said:
Work around I've found for flashing the recovery image if you can't figure out fastboot (I've never got it to work) is like this:
1. Follow the root procedure.
2. Install the most recent CM rom without using the HTC image (reason I do this is he's got some linux commands built into his ROM that aren't installed in the vanilla android build).
3. Download the cm-recovery-1.4.img to your sd card (or whichever recovery image you like)
4. Run terminal commands like so:
$su root (the reason I do this is it gives you higher level access to the system than just su, and I've found it doesn't work with just su for some reason)
#flash recovery /sdcard/cm-recovery-1.4.img
#reboot
5. Hold your home key as it powers up, and you should have the new recovery image installed.
Of course, I'd say do a full wipe, then install the ROM, and go through the fix permissions and clear cache.
Click to expand...
Click to collapse
Am not even able to access terminal. I get the following 3 options only
1. Alt+L Toggle log text display
2. Alt+S apply sdcard:update.zip
3. Alt+W Wipe Data/factory reset
hifake said:
Am not even able to access terminal. I get the following 3 options only
1. Alt+L Toggle log text display
2. Alt+S apply sdcard:update.zip
3. Alt+W Wipe Data/factory reset
Click to expand...
Click to collapse
You won't be able to use terminal from recovery until you have a thirdparty recovery image installed. The steps I've listed are for a working phone, and I'm sure that's where part of your problem is. I'd suggest doing a wipe (Alt+W) and going through the root process again. When you get the CM Rom, change the name of it to update.zip, then try the steps I mentioned. I'd suggest having a separate SD card with just DREAMIMG.nbh installed on it for emergencies (especially if you're going to partition your main card).
Thanks
2) Install the most recent CM rom without using the HTC image(What is it? Can explane?)
4) Terminal as i understand its Telnet?
Can i do works a boot mode and then downgrade it to RC29?? Because after it i'll know what to do... Thanks!
EvGeNN2007 said:
Thanks
2) Install the most recent CM rom without using the HTC image(What is it? Can explane?)
4) Terminal as i understand its Telnet?
Can i do works a boot mode and then downgrade it to RC29?? Because after it i'll know what to do... Thanks!
Click to expand...
Click to collapse
Basically to get this working you're going to need to downgrade to RC29 first - so follow the root instructions.
CM = CyanogenMod ROM. To get his working fully you need two roms, which are the HTC Developer ROM and the 4.x ROMs he created (reason being legal distribution of software), but for my instructions, on his ROM page, you're going to skip his instructions, just download his ROM, rename it to update.zip and just flash it from the stock recovery, just so you can get to the terminal once the phone boots up and load terminal (it's in the programs tray). When another screen pops up asking if you want to allow it to use SU functions (it will as soon as you type "su") hit allow.
Terminal is a program downloadable from the Market, it's included with the CM ROM.
His instructions for install are not going to work unless you have a thirdparty recovery image, which at this point from the description, the triangle with the exclamation point is the default system recovery image.
CM Rom page
You should be able to find the Root posts and choose a customed recovery image, there's about 4 or 5 really good ones, I use Cyanogen's, thus my instructions on how to flash it.
You're fortunate that you're getting to the stock recovery, means your phone isn't bricked.
JonnyFlash said:
You won't be able to use terminal from recovery until you have a thirdparty recovery image installed. The steps I've listed are for a working phone, and I'm sure that's where part of your problem is. I'd suggest doing a wipe (Alt+W) and going through the root process again. When you get the CM Rom, change the name of it to update.zip, then try the steps I mentioned. I'd suggest having a separate SD card with just DREAMIMG.nbh installed on it for emergencies (especially if you're going to partition your main card).
Click to expand...
Click to collapse
I have successfully installed RC 29
FW 1.0
Baseband 62.33.20.08H_1.22.12.29
Kernel: 2.6.25-01843-gfea26b0
Build: kila-user 1.0 TC4-RC29 115247
But Am not able to download telnet (or any other app) from market. I have tried several times with wifi & Cell data .
hifake said:
I have successfully installed RC 29
FW 1.0
Baseband 62.33.20.08H_1.22.12.29
Kernel: 2.6.25-01843-gfea26b0
Build: kila-user 1.0 TC4-RC29 115247
But Am not able to download telnet (or any other app) from market. I have tried several times with wifi & Cell data .
Click to expand...
Click to collapse
Not sure what you mean? Telnet for these intents and purposes is basically just a command. The page on how to root has become pretty convoluted at this point. The part where it tells you to type 'telnetd' is just running a script which is an exploit in the old releases of android. You won't be messing with Terminal really until you get to the point where you've updated the rom. From this point, I'd suggest downloading this root.apk from your browser, install it, allow it, follow the instructions step by step in the program.
My problem consist of that i can't turn on my phone and i can't get into bootloader...only recovery can you give me a link for RC29 download and then install it from recovery on my g1 from recovery.
Thanks!
EvGeNN2007 said:
My problem consist of that i can't turn on my phone and i can't get into bootloader...only recovery can you give me a link for RC29 download and then install it on my g1 from recovery.
Thanks!
Click to expand...
Click to collapse
You're probably going to need a card reader...here's the instruction for rooting with a download for the RC29.
http://forum.xda-developers.com/showthread.php?t=442480
I know all this steps but i Tell that i CAN'T get into boot mode and in boot downgrade from DREAMIMG.nbh to RC29... In that All my problem...
How can i flash to RC29 from Recovery Mode?
EvGeNN2007 said:
I know all this steps but i Tell that i CAN'T get into boot mode and in boot downgrade from DREAMIMG.nbh to RC29... In that All my problem...
How can i flash to RC29 from Recovery Mode?
Click to expand...
Click to collapse
You don't...with the DREAMIMG.nbh or any .nbh file you start up the phone holding power+camera. The recovery mode looks for an update.img file. You'll make it through, don't get frustrated.
Here's a more updated rooting guide:
http://forum.xda-developers.com/showthread.php?t=553416
Hello all,
I'm having a problem with the stock recovery. I have tried installing G.O.T. Open Recovery 2.01 and the install is OK, and I can do stuff in the menus, but every time I reboot, the stock recovery comes back. I followed the instructions by nadlabak on how to remove the script that reinstalls the stock recovery (android.doshaska.net/rootable, sorry the forum isn't allowing me to post the actual link as I'm a new user), but it doesn't work. There is no error message, just nothing happens. Can someone help? Thanks.
Xenobio said:
Hello all,
I'm having a problem with the stock recovery. I have tried installing G.O.T. Open Recovery 2.01 and the install is OK, and I can do stuff in the menus, but every time I reboot, the stock recovery comes back. I followed the instructions by nadlabak on how to remove the script that reinstalls the stock recovery (android.doshaska.net/rootable, sorry the forum isn't allowing me to post the actual link as I'm a new user), but it doesn't work. There is no error message, just nothing happens. Can someone help? Thanks.
Click to expand...
Click to collapse
Can you describe in detail what you did?
Method 1: command line
1. Booted into recovery
2. Installed GOT Open Recovery
3. Immediately after that (without rebooting, as it would have caused the stock recovery to be reinstalled) went into console and typed "rm -f /system/etc/install-recovery.sh"
4. Nothing happens, the command line # symbol just appears on the next line
5. Went back to main menu and rebooted, stock recovery came back
Method 2: script
1. Downloaded the "Disable_recovery_check_by_OTA.zip" file from the page mentioned previously
2. Unzipped and copied the .sh file to my sdcard in the OpenRecovery scripts folder
3. Step 1 and 2 like above
4. Went to the "Miscellaneous > Run script" menu
5. Ran "Disable_recovery_check_by_OTA.sh"
6. It says "-- Shell script..." then the path and filename of the script, then it says "Done" on the next line
7. Went back to main menu and rebooted, stock recovery came back
I also tried something after removing the install-recovery.sh...if I reboot into recovery (press and hold X immediately after selecting "Reboot" from the GOT main menu), I get Open Recovery back. But, if I reboot into Android and then turn it off and then boot into recovery, it's the stock recovery.
But every time you can use openrecovery right? If so, that's normal behavior. We can't replace recovery.
did you try to put the script into the init folder? I'm not sure anymore if its that one, but one of these folders contains a bunch of script that will be executed on boot up.. it worked for me (once) before i bricked my phone.. lol
Xenobio said:
Hello all,
I'm having a problem with the stock recovery. I have tried installing G.O.T. Open Recovery 2.01 and the install is OK, and I can do stuff in the menus, but every time I reboot, the stock recovery comes back. I followed the instructions by nadlabak on how to remove the script that reinstalls the stock recovery (android.doshaska.net/rootable, sorry the forum isn't allowing me to post the actual link as I'm a new user), but it doesn't work. There is no error message, just nothing happens. Can someone help? Thanks.
Click to expand...
Click to collapse
I am sure there is a way. OpenRecovery from G.O.T is slightly differrent, try to use the one from nadlabak and see what happens....?
Sorry guys, I have searched through, tried all possible things... but cannot get things working... here's my story (long, but gives the whole picture)
1. Was on CM 6.0 (stable) and Amon RA 1.7 recovery
2. Got a new SD card (8gb class 6)
3. Had Nand backups, so just removed the old card and inserted the new
4. Booted into recovery, partitioned SD card, copied CM 6.1.0 RC and gapps onto the SDCard
5. Performed Wipe Data/Factory reset, Wipe cache, Wipe Dalvik-cache and flashed CM 6.1.0 rc and gapps
6. Booted into the ROM, signed into my account, got all my apps from market
7. Everything was running fine
8. Booted into recovery, made a Nand backup and installed Steel my Elegance
9. Booted into the ROM and realized something was not correct, so decided to restore from the Nand backup
10. Booted into recovery and tried to restore - failure, asked me to run nand backup from adb
11. Did that but that did not resolve the situation
12. Performed step #5 (above) again and got it to the original state
13. Did not login into my account, as I wanted to get a backup of a fresh install
14. Booted into recovery made a Nand backup successfully
15. Just to be on the safer side, tried restoring... did not work. Same error - run SH from adb - tried that, but did not work
16. Read somewhere on the forums to wipe cache before backup and try, did that backed up and tried restoring - no go
17. Decided to flash ClockWork recovery - did that through terminal (ROM booting properly)
18. Booted into recovery - successfull
19. Tried creating Nand backup - failed at Cache - cannot image cache error message or something
20. Performed format SD card, cache, system and all other formats available from the recovery (ClockWork mod)
21. Tried performing nand backup - created some folders/files under the clockwork mod folder with junk characters
22. Performed a SD card format from computer (FAT32)
23. Booted into recovery and tried nand backup - no go
24. Decided to revert back to Amon RA 1.7 - flashed through terminal and rebooted into recovery - phone won't go to recovery
25. Though there might be some problem with the img file, so downloaded from multiple locations and tried it - still no go
26. Followed all sorts of instructions - mount/remount, flash_image - no go. When I do flash_image recovery <image name>, the command exits without any errors, but still can't boot into recovery
27. Installed ROM manager and flashed clockworkmod recovery from within, still no go.
28. Performed "Fix permissions" - ended with "Could not run some privileged commands"
29. I can still boot into the ROM and when I go to terminal can do SU - takes me to "#" from "$" - so I am guessing I still have root
It just doesn't add up... and I feel very lost, right now. I guess the only thing remaining to do is go back to 2.1 RUU, reroot and go from there. Is there any other way? Or did I do something wrong?
Can someone please help?
Edit: I had enough battery juice or wall power plugged into the phone while trying the backups and restores...
Do you still have the super user app? Check the permissions in the app, maybe one couldve gotten declined???
go to impalers cyanogen mod q&a, ask there, impaler is really knowlegable and helpful, you should get some concrete help.
I don't think this has anything to do with CM, else would have posted there.
Thanks anyways.
cordell12 said:
Do you still have the super user app? Check the permissions in the app, maybe one couldve gotten declined???
Click to expand...
Click to collapse
Checked that, everything that needs access seems to have it.
Any other ideas? I am so close to going RUU route......
Maybe this can help? I dont know never had this happen?
http://forum.xda-developers.com/showthread.php?t=845069
Thanks everyone... I ended up going the RUU way. Got my recovery back, backup/restore and CM6.1.0 RC up & running. Loooonnnnggg night .
andythegreenguy said:
Thanks everyone... I ended up going the RUU way. Got my recovery back, backup/restore and CM6.1.0 RC up & running. Loooonnnnggg night .
Click to expand...
Click to collapse
I hate that you had to go that route, but atleast all is well now. It couldve been worse and not even let you RUU Thats a Scary thought!
cordell12 said:
I hate that you had to go that route, but atleast all is well now. It couldve been worse and not even let you RUU Thats a Scary thought!
Click to expand...
Click to collapse
No kidding... . It was so frustrating, just going through it all.
Originally, I had rooted my phone that had 2.31.651.7 on it. So, I applied that RUU and went through the root. It seemed to have rooted fine, but then it won't allow me to flash recovery - did the same steps as I had performed during my first rooting process, but didn't work. Then went through all possible ideas suggested on the forums... still no luck. So, finally put the 2.27.651.5 RUU, followed regaw_leinad's rooting method and everything worked out.
All-in-all a good learning experience .
BTW, for anyone that is reading, I think the issue was a corrupted SD card. I might have pulled it while the phone was running and then applied a corrupted recovery image.
I've read the guides, tried manual and the simple download from the Android Market. Here's what happens:
I've rooted my Thrill with SuperOneClick 2.1.1. It was a successful root from what I can tell, it added Superuser into my apps, and I was able to download Rom Manager from the Android Market.
If I try using Rom Manager and click "Flash ClockworkMod Recovery" It appears to install. But when I hit "Reboot into Recovery" it just reboots like normal.
If I try to manually get into recovery mode by holding volume down and the 3D button it just boots into the stock recovery mode.
When I try to manually install Clockwork and copy recovery.img to /data with cmd I get this:
failed to copy recovery.img permission denied
Click to expand...
Click to collapse
Thanks for any help, I'm hoping it's just a small little step I missed.
mikeeey said:
I've read the guides, tried manual and the simple download from the Android Market. Here's what happens:
I've rooted my Thrill with SuperOneClick 2.1.1. It was a successful root from what I can tell, it added Superuser into my apps, and I was able to download Rom Manager from the Android Market.
If I try using Rom Manager and click "Flash ClockworkMod Recovery" It appears to install. But when I hit "Reboot into Recovery" it just reboots like normal.
If I try to manually get into recovery mode by holding volume down and the 3D button it just boots into the stock recovery mode.
When I try to manually install Clockwork and copy recovery.img to /data with cmd I get this:
Thanks for any help, I'm hoping it's just a small little step I missed.
Click to expand...
Click to collapse
This is covered in the cwm thread in development section you need to use a file explorer that has root access and change permissions to the /data folder. You can use es file explorer, its free. Open it go into settings then browse as root... not really sure exact steps but they are in the came thread.
O my such a small step I missed! Thank you! Ill try this later today.
Permissions of /data are set to R/W but I still get the same error..
I'm starting to wonder if the cause of this is because I tried using Rom Manager to flash clockwork, THEN tried the adb method. Maybe it already being there is causing the permission denied?
edit: so it looks like it was as simple as me looking over the permissions and thinking I saw everything was checked, but really the two checks from the left under "other" were grayed out lol, checking those fixed it.
I just updated to V20 and didn't realize it wiped out everything. Now I can't get CWM on my phone. When I try to push the recovery.img, I get permission denied. Is there a new way of installing cwm with GB or am I doing something wrong.
You can use ROM Manager to install it. You will just have to select Optimus 3D as the phone. I used this method and it worked perfectly.
If you are using Terminal Emulator to get CWM on your phone make sure the su is lower case. I had to turn off auto caps on mine.