yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 4 Original Android Development] MrHomebrew:
THERE ARE THE PHOTOS FROM MY GALAXY TAB 4.

These would be the correct locations I need clarification so I know which ones are boot and recovery for pulling/extracting in terminal.
[Galaxy Tab 4 Original Android Development] pre4speed:
These two represent your recovery and boot partitions. So in the quotes you'll put the mmcblk0p15 for recovery.img.

I found that pulling the recovery is that exact code, whereas pulling the boot was a different code, but found easily on the internet. I got the recovery easy, the boot was a little more work, but did get it.
[Galaxy Tab 4 Original Android Development] MrHomebrew:
Think I am not typing it exactly how it needs to be. Even tried copy and pasting. So close but yet so far lol. I really think we have all been making progress the last few days. This would help if I could get it to work. Would be useful and handy to have a backup for each device variation.
[Galaxy Tab 4 Original Android Development] MrHomebrew:
Pic did not upload for me the first time. Backup did not work yet. I must be typing or copy and pasting wrong
[Galaxy Tab 4 Original Android Development] pre4speed:
I'm trying to remember how I did it. I believe you open terminal, type su then press enter, then type the rest. Let me do it again and see what my steps were.

---------- Post added at 01:26 PM ---------- Previous post was at 01:13 PM ----------

Ok, I'm sorry. The code I gave you is actually for the boot.img not recovery. Here is the right code. Sorry again.

Type it exactly as I did and you'll find the backup on your sdcard (not external). I actually found the correct code in the 7.7" tab thread. Lol http://xdaforums.com/showthread.php?t=1540641
[Galaxy Tab 4 Original Android Development] MrHomebrew:
I'm just out right now but will give it a try as soon as I get home. Thanks again much help. Will report back.
[Galaxy Tab 4 Original Android Development] MrHomebrew:
Ok I have got both recovery and boot.img backed up/pulled. Finally lol thanks a lot
[Galaxy Tab 4 Original Android Development] MrHomebrew:
I think we have most of the necessary files to get the job done. If you say you have got you boot.img and recovery backed up and so do I. We have source files also. All we need now is for the recovery to be compiled. For a skilled experienced developer to finish up what we started probably would not be too hard. If only we had someone to really take the time with us with some of the next key steps. I am looking up guides and resources all over the Internet but nothing concrete to get the job done ?
[Galaxy Tab 4 Original Android Development] pre4speed:
Yeh, I hear that. Like I said before, I've got my buddies looking at it, but these devices that they don't own aren't a priority for them. I don't feel right bugging them about it every day. I'll see if there's anything I can find. I'm not a developer and get lost with code, but guides I can help to find if you have the build environment.

http://rootzwiki.com/topic/23903-how-to-compile-twrp-from-source/

http://xdaforums.com/showthread.php?t=1943625

I am so lost with all that[emoji30]
[Galaxy Tab 4 Original Android Development] sub77:
if you are able to install an omnirom build environment on linux i will make you a local_manifest and show how to build.
[Galaxy Tab 4 Original Android Development] MrHomebrew:
I am going to install Linux in vmware. My computer has 8gb of Ram so I can dedicate 4gb to Linux.

I looked up the link you put up I just want to clarify that these are the steps I need to take for preparation and make sure I know where to stop with the preparation. Half way down the page it says Mac OS X so I am guessing from that point on the instructions are strictly for a mac.

Pictures to show what I mean. Last picture would be the last step for building the environment if I am not mistaken.

Is there a version of Linux you would recommend or be able to put a link up to? If not I will just grab Ubuntu Linux or something.
[Galaxy Tab 4 Original Android Development] MrHomebrew:
UPDATE I'M thinking this would be my last step for installing environment with Ubuntu Linux.
[Galaxy Tab 4 Original Android Development] sub77:
can someone pls try my twrp build for tab 4 8.0.

