I have tried different firmware (original and updated - two each) different usb cables and different usb ports.
I have factory reset and cleared cache numerous times, but every time the tablet only boots to the screen "Samsung Galaxy Powered by Android" and goes no further. I can boot to Recovery, Fastboot mode and Download, but not to System. The firmware is correct - downloaded with Frija.
Please , Can anyone help.
Checks Odin, let's see Pic after your attached file each slot also see Odin options.
tom.android said:
Checks Odin, let's see Pic after your attached file each slot also see Odin options.
Click to expand...
Click to collapse
Can show download mode Pic.
tom.android said:
Can show download mode Pic.
Click to expand...
Click to collapse
Can't read, pleases tell me oem lock , kg status , secure download
Oh. I saw your kg status is broken , it is not unlocked completely.
Your Tab is india government ? Not commercial Samsung.
You must change kg status from broken to checking. There are your community here. Pleases consult india group.
tom.android said:
Oh. I saw your kg status is broken , it is not unlocked completely.
Your Tab is india government ? Not commercial Samsung.
You must change kg status from broken to checking. There are your community here. Pleases consult india group.
Click to expand...
Click to collapse
I am in South Africa not India. It is a genuine Samsung Tablet. I bought it here. Thank-you very much for your help. I will search for a solution tomorrow.
jorjee said:
I am in South Africa not India. It is a genuine Samsung Tablet. I bought it here. Thank-you very much for your help. I will search for a solution tomorrow.
Click to expand...
Click to collapse
Oh sorry for my first introducing .
TRY
To begin with, install the stock firmware onto your Samsung device via Odin [Flash Samsung Stock Firmware via Odin].
Once flashing is complete, boot up the device and skip all the setup.
Then go to Settings > General Management > Date and Time.
Turn off Automatic Automatic date and time. Now manually set the date back to 10-15 days (7 days is the waiting time, we are keeping a few days in the buffer).
After this, go to Settings > Biometrics and Security > Other Security settings and turn off Find My Device.
At this point in time, make sure that you aren’t connected to any network. To be on the safer side, consider enabling the Airplane Mode.
Now go to Developer Options and enable OEM Unlock, If it’s already enabled or greyed out, then the bootloader is unlocked.
You may now boot the device to the Download Mode and verify that the KG has indeed been bypassed. To verify the same, you may see KG STATE as Checking, FRP LOCK: Off, and OEM LOCK: ON(U).
tom.android said:
Oh sorry for my first introducing .
TRY
To begin with, install the stock firmware onto your Samsung device via Odin [Flash Samsung Stock Firmware via Odin].
Once flashing is complete, boot up the device and skip all the setup.
Then go to Settings > General Management > Date and Time.
Turn off Automatic Automatic date and time. Now manually set the date back to 10-15 days (7 days is the waiting time, we are keeping a few days in the buffer).
After this, go to Settings > Biometrics and Security > Other Security settings and turn off Find My Device.
At this point in time, make sure that you aren’t connected to any network. To be on the safer side, consider enabling the Airplane Mode.
Now go to Developer Options and enable OEM Unlock, If it’s already enabled or greyed out, then the bootloader is unlocked.
You may now boot the device to the Download Mode and verify that the KG has indeed been bypassed. To verify the same, you may see KG STATE as Checking, FRP LOCK: Off, and OEM LOCK: ON(U).
View attachment 5686517
View attachment 5686525
Click to expand...
Click to collapse
I cannot boot the tablet.
jorjee said:
I cannot boot the tablet.
Click to expand...
Click to collapse
Can see oem lock status in developer option?
Look at here https://forum.xda-developers.com/t/...e-by-rooting-can-work-on-a03s-phones.4380053/
tom.android said:
Can see oem lock status in developer option?
Click to expand...
Click to collapse
OEM LOCK: OFF (U)
as your bootloader is unlocked already, just install TWRP and flash multidisabler
https://forum.xda-developers.com/t/4467157
Did ODIN flash passed or stuck during this entire process?
Did you try it without patched ODIN version?
Also did you check binary version...
jorjee said:
I have tried different firmware (original and updated - two each) ...
Click to expand...
Click to collapse
Keshav4 said:
Did ODIN flash passed or stuck during this entire process?
Did you try it without patched ODIN version?
Also did you check binary version...
Click to expand...
Click to collapse
Have you flashed update or FW using ODIN successfully?
Not, now I'll make sure nothing breaks it to a permanent damage
Related
Hi Evryone.
Because I didn't found CWM or TWRP Recovery or any root method for the galaxy J5 J5108 and the J7 J7108, I made a pre-rooted firmwares for those models.
This firmware base on the hong kong firmware which include the Google apps, this a full firmware exactly like the original, except the root.
After flash you will see the SuperSU app in the app drawer.
Also, this firmware contains the bootloader from the china firmware which doesn't have frp lock.
The root include the binary files in the system, and a pathed boot. (from Android 6.0 or samsung 5.1.1 pathing the boot is necessary for the root work properly)
Flashing this firmware will not wipe data automaticly. you should not lose anything.
This file will work on any firmware/baseband/csc. you can always flash it like a stock firmware.
J5 - base on - J5108ZHU1APD2.
Android version: 5.1.1
J7 - base on - J7108ZHU1APD1.
Android version: 5.1.1
Downloads
J5
http://www.mediafire.com/download/o8hfu81j3j4irjt/J5108ZHU1APD2_Rooted_by_avicohh.exe
J7
http://www.mediafire.com/download/z7bh4sdmzqer6nb/J7108ZHU1APD1_rooted_by_avicohh_v2.exe
Installation instructions
Before flashing check the CROM Service status in Download mode, if it locked you will need to unlock the bootloader first with the app attached.
Install samsung usb drivers from here.
Download the self extracting 7z file above and extract it (just double tap) to some folder, you should receive a tar.md5 file.
Open odin 3 (attached in the zip)
Put the tar.md5 file in AP.
Put the device in download mode. (vol down + home + power button, and then click on vol up)
Connect your phone to usb and wait for odin detect the device.
Click start.
After it finish choose reboot system now in recovery.
Enjoy.
If you want to thank me for this work, you can do this by donating.. :good:
Thanks a lot avicohh. This was simple and painless. I now have google services on my mainland China phone. And root too! And like you said - I did not loose anything.
well now i am stuck. I enabled my google account, installed and updated my apps through google play, shutdown and now I can't boot. The message in red on the top of the boot screen is:
"KERNEL IS NOT SEANDROID ENFORCING
Custom Binary blocked by FRP lock."
I also cannot reflash the same HK rooted firmware using Odin
apparently I should have enabled developer options then enabled OEM unlocking before rebooting. But I didn't know that so for now I am bricked
Also apparently, the fix for it is to reflash the original firmware using Odin. I am now downloading the firmware from http://updato.com/firmware-archive-select-model?record=1F170CA05E5611E6B055FA163EE8F90B but it is still another 2-3 hours to complete the download (yes, poor internet connection here.)... So I'll see how that goes...
OK, that didn't work. Now the message on the download mode screen says:
SW REV. Invalid type.
FRP is enabled, not allow download non FRP bootloader binary
Well..
I just recently had the same problem in another device.
I don't think the "Oem unlock" has nothing to do with this. the problem is that when you're adding Google account the frp (factroy reset protection) is automaticly enabled, and then it blocks the pathed boot.
The reason reflash the original firmware didn't work for you is because you tried to flash the china version, that doesn't have google service and also doesn't have frp in the bootloader. (apparently once frp is enabled this kind of operation is not allowed because you are actually trying to remove the frp lock by flashing bootloader..)
I think the solution will be to flash the original hong kong firmware with the frp bootloader and original boot. (or just the original boot)
http://updato.com/firmware-archive-select-model?record=5C13445B54D811E6B055FA163EE8F90B
Then, try to enable the "Oem unlock" option and finally flash the rooted firmware again.
maybe it will work, I'm not sure about it but I would like to know.
If this won't work, I'll try to combine the rooted hong kong firmware with the non-frp bootloader from the china firmware.
Thanks so much for replying avicohh
avicohh said:
Well..
The reason reflash the original firmware didn't work for you is because you tried to flash the china version, that doesn't have google service and also doesn't have frp in the bootloader. (apparently once frp is enabled this kind of operation is not allowed because you are actually trying to remove the frp lock by flashing bootloader..)
Click to expand...
Click to collapse
This makes sense. I was actually suspecting this and was considering trying the 6.01 HK version since that is the only one I could find: http://updato.com/firmware-archive-select-model?record=5C13445B54D811E6B055FA163EE8F90B
Now that you've posted a link to your original 5.1 HK firmware I'll try what you suggest. I'll wait to get home before I start the download.
But I still wonder if the 6.01 would work on my phone?
It's a mistake.
This link above is 5.1.1, not 6.0.1.
There is no 6.0.1 fro this model for now.
yes, I see, the website says its 6.01, but its actually 5.1.1. How do I know? BECAUSE IT WORKED!!! It took 7 hours to download but when I got up this morning it was done, I flashed and it worked!!!
I'm going to read up some more on this FRP business before flashing the rooted version again. My old phone (very old) had no such thing. I'd never heard of it till this unpleasant way of learning about it.
downloading
Same problem downloading the stock firmware from http://forum.xda-developers.com/gal...108-how-to-root-galaxy-j7-2016-model-t3426967
I hope this works....
---------- Post added at 12:27 AM ---------- Previous post was at 12:26 AM ----------
Tukuvai said:
Same problem downloading the stock firmware from http://forum.xda-developers.com/gal...108-how-to-root-galaxy-j7-2016-model-t3426967
I hope this works....
Click to expand...
Click to collapse
I meant http://updato.com/firmware-archive-s...55FA163EE8F90B
Hi guys.
Thanks for your replies.
I've just checked it now on another device.
As it turn out after a several tests, this "custom binary blocked by frp lock" problem occurs only if the oem unlock option is disabled.
Here is what I did, step by step:
First, I enabled the oem unlock option and then I added Google account - nothing happened. frp lock in Download mode is still off and everything working fine.
I removed the google account, turned off the oem unlock option and finally added the google account again - frp lock in download mode immediately switch to on, and when I tried to restart, the device has stuck on the boot. (custom binary..)
I flashed stock firmware (from the link above), the device now bootup normally but the frp lock in download mode is still on. (I didn't remove the google account yet)
Final check - I enabled the oem unlock again, and the frp lock in download mode switch to off.
So..
I can safely say that all you need to do is just enable oem unlock in developer options, and then flash the rooted firmware.
Anyway, to be even more sure, I made a new firmware with the china bootloader, frp now is not even exist in download mode.
You can download the new firmware from here
http://www.mediafire.com/download/z7bh4sdmzqer6nb/J7108ZHU1APD1_rooted_by_avicohh_v2.exe
Good luck!
avicohh said:
Hi guys.
Thanks for your replies.
I've just checked it now on another device.
As it turn out after a several tests, this "custom binary blocked by frp lock" problem occurs only if the oem unlock option is disabled.
Here is what I did, step by step:
First, I enabled the oem unlock option and then I added Google account - nothing happened. frp lock in Download mode is still off and everything working fine.
I removed the google account, turned off the oem unlock option and finally added the google account again - frp lock in download mode immediately switch to on, and when I tried to restart, the device has stuck on the boot. (custom binary..)
I flashed stock firmware (from the link above), the device now bootup normally but the frp lock in download mode is still on. (I didn't remove the google account yet)
Final check - I enabled the oem unlock again, and the frp lock in download mode switch to off.
So..
I can safely say that all you need to do is just enable oem unlock in developer options, and then flash the rooted firmware.
Anyway, to be even more sure, I made a new firmware with the china bootloader, frp now is not even exist in download mode.
You can download the new firmware from here
http://www.mediafire.com/download/z7bh4sdmzqer6nb/J7108ZHU1APD1_rooted_by_avicohh_v2.exe
Good luck!
Click to expand...
Click to collapse
Hey, How do I enable OEM unlock when I can't even boot my device. it simply refuses to boot.
Hi
First flash the original HK firmware from here. the device should boot up normally.
http://updato.com/firmware-archive-select-model?record=5C13445B54D811E6B055FA163EE8F90B
Then, enable oem unlock.
Thanks for making the root version of mainland firmware. I'm going to stick with the HK version as I want to have google services. and thanks for testing the oem unlock
I informed myself some more about FRP and OEM unlock and I am now feel safe to use the rooted HK firmware. Except, I came across one note for which I want further clarification before proceeding. The note is from http://www.androidcentral.com/factory-reset-protection-what-you-need-know and it says:
"A couple notes need added here. This doesn't undo Samsung's (or anyone else's) version of Reactivation Lock. If you've enabled data reset protection through your Samsung account, you'll need to turn that off in your Security settings. You can find the switch under the "Find My Mobile" section."
So, I want to be sure I don't have this samsung Reactivation Lock enabled. and that I am in no danger of it auto-enabling. I believe I am safe but I would like to know if anyone has more clear information.
What I do know is before I flashed to HK ROM, when I went into download mode, there displayed a setting:
"REACTIVATION LOCK: OFF"
now, using the HK ROM, it is gone, but in that exact same location is the setting:
"FRP LOCK: OFF"
I think, that means the mainland version of the FRP lock (Samsung Reactivation Lock), is now replaced with the google FRP lock and as I don't have to worry about the samsung reactivation lock anymore. Is that so?
even so, as the article says, I look in "Settings" >> "Lock screen and security" >> "Find my mobile" >> log into Samsung Account when prompted, then it does not display the "Reactivation Lock" option that is shown in at least one guide that I found. I really think this is further proof I don't have to worry about Samsung Reactivation Lock. Can anyone confirm?
Yes I can confirm.
But pay attention that because of the FRP, is not possible to make a pre-rooted firmware for Android 6.0 and above or 5.1.1 Samsung devices, from firmware contains FRP protection like the HK one.
From those android versions (and above), a pre-rooted firmware (or any root method) must include a patched kernel.
Due to the FRP protection, once it turn on, it detect the custom kernel (boot) and not allow the device to boot. (custom binary blocked by FRP lock)
That's the reason I had to replace the HK bootloader which contain FRP protection, with the China bootloader which contain the Samsung reactivation lock. (instead of FRP, because china firmwares doesn't include any google services)
I don't know what the policy of the Samsung reactivation lock, about custom kernels.
And also I don't know if the Samsung reactivation lock turns on automaticly if you are adding Samsung account. (Like the FRP lock)
And one more thing, I beleive most people don't use Samsung account at all.
So after all this,
If it come to decision what to use, the FRP lock or the Samsung one (depends only in the bootloader), I'm pretty sure that in this case (custom boot), the best is to use the Samsung lock, and just dont add Samsung account, or add Samsung account if needed but turn off the Reactivation lock in the Find my mobile settings.
I hope it help you a bit.
Good luck.
btw, If you can check the Samsung lock after root and report here, it would be great.
avicohh said:
Anyway, to be even more sure, I made a new firmware with the china bootloader, frp now is not even exist in download mode.
You can download the new firmware from here
http://www.mediafire.com/download/z7bh4sdmzqer6nb/J7108ZHU1APD1_rooted_by_avicohh_v2.exe
Good luck!
Click to expand...
Click to collapse
Oh, at first I thought you meant you rooted the mainland firmware. Now, based on your later post, I believe what you did was to put the mainland bootloader in the rooted HK firmware. Is this the case? If so, that means I can still have google services, and root, and no possibility of FRP issues because its a mainland bootloader. OK, I will try tonight. The Samsung reactivation lock is off by default. Even adding a Samsung account does not turn it on, you have to go into "find my phone" to turn it on. So it should be safe. I will confirm tonight after I download your new firmware.
Yes, this is exactly what i did.
Thanks for testing the samsung account. so it is pretty safe.
yes, this new version with mainland bootloader is good. It seems almost impossible to lock.
Now when I go to download mode, there is no more "FRP LOCK: OFF". in its place is "REACTIVATION LOCK: OFF".
Just for fun I tested by going inter developer options and turned off OEM unlock - then I tried to reboot = success. Enter download mode = still "REACTIVATION LOCK: OFF". Of course I turned it back on again after the test.
and in settings, find my mobile, there is still not a setting for "REACTIVATION LOCK". I have seen an example on the web that this reactivation lock setting should be at the bottom of the options under find my mobile. So, actually now I cannot find any way to turn on the reactivation lock - this is good, its what we want.
Of course to even enter the "find my mobile" section I can do nothing at all (in fact it does not even show me what the options are) untill I give my samsung account credentials. Once I give credentials I can see the options but there is no option to turn on reactivation lock. There is just one thing, maybe, is that in "find my mobile", there a place that says: for more information go to findmymobile.samsung.com. When I go there I have 2 options:
-1) FIND - Find, Lock, Wipe my device
-2) PREPARE - Ready device for Find my Mobile
this "prepare" option I am afraid to try, I am afraid it may be the one to enable reactivation lock. Clearly it is not required to actually find my mobile because I just click the "Find" button and it it finds it for me. So, what would be the use of "prepare"?
At any rate, we know that just creating a samsung account does not activate the lock. I never had a Samsung account before. When I set up this new phone I never did enter developer mode to turn on oem unlock but i did create the samsung account. It was after that I flashed version 1 of avicohh's rooted firmware and when I went into download mode, it said REACTIVATION LOCK: OFF, so creating the Samsung account does not turn it on.
avicohh said:
Hi Evryone.
Because I didn't found CWM or TWRP Recovery or any root method for the galaxy J5 J5108 and the J7 J7108, I made a pre-rooted firmwares for those models.
This firmware base on the hong kong firmware which include the Google apps, this a full firmware exactly like the original, except the root.
After flash you will see the SuperSU app in the app drawer.
Also, this firmware contains the bootloader from the china firmware which doesn't have frp lock.
The root include the binary files in the system, and a pathed boot. (from Android 6.0 or samsung 5.1.1 pathing the boot is necessary for the root work properly)
Flashing this firmware will not wipe data automaticly. you should not lose anything.
This file will work on any firmware/baseband/csc. you can always flash it like a stock firmware.
J5 - base on - J5108ZHU1APD2.
Android version: 5.1.1
J7 - base on - J7108ZHU1APD1.
Android version: 5.1.1
Downloads
J5
http://www.mediafire.com/download/o8hfu81j3j4irjt/J5108ZHU1APD2_Rooted_by_avicohh.exe
J7
http://www.mediafire.com/download/z7bh4sdmzqer6nb/J7108ZHU1APD1_rooted_by_avicohh_v2.exe
Installation instructions
Before flashing check the CROM Service status in Download mode, if it locked you will need to unlock the bootloader first with the app attached.
Install samsung usb drivers from here.
Download the self extracting 7z file above and extract it (just double tap) to some folder, you should receive a tar.md5 file.
Open odin 3 (attached in the zip)
Put the tar.md5 file in AP.
Put the device in download mode. (vol down + home + power button, and then click on vol up)
Connect your phone to usb and wait for odin detect the device.
Click start.
After it finish choose reboot system now in recovery.
Enjoy.
If you want to thank me for this work, you can do this by donating.. :good:
Click to expand...
Click to collapse
sir, you are awesome!!
I'll try to install in my J5108. I will give to my daughter. Is there a form to unroot the phone? Thanks!
Yes.
Just install stock rom.
http://updato.com/firmware-archive-select-model?record=A097D215549D11E6B055FA163EE8F90B
Hey,
I just wanted to inform you guys that switching on the OEM Unlock will force a factory reset after the next reboot (Security Integrity Check). So do it rather sooner then later, before you have to setup all again.
Update:
I took the time and tested it on ARC5, you can see the results on the attached image.
PS: Deactivating the OEM Unlock results in the same situation -> Factory Reset.
Tested and confirmed :good:
Savoury said:
Hey,
I just wanted to inform you guys that switching on the OEM Unlock will force a factory reset after the next reboot (Security Integrity Check). So do it rather sooner then later, before you have to setup all again.
Tested and confirmed on 3 different devices. :good:
Click to expand...
Click to collapse
Exynos or Snapdragon ?
Exynos.
I would expect the SD to act the same, as its a Knox related thing.
Savoury said:
Hey,
I just wanted to inform you guys that switching on the OEM Unlock will force a factory reset after the next reboot (Security Integrity Check). So do it rather sooner then later, before you have to setup all again.
Tested and confirmed on 3 different devices. :good:
Click to expand...
Click to collapse
Thanks for the heads-up, mines due here in a few hours, it'll be turned on before I do any personal config stuff :good::good:
Does it trip Knox if you turn on unlock bootloader and reboot?
candiesdoodle said:
Does it trip Knox if you turn on unlock bootloader and reboot?
Click to expand...
Click to collapse
No
but isn't always a locked bootloader as usual ? Qualcomm and Samsung as always can't allow to flash TWRP on Snap Galaxys
wolfgart said:
but isn't always a locked bootloader as ususal ? Qualcomm and Samsung as always can't allow to flash TWRP on Snap Galaxys
Click to expand...
Click to collapse
Right, you need to be on Exynos for the software switch
OEM unlock is hiddin on my GS9+ (Exynos) [emoji848]
It's right there.. dunno where yours is hiding.
Savoury said:
It's right there.. dunno where yours is hiding.
Click to expand...
Click to collapse
Might be a CSC problem
Maybe. I'm on DBT..
What does OEM unlock accomplish on a US Snapdragon carrier phone?
El Maestro said:
OEM unlock is hiddin on my GS9+ (Exynos) [emoji848]
Click to expand...
Click to collapse
Boot into Download mode - see if it says "Pre-Normal" - if so, you will have to wait 7 days before you can use OEM unlock - if it does say Pre-Normal, you are locked from flashing anything until it does show OEM unlock. This will happen in 7 days - if we have twrp by then and you plan to flash twrp - you will need to get the RMM State Fix and flash that immediately after flashing TWRP. You can find the RMM FIX here:
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
The "Pre-Normal" thing is a known thing for S8/S8Plus and Note 8 Phones and at least for now, will be something many of us will have to deal with from now on.
meyerweb said:
What does OEM unlock accomplish on a US Snapdragon carrier phone?
Click to expand...
Click to collapse
I'd be really surprised if there is a functioning OEM unlock switch on the US SD phone.
Geekser said:
Boot into Download mode - see if it says "Pre-Normal" - if so, you will have to wait 7 days before you can use OEM unlock - if it does say Pre-Normal, you are locked from flashing anything until it does show OEM unlock. This will happen in 7 days - if we have twrp by then and you plan to flash twrp - you will need to get the RMM State Fix and flash that immediately after flashing TWRP. You can find the RMM FIX here:
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
The "Pre-Normal" thing is a known thing for S8/S8Plus and Note 8 Phones and at least for now, will be something many of us will have to deal with from now on.
Click to expand...
Click to collapse
i would but I'm almost half way to my "7 days jail".
El Maestro said:
i would but I'm almost half way to my "7 days jail".
Click to expand...
Click to collapse
Then you already know what to do - for what it's worth, I went thru this on my S8 Plus - contrary to what some have said, you can turn the phone off - doesn't effect your time in jail at all - you just need to keep data enabled while the phone is on -- and not take out the sim card.
good luck to you my friend.
Savoury said:
Hey,
I just wanted to inform you guys that switching on the OEM Unlock will force a factory reset after the next reboot (Security Integrity Check). So do it rather sooner then later, before you have to setup all again.
Tested and confirmed on 3 different devices. :good:
Click to expand...
Click to collapse
I don't think you are correct. I changed my OEM Unlock on this phone and every other phone I own and it NEVER does a factory reset. Never. Switched on OEM unlock today and it did not do a factory reset on my S9 Plus.
Geekser said:
I don't think you are correct. I changed my OEM Unlock on this phone and every other phone I own and it NEVER does a factory reset. Never. Switched on OEM unlock today and it did not do a factory reset on my S9 Plus.
Click to expand...
Click to collapse
You did reboot the phone after enabling OEM Unlock?
This is the time, when Integrity check fails and you need to factory reset. And yes, that is completely new for Samsung and at the moment only on the S9/S9+
maik005 said:
You did reboot the phone after enabling OEM Unlock?
This is the time, when Integrity check fails and you need to factory reset. And yes, that is completely new for Samsung and at the moment only on the S9/S9+
Click to expand...
Click to collapse
Yes, I rebooted the phone immediately after I switched on OEM unlock and it did not do a factory reset.
I need to flash a different firmware onto my Note 20. I haven't dealt with this before so I'm pretty new.
The situation: I removed the frp lock but I still have an OEM lock and KG Lock on it.
I have tried to mess with PIT files but no luck. A friend that crossed me locked it so I cant even go into setting to disable the OEM lock.
Wdym locked it?
You mean your screen lock?
Kenora_I said:
Wdym locked it?
You mean your screen lock?
Click to expand...
Click to collapse
No I mean the KG lock, my friend put some sort of lock on it that reappears after a factory reset and needs a pin to access the phone.
Coolbeans007 said:
No I mean the KG lock, my friend put some sort of lock on it that reappears after a factory reset and needs a pin to access the phone.
Click to expand...
Click to collapse
Laiyox said:
Hello Guys
I want to tell how to bypass RMM state: prenormal to install TWRP
Also this will resolve "Only official binaries are allowed"
Disclaimer:
I am NOT responsible for any damage done if you use my guide.
It worked for me 100% and should normally work for everybody!
Feel free to share to anyone else or to embed if you want.
-------------------------------------------------
1. Download latest Stock base via SamFirm
2. Install latest Stock base via Odin Odin v3.13.1 direct download
3. Boot into system
4. Skip the setup
5. Activate Developer settings
6. search and turn of automatic system update
7. Go to time settings and deactivate automatic time
8. Turn back the day for more than 7 days. ( I have turned to the 20th Dec 2018)
9. Search for Software update -> Don't install update
10. Look if latest time searched for updates is the date which you have set. (for me 20th Dec 2018)
11. Reboot your device
12. go into the time settings and reactivate the automatic time
13. Search again for software update - > Still don't install
14. Go to Developer settings
15. deactivate OEM Unlock and reactivate
16. Go to download mode and you will don't see RMM state anymore
18. install TWRP by odin
19. boot into TWRP
20. format data
21. reboot recovery
22. flash verity.zip // found on https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
23. Et voilà! You got completely functional TWRP on your device with Pie Bootloader
24. Flash your preferred Rom!
-------------------------------------------------
Thanks to:
zxz0O0 for SamFirm
Have Fun
Click to expand...
Click to collapse
This that?
Hi folks,
my trusty S3 (SM-T825) got broke unexpectedly. It showed "100% battery" in the morning but was unresponsive. A forced shutdown did reboot the device up to the logo-screen - from where it rebooted again. So obviously it's stuck in a boot loop.
Unfortunately, it does not enter "recovery" either (home) (up) (power). However, it DOES enter "ODIN mode" (home) (down) (power). There it shows me that FRP Lock and OEM lock both are still active. This is no wonder as it caught me unprepared. FRP lock wouldn't be a problem, as I'm the owner of the account and can supply credentials once it boots up again.
Everywhere it is STRONGLY advised to turn off OEM lock before flashing anything to not make it even worse. This renders the device essentially dead, right?
The device is still as original as it can be.
Any chance I can revive it or does that more look like a mainboard problem?
I already have ODIN and I even have an actual 4-part "Original ROM" for my region (Samfw.com_SM-T825_ATO_T825XXU3CTD1_fac.zip), but maybe TWRP and Lineage would be the better options.
Before I just go and make things worse, I'd like to ask for a qualified advice ;-)
smallfreak said:
...... There it shows me that FRP Lock and OEM lock both are still active. This is no wonder as it caught me unprepared. FRP lock wouldn't be a problem, as I'm the owner of the account and can supply credentials once it boots up again.
Everywhere it is STRONGLY advised to turn off OEM lock before flashing anything to not make it even worse. This renders the device essentially dead, right?
Click to expand...
Click to collapse
Afaik you should be able to flash stock with OEM lock active BUT idk if FRP will block flashing process.
If that happens it's imo afterwards in the same state as before so at least it won't worsen it.
Gonna loose all your data anyhow.
Got Smartswitch? This might help as well.
smallfreak said:
....... I already have ODIN and I even have an actual 4-part "Original ROM" for my region (Samfw.com_SM-T825_ATO_T825XXU3CTD1_fac.zip), but maybe TWRP and Lineage would be the better options.
Click to expand...
Click to collapse
You can't replace recovery without OEM unlock.
smallfreak said:
Before I just go and make things worse, I'd like to ask for a qualified advice ;-)
Click to expand...
Click to collapse
Dunno if I'm qualified enough
Next turn ...
I tried flashing TWRP into the AP slot with SamFW FRP-Tool (ODIN). This worked so far but got me a note on the tablet "custom recovery blocked due to FRP lock".
Checking boot on the tablet - as before. Boot loop.
Next turn ...
Code:
Select file AP_T825XXU3CTD1_CL17011592_QB30231355_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar.md5
Select file CP_T825XXU3CTA1_CP14962504_CL17011592_QB28791445_REV00_user_low_ship_MULTI_CERT.tar.md5
Select file CSC_ATO_T825ATO3CTD1_CL18361310_QB30233690_REV00_user_low_ship_MULTI_CERT.tar.md5
Reading... OK
Detect mode: Download mode
Model : SM-T825
Bit : 4
Unique number : CBJ100915EAF124
Storage : 32
Vendor : SAMSUNG
Disk : BJNB4R
Firmware : https://samfw.com/firmware/SM-T825/
Analyze files...
Flashing with SAMSUNG Mobile USB Modem (COM5)
Flash failed
Flash time: 00:47
Reading... FAIL
unchecking CP and CSC, leaving only AP.
Code:
Analyze files...
Flashing with SAMSUNG Mobile USB Modem (COM5)
Flash failed
Flash time: 10:00
Reading... FAIL
Reboot tablet in download-mode, next turn: Try BL + AP:
Code:
Select file BL_T825XXU3CTD1_CL17011592_QB30231355_REV00_user_low_ship_MULTI_CERT.tar.md5
Reading... OK
Detect mode: Download mode
Model : SM-T825
Bit : 4
Unique number : CBJ100915EAF124
Storage : 32
Vendor : SAMSUNG
Disk : BJNB4R
Firmware : https://samfw.com/firmware/SM-T825/
Analyze files...
Flashing with SAMSUNG Mobile USB Modem (COM5)
Checking file BL_T825XXU3CTD1_CL17011592_QB30231355_REV00_user_low_ship_MULTI_CERT.tar.md5
Checking file AP_T825XXU3CTD1_CL17011592_QB30231355_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar.md5
Flashing (1/20) emmc_appsboot.mbn.lz4 OK
Flashing (2/20) lksecapp.mbn.lz4 OK
Flashing (3/20) xbl.elf.lz4Flash failed
Flash time: 01:26
Tablet moans about
SW REV CHECK FAIL : [lksecapp] Fused -1 > Binary 0
Click to expand...
Click to collapse
So maybe the firmware revision is different to the currently installed one? The latest file is from 2020 and since I did the usual OTA updates, this should be the version installed. But even if not, it sould not matter to upload a newer one, right?
Anything I can check?
So then obviously "Game Over"
Another piece of expensive waste that otherwise could have served well for years to come. Yes I know, selling something just once is an inferior business model to repeatedly draining my account for the same service.
Hello! So I am on a journey to attempt to root a Samsung tab a7 lite sm-t227u. So I want to be extremely transparent as to my reason for rooting:
I was given this tablet by my father whom got it from a previous job. When he left the job they never asked for it back, a long with a good bit of supplies he had that he got to keep.
So, I have this tablet, I can get into it as it doesn't have a passcode. I have wiped it by factory reset as well. However, it has IBM's MAAS360 installed and after factory reset AND a firmware flash using odin I still cannot get rid of this maas360 mdm. It is not Knox locked. I can activate developer mode and change all those settings, but I cannot download any apps through the app store at all or enable unknown source app install as those are under an IT block. I also do not have the OEM unlock option in dev options. I've tried the whole changing the date and connecting to wifi, with and without sim card but I cannot get this option to show, nor can I unlock the bootload through fastboot.
I have read that most of the new samsung phones do not have a bootloader unlock option, but from what I can tell that is specific to the snapdragon phones, and this tablet is running a mediatek chip.
Now, if I can remove mdm restrictions without rooting that's great, but I have a feeling that is the only way to properly flash this thing to completely remove the mdm.
I have tried the recovery tar that is posted in this forum but I cannot get it to flash, likely because I still don't have an unlocked bootloader
Have any of you all faced something similar or know of a solution? I may call the company the mdm is managed by and just see if they will remove it from their system, but I find it highly unlikely.
SM-T227U is an American model wich doesn't have the OEM unlocking option, you could unlock using unofficial ways but those are not pretty "stable".
coocooguy246 said:
Hello! So I am on a journey to attempt to root a Samsung tab a7 lite sm-t227u. So I want to be extremely transparent as to my reason for rooting:
I was given this tablet by my father whom got it from a previous job. When he left the job they never asked for it back, a long with a good bit of supplies he had that he got to keep.
So, I have this tablet, I can get into it as it doesn't have a passcode. I have wiped it by factory reset as well. However, it has IBM's MAAS360 installed and after factory reset AND a firmware flash using odin I still cannot get rid of this maas360 mdm. It is not Knox locked. I can activate developer mode and change all those settings, but I cannot download any apps through the app store at all or enable unknown source app install as those are under an IT block. I also do not have the OEM unlock option in dev options. I've tried the whole changing the date and connecting to wifi, with and without sim card but I cannot get this option to show, nor can I unlock the bootload through fastboot.
I have read that most of the new samsung phones do not have a bootloader unlock option, but from what I can tell that is specific to the snapdragon phones, and this tablet is running a mediatek chip.
Now, if I can remove mdm restrictions without rooting that's great, but I have a feeling that is the only way to properly flash this thing to completely remove the mdm.
I have tried the recovery tar that is posted in this forum but I cannot get it to flash, likely because I still don't have an unlocked bootloader
Have any of you all faced something similar or know of a solution? I may call the company the mdm is managed by and just see if they will remove it from their system, but I find it highly unlikely.
Click to expand...
Click to collapse
Hey man! Still got your tab 7? I also have a SM-T227U and have oem unlocked! After doing the usual stuff, you will want to turn off automatically update in developer settings. After that, go to settings>General management>Date and time and select manual time and date, and set it for exactly 10 days before the day you attempt this. OEM unlock will appear in dev settings!!!
Then turn off device and while holding power up + power down, plug into PC. It will show the pre-download mode screen where it asks if you want to continue. Just follow the on screen instructions to unlock bootloader!
*note that the bootloader unlocking results in an unavoidable factory reset**
evan5935 said:
Hey man! Still got your tab 7? I also have a SM-T227U and have oem unlocked! After doing the usual stuff, you will want to turn off automatically update in developer settings. After that, go to settings>General management>Date and time and select manual time and date, and set it for exactly 10 days before the day you attempt this. OEM unlock will appear in dev settings!!!
Then turn off device and while holding power up + power down, plug into PC. It will show the pre-download mode screen where it asks if you want to continue. Just follow the on screen instructions to unlock bootloader!
*note that the bootloader unlocking results in an unavoidable factory reset**
Click to expand...
Click to collapse
Sweet! I will absolutely try this when I get home this afternoon, will report back with results!
But just for clarity. Let's say I start with a freshly wiped tablet. Go through set up and connect to wifi, do I need to add a Google and Samsung account? Then in dev settings, enable USB debugging, also enable wifi debugging? Then change the date. Is there any step I am missing?
coocooguy246 said:
Hello! So I am on a journey to attempt to root a Samsung tab a7 lite sm-t227u. So I want to be extremely transparent as to my reason for rooting:
I was given this tablet by my father whom got it from a previous job. When he left the job they never asked for it back, a long with a good bit of supplies he had that he got to keep.
So, I have this tablet, I can get into it as it doesn't have a passcode. I have wiped it by factory reset as well. However, it has IBM's MAAS360 installed and after factory reset AND a firmware flash using odin I still cannot get rid of this maas360 mdm. It is not Knox locked. I can activate developer mode and change all those settings, but I cannot download any apps through the app store at all or enable unknown source app install as those are under an IT block. I also do not have the OEM unlock option in dev options. I've tried the whole changing the date and connecting to wifi, with and without sim card but I cannot get this option to show, nor can I unlock the bootload through fastboot.
I have read that most of the new samsung phones do not have a bootloader unlock option, but from what I can tell that is specific to the snapdragon phones, and this tablet is running a mediatek chip.
Now, if I can remove mdm restrictions without rooting that's great, but I have a feeling that is the only way to properly flash this thing to completely remove the mdm.
I have tried the recovery tar that is posted in this forum but I cannot get it to flash, likely because I still don't have an unlocked bootloader
Have any of you all faced something similar or know of a solution? I may call the company the mdm is managed by and just see if they will remove it from their system, but I find it highly unlikely.
Click to expand...
Click to collapse
If it has Mediatek chipset then you can use SP flash tool to format the tablet firmware and reflash it.
I would strongly recommend you to backup the NV DATA and NVRAM files before you format the tablet.
coocooguy246 said:
Sweet! I will absolutely try this when I get home this afternoon, will report back with results!
But just for clarity. Let's say I start with a freshly wiped tablet. Go through set up and connect to wifi, do I need to add a Google and Samsung account? Then in dev settings, enable USB debugging, also enable wifi debugging? Then change the date. Is there any step I am missing?
Click to expand...
Click to collapse
You can follow this guide actually! ( https://forum.xda-developers.com/t/...220-t225-install-lsposed-magisk-mods.4406933/) it recommends just skipping the setup junk
I have found that many times, rooting methods work across different models of the same device unless there are some sort of major differences in chipsets or some sort of random change lol
The only thing that doesn't seem to work for our model is section V of the guide which is for the removal of the "bootloader is unlocked" screen at startup. so you will still need to press the power button on that screen to boot up. It's a tiny hassle, but otherwise no big deal in my personal opinion
Make sure to read all the way to the end of the root section (section 4) and especially remember step 7. I retried probably 4 times and even patched the entire AP file of the firmware for use in odin (doing this gives a second warning on Knox screen that it isn't samsung official fw then boots normally into the bootlogo screen) before realizing everything was going fine.. I recommend just using the patched Magisk boot.img first just because I find it unsightly
Just flash the boot.tar in the AP slot. Don't download any of the boot imgs from the guide because they are for the t220's and t225's. I'll link the one I made according to the guide below. It'll save you some time and you won't need to install zarchiver and Magick just to have it factory reset again lol. Just download the latest Magisk apk (26.1) from the official github (https://github.com/topjohnwu/Magisk/releases) and install it when you have completed the 2nd factory reset/the patched boot img install.