yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 7.7 Android Development] Y Ddraig Goch:
P4 - https://rapidshare.com/files/2298175628/mmcblk0p4.img?bin=1

P5 - https://rapidshare.com/files/2298175628/mmcblk0p4.img?bin=1

P6 - (/recovery) https://rapidshare.com/files/1289796625/recovery.img?bin=1

Let me know what you find and if you don't mind how you went about it. Have got to go and be sociable now :)
[Galaxy Tab 7.7 Android Development] ezynow:
looking in /sys/block/mmbclk0/

gives all the partition info - name,size,ofset, corresponds with pit info from heimdall.

also interested in this

Heres the info (not sure if it helps):

mmcblk0/mmcblk0p4

alignment_ofset	0

discard_alignment	4265607168

inflight	0	0

partition	4

partition_name	param

size	16384

start	57344

stat	25	118	1144	0	0	0	0	0	25	40

mmcblk0/mmcblk0p5

alignment_ofset	0

discard_alignment	4257218560

inflight	0	0

partition	5

partition_name	kernel

size	16384

start	73728

stat	0	0	0	0	0	0	0	0	0	0

mmcblk0/mmcblk0p6

alignment_ofset	0

discard_alignment	4248829952

inflight	0	0

partition	6

partition_name	recovery

size	16384

start	90112

stat	0	0	0	0	0	0	0	0	0	0

mmcblk0/mmcblk0p7

alignment_ofset	0

discard_alignment	4240441344

inflight	0	0

partition	7

partition_name	cache

size	409600

start	106496

stat	11	128	20	6	2	64	465	0	280	485

mmcblk0/mmcblk0p8

alignment_ofset	0

discard_alignment	4030726144

inflight	0	0

partition	4

partition_name	modem

size	32768

start	516096

stat	58	2560	20944	380	0	0	0	0	330	380

mmcblk0/mmcblk0p9

alignment_ofset	0

discard_alignment	4013948928

inflight	0	0

partition	9

partition_name	factoryfs

size	1703936

start	548864

stat	8796	407	701658	31365	0	0	0	0	15540	31325
[Galaxy Tab 7.7 Android Development] Y Ddraig Goch:
Thanks - that helps confirm what I had found by digging around and completes the list of partitions.

I have now extracted initramfs from both the runtime and recovery kernels.

Now I need to find time to do some reading on how to port CWM recovery.

Anyone know whats in the param partition?
[Galaxy Tab 7.7 Android Development] Y Ddraig Goch:
A quick update....

The partitioning for the 7.7 is very similar to the 7plus.

I have been in contact with the garyd9 who ported CWM to the 7plus and he has given us a few pointers including his github username.

See:-

http://xdaforums.com/showthread.php?p=21717604#post21717604

Interestingly he says that it's likely that the samsung's kernel source release will not have the correct defconfig so we are going to need to tweak it.

The recovery binary gets compiled from the Cyanogenmod sources which are easily obtained.

Unfortunately I'm going to be tied up with my day job for most of this week but will try and look at this again on Friday.

Is there anyone that can keep the ball rolling while I'm busy?

Thanks

Ddraig
[Galaxy Tab 7.7 Android Development] Dark-Master:
I'm getting this one and selling my Note. I'm so excited to see you guys working out of something for P6800 here.:)

Thanks to all devs in advance! :cool:
[Galaxy Tab 7.7 Android Development] ozren:
...........
[Galaxy Tab 7.7 Android Development] lucid:
+1 here

Anybody want to buy my outdated,used Note?

Hehehe.. well, at least I just *seconds ago* ordered my Tab 7.7 from ebay uk.

Let the modding and ROM flashing begin!
[Galaxy Tab 7.7 Android Development] maconsultant:
@Lucid what's wrong with your Note..?

Sent from another Galaxy...

Nexus
[Galaxy Tab 7.7 Android Development] lucid:
There is nothing wrong with my Note, it is the best phone I've ever had.

