A friend forgot the pattern of his tab A sm-t585 and I tried to flash the 7.0 firmware through odin but odin stopped responding and closed before the flash could complete and now the tab is stuck in emergency recovery (a blue screen with an exclamation mark in a triangle with the message "An error has occurred while updating device software. Use the Emergency recovery function in the Smart Switch PC software).
1. I've tried using smart switch software but the tab doesn't show in the list.
2. I tried Kies, and it was the same.
3. I tried older version of Smart Switch and use firmware upgrade and initialization, download was stuck at 69% and the after a period of time changed to 85% and the to 0%, left it overnight and it remained unchanged.
4. I tried odin again, it gave an error (couldn't establish connection)
UPDATE: I just tried odin again and this is the log.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Pls, is there something I'm missing?
gemer45a said:
A friend forgot the pattern of his tab A sm-t585 and I tried to flash the 7.0 firmware through odin but odin stopped responding and closed before the flash could complete and now the tab is stuck in emergency recovery (a blue screen with an exclamation mark in a triangle with the message "An error has occurred while updating device software. Use the Emergency recovery function in the Smart Switch PC software).
1. I've tried using smart switch software but the tab doesn't show in the list.
2. I tried Kies, and it was the same.
3. I tried older version of Smart Switch and use firmware upgrade and initialization, download was stuck at 69% and the after a period of time changed to 85% and the to 0%, left it overnight and it remained unchanged.
4. I tried odin again, it gave an error (couldn't establish connection)
Pls, is there something I'm missing?
Click to expand...
Click to collapse
Hi. Check your installed drivers on Windows. Maybe reinstall. Check usb-cable and connection . Maybe need to change. And try Odin again.
repey6 said:
Hi. Check your installed drivers on Windows. Maybe reinstall. Check usb-cable and connection . Maybe need to change. And try Odin again.
Click to expand...
Click to collapse
I've installed the drivers and whiles updating the Smart Switch software in installed the drivers again.
Update: I just tried odin and this is the results:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin engine v(ID:3.1203)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
gemer45a said:
I've installed the drivers and whiles updating the Smart Switch software in installed the drivers again.
Update: I just tried odin and this is the results:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
What the firmware you flash? BL , AP, CP , CSC - yes?
All screenshots please.
repey6 said:
What the firmware you flash? BL , AP, CP , CSC - yes?
All screenshots please.
Click to expand...
Click to collapse
We're not able to tell the region which the device is from, but I downloaded this "NEE-T585XXU2BQI9-20171106145036" I think it's UAE. I only loaded AP.
Screenshot attached
gemer45a said:
We're not able to tell the region which the device is from, but I downloaded this "NEE-T585XXU2BQI9-20171106145036" I think it's UAE. I only loaded AP.
Screenshot attached
Click to expand...
Click to collapse
Why not all ? Odin settings : ticked checkbox "auto-reboot" and " f.reset-time" yes?
repey6 said:
Why not all ? Odin settings : ticked checkbox "auto-reboot" and " f.reset-time" yes?
Click to expand...
Click to collapse
Ok, then I'll load all and try. Yes "Auto Reboot and F.reset-time" checked.
So after selecting it all it's stuck at initializing. Here's the log:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin engine v(ID:3.1203)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
Click to expand...
Click to collapse
gemer45a said:
Ok, then I'll load all and try. Yest "Auto Reboot and F.reset-time" checked.
So after selecting it all it's stuck at initializing. Here's the log:
Click to expand...
Click to collapse
Your internal memory is corrupt. You need to try in recovery mode do wipes: Wipe data/factory reset>>Wipe cache Partition . Then try flash via Odin again. If not success in Odin tick checkbox "Nand Erase All" else and flash again.
repey6 said:
Your internal memory is corrupt. You need to try in recovery mode do wipes: Wipe data/factory reset>>Wipe cache Partition . Then try flash via Odin again. If not success in Odin tick checkbox "Nand Erase All" else and flash again.
Click to expand...
Click to collapse
Thanks for your reply, I'm not able to power on the device at all. It only turns on when I connect the cable so I'll try the "Nand Erase All" option with Odin.
I've checked the "Nand Erase All" option in Odin and from 7:40pm GMT yesterday till now, it's stuck at initialization. Here's the log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Erase...
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
gemer45a said:
Thanks for your reply, I'm not able to power on the device at all. It only turns on when I connect the cable so I'll try the "Nand Erase All" option with Odin.
I've checked the "Nand Erase All" option in Odin and from 7:40pm GMT yesterday till now, it's stuck at initialization. Here's the log:
Click to expand...
Click to collapse
Sorry but in this case your problem have hardware propeties. Perhaps damaged flash memory contacts. Need SC.
repey6 said:
Sorry but in this case your problem have hardware propeties. Perhaps damaged flash memory contacts. Need SC.
Click to expand...
Click to collapse
I'm not able to boot into recovery but I've managed to get it into download mode but still stuck at initialization. The samsung service contact is quite expensive (GHS 350) but might be the only option now.
gemer45a said:
I'm not able to boot into recovery but I've managed to get it into download mode but still stuck at initialization. The samsung service contact is quite expensive (GHS 350) but might be the only option now.
Click to expand...
Click to collapse
Post a screen shot of odin when attempting to flash the firmware.
You may need the PIT file and repartition to repair this device.
ashyx said:
Post a screen shot of odin when attempting to flash the firmware.
You may need the PIT file and repartition to repair this device.
Click to expand...
Click to collapse
Thanks for the reply, I've attached the screenshot of the Odin when attempting to flash the Tab A. It stays at initialization for about 8 hours. I've searched for the Pit file with no results. I've attached a screenshot of the files I have as well.
gemer45a said:
Thanks for the reply, I've attached the screenshot of the Odin when attempting to flash the Tab A. It stays at initialization for about 8 hours. I've searched for the Pit file with no results. I've attached a screenshot of the files I have as well.
Click to expand...
Click to collapse
Are you certain you are in download mode? What do you see on the screen?
If you are then the first thing to try is swapping the USB cable, preferably for the stock Samsung cable.
Being stuck at initialization is a communication error between device and PC. This is either the device is not in Download mode, bad USB cable or problem with the USB port on either device or PC.
Also make sure the PC and ODIN is in Admin mode.
ashyx said:
Are you certain you are in download mode? What do you see on the screen?
If you are then the first thing to try is swapping the USB cable, preferably for the stock Samsung cable.
Being stuck at initialization is a communication error between device and PC. This is either the device is not in Download mode, bad USB cable or problem with the USB port on either device or PC.
Also make sure the PC and ODIN is in Admin mode.
Click to expand...
Click to collapse
Yes, I'm in download mode. I see the download sign at the center of the screen and something written at the top left corner of the screen.
I have tried different cables and port and The PC and Odin is in admin mode
gemer45a said:
Yes, I'm in download mode. I see the download sign at the center of the screen and something written at the top left corner of the screen.
I have tried different cables and port and The PC and Odin is in admin mode
Click to expand...
Click to collapse
Try removing the md5 extension.
Apart from trying another PC there's is not much else to suggest except download the files again or try a different odin version.
If the device is actually stuck in emergency recovery mode and not just download mode, then Samsung Smart Switch PC App is specificially designed to fix the emergency firmware restore.
We have ODIN. Samsung has Smart Switch. It's like ODIN 7.0. Smart Switch even uses the same ODIN Firmware. ODIN is just their base communications protocol.
Hi Guys, i have the same problem. Update went wrong and now stuck at blue screen. Smart Switch says the tablet is not supported. In odin, same problem as above. Is there any recent solution to this problem?
legend999C2A said:
Hi Guys, i have the same problem. Update went wrong and now stuck at blue screen. Smart Switch says the tablet is not supported. In odin, same problem as above. Is there any recent solution to this problem?
Click to expand...
Click to collapse
Just reboot to download mode and go again.
ashyx said:
Just reboot to download mode and go again.
Click to expand...
Click to collapse
I can't go into download mode. Power button doesn't work and it only goes on when i connect the usb cable with the message to connect to smart switch. I already tried charging it.
Related
it seems to be that I did it totaly wrong when flashing my phone. I get a bootup: "Firmware upgrade encountered an issue." bla...
What did happend:
I had a custom rom from here (Android 4.3): "PACman v4.3 Build 1 nightly 20130909".
My baseband version was (as far as I can remember): XXUBMF8
I wanted to update to 4.4.2 and at first I tried to update the bootloader and modem with Odin 3.09
For bootloader I used this:
BL_I9505XXUFNAD_481100_REV06_user_low_ship_MULTI_C ERT.tar.md5
For modem I used this:
I9505XXUFNC9_GSM_LTE_Modems.tar
The flash with Odin was succesfull and it restarted. Unfortunately I coulnd find any changes in the settings windows under Android. There was still the old version under baseband (I think XXUBMF8) which was strange for me becaue of the flash. I also checked the baseband with a baseband checker tool and it was the same old version. I trayed the flash process a several time and it was always succesull but with no change in the settings.
Anyway, I flashed than a custom rom:
I9505_Omega_v28_XXUFNC9_md5_7C1D639DBBE5C01FE689DA F3B82406AC.zip
FLash was succesfull and Android started.
Under settings, still old baseband: XXUBMF8.
So I decided to update this (this was my first big mistake)..
I used Odin and flashed again the bootloader
BL_I9505XXUFNAD_481100_REV06_user_low_ship_MULTI_C ERT.tar.md5
And from here I get the error message "Firmware upgrade encountered an issue."
Than - maybe my second big mistake - I tried to flash a stock rom to reset my phone. but I used an downgraded version...
[rom]i9505][xxubmf8][4.2.2] (24.06.2013)
I check also during the flashing process with odin "re-partition" and used the pit file and the 4 other files of this firmware. the flash process didnt go to the end, it interrupted. maybe because of the repartition, it goes more and more wrong...
I can still enter the download mode. But what should I try to flash now?
Is it possible to unbrick in my situation...?
And should I use the pit file "CSB_signed_Fusion3_EUR_0325_V2.pit" or should I leave it (just use the firmware?)
Should I use 1-file or 3-file version for odin?
I would appreciate your help a lot. I need the phone for work tomorrow. It is very important for me. Sorry to hustle and thank you very very much!
tried to flash I9505XXUFNAD. added pit file + 4 files (bl, ap, cp, csc) to odin. but I cant run the flash till the end.
without the pit file it doesnt want to start. i used "CSB_signed_Fusion3_EUR_0325_V2.pit" as pit file.
this is my error log...:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_I9505XXUFNAD_481100_REV06_user_low_ship_MULTI_CERT.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> AP_I9505XXUFNAD_481100_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_I9505XXUFNAD_481100_REV06_user_low_ship_MULTI_CERT.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_OXX_I9505OXXFNA2_549230_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
ok...
after hours of searching....: changed the usb slot.... than it managed to flash....
SO, I made a stupid mistake and along with AP CSC and CP flashed BL to my Verizon S7. I tried to go back and do the steps correctly, but the odin flash's are failing now over and over. Get the "software update failed, use verizon repair assist." screen. Issue is in this state I can't get it in software install mode to use said repair assistant. Please tell me someone can help me fix my screw up!? I have googled and tried to solve this, but I came up empty.
T1geR086 said:
SO, I made a stupid mistake and along with AP CSC and CP flashed BL to my Verizon S7. I tried to go back and do the steps correctly, but the odin flash's are failing now over and over. Get the "software update failed, use verizon repair assist." screen. Issue is in this state I can't get it in software install mode to use said repair assistant. Please tell me someone can help me fix my screw up!? I have googled and tried to solve this, but I came up empty.
Click to expand...
Click to collapse
What did you flash, firmware wise? What are you trying to flash?
I was going from the newly updated PH1 (OTA) to Samsung_G930x_QC_Rooted_BOOT.TAR I was just not paying attention ...lol singing and goofing off but yeah I flashed BL AP CP and CSC.
ps. Then I did try to go back and flash the right things, but not surprisingly it was unsuccessful. I after that found a stock tar to try to redo the whole thing (G935VVRS4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.zip) and that was also failed.
T1geR086 said:
I was going from the newly updated PH1 (OTA) to Samsung_G930x_QC_Rooted_BOOT.TAR I was just not paying attention ...lol singing and goofing off but yeah I flashed BL AP CP and CSC.
ps. Then I did try to go back and flash the right things, but not surprisingly it was unsuccessful. I after that found a stock tar to try to redo the whole thing (G935VVRS4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.zip) and that was also failed.
Click to expand...
Click to collapse
I was having flashing issues before. I was doing it on my laptop. What I did was deleted the firmware files and re-downloaded it and was able to flash.
Sent from my SM-G930V using XDA-Developers mobile app
ickedmel said:
I was having flashing issues before. I was doing it on my laptop. What I did was deleted the firmware files and re-downloaded it and was able to flash.
Sent from my SM-G930V using XDA-Developers mobile app
Click to expand...
Click to collapse
I tried re downloading:
BL_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.tar
AP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.tar
CP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.tar
CSC_VZW_G935VVZW4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.tar
HEROQLTE_USA_VZW.pit Tried several more times.
Errors:
"re-partition operation has failed" nearly immediately after start of ODIN flash every time.
On boot attempts it does "erase" and "System Update", reboots and comes up in Android Recovery with "Supported API: 3" and "dm-verity verification failed..."
If someone could point me I don't mind learning and figuring it out, but yeah....tad frusterated so I'm gonna smoke some cancer lol brb.
Are you using the modified odin? The original one wont work. The modified one is in the root guide.
Do what he suggests. Use the modified Odin. If that does not work try swapping cables, computers, etc...
craazy82013 said:
Are you using the modified odin? The original one wont work. The modified one is in the root guide.
Click to expand...
Click to collapse
PrinceComsy version and the ? non PrinceComsy version linked in http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039
Neither worked. Everything failed the same way as described previously (re-partition op. failed, and on recovery dm-vert failure)
Will try again.
Flash BL AP CP CSC, or BL AP CP CSC +pit or AP CP CSC?
Want to make sure I at least get this right.
T1geR086 said:
PrinceComsy version and the ? non PrinceComsy version linked in http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039
Neither worked. Everything failed the same way as described previously (re-partition op. failed, and on recovery dm-vert failure)
Click to expand...
Click to collapse
Does the phone even boot? USB debugging on?
craazy82013 said:
Does the phone even boot? USB debugging on?
Click to expand...
Click to collapse
It powers on. then go's to recovery, I have turned on USB debugging while trying to figure out wtf I did last night through maintence boot or not sure what its called but it has the option to enable debugging.
T1geR086 said:
It powers on. then go's to recovery, I have turned on USB debugging while trying to figure out wtf I did last night through maintence boot or not sure what its called but it has the option to enable debugging.
Click to expand...
Click to collapse
Check for usb debugging in maintenance mode. Power off device hold volume down and power at same time till maintenance mode shows up.
craazy82013 said:
Check for usb debugging in maintenance mode. Power off device hold volume down and power at same time till maintenance mode shows up.
Click to expand...
Click to collapse
Does it stay enabled or do I need to do it every so often. I will do it again, but I had already last night.
T1geR086 said:
Does it stay enabled or do I need to do it every so often. I will do it again, but I had already last night.
Click to expand...
Click to collapse
I would think it would stay. I know you did some of this. Im not a dev. Just trying to help. Redownload everything. Try a different computer. Different usb cable. Try everything. Gotta get back to it but ill hit up a dev and see what he thinks. Sorry if im no help brother
craazy82013 said:
I would think it would stay. I know you did some of this. Im not a dev. Just trying to help. Redownload everything. Try a different computer. Different usb cable. Try everything. Gotta get back to it but ill hit up a dev and see what he thinks. Sorry if im no help brother
Click to expand...
Click to collapse
Not trying to be short. Sorry if it came off that way. I appreciate hitting up a dev. I've been rather fixated on fixing this...*phone detox itch*
New error (or first I noticed it) when attempting to flash:
BL_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
AP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
CP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
CSC_VZW_G935VVZW4APH1_CL8875708_QB10880117_REV02_u ser_low_ship_MULTI_CERT.tar
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> persist.img.ext4
<ID:0/003> Home Binary Download
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> xbl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Auth error instead of re-partition failure.
T1geR086 said:
New error (or first I noticed it) when attempting to flash:
BL_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
AP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
CP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
CSC_VZW_G935VVZW4APH1_CL8875708_QB10880117_REV02_u ser_low_ship_MULTI_CERT.tar
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> persist.img.ext4
<ID:0/003> Home Binary Download
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> xbl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Auth error instead of re-partition failure.
Click to expand...
Click to collapse
What version of Odin are you using?
Illogi.xbone said:
What version of Odin are you using?
Click to expand...
Click to collapse
3.12 Princecomsy
I am DLing APE1 zip from sammobile because that's the version that shows up in recovery. heh have 2hrs left on that DL (non premium throttling)
Try using Odin 3.14
T1geR086 said:
3.12 Princecomsy
I am DLing APE1 zip from sammobile because that's the version that shows up in recovery. heh have 2hrs left on that DL (non premium throttling)
Click to expand...
Click to collapse
Dont think you can downgrade ph1. Bootloader supposedly changed. There is a faster download in the forum. Way faster. http://downloadmirror.co/29Uj/G930VVRU2APE1_G930VVZW2APE1_VZW.zip<br />
Illogi.xbone said:
Try using Odin 3.14
Click to expand...
Click to collapse
Ty will try. Best place to find that? Odin downloader lists odin3 3.11.2 as latest? Didn't see any 14 ending versions.
Basically my device is the Samsung Galaxy S7 Edge, obviously. SM-G935A. It is the AT&T version, and I believe I may have soft bricked it. I played with roots and never successfully rooted it before, but now it is most likely soft bricked. I turned off the device, turned it back on, and I got stuck on a frozen AT&T boot logo. I was able to get into Recovery Mode later on and I have factory reset it several times, but each time I do, it loads directly back into Recovery mode. I have tried several different versions of ODIN, and several different ROM's and Firmware's with each version of ODIN and I get errors every single time.
At this point, I'm willing to try anything, so if you suggest something to me, I will give it a shot because I just want my phone back.
Thanks in advance, I appreciate anything.
You need to start by flashing your original rom with odin, then follow tutorials on xda on methods to root your model.
Deano89 said:
You need to start by flashing your original rom with odin, then follow tutorials on xda on methods to root your model.
Click to expand...
Click to collapse
What exactly do you mean by my original rom? If you could provide a link I would really appreciate it.
EDIT: I found an original AT&T rom, and it would not flash correctly. The log is below.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> xbl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone: SW REV CHECK FAIL : [aboot]Fused 4 > Binary 2 [1] eMMC write fail: aboot
Same issue here man, i been trying everything with no success. My phone keeps rebooting from the samsung logo. Nothing has been successfully flashed either.
If anyone has any firmware or ROM's or versions of ODIN you could suggest. Original firmware, stock ROM's, custom ROM's, unlocked ones, whatever, please post them and I will try them.
Try flashing all the ROM files apart from BL
Just AP, CP, CSC
*Detection* said:
Try flashing all the ROM files apart from BL
Just AP, CP, CSC
Click to expand...
Click to collapse
I believe I may have tried that last night, however, I didn't save the log. It got me a bit farther, I believe. I will try it again today and post the log this time.
Thanks for the response!
Download Samsung Kies 3 from here:
http://www.samsung.com/uk/support/usefulsoftware/KIES/
Then once you downloaded/installed kies you put your device in Download mode.
In Kies 3 go to the top menu bar and select Tools > Firmware upgrade and initialization.
It will prompt you to enter your device's model name and in the next window it will ask for your Serialnumber (which is on the back of your device (rip dbrand skin) )
After that a download will start in Kies 3 and now you just have to wait for it to download and install.
Good luck!
LennARTpas said:
Download Samsung Kies 3 from here:
http://www.samsung.com/uk/support/usefulsoftware/KIES/
Then once you downloaded/installed kies you put your device in Download mode.
In Kies 3 go to the top menu bar and select Tools > Firmware upgrade and initialization.
It will prompt you to enter your device's model name and in the next window it will ask for your Serialnumber (which is on the back of your device (rip dbrand skin) )
After that a download will start in Kies 3 and now you just have to wait for it to download and install.
Good luck!
Click to expand...
Click to collapse
Will give this a shot now that I know how to use Kies. I installed it last night while I was trying to fix it, and I thought it was just a different driver haha.
Pyroshox said:
Will give this a shot now that I know how to use Kies. I installed it last night while I was trying to fix it, and I thought it was just a different driver haha.
Click to expand...
Click to collapse
Let me know if you fixed the issue you're having!
Pyroshox said:
What exactly do you mean by my original rom? If you could provide a link I would really appreciate it.
EDIT: I found an original AT&T rom, and it would not flash correctly. The log is below.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> xbl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone: SW REV CHECK FAIL : [aboot]Fused 4 > Binary 2 [1] eMMC write fail: aboot
Click to expand...
Click to collapse
Download the newest Odin version.
Make sure the re-partition mode is OFF.
Try again with the base firmware from Sammobile
@LennARTpas - I am trying this on a separate computer, but I am getting errors that my device is not supported and that the S/N is incorrect even though I have typed it in several times. Any assistance would be greatly appreciated.
@roba93 - I will be sure to try your method once I am back in the environment to do so.
Pyroshox said:
@LennARTpas - I am trying this on a separate computer, but I am getting errors that my device is not supported and that the S/N is incorrect even though I have typed it in several times. Any assistance would be greatly appreciated.
@roba93 - I will be sure to try your method once I am back in the environment to do so.
Click to expand...
Click to collapse
here!
@LennARTpas - I tried your method, however, the same issue occurred. I got several recurring errors telling me that my device was not recognized by Kies, and when I attempted to submit the S/N, it told me it was incorrect.
@roba93 - I tried your method as well, however, SamMobile does not offer firmware for SM-G935A, so I tried the unlocked version, SM-G935U, and it gave me this log below. If I did not use the correct firmware, if you could point me in the direction of which to use that would be greatly appreciated. I feel as though I'm coming off like a needy n00b, and I don't mean to in any way for future reference.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> FAIL! SHA256 is invalid
<OSM> All threads completed. (succeed 0 / failed 1)
EDIT: @*Detection* - I tried your method where I didn't use the BL in ODIN, and I got this log.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Pyroshox said:
@LennARTpas - I tried your method, however, the same issue occurred. I got several recurring errors telling me that my device was not recognized by Kies, and when I attempted to submit the S/N, it told me it was incorrect.
@roba93 - I tried your method as well, however, SamMobile does not offer firmware for SM-G935A, so I tried the unlocked version, SM-G935U, and it gave me this log below. If I did not use the correct firmware, if you could point me in the direction of which to use that would be greatly appreciated. I feel as though I'm coming off like a needy n00b, and I don't mean to in any way for future reference.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> FAIL! SHA256 is invalid
<OSM> All threads completed. (succeed 0 / failed 1)
EDIT: @*Detection* - I tried your method where I didn't use the BL in ODIN, and I got this log.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You said that you are using the G935A.
Please try the following firmware: http://downloadmirror.co/1Ksx/G935AUCS4API2.zip
Hope this helps
roba93 said:
You said that you are using the G935A.
Please try the following firmware: http://downloadmirror.co/1Ksx/G935AUCS4API2.zip
Hope this helps
Click to expand...
Click to collapse
I love you so much right now.
I tried this firmware on a separate computer, and didn't try it on my main PC because it wasn't necessary, however, it worked. It went through and flashed correctly, and my phone booted into recovery mode. I had to wipe the cache, and it began setting up the phone like normal.
THANK YOU SO MUCH!
Pyroshox said:
I love you so much right now.
I tried this firmware on a separate computer, and didn't try it on my main PC because it wasn't necessary, however, it worked. It went through and flashed correctly, and my phone booted into recovery mode. I had to wipe the cache, and it began setting up the phone like normal.
THANK YOU SO MUCH!
Click to expand...
Click to collapse
No problem mate
Glad it worked
roba93 said:
No problem mate
Glad it worked
Click to expand...
Click to collapse
Yay it unbricked my phone too!
it is hard to find a guide with all the phone versions/updates, just specific solutions. Well this one magically worked, thank you.
I have a sm-g935a (att) - It would bootloop, after several attempts to recover by flashing various files the phone would give all sorts of errors depending on the version flashed, stop at recovery mode and not go any further, although let me wipe it. hope this helps if you have a similar porblem
Hi everyone, I think my Galaxy S7 Edge might be bricked.
The phone won't boot at all even in Recovery Mode. Still, I can access the Download mode to try to reinstall the firmware.
The Problem is that Odin won't pass the <ID:0/003> Initialzation.. message.
I've tried two versions of Odin, being V3.12.7 and V3.12.3. Both running as normal user and as admin.
Also, I've tried three different firmwares, as follows:
G935FXXU1DQJ3_G935FEVR1DQJ1_EVR
S7_Edge_Nougat_7.0_Stock_ROM_S7FanClub.com_G935FOXA1DPLT_BTU
SM-G935F_1_20171018210052
None of them worked since Odin can't reinstall the firmware. I think USB debugging is not enable and there is no way to do that now.
Here is the log on Odin:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1207)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
Is there anything that I can do to make Odin pass this?
Attached are the screenshots of Odin and the phone screen.
Acir said:
Hi everyone, I think my Galaxy S7 Edge might be bricked.
The phone won't boot at all even in Recovery Mode. Still, I can access the Download mode to try to reinstall the firmware.
The Problem is that Odin won't pass the <ID:0/003> Initialzation.. message.
I've tried two versions of Odin, being V3.12.7 and V3.12.3. Both running as normal user and as admin.
Also, I've tried three different firmwares, as follows:
G935FXXU1DQJ3_G935FEVR1DQJ1_EVR
S7_Edge_Nougat_7.0_Stock_ROM_S7FanClub.com_G935FOXA1DPLT_BTU
SM-G935F_1_20171018210052
None of them worked since Odin can't reinstall the firmware. I think USB debugging is not enable and there is no way to do that now.
Here is the log on Odin:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1207)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
Is there anything that I can do to make Odin pass this?
Attached are the screenshots of Odin and the phone screen.
Click to expand...
Click to collapse
Did you give it a couple of minutes to load? Also try redownloding from another place
tactical bacon said:
Did you give it a couple of minutes to load? Also try redownloding from another place
Click to expand...
Click to collapse
Thanks for the answer.
I did give hours actually. For some reason, my computer shows the BSOD and then reboots. I used 3 different firmwares from 3 different locations, being one of them from SamMobile.
I have no idea what to do next. I thought in try to install TWRP, but since the USB debugging is not enable, it might be worse.
Anything else that I could have missed?
Acir said:
Thanks for the answer.
I did give hours actually. For some reason, my computer shows the BSOD and then reboots. I used 3 different firmwares from 3 different locations, being one of them from SamMobile.
I have no idea what to do next. I thought in try to install TWRP, but since the USB debugging is not enable, it might be worse.
Anything else that I could have missed?
Click to expand...
Click to collapse
FRP Lock was enabled, if you are able to boot into the system disable FRP Lock.
zzThrain said:
FRP Lock was enabled, if you are able to boot into the system disable FRP Lock.
Click to expand...
Click to collapse
I can't boot into the system, that's the problem.
The only screen I can see is the Download mode. The boot is stuck in bootloop and Recovery mode is not working too.
Acir said:
I can't boot into the system, that's the problem.
The only screen I can see is the Download mode. The boot is stuck in bootloop and Recovery mode is not working too.
Click to expand...
Click to collapse
I had a similar issue when first Flashing ROM. I suggest you to retry flashing The Stock Firmware Of Nougat For Your Device Model. This Time Uninstall Odin. Re-install Samsung USB Drivers, And Use OEM Usb Cable Then Re Install Odin Then Re Flash Stock Firmware Then Boot Into Stock Recovery Full Wipe And Reboot System.
Make Sure Auto Reboot Is Disabled In Odin.
Good Luck
zzThrain said:
I had a similar issue when first Flashing ROM. I suggest you to retry flashing The Stock Firmware Of Nougat For Your Device Model. This Time Uninstall Odin. Re-install Samsung USB Drivers, And Use OEM USB Cable Then Re Install Odin Then Re Flash Stock Firmware Then Boot Into Stock Recovery Full Wipe And Reboot System.
Make Sure Auto Reboot Is Disabled In Odin.
Good Luck
Click to expand...
Click to collapse
I tried your tips, but nothing worked. Still, it won't pass the <ID:0/003> Initialzation.. message no matter what I do.
This is so bad. And everywhere where I looked on the internet, no one had a similar issue.
Any other recommendations?
Hello,
I am a newbie but I have tried reading and researching. Got past a few of my questions but got stuck so looking for some suggestions.
I have a samsung galaxy tab a sm-t510 (2019??) i believe. Its about 2 to 3 years old so the 2019 version would match. Physically looking at the device its smt-510 and it says this on the oden download mode page as well. All i have access to, to verify this. OS is dead. Here is my issue. I got this tab for my nephew and it died. It was low on battery and he just left it for like a month. Since then he said it just stopped working and kept on restarting. Reading online it seems like the battery died to the point where the charging module cant load so it cant change and boot into the os. It just keeps restarting with the error "could not do normal boot invalid Kernel length". I cannot get into the recovery mode and can only get it into the download mode. Reading online says i should just reload the firmware which should fix the issue. So this is what i am trying to do. The region for this device is in canada. Next in the download mode it says secure boot enabled and oem lock on. I cant get into the os to turn these off. I cant find a way to disable these without getting into the OS. My goal is to get it working, custom rom or oem, dont really care. I know if i load an oem firmware these settings should not matter. I've downloaded a few different versions of the oem image (sammobile and using frija).
I keep getting Re-Partition operation failed. when trying to load the image. I have tried v9 which came with the tab and tried latest v11 using frija.
I can see it connect fine and all is good but it seems like i have the wrong image and this is why i keep getting the re-partition failed? I have tried this with Oden 3.09 which has a few check boxes and one is re-partition. its unchecked. Defaults (auto reboot and f. reset time) are only on. I have also tried it with Oden 3.13.3 with same options. Again my goal is to load anything on it to get it working. Any thoughts on options and what i can do to recover this? My theory is i have the wrong image and thats why the oem and secure download is giving me an error but not sure. Any help would be nice.
just to add. if i select the home csc file i get the there is no pit partition error.
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_T510XXU2ASK5_CL17420370_QB27658722_REV02_user_low_ship.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_OMC_OXM_T510OXM2ASK5_CL17420370_QB27658722_REV02_user_low_ship.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> AP_T510XXU2ASK5_CL17420370_QB27658722_REV02_user_low_ship_meta_OS9.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Re-Partition operation failed.
Thanks,
Mike