TWRP2810_10272014-SM-T330NU
[Galaxy Tab 4 Original Android Development] MrHomebrew:
No file in link
[Galaxy Tab 4 Original Android Development] MrHomebrew:
Ext4
[Galaxy Tab 4 Original Android Development] sub77:
dont install. doesnt boot
[Galaxy Tab 4 Original Android Development] MrHomebrew:
Not yet but hopefully it is an easy fix. Fingers crossed
[Galaxy Tab 4 Original Android Development] rsktkr1:
Hey, I installed Ubuntu to my Winbook 8" tablet which runs Windows 8.1 via vmware player and installed Ubuntu and VMware on my SDcard (64GB). Are you planning to install it on your SMT330NU which runs Android? I did not know VMWare player had a version for Android or maybe I am confused. I have the Samsung Galaxy Tab 4 8 too. I tried to install Linux on my Tab with a couple apps that are out there (Linux Installer, etc.) but would not work. Oh by the way my Winbook only has 2 megs of ram so I only allocated 1 meg of ram to Ubuntu and it runs pretty good. I also enabled quad core on the VMwareplayer for Ubuntu - can't really tell if it is using all four cores of my Winbook Anton processor. I used Gnome 3 as my GUI as it won't show full screen if you use Unity or something. If you go into terminal and type the word "onboard" (no quote marks) it will enable the oncreen keyboard. There are also other settings to enable the onscreen keyboard so you don't have to execute the command in terminal - since you need to be able to type to run terminal.

Maybe you were talking about running Ubuntu on your desktop. I am running Ubuntu too on my desktop with VMPlayer.

---------- Post added at 08:02 PM ---------- Previous post was at 07:50 PM ----------

Now back to the Tab 4 8 - well still really anxious for the recovery for this device. Again, if you guys need some leg work or something let me know.
[Galaxy Tab 4 Original Android Development] MrHomebrew:
I got Linux up and running and omni build environment done at the moment.
[Galaxy Tab 4 Original Android Development] sub77:
congratulations, can you please test my second twrp build: i cant, because i have just the tab 4 10.0

TWRP 2.8.1.0_milletwifi_b2
[Galaxy Tab 4 Original Android Development] MrHomebrew:
Appreciate all the help and support considering this is not your day to day device.

Currently I get put into download mode when trying to load recovery with this version. I have sent some info to you. If anyone else would like to give it a try it is worth a shot but be warned I tried and got forced into download mode.

To fix that issue and get your tab working again just flash stock Samsung Rom using Odin and let your tab boot back up. Do not restore factory settings in recovery there is no need if you are just trying to get your tab back up and running after giving this a try.
[Galaxy Tab 4 Original Android Development] smknutson:
Can confirm it sends you to download mode. So if you odin the stock Rom and just reboot, everything should be good?
[Galaxy Tab 4 Original Android Development] MrHomebrew:
Yes just flash stock Rom in odin and just let the phone reboot. All your apps and settings will be as they were before you tried the recovery. And yes stock recovery will be back.
[Galaxy Tab 4 Original Android Development] MrHomebrew:
I was in a car accident and have had a lot of things to take car of the last few days. Very stressful and busy stuff
[Galaxy Tab 4 Original Android Development] Darkman:
Hi Guys,

any News about a Recovery?

I have the new Galaxy Tab Active . This is based on the Tab 4 8" and i need now a Custom Recovery too.

The Devices have the same base etc and what we need is a Device Tree for this Devices. Then we can make a Recovery.
[Galaxy Tab 4 Original Android Development] pre4speed:
Hey Darkman, I've used your ROMS on the note 10.1 og. We still have one person working to get a recovery for us, but it seems to be bootlooping, so still at the drawing board. Source is there, just not any developers that own it. I had to go to someone who is trying to make a recovery without the device so it's slow. I know you are a bit more knowledgeable in the area of building, so possibly you can jump start.
[Galaxy Tab 4 Original Android Development] Darkman:
We need to make a Device Tree for the Tab 4 / Tab Active. Then i can try to make a Recovery.

But i need an other Device wich is using the CPU Qualcomm MSM8926 and have a working Recovery. So but i can find one....
[Galaxy Tab 4 Original Android Development] pre4speed:
I have the 337a which uses Qualcomm. That is the recovery that I am trying to get built.
[Galaxy Tab 4 Original Android Development] sub77:
http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device

