Alright guys, i rooted a bit back and then ddid the recovery image just fine. I even loaded fresh and ran it for several months. Now i loaded the new radio that fresh put out ( i had the non google phone with the old radio ) since i loaded the new radio i had to re-root. The root went ok. I can teather and all and i pushed the recovery image ok ( it said xxxx bytes in xxxx seconds ) but when i re-boot into recovery i get the skateboard androids... any idea on whats up?
Bummpppo.......
You didn't say that you flashed the recovery image. You need to flash it, not just push it...
adb shell
su
flash_image recovery /sdcard/RA-blah-blah.img
reboot recovery
mroneeyedboh said:
Bummpppo.......
Click to expand...
Click to collapse
Flipz has a point.
You also can flash using flashrec.
I was able to root and flash a custom rom all from my phone using this method.
**** sry i did push to sd card and flashed it. It said completed and all and when i do reboot recovery it sends me to the skateboards.
Will look into flashrec.
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!
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
So up until about the other day i had successfully rooted wit 2.2.1 for my mytouch 4g and had royalginger rom installed and working fine. Then i turned on my phone and it had mad force closes and would not stop popping up thoses error messages so then i go into recovery attempt to do factory resets and all i get now is being stuck a boot screen. I try to use adb for pushing the recovery of clockwork back on my phone and all i get is device offline. all im tryna do at this point is flash the stock rom. i downloaded the 312 mb stock rom i believe named it to pd15img tried to flash thru hboot then even named to update.zip and tryed thru the stock recovery sdcard update.zip apply? am i sol or is there a chance to get an operation
Cliff Notes.
phone stuck at boot screen
cant get anything other than hboot/stock recovery for use currently
trying to load clockwork mod recovery or simply flash stock rom
csaunders1 said:
So up until about the other day i had successfully rooted wit 2.2.1 for my mytouch 4g and had royalginger rom installed and working fine. Then i turned on my phone and it had mad force closes and would not stop popping up thoses error messages so then i go into recovery attempt to do factory resets and all i get now is being stuck a boot screen. I try to use adb for pushing the recovery of clockwork back on my phone and all i get is device offline. all im tryna do at this point is flash the stock rom. i downloaded the 312 mb stock rom i believe named it to pd15img tried to flash thru hboot then even named to update.zip and tryed thru the stock recovery sdcard update.zip apply? am i sol or is there a chance to get an operation
Cliff Notes.
phone stuck at boot screen
cant get anything other than hboot/stock recovery for use currently
trying to load clockwork mod recovery or simply flash stock rom
Click to expand...
Click to collapse
Royal Ginger is a 2.2 ROM, if you are using Clockwork mod 3.0.0.5, there lays your problem. I have thread that is sticked to the top of the Q&A section that should be able to help you out. It's also the green link in my signature.
the reason the the PD15IMG didn't work is you need to download the PD15IMG image, it's not a ROM it's the actual file that HTC flashed to your phone to make it come alive, and flash it via the hBoot screen. IT will do it automatically. But i don't think you need to do that to resolve your issue.
i thought royal ginger was a gingerbread rom cause it said 2.3.3 on my about phone menu , not sure. but ill check out your thread and see if it can free my phone
csaunders1 said:
i thought royal ginger was a gingerbread rom cause it said 2.3.3 on my about phone menu , not sure. but ill check out your thread and see if it can free my phone
Click to expand...
Click to collapse
I'm sorry u are correct. RoyalGlaicer is the 2.2 variant.
since that is the case are you getting any errors in the recovery image about not being able to mount anything?
i have tried to use the pd15img.zip in my stock recovery and even changing it to update.zip and flashing through my stock recovery but my stock recovery says invalid operation for any zip? now im like wtf..
csaunders1 said:
i have tried to use the pd15img.zip in my stock recovery and even changing it to update.zip and flashing through my stock recovery but my stock recovery says invalid operation for any zip? now im like wtf..
Click to expand...
Click to collapse
the PD15IMG needs to be left named PD15IMG, and you flash if via the HBoot image. You do not need to use the recovery image to flash it. Just store it on the root of the SDcard and boot into bootloader. make sure to check the MD5SUM of the download to verify it's a good download. you can find hundreds of ways to do that via Google.
sir is there a instant messaging medium i can reach you on and when i dowloading it it was a zip ill see how to check the md5sum now but should i leave as pd15img.img and go to hboot again?
csaunders1 said:
sir is there a instant messaging medium i can reach you on and when i dowloading it it was a zip ill see how to check the md5sum now but should i leave as pd15img.img and go to hboot again?
Click to expand...
Click to collapse
ok so everytime i try to flash a zip in my stock recovery which i only have access to know it says invalid operation
how could this be?
csaunders1 said:
ok so everytime i try to flash a zip in my stock recovery which i only have access to know it says invalid operation
how could this be?
Click to expand...
Click to collapse
So your saying you can get into recovery, but not hboot? Lol on the MT4G you have to go through hboot to get to recovery. Also, your trying to use stock recovery? If so (you need adb) download the cwm recovery image from somewhere and push it to your phone via adb and that should give you a fresh recovery to work with which would eliminate the possibility of a bad recovery hope that helps
Sent from my HTC Glacier using XDA Premium App
Ok I have no idea what happened but I can not get into recovery mode. Rom manager takes me straight to bootloader and selecting recovery in bootloader takes me back to bootloader...! I've tried reflashing recovery via clockwork but no go, and flashing old 2.X.X versions gives me an error...
Help?
ROM Manager seems to be the least reliable way to flash the recovery. Try flashing it through terminal emulator or better yet, if you have the engineering SPL, do it through fastboot.
If you don't know how though you could try a reinstall of rom manager and if your running a custom rom boot straight into recovery from there to see what happens
TeeJay3800 said:
ROM Manager seems to be the least reliable way to flash the recovery. Try flashing it through terminal emulator or better yet, if you have the engineering SPL, do it through fastboot.
Click to expand...
Click to collapse
The thing is that is how I have always done it and how I did it with this phone originally but something got messed up somehow. Anyhow how do I flash that with Terminal? I have never done that before. Do you have a link to a totorial and a download for clock work that can be flashed that way?
dcwiker05 said:
The thing is that is how I have always done it and how I did it with this phone originally but something got messed up somehow. Anyhow how do I flash that with Terminal? I have never done that before. Do you have a link to a totorial and a download for clock work that can be flashed that way?
Click to expand...
Click to collapse
First download CWM 3.0.0.6 from here and put the file in the root of your SD.
Then open terminal emulator and enter these commands:
Code:
$su
#flash_image recovery /sdcard/recovery.img
Hi guys, i have cwm 3.0.0.5 which is really a cwm 3.0.0.6 mod i downloaded from here. anyway,i cant get back too 2.5.1.2. when i go into rom manager the lowest it says is 2.5.1.3 and none of the 2.x work for me except my old one. i tried rebooting it, and flashing the original 3.0.0.5 and it still doesnt show up and i have the paid version by the way. so my question is how do i get it back?
second problem is i flashed a splash screen and its stuck on there with a staticky looking bar covering the top of the screen when i reboot. i have deleted the custom.img on the sdcard, wiped the phone, flashed another custom.img, factory reset the phone, and it still is there and i pushed the files through terminal emulator, i do everything from my phone because my computer is very laggy. can anyone help with the above problems?
TamiaSky said:
Hi guys, i have cwm 3.0.0.5 which is really a cwm 3.0.0.6 mod i downloaded from here. anyway,i cant get back too 2.5.1.2. when i go into rom manager the lowest it says is 2.5.1.3 and none of the 2.x work for me except my old one. i tried rebooting it, and flashing the original 3.0.0.5 and it still doesnt show up and i have the paid version by the way. so my question is how do i get it back?
Click to expand...
Click to collapse
you can always find just the recovery image and flash it via the ADB commands.
TamiaSky said:
second problem is i flashed a splash screen and its stuck on there with a staticky looking bar covering the top of the screen when i reboot. i have deleted the custom.img on the sdcard, wiped the phone, flashed another custom.img, factory reset the phone, and it still is there and i pushed the files through terminal emulator, i do everything from my phone because my computer is very laggy. can anyone help with the above problems?
Click to expand...
Click to collapse
you need to flash a new image, that is the only way to fix it.
neidlinger said:
you can always find just the recovery image and flash it via the ADB commands.
you need to flash a new image, that is the only way to fix it.
Click to expand...
Click to collapse
and where would i find the recovery image? and can it be done using terminal emulator, becuase my computer has a virus and it takes days to load stuff or do anything, thats why i do it straight from my phone
and i have flashed a new image just like u quoted me i deleted the stuck one, wiped the phone, then i flashed another one, then factory reset the phone and its still there!
TamiaSky said:
and where would i find the recovery image? and can it be done using terminal emulator, becuase my computer has a virus and it takes days to load stuff or do anything, thats why i do it straight from my phone
and i have flashed a new image just like u quoted me i deleted the stuck one, wiped the phone, then i flashed another one, then factory reset the phone and its still there!
Click to expand...
Click to collapse
i'm sure google has something on the recovery image. I only have 3.0.0.6 stored in a .zip.
you CAN flash the recovery image via the terminal but not the boot image.
TamiaSky said:
and where would i find the recovery image? and can it be done using terminal emulator, becuase my computer has a virus and it takes days to load stuff or do anything, thats why i do it straight from my phone
and i have flashed a new image just like u quoted me i deleted the stuck one, wiped the phone, then i flashed another one, then factory reset the phone and its still there!
Click to expand...
Click to collapse
Download a fresh cope of the latest version here: http://mirrorbrain.cyanogenmod.com/cm/recoveries/recovery-clockwork-3.0.2.4-glacier.img and flash it via terminal emulator. It automatically overwrites the previous installation.