[HELP] Odin stucks at "Get PIT for mapping.." - Galaxy Note II Q&A, Help & Troubleshooting

Hi guys,
My Note II (with Cyanogen mode) was resetting itself. And Today It reset again, then, my entire settings are gone. (even I couldnt open notification bar. Apps etc. were working) . Because of that, from settings, Ive tried factory reset. But again another problem occured and it stuck at deleting screen. Each 10-15 minutes, it resets and always the same erasing screen.
The same with this screen:
{
"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 then I used Odin for clear installation. But when the process is done, phone started to open in always Download mode (without upper left odin mode info texts) (even with normal power button or recovery mode buttons)
Odin mode info texts only can be seen with download mode buttons (power, volume-down, menu)
And after that problem I tried again. And Odin started to give me "There is no Pit Partition" error. I used couple of pit file that I can find on Internet but this time, It stucks at "Get PIT for mapping.."
I tried Kies but it couldnt recognise the device. I use samm's firmwares and also 4-files rom. (noone did work)
I tried with different version of Odin in all USB ports of two computers.
additional detail: I couldnt remember If the USB debugging is open or not when phone is broken
ODIN MODE
PRODUCT NAME: GT-N7100 (Yes There is a product name!)
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
KNOX WARRANT VOID: 1
AP SWREV: A2
Odin Stuck Screen:
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
Click to expand...
Click to collapse
Thank you in advance!

Have you tried different USB cables and USB computer ports?

audit13 said:
Have you tried different USB cables and USB computer ports?
Click to expand...
Click to collapse
I've tried with 3 computers and 2 cables also :crying:

Did you try with the original Samsung cable? I have flashed a few Samsung s4 phones and always needed an original Samsung cable in order to get Odin to read the partition information from the phone.

audit13 said:
Did you try with the original Samsung cable? I have flashed a few Samsung s4 phones and always needed an original Samsung cable in order to get Odin to read the partition information from the phone.
Click to expand...
Click to collapse
I guess It was not the original one :/ when I find an original, I will try

Related

[Q] My Lovely Arc 'Bricked'? Stuck at Sony Logo

Please don't yell at me for using the 'search' thing....everything directs to "You've gotta flash your phone" blah...but the PC doesn't even detect the Arc.
So. I just rooted the phone a couple of days ago, and I'm pretty noob-ish at this whole thing, I've got no idea what I'm doing XD
So, what's happened is I flashed the Xperia Ultimate HD 2.0 thing onto the Arc, and then felt like changing stuff so...I did a very stupid, stupid, stupid beyond stupid thing and installed another ROM (via the CWM menu thing on the phone) without factory resetting etc...
Then I rebooted the phone, and now it's stuck at the Sony logo ahhahaha
The PC doesn't seem to detect the phone (or maybe there's a way it will?)
I'm screwed, aren't I? Please help the helpless noob? :3 I'll give you a free imaginary bag of chocolate home-made cookies
well what you saw about 'flash your phone' is actually correct Download flashtool, download a rootable stock ics rom, and flash it lol. Here's a tutorial. When you flash through flashtool, the software recognises your phone so don't worry about it
after flashing, root your phone and you're back at where you started
i can help you...
well i think i can help you just follow instructions...
first you need to download flash tool from here > http://androxyde.github.com/index.html?1353476156000
2nd is download stock firmware here > http://hotfile.com/dl/151203731/2a62e2b/LT18i_4.0.2.A.0.62_(1254-8596).ftf.html
after download all files..
1. install Flashtool in your pc.
2. copy "LT18i_4.0.2.A.0.62_(1254-8596).ftf" file to flash tool installed location in firmware folder > "C:\Flashtool\firmwares"
3. Open Flashtool and Click on Flash Button (see Screen Below)
{
"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"
}
4. Now Click on Flashmode then click ok
5. Firmware Selection Window will open then select firmware which you have copied downloaded .ftf File.
6. then click ok and follow screen instruction.
* - Unplug The Device (if connected already with pc)
* - Power off the device (Turn Of Mobile)
* - Press the back button and hold it (back button in your mobile)
* - then Plug the USB Cable (Connect your mobile with pc usb cable while holding back button)
7. wait for 2 min process will take 2 or 3 min.
8. after complete all process remove cable and restart you phone.
9. that's it. :good:
10. if this helped then please come back this thread and press thanks button on my post
same problem, arc struck at sony logo!
I have the same problem with my xperia arc, its struck at sony logo! i flashed as you instructed above, but still after flashing it, its still struck on the sony logo! also I am not able to root it. however when i proceed with the rooting instructions as provided by doom-lord with his root toolkit and start runme.bat it keeps waiting for the device.
please help
rmgunawat said:
I have the same problem with my xperia arc, its struck at sony logo! i flashed as you instructed above, but still after flashing it, its still struck on the sony logo! also I am not able to root it. however when i proceed with the rooting instructions as provided by doom-lord with his root toolkit and start runme.bat it keeps waiting for the device.
please help
Click to expand...
Click to collapse
Try another firmware.
Sent from my LT18i using Tapatalk 2
jimmysmart83 said:
Try another firmware.
Sent from my LT18i using Tapatalk 2
Click to expand...
Click to collapse
thanks a lot mate..:good:!! my dead phone now back to life..!!
I did face the similar issue couple of times after flashing Ultimate Xperia HD and another ROM. But both times, clearing Dalvik Cache by booting to CWM and then booting to system did the trick. Try it...