And the kernel source. You dont need a complete device tree for building a custom recovery
[Galaxy Tab 4 Original Android Development] drsn0w:
I'm currently cloning the omni repo, i'm going to try a few builds myself.
[Galaxy Tab 4 Original Android Development] drsn0w:
I know this thread is mainly about TWRP but i'm working on building CWM for this device now. Running a build right now. I only have an FX-6300 so it's going to take some time, i'll post results when it comes out.

---------- Post added at 04:37 AM ---------- Previous post was at 03:48 AM ----------

The build dumps me into download mode :(

---------- Post added at 04:53 AM ---------- Previous post was at 04:37 AM ----------

Downloading the stock firmware now...perhaps the bootloader is locked and that's why its kicking us into download?
[Galaxy Tab 4 Original Android Development] pre4speed:
I know the 337a is locked.
[Galaxy Tab 4 Original Android Development] drsn0w:
any way of getting it unlocked? I have the 337T
[Galaxy Tab 4 Original Android Development] pre4speed:
Mine is locked by the wonderful giant att. You're t-mobile so yours, in theory because tmo doesn't usually lock their devices, is unlocked.
[Galaxy Tab 4 Original Android Development] drsn0w:
Right, I forget that Samsung usually leaves bootloader locking to the carriers. How can I tell if it's locked or not?

---------- Post added at 03:19 PM ---------- Previous post was at 03:16 PM ----------

Though technically wasn't the Galaxy S3 the last device to not be bootloader locked by Samsung itself?
[Galaxy Tab 4 Original Android Development] pre4speed:
You are correct, the S3 for att was not bl locked. As for finding out about locked bl, I only found out when I flashed a recovery a developer made and got the unauthorized software message. You may have better luck contacting t mobile for verification. Att is useless in that department.
[Galaxy Tab 4 Original Android Development] drsn0w:
I'll contact them later today (:

I didn't get any sort of unauthorized software warning though, just kicked into download, which I assume isn't anything to do with the bootloader if a locked one gives the unauthorized software message
[Galaxy Tab 4 Original Android Development] :
d,

hi,

it's possible the kernel source is wrong, even if it is the official release, samsung has proven to be a little on the sloppy side.

check your boardconfig for dt image settings if required

in BOARD_MKBOOTIMG_ARGS should be an entry --dt dt.img

as well as the entry

BOARD_KERNEL_SEPERATED_DT := true

additionally you need

device_qcom_common_dtbtool.

m
[Galaxy Tab 4 Original Android Development] drsn0w:
I'm not using the kernel source, i'm using the kernel pulled out of a boot.img using mkvendor.sh. Maybe i'll try using the kernel source. I'll also try with those flags you said. where does "device_qcom_common_dtbtool." go?
[Galaxy Tab 4 Original Android Development] :
hi,

goto the main git for the distro your building through and in the

search repository field enter

device_qcom_common

look around in that area just to get the idea of the layout

now back at device_qcom_common on your right hand side you see a field with the cloning url above a link to optionally

download that portion of the source as a zip file.

for cloning

navigate to device/qcom/ and open a terminal, enter

git clone the/url/you/copy/from/the/field/i/mentioned

when cloning is done rename the cloned directory to common

for zip

after the zip is downloaded , extract to device/qcom/ and rename to common

m
[Galaxy Tab 4 Original Android Development] drsn0w:
I'll try that, but since I cloned the whole Cyanogenmod repository, shouldn't that already be there? Or is it some weird thing with git?

---------- Post added at 06:09 PM ---------- Previous post was at 06:01 PM ----------

I'm building a new image :P

---------- Post added at 06:10 PM ---------- Previous post was at 06:09 PM ----------

So this happened

----- Made recovery filesystem --------/home/server/android/system/out/target/product/milletltetmo/recovery/root
----- Making uncompressed recovery ramdisk ------
/home/server/android/system/out/host/linux-x86/bin/mkbootfs /home/server/android/system/out/target/product/milletltetmo/recovery/root > /home/server/android/system/out/target/product/milletltetmo/ramdisk-recovery.cpio
----- Making recovery ramdisk ------
/home/server/android/system/out/host/linux-x86/bin/minigzip < /home/server/android/system/out/target/product/milletltetmo/ramdisk-recovery.cpio > /home/server/android/system/out/target/product/milletltetmo/ramdisk-recovery.img
----- Making recovery image ------
error: could not load device tree image 'dt.img'
make: *** [/home/server/android/system/out/target/product/milletltetmo/recovery.img] Error 1
server@ubuntu:~/android/system$

---------- Post added at 06:11 PM ---------- Previous post was at 06:10 PM ----------

sorry for the barrage of replies, I probably should make the dt.img first :)
[Galaxy Tab 4 Original Android Development] :
hi,

