Philz Advanced CWM v.6.5X SM-T53X SM-T33X - SM-T23X List is expanding... - Galaxy Tab 4 Android Development

OKay,
Philz/Advanced CWM build for;
SM-T230/NU/31 Philz 6.59 and Aromafm [Marvell]
https://www.androidfilehost.com/?w=files&flid=28382
SM-T237p Philz 6.59 [QCOM/MSM] Thanks @hookem2oo7 for testing.
https://www.androidfilehost.com/?fid=95916177934549969
SM-T230nt Philz 6.59 [QCOM/MSM] Thanks @Erus Tyrannus for testing.
https://www.androidfilehost.com/?fid=23991606952612934
SM-T330/NU/31 Philz 6.58.9
https://www.androidfilehost.com/?w=files&flid=23544
SM-T530NU/31/35 Philz 6.58.9
https://www.androidfilehost.com/?w=files&flid=23537
SM-T533 Philz 6.58.9 <-this is a temporary test build - no noobs.
https://www.androidfilehost.com/?fid=24336189125296272
After usage you may need to reflash the stock LP 5.1 releases recovery.
https://www.androidfilehost.com/?fid=24338798368260119 <-This zip is recovery flashable.
Click to expand...
Click to collapse
NOTE remove .md5 extension if Odin complains -- 64gig sdcards must be formatted exfat
As soon as i get reorganized i will get device trees reconstructed and posted.
My hard drive failed and i lost most of what i had.
the source code for Philz recovery is here https://github.com/PhilZ-cwm6/philz_touch_cwm6
----------------------------------------------------------------------------------
Thanks to the following for support and testing
Huge thanks to @g_ding84 for testing the SM-T230/NU31 process
A special thanks to @Aben314 for supporting me in my efforts.
On the SM-T33XX- @Rusell - the main man , primary tester @pre4speed initial tester and moral support @Flashalot device tree and moral support
On the SM-T53XX thanks to @tgalal @sub77 for their previous work and @mariojuniorjp for testing on the sm-t531
-----------------------------------------------------------------------------------
These are the tools you need if you don't have them already - Odin and Samsung USB Drivers
https://www.androidfilehost.com/?w=files&flid=25040
----------------------------------------------------------------------------------
For builders, this is the default.prop of the sm-t330nu recovery, to make sure your rom assert entries will be correct
Code:
# PHILZ SM-T330NU-MB74
#
persist.security.ams.enforcing=0
ro.adb.secure=0
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=adb
persist.sys.root_access=1
ro.build.product=milletwifi[COLOR="Red"]ue[/COLOR]
ro.product.device=milletwifi[COLOR="Red"]ue[/COLOR]
ro.product.model=SM-T330NU
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.board.platform=msm8226

---

Sources
Device Trees Per Build
MOD EDIT: LINKS REMOVED

---

dev host link does not work for me.

---

rsktkr1 said:
dev host link does not work for me.
Click to expand...
Click to collapse
Did you read the OP completely?
If so, my apologies. Sometimes devhost goes down for inexplicable reasons.
Try again later.
m

---

UPDATE; see OP
SM-T330NU Philz/ADV CWM recovery
corrected storages, sdcard1 , usb-otg
TODO - orient to landscape, adjust/optimize read/write speeds
I now have the sm-t330nu so, hopefully, things will pick up.
m
EDIT- Okay, new version, storages corrected, no landscape orientation yet.
YOU MUST MAKE A NEW BACKUP AFTER INSTALL !
Backups made with previous version encounter selinux context/permission problem
and result in bootloop.

---

Double-checking file info for Odin
Does the sm-t330nu-philz-recovery-D-3.tar file for Odin contain the same update as the zip? I'm still new to Odin, but I've gleaned from searching that it can't use flashable zip files, they must be tar or tar.md5. Want to make sure I get the correct file before giving this a go. Thanks for a small bit of hand-holding.

---

K,
hi, no, odin flash d-3 first then flash the update in recovery.
i'm working on final build, so once that's done the current odin flashable file and the update zip
will be replaced, read the update post as well as the OP and be aware of the selinux issue ,
i believe i've corrected that issue in the current/final build i'm working on and should hopefully
have it up soon
thanks.
m.

---

Final Build Uploaded
Okay,
see OP for link, will be moving things over to android file host soon [mirror], will add link to OP
Final Build, orientation will remain in portrait, from what i've been reading, i would need to modify
kernel source to achieve landscape, which i won't be doing until after i get a rom [successful] to build through, sorry.
I tried increasing font size but, in portrait the text becomes jumbled and looks sloppy, [ yuck ! ]
The virtual keys will come in handy
Storages and selinux issue corrected, sdcard1 :good: usb-otg :good:
As a precaution, make a brand new backup, especially to preserve your full stock rom !
When/if i get landscape orientation and font sizes done i will release a really final version,
provided someone else doesn't do it first.
Sorry for the goofs and delays.
m

---

Thank you all!!!!

---

I'm getting a MD5 error when attempting to flash this Recovery to my T330NU Galaxy tab 4 8.0 Via ODIN
I tried redownloading it several times and got the same results.. I tried to flash this over the TWRP recovery port, its not mounting Cache so I can't flash the Zip..

---

Zaphodspeaks said:
I'm getting a MD5 error when attempting to flash this Recovery to my T330NU Galaxy tab 4 8.0 Via ODIN
I tried redownloading it several times and got the same results.. I tried to flash this over the TWRP recovery port, its not mounting Cache so I can't flash the Zip..
Click to expand...
Click to collapse
Z,
hi,
the .md5 extension can be removed, meaning, rename blah.recovery.tar.md5 to blah.recovery.tar
i scripted the odin packing process for my recovery builds a while back so, the md5 gets added as a matter of course.
the recovery will flash, as a step to defeat the automatic restoration of the stock recovery by the rom,
uncheck auto restart/reboot in odin and perform your flash, wait for the RES OK message, give it a second or two longer,
then disconnect your tab and use the three button combo to force boot to recovery, home,volume-up,power
from recovery reboot as normal.
m

---

moonbutt74 said:
Z,
hi,
the .md5 extension can be removed, meaning, rename blah.recovery.tar.md5 to blah.recovery.tar
i scripted the odin packing process for my recovery builds a while back so, the md5 gets added as a matter of course.
the recovery will flash, as a step to defeat the automatic restoration of the stock recovery by the rom,
uncheck auto restart/reboot in odin and perform your flash, wait for the RES OK message, give it a second or two longer,
then disconnect your tab and use the three button combo to force boot to recovery, home,volume-up,power
from recovery reboot as normal.
m
Click to expand...
Click to collapse
Ill do just that.. While I was sleeping, that idea did occur to me
Edit, yup that worked! Thanx..
Edit: Like the TWRP recovery, this recovery won't mount Cache..?

---

deleted, no longer relevant.

---

Pulling this conversation into the right thread.
I have the milletwifiUE SM-T330NU. This recovery wouldn't flash on it. The title is misleading b/c this recovery isn't for all of the SM-T330NU devices. Since it wouldn't flash, there isn't any harm done, but having read almost every other thread in the Tab 4 forum, I'd suggest pointing out the code name of each device is important in the OP. There are differences between the SM-T330NUs apparently.
Still, M, thank you for your work on the device. If you can link me to directions on how to pull a recovery.log or boot.img or whatever you may need to include the milletwifiue, I'd be glad to. If you've already posted those directions and I missed them, point me to the post.

---

Can you make one for smt331

---

Dewang rocky said:
Can you make one for smt331
Click to expand...
Click to collapse
D,
hi, try this version, flash via odin. http://d-h.st/de2u click the download now button.
the name of the file is sm-t331-Philz-6_58_9-recovery-round1.tar
m

---

xnatex21 said:
Pulling this conversation into the right thread.
I have the milletwifiUE SM-T330NU. This recovery wouldn't flash on it. The title is misleading b/c this recovery isn't for all of the SM-T330NU devices. Since it wouldn't flash, there isn't any harm done, but having read almost every other thread in the Tab 4 forum, I'd suggest pointing out the code name of each device is important in the OP. There are differences between the SM-T330NUs apparently.
Still, M, thank you for your work on the device. If you can link me to directions on how to pull a recovery.log or boot.img or whatever you may need to include the milletwifiue, I'd be glad to. If you've already posted those directions and I missed them, point me to the post.
Click to expand...
Click to collapse
The recovery is for the milletwifi sm-t330nu, again if you read the op you will see the codename clearly stated in the posted default.prop.
If i understand your issue, you either attempted to flash this recovery's .zip installation from another recovery, or you attempted to flash
a modified repackaged "stock" rom in which, during the process, the assert in the updater-script determined your device to be incorrect.
In which case your custom rom and/or previous custom recovery are in error.
I say this bluntly yet, without malice, I have done this before and have a fairly good handle on it. I would certainly modify a version for you
if you provide me with the actual original stock boot or recovery image for your device. Images from custom/modded roms will not do.
m

---

moonbutt74 said:
The recovery is for the milletwifi sm-t330nu, again if you read the op you will see the codename clearly stated in the posted default.prop.
If i understand your issue, you either attempted to flash this recovery's .zip installation from another recovery, or you attempted to flash
a modified repackaged "stock" rom in which, during the process, the assert in the updater-script determined your device to be incorrect.
In which case your custom rom and/or previous custom recovery are in error.
I say this bluntly yet, without malice, I have done this before and have a fairly good handle on it. I would certainly modify a version for you
if you provide me with the actual original stock boot or recovery image for your device. Images from custom/modded roms will not do.
m
Click to expand...
Click to collapse
If I'm one of the only people that would benefit from it, lets not worry about it. At this point I don't have the stock recovery b/c I flashed twrp first and then tried to flash this.
I see you did post the code name in the OP but I think it would help to point out that there are sm-t330nu variants, like mine. Coming from years of flashing, I know most people here are used to checking model #s that are posted in the title. Its very unusual to get a model with different code names and not a different carrier, in this case wifi (as opposed to Verizon ot Sprint etc).
Edit: typos

---

X,
hi,
the ue thing is weird, , i am wondering if my tab might have been a refurbished device.
this should do you, it the same recovery adjusted to milletwifiue
Derp on me, sorry https://www.androidfilehost.com/?fid=95887005526787734
the name of the file is sm-t330nu-Philz-6_58_9-milletwifiue-recovery.zip
I'll add it to OP and make an edit. Let me know if you have an issue.
m

---

moonbutt74 said:
X,
hi,
the ue thing is weird, , i am wondering if my tab might have been a refurbished device.
this should do you, it the same recovery adjusted to milletwifiue
https://www.androidfilehost.com/?fid=95887005526787126
I'll add it to OP and make an edit. Let me know if you have an issue.
m
Click to expand...
Click to collapse
M,
I flashed it in twrp .3 and it failed. It didn't give me the wrong device error though.
My device is a refurb too. I pulled this from bug report, not sure if it helps:
milletwifiue-user 4.4.2 KOT49H T330NUUEU1ANCA