I own a, Galaxy Tab s4, SM-T830. It is rooted with Magisk 25.2 and TWRP recovery, The tablet is FRP locked. I inadvertently re-enabled OEM unlock and turned off my tablet. When I turned it back on it went directly to the FRP screen. I cannot access recovery or anything else.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can get it to Download mode only by plugging it in to my PC, holding the power and both volume up and down at the same time.
I then try to flash the current firmware, T830XXU5CVG2_T830OXM5CVG2_XAR.ZIP from Sammobile through Odin and it fails. I extracted the PIT file and tried to repartion and flash the firmware and that fails also. I cannot find or create a combination file to break the FRP lock. Does anyone have suggestions to fix this? Nothing I've tried seems to work. Thanks!
The partition that FRP uses is not accessible and overwritable.
You need to find a way to flash the rescue firmware with the same BIT.
Show the log from Odin.
This is the PIT file I extracted from the firmware: GTS4LWIFI_EUR_OPEN.pit
Here is my Odin flash log:
Why don't you use all 4 files like the ones below?
AP_T830XXU5CVG2_CL22915538_QB54340207_REV00_user_low_ship_MULTI_CERT_meta_OS10.tar.md5
BL_T830XXU5CVG2_CL22915538_QB54340207_REV00_user_low_ship_MULTI_CERT.tar.md5
CSC_OMC_OXM_T830OXM5CVG2_CL22915538_QB54340207_REV00_user_low_ship_MULTI_CERT.tar.md5
HOME_CSC_OMC_OXM_T830OXM5CVG2_CL22915538_QB54340207_REV00_user_low_ship_MULTI_CERT.tar.md5
I've tried all and in different combinations. From what I understand, the Home_CSC and regular CSC files are the same except the Home_CSC version does not erase all your data and the CSC does. it is now... It boots into that first warning screen and I can do nothing else. I can't access recovery and the only way to access download mode is to plug it into my PC with Odin running while holding down the power and both volume buttons. I've searched all over the internet and haven't found anyone else who has been this locked out. Did I brick my tablet? Is it possible to totally wipe the memory in this tablet and reinstall the firmware? I used ADB a long time ago on one of my phones I have forgotten how to use it.
EDIT: REMOVED RANT
7ravler said:
I've tried all and in different combinations. From what I understand, the Home_CSC and regular CSC files are the same except the Home_CSC version does not erase all your data and the CSC does. it is now... It boots into that first warning screen and I can do nothing else. I can't access recovery and the only way to access download mode is to plug it into my PC with Odin running while holding down the power and both volume buttons. I've searched all over the internet and haven't found anyone else who has been this locked out. Did I brick my tablet? Is it possible to totally wipe the memory in this tablet and reinstall the firmware? I used ADB a long time ago on one of my phones I have forgotten how to use it.
{Start Rant}I paid a lot of money for this tablet and I should have the right to mess with the firmware without Samsung totally locking me out of it! I can understand if I did something and really broke it. But to have Samsung actually lock me out because they don't like me putting other software on my paid for, expensive tablet? That's just wrong! {End Rant}
Click to expand...
Click to collapse
You own only the hardware. The software has been licensed to you under a number of conditions, which you accepted when you first launched the tablet.
I wish you find a solution in the end, but you shouldn't hold a grudge against anyone for what you did yourself.
You own only the hardware. The software has been licensed to you under a number of conditions, which you accepted when you first launched the tablet.
I wish you find a solution in the end, but you shouldn't hold a grudge against anyone for what you did yourself.
Click to expand...
Click to collapse
You are right. I apologize for going off topic.
So... I downloaded the newest firmware:
AP_T830XXU5CVG2_CL22915538_QB54340207_REV00_user_low_ship_MULTI_CERT_meta_OS10.tar.md5
BL_T830XXU5CVG2_CL22915538_QB54340207_REV00_user_low_ship_MULTI_CERT.tar.md5
CSC_OMC_OXM_T830OXM5CVG2_CL22915538_QB54340207_REV00_user_low_ship_MULTI_CERT.tar.md5
HOME_CSC_OMC_OXM_T830OXM5CVG2_CL22915538_QB54340207_REV00_user_low_ship_MULTI_CERT.tar.md5
Then I used FRP Hijacker by Hagard v1.0 to break the FRP lock. I pointed it to the AP and BL binaries to make a combination file, but I didn't actually flash that with Odin. I don't know if FRP hijacker used it. I had to go through it several times because It kept reporting adb problems and device detection problems. Finally I got this:
I did try Smart switch but It kept losing connection.
Without turning off my tablet I disconnected the tablet and opened Odin3-v3.14.1-3B-PatcheD.zip then attached the tablet again. Earlier I extracted GTS4LWIFI_EUR_OPEN.pit from the CSC binary. In Oden I checked NAND ERASE and RE-PARTITION. I loaded the PIT file in the PIT entry and flashed. I had to do this a few times then it succeeded! I unplugged the tablet, didn't turn it off and restarted Odin. Plugged the tablet in and loaded the new firmware. My tablet is like NEW!! Knox is tripped though.
{EDITED} I keep editing this post as I remember more of what I did. Sorry I didn't keep an organize log of what I did. Maybe some of you experts can look at what I did and figure out how it worked.
7ravler said:
So... I downloaded the newest firmware:
AP_T830XXU5CVG2_CL22915538_QB54340207_REV00_user_low_ship_MULTI_CERT_meta_OS10.tar.md5
BL_T830XXU5CVG2_CL22915538_QB54340207_REV00_user_low_ship_MULTI_CERT.tar.md5
CSC_OMC_OXM_T830OXM5CVG2_CL22915538_QB54340207_REV00_user_low_ship_MULTI_CERT.tar.md5
HOME_CSC_OMC_OXM_T830OXM5CVG2_CL22915538_QB54340207_REV00_user_low_ship_MULTI_CERT.tar.md5
Then I used FRP Hijacker by Hagard v1.0 to break the FRP lock. I had to go through it several times because It kept reporting adb problems and device detection problems. Finally I got this:
View attachment 5752231
Without turning off my tablet I opened Odin3-v3.14.1-3B-PatcheD.zip and attached the tablet again. Earlier I extracted GTS4LWIFI_EUR_OPEN.pit from the CSC binary. In Oden I checked NAND ERASE and RE-PARTITION. I loaded the PIT file in the PIT entry and flashed. I had to do this a few times then it succeeded! I unplugged the tablet, didn't turn it off and restarted Odin. Plugged the tablet in and loaded the new firmware. My tablet is like NEW!! I am pretty sure but, I think Knox is reset.
Click to expand...
Click to collapse
Hello, I'm glad you have got you tablet back to life. I am facing the same issue, with the same U5 model, I tried to follow the same process you did but have no luck so far. Just wondering, for using the FRP Hijacker by Hagard v1.0 tool, which device do you selected? Or did you just use the adb operation mode? If you have used the ADB mode, can you please give some more detail on how you got to adb mode? I'm having some trouble getting the adb mode to work. I can select a random device from the drop down list of the tool and got to the screen in your screenshot, but it still wouldn't flash the pit file, saying the FRP enabled and pit is blocked. and all subsequent steps would not work at all.
For the device, I actually typed in SM-T830. But, I downloaded my firmware from Sammobile.com. My ADB failed too but I kept hitting it. Also...I checked Remove FRP and Softbrick Fixer on the first tab and kept hitting that. I was having problems with it not seeing my device but I kept clicking at it and eventually it took. Not a very scientific method but I just kept beating it until it worked.
7ravler said:
For the device, I actually typed in SM-T830. But, I downloaded my firmware from Sammobile.com. My ADB failed too but I kept hitting it. Also...I checked Remove FRP and Softbrick Fixer on the first tab and kept hitting that. I was having problems with it not seeing my device but I kept clicking at it and eventually it took. Not a very scientific method but I just kept beating it until it worked.
Click to expand...
Click to collapse
I had a similar experience to the OP in this thread - Galaxy Tab S4 got stuck in a boot loop after trying to move apps to microSD card. I can't get anywhere with Odin and the firmware without getting a "Complete(Write) operation failed" error. Possibly this is due to FRP lock? On my download mode screen it says "FRP Lock: On".
Anyway I tried FRP Hijacker as well but it just loops saying "Detecting Device Interface: OK" and "Setting to Download Mode: OK" but never actually does anything. How did you make the programme work on this device? What did you keep hitting? Many thanks.
I did not get the "Complete(Write) operation failed" error. Was that in Odin or FRP Hijacker?
All I know is after this screen showed
Everything started working. Odin succeeded and my tablet was restored.
For future reference use samfw’s frp unlocler
Related
Guide
Yesterday I first successfully flashed G5 firmware + root. Later I unsuccessfully tried to make the lag fix for memory card. After that I recovered back up using Back UP Pro and restarted. Got a bunch of FC, so decided to reflash.
During the flash on first step odin crashed (just a nondescript message with attention sign and path to Odin) + second error right after first one, only with some strange symbals-hieroglyphs after the path to odin).
Edit - pics:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and
After that nothing is happening in odin and everything is grayed out. Error can be different (that was just my error), but the point is that phone is bricked (does not turn on). Causes can vary from you disconecting device during flash, computer crashing, ODIN crashing (my case), alien abductions and other very possible reasons =)
After that I always got the same problem - either stuck on reading file (or what is the first step analyses, etc) or crashes (mostly now).
Phone is bricked - I can either go to download screen, or some screen with phone and computer icons connected by dotted line with attention icon - screenshot, thanks to m3keni.
I looked at "Disable Driver Signature Enforcement" (thanks goes to blackerwater) advice and several recovery advices (up + menu + power; down + power; laptop does not recognize apd device).
Win 7 x64.
Solution
try odin on a different computer phone should be ok once you flash.. i flash multiple times on one then suddenly wouldnt flash anymore.. just hung.. re-did it on a laptop and it worked fine.
dupel said:
Yesterday I first successfully flashed G5 firmware + root. Later I unsuccessfully tried to make the lag fix for memory card. After that I recovered back up using Back UP Pro and restarted.
Got a bunch of FC, so decided to reflash.
During the flash on first step odin crashed (just a nondescript message with attention sign and path to Odin) + second error right after first one, only with some strange symbals-hieroglyphs after the path to odin).
After that I always got the same problem - either stuck on reading file (or what is the first step analyses, etc) or crashes (mostly now).
Phone is bricked - I can either go to download screen, or some screen with phone and computer icons connected by dotted line with attention icon.
I looked at "Disable Driver Signature Enforcement" advice and several recovery advices (up, menu, power; down, power; laptop does not recognize apd device), however, haven't found anything good. Including restarting (device, laptop), using different usb slots (eventually run out of), etc.
What are the other options for recovery? And any possible advice on such an error? Like how to do a complete wipe, hardreset, recovery, better flashing advice?
My first time bricking Android (god knows how much times I did it to my symbian )
Win 7 x64. Will add screenshots (if forums will allow me) tomorrow afternoon, now I need some sleep and have to wake up early.
Click to expand...
Click to collapse
something like this???
If so, try to remove the battery.. leave it out for about 30 - 60 seconds.. patience is the key..
Try to restart your computer and then upon restart.. load odin.. load pit.. code.. modem.. csc..
Now on your phone.. press the volume down + home key then power ON the phone.
Connect your device to your computer.. ding ding..
As per the odin application choose, enabale re-partition..
Then press START.
**cross your fingers and hope for the best.
**i encountered that screen when my lappy suddenly died.. unplugged the wrong power cord (my lappy's battery is MIA at the moment).
Wish you all the best and hope this works.
m3keni said:
something like this???
Click to expand...
Click to collapse
Yup, thats the screen. Today quickly in the morning managed to start up odin, but it got stuck on "set pit file, do not turn off" step. Stuck there for some 5 min already.
dupel said:
Yup, thats the screen. Today quickly in the morning managed to start up odin, but it got stuck on "set pit file, not dot retn off" step. Stuck there for some 5 min already.
Click to expand...
Click to collapse
..since it's been 5 minutes already.. disconnect your phone and then remove the battery for about a minute or 2.
..prepare the following..
s1_odin_20100512.pit *from http://forum.xda-developers.com/attachment.php?attachmentid=359929&d=1279109916
PDA: CODE_I9000XWJG5.tar *from JG5 firmware
PHONE: MODEM_I9000XXJG1.tar *from JG5 firmware
CSC: CSC_I9000OXXJG4.tar *from JG5 firmware
..Access the download mode of your phone.. vol down + home ++ ON..
..Open ODIN3 and then set the directories for the files listed above..
..Connect your phone to the PC and wait for about a minute or 2..
..On ODIN3.. ID:Com should show something.. yellow bar with com port ranging from 1 to 10..
..tick Re-Partition and when you are ready click START.
[that is the exact steps I followed]
m3keni said:
..since it's been 5 minutes already.. disconnect your phone and then remove the battery for about a minute or 2.
..prepare the following..
s1_odin_20100512.pit *from http://forum.xda-developers.com/attachment.php?attachmentid=359929&d=1279109916
PDA: CODE_I9000XWJG5.tar *from JG5 firmware
PHONE: MODEM_I9000XXJG1.tar *from JG5 firmware
CSC: CSC_I9000OXXJG4.tar *from JG5 firmware
..Access the download mode of your phone.. vol down + home ++ ON..
..Open ODIN3 and then set the directories for the files listed above..
..Connect your phone to the PC and wait for about a minute or 2..
..On ODIN3.. ID:Com should show something.. yellow bar with com port ranging from 1 to 10..
..tick Re-Partition and when you are ready click START.
[that is the exact steps I followed]
Click to expand...
Click to collapse
Thats exactly what I have been doing (and tried flashing pit 513 + JG1, as it was my previous firmware), but once again am stuck at crashes in odin.
Will try, if everything fails today, to flash it from friends computer in the evening.
Have you tried downloading a fresh copy of odin? Odin should not need any compatibility modes so you should start looking for what you changed on your PC between the last working and the non-working flash. But rest (relatively) easy: The state your phone is in, is quite easily recovered (given you have a working PC)
Just reflashed my phone successfully. In case anyone has the same error in future what I did is:
1) Run ODIN with admin rights and in comparability mode.
2) Restart. I did about gazilion restarts, both windows and phone.
3) Every flash - restart of phone (remove battery), without SD card or SIM card, restart of Windows (7 x64) - during the boot process press F8 and Select "Disable Driver Signature Enforcement". (thanks to http://forum.xda-developers.com/showthread.php?t=723041 ).
Every restart - new USB port, not sure if it did affect anything.
4) While I have seen recommendations to close Kies and any other software that could use COM ports (I have OVI Suite and Nokia PC Suite installed for my old Nokia 5800) on last sucesful flash-reboot I left everything running.
5) Try re-downloading ODIN again, in case it is corrupted. Or re-downloading the firmware.
6) Very possible solution for my original problem (screenshots) - starting ODIN as soon as windows starts and to flash as soon as you can after windows start. Seems to fix my original issue.
7) Interesting solution by eizyark
The most sucessful combination proved to be:
a) Restart the PC using the Disable Driver Signature Enforcement.
b1) Optionally (if you already have bricked device) try leaving Kies on (tray icon).
b2) Run ODIN and select files you wish to flash (I used pit 512 and JG5 files - all 3, code-pda, modem-phone and csc).
b3) Usually it is recommended to select "Re-Partition" (in some cases might actually help you unbrick - experiment) - I did not.
c) Switch on the phone (insert the battery) and boot into download mode (Volume down + Menu + power)
d) Connect the cables (cable was disconnected from both the device and laptop). At this stage Odin should see your device, as described by flash tutorials (yellow + COM).
e) Flash.
Darkstriker said:
Have you tried downloading a fresh copy of odin?
Click to expand...
Click to collapse
Actually I did. Don't think it was actually a problem with ODIN as its just an executable file. Old-new file sizes were the same and it made no difference trying to flash.
All I can say - Im guite a geek, have been playing around with computers for more than decade and I still dont understand them. I really have no idea what was so different this time, but I actually did flash my phone again.
What is even funnier - just tried to flash the modified kernel for ext4 partition on sd card - same error (phone though reboots without any problems).
I think I found another way as well on how to save your phone. I had a similar problem. what I did was, when odin has detected the phone, press start without adding anything. after a few seconds the phone will boot up normally. well it worked for me, maybe this might help others as well.
Sent from my GT-I9000 using XDA App
Maybe we should pin this or any other topic for people to post if they have bricked their device?
I'm sorry to say this and I in no way mean to offend you:
This "Solution" is a seemingly random collection of steps, any of which may have originally been the real solution. However, many of the steps are likely superfluous and before this can become a guide/reference, you would definitely need to narrow this down to steps that need to be taken in specific situations.
m3keni said:
something like this???
If so, try to remove the battery.. leave it out for about 30 - 60 seconds.. patience is the key..
Try to restart your computer and then upon restart.. load odin.. load pit.. code.. modem.. csc..
Now on your phone.. press the volume down + home key then power ON the phone.
Connect your device to your computer.. ding ding..
As per the odin application choose, enabale re-partition..
Then press START.
**cross your fingers and hope for the best.
**i encountered that screen when my lappy suddenly died.. unplugged the wrong power cord (my lappy's battery is MIA at the moment).
Wish you all the best and hope this works.
Click to expand...
Click to collapse
If you have this screen then just disconnect the USB lead, press and hold, power, vol. down and home until the 'Downloading' screen appears, start ODIN and then reconnect the USB and reflash.
Darkstriker said:
I'm sorry to say this and I in no way mean to offend you:
This "Solution" is a seemingly random collection of steps, any of which may have originally been the real solution. However, many of the steps are likely superfluous and before this can become a guide/reference, you would definitely need to narrow this down to steps that need to be taken in specific situations.
Click to expand...
Click to collapse
I know =) It was just a solution for my original problem. Thats why I said that this, or any other topic. Its just now we had close to 10 topics, not to mention posts in faq or original topics about each firmware asking pretty much the same questions and describing the almost the same problem.
Introduce a bit of order to anarchy, so to say
dupel said:
I know =) It was just a solution for my original problem. Thats why I said that this, or any other topic. Its just now we had close to 10 topics, not to mention posts in faq or original topics about each firmware asking pretty much the same questions and describing the almost the same problem.
Introduce a bit of order to anarchy, so to say
Click to expand...
Click to collapse
The problem is that (unlike your issue) 95% of those could be resolved simply by reading the FAQ properly.
ODIN
1st post
My phone was stuck in this infinite loop where try as I might I couldn't get it to re-flash I tried different computers and all and the only thing that worked was getting odin to flash without a rom.
it got my phone out of the loop
Helped heaps
m3keni said:
If so, try to remove the battery.. leave it out for about 30 - 60 seconds.. patience is the key..
Try to restart your computer and then upon restart.. load odin.. load pit.. code.. modem.. csc..
Now on your phone.. press the volume down + home key then power ON the phone.
Connect your device to your computer.. ding ding..
As per the odin application choose, enabale re-partition..
Then press START.
**cross your fingers and hope for the best.
**i encountered that screen when my lappy suddenly died.. unplugged the wrong power cord (my lappy's battery is MIA at the moment).
Wish you all the best and hope this works.
Click to expand...
Click to collapse
When I press the Volume Down + Home Key and then Power I get the Phone!PC screen instead of the download screen.
was bored at work and just kept pressing the Download mode combo over and over and it went to download mode from the dreaded cell!pc screen. got the stock rom to flash finally and all appears to be well.
Hi,
Sorry to interrupt but I've managed to brick mine completely...I was trying to update to Froyo without getting any far (not applied any firmware as yet) but I thought I could try the three button fix first so I downloaded the .zip file and stored in root directory of phone.
Before I could apply the fix...i was messing around and the three button worked without applying the fix. However, in recovery mode, first i deleted the data and did a factory reset followed by .zip update (three button fix file...what was i thinking!) which screwed up the phone useless.
It does not power up at all even after removing battery etc...the pc will not recognise it either!
Anything i can do without sending back to samsung/vodafone (the phone was rooted!)
Thanks in advance..ash
Trhow it in the water if you have insurance and hope they give you a new one
Sent from my GT-I9000 using XDA App
EDIT March 11, 2016: Finally found a solution and no data was lost!
See post #5.
(is there no way to indicate on the thread that this is solved? I don't know exactly how it works on this forum...)
---------------------------------------------------------------
Hi!
So I've posted my problem on another forum but didn't get any reply, and I just realized I might have more chances to get faster replies on here.
Well, to make it short, I've tried to root my mothers' Galaxy Tab 3 (GT P5210), and as I've already rooted several devices (including another Galaxy Tab) without any problem, I didn't bother saving all the data on it... I'm afraid this was a big error.
I decided to root because it was getting stuck sometimes because of too many things running at a time in the background, and it made the tablet unusable until I reboot it. I wanted to install Greenify and make it work alone so my mother doesn't have anything to worry about but play without the tablet getting stuck. But I needed to root to use Greenify at its best...
As I've rooted several phones before, I know rooting doesn't wipe any data, unlike flashing seems to do. So I wasn't afraid of doing it.
I've followed this tutorial after installing the drivers.
Everything seemed to work correctly, Odin did what it had to do and it succeeded.
Though, now I can't turn on the tablet anymore: if it's turned on and that I press and hold the Power button, the "Samsung Galaxy Tab 3" screen shows up. But it doesn't move, it just stays here and does nothing.
I can turn it off, and try again, but the result is the same.
On the Internet I've read that charging it to 100% could solve the problem, but it doesn't seem to do anything as it was plugged all night and it's the same.
Now I've tried all combinations of buttons, because it was said that a second solution was to wipe the cache partition. But the only combination that works is Volume Down + Power, which brings the Download mode I had to get through in order to run Odin.
I've found this tutorial on here, but I don't even know if the correct word for my situation is "brick". And like many things I've found on the net, the tutorials for unlocking the tablet are for the tablets that have been flashed. But this is not what I wanted to do and I hope this is not what I did. And it doesn't inform if I'll lose data or not... which I'm afraid of.
I made the error of not making any backup before starting the process... I seriously hope nothing is lost.
Is there a way I can restart the tablet correctly again, even if I have to unroot, without losing anything?
Thanks by advance!
(sorry for the double-post)
No one?
Please, at least give me a clue on what I should do, or if there's hope to get back the data from it.
Joey79100 said:
(sorry for the double-post)
No one?
Please, at least give me a clue on what I should do, or if there's hope to get back the data from it.
Click to expand...
Click to collapse
I don't know if you've lost data or if this method will wipe data, but it's what I used to root stock kitkat
Method
Also - I seem to remember that you should uncheck auto reboot, and after flashing is finished power off and back on
Good luck
Thank you for your answer.
The thing is that I've already gone through some steps of the tutorial I linked in the OP (until step 10 / step 11), and when the tablet was meant to reboot, it got stuck on the "Samsung Galaxy Tab 3" screen. I can turn it off and on, but it won't go further than this screen.
I can still bring up the Download Mode (by pressing Volume Down + Power), but there's no way to bring up anything else. Even the debug menu with Volume Up + Power (though I don't know if it was even available this way before trying to root). It will just load the boot screen and nothing more.
I'd try something with the Download Mode only if I can be sure that no data will be lost. If it may erase data, I prefer not doing it and to find a way to get it back before anything else.
Do you know if there's some way to access the memory?
Okay okay... I've struggled a long time with this problem, brought the tabled to a local repair shop but didn't find anything that couldn't risk any data loss... And finally I've found something, so I'll post my solution in case other people have the same problem.
Remember, I could only boot the tablet in Download mode. Every other button combination led me to the boot screen.
The problem was indeed the cache, that I needed to wipe, but without being able to access the Recovery mode there was no way to do it.
-------------------------------------
Solution:
First, I downloaded Odin 3.07 from somewhere else than from the link given in the tutorial (quick search on Google), because I had to untick Auto-reboot. Actually I'm not sure this is needed, but it worked for me with it unticked (while the version of Odin given in the tutorial doesn't let you untick it).
Then, download TWRP for P5210 (a quick search through Google led me to this ). Take out the .tar file from the .zip, but DON'T try to extract anything from the .tar file.
(basically, we'll "install" it onto the tablet using the same method as described in the tutorial)
Boot the tablet in Download Mode (Volume- and Power), choose Continue (Volume+ IF I remember correctly, but it's written anyway), then plug the tablet to your computer.
Run Odin, untick Auto-Reboot (as said before, not sure it's needed, but oh well, it worked...). Then click PDA, select the file you've downloaded (for me it was twrp-2.8.6.0-p5210.tar).
Then press Start, and wait (I waited approx. 2 minutes) until Odin displays "PASS!".
Now unplug the tablet, and turn it off.
Turn it on with Volume+ and Power, this time it will bring you to the TWRP menu (it asks to stay in Read-Only mode or not... choose no). Go to Wipe > Advanced Wipe, and tick Cache ONLY. "Swipe" to start the operation, wait, wait... then, once it's completed, press back until you go back to the main menu, press Reboot > System (then Swipe).
Now the tablet will boot normally. It won't be rooted, but at least it will work again, and fortunately, without any data loss.
You couldn't flash super user from TWRP?
I have the same issue, my Tab 3 is stuck on the Samsung logo.
And the Odin is stuck on the file mentioned above.
Can someone please help?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've been reading through dozens of "bricked" threads for the last day, trying to figure this out, as I've been rooting/flashing android since the Hero and have managed not to brick anything in all those years. This is an unlocked Pixel 2XL bought from Google Store.
I unlocked the bootloader probably a year ago. I'd been rooted at one point, but after installing a security update around September I ended up leaving it stock.
Picked up a Pixel 3 and wanted to sell the Pixel 2. Confirmed I was all stock everything, and locked the bootloader. When trying to reboot after locking, I now get the "Can't find valid operating system. The device will not start" error.
I can access the fastboot menu, and my device is detected with fastboot devices. However, when I try "fastboot flashing unlock" or "unlock_critical" I get:
"FAILED (remote: 'Flashing Unlock is not allowed')"
I've tried Deuce's script, same errors.
Saw a suggestion regarding switching to the other partition, this errors out as well due to device being locked.
Tried booting into recovery from the Fastboot screen; it just goes to the "Can't find valid operating system" error screen with the only option being press power to power off so apparently my recovery partition is wiped as well. Also tried booting from the TWRP recovery image, this errors out due to device being in Lock State.
I have tried multiple PC's, USB cables, and USB slots. All have the same issue. Confirmed that I was using latest Platform Tools from Google as well.
My assumption is that I missed something and my device was not fully stock when I re-locked the bootloader. Before I give up hope and throw myself at the mercy of Google, I just thought I'd throw this up here to see if I missed something in one of the threads or if someone has any other ideas. Thanks!
So many cases from relocking the bootloader, guess i just leave it unlock then., care to share with us the method you use to return to stock ? did you use the Deuce script ?
Unfortunately I did not use the Deuce script. I just factory reset, flashed the December factory image with ADB, and then locked the bootloader (also with ADB).
I have exactly the same problem; have you found any solution? And will Google accept the device if it's under warranty knowing that the device was once unlocked?
ASMstudent said:
...will Google accept the device if it's under warranty knowing that the device was once unlocked?
Click to expand...
Click to collapse
Yes. Google is rather lenient in that regard.
That's good news!
Do they require a proof of purchase or a warranty card because I don't have either of them.
Sent from my PLK using Tapatalk
ASMstudent said:
That's good news!
Do they require a proof of purchase or a warranty card because I don't have either of them.
Click to expand...
Click to collapse
No proof of purchase means Google is not obligated to help you. You'll need to talk to them. On a side note, run the IMEI through imeipro.net's LG IMEI search engine so you know when the phone was manufactured, as that may be useful information in dealing with Google.
I found out that this happen when I press volume up while the device Boots up.
First it says download mode then it goes to the second screen. On this state, the device is detected by the PC, but when I type adb or fastboot devices I don't get any connected device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my PLK using Tapatalk
ASMstudent said:
I found out that this happen when I press volume up while the device Boots up.
First it says download mode then it goes to the second screen. On this state, the device is detected by the PC, but when I type adb or fastboot devices I don't get any connected device.
Click to expand...
Click to collapse
If your wanting to get into bootloader mode, with the phone off, hold power + volume down until you get to the bootloader screen. Or, were you trying to do something else?
Badger50 said:
If your wanting to get into bootloader mode, with the phone off, hold power + volume down until you get to the bootloader screen. Or, were you trying to do something else?
Click to expand...
Click to collapse
I was playing around hoping for some thing to change. I searched around and found out that LG ( the original ODM of pixel 2 xl) has a way to unbrick using download mode ( accessed by pressing and holding power button+ volume up) which is similar to what is happening to me. The problem is that you can only flash KDZ updates with LG flash tool. This works for hard bricked devices when nothing else worked. I was thinking to connect the device in this way and update drivers using LG drivers instead of pixel's but still I can't get an update in kdz format.
ASMstudent said:
...but still I can't get an update in kdz format.
Click to expand...
Click to collapse
And you won't either. Google doesn't offer them, so you'll have to hope a developer creates one or one gets leaked by someone at Google.
Just installed LG mobile drivers and connected my device in download mode. In manage devices, it's now shown as an LG mobile connected, so theoretically it could work.
Sent from my PLK using Tapatalk
I downloaded a patched LGUP flash tool from LG v30 forums that could allow cross flashing between different variants and it detected my pixel 2 XL. Still it needs a kdz or tot file to flash, but when I chose boot.img from Google factory image, it gave me an error on the LGUP but also on my device which means there is a connection between my PC and my device which means this might actually work .View attachment 4719702
Sent from my PLK using Tapatalk
ASMstudent said:
I found out that this happen when I press volume up while the device Boots up.
First it says download mode then it goes to the second screen. On this state, the device is detected by the PC, but when I type adb or fastboot devices I don't get any connected device.View attachment 4718679View attachment 4718680
Sent from my PLK using Tapatalk
Click to expand...
Click to collapse
were you able to find a good solution to your problem, am in the same situation.?
Nope
I found out that this is EDL or Qualcomm emergency download mode and you need Google proprietary programmer firehouse file, blank flash files and rawprogram0.xml file; last two can be extracted from a working device. I contacted Google support forum and they told me that they wouldn't release these files to anyone as they may be used to find software vulnerabilities in the device. I contacted software repair center known for dealing with these problems, he told me that they have the programmer firehouse for the pixel 2xl ( not sure if they actually do or it's just a scam) but they would need time to extract the other needed files. I paid a sponsorship fee ( only 21$ ) and gave them 2-3 months, but they provided no updates so I requested a refund and sold the device as spare parts. EDL mode is theoretically your best bet to fix the device, but without the appropriate files ( which may never be available) it's useless.
You can look up EDL mode, QFIL, QPST tools and the store's name is aryktech.
ASMstudent said:
Nope
I found out that this is EDL or Qualcomm emergency download mode and you need Google proprietary programmer firehouse file, blank flash files and rawprogram0.xml file; last two can be extracted from a working device. I contacted Google support forum and they told me that they wouldn't release these files to anyone as they may be used to find software vulnerabilities in the device. I contacted software repair center known for dealing with these problems, he told me that they have the programmer firehouse for the pixel 2xl ( not sure if they actually do or it's just a scam) but they would need time to extract the other needed files. I paid a sponsorship fee ( only 21$ ) and gave them 2-3 months, but they provided no updates so I requested a refund and sold the device as spare parts. EDL mode is theoretically your best bet to fix the device, but without the appropriate files ( which may never be available) it's useless.
You can look up EDL mode, QFIL, QPST tools and the store's name is aryktech.
Click to expand...
Click to collapse
How sure its not your device that i bought of ebay?:laugh:
0x0null said:
How sure its not your device that i bought of ebay?[emoji23]
Click to expand...
Click to collapse
Lol
Actually I sold it locally in my country.
You can contact aryktech if they made any progress just don't pay upfront
Sent from my PLK using Tapatalk
Aiit.tnx
@ASMstudent or @0x0null - any other progress? Exact same situation with Taimen (Pixel 2 XL). Dunno if I should make this my month-long side project, or just chuck the phone.
SimFox3 said:
@ASMstudent or @0x0null - any other progress? Exact same situation with Taimen (Pixel 2 XL). Dunno if I should make this my month-long side project, or just chuck the phone.
Click to expand...
Click to collapse
Nah, i got a new board.
Hello guys,
I received the following unbrick tool from my supplier in Shenzhen - China and wanted to share it with you since I noticed that many people are desperate to fix their RM6 and swap it to EU.
The process is super easy:
1) Download & extract the following .zip
https://mega.nz/file/ntBSxDKa#h9vUPGoWVyqtyDYWYmSgz8bE1_vNimBMAqTp9csvv-w
2) Make sure all the drivers are installed correctly (Qualcomm, EDL etc...)
3) Open the MiTool application
4) in MiTool, select the folder images
5) Put your phone in EDL mode
6) Once connected, Click flash - the brushing process will start automatically.
7) Once done, force reset and Voilà!
There's an alternative as well: MultiportQLoader
I haven't tried it myself, feel free to try it and share the steps.
Im sorry if any details aren't clear, but I'm typing this while driving xD
Good luck and would appreciate a shout-out on insta @Out.Geeked ^^
THANK YOU SIR
To ask a dumb question, but is this only the 6 or for the pro as well?
Works for both
Thank you so much, it work after someone help me erase flash
Outgeeked.net said:
Works for both
Click to expand...
Click to collapse
Yeah I checked the model number against the box it came in and gave it a shot, now it shows the RM logo and then reboots to the bootloader lmao this phone legit hates me
*edit*
So I think either I'm doing something wrong or this phone is actually messed up. Checked the drivers, tried 2 other cables, all my USB ports and still all it does is briefly show the white "System Rebooting" screen and then the RM logo for about 20 seconds and then reboots to fastboot/bootloader.
MiFlash shows "couldn't find flash script" but otherwise looks like it goes through the reflash process completely but QLoader always fails with an error "Unknown chunk type cac2"
Does this unbrick method require the bl to be unlocked?
anyone lost their imei after doing this? hahahha
i did lost my imei, but manage to repair it but... it still doesnt detect mobile network idk what to do now lol
Nocturne Seigneur said:
anyone lost their imei after doing this? hahahha
i did lost my imei, but manage to repair it but... it still doesnt detect mobile network idk what to do now lol
Click to expand...
Click to collapse
Did you ever find a way to recover your IMEI? Turns out that I'm in the same situation as you with a lost IMEI
CyberWolf92 said:
Did you ever find a way to recover your IMEI? Turns out that I'm in the same situation as you with a lost IMEI
Click to expand...
Click to collapse
loool welcome to the club xD, I didn't found any solution yet, i will tell u once confirmed, for now i can write imei but mobile network still not functioning
Does it actually work?
According to the file name, it's EU V3.10.
I thought we should apply the NA/Asia version.
cannon3025 said:
Does it actually work?
According to the file name, it's EU V3.10.
I thought we should apply the NA/Asia version.
Click to expand...
Click to collapse
yes it does work, some ppl lose imei some not idk why, mine lose imei and cant connect to any mobile network right now T^T
after u unbrick it, u can flash via local update to v4.13 i did that working fine
Nocturne Seigneur said:
yes it does work, some ppl lose imei some not idk why, mine lose imei and cant connect to any mobile network right now T^T
after u unbrick it, u can flash via local update to v4.13 i did that working fine
Click to expand...
Click to collapse
After you update to V4.13, your phone still no IMEI right?
How about flashing it again?
cannon3025 said:
After you update to V4.13, your phone still no IMEI right?
How about flashing it again?
Click to expand...
Click to collapse
its gone, forever lol
i just gave my phone to someone else to fix this, if he can.
[Guide] Restore Lost IMEIs / Repair Network or Radio Issues
I accidentally restored TWRP backup of another Zuk Z2 phone on my new pgone and in this process over-wrote the EFS partition. This left me with a phone having no IMEI, no mac for Wifi and Bluetooth. Effectively No Network on phone. Worried, I...
forum.xda-developers.com
this maybe work, havent test it out
Since we have the partition layout & the correct firehose, it should actually be a good practice by anyone wanting to play with their phone (BL unlock, root, dev, etc) to first dump the critical partitions.
That way, you can always restore. Example: EFS, misc, persist, etc.
Thanks for your help
When I use MiFlash shows "couldn't find flash script"
Can you please help
My RM6pro restarting all time to fastboot mode after I tried to relock bootloader and oem
Now I need to solve this issue by using this tools
I am beginner
Thanks
Same issue for @CyberWolf92
Alaryani said:
Thanks for your help
When I use MiFlash shows "couldn't find flash script"
Can you please help
My RM6pro restarting all time to fastboot mode after I tried to relock bootloader and oem
Now I need to solve this issue by using this tools
I am beginner
Thanks
Click to expand...
Click to collapse
Select the images folder and then hit flash.
Mine is alive again, no more problems.
I think I know why a lot of people have probably bricked their device after flash from CN to Global. If you do a local update, let the device REboot until the end. After the restart it uses the update.zip again. I think a lot of people did a factory reset immediately after the reboot (like me in Recovery) and the system can no longer find the update.zip.
Therefore, let the update run through, reboot until you are back in the system. Then you can do a factory reset.
Outgeeked.net said:
Select the images folder and then hit flash.
Click to expand...
Click to collapse
When I selected images folder shows "couldn't find flash script"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And when I go to edl mode my phone disappeard from list devices in MiFlash.
but still showing in driver manger
What driver needs for this issue "Make sure all the drivers are installed correctly (Qualcomm, EDL etc...)" what else I need?
also when i did it on fastboot mode i face this massge
Alaryani said:
When I selected images folder shows "couldn't find flash script"
View attachment 5329645
And when I go to edl mode my phone disappeard from list devices in MiFlash.
View attachment 5329643
but still showing in driver manger
View attachment 5329647
What driver needs for this issue "Make sure all the drivers are installed correctly (Qualcomm, EDL etc...)" what else I need?
also when i did it on fastboot mode i face this massge
View attachment 5329661
Click to expand...
Click to collapse
you must be in edload mode not fastboot
Hello,
I got on yard sale Galaxy Tab 3 but it's displaying message on boot `This device managed by your organization`.
I tried factory wipe/Reset from boot menu but it reboots back to being locked. How do I unlock it for my use?
You don't. Have the organization that locked it access it.
blackhawk said:
You don't. Have the organization that locked it access it.
Click to expand...
Click to collapse
That's the point of XDA - doing something you are not allowed to do. I'm pretty sure there is a way to completly wipe it. It's not Apple product and I expect there is some clever hackery can be done with Android/Samsung to revert back to factory with no MDM software.
artisticcheese said:
That's the point of XDA - doing something you are not allowed to do. I'm pretty sure there is a way to completly wipe it. It's not Apple product and I expect there is some clever hackery can be done with Android/Samsung to revert back to factory with no MDM software.
Click to expand...
Click to collapse
That is not the point. Many things such as change IMEI’s are disallowed in Xda. But it anwser your question, can you enter the system, or are you stuck on the managed screen?
Tab boots and asks tells device is managed by company and asks for password. I can get into bootloader as well but factory reset seems to be disallowed. I did flash ROM, rooted and stuff like that years back so I'm familiar with process of doing something one shall not be doing but I'm wondering if it's possible with tab in current setup
What do you mean disallowed? Boot to recovery and reset form there? What happened if you try?
If that doesn’t work try flashing stock
Arealhooman said:
What do you mean disallowed? Boot to recovery and reset form there? What happened if you try?
Click to expand...
Click to collapse
MDM blocks reset.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
artisticcheese said:
That's the point of XDA - doing something you are not allowed to do. I'm pretty sure there is a way to completly wipe it. It's not Apple product and I expect there is some clever hackery can be done with Android/Samsung to revert back to factory with no MDM software.
Click to expand...
Click to collapse
Don't get XDA in legal trouble. This isn't the dark web.
The reason it's lock is because the owner wants it locked. How thoughtless of them.
He legally purchased it. You may want to try to return it to the seller.
I actually have somewhat the same problem, however it is MY tablet. Samsung Tab 3, was setting tablet up for first time and also enrolled in new MDM platform with heavy restrictions. Tablet soft-bricked while applying may initial OS updates. It now boots to the black samsung logo and no further. Oddly, when it booted, it was chedking into MDM, but none of the policy changes to reduce restrictions were being received. I disenrolled it but to no avail.
I can enter Recovery mode, but factory reset is not available. I can enter ADB sideload mode and ADB sees the device, but the sideload of the stock recovery errors with failed signature verification. Same thing with an SD card load. I see the option to reboot to bootloader in Recovery Mode, but when I choose it, it does a "normal" boot and gets to the black samsung logo. The key combo to enter downlod / odin mode does not work either - the tablet just enters a reboot loop while I am holding the buttons. The only thing I have not reied is different stock ZIP files from the SD card, which I will continue to try. I have also tried all other recovery options - optimize apps, wipe cache partition, etc. Any ideas appreciated.
kgilderhus said:
I actually have somewhat the same problem, however it is MY tablet. Samsung Tab 3, was setting tablet up for first time and also enrolled in new MDM platform with heavy restrictions. Tablet soft-bricked while applying may initial OS updates. It now boots to the black samsung logo and no further. Oddly, when it booted, it was chedking into MDM, but none of the policy changes to reduce restrictions were being received. I disenrolled it but to no avail.
I can enter Recovery mode, but factory reset is not available. I can enter ADB sideload mode and ADB sees the device, but the sideload of the stock recovery errors with failed signature verification. Same thing with an SD card load. I see the option to reboot to bootloader in Recovery Mode, but when I choose it, it does a "normal" boot and gets to the black samsung logo. The key combo to enter downlod / odin mode does not work either - the tablet just enters a reboot loop while I am holding the buttons. The only thing I have not reied is different stock ZIP files from the SD card, which I will continue to try. I have also tried all other recovery options - optimize apps, wipe cache partition, etc. Any ideas appreciated.
Click to expand...
Click to collapse
So you can’t factory reset, even from recovery? Did you try to disable Knox packages using adb?
kgilderhus said:
I actually have somewhat the same problem, however it is MY tablet. Samsung Tab 3, was setting tablet up for first time and also enrolled in new MDM platform with heavy restrictions. Tablet soft-bricked while applying may initial OS updates. It now boots to the black samsung logo and no further. Oddly, when it booted, it was chedking into MDM, but none of the policy changes to reduce restrictions were being received. I disenrolled it but to no avail.
I can enter Recovery mode, but factory reset is not available. I can enter ADB sideload mode and ADB sees the device, but the sideload of the stock recovery errors with failed signature verification. Same thing with an SD card load. I see the option to reboot to bootloader in Recovery Mode, but when I choose it, it does a "normal" boot and gets to the black samsung logo. The key combo to enter downlod / odin mode does not work either - the tablet just enters a reboot loop while I am holding the buttons. The only thing I have not reied is different stock ZIP files from the SD card, which I will continue to try. I have also tried all other recovery options - optimize apps, wipe cache partition, etc. Any ideas appreciated.
Click to expand...
Click to collapse
Welcome to XDA.
Why would you do that?! That's not a normal setup option...
Contact Samsung tech support if you purchased the device new and you're the legal owner. They may help you...
Arealhooman said:
So you can’t factory reset, even from recovery? Did you try to disable Knox packages using adb?
Click to expand...
Click to collapse
Correct, factory reset is not available - removed as part of the MDM policy. I didn;t know about disabling Know, but tried tried adb shell command and retutrned error: closed. The device is recognized in ADB in sideload.