[klte][CWM Advanced Edition] PhilZ Touch - Galaxy S 5 Android Development (Snapdragon)

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
To take a screen shot, just long press outside a menu (2 sec and slightly change pressure after the delay)
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Galaxy S5 Unified (klte): International, Canada, Sprint, TMO
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/klte
Notice: ATT and VZW are locked. You must unlock them to be able to flash a recovery
Click to expand...
Click to collapse
special credits to @PlayfulGod for his unified device tree
https://github.com/playfulgod
XDA:DevDB Information
[klte][CWM Advanced Edition] PhilZ Touch, a Tool/Utility for the Samsung Galaxy S 5
Contributors
Phil3759
Version Information
Status: Stable
Created 2014-04-04
Last Updated 2014-04-16

reserved

You did notice that there was a issue with internal storage right?? It was suggested I could fix using a init file but I've not had a chance to work on it yet. If you happen to have the same issue and fix it, please share and let me know what you did.

PlayfulGod said:
You did notice that there was a issue with internal storage right?? It was suggested I could fix using a init file but I've not had a chance to work on it yet. If you happen to have the same issue and fix it, please share and let me know what you did.
Click to expand...
Click to collapse
ups, sorry, I did not notice
Link to the exact issue?
Sure if I find a fix I will share all sources. That's what I always do now, outside the touch code

Phil3759 said:
ups, sorry, I did not notice
Link to the exact issue?
Sure if I find a fix I will share all sources. That's what I always do now, outside the touch code
Click to expand...
Click to collapse
not sure of the source of the issue, but its internal sd/storage is read only. So no backups can be made to internal storage. Restoring data works fine tho.
TWRP doesnt have this issue tho, so I think its in the device repo and prolly something simple. lol
Also this is only known to work with the G900F so far. The kernel src I have on github is technically for the G900D, but its working in CWM. Just seems to be missing model specific dts files.

PlayfulGod said:
not sure of the source of the issue, but its internal sd/storage is read only. So no backups can be made to internal storage. Restoring data works fine tho.
TWRP doesnt have this issue tho, so I think its in the device repo and prolly something simple. lol
Also this is only known to work with the G900F so far. The kernel src I have on github is technically for the G900D, but its working in CWM. Just seems to be missing model specific dts files.
Click to expand...
Click to collapse
Not having the device makes it a too long debug process. Also, seems few users interested in debugging it
About write to sdcard, it is probably a selinux permission issue. At least that's what I most often encountred
I looked at your twrp sources. They use custom selinux permission files
Well, in fact they are using Samsung enforced permissions and they run this at boot:
Code:
toolbox setenforce permissive
You'll have to mount /system for that than unmount it as we have still no setenforce in busybox (they are in Pruvot custom busybox repo though)
Can you try this:
ensure you are not using the recovery.fstab file in your device tree but the fstab.qcom
adb shell:
Code:
mount /system
/system/bin/toolbox setenforce permissive
Click to expand...
Click to collapse
See if you can now access internal storage in write mode

Phil3759 said:
Not having the device makes it a too long debug process. Also, seems few users interested in debugging it
About write to sdcard, it is probably a selinux permission issue. At least that's what I most often encountred
I looked at your twrp sources. They use custom selinux permission files
Well, in fact they are using Samsung enforced permissions and they run this at boot:
Code:
toolbox setenforce permissive
You'll have to mount /system for that than unmount it as we have still no setenforce in busybox (they are in Pruvot custom busybox repo though)
Can you try this:
See if you can now access internal storage in write mode
Click to expand...
Click to collapse
Agreed, debugging w/o the device is a pita. lol
I seen that as well and had the tester try to set it. Not sure if they mounted system first, so will have them try it again to make sure. If they did, it didnt help.
I will have to check and see which fstab I have it using too. When I hear from my tester I will test all your suggestions. And thanks.
Its using the fstab.qcom.

PlayfulGod said:
Agreed, debugging w/o the device is a pita. lol
I seen that as well and had the tester try to set it. Not sure if they mounted system first, so will have them try it again to make sure. If they did, it didnt help.
I will have to check and see which fstab I have it using too. When I hear from my tester I will test all your suggestions. And thanks.
Its using the fstab.qcom.
Click to expand...
Click to collapse
Oh, you're also doing it blindly
It can be possible, but not with such a non existing feedback from users
If you think testers are just able to boot and check, try to add the needed lines to postrecoveryboot.sh (inherited from msm8960-common/recovery)
Code:
mount [BLKID] /system
/system/bin/toolbox setenforce permissive
umount /system
However, I think you need the blkid, not sure the path symlink to partition will work
You cannot just make a mount /system from postrecoveryboot.sh as the fstab file is not yet generated by recovery at that level

Phil3759 said:
Oh, you're also doing it blindly
It can be possible, but not with such a non existing feedback from users
If you think testers are just able to boot and check, try to add the needed lines to postrecoveryboot.sh (inherited from msm8960-common/recovery)
Code:
mount [BLKID] /system
/system/bin/toolbox setenforce permissive
umount /system
However, I think you need the blkid, not sure the path symlink to partition will work
You cannot just make a mount /system from postrecoveryboot.sh as the fstab file is not yet generated by recovery at that level
Click to expand...
Click to collapse
I will give that a try. thanks
img built and linked to tester(s).

