I'm trying to use Rom Manager to search for Rom updates.
When i click search for updates it says i must have Clockworkmod recovery installed and when i press install it says please confirm model but Xperia play isn't on the list.
I am on official CM7 android 2.3.7 thanks
Sent from my R800i using XDA Premium App
The Xperia play is not on the list, I think this is due to it still being in development and not "stable". As for now you must do the update with the CWM recovery and install or update from zip
Even if it was official, you can't update with ROM Manager alone, since the kernel has to be updated with Fastboot.
Logseman said:
Even if it was official, you can't update with ROM Manager alone, since the kernel has to be updated with Fastboot.
Click to expand...
Click to collapse
with the latest release you can flash a new rom with the update with out fastboot, I am now able to boot into recovery with out an issue.
And how do you flash the updated kernel? There is no recovery partition, it's embedded there. You can't access the kernel from the recovery because it's the same partition.
As logseman said, Rom manager will never work on the xperia play. Unlike other devices, the xperia range has no dedicated recovery partition. Recovery is held on the boot partition, the same partition as the kernel.
As you know when you flash a partition the said partition is formatted in the process. This means flashing a recovery image would format boot partition and erase the kernel. And flashing a kernel would do the same and erase recovery. This is why recovery needs to be embedded in the kernel
Sent from my R800i using Tapatalk
Related
Searched, but couldn't find an answer to this. I rooted and installed ROM Manager so I can do a nandroid backup before installing a custom ROM. However, when I press back up in ROM Manager, it restarts and hangs/freezes on the HTC MyTouch 4g splash screen.
What am I doing wrong?
Have you flashed CWM recovery after installing Rom Manager. You must flash the recovery before you can backup/restore or install roms. I almost did that myself but luckily i read the thread concerning it again and flashed REcovery before trying to back up rom.
Yeah, I did that first and the problem remains. I just uninstalled and reinstalled ROM Manager and am about to try "backup current rom" again (unless I should reboot into recovery and back up from clockwork recovery?).
FWIW; Current recovery is ClockworkMod 2.5.1.2
anyone?
Did you ever find a solution to this problem? I just started getting exactly the same. Cant reboot manually into clockwork recovery or from Rom manager :/
If you have flashed a recovery beyond that supported by ROM manager, you will not be able to perform recovery functions from the app (i.e. backup). CW3 is required for CM7 ROMs, but will not be supported by ROM manager until the CM7 RC drops. You can still manually boot to recovery (I always Vol up when powering then select Recovery) and if you have CM7 nightly installed, it has a "reboot to recovery" option in the reboot menu.
You need CWM3 to use CM7.
neronian said:
anyone?
Click to expand...
Click to collapse
Sometimes it is necessary to flash clockwork recovery more than once before it will actually stick. Also, occasionally it will freeze on the splashscreen after a backup, but a battery pull and turning out the phone should be fine.
Sent from my HTC Glacier using XDA App
Here's what's going on:
The Clockworkmod Recovery that you can download from the Market only supports up to CyanogenMod 6.x. For CM7, you need to install Clockworkmod Recovery 3.x, but that version isn't available on the Market yet.
What this means is that you need to find the image file for a CWR 3.x on these forums and manually install it through either a terminal emulator or fastboot. The post below explains how to do it:
http://forum.xda-developers.com/showpost.php?p=10862819&postcount=3
If you flash CM7 using CWR 2.x, your phone won't boot. There's just no way around it.
hammondnav said:
Here's what's going on:
The Clockworkmod Recovery that you can download from the Market only supports up to CyanogenMod 6.x. For CM7, you need to install Clockworkmod Recovery 3.x, but that version isn't available on the Market yet.
What this means is that you need to find the image file for a CWR 3.x on these forums and manually install it through either a terminal emulator or fastboot. The post below explains how to do it:
http://forum.xda-developers.com/showpost.php?p=10862819&postcount=3
If you flash CM7 using CWR 2.x, your phone won't boot. There's just no way around it.
Click to expand...
Click to collapse
Careful with the terminology there. ROM Manager, the app you download from the Market, is a GUI front-end to the CWM recovery image, but you can download and install CWM without using ROM Manager at all. Just because you have ROM Manager installed doesn't mean that CWM recovery is also successfully installed.
TeeJay3800 said:
Careful with the terminology there. ROM Manager, the app you download from the Market, is a GUI front-end to the CWM recovery image, but you can download and install CWM without using ROM Manager at all. Just because you have ROM Manager installed doesn't mean that CWM recovery is also successfully installed.
Click to expand...
Click to collapse
Thanks for pointing that out. I didn't imply that CW ROM Manager and CW Recovery are the same thing though...
hammondnav said:
Thanks for pointing that out. I didn't imply that CW ROM Manager and CW Recovery are the same thing though...
Click to expand...
Click to collapse
You said "the Clockworkmod Recovery that you can download from the Market", and that kinda does. No biggie though.
Just an update for my problem, it turned out that clockwork recovery had corrupted for whatever reason and couldn't be reinstalled from rom manager. As I wanted to test Cm7 anyways I just ended up flashing clockwork recovery 3 manually through fastboot and its all gravy again
Sent from my Desire HD using XDA App
How to flash clockwork recovery from fastboot or fron clockwork recovery 2.51?
Sent from my SGH-T959 using XDA App
Thanks, everyone. What happened with mine, I have no idea, but I randomly opened rom manager and was greeted with an update to the recovery. So I downloaded it and voila - I can now boot into recovery and do backups, etc...
Hello!
I am sorry if this question was posted before, I just wasn't able to find it.
I'd like to know if it is possible to install ClockWorkMod recovery using ROM Manager or I have to do it in fast boot anyway?
My friend has this phone and I wouldn't like work with fasboot and things like that I've never heard about, because it seems more complex than the methods of installing a custom recovery for my Optimus One.
Again I'm sorry if it's a noob question.
As far as I know ROM Manager is not working on GT540.
pRo_lama said:
As far as I know ROM Manager is not working on GT540.
Click to expand...
Click to collapse
I think we should contact Koush and see if we can get ROM Manager to support our device, but add a warning about flashing fastboot ROMs first (as we need them for recovery to work, lets just say its our version of the Nand Lock )
you can install recovery with root tool box or you can use terminal emulator.
I use yaffs expert.I update recovery very easy
Sent from my GT540 using Tapatalk
No, you will have to use fastboot or flash_image.
Sent from my GT540 using Tapatalk
Incorrect
I flashed the LG Optimus One P500 Recovery image on ROM Manager and then restarted it via ROM Manager. It got stuck, so I flashed a LG GT540 compatible ClockworkMod Recovery image via fastboot and now I can use ROM Manager (for fixing permissions, booting into recovery, etc.)
I think you can flash Recovery ROMs via KDZ Updater
jhonnyx1000 said:
I flashed the LG Optimus One P500 Recovery image on ROM Manager and then restarted it via ROM Manager. It got stuck, so I flashed a LG GT540 compatible ClockworkMod Recovery image via fastboot and now I can use ROM Manager (for fixing permissions, booting into recovery, etc.)
I think you can flash Recovery ROMs via KDZ Updater
Click to expand...
Click to collapse
Yeah thas is how I done it, sort of. I flashed the GT540 recovery in fastboot, and then in ROM Manager I pressed menu and there was an option to override so I chose Optimus One and it worked fine.
Someone
Someone contact the developers and provide support?
I was wondering.. Now that we have CWM recovery working on our phones, why cant we use the ROM Manager app to update the recovery, flash roms or partition the sd card?
I think its because the app doesn't reconize the recovery.
Sent from my GT-I5800D using XDA App
vonuzu said:
I was wondering.. Now that we have CWM recovery working on our phones, why cant we use the ROM Manager app to update the recovery, flash roms or partition the sd card?
Click to expand...
Click to collapse
The cwm recovery we have is unofficial.. Koush, ROM Manager dev, needs to add our device to it.. Unless official cwm is released for our device, we can't use rom manager..
i just installed cm7 (Mills00013's cdma version) and was wondering if i go to the clockwork mod recovery app that was installed with it, would flashing clockworkmod recovery mess up my phone, or would it work because i heard that cm7 for xplay can use cmw recovery?
thanks in advance
bump
10 chars blah
loismustdie555 said:
i just installed cm7 (Mills00013's cdma version) and was wondering if i go to the clockwork mod recovery app that was installed with it, would flashing clockworkmod recovery mess up my phone, or would it work because i heard that cm7 for xplay can use cmw recovery?
thanks in advance
Click to expand...
Click to collapse
Old thread, but Clockwork red is normally needed to get CM7 or MIUI started, then Clockwork Blue is installed, and you re-install the ZIP for CM7/MIUI full functional. Clockwork just replaces the stock recovery files.
You can't flash clockworkmod recovery. When you open rom manager, you'll notice that there is no available recoveries for our phones. In addition to that, there is no way for the system to flash a recovery if it wanted to because there is no actual recovery partition to overwrite for our devices. The recoveries we are blessed with using now use a kernel modification to allow recovery to boot from the boot partition, which cannot be touched except with fastboot.
Sent from my R800x using XDA App
@o-l-a-v have made latest twrp 2.8.6.0 recovery with f2fs for flashing on fota partition. I publish it here bcs there is no development behind it. It works with latest cm12 nightlies
f2fs is untested report pls
All thanks to @o-l-a-v
Install through fastboot:
fastboot flash recovery
https://mega.co.nz/#!3gRwGZiK!sXMsMx1GGwUVkTCCsr8ntZekCE-o-hB4DDp6wlhVQqA
New version again
You don't need any app for flashing, use fastboot, see above
be careful if you write: fastboot flash boot you won't be able to boot
Cool, what ROMs did you test this on ?
OmarEinea said:
Cool, what ROMs did you test this on ?
Click to expand...
Click to collapse
i´m on liquid, but it works on every no stock rom,i used previous version on all your roms
i have made it bcs @championswimmer has not amami support for twrp in his recovery manager only for philz and i prefer twrp
funiewski said:
I have made latest twrp 2.8.0.1 recovery for flashing on fota partition. I publish it here bcs there is no development behind it.
Install through fastboot:
fastboot flash recovery fotaZ1cTWRP2.8.0.1.img
https://dl.dropboxusercontent.com/u/17658154/fotaZ1cTWRP2.8.0.1.img
Click to expand...
Click to collapse
How does this work? I wasn't aware that the amami had a recovery partition... How is it accessed after installation?
Rekoil said:
How does this work? I wasn't aware that the amami had a recovery partition... How is it accessed after installation?
Click to expand...
Click to collapse
That was TWRP developer @Dees_Troy who found the possibility of using fota partition on xperia devices for recovery flashing. Here: http://forum.xda-developers.com/showpost.php?p=38640389&postcount=2
You access it in usual way, Sony logo+led light press volume+. Advantage of it is that recovery persist new kernel or rom flashing, aosp and cm roms and kernels use different recoverys, a backup made with one recovery is maybe not compatible with new recovery you have just flashed. If you are flashoholic like me it is quite a pain. With recovery on fota partition it is no longer a problem. @championswimmer has made a small paid app for flashing recovery on fota, but as i wrote before it does not support twrp for amami only philz and you can flash it easily with fastboot. This works only on aosp and cm roms, if you want to overwrite recovery on fota you can either use flashtool and flash only fota, uncheck all other boxes or you can use recovery manager i mentioned earlier.
funiewski said:
Advantage of it is that recovery persist new kernel or rom flashing, aosp and cm roms and kernels use different recoverys, a backup made with one recovery is maybe not compatible with new recovery you have just flashed.
Click to expand...
Click to collapse
Nice, expirienced same problems.
Thanx @funiewski
Thanks, finally we can install a persistent recovery after flashing another boot.img. So is this a usual recovery.img or has it a special format for xperia devices?
CoolDevelopment said:
Thanks, finally we can install a persistent recovery after flashing another boot.img. So is this a usual recovery.img or has it a special format for xperia devices?
Click to expand...
Click to collapse
As you know i´m far from developer, you can read about twrp for xperia devices here: http://teamw.in/project/twrp2/144
z1c is not officially supported by teamwin, there is philz touch fota recovery images for xperia devices made by @championswimmer: http://forum.xda-developers.com/crossdevice-dev/sony/recovery-philz-touch-fotakernel-images-t2826333, downloads here:http://files.championswimmer.in/?developer=championswimmer&folder=recovery/philz
what i have done: i used teamwin recovery image for sirius, unpacked it with this tool: http://forum.xda-developers.com/showthread.php?t=2073775 (this is simple enough even for me),edited default.prop with notepad++ (model,device, fingerprint, density and so on) , changed res folder to one from twrp for z1c ( i think i use one from @[NUT] ) than repacked it.
If you can get it to work with your f2fs patch it would be great bcs it´s way over my horizon
funiewski said:
As you know i´m far from developer, you can read about twrp for xperia devices here: http://teamw.in/project/twrp2/144
z1c is not officially supported by teamwin, there is philz touch fota recovery images for xperia devices made by @championswimmer: http://forum.xda-developers.com/crossdevice-dev/sony/recovery-philz-touch-fotakernel-images-t2826333, downloads here:http://files.championswimmer.in/?developer=championswimmer&folder=recovery/philz
what i have done: i used teamwin recovery image for sirius, unpacked it with this tool: http://forum.xda-developers.com/showthread.php?t=2073775 (this is simple enough even for me),edited default.prop with notepad++ (model,device, fingerprint, density and so on) , changed res folder to one from twrp for z1c ( i think i use one from @[NUT] ) than repacked it.
If you can get it to work with your f2fs patch it would be great bcs it´s way over my horizon
Click to expand...
Click to collapse
Seems it still (not surprisingly) requires interaction from the boot image to load the recovery from the FOTA partition, making it pretty useless as you can just stick it in the boot partition in that case. Pity, this is about the only irritating thing about Xperia devices, no recovery partition.
How does it work that the phone enters recovery from FOTA partition and not kernels internal recovery?
Rekoil said:
Seems it still (not surprisingly) requires interaction from the boot image to load the recovery from the FOTA partition, making it pretty useless as you can just stick it in the boot partition in that case. Pity, this is about the only irritating thing about Xperia devices, no recovery partition.
Click to expand...
Click to collapse
as i wrote the difference is the recovery on fota partition persist flashing of roms and kernels regardless which recovery they use, thats the point for me
funiewski said:
as i wrote the difference is the recovery on fota partition persist flashing of roms and kernels regardless which recovery they use, thats the point for me
Click to expand...
Click to collapse
Yeah but it is still executing the kernel from the boot partition, so if you **** up boot partition you'll **** up recovery, so it's not much of a recovery. It just loads data from the FOTA partition. A true recovery has its own kernel.
On the TWRP webpage the xperia z2 is "officially" supported. How does this work? recovery?
paulle said:
On the TWRP webpage the xperia z2 is "officially" supported. How does this work? recovery?
Click to expand...
Click to collapse
Exactly in same way as this one.
@funiewski can i post here working boot.img for stock ROM (UB)?
with this boot.img recovery is working very well
russel5 said:
@funiewski can i post here working boot.img for stock ROM (UB)?
with this boot.img recovery is working very well
Click to expand...
Click to collapse
Do you mean fota recovery is working with stock kernel?I thought it was not possible, of course you can post it here
funiewski said:
Do you mean fota recovery is working with stock kernel?I thought it was not possible, of course you can post it here
Click to expand...
Click to collapse
Not stock, but for stock ROM with stock ramdisk (except RIC is disable)
This boot NOT have any recovery, only work with FOTA recovery
View attachment boot.zip
Hi! Thanks for this
But there seems to be several problems with it. I can boot it, but I'm unable to mount external sd-card, and backup fails. I have not had balls to try anything other than that.
Does the recovery actually work as it should on your phone?
(I'm on CM11 nightly from 21.10.. No custom kernel)
o-l-a-v said:
Hi! Thanks for this
But there seems to be several problems with it. I can boot it, but I'm unable to mount external sd-card, and backup fails. I have not had balls to try anything other than that.
Does the recovery actually work as it should on your phone?
(I'm on CM11 nightly from 21.10.. No custom kernel)
Click to expand...
Click to collapse
Are you on "stock " cm kernel? Bcs I'm on pimped kernel with liquid rom which is cm based and have no problems with ext-sd card or with backup, and it´s same for me with carbon which is aosp
funiewski said:
Are you on "stock " cm kernel? Bcs I'm on pimped kernel with liquid rom which is cm based and have no problems with ext-sd card or with backup, and it´s same for me with carbon which is aosp
Click to expand...
Click to collapse
Yes, stock CM kernel. Hm. I'll try again. Eventually try that custom kernel.