Stock SM-T580 Bricked, can't restore stock image - Samsung Galaxy Tab A series Questions & Answers

Hello, I tried to use my unrooted, stock Samsung Tab A (SM-T580) and discovered the battery was completely dead. After leaving it on charge, I tried to start it and it would only sit at the Samsung logo. I have tried a soft reboot, hard reboot, pulling the battery, etc. I cannot enter recovery mode, but I can enter download mode. As a precaution, I installed a new battery, but this did not fix the problem. After this, I tried the following while in download mode since it was the only time USB is recognized by my PC:
Samsung Smart Switch
Using the emergency recovery option it says my device cannot be updated
Odin3 v3.12
Using the latest image from SamMobile for the SM-T580 and the XNZ region (I am in the US but this is not available as a region on the site, my device is wifi only so I didn't think it mattered)
I selected the BL, AP, and CSC and clicked start
There is no indication on the tablet that anything is happening
Odin last says "Initialization..."
It stays this way for up to an hour before I stop the operation
I have tried turning on the repartition and nand erase all options, but the result is the same
I have tried different USB cables
Am I missing a step here? My tablet definitely cannot enter recovery mode, I have tried all sorts of methods to try, which I think unfortunately means I can't turn on USB Debugging? Any thoughts on what happened to my tablet?
My Device:
Samsung SM-T580
Current Binary: Samsung Official
System Status: Official
FRP Lock: On
Secure Download: Enabled
Warranty Void: 0
AP SWREV: B:5 K:2 S:3
Edit: Oh, I don't care about any of the data. If that wasn't apparent already from the steps I've taken.
Edit2: The tablet was always stored in my home, which is constantly between 65 and 78 degrees farenheight, the relative humidity can fluctuate from below 50 to over 60% (a reply asked what conditions the tablet was stored, and mentioned corrosion). I would sometimes not use the tablet for an extended period of time.
Thanks!

For example, they could corrode the sockets.
You did not write how long and under what conditions the tablet was stored.

ze7zez said:
For example, they could corrode the sockets.
You did not write how long and under what conditions the tablet was stored.
Click to expand...
Click to collapse
I've updated my post with the conditions my tablet was stored in. If corrosion is a problem, I'm never purchasing a Samsung tablet again because that would be appalling considering how well taken care of it was.

Related

SM-N910F FW problem

Hello everyone!
I need a little advice to fix my softbricked note 4
So here are the facts:
I boght a bricked N910F i tryed different roms from sammobile using odin and twre, more than 7 to be specific, and most of them did t work as it shoul. My imei was the same as on the case but i noticed SN was different in system and knox 0x1.... I got a version of android 6.0.1 to work but there were different little, big problems like not rememering wi fi passwords, fingerprint not working version :null in testing, and often restarts and bootloops after installing different aplications. i tryed many things even repartition with proper pit file, i still had back-up of my efs but considering the serial number was screwed up i gave up trying anything else. I tryed rooting with different methods but everything failed.
I boght another N910F with screen broken but working mainboard and knox 0x0
Swaped the mainboard, tryed samsung kies 1, entered serial and model and it gave me the fw i needed to flash. Tryed flashing with kies and at the middle of transfer it said failed and phone froze, didnt even power on for a while. Tryed again after a few howrs, same rezult with message emmc read fail, and at the bottom emmc write fail.
kies said i need PDAG2/CSCE2 / PHONEE3 CNX
Now, later in the evening i managed to power it on agan and i dont know what to try so i dont screw up with knox
Here are some pictures of my current status:
Current status: cant post picture...
ODIN MODE (HIGH SPEED)
PRODUCT NAME SM-N910F
CURRENT BINARY Samsung Official
System Status Official
REACTIVATION LOCK OFF
Knox 0x0
qualcomm secureboot enable csb
RP SWREV S1 T1 R1 A1 P1
secure download enable
UDC STAR
"Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
What should i try next?
Thanks
Later Edit:
looked up on youtube and found that smart switch can do the work, tryed it and seems it went all the way and installed proper rom without fail. LOL
Morning edit:
So everything worked perfect last night so i left it on fastcharger. In the morning i found it in download mode with dii emmc read fail, could not do normal boot.... After this i have to let it rest a bit without battery, then it boots up ok, works a few minutes then it shuts down and never wake up
faurionutz said:
eMMC from phone is damaged harware
Click to expand...
Click to collapse
I found the only way to keep it working is by preventing it to go into sleep mode. Play music on repeat muted keeps it working
Lucky i have fast chargers and 3 battery
i tried different keep alive apps but they eventually fail and phone dies

Stuck on Samsung Logo Odin and Wipe done

Hi, I recently became a Galaxy S6 Edge+ as a gift, which is stuck on the Samsung Logo (blinking). I am not new to flashing Firmware and Roms (came from the HTC HD2 and Dell Streak 5), but everything I do, I can not come through this. Now I need your help, since it's my first Samsung device. Maybe I have something forgotten?
My device:
SM-G928F with Regional Code AUT (free Switzerland firmware) --> Also Samsung Smart Switch shows me this AUT Version (but it wont recognize it, shows it after typing in the serial)
What have I done:
Samsung Smart Switch does not recognize it.
The last 24 hours I have downloaded the firmware through SamFirm 4 times, I have flashed the phone via Odin about 8 times, after the flashs I have wiped the cache and resettet data (full wipe) through the recovery. One time, the phone came to the android optimatization, but it was stuck on the last app (was 30 minutes on this), after reboot it was stuck on the Samsung logo.
Now I need your help. What can I do further? Do I missed something? Any ideas?
Something strange I noticed: When the phone is off and I plug it in to the wall, the battery drains. I have to put the phone to Download-Mode to charge it. Is it linked to the firmware problem? The charger is original Samsung.
So, I flashed TWRP, the Note7 Deodexed Rom and SkyHigh kernel, but it's the same... any sugestions?
I read about a pit file, what is that? May be this the solution?
What I did the last 3 houers was to test Smart Switch With the mac version, the rescue function did not work, the hole program crashed each time. On the windows version it suceed, but my phone is showing just the blinking Samsung logo. Every now and then it vibrates, but nothing happens, so I am at the start of the problem again. Any ideas?
Next update: I flashed the original firmware with a pit file 3 minutes ago. I learned a lot, learnt that the pit files are the partition-files. Now I'm hoping, that with the new partitions it will boot properly :good: . Stay tuned!
Still the same issue. Please help me
Whenever I start the Recovery, it says "installing system update" and then there is a dead Android, does this matter?
A 4 part firmware with pit file did not help. I downloaded another Firmware from another source, also the same. Now I will do a downgrade and look, if this helps. Pleeeeease, help me!
Infos from the download mode:
Produkt Name: SM-G928F
CA_Type: CA_3
Current Binary: Samsung Official
System status: Custom
Secure Download: Enabled
Know warrenty void: 1 (0x0203)
RP SWREV: B:3 K:0 S:1
Maybe the TWRP Log helps: There are errors in writing, is there something missing? It is the original firmware, with the newest TWRP and SuperSU installed. Still stuck on Samsung (animated) logo.
Listen do you have windows on ur mac i use parallels
but do you have windows anyhoe
Sent from my SM-N920G using Tapatalk
Same here
Hello,
I'm quite new here, but not with flashing.
My son got an S6 Edge plus too, with almost the same problem.
I tried also almost anything, the last few days.
ADB sideload, Odin several versions.
It started out with FRP lock.
After I tried al I could find I think it bricked.
And now it is in the state as described above.
Only first screen and draining the battery if not in download mode.
And when I put it on USB cable it says: "An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
But Smart Switch doesn't recognise the phone!
I can however get the phone in download mode by pushing vol. down, power and home and then vol up.
But in Odin only works: Pit, CP and CSC.
With AP and BL I get errors and fails.
Please help?
For me AP and BL works with Odin. I am a step furhter now. First I flashed with the option: Erase All Nand. Then I installed TWRP and a made a repair for the System and the Caches partitions. With SuperSU installed, and the caches wiped (manual, dalvik and normal caches), it says "Android is starting, Optimizing Apps" and then "Androis is starting, Starting Apps" on a blue screen and when it loads to the end, it is stuck there.
.You get only the first Samsung S6 Edge+ Screen? Then the system files are missing, there is no OS to start (flashed with AP in Odin). Your flash problem sound quite strange. Did you test another cable?
If you want to do it with Smart Switch, the phone should be in download mode. I also had to try it several times. Did you installed the drivers?
@ KatariaMax: I have Windows and Mac PCs, no Parallels. Does it work with Parallels?
So, one problem less. With the Audax rom and kernel, the phone charges normally (but not with Quickcharge), so I don't have to put the phone to download mode. But here is the same problem, after "starting apps" it is stuck. I will do a log from the install, maybe this helps.
@ HugoGroot: Maybe the second post could be the solution for you: http://forum.xda-developers.com/galaxy-s6/help/s6-bricked-t3497687
I read about Sony devices, which are in a bootloop because of the battery. Could this be possible also for Samsung devices? I have bought a battery, just to be sure. Any other suggestions?
I found the problem here: https://talk.sonymobile.com/t5/Xperia-Z3-Compact/Continuous-Restart-and-Optimizing-Apps/td-p/1020656

Killed my phone, still in warranty - or not ? please help !

Hi all !
I have a Samsung A8 (model SM-A800F) which was working great. I ran Kingo Root to try to install Youtube ad free. The next time I restarted it, it didn't load, and restarted in an endless loop to where "Samsung" logo appears (then restarted again). I booted into System Recovery and chose to reset to factory, but it didn't help. Then I tried flash it using Odin in Download mode. I installed the Windows drivers, downloaded the 6.0.1 firmware for Vietnam (where it was purchased), loaded the file into the AP field, and once verified clicked Start. The progress was frozen when reaching mid-way every time I tried, until it said "an error occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software"...
I downloaded Smart Switch and installed in Windows, but the drivers were not able to install correctly, and failed on the component referring to the ID or something... while Modem driver was installed correctly and the phone appeared in Device Manager. Smart Switch didn't recognize my phone and said "unsupported device".
Now I cannot get the phone stay constantly ON, and the screen shuts down and loads in an endless loop, to the "Error occured" screen... When trying to boot to the ODIN Download page, it loads, I press UP for Continue, and then it again shuts down and loads to "Error Occured".
I tried to charge over night but it didn't help. It does the same thing when the phone is connected to the charger...
However it seems that by IMEI it is sill under warranty. I'm not sure if I voided it :/
Here's what the Download mode page says:
ODIN MODE
PRODUCT NAME: SM-A800F
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FAP LOCK: ON
Secure Download: Enabled
KNOX WARRANTY VOID: 0
AP_SWREV: 1
Would appreciate any help, this phone is almost new but now it's dead :/
Your warranty is not voided. Your Knox E-Fuse still intact.
Also this is for S8 not A8 forums.
Paradoxxx said:
Your warranty is not voided. Your Knox E-Fuse still intact.
Also this is for S8 not A8 forums.
Click to expand...
Click to collapse
Thanks,
I just couldn't find any A8 forum, and thought there would be more people here who can help.
Would appreciate any help on this... thanks in advance
wurlitzer99 said:
Thanks,
I just couldn't find any A8 forum, and thought there would be more people here who can help.
Would appreciate any help on this... thanks in advance
Click to expand...
Click to collapse
No worries, your phone is not dead.
Try to find a firmware that correspond to the one you got :
http://updato.com/firmware-archive-select-model?exact=1&q=SM-A800F
and use ODIN : http://dl.sammobile.com/Odin3-v3.12.7.zip
You should be good to go.
EDIT : Also for that error occurred thing, try to be faster than it by starting odin flash before it appears.
Thanks,
The problem is that neither the error nor the Odin page would stay on for more than a few seconds. Once they appear, the screen would go dark after 5-10 seconds and then the "error" page would load again (after being darks for another 10 seconds or so). So I can never have ODIN or Smart Switch connecting to the device (the drivers won't connect in Windows)... making it impossible to upload any firmware.
wurlitzer99 said:
Thanks,
The problem is that neither the error nor the Odin page would stay on for more than a few seconds. Once they appear, the screen would go dark after 5-10 seconds and then the "error" page would load again (after being darks for another 10 seconds or so). So I can never have ODIN or Smart Switch connecting to the device (the drivers won't connect in Windows)... making it impossible to upload any firmware.
Click to expand...
Click to collapse
Could you take a picture of that error ? I've never heard/seen such thing
Hi, thanks for the help !
The error is this:
http://statics1.grupoandroid.com/up...1850.jpg.d2bb2a8b77e4fba5fc6467f3d1547886.jpg
I *think* I have some direction... here's what I did/found:
- I installed Smart Switch on my Mac, and chose "Reinstall Device Driver" from the menu. Then restarted the MAC
- I loaded Smart Switch, and Chose "Emergency Software Recovery and Initialization". Then chose the "Device Initialization" tab
- Added the model number "SM-A800F" and the device's serial number (which are physically written on my device).
Smart Switch determined the firmware version to be used for initialization, as:
PDA:QC3 / PHONEG3 / CSCH4(XXV)
- Smart Switch asked to:
1. Power the device down
2. Load recovery mode by pushing Power+Vol Down+Home, then connect the device to the MAC and choose "Continue" to start the initialization...
The problem/s:
My device won't turn on at all, if I do not connect it to either the charger or the MAC (which acts as a supply source?) - which makes me think the battery is fully drained ? i.e when not connected at all, it won't power on.
But when connected to either the charger or MAC, it would bootloop endlessly. i.e it will load the "error" page mentioned above, shut down itself, reload again, shut down and so on.
(I have to mention, that when I first noticed the bootloop, I reset everything to factory settings, cleared cache etc, and it still bootlooped on the Samsung logo).
If when it shuts down during the loop, I push Power+Vol Down+Home, it would boot to ODIN recovery page, where I can push UP for the Download page, but it will still reboot and will again load into the "error" page, which will again reboot endlessly. If I take the charger off the device, it powers off and won't load with any combination of button push.
I also cannot just make it shut down when the charger is connected, using any of the possible button combinations...
I wonder:
- Is there there's a problem which prevents the battery from being charged at all ?
What's strange is that the original problem which made me get into this whole issue, was that is was endlessly booting to the "samsung" logo - but when I booted to System Recovery or Download/ODIN modes, it stopped rebooting endlessly and stayed on... it was also showing the charging indication when powered off... the battery was charging well ever since.
- Why would it bootloop when connected to the charger ? is it possible that the bootloader went bad during my attept to install firmware using ODIN ? I know it always went through the boot.img and recovery.img successfully and only got stuck at about 50% when installing system.img...
I think the current bootloop problem began only once the battery ran out of power. But why wouldn't it charge at all now ??? It's supposed to still charge in this state, isn't it ?
wurlitzer99 said:
Hi, thanks for the help !
The error is this:
http://statics1.grupoandroid.com/up...1850.jpg.d2bb2a8b77e4fba5fc6467f3d1547886.jpg
I *think* I have some direction... here's what I did/found:
- I installed Smart Switch on my Mac, and chose "Reinstall Device Driver" from the menu. Then restarted the MAC
- I loaded Smart Switch, and Chose "Emergency Software Recovery and Initialization". Then chose the "Device Initialization" tab
- Added the model number "SM-A800F" and the device's serial number (which are physically written on my device).
Smart Switch determined the firmware version to be used for initialization, as:
PDA:QC3 / PHONEG3 / CSCH4(XXV)
- Smart Switch asked to:
1. Power the device down
2. Load recovery mode by pushing Power+Vol Down+Home, then connect the device to the MAC and choose "Continue" to start the initialization...
The problem/s:
My device won't turn on at all, if I do not connect it to either the charger or the MAC (which acts as a supply source?) - which makes me think the battery is fully drained ? i.e when not connected at all, it won't power on.
But when connected to either the charger or MAC, it would bootloop endlessly. i.e it will load the "error" page mentioned above, shut down itself, reload again, shut down and so on.
(I have to mention, that when I first noticed the bootloop, I reset everything to factory settings, cleared cache etc, and it still bootlooped on the Samsung logo).
If when it shuts down during the loop, I push Power+Vol Down+Home, it would boot to ODIN recovery page, where I can push UP for the Download page, but it will still reboot and will again load into the "error" page, which will again reboot endlessly. If I take the charger off the device, it powers off and won't load with any combination of button push.
I also cannot just make it shut down when the charger is connected, using any of the possible button combinations...
I wonder:
- Is there there's a problem which prevents the battery from being charged at all ?
What's strange is that the original problem which made me get into this whole issue, was that is was endlessly booting to the "samsung" logo - but when I booted to System Recovery or Download/ODIN modes, it stopped rebooting endlessly and stayed on... it was also showing the charging indication when powered off... the battery was charging well ever since.
- Why would it bootloop when connected to the charger ? is it possible that the bootloader went bad during my attept to install firmware using ODIN ? I know it always went through the boot.img and recovery.img successfully and only got stuck at about 50% when installing system.img...
I think the current bootloop problem began only once the battery ran out of power. But why wouldn't it charge at all now ??? It's supposed to still charge in this state, isn't it ?
Click to expand...
Click to collapse
Hmmm, the thing is, the battery charging process is actually held on some kind of "mini-boot" OS on Samsung I believe, where the phone boots into a certain state, with that said mini-os to display the battery charging info and this kind of things.
My guess is that you *might* have, or more likely your phone did corrupt the flash at some point for x or y reason.
What I'd do is :
Let the phone on a charger a whole night doing its bootlooping thing. And see from there if the battery would charge.
I'd try another computer with Odin just to be sure something is not triggering the reboot process at some point.
And if all the above fails, you still have the warranty, so beside time, you would not be losing any money..
I'm going to write a long post. But I believe it will help a lot of people having a similar problem.
Long story short - problem solved! but it took much of my nerves (and time).
I'll start with the "warranty". The so-called Samsung "warranty" which basically worths nothing!
Calling Samsung international service center, they "informed" me that I must contact Samsung Vietnam, where I bought the device, although I am not there anymore... Needless to say the local dealer in my country refused to take care of this situation, saying Samsung's warranty is regional based, rather than international... which means, only Samsung in the original country where the device was sold in, are responsible for the warranty (and therefore repair!). I had a chat with a Samsung Vietnam representative, who just kept saying "I'm sorry", and refused to let me sent the device out to them for repair! asking me to "bring it to them", although I noted him a few times that I bought it as a tourist and I am not in Vietnam anymore.... Thank you Samsung !! From now on every traveler in the world will know they basically have NO WARRANTY if they buy any Samsung device in a "foreign" country while traveling abroad!
Now for the solution:
I started by letting the device staying connected to the charger overnight, which didn't help. With the OS now installed, I realize that the battery was NOT CHARGED ! it was completely drained, although connected to a charger for long hours... So, know from now on that if your boot data is corrupted, it may cause the device NOT TO CHARGE THE BATTERY at all. Luckily, my desktop PC could use the device while connected to it although the battery was empty, until the problem was sorted out. I did get a crash on my MAC tough (Log said it was USB related), while using Smart Switch, so one option is that it could not supply enough power to the device to keep it keep working at all, or working correctly... So my suggestion is to use a desktop Windows PC in this case, which can potentially provide more power to a device with 0% battery power.
After scratching my head, and considering removing the front panel for replacing the battery (a very risky procedure) I decided to keep on investigating....
I followed a youtube video who suggests that you should install Smart Switch on a PC, choose "reinstall driver" from the menu, restart the PC, then use Emergency Recovery and Initialization, enter the phone model number in the search box (as appearing on the back of the device) , and once it recognizes the model, also to enter its serial number. Here's the video:
https://www.youtube.com/watch?v=1yXQUFrEWg4
This basically brings up a popup message saying Smart Switch detects a compatible firmware for this device, and is about to download and install it. It then asks the user to do the Power+Vol Up+Home push combination trick + pushing UP once the page is loaded in order to "Continue" and bring up the ODIN Download screen, which worked for me if did that as soon as the device shuts down (in the middle of the bootloop). As I couldn't make it load at all with no charger connected, I had it connected to the charger, and once I saw the Smart Switch message asking to do the push combination, I quickly connected it to the computer using another cable which was already connected to the PC USB port on its other end.
Somehow, I could at last make Smart Switch finally start downloading the firmware from the web, and the device again disconnected (bootlooped), but luckily Smart Switch didn't care about it disconnecting, and kept on downloading the firmware. At about 85% of the progress bar state, I could find the downloaded firmware on the temp folders, which are described in this thread:
http://forum.gsmhosting.com/vbb/f777/samsung-firmware-download-belongs-his-serial-number-2038404/
I had to make sure it wasn't still downloading, and watched the "last modified" state of the file to make sure they are not being downloaded anymore. CAUTION: although the AP was not downloading anymore, I know it was probably not good as ODIN couldn't verify it when I tested it. USE ONLY SMART SWITCH !
I quickly copied the folder to which the app extracted the BL and AP files it downloaded, and finally had an officialy bootloader (BL) image, which I could use in ODIN in order to reupload a correct, "official" bootloader to the device....
I hoped the device won't bootloop in the middle, but luckily ODIN was fast enough to send the image successfully, with a "PASSED" status, and the device booted with a nice "Samsung" logo directly to a System Recovery page!
What I exactly did, was loading ODIN, then loading ONLY the BL file into the BL field in ODIN, having it verifying it, and once verified I connected the device, and as soon as ODIN recognized it, pushed START. It managed to upload the image into the device in a few seconds! It seems then, that the bootloop was not caused by a bad battery, but as a result of a corrupt upload of an AP image through ODIN - or because I possibly was using an incorrect version when I tried to upload an AP files to the device on my first attempt to flash it.
Note that I did search for the correct, compatible AP file, by country and model (on Sammobile) but it didn't' work (stuck at 50% in ODIN) ! so I really suggest everyone TO ONLY USE SMART SWITCH if they want to be sure that the correct firmware is being used, and avoid similar situations...
I then deleted the temp files from the PC (the actual ones which were in the temp folder), reinstalled the drivers from inside Smart Switch (just in case), booted the device to Download mode (WHICH DIDN'T BOOTLOOP this time), let Windows installing the drivers (checked in Device Manager), then restarted the PC, and ran Smart Switch again. I repeated the procedure of loading Emergency and Initialization, entering the model and serial number, having it fully downloading the firmware (again) from the web, and installing the firmware into the device. This time it completed the process, and I finally had the device installing and booting into a fresh version 6.0.1 of Android!
Hope it helps!

Test Device and aboot -2???

Ok so the phone i have is/was actually a G935T, and had G935T firmware (BRC1) even though it says G935A on the board inside the phone. I tried to flash a different firmware, foolishly without turning off FRP, or turning on OEM, yeah im dumb. I ended up being stuck with the SBL error upload mode and couldnt even get back to download mode no matter how many times i tried, eventually i learned about EDL mode and took the phone apart and shorted the TP and re programmed the phone etc. and got it back to download mode.
Everything i flashed would always be successful in Odin, however nothing would ever boot past the looping S7 edge boot screen and recovery on every single firmware would also loop and ultimately give me kernel panic errors. i began to suspect that maybe i left something unplugged inside so i took it apart again and tried to keep the heat shield pressed down a bit more (since i had to open it up to access the test point) as i assembled the phone back together. No more kernel panics, but the boot looping was still present. I have tried G935T, A, P, V and U firmware and all of them do the same thing. Ive used the proper PIT files.
To make things worse, i flashed Oreo without realizing that i was putting my bootloader in handcuffs. To make things even MORE worse, i used a tool which claimed to convert an odin archive to be ADB enabled. now my device boots and says S7 edge etc, but then immediately goes to SBL error upload mode. Recovery still loops. Whats interesting though, is that since i used the converted archive, my device says exactly this in download mode:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-G935A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: ON
WARRANTY VOID: 0xffffffff (0x0)
QUALCOMM SECUREBOOT: ENABLE fffffffe
RP SWREV: B-2 (-2, -2, -2, -2, -2) K8 S8
RP SWREV: TEST DEVICE
SECURE DOWNLOAD: ENABLE
IDDQ: G(25), S(7) mA
CPU SERIAL NUM : 0X1b9cea13
Fused open loop voltage: 1030mv
RPMB PROVISIONED
Any help would be much appreciated. Its going on nearly a month now trying to get this thing to work. I dont care about warranty, i dont care about knox i just want my phone to work....i cannot find any information about test device, how to go back to system status official or how to properly reformat all partitions that effect FRP or whatever the hell is locking me out of it. Also i am now not even able to flash ANY firmware because it keeps failing saying something about aboot fused -2 and none of the firmware i have will successfully flash. Im stumped.
I called a repair shop today and they want to charge me $30.00 to flash it with what they have. That seems a bit high to be honest. Should only take about 10 minutes right?
How to change Fuse -2 -> 1
Elem3nt0 said:
I called a repair shop today and they want to charge me $30.00 to flash it with what they have. That seems a bit high to be honest. Should only take about 10 minutes right?
Click to expand...
Click to collapse
Fuse -2 happened to my T380 Tab A tablet when I flashed wrong aboot and boot in the same TAR package.
So steps to fix it:
find the right combination firmware;
unzip it with 7zip archiver;
download TAR_MD5_PACKAGER;
open folder with unzipped comb_firmware and delete all files below from it:
-aboot,
-apdp,
-boot,
-devcfg,
-msadp,
-rpm,
-sbl1,
-tz.
copy all files what left to TAR_MD5_PACKAGER\parts;
start TAR_MD5_PACKAGER and press 1 to make tar file;
flash this file with Odin as AP;
now the fuse should switch to 1;
next flash the full combination file or stock firmware.
FUSE Number stands for software version,
samsung has protection against downgrading software,
So once you flashed firmware with number 2 in it, the device will change the fuse to 2 and after that
you will not able to flash anything less than with number 2 and so on.
S7 edge up and running
Dude thanks a lot!!! I read through multiple threads. Some more technical than others but this one was plain simple and it worked. Some of the files I deleted were a bit different, but hey, it got bit to work. One other thing for anyone experiencing the same issue, just look for a combination file matching your phones actual bootloader. Once you find it, just start deleting the files Odin is indicating are not letting the flash complete. In my case, files: hyp.mbn, pmic.elf, emmc_appsboot.mbn, xbl.elf. once I deleted those files I was golden. :laugh::laugh::laugh:
HI
I have smiliar problem.
I have a problem with a friend's phone. they give S7 Edge to the service because he have problem witch turn on telephone
When he received the phone displays an error: "An error has occured while updating software.. Use the Emergency recovery function in the Smart Switch PC"
Smart Swhitch doesn't recognized the phone
I try update firmware with odin but when i flashing i have error: SV rev. check fail(bootloader) Device: -1 Binary: 6
I try to insert TWRP and i have next error: Custom binary (recovery) blocked By FAP lock
I can not insert custom recovery witch TWRP, and I don't have any idea what official rom was uploaded last time :/
Sorry for my English :/

I DONT KNOW which direction to go

Ok so the phone i have is/was actually a G935T, and had G935T firmware (BRC1) even though it says G935A on the board inside the phone. I tried to flash a different firmware, foolishly without turning off FRP, or turning on OEM, yeah im dumb. I ended up being stuck with the SBL error upload mode and couldnt even get back to download mode no matter how many times i tried, eventually i learned about EDL mode and took the phone apart and shorted the TP and re programmed the phone etc. and got it back to download mode.
Everything i flashed would always be successful in Odin, however nothing would ever boot past the looping S7 edge boot screen and recovery on every single firmware would also loop and ultimately give me kernel panic errors. i began to suspect that maybe i left something unplugged inside so i took it apart again and tried to keep the heat shield pressed down a bit more (since i had to open it up to access the test point) as i assembled the phone back together. No more kernel panics, but the boot looping was still present. I have tried G935T, A, P, V and U firmware and all of them do the same thing. Ive used the proper PIT files.
To make things worse, i flashed Oreo without realizing that i was putting my bootloader in handcuffs. To make things even MORE worse, i used a tool which claimed to convert an odin archive to be ADB enabled. now my device boots and says S7 edge etc, but then immediately goes to SBL error upload mode. Recovery still loops. Whats interesting though, is that since i used the converted archive, my device says exactly this in download mode:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-G935A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: ON
WARRANTY VOID: 0xffffffff (0x0)
QUALCOMM SECUREBOOT: ENABLE fffffffe
RP SWREV: B-2 (-2, -2, -2, -2, -2) K8 S8
RP SWREV: TEST DEVICE
SECURE DOWNLOAD: ENABLE
IDDQ: G(25), S(7) mA
CPU SERIAL NUM : 0X1b9cea13
Fused open loop voltage: 1030mv
RPMB PROVISIONED
Any help would be much appreciated. Its going on nearly a month now trying to get this thing to work. I dont care about warranty, i dont care about knox i just want my phone to work....i cannot find any information about test device, how to go back to system status official or how to properly reformat all partitions that effect FRP or whatever the hell is locking me out of it. Also i am now not even able to flash ANY firmware because it keeps failing saying something about aboot fused -2 and none of the firmware i have will successfully flash. Im stumped.

Categories

Resources