Database Users

S4 DUOS, GT-I9502, can´t finish “Odin updating” even for stock roms

Hi everyone, I´m really pissed about that issue; I´d really appreciate any help and thanks in advance to you all.
Story: I was using Sva´s rom for kitkat, everything normal, then I´ve seen Sasikas´s for lollipop and decided to try it out. I flashed the original firmware and then the custom, both via odin, used them normal as usual. For some reason, I decide to compare the new sva´s, also for lollipop and when I tried to flash, THE ISSUE BEGAN!
Issue: after doing the normal odin process, when the message “complete” shows up and the phone reboots, the bar of updating progress stop about 25% and the phone reboot to the normal mode, but only with a black screen. This is the screen I´m talking about: 3w generacionandroid.com/wp-content/uploads/2014/09/Android_updating.jpg
What I already tried and it didn´t work:
1 – factory reset after the “boot”; I think the problem is that the “system isn´t being write” so …
2 – different roms, both custom and stock; something interesting about this is that the point of the bar that resets the phone varies according to the rom I use, just as follow:
Rom lollipop: at 25% of the bar the system restarts;
Rom kitkat: the bar jumps from 25% to the end and boots the system until Samsung logo. I noticed that the carrier logo sound is cutted in the end.
I can freely install any recovery and enter dl mode.
By the way, the bootloader file must be flashed at pda or bl in odin?

Flash the bootloader file in the BL slot.

about the bootloader...
I´ve installed a bootloader to try the new lollipop in sva´s rom, maybe because of this I can´t flash anymore? I´ve found this info about bootloaders, could someone tell me if I´m thinkg right about it?
"In literal terms, bootloader is code that is executed before any Operating System starts to run. "
This way what I need is a bootloader for kitkat or previous? Where can i find it?

cry for help
almost givin up...
so, happy new year to everyone, I´ll wait until January to check any replies, otherwise selling for parts. ='[.
Shortening: I can enter recovery and dl mode BUT not getting to install roms;
I know I fixed selinux permissions once and installed a bootloader said to be to install a version of lollipop, that´s all new stuff I did.

Bootloader Status, OTA and gapps