So I went ahead and bought the 7.7 to see if that one is even better. Needs to arrive still.

I intend to use it as a daily phone and will keep it to my ear if needed,

no matter the reactions of other people.

Gadgetwise, I live for myself, not the general public.

I might sell on of them, but history shows I keep all my "old" phones.
[Galaxy Tab 7.7 Android Development] maconsultant:
I use my galaxy nexus for day to day but since finding out about phoneleash i dont really touch my phone anymore.. check out phone leash if you have two SIMs.. although i guess it can work with GV also..

Sent from another Galaxy...

Tab 7.7
[Galaxy Tab 7.7 Android Development] monakh:
I placed my 7.7 next to my Titan, Sensation and the Galaxy Note today to see how it fares, no way is it practical to put to the ear and it is pretty ridiculous to carry. It's a compact device but not THAT compact. My Kindle Fire was more handy. The bezel is too large.

However, the phone functionality is superb and if one can find an unobtrusive way to carry it, we could finally unify our communication requirements in one device.
[Galaxy Tab 7.7 Android Development] burhanistan:
Check out the Samsung HM5000 Bluetooth pen thingy.
[Galaxy Tab 7.7 Android Development] ezynow:
Ddraig - I have been trying to get this get up and running.

So far I have managed to compile a zImage (recovery.img) using pretty much with the default config. Flashed through heimdall

I have used garyd9 recovery_initramfs, used his /sbin folder as is. The rest of the files are taken from the stock gt-6800 ramdisk inc modules. Where necessary make changes to partition entrys.

It boots in to clockworkmod recovery fine. It can mount all partitions but not /cache partition properly. I have checked the path and it seems correct ??

(I can mount via adb but cwm says it cant find it)

I will try building recovery binary at some point but will be busy for some days now.

I can you sent you some of my config files / recovery.img if it helps.
[Galaxy Tab 7.7 Android Development] kassemja:
Sounds like you have made some progress with custom recovery, you need to be careful if you are using garyd9 recovery_initramfs on your device, note one i think this for a wifi device being p6210 if you device is a p6800 check all the mounting points as there are some slight differences between wifi and 3g devices. how did you compile your source and make compatible odin file. i'm on a mac and so far i can't get heimdall to work with p6810.
[Galaxy Tab 7.7 Android Development] davp:
After 2 days of kernel building and insmod, I've finally got a P6810 module to insmod successfully into my stock device. This is the config. It comes from the samsung source (GT-P6810_HC_Opensource) download with some DEBUG params turned off, and the local version set for the Australian DTKL5 firmware. I hope it can help someone avoid some trial and error pain. The p6800 guys may be able to turn off similar debugs and get theirs working. This is not fully tested, if you find other params that need changing please advise.

EDIT: I flashed this kernel to my device and it worked.

Here is more information on the environment.

CodeSourcery toolchain arm-2009q3-67-arm-none-linux-gnueabi.bin

Change the supplied Makefile CROSS_COMPILE to point to installed toolchain (eg, /home/davp/toolchains/arm-2009q3/bin/arm-none-linux-gnueabi-)

Copy the supplied file to .config in the directory where you unpacked the kernel source, then run make

Links http://xdaforums.com/showpost.php?p=21870378&postcount=23 for how to do a basic initramfs to go with the new kernel (the result of this is running a command like: make -j5 CONFIG_INITRAMFS_SOURCE=initramfs_root, and then tar and flash the zImage).

Copy of the .config file (from the kernel directory):
[Galaxy Tab 7.7 Android Development] kassemja:
Can you confirm you have suscessfully compiled and flashed a working kernel?

I want to have a crack at custom recovery for the p6810, i'm pretty confident we can getting going using a blend of sources from https://github.com/garyd9/initramfs_recovery_GT-P6210 and our kernel stuff.
[Galaxy Tab 7.7 Android Development] Entropy512:
Oh great - the 7.7 also has binary-only modules?

Freaking Samsung, I thought they were making progress with the I9100/I777 (100% open-source kernels, no proprietary modules).

