yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
h,

okay, the recovery's in house root is out of date for LP and cannot be used. You will need to upload your 5.1 boot.img so i can build a kernel with selinux disabled. Or if you require selinux to function then i believe chainfire has a new beta approach with supersu for LP 5.1 that roots in the boot.img but I don't actually know the specifics.

Reboot shutting down instead is odd. :confused: To find out why [maybe] reboot to recovery and connect via adb and do the following,

once connected via adb, run

adb shell logcat

keep that running and on your tab while in the recovery select the reboot option. As you "reboot" adb will disconnect but maybe the output of logcat up to that point may catch the reason.

In the interim i will remove the supersu rooting component from the recovery. I am still not seeing the system, data etc in the mount listing. :confused:

m

[MENTION=3132221]sub77[/MENTION] hey hey, okay this is my working kernel source for the sm-t533 from opensource. [LL]

https://github.com/moonbutt74/kernel_SM-T533_T533XXU1BOI3

The [KK} release seems bad i have that as well but am planning to delete the repository.

I built the kernel outside the android build system as it still seems to have some issues compiling otherwise.

Philz is probably on it's way out just due to no upkeep with even the latest patches to cm11 so it looks like

twrp is going to end up being the only recovery option soon.

The kernel is 32 bit in spite of the cortex a53 arm64 hoop-la as far as i can tell.

This is a basic tree as well https://github.com/moonbutt74/device_samsung_matissevewifi

The fstab for twrp still needs to be created. This is setup for using a prebuilt kernel/dt.img

