After having overheating issues (presumably voltage related?) with the official XWLP7 XEU (UK) ROM I decided to try my luck on a custom slim version.
Phone was successfully CF rooted before Dynamic v1.4 ★[ICS][Slim][Performance & Battery life][25April] was installed.
Custom ROM is running fine, however when I was playing around in the recovery menu the phone screen randomly displayed artifacts after selecting "reboot now". So I was wondering if it's possible to downgrade clockworkmod to the generic public release version - namely this puppy?
Thanks for reading my first post lol
I suspect CWM went retarded during the CF to Dynamic v1.4 transition - can someone provide some insight here? I've deduced kernels were changed, but was unaware of the implications to the recovery console in doing so
Functionality only becomes an issue in the recovery menu before OS loads otherwise everything is tight as a drum
Recovery is linked to the kernel. Obviously your kernel changed when you flashed that ROM. If you want to change your CWM recovery, flash a different kernel which has the version you want.
Ok, I've gone ahead and been an inpatient muppet installing ROM manager from Google play and flashed the respective recovery console. Will this cause conflicts? It seems the original one still stands using the the three button combo when powering up where as the generic recovery console I just put on has to be executed via OS.
no issues keeping both if working perfectly....
Normaly there is a mismatch seen between ROM manager and other custom recoveries..
if you are rebooting from ROM manager to CWM if the update package flashes smoothly and flashed CWM is appears then no issue you can use it. i think its only flashes temporerly,
when you use the 3 combo you can get the recovery which is incorporated with your kernel....we only need a working CWM to flash zips, and backup,
Related
Hi,
Due to HTC's special touches, the recovery image doesnt stay flashed, and on normal boot its flashed over (meaning if i try to go to recovery after a normal boot, i get the red triangle stuff, and have to pull the battery). I was wondering if this would potentially cause troubles if i was trying to flash a custom ROM from recovery? in other notes, i do find sometimes i have to pull the battery 4 or 5 times to get it to normally boot (thats without holding the buttons >.>).
Thanks in advance.
HTC HERO recovery image flashing problems
I am having exactly the same problem!
I did a quite a bit of research on how to root, backup and flash my HERO and every guide I found describes the process using Universal AndRoot + Rom Manager and it seems there should be no problems. I already rooted my phone successfully, installed Rom Manager and flashed either ClockworkMod 2.5.0.1 or RA Recovery 1.7.0.1 which are able to boot but only once. The next time I reboot I get the red triangle warning and it loads into stock recovery (by pressing vol_up + powroff buttons), so the custom recovery lasts only one boot cycle. I was able to backup but I don't want to risk to wipe and flash since there is a chance it might stuck in the bootscreen loop afterwards and I won't be able to do anything.
There is a thing with s-off and SPrecovery which helps to resolve the problem but it doesn't look like there is anything for HERO.
Any help would be appreciated.
ps I tried to manually flash recovery from inside the phone and from windows command line with the same result.
forum.cyanogenmod.com/topic/8182-how-to-root-your-hero
posted some similar comments over there, and the only init script that i can find when in recovery.
Yeah I posted my question there too.
I was able to find some information about the issue (he is talking about Villain ROM but I think it doesn't really matter):
pulser_g2:
Repeat the process again, as I think stock ROMs try and overwrite the recovery each time they boot. When you finish the process, immediately nandroid and flash VR12. That will then flash a new recovery, AmonRA 1.6.2a, and you will be sorted
Click to expand...
Click to collapse
So it looks like we should just go ahead and flash a custom rom which, in theory, will eliminate the problem.
yeah was tempted to just flash, but sending duck my system img for him to dissect anyway.
yeah worked fine, running cm6.1 now
Yeah once you root you have to flash a custom rom before reboot or u loose the root
I learnt it after lots of reboots and re roots.
but now I wanted to know if I could save the original rom which i have as nand backup to make as an update.zip like custom rom for safe keepimg
I flashed CM6.1 -based TastyFroyo 1.2 and I can confirm custom recovery stays flashed now.
Here's the situation:
I recently s-off'd my Legend (Bell Canada variant) in order to try out ogo2's NewSense ROM and do some metamorph stuff. I also attempted in install ClockworkMod 3.0.2.8 via the fastboot method which seemed to work just fine.
I used ogo2's NewSense beta 2 without any difficulty, but decided to switch back to CM7 via a backup I made earlier. No problems so far.
Here's the problem:
Yesterday I tried to flash beta 4, and this is where things got a bit weird.
When I use Rom Manager to try flashing beta 4, it loads ClockworkMod 2.5.0.7. Likewise, if I reboot into recovery from ROM Manager, I end up in ClockworkMod 2.5.0.7.
If, however, I manually boot into recovery then I end up in ClockworkMod 3.0.2.8.
I've tried flashing beta 4 manually and through ROM Manager and each time the ROM seems to install just fine but I end up stuck at the splash image. Naturally, I try to manually boot into recovery so I can restore, but it often just reboots or gets stuck at the splash image before CWM can load. Not a problem anymore.
I have to do a couple of battery pulls before I can sucessfully enter recovery (when I do, it's CWM 3.x).
Since then I've restored to CM7, but I can't flash beta 4 and the CWM disparity doesn't seem right to me. In otherwords, my phone is completely usable but CWM doesn't seem right.
Does anyone have any insight into this problem or a possible solution?
The issue lies in the way ROM Manager deals with recoveries. When the Legend was first given ROM Manager support S-OFF was a thing of dreams, we had to use the fakeflash method to get to CWM, so Koush made ROM Manager use fakeflash with some phones. Ours was one of them. When you "flash" a recovery using ROM Manager a fakeflash .zip is downloaded to your phone and stored somewhere, then using a method I don't fully understand ROM Manager reboots to recovery and "flashes" the fakeflash .zip. Now, because S-OFF we can flash recoveries to the recovery partition, but Koush hasn't updated his app to allow us to make use of it, nor has he made an updated version of CWM in fakeflash format for it. If someone cared enough they could probably get support for the latter at least. Because Koush hasn't updated his stuff to make use of new developments for our phone, ROM Manager assumes S-ON and still uses the fakeflash method, hence CWM 2.0.5.1 when using ROM Manager.
Thanks for the info. I was beginning to suspect something along those lines but it's always nice when someone who actually knows something about it gives an explanation.
I've seen on the Cyanogen forum that there is a fake flash 3.0.2.8. Anyone who can confirm this? I can't manage to get it to work :S
Sent from my HTC Legend using Tapatalk
Is ROM Manager fully functional on this phone now? Just wondered if all of the options: CWM, Updates, Fix permissions, etc. are all working for folks - with no issues. Will it update to CWM Touch?
Thanks for any input.
im running touch flawless but i cant seem to download and go straight to recovery i have to manual but cwm is working fine
I posted a lengthy question earlier on this....for me, ROM Manager 6.0.1.5 (non touch) insatalls and seems to work fine, however when I try to do a backup of my current ROM it does not fully do it.
Uninstalling ROM Manager and flashing via fastboot the posted CWM recovery, I was able to do a successful Nandroid.
Just sucks not being able to use ROM Manager to backup your current ROM...for me at least.
At the Rom Manager Website I see both versions for the DNA:
http://www.clockworkmod.com/rommanager
It says the version number (for both) should be 6.0.1.5. Currently running 6.0.1.2 on my phone.
But on my phone, if I click on Flash ClockworkMod Recovery, it says Unsupported Device. Hmmmmm
Any update on this?
Is ROM Manager now supporting the DNA?
I'd have put this question and bug report directly to the [PhilZ-cwm6][i9100/P] Stock Kernel+CWM6+Root+exFAT+NTFS-MS3 thread but my post count doesn't allow me to post in there yet, need 10 posts ....
Samsung Galaxy S2 - GT-I9100
Updated quickly from ICS to JB to KK over the last week or so.
CWM
I went for Philz Touch philz_touch_6.07.1-i9100.zip that gave me CWM 6.0.4.9 and the fancy purple GUI stayed for one boot but then reverted to a simpler layout though retaining the touch functions.
I also tried another Philz version which didn't boot at all.
And another philz_touch_6.43.4-i9100.zip which worked except that WiFi wouldn't switch on. That also gave the purple GUI for one boot only before reverting. Curiously this one gave me CWM 6.0.4.8
So I've gone back to the philz_touch_6.07.1-i9100.zip for now as that's the best I've found so far that works without problems for me.
My Questions are:
1. Is this normal?
2. Is there some hidden intelligence at work here changing the versions?
3. Is the CWM updating itself as I install it??
The root of your issue is this - any recovery flashed independently of the kernel on the I9100 will only persist until the next reboot. Why ? Because recovery is 'baked' into the kernel on this device & is not in its own separate partition like many other phones (where you can flash whatever recovery you want with whatever kernel you want; on the I9500/I9505 as an example). Once you reboot, your recovery will revert to that included with whatever kernel you're running.
If you want to use a particular CWM version permanently, you need to run a kernel that has it.
Excellent answer.
Baked in eh?
I'm beginning to understand but it's odd that the CWM 6.0.4.9 and the CWM 6.0.4.8 DID persist but the purple GUI front end didn't.
Either way, the CWM 6.0.4.9 I've got in there now is working happily with my ParanoidAndroid ROM and that's the main thing isn't it.
I had little issue moving up to 4.0.4 so I don't have to worry about the EMMC erase bug, but I'm realizing I have no way to get up further.
Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details.
Final edit, I found a much better solution.
It does not seem as though you can flash a upgraded kernel from the CWM interface itself and reboot reliably failed on multiple kernels.
Solution
Download mobile Odin
Download the 4.4 ROM of your choice (compatable)
Gapps too stick them all somewhere you can find them (i just leave em in downloads)
Download and flash CWM 6.0.4.4 for Kitkat i777.. no clue where I found it wasn't on XDA though.
Turn the phone off (if you reboot and don't reboot too recovery you get a loop)
Boot to recovery (if you get in a loop here pull the battery THEN boot to recovery)
Now you'll notice your not on your old version of CWM anymore.
Install your ROM and Gapps.
Boot to rom
Boot back to recovery Now your once again on a different version of CWM.
I strongly advise cleaning everything up and installing it again I had some issue until I did.
GL to anyone who finds this thread. If there seems to be a need I could rewrite it with a better title.
TheEgonSpengler said:
I had little issue moving up to 4.0.4 so I don't have to worry about the EMMC erase bug, but I'm realizing I have no way to get up further.
Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details.
Final edit, I found a much better solution.
It does not seem as though you can flash a upgraded kernel from the CWM interface itself and reboot reliably failed on multiple kernels.
Solution
Download mobile Odin
Download the 4.4 ROM of your choice (compatable)
Gapps too stick them all somewhere you can find them (i just leave em in downloads)
Download and flash CWM 6.0.4.4 for Kitkat i777.. no clue where I found it wasn't on XDA though.
Turn the phone off (if you reboot and don't reboot too recovery you get a loop)
Boot to recovery (if you get in a loop here pull the battery THEN boot to recovery)
Now you'll notice your not on your old version of CWM anymore.
Install your ROM and Gapps.
Boot to rom
Boot back to recovery Now your once again on a different version of CWM.
I strongly advise cleaning everything up and installing it again I had some issue until I did.
GL to anyone who finds this thread. If there seems to be a need I could rewrite it with a better title.
Click to expand...
Click to collapse
Always remember that when you flash a ROM, that you typically get the Recovery that is tied to the Kernel contained in that ROM. So, you flashed the Kernel, got Recovery A, then you flashed the ROM and got Recovery B. A KK Kernel can be flashed independent of a KK ROM, and will add different/additional/improved functionality, depending on the dev, but it also contains it's own Recovery in most cases.
desteele said:
Always remember that when you flash a ROM, that you typically get the Recovery that is tied to the Kernel contained in that ROM. So, you flashed the Kernel, got Recovery A, then you flashed the ROM and got Recovery B. A KK Kernel can be flashed independent of a KK ROM, and will add different/additional/improved functionality, depending on the dev, but it also contains it's own Recovery in most cases.
Click to expand...
Click to collapse
"Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details. "
Yes I know, thanks for the advice.
TheEgonSpengler said:
"Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details. "
Yes I know, thanks for the advice.
Click to expand...
Click to collapse
Oh, sorry...sounded like you expected to find the latest recoveries on JB kernels. My bad.
desteele said:
Oh, sorry...sounded like you expected to find the latest recoveries on JB kernels. My bad.
Click to expand...
Click to collapse
Nah, you just can't install the latest ROM with an older recovery.
So if you want to go up you have to do the little dance I described above. (Yes I know certain walkthroughs indicate you can do the first step in recovery, I simply found that to not be true and gained me only bootloops and the joys of reflashing stock then reinstalling a updated-er version so I could try again.)
wil this work in my situation
Quick question.. am on:
android 4.1.2
Shostock v 3.0.2
my cwm v6.0.2.7.
I want to move for a slimmer kitkat rom..