Good luck bedwa - feel free to browse my github for Exynos tips (although much of it will not directly patch onto HC kernels), garyd9 knows what he's doing too.
[Galaxy Tab 7.7 Android Development] davp:
No, I can just confirm that this config builds "a kernel". It also builds modules that load in my stock device (which was my goal when I started). I have a little more reading to do before I am confident how to check the kernel is good and to package and flash. Eg someone confirm similar config is good via a better method than trial and error. Also, if there is a way to direct write the kernel only to this device, so as to leave exactly the current initramfs etc, and just test new kernel in isolation (eg I mean the vmlinuz rather than the zImage)?
[Galaxy Tab 7.7 Android Development] kassemja:
From what i've read (kernel building on galaxy s2), the only way to check if you kernel works is to build intramfs (zImage) and flash. As we have odin and and recovery images there should be no reason why you couldn't restore to stock if you brick. I hoping to get CWM up running i will test a full and restore functionality and report back. Check this thread if you need help building intramfs. http://xdaforums.com/showthread.php?t=1442870
[Galaxy Tab 7.7 Android Development] davp:
Ok, I used a script called unpack-initramfs (https://github.com/mistadman/Extract-Kernel-Initramfs), to get my current stock DTKL5 initramfs. Then your link (thanks) to build DTKL5 initramfs with my new kernel. I kept all the original modules, so it was a kernel only change.

Then flashed with odin.

Guess what - it worked. I sent the screen shot via gmail/wifi, so the most important stuff is ok. (I need a cup of strong tea now).
[Galaxy Tab 7.7 Android Development] ezynow:
Nice one - davp.

Basically with a bit of luck, we can get an recovery initramfs with clockwork mod recovery working soon.

So far I have used only the parts of garyd9 recovery_initramfs which contains the binary of recovery in the /sbin folder and changed the fota.rc to look like his. (from memory). (The recovery binary is generic enough I think)

If you can do something similiar to the your stock initramfs_root folder. Make changes to all mount points in the *.rc files that might refer to something like

/system ext4 /dev/block/mmcblk0p* (check partitions shoud be 9). The main difference with garys is that his system is 8 and check all the other partitions off course. Also change the recovery.fstab file in /etc.

The rest of the files should be ok with the stock initramfs_root folder.

Also in default.prop => if you change (at the top) the ro.secure = 0 (you will get a root shell in adb). useful for debugging !!

Re-make linked to the modified initramfs_root and flash to recovery partition.

So far I can boot into clockword recovery but mounting of /cache is not working. All other partition seem to mount ok. Off course dont try backup and restore - just stating the obvious :)

Can you confirm the same behaviour?

Also I was digging in the clockwork recovey code ( if you look at root.c or something it tries to create an /etc/fstab by reading in the recovery.fstab.)

However the fstab file it creates is all screwed up so I am assuming its a bug iof some sort we should change the code or at least debug here.

I will not have much time to look into this over the weekend so appreciate any comments by you, kassemja.

And if you get a working recovery send it my way ;)
[Galaxy Tab 7.7 Android Development] kassemja:
Hi dvap, well done on getting your kernel going, i'm a little stuck on making intitramfs, can you tell me where (directory) to put your config file, what name should it be called. i'm about to compile a recovery image. cheers... great work.
[Galaxy Tab 7.7 Android Development] davp:
Its a copy of the .config file from my kernel source directory (I updated the original post).
[Galaxy Tab 7.7 Android Development] kassemja:
No dice stuck trying to get the cross compiler working keeps giving me errors cc1 and stuff, perhaps you can trying compling a recovery image. Are using a build script?
[Galaxy Tab 7.7 Android Development] VeEuzUKY:
As much as I love the "idea of the 7.7 tab, its too late. This thing was announced almost 5 months ago, never happened, now it comes out still with HoneyComb.. Aside from a fabulous screen, the truth is the specs are absurd with stuff the same 3MP camera the 7.0 Tab had over a year ago. This is an interim product not worth a lot of time IMO. Had a Samsung released it in September great, but now, they released the 7.0 Plus that also makes little sense and now this.

