"permanent" CWM 5.0.2.6 mod : nandroid BAK & RESTORE - Galaxy Y GT-S5360 Themes and Apps

from REPENCIS custom ROM for SGY we get a new ClockworkMod recovery menu. it stays resident (though not in some tests) and replaces the "Android system recovery" menu to boot into. to quickly boot into it, use "quick boot app"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
please report back below, whether new CWM works flawlessly

mai77 said:
from REPENCIS custom ROM for SGY we get a new ClockworkMod recovery menu. it stays resident and replaces the "Android system recovery" menu to boot into. to quickly boot into it, use "quick boot app"
please report back below, whether new CWM works flawlessly
Click to expand...
Click to collapse
I've been fkaahi it via recovery but if I rebiit and go to recovery again it not replace stock dude
Sent from my GT-S5360 using xda premium

oh my golly
evanlocked said:
I've been entering it via recovery but if I reboot and go to recovery again, it did not replace "stock recov.", dude !
Click to expand...
Click to collapse
oops. that is not too good to hear. when I tested it, I had the same result: stock recovery was still active. needs fixing ...
but do the backups restore properly ?
I actually prefer the fstab from "cwm-madteam-galaxY.zip" over this one:
# mount fstype device [device2] [fstype2] [fsoptions] [fsoptions2]
/data __ext4 /dev/block/stl11 NULL rfs NULL check=no
/sdcard vfat /dev/block/mmcblk0p1
/system ext4 /dev/block/stl9 NULL _rfs NULL check=no
/cache _ext4 /dev/block/stl10 NULL rfs NULL check=no

yeah... i think it isn't permanent sir...

ow i thought we will have a permanent CWM ^_^ good job BTW

I thougt it permanent..
Sent from my GT-S5360 using XDA

It seemed like a new release. In fact some dude just changed da filename. What a scam
also cwm cannot bak / restore kernel. bug.
SGY badass Yphone

Related

[Q] CWM - Error mounting /sdcard - thanks for the help :)

I've read a few random Galaxy related topics on the SD card not mounting, but Im worried about using methods from other devices on this device.
In Rom manager premium, Flash ClockworkMod recovery was used, selected Vibrant, it said no official recovery, and asked if I had installed version 2 or 3 of CWM. I selected 2 and it said its using CWM with Rom Manager.
Well now anytime I reboot into recovery, or try to flash a rom from Rom Manager Premium it cannot mount the SD card.
I go into mounts and storage and try and mount the SD, nothing.
Is this something as simple as re-partitioning the SD? Or has something corrupted in my recovery?
BTW, XDA, you guys ROCK!! I dont post usually, cause I dont need to! Except this time
The guides and walk through here are so easy I usually never have troubles. Rooted and rom MANY different android models for work here All thanks to XDA!
***** CHECK OUT THE COOL PACKAGE I JUST RECEIVED!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
asb2106 said:
I've read a few random Galaxy related topics on the SD card not mounting, but Im worried about using methods from other devices on this device.
In Rom manager premium, Flash ClockworkMod recovery was used, selected Vibrant, it said no official recovery, and asked if I had installed version 2 or 3 of CWM. I selected 2 and it said its using CWM with Rom Manager.
Well now anytime I reboot into recovery, or try to flash a rom from Rom Manager Premium it cannot mount the SD card.
I go into mounts and storage and try and mount the SD, nothing.
Is this something as simple as re-partitioning the SD? Or has something corrupted in my recovery?
Click to expand...
Click to collapse
were you able to solve this?