m
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
M, the recovery sadly has no logcat available :( but rebooting from recovery boots recovery, the only way to boot into the system is to reflash stock recovery. Backup/Restore works. Attched is the boot.img from Lollipop T533XXU1BOI3

cheers and a nice weekend

Hans
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
h,

hmm, okay so give this a try

sm-t533-booting-test_7-recovery-philz.tar

after you flash and boot to recovery,

goto Mounts and Storage

manually mount /system /data /cache /sdcard

go back to main screen and select Power Options and then Power Off

then reboot your tab normally.

I didn't see any link for the 5.1 boot.img.

I've notified [MENTION=3132221]sub77[/MENTION] and hopefully he'll pick up the project and get a twrp build done for the sm-t533 since philz seems to be falling behind.

m

i restored a kernel command line on this image.

i also need a listing of your modules

ls /system/lib/modules/
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
M, flashed and did the mount thing (no error messages) went to power options -> power off: reboots to recovery

sorry about the missing link :(

Hans
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
h,

okay , i am trying to confirm whether this is a dmverity thing in the stock [lp5.1] kernel.

can you detect if there is an extended delay of even a second or two when you reboot from within recovery to normal operation ?

i will have a test boot.img up shortly. if the recovery is making backups correctly, meaning you have verified the size of backups

and succeeded in restoring the backup in part or whole i will post package the image as recovery flashable.

Hey , why does this say 511 ?

m

[MENTION=3126603]HausiX10[/MENTION]

okay here's the test boot.img, wifi will not work. This is just to see if the tab will reboot to normal operation

from recovery.

Download to your tab, reflash recovery, reboot to recovery and make a full backup if you have not done so.

Flash the kernel package, rememberr do not use the recovery's rooting function.

When the flash is complete, reboot to normal operation.

If the same results as before, do a custom restore from your rom backup of your backed up boot.img

Then restore stock recovery and reboot tab to normal operation.

If it turns out that the restoration of stock boot.img fails then it means the recovery is totally porked and i need to start over.

SM-T533-LP-5.1.1-TEST-PERMISSIVE-ROOTABLE.zip

This is a recovery flashable zip. DMVERITY should now be disabled.

You may need to reflash the firmware release again, if so i do apologize, just keep in mind i'm fighting with samsung here.
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
M,

backed up to external sdcard

flashed above file, rebooted from recovery menu and got the battery symbol after a delay. However I was able to boot the system normally using the power button, this is new. Then restored boot image from backup, flashed stock recovery and eveything was back to normal. Funy thing is that I had to reconfigure my WiFi access.

Hans
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
[MENTION=3126603]HausiX10[/MENTION]

okay just to clarify,

Okay i am almost certain, with dmverity and selinux being slain in the boot.img which also includes the signature verification of the boot,img on boot, that the issue is more likely the boot.img now and less likely the recovery.

After i upload the newest boot.img test, repeat the process from before as to flashing the recovery and then flashing the kernel package.

Verify if the wifi works. If good on that front operate the tab for a while with the custom recovery AND the custom boot.img in place and see how it goes.

I may have used the wrong common sources in compiling the recovery [msm8226 INSTEAD of msm8916] so i will have to tinker with my build system a little before i do a fresh build.

here is the new kernel package SM-T533-LP-5.1.1-TEST_2-PERMISSIVE-ROOTABLE.zip

Also can you confirm adb access in both custom boot.img AND recovery.img please ?

m
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
M, pretty quick I must say. Ok, flashed recovery and then the kernel. System came up ok, but only once. When I rebooted into recovery, bootingthe system went to recovery again. WiFi works ok. So I have to flash the stock recovery to be able to use the system.

Hans

n.b. you probably have to reconsider the name of this kernel ;) (or insert the missing -h-)
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
h,

okay so to clarify,

the custom boot.img is functioning correctly ? wifi, bluetooth, etc. ?

if the new kernel is functioning correctly , reflash the custom recovery and flash the recommended supersu beta mentioned in my kernel thread. https://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip

Make a full backup first with the new kernel/boot.img before flashing supersu beta. DO NOT use the recovery's in house root.

Give me a little bit to package the stock recovery as a recovery flashable zip so you can reduce the amount of odin usage.

the kernel in the custom boot.img has no significant modifications, only selinux, dmverity, anti-root feature disabled. = bottom-end

and i'm ALWAYS thinking about coffee = ole

xD

EDIT- can you upload the current stock recovery ?
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
M, I said WiFi is working but I loose the password each time I reboot. The flashing actions have to wait till tomorrow, I'll be back...

please give me the link to that supersu beta

Hans
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
M, mixed results:

- flashed recovery

- flashed supersu

- reboot system -> OK

- reboot system -> recovery (forever)

- reflashed stock recovery -> boots normal

- WiFi still wants password after rebooting

Hans
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
h,

okay supersu https://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip

the stock LP recovery repacked to flash via recovery SM-T533-LP-STOCK-RECOVERY.zip

I'm gonna have to look up why that is on the wifi password being forgotten.

it should be storing itself in a file in /data/misc/wifi.

m

Edit, okay so you have/get root though ? su in terminal is good ?

[MENTION=3126603]HausiX10[/MENTION]

okay the possible cause of the wifi password issue may be the following as described here,

Issue 58863:	WiFi password not saving after turning off then on....

which , if i'm seeing it right goes back to something [MENTION=2954020]starlightknight[/MENTION] and [MENTION=3132221]sub77[/MENTION] had covered about a patch needed to the pronto driver so

the proper mac address can be read from /efs. For now if you can tolerate the situation and keep your root then okay, try using the function to forget the wifi connection, then reboot and re-establish your connection information, connect to verify you're up, then reboot again and see if it sticks. In the interim, i will locate that patch and do another build.

m

For my reference Add support for passing in MAC from user space These changes all exist in my working source already. :eek: :confused:
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
M, thanks for the stock recovery, supersu works fine, su in terminal too (removed kingroot)

Hans
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
h,

okay. still trying to find out what the reboot issue is about.

Perform the requested procedure in previous reply to see if it resolves the wifi issue.

Please confirm that adb access in both recovery and normal operation modes functions correctly please?

m
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
M, I'm away from home tomorrow, but I'll try as soon as possible

Hans
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
M, ok done a few tests:

- forget wifi -> reboot

- /system/etc/wifi/wpa_supplicant.conf & /data/misc/wifi/wpa_supplicant.conf have no AP info

- after configuring AP /data/misc/wifi/wpa_supplicant.conf has AP info, but looses it with a reboot

- flash reco -> reboot -> pwr off but booting into system after pressing pwr button -> reboot -> recovery

the rest works quit nicely with your kernel :)