The announced 8.2 (or some say 8.3) Tab with EXACT same form factor and just a slimmer bezel sporting a quad-core processor an ICS native is around the corner.. that will be the real deal..

Ill wait for that.. I still have the original tab 7.0, its great, the 7.0 plus is a waste and the 7.7 is great but outdated in every way aside from having a great screen.. the next quad-core version with larger display, same form factor with a slimmer bezel is the real upgrade deal.. the 7.7 is a waste of time....

My 2 cents:)
[Galaxy Tab 7.7 Android Development] ezynow:
what has this got to do with anything :confused:
[Galaxy Tab 7.7 Android Development] davp:
Attempted today to build recovery image from stock recovery initramfs and my kernel. Unfortunately no luck, it wont enter recovery and after a while boots normally.

Heres what I tried using my new kernel:

(1) extract initramfs from stock DTKL5 recovery.img firmware

build zImage with their modules in initramfs

rename zImage to recovery.img

tar+flash with odin

(2) as above but with my modules plus their stock jfs4.ko

Flashed tar of stock recovery.img, all back to normal.

Edit. Got it working ok.
[Galaxy Tab 7.7 Android Development] davp:
Edit: ok. I see your cache mount messages now:

CWM-based Recovery v5.0.2.7

E:Can't mount /cache/recovery/command

E:Can't mount /cache/recovery/log

E:Can't open /cache/recovery/log

E:Can't mount /cache/recovery/last_log

E:Can't open /cache/recovery/last_log

Further edit:

fstab screwup is due to cr/lf in the recovery.fstab file. Removing the cr's from the recovery.fstab in the initramfs

then generates ok fstab, no more cache mount error for me.

Latest edit:

Heres the P6810 initramfs I am using, it seems to work ok for me. Remember partition numbers will need changing for the P6800!

ezynow and kassemja, please compare with yours, any comments appreciated.
[Galaxy Tab 7.7 Android Development] kassemja:
Win..... port of garyd recovery for p6810 working, backing up now will report back on sucess.
[Galaxy Tab 7.7 Android Development] ezynow:
cheers davp,

forgot to do the dos2unix conversion on the sammy stuff. :rolleyes: so mounting should be fine for me also.

have you done a nandroid backup? also a restore?

assuming, gary9d has changed what partitions are backed and restored up in his cwm binary. As we have the same partition structure as the 7.0 plus, just different mount points, it should be ok for our tabs. cant be sure without his source files.

but great if all is ok -cheers gary :)

Davp / kassemja you might as release a flashable tar of the recovery.img so other people can test it working.

ill do the same for the 6800 when i get the chance later today or send it to you guys to put in one post.
[Galaxy Tab 7.7 Android Development] davp:
Backup/restore yes, a few advanced restores yes, wipe cache yes.

Wipe Dalvik Cache - Yes, seems ok, bit of a delay starting up after.

Other options NO (not enough time).

Some things to consider:

Remember garyd9's partitions match for P6810, so bigger risk is with any binary or porting errors for P6800.

Remember if this is installed on the wrong device a restore could (and probably will) trash it!

If there is some combination that splats the efs partiton on a 3G device,

if they are anything like the phone efs partion, the IEMI will be clobbered and

it is NOT recoverable (except back to samsung) without a proper backup.

I dont think the CWM backups cover this area - maybe the tabs are different?

Other tools have some problems with this device. This could also be a worry, remember ozren got his in bootloop with Titanium and some cleanup option. I've just reflashed a friends 7.7 that went into bootloop after pressing some performance enhance button on an app called VM HeapTool.

I urge some level of testing, due caution, or a lot of warnings/care before posting an easily flashable tar. Remember garyd9 has carefully arranged his rom manager so it cannot be installed on other than the intended model (wifi only). We cant protect a flashable that way.

