Develop Bugs

GT-P5210 stuck on boot screen after trying to root

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"
}

Realme UI 2.0 update issue

Hello everyone. Hope you all are doing well.
I had updated my Realme 6 Pro from Android 10, version RMX2061_11.A.49 to the Android 11 update i.e. Realme UI 2.0, version RMX2061_11.C.15. The thing is, after optimizing apps during the first boot, the phone is stuck at the lock screen and the touchscreen is not responding.
Video of the issue is here: Realme 6 pro UI 2.0 issue
Kindly do help on what to do next. Doing a reset is the last step I want to undertake, since I forgot to take a backup.. Will flashing the Realme UI 2.0 update via stock recovery help? Any help and suggestions would be much appreciated.
Thank you.

soham93 said:
Hello everyone. Hope you all are doing well.
I had updated my Realme 6 Pro from Android 10, version RMX2061_11.A.49 to the Android 11 update i.e. Realme UI 2.0, version RMX2061_11.C.15. The thing is, after optimizing apps during the first boot, the phone is stuck at the lock screen and the touchscreen is not responding.
Video of the issue is here: Realme 6 pro UI 2.0 issue
Kindly do help on what to do next. Doing a reset is the last step I want to undertake, since I forgot to take a backup.. Will flashing the Realme UI 2.0 update via stock recovery help? Any help and suggestions would be much appreciated.
Thank you.
Click to expand...
Click to collapse

Hello soham,
I have the exactly same problem since the yesterday update with my Realme X2 Pro.
If you find a solution please let me know
...at the moment i have no idea.

yeah bro same with mine,
but we have another choice,
drain the battery and let the mobile turn off
after that go to the recovery mode and wipe your data.
or else we need to update the software in the recovery mode which is not arrived yet.

Press the power off and volume up button for about 7 sec and it should power off. when u turn it on press the power off and volume down button for 10 sec and you will boot to recovery mode. After that, u will have to format your data which will cause ur data to be removed.

I dont think there is any other way to fix this. Unless you have your data back up in the cloud. Maybe you can also take out the storage card from your phone which is difficult and then back up your data from a pc or something.

I thought of flashing the ROM, but it was not available anywhere. So I ended up performing a factory reset to boot the phone. There seems to be no other solution for this.

I have no backup..so i wait for the next update..
Wipe data doesnt work for me and i do not format the device.

