I've searched, I've tried but to no avail have I been able to fix my poor note 8..and I'm hoping someone can help!
I HAD a stock 4.4.2 Note 8 (AT&T version I-467) running, and I went with the Kingroot method to root. The device rooted but ran like a dog, and in my infinite wisdom did a wipe/reset to see if that would help.
Now here is where I stand:
1) The device boots to a screen saying unauthorized firmware
2) I can get to download mode (power+vol. down+Home)
3) I can NOT get to the screen with (power+col. up+Home)
I have tried Kies, and it won't take the serial number/model number, and Odin can only seem to flash the boot loaders. I have tried 4 different ROM's from samsung (with different international codes), and none of them are able to update the system (they all fail at about 90%). I've tried the all in one toolkit, and since I can't enable USB debugging at this point, it never recognizes the device as attached.
I've tried manually flashing with Odin TWRP, Phils, and stock recovery,(in the hopes of getting one to take so I could load a new ROM from SD card) and they all fail as well.
When I split any of the system images I can load a boot loader file from them, and it succeeds, but everything else fails.
Can anyone point me in the right direction, or am I completely hosed?
Sparkinman said:
I've searched, I've tried but to no avail have I been able to fix my poor note 8..and I'm hoping someone can help!
I HAD a stock 4.4.2 Note 8 (AT&T version I-467) running, and I went with the Kingroot method to root. The device rooted but ran like a dog, and in my infinite wisdom did a wipe/reset to see if that would help.
Now here is where I stand:
1) The device boots to a screen saying unauthorized firmware
2) I can get to download mode (power+vol. down+Home)
3) I can NOT get to the screen with (power+col. up+Home)
I have tried Kies, and it won't take the serial number/model number, and Odin can only seem to flash the boot loaders. I have tried 4 different ROM's from samsung (with different international codes), and none of them are able to update the system (they all fail at about 90%). I've tried the all in one toolkit, and since I can't enable USB debugging at this point, it never recognizes the device as attached.
I've tried manually flashing with Odin TWRP, Phils, and stock recovery,(in the hopes of getting one to take so I could load a new ROM from SD card) and they all fail as well.
When I split any of the system images I can load a boot loader file from them, and it succeeds, but everything else fails.
Can anyone point me in the right direction, or am I completely hosed?
Click to expand...
Click to collapse
+1 on that, I'm stuck in an exact same situation. No help from Samsung either. After rooting with Kingroot my tab started acting like crazy with flickering screen and random reboots, did exactly like you did.
There are many with similar issue and as per my research most of them have given up. Getting a system image dump from a rooted tab running 4.4.2 might be the only way out. Unless of course Samsung/AT&T decides to release full odin flashable image.
I was in a similar situation from trying to fix a eff problem and took my sgh-i467 to a Samsung Experience Center located in many Best Buys and they fixed it free of charge. They were not able to fix my issue with a corrupted EFF file that is keeping my 4G from working though as I had hoped. If you have a Best Buy around with the Samsung Kiosk in it I would give it a try. I ended up trying a few different ones to fix the eff issue and some of the employees at the Samsung centers were about as smart as a head of cabbage (they laughed at me when I said my Note 8 was the issue and said "you can't have a Note 8 the Note 5 just came out") but some were at least helpful and listened when I told them they have the tools to fix my tab (reflash it back to life) and they did. Hopefully they can help you.
man Im in the same exact situation.. And I cant seem to find any help anywhere. I cant locate a stock 4.4.2 kit kat odin flashable file anywhere for the n5120
Sparkinman said:
I've searched, I've tried but to no avail have I been able to fix my poor note 8..and I'm hoping someone can help!
I HAD a stock 4.4.2 Note 8 (AT&T version I-467) running, and I went with the Kingroot method to root. The device rooted but ran like a dog, and in my infinite wisdom did a wipe/reset to see if that would help.
Now here is where I stand:
1) The device boots to a screen saying unauthorized firmware
2) I can get to download mode (power+vol. down+Home)
3) I can NOT get to the screen with (power+col. up+Home)
I have tried Kies, and it won't take the serial number/model number, and Odin can only seem to flash the boot loaders. I have tried 4 different ROM's from samsung (with different international codes), and none of them are able to update the system (they all fail at about 90%). I've tried the all in one toolkit, and since I can't enable USB debugging at this point, it never recognizes the device as attached.
I've tried manually flashing with Odin TWRP, Phils, and stock recovery,(in the hopes of getting one to take so I could load a new ROM from SD card) and they all fail as well.
When I split any of the system images I can load a boot loader file from them, and it succeeds, but everything else fails.
Can anyone point me in the right direction, or am I completely hosed?
Click to expand...
Click to collapse
please help me i need de 4 files repair from this tablet
Try the forum thread started by djjiz, https://forum.xda-developers.com/galaxy-note-8-0/help/i467-4-4-2-t3537302... He posted the files and yes I was able to bring back my previously bricked AT&T Note 8.
Related
So I have an Att Note 2, which is bricked or soft bricked. I am a very rookie Android guy when it comes to modifying or hacking. I did root my Note 2 with Cyanogenmod. However, I missed S Note and the use of my S Pen so I researched a bit to get back to stock with the use of Odin and stock roms found on the net. I was successful, and actually amazed it worked. Long story short, a few days after that, an OTA update hit my phone, didn't even think about it and began the download. The phone downloaded the update, and rebooted to complete the install. The problem is, during reboot, the phone got stuck on the "Samsung Galaxy Note II" screen. I researched a bit online, and everyone said get to recovery mode and do a few things. Problem is, I can't get into recovery mode, I can only get the screen described above, and the download screen, THAT IS ALL. Looked a bit more online and attempted to flash various stock roms with Odin. Some were successful, Odin passed, and the phone would get stuck on the Note II screen again, and would not boot into recovery mode, same issue with only being able to access download mode. The unsuccessful flash attempts got me to screen informing me that Kies needs to be used to update my firmware. Kies showed a recovery code, which was downloaded, but unsuccessful. It would download all the way, but at the end of install, it would fail. Funny thing is it would work enough to get me back to the ability to get into download mode. I just want my Note 2 working again. Is there any way to wipe my phone completely clean, and start over? Or is there any way to even re-root it, or flash any sort of rom on there, just so I can use the damn thing? I need some help by you pros out there ! Please!
titostats said:
So I have an Att Note 2, which is bricked or soft bricked. I am a very rookie Android guy when it comes to modifying or hacking. I did root my Note 2 with Cyanogenmod. However, I missed S Note and the use of my S Pen so I researched a bit to get back to stock with the use of Odin and stock roms found on the net. I was successful, and actually amazed it worked. Long story short, a few days after that, an OTA update hit my phone, didn't even think about it and began the download. The phone downloaded the update, and rebooted to complete the install. The problem is, during reboot, the phone got stuck on the "Samsung Galaxy Note II" screen. I researched a bit online, and everyone said get to recovery mode and do a few things. Problem is, I can't get into recovery mode, I can only get the screen described above, and the download screen, THAT IS ALL. Looked a bit more online and attempted to flash various stock roms with Odin. Some were successful, Odin passed, and the phone would get stuck on the Note II screen again, and would not boot into recovery mode, same issue with only being able to access download mode. The unsuccessful flash attempts got me to screen informing me that Kies needs to be used to update my firmware. Kies showed a recovery code, which was downloaded, but unsuccessful. It would download all the way, but at the end of install, it would fail. Funny thing is it would work enough to get me back to the ability to get into download mode. I just want my Note 2 working again. Is there any way to wipe my phone completely clean, and start over? Or is there any way to even re-root it, or flash any sort of rom on there, just so I can use the damn thing? I need some help by you pros out there ! Please!
Click to expand...
Click to collapse
Download the latest kies from the samsung website.. and then open tools and then firmware update and initialization.. pull out the battery and type the model number and serial number kies asks.. follow the instructions.. your phone will be fine..
Sent from my GT-N7100
titostats said:
So I have an Att Note 2, which is bricked or soft bricked. I am a very rookie Android guy when it comes to modifying or hacking. I did root my Note 2 with Cyanogenmod. However, I missed S Note and the use of my S Pen so I researched a bit to get back to stock with the use of Odin and stock roms found on the net. I was successful, and actually amazed it worked. Long story short, a few days after that, an OTA update hit my phone, didn't even think about it and began the download. The phone downloaded the update, and rebooted to complete the install. The problem is, during reboot, the phone got stuck on the "Samsung Galaxy Note II" screen. I researched a bit online, and everyone said get to recovery mode and do a few things. Problem is, I can't get into recovery mode, I can only get the screen described above, and the download screen, THAT IS ALL. Looked a bit more online and attempted to flash various stock roms with Odin. Some were successful, Odin passed, and the phone would get stuck on the Note II screen again, and would not boot into recovery mode, same issue with only being able to access download mode. The unsuccessful flash attempts got me to screen informing me that Kies needs to be used to update my firmware. Kies showed a recovery code, which was downloaded, but unsuccessful. It would download all the way, but at the end of install, it would fail. Funny thing is it would work enough to get me back to the ability to get into download mode. I just want my Note 2 working again. Is there any way to wipe my phone completely clean, and start over? Or is there any way to even re-root it, or flash any sort of rom on there, just so I can use the damn thing? I need some help by you pros out there ! Please!
Click to expand...
Click to collapse
Try flashing a recovery for ur device with Odin, not a ROM, just flash twrp recovery with Odin, after u flash the recovery u will be able to access recovery and flash a stock ROM through twrp. I think what happened to u is when u flashed the update it tried to right over the unlocked bootloader which caused the soft brick, try flashing the recovery for ur device and if that doesn't work try the above posters way...
Sent from my Nexus 5 using XDA Premium 4 mobile app
Hello, I managed to soft brick my phone while overseas and am writing this message at 2:00am in the morning (at least in this time zone) after two days of trying to fix it. Some background info--I'm usually based in the U.S., have a Samsung Galaxy S6 edge+ with service from T-mobile. Have never rooted or modified the phone in any way. I'm using a macbook pro laptop (running a windows virtual machine/vmware, on the mac) on this trip.
While on this current trip to Asia (currently in the Philippines) (much to my surprise it seems like the phone was getting 4G data here), I accidentally bumped the "yes" button on t-mobile's persistent OTA upgrade request box and the phone started a OTA upgrade, I assume to Android 6.0.1. I kept an eye on the phone as it went through various stages of progress in the upgrade. didn't see any error messages. It eventually restarted, got to the T-mobile screen, and got stuck there. That was two days ago. I've done quite a bit since that time to try to figure out what went wrong, searched all over online to find potential solutions. it goes without saying if there is any way possible i need to recover many important files on the device, so a reset is the option of last resort.
Long story short, seems like the farthest I can get on the phone is to Android Recovery mode, or the download screen. I installed the android tools and have "adb" working from the mac command line. Bad news is, it looks like I didn't have USB debugging mode activated on the phone, now I can't see any possible way to activate usb debug mode because the phone just won't boot past the t-mobile screen. I can get adb to detect the phone for a moment if I select "apply update from adb" on the recovery mode screen but that's about it, haven't been able to issue any other commands to the phone through adb other than detect and sideload.
tried to reload the android image...via command line adb sideload G928TUVU2DPD1 but get error messages about failure to verify (i think), anyways adb sideload wasn't happening. I installed Odin on my windows VM, attached the usb bridge from the mac to the windows vm and Odin was able to see the device. I was able to successfully push G928TUVU2DPD1 to the phone's download mode, both Odin and phone seemed happy about the file transfer, the phone went through a install process, restarted, with the exact same result as when the OTA update finished - phone stuck at the t-mobile screen after reboot.
I tried to load TWRP to the phone with hopes to run backups, and was actually able to transfer TWRP to the phone using Odin, yet TWRP wouldn't install -- the phone complained of the unauthorized binary. i guess the phone has to be rooted first or something else needs to be flashed to defeat the binary check, haven't tried that yet.
So I'm stuck with a soft bricked phone for now, yet instinct tells me with Odin working and talking to the phone, I should be able to install -something- that will get me back in business...that's why I'm posting this message, to ask for help as it seems like this group is the go to place for this type of specific info.
i am not at all familiar with custom android work yet have been active with tech stuff for the greater part of my life, plenty of coding and experience dating back years and have done dev work in most of the popular languages, very comfortable with command lines, log files and so forth...just never had a reason to mess around at a low level with my android phone until the past 48 hours, so i'm not really familiar. does anyone have any ideas? as a next step i'm thinking of trying to push a downgrade to the phone through Odin which I suppose would be Android 5.1.1 , although I haven't yet located binaries that feel exactly right for t-mobile and s6 edge+ ... sigh, this has been quite a time consuming way of learning the bricked phone recovery process..
:good:
thanks in advance for any ideas or help on this...it's quite disturbing to be on a business trip with no phone, and the past 6+ months worth of not backed up (gulp) data still sitting on the device (hopefully)..
here's some data from the Android Recovery screen:
6.0.1/MMB29K.G928TUVU2DPD1
samsung/zenltetmo/zenltetmo
was flipping through the recovery logs and i notice quite a few log entries about "couldn't find any tzdata when looking for localtime!" , I notice entries like "Starting recovery on Fri Jan 2 03:55:29 2015" -- i'm wondering if the phone is having trouble setting internal time and date which might be preventing it from booting...just a theory.
sorry for the long message, wanted to completely describe this fun scenario, just in case anyone has any ideas..thanks again
keep trying to load TWRP from the download screen on my phone...but get the "custom binary blocked by FTP lock" message. There's no way to change any settings on the phone as it still won't boot past the t-mobile screen..
platinum5 said:
keep trying to load TWRP from the download screen on my phone...but get the "custom binary blocked by FTP lock" message. There's no way to change any settings on the phone as it still won't boot past the t-mobile screen..
Click to expand...
Click to collapse
Can you download Odin?
Sent from my SM-N910T using Tapatalk
yes i have installed Odin and it's working fine...I can push files to the phone in download mode and it works fine, but the Android images i have loaded so far all seem to result in the phone getting stuck at the t-mobile screen...it won't go past there
Did you ever get this figured out? My guess is it has something to do with not being connected to t-mobile home network. The fact you can get to download mode & Odin sees your phone should mean all hope is not lost yet on recovering your files and getting it working again.
Twrp isn't going to work unless you had root installed with the USB debugging & oem unlock option turned on in developer mode.
Maybe try asking in some of the other s6 forums. There's a lot of knowledgeable people here & I'm sure someone knows how to fix this.
Goodluck, I hope you get it figured out, I know how frustrating it can be.
Hi,
I recently got a SM-T210 from a friend to repair. The description given was that their kids factory reset the unit and won't boot anymore. First the tablet had the death sleep issue which is a easy fix. But after that the tablet simply continues to show the "Samsung GALAXY TAB3" boot screen and never finishes booting.
As I'm known with Odin I simply downloaded the original firmware from sammobile for this tablet and took the firmware version for the Netherlands as that's where I live. There are 2 4.4.2 versions available and downloaded them both. When using Odin 3.09 and higher I simply cannot install the firmware, but on Odin 3.07 it can. Although it installs the tablet still fails to boot properly and hangs at the tab logo as described earlier.
With Odin 3.09 or higher I'm not even able to install the firmware as it says that there is no PIT file and NAND flash write fails. I've found 2 PIT files for this tablet on the forums and even with the use of these PIT files it still errors with the same issue and installation seems impossible with these versions of Odin.
I've also tried installing TWRP recovery but that won't boot either. When booting the tablet with volume key up it shows the Andriod icon with the spinnng "intestines" and alot of red error messages show not able to find /system and /data. My guess is that this is pretty bad, but that is what I want to fix with the stock firmwares and/or the PIT files (LT02.pit and T210(R).pit).
I'm currently out of ideas to revive this tablet and almost start thinking that it's completely dead, but before throwing it in the garbage bin I'm wondering if anybody here is able to help me further with this issue.
If you think you miss critical information, let me know so I can supply it!
Any help is greatly appreciated and thanked for!
langerak said:
Hi,
I recently got a SM-T210 from a friend to repair. The description given was that their kids factory reset the unit and won't boot anymore. First the tablet had the death sleep issue which is a easy fix. But after that the tablet simply continues to show the "Samsung GALAXY TAB3" boot screen and never finishes booting.
As I'm known with Odin I simply downloaded the original firmware from sammobile for this tablet and took the firmware version for the Netherlands as that's where I live. There are 2 4.4.2 versions available and downloaded them both. When using Odin 3.09 and higher I simply cannot install the firmware, but on Odin 3.07 it can. Although it installs the tablet still fails to boot properly and hangs at the tab logo as described earlier.
With Odin 3.09 or higher I'm not even able to install the firmware as it says that there is no PIT file and NAND flash write fails. I've found 2 PIT files for this tablet on the forums and even with the use of these PIT files it still errors with the same issue and installation seems impossible with these versions of Odin.
I've also tried installing TWRP recovery but that won't boot either. When booting the tablet with volume key up it shows the Andriod icon with the spinnng "intestines" and alot of red error messages show not able to find /system and /data. My guess is that this is pretty bad, but that is what I want to fix with the stock firmwares and/or the PIT files (LT02.pit and T210(R).pit).
I'm currently out of ideas to revive this tablet and almost start thinking that it's completely dead, but before throwing it in the garbage bin I'm wondering if anybody here is able to help me further with this issue.
If you think you miss critical information, let me know so I can supply it!
Any help is greatly appreciated and thanked for!
Click to expand...
Click to collapse
Nothing to loose so i should give it one more try with Kies. I remember that years ago i had a problem with a samsung phone and even Odin wasn't helping me. I did it with Kies then which fixed it. No garantuees though.
Droidphilev said:
Nothing to loose so i should give it one more try with Kies. I remember that years ago i had a problem with a samsung phone and even Odin wasn't helping me. I did it with Kies then which fixed it. No garantuees though.
Click to expand...
Click to collapse
Thanks, I've tried it with Kies but it won't even recognize the tablet. When I put it in Download mode and connect it to my computer the Kies welcome screen keeps switching every 2 seconds to the connecting screen, back to the welcome screen and keeps on going like that.
Any ideas left?
langerak said:
Thanks, I've tried it with Kies but it won't even recognize the tablet. When I put it in Download mode and connect it to my computer the Kies welcome screen keeps switching every 2 seconds to the connecting screen, back to the welcome screen and keeps on going like that.
Any ideas left?
Click to expand...
Click to collapse
Except for correct drivers etc etc not really, no.
I am facing same problem.
My Tab 3 (Sm-T210) has gone too.
Now I can't restore it.
I have downloaded Stock ROM from sammobile.org,
but I can't extract this properly.
It always says that "files are corrupted".
I am also going to be hopeless as like as you.
Hello!
Few days ago i found my Samsung Tab 3, and decided to charge it and biit it up.
It got stuck on Samsung logo when i booted it.
So i did a factory reset using the recovery mode.
After i did that the device booted up. with lots of errors.
I was on the setup screen for my device and these errors appeard and said like core has stopped working and every like preinstalled app on my samsung device aswell (NAME has stopped working). So i was not able to fullfill the setup of my device.
I read about it online and a firmware upgrade could fix the problem ( Like the easiest way i read )
So i did some googling and downloaded Odin and a firmware. Followed a guide and did everything right. BUT the process faild like 8min into the flash.
And now my device is stuck on "download mode" but with the error "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I cant get the phone to turn off, nor get into recovery mode or anything else. I tried flash again but no luck.
I also tried another firmware i found. still same problem.
How do i fix this and how can i use my samsung tab 3 again.
WHen i bought it years ago i never really used it. So it's in "new shape" and has never really been used. And now i wanna give it to my little sister for some kids games to play at Xmas.
I hope we can solve this problem.
Thanks in advance
Regards
Timmie
Hyldran0 said:
Hello!
Few days ago i found my Samsung Tab 3, and decided to charge it and biit it up.
It got stuck on Samsung logo when i booted it.
So i did a factory reset using the recovery mode.
After i did that the device booted up. with lots of errors.
I was on the setup screen for my device and these errors appeard and said like core has stopped working and every like preinstalled app on my samsung device aswell (NAME has stopped working). So i was not able to fullfill the setup of my device.
I read about it online and a firmware upgrade could fix the problem ( Like the easiest way i read )
So i did some googling and downloaded Odin and a firmware. Followed a guide and did everything right. BUT the process faild like 8min into the flash.
And now my device is stuck on "download mode" but with the error "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I cant get the phone to turn off, nor get into recovery mode or anything else. I tried flash again but no luck.
I also tried another firmware i found. still same problem.
How do i fix this and how can i use my samsung tab 3 again.
WHen i bought it years ago i never really used it. So it's in "new shape" and has never really been used. And now i wanna give it to my little sister for some kids games to play at Xmas.
I hope we can solve this problem.
Thanks in advance
Regards
Timmie
Click to expand...
Click to collapse
That depends on various things, such as the Android version, kernel and change ID. Than also the Odin version you've used and/or the settings during the attempt of flashing. I found that using the wrong Odin version on a particular Android version, that may prevent the flash of being successfull. B.t.w, did you format both user and cache partition while trying to reset to factory default?
xdausernl said:
That depends on various things, such as the Android version, kernel and change ID. Than also the Odin version you've used and/or the settings during the attempt of flashing. I found that using the wrong Odin version on a particular Android version, that may prevent the flash of being successfull. B.t.w, did you format both user and cache partition while trying to reset to factory default?
Click to expand...
Click to collapse
Yeah, I've found out what Odin version to use that worked for others. I've downloaded lots of different firmwares and such and tried. ALL fails.
When i did a factory reset i also cleared cash and user.
Now i cant even turn off the damn thing. If i charge it up and start, it just goes directly to the screen where it says "Firmware upgrade encountered an issue" and if i try to turn it off, it just reboots and goes back. And i cant even return to factory reset page.
I think that my Micro-USB cable might not work for this, or is that a thing? Do i need a good cable from PC to Phone for this? Or does any cable work?
I just want this tab to work. been trying for weeks.
Thanks for your reply. I hope we can sort this out.
Hyldran0 said:
Yeah, I've found out what Odin version to use that worked for others. I've downloaded lots of different firmwares and such and tried. ALL fails.
When i did a factory reset i also cleared cash and user.
Now i cant even turn off the damn thing. If i charge it up and start, it just goes directly to the screen where it says "Firmware upgrade encountered an issue" and if i try to turn it off, it just reboots and goes back. And i cant even return to factory reset page.
I think that my Micro-USB cable might not work for this, or is that a thing? Do i need a good cable from PC to Phone for this? Or does any cable work?
I just want this tab to work. been trying for weeks.
Thanks for your reply. I hope we can sort this out.
Click to expand...
Click to collapse
It is quite easy to turn the device off, for that to happen you have to press and hold the on/off button. You'll see that the device will shutdown and try to reboot and then finally shuts down again and stay off, then release the on/off button.
Are you sure trying to flash the correct firmware with correct changes, etc??
Please share with us the device and Android version, as well as the stock ROM version with changes you're trying to flash.
Put (copy and paste) the output of Odin below.
Another way to get the firmware flashed is by using Heimdall, but for that to happen you first need to rename the extension of the stock ROM (remove .md5 and leave .tar) and than extract all seperate pieces that are contained within the stock ROM.
All those extracted pieces from the stock ROM you have to upload seperately onto Heimdall and try to flash them to your tablet, one by one.
Heimdall you'll find 'here' or use FWUL instead which has Heimdall pre installed, download is to be found 'here' and install it on a USB medium a stick, to put FWUL onto USB, use Balena-Etcher and the download is to be found 'here'.
Micro USB cable does work, but if you're unsure, try another one and make sure using the correct drivers too.
Using Odin, make sure the tablet is recognised and 'connected' in Odin, also make sure 'repartitioning' is unchecked.
If you've used the wrong Odin version, flashing will fail!
You have Discord by any chance?
If so, please add me @Hyldran0#8832
Thank you for you time man!
Hyldran0 said:
You have Discord by any chance?
If so, please add me @Hyldran0#8832
Thank you for you time man!
Click to expand...
Click to collapse
You're welcome.
Hi, complete novice here, does anyone know where I can get a working Firmware for my Tab 3 v7 (SM-210)?
I have searched through various forum articles here, and tried to install with several builds but none will install. The only one that gets anywhere near is the JASBR build by gr8nole. It appears to install, but on restart, the TAB just sits on the "Samsung Tab3" start screen.
I read that I may need to flash the firmware 4.4.4 (Kit Kat), but can't find it!
The unit is not totally bricked (yet), as I can run TWRP 2.8, with which I created a backup of the original build, but when I try to restore the backup, it fails at just over 31%.
Can anyone help please?
Before I get going - yes I know I messed up. I do have plenty of experience flashing ROMs etc, albeit I'm absolutely not an expert. This was purely a not thinking moment.
So I flashed my Samsung Tab S4 with Kali Nethunter a while back, not really used the tab since. Without a great deal of thought, I decided to put the device back to factory. I went back into the OS and flicked the OEM toggle - utter braindead move. Obviously the device now comes up with a warning, the exact wording is:
"Security Error: This device has been flashed with unauthorized software & is locked. Call your mobile operator for additional support. Please note that repair / return for this issue may have additional cost"
I can still access download mode.
Right, now you've finished laughing/cussing me I did some digging and apparently I can still flash with Odin if its the official ROM? I went to SAMMobile and downloaded the latest ROM and Odin fails with a write error.
What I need to know is:
How bad have I messed up?
Is this recoverable?
Any help appreciated.
Hello there,
So yes, pretty bad mistake but these things happen but it should be recoverable. Just follow the link to get your device booted up! Hopefully the link is for your variant, if not look into installing twrp recovery for your device. Once installed you can back up your data and flash the rom compatible using twrp. Then set up the device and restore your data but make sure it's unlocked or your error may repeat itself! Also you have to find the right version of Odin, they do vary some are patched. Have fun!!
Recovery
Hi,
Thanks for the reply Jedi.
It already has TWRP on it, but recovery is inaccessible since I turned the OEM lock back on. The only thing I can now access is download mode but it can't seem to write to it, which I'm guessing is because the OEM lock is back on. I thought I might still be able to write the official Samsung ROMs even with the OEM lock but it doesnt seem like its the case. Obviously no access to ADB to do a Fastboot unlock either. Fresh out of ideas.
Any other solutions?
bump - anyone? lol, really not looking for an expensive door stop.
It seems you're at the dead end. However, there might be a solution for this, not sure though does it work. But go to OnePlus forum and you'll find how to recover from bricked device. You still got hope because of TWRP. good luck bro
OK, so for anyone wondering if this is fixable, the answer is YES!
You can flash the standard ROM even with the bootloader locked. Clearly what I downloaded from SAMMobile wasnt compatible, however when I used Frija, it found and downloaded the correct ROMs.
Another sticking point of this was the infamous USB 2.0 issue, I assumed the ROM was failing again, however when I finally could be arsed to try it on my old PC, its worked like a charm.
So there you have it:
Latest version of Odin
Latest Samsung USB drivers
Latest ROM downloaded from Frija
Put the tablet into download mode and flash away.