dt.img making should be handled by the mkbootimg script in your device tree.

you won't download everything in the cyanogenmod build environment by default

additional resources may need to be added via a local_manifest.xml or seperately

as you determine what you need by git-hopping through cm's repo and cloning.

re-examine your device tree and compare to what others you can find on git-hub to

determine what you may need.

m
[Galaxy Tab 4 Original Android Development] drsn0w:
I'm still not sure how to get the dt.img. I've tried guids using dtbTool but it doesn't seem to work...and it wont automatically do it when i make recoveryimage
[Galaxy Tab 4 Original Android Development] :
d, okay i think i got it

this isn't exactly perfect though

extract and place the attached file in your device tree

and in boardconfig.mk add the line in kernel section

BOARD_CUSTOM_BOOTIMG_MK := device/samsung/milletltetmo/mkbootimg.mk

adjust for your device name, i am using this file for milletwifi

which i orignally used for matissewifi

also in you package manager install device-tree-compiler , which is more for kernel builds outside of android trees

but still useful.

Target dt image: /media/Storage/pac-rom-44/out/target/product/milletwifi/dt.img
/media/Storage/pac-rom-44/out/host/linux-x86/bin/dtbToolCM -2 -o /media/Storage/pac-rom-44/out/target/product/milletwifi/dt.img -s 2048 -p /media/Storage/pac-rom-44/out/target/product/milletwifi/obj/KERNEL_OBJ/scripts/dtc/ /media/Storage/pac-rom-44/out/target/product/milletwifi/obj/KERNEL_OBJ/arch/arm/boot/
DTB combiner:
Input directory: '/media/Storage/pac-rom-44/out/target/product/milletwifi/obj/KERNEL_OBJ/arch/arm/boot/'
Output file: '/media/Storage/pac-rom-44/out/target/product/milletwifi/dt.img'
Found file: msm8226-sec-milletwifieur-r04.dtb ... Old Version:1
chipset: 3339255553, rev: 131072, platform: 8, subtype: 0
Found file: msm8226-sec-matissewifi-r03.dtb ... Old Version:1
chipset: 3339255553, rev: 131072, platform: 3, subtype: 0
Found file: msm8226-sec-milletwifieur-r00.dtb ... Old Version:1
chipset: 3339255553, rev: 131072, platform: 4, subtype: 0
Found file: msm8226-sec-matissewifi-r00.dtb ... Old Version:1
chipset: 3339255553, rev: 131072, platform: 0, subtype: 0
Found file: msm8226-sec-milletwifieur-r05.dtb ... Old Version:1
chipset: 3339255553, rev: 131072, platform: 9, subtype: 0
Found file: msm8226-sec-matissewifi-r01.dtb ... Old Version:1
chipset: 3339255553, rev: 131072, platform: 1, subtype: 0
Found file: msm8226-sec-milletwifieur-r02.dtb ... Old Version:1
chipset: 3339255553, rev: 131072, platform: 6, subtype: 0
Found file: msm8226-sec-matissewifi-r02.dtb ... Old Version:1
chipset: 3339255553, rev: 131072, platform: 2, subtype: 0
Found file: msm8226-sec-milletwifieur-r03.dtb ... Old Version:1
chipset: 3339255553, rev: 131072, platform: 7, subtype: 0
Found file: msm8226-sec-milletwifieur-r01.dtb ... Old Version:1
chipset: 3339255553, rev: 131072, platform: 5, subtype: 0
=> Found 10 unique DTB(s)