I have the exact same issue. This problem generally applies to all Realme devices upgraded to Realme UI 2.0. The root cause is the disabling of com.coloros.weather.service package, usually done during debloating through adb. Further analysis I have done is explained on my thread.
Quick fixes you have now:
If you have adb enabled and ticked "Always allow from this computer" on the prompt below when your phone is still working, you can connect your phone in the blinking state and issue the following command: adb shell cmd pm enable com.coloros.weather.service. Then, reboot your phone. It will work normally on Realme UI 2.0.
{
"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"
}
Click to expand...
Click to collapse
[DATA LOSS] Download this ozip and put it on an SD card. A used SD card works fine as long as it isn't encrypted and has enough free space. Make sure the file name matches your device model. Enter realme UI Recovery (on Realme 7, you press VolumeDown + Power, which might differ for each device) and choose 'Install from Storage'. Enter your device password, select 'SD Card', and pick the ozip you have downloaded. The phone will wipe itself, and you end up with a working phone on Realme UI 1.0.
[DATA LOSS] If your phone is still on warranty period, go to any Realme Service Centre, and use the following statement; the service centre will either replace your phone free of charge or if they don't have any replacements in stock, put you on a waitlist and calls you back once the replacement device is available.
I am updating my device to Realme UI 2.0 when suddenly the device turns off and reboot itself. Now, this device won't allow me to unlock it.
Click to expand...
Click to collapse
Other possible, longer-term solutions are:
Wait for Realme to realize this problem and issue an OTA update. The fix is easy on their side; just add a simple one line on the after-flash script of the next OTA/ozip to enable the weather services package:
Code:
pm enable com.coloros.weather.service
The command pm enable would do nothing if a package is already enabled. However, Realme might not realise this problem. Even if they recognise it, Realme might think it is not their own problem (debloating = user's fault?). If they release this fix, we can just boot into recovery and install it. Realme has support for OTA updates on their recovery. Just enter the device password and then the WiFi password.
I have tried exploring the Realme forums, albeit not directly filing a bug report. I found many, many users experiencing a similar issue as ourselves. Most of it was responded to by Realme representatives in this fashion: "enter recovery mode by pressing this and this, and then choose to wipe data. This will reset your phone to its working state." This is not acceptable for me since a functioning phone is lower on my priority than keeping my data (albeit in limbo).
Suppose your device has MediaTek SoC, and you have not set up any password/PIN/pattern on your device. In that case, you could possibly extract the userdata partition, exploiting the Boot ROM (BROM) exploit by Dinolek and k4y0z with the SP Flash Tool. You first need to find a specific scatter file for your device; however, if none is available, you could generate one from a preloader dump using a tool named Wwr MTK.
If you have set up a password, then this would be infeasible, apparently, since not only the device password is needed to decrypt it, but also some salt stored on the SoC itself; hence this thread highly suggests swapping SoC and eMMC to another working exact same phone (cannibalize another phone).
However, even after you swapped the SoC to a new phone and write your userdata partition on it, you faced a new dilemma:
previously on the old phone, you have a non-working software config, but the decryption key to the userdata is the same as the decryption key to the other partitions
now on the new phone, you have a working software config. The decryption key is available on SoC, but the other partitions are unreadable to the bootloader. They are either unencrypted or encrypted with a different key.
I have not been able to solve the above dilemma.
Hence, my current objective is to nag Realme and invite others to also nag them to implement that simple one line on their OTA update.

any updates? today i update realme 6 to realme ui 2.0 it broke my phone... because of this weather crap usb debugging not working for me...

I too ran into this issue just now. Thanks @said1219 for your suggestion. A single change in my case. I haven't disabled the app, I have uninstalled it. So I ran
adb shell cmd package install-existing com.coloros.weather.service
This fixed the issue. This didn't require restart.
I use Realme C3. After this update again there is a new update of 280MB released on Dec 9, 2021, specifies system optimization.
It doesn't make any issue after this.

vigneshrajarr said:
I too ran into this issue just now. Thanks @said1219 for your suggestion. A single change in my case. I haven't disabled the app, I have uninstalled it. So I ran
adb shell cmd package install-existing com.coloros.weather.service
This fixed the issue. This didn't require restart.
I use Realme C3. After this update again there is a new update of 280MB released on Dec 9, 2021, specifies system optimization.
It doesn't make any issue after this.
Click to expand...
Click to collapse
I have a question, how did you reinstall the weathersystem even if your phone is flickering? Did you do it on power on or in recovery mode? That is an adb fastboot right?? Does your phone prompt you and asks to "file transfer" and "charging only"? Because that's the only last thing I have to do, let my pc run adb fastboot to turn it on

Quasar.Illumia said:
I have a question, how did you reinstall the weathersystem even if your phone is flickering? Did you do it on power on or in recovery mode? That is an adb fastboot right?? Does your phone prompt you and asks to "file transfer" and "charging only"? Because that's the only last thing I have to do, let my pc run adb fastboot to turn it on
Click to expand...
Click to collapse
You let the phone complete boot and enter the flicker-state. Then run "adb devices" as per your photo in my thread.
The following step can be done either on normal boot, fastboot, or recovery mode:
If no device is found, it is likely that USB debugging is disabled on your device.
If your device is found, but it says 'unauthorized', it means that you didn't tick "Always allow connections from this device" or a long time has lapsed since you've connected your PC's ADB to your phone.
If your device is found and it says 'device' on the right of the serial number, you're good to go.
Except for the last scenario, you're possibly getting back to square one.
The following step must be done after the phone completed normal boot, recognized your PC, and enter the flicker-state:
If you disabled the weather package, run
Code:
adb shell cmd pm enable com.coloros.weather.service
If you uninstalled the weather package, run
Code:
adb shell cmd package install-existing com.coloros.weather.service
Your phone will immediately stop flickering and you can enter your password normally. And, as per my reply in my thread, "Allow charging only" could prevent you from accessing ADB.

I thought it wasn't working when I entered adb shell yesterday. Thank you UwU it is working now
said1219 said:
You let the phone complete boot and enter the flicker-state. Then run "adb devices" as per your photo in my thread.
The following step can be done either on normal boot, fastboot, or recovery mode:
If no device is found, it is likely that USB debugging is disabled on your device.
If your device is found, but it says 'unauthorized', it means that you didn't tick "Always allow connections from this device" or a long time has lapsed since you've connected your PC's ADB to your phone.
If your device is found and it says 'device' on the right of the serial number, you're good to go.
Except for the last scenario, you're possibly getting back to square one.
The following step must be done after the phone completed normal boot, recognized your PC, and enter the flicker-state:
If you disabled the weather package, run
Code:
adb shell cmd pm enable com.coloros.weather.service
If you uninstalled the weather package, run
Code:
adb shell cmd package install-existing com.coloros.weather.service
Your phone will immediately stop flickering and you can enter your password normally. And, as per my reply in my thread, "Allow charging only" could prevent you from accessing ADB.
Click to expand...
Click to collapse

Well then, another year has gone by
No changes so far? I noticed new Realme UI updates have been launched in the meantime. Has anyone tried them out yet on the blocked phones?
As you've recommended @said1219 , I've kept my battery in good condition and still hope that this problem can get solved in the future...
However, since this issue started, by principle I've refused to buy any new Realme product...

Question is it possible to backup my phone with my current issue?

i need help making a backup of my phone, my screen is black so i can't see anything. my pc does recognizes it when connected.
p.s. haven't rooted my phone

testask123 said:
i need help making a backup of my phone, my screen is black so i can't see anything. my pc does recognizes it when connected.
p.s. haven't rooted my phone
Click to expand...
Click to collapse
does the phone still have touch working despite screen is black? Touch is required because you will need to enable Developer Options and then USB debugging. Afterwards, you should be able to control your device via scrcpy using a computer. Or, make file backups by leveraging ADB command "adb pull", though this would already be possible when you connect the device and choose "File transfer" on a window that appears.

TechnoSparks said:
does the phone still have touch working despite screen is black? Touch is required because you will need to enable Developer Options and then USB debugging. Afterwards, you should be able to control your device via scrcpy using a computer. Or, make file backups by leveraging ADB command "adb pull", though this would already be possible when you connect the device and choose "File transfer" on a window that appears.
Click to expand...
Click to collapse
i can't tell, i don't here or feel vibration.
if i can't access debug, can i not backup?
is there no program that can make one?

testask123 said:
i can't tell, i don't here or feel vibration.
if i can't access debug, can i not backup?
is there no program that can make one?
Click to expand...
Click to collapse
I have an idea but i may have to test first.
Is your phone stock or have you unlocked the bootloader?

TechnoSparks said:
I have an idea but i may have to test first.
Is your phone stock or have you unlocked the bootloader?
Click to expand...
Click to collapse
bootloader is not unlocked

testask123 said:
bootloader is not unlocked
Click to expand...
Click to collapse
Is the warranty still valid? If YES, then i cannot help you, because unlocking the bootloader may render the warranty void (but i am not sure, you may confirm with relevant Xiaomi service centres).
ignore everything. this is because there is nothing we can do without the authorization from adb, or choosing "file transfer" during USB connection when in the OS
i am sorry
edit: also because i totally forgot that unlocking the BL will definitely wipe the device, which defeats the purpose of this thread!

TechnoSparks said:
Is the warranty still valid? If YES, then i cannot help you, because unlocking the bootloader may render the warranty void (but i am not sure, you may confirm with relevant Xiaomi service centres).
ignore everything. this is because there is nothing we can do without the authorization from adb, or choosing "file transfer" during USB connection when in the OS
i am sorry
Click to expand...
Click to collapse
is there no trustworthy program that could back it up?

testask123 said:
is there no trustworthy program that could back it up?
Click to expand...
Click to collapse
With what i knew so far with [AOSP] Android, no, because there needs to be a user confirmation on the screen. I suppose maybe Xiaomi have some proper backup tools? (I guess)

Oh yeah, maybe an external display could work. Please wait while I try to gather some limited information

After some quick googling @testask123 , the Poco F3 does not support HDMI-out through the usb-c port. This looks to me like a dead end, and we won't be able to backup the data from the phone. Because as previously mentioned, in order to backup any meaningful data, the user have to interact with the screen for confirmations.
I actually under the assumption that you want to backup the device before sending it for warranty replacement. I also assume that your screen is broken in some way, but the device is functional, for example, you can receive calls. If you are not going to warranty claim the phone, then you may replace the screen at repair shops without needing to format your data at all, thus giving you access to everything on your device once everything is up and running.
Final question, does the touch screen still work despite the screen is black?

Did you have a recovery on it? Did it have ADB enabled on it? Can you get to recovery?
If you were unlocked and especially if you had Magisk'ed it we could easily mod the boot image to enable ADB.

Renate said:
Did you have a recovery on it? Did it have ADB enabled on it? Can you get to recovery?
If you were unlocked and especially if you had Magisk'ed it we could easily mod the boot image to enable ADB.
Click to expand...
Click to collapse
Could you go into details as to how to modify boot.img to enable adb?
I tried searching a bit but nothing came up

It's mostly changing prop.default in the image, maybe add something to start adbd earlier in the boot process.
Or making a rooted recovery.
But this is all based on being able to flash something, either in fastboot or at a lower level with EDL/MSM.

Renate said:
It's mostly changing prop.default in the image, maybe add something to start adbd earlier in the boot process.
Or making a rooted recovery.
But this is all based on being able to flash something, either in fastboot or at a lower level with EDL/MSM.
Click to expand...
Click to collapse
Ahhh I see , but why boot.img? It's rather difficult to modify for you gotta unpack ramdisk and all? ( I tried doing this long time ago but got stuck on how to repack properly x: )
System.img / vendor.img should be better targets for u can unsparse them ( make rw ) on PC and easily edit .prop files
It's a rly good idea

It's easier to pack something if you never unpack it.
imgutil.exe in my sig lets you modify boot images without taking it all apart.
Warning: Android moves on and many busy bees are working to make our lives more difficult.
If you have problem with imgutil.exe contact me about it.
Code:
C:\>imgutil.exe /v /x boot.img prop.default
C:\>my-fave-editor.exe prop.default
C:\>imgutil.exe /v /r boot.img prop.default
Just don't use some ignorant Windows editor like "Notepad" that uses \r\n.
I like Notepad++.
Also, with a boot image you can try booting it without flashing it.

TechnoSparks said:
After some quick googling @testask123 , the Poco F3 does not support HDMI-out through the usb-c port. This looks to me like a dead end, and we won't be able to backup the data from the phone. Because as previously mentioned, in order to backup any meaningful data, the user have to interact with the screen for confirmations.
I actually under the assumption that you want to backup the device before sending it for warranty replacement. I also assume that your screen is broken in some way, but the device is functional, for example, you can receive calls. If you are not going to warranty claim the phone, then you may replace the screen at repair shops without needing to format your data at all, thus giving you access to everything on your device once everything is up and running.
Final question, does the touch screen still work despite the screen is black?
Click to expand...
Click to collapse
it's hard to tell, maybe i should try to see if i can pull it of, but don't know the exact position of the usb setting in the dropmenu.
if someone could provide some screenshot, it might give me an idea where to tap.

Renate said:
Did you have a recovery on it? Did it have ADB enabled on it? Can you get to recovery?
If you were unlocked and especially if you had Magisk'ed it we could easily mod the boot image to enable ADB.
Click to expand...
Click to collapse
i remember turning on wifi debugging, but dont know if that's still the case or even useful

testask123 said:
i remember turning on wifi debugging, but dont know if that's still the case or even useful
Click to expand...
Click to collapse
Well, try to connect. Is WiFi on? Do you know the IP address? Can you get it from the router? Can you ping it?
Code:
C:\>adb connect 192.168.1.?
("?" is not literally a question mark, put a small number in there.)

Renate said:
Well, try to connect. Is WiFi on? Do you know the IP address? Can you get it from the router? Can you ping it?
Code:
C:\>adb connect 192.168.1.?
("?" is not literally a question mark, put a small number in there.)
Click to expand...
Click to collapse
the ip from the phone?
sorry i'm not so knowledgeable about these things and wanted to make sure

{
"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"
}
Yeah, the IP of your phone.
If you're on your own router you can log in and see if your phone is there and what IP.
Now you know that my cheap Walmart tablet is on (local) IP 192.168.1.4

FRP Locked!

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

Question Phone stuck in a boot loop please help :(

Hello everyone good day.
Sadly my phone Samsung galaxy A22 has stumbled into a boot loop been happening for couple days it started when I put the phone on charge and heard it vibrating to which It was constantly rebooting over and over as soon as the Home Screen loads after a second it just reboots I tried to do a reset using power + volume down and no luck also tried wipe cache partion in the recover menu and repair apps but no luck tried searching YouTube for fixes and also called a phone repair shop and said it’s a tough one as I want to keep my data meaning I can’t do a factory reset as I have a lot of stuff I need on the phone so I am reaching out here as a last resort it would make my day if someone could help thanks.
Note: after many restarts the phone managed to come on a couple of times to which after entering my pin a pop up would happen saying “ serious software issue detected check for update “ if i click check the message goes away then it says android starting but fails to start up after 30 seconds to a minute it just re boots again I had some hope as it happened a few times it allowed me to put my pin in but on the android starting screen it would never get past and eventually reboot again I haven’t updated the phone for a while so is it also possible to update from download mode without losing my data or do I need some room for that??

Read I could try safe mode unfortunately that didn’t work either

Try downloading your phones firmware on samfw and installing it with the HOME_CSC, not CSC without HOME!!!

HeroGamer007 said:
Try downloading your phones firmware on samfw and installing it with the HOME_CSC, not CSC without HOME!!!
Click to expand...
Click to collapse
Hey how can this be done? Never done this before any guides you could link me to?

ThePhoneGuyy1 said:
Hey how can this be done? Never done this before any guides you could link me to?
Click to expand...
Click to collapse
IF SOMETHING FAILS DO NOT PROCEED TO AVOID ANY FURTHER DAMAGES!!!
I AM NOT RESPONSIBLE FOR ANY DAMAGES DO TO YOUR PHONE!!!
1. Power off your Phone
2. Now hold the volume up + down button and while doing that plug in a usb cable that is connected to your pc
3. You should see some kind of blue screen, press volume up and it will show "Downloading..."
4. Now Download Odin3, unzip it and Open the EXE on your PC (Click OK on the Warning)
5. You should see COM0 (the 0 can be any other number) under the ID:COM label, if it doesnt appear check your USB connection
6. Download your Device's Firmware:
go to SamFW.com and search for your model on the big Search Bar, if you don't know if its the F or M variant check the packaging, it should be on there. then Click on the Country you're in (or the Country your phone is from) and scroll down until you see this section:
{
"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"
}
Click on the Most-Top Version and select "Download on Browser" (you might need to login with google).
7. after that you should have 5 files starting with AP_, BL_, CP_, CSC_ and HOME_CSC
8. go into Odin and click "BL", then select the "BL_" file, do that for BL, AP and CP
9. now select the "HOME_CSC_" file on the "CSC" button, make sure its the HOME_CSC File!!!
10. after you made 10 time sure its the HOME_CSC file click start and pray
11. after the whole process your device should reboot and work.

HeroGamer007 said:
IF SOMETHING FAILS DO NOT PROCEED TO AVOID ANY FURTHER DAMAGES!!!
I AM NOT RESPONSIBLE FOR ANY DAMAGES DO TO YOUR PHONE!!!
1. Power off your Phone
2. Now hold the volume up + down button and while doing that plug in a usb cable that is connected to your pc
3. You should see some kind of blue screen, press volume up and it will show "Downloading..."
4. Now Download Odin3, unzip it and Open the EXE on your PC (Click OK on the Warning)
5. You should see COM0 (the 0 can be any other number) under the ID:COM label, if it doesnt appear check your USB connection
6. Download your Device's Firmware:
go to SamFW.com and search for your model on the big Search Bar, if you don't know if its the F or M variant check the packaging, it should be on there. then Click on the Country you're in (or the Country your phone is from) and scroll down until you see this section: View attachment 5891443
Click on the Most-Top Version and select "Download on Browser" (you might need to login with google).
7. after that you should have 5 files starting with AP_, BL_, CP_, CSC_ and HOME_CSC
8. go into Odin and click "BL", then select the "BL_" file, do that for BL, AP and CP
9. now select the "HOME_CSC_" file on the "CSC" button, make sure its the HOME_CSC File!!!
10. after you made 10 time sure its the HOME_CSC file click start and pray
11. after the whole process your device should reboot and work.
Click to expand...
Click to collapse
I’ll make sure to give it a good read I appreciate that hopefully this can fix for good quick question before i proceed do I need enough storage for this to update because I remember it being almost full if that’s the case is this possible by inserting an SD card without losing data? Just wanted to check before I proceed as my storage was close to being full

ThePhoneGuyy1 said:
I’ll make sure to give it a good read I appreciate that hopefully this can fix for good quick question before i proceed do I need enough storage for this to update because I remember it being almost full if that’s the case is this possible by inserting an SD card without losing data? Just wanted to check before I proceed as my storage was close to being full
Click to expand...
Click to collapse
It shouldn't need storage, it rewrites the system files and does not just "adds" them, so it should be at max 1-5 hundred MB bigger

HeroGamer007 said:
It shouldn't need storage, it rewrites the system files and does not just "adds" them, so it should be at max 1-5 hundred MB bigger
Click to expand...
Click to collapse
Perfect thank you so much will give this a try soon will update you what happens really appreciate you taking the time

ThePhoneGuyy1 said:
Perfect thank you so much will give this a try soon will update you what happens really appreciate you taking the time
Click to expand...
Click to collapse
Oh also to check the Country from which your phone is (you need to select that when downloading firmware) you can apparently use recovery mode, go into recovery mode (volume up + power while being plugged into a pc) and check if it says something with CSC-Code on the bottom, the 3-digit code after that is the Country Code which you will need to download.

T0stbrot said:
Oh also to check the Country from which your phone is (you need to select that when downloading firmware) you can apparently use recovery mode, go into recovery mode (volume up + power while being plugged into a pc) and check if it says something with CSC-Code on the bottom, the 3-digit code after that is the Country Code which you will need to download.
Click to expand...
Click to collapse
Sadly I haven’t been able to get this to fix used Odin and downloaded correct version for my model and csc code Odin said pass but phone still in boot loop

ThePhoneGuyy1 said:
Sadly I haven’t been able to get this to fix used Odin and downloaded correct version for my model and csc code Odin said pass but phone still in boot loop
Click to expand...
Click to collapse
I seen a video of someone using Odin once done there phone rebooted and showed a pop up saying updating apps etc along those lines but for me it just rebooted after Odin showed pass then bootloop again and a menu saying phone couldn’t start properly and get the same message “ serious software issue check for update “

ThePhoneGuyy1 said:
I seen a video of someone using Odin once done there phone rebooted and showed a pop up saying updating apps etc along those lines but for me it just rebooted after Odin showed pass then bootloop again and a menu saying phone couldn’t start properly and get the same message “ serious software issue check for update “
Click to expand...
Click to collapse
Try going into recovery maybe and deleting the cache and repair apps

T0stbrot said:
Try going into recovery maybe and deleting the cache and repair apps
Click to expand...
Click to collapse
Is that wipe cache partion? If so sadly not work for me and repair apps no fix but upon some research I’ve read it’s possible the storage can cause a bootloop also? Not sure if true but my phone was literally almost full as unfortunately didn’t make some room in time it seems this is most likely the reason as before bootloop I never installed any updates or did anything just simply put the phone on charge then it bootloop I’ve read that because there is almost no storage the phone just can’t boot up properly? No idea tbh but seems most reasonable as of now :/

ThePhoneGuyy1 said:
Is that wipe cache partion? If so sadly not work for me and repair apps no fix but upon some research I’ve read it’s possible the storage can cause a bootloop also? Not sure if true but my phone was literally almost full as unfortunately didn’t make some room in time it seems this is most likely the reason as before bootloop I never installed any updates or did anything just simply put the phone on charge then it bootloop I’ve read that because there is almost no storage the phone just can’t boot up properly? No idea tbh but seems most reasonable as of now :/
Click to expand...
Click to collapse
Also whilst my phone was bootlooping I got a menu similar to recovery menu saying android failed and a few options I believe was
1) try again
2) wipe app data
3) power off
Also a message saying if you don’t want to lose any data then it should be taken to a technician however one of the places I called said there is not much they can do as I wanna keep my data :/