PlayfulGod said:
I will give that a try. thanks
img built and linked to tester(s).
Click to expand...
Click to collapse
Thanks,
will watch your thread and wait for testers before wasting more time on it

Phil3759 said:
Thanks,
will watch your thread and wait for testers before wasting more time on it
Click to expand...
Click to collapse
Philz, its boot looping! it doesnt work at all !

leoaudio13 said:
Philz, its boot looping! it doesnt work at all !
Click to expand...
Click to collapse
Can you post a stock recovery.img please!

Phil3759 said:
Can you post a stock recovery.img please!
Click to expand...
Click to collapse
Here you are : https://drive.google.com/file/d/0B3HkAzPm36j4b05kbDNtTVA1ZnM/edit?usp=sharing

I'll test this on Friday. Verizon S5 on it's way that day.
Sent from my SCH-I545 using XDA Premium 4 mobile app

Philz,
Thank You for all you did.
Every time i'm buying a new phone, i have the pleasure to get your recovery "ready to install".
Great work, great support.

Update Alpha 6.26.1
- proper repack on stock kernel
- selinux permissive hack
Download: (flash in odin)
http://d-h.st/B20
The aim is to only see if it boots
If it boots, we're ready to fix any bugs and make it stable

Phil3759 said:
Update Alpha 6.26.1
- proper repack on stock kernel
- selinux permissive hack
Download: (flash in odin)
http://d-h.st/B20
The aim is to only see if it boots
If it boots, we're ready to fix any bugs and make it stable
Click to expand...
Click to collapse
Has this been tested on a 900H Model?

Phil3759 said:
Update Alpha 6.26.1
- proper repack on stock kernel
- selinux permissive hack
Download: (flash in odin)
http://d-h.st/B20
The aim is to only see if it boots
If it boots, we're ready to fix any bugs and make it stable
Click to expand...
Click to collapse
Gahhh! Ive been waiting for yours to test. Now im in Cambodia on business. Will test when im bak by 2mo tks again Philz
Sent from my SM-G900F using Tapatalk

leoaudio13 said:
Gahhh! Ive been waiting for yours to test. Now im in Cambodia on business. Will test when im bak by 2mo tks again Philz
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
LoL
Two months!
Hope someone else will test before

Phil3759 said:
LoL
Two months!
Hope someone else will test before
Click to expand...
Click to collapse
U dissapeared since I post u the stock recovery lol. I was wondering
Sent from my SM-G900F using Tapatalk

Related

Getting update.zip with test key working on froyo

