Database Info

[ROM](Working Update.zip) -> Defy Update.zip Cookie Cutter Rom

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

[MOD][Update: 12-Aug-2011]Rooted CG from CH Leak

Thanks to dangpzanco for the GREAT IDEA.
I finally got my Rooted GB working here. I can't provide a download link now but I'm going to do it later for sure.
Apparently there was a final signature check that was done somewhere after mounting the cache partition, preventing me from booting with a pure update.zip on top of froyo /system. Thanks to dangpzanco I could bypass it and get root.
Quick Guide (requires froyo, root and Droid2bootstrapper):
1. Download fixed SBF bellow. It's made from the CH leak containing ONLY: CG35.smg (boot) CG47.smg (recovery) CG61.smg (devtree) firmware.hmg (header) RAMDLD.smg (flash updater).
2. Download root_and_recovery.zip and copy it to SD Card.
3. Download full leaked SBF from General Forum (CH, signed) and use MotoAndroidDepacker to extract all images.
4. Copy the CG39.smg to /sdcard/
5. Boot into CWM
6. From CWM open adb shell and use this command: dd if=/sdcard/cg39.sm of=/dev/block/system
7. Still on CWM apply root_and_recovery.zip
8. Still on CWM wiped everything
9. Boot on bootloader and flash fixed SBF
10. Reboot

I actually did the same thing! I read it somewhere in one of the topics. I installed Defy BootMenu instead of CWM. Works great! Right now I've almost removed all the Chinese crap and got the GApps working (from CM7).
I also removed the Blur items for the Chinese SN's. I'll see if I can get Twitter and Facebook working with it.
2nd-init would be nice too actually. Does the method provided in the other thread work with this ROM?
Edit: the instructions were indeed from dangpzanco!

And right now I found a possible bug. My camera doesn't work. Everything is black and stays black. Photo's are take as they should however.
Can you check whether you have the same issue?

w0ndersp00n said:
And right now I found a possible bug. My camera doesn't work. Everything is black and stays black. Photo's are take as they should however.
Can you check whether you have the same issue?
Click to expand...
Click to collapse
Here it works fine. Have you tried to edit /system/build.prop?
Change device from ME722 to A953.

Yes, I changed it to A953...
Maybe I have deleted something that was necessary for the viewfinder... But what xD
Edit: Allright, nevermind. Somehow a reboot fixed it :-D On to the next step

Something bad happened when I tried to apply 2nd-init on this. The phone rebooted just after 2nd M logo not allowing me to get into CWM. Wierd, since CWM should take place before 2nd-init. Will need to raflash froyo and start over. We should find a way to root Gingerbread without CWM to make things faster.

That's odd indeed. I have to say, I think the CWM method of rooting is actually quite easy. For SuperOneClick I need to get my PC/laptop out every time and with the update.zip I can do it as I please.
I really hope you'll succeed wit 2nd-init. If you need help, just shout! Today and tomorrow I have enough time.
I'll make a nandroid of my current setup, so I can continue trying out stuff.

w0ndersp00n said:
That's odd indeed. I have to say, I think the CWM method of rooting is actually quite easy. For SuperOneClick I need to get my PC/laptop out every time and with the update.zip I can do it as I please.
I really hope you'll succeed wit 2nd-init. If you need help, just shout! Today and tomorrow I have enough time.
I'll make a nandroid of my current setup, so I can continue trying out stuff.
Click to expand...
Click to collapse
Yeps, it is easy indeed, but to do it I need to SBF froyo before installing GB again. In other words if I mess up the phone I will need to flash 2 versions instead of one. That's why it would be easier to flash just GB.

Hey there, nice I could help.
I think you could copy the /dev/block/system back after rooting and build the SBF with it.
@Milestone 2 (Finnaly on Gingerbread!)

dangpzanco said:
Hey there, nice I could help.
I think you could copy the /dev/block/system back after rooting and build the SBF with it.
@Milestone 2 (Finnaly on Gingerbread!)
Click to expand...
Click to collapse
I tried that with froyo but it didn't work.

you can try also this defy leaked gb rooted nandroid backup.
http://www.multiupload.com/SPZ8SIEC60
version 4.5.1-134 multilanguage.
use fixedsbf from new leaked milestone2 rom and milestone2patch from MS2Ginger thread.
In this rom /system/app/kpilogger.apk cause battery drain so delete it after install.

