Related
This is the latest Sprint Rom based on the latest RUU leak with A2SD support (I used Darktremor A2SD 2.7 since it was easy to add it).
I have verified that A2SD is working as I downloaded and installed a couple of programs from the market. The programs are being stored in /system/sd/app.
Here's the link: http://www.darktremor.info/files/2.1/2.1-ruu-a2sd-signed.ziphttp://www.darktremor.info/files/2.1/sprintstock-21-a2sd-b-signed.zip
This one now has adb rooted (thanks to nfinitefx45 for his assistance) and does flash (heard complaints on the symlink issue...never sure what causes that, but ended up starting over and porting the files from the previous build).
This is for those people who want to keep with the stock installation but want the addition of A2SD. If you want a customized look, faster performance and A2SD support, I suggest a custom rom. Fresh 2.1.2 or FreshToast is a good one to use.
Note: It will not affect recovery.
Enjoy and I'll answer any questions you may have (if I can answer them).
did you manually edit the init.rc? and you should mention that this is a ROM, not an RUU
tkirton said:
This is the latest Sprint RUU leak with A2SD support (I used Darktremor A2SD 2.7 since it was easy to add it).
This is definitely an RUU as when I go into adb shell, I get the dollar sign as a prompt rather than the pound sign...I'm pretty certain it is not rooted.
.
Click to expand...
Click to collapse
<<<snip>>>
This makes no sense at all.
Good point about the Rom vs RUU. Edited to correct.
As for the init.rc. Mainly it was init.rc edit.
regaw_leinad said:
did you manually edit the init.rc? and you should mention that this is a ROM, not an RUU
Click to expand...
Click to collapse
Don't look at me...that's what I'm getting. Doesn't make much sense to me, either. I just know if I do adb shell, I don't have root access. But A2SD works fine.
I went ahead and released it since the goal was to get A2SD working...and I did that. Everything else is for a Rom developer.
wctom said:
<<<snip>>>
This makes no sense at all.
Click to expand...
Click to collapse
tkirton said:
Don't look at me...that's what I'm getting. Doesn't make much sense to me, either. I just know if I do adb shell, I don't have root access. But A2SD works fine.
I went ahead and released it since the goal was to get A2SD working...and I did that. Everything else is for a Rom developer.
Click to expand...
Click to collapse
Thanks, I'll just use your boot image for RegawMOD 2.5. saves me a few minutes
working perfectly all apps installed and 132 megs still open internal
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
sandboxlove said:
is it a general consensus that if you want to run a2sd successfully you should use a class6? i currently have a class4
Click to expand...
Click to collapse
right now, I switched back to my class 4 and its working great
nvmchars....
tkirton,
here is your exact rom that's in your first post, but I deodexed it. You can add that to the OP if you'd like.
Everyone else, here it is too:
http://www.4shared.com/file/Fm3pXapi/21-ruu-a2sd-deodexed-signed.html
I have not tested it, but it should work fine. Deodexed /system/app and /system/framework
sandboxlove said:
i just want to be clear...this is the latest sprint leak? you seriously deodexed the whole thing?
i thought vince was crazy for trying, your completely BANANNAS
Click to expand...
Click to collapse
yeah, i thought I'd post it in here. Didn't think since it's the same thing as he posted but deodexed that I should make another thread.
and yes, the latest sprint leak. you should test this. I can't right now.
Oooh...cool. Enhancements. I like enhancements.
regaw_leinad said:
tkirton,
here is your exact rom that's in your first post, but I deodexed it. You can add that to the OP if you'd like.
Everyone else, here it is too:
http://www.4shared.com/file/Fm3pXapi/21-ruu-a2sd-deodexed-signed.html
I have not tested it, but it should work fine. Deodexed /system/app and /system/framework
Click to expand...
Click to collapse
tkirton said:
Oooh...cool. Enhancements. I like enhancements.
Click to expand...
Click to collapse
Well, I like your work, so that's for you
did anyone test it out to make sure it boots?
Sorry to be such a noob, but what is "deodexed" a ROM mean?
regaw_leinad said:
tkirton,
here is your exact rom that's in your first post, but I deodexed it. You can add that to the OP if you'd like.
Everyone else, here it is too:
http://www.4shared.com/file/Fm3pXapi/21-ruu-a2sd-deodexed-signed.html
I have not tested it, but it should work fine. Deodexed /system/app and /system/framework
Click to expand...
Click to collapse
Well I flashed it and stuck on the HTC screen. Flashed the non deodexed version and loads fine.
So apparently i f***ed up deodexing lol. I guess that ROM that I did wont work..
well just loving this rom, but one question, can we get a updated boot.img with the adb enabled for access as root?
Now that the A2SD stuff is behind me, I'll take a look at that. Flipzmode or Toastcfh may be able to shed some light on how you get this image rooted correctly, especially Flipz since he's using the latest leak for Fresh 2.1.1.
The original goal was to get A2SD working on a stock rom, which I did....but it is rather annoying that it isn't rooted (or fully rooted).
Damage said in his point that it was rooted, but I got the same thing you did...no root when doing adb.
I'll talk to Flipz or Toast and see if they can point me in a direction to go.
nfinitefx45 said:
well just loving this rom, but one question, can we get a updated boot.img with the adb enabled for access as root?
Click to expand...
Click to collapse
well this is a piece from some of the reading I've been doing I beleice this needs to be done with in the boot image. I dont know if this will help in your research,
-------------------------
You also need to modify the ROM update script to change the default permissions for /system/bin/su so it can be used to elevate privileges to root. The script is in $WKD/dst/META-INF/com/google/android/update-script. Open it in your favorite editor and find the line starting with set_perm 0 2000 0550 SYSTEM:etc/init.goldfish.sh and after it add the following set_perm 0 0 04755 SYSTEM:bin/su
=======================
Hi tkirton,
Nice job on this and thanks for all your hard work on everything! I am also wondering what dedoxed means? Is it like where application data is also stored on the SD card instead of on the phone itself?
Thanks!
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]
There is now a super thread over here with this root information and some more recoveries. I plan on expanding as more things are developed for the Rugby Pro.
I have added other hacks to this thread below the root download links. Enjoy.
The below guide outlines how to gain root on the Samsung Galaxy Rugby Pro (SGH-I547 ATT / Bell (Yes, Canada works!) / commanche). Please read through the full guide before attempting to root your device.
You will need ODIN v3.04 in order to gain root on the Rugby Pro (comanche), I will not post a link due to the nature of the package. Google has plenty of links for it.
BIG thanks to utkanos for all the help and making this a reality
Install instructions -- goldenlederhosen has provided some further information and detail about the below procedure here
Please read his post as well as the instructions before attempting this procedure
Install drivers from link below
Download necessary packages (clockwork recovery, root update) from the links below
Copy root update to your devices sdcard(s) -- Copy to both if external SD card is present
Charge phone to at least 80%
Power off the phone
Unplug from USB / Charger
Boot into download mode (Home + Volume Down + Power)
When asked if you want to continue, press Volume Up to enter download mode
Plugin phone and
Launch ODIN
Check the checkbox next to "PDA"
Click the PDA button
Select the comanche_cwr_6015_utkanos.tar.md5 file
Make sure only "Auto Reboot" and "F. Reset Time" are selected
Click start
Your phone will reboot one the flash is complete
You now have Clockwork Recovery, continue with the steps to get root
Power off your phone
Unplug from USB / Charger
Boot into Clockwork Recovery (Home + Volume Up + Power -- Release when Samsung logo appears)
Select "Install zip from sd card"
Select "Choose zip from sd card"
Navigate to zip
Select zip
Confirm
Reboot
You should now have root
I am not responsible for anything bad that comes to your device when using the information posted in this thread. Everything here is dangerous, may cause a brick, will void a warranty and has the potential to just plain wreak havoc. Do not complain you followed my instructions and met with a dead device. Consider yourself warned
I've tested to the best of my ability, but I am one person with one device, I cannot catch all potential failure modes. If you find a problem and a fix, or have information that should be added let me know and I will update the necessary information.
Download Links
Head over to the super thread here (link) for links.
CWR Touch / ODIN
Courtesy of childrenofthehorn there is a now a Clockwork Recovery Touch and ODIN images for the ATT varient. The thread is: http://forum.xda-developers.com/showthread.php?t=1990519
Rootz Wiki Forum
childrenofthehorn has gotten a dedicated forum setup over at Rootz Wiki. Check it out: http://rootzwiki.com/forum/556-galax...o-development/
Works like a charm!
Thanks for doing this guys. I was thinking I would have to create an insecure kernel for the stock ROM in order to get root. You saved me a lot of time & energy. Expect a donation coming from my way.
dweide9 said:
Thanks for doing this guys. I was thinking I would have to create an insecure kernel for the stock ROM in order to get root. You saved me a lot of time & energy. Expect a donation coming from my way.
Click to expand...
Click to collapse
Thank you much for the donation
Would you be willing to pull an image of the stock boot partition (dd if=/dev/block/mmcblk0p7) and PM me a link?
Also: check the OP, I've added some info on how to get tethering (after rooting) without the need for a dedicated ATT tethering plan.
re: post-root stuff
>Would you be willing to pull an image of the stock boot partition (dd >if=/dev/block/mmcblk0p7) and PM me a link?
I would if I had any experience. My plan to insecure the kernel would have been my 1st time getting my feet wet with such a thing.
>Also: check the OP, I've added some info on how to get tethering (after rooting) without >the need for a dedicated ATT tethering plan.
Thanks, I did but I don't find Tethering Manager. I did find Tethering Provision. Is that the same?
dweide9 said:
I would if I had any experience. My plan to insecure the kernel would have been my 1st time getting my feet wet with such a thing.
Click to expand...
Click to collapse
You can copy the contents of boot by:
Install a terminal emulator from the market
Launch terminal
su
Accept request for root
dd if=/dev/block/mmcblk0p7 of=/mnt/sdcard/mmcblk0p7_boot.img
Transfer mmcblk0p7_boot.img to your favorite cloud storage provider
Share link
If you run into trouble or have any questions let me know.
dweide9 said:
Thanks, I did but I don't find Tethering Manager. I did find Tethering Provision. Is that the same?
Click to expand...
Click to collapse
Provision is a separate app. When I'm back by my laptop in the morning I'll double check the paths and report back. I froze mine using Ultimate Backup or Titanium Backup. I forget offhand.
Sent from my SAMSUNG-SGH-I547 using Tapatalk 2
boot partition image
I tried to provide the link to both tarball & zipped files of my boot partition image, but I haven't done 10 posts yet, so xda has restricted me. Let see if a little disguise will work:
secured [email protected]/#folders/0BwUellf9svE3M01kampaMU54NWc
So what fun stuff can you do with this file & how would my image be any different then yours? Or is it another issue, like uploading being restricted because you're a developer?
Also, I'm interested in learning the process of how you created/edited the files , in order to root the Rugby Pro. I'm sure your busy, so pointing me toward a tutorial would be great.
kemonine96 said:
Provision is a separate app. When I'm back by my laptop in the morning I'll double check the paths and report back. I froze mine using Ultimate Backup or Titanium Backup. I forget offhand.
Click to expand...
Click to collapse
Looks like TetheringProvision.apk is the one to freeze (do not delete unless you have a backup). If you try this let me know.
dweide9 said:
I tried to provide the link to both tarball & zipped files of my boot partition image, but I haven't done 10 posts yet, so xda has restricted me. Let see if a little disguise will work:
secured [email protected]/#folders/0BwUellf9svE3M01kampaMU54NWc
Click to expand...
Click to collapse
Thanks for the file. I just finished pulling it.
dweide9 said:
So what fun stuff can you do with this file
Click to expand...
Click to collapse
I plan on using a stock boot image so I can put together an ODIN image that will flash the phone back to a stock state. If you root your phone or have a custom recovery / system / boot OTA updates will generally fail to apply. The best way to get an OTA update applied is to rollback to stock and install the OTA.
dweide9 said:
how would my image be any different then yours?
Or is it another issue, like uploading being restricted because you're a developer?
Click to expand...
Click to collapse
The boot partition should be the same across devices unless you make modifications.
I had to blindly update the boot partition on my device to get root, so I do not have an un-changed copy of it. In order to get an OTA update applied and to work with some Cyanogen / Clockwork Recovery stuff I will need a clean boot partition image.
dweide9 said:
Also, I'm interested in learning the process of how you created/edited the files , in order to root the Rugby Pro. I'm sure your busy, so pointing me toward a tutorial would be great.
Click to expand...
Click to collapse
I worked with a few people to get help putting together an ODIN image that allowed me to get custom recovery and the clockwork recovery update.zip. There is no general guide on the steps necessary.
If you are interested in diving into the custom rom / recovery stuff I will be doing some work with improving clockwork recovery for the Ruby Pro (commanche) and hopefully working on a Cyanogenmod 10 (JellyBean) port in the future. I am working on some items for the Rugby Smart (apache) at present, as soon as that stuff is taken care of I'll be focusing more on the Rugby Pro (commanche). If you are interested in taking a shot at updating the clockwork recovery for the commanche let me know and I can maybe point you in a few directions to get you going.
stuff
>I had to blindly update the boot partition on my device to get root, so I do not have an >un-changed copy of it.
You probably know this, but here's where I downloaded Samsung's ROM (disguised again, & I'm pretty sure the new "c" version is for Canada) Just search for sgh-i547:
[email protected]
>If you are interested in diving into the custom rom / recovery stuff I will be doing some >work with improving clockwork recovery for the Ruby Pro (commanche) and hopefully >working on a Cyanogenmod 10 (JellyBean) port in the future.
I am interested. Realize I have miniscule programming skills (http, xml & Google {now MIT} App Inventor).
Also, I did freeze TetheringProvision, but I rarely tether. Usually I only need to when it's raining & my home DSL slows too much. I'll let you know if I have any problems when I do finally try it.
dweide9 said:
>I had to blindly update the boot partition on my device to get root, so I do not have an >un-changed copy of it.
You probably know this, but here's where I downloaded Samsung's ROM (disguised again, & I'm pretty sure the new "c" version is for Canada) Just search for sgh-i547:
[email protected]
Click to expand...
Click to collapse
I pulled that package as well. Unfortunately it is only the GPL components they are required to release, not the full ROM sources. It does contain the kernel sources which will be very helpful down the line.
dweide9 said:
>If you are interested in diving into the custom rom / recovery stuff I will be doing some >work with improving clockwork recovery for the Ruby Pro (commanche) and hopefully >working on a Cyanogenmod 10 (JellyBean) port in the future.
I am interested. Realize I have miniscule programming skills (http, xml & Google {now MIT} App Inventor).
Click to expand...
Click to collapse
There is a lot of testing work and guess/check for the ROM building stuff. I was thinking of setting up an IRC channel on FreeNode for discussing work on the device. Would you be interested / willing to move some of the interactive discussion over there once I have a channel setup?
dweide9 said:
Also, I did freeze TetheringProvision, but I rarely tether. Usually I only need to when it's raining & my home DSL slows too much. I'll let you know if I have any problems when I do finally try it.
Click to expand...
Click to collapse
Keep me in the loop. I tend to only tether for the purpose of my tablet when I'm not near a WiFi AP. I wanted to point it out just in case, better to have it working before it's necessary.
Let me know if you want a modded stock kernel . I'l be willing to help, even though I don't have the device on-hand.
IRC channel on FreeNode is setup: #rugby-pro-dev for those that are interested.
Motorhead1991 said:
Let me know if you want a modded stock kernel . I'l be willing to help, even though I don't have the device on-hand.
Click to expand...
Click to collapse
I think we should be covered at the moment. The first priority will likely be getting a recovery nailed down and 100% before working on a customized kernel. I'm hoping to get recovery nailed sooner than later so we can do things like nandroid and similar before starting in on CM10 or another ROM.
I am also working on the Rugby Smart (apache) CM9/3.0 Kernel/CM10 stuff as well so my time with the Pro is limited at the moment. Hopefully the Smart stuff moves quickly so I can loop back around to the Pro quickly.
>I pulled that package as well. Unfortunately it is only the GPL components they are >required to release, not the full ROM sources.
Ah, learn something new every day.
>I was thinking of setting up an IRC channel on FreeNode for discussing work on the >device. Would you be interested / willing to move some of the interactive discussion >over there once I have a channel setup?
Sure, I already monitor #opennic on freenode, so I can just open another channel.
kemonine96 said:
Looks like TetheringProvision.apk is the one to freeze (do not delete unless you have a backup). If you try this let me know.
Click to expand...
Click to collapse
I deleted it, and now when I try and turn on the hotspot the device temporarily freezes and then I get the message "Unfortunatley, Settings has stopped."
MCKINLEC said:
I deleted it, and now when I try and turn on the hotspot the device temporarily freezes and then I get the message "Unfortunatley, Settings has stopped."
Click to expand...
Click to collapse
Odd, I'll have to double check my device again. Do you have a backup of the apk, or do you need a copy of it to restore?
kemonine96 said:
Odd, I'll have to double check my device again. Do you have a backup of the apk, or do you need a copy of it to restore?
Click to expand...
Click to collapse
Thanks, but I made a backup copy, Think the issue could be because it was deleted instead of frozen?
ETA, help, donation etc
I'm very interested in buying the Samsung Galaxy Rugby Pro for AT&T. However, there is no Cyanogenmod port for it yet. I really only want to have a phone if it can run a free ROM.
@kemonine96 et.al.:
When do you think a beta CM port will be ready?
I have not done any Android development and very little administration, but I am a seasoned Linux software engineer. Is there any way I can help with porting CM to this phone?
Finally, would a donation (kemonine96 has a paypal donations link) speed up the process? I can't afford to pay hundreds of dollars, but I could do something like 50....
goldenlederhosen said:
I'm very interested in buying the Samsung Galaxy Rugby Pro for AT&T. However, there is no Cyanogenmod port for it yet. I really only want to have a phone if it can run a free ROM.
Click to expand...
Click to collapse
You are not alone in that sentiment. I won't run a device I know won't receive a CyanogenMod port. The good news is as long as there is root, CyanogenMod can be made to work.
goldenlederhosen said:
When do you think a beta CM port will be ready?
Click to expand...
Click to collapse
"Soon". Myself and a couple others are working on a set of changes for the Rugby Smart (predecessor to the Pro) and once they are further along I will be looking into starting the CyanogenMod port for the Pro.
goldenlederhosen said:
I have not done any Android development and very little administration, but I am a seasoned Linux software engineer. Is there any way I can help with porting CM to this phone?
Click to expand...
Click to collapse
Most definitely, there are a few things that would help out a CyanogenMod port significantly. If you contact me via IRC (see OP) or via PM we can discuss some of the options and take it from there. Please note I leave my IRC connection active 24x7 so I may not respond right away.
goldenlederhosen said:
Finally, would a donation (kemonine96 has a paypal donations link) speed up the process? I can't afford to pay hundreds of dollars, but I could do something like 50....
Click to expand...
Click to collapse
As much as I may appreciate a donation, please hold off as I cannot commit to working on CyanogenMod for the Pro in a paid capacity I am comfortable with. I am working 50-60 hour work weeks at my day job so my free time is severely limited. I have every intention on bringing CyanogenMod to the Pro but it is a free time problem more than anything else.
Foreign anglopu
kemonine96 said:
Most definitely, there are a few things that would help out a CyanogenMod port significantly. If you contact me via IRC (see OP) or via PM we can discuss some of the options and take it from there. Please note I leave my IRC connection active 24x7 so I may not respond right away.
Click to expand...
Click to collapse
Okay, will do.
This is MIUI For the ONE S C2, It is based on bilal_liberty's CM10 Rom so expect similar performance and bugs. You will be running Android 4.1.2 With MIUI For Jelly Bean. It is currently not tested so make a full backup before you flash it, also do a logcat and post it if you can so we fix the issue if you have one.
Notice - This Rom has currently not been tested so use at your own risk, this is why it is labelled TEST.
Download - Soon
How To - To install this ROM just follow the usual way, Back up, Flash Rom, Clear Cache and everything and then boot.img.
V1.3 - Flashes, Boots but force closes and not stable, will release soon.
V1.2 - Re worked Port added, Not sure if issue has been fixed, you tell me.
V1.1 Test - Flashable .ZIP available but issues with flashing.
V1 Test - Launch
[removed]
clewis said:
Hmmm so there is already a miui rom....
But about my rom, i got an error on flash, it did start booting with the boot animation but got stuck.
Click to expand...
Click to collapse
use logcat to see whats going wrong
adb logcat > logcat.txt
http://forum.xda-developers.com/showthread.php?t=1726238 for more info
bilal_liberty said:
use logcat to see whats going wrong
adb logcat > logcat.txt
http://forum.xda-developers.com/showthread.php?t=1726238 for more info
Click to expand...
Click to collapse
I am doing a new build at this time i think i did something wrong the first time, so im going to add another unsigned file in a minute if you or someone else could make it a flashable zip and do a logcat when you do to save time would be good help, ill edit this page when it goes live on dropbox.
BTW this is how im trying to port it if anyone else wants a go - http://forum.xda-developers.com/showthread.php?t=1994503
For making flashable zip just select meta-inf folder system folder and boot.img and add them archieve, there is nothing extra to do.
bilal_liberty said:
For making flashable zip just select meta-inf folder system folder and boot.img and add them archieve, there is nothing extra to do.
Click to expand...
Click to collapse
Alright mate i have taken other one down and put a flashable zip on dropbox its going up now i can't try it myself as i dont have a usb cable that works to flash the boot.img so could someone else test it when it is uploaded.
clewis said:
Alright mate i have taken other one down and put a flashable zip on dropbox its going up now i can't try it myself as i dont have a usb cable that works to flash the boot.img so could someone else test it when it is uploaded.
Click to expand...
Click to collapse
Updated Flashable .Zip - https://www.dropbox.com/s/umsohpgmn1hh2z2/miui_unsigned.zip
Again use at your own risk, this has not been tested also everyone that does give it a try do a logcat so we can see if there is any problems.
Installation failed.
"set_perm: some changes failed"
"E:Error in /sdcard/miui_unsigned.zip"
work for old hboot??
DeanderDean said:
Installation failed.
"set_perm: some changes failed"
"E:Error in /sdcard/miui_unsigned.zip"
Click to expand...
Click to collapse
There is problem in updater script.try fixing permissions in updater script
u can use updater script from this to solve flash problems:
http://pan.baidu.com/share/link?shareid=341288&uk=4112589721 by jswei521
Great Work Man!!
Thanks for the port. I will test soon.
Sent from my HTC One S using xda app-developers app
bilal_liberty said:
u can use updater script from this to solve flash problems:
http://pan.baidu.com/share/link?shareid=341288&uk=4112589721 by jswei521
Click to expand...
Click to collapse
This rom from the above links works well, ive tried it.
Is old hboot 2.09 supported ?
can we flash this over 4.0.3 or do we need 4.0.4 as base ?
Paint in more detail information on ROM.
From what device port that was done, lay out screenshots, competently issue a post, write the detailed instruction. That works that doesn't work.
Thanks.
bilal_liberty said:
This rom from the above links works well, ive tried it.
Click to expand...
Click to collapse
Im getting an error?type=1 link when i go to that page, if you could attach the updater script so i could just switch them would be a big help.
Paint in more detail information on ROM.
From what device port that was done, lay out screenshots, competently issue a post, write the detailed instruction. That works that doesn't work.
Thanks.
Click to expand...
Click to collapse
Dont worry i will when i get it all up and running, its only a test version at this time. I have never made a ROM before and i have only published it this earlier because i need help in development which i am getting .
clewis said:
Im getting an error?type=1 link when i go to that page, if you could attach the updater script so i could just switch them would be a big help.
Dont worry i will when i get it all up and running, its only a test version at this time. I have never made a ROM before and i have only published it this earlier because i need help in development which i am getting .
Click to expand...
Click to collapse
Well, we wait for registration and the instruction, it will exclude many questions.
LeiManPRO said:
Well, we wait for registration and the instruction, it will exclude many questions.
Click to expand...
Click to collapse
I have registered and replied to a the original thread, got the download link and when i go to it i get an error, it's not there for me, if anyone has it please send the update script to me, i can't fix anything without that file.
clewis said:
Im getting an error?type=1 link when i go to that page, if you could attach the updater script so i could just switch them would be a big help.
Click to expand...
Click to collapse
Here u go best of luck
Edit: if you want some files from that rom here it is: http://www.mediafire.com/?mb04ljce767sd8m
bilal_liberty said:
Here u go best of luck
Edit: if you want some files from that rom here it is: http://www.mediafire.com/?mb04ljce767sd8m
Click to expand...
Click to collapse
Awesome mate, doing edits tonight will upload later.
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