hth

Hans
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
h,

Okay, so the outstanding issues we have are;

the reboot/boot issue with the recovery

- This requires a rebuild - which will be a little while. But in the interim, on a one time flash it can be used to back up and or/flash a package

[*]the wifi password being forgotten with the custom kernel.

- I am wondering if this may be the result of a "mismatch" between some of the firmware related files and modules from the kernel build

- which were not included with the kernel package. :confused:

If you're up for another test, i will post a package that will also update modules and firmware files. It would be a good move to back up your current rom w/root completely. I'll get the package up today or tomorrow.

m
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
? i'm in...
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
:good:

h,

okay, first in rotation here is another recovery test, this is a new build, so i'm not sure how this will go,

sm-t533-booting-test_8-recovery-philz.tar

same routine as before. i am trying to fix a few things here and there.

[MENTION=3126603]HausiX10[/MENTION]

okay here is the new kernel package SM-T533-LP-5.1.1-TEST_3-PERMISSIVE-ROOTABLE.zip

includes modules and prima/wcnss firmware stuff. Hope this does the trick.

Note; if this doesn't work correctly you will need to restore both system AND boot.img from your rooted backup.

m
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
M,

- recovery #8 does not mount/see external sdcard

- kernel #3 bootloops

- restore went ok :cool:

Hans
[Galaxy Tab 4 Q&A, Help & Troubleshooting] myheroduane:
Hello, firstly thank you for your hard work. Just curious if development was still in progress or did o miss something and its ready..
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
@m, happy new 'everything' :laugh:

I just wanted to ask the same as myheroduano above

Hans

n.b. your kernel does not like to be slowed down to 200MHz, the lowest it goes is 800MHz
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
@h, hey !

i was wondering the same thing as well, :silly:

before i go any further i still need answer to some of the questions i asked.

in both current kernel and recovery [the ones that work and are posted as temp/test status] ;

confirm adb access, kernel AND recovery. confirm root access in adb for recovery.

pull logs,

does the last working recovery still contain the reboot issue, [external card is unimportant ATM].

m
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
m,

here we go:

philz #7 + kernel #2:

adb: both kernel and recovery OK

root: adb OK

logs: attached

reboot issue: reboot to recovery -> shutdown, reboot to bootloader OK

HTH

Hans
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
h,

okay the reboot with recovery issue has me stumped....,

on the kernel/boot.img i see alot of error messages from secure storage, and something called com.painless.pc.BootDialog
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
m, painless is from powertoggles
[Galaxy Tab 4 Q&A, Help & Troubleshooting] myheroduane:
Can I achieve root with your latest build?
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
According to h, the answer would be yes, but i have no confirmation yet as to the issue being resolved with the wifi login information being forgotten

on reboot yet.

Go back through this thread and read all the relevant portions. The temporary/test offerings are located at my kernel and recovery threads.

As of yet I do not know if sub will build a TWRP recovery for this model.

m
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
[MENTION=3126603]HausiX10[/MENTION]

hey, been a little distracted since the holidays :eek:

okay, are you still experiencing the loss of your wifi login on reboot ?

as to the recovery reboot i'm going to try an alternate/static reboot binary.

Let me know.

m
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
m, all still the same ?, keep going...

btw if i would like to install a custom rom, which one would you advise? bliss or cm?
[Galaxy Tab 4 Q&A, Help & Troubleshooting] repey6:
5.1.1 bliss
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
[MENTION=5704037]repey6[/MENTION], care to provide a link, blisspop site is 404 and afh empty ?

thanks hans
[Galaxy Tab 4 Q&A, Help & Troubleshooting] repey6:
https://www.androidfilehost.com/?fid=24052804347832857