Hi.
Can some one help check my Elephone S7 (4G-64GB) bootloader status? I've tried the code and some apps, but the code doesn't work and the apps some don't work while others say "unknown" .
On another subject, stock rom related:
- After installing twrp and the latest stock rom, does OTA still work? I think it should since it's the same rom just a different recovery, but I would like confirmation.
- I don't know why but on my Elephone S7 the google startup wizard doesn't start. I even got the wizard apk, but it installs and doesn't run. So I'm thinking... (maybe I shouldn't ) can we install open gapps using twrp without any problems?
Thanks!

Flashed roms stuck on bootscreen (logo screen)

Hi guys,
I need an advice. It will be appreciated!
I am with TRWP 3.1.0-1 alice.Flashed an image through official TRWP app.
I flashed "ressurection remix" , "stock 8.0" , "lineage OS". They all just get stuck on logo screen after install.I waited for 25 mins and nothing happens; only once the phone restarted & then froze again.
If i turn it off, after 4 secs. it turns on by itself.
(but if i go quickly with combo buttons, i am able to get into TRWP and go back to backed up system...)
I'm currently running Android 5.0.1 / EMUI 3.1 ;
I have rooted the phone with Kingoroot
(without pc)
***
If you can give some advice, i'll be very gratefull...
Thank you!

The best is you update your stockrom to emui 8 first, after this it should work with customs.

I see there are emui 8 updates, but they all seem to be for 2017 version.
I bought my phone in 2015.
Not sure if it is safe to flash something , that is for the later version.
What do you think?

crystalsun111 said:
I see there are emui 8 updates, but they all seem to be for the 2017 version.
I bought my phone in 2015.
Not sure if it is safe to flash something, that is for the later version.
What do you think?
Click to expand...
Click to collapse
As far as I know, Resurrection Remix, LineageOS, and all other Custom ROMs only work on B896 Version (this is meant for Vodafone). First, you need to have this ROM and only then you can successfully flash Custom ROMS, unless, you're searching for in P8Lite (2017)...
Do read the main part before installing... They should have mentioned it there...

Galaxy Tab A 10.1 2016 (blocked by Chinese firmware) - SM-T580

Hello everyone, I flashed the stock firmware (T580ZCU6CTA) to my SM-T580 , trying to "fix it"; all the memory was occupied by the system files. The flash went well, still when the tab rebooted the screen went crazy for a while, anyways after booting up the tab works way better than before, but its block, meaning that it wont let me install some apps, I also tried to flash many different stock firmware but I always get a message that the boot-loader is block (in Chinese language). I was able to flash the U6 combination files, but it did not fix it. Please I need some help.

greynao said:
Hello everyone, I flashed the stock firmware (T580ZCU6CTA) to my SM-T580 , trying to "fix it"; all the memory was occupied by the system files. The flash went well, still when the tab rebooted the screen went crazy for a while, anyways after booting up the tab works way better than before, but its block, meaning that it wont let me install some apps, I also tried to flash many different stock firmware but I always get a message that the boot-loader is block (in Chinese language). I was able to flash the U6 combination files, but it did not fix it. Please I need some help.
Click to expand...
Click to collapse
Did you enable OEM unlock on the Chinese firmware or the U6 combination firmware?
Edit: I forgot that the Chinese firmware had Crom Service...

JJcoder said:
Did you enable OEM unlock on the Chinese firmware or the U6 combination firmware?
Click to expand...
Click to collapse
Hi JJcoder. I actually did enable OEM unlock on the Chinese firmware and had no luck. While in the U6 combination firmware; for some reason the "OEM unlock" option is not available even after enabling the developer mode menu.

Hello! The problem is that in the Chinese version they install a thing called crom protection.
To deactivate it you have to install an apk on the tablet called "crom service" and do the steps that come on this website https://www.teamandroid.com/2018/06/27/unlock-bootloader-chinese-samsung -devices-crom-service /
It has worked for me, if you realize it, before using and entering bootloader mode you get "CROM SERVICE: ON"
then once done the steps you will get "CROM SERVICE: OFF"
when that comes out install twrp and from there install the rom you want. If you have problems reinstall the Chinese version with odin and do the same again. Sorry for my bad English!

Gnzlo said:
Hello! The problem is that in the Chinese version they install a thing called crom protection.
To deactivate it you have to install an apk on the tablet called "crom service" and do the steps that come on this website https://www.teamandroid.com/2018/06/27/unlock-bootloader-chinese-samsung -devices-crom-service /
It has worked for me, if you realize it, before using and entering bootloader mode you get "CROM SERVICE: ON"
then once done the steps you will get "CROM SERVICE: OFF"
when that comes out install twrp and from there install the rom you want. If you have problems reinstall the Chinese version with odin and do the same again. Sorry for my bad English!
Click to expand...
Click to collapse
Thank you so much for your help; everything went well. I had a little problem trying to get the tablet into recovery mode after installing the TWRP, but I found a solution (when the TWRP flash is complete and the tablet starts to reboot, press and hold volume up and home to get it to boot into recovery, this has to be done quickly in order to catch the beginning of the tablet rebooting or the stock recovery will overwrite on the TWRP). I had to mentioned just in case someone else runs by this problem.
Please reply with your pay pal so I can buy you a beer for your help. Thank you.

greynao said:
Thank you so much for your help; everything went well. I had a little problem trying to get the tablet into recovery mode after installing the TWRP, but I found a solution (when the TWRP flash is complete and the tablet starts to reboot, press and hold volume up and home to get it to boot into recovery, this has to be done quickly in order to catch the beginning of the tablet rebooting or the stock recovery will overwrite on the TWRP). I had to mentioned just in case someone else runs by this problem.
Please reply with your pay pal so I can buy you a beer for your help. Thank you.
Click to expand...
Click to collapse
hahaha don't worry!! I had the same problem and spent several hours researching because I couldn't install twrp or another rom, so you don't need a beer, I just need to know that it was useful and someone else didn't have to go through the same as me XD

some basic questions on sm-t235 re: root/custom rom/custom recovery

Hi,
the other day a friend gave me her old Samsung tab 4 7.0 (SM-T235). It's in its default state, running Android 5.1.1 stock ROM with all the most recent (5 year old) updates. "KNOX" appears to be ok, afaik.
This is my first Samsung device, up to the date I had experience with HTC Desire, Sony Xperia (2x) and OnePlus devices. I unlocked / rooted and installed custom ROMs on all of them.
Done quite a bit of googling and playing around with my "new" Samsung to see where it's different compared to my other devices. But there still are some blank spots, and there doesn't seem to be too much information out there regarding that specific tab 4 device. Before I start messing around I'd love to have some input from experienced Samsung users in regards to custom recoveries and ROMs, and possibly rooting. If there are comprehensive guides etc. out there that I simply didn't find don't hesitate to give me some hints:
First of all it appears to me that this device is going under the codename "degas". Correct? (meanwhile confirmed)
I hooked up the device to my PC, made sure that adb found it alright, then called "adb reboot recovery". That worked nicely, got me into Samsung recovery
Next I again tried to connect through ADB to the device still being in recovery, but that didn't work. To be expected?
Still in recovery I chose the "boot to bootloader" option, but that got me back into system instead.
So from system I again connected to adb then called "adb reboot bootloader". Device booted alright, but again it just rebooted into system.
>> Is there really no way to get into bootloader?
Trying to find out what has to be done in order to flash a custom ROM (rooted or not): from what I get, and unlike my other devices, I do not have to unlock the device / bootloader to begin with. It looks as if it was sufficient to boot into what they call "download mode", then hook up the device to my PC where ODIN is waiting already. Following this thread (and others) it then is sufficient to just flash TWRP from ODIN, boot to recovery and then do what is usually done here (like flash custom ROM, flash Gapps and possibly Magisk etc.). Is there something else / important I should know / observe?
Speaking about TWRP and Custom ROMs: TWRP.me lists that device on their site. So has anyone here flashed latest TWRP (3.6.2_x)? Or should I rather start with an older version like the one listed here, then possibly upgrade from there?
In regards to Custom ROMs I basically just found this LOS 16 thread (which is the same linked in the previous "TWRP" bullet). I assume that's it, or does anyone know about a newer android version (which I didn't find so far)? There seems to be lots of activity around "matisse" and "millet", but apparently those aren't the right devices, right?
Back to recovery: I see that in stock recovery there is an option to "wipe data/factory reset": should I do that before flashing TWRP from ODIN, or is it sufficient to wipe everything once I booted into TWRP?
I'm aware that I'll lose "Knox" as soon as I flash a different ROM / Recovery. As I don't want to use the tab 4 in some critical "BYOD" area I don't care (neither do I care about warranty, that's long gone anyways). But just to be sure: is it true that I'll lose "Knox" access?
In case I would decide to "go back" to stock ROM one day, how would I proceed then? Would ODIN still work so that I can flash latest stock ROM? Would Knox then be restored, or is that a thing of the past once I leave the stock ROM path?
Again: if you think I've done a bad job searching for answers don't hesitate to let me know but please be so kind then to hint the phrases I should look for ("SM-T235" really doesn't bring up that much valuable info)
Thanks and cheers
Update 2022-08-03: meanwhile I realized that the device is connected to my PC through generic drivers. Would it help to install specific Samsung drivers although both ADB and ODIN are acknowledging the device? Or can I just neglect that?

Since no answers came in I dared to just try. Meanwhile I'm running the device on LOS 16 with TWRP 3.5.2_9. Then flashed MindTheGapps (arm/Android 9 flavour)The switch wasn't as easy as I expected for some reason not obvious to me (somehow I couldn't get into TWRP after flashing it through ODIN. Then after the ~25th attempt it suddenly worked). Meanwhile I installed the official Samsung drivers, and maybe that helped, in combination with other adjustments I lost trace of...
I'll answer some of the above questions, for anyone who's interested:
#3: while in recovery (TWRP 3.5.2, as it is now) I still cannot access the device through adb. But I have access from windows' file explorer, so at least I can exchange files while being in recovery. Strange thing, this is the only one of my devices that behaves this way. The other day I'll try again from a Linux machine. maybe that works...
#4/5/6: boot to bootloader still doesn't work no matter what I try - devices always boots back into system
#7: Once I managed to get into TWRP the rest was a breeze
#8: I tried TWRP 3.6.0_9-0 which worked but on every boot into recovery it shows first a red notice that recovery was not enforcing SEAndroid. The notice then turns into blue and a second later TWRP logo shows up. This dowsn't happen with TWRP 3.5.2_9, so I stay there for the time being. Then I felt lucky and installed TWRP 3.6.2_9 image from running TWRP recovery, then rebooted. That again showed the red "not enforcing" message - and got stuck there. Solution was to get back into "Download mode" then re-flash TWRP 3.5.2 through ODIN.
Conclusion TWRP 3.6.2 is not fit to be used on that device (no, I didn't try 3.6.1...)
#9: since there aren't any more security updates released by google for A9 ROMs it would really be great to be able to upgrade to an A10 or even A11 ROM... anyone ever tried to use a "matisse" or "millet" ROM?
#10: I decided to use that - wiping everything that was on the device then doing a factory reset as well before flashing LOS 16. Then after first boot into LOS 16 a strange thing happened: when I made a basic setting (in regards to location services" the device told me that in a previous version I had decided to NOT allow google to use those services: after all that wiping and factory resetting: how could the device know that? By that time I had not yet logged myself into Google. Very mysterious!
#11/12: I guess I know the answer: I'm out of "Knox" now once and forever. And apparently ODIN is still working and recognizing the device.
Cheers!