Something is seriously wrong... My backlight never shuts down. It's black, but when it's dark you'll see it's still on!
I actually can't change the brightness from settings. So I did a complete reinstall and the problem persists!
I'm using brightcontrol app now to adjust the brightness, but does anyone else has this issue? Or is it something I did?

r2beta0 can you please upload the nandroid of your system?
I try to get adb in CWM but it didn't recognize it.

julianlatasa said:
r2beta0 can you please upload the nandroid of your system?
I try to get adb in CWM but it didn't recognize it.
Click to expand...
Click to collapse
My system is messed. I still need to get 2nd-init to work. I'm having a lot of trouble trying to compile my custom version of logwrapper hijack. As I don't have experience in compiling stuff to ARM/Android it is being a pain in the a**. I'd appreciate some help here

Try setting up a QEMU environment with the GB leak kernel's zImage.
Edit: Now we can port CM7!!! Devtree.img is now signed.
@Milestone 2 (Finnaly on Gingerbread!)

dangpzanco said:
Try setting up a QEMU environment with the GB leak kernel's zImage
@Milestone 2 (Finnaly on Gingerbread!)
Click to expand...
Click to collapse
And how do I do that?
I tried some ways till this point:
- Installed CodeSourcery G++ Lite toolchain (could compile, but android didn't run)
- Installed NDK and tried some commands I could find on blog posts (no luck)
- Now I just finished setting up an ubuntu 10 VM with all the steps described on developer.android.com. I think I am now able to compile android system, but I don't want to as it will take a LOOONG time.
Do you know how do I build a specific module into android source? For example:
system/core/toolbox
I'm a developer, and have compiled stuff to run on linux/unix many times. But this ARM stuff is way complicated. Writing the code isn't the problem, but compiling is. Lots of flags I haven't seem before, and so on.

r2beta0 said:
And how do I do that?
Do you know how do I build a specific module into android source? For example:
system/core/toolbox
Click to expand...
Click to collapse
I just uncovered this answer by myself.
A 'make toolbox' on root folder seems to work just fine. Now I need a way to define new targets on android build system.

http://and-developers.com/
Has a page just for compiling the kernel from source. (I can't remember the link)
I also got stuck when trying to compile from AOSP... but I think you need to have ALL the files downloaded from source (specially the big prebuilt folder) even if you want to compile a single binary.
Well I'm not sure of anything...
Edit:Now I read what you wrote... so never mind you got it.
@Milestone 2 (Finnaly on Gingerbread!)

dangpzanco said:
http://and-developers.com/
Has a page just for compiling the kernel from source. (I can't remember the link)
I also got stuck when trying to compile from AOSP... but I think you need to have ALL the files downloaded from source (specially the big prebuilt folder) even if you want to compile a single binary.
Well I'm not sure of anything...
Edit:Now I read what you wrote... so never mind you got it.
@Milestone 2 (Finnaly on Gingerbread!)
Click to expand...
Click to collapse
Yeps I've made a full repo sync. It took 3 hours and is worth 6GB disk space

Great news! Can't wait to see a true custom ROM working
Just thought I'd share what I've learned: don't mess too much with your build.prop Somehow my modifications were the reason of my backlight not working right and making every app crash that wanted to use a sensor. But it's working again

Signed .zip files

So I have rooted my Infuse
I have gotten the stock source code as well as a rom to try out
I had attempted to 'run' this rom however I can not as it is unsigned.
I saw one solution that is to buy AnyRootExplorer
What else can I do?
On a side note, I also attempted to 'run' the stock Infuse but I wasnt able to again a
sign problem.
I do apologize if this is not the place to post this.
Anyhelp would be appreciated.

a couple of of those words in the search box would have found this thread..
http://forum.xda-developers.com/showthread.php?t=1091465

Well thank you, I know that was strictly mentioned in the video
My solution (what I in the end did based on random findings on the web):
Install the 3e Recovery Mod (followed instructions)
Installed AndroZip (for browsing) and SuperManager (for actual overwriting files)
Used the Terminal Emulator (mount rw)
Voila
Today I am running the Infused 1.5 ROM offered here for free (what a great bunch of guys )
Yesterday the stock stock Samsung ROM
Tomorrow? I don't know, I wish I could mount the ROM that I had designed, however I don't know how to build a ROM yet, seems like a rather lengthy process that not just any beginner can do.
I was trying it out, Serendipity wasn't so 'works on first try' .
I don't know how to compile yet, it sucks I have only learned C++ so far.
That doesn't even apply I don't believe so anyways, either Java or Linux.
Thanks for the help though my good sir.

No Problem, i hope you get your stuff up and Going.....we could ALWAYS use another Dev or Dev in the making....
keep it up bruh.

FYI, a "shortcut" way to doing things, such as S7, would be:
Odin/Heimdall a Gingerbread kernel
Enter recovery using the three-finger salute (VolUp + VolDn + Power when the device is off, let go of power after the Samsung logo appears but keep holding VolUp + VolDn for 5-10 more seconds)
Flash the zip and wipe

@the2rell - thanks for the kind words
I appreciate it I feel welcome already
@Entropy512 - does what you have said apply to Froyo? Forgive me if thats a dumb question, I asked because you mentioned gingerbread.
I have yet to explore the rainbow of booting
odin/Heimdall, I don't know what that means. More reading
Thanks for that tip, I'll need to learn it.

GreenAce92 said:
@the2rell - thanks for the kind words
I appreciate it I feel welcome already
@Entropy512 - does what you have said apply to Froyo? Forgive me if thats a dumb question, I asked because you mentiobed gingerbread.
I have yet to explore the rainbow of booting
odin/Heimdall, I don't know what that means. More reading
Thanks for that tip, I'll need to learn it.
Click to expand...
Click to collapse
Odin the program used to Flash, Kernels and its used to go back to stock.
and Froyo or Not i think E was just telling you to flash the GB kernel to get to Recovery(instead of messing with the system files) like he said its just a faster way of going about it.

Indeed, probably less of a PITA as well.
Alright I'm going to have a read
Hopefully I'll catch up soon (few weeks not really sure about the learning curve)
As always, my thanks go out for the wealth of information
Another dumb question, does flashing mean similar to boot off of another source? Or is it the way it is loaded on, flash memory not NTFS or FAT32 etc... ?

Gahh this is seriously making me flustered
This is my fourth infuse, first (original NIB) screen damaged, 2 Refurbes stolen, now the current refurb
I am trying to get 3e to work on here
Maybe I was just trying to believe in something that isnt true but I really believe that I had gotten the 3e to work via phone only
Now I can't get it to work
Is it even doable?
My procedure-
Downloaded 3e zip to downloads folder (phone memory)
Extract within same folder
Use terminal emulator (free) # sign is fixed on emulator
su (or su root tried both)
mount -o remount, rw -t yaffs2 /dev/block/mtdblock3/system
tried mtdblock5 (from MD5)
tried system/bin
how do I know if I am currently in a rw mount?
How could I test?
After this I try to copy or move the recovery file from downloads folder to system/bin wjere another system recovery file is dated aug 4, 2011
I've tried multiple free file exlporers
Andro Zip
Astro
Super Manager
ES File Explorer (pretty)
File expert (crashes when I try to rename original recovery to recovery.orig)
What am I doing wrong? (Besides having a weak ass phone)
Btw what does it take to develop a virtual core?
Is it possible to get the Infuse up to 2.0+ Ghz?

Are you rooted?
http://www.addictivetips.com/mobile...amsung-infuse-4g-to-flash-unsigned-zip-files/
GreenAce92 said:
Gahh this is seriously making me flustered
This is my fourth infuse, first (original NIB) screen damaged, 2 Refurbes stolen, now the current refurb
I am trying to get 3e to work on here
Maybe I was just trying to believe in something that isnt true but I really believe that I had gotten the 3e to work via phone only
Now I can't get it to work
Is it even doable?
My procedure-
Downloaded 3e zip to downloads folder (phone memory)
Extract within same folder
Use terminal emulator (free) # sign is fixed on emulator
su (or su root tried both)
mount -o remount, rw -t yaffs2 /dev/block/mtdblock3/system
tried mtdblock5 (from MD5)
tried system/bin
how do I know if I am currently in a rw mount?
How could I test?
After this I try to copy or move the recovery file from downloads folder to system/bin wjere another system recovery file is dated aug 4, 2011
I've tried multiple free file exlporers
Andro Zip
Astro
Super Manager
ES File Explorer (pretty)
File expert (crashes when I try to rename original recovery to recovery.orig)
What am I doing wrong? (Besides having a weak ass phone)
Btw what does it take to develop a virtual core?
Is it possible to get the Infuse up to 2.0+ Ghz?
Click to expand...
Click to collapse

Yes
I ran 'rage the cage' through linux
I have super user and my terminal prompt (as stated above) is a #

GreenAce92 said:
Yes
I ran 'rage the cage' through linux
I have super user and my terminal prompt (as stated above) is a #
Click to expand...
Click to collapse
not sure why you are having so much trouble.
i dont use TE.
i used root explorer..if you dont want the purchased version,
http://www.4shared.com/android/XdtGx9oo/Root_Explorer_v2171.html
http://www.youtube.com/watch?v=PkMo8rBehHg

So is it retarded for me to have tried to install the Infusion 1.8 zip through recovery as a ROM ? hahaha I just have the SAMSUNG logo fixed on the screen
Also I heard some weird robotic woman voice
"Systems Not Available"
"Convert Partition"
Oh looky! It's fine hehehe neat I have a girl friend now hahaha

GreenAce92 said:
So is it retarded for me to have tried to install the Infusion 1.8 zip through recovery as a ROM ? hahaha I just have the SAMSUNG logo fixed on the screen
Also I heard some weird robotic woman voice
"Systems Not Available"
"Convert Partition"
Oh looky! It's fine hehehe neat I have a girl friend now hahaha
Click to expand...
Click to collapse
I'm not sure what you mean...you can install infusion 1.8 through red recovery cwm once you have the proper setup.
The robotic woman voice is voodoo lag installation...you should be able to reboot into red recovery now and flash your ROM...

See I seem to keep stumbling around and not really understanding anything
So... first off
There is the sd card within the phone, then the external micro sd card right?
Also I did get to a red CWM and then also to a green, and then the blue ... the green seems to be the recovery for the i9000 which I used to get myself out of trouble
Thanks for linking the Root File Explorer, that is such a great program, it beats the other bs
I'm going to try and flash Bionix Infusion (only because of the infusion) I want that "1.5+Ghz speed"
Thanks for your help
How exactly do you bounce from one CWM to another or you don't?
When going into recovery by holding the three physical click buttons till SAMSUNG pops up and release
which recovery is this? I can't remember what color mine was
-----------------------------------------
In regards to my post above about the 1.5 speed
Installing infusion 1.8 (a small zip file) will change the kernel ?
I'm currently only after 3e recover and getting the kernel for 1.5ghz speed
-------------------------------------------
Just to be clear
once I have pasted the contents of the 3e zip folder (recovery file) into /system/bin
What is supposed to happen next? (what am I supposed to do)

Gahhh finally it is done
I'm sorry for my exceeding lack of competence
I seem to be retarded in many ways hahaha
Anyways... the 3e Recovery is running and I have just installed the 1.8Zip through Red CWM
Just a note for myself and anybody else who may be as mentally inept as I
To get 3e Recovery
Download 3e Recovery Zip file to downloads folder
Download Root Explorer (through link)
Use the incredibly easy toggle r/w r/o buttons of Root Explorer to replace the old recovery file in /system/bin with new one (3e)
reboot
proceed to flash other roms / install zip files of various sorts
Just curious once the Infusion 1.8 zip was installed
Do I immediately notice the effects? ie a faster processor
Or are there more steps needed to be completed?
----- wait i see! Use antutu to overclock wow! Goes up to 1.8 !!! -----
Curious what is the min / max ?
Should I have min 100mhz max 1500mhz ? Or
min 1200mhz max 1500mhz ?

read more threads...
click thanks for a simple thank you..
have fun..
GreenAce92 said:
Gahhh finally it is done
I'm sorry for my exceeding lack of competence
I seem to be retarded in many ways hahaha
Anyways... the 3e Recovery is running and I have just installed the 1.8Zip through Red CWM
Just a note for myself and anybody else who may be as mentally inept as I
To get 3e Recovery
Download 3e Recovery Zip file to downloads folder
Download Root Explorer (through link)
Use the incredibly easy toggle r/w r/o buttons of Root Explorer to replace the old recovery file in /system/bin with new one (3e)
reboot
proceed to flash other roms / install zip files of various sorts
Just curious once the Infusion 1.8 zip was installed
Do I immediately notice the effects? ie a faster processor
Or are there more steps needed to be completed?
----- wait i see! Use antutu to overclock wow! Goes up to 1.8 !!! -----
Curious what is the min / max ?
Should I have min 100mhz max 1500mhz ? Or
min 1200mhz max 1500mhz ?
Click to expand...
Click to collapse

Thanks man
And I have
Now to create my dream theme

having fun in recovery... (and messing with Red5)

So, I'm playing with recovery... In particular, I'm working on replacing the stock recovery with CWM Recovery. A good nandroid backup is always the first step to hacking an android device.
I've managed to repack the recovery partition (finally) as unsecure (meaning I can boot into recovery, adb shell into the device, and have root access.) While in here, I'm just noticing something different on the tablet:
It appears that the firmware update from kies has added some odd bloat: the default factory recovery starts by copying several items from a "preload" partition to your /sdcard partition. How nice of Samsung to add even more addition BLOAT to our devices. (I'll be removing that aspect of recovery, I promise.)
Another oddity I'm finding is that, normally with these devices when they are booted normally (and adb is able to connect), the commandline "adb reboot recovery" will reboot the device into recovery mode. That does NOT happen with this tablet (but I'm not sure why.) I have to power down and power back on with the proper volume switch held down.
Okay... time for me to build a copy of CWM Recovery that'll (hopefully) work on this tablet. Wish me luck!
Gary

Thanks in advance! Always glad to hear the interesting finds in a new device.
Sent from my GT-P6210 using Tapatalk

ah, yes... the "new" shared partitions in honeycomb (and ICS.) No longer is there supposed to be dedicated space for /data and /sdcard partitions. They are supposed to use the same space.
Actually, that makes sense. You never have to use something like app2sd, because it's all really the same space. How it gets there, however, is annoying (when trying to reverse engineer a gingerbreak CWM recovery to a honeycomb device.) There is no /sdcard parition on this thing. /sdcard is actually a remap of the /data/media directory. Nice.
My problem is getting CWM Recovery to understand that. pfft.
I wish I could find some source for a CWM recovery partition for another honeycomb tablet. that'd make my life easier, I think.

WARNING: Playing "world of goo" is a major distraction to getting other things accomplished.

have recovery making a nandroid. This would probably be easier if I knew what I was doing. Oh, btw, who wants to test this stuff for me?

garyd9 said:
have recovery making a nandroid. This would probably be easier if I knew what I was doing. Oh, btw, who wants to test this stuff for me?
Click to expand...
Click to collapse
Hey,
I'm also working on it, I'm an dev who ported CWM to the Galaxy Note.
Wait a few hours and you will have CWM

netchip said:
Hey,
I'm also working on it, I'm an dev who ported CWM to the Galaxy Note.
Wait a few hours and you will have CWM
Click to expand...
Click to collapse
I might have just beat you to it. I'll give you a hint, though: honeycomb does some things with partitioning thats very different from previous android versions. CWM tries to take some of that into account, but because of how /data is set up in recovery.fstab, it's not detected that /sdcard should really be /data/media. (I'm rambling.. heh..)
Anyway, pershoot worked this out, so if you pull a specific changeset from his github (https://github.com/pershoot/android...mmit/6dacf061b8476c3e3e2857ca078df95706d62770), and apply it to the CWM in the current cyanogen 7.2, everything should work.
Well, so far everything appears to be working. I've validated the backup works, but haven't verified the restore. I've also modified the code to discourage people from partitioning their sdcards (and it's a bug in CWM that they can choose that option when /sdcard is just a symlink to /data/media)
Anyway, I'll dump the image someplace if anyone wants to mess with it. I honestly have NO idea how to build any kind of package to automate installing it. I've been using "dd" all night long.

On second thought, maybe I'll go to bed... (been awake for over 24 hours)
I'm in the middle of testing the nandroid restores, and there's no way I'll post anything until I'm sure it works. Considering how tired I am, I'll feel better testing this when I'm rested.
One issue I'm REALLY getting annoyed by: For some reason, when I do a "adb reboot recovery", the tablet doesn't reboot into recovery. Even if I'm in a root shell, "reboot recovery" isn't taking me into recovery.
Good night!
Gary

garyd9 said:
On second thought, maybe I'll go to bed... (been awake for over 24 hours)
I'm in the middle of testing the nandroid restores, and there's no way I'll post anything until I'm sure it works. Considering how tired I am, I'll feel better testing this when I'm rested.
One issue I'm REALLY getting annoyed by: For some reason, when I do a "adb reboot recovery", the tablet doesn't reboot into recovery. Even if I'm in a root shell, "reboot recovery" isn't taking me into recovery.
Good night!
Gary
Click to expand...
Click to collapse
I think the kernel is not connected with HC
ICS == almost HC.
There we also don't need the patch

thank you guys so much! great job!

chrisrotolo said:
thank you guys so much! great job!
Click to expand...
Click to collapse
Is on this device the Download mode?
I compile my kernels from source, now I need a tester who don't care about warranty.
I use a module of the SGS2, I've contacted a few people experieced in param.lfs, and they say if the kernel can't mount it it says "logo.jpg not found" and it still boots further.
PM me if you are interested!

posted CWM Recovery.

this is habit forming.
the upcoming version will, in addition to being in a nice update.zip, will also install 'su' so you can root your tab and install recovery all at once.
I am _not_, however, installing the SuperUser application (which is needed as well.) That can easily be done from the market after installing this update file.
All will be documented soon.

I could swore I had an sdcard partition, under it's own or external
Sent from my GT-P6210 using xda premium

For the internal, it's not a real partition. The "/mnt/sdcard" mount is a FUSE link to /data/media. (It's a real parition on the external sdcard if you have one installed.)

I'm working with someone to get copies of the recovery and normal boot kernel partitions from the P6200 (international 3g.) Once I have that, and assuming my blind kernel compiles actually work, we'll have CWM recovery for that tablet as well.
Take care
Gary

I have an international 6200. If you tell me what you need and maybe some help in how to get it, I will dump whatever you want.
Z.

garyd9 said:
I'm working with someone to get copies of the recovery and normal boot kernel partitions from the P6200 (international 3g.) Once I have that, and assuming my blind kernel compiles actually work, we'll have CWM recovery for that tablet as well.
Take care
Gary
Click to expand...
Click to collapse
BTW, have you confirmed that recoveries are incompatible between variants? The 10.1 was "one recovery fits all".

Entropy512 said:
BTW, have you confirmed that recoveries are incompatible between variants? The 10.1 was "one recovery fits all".
Click to expand...
Click to collapse
Currently, they all share the same "recovery" binary (entire /sbin directory, actually), but they need different recovery.fstab files in the initramfs due to different /system (and /data, I think) locations. I'm not at home, so I can't check if it was only 'system' or both.
That one file being different causes them to have a different initramfs, and therefore a different zImage (recovery.img.) I once considered using init.rc to dynamically put a different recovery.fsab into place based on the tablet model at runtime, but how would I be able to determine the tablet model dynamically? default.prop would be useless (as it's also part of the recovery initramfs) and it wouldn't be a good idea for the RECOVERY to rely on the existance of valid data on any other partition. There are ways to take educated guesses based on partition counts and other strange things, but I don't think it's worth the risks.
I do have to admit that I've been having fun messing with this stuff.
Take care
Gary

Ah, that's odd/rare - kind of disappointing.

[Q] Samsung Stellar Verizon SCH-I200 Stock Firmware

So I accidentally bricked the new Samsung Stellar and my backups got wiped during the process.
Can anyone find the stock firmware/kernel for the Samsung Stellar?
Much appreciated.

sovereign73811 said:
So I accidentally bricked the new Samsung Stellar and my backups got wiped during the process.
Can anyone find the stock firmware/kernel for the Samsung Stellar?
Much appreciated.
Click to expand...
Click to collapse
mines isnt bricked but im looking for the same thing. Deleted some stuff I shouldnt have and no getting system ui force close. Let me know if you have an luck. Ill do the same

Do you still have the stock recovery? I may be able to get into my old OS if you can get the stock recovery pulled off.
Unfortunately I'm not sure how you will extract the recovery ROM off of your phone...I'll keep looking around.

mcarrion78 said:
mines isnt bricked but im looking for the same thing. Deleted some stuff I shouldnt have and no getting system ui force close. Let me know if you have an luck. Ill do the same
Click to expand...
Click to collapse
I'm curious, have you reinstalled the pesky stock apps to see if the OS crashes would stop? There may be something to that.
Also I possibly can help you get an image but I need a recovery image. If you're still rooted, download this:
http://android.podtwo.com/romdump/
Download Terminal Emulator from the Google Play Store and then follow these instructions:
http://forum.xda-developers.com/showthread.php?t=1771347
If I can get back into my phone by restoring the stock recovery, I may be able to get you an image that works.

Uh...OK...feel free to; it keeps the topic up fresh on the first page! lol.
Anyways I managed to theorize that a recovery is all I need....dang, looks like that's both of us now eh?

Im still rooted. im trying to figure out how to pull the recovery myself to possibly help in building CWM for the phone. I know removing some stock apps is what caysed my force close i just dont know all of the ones i deleted. I didn't think to back any of them up

I've got something up there that should help you pull out the stock recovery as well.
Romdump should work and should not brick anything so please give it a try.
sovereign73811 said:
Also I possibly can help you get an image but I need a recovery image. If you're still rooted, download this:
http://android.podtwo.com/romdump/
Download Terminal Emulator from the Google Play Store and then follow these instructions:
http://forum.xda-developers.com/showthread.php?t=1771347
If I can get back into my phone by restoring the stock recovery, I may be able to get you an image that works.
Click to expand...
Click to collapse

used romdump and this is what i get. it leaves me a text file thats 2.46 know that cant be it
c:\SDK\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # /data/local/romdump
/data/local/romdump
Android ROM dumper v0.82b
(c)2011 Sebastian404
Device : IMM76D.I200VRALG4
Creating required files... cat: can't open '/proc/mtd': No such file or directory
Opening mtd table... Segmentation fault
139|[email protected]:/ #

mcarrion78 said:
used romdump and this is what i get. it leaves me a text file thats 2.46 know that cant be it
c:\SDK\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # /data/local/romdump
/data/local/romdump
Android ROM dumper v0.82b
(c)2011 Sebastian404
Device : IMM76D.I200VRALG4
Creating required files... cat: can't open '/proc/mtd': No such file or directory
Opening mtd table... Segmentation fault
139|[email protected]:/ #
Click to expand...
Click to collapse
That's complicated. It looks like you use ADB from your PC. I'm curious, is your phone stable enough to run the Romdump from the phone itself? You will need terminal emulator to do this.
There is also a method that just works for recovery and boot partitions (the ones I and a few others need). Take a look here and scroll down to the heading that says "Alternative Method If The Above Does Not Work:".
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/

i get the same thing using terminal on my phone

http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
Have you looked at this link? It even has an alternate way to use romdump.

I don't know if this has anything to do with what we need for a stock ROM but here's something interesting:
http://androidforums.com/elite-all-things-root/551775-well-lets-get-ball-rolling-11.html
Again to any of you who have a rooted Samsung Stellar, please help us with a Stock ROM image!

heres the verizon stuff you were looking for
https://www.dropbox.com/sh/chkru9gi16k9ar8/G-DHp6SgnD

Thanks, although we already have that and we got a phone fixed for it...too bad not mine.
Hey did you get the message? Here I'll post it again:
OK people: here's a tip I've received from an XDA developer expert:
Quote:
a quick and dirty explanation (need root)
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/output.img
this will save the partition mmcblk0p1 to output.img
now, to determine what partitions are
on my device its:
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name/
but you're scheme and directory structure there might be a little different, so adjust accordingly
Longer Version:
http://www.darkyrom.com/index.php?th...with-adb.8059/

yeah i got that message and i got the output.img just havent uploaded it

What were you able to extract by chance?
If you could find a recovery partition, that would be great.

even in recovery its actually loaded to RAM and not mounted (this allows you to flash to it while in recovery)
do:
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name
(its msm_sdcc.1 on my device, yours may be different but it should be similar)
Click to expand...
Click to collapse
Another tip to extract and backup the stock recovery.

stock rom
hey so im reading the threads and i wanted to know some kind of update. Did people test out the stock rom yet? Any good news?

Yes, thankfully we've got them working (thanks invisiblek!) and I'll make a further update in a few hours.

Where is the thread for this at?
Has this been dropped all together? I was looking for some stock and/or stock-rooted roms for this thing. Any hope out there?