If you have 404 try another browser
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
? thanks
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
[MENTION=3009153]repe[/MENTION]y, i was hoping for a marshmallow based rom, meh :)
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
[MENTION=5704037]repey6[/MENTION], this blisspop 5.1.1 doesnt work, says the rom is for matissewifi and not for the matisseVEwifi :(
[Galaxy Tab 4 Q&A, Help & Troubleshooting] repey6:
Not afraid of disappointment?

Yes it is your problem . You need to ask sub77 to do fix for you personal . We have other kernels
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
@m and [MENTION=3132221]sub77[/MENTION], bump (not push)! anything new?

cheers hans
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
h,

hey hey, still here, i've got a project in front of me, i'll pick back up on this soon though.

m
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
no problem, no need to rush things ?
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
@m, just tried [MENTION=3132221]sub77[/MENTION]'s trwrp 3.0. it comes up nicely and looks great, but there is a problem with mounting the sd card so i cannot check the functionality. booting still is shaky, it sticks to booting recovery. do you think should we close this thread and move over to sub?
[Galaxy Tab 4 Q&A, Help & Troubleshooting] ajeeva:
Dear friends!

I have the same device sm-t533. It was on kitkat4.4.4 and i rooted by using kingroot app. Later i decided to update to latest firmware via samsung smartswich and did the update. But after the update i am unable to boot the device. No power no download mode, no recovery mode. I tried 300k jig method but no luck. It was hard bricked. I recently found a solution sd card boot method for galaxy s3 device. I would like to try the method but my bad luck is i have not any other same device to create debrick boot file. Dear friends kindly anyone can create and share the debrick sd card boot file please...?
[Galaxy Tab 4 Q&A, Help & Troubleshooting] InTheY2K:
Today a friend gave me his SM-T533 as a present as it had been lying around in his drawer catching dust.

Now, I managed to install TWRP and root it with SuperSU. So now I'm ready to put a nice new ROM on it as it's still running on stock KitKat. But looking around here on XDA there doesn't seem to be going on much with the Tab 4 anymore, especially not with the SM-T533. Does anybody have a ROM like LOS14.1 or even later (Oreo? Pie would be a dream, as I'm running that on a Galaxy S3)?

What's the latest stable ROM recommendable as a daily driver?

Cheers,

