Related
So as many of you are now finding out is that clockwork is borked and so is root with the new update. The root method on cyanogenmod wont work. The rootboot.img breaks wifi and you still cannot get into clockwork recovery ... well at least I can't. Anyone else seeing this and possibly have a solution?
zeiroe said:
So as many of you are now finding out is that clockwork is borked and so is root with the new update. The root method on cyanogenmod wont work. The rootboot.img breaks wifi and you still cannot get into clockwork recovery ... well at least I can't. Anyone else seeing this and possibly have a solution?
Click to expand...
Click to collapse
ya the OTA breaks root and CWM,,,thats why in roms the ability to OTA is removed
Reflash koush's clockwork recovery via fastboot.
After the successful flash, you can get into CWM recovery by selecting Recovery while still in fastboot.
Once in CWM, go to mount options menu and mount /system.
Then use adb shell to navigate to /system/bin.
Once in /system/bin type chmod 6775 su
Root functionality should now be restored when you're in normal boot mode.
Getting permanent CWM recovery back is proving more problematic for me. Once you reboot the phone after that first install, selecting Recovery gives you the Android and "!" screen. Battery pull required.
You can however, get back into CWM recovery by either fastboot flashing the image again as above, or from the ROM Manager app where you flash the recovery and then select boot into recovery.
Pain in the butt, but not totally lost.
Just a minor issue that comes from running custom recoveries and roms. Koush already is working on a flashable update that will work with CWR. Just gotta be patient. Chances are that if you have been keeping up with the tweaks and new apk's in the dev forum, this update won't really mean that much anyway. I am a sucker for wanting the latest version number in my "about phone" though
distortedloop said:
Reflash koush's clockwork recovery via fastboot.
After the successful flash, you can get into CWM recovery by selecting Recovery while still in fastboot.
Once in CWM, go to mount options menu and mount /system.
Then use adb shell to navigate to /system/bin.
Once in /system/bin type chmod 6775 su
Root functionality should now be restored when you're in normal boot mode.
Getting permanent CWM recovery back is proving more problematic for me. Once you reboot the phone after that first install, selecting Recovery gives you the Android and "!" screen. Battery pull required.
You can however, get back into CWM recovery by either fastboot flashing the image again as above, or from the ROM Manager app where you flash the recovery and then select boot into recovery.
Pain in the butt, but not totally lost.
Click to expand...
Click to collapse
Bah im a douche up arrow and didnt read the line and I was flashing the stock boot.img over and over lol ... Thanks
zeiroe said:
Bah im a douche up arrow and didnt read the line and I was flashing the stock boot.img over and over lol ... Thanks
Click to expand...
Click to collapse
LOL, don't you hate when that happens.
Glad it worked out for ya in the end!
I want to flash CM7, but everytime I try flashing Clockwork recovery 3, it ends up staying at 2.5.1.2. What am I doing wrong? I tried flashing it from ROM Manager and that didn't help, and I don't know if I can flash it with the fastboot method since I'm using CWR already. What can I do?
Additional notes: Right now, I'm running CM6 RC2. And my phone looks sexy.
Like you I also came across that issue but trying to install kernel in Ice Glacier. Now what you want to do is install it manually via console. Check my other thread all you need is the flash image and clockworkmod recovery. I myself flashed ClockworkMod 3.0.0.0 as other howoto failed and True's didn't stick.
OptLynx said:
Like you I also came across that issue but trying to install kernel in Ice Glacier. Now what you want to do is install it manually via console. Check my other thread all you need is the flash image and clockworkmod recovery. I myself flashed ClockworkMod 3.0.0.0 as other howoto failed and True's didn't stick.
Click to expand...
Click to collapse
true's method seems to be broken for now, but he has posted that he will be looking into the issue as soon as he get home.
GazaIan said:
I want to flash CM7, but everytime I try flashing Clockwork recovery 3, it ends up staying at 2.5.1.2. What am I doing wrong? I tried flashing it from ROM Manager and that didn't help, and I don't know if I can flash it with the fastboot method since I'm using CWR already. What can I do?
Additional notes: Right now, I'm running CM6 RC2. And my phone looks sexy.
Click to expand...
Click to collapse
Go here,
http://forum.xda-developers.com/showthread.php?t=916930
And hit on the link to download the cwm 3.xxxx
Once the file is downloaded use root explorer, navigate to /sdcard/downloads/ and find the recovery. Make sure that it shows as .img and not as .zip. if it is a zip then unzip to get the .img file
Select the recovery and change the name to some easier name like f.e cwmrec3 (nnow u will have a cwmrec3.img file).
Move it to /sdcard (root) for ease of method
Open terminal emulator and do
Su (enter) (# will change for $)
flash_image recovery /sdcard cwmrec3.img
Wait for it to go to the next line.
Reboot to recovery and ur text will now be orange. You now haz recovery 3.xxxx
Also, note that if u enter rom manager it will still say that you have cwm 2.xxx that does not matter though as long as ur recovery txt is orange and not green
Sent from my rooted glacier running CM7
Flashing via terminal worked, thanks!
GazaIan said:
Flashing via terminal worked, thanks!
Click to expand...
Click to collapse
You are welcome my friend enjoy cm7
Sent from my rooted glacier running CM7
GazaIan said:
I want to flash CM7, but everytime I try flashing Clockwork recovery 3, it ends up staying at 2.5.1.2. What am I doing wrong? I tried flashing it from ROM Manager and that didn't help, and I don't know if I can flash it with the fastboot method since I'm using CWR already. What can I do?
Additional notes: Right now, I'm running CM6 RC2. And my phone looks sexy.
Click to expand...
Click to collapse
the fastboot method will work if you have CWM 3.5.1.3 already. I did that this morning, and it worked like a charm.
so I was able to do the easy cw method installing the zip from recovery then choosing 2.5.1.4, but after a few runs with the latest builds of CM7 i was having major issues with my mobile data connection jumping from H to 3G, each time lagging out my connection and making streaming videos, etc impossible to play. So I reflashed to stock, and my H returned to normal. So i thought I'd give it another shot, rooted, downloaded ROM Manager, flashed to 2.5.1.2 smooth, then tried the above method. When I tried to load the 2.5.1.4 in ROM manager, it said "An error occurred while flashing your recovery." So I tried the terminal, and no matter how I rename the file, and I know I followed the instructions flawlessly, it says flash_image: not found. So while ROM Manager seems completely capable of flashing to the 2.5.1.2 version, nothing seems to work to get me past it. What could I be missing?
darinmc said:
so I was able to do the easy cw method installing the zip from recovery then choosing 2.5.1.4, but after a few runs with the latest builds of CM7 i was having major issues with my mobile data connection jumping from H to 3G, each time lagging out my connection and making streaming videos, etc impossible to play. So I reflashed to stock, and my H returned to normal. So i thought I'd give it another shot, rooted, downloaded ROM Manager, flashed to 2.5.1.2 smooth, then tried the above method. When I tried to load the 2.5.1.4 in ROM manager, it said "An error occurred while flashing your recovery." So I tried the terminal, and no matter how I rename the file, and I know I followed the instructions flawlessly, it says #flash_image not found. So while ROM Manager seems completely capable of flashing to the 2.5.1.2 version, nothing seems to work to get me past it. What could I be missing?
Click to expand...
Click to collapse
Thats because you flashed back to stock and stock roms do not have "flash_image" on /system/bin
Download this
http://db.tt/Rv63e76
Use root explorer and paste it to /system/bin
Try terminal again
Sent from my rooted glacier running CM7
worked like a charm, thanks.
darinmc said:
worked like a charm, thanks.
Click to expand...
Click to collapse
You can hit thanks
glad i could help
Sent from my rooted glacier running CM7
HTC Magic
SAPPHIRE PVT 32B
HBOOT-1-33.006
CPLD-10
RADIO-2.22.19.261
I have problems getting in to the recovery mode (pwr button + home) it just gives me de red vodafone screen and hangs.
I am trying to install a custom rom.
- rooted the device with universal androot. it says my device is rooted succesfully.
- i also installed rom manager and installed the default clockwork recovery.
But i cant reboot into flash recovery.
I also tried another thread with a custem flash recovery recovery-RA-sapphire-v1.7.0G.img. I followed it's instructions.
the instructions tells me on a terminal session or CMD prompt to install this custom ROM.
adb shell
su
(Now look at your device. If the superuser app is asking for permissions, then just push "allow" and make sure that the "remember" option is checked.)
cd /system/bin
ls
But i get no permission. I cant get root user when i type su.
so I must not have a rooted device or my permissions are incorrect on the sd-card.
Does anyone have an idea what i should do?
Did you reboot your phone after running Universal Androot?
Sent from my LG-P500 using Tapatalk
What happens if you switch off the phone and then press and hold home button while pressing the on/of button to switch on the phone.
If you are root and have installed the recovery properly, it should be shown within a few seconds after showing the red vodafon screen. From there you should be able to flash any custom rom. Meanwhile I flashed many recoveries and roms on both my tattoo and my magic 32b. Never had any problem execept those when forgetting to wipe.
And to be honest, I'm far away from beeing an expert!
I installed rom manager first and then universal androot.
also when i use adb from the android sdk i sometimes get the problem that i have no permission.
Could it be that the phone is'nt correctly rooted?
I tried all kinds of tools either on pc or mac. nithing really works
what would be the best way to root the HTC Magic correctly and what recovery image should i use. Also wich order.
I'm quite the noob when it comes to installing custom roms
Try "SuperOneClickv1.6.3-ShortFuse.zip" (available at xda).
This was very easy to use and worked like a charm.
I used it twice on my magic 32b, no problem!
I tried that also.
the rooting works. I tried an app to check if i have root access and it says I have root acces.
but when I use adb commands and su to root it will say no permission.
i think this is why installing the recovery in clockwork fails.
any suggestions?
I'll repeat myself. Have you rebooted the phone after running the root programs? Either one?
yes. I rebooted after each try but still I can't get into recovery mode. it just hangs.
also when i try to install a recovery image file i still get the no permissions errors.
the only recovery mode install that worked was the recovery from clockwork in ROM manager.
If ADB is working, goto shell (adb shell).
What do you see in prompt,
is it '$' or '#'?
If it's '$' try "su".
What is the output of "id"?
If you're root you should see something like "uid=0(root) gid=0(root)"
I See a $ and my id is shell instead of root.
if I type su it will give me a no permission error.
however I did download a terminal tool for android
from there I can su and it will make me root.
is there anyway i can use the terminal to install a recovery image so that if i boot my phone with home+power I will get into the recovery?
Try something like this:
http://forum.xda-developers.com/showpost.php?p=4056530&postcount=6
Replace the recovery image in the post by for example recovery-RA-sapphire-v1.7.0G.img.
I did it almost the same way.
I was also having a recovery problem (Tmobile) after trying to flash_image RA-1.7.0G into recovery in rooted 2.2.1 OTA (obviously not the way to go). I downloaded the Clockwork Rom Manager from the Market and it was able to flash both Clockwork or Amon RA recovery with no problem and then reboot it into recovery.
sickbox said:
I was also having a recovery problem (Tmobile) after trying to flash_image RA-1.7.0G into recovery in rooted 2.2.1 OTA (obviously not the way to go). I downloaded the Clockwork Rom Manager from the Market and it was able to flash both Clockwork or Amon RA recovery with no problem and then reboot it into recovery.
Click to expand...
Click to collapse
When you reboot and go into recovery, does it load amon_RA or clockworkmod?
I had problems with that from the 2.2.1 OTA.
I was rooted for a long time, and then had to try the t-mo 2.2.1 so I unrooted and ran that for a while after their ota update. It was sluggish and I didn't much like it so I thought I would try using z4root and superoneclick to root it and put setcpu and overclock it a bit to see if it improved. Z4root didn 't work and superoneclick appeared to work. If you went into terminal it would give you # and seem to be rooted. I could install and run set cpu and it would work. However no matter what recovery I tried to install, it would disappear and return to stock recovery upon reboot with the 2.2.1 OTA.
You could get rom manager to load, or seemingly so , clockworkmod recovery. You could also have rom manager load into clockworkmod from within rom manager. Buit as soon as you reboot, it goes back to the default stock recovery.
I eventually gave up with that and decided to reroot old school and rooted it manuallyl. I went back to the sappimg.nbh file, installing the old cyanogen 1.4 recovery, the 1.33.2005 SPL. I then put clockwork mod 2.5.0.7 recovery on and then the t-mo 2.22.23.02. I was running cm6.1 for a while and now Yoshi's ginger rom.
And so, after this wandering tale, lol, I am wondering if you had more success that I did with the 2.2.1 and getting a recovery to load.
cyberstoic said:
When you reboot and go into recovery, does it load amon_RA or clockworkmod?
I had problems with that from the 2.2.1 OTA.
I was rooted for a long time, and then had to try the t-mo 2.2.1 so I unrooted and ran that for a while after their ota update. It was sluggish and I didn't much like it so I thought I would try using z4root and superoneclick to root it and put setcpu and overclock it a bit to see if it improved. Z4root didn 't work and superoneclick appeared to work. If you went into terminal it would give you # and seem to be rooted. I could install and run set cpu and it would work. However no matter what recovery I tried to install, it would disappear and return to stock recovery upon reboot with the 2.2.1 OTA.
You could get rom manager to load, or seemingly so , clockworkmod recovery. You could also have rom manager load into clockworkmod from within rom manager. Buit as soon as you reboot, it goes back to the default stock recovery.
I eventually gave up with that and decided to reroot old school and rooted it manuallyl. I went back to the sappimg.nbh file, installing the old cyanogen 1.4 recovery, the 1.33.2005 SPL. I then put clockwork mod 2.5.0.7 recovery on and then the t-mo 2.22.23.02. I was running cm6.1 for a while and now Yoshi's ginger rom.
And so, after this wandering tale, lol, I am wondering if you had more success that I did with the 2.2.1 and getting a recovery to load.
Click to expand...
Click to collapse
You could have just got booted into recovery once, flashed the engineering SPL only (there's a ZIP you can flash from recovery to do this), which would only change the SPL, from recovery, then erase/reflash the recovery from fastboot, and finally change the SPL back.
DonJuan692006 said:
You could have just got booted into recovery once, flashed the engineering SPL only (there's a ZIP you can flash from recovery to do this), which would only change the SPL, from recovery, then erase/reflash the recovery from fastboot, and finally change the SPL back.
Click to expand...
Click to collapse
Thanks; that is very useful , and I didn't even think of that at the time. I think I was so frustrated that the recovery would not stay I just had a "I will make it work moment" and I knew what I was doing would work.
But thanks, I will definitely remember that if I have to do that again
Just here to help ;D
Sent from my LG-P500 using Tapatalk
Hi i have a MyTouch 4G rooted with Virtuous Fusion ROM. Everything was working until when I tried to install Miui Music Player on it. I did adb push but after doing it when i unplugged the phone from my computer several Force Close came up then i rebooted my phone then the MYTOUCH Tmobile logo start up screen came then the HTC logo came then my phone will shut down. I tried to start my phone again the same thing happen. I did Hboot and tried recovery from there but it didnt work. I tried Factory Reset but it failed. I go to clockwork recovery mode if i do backup and restore or factory reset nothing happens. Does it mean my phone is gone? Is there anything i can do to fix it? Please anybody help
Try going into recovery again and just reflash fusion again.
coupetastic-droid said:
Try going into recovery again and just reflash fusion again.
Click to expand...
Click to collapse
I tried doing that i booted to clockwork recovery then on the menu any button i click like install from zip, backup and restore and so on. After i click it nothing happens its like clockwork recovery is not working. Does this mean my Phone is BRICK. I cannot fix it anymore
pching999 said:
I tried doing that i booted to clockwork recovery then on the menu any button i click like install from zip, backup and restore and so on. After i click it nothing happens its like clockwork recovery is not working. Does this mean my Phone is BRICK. I cannot fix it anymore
Click to expand...
Click to collapse
Im kind of a noob but did you reflashing cwm via adb? Do some research first though.
Also I think there is a trick to flash an older cwm via adb and then flash an older romm that needs cwm 2.xxx but I could be wrong
tjlawson09 said:
Im kind of a noob but did you reflashing cwm via adb? Do some research first though.
Also I think there is a trick to flash an older cwm via adb and then flash an older romm that needs cwm 2.xxx but I could be wrong
Click to expand...
Click to collapse
NO how do i reflash Clock work MOD through adb? Can you give me the steps to do it. I could try if it will work
pching999 said:
NO how do i reflash Clock work MOD through adb? Can you give me the steps to do it. I could try if it will work
Click to expand...
Click to collapse
Download a new copy of CWM from here. Rename the file "recovery.img" and put it in the root of your SD card. Then start ADB and enter:
Code:
adb flash_image recovery /sdcard/recovery.img
TeeJay3800 said:
Download a new copy of CWM from here. Rename the file "recovery.img" and put it in the root of your SD card. Then start ADB and enter:
Code:
adb flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
when i use the track pad it worked but what should i do next do i have to do a back up and restore or reflash the custom rom
pching999 said:
when i use the track pad it worked but what should i do next do i have to do a back up and restore or reflash the custom rom
Click to expand...
Click to collapse
See my post in your other thread. It sounds like your recovery is fine, so all you need to do is wipe and re-flash.
TeeJay3800 said:
See my post in your other thread. It sounds like your recovery is fine, so all you need to do is wipe and re-flash.
Click to expand...
Click to collapse
Hi im having problem with data connection 3G/4G (H) before i was getting H most of the time but now its 3G most of the time. Can you help me how to fix this. Also do you know what version of Miui Music Player is best for Mytouch 4G running on Virtuous Fusion ROM. I like the one with graphic equalizer when playing songs. Can you suggest something and how to install it
Thanks
this morning was dead at work, so i decided to go ahead and tinker with my phone. i was on 1.8.3, rooted, and running gingerblur 4.5.
i followed the instructions for the bootloader and root, everything went smoothly updating to 2.3.4 at first, but it doesnt seem to hold root. superuser kept corrupting, then when i got that settled, CWM started hanging up, and now when i try to use that, i get an error saying the path is null. aaaand now superuser says my su binaries are out of date. anyone have any idea? i tried searching, but couldnt find anything relative to my problem...
EDIT: super user is jacked up again.. so basicly my phone wont hold root...
EDIT 2: my home key doesnt seem to do anything now either...
Sounds like you did a titanium backup restore on your phone? Try doing a factory reset and try re-rooting the rom you have and give it super user access. A factory reset should work.
Sent from my MB860 using XDA App
i didnt do a titanium backup... but i did just try a factory reset, and i think it bricked my phone... i have the little android guy standing next to the yellow triangle with an exclamation point... now what? lol
can you boot into fastboot or Android Recovery?
yes. should i use android recovery, or reflash 2.3.4 or kenn's alien rom?
PParcells said:
yes. should i use android recovery, or reflash 2.3.4 or kenn's alien rom?
Click to expand...
Click to collapse
who's recovery/CWM are you currently using?
i had the latest of tenfars CWM, but like i said, it kept botching since root wouldnt stick
i seem to be able to access the CWM in android recovery mode though. should i try reflashing kenn's alien rom, or start from scratch with 2.3.4?
Try booting into fastboot mode and trying the command: fastboot -w
Then: fastboot reboot
Does it boot up now? Still have some more stuff to tell you.. just wanted to see if that got the phone booted first.
PParcells said:
i seem to be able to access the CWM in android recovery mode though. should i try reflashing kenn's alien rom, or start from scratch with 2.3.4?
Click to expand...
Click to collapse
Yeah, but can you still put flashable .zip files on your phone, if you can't boot?
it booted up just fine, as if the factory reset did nothing. all my apps and stuff are still there, root still isnt working, and neither is the CWM app in the app drawer. so im not sure if i should try re-rooting again, or what to do. this is weird, i never had any issues fiddling with gingerblur or any of that stuff...
PParcells said:
it booted up just fine, as if the factory reset did nothing. all my apps and stuff are still there, root still isnt working, and neither is the CWM app in the app drawer. so im not sure if i should try re-rooting again, or what to do. this is weird, i never had any issues fiddling with gingerblur or any of that stuff...
Click to expand...
Click to collapse
Ok, here we go...
1) Check to see if you have file "install-recovery.sh" @ /system/etc. If you do, delete it.
2) Uninstall Tefnar's CWM you have installed.
3) Download RomRacer's CWM/Recovery, and install via fastboot, or install via ROM Manager via the instructions in my N00B Guide thread.
4) Once you have RomRacer's CWM installed, boot into CWM and wipe dalvik cache, cache partition and format data.
5) Flash Alien ROM (not theme, just ROM). - Make sure to put this on you phone before booting into CWM and clearing everything; want to flash immediately after clearing things listed in step 4.
6) Reboot and see what you have and if everything is working correctly...
rom manager says i need root. which i dont have. i tried installing via fastboot, but couldnt figure it out. i cant remember if im supposed to use the command prompt, or rsdlite, rsdlite says the CWM zip isnt a valid compressed file...
PParcells said:
rom manager says i need root. which i dont have. i tried installing via fastboot, but couldnt figure it out. i cant remember if im supposed to use the command prompt, or rsdlite, rsdlite says the CWM zip isnt a valid compressed file...
Click to expand...
Click to collapse
Need to use command promt for fastboot... put RomRacer's CWM .img file in the same place as your fastboot files, and then type the commands in Rom Racer's OP, except if your using fastboot, you can ignore the "moto" part of the commands and just type fastboot ....
You need Romracer's fastboot file, which is on the left side... not the flashable .zip file which is for CWM.
you are my new favorite person in the whole wide world. its currently formatting, and i'll be sure to log on in the morning to post my results. but this is far enough for the night i think. im beat. thanks for ALLLL the help and patience!
Oh. I guess I should add this piece of advice since no one else has. Don't get bored at work and try flashing roms. You don't have recovery available or another rom available. I speak from experience.
I voided my warranty.
just wanted to say i have everything up and running. super fast, super smooth, and so far, no errors or issues. thanks alot guys!