Hi guys,
For the last 2 nights I´ve been trying to get a CG Mod 6.1 on my HTC Magic 32B.
I have rooted it with onclick-root method and tried a bunch of things like ROM Manager and flashing via fastboot (brings up "remote not allow" error). Nothing worked out.
Here are the facts:
HTC Magic with OTA upgrade to 2.2.1
hboot: 1.33.0013
radio: 2.22.28.25
Rooted with Oneclick method
Do I need a goldcard? How do I do that? What hboot Version do I need? What Radio do I need? What do I have to do first?
Are you certain the Root took? Are you seeing the Superuser icon in your app drawer?
When you were using Rom Manager did you flash, or attempt to flash a custom recovery, and if so did it install ok?
What happened when you tried to flash a ROM using Rom Manager?
I'm sure we'll get to the bottom of this
Yes, rooting has worked...Icon is there everything looks fine.
With the Rom Manager i tried to install "update-cm-6.1.0-DS-2708port_S" aswell as the "update-cm-6.1.0-DS-signed". Both did not work.
I still can boot to my standard OTA 2.2.1
Try wiping your phone in recovery and then install the rom
hang on a minute...
it sounds like you haven't installed a custom recovery before trying to flash the rom. Can you clarify...have you actually done this yet?
The process should go root/recovery/nandroid backup/rom in that order.
yeah you re right...i dont have a custom recovery
i just tried to load "recovery-RA-sapphire-v1.7.0G.img" on the console
su
# flash_image recovery /sdcard/recovery.img
does not work, i get: flash_image: not found
USB debugging is enabelde
3rd party software is enabeled
is there another way to get flash the recovery ?
Rom Manager!
At the top you should have the option to flash clockworkmod recovery. Select that; it will run and then the phone should reboot. I usually do it again to confirm. If it installed correctly the first time you'll get a pop up saying that it is installed.
If all goes to plan select 'backup current rom' from within Rom Manager. This is a nandroid backup and can be re-installed from recovery any time you wish to return to stock.
NOW you are free to install a custom ROM of your choice
Post back if you encounter any issues.
I have tried that. It flashes, gives my a popup that it installed correctly.
But it does not reboot.
When i choose restart in recovery mode it boots up the phone an gets stuck on the vodafone logo. BatteryOut reboot and i am back at the good old 2.2.1 OTA
do i have to wait long?!? cant be, right? do i need to hold down any buttons?
If you try the backup option now you'll soon find out if the recovery did indeed install ok. (it won't backup if the recovery isn't installed)
i restarted...flashed the recovery again. got popup confirmation. then chose backup rom and got stuck at the vodafone logo
You must be pretty frustrated by now. It might be time to start asking for more help in the dev section of the Magic forum HERE.
I hope that somebody has the answer!
Thanks for your help...i ll see if someone else has any ideas.
roodee said:
yeah you re right...i dont have a custom recovery
i just tried to load "recovery-RA-sapphire-v1.7.0G.img" on the console
su
# flash_image recovery /sdcard/recovery.img
does not work, i get: flash_image: not found
USB debugging is enabelde
3rd party software is enabeled
is there another way to get flash the recovery ?
Click to expand...
Click to collapse
Are you are aware that the command you need to type will be
flash_image recovery /sdcard/recovery-RA-sapphire-v1.7.0G.img
The command points to the exact file name on your sd card so if you just wrote flash_image recovery /sdcard/recovery.img and the recovery file was not called "recovery.img" it would not know what to look for.
I'm not sure if this is what you have or whether you just copied and pasted from a guide, but I just thought I'd put it out there in case that is the case.
Hope this helps.
Related
hey i rooted my nexus s and installed clockworkmod 3.0.0.0
i have installed rommanager 3.0.0.2
when i open the rommanager it says that there is a update to version 3.0.0.5
i tap on install after a wile it says that is installed correct
BUT
when i boot into recovery ... it dont work ... i boot the nexus s again an step back to clockwork 3.0.0.0 an i can boot to the recovery ...
so what is wrong?????
thx
footballpics.info said:
hey i rooted my nexus s and installed clockworkmod 3.0.0.0
i have installed rommanager 3.0.0.2
when i open the rommanager it says that there is a update to version 3.0.0.5
i tap on install after a wile it says that is installed correct
BUT
when i boot into recovery ... it dont work ... i boot the nexus s again an step back to clockwork 3.0.0.0 an i can boot to the recovery ...
so what is wrong?????
thx
Click to expand...
Click to collapse
you may just have to install CWM manually like you first did
ok ok ... i will do that ... thx for the hint
BUT
what for is the updatefunction in the rommanager then if it is not working???
slowz3r said:
you may just have to install CWM manually like you first did
Click to expand...
Click to collapse
You could probably flash it from fastboot, but the OP is correct, the 3.0.0.5 update "breaks" ROM Mgr and CWM.
With 3.0.0.0 you can open ROM Mgr, then select Reboot To Recovery, and the phone will quickly reboot into CWM recovery.
Upgrade to 3.0.0.5 and when you select Reboot To Recovery, the phone gets stuck on the white Google on black background screen. A battery pull is required.
Downgrade to 3.0.0.0 and the expected behavior returns.
Seems to be a bug to me with 3.0.0.5. Need to let koush know.
To the original poster, you're aware that if you're on Android 2.3.1 that any fresh normal boot of the phone restores the stock recovery to the device unless you remove/rename the appropriate script in the /etc folder, right?
i have Android 2.3.1
which file i have to remove/reneame in dhe "/etc" folder?
is this different to the way to update the clockwork as on the HTC Desire?
thx
footballpics.info said:
i have Android 2.3.1
which file i have to remove/reneame in dhe "/etc" folder?
is this different to the way to update the clockwork as on the HTC Desire?
thx
Click to expand...
Click to collapse
/etc/install-recovery.sh
Be aware there are some who think it's risky. I'd advise reading this thread before proceeding, at least the last few pages of it.
I'd also be leary of messing with the recovery until you're sure you're able to get into at least CWM to make fixes if needed (e.g., have CWM 3.0.0.0 working).
Also, I just went to the Market, found Rom Manager (Premium) and scrolled down to the email the author link and sent a bug report. I'm not encouraging spamming him with complaints, but those anxious for a fix might want to report the bug as well if they have it.
i installed Clockwork again from: http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html (Nexus S 3.0.0.5)
an installed it manualy with: fastboot flash recovery recovery.img
after taht i loaded the recovery and it told me that i have 3.0.0.5
rommanager told me i have 3.0.0.0 and there is a update for me *g*
but when i tryed to reboot an go to the recovery again its not possible ... i got an error and had to hardboot - its possible to load android ...
so now ... whats the problem ... i downloaded the right CW and installed it like i did 1st. time ...
i read the link you gave me - found that:
Originally Posted by Luxferro
well in order to prevent your recovery from returning to stock, you need to use root explorer, or another method to rename the following file:
/etc/install-recovery.sh
rename it to something like install-recovery.sh.old
now when you phone boots, it won't be able to run that script to replace your recovery.
That's all there is to it. It's that simple. Root explorer is a file explorer with root access. When you browse to the file, click the button to enable read-write access in root explorer, and then long press on the filename and rename it.
...............................................
when i have 3.0.0.0 as recovery and i reboot and then reboot to recovery anything is working i kan go to the recovery menue - i have root rights and i can install what i want .. so what is set back with this "bootscript"?
for me everything sounds a little bit wierd ... i am sorry ...
thx
flo
My 3.0.0.5 recovery wasn't there as well. I reflashed it in Rom Manager, and then it worked.
Rom Manager had a problem on Droid 1, where you had to flash the recovery a couple times. I'm hoping that bug doesn't apply to Nexus S as well.
so now its not possible to boot into the recovery ... its 3.0.0.0 or 3.0.0.5 ...
ok i renamed this /etc/install-recovery.sh to /etc/install-recovery.sh.sav now the update seems to work ...
I was running 3.0.1 unlocked/rooted, Tiamat's 1.4.1 kernel. I followed the steps to update to 3.1 from here, and had no issues what so ever. This was earlier this week, and today I was going to run fix permissions in recovery. I used Quick Boot (also tried Reboot to Recovery in ROM Manager) to boot to recovery, and I got to the Android with the exclamation point...
I tried sending the modified 3.0.2.8 recovery listed in the Dev Forums using fastboot commands, and everything went smooth with no errors, but still got the Android/exclamation point.
I tried reflashing recovery via ROM Manager, and it wouldn't pop up anything, so I uninstalled/reinstalled, and the flash of recovery worked. Boom! Recovery is back! So I can do what I need (run fix permissions), and rebooted the device.
I try to reboot into Recovery again, back to Android with exclamation point. Any thoughts here as to why I must do this, and thoughts to what I can try to make Recovery "stay"?
Thanks!
RMarkwald said:
I was running 3.0.1 unlocked/rooted, Tiamat's 1.4.1 kernel. I followed the steps to update to 3.1 from here, and had no issues what so ever. This was earlier this week, and today I was going to run fix permissions in recovery. I used Quick Boot (also tried Reboot to Recovery in ROM Manager) to boot to recovery, and I got to the Android with the exclamation point...
I tried sending the modified 3.0.2.8 recovery listed in the Dev Forums using fastboot commands, and everything went smooth with no errors, but still got the Android/exclamation point.
I tried reflashing recovery via ROM Manager, and it wouldn't pop up anything, so I uninstalled/reinstalled, and the flash of recovery worked. Boom! Recovery is back! So I can do what I need (run fix permissions), and rebooted the device.
I try to reboot into Recovery again, back to Android with exclamation point. Any thoughts here as to why I must do this, and thoughts to what I can try to make Recovery "stay"?
Reflash cmw afterward and it should stay.
Thanks!
Click to expand...
Click to collapse
Use your computer to do this:
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
or alternately, you can use a root file manager such as root explorer to remove the files (I personally just renamed mine so they wouldn't be recognized. I don't like burning bridges).
Re-flash cmw afterward and it should stay.
Thanks! That worked, you the man! I renamed them as well, as I don't want to burn bridges either.
hi there
when i try to install the new recovery with:
1.: Rommanager it makes the update but i cant boot into recovery
2.: i tryed to install it with: "flash_image recovery /sdcard/name-of-recovery.img"
but both ways are not working ..
so what to do?
thx
flo
There is now 5.0.1.0 update posted on koush's page (Google Nexus S):
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.1.0-crespo.img
Click to expand...
Click to collapse
You can open Android Terminal app and type the following commands:
su
flash_image recovery /sdcard/recovery-clockwork-5.0.0.0-crespo.img
reboot recovery
Click to expand...
Click to collapse
I was able to update via ROM Manager successfully though (it will take quite awhile to switch from Google logo to boot animation on your first reboot).
i allready tryed that terminal thing .. last time it worked (3.0.0.5 to 3.0.2.4) but this time .. no chance ..
the update with rom manager dindnt work on my Nexus S anyways .. i dont know why ..
i tryed that with different roms ..
i had such a problem on my Desire like a year ago and than i had to delete a file .. i cant remember but is it possible that i have to delete the file here too?
thx
flo
ok .. in this Thread:
http://forum.xda-developers.com/showthread.php?t=1039584&page=5
i found this:
"anyone having issues with recovery flashing open rom manager and press menu and go to settings. now check erase recovery. this will wipe the recovery partition prior to flashing. this makes the recovery img flash correctly 99% of the time. if not on the main page in rom manager press menu and clear your download cache. this will remove all the files and folders inside /sdcard/clockworkmod/ so you will los e any roms downloaded. then click to flash the recovery again. it will redownload the recovery and reflash. you should still keep the erase option in settings checked. if it still does not flash correctly try flashign twice in a row. if that doesnt work fastboot erase recovery . and fastboot flash recovery \path\to\recovery\here.img"
delete recovery BEFOR flashing a new is working here ...
Flash_image gui by Joeykrim will work great for you
I did an update to v5 and couldn't boot into recovery too, but that was because i did it by the usual hardware buttons Power + VolumeUp.
Then by accident, i was able to boot into recovery, and that is by the "Reboot into Recovery" menu in ROM Manager itself.
Have you tried this method of rebooting yet?
the new cwm flashed fine for me no issues.
I can no longer reboot into recovery after updating to CWM5.01. Tried using rom manager and terminal emulator with no luck. Also tried reverting back to my old recovery and still nothing. The above steps posted didn't work either. Someone please help. I can't restore any backups because I can't boot into recovery.
Edit: Working and fixed by pushing it through adb
Unlocked and rooted ATT HTC One X and flashed pa_evita-2.54-09NOV2012-210217 ROM.
Boot up as far as an Android character with the lettering Paranoid Android 2.+ and then freezes there.
Any suggestions?? If nothing else, how do I get back to stock ROM?
Noob rldieb
rldieb said:
Unlocked and rooted ATT HTC One X and flashed pa_evita-2.54-09NOV2012-210217 ROM.
Boot up as far as an Android character with the lettering Paranoid Android 2.+ and then freezes there.
Any suggestions?? If nothing else, how do I get back to stock ROM?
Noob rldieb
Click to expand...
Click to collapse
1. What recovery are you using?
2. Did you wipe cache/dalvik-cache, factory reset?
In order to get back to a stock ROM, you will need to boot into recovery, then mount your usb storage. Put the rom on your sd card and then unmount. To be safe, wipe the cache and dalvic cache, then flash the stock rom.
What hboot are you on?
You may have flash boot.img first if you are on hboot 1.14
I think he just didn't full wipe
That's just wrong!
Sent from my Nexus 7 using Tapatalk 2
I'm having the same issue. I'm trying to flash this same rom on a device rooted on 2.20. I think my issue has something to do with flashing the boot.img. I have tried to flash using hasoon's toolkit, which doesnt seem to work, i have extracted the zip and placed the boot.img in the kernel folder, and when the command prompt tries to flash it, it says error. I have also tried flashing the kernel from the phone directly using the flash flash image gui app, and it says flash is successful, but when it prompts to boot into recovery, the command doesnt work from my phone so i have to boot into recovery manually.
can anyone give a solid link or tutorial on how to successfully flash the boot img onto my device, every link I have read uses windows cmd prompt, which when i try to replicate, it never works.. So, for now I flashed back to viper rom, since it has its own installer. It would be so nice if all these other roms were able to install like that.
thanks in advance for the help
threetwentyfizzle said:
I'm having the same issue. I'm trying to flash this same rom on a device rooted on 2.20. I think my issue has something to do with flashing the boot.img. I have tried to flash using hasoon's toolkit, which doesnt seem to work, i have extracted the zip and placed the boot.img in the kernel folder, and when the command prompt tries to flash it, it says error. I have also tried flashing the kernel from the phone directly using the flash flash image gui app, and it says flash is successful, but when it prompts to boot into recovery, the command doesnt work from my phone so i have to boot into recovery manually.
can anyone give a solid link or tutorial on how to successfully flash the boot img onto my device, every link I have read uses windows cmd prompt, which when i try to replicate, it never works.. So, for now I flashed back to viper rom, since it has its own installer. It would be so nice if all these other roms were able to install like that.
thanks in advance for the help
Click to expand...
Click to collapse
I do have a solution! Download Flash Image GUI from the market (it's $1.99) and it will do the process for you, no commands needed! The app is also available via XDA for free, do a search and download it.
Good day everyone,
Thanks for taking the time to read this. I am in desperate need of your help. I recently purchased a HTC One S from an online store they told me it was new never used locked phone. Turns out phone was rooted, 4g does not work, and it could not recognize e drive, (internal sd card)
After reading the all in one i re-rooted it and install the teamwin version of recovery.
Now i never had any back ups or any factory files. as i got the phone rooted with software that did not work. My phone now has no rom and i cannot install from adb sideloader, or an other means. I am new to this and cannot seem to figure out how to get my phone back to even stock un-rooted etc. I tried multiple forums and download links but nothing.
i was able to install vipers rom at one point but despite several attempts to reinstall. recovery does not see files loaded. which i can see on my mac or pc.
the other strange thing i notice is that at the top in fastboot mode i sometimes see unlocked in pink only and other times i see both unlocked and tampered. when its unlock only none of my computers recognize connection.
I also tried boot.img for flash. The furthest my screen no goes is the htc logo, then goes black.
Please help, even to just point me in rite direction to have this resolved.
the boot.img, did you flash it via fastboot? (fastboot flash boot boot.img)
And, one question that comes to mind... they sold you a device as new, yet it wasnt.. Why didnt you return it?
Goatshocker said:
the boot.img, did you flash it via fastboot? (fastboot flash boot boot.img)
And, one question that comes to mind... they sold you a device as new, yet it wasnt.. Why didnt you return it?
Click to expand...
Click to collapse
Yes I tried several times loading the boot.img via fastboot.
As far as returning the device i trashed the mailing box but kept original packaging so no return address. I called the company which i made the purchase from "N1wireless" several times and sent several emails to them. They have yet to reply or answer any of my calls. Which is why I am so frustrated.
mnitllc said:
Yes I tried several times loading the boot.img via fastboot.
As far as returning the device i trashed the mailing box but kept original packaging so no return address. I called the company which i made the purchase from "N1wireless" several times and sent several emails to them. They have yet to reply or answer any of my calls. Which is why I am so frustrated.
Click to expand...
Click to collapse
Boot into recovery, select mount > mount usb storage. From pc move the Rom.zip to your sd card which should now be showing on your pc. After it is moved to your phone select unmount then press home button in twrp recovery. Then install the Rom. After install open up adb and type adb reboot bootloader then press enter. Now fastboot flash the boot img from inside the Rom.zip on your computer. After that reboot your phone and report back
Sent from my HTC One S using xda premium
bochocinco23 said:
Boot into recovery, select mount > mount usb storage. From pc move the Rom.zip to your sd card which should now be showing on your pc. After it is moved to your phone select unmount then press home button in twrp recovery. Then install the Rom. After install open up adb and type adb reboot bootloader then press enter. Now fastboot flash the boot img from inside the Rom.zip on your computer. After that reboot your phone and report back
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Hi, thanks for the reply, thats just the thing I cannot in recovery install any rom loaded to sd card. It fails. I tried reinstalling the recovery and it still not reading my sd card.
So my guess is i need a new twrc or how to do it from my mac, as now when i try on my pc it is failing as-well. Once I get the recovery to work I will try your other suggestions as I think it will work based on the steps you mentioned.
I am trying to figure out how to use terminal to reinstall recovery. any suggestions or links will be greatly appreciated.:good:
you install recoveries through fastboot, fastboot flash recovery recovery.img
Goatshocker said:
you install recoveries through fastboot, fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I reinstalled recovery several times now and it wont recognize the sd card. is there another recovery i can download and use? Also is there any instructions for a newby to use terminal to re-boot, everything from scratch. Meaning if the phone is completely blank except the fast boot and a recovery manager no backups or stock kernel etc. what is the format to be used in order for the computer and recovery to recognize the sd card?
I think I need a good recovery rom like cmod if there is one for the htc one s or the stock one if someone has it.
hi i had that problem
mnitllc said:
I reinstalled recovery several times now and it wont recognize the sd card. is there another recovery i can download and use? Also is there any instructions for a newby to use terminal to re-boot, everything from scratch. Meaning if the phone is completely blank except the fast boot and a recovery manager no backups or stock kernel etc. what is the format to be used in order for the computer and recovery to recognize the sd card?
I think I need a good recovery rom like cmod if there is one for the htc one s or the stock one if someone has it.
Click to expand...
Click to collapse
I had that problem the sd card would not be seen by my laptop and the phone would not boot at all if you plug in the phone to your go to start and then computer right click on your c drive go to manage and see if you can see it there if so try to format it and then reboot the phone if it works you can then install cwm as a recovery system then you can put what rom you wont on it i am use in zenRom 1.05 and to me its the best coz it like the htc rom that the phone come with if that don`t work let me know coz i have more tricks to try i hope this helps you out.
Theres only TWRP and CWM for the S afaik, and CWM sucks. TWRP is the one to use.
I had a similar problem a few days ago, luckily there's not such a bad solution.
1) Pick a custom ROM you want to install from the HTC One S developer forums (I went with Trickdroid) and download the ROM/boot image.
2) Then download and flash the stock recovery here: http://www.4shared.com/file/1UuxTh0k/stock_recovery.html
3) Boot into bootloader, clear storage and then reset to factory defaults.
4) Flash TWRP
5) Reboot into recovery, sdcard should now be mounted/visible
Then push the ROM to your sdcard with adb or mount USB storage and flash it/flash the boot image and you should be sorted.
Edit: Here's where I got the solution from btw (post #8):
http://forum.xda-developers.com/showthread.php?t=1630459
Hope that helped!
violentlighting said:
I had a similar problem a few days ago, luckily there's not such a bad solution.
1) Pick a custom ROM you want to install from the HTC One S developer forums (I went with Trickdroid) and download the ROM/boot image.
2) Then download and flash the stock recovery here: http://www.4shared.com/file/1UuxTh0k/stock_recovery.html
3) Boot into bootloader, clear storage and then reset to factory defaults.
4) Flash TWRP
5) Reboot into recovery, sdcard should now be mounted/visible
Then push the ROM to your sdcard with adb or mount USB storage and flash it/flash the boot image and you should be sorted.
Edit: Here's where I got the solution from btw (post #8):
http://forum.xda-developers.com/showthread.php?t=1630459
Hope that helped!
Click to expand...
Click to collapse
got it. will try it asap.
I could not get the stock recovery via that link you provided. If there is another link to the stock I would appreciate it. I had to flash it wit cwm twice then reflash with twrc to get it to identify the sd card. i had tried the viper rom but my 4g and wifi doesnt work. Will try trickmod hopefully that works with no more issues
violentlighting said:
I had a similar problem a few days ago, luckily there's not such a bad solution.
1) Pick a custom ROM you want to install from the HTC One S developer forums (I went with Trickdroid) and download the ROM/boot image.
2) Then download and flash the stock recovery here: http://www.4shared.com/file/1UuxTh0k/stock_recovery.html
3) Boot into bootloader, clear storage and then reset to factory defaults.
4) Flash TWRP
5) Reboot into recovery, sdcard should now be mounted/visible
Then push the ROM to your sdcard with adb or mount USB storage and flash it/flash the boot image and you should be sorted.
Edit: Here's where I got the solution from btw (post #8):
http://forum.xda-developers.com/showthread.php?t=1630459
Hope that helped!
Click to expand...
Click to collapse
Hey thanks allot for your suggestions. I made some progress. It kinda worked. However I my wifi and data connections no good. I tried the 9.1 update and then tried the tweaks.
Do you know if it is possible to get stock kernel and stock rome to undo changes on device?