[Cwm] Xiaomi Mi3

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ClockworkMod recovery is a special boot mode by Koushik Dutta that gives access to administrative functions, such as installing the base firmware (ROM), making backups, and performing a 'factory reset'. .
This Recovery have this
Features:
install zip from sdcard or sideload into system1 or system2
backup system1 and system2 individual or together into one package
much choices of where you want to restore backups to
mount and format system1 or system2
fix permissions on system1 or system2
set bootmode to system1 or system2
automatically checks for install-recovery.sh on both systems and asks you if you want to delete them
TrueDualBoot
TrueDualBoot notes:
Enabling or disabling TDB will completely wipe your data-partition. Once enabled your data partition will be VIRTUALLY split which means that both systems together can use the full space of the data-partition.
There are some things which will break TDB:
everything which removes CWM(like Xiaomi Updater App's live install)
ROM's which don't support mount_ext4.sh (I did not see any ROM without support yet)
Recovery CWM --->http://d-h.st/zAe
Recovery Stock ---> http://d-h.st/czl
Download recovery-signed-***.zip
Copy the file in the root directory of your sdcard
Use updater installation from settings/info
This work will be impossible without previous work and actual help of @m1cha
Github: https://github.com/M1cha/android_bootable_recovery/tree/cm-10.1
Hello, is this recovery for Tegra or for Snapdragon MI3?
Pepe.II said:
Hello, is this recovery for Tegra or for Snapdragon MI3?
Click to expand...
Click to collapse
Snapdragon
Well, a Tegra version would be nice
Thank you for the Snap one
I have problems when wiping cache and installing ROMs... It takes a very long time to do it.
magarto said:
I have problems when wiping cache and installing ROMs... It takes a very long time to do it.
Click to expand...
Click to collapse
Download any rayglobe rom on miui.it. I use a different rom script to flash to avoid this problem
acer73 said:
Download any rayglobe rom on miui.it. I use a different rom script to flash to avoid this problem
Click to expand...
Click to collapse
I don't understand. If I download a rom what could it help me? I need a CWM recovery for the Mi 3W without that flashing delay.
Thanks mate

[RECOVERY] 3e Recovery No Sig Check

RECOVERY 3e Recovery Modded w/ No Verification​ :highfive:
I have noticed some of you are having issues after installing a new kernel or rom, when you boot into recovery you now have 3e, which does not allow unsigned zips to be flashed. With this version of 3e it has no-verification check, now allowing you to flash whatever you want.
This zip has
1) 3e recovery modified to disable signature checking
2) disables the forced wipe after installing any update.
Click to expand...
Click to collapse
Instructions
1)Download and extract the file here
2)Use a terminal emulator or ADB shell and type.. (or you can use Root Explorer or SGSTools to mount system RW)
Code:
mount -o rw,remount /dev/block/stl9 /system
Click to expand...
Click to collapse
3)Use a file manager like Root Explorer and copy the recovery file to /system/bin and replace the one there
4)Now, reboot and you should have a modded 3e recovery with no signature verification
You can either leave the modded 3e recovery or you can now flash CWM via Rom Manager
**Just like anything else, I am not responsible if this bricks your phone, this is fairly simple, follow the guide...Do at your own risk**
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Great thread. I've extracted 3e recovery from vivo xshot. Can you explain me how disable security check? This phone don't have recovery file in system/bin but I've found a way to open bootloader
Nice App....
The file link is broken.
Hi Jawad Twam,
Very useful. I am also trying the same on my samsung galaxy S5. However, I could not download your recovery file since the link is broken. Can you please upload the file in somewhere and share the link?.
Thanks in adv,
Prakash.
Hi I get a message "operation not permitted" in the terminal emulator after typing the line. How can I fix that?

MICROMAX AQ4501 [E: Not able to mount /cache /system /data partition]

Hii there!
I am relatively new to this so I'll explain everything I know and tried so far.
I have a Micromax AQ4501 Android Phone running marshmallow. Recently My phone started acting strange like apps suddenly crashing. Yesterday, My phone ran out of juice. After charging it for a while, I switched it on and it was stuck on a boot loop. It has happened many times before. I usually fix by flashing it with stock ROM available on Micromax website. But now the case seems different. I first unlock the bootloader by going to fast boot and by using "fastboot oem unlock" then "fastboot -w" then when I restart my phone I should get a Micromax boot logo with oem unlocked written below. I then went to recovery to check something out. When I entered recovery, It showed E: cannot mount /cache (Invalid Argument). I tried to factory reset in recovery menu, it still showed the same thing. Even /system couldn't be mounted. I cannot even flash the ROM as I cannot unlock the OEM. I read few forums and many suggested to try it with different recovery. As I couldn't flash it, I used Android One Toolkit and booted into TWRP, CWM and Philz8 recovery. In all those, I got the same error message. In TWRP, the internal memory showed 0MB and in the mount selection, I the system, data and cache option were grayed out( Couldn't select them). I even tried to wipe cache method, still no luck. So From boot loop, now my phone is bricked. I have attached the images regarding this. Images 1 and 2 are of stock recovery. The remaining are from TWRP recovery.
Can someone please suggest or guide me through how to restore my phone. Here is my email just in case [email protected]
Since this is my first post I cannot share the link to my drive. Upon request, I will surely share those images.
Thankyou
Shamanth S
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Use F2FS FileSystem on your Redmi 9(Lancelot)

If you think your device get slow then you can convert your EXT4 filesystem to F2FS...
Step of work:
1.Download zip file from below link and extract it ..you got a file...
31.74 MB file on MEGA
mega.nz
2. Boot into your custom recovery and flash the file...(it is a twrp recovery.img file ....I think you know how to flash a .img file via custom recovery)
3.Reboot into recovery...
4.Then flash "F2fs-patcher.zip" via recovery (From this post)
5.You need a custom kernal which support f2fs file system.. Currently genom kernla support it..downtown it from my post and flash it via recovery.
6.Now format your data as F2FS ...
.....................................................
Step for F2Fs format:
1.Select "Wipe" tab on twrp recovery.
2.select "Advance Wipe".
3.Tick "data" and select "Repair or Change File System".
4.Select " Change File System ".
5.Select " F2FS" and swip to confirm..
.............................................................
7.Reboot and enjoy...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Which step to install the ROM? Which rom have u tested, I try some OSS rom but always get boot loop
cqkhai06 said:
Which step to install the ROM? Which rom have u tested, I try some OSS rom but always get boot loop
Click to expand...
Click to collapse
I try non oss rom..rom link..
e-0.15-q-20210310-UNOFFICIAL-lancelot.zip
Uploaded using Userge
drive.google.com
sorry boss. i have tested it. failed. if it runs in another room I think it's useless. I tried to force it to run with the strombreaker kernel, the result still failed, had to reformat the data data

Categories

Resources