I wasnt sure which redbend? (going from memory) should go in, in the end I decided to use the one from our device rather than garyd9's. What do you think?
[Galaxy Tab 7.7 Android Development] DiP7:
ClockworkMod Recovery 5.0.2.7 for Samsung Galaxy Tab 7.7 (GT-P6800)

http://www.max-up.ru/news-apple/clockworkmod-recovery-5027-samsung-galaxy-tab-77-gt-p6800.html
[Galaxy Tab 7.7 Android Development] ezynow:
Hey Dip,

Good to see you on the 7.7. Hopefully u get up to ur old tricks :)

Is this the cwm versioned modified by you. Any major changes from stock cwm

Just been looking at cwm. I have garyd9 cwm for the 7.0 plus on mt gt-p6800 tab. It seems to be working properly. Looks like stock cwm.

Our tab has a seperate kernel partition and recovery partition. Stock cwm does not back up/restore the kernel partition (zImage).

Does the /boot mountpoint in recovery.fstab point to /kernel partition?

Edit - garyd9 does backup the /kernel in recovery fstab it points to this partiton.

Edit - Dip looks like ur /boot in recovery.fstab points to actual bootloaders ????? :confused:
[Galaxy Tab 7.7 Android Development] ezynow:
Just a quick update - I was using the defaut recovery.fstab from the recovery initramfs.

the /boot pointed to my actual bootloader partition sbl.bin.

Very Bad idea to backup / restore this in cwm.

This partition needs to point to the path of the zImage partition. (kernel)

Anyway - just a shout out for anyone.
[Galaxy Tab 7.7 Android Development] davp:
Thanks, if you have time can you check the initramfs I posted to see if I have same mistake. I wont be able to check/rebuild till I get back from work. Edit: ok the file sizes are wrong, I do have the same mistake! cheers

Further edit: fixed and tested with restoring boot between stock and insecure.
[Galaxy Tab 7.7 Android Development] bedwa:
So excited to see the progress here since I pulled and put up the git. I JUST got my 7.7 Mon, been searching github for other exynos projects for OC/UV commits and other improvements. Fortunately most tweaks for the exynos proc has been done (similar to Hummingbird proc and Infuse when I started), but unfortunately it means I won't be able to make many of my own tweaks. It's time to get cracking on a SamTabulous kernel. ;)

Edit: Guys, feel free to make commits for basic compiling purposes. The initial git repositories are supposed to be a starting point for any dev, new or experienced to use. :)
[HTC EVO 3D] bsintzel:
Folks,

I just bought two new HTC EVO 3D's from Rogers. They came loaded with crap apps that can't be removed and that doesn't sit well with me.

What I know today: HBOOT=1.49.0008 and they're S-ON.

I'm not entirely sure if the GSM rooting instructions I found here (by happyhillsy8) apply as they run over the Rogers UMTS network. As I understand it, UMTS is a GSM variant.

Question:

1 - Do GSM rooting instructions apply to these devices?

2 - How do you determine which ROM version they have?

Thanks in advance
[HTC EVO 3D] alexjzim:
well there are a few different ways to root the 3d. The simplest and most effective imo is revolutionary (revolutionary.io). The program is compatible with the evo 3d gsm with your hboot, just make sure you dont upgrade it before using the program. the complete list can be found here:

http://unrevoked.com/rootwiki/doku.php/public/revolutionary

as for determining which rom, im not quite sure what you mean. You can figure out which rom you have by going into your settings and looking at your software information. If you're asking about which roms work on the gsm 3d, theres a whole gsm developement section.

Cheers. I just got my evo 3d (cdma) a few hours ago, and rooted with revolutionary. running infectedrom. works great
[Samsung Infuse 4G] endine:
Hey guys, I flashed Miui yesterday and I really dont like it, so I was going to try something else but now I can not get in to recovery. Ive done some research and I need the CWM Community Kernel v8, unfortunately since multiupload is down/gone I cannot download it. Does anybody have a copy they can send me? I have the sgs kernel flasher.