Does it say wipe all data or wipe app data?

T0stbrot said:
Does it say wipe all data or wipe app data?
Click to expand...
Click to collapse
Wipe app data if I remember right it said about wiping the data of apps and configuration so this has also lead me to thinking it could be an internal storage also no idea as phone says there is a serious software issue it’s been a nightmare hopefully fix eventually just worried about my data I believe wipe app data will keep photos and videos safe but it would log out all my emails and wipe all my apps also? :/

ThePhoneGuyy1 said:
Wipe app data if I remember right it said about wiping the data of apps and configuration so this has also lead me to thinking it could be an internal storage also no idea as phone says there is a serious software issue it’s been a nightmare hopefully fix eventually just worried about my data I believe wipe app data will keep photos and videos safe but it would log out all my emails and wipe all my apps also? :/
Click to expand...
Click to collapse
Yeah it will delete all app data, so for example your google login or email login, it should keep your photos tho as that is not app data

T0stbrot said:
Yeah it will delete all app data, so for example your google login or email login, it should keep your photos tho as that is not app data
Click to expand...
Click to collapse
Hmm do you think this is pretty much the last resort for me to try if I can keep pics and videos I guess that’s a bonus just would have to pray it does let me boot my phone up and that I can regain access to emails and other stuff via logins not all wrote down so I guess at this point with nothing I’ve tried working seems one of the last options unless there is other ways to extract data whilst phone is in bootloop but haven’t found many also

Did you setup any 2FA Authenticator apps that aren't synced with a cloud? That would be pretty dumb and you probably won't be able to login except you saved the backup codes. But otherwise if it really only deletes app data it should be fine, and as long as you have access to your email you should be able to reset all your passwords.

Do you can share your phone recovery mode picture with download mode