Generating master DTB... completed
Made DT image: /media/Storage/pac-rom-44/out/target/product/milletwifi/dt.img
----- Making recovery image ------
/media/Storage/pac-rom-44/out/target/product/milletwifi/recovery.img maxsize=280203264 blocksize=135168 total=10307584 reserve=2838528
Made recovery image: /media/Storage/pac-rom-44/out/target/product/milletwifi/recovery.img
root@kali:/media/Storage/pac-rom-44# \

m
[Galaxy Tab 4 Original Android Development] drsn0w:
I'll do that as soon as I get back home ~20 minutes. thanks!!!

---------- Post added at 08:33 PM ---------- Previous post was at 08:07 PM ----------

No rule to make target 'dtbToolCM'
[Galaxy Tab 4 Original Android Development] :
d

hi,

did you download/clone device_qcom_common ?

https://github.com/CyanogenMod/android_device_qcom_common

m
[Galaxy Tab 4 Original Android Development] drsn0w:
I did, into device/qcom right, then rename the folder to common
[Galaxy Tab 4 Original Android Development] :
d

hmm, okay post your boardconfig.mk as a text attachment to your next post.

ensure mkbootimg scripts is in your device tree.

it's late and i'm crashing but i'll look at it in the morning and hopefully find what's missing. :good:

m
[Galaxy Tab 4 Original Android Development] drsn0w:
Thanks, here's the BoardConfig and a screenshot of the directory
[Galaxy Tab 4 Original Android Development] :
ahh, you're missing your dt.img :p

your entry from boardconfig

BOARD_MKBOOTIMG_ARGS := --dt dt.img

should look like this [maybe]

BOARD_MKBOOTIMG_ARGS := --dt device/samsung/milletltetmo/dt.img

but according to your directory listing, you do not have a dt.img

try a build with the following lines commented out

#BOARD_CUSTOM_BOOTIMG_MK := device/samsung/milletltetmo/mkbootimg.mk

#BOARD_MKBOOTIMG_ARGS := --dt dt.img

#BOARD_KERNEL_SEPARATED_DT := true

additionally i don't see the necessary flags for your recovery build, this is a general idea from my boardconfig

# Recovery cwm/philz
DEVICE_RESOLUTION := 1280x800
RECOVERY_SDCARD_ON_DATA := true
COMMON_GLOBAL_CFLAGS += -DNO_SECURE_DISCARD
BOARD_HAS_LARGE_FILESYSTEM := true
BOARD_HAS_NO_MISC_PARTITION := true
BOARD_HAS_NO_SELECT_BUTTON := true
BOARD_RECOVERY_SWIPE := true
BOARD_USES_MMCUTILS := true
BOARD_USE_CUSTOM_RECOVERY_FONT := \"roboto_10x18.h\"
TARGET_RECOVERY_FSTAB := device/samsung/milletwifi/recovery.fstab
TARGET_USERIMAGES_USE_EXT4 := true
TARGET_RECOVERY_PIXEL_FORMAT := "RGBX_8888"

i would definitely recommend using the inline/integrated kernel build instead.

m
[Galaxy Tab 4 Original Android Development] drsn0w:
hmm. good advice. I'll try this tomorrow. it's given me a headache so I'm done for today (:

---------- Post added at 11:47 PM ---------- Previous post was at 11:44 PM ----------

I did do a build without the dt things and it kicked me directly to download, but now I'm wondering if that's because I somehow neglected to put those other options in the BoardConfig. I was following the CyanogenMod porting guide and there wasn't any mention of those options, but they do make a lot of sense... :P
[Galaxy Tab 4 Original Android Development] corrystile:
Hello,