Hi guys, it just came to my mind that test-key signed update.zip files were working back in the eclair days, so i guess the problem is the new recovery in the froyo builds needing Samsung signed files. Same problem was present on the sgs when it moved to froyo, but the devs there managed to change back to old recovery to make them work again, would be nice if someone could find a similar solution for the sg3 also... for more info search for recovery 2e 3e howto in sgs dev section... i am very busy at the moment and go for vacation on Sunday so wont find time to look into this before beginning of March, but eventually someone else could do it and just needed the hint....
Ok, to give this a bump, i need someone with a eclair rom installed and a rooted system. What i need is two files: /sbin/recovery and /sbin/recovery.sh
I think if we swap those files in jpf or whatever Froyo version we could use update.zip files again...
FadeFx
I have JK1 but in sbin directory I have only recovery file, no signs of recovery.sh
sorry, my bad, recovery.sh is part of the modified clockwork mod recovery on sgs custom kernel. also i am in conversation with hardcore about this, and eventually wed have to change the file in initramfs of the kernel... but we will see. to bad i go on vacation tomorrow and will be away for 3 weeks (going to thailand, cant wait to be there...) so i wont have time to complete this, but i will gather info and eventually gsam101 could compile a zimage with old recovery...
Ok, here is my pm conversation with hardcore, seems it can be done easily with loosing new recovery, or the complicated way keeping new recovery for system calls (CSC changes and stuff) and loading old recovery when using 3 button combo. All this is done by recovery.sh
hardcore said:
No u replace /system/bin/recovery in the rom, not kernel.
For kernel if u want to reroute to another recovery u have to use some shell script logic. Check out the initramfs source of my kernel for recovery.sh.
ok, thanx... so we would have to change the file /system/bin/recovery in the zimage´s initramfs to exchange recovery, right?
can we also put the replacement recovery into /sbin to replace the original? and if how is it then called when actually entering recovery mode so we dont enter the old recovery?
thanx Gerd
The recovery executable that comes with the ROM is actually in /system/bin/recovery
Modified kernels like mine have another CWM recovery in the kernel which is in /sbin/recovery which is compiled into the kernel's read-only initramfs.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Content of recovery.sh:
(lagfix stuff is about sztupys lagfix for the sgs and can be ignored for g3 at the moment.
This replaces stock froyo recovery (3e) with clockwork recovery, but same procedure applies to old 2e recovery.
Code:
#!/sbin/busybox sh
/sbin/busybox cp /sbin/fat.format /system/bin/fat.format
# use default recovery from rom if we have an update to process, so things like CSC updates work
# Use CWM if we simply entered recovery mode by hand, to be able to use it's features
if /sbin/busybox [ -f "/cache/recovery/command" ];
then
# if we use the original recovery it might modify the filesystem, so we erase our config, in order to avoid regeneration
# of the filesystems. The drawback is that the lagfix has to be re-applied by hand
/sbin/busybox rm /system/etc/lagfix.conf
/sbin/busybox rm /system/etc/lagfix.conf.old
rm /sdcard
mkdir /sdcard
#/sbin/rec2e &
/system/bin/recovery &
else
# TODO: CWM is a bit more intelligent, but it might fail to
/sbin/recovery &
fi;
Hope someone can make use of this to get update.zip working again...
Nobody looked into this yet? This would make much things easier for us...
Bump
....
realy hope we get some good progress and development on this thread....
sry but im just a noob and flashing is all i do right now
but if i can give any help feel free to ask
Gonna check this out. If I get OCD about this, v1.2 will be delayed.
This could be really useful. For everyone.
Sent from my Lestatious v1.2 Galaxy 3 FROYO
Lestat, i think this is info enough, if not pm me with the questions and ill do my best to find out.
FadeFx said:
Lestat, i think this is info enough, if not pm me with the questions and ill do my best to find out.
Click to expand...
Click to collapse
Alright. Will do chief. Gonna bookmark this thread so I remember tomorrow.
Sent from my Lestatious v1.2 Galaxy 3 FROYO
I have the 2.1 recovery file. . If anyone interested i think i can post if xda allows. ..
Sent from my GT-I5800 using XDA App
I was going to respond, but you responded for me: I tried to make some change to the recovery, basically to make Clockworkmod Recovery work. It seems that in Samsung's phones, the recovery is stored in /system, which is a total nonsense. I managed to get CWN almost work, but it was really buggy.
Gsam101 said:
I was going to respond, but you responded for me: I tried to make some change to the recovery, basically to make Clockworkmod Recovery work. It seems that in Samsung's phones, the recovery is stored in /system, which is a total nonsense. I managed to get CWN almost work, but it was really buggy.
Click to expand...
Click to collapse
How buggy is it?
And i noticed that's where recovery was also. I was like, Hmm. Strange.
The Dark Lestat said:
How buggy is it?
And i noticed that's where recovery was also. I was like, Hmm. Strange.
Click to expand...
Click to collapse
Like i had to flash my phone back to make it work ^^
Did u use the sgs version of cwm or did u do an own port for the g3? I guess the sgs version wont run due to different bml layout
Gsam101 said:
I was going to respond, but you responded for me: I tried to make some change to the recovery, basically to make Clockworkmod Recovery work. It seems that in Samsung's phones, the recovery is stored in /system, which is a total nonsense. I managed to get CWN almost work, but it was really buggy.
Click to expand...
Click to collapse
Hi Gsam101
I interested in compile custom recovery too.
Can You please share build configs for apollo projects?
just wanted to bump this thread, since i think we should now have devs that should be capable of doing such stuff, update.zip support is normally a must have for any android device
is this helpful in any way? -> http://forum.xda-developers.com/showpost.php?p=12244509&postcount=159
No, not yet. Clockwork needs to be ported to our device to run, which i am not able to do. If u can port it i can eventually give some hints...
i have wrote to the developer of ROM Manager APP (Clockwork Recovery) asking him to support our phone. I wrote just because i saw
Don't see your phone? Email me if you want to help me get it working!
Click to expand...
Click to collapse
on his page (http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html)
i'm not good at programming so i think if the developer replies and the answer will be yes then someone like FadeFx or anyone else who can help should contact [email protected] or [email protected]

[RECOVERY][MOD][Desire][02-Nov-2011] Clockwork 5.0.2.7.111102

First of all, this is not my work. I only compiled it.
This is the usual ClockworkMod recovery, compiled from the CM7 sources with additions/modifications by j_r0dd. What I've done is only to compile it for the HTC Desire. For details, check out the link to j_r0dd's original thread for the Nexus S.
The credits go to Koush for the recovery itself and to j_r0dd for the modifications.
j_r0dd said:
This is based on the latest CM7 source which I modified for myself. I take no credit for the recovery whatsoever, but I will take all the blame for my mods . We all know this is Koush's hard work. Just some things were driving me crazy personally. First was the confirmation menu. I really got sick of scrolling through all those "No"s just to flash something, so i changed it for me personally and just thought I would share. I also created a proper wipe menu. I got sick of some wipes in the main menu and the rest in the "advanced" menu. I made this more Amon_RA like. See the attached screenshot for my changes. That change has led to a few others by me. flash with fastboot or flash_image. THESE ARE NOT IN ROM MANAGER. Also if you have an issue with this take it up with me NOT Koush.
Click to expand...
Click to collapse
Original Nexus S thread with changelog here.
Download:
recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-bravo.zip
(old) recovery-clockwork-5.0.2.7.111027-j_r0dd_mod-bravo.zip
Change log:
02-Nov-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo again (some bugfixes)
Added option to wipe cache partition and dalvik cache at the same time
27-Oct-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo (support for internal/external sdcard in backup/restore)
07-Oct-2011 (v5.0.2.6):
Rearranged wipe menu to avoid accidental factory wipes
Added "Reboot Bootloader"
Moved SD Card partitioning into a function of its own for both int/ext SD card
Merged 5.0.2.6 sources from CM7 repo
Added a menu choice of ext2/ext3/ext4 when partitioning SD card
25-Sep-2011 (v5.0.2.3):
Updated to j_r0dd's 5.0.2.3 version. Currently no changes made by myself.
17-Jun-2011 (v4.0.0.5):
Moved the "Wipe data/factory reset" to the bottom of the wipe menu to reduce the risk of accidental factory wipes.
19-Jun-2011 (v4.0.0.5):
Added "Reboot bootloader" option in advanced menu.
Added the ext4 modifications kindly supplied by roalex. Needs testing. Please make a proper nandroid backup with a proven working recovery version before trying this.
20-Jun-2011 (v4.0.0.5):
Added "Show log" in the advanced menu. This can help when reporting errors here. Use it.
21-Jun-2011 (v4.0.0.5.z110621):
Reverted and correctly added roalex's ext4 additions.
Modified recovery.fstab for ext4 support on some devices.
23-Jun-2011 (v4.0.0.5.z110623):
Removed NULL ext3 in recovery.fstab to hopefully get ext4 working properly.
06-Jul-2011 (v4.0.0.5.z110706):
Added "Advanced backup". Now you can backup/restore individual partitions.
Some other commits from other devs in github
Changed file limit from 10000 to 50000 in unyaffs. Should help when restoring large data partitions fails.
17-Jul-2011 (v4.0.1.0.110717):
Rebased completely on j_r0dd's 4.0.1.0 source and removed roalex's ext4 additions, as it wasn't working for everyone. Now trying with the original ext4 support which is included in CWM.
20-Jul-2011 (v4.0.1.4.110720):
Bug fixes
Disclaimer
These recoveries are compiled using the latest commits from koush, j_r0dd and others. That means they haven't been thoroughly tested and might have minor/major issues. I take no responsibility for any damages this thing might cause, but most things should work as intended. If you want something guaranteed to work, I think you should stick with one of the older versions.
Source code available here.
it works... thank you
suiller said:
it works... thank you
Click to expand...
Click to collapse
Superb! I'll change the OP to confirmed then.
bit hesitant to flash this, had a few usb bricks from recent clockworks. reckon some people who have flashed it could nandroid backup then restore and check it all works?
sjknight413 said:
bit hesitant to flash this, had a few usb bricks from recent clockworks. reckon some people who have flashed it could nandroid backup then restore and check it all works?
Click to expand...
Click to collapse
Well, like I said, I can't guarantee that it works, especially since I have no Desire to test it on. I've used j_r0dd's source which is based on Koush's source for the official CM7 3.2.0.0 ClockworkMod recovery. It might work, or it might not work. Testing it is up to each person.
zyonee said:
Well, like I said, I can't guarantee that it works, especially since I have no Desire to test it on. I've used j_r0dd's source which is based on Koush's source for the official CM7 3.2.0.0 ClockworkMod recovery. It might work, or it might not work. Testing it is up to each person.
Click to expand...
Click to collapse
dont get me wrong, i didnt mean any disrespect looks like you have done good work! but i have only had my desire 4 days and already had 2 usb bricks! will probably test in a couple of days
sjknight413 said:
dont get me wrong, i didnt mean any disrespect looks like you have done good work! but i have only had my desire 4 days and already had 2 usb bricks! will probably test in a couple of days
Click to expand...
Click to collapse
Don't worry about it, I wasn't offended in any way. I'm wondering though if the USB bricks are caused by flashed (.img) recoveries. As I remember it, USB bricks were common with the earliest attempts to run recoveries by uploading the recovery binary to the phone's RAM while having to keep it plugged in to the computer.
well i know i got the usb bricks whilst restoring nandroids when my phone wasn't plugged in. that help in any way?
sjknight413 said:
well i know i got the usb bricks whilst restoring nandroids when my phone wasn't plugged in. that help in any way?
Click to expand...
Click to collapse
Maybe your misc partition got overwritten with garbage. In my opinion, nandroid shouldn't touch this partition. The USB brick issue is usually caused by a corrupt misc partition.
Sent from my Nexus S using Tapatalk
yeah i dont really know why it does, its easily fixable by reflashing the mtd0.img file generated from your cid and rom version though, its just a massive nuisance!
sjknight413 said:
yeah i dont really know why it does, its easily fixable by reflashing the mtd0.img file generated from your cid and rom version though, its just a massive nuisance!
Click to expand...
Click to collapse
You should check your nandroid backup folder. If there's a misc.img or something like it, maybe you should move that file elsewhere. That way, nandroid shouldn't overwrite your misc (mtd0) partition. I'm only guessing that it does handle that partition.
Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.
teorouge said:
Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.
Click to expand...
Click to collapse
No idea, not using sd-ext in any of my phones.
teorouge said:
Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.
Click to expand...
Click to collapse
I'd like to know this too. Can anyone who's upgraded to this version of 3.2.0.0 let us know their findings?
Jameswgm said:
I'd like to know this too. Can anyone who's upgraded to this version of 3.2.0.0 let us know their findings?
Click to expand...
Click to collapse
It'll probably behave the same way, seeing as this one only changes the menus, I think.
Updated OP to version 4.0.0.0.
Thanks, please see http://forum.xda-developers.com/showpost.php?p=14598355&postcount=357 .
You should mod 3.1.0.1, no later CWM worked ok.
teorouge said:
Thanks, please see http://forum.xda-developers.com/showpost.php?p=14598355&postcount=357 .
You should mod 3.1.0.1, no later CWM worked ok.
Click to expand...
Click to collapse
Yeah, I got that even on my Nexus S.. I'm just cloning & compiling. Got no idea how to downgrade to an earlier version. Limited programming skills.
I fixed the SD card mounting bug. Please re-download 4.0.0.0.
Still buggy. Each time you leave a file list, you'll need to "adb shell umount /sdcard" from your computer. Looking into it.
Added back the 3.2.0.0 version in the OP so you won't have the /sdcard mounting issue. Hopefully it can be resolved soon, so we can start using the 4.0.0.0 version. Sorry for the inconvenience.

[RECOVERY][MOD][DesireHD][02-Nov-2011] Clockwork 5.0.2.7.111102

First of all, this is not my work. I only compiled it.
This is the usual ClockworkMod recovery, compiled from the CM7 sources with additions/modifications by j_r0dd. What I've done is only to compile it for the HTC Desire HD. For details, check out the link to j_r0dd's original thread for the Nexus S.
The credits go to Koush for the recovery itself and to j_r0dd for the modifications. I haven't been able to test it on the HTC Desire HD, since I don't own one.
j_r0dd said:
This is based on the latest CM7 source which I modified for myself. I take no credit for the recovery whatsoever, but I will take all the blame for my mods . We all know this is Koush's hard work. Just some things were driving me crazy personally. First was the confirmation menu. I really got sick of scrolling through all those "No"s just to flash something, so i changed it for me personally and just thought I would share. I also created a proper wipe menu. I got sick of some wipes in the main menu and the rest in the "advanced" menu. I made this more Amon_RA like. See the attached screenshot for my changes. That change has led to a few others by me. flash with fastboot or flash_image. THESE ARE NOT IN ROM MANAGER. Also if you have an issue with this take it up with me NOT Koush.
Click to expand...
Click to collapse
Original Nexus S thread with changelog here.
Download:
recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-ace.zip
(old) recovery-clockwork-5.0.2.7.111027-j_r0dd_mod-ace.zip
Change log:
02-Nov-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo again (some bugfixes)
Added option to wipe cache partition and dalvik cache at the same time
27-Oct-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo (support for internal/external sdcard in backup/restore)
07-Oct-2011 (v5.0.2.6):
Rearranged wipe menu to avoid accidental factory wipes
Added "Reboot Bootloader"
Moved SD Card partitioning into a function of its own for both int/ext SD card
Merged 5.0.2.6 sources from CM7 repo
Added a menu choice of ext2/ext3/ext4 when partitioning SD card
25-Sep-2011 (v5.0.2.3):
Updated to j_r0dd's 5.0.2.3 version. Currently no changes made by myself.
17-Jun-2011 (v4.0.0.5):
Moved the "Wipe data/factory reset" to the bottom of the wipe menu to reduce the risk of accidental factory wipes.
19-Jun-2011 (v4.0.0.5):
Added "Reboot bootloader" option in advanced menu.
Added the ext4 modifications kindly supplied by roalex. Needs testing. Please make a proper nandroid backup with a proven working recovery version before trying this.
20-Jun-2011 (v4.0.0.5):
Added "Show log" in the advanced menu. This can help when reporting errors here. Use it.
21-Jun-2011 (v4.0.0.5.z110621):
Reverted and correctly added roalex's ext4 additions.
Modified recovery.fstab for ext4 support on some devices.
06-Jul-2011 (v4.0.0.5.z110706):
Added "Advanced backup". Now you can backup/restore individual partitions.
Some other commits from other devs in github
Changed file limit from 10000 to 50000 in unyaffs. Should help when restoring large data partitions fails.
17-Jul-2011 (v4.0.1.0.110717):
Rebased completely on j_r0dd's 4.0.1.0 source and removed roalex's ext4 additions, as it wasn't working for everyone. Now trying with the original ext4 support which is included in CWM.
20-Jul-2011 (v4.0.1.4.110720):
Bug fixes
Disclaimer
These recoveries are compiled using the latest commits from koush, j_r0dd and others. That means they haven't been thoroughly tested and might have minor/major issues. I take no responsibility for any damages this thing might cause, but most things should work as intended. If you want something guaranteed to work, I think you should stick with one of the older versions.
Source code available here.
Thanks dude,
if i use sense roms, this will still work fine right?
DubelBoom said:
if i use sense roms, this will still work fine right?
Click to expand...
Click to collapse
I don't know of any issues when flashing Sense ROMs with ClockworkMod recoveries, but then I'm also not using Sense ROMs.
SD card is not recognized any fix for this ?
Sent from my Desire HD using XDA Premium App
Thanks..Flash it at once!
Sent from my HTC Sensation Z710e using XDA App
p2pjack said:
SD card is not recognized any fix for this ?
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
Correct, because of a bug in the ClockworkMod 4.0.0.0 source code. Keep an older recovery handy if you're testing this.
You can get around the bug. Each time you get the error, you can "adb shell umount /sdcard" from your computer. It's annoying, and hopefully we can find a solution for it soon.
p2pjack said:
SD card is not recognized any fix for this ?
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
+1 on this Had to return to 3.2.0.0
I edited 4.0.0.2, adding j_r0dd's mods and compiled it. Works well on Nexus One and Nexus S. No more sdcard mounting bug, it's been fixed. Can't test it on any other models myself. Updated first post of this thread.
how do you install this?
Doo Doo said:
how do you install this?
Click to expand...
Click to collapse
Through terminal emulator:
type
su
flash_image recovery /sdcard/nameofyourrecovery.img
dirk089 said:
Through terminal emulator:
type
su
flash_image recovery /sdcard/nameofyourrecovery.img
Click to expand...
Click to collapse
thanks for the info
does this work & are you using it ?
Doo Doo said:
thanks for the info
does this work & are you using it ?
Click to expand...
Click to collapse
since few minutes
and it works great.
also the sd-card mount !
dirk089 said:
since few minutes
and it works great.
also the sd-card mount !
Click to expand...
Click to collapse
Glad to hear it!
Sent from my Nexus S using Tapatalk
will it work on EXT4 roms?
Doo Doo said:
will it work on EXT4 roms?
Click to expand...
Click to collapse
That's a good question.
I just tried flashing it through terminal on my ext4 ROM and I just get a "scanning partitions" error.
when i try to flash it says image not found why when its on my sdcard
SD card working here to thank you zyonee
Sent from my Desire HD using XDA Premium App
p2pjack said:
SD card working here to thank you zyonee
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
That's the work of Koush, I think. Glad it works, though.
Sent from my Nexus S using Tapatalk
Doo Doo said:
when i try to flash it says image not found why when its on my sdcard
Click to expand...
Click to collapse
Try renaming it to something short like recovery.img.
Sent from my Nexus S using Tapatalk

SM-T237P Stock Rooted ROM - MOVING TO THE DEV SECTION

DOWNLOAD LINKS REMOVED - MOVED TO THE DEV SECTION!!! YAY!!
LINK : http://forum.xda-developers.com/tab...ooted-odexed-2015-04-11-t3079083#post60044636
Thanks for all the support
MOVED -
Looking forward to trying this out. Thank you for the work.
VerneVerne said:
Looking forward to trying this out. Thank you for the work.
Click to expand...
Click to collapse
Check your PM
Stock rooted boots but WiFi appears to be broken. This was with a clean install. I will try stock debloated either tonight or tomorrow.
VerneVerne said:
Stock rooted boots but WiFi appears to be broken. This was with a clean install. I will try stock debloated either tonight or tomorrow.
Click to expand...
Click to collapse
I forgot to ask on PM. Did you try forget and try your WiFi connection again? Like I said might be kernel related or system/etc/wifi files.
Root access / 3G/4G LTE work?
Can someone pull a logcat while trying to connect to WiFi.
g_ding84 said:
I forgot to ask on PM. Did you try forget and try your WiFi connection again? Like I said might be kernel related or system/etc/wifi files.
Root access / 3G/4G LTE work?
Click to expand...
Click to collapse
I'm sorry but I already went back to stock. I did try the forget Wi-Fi password trick but still didn't help.
The limited time I was using it everything checked out good...root, 3g, 4g(very spotty for me, but it did connect).
My data is very limited so Wi-Fi is important for me. I will try the debloated tomorrow though. Do you think it will have the same Wi-Fi issue? If so, I will grab a logcat if no one else gets to it before me. I'm going to have to wait until tomorrow afternoon unfortunately though.
@VerneVerne sounds good. It might have the same issues.....also see if you can pull /cache/recovery/last_log after you flash the ROM. That can give me some insight on if I messed up the updater-script. (Invalid arguments)
g_ding84 said:
@VerneVerne sounds good. It might have the same issues.....also see if you can pull /cache/recovery/last_log after you flash the ROM. That can give me some insight on if I messed up the updater-script. (Invalid arguments)
Click to expand...
Click to collapse
Ahhh, you say updater script. Come to think of it there was something mentioned of a script being outdated and needing to be updated while flashing the rom. I'll be sure to find out what that says exactly when I can get back to testing later.
VerneVerne said:
Ahhh, you say updater script. Come to think of it there was something mentioned of a script being outdated and needing to be updated while flashing the rom. I'll be sure to find out what that says exactly when I can get back to testing later.
Click to expand...
Click to collapse
I need a new update-binary. It is legacy but still should work. Philz switches to a legacy environment for compatibility..... That a huge plus with using philz recovery.
Its outdated because it uses set_perm command. Newer binaries use set_metadata (for selinux support). I might have too cook up a newer script with a newer binary.
Huge thanks to @moonbutt74 - it was an updater-script issue. I missed a symlink command. I added that in and WiFi should work now. Just need the stock kernel pulled from the T237P if someone would be so kind.
Code:
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
and send me the kernel img....please.
if not - drop /msm_sdcc.1/by-name/boot and use the mmcblk0p(xx) use xx as the block number
G,
https://www.androidfilehost.com/?fid=95916177934549973
:good:
m
@moonbutt74. The man. Ty
@VerneVerne - lead tester
@mysticjp - tester
@dave5777 - tester
@trevortf - tester
@amphillips82277 - tester
@moonbutt74 - custom recovery (philz) and support (various tips and help)
Guys check your PM. I uploaded a fixed version to you guys for testing. If all is well, this thread can be moved to the Dev section and public download links.
Everyone else following this thread, please thank the testers above, without them there wouldn't be a ROM. :highfive::good:
Thank you! I was about to throw this thing in my box of shame next to my gtab2 ;p
Download links available for public release.
Just need someone to confirm init.d is working correctly.?
After that we can call this stable and move this thread to the Dev section.
g_ding84 said:
Download links available for public release.
Click to expand...
Click to collapse
:good:
Good to hear that we have recovery and custom rom for T237P!
I flash recovery, and download firmware now.
Rooted yesterday so far so good... Just need that free Hotspot going.
There are a few 3rd party apps that will do the job in the mean time.

Team Win Recovery Project for the LG G Pad X 8.0 (V521, V522, V525)

[RECOVERY] TWRP 2.8.7.0 - TeamWin Recovery Project
TeamWin is proud to present TWRP v3.0.2.0 for the LG G Pad X 8.0 (V521, V522, V525)
Youtube video: http://www.youtube.com/watch?v=RIvWVS_Rkxo
Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2
Introduction:
Team Win Recovery Project or twrp for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
See changelog below for new features
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/omnirom/android_bootable_recovery
Gerrit for TWRP Official Device Configs - http://gerrit.twrp.me
Gerrit Instance - http://gerrit.omnirom.org
If you have made your own twrp build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
b3 Device Config: https://github.com/Shabbypenguin/android_device_lge_b3
DOWNLOAD:
http://www.t2h-gh0st-is-garbage.xyz/TWRP-V521-3.0.2.0.img
Support:
Only ask for support in the chat for general twrp issues, not device specific problems.
Click http://webchat.freenode.net/?channels=twrp for live support or join us in #twrp on Freenode IRC servers[/QUOTE]
8/21/2016
updated the link, same file name fixed internal storage mount and a few other minor issues
8/20/2016 - initial release
Youll need to use flashify to flash the image after rooting. this should work on all b3 models, aka lg v525, v521 etc
For the test version i had of 2.7.8.0 i had to do this, since i have already done it i cant confirm if you need to on 3.0.2.0 or not. ----- data/internal storage wont mount/work until you go to wipe> format data and format without encryption reboot recovery and then do a factory reset. this will wipe your ENTIRE device but allow you to use twrp normally.
Thanks a lot, i'll flash it soon. Any idea if xposed would work on this device?
shabby is the man
emilyrugburn said:
Thanks a lot, i'll flash it soon. Any idea if xposed would work on this device?
Click to expand...
Click to collapse
I dont use or follow xposed development (my last 3 personal phones werent even rooted) i dont see any reason why it wouldnt we have twrp as well as stock kdz so you can mess things up pretty bad and still recover.
shabbypenguin said:
I dont use or follow xposed development (my last 3 personal phones werent even rooted) i dont see any reason why it wouldnt we have twrp as well as stock kdz so you can mess things up pretty bad and still recover.
Click to expand...
Click to collapse
Xposed looks to work just fine. Thanks again
emilyrugburn said:
Xposed looks to work just fine. Thanks again
Click to expand...
Click to collapse
glad to hear it
i grabbed the tablet as it was a great deal and ive loaded it up with apps for my daughter who is the primary user for it so i wont be doing much with it but its good to see the community finally taking off .
Please add the installation instructions - http://www.xda-developers.com/how-to-install-twrp/
Also, add a 'Donation' segment if you're interested in accepting them
avishah395 said:
Please add the installation instructions - http://www.xda-developers.com/how-to-install-twrp/
Also, add a 'Donation' segment if you're interested in accepting them
Click to expand...
Click to collapse
there is a donate to me button under my name and those instructions dont apply to this device. i specify how to use this in the second post.
IF POSSIBLE, please add your thread to our device ET so we can get a full thread eventually - http://forum.xda-developers.com/t/lg-g-padx
Also, update the version number in the title. I was able to get TWRP working, you do still need to wipe to clear the encryption (it says it does this in red). Then, you can continue using it normally.
avishah395 said:
IF POSSIBLE, please add your thread to our device ET so we can get a full thread eventually - http://forum.xda-developers.com/t/lg-g-padx
Also, update the version number in the title. I was able to get TWRP working, you do still need to wipe to clear the encryption (it says it does this in red). Then, you can continue using it normally.
Click to expand...
Click to collapse
i was on that page and clicked new thread, not sure why it didnt work or how exactly you are supposed to do it as that logically made the most sense to me.
i know you need to wipe to clear the encryption, but i wasnt sure if you needed to clear the encryption in order to use twrp properly as i had already done it on an older version. good catch on the version number
shabbypenguin said:
i was on that page and clicked new thread, not sure why it didnt work or how exactly you are supposed to do it as that logically made the most sense to me.
i know you need to wipe to clear the encryption, but i wasnt sure if you needed to clear the encryption in order to use twrp properly as i had already done it on an older version. good catch on the version number
Click to expand...
Click to collapse
I'm not entirely sure about clearing encryption to use TWRP. I know when I did it, TWRP functioned normally.
Ill ask XDA about the ET, maybe it has a second page that isn't showing.
UPDATE: To add our tag, look for "Edit Tags" (CTRL+F) or use this URL http://forum.xda-developers.com/threadtag.php?t= {add thread id - yours is 3443944}. Our ET/tag is "lg-g-padx"
If it could be made as flashable .dz or .tot, that would be excellent.
mingkee said:
If it could be made as flashable .dz or .tot, that would be excellent.
Click to expand...
Click to collapse
as previously mentioned, only people who have leaked lg tools can make flashable tots etc. i spent hours researching it, testing out different methods and reflashing stock kdz a bunch of times.
the only way i could streamline this is if i submitted this to be made official so once rooted you could use twrp manager, but the submission process isnt exactly one that is a lot of fun to do. especially considering with flashify you only have to do like 3 clicks anyways.
Got something for you, shabbypenguin.
My intitial partitions-being-unmountable-due-to-unknown-error-150 likely because of faulty .tot file. the 1.4GB one works. of course after flashing 10c
Device still reports as LG V510 via MTP. Not a huge deal.
In TWRP file browser, internal storage is mounted as /emmc ?!
SD Card will not mount, log attached. Complete. /external_sd is not /dev/block/mmcblk0p1. It's /dev/block/mmcblk1p1 I manually mounted it there and it works.
Some errors about /sdcard as well. Probably cant mount /data/media/0 there. is my guess.
OTG does not mount properly as well, in recovery it shows up at /dev/block/sda1, recovery's fstab points at /usb-otg?
Was gonna put the output of mount/df from recovery and android but thought that wouldn't help.
eriklion said:
Got something for you, shabbypenguin.
My intitial partitions-being-unmountable-due-to-unknown-error-150 likely because of faulty .tot file. the 1.4GB one works. of course after flashing 10c
Device still reports as LG V510 via MTP. Not a huge deal.
In TWRP file browser, internal storage is mounted as /emmc ?!
SD Card will not mount, log attached. Complete. /external_sd is not /dev/block/mmcblk0p1. It's /dev/block/mmcblk1p1 I manually mounted it there and it works.
Some errors about /sdcard as well. Probably cant mount /data/media/0 there. is my guess.
OTG does not mount properly as well, in recovery it shows up at /dev/block/sda1, recovery's fstab points at /usb-otg?
Was gonna put the output of mount/df from recovery and android but thought that wouldn't help.
Click to expand...
Click to collapse
thanks for the info, my sdcard is provisioned as internal storage so it doesnt show up as a micro sdcard in recovery, not sure how i got it so mixed up but ill push an updated version out later tonight
what do you mean it shows up as emmc?
shabbypenguin said:
thanks for the info, my sdcard is provisioned as internal storage so it doesnt show up as a micro sdcard in recovery, not sure how i got it so mixed up but ill push an updated version out later tonight
what do you mean it shows up as emmc?
Click to expand...
Click to collapse
When you're browsing for things to flash/etc, theres the path/directory /emmc, you enter it and it contains things that are supposed to be in /data/media/0
Confused About Install Instructions
shabbypenguin said:
8/20/2016 - initial release
Youll need to use flashify to flash the image after rooting. this should work on all b3 models, aka lg v525, v521 etc
For the test version i had of 2.7.8.0 i had to do this, since i have already done it i cant confirm if you need to on 3.0.2.0 or not. ----- data/internal storage wont mount/work until you go to wipe> format data and format without encryption reboot recovery and then do a factory reset. this will wipe your ENTIRE device but allow you to use twrp normally.
Click to expand...
Click to collapse
I have flashed TWRP many times in the past on many devices. Yet for the 1st time after using Flashify, it obviously did not install properly as it didn't mount internal storage on this pad. It doesn't even recognize show that there's anything available in internal storage to back up to. Frankly, I don't understand your above instructions on how to property install it.
Typing clear instructions would be greatly appreciated as I can't use it. But do appreciate the time you put into it and will make a donation once this has been fixed.
pressmoon said:
I have flashed TWRP many times in the past on many devices. Yet for the 1st time after using Flashify, it obviously did not install properly as it didn't mount internal storage on this pad. It doesn't even recognize show that there's anything available in internal storage to back up to. Frankly, I don't understand your above instructions on how to property install it.
Typing clear instructions would be greatly appreciated as I can't use it. But do appreciate the time you put into it and will make a donation once this has been fixed.
Click to expand...
Click to collapse
you need to go to wipe > format data. your devices data is by default encrypted and twrp cant decrypt it. once youve wiped data, reboot recovery and then do a factory reset. your device will boot and function as normal and youll have a fully working twrp
eriklion said:
When you're browsing for things to flash/etc, theres the path/directory /emmc, you enter it and it contains things that are supposed to be in /data/media/0
Click to expand...
Click to collapse
ive uplaoded a version taht fixed that, but im unable to mount external_sd or usb otg. sda1 doesnt show up for me in /dev/block and even manually trying to mount sdcard to mccblk1p1 fails due to an invalid arguement, how did you mount yours?

Categories

Resources