Sascha
[Galaxy Tab 4 Q&A, Help & Troubleshooting] Bence98007:
Same thing, waiting for answer...Did U find any ROM for this T533? For matissevewifi there is a lot of roms, but for matissevewifixx nothing :(
[Galaxy Tab 4 Q&A, Help & Troubleshooting] InTheY2K:
No, unfortunately I haven't found anything. The tablet is still running on Stock KitKat, hence I cannot install several apps, which require Android 7 or higher (e.g. banking apps etc.).

I highly doubt that there is any usable ROM for th T533 out there as this doesn't seem to be a popular device. :(
[Galaxy Tab 4 Q&A, Help & Troubleshooting] Karibes:
Hello,

how the heck did you even manage to install TWRP? Must my tablet have KitKat or something? Because anything I do, nothing works. It gets stuck in Samsung logo if I try to boot into recovery... I would be appreciated for any tips. Thanks

Karibes
[Galaxy Tab 4 Q&A, Help & Troubleshooting] InTheY2K:
Hi,

to be honest, I don't quite remember how I did it. It's almost six months ago! :laugh: I had to google that again, myself. :laugh:

I found a TWRP in this thread: https://xdaforums.com/tab-4/develop...ung-galaxy-t2922795/post65556507#post65556507 (follow the thread from there on, as it also contains info about troubleshooting).

And SuperSU is from here: https://androidfilehost.com/?fid=529152257862688685

But don't ask me how I proceeded. I was totally in the zone back then, trying different things, failing, trying again, softbricking the tab, and trying again until I finally found a version that worked.

I hope you will make something from it. Let me know if it worked out for you.

Cheers,

Sascha
[Galaxy Tab 4 Q&A, Help & Troubleshooting] Karibes:
Hello,

oh dear... then that means using 3.0.0.0 mattise version doesn't even work on this tablet at all... That was quite silly of me.... well, sadly even with that info you provided me gracioucly, I hard bricked tablet by stupid mistake I have ever done in my life... To answer the question in the advance, I checked nand erase by stupid accident which it should have never been checked at all and tablet doesn't power on at all... To restore it I would need to buy a equipment. But oh well, tablet was sitting there doing nothing for 2 years. And to think, it was actually Mattise VE WIFI... another dumb part of me....

Cheers,

Karibes
[Galaxy Tab 4 Q&A, Help & Troubleshooting] InTheY2K:
I am sorry to hear that. But mistakes happen. I once bricked my Galaxy S3 and rendered it unusable by deleting the IMEI. I had already given it up, when some day I gave it a shot and took it to one of those hundreds of mobile phone repair shops, which there are in practically every city. They managed to restore the Stock ROM and only charged 15 EUR for it. Of course, all the data was lost, but I could use the phone again. It's now my secondary phone for my little business (with a VoIP number, no SIM) and still in use to this day. You might give it a try and ask in one of those shops if they can fix your tab, too.

Cheers,

Sascha
[Galaxy Tab 4 Q&A, Help & Troubleshooting] meric57:
Hello HauxiX10 and Myheroduane, I love this post since 2019 its date back.

Just to know still no development of a custom rom for an SM-T533 (2015).

Request for a member who owns a tablet model T533 samsung.

Thanks in advance
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HellHammer83:
Right here you have one
[Galaxy Tab 4 Q&A, Help & Troubleshooting] Azertix:
Hello. Where ?
[Galaxy Tab 4 Q&A, Help & Troubleshooting] STVWonder:
3 weeks now looking and searching for TWRP and LINEAGE OS for my Samsung SM-T533, I found the correct TWRP ( twrp-3.7.0_9-0-matissevewifi ) but can't find suitable LINEAGE OS or any OS for this Samsung SM-T533 matissevewifi Model. Please HELP!!! Thank you.
[LG G Flex 2] 05token:
Does anyone know, how to take fotos in raw-mode (dng-file)?
[LG G Flex 2] englishmale:
[MENTION=4268390]05token[/MENTION] have a look at this app on Google, it does raw and has lots of options. There is a demo version available to try before you buy. https://play.google.com/store/apps/details?id=com.riseupgames.proshot2
[LG G Flex 2] pelelademadera:
Manual camera, search for the apk and done... If you like, buy it

Enviado desde mi LG-H955 mediante Tapatalk
[LG G Flex 2] saeba77:
the day was very cloudy

original jpg https://ibb.co/nApzDG

jpg from dng https://ibb.co/egoHYG

the dng had much more information...i'can't understand why by default can't be save

to open the dng i use rawtherapee
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] luison:
Hi everyone. I've been reading for a while and think I've now got enough threads, tools and comments to go ahead and upgrade my Vodafone Hermes to WM6 and one of the cooked ROMs arround.

My only concern is that I still do not have a clear picture about if it's possible to have a full backup of my current ROM as is today in the event my upgrade process is not succesfull (been positive here ;). I thought I could just pack my current ROM into my PC so I could later restore it but not at all sure how.

Any threads, links or tools would be appreciated. Thanks to everyone for their unvaluable work in this forum... what would we do without it!!!

Jose Luis
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] moisha:
Absolutely ! SPB Backup and Sprite - two packages I know off. I've being using SPB for quite a while now. It does a complete snapshot of your device an in case your new ROM installation does not go smooth or you simply are not happy with it - just reflash with the orginal base ROM and execute the backup.exe file to return to the point where you started from. So the important thing to remember - before doing anything - make sure you have the original distro base of a ROM you are running right now and if you'll be flashing your device - ensure you have Hard SPL installed.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] mr_skot_a:
what is distro base of current rom and also hard spl? Sorry... I am so new to this world of flash upgrades and everything... I am also unsure about the official "official" release of the ROM that was postedlast month for the 8525. First question is... If this doesnt work or I dont like it... can i reinstall the upgrade that will be coming out that is official?
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] juzzie:
it is very simple. Just do a search for hermes unlocker. The current version is v3a. Or just follow this link: http://xdaforums.com/showthread.php?t=293665&page=2

You will have to download that unlocker application and follow the instructions. After that, hard SPL and unlocker will be installed automatically. Then you need to buy Sprite Backup software for PPC (there is no good hacked version out there) and backup the phone using that ROM backup feature. After backup is done, it is safe to proceed to ROM upgrade. I would strongly recommend to do the backup before the upgrade because it's much safer. It will save you a lot of troubles if something goes wrong.