Related
Hello.i recently bought the at&t galaxy s7 edge sm-g935a.i am from greece and would like to ask if i can flash firmware from the sm-g935f via odin?is that possible?
Sent from my SAMSUNG-SM-G935A using XDA-Developers mobile app
johnaras said:
Hello.i recently bought the at&t galaxy s7 edge sm-g935a.i am from greece and would like to ask if i can flash firmware from the sm-g935f via odin?is that possible?
Click to expand...
Click to collapse
Nope. The F model has a different chipset. You can flash the 935U version though.
ShrekOpher said:
Nope. The F model has a different chipset. You can flash the 935U version though.
Click to expand...
Click to collapse
There's only one Stock ROM 935u version right? I'm looking for a Custom ROM 935u.. Thanks..
elnene03 said:
There's only one Stock ROM 935u version right? I'm looking for a Custom ROM 935u.. Thanks..
Click to expand...
Click to collapse
The 935a model does not have an unlocked bootloader so there are not custom ROMs. You can flash different firmware, and have laggy ENGBOOT root, but there is really no development for the device right now.
Ok.so i can flash only the u firmware without any problem?is that better than the a??
Sent from my SAMSUNG-SM-G935A using XDA-Developers mobile app
Hello,
Ineed help on installing stock firmware too for samsung s7 SM-G930A AT&T mobile.
https://drive.google.com/drive/folders/0Bz4qV62uoY6aQXpfZWpRV0MxUkE
These are errors videos. I'm stuck here with this issue
I rooted my phone, ran the S7 fixes script, the debloat script, then the root seemed to work fine for a day. Then the wireless charging stopped working, then it unplugged and replugged itself over and over and over in the charging mode, like it "recognizes" the charging cable over and over all day long while it's plugged into the charger, making the "beep beep" sound that it makes when you plug in the charger. So I rebooted the phone to see if it would fix it, and now it hangs at the at&t logo screen forever. I can't power it down. I can get into odin mode, but odin fails every time I try to reinstall the factory ROM. I tried to clear the cache, but it didn't work. I tried booting into recovery mode, but it fails. basically I've tried just about everything to unbrick and it's still bricked.
also note that I used odin 3.12.3, the lastest. and I tried to install G930AATT1APB5_User_Binary, which fails every time.
also tried smartswitch, but the program just shuts off instantly after entering the SN in the device initialization in the emergency software and device initialization tab.
I enter the SN and hit okay and then it just shuts down the program, it just disappears.
<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> 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)
Hello every one, i am here to ask help for a special case, if is there someone with the knowlege in XDA to help mein this, i got a friend who has his s7 edge from at&t one day not working anymore it got stuck in boot loop, he never try to root or nothing he is a normal simple phone user. so now i am trying to help him but i dont know which firmware the phone had, i cant put developer options , the usb debugging nothing etc, i try to start in recovery mode but it get stuck in blue letters that say recover booting and never boot into recovery, the only thing the phone do now is get into download mode, and the pc recognize it and odin too, i have read every single thread i think to flash every single stock rom available and none has work i try diferent pc´s, cables, usb port, odin version etc. the most common error i got all times by odin was this one
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> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i am noob in this things i barely know a little readding all the threads i have put so much effort on this without success ,
can someone guide me please i will apreciate it
Darkboss10 said:
Hello every one, i am here to ask help for a special case, if is there someone with the knowlege in XDA to help mein this, i got a friend who has his s7 edge from at&t one day not working anymore it got stuck in boot loop, he never try to root or nothing he is a normal simple phone user. so now i am trying to help him but i dont know which firmware the phone had, i cant put developer options , the usb debugging nothing etc, i try to start in recovery mode but it get stuck in blue letters that say recover booting and never boot into recovery, the only thing the phone do now is get into download mode, and the pc recognize it and odin too, i have read every single thread i think to flash every single stock rom available and none has work i try diferent pc´s, cables, usb port, odin version etc. the most common error i got all times by odin was this one
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> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i am noob in this things i barely know a little readding all the threads i have put so much effort on this without success ,
can someone guide me please i will apreciate it
Click to expand...
Click to collapse
Remove PIT file and try again.
From Edge of Galaxy Seven
Darkboss10 said:
Hello every one, i am here to ask help for a special case, if is there someone with the knowlege in XDA to help mein this, i got a friend who has his s7 edge from at&t one day not working anymore it got stuck in boot loop, he never try to root or nothing he is a normal simple phone user. so now i am trying to help him but i dont know which firmware the phone had, i cant put developer options , the usb debugging nothing etc, i try to start in recovery mode but it get stuck in blue letters that say recover booting and never boot into recovery, the only thing the phone do now is get into download mode, and the pc recognize it and odin too, i have read every single thread i think to flash every single stock rom available and none has work i try diferent pc´s, cables, usb port, odin version etc. the most common error i got all times by odin was this one
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> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i am noob in this things i barely know a little readding all the threads i have put so much effort on this without success ,
can someone guide me please i will apreciate it
Click to expand...
Click to collapse
Not knowing WHAT you are flashing, makes it a little harder to determine what is going wrong.
Go HERE and flash this in Download Mode. This is the latest Stock 935A ROM, This will wipe Everything on the device, and it'll be like it came brand new
norbarb said:
Remove PIT file and try again.
From Edge of Galaxy Seven
Click to expand...
Click to collapse
which is the pit file, sorry for dumb question
Darkboss10 said:
which is the pit file, sorry for dumb question
Click to expand...
Click to collapse
If I remember correctly you need to uncheck PIT in odin and this should help. BTW. What are you trying to flash?
From Edge of Galaxy Seven
I have try the stock rom version 935a...pf2 . And any other stock rom i have found for the 935a seeing which will work .
Darkboss10 said:
I have try the stock rom version 935a...pf2 . And any other stock rom i have found for the 935a seeing which will work .
Click to expand...
Click to collapse
If you are currently on a ROM that has v4 boot loader's, part of your problem may be that you are trying to flash a rom with v2, v3 bootloaders
Sent from my SM-G935T using XDA-Developers Legacy app
so i do better go with the v4 bootloader and i will check if the pit file is uncheck, what should i put on the re-partition case of odin active or inactive?
by the way thanks for your help
kangi26 said:
If you are currently on a ROM that has v4 boot loader's, part of your problem may be that you are trying to flash a rom with v2, v3 bootloaders
Sent from my SM-G935T using XDA-Developers Legacy app
Click to expand...
Click to collapse
hey i did exactly as you told me , and for first time i guess i have an advance, i still get an error but at least a new error , check it out maybe you know what it is
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> emmc_appsboot.mbn
<ID:0/005> lksecapp.mbn
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
any idea what can be?
i try to flash the G935a...PI2 rom bot without the CSC which i guess is the pit file right?
When you try to get the device into Recovery, it will appear like it isn't doing it or looks like an "No Command" error and it can take a couple of min to actually get into Recovery.
I would boot into Recovery again, let it sit for a few min. My bet is that it will eventually get into Recovery. Once it does, do a Factory reset, and then reboot into Download Mode, open Odin connect the device to your PC and install all 4 of the items from the Stock ROM thread, don't mess with any of the settings in Odin, just populate the slots with the BL, AP, CP and CSC
kangi26 said:
When you try to get the device into Recovery, it will appear like it isn't doing it or looks like an "No Command" error and it can take a couple of min to actually get into Recovery.
I would boot into Recovery again, let it sit for a few min. My bet is that it will eventually get into Recovery. Once it does, do a Factory reset, and then reboot into Download Mode, open Odin connect the device to your PC and install all 4 of the items from the Stock ROM thread, don't mess with any of the settings in Odin, just populate the slots with the BL, AP, CP and CSC
Click to expand...
Click to collapse
This is what i get . But it doesnt enter recovery at the end. It just shut off ....
Darkboss10 said:
This is what i get . But it doesnt enter recovery at the end. It just shut off ....
Click to expand...
Click to collapse
Looks like the device is just rebooting
Sent from my SM-G935T using XDA-Developers Legacy app
kangi26 said:
Looks like the device is just rebooting
Sent from my SM-G935T using XDA-Developers Legacy app
Click to expand...
Click to collapse
if you watch the top corner blue letters it says recovery booting....
Darkboss10 said:
if you watch the top corner blue letters it says recovery booting....
Click to expand...
Click to collapse
I'm at a loss man, I'm sorry. I haven't seen that before, I dont get the "Samsung" part when I enter Recovery
Darkboss10 said:
if you watch the top corner blue letters it says recovery booting....
Click to expand...
Click to collapse
Can you post screen from download mode?
From Edge of Galaxy Seven
norbarb said:
Can you post screen from download mode?
From Edge of Galaxy Seven
Click to expand...
Click to collapse
There you go . By the way i should mention the phone only turns on download mode when plugged.
Darkboss10 said:
There you go . By the way i should mention the phone only turns on download mode when plugged.
Click to expand...
Click to collapse
OK you got bootloader v2. Try to flash some older version of MM in download mode using odin
Like from here: http://forum.xda-developers.com/showthread.php?p=67601581
From Edge of Galaxy Seven
You need to start by using the latest Odin, 3.12.3 for installing the original ROM. If you try to unlock, you need to go get the PrinceComsy version. PrinceComsy won't work for in-bricking a device, and if you have any of the stock versions of the ROM, you need the 3.12.3 version.
norbarb said:
OK you got bootloader v2. Try to flash some older version of MM in download mode using odin
Like from here: http://forum.xda-developers.com/showthread.php?p=67601581
From Edge of Galaxy Seven
Click to expand...
Click to collapse
I try that . Now i got this error but only on the phone screen and odin is stuck at initialization .. any idea what could be
i download the venom stock rom and the odin file he suggest but that odin is v 3.11.2 , so that was the one that trows me the odin protocol error, i try the same rom but with the v 3.12.3 odin , and it start working but it says fail at the on the recovery image, do that has to do something with my problem that the phone can boot into recovery mode?
here are the logs
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> FAIL! (Erase)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
Hello everyone,
I'm following this forum for mounths but just had chance to register.
I tried to root my phone, then I think something went wrong. Turned on the phone and used for a while, but had a fingerprint sensor error. After that I reboot the phone, but while showing the Samsung logo, I got "only official released binaries are allowed to be flashed" top of the screen. And phone was automaticly turning off after that.
Then I put the phone download mode and tried to install official firmware. Odin was failed.
I tried to flash bootloader only, and fail neither.
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> cm.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I thought maybe the stock rom that I trying to install is older. But now I can't open the TWRP with the buttons for the wipe data. The Samsung Galaxy logo views, after that it turns off.
Trying to install twrp again, Odin gives me fail too. Now I can only open the download mode.
I need my phone today urgently for contact with my colleagues.
Please ask me for the missing informations and please help me ASAP.. Sorry for my bad and complicated English..
Try to flash an earlier Version of the bootloader maybe QF7.
I found the flashable odin archive at https://mega.nz/#!5Q4TATzQ!DT2OQO01KHfw7HsVNElZSfZ4DHoO9W99k3dJqfumMhg for s8 and at https://mega.nz/#!dMZ0zbDL!oYrcBh8DeOqMFeO9QObu8eNXVrjsajXICJ0o3MJPJ-o for s8+.
I also find a video for this issue at https://youtu.be/VTi3uBkpJic
Try this and reply back..
- ————————————
Or just try to flash the stock rom without the cm.bin/ bl firm.
memreb1801 said:
Try to flash an earlier Version of the bootloader maybe QF7.
I found the flashable odin archive at for s8+.
I also find a video for this issue at
Try this and reply back..
Click to expand...
Click to collapse
Thank you for helping but I tried these solutions allready. Now downloading another country's official rom from sammobile. I'm going to try this one but I have no hope
Good luck!!??
My solution did work. Download the latest firmware and install it with Odin. Thanks everyone anyway..
This is a continuation of a discussion in the TWRP support thread as it's getting a bit off-topic for that thread.
My trusty Galaxy Note 3 N9005 32GB has been giving me a few minor file errors recently, so I re-installed from a nandroid backup (ROM is MagMa NX VX PCE 6.0.1) with Phantom kernel) and it's been great for a few weeks now, performing better than ever in fact.
However yesterday, I glanced at the phone mid-afternoon (after using it fine all day listening to music and reading emails, etc) and it had reverted to the Download screen, reporting "Could not do normal boot, ddi : mmc_read failed."
I can't get into Recovery or use ADB, so I ran Odin on my PC and it showed the device as Added, so I thought I'll re-upload TWRP so I can at least get into Recovery and see what's going on, but although Odin started sending the TWRP .tar file normally, it quickly reported "Get PIT for mapping ... There is no PIT partition". The phone screen showed "UDC START" then "MMC: mmc_read fail". The USB port and USB cable are the same ones I've been using for some recent adb pull backups so they should be OK.
I tried installing a new PIT file (first from a previous backup of my own setup, and then from generic versions for this device) but Odin with AutoReboot, Re-Partition, and F.Reset Time ticked showed:
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And the phone showed:
UDC START
MMC: mmc_read fail
I then tried downloading a 4files repair installation of a stock Lollipop ROM (the most recent I could find for this device, N9005ZSUGPJ2) and used Odin to install the included PIT, AP, BL, CP and CSC files, with Nand Erase All selected too:
<ID:0/007> Odin engine v(ID:3.1101)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Erase...
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This time, the phone showed:
UDC START
MMC: mmc_read fail
ERASING USERDATA PARTITION...
I could really do with some expert help or advice here from anyone who knows more about these things than I do... or do I have an unexpected brick on my hands? Thanks!
Andre
I'm afraid that your phone memory died...this error is a corrupted memory flash
if 4 files + pit doesn't work...which version did you get????
here is the procedure you have to follow...
PLEASE.....DO NOT skip ahead, just follow my instructions in sets,
Here are the Files you NEED to download:
Odin3 v3.10.zip
CHARGE the device to 100% Battery BEFORE beginning!
Download and extract the Files.
Open ODIN, place each of the Files in corresponding boxes:
BL = BL
AP = AP
CP = CP (MODEM)
CSC = CSC
Please select these Check-boxes:
Auto-Reboot
Re-Partition
F. Reset Time
NAND Erase All
Phone Bootloader Update
Phone EFS Clear
START!!
After it reboots, WAIT 10 Minutes, Skip the Wizard and perform a Factory Data Reset!
rayman95 said:
I'm afraid that your phone memory died...this error is a corrupted memory flash
if 4 files + pit doesn't work...which version did you get????
Click to expand...
Click to collapse
Which phone version, or which 4files?
Phone is a Galaxy Note 3 N9005 (UK 32GB).
File was from https://zfirmware.com/download-samsung-repair-firmwares/ , version http://www.mediafire.com/file/9ux01...3-N9005-Full-Factory-rom-5.0-N9005ZSUGPJ2.zip . I guess I could try an earlier KitKat version, or if you have any better suggestions, but it's looking less and less hopeful.
I was hoping to be able to use this device until the Note 10 is released, but maybe I'll have to settle for an S10+. Problem is, I prefer my nice Note 3 to anything they have released since (removable battery, no stupid curved-edge display, proper physical front buttons away from the main screen, a bigger - OK, wider - display than anything since, etc)
Andre
andrewilley said:
This is a continuation of a discussion in the TWRP support thread as it's getting a bit off-topic for that thread.
Click to expand...
Click to collapse
From my own experience, this problem is a manufacturing defect that affects a lot of samsung devices produced from Q3 of 2014 until Q2 of 2015. The error starts to appear generally after 2 years of use. Note 4 is the most affected, including mine who died last year.
However, I managed to fix a Galaxy S5 with the method I already described. And that has been presented as a momentary solution by several xda users, like here.
I wrote : momentary solution because this error is definitely a hardware failure, a fixed device will only work for a random period then the problem will get worse until the device become completely unusable.
Fortunately, you can buy a new motherboard for less than 30euro. And that's what I recommend you to do.
andrewilley said:
Galaxy-Note3-N9005-Full-Factory-rom-5.0-N9005ZSUGPJ2.zip[/url] . I guess I could try an earlier KitKat version, or if you have any better suggestions, but it's looking less and less hopeful.
Andre
Click to expand...
Click to collapse
this firmware is not for european device but asian... you must find another one, or try kitkat, otherwise I can send you mine, french one
N9005XXUGBNL8_OXAGBNL8_v5.0_Repair_Firmware
zlazaar said:
The error starts to appear generally after 2 years of use. Note 4 is the most affected, including mine who died last year.
Click to expand...
Click to collapse
I've been noticing a few file-read errors over the last 5 months or so, which I put down to bad blocks even though e2fsck -cfv showed zero errors. I thought a reformat and nandroid restore had fixed it, but obviously if the problem is lower down that might just have been delaying the inevitable. I suspect that installing a new mobo would not really be a good long-term plan as that could just as easily have the same issue (as they'll all be 4+ years old by now).
rayman95 said:
this firmware is not for european device but asian... you must find another one, or try kitkat, otherwise I can send you mine, french one
N9005XXUGBNL8_OXAGBNL8_v5.0_Repair_Firmware
Click to expand...
Click to collapse
I'll try the KitKat version (normally I'd look for a BTU version, but beggars can't be choosers as the saying goes). If I can at least get it running for now and restore my backup via TWRP then I can do a more relaxed and controlled switchover to an S10+.
Andre
Whatever I try, I can't get a new PIT file to re-partition the memory:
<ID:0/007> Odin engine v(ID:3.1301)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 2252 M
<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> FAIL!
<ID:0/007>
<ID:0/007> Re-Partition operation failed.
Phone shows MMC: mmc_read fail
Does anyone have a known good PIT file for the UK Note 3 N9005 32GB, along with a matching BL/AP/CP/CSC combo (any ROM version would do) that they would be willing to either upload or point me to?
Thanks,
Andre
I guess I probably should treat this device as a brick now and get it replaced, no other suggestions?
Andre
sammobile forum ??
JJEgan said:
sammobile forum ??
Click to expand...
Click to collapse
Thanks for the tip. I did ask nicely in their forums, but got a very terse response that they don't discuss devices that have been rooted.
Andre
andrewilley said:
Thanks for the tip. I did ask nicely in their forums, but got a very terse response that they don't discuss devices that have been rooted.
Andre
Click to expand...
Click to collapse
i send you my french files....
take here my files...
Thanks, I'll download and give them a try when I get back on home wi-fi. I fear I'll probably get the same results, but at least I'll have tried everything before giving up on it.
Andre
File downloaded, thank you. There doesn't seem to be a matching PIT file in there though, just the BL, AP, CP and CSC. Is that correct? As stated earlier in the thread, the PIT seems to be corrupted on my device, so was hoping for all 5 files to match...
Andre
rayman95 said:
take here my files...
Click to expand...
Click to collapse
I did try the 4files in your ZIP, but without a new PIT file I got the same partitioning error as before:
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 2340 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Andre
the pit HERE...
good luck..
rayman95 said:
the pit HERE...
good luck..
Click to expand...
Click to collapse
Many thanks for all your help, but still dead even with the correct PIT I'm afraid.
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 2340 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I guess this phone is on its way to the Great Home for Expired Technology in the Sky.
Andre
Just read some user not this phone replaced eMMC chip.
From Aliexpress
OK, so have a Galaxy Tab A 10.1, SM T580. An attempt to drop a rom on it failed(not sure why tbh, plugged into the front usb hub instead of unplugging an external HD to free up a usb port, bad rom, not sure), and I am unable to restore it to default. It now goes straight to the 'Use emergency recovery software' screen which doesn't work for that model, and every attempt I have made to utilize Odin has failed, with both 3.09 and 3.13, utilizing XAR-T580UEU2BQF1-20170623075724 files; inevitably it ends up stuck on the 'Initializing' step with no further activity(up to 2 hours anyway).
Requesting some semi-detailed assistance.
Thaser said:
OK, so have a Galaxy Tab A 10.1, SM T580. An attempt to drop a rom on it failed(not sure why tbh, plugged into the front usb hub instead of unplugging an external HD to free up a usb port, bad rom, not sure), and I am unable to restore it to default. It now goes straight to the 'Use emergency recovery software' screen which doesn't work for that model, and every attempt I have made to utilize Odin has failed, with both 3.09 and 3.13, utilizing XAR-T580UEU2BQF1-20170623075724 files; inevitably it ends up stuck on the 'Initializing' step with no further activity(up to 2 hours anyway).
Requesting some semi-detailed assistance.
Click to expand...
Click to collapse
You need to put it in download mode first.
I have done so with every attempt. It still continues to simply hang at 'initializing'.
Thaser said:
I have done so with every attempt. It still continues to simply hang at 'initializing'.
Click to expand...
Click to collapse
Post a screen shot of your download screen and odin log.
ashyx said:
Post a screen shot of your download screen and odin log.
Click to expand...
Click to collapse
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 22 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:26244/000> Odin engine v(ID:3.1301)..
<ID:26244/000> FAIL open(COM:4)
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Thaser said:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 22 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:26244/000> Odin engine v(ID:3.1301)..
<ID:26244/000> FAIL open(COM:4)
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
looks like your baseband got messed up, download this latest firmware for this tablet and install it using Odin
https://samfrew.com/download/Galaxy__Tab__A⑥__/dzjs/LUX/T580XXU4CSA1/T580LUX4CSA1/
zfk110 said:
looks like your baseband got messed up, download this latest firmware for this tablet and install it using Odin
https://samfrew.com/download/Galaxy__Tab__A⑥__/dzjs/LUX/T580XXU4CSA1/T580LUX4CSA1/
Click to expand...
Click to collapse
It remains stuck at initialization, longest time an hour and a half. No response.
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> param.bin
<ID:0/005> userdata.img
<ID:0/005> Home Binary Download
<ID:0/005> Total Binary size: 2658 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
Thaser said:
It remains stuck at initialization, longest time an hour and a half. No response.
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> param.bin
<ID:0/005> userdata.img
<ID:0/005> Home Binary Download
<ID:0/005> Total Binary size: 2658 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
Click to expand...
Click to collapse
use this odin
https://androidfilehost.com/?fid=890129502657595813
also change your usb cable and install Samsung USB drivers from here
https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
zfk110 said:
use this odin
https://androidfilehost.com/?fid=890129502657595813
also change your usb cable and install Samsung USB drivers from here
https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
Click to expand...
Click to collapse
Did the above, still no success. Stuck at initialization
Thaser said:
Did the above, still no success. Stuck at initialization
Click to expand...
Click to collapse
Make sure the cable you are using is short and you see the added message in odin.
Long cables will not work.
If the issue still persists and changing USB port doesn't help then trying another pc is the only option.
ashyx said:
Make sure the cable you are using is short and you see the added message in odin.
Long cables will not work.
If the issue still persists and changing USB port doesn't help then trying another pc is the only option.
Click to expand...
Click to collapse
I will second this. My laptop will not see Odin added at all for most of my devices. And out out of like 6 USB cables only 1 works for Odin downloading but good for everything else
Custom Binaries Blocked by FRP Lock
May I start you over with your diagnostics. Not initializing? Does this mean you cannot boot into recovery, at all? But can get into download mode which you cannot use?
Try booting to recovery and tell me if you see little red letters at the top left that say something about FRP lock. If this is your issue I'll explain what's going on with your device.
There are two types of FRP protection I've seen in this tablet. The first one most of us know of and it can be best described as being able to boot or power on compared to the other one which acts similar to a bootloop and does not power on.
This seems to be a common bug with the current Rootings applied to this device that are using CF-Root or a variation thereof. Samsung insisted that CF-Root shouldn't be used on this device and that's where the problem apparently comes from. The device owner is caught in a bootloop type of mode where the logo comes and goes and somehow accessing recovery is impossible. At the top left side of the screen in fine red letters reads, "Custom Binaries Blocked By FRP Lock. " This apparently shuts off the OEM unlock also leaving you with access to the Bootloader/Downloader, but Odin3 would refuse to flash even the official Firmware. Suddenly the impossible Hard-Brick comes to mind. Fortunately for all of us someone invented Odin3 and Samsung device owners rarely have to deal with a hard bricked device..
Here's what you need.:
Odin3.10 to Odin3,13. Either one works. The following file will give you Odin3.13.
The SM-T580 Binary 4 FRP Unlock file can be obtained here (this is a 1.98GB rar file):
https://drive.google.com/file/d/1Rip0qIGo-GbzFdH55s1vIpe6f1aqYKbD/view
Extract the file, preferably to a folder of its own that you create.
Prep device for flashing (boot to download mode), connect to PC and fire up Odin3. The first section should light up blue means you're connected. Click on AP, go to the extracted 3file and doublr click on the file starting with the word "unlock." Wait til Odin does it's checksum and then you can press start.
This will reset your device to factory!!
Now you're going to want to Bypass the Google Account and remove FRP which is the first FRP I mentioned.
Let me know how it goes for you..