i would like to build a rom too (Galaxy Tab 4 7.0), or port a cyanogen one, i know some C and C++ (i know that aren't needed to build a rom), but what are you using to build a rom based on the samsung rom? Android Kitchen? ArchiKitchen? I have a Mac, and Vmware, so no problem using windows or mac.

Thanks in advance :o
[Galaxy Tab 4 Original Android Development] troy5890:
Do u have a 64-bit computer
[Galaxy Tab 4 Original Android Development] corrystile:
Yess, on vmware or phisically another pc, so no problem
[Galaxy Tab 4 Original Android Development] troy5890:
Of u do make a custom rom for the 7 inch, I wish u look my friend
[Galaxy Tab 4 Original Android Development] corrystile:
Yeah, i will get a look on how to port and build a rom, im now installing cygwin.

PS: If someone have tips for a noobie is welcome.
[Galaxy Tab 4 Original Android Development] corrystile:
Installed successfully cygwin and tried to build a small rom deoxed, zipalligned, prerooted, with app2sd, seems to be a little bit easy but so much hard. I will study more how to port cyanogen on a tab like that.
[Galaxy Tab 4 Original Android Development] troy5890:
So u managed to install cygwin and your going to build/port a rom?
[Galaxy Tab 4 Original Android Development] corrystile:
I will try to build one. For sure i will release a stock one with app2sd, deoxed, zipalligned, prerooted, free by all the locks and similar
[Galaxy Tab 4 Original Android Development] corrystile:
Finally i succeeded to build a rom, only a stock one (will try to build a port or something of mine in these days):

GALAXY TAB 4 7.0 (7'') SM-T230 BASE FIRMWARE

-DEOXED

-Zipalligned

-App2sd built in

-PREROOTED

-Customization enabled

-Will not wipe data

-Better ram usage (?)

Can someone try that? My Tab 4 is on shipping phase (have bought it through ebay), so i cannot try.

Let me know

Here you are: https://www.dropbox.com/s/a0hwpm48uuvnmeb/Tab_4_7i_CLEAN-STOCK.zip?dl=0

Download the file and flash it through a custom recovery.

EDIT: Only for TAB 4 7 inch (SM-T230)
[Galaxy Tab 4 Original Android Development] troy5890:
Good job man hope u can port cyanogenmod to this device.
[Galaxy Tab 4 Original Android Development] wire55:
Hopefully we can get cyanogenmod on the sm-t330/no soon. Would really like a custom rom.
[Galaxy Tab 4 Original Android Development] rsktkr1:
I only installed the one I guess you made for TWRP - Thanks I like it. Has anyone tried the Clockwork Mod recovery - that one does not want to download for me. I think I like TWRP better and can use it with Rom Manager now. If there were not people like gr8nole this device would go nowhere.
[Galaxy Tab 4 Original Android Development] JustZaphod:
I expected more out of a Samsung Device.. But Samsung has the market over saturated and they just have way to many devices available, too much choice that it makes it hard for a developer to keep up.. Its a decent device with good battery time..

This tablet was released back in May, and like 1 week ago we just finally got a TWRP port.. I seriously doubt that this tablet will get a Cyangenmod port, or any custom rom...Unless someone has a passion for this device.. If I didn't have my Nexus, I would of returned this Tablet...
[Galaxy Tab 4 Original Android Development] :
Hi, my Philz Recovery Final build for the SM-T330NU is up and works tight. Read the OP for instructions.

Stop complaining, you are not entitled to anything. If you need something, then do it for yourself. That's what's XDA is for.

Meant in the best way.

m
[Galaxy Tab 4 Original Android Development] JustZaphod:
I'm not complaining, this device is my daily driver.. It replaced my Nexus 7 2013 to which I still use, but I love the 8 inch screen.. It performs well and does what I need it to do.. I never said I was entitled to anything, this is just the only device I have ever owned where there at this time almost no development for.. That is my only gripe. The Touchwiz rom is just fine, no complaining on that end.. Its a good device, just not a great device.. If Samsung wouldn't of over saturated the market with tons and tons of devices that overlap each other, this tablet would of had more developers on hand.. Don't put words into my mouth.. If I didn't like it, I would of returned it and got a Nexus 10..