Amon_RA/Koush,
Would it be possible for you to integrate PSFreedom into your recovery image as a selectable option?
So theoretically you can have all the recovery features with the option to run PSFreedom.
Anyone else please feel free to post your thoughts and comments.
Thanks
N0ble
n0ble said:
Amon_RA,
Would it be possible for you to integrate PSFreedom into your AmonRA recovery image as a selectable option?
So theoretically you can have all the recovery features with the option to run PSFreedom.
Anyone else please feel free to post your thoughts and comments.
Thanks
N0ble
Click to expand...
Click to collapse
I'm pretty much sure that's possible. Guess we should ask Koush too
Sent from my HTC Desire using XDA App
I'm waiting for this great feature too.
Sent from my HTC Desire
If someone could get this working it would be great.
I've never used USB mount in recovery. If this feature is lost its a worthy sacrifice.
as far as it looks like , he stoped the support for his recovery image ...
mercianary said:
If someone could get this working it would be great.
I've never used USB mount in recovery. If this feature is lost its a worthy sacrifice.
Click to expand...
Click to collapse
AFAIK, you also lose ADB
I would really like this too.
I can understand that we would lose ADB and USB mount when in recovery but it would be allot more convenient. I imagine it won't be too much further down the line until someone figures out a mod in the kernal of the ps3 itself to boot unsigned code, now we have the ability to dump and write it.
Sent from my HTC Desire using XDA App
You do loose ADB & Mass Storage in the recovery image, also a toggle between PSFreedom & ADB etc is not possible, as ADB... can not be built into a kernel module.
Fake-Flash will also not re-enable these features for you as it does not contain a kernel in itself.
It would be a nice feature, but after talking with AmonRa and exploring the possible routes to doing this, it simply is not possible as it is.
Later today or early tomorrow I will release a updated pack that does not have the OD 4.0.4 requirement, it will however still have AOSP as a requirement until HTC release kernel source.
Is a dual boot not possible? mount an img file as a virtual drive and boot from it?
can be a stripped down kernel with just psfreedom in it!!!
AmunRA already did this with his, you have to permanently flash it but it works.
neoKushan said:
AmunRA already did this with his, you have to permanently flash it but it works.
Click to expand...
Click to collapse
No, the question was for a recovery with a toggle, that's not possible.
Nice so it now seems that AmunRA and Klutsh have both made recovery images with ADB and USB working with a PSFreedom toggle.
Thats excellent work!
yyou guys are way too late google amon ra recovories google might just have a gift 4 you
turtleiscool said:
yyou guys are way too late google amon ra recovories google might just have a gift 4 you
Click to expand...
Click to collapse
Did you even bother to notice that this thread was month's old!!!
Related
thanks to skeeterslint, koush #sgs-dev , #samsung-epic , #sdx-developers
tester: me, skeeterslint, raiderep
based on koush's clockworkmod 2.5.1.0
new one click with root and recovery: http://forum.xda-developers.com/showthread.php?p=7933592#post7933592
download: http://www.sdx-downloads.com/devs/noobnl/one.click.clockworkmod2.5.1.0-flasher-fixed.zip
1. you need samsung galaxy s drivers
64-bit OS http://firon.net/xda/usb_drivers_GalaxyS_x64.zip
32-bit OS http://firon.net/xda/usb_drivers_GalaxyS_x64.zip
2. push MENU, select Applications > Development, then enable USB debugging.
3. extract and run runtryfirst.bat or runtrylast.bat
4. enjoy!
update.zip method:
1. boot into ClockworkMod Recovery
2. Apply : http://www.sdx-downloads.com/devs/noobnl/clockworkmod2.5.1.0update-fixed.zip
known issues:
adb reboot recovery quickboot boots to stock recovery
workaround:
while phone is off, hold vol down and camera button, then power on the phone
change log:
fixed in build 30: system doesn't unmount
fixes in build 31 incompatblilty with build 30 and di07 kernel
32 fixes added mount rw to the script, thanks bubby!
2.5.1.0 based on koush recovery and fixes the keys!
final fixed! forgot something to add to the scripts!
Yeah...I'm on this..thanks
Sent from my SPH-D700 using Tapatalk
Link is down.
dondadah88 said:
Link is down.
Click to expand...
Click to collapse
Awww...damn....lol. I was about to kick the wifey off the computer...lol
Sent from my SPH-D700 using Tapatalk
uploaded!..
This is something I'm looking for.
It says 0 btyes. and when you open it there's nothing there. lol.
i'm excited.
Oh and that link seems to be down.
miror: http://www.mediafire.com/?b66a2yak832uw20
thanks for the mirrir. downloaded and installed.
how do we boot into the recovery??? using quick boot goes into samsung's recovery...
while phone is off, hold vol down and camera button, then power on the phone
What functions work?
rjmjr69 said:
What functions work?
Click to expand...
Click to collapse
Well Backup works. i dont know what else?
I ran the bat file and everything but my phone still hasn't restarted yet...wtf.
What does this allow us to do? Please answer before I do this?
Backup and restore work fine for me. After the game I'll see if I can get a rom flashed but football > epic atm.
wjohnson1186 said:
What does this allow us to do? Please answer before I do this?
Click to expand...
Click to collapse
Backup everything and flash custom roms.
davidrules7778 said:
Backup everything and flash custom roms.
Click to expand...
Click to collapse
Can you explain how this is done? When I run the files does it copy what is on the phone to the computer so that I can just re-image it back onto the phone?
I maybe asking questions, but I really don't know what I am doing and want to be safe. I already have the one click flasher by noobnl, I trust him. I just want to be sure and understand what I am doing.
Thanks for all the info.
wjohnson1186 said:
Can you explain how this is done? When I run the files does it copy what is on the phone to the computer so that I can just re-image it back onto the phone?
I maybe asking questions, but I really don't know what I am doing and want to be safe. I already have the one click flasher by noobnl, I trust him. I just want to be sure and understand what I am doing.
Thanks for all the info.
Click to expand...
Click to collapse
No it saves under clockwork mod on the sd card in 3 convenient files. So when u flash a custom rom u can run restore and it will restore all your files and data.
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]
Defy Froyo 3.4.2 Cookie Cutter Rom
Q. How Do I use the Update.zip?
A. Go to Market & Download Defy SD-Recovery & Install..
1. Next place the Update.zip on the /sdcard via PC
2. Turn on MoTo Phone Portal ( SD-Recovery is SD Based so you need to Turn Off USB Mass Storage )
3. ADB Debugging does not have to be Turned Off on my version
Once Booted into the Recovery apply the update.zip
wait a few minutes & it should be done...
Please Reads the notes I left in the Update.zip if you build a Custom Update.zip, this will save you trouble down the road.
What's Flashed?
A. Boot.img
B. dev_tree
C. Moto Blur 3.4.2 Rom ( Yes I know it's not the latest, built off what I had )
D. UNO & TMO-TV Removed
E. Rooted ( SU & Superuser )
F. Busybox Installed to xbin
G. Rest of Rom is stock
Once installed, remove eugene.apk from /system/app ( Old boot strap that need adb turned off before rebooting / defy sd-recovery does not have this issue)
Q. I Edited the update.zip & Now it fails verf. in recovery when trying to flash!
A. example of signapk on signing the edited update
java -Xmx1024m -jar signapk.jar -w testkey.x509.pem testkey.pk8 update1.zip update.zip
Download: Original Post
To Update other parts of the Phone: Add this to the update-scripts for what you are flashing.
If we had all these Parts from 2.1 we could go back.
package_extract_file("lbl", "/tmp/lbl");
write_raw_image("/tmp/lbl","lbl");
delete("/tmp/lbl");
package_extract_file("device_tree.bin", "/tmp/device_tree.bin");
write_raw_image("/tmp/device_tree.bin","devtree");
delete("/tmp/device_tree.bin");
package_extract_file("cdrom", "/tmp/cdrom");
write_raw_image("/tmp/cdrom","cdrom");
delete("/tmp/cdrom");
package_extract_file("logo.bin", "/tmp/logo.bin");
write_raw_image("/tmp/logo.bin","logo.bin");
delete("/tmp/logo.bin");
package_extract_file("umts_wrigleyref_build.bin", "/tmp/umts_wrigleyref_build.bin");
write_raw_image("/tmp/umts_wrigleyref_build.bin","bpsw");
delete("/tmp/umts_wrigleyref_build.bin");
package_extract_file("cdt.bin", "/tmp/cdt.bin");
write_raw_image("/tmp/cdt.bin","cdt.bin");
delete("/tmp/cdt.bin");
Hey eugene,
Glad to see you working on Defy too
I think this will be major help for developers and btw that 3.4.2 version did you used? since there are many of them.
Thanks.
um. 107 I think since it has a floating update.zip someplace & sbf.
Ill update to the latest when I start building roms
Sent from my MB525 using XDA App
i don't understand. is the boot.img still the signed cg35.smg?
if so, can't we just use the cmw to do that?
can you post more detailed chages you made over cmw?
other than the signapk and usb debugging described.
many thanks.
eugene373 - great work!
racca said:
i don't understand. is the boot.img still the signed cg35.smg?
if so, can't we just use the cmw to do that?
can you post more detailed chages you made over cmw?
other than the signapk and usb debugging described.
many thanks.
Click to expand...
Click to collapse
Same here, i'm pretty interested in more details, thank you
this Zip File is for what ?
Thanks
Greetings
you can not use cwm due encryption. If you dont know what an update.zip is stick to nandroid...
This is for rom builders.
Heading out, when I get home ill make it clearer.
Though, now that I think about it cwm might be fine due to the nature of how it works.
Ill test later and let everyone know
Sent from my MB525 using XDA App
So we are able to install updates via the "normal" Motorola Recovery mode? So we are able to get a "unbrickable" Defy?
Edit: got it myself. The ZIP File won't be recognized by the motorola recovery... anyway thanks for your job
Now, what can SD-recovery do? Can it write other partitions, like cdt.bin?
Simplestas said:
Now, what can SD-recovery do? Can it write other partitions, like cdt.bin?
Click to expand...
Click to collapse
Yes. I can add the string if you would like
eugene373 said:
To Update other parts of the Phone: Add this to the update-scripts for what you are flashing.
package_extract_file("lbl", "/tmp/lbl");
write_raw_image("/tmp/lbl","lbl");
delete("/tmp/lbl");
package_extract_file("device_tree.bin", "/tmp/device_tree.bin");
write_raw_image("/tmp/device_tree.bin","devtree");
delete("/tmp/device_tree.bin");
package_extract_file("cdrom", "/tmp/cdrom");
write_raw_image("/tmp/cdrom","cdrom");
delete("/tmp/cdrom");
package_extract_file("logo.bin", "/tmp/logo.bin");
write_raw_image("/tmp/logo.bin","logo.bin");
delete("/tmp/logo.bin");
package_extract_file("umts_wrigleyref_build.bin", "/tmp/umts_wrigleyref_build.bin");
write_raw_image("/tmp/umts_wrigleyref_build.bin","bpsw");
delete("/tmp/umts_wrigleyref_build.bin");
package_extract_file("cdt.bin", "/tmp/cdt.bin");
write_raw_image("/tmp/cdt.bin","cdt.bin");
delete("/tmp/cdt.bin");
Click to expand...
Click to collapse
eugene373 said:
Yes. I can add the string if you would like
Click to expand...
Click to collapse
CwM can do exactly the same afaik, i've already made quite a few update.zip with it.
after reading all your notes, do you actually mean that we can't use format on those patitions?
if you do, well, i learned it the hard way, and delete_recursive also works for me.
thanks for putting up an excellent example if not for anything else, it's much needed.
racca said:
CwM can do exactly the same afaik, i've already made quite a few update.zip with it.
after reading all your notes, do you actually mean that we can't use format on those patitions?
if you do, well, i learned it the hard way, and delete_recursive also works for me.
thanks for putting up an excellent example if not for anything else, it's much needed.
Click to expand...
Click to collapse
Correct, you can only format with the stock recovery ( Hence the reason why I used the Stock Recovery ) any Partition with cwm recovery will cause a non-booting system..
regarding cwm I've not tested it, so Likely it will work.. Steven is still working on the cwm recovery & there is no point in me adding another cwm bootstrap recovery... Mine is just pure stock & works perfect.
I'm still weeding through the /bin /etc file's to find exactly what needs left...
but main goal was to provide an example of what is needed to make an update.zip with out breaking the system.
what exactly is the benefit of this new method?
drsouly said:
what exactly is the benefit of this new method?
Click to expand...
Click to collapse
um? Your joking right!
Update versus a nandroid, I would have thought it was a no brainier....
Build & edit roms on the fly + being able to flash boot.img & downgrading is fine without sbf unless you screw up completely..
eugene373 said:
um? Your joking right!
Update versus a nandroid, I would have thought it was a no brainier....
Build & edit roms on the fly + being able to flash boot.img & downgrading is fine without sbf unless you screw up completely..
Click to expand...
Click to collapse
ok now i got it thx
drsouly said:
ok now i got it thx
Click to expand...
Click to collapse
no problem, wasn't sure if you was being a smart-ass or honestly didn't know...
either way, sorry If I offended you.
~Eugene
I didn't understand yet . I can or not apply the update file using stock recovery?
EDIT: forget I understood now.
Sent from my MB525 using XDA App
psicodelico said:
I didn't understand yet . I can or not apply the update file using stock recovery?
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Read OP.... Download Defy SD-Recovery from Market
Yeah, I read again slowly and understood.
Sent from my MB525 using XDA App
Some of you may know me and some not. I was asked to help out on the SK4G development, so here I am.
I have some questions first.
1. You are using CWM?
2. Amend or Edify?
3. Do you have the drivers and adb set up yet?
Depending on the answers I can put out a couple of tests and then get to work on this.
I will need your newest deodexed framework-res.apk, twframework-res.apk, settings.apk, services.jar - and others as needed.
If you do not have a deodexed rom yet then I need a copy of your systemfs.rfs or a full odin to deodex it myself. I have the system dump, is this your newest rom? If so then I have already deodexed it - just let me know.
1. Yes, the epic 4g version which is buggy
2 don know
3.yes
Sent from my SGH-T839 using Tapatalk
1) No. It doesn't sound like the currently available CWM firmwares work well on the SK4G. I am waiting for one designed for this hardware. I have run CWM on other handsets, of course.
2) No. Had not heard of those until you'd mentioned them.
3) Yes. Working well. We're all set here, at least.
System dump: There only seems to be one ROM/firmware version for this phone so far. The one you have should be current. I pulled mine in this thread:
http://forum.xda-developers.com/showthread.php?t=1037403&page=5
Specifically here:
http://forum.xda-developers.com/showpost.php?p=13210149&postcount=59
I'm happy to help further. Please simply let me know what you need.
And thanks for taking this on! This could be a solid phone without some of the bloatware trash foisted on it.
1. They are using the one click root for the epic by noobnl which installs CWM 2.5.1.0
2. Amend though can't you just use update-binary and make it compatible with both
blu9987 said:
1. They are using the one click root for the epic by noobnl which installs CWM 2.5.1.0
2. Amend though can't you just use update-binary and make it compatible with both
Click to expand...
Click to collapse
Yes, but I am old school and still use amend most of the time and needed to make sure it was going to be compatible.
Once I see some feedback on the theme I posted I will move forward - I just need to know how it turns out so I will have a better understanding of the phones layout.
Might need to send Koush a message and see if we can get a proper recovery going.
I really would love it if this phone got some custom roms. I don't want to get rid of it. But I put a ad up on craigslist to trade for a mytouch 4g.
Sent from my SGH-T839 using XDA App
Also as far a getting a proper working recovery, i think we may need a recovery that supports the ext-SD card. our internal memory isnt used by us because its so small. its used for things like installing apps i believe. if you use a file manager you'll see the only available SD card is the external one and same when mounting the phone. i think the epic and vibrant recovery would work just fine except we'd need one that supports the external SD card.
there is a kernel called dead horse that i used on my vibrant that had this support for ext SD but i dont think theres a way to get just the recovery out of it. hopefully someone might know a way to direct CWM to our ext SD then we might be on to something ..
ayoteddy said:
Also as far a getting a proper working recovery, i think we may need a recovery that supports the ext-SD card. our internal memory isnt used by us because its so small. its used for things like installing apps i believe. if you use a file manager you'll see the only available SD card is the external one and same when mounting the phone. i think the epic and vibrant recovery would work just fine except we'd need one that supports the external SD card.
there is a kernel called dead horse that i used on my vibrant that had this support for ext SD but i dont think theres a way to get just the recovery out of it. hopefully someone might know a way to direct CWM to our ext SD then we might be on to something ..
Click to expand...
Click to collapse
Its just a driver issue. We need to know exactly which SD card reader is in the phone and see if we can contact the manufacturer for the source.
I do not know how to decompile things like drivers, but I would like to know so I could get the ball rolling on this.
I'd love to see development pickup on this phone.
I've had my G1 since Dec 08 and happily rooted and did whatever I wanted to do it with the huge support from the developer community that the G1 received.
I'm keeping myself stock until someone gets Clockwork working with nandroid and there's an unroot method.
d4n137_91 said:
I'd love to see development pickup on this phone.
I've had my G1 since Dec 08 and happily rooted and did whatever I wanted to do it with the huge support from the developer community that the G1 received.
I'm keeping myself stock until someone gets Clockwork working with nandroid and there's an unroot method.
Click to expand...
Click to collapse
I feel the exact same way. I just picked mine up today and I really want to dive into it.
Yeah man, id like to see some development for this phone. I'm willing to help with whatever. This forum seems very dead though. Let's hope it picks up.
Sent from my Sidekick 4G using XDA app
what is the sdcard mounted as? mmcblk0p1? mmcblk1p1? This is key to getting recovery set up.
Where do I find that? I just rooted the phone but I haven't flashed the buggy recovery image
Sent from my little sidekick
gearhead27 said:
Where do I find that? I just rooted the phone but I haven't flashed the buggy recovery image
Sent from my little sidekick
Click to expand...
Click to collapse
adb shell
cd sys
cd block
ls
pastebin that info
that should tell me what I need to know
ive got it. it's mmcblk0p1
Same as the Vibrant, but theirs is mounted to internal sd. I would just need to switch up some stuff.
1st and foremost.... I need your guy's initramfs from your kernel
Idk too much about the initramfs nor how to extract it.
If I'm right the zImage is the kernel maybe this could help you so I've uploaded it to dropbox aswell.
http://db.tt/hhJIGXn
If it needs to be done from our phone could you point us in the right direction on how to get the initramfs.
Sent from my SGH-T839 using XDA App
So exciting seeing the development picking up
so happy to have someone look in this 4rum......im willing to help,,,,,if you guys need someone to be a tester.....just let me know....
ayoteddy said:
Idk too much about the initramfs nor how to extract it.
If I'm right the zImage is the kernel maybe this could help you so I've uploaded it to dropbox aswell.
http://db.tt/hhJIGXn
If it needs to be done from our phone could you point us in the right direction on how to get the initramfs.
Sent from my SGH-T839 using XDA App
Click to expand...
Click to collapse
Thanks, I'll get you guys something to test with tomorrow night when I get to work.
krylon360 said:
Thanks, I'll get you guys something to test with tomorrow night when I get to work.
Click to expand...
Click to collapse
can't wait to test it.....thanks a lot
Special thanks goes out to everyone who tested for me.
I do not have the device, so I rely heavily on testers to report any bugs.
Here is CWM for the SK4G.
You will need to modify your stock recovery binary to be able to use CWM.
Kernel Devs can also compile CWM into their kernel by extracting the update.zip and building it into their initramfs.
To replace your stock recovery binary with the modified binary:
download this file
DEAD. USE BALI KERNEL
Exatract and take the recovery binary file inside of it and use root explorer or adb push the file to /system/bin.
DO NOT delete the current one there, or rename any files.
Just overwrite it.
I would however, recommend getting Android Commander from www.androidcommander.com It's a lot easier, and a lot more useful.
CWM Final
DEAD. USE BALI KERNEL
Place in the root of your SD.
You can now use Quick Boot from the market, or adb reboot recovery to boot into CWM
I have sent Koush the device tree to have the official update.zip supported within Rom Manager.
UNTESTED:
You can also take the contents from the update.zip and replace the contents that are in noobnl's recovery rerouter/root.
Again, I haven't tested that due to not having the device.
First! Congrats krylon and thank you
Krylon: link 404'd
Sent from my SGH-T839 using XDA App
Thank you very mucho!
Sent from my SGH-T839 using XDA App
i cant dowload recovery zip
I don't know if its just me but the first link is not working
Sent from my SGH-T839 using XDA App
Guys... add a /sk4g to the first url so its like the 2nd url... thank me later
Sent from my SGH-T839 using XDA App
http://www.krylon360.com/file_host/sk4g/recovery.zip
mattpall said:
Guys... add a /sk4g to the first url so its like the 2nd url... thank me later
Sent from my SGH-T839 using XDA App
Click to expand...
Click to collapse
Datlilboricua said:
http://www.krylon360.com/file_host/sk4g/recovery.zip
Click to expand...
Click to collapse
Fixed. thanks.
Thanks lilboricua
Sent from my SGH-T839 using XDA App
Krylon... quick question... how much effort would it be to make a "reorient kernal" similar to wat the captivate had so it could use i9000 roms. Since this phone is basically a galaxy s...
Sent from my SGH-T839 using XDA App
Nand backup error
with the new recovery (remapped buttons) i tried to do a nand backup and it wouldnt start and it'd auto matically say error while backing up boot image... can anyone see if they come across this aswell ..
mattpall said:
Krylon... quick question... how much effort would it be to make a "reorient kernal" similar to wat the captivate had so it could use i9000 roms. Since this phone is basically a galaxy s...
Sent from my SGH-T839 using XDA App
Click to expand...
Click to collapse
this phone is not basically a galaxy S. heck, when the SGS4G came out people said it was basically a vibrant. NOPE. Wrong.
It would be hard to do, but might be doable.
ayoteddy said:
with the new recovery (remapped buttons) i tried to do a nand backup and it wouldnt start and it'd auto matically say error while backing up boot image... can anyone see if they come across this aswell ..
Click to expand...
Click to collapse
didn't you test this?
mattpall said:
Krylon... quick question... how much effort would it be to make a "reorient kernal" similar to wat the captivate had so it could use i9000 roms. Since this phone is basically a galaxy s...
Sent from my SGH-T839 using XDA App
Click to expand...
Click to collapse
if we could get a stock kernel with just the ext4 patch so we would be able to run our system, data and cache on ext4 i'd be pleased enough . idk if anyone with this phone would be able to rebuild the kernel with that patch but if so our phones would easily be 3x faster
I also see the same problem. I didn't think to test backups. What was all changed from the working version to the current version? all that needed to be changed was the lun map and BOARD_USES_CUSTOM_KEYMAP
krylon360 said:
didn't you test this?
Click to expand...
Click to collapse
yes i tested the original one completely and everything worked, the new one you sent me i only tested the buttons and mapping which were fine . but it seems now the nand backup/restore has a problem.
Edit: i just made another nand backup with the original recovery without the back button mapping and it works. seems the edited one got the backup/restore broken somehow
ayoteddy said:
if we could get a stock kernel with just the ext4 patch so we would be able to run our system, data and cache on ext4 i'd be pleased enough . idk if anyone with this phone would be able to rebuild the kernel with that patch but if so our phones would easily be 3x faster
Click to expand...
Click to collapse
not hard to do at all. unpack, add in ext4 mount options, repack, then flash kernel, and script to convert.
sduvick said:
I also see the same problem. I didn't think to test backups. What was all changed from the working version to the current version? all that needed to be changed was the lun map and BOARD_USES_CUSTOM_KEYMAP
Click to expand...
Click to collapse
Omg didn't test backups? :facepalm
Sent from my SGH-T839 using XDA App
ayoteddy said:
yes i tested the original one completely and everything worked, the new one you sent me i only tested the buttons and mapping which were fine . but it seems now the nand backup/restore has a problem.
Edit: i just made another nand backup with the original recovery without the back button mapping and it works. seems the edited one got the backup/restore broken somehow
Click to expand...
Click to collapse
the new one all I did was change key mapping and UMS path... odd.
Ok I did the recovery to system bin and did the update it changed to cwm and I tried nand errors out I reboot and reboot back into recovery I'm back to stock recovery
Sent From My Rooted Sidekick 4g Premium XDA App