[Q] samsung galaxy ace 2 I8160 rooting problems

Hello all I have recently purchased a samsung galaxy ace 2, and wish to root it so i can install clock work recovery so i can install a custom ROM.
I have followed guides about using odin to install a stock rooted ROM or rooted kernel, but i cannot seem to get odin to work this is causing me alot of frustration. I have installed kies and the updated samsung driver's, I have opened task manager and exited everything to do with kies before opening odin, my device is detected in odin as COM4 all is well its just when i start the flash it freezes on setup connection... then fails after about 10 minutes.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> system_rooted.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> csc.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have read other people with the same problems and have followed their steps, I have removed my sim and micro sd card I also took out my battery for a couple of minutes and put it back in. I have even tried plugging it in before and after starting up odin, I have also tried 3 different versions of odin and also tried heimdall. I also start the phone up in download mode with usb debugging active I have tried every single custom rom on xda for the ace 2. i really have run out of ideas and cant find any other solutions for my problem so i thought someone might be able to help
thanks in return
sam
Have also just tried it on my netbook and tower pc trying every usb port on each with no luck. I am also using a samsung stock cable, I have tried kies and just the samsung drives on every computer. I have tried plugging the phone in before odin has started and after, I have also plugged the cable in from both sides be it the phone or computer. some help would be really apreciated Im begining to get edgy at how annoyed I am at this thing its not good, I would try to flash another android phone but I don't have one and look's like i have tried pretty much everything. is there any other way to root an ace 2 without odin as it is being way to frustrating and just seems crappy unless im being a n00b and missing something simple here i'm begining to get p***ed of I have wasted a day for nothing......
You know, it would be better to add screenshots, pictures can explain most of the things you typed.
Most people tend to not read all of what you typed. Also, screenshots make it easier to help you since we would know exactly what you're doing wrong.
But enough of the nagging. Here's what it should look like before flashing (Before clicking "START")
{
"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"
}
Oh, DO NOT install Kies if you are going to use Odin. Or get rid of any process related to Kies.(tray_agent.exe or something like that.)
Kies leaves a lot of hidden processes and some say Odin will not work properly if these hidden processes are still running in the background.
I suppose you know what you named the files generated from stock pre-rooted roms. So just try again.
Thanks for the advice i have uninstalled kies, but i dont know how to tell if it is running any hidden things how do i go about doing that ?
I am still having the same problem though I have made some screenshots of odin
You have to have USB Debug on I think. Just flashed my friends Galaxy S3 and I had the same errors you are having on Odin. After numerous unsuccessful attempts,I switched on USB Debug and flashed successfully.
Try last version of Odin (v3.07 : http://forum.xda-developers.com/showthread.php?t=1738841)

Trouble with rooting Samsung Galaxy S3 International version CF-Auto-Root

Dear XDA Members, I have a problem with rooting the Samsung Galaxy S3 International version. Can anyone help me?
{
"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"
}
This picture may help you find the solution.
I'd love to hear a solution.
Please help me,
Spirit.
(This is what the picture is meant for.)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-m0-m0xx-gti9300.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
First off, this is the Sprint GSIII Q&A forum, you might be better off posting here http://forum.xda-developers.com/forumdisplay.php?f=1569
Looking at that screenshot nothing shows up under ID:COM, which would indicate that you don't have the phone in download mode or possibly no USB drivers. Is your phone plugged into your PC and in download mode? Do you have the correct USB drivers for your phone?
noother84 said:
First off, this is the Sprint GSIII Q&A forum, you might be better off posting here http://forum.xda-developers.com/forumdisplay.php?f=1569
Looking at that screenshot nothing shows up under ID:COM, which would indicate that you don't have the phone in download mode or possibly no USB drivers. Is your phone plugged into your PC and in download mode? Do you have the correct USB drivers for your phone?
Click to expand...
Click to collapse
I am not quite sure if I have the drivers...My phone randomly disconnects sometimes.
And I have my phone in download mode, its saying ( ODIN MODE PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS : Official
Downloading...
Do not turn off target!!!)
That's download mode right?
SpiritofFreedom said:
I am not quite sure if I have the drivers...My phone randomly disconnects sometimes.
And I have my phone in download mode, its saying ( ODIN MODE PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS : Official
Downloading...
Do not turn off target!!!)
That's download mode right?
Click to expand...
Click to collapse
Yes, that's download mode. What carrier are you on? I can't really provide drivers without knowing as they're based on model number.
Hmm..
noother84 said:
Yes, that's download mode. What carrier are you on? I can't really provide drivers without knowing as they're based on model number.
Click to expand...
Click to collapse
This is my Device Info
ModelNumber: GT-I19300
Adnroid-Version:4.1.2
Baseband-Version I19300CEELL1
Buildnumber JZO54K.I19300XXEMC2
SpiritofFreedom said:
This is my Device Info
ModelNumber: GT-I19300
Adnroid-Version:4.1.2
Baseband-Version I19300CEELL1
Buildnumber JZO54K.I19300XXEMC2
Click to expand...
Click to collapse
Give these a try (first one)
http://www.samsung.com/uk/support/model/GT-I9300MBAVOD-downloads
---------- Post added at 10:15 AM ---------- Previous post was at 10:12 AM ----------
Oh, click on "Software". The link goes to Manuals for some reason.
noother84 said:
Give these a try (first one)
---------- Post added at 10:15 AM ---------- Previous post was at 10:12 AM ----------
[/COLOR]Oh, click on "Software". The link goes to Manuals for some reason.
Click to expand...
Click to collapse
I am still not rooted though...I try so hard but my Odin 307 just wont detect my phone, whatever I try.
I need experts...
SpiritofFreedom said:
I am still not rooted though...I try so hard but my Odin 307 just wont detect my phone, whatever I try.
I need experts...
Click to expand...
Click to collapse
Do you have Kies installed on your computer? I know that it has had caused issues with Odin detecting the phone. Uninstall Kies and it might work.
topherk said:
Do you have Kies installed on your computer? I know that it has had caused issues with Odin detecting the phone. Uninstall Kies and it might work.
Click to expand...
Click to collapse
I just reinstalled it ._. But I close all processes and try again. :/
I uninstalled it, now I can't connect my phone <_> I didn't delete the driver... just kies. But is kies requered to detect ur phone?
SpiritofFreedom said:
I just reinstalled it ._. But I close all processes and try again. :/
I uninstalled it, now I can't connect my phone <_> I didn't delete the driver... just kies. But is kies requered to detect ur phone?
Click to expand...
Click to collapse
Kies is required when you want to sync your phone. The drivers alone are required to detect your phone.
Kies has been known to interfere with the Odin detection process, so that could be the issue.
topherk said:
Kies is required when you want to sync your phone. The drivers alone are required to detect your phone.
Kies has been known to interfere with the Odin detection process, so that could be the issue.
Click to expand...
Click to collapse
Can you give me an alternatice program?
SpiritofFreedom said:
Can you give me an alternatice program?
Click to expand...
Click to collapse
Go here http://forum.xda-developers.com/showthread.php?t=1655286 and download the drivers. Install them on your computer and try it once again. If that doesn't work, try a different cable or even a different USB port on your computer.

Pixel 2 XL (rooted) bootlooping to TEAMWIN splash after factory reset

I am helping someone with this phone, so I don't have all the details, but I know the phone was rooted and most likely it was running stock Android 10. It had been working fine until a factory reset (from Android settings I am assuming) was done on it.
1. Now when it turned on, it displays the "Bootloader unlocked" warning:
{
"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"
}
2. After the message, it goes to the Google logo for a second and then to the TEAMWIN splash screen, and it just stays there. I have to long-press the power button to power it off.
3. I can get into the bootloader using the power and volume-down keys, and the "Barcodes", "Restart bootloader" and "Power off" option work, but "Start" and "Recovery mode" just take me back to step 1 and then 2.
So, I cannot get into "Recovery mode". I have also connected the phone to my pc (Ubuntu), but the OS does not detect it, so I cannot use fastboot either.
Any ideas on how to fix this?
If you cant connect to it via fastboot while its in bootloader mode things are grim, thats your best bet at fixing it...
Connect to PC and flash the Android 10 stock ROM by running flash-all.bat while phone is at bootloader
Without editing the flash-all.bat file to remove the -w flashing stock ROM will format user data
Thats it
The state of the phone in the pic does not inspire confidence....
Im starting to think the two things are related....
73sydney said:
If you cant connect to it via fastboot while its in bootloader mode things are grim, thats your best bet at fixing it...
Connect to PC and flash the Android 10 stock ROM by running flash-all.bat while phone is at bootloader
Without editing the flash-all.bat file to remove the -w flashing stock ROM will format user data
Thats it
The state of the phone in the pic does not inspire confidence....
Im starting to think the two things are related....
Click to expand...
Click to collapse
After connecting a working and identical phone to my PC, I found out that the reason my PC didn't detect this phone was that the USB port on phone was dirty and the connector didn't go all the way in.
After I cleaned the USB port I was able to flash the stock ROM to it. I was getting an error mid-way through, so I removed the "-w" as per your advice, tried again and it worked. The phone works now. Thank you 73sydenay!
I would like to mark this thread as solved, but I am not sure how to do that, I don't see an option to edit the title.
droidmart said:
I would like to mark this thread as solved, but I am not sure how to do that, I don't see an option to edit the title.
Click to expand...
Click to collapse
Hi,
You could press edit > advanced and edit your title with:
[SOLVED] Pixel 2 XL (rooted) bootlooping to TEAMWIN splash after factory reset
Cheers...
Sébastien.

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

Categories

Resources