PS, Ive tried flashing different recoveries, google searched the kernel but the links are dead.

Thanks,

e
[Samsung Infuse 4G] Rocket42:
i think i may have found someone to get it to you if you still need it....i gave them the link to this post
[Samsung Infuse 4G] CheesyNutz:
uploaded this to my dropbox

http://db.tt/rKViw0Wj
[Samsung Infuse 4G] endine:
Thanks for the help!
[Samsung Infuse 4G] xolanir:
I was in the same predicament and now I'm wondering, is this Odin/sgs kernel flashable? Thx
[Samsung Infuse 4G] CheesyNutz:
CWR flashable and yea you can use sgs to flash this
[Samsung Infuse 4G] THRiLL KiLL:
thankyou for this post!!!
[HTC Rezound] awenthol:
Would anyone be willing to mod the ICS Mail.apk to bypass security setup? I already tried the GB Sense 3.5 Mail.apk I have, and it's a no-go.
[HTC Rezound] dmoses1969:
I would like this also. Anyone that can do this?
[HTC Rezound] Fenny:
Here you go. :D

And since I am in some sort of mood... This is a quote that I demand may or may not be accurate:
[HTC Rezound] awenthol:
Thanks for helping with this one also...just when I get GB Sense 3.5 mail.apk taken care of, they throw this my way :D
[HTC Rezound] dmoses1969:
Yes, thank you very much.

Sent from my ADR6425LVW
[HTC Rezound] dmoses1969:
Could you please do the same thing with this one? This is from the BAMF ISC rom recently posted. It is a little bigger in size compared to the last ICS Mail.apk you fixed. Must be the reason why I cant use it.

Edit: Well, looks like it is actually the same size as the one in op but for some reason every time i try to add my exchange account it force closes as soon as I click on exchange active sync. It goes a little further on some of the other types of accounts but eventually force closes.

Thank you very much.
[HTC Rezound] awenthol:
I never did get around to loading ICS, gonna have a go now that we have an "official" ROM. Can anyone confirm I need to do this again with the latest (ie, Sense 3.6) apk?

If so, I'd be willing to put up a bounty again....
[HTC Rezound] dmoses1969:
Try this one :D

http://xdaforums.com/attachment.php?attachmentid=938812&d=1331295706
[HTC Rezound] sirtom1:
Is there a newer one that will work with cm10 / android 4.2.1 ?
[HTC Rezound] hgoldner:
Try the one in this thread.
[Optimus One, P500, V General] klstreet:
Is it possible to port a rom for Optimus one to an Optimus V? If so what would have to be changed, I realize the kernel most likely will, but what else?
[Optimus One, P500, V General] culmea:
Theoretically, no.
[Optimus One, P500, V General] NicoC72:
People port ROMs from one phone to another all the time, so yes, you can. The Optimus V is a Optimus One phone anyways. There are some differences, but its not like a GSII to Optimus V, which I think can not be done.
[Optimus One, P500, V General] ken2kold:
so it can work like seriously???
[Optimus One, P500, V General] ccdreadcc:
no dont fash p500 rom...

flash when its ported by devs only
[Optimus One, P500, V General] skarookidoo:
What ROM are you thinking? I have miks CM7 running on my Optimus T.
[Optimus One, P500, V General] ken2kold:
can that rom run on a optimus v???
[Optimus One, P500, V General] NicoC72:
My guess is no. Optimus V uses different signals then the rest of the Optimus One line, if it didn't we would have an Optimus S without the bloatware.
[Optimus One, P500, V General] klstreet:
I wanted yo do the porting on my own as a learning experience so I was mainly wondering what the differences in the phones are and what all I'd have to change as far as kernel anxious build props etc
[Off-topic] LiLChris06:
Looks like Multiupload is currently down, anyone have an idea if this is related to Megaupload?

Is RS, Dropbox, 4shared etc next?

Many roms/themes have been uploaded there, is torrents are next alternative? :eek: