Clockworkmod 6.0.5.0 Galaxy Tab 4 10.1 [SM-T530]

[tgalal]

CWM for Galaxy Tab 4 10.1
From Wikipedia:

CWM replaces the stock recovery of your Android phone. Using this recovery you can then do various system level operations on your phone, such as create and restore images backups of your phone, flash a portion of or an entire custom ROM, and use other developer tools.

XDA:DevDB Information
Clockworkmod 6.0.5.0 Galaxy Tab 4 10.1 [SM-T530], ROM for the Samsung Galaxy Tab 4

Contributors
tgalal
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod

Version Information
Status: Testing
Current Stable Version: 6.0.5.0
Current Beta Version: 6.0.5.0

Created 2014-07-28
Last Updated 2014-07-28

 

[tgalal]

Reserved

Attached is Clockworkmod v6.0.5.0 for Tab 4 10.1 (SM-T530)
Configuration for building: https://github.com/tgalal/android_device_samsung_matissewifi
Compiled kernel sources for SM-T530 from http://opensource.samsung.com/

This is still in testing, try at your own risk.

WARNING: THIS WILL TRIGGER KNOX COUNTER AND VOID YOUR WARRANTY

Install instructions:

Flash using Odin or Heimdall. For Heimdall extract the tarball first

heimdall flash --RECOVERY recovery.img

Feel free to submit changes/ report any bugs/enhancements

 

[Setialpha]

Attached is Clockworkmod v6.0.5.0 for Tab 4 10.1 (SM-T530)
Configuration for building: https://github.com/tgalal/android_device_samsung_matissewifi
Compiled kernel sources for SM-T530 from http://opensource.samsung.com/

This is still in testing, try at your own risk.

Install instructions:

Flash using Odin or Heimdall. For Heimdall extract the tarball first

Feel free to submit changes/ report any bugs/enhancements

heimdall didn't work for me. But what I did (on rooted device) was:

adb shell
su
dd if=/dev/block/mmcblk0p15 of=/sdcard/stock-recovery.img
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p15
reboot recovery

CWM is booting fine, but gives several errors:

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
E: can't mount /cache/recovery/last_install
E: can't open /cache/recovery/last_install

on each operation. The log gives:

mount: mounting /dev/block/platform/msm_sdcc.1/by_name/cache on /cache failed: invalid argument
W: failed to mount /dev/block/platform/msm_sdcc.1/by_name/cache (file exists)

Also mount the external sdcard to /sdcard failed, this fixed it:

adb shell
rm /sdcard
mkdir /sdcard
mount /sdcard

but only temporary of course. In your image /sdcard is a link to /sdcard (to itself), so it can't work. For /cache however

adb shell
mount /dev/block/platform/msm_sdcc.1/by_name/cache /cache

worked just fine, until doing something. I can't find the issue here.

 

[hasek82]

Not working on tab 4 10.1 wifi i cant find my sdcard and external sdcard

Skickat från min SM-T530 via Tapatalk

 

[amin1374]

Please support galaxy tab4 sm T531 tnx

 

[MrHomebrew]

Please support Galaxy tab 4 T300NU

 

[moonbutt74]

@tgalal

hi, thank you for your work and effort.

I may be getting one of these tabs to work on and had a question as to if i need degas boot image tools.
looking in you tree for matissewifi i noticed the inclusion of recovery.img-dt.

If i do come into the device I would first need to secure a back up of the original boot and recovery .img's

Any help, tips, pointers would be greatly appreciated.

I ask because i will need to perform the entire process from scratch regardless of existing source/work.

thank you for your time.

m

 

[MrHomebrew]

I have a backup of boot and recovery. IMG backed up and posted online for download for the t330nu

---------- Post added at 11:03 PM ---------- Previous post was at 11:03 PM ----------

If it helps for me to post download links let me know

 

[Bortholm]

@Setialpha, have u solved the mounting-problem ?

 

[amyren]

CWM for Galaxy Tab 4 10.1
Clockworkmod 6.0.5.0 Galaxy Tab 4 10.1 [SM-T530], ROM for the Samsung Galaxy Tab 4
Created 2014-07-28
Last Updated 2014-07-28

Hi, thanks for your work here.
However, it seems that there still are a few issues that is not yet solved here. I'm thinking of the sdcard mounting reported by some users.
Is there perhaps any chance for an updated version that corrects these issues?

EDIT:
I just read through the similar thread for TWRP on the SM-T530.
From what I read there, there was similar problems with internal/external SD, but reading the latest posts there I got the understanding that the issues was solved and everything work as it should.
Now, I do have a "stupid" question. I have use CWM before on my phone, so I know basicly how it works. Does this TWRP do exactly the same thing as CWM, but using touch screen interface instead of the buttons?

regards

 

[thisisapoorusernamechoice]

Now, I do have a "stupid" question. I have use CWM before on my phone, so I know basicly how it works. Does this TWRP do exactly the same thing as CWM, but using touch screen interface instead of the buttons?

regards

Yes. I was used to CWM and a little hesitant switching to TWRP, but it has all the same functionality, but with touch interface (as well as buttons) instead of just buttons. If anything, TWRP is more powerful, more functional, and more customizable. Plus these days there's just way more development support for TWRP. So yes, TWRP replaces all the functionality of CWM, just better lol.

TLDR: Yes

Edit: Make sure to look here, don't use any of the outdated builds

 

[buzzworkers]

My bad

I think i did something wrong !

- just got my tab SM t530 & tried to have a working recovery to be able to install custom rom
- first i tried TWRP but could not manage to go to recovery, instead it would simply boot to android stock
- so i tought ok let's try to have Clockworkmod working : flashed the recovery.tar from this thread using Odin

the result is a very weird boot loop, where i see tons of weird graphical glitchs instead of the normal boot/recovery
on the top left of the screen i can read :

recovery booting (blue)
recovery is not SEAandroid Enforcing (red)
set warranty bit recovery (yellow)

after that i see the very fast graphic glitchs on the screen, then screen goes black with a white line or no pixel at all
and it stay stuck like this 1 min, then screen goes back to black.

This is a video showing what is happening : https://www.youtube.com/watch?v=90cknbPQjFE

and the only thing i can do is to reboot, but no matter what i do (button combination, it always go back to recovery)

I can't go back to download mode, so i can't restock my tablet or restore i backup.

any advice for me on how to proceed and get back from this mistake ?

 

[moonbutt74]

b,

reflash a current working recovery via odin with the auto restart option unchecked
when the flash is done [res-ok]
disconnect tab and manually reboot to recovery - vol+ home power

m

 

[buzzworkers]

b,

reflash a current working recovery via odin with the auto restart option unchecked
when the flash is done [res-ok]
disconnect tab and manually reboot to recovery - vol+ home power

m

How do i reflash anything without access to download mode ?

---------- Post added at 08:34 PM ---------- Previous post was at 08:31 PM ----------

Video of my problem above : https://www.youtube.com/watch?v=90cknbPQjFE

it seems this tab is on it's way to the dustbin, i flashed many devices, since a few years, never saw a brick like this.. :/

 

[moonbutt74]

How do i reflash anything without access to download mode ?

are you on hangouts ?
i had this same issue after flashing a twrp recovery build, the issue actually occured when i flashed back to philz.
before you do anything else,

1 search xda for instructions to get adb installed for your operating system,
2 accept that we will be flashing my philz build, so we can be on the same sheet of music, you can switch to whatever
afterwards
3 do better research on CURRENT WORKING recoveries

if you have adb installed already, plug your tab in and turn it on,
when you get your OS's signal that it's picked up the device run the following immediately

adb reboot-bootloader

which should with luck get you into odin mode

m

 

[buzzworkers]

Thanks so much !

are you on hangouts ?

YES ! pm me ?

1 search xda for instructions to get adb installed for your operating system,

I have ADB already setup, but right now under the current boot mode i'm able to use, i get : error device not found
when i try to adb my device or just to get it's status..

2 accept that we will be flashing my philz build, so we can be on the same sheet of music, you can switch to whatever
afterwards

no worry, I know Philz recovery and used it a lot on other devices i owned.

3 do better research on CURRENT WORKING recoveries

I swear i will !!

 

[moonbutt74]

b,

you have pm blocked , well screw it

start by holding down only power,
let it cycle once or twice

keep the tab connected to pc the entire time, you running a linux os by any chance ?

windows has mental problems
if linux picks it up have a terminal open and ready, prestart adb server
adb start-server

then have the following command ready
adb logcat
@buzzworkers

if that doesn't grab it , next we try a boot into safe mode, vol+ vol- power
when boot screen comes up release power but keep vol buttons held down.

 

[buzzworkers]

b,

you have pm blocked , well screw it

start by holding down only power,
let it cycle once or twice

keep the tab connected to pc the entire time, you running a linux os by any chance ?

windows has mental problems
if linux picks it up have a terminal open and ready, prestart adb server
adb start-server

then have the following command ready
adb logcat

-
just sent you a link with my hangout link..would that work ?

i can switch back to arch linux but not sure i have the android suite installed there..
but if we are sure to have better results i can prepare the OS to have everything android
and then i come back here when i'm ready ?

 

[moonbutt74]

No, unblock pm's.

you're goal is to get the tab back into odin mode OR get access via adb

 

[buzzworkers]

No, unblock pm's.

you're goal is to get the tab back into odin mode OR get access via adb

OK i think I have my settings open to anyone to PM me now..

about ADB i'm now on my arch linux with the whole android sdk, platform-tools setup.

when i do adb get-state i have :

* daemon not running. starting it now on port 5037 *
* daemon started successfully *
recovery


is that better ?

---------- Post added at 09:23 PM ---------- Previous post was at 09:21 PM ----------

when i do adb reboot-bootloader

it works, it actuall reboot my tab, but i'm back to the usual : recovery
and ends up with those weird graphic glitches..then goes black..