Related
Before marking this as a duplicate, please note that I've gone through almost every thread on this and different possibilities, but nothing had worked.
This morning, I rooted my AT&T Samsung Galaxy S5 (US) using towelroot. The root was successful. Next I downloaded Superuser from the Play Store (not the Chainfire one). It said it needed to update something using recovery mode, but it failed with an error. So, I ignored it and continued using the phone. Next, I downloaded the Google Now Launcher from Android L, to get Material Design. I installed Sliding Explorer from the Play Store to access root files. I also got a simple text edit app. To get Material Design, I needed to change ro.build.version.codename=REL to =L in build.prop. When I did and tried to save, it said access denied, so I changed permissions (oops!) to allow the file to be saved. Still didn't work for some reason so I saved the file as build.prop somewhere else and cut and pasted it in. Then, I rebooted my device and it got stuck on the boot screen with the Samsung Galaxy S5 logo with powered by Android beneath it.
What I've tried:
- I have wiped data, the cached, but there is no advanced option for me to wipe dalvik in the stock recovery for the Galaxy S5.
- When I try to use ADB, my device shows up as sideload and sideloading a ROM goes to 100% but ends up in an error. I cannot run ADB Shell, which ends in error:close.
- Using Odinv3 Build 3.09, I think, gets stuck on connecting to the phone, while Odinv3 Build 1.85, I think, gets fails at Complete(Write) error after something to do with NAND write.
My device drivers are all updated, and I've tried different USB ports, even different PC's. Nothing works. How can I fix this? Thanks!
I am allergic to posts that use Urgent in the title. Obviously you'd like to regain use of your phone ASAP. But how that makes your post more important than someone else's is a mystery. Nevertheless, I'm sure that someone else will be along soon to help you.
If you don't find something more expedient, the most reliable solution for a non-bricked phone is to Odin flash a full, stock firmware image that matches your baseband version.
.
fffft said:
I am allergic to posts that use Urgent in the title. Obviously you'd like to regain use of your phone ASAP. But how that makes your post more important than someone else's is a mystery. Nevertheless, I'm sure that someone else will be along soon to help you.
If you don't find something more expedient, the most reliable solution for a non-bricked phone is to Odin flash a full, stock firmware image that matches your baseband version.
.
Click to expand...
Click to collapse
Problem is, as I said, Odin has errors every time I try to flash, different ports and even different PC's. Maybe I'm not doing it correctly? And I'm sure I get the correct version.
Sorry for the Urgent ?.
tforkan99 said:
Problem is, as I said, Odin has errors every time I try to flash, different ports and even different PC's. Maybe I'm not doing it correctly? And I'm sure I get the correct version.
Sorry for the Urgent ?.
Click to expand...
Click to collapse
You've made some ill advised mods. Now we need more information. Post as many details as you can so that we can spot were the exact problem is.
Paste the exact error from both Odin vetsions here.
Is this originally an ATT phone?
Regular model (i.e. not the special unlocked Developer version)?
Do you know if it the new re-activation lock feature is enabled?
Do you know the phone's baseband /exact firmware version?
Do you have a recent backup?
Are you still able to boot to recovery mode (vol up + home + power)?
Did you ever successfully use Odin with this phone before the bootloop happened?
Perhaps you could remove the Urgent from your title? Edit /Delete > Go Advanced
.
fffft said:
You've made some ill advised mods. Now we need more information. Post as many details as you can so that we can spot were the exact problem is.
Paste the exact error from both Odin vetsions here.
Is this originally an ATT phone?
Regular model (i.e. not the special unlocked Developer version)?
Do you know if it the new re-activation lock feature is enabled?
Do you know the phone's baseband /exact firmware version?
Do you have a recent backup?
Are you still able to boot to recovery mode (vol up + home + power)?
Did you ever successfully use Odin with this phone before the bootloop happened?
Perhaps you could remove the Urgent from your title? Edit /Delete > Go Advanced
.
Click to expand...
Click to collapse
Odin3 v3.09: Stuck on "SetupConnection"
Odin3 v1.85:
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Yes, originally ATT
Regular model
Don't know about re-activation lock
I think the firmware version is the problem. The last update was the one from ATT that added Yellowpages and Lookout in May. Don't know version. I've been download an April build so maybe that's why there is an error. My phone says "SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1" which apparently occurs when downgrading. Maybe if I can get an updated ROM, I can use Odin? And I've seen suggestions to use Odin3 v3.04, but same error with the April build. I can't find the May build anywhere.
Maybe this will work?:http://forum.xda-developers.com/showthread.php?t=2737257 But it's .zip and I can't flash it with Odin.
I have a Kies backup, that's it. This always happens to me . I'm always too lazy to back up my devices.....
Yes recovery mode works and I can get into ADB Sideload.
Nope, never used Odin before. never tried.
I may have something here!
http://forum.xda-developers.com/showthread.php?t=2785185
My firmware is G900AUCU2AND3.
I will update after following the guide.
It works! The only thread that I needed in the world and I couldn't find until after I wiped my device....
Device successfully restored to functionality.
tforkan99 said:
Device successfully restored to functionality.
Click to expand...
Click to collapse
Great to hear.
As I commented at the outset, all you needed to do was restore a full, stock firmware image to recover. Ideally one that matches your existing baseband. Which is essentially what that thread did. Collected all of the pieces to do a 100% reversion to stock.
I've written similar posts for Verizon and TMobile. Was in fact just rewriting the Verizon one for you when you updated the thread. Anyway, good work. Give yourself a pat on that back and promise to make more backups this time.
.
Ego?
fffft said:
I am allergic to posts that use Urgent in the title. Obviously you'd like to regain use of your phone ASAP. But how that makes your post more important than someone else's is a mystery. Nevertheless, I'm sure that someone else will be along soon to help you.
If you don't find something more expedient, the most reliable solution for a non-bricked phone is to Odin flash a full, stock firmware image that matches your baseband version.
.
Click to expand...
Click to collapse
I'm allergic to egocentric attitudes when it comes to answers in a Q & A thread.
tforkan99 said:
It works! The only thread that I needed in the world and I couldn't find until after I wiped my device....
Device successfully restored to functionality.
Click to expand...
Click to collapse
Happy to hear it that worked out for you!
Ok so I'm not sure where to put this thread and please forgive my bad grammar and punctuation if I have any. I already read some threads on this forum about a problem like mine and tried to follow the instructions to get back into my phone, but none of it worked so....
I have a Samsung Go Prime that I bought from Wal-Mart for around $100. I rooted it, and got the message "unauthorized software has been found on your phone, please take it to nearest AT&T etc etc". So I did just that, took it to AT&T, called up Samsung customer care on the phone, and took the phone to some sort of Samsung representative or worker person in Best Buy and nobody seems to be able to help me. I downloaded Odin and Philz Touch and tried to flash that and I kept getting Nand fail. I tried Kies and evidently Sammobile website doesn't seem to have the firmware I need either.
Somebody plleeeaassee help me. I had to pay another $100 just to get another phone so now I feel like I wasted $100 for a phone that wont work now. Maybe I didn't use Odin or Philz Touch firmware properly or didn't follow a certain instruction correctly at some point?
Any help would be massively appreciated.
Kies does work, just go to Tools > Firmware Upgrade and Initialisation and enter the serial number, its gonna say not supported but it works Ive done it
Sent from my SM-G935T using Tapatalk
marioca said:
Kies does work, just go to Tools > Firmware Upgrade and Initialisation and enter the serial number, its gonna say not supported but it works Ive done it
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
I tried that and after clicking for it to start it again said something like "please check the serial number" etc like I put in the incorrect number. I'm pretty sure what I put in was the correct serial number. It was on the sticker under the battery....
model: SM-G530A
SN: R28H30GVPCN
I'm pretty sure your phone is bricked, nand fail was the superbrick error on the i9100 (Galaxy S2 Int) if I'm remembering correctly.
If I'm right, sorry man :/
Anybody know how to fix the nand fail? Anything I can flash to fix it?
When I tried to flash Philz Touch I read in one of the threads that I had to do something like putting the file in some kind of folder (might have been called tar tool) and click a certain batch.bat file. i tried that and nothing happened, so I just loaded the Philz Touch file directly into Odin.
Did I make a mistake somewhere? Is there anything at all that I can do to fix this? If not, then how and where would I find the contact info and address of the manufacturer so I can send the phone in for fixing?
I've had many phones in the past and never had a problem flashing stock and custom on any of them, but i've run into a issue with my sisters J5 2016 that i cant sort out.
As far as i understand she did an OTA update, but it failed halfway. The phone turned off, then wouldn't reboot......thats when she gave to me.
I first tried to access recovery mode, but this was not working.
If you just try to power up normally, then you get the samsung screen, but with the error message in corner.
View attachment 4231349
Only mode working is download mode, but this has an error in the first line that i have never seen before (it actually starts my worry that the internal memory is damaged somehow)
View attachment 4231345
I tried a firmware (single file in the AP box), but failed on pit.
So tried a version of firmware with the 4 separate files, but same error messages, so retried with the separate .pit file included in the flash.....still no joy, same error messages.
View attachment 4231346 View attachment 4231347
I have searched Internet and xda, but can not find this fail, so hoping someone might have a solution, or a way i can prove the internal memory is damaged (maybe theres another piece of software that i can use)
meerameer said:
I've had many phones in the past and never had a problem flashing stock and custom on any of them, but i've run into a issue with my sisters J5 2016 that i cant sort out.
As far as i understand she did an OTA update, but it failed halfway. The phone turned off, then wouldn't reboot......thats when she gave to me.
I first tried to access recovery mode, but this was not working.
If you just try to power up normally, then you get the samsung screen, but with the error message in corner.
Only mode working is download mode, but this has an error in the first line that i have never seen before (it actually starts my worry that the internal memory is damaged somehow)
I tried a firmware (single file in the AP box), but failed on pit.
So tried a version of firmware with the 4 separate files, but same error messages, so retried with the separate .pit file included in the flash.....still no joy, same error messages.
I have searched Internet and xda, but can not find this fail, so hoping someone might have a solution, or a way i can prove the internal memory is damaged (maybe theres another piece of software that i can use)
Click to expand...
Click to collapse
Use Smart Switch. It will automatically download and restore anything needed even if that means a pit file. Give it a try using thr Emergency Recovery option.
Amarius1 said:
Use Smart Switch. It will automatically download and restore anything needed even if that means a pit file. Give it a try using thr Emergency Recovery option.
Click to expand...
Click to collapse
Thank you for trying to help, that is much appreciate, but maybe i didn't make it clear.
The only working option is the Download mode, the Recovery mode doesn't work, so Smart Switch cant connect/see the phone
meerameer said:
Thank you for trying to help, that is much appreciate, but maybe i didn't make it clear.
The only working option is the Download mode, the Recovery mode doesn't work, so Smart Switch cant connect/see the phone
Click to expand...
Click to collapse
Doesn't matter. Just enter your s/n of the phone found behind the battery in the Smart Switch menu saying "Emergency Recovery"
It doesn't specifically need to recognise it or show as connected. Just make sure ur in download mode with cable in and enter the emergency data in the bokes so Smart Switch can force download the stock firmware for your phone
Amarius1 said:
Doesn't matter. Just enter your s/n of the phone found behind the battery in the Smart Switch menu saying "Emergency Recovery"
It doesn't specifically need to recognise it or show as connected. Just make sure ur in download mode with cable in and enter the emergency data in the bokes so Smart Switch can force download the stock firmware for your phone
Click to expand...
Click to collapse
Unfortuantly it was a fail.
Smart Switch downloaded the firmware, but could not install it and displayed a user friendly "Unknown Mode" message (i did check by plugging into odin without switching the phone off and odin showed it was in download mode).
The last message on phone screen reads "mmc: mmc_read fail" (this appeared when Switch came up with its fail message)
Just for clarity I tried all the above multiple times with different leads, and even different laptops and have upgraded my own phone without issues earlier .....so i am near admitting defeat with this J5 6
I do have to say again, thanks for suggesting and helping
meerameer said:
Unfortuantly it was a fail.
Smart Switch downloaded the firmware, but could not install it and displayed a user friendly "Unknown Mode" message (i did check by plugging into odin without switching the phone off and odin showed it was in download mode).
The last message on phone screen reads "mmc: mmc_read fail" (this appeared when Switch came up with its fail message)
Just for clarity I tried all the above multiple times with different leads, and even different laptops and have upgraded my own phone without issues earlier .....so i am near admitting defeat with this J5 6
I do have to say again, thanks for suggesting and helping
Click to expand...
Click to collapse
i dont know my answer will help or not. but i have met some older samsung phones with error in mmc. mmc is a hardware, so if you want to fix you have to change the mmc. maybe you can search for information about mmc on google to make sure.
by the way, why dont you go to service center? your waranty still 0x0
yea like mfmuam mentioned, take it to service centre and most likely they will change your motherboard. If your warranty is unexpired it will be totally free.
mfmuam said:
i dont know my answer will help or not. but i have met some older samsung phones with error in mmc. mmc is a hardware, so if you want to fix you have to change the mmc. maybe you can search for information about mmc on google to make sure.
by the way, why dont you go to service center? your waranty still 0x0
Click to expand...
Click to collapse
Unfortuantly her warrenty expired about 3 weeks ago (almost like the phone knew it had to break away that date ), but yes i have considered hitting ebay and getting her another board. Shes on holiday at moment, so will have to wait to see what she wants to do....... Thanks for advise though :good:
check your android security patch level ( im now in may 1 2017 region XID ) and than you download stok rom same like security patch level in your phone and than flash with odin put in pda.
---------- Post added at 11:44 PM ---------- Previous post was at 11:29 PM ----------
now i've 3 stok rom with different sec patch lvel,if i flash the first stokrom odin says fail like your ss,and then i flash the second stokrom odin says fail too,now im flash the third stokrom and tarraaa its work,because what?the third stokrom i have sec patch lvel in May 1 2017 same like im using my phone now.
pls correct if i wrong
check patch lvl - setting - about device - softwre info
Doni Artjoe said:
check patch lvl - setting - about device - softwre info
Click to expand...
Click to collapse
LOL, how could he check it when there is no system
installed on the phone and the phone cant boot up?
@meerameer
Hello,
please dont give up.
But also please dont be a fool and try repair change motherboard
by yourself.
You could try to re-flash with Heimdall program at Linux-System.
But before you can try to flash in Windows with Odin 3.12 program again.
download the very first firmware rom from samdownloads (they have 4-part rom with pit file)
make sure your battery is at 80% minimum
take out the battery
wait 30 sec
press and hold only power button for 10 sec
put back battery
start phone in download mode with no keys but only usb jig insert
start odin 3.12 and prepare all files but take CSC_(your-code) (do not use the csc_home!), take option with reboot, and also re-partition
connect phone with pc and start odin flash
Another idea would be to flash some custom recovery only and do full wipe
there, and then let Smart Switch emergency repair the phone.
You also have still a chance to get it repaired by the Samsung Service,
for maybe just a small fee. Just write them some short lovely email.
franticfreddy said:
LOL, how could he check it when there is no system
installed on the phone and the phone cant boot up?
@meerameer
Hello,
please dont give up.
But also please dont be a fool and try repair change motherboard
by yourself.
You could try to re-flash with Heimdall program at Linux-System.
But before you can try to flash in Windows with Odin 3.12 program again.
download the very first firmware rom from samdownloads (they have 4-part rom with pit file)
make sure your battery is at 80% minimum
take out the battery
wait 30 sec
press and hold only power button for 10 sec
put back battery
start phone in download mode with no keys but only usb jig insert
start odin 3.12 and prepare all files but take CSC_(your-code) (do not use the csc_home!), take option with reboot, and also re-partition
connect phone with pc and start odin flash
Another idea would be to flash some custom recovery only and do full wipe
there, and then let Smart Switch emergency repair the phone.
You also have still a chance to get it repaired by the Samsung Service,
for maybe just a small fee. Just write them some short lovely email.
Click to expand...
Click to collapse
Thank you Mr Frantic for the nice clear instructions :good:
I actually spend all day fixing hardware on phones and laptops, but thats hardly the rocket science of software like you developers get into. I have done flashing etc since the days of my beloved ACE.
I followed you so far down to 7, as i don't have a separate csc, apart from the csc_home file and for all my searching for a UK separated file firmware i had no luck, only got the combined one
I have tried what you suggested, but am going to try again following you to the letter :highfive:
PS Custom Recovery wouldn't go on, failed on odin at the .pit and theres no recovery (as far as i can tell) on the phone, just displays the J5 6 first screen, with the addition of the info text you get when in Download Mode.
@meerameer
Hello,
you could also try firmware for another country like germany, as the chance is good
that there it will be possible to choose english language in setup.
Maybe you can try this german firmware with csc_dbt.
But you need to be registered to samdownloads and firmware zip has password for encrypt
but its written on the download site (its mostly samdownloads.de)
The csc_home will not erase the internal storage since there is normally no pit file in it.
Because you need to re-pit and format the phone completely, you must use any
csc_(any country) but not csc_home.
Maybe thats why Odin fail for you so many times, because you never got any csc part
with the pit file in it?
You can check the csc part file if there is a pit file in it, you can open csc file with 7-zip.
EDIT:
Anyways, i have attach now the single pit-file for the j5-2016 european version.
So now you can try flash your 4 firmware in Odin with this additional pit file.
In Odin you got the menu for repit, where you can select the pit-file
manually (there is a warning that pit from csc will be used, but since you dont
have any csc file with pit in it, you can give a try.)
Else you still have the option to use SamFirm download program, where
you can download the newest firmware with option in binary nature (that means 4-parts)
and there will be csc file with the pit file already in it,
so you can flash like you already did.
I hope that helps..
franticfreddy said:
@meerameer
Hello,
you could also try firmware for another country like germany, as the chance is good
that there it will be possible to choose english language in setup.
Maybe you can try this german firmware with csc_dbt.
But you need to be registered to samdownloads and firmware zip has password for encrypt
but its written on the download site (its mostly samdownloads.de)
The csc_home will not erase the internal storage since there is normally no pit file in it.
Because you need to re-pit and format the phone completely, you must use any
csc_(any country) but not csc_home.
Maybe thats why Odin fail for you so many times, because you never got any csc part
with the pit file in it?
You can check the csc part file if there is a pit file in it, you can open csc file with 7-zip.
EDIT:
Anyways, i have attach now the single pit-file for the j5-2016 european version.
So now you can try flash your 4 firmware in Odin with this additional pit file.
In Odin you got the menu for repit, where you can select the pit-file
manually (there is a warning that pit from csc will be used, but since you dont
have any csc file with pit in it, you can give a try.)
Else you still have the option to use SamFirm download program, where
you can download the newest firmware with option in binary nature (that means 4-parts)
and there will be csc file with the pit file already in it,
so you can flash like you already did.
I hope that helps..
Click to expand...
Click to collapse
Seems I was having a dumb moment earlier. :silly:
Yes I checked before and the csc contained "J5XNLTE_EUR_OPEN_HIDDEN220M.pit". Thanks for the pit file also, I have checked on file size and they are exactly the same .
I have been questioning myself wondering if had right pit for my model, but screen and sticker (under battery) all say J510FN and all the .pit files i have found are all exactly same file size.
In total I've tried two 4 file firmwares, and 3 single file ones from different regions and release dates. All stop on that pit error before it even gets into the essence of the firmware.
Can you think of any software that can test the mmc , something that might give a bigger hint to whether its a hardware issue?
Hello,
well there is the option to test the mmc with special equipment for experts.
But its difficult and requires knowledge.
Did you try another Odin version?
Maybe Odin 3.09 or 3.10.7 can flash the firmware.
In older version of Odin, only check option for re-pit.
Do not make auto-reboot.
Only check re-partition and f.reset-time.
Do not use BL.
Only use AP+CP+CSC+pit file
When flash is finished, take out battery and put back in,
and restart manually into download mode and flash again the single firmware file
in AP.
I think you have flashed a different firmware version which is not suitable for your pit file
with the 220M addition.
It is very important to use the corresponding firmware files.
Maybe you only use the provided pit file for flash (do not select anything in BL, etc),
just select the pit file in re-pit menu.
franticfreddy said:
Hello,
well there is the option to test the mmc with special equipment for experts.
But its difficult and requires knowledge.
Did you try another Odin version?
Maybe Odin 3.09 or 3.10.7 can flash the firmware.
In older version of Odin, only check option for re-pit.
Do not make auto-reboot.
Only check re-partition and f.reset-time.
Do not use BL.
Only use AP+CP+CSC+pit file
When flash is finished, take out battery and put back in,
and restart manually into download mode and flash again the single firmware file
in AP.
I think you have flashed a different firmware version which is not suitable for your pit file
with the 220M addition.
It is very important to use the corresponding firmware files.
Maybe you only use the provided pit file for flash (do not select anything in BL, etc),
just select the pit file in re-pit menu.
Click to expand...
Click to collapse
Ok tried this, but still no joy.
I think you are certainly correct about what you were saying about the 220m pit file, as that one on the phone screen gives the message "ERROR There is no pit binary".
The pit file you posted gives the error "SECURE CHECK FAIL : PIT"
But the only time i have seen a SECURE CHECK FAIL message before is when i have accidentally in past tried putting completely wrong firmware on a phone , does that fit with what you know ?
ADDITIONAL INFO
My sister told me last night she had in fact taken it to her local indepentant phone shop to see if they could repair, they had no luck.
So i dont know what they did to it in their attempts. I do now have to wonder if they badly failed and now the phone is confused to what pit it should have, hence errors on software that should have fixed it
I've checked with the imei and the serial to make sure I'm defiantly looking for right files (J510FN), also my sister had from new and its never had a replacement board etc.......so im sort of hitting a brick wall.
Seems only option is to drive the 50 miles to the city, where i know there is an authentic Samsung repair store and hand over my life saving for them to look at it and tell me what we already know
Hello,
its really weird, its hard to find out what went wrong with your phone..
Maybe the guys at the generic repair center did the final brick of it.
As you said with the pit file i provided you got another kind of error.
I think there was some mix in bootloader and pit files which were used
at begin error stage 1.
I seen some kind similar problem when people was cross-mixing the 4-part
firmware files (they wanted use older bootloader but newer modem and system
or vice versa).
As there is still shown the samsung official binary but custom system, it is
possible the guys at generic repair center did use Odin and checked the
nand erase all option which is never, never, never a good idea.
Try to flash with this Odin v3.10.7 version
I strongly recommend you get your firmware file with
the SamFirm downloader ,
where you can search for your model SM-J510FN with countrycode BTU,
and check option to download in binary nature , so you will get the 4 parts.
The program requires .NET Framework 3.5 (Microsoft Visual C++ 2008 Redistributable Package (x86) and Microsoft Visual C++ 2010 Redistributable Package (x86) installed)
Here and here.
If you have the firmware there is no need to extra select the pit file for
flashing since its in csc_btu integrated. Just check option repartition, f.reset time.
These files also get checksum, then the secure fail *should* not happen...
If not fail then after finish flash take out battery, wait, put back,
goto recovery and do factory reset..
Im running out of ideas.. , anyways good Luck .
franticfreddy said:
Hello,
its really weird, its hard to find out what went wrong with your phone..
Maybe the guys at the generic repair center did the final brick of it.
As you said with the pit file i provided you got another kind of error.
I think there was some mix in bootloader and pit files which were used
at begin error stage 1.
I seen some kind similar problem when people was cross-mixing the 4-part
firmware files (they wanted use older bootloader but newer modem and system
or vice versa).
As there is still shown the samsung official binary but custom system, it is
possible the guys at generic repair center did use Odin and checked the
nand erase all option which is never, never, never a good idea.
Try to flash with this Odin v3.10.7 version
I strongly recommend you get your firmware file with
the SamFirm downloader ,
where you can search for your model SM-J510FN with countrycode BTU,
and check option to download in binary nature , so you will get the 4 parts.
The program requires .NET Framework 3.5 (Microsoft Visual C++ 2008 Redistributable Package (x86) and Microsoft Visual C++ 2010 Redistributable Package (x86) installed)
Hereand here.
If you have the firmware there is no need to extra select the pit file for
flashing since its in csc_btu integrated. Just check option repartition, f.reset time.
These files also get checksum, then the secure fail *should* not happen...
If not fail then after finish flash take out battery, wait, put back,
goto recovery and do factory reset..
Im running out of ideas.. , anyways good Luck .
Click to expand...
Click to collapse
OK, I have a couple of hours free now, so will try this.
Just like to say again, thanks for all your suggestions, you have been more than helpful :fingers-crossed:
UPDATE
Tried what you suggested, but still no joy.
Tomorrow i need to go near the city, so going to take a detour and take phone to the Samsung Shop. I'll update you on what they have to say about it .
Thanks again
Sad to hear it didnt work
I just was about to say, try what I said but also select the same separate pit file in the pit menu.
Im pretty sure the "right" mix of the right pit file and the corresponding firmware files could
help. But theres so many versions to try and its hard to find especially older firmwares..
Best regards.
franticfreddy said:
Sad to hear it didnt work
I just was about to say, try what I said but also select the same separate pit file in the pit menu.
Im pretty sure the "right" mix of the right pit file and the corresponding firmware files could
help. But theres so many versions to try and its hard to find especially older firmwares..
Best regards.
Click to expand...
Click to collapse
***Final Update***
I managed to get the logic board checked by Samsung and the emmc was corrupted. They wanted £124 to fix it.... Which I declined, as I can a replacement board on ebay for around. £60.
Chances are that the fault was caused by when my sister took it to a local generic repair shop, and might have been ok if she has gone to a more reputable repair shop.
So my note to all is research your repair stores when you have a fault, as the cheapest doesn't always mean the best.
I flashed the firmware from here https://forum.xda-developers.com/tmobile-s7-edge/how-to/6-8-t-mobile-935u-firmware-qe2-t3619151 along with the Tmobile radio via Odin 3.13.1, it failed in Odin and now the phone is stuck on the samsung logo. I used the BL and the AP from the zip, the CP I used from the separate tmobile download link. For the CSC I first tried the CSC that is in the package and when that failed I tried the HOME CSC even that failed. the User data I kept blank both times.. Then I tried it a third time same as above except in the CSC I put the CSC file from the zip and in Userdata I put the Home CSC file, it failed again. Am i doing something wrong ?
Update: I have been trying to flash the stock firmware from samobile, but I am unable to do even that. It keeps failing. I downloaded the firmware from here https://www.sammobile.com/firmwares/...S5BRA1/206887/, extracted it, added just the AP and as per instructions went in to download mode, clicked on start and it keeps failing. In Options only auto reboot and f reset is clicked.
I would really appreciate any help to unbrick this device, it is stuck on an exclamation mark saying " An error has occurred while updating the device software. Use the emergency recovery function in the smart switch PC software". Smartswitch is not recognizing this device saying it's an unsupported device so emergency restore software wont work from there. I can get it into download mode but as I said flashing the firmware via Odin is not working. I can also get it into recovery mode but it keeps endlessly trying to update, fail and loop back to trying to update.
Thanks in advance.
Firstly I would check your use cable, I have a bunch and not all of them work. Secondly, make sure that your phone is being recognized on PC, hence the cable check. and third, make sure you are flashing the correct firmware. You said TMB, but I see you are flashing 3 different company files. Hi back to full G935P firmware , you front need to flash TMB on t, it should be fine cause I have a g935p with TMB sim in it
Anything else I'll be glad to help
bothambhai said:
I flashed the firmware from here https://forum.xda-developers.com/tmobile-s7-edge/how-to/6-8-t-mobile-935u-firmware-qe2-t3619151 along with the Tmobile radio via Odin 3.13.1, it failed in Odin and now the phone is stuck on the samsung logo. I used the BL and the AP from the zip, the CP I used from the separate tmobile download link. For the CSC I first tried the CSC that is in the package and when that failed I tried the HOME CSC even that failed. the User data I kept blank both times.. Then I tried it a third time same as above except in the CSC I put the CSC file from the zip and in Userdata I put the Home CSC file, it failed again. Am i doing something wrong ?
Update: I have been trying to flash the stock firmware from samobile, but I am unable to do even that. It keeps failing. I downloaded the firmware from here https://www.sammobile.com/firmwares/...S5BRA1/206887/, extracted it, added just the AP and as per instructions went in to download mode, clicked on start and it keeps failing. In Options only auto reboot and f reset is clicked.
I would really appreciate any help to unbrick this device, it is stuck on an exclamation mark saying " An error has occurred while updating the device software. Use the emergency recovery function in the smart switch PC software". Smartswitch is not recognizing this device saying it's an unsupported device so emergency restore software wont work from there. I can get it into download mode but as I said flashing the firmware via Odin is not working. I can also get it into recovery mode but it keeps endlessly trying to update, fail and loop back to trying to update.
Thanks in advance.
Click to expand...
Click to collapse
just checking... are you using the edited princecomsy odin? http://d-h.st/gsDA or use the link here https://forum.xda-developers.com/att-s7-edge/help/princes-odin-t3545104
find the correct rom here https://forum.xda-developers.com/sprint-s7-edge/how-to/odin-stock-nougat-firmware-s7-edge-t3569834
just use files from one rom at a time. get good at that first. maybe you are careful but it really looks like you were guessing what goes where at the end of your post.
i just have tips on what helped me. passing along the info and the link.
epikroms said:
Firstly I would check your use cable, I have a bunch and not all of them work. Secondly, make sure that your phone is being recognized on PC, hence the cable check. and third, make sure you are flashing the correct firmware. You said TMB, but I see you are flashing 3 different company files. Hi back to full G935P firmware , you front need to flash TMB on t, it should be fine cause I have a g935p with TMB sim in it
Anything else I'll be glad to help
Click to expand...
Click to collapse
What is your APN settings ? With the sprint firmware I could either get LTE data or calls and text not both at the same time.
Thanks.
bothambhai said:
What is your APN settings ? With the sprint firmware I could either get LTE data or calls and text not both at the same time.
Thanks.
Click to expand...
Click to collapse
Im actually on the G935U rom from jrkruse. If you are on the latest firmware just skip the flashing of the stock U firmware. Just flash eng boot, root it, and follow his process in his t-mobile thread for flashing in flashfire. When aroma starts it asks you what kernel to flash just choose tmobile and it works instantly. But fo APN settings whatbi had was this:
Name
T-Mobile US LTE
Apn
fast.t-mobile.com
Mmsc
http://mms.msg.eng.t-mobile.com/mms/wapenc
Apn Type
default,supl,mms or Internet+MMS
epikroms said:
Im actually on the G935U rom from jrkruse. If you are on the latest firmware just skip the flashing of the stock U firmware. Just flash eng boot, root it, and follow his process in his t-mobile thread for flashing in flashfire. When aroma starts it asks you what kernel to flash just choose tmobile and it works instantly. But fo APN settings whatbi had was this:
Name
T-Mobile US LTE
Apn
fast.t-mobile.com
Mmsc
http://mms.msg.eng.t-mobile.com/mms/wapenc
Apn Type
default,supl,mms or Internet+MMS
Click to expand...
Click to collapse
I managed to flash back the Sprint firmware. I feel the problem is Sprint is probably the only one with an upgraded baseband due to their last update. Both the TMO and U firmwares are based on the 4 baseband G930TUVS4BRA1 and the last Sprint update put it on a 5 baseband G935PVPS5BRA1. That is what is causing for it to fail, I feel. Do you think if I follow the eng.boot method I should be able to overcome the problem ?
bothambhai said:
I managed to flash back the Sprint firmware. I feel the problem is Sprint is probably the only one with an upgraded baseband due to their last update. Both the TMO and U firmwares are based on the 4 baseband G930TUVS4BRA1 and the last Sprint update put it on a 5 baseband G935PVPS5BRA1. That is what is causing for it to fail, I feel. Do you think if I follow the eng.boot method I should be able to overcome the problem ?
Click to expand...
Click to collapse
Okay the problem you are having is that you are actually on bootloader 5 not baseband 5. So that number represents the bootloader and there is no way of downgrading as of yet. Samsung does this thing with fuses on the phone being blown as the bootloader upgrades, well as far as i know from the s8&s8+. So your problem you are having is that you are trying to flash a previous bootloader which isn't going to happen. Flashing the QK5 or the BRA1 firmware will work. Cause it's on bootloader 5. I'd you do what I said a couple posts ago you'll be fine I'm still running the U series tom with tmo kernel installed and I have actually had 0 issues so far. It's been completely solid and everything works, data, sms, Wi-Fi calling, etc...... it works after flashing and boot. With the Sprint tom I got headache after headache and the activating thing is annoying. Just do what I said and you'll see a that what jrkruse then did is probably going to be the only best thing the Sprint variant gets. Try it
epikroms said:
Okay the problem you are having is that you are actually on bootloader 5 not baseband 5. So that number represents the bootloader and there is no way of downgrading as of yet. Samsung does this thing with fuses on the phone being blown as the bootloader upgrades, well as far as i know from the s8&s8+. So your problem you are having is that you are trying to flash a previous bootloader which isn't going to happen. Flashing the QK5 or the BRA1 firmware will work. Cause it's on bootloader 5. I'd you do what I said a couple posts ago you'll be fine I'm still running the U series tom with tmo kernel installed and I have actually had 0 issues so far. It's been completely solid and everything works, data, sms, Wi-Fi calling, etc...... it works after flashing and boot. With the Sprint tom I got headache after headache and the activating thing is annoying. Just do what I said and you'll see a that what jrkruse then did is probably going to be the only best thing the Sprint variant gets. Try it
Click to expand...
Click to collapse
Thanks for your reply. If it is not too much can you please break down the steps a bit more because I don't want to guess and mess it up again and also if you could please kindly point me to the other thread as well so I can download the appropriate stuff from there and read a bit more about it. I am right now unable to use the phone with the sprint firmware on it on TMo, it's super annoying.
Thanks in advance.
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
Don't mind all the instructions there .
1. Download the flashfire zip file and place it in your phone.
2. Download the Ufirm_multi_carrier.zip and unzip it and place the AP or TaR on your phone(the file that's inside the zip)
3. Make sure to use the eng boot and the root provided in this thread and root your phone.(root is a pain but it's worth doing for this room.)
(Note, if you have flashfire stuck on enumerating partitions you can try rebooting or Google flashfire latest app or flashfire 0.73 app and download and install it)
4. In flashfire allow root permissions and select zip and choose flashfire flashable.zip and select mount system read/write,
5. In flashfire select firmware and select the AP or TaR that you downloaded and it should have all partitions checked. Leave it and press the check mark.
6. Make sure that SuperSU is not injected. MNow click on wipe and select dalvik/cache format cache .
7. The order should be firmware then zip then wipe in flashfire.
8. Click the flash tab at bottom in flashfire.
9. In aroma, select the wipe SuperSU image, I think it's selection 2, and the rest of it is entirely up to you for what carrier you are on and so forth.
There is no need to download the Ufirmware stock for Odin because it won't stick because if the new software you have on your phone. Please make sure you know what you are doing to apply these things. These instructions worked for me and if you choose to do otherwise that's on you. I claim no responsibility for bricked devices or what you create . Flashing is a risk that we all take and it's entirely up to you.
Any more questions I'll be glad to answer. Trying to get the oreo working but having issues.
---------- Post added at 10:49 AM ---------- Previous post was at 09:58 AM ----------
May have been the wrong link sorry here is the correct one:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3637375
Did you get it sorted out? Hopefully you are on the rom and haven't bricked your device. I attached a picture so you could see that I am on what I say I am on.
epikroms said:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
Don't mind all the instructions there .
1. Download the flashfire zip file and place it in your phone.
2. Download the Ufirm_multi_carrier.zip and unzip it and place the AP or TaR on your phone(the file that's inside the zip)
3. Make sure to use the eng boot and the root provided in this thread and root your phone.(root is a pain but it's worth doing for this room.)
(Note, if you have flashfire stuck on enumerating partitions you can try rebooting or Google flashfire latest app or flashfire 0.73 app and download and install it)
4. In flashfire allow root permissions and select zip and choose flashfire flashable.zip and select mount system read/write,
5. In flashfire select firmware and select the AP or TaR that you downloaded and it should have all partitions checked. Leave it and press the check mark.
6. Make sure that SuperSU is not injected. MNow click on wipe and select dalvik/cache format cache .
7. The order should be firmware then zip then wipe in flashfire.
8. Click the flash tab at bottom in flashfire.
9. In aroma, select the wipe SuperSU image, I think it's selection 2, and the rest of it is entirely up to you for what carrier you are on and so forth.
There is no need to download the Ufirmware stock for Odin because it won't stick because if the new software you have on your phone. Please make sure you know what you are doing to apply these things. These instructions worked for me and if you choose to do otherwise that's on you. I claim no responsibility for bricked devices or what you create . Flashing is a risk that we all take and it's entirely up to you.
Any more questions I'll be glad to answer. Trying to get the oreo working but having issues.
---------- Post added at 10:49 AM ---------- Previous post was at 09:58 AM ----------
May have been the wrong link sorry here is the correct one:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3637375
Click to expand...
Click to collapse
First up, thanks a lot for your help. After a lot of tries I managed to root the phone or so I thought and that's what the phone said after I ran the root.bat file on the computer and the phone rebooted. I downloaded the flashfire app but when I turned it on it says "root access could not be acquired, are you rooted ?".
After I ran the root.bat file and the phone rebooted the phone clearly said it was rooted. How do I go ahead now ?
bothambhai said:
First up, thanks a lot for your help. After a lot of tries I managed to root the phone or so I thought and that's what the phone said after I ran the root.bat file on the computer and the phone rebooted. I downloaded the flashfire app but when I turned it on it says "root access could not be acquired, are you rooted ?".
After I ran the root.bat file and the phone rebooted the phone clearly said it was rooted. How do I go ahead now ?
Click to expand...
Click to collapse
Get the root from the thread in the link I provided .
In the file there should be something OS something flash the bat file in there it kills all Sprint stuff. Then do the root.batch file and don't worry when it removes all the SuperSU, flashfire, and so on, it's normal okay do on to the painful part......
In the command screen or terminal, it'll say to press a button when your phone has registered on the PC., this is probably where you are messing up. Watch your computer screen until the s7 pips up and watch your phone when it says Allow, MAKE SURE YOU TAP ALLOW! wait for your phone to click off on the PC and then click back on( it takes a while) then press whatever button you like and watch the terminal, if it has errors then it's not rooted if it is rooted then the terminal will close and your phone will reboot. Then proceed to flashfire and do it's thing. For good measure when your phone is booted open SuperSU app first and you'll know if your rooted. Let me know if you need more help
thats pretty interesting being on the binary 5 baseband and binary 4 rom. to clarify, you were on the binary 5 rom and reverted? or were you on the baseband 4 and upgraded just the baseband? thanks for the info.
epikroms said:
Get the root from the thread in the link I provided .
In the file there should be something OS something flash the bat file in there it kills all Sprint stuff. Then do the root.batch file and don't worry when it removes all the SuperSU, flashfire, and so on, it's normal okay do on to the painful part......
In the command screen or terminal, it'll say to press a button when your phone has registered on the PC., this is probably where you are messing up. Watch your computer screen until the s7 pips up and watch your phone when it says Allow, MAKE SURE YOU TAP ALLOW! wait for your phone to click off on the PC and then click back on( it takes a while) then press whatever button you like and watch the terminal, if it has errors then it's not rooted if it is rooted then the terminal will close and your phone will reboot. Then proceed to flashfire and do it's thing. For good measure when your phone is booted open SuperSU app first and you'll know if your rooted. Let me know if you need more help
Click to expand...
Click to collapse
I odined the AP_Nougat_S7_Edge_EngBoot.tar.md5 then ran the root.bat file from Nougat_S7_Root_2_82_All_Carriers_V2 , I chose the options to install the fingerprint fix and install the root without any gpu tweaks. I watched the whole process complete and the cmd prompt close, my phone never asked my permission to ALLOW anything, everything was on the computer. I ran the root.bat from cmd as an administrator and the program ran evidently because it asked me about the fingerprint fix and root with or without tweaks etc. I noticed the phone reboot and there was a notification, the phone was rooted but no SU and flashwire says no root access. I tried it back from square one a couple of tries more right back from flashing stock sprint firmware and trying the whole rooting process again, same results except the next two times the phone doesn't reboot after running the root.bat file. I notice now when the phone boots up there is a sign saying "CUSTOM" beneath the samsung logo on the screen. I don't know where I am going wrong in the process though. I don't know if it is because I am on the binary 5 however I also read somewhere that people have been successful in rooting their binary 5 sprint S7 edges. I have rooted many devices before and installed roms etc, this has been, by far, the most perplexing phone in every which way.
Fownt know what to say,but, you are saying that you are on binary 5 and have successfully downgraded bootloader's by flashing stock vzw firmware which is on binary 4? I don't think downgrading is possible yet?? The way I explained it to you is exactly how I did mine numerous times. I can no longer assist you though because, I kinda bricked my s7edge,
Here's something for everyone to note on a DONT DO!!!!
Do not flash the latest ENG_BOOT AND COMBO FIRMWARE.
I think it was the binary 5 QK1 eng boot and combo I forget, but after flashing back to stock firmware you will get a SBL ERROR in upload mode and let me tell you....... It is not fun at all. I had all the files necessary for unbricking, the complete restore files, I tried the z3x box, I tried octoplus, and I tried the uni-android tools and nothing flashes it over. It's insane. But I ended up sort of destroying the body of the phone but not the internal, so I now have a skeleton phone and no screen or mid frame.
So I wish you luck and probably a final goodbye to Samsung and their insaniy with phones.
epikroms said:
Fownt know what to say,but, you are saying that you are on binary 5 and have successfully downgraded bootloader's by flashing stock vzw firmware which is on binary 4? I don't think downgrading is possible yet?? The way I explained it to you is exactly how I did mine numerous times. I can no longer assist you though because, I kinda bricked my s7edge,
Here's something for everyone to note on a DONT DO!!!!
Do not flash the latest ENG_BOOT AND COMBO FIRMWARE.
I think it was the binary 5 QK1 eng boot and combo I forget, but after flashing back to stock firmware you will get a SBL ERROR in upload mode and let me tell you....... It is not fun at all. I had all the files necessary for unbricking, the complete restore files, I tried the z3x box, I tried octoplus, and I tried the uni-android tools and nothing flashes it over. It's insane. But I ended up sort of destroying the body of the phone but not the internal, so I now have a skeleton phone and no screen or mid frame.
So I wish you luck and probably a final goodbye to Samsung and their insaniy with phones.
Click to expand...
Click to collapse
Bummer about your phone. On a glad note I managed to root and flash my phone and everything works great now. I was taking the hard nerdy way to do it by running cmd as an administrator and having that run the root.bat file. I read somewhere else you could just double click the file and it worked for me . From there on the aroma part was pretty straightforward. I am grateful to you for pointing me in this direction and breaking it down for me, I seriously doubted me being able to achieve this on my binary 5 phone but it turned out to be smooth.
I do wish you the best and thanks once again.
i have the T580 32GB of a friend here, that does not work at the moment (and maybe never again ) - the problem is that on startup it only gives this message in red letter :
could not do normal boot invalid kernel length
Click to expand...
Click to collapse
the only thing i can do is get into download mode - but i fail when i try to install a stock rom via odin - after NAND Write Start!! it times out and gives me a fail.
i already tried a 3 different odin versions and adroid 6.0, 7.0 and 8.01 Stock Rom for SM-T580 but no luck so far.
another problem is my friend does not know what the android version he was on before that hapend - and the tablet has Samsung FRP on.
maybe some of the experts here have an advice what i can try otherwise this tab a is really bricked - furthermore i wonder how this could happen as my friend swears he did not try to put twrp or anything else onto the tablet ....
Have you tried flashing TWRP using ODIN? (AP Slot)
i do not know if flashing twrp is a good idea as i do not know if oem unlock is enabled - and as it does not boot up i cannot switch it on in developer options
ilovebytes said:
i do not know if flashing twrp is a good idea as i do not know if oem unlock is enabled - and as it does not boot up i cannot switch it on in developer options
Click to expand...
Click to collapse
Wouldn't it simply fail if OEM unlocking was disabled? I don't know honestly. I'd try it if no other solutions come up.
ilovebytes said:
i have the T580 32GB of a friend here, that does not work at the moment (and maybe never again ) - the problem is that on startup it only gives this message in red letter :
the only thing i can do is get into download mode - but i fail when i try to install a stock rom via odin - after NAND Write Start!! it times out and gives me a fail.
i already tried a 3 different odin versions and adroid 6.0, 7.0 and 8.01 Stock Rom for SM-T580 but no luck so far.
another problem is my friend does not know what the android version he was on before that hapend - and the tablet has Samsung FRP on.
maybe some of the experts here have an advice what i can try otherwise this tab a is really bricked - furthermore i wonder how this could happen as my friend swears he did not try to put twrp or anything else onto the tablet ....
Click to expand...
Click to collapse
I think you are going about it wrong. Instead of booting to download mode, try booting to recovery mode via Home, Vol Up and Power and then selecting Factory Reset. This is always necessary before you can use download to flash a ROM via Odin and it might make using Odin unnecessary.
of course i tried to get into receovery mode but the problem is i can't - when i do home, vol up and power absolutely nothing happens, i only get into download mode
edit: i believe FRP is the Problem this prevents odin from writing the files to the tablet - as it allways times out with :
Complete(Write) operation failed.
Click to expand...
Click to collapse
what i do not really understand is why FRP does not let odin flash an original samsung firmware ?
[QUOTE what i do not really understand is why FRP does not let odin flash an original samsung firmware ?[/QUOTE]
This sounds more like a binary issue. I have reason to believe you are what's called an FRP Binary Lock. Recovery is usually inaccessable or re-routed and you cannot "seem" to use Odin3 but in fact you can. This issue you apparently are having sounds oddly like some issues I've had on these devices and is often a result of bad Rooting or invalid firmware being installed. This overloads the binaries and puts the device in a locked mode with symptoms of an inaccessible Recovery a difficult to use Odin3 or a bootloop. Most of the time I hear of a notification somewhere of an FRP lock. If this is the situation you are in here is a link to a page of mine that will give you the files to helpfully solve your issue. Let me know if that works or not.
https://forum.xda-developers.com/general/help/custom-binary-blocked-frp-lock-2019-t3979661
Casper Young said:
If this is the situation you are in here is a link to a page of mine that will give you the files to helpfully solve your issue. Let me know if that works or not.
https://forum.xda-developers.com/general/help/custom-binary-blocked-frp-lock-2019-t3979661
Click to expand...
Click to collapse
it sounds like i am in the same situation and i tried your files but it does not let me download them through odin - i also wrote you a pm maybe you find the time to answer me.
i really wonder how this could happen as my friend swears he did never try to flash anything onto the tab, and i really believe him as he absolutely knows nothing about flashing or where to get a firmware and not even how to get into dl mode ....
ilovebytes said:
it sounds like i am in the same situation and i tried your files but it does not let me download them through odin - i also wrote you a pm maybe you find the time to answer me.
i really wonder how this could happen as my friend swears he did never try to flash anything onto the tab, and i really believe him as he absolutely knows nothing about flashing or where to get a firmware and not even how to get into dl mode ....
Click to expand...
Click to collapse
The situation I was suspecting is a "Custom Binaries are Blocked by FRP Lock" to which you would have seen a notification of it in one of 4 ways. Your situation is somewhat similar because you cannot access Recovey and although Download Mode is accessable it appears useless. Your device is not Bricked. A bricked device is unusable in any way and these days most devices can be restored.
You do seem to be having some difficulties that are usually common with binary issues. You can in fact use Odin3 but how is the question. Usually one can flash in the Stock firmware and that returns the device to normal. When it becomes impossible to flash in stock firmware or anything else it seems, to my experiance has always been a Binary issue. I will provide a link to the 4File Official firmware. And instructions for you to properly use it for your needs.
SM-T580 Official Stock Firmware 4Files
https://drive.google.com/open?id=1zvhwUfSRW44V1ZwEsHLRvlh-T0M79ks9
I'll assume you know something about using Odin3. Unzip the file to your desktop. There are 4 files but you'll only use 3 of them. You can use the patched version of Odin3.13B or you can use Odin3.14. Place the files in their respective places. BL, and AP are easy enough to see where they go. Now there is a file labeled CSC and one labeled HOME CSC. You will only use one of them. The CSC file returns your app data to factory settings (it erases everything). The Home CSC file keeps the app data. So it's your choice which one you choose. These are Official Firmware Files so you should be able to flash them in. Should that not work for you my most likely answer would be that your binaries are the issue and that is why you can't as of yet use Odin sucessfully. Does Odin even try to initiate a flash then stalls or does it do nothing altogether?
There are two different Binary files for the SM-T580 that I have. I would suggest using the Binary 4 FRP first. f I recall correctly the Odin3.13B patched version was made for this. Place the file in the AP section and try flashing it. You should get a few gears on the screen turning if it applied, or maybe not. If that fails use the U4 Binary Unlock file. It is only after you flash in the binary files that you can then install the Stock Firmware. It is the overloaded binaries that prevent the use of Odin as you may be experiancing. I am also including the Knox cleaner in case you need to reset it.
SM-T580 Binary files:
Binary 4 FRP Unlock
https://drive.google.com/open?id=1iXrZR2E7m6Ai5InAw8u3lzeLhb3ThRo5
U4 Binaries. This is two files. Flash one at a time using the AP section. They are labeled 1rst or 2nd
1. https://drive.google.com/open?id=1rX_luP_0W4ygdloIr2Gr9TCSfqFyaTK-
2. https://drive.google.com/open?id=1xsw4GVYtNMJhiMXV2cR2jaJvToG_n6Pi
Knox Cleaner: Also flashed in using the AP section of Odin3
https://drive.google.com/open?id=1EolYe9auY9jslYSpSgHoon_YB00D2noV
Good Luck and let me know if this helps or not.
lewmur said:
I think you are going about it wrong. Instead of booting to download mode, try booting to recovery mode via Home, Vol Up and Power and then selecting Factory Reset. This is always necessary before you can use download to flash a ROM via Odin and it might make using Odin unnecessary.
Click to expand...
Click to collapse
Only if they could get into Recovery they may be able to reset it.
I have never once needed to go to Recovery to do "anything" before using Odin3 to flash.
The only time I've had to go there (repetedly) and reset was when trying to get past FRP Google Account Protection. Sometimes it takes out the page I want to get to and I need to reset it to get to it again. This is "not" always neccesary before flashing a ROM which rewrites the device programing.
sorry for double post
@Casper Young
thanks for your help so far, i am gonna try your suggestions on weekend when i have a bit more spare time - hope i can get the tab running again