Database Users

[fully functional] CyanogenModRecovery 5.0.2.6

Preambula:
When Grif_07 compiled his CM, as a result he got a new version of the CWM.
The CWM text color changed to blue.
After the flash you will get a cyclic reboot CWM, as is the case with the installation of CWM by means of Rom Manager.
Functions not tested. So it is not responsible for the performance. Solely for testing purposes.
How to install:
Flash in recovery.
Ambula:
thanks to Grif_07 and ketut.kemujaya we have fully working CWM 5.0.2.6.
Download here.
Proof

I'll try, maybe the boot cyclic to CWM problem comes from the kernel that I could fix or you can try to flash back the boot image (boot.img) after flashing the recovery image. I have an experience even using a fixed kernel I got boot cyclic and resolved by flash back the boot image.

ketut.kumajaya said:
...that I could fix.
Click to expand...
Click to collapse
It would be great!

If only I was good at this :/
Forever living in my Galaxy Ace using XDA App

ketut.kumajaya said:
you can try to flash back the boot image (boot.img) after flashing the recovery image.
Click to expand...
Click to collapse
It does not help with bootloop on this version CWM(
P.S. flash this CWM and try to make a backup - get error when backup boot.img(
Flash back to CWM 4... - bootloop, flash boot.img - normal boot.

Lovetz said:
It does not help with bootloop on this version CWM(
P.S. flash this CWM and try to make a backup - just error(
Flash back to CWM 4... - bootloop, flash boot.img - normal boot.
Click to expand...
Click to collapse
That means you got CWM v5 ?
Forever living in my Galaxy Ace using XDA App

EmoBoiix3 said:
That means you got CWM v5 ?
Click to expand...
Click to collapse
I flash it, but got a bootloop, and flashback to CWM 4.0.0.9.

EmoBoiix3 said:
That means you got CWM v5 ?
Click to expand...
Click to collapse
No, but he can back to CWM4 without bootloop

ketut.kumajaya said:
No, but he can back to CWM4 without bootloop
Click to expand...
Click to collapse
I am preparing to compile new CM build right now. What I need to change in sources for CWM5 bootloop fixing?

Grif_07 said:
I am preparing to compile new CM build right now. What I need to change in sources for CWM5 bootloop fixing?
Click to expand...
Click to collapse
I think the fix is in kernel. Give me time to fix above CWM5 shared by Lovetz.

ketut.kumajaya said:
I think the fix is in kernel. Give me time to fix above CWM5 shared by Lovetz.
Click to expand...
Click to collapse
Ok... Then I am starting to compile... Maybe a new version of CWM will built to.

Grif_07 said:
I am preparing to compile new CM build right now. What I need to change in sources for CWM5 bootloop fixing?
Click to expand...
Click to collapse
Apply this fix
https://github.com/PabloPL/android_...mmit/46e96915a7e0459dc6b3aec04aa47329371fff44
To return from recovery, our kernel need to call reboot with recovery_done option.
(you can test this - while in CWM5, try to run reboot recovery_done, you should back to Android).

Fixed using CF-Root's CWM4 kernel (a kernel with a patched pm2.c, thanks to ilarrain) and add 2 lines command to init.rc to load jbd2 and ext4 modules.
For CyanogenMod 7.1 and advance user only for now!
How to flash:
- Boot your device into CWM recovery
- Push recovery-clockwork-5.0.2.3-galaxyace.img to your device using "adb push recovery-clockwork-5.0.2.3-galaxyace.img /tmp/" command
- Login to your device over "adb shell"
- Mount /system using "mount /dev/block/stl12 /system" command
- Flash CWM recovery using "flash_image recoveryonly /tmp/recovery-clockwork-5.0.2.3-galaxyace.img" command
- Umount /system using "umount /system" command
- Reboot your device using "reboot recovery" command to test your new CWM recovery
- Reboot your device
Not fully tested and have no enough space to try the backup/restore function
EDIT:
Recovery flashable zip added.
EDIT2:
Please try the *-fix.zip version.
Changelog:
- mount, umount, and rm scripts taken from my CF-Root-S5830 CWM to fix mount error problem
- /etc/recovery.fstab changed to mount /sd-ext partition and to fix recovery backup problem
EmoBoiix3 and Lovetz, waiting for your report
EDIT3:
The fix version almost same as clockwork-5.0.2.6 I have modified before and shared here by Grif_05, except:
- remove a garbage file
- ext4 support compiled in kernel, not as a module
- using new Samsung proprietary modules taken from DXKPD

ketut.kumajaya said:
Fixed using CF-Root's CWM4 kernel (a kernel with a patched pm2.c, thanks to ilarrain) and add 2 lines command to init.rc to load jbd2 and ext4 modules.
For CyanogenMod 7.1 and advance user only for now!
How to flash:
- Boot your device into CWM recovery
- Push recovery-clockwork-5.0.2.3-galaxyace.img to your device using "adb push recovery-clockwork-5.0.2.3-galaxyace.img /tmp/" command
- Login to your device over "adb shell"
- Mount /system using "mount /dev/block/stl12 /system" command
- Flash CWM recovery using "flash_image recoveryonly /tmp/recovery-clockwork-5.0.2.3-galaxyace.img" command
- Umount /system using "umount /system" command
- Reboot your device using "reboot recovery" command to test your new CWM recovery
- Reboot your device
Not fully tested and have no enough space to try the backup/restore function
recovery-clockwork-5.0.2.3-galaxyace.img (4.89 MB)
Click to expand...
Click to collapse
I'll flash this image and see whether backups work . Will edit this post .
EDIT: Error while backing up recovery image . Backup stops .
Edit2: This CWM doesn't support mounting /sd-ext
Edit3: Restore works though .

ketut.kumajaya said:
EDIT:
Recovery flashable zip added.
Click to expand...
Click to collapse
1. When try to make backup:
Backing up boot image...
Backing up recovery image...
Error while backing up recovery image!
Click to expand...
Click to collapse
2. After boot in to CWM /cache and /sdcard are already mounted.
3. When try to wipe cache
wiping cache....
Formatting /cache...
Cache wipe complete.
Click to expand...
Click to collapse
4. But in log:
Formatting /cache...
I:Formatting unknown device.
mount: mounting /dev/block/stl14
on /cache failed: Invalid argument
W:failed to mount /dev/block/stl14 (File exists)
rm: can`t remove '.' or '..'
rm: can`t remove '.' or '..'
Cache wipe complete.
mount: mounting /dev/block/stl14
on /cache failed: Invalid argument
W:failed to mount /dev/block/stl14 (File exists)
Click to expand...
Click to collapse

Please try the (still not sure) fixed version: recovery-clockwork-5.0.2.3-galaxyace-fix.zip

ketut.kumajaya said:
Please try the (still not sure) fixed version: recovery-clockwork-5.0.2.3-galaxyace-fix.zip
Click to expand...
Click to collapse
Ketut, I have 5.0.2.6 version. Do you need it?

Grif_07 said:
I have 5.0.2.6 version.
Click to expand...
Click to collapse
Upload here, why not?

ketut.kumajaya said:
Please try the (still not sure) fixed version: recovery-clockwork-5.0.2.3-galaxyace-fix.zip
Click to expand...
Click to collapse
Backup works fine now . Thanks a lot ketut !
I even have the CF-Root indication :3

Lovetz said:
Upload here, why not?
Click to expand...
Click to collapse
because it has bootloop and not working backup.

[Q] Cannot flash CM7 on Fascinate

I am attempting to flash CM7 stable on my stock 2.3.5 fascinate, with CwM recovery ( 2.5.1 ). But I get this error- "assert failed: getprop(re.product.device)"
Anyone know what the problem is?

You need to use the CWM in the OP of the nightly thread.
http://forum.xda-developers.com/showthread.php?t=1190668
Its an attached file.
Also IMO the nightlies are better than the stable.

imo the cm7 skang by makelegs is better than all of them!

mentose457 said:
You need to use the CWM in the OP of the nightly thread.
http://forum.xda-developers.com/showthread.php?t=1190668
Its an attached file.
Also IMO the nightlies are better than the stable.
Click to expand...
Click to collapse
Thanks, cm7 is running great, except for one problem. I cannot install the google add ons. I flashed the add ons from the cm wiki ( I cleared catch before ), and it seemed to have flashed correctly but when I reboot there is nothing. I have fixed permissions via rom manager, but still no add ons. I am running the CWM from the link you provided.

StevaB793 said:
Thanks, cm7 is running great, except for one problem. I cannot install the google add ons. I flashed the add ons from the cm wiki ( I cleared catch before ), and it seemed to have flashed correctly but when I reboot there is nothing. I have fixed permissions via rom manager, but still no add ons. I am running the CWM from the link you provided.
Click to expand...
Click to collapse
I would try mounting /system (in cwm) before flashing gapps.
Sent from my SCH-I500 using Tapatalk

it says "error mounting /system", any other solution?

mentose457 said:
I would try mounting /system (in cwm) before flashing gapps.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Says "Error mounting /system", should I install another version of cwm?

StevaB793 said:
Says "Error mounting /system", should I install another version of cwm?
Click to expand...
Click to collapse
Try holding the power button > reboot recovery > flash this kernel in recovery.. http://androtransfer.com/tk-glitch/CM7kernels/Glitch 13.1/CM7Fascinate-Glitch-V13_1-REL.zip
That should update your recovery to the latest CWM. After that, reboot into recovery again, wipe cache/dalvik cache and flash the latest GAPPS for CM7. That should get you working.

Can't seem to flash on top of CM10.2

SOLVED: MAKE SURE THAT THE ROM YOU'RE FLASHING IS FOR YOUR DEVICE!
Hello,
I can't seem to be able to flash any rom on top of my current CM10.2Nightly.
I'm trying to flash ParanoidAndroid3.99 onto my Nexus 4 and it won't let me.
It says that the ROM and GAPPS are installed successfully but when I boot
the CyanogenMod boot animation starts and CM10.2 boots.
Why?
I did the following(Using TWRP):
- FACTORY RESET
- INSTALL ROM and PA GAPPS
- WIPE CACHE & DALVIK CACHE
- REBOOT
Also, my phone connects to my computer using debug, but once it gets to the bootloader it loses connection and can't install anything.(Using Nexus Root Toolkit.)
Any help would be greatly appreciated!

Odd. Try going into advanced wipe within twrp, select system and wipe it. Then flash PA.
Sent using xda-developers app

Chromium_ said:
Odd. Try going into advanced wipe within twrp, select system and wipe it. Then flash PA.
Sent using xda-developers app
Click to expand...
Click to collapse
I'l try that now, I have since installed a new bootloader and radio.
EDIT:
I tried what you said, now I'm getting "Failed"
Mounting system...
file_getprop: failed to stat "/system/build.prop": No such file or direc
E: Error executing updater binary in zip (It goes on)
Click to expand...
Click to collapse

BlueShiftXD said:
I'l try that now, I have since installed a new bootloader and radio.
EDIT:
I tried what you said, now I'm getting "Failed"
Click to expand...
Click to collapse
Try reflashing twrp. Also redownload PA and make sure the md5 sum is correct.
Sent using xda-developers app

Chromium_ said:
Try reflashing twrp. Also redownload PA and make sure the md5 sum is correct.
Sent using xda-developers app
Click to expand...
Click to collapse
Oh god, I'm sorry haha
I made a very stupid mistake and downloaded the rom but for a Note II..
1AM, tired. haha
Sorry for wasting your time, thanks for your help!

BlueShiftXD said:
Oh god, I'm sorry haha
I made a very stupid mistake and downloaded the rom but for a Note II..
1AM, tired. haha
Sorry for wasting your time, thanks for your help!
Click to expand...
Click to collapse
Oh my, just be glad you didn't brick the phone. Be careful next time.
Sent using xda-developers app

Not booting

Hey guys question. Ever since yesterday for some reason anything i try to install will not boot. I have tried different roms and cant figure it out. any help would be appreciated. this is my only phone.

What have you tried, what model?
If you used Dirty Santa , I've seen a lot of people able to fix boot issues by following this step in his guide
me2151 said:
*****VERIZON USERS******
It has come to my attention that some users have encountered abnormally long first boot time(over 20 minutes before first time setup)
To resolve this issue:
Boot into bootloader by pulling the battery and reinserting it and holding VOL- and phugging in the phone. then typing:
Code:
fastboot flash boot boot2.img
fastboot reboot
**************
Click to expand...
Click to collapse

TGtheImmortal said:
What have you tried, what model?
If you used Dirty Santa , I've seen a lot of people able to fix boot issues by following this step in his guide
Click to expand...
Click to collapse
I have tried about 4 different roms and completely wiping and installing. the only thing that works is re flashing my stock backup i made after i rooted. I will try flashing boot2. Do roms change boot images when you flash? I am on the verizon verient.

pcwizkid1994 said:
I have tried about 4 different roms and completely wiping and installing. the only thing that works is re flashing my stock backup i made after i rooted. I will try flashing boot2. Do roms change boot images when you flash? I am on the verizon verient.
Click to expand...
Click to collapse
I'm not sure if you should flash the boot if you're on a custom rom. I am no expert so I don't want to make you brick your device.
Full wipe including formatting data when you are reinstalling custom roms?

TGtheImmortal said:
I'm not sure if you should flash the boot if you're on a custom rom. I am no expert so I don't want to make you brick your device.
Full wipe including formatting data when you are reinstalling custom roms?
Click to expand...
Click to collapse
Yes sir.

pcwizkid1994 said:
Yes sir.
Click to expand...
Click to collapse
Are you getting any errors whilst flashing custom roms?
The only thing I can think of right now would be following the steps from step 4 and reinstall and root a stock Verizon rom to see if it fixes your issue.
If that doesn't work someone else will have to come along and suggest some things.

TGtheImmortal said:
Are you getting any errors whilst flashing custom roms?
The only thing I can think of right now would be following the steps from step 4 and reinstall and root a stock Verizon rom to see if it fixes your issue.
If that doesn't work someone else will have to come along and suggest some things.
Click to expand...
Click to collapse
No nothing. Everything is flashing like it should.

Are /system and /data mounted in TWRP under mount before/after you flash a custom rom?

TGtheImmortal said:
Are /system and /data mounted in TWRP under mount before/after you flash a custom rom?
Click to expand...
Click to collapse
Now I am getting a system mount error when I try to back up my stock Rom... Will check when on break at work

TGtheImmortal said:
Are /system and /data mounted in TWRP under mount before/after you flash a custom rom?
Click to expand...
Click to collapse
Cach and data are the only things mounted

pcwizkid1994 said:
Cach and data are the only things mounted
Click to expand...
Click to collapse
/system definitely needs to be mounted before flash and after flash as well, otherwise it cannot override your stock rom.
Are you getting an error while trying to mount it? Or only during backup procedure? I was able to fix some mounting issues by simply rebooting TWRP.

TGtheImmortal said:
/system definitely needs to be mounted before flash and after flash as well, otherwise it cannot override your stock rom.
Are you getting an error while trying to mount it? Or only during backup procedure? I was able to fix some mounting issues by simply rebooting TWRP.
Click to expand...
Click to collapse
Ok so i went back into recovery and the only way I can get system to be cheacked is if I mount it as read only

TGtheImmortal said:
/system definitely needs to be mounted before flash and after flash as well, otherwise it cannot override your stock rom.
Are you getting an error while trying to mount it? Or only during backup procedure? I was able to fix some mounting issues by simply rebooting TWRP.
Click to expand...
Click to collapse
Hey. I emailed you back. Did you get my pm? Thanx

Cant mount R/W

Ok, I'm running Resurrection Remix on the Qualcomm Chipset. I have 3.2.0 R1 version of TWRP. I tried to install Xposed when it said it couldn't install because the /system was Read Only. I had tried everything... Any help would be appreciated, Thanks

codyalan said:
Ok, I'm running Resurrection Remix on the Qualcomm Chipset. I have 3.2.0 R1 version of TWRP. I tried to install Xposed when it said it couldn't install because the /system was Read Only. I had tried everything... Any help would be appreciated, Thanks
Click to expand...
Click to collapse
in the mount section unselect read only and tick mount system and flash .zip framework again

like so ..then you can flash it

Did that, like 2000 times...

do this
mount -o rw,remount /system
within the twrp terminal mode.

Francesco Franz said:
do this
mount -o rw,remount /system
within the twrp terminal mode.
Click to expand...
Click to collapse
Tried this twice, got two different responses...

codyalan said:
Tried this twice, got two different responses...
Click to expand...
Click to collapse
you need to correct mount flags in recovery.fstab within the recovery ramdisk.
---------- Post added at 08:54 AM ---------- Previous post was at 08:53 AM ----------
codyalan said:
Tried this twice, got two different responses...
Click to expand...
Click to collapse
or use another twrp recovery.
from Ressurection rom zip file works fine.

Francesco Franz said:
you need to correct mount flags in recovery.fstab within the recovery ramdisk.
Click to expand...
Click to collapse
How would one go about doing this?

codyalan said:
How would one go about doing this?
Click to expand...
Click to collapse
you could try installing systemless xposed from within magisk .....
if not your other option under advanced tab select terminal and run this command
“mount -t ext4 /dev/block/bootdevice/by-name/system /system”
* if that doesn't work get another recovery *

KevMetal said:
you could try installing systemless xposed from within magisk .....
if not your other option under advanced tab select terminal and run this command
“mount -t ext4 /dev/block/bootdevice/by-name/system /system”
* if that doesn't work get another recovery *
Click to expand...
Click to collapse
Yeah have Xposed systemless already, but command doesn't work either, not sure if any other recovery for our phones... Would formatting data fix this?

codyalan said:
Yeah have Xposed systemless already, but command doesn't work either, not sure if any other recovery for our phones... Would formatting data fix this?
Click to expand...
Click to collapse
well if your problem is mounting system formatting data wouldn't necessarily fix it ..what kind of error do you get when trying to mount system from terminal ? try posting a screenshot of recovery output and terminal output error when you try mounting system ..i don't know if there are any other recoveries for your variant
try flashing it via flash fire apk instead ..it might work

*out of interest *
i noticed you have twrp 3.2. ...the first recovery for moto e4 was 3.1...
i got this exact same error ..if you really MUST have latest recovery flash back to recovery version 3.1..
flash xposed zip ..flash back to recovery 3.2...
i went back to using recovery 3.1.... for mediatek due to a few errors in 3.2.... including error 1 above. didn't notice that before but there is definitely both a mtk and Qcom recovery version 3.1... ( old or first version ) available floating around the threads

codyalan said:
Yeah have Xposed systemless already, but command doesn't work either, not sure if any other recovery for our phones... Would formatting data fix this?
Click to expand...
Click to collapse
Instead of formatting /data, you can try going to /data/media/0/TWRP and delete the .twrps file and then boot to twrp and make sure you allow it to modify /system when it asks and try to flash Xposed again. Check for /data/media/TWRP also because sometimes you'll have both. Does this happen with other ROMs, or only RR? I don't think it has anything to do with wrong recovery mount flags.
Sent from my Moto E (4) Plus using XDA Labs

volatile1 said:
Instead of formatting /data, you can try going to /data/media/0/TWRP and delete the .twrps file and then boot to twrp and make sure you allow it to modify /system when it asks and try to flash Xposed again. Check for /data/media/TWRP also because sometimes you'll have both. Does this happen with other ROMs, or only RR? I don't think it has anything to do with wrong recovery mount flags.
Click to expand...
Click to collapse
Not sure if it happens with other ROMs, I'll try what you said and if that doesn't work I'll try another ROM

codyalan said:
Not sure if it happens with other ROMs, I'll try what you said and if that doesn't work I'll try another ROM
Click to expand...
Click to collapse
I forgot to ask if you were using the 3.2 TWRP and if it happened with 3.1 versions?
Sent from my Moto E (4) Plus using XDA Labs

volatile1 said:
I forgot to ask if you were using the 3.2 TWRP and if it happened with 3.1 versions?
Click to expand...
Click to collapse
Yeah.. should I install 3.1 and see if mounts as r/w?

codyalan said:
Yeah.. should I install 3.1 and see if mounts as r/w?
Click to expand...
Click to collapse
It can't hurt to try. It also can't hurt to get a recovery log after the failed flash with 3.2 and post it and mention your problem in the recovery thread if it doesn't happen with 3.1.
Sent from my Moto E (4) Plus using XDA Labs

Edit : Deleted