DISCLAIMER: Since this is a third-party supplied file, flashing this file places any and all outcomes on YOU, the flasher (get your mind out of the gutter, thanks.) This file, though supplied by Samsung Kies 3, may cause issues or have undesirable effects. What these effects are, I have no clue. If you have a custom recovery, it will be overwritten with the stock recovery. Again, if you use this, you are the one responsible for any negative outcome.
This the official stock ROM flashable via Odin. This took me a few hours to download several times and locate the temp directory that housed it. It is a 2.12 gig tar.md5 file. Since Samsung does not have an open source copy for us to download, I used Kies 3 to download it.
FLASHING INSTRUCTIONS:
Using the most recent Odin, put the file in the AP section and flash it.
Link
Thank you so much it fixed my bricked device!
Thank you so much - Accidentally upgraded firmware and lost root and could not re-root. Worked like a charm and used kingroot to gain root again. You rock!
It downloads as a .RAR file if converted to .TAR, ODIN can not load it. How can the .rar file be used by ODIN?
bunivers said:
It downloads as a .RAR file if converted to .TAR, ODIN can not load it. How can the .rar file be used by ODIN?
Click to expand...
Click to collapse
The flashable .Tar file that you will use to restore your device via Odin, is located inside the .RAR provided in the download link. Once the .RAR file has been unrared/unzipped using 7zip, you will have your restore .Tar file that you're referring to. If you need to, you can Google 7zip and download it. The program is free and open-source, and it supports .RAR .TAR .ZIP etc. Happy Restore!
@jaywillsoul Please add to the OP that this firmware will wipe the device.
Thanks again for the firmware!
Sent from my XT1528 using XDA Labs
I was able to un-brick my wife's Verizon Core Prime with this. Thank you for your time and effort, @jaywillsoul.
Donation sent.
Fail
I downloaded the firmware, began to flash and Odin wrote "FAIL", and the screen after turning on is "Software update failed. Your device didnt update successfully. Use the Verizon Software Repair Assistant on a computer to repare your device and complete the update." But the Verizon Software Repair Assistant after this can not find the phone.
Thank you for this wonderful gift to the underdeveloped Core Prime! :good: worked for me and I was able to root afterwards!
is that process unlock the sim card lock for Verizon
ty it work's. I can root now
Sorry to bump this thread, but will updating through recovery mode end up wiping all the data of the phone? (like pictures, and files)
I was dumb and didn't enable usb debugging before my phone got soft bricked, now it freezes on the carrier animation
My phone is a model SM-G360T1
Link999123 said:
Sorry to bump this thread, but will updating through recovery mode end up wiping all the data of the phone? (like pictures, and files)
I was dumb and didn't enable usb debugging before my phone got soft bricked, now it freezes on the carrier animation
My phone is a model SM-G360T1
Click to expand...
Click to collapse
You have the wrong model - this guide is for the G360V, not the G360T1. Sorry.
Related
Need help. I am trying to restore my Skyrocket to factory. I down loaded the necessary files
-ODIN
-SGH-I727-UCKJ2-k0nane
The thing is that when I open Odin, click PDA and browse, I don't see the tar file(SGH-I727-UCKJ2-k0nane)? Do I have to convert the file to tar?
The SGH-I727-UCKJ2-k0nane is in the download file and I see it but when I use Odin to browse, I don't see the file?
Am I doing something wrong or am I missing a step?
I am using Window's Vista. Does it make any difference?
I have read instructions many many times and I can't figure it out.
anyone out there?
Sorry bro. I would help you but seeing as I have yet to have my SkyRocket in Hand and have not gone through the rooting and ROM process on THIS device. I am not comfortable giving advice. Best to wait for someone who has more experience with the SkyRocket than I.
Juroid said:
Need help. I am trying to restore my Skyrocket to factory. I down loaded the necessary files
-ODIN
-SGH-I727-UCKJ2-k0nane
The thing is that when I open Odin, click PDA and browse, I don't see the tar file(SGH-I727-UCKJ2-k0nane)? Do I have to convert the file to tar?
The SGH-I727-UCKJ2-k0nane is in the download file and I see it but when I use Odin to browse, I don't see the file?
Am I doing something wrong or am I missing a step?
I am using Window's Vista. Does it make any difference?
I have read instructions many many times and I can't figure it out.
Click to expand...
Click to collapse
the .tar file is INSIDE the file you downloaded. the file you downloaded is a .7z or 7zip file. 7zip is a free archive/extractor. unzip it with 7zip and you will find your tar file.
i find it always helps to have your WINDOWS configured to show file extensions to keep confusion like this to a minimum, since you would have actually seen the file extension type.
careful! this method trips the ROM counter. why are you returning to stock?
I figuered it out. I bricked my phone trying to update to 2.36.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
You know there is a cwm flashable rooted zip for 2.3.6 right? Its here http://forum.xda-developers.com/showthread.php?t=1361144
Im getting the nfc service has stopped message non stop when at the play store. It takes me 20 mins to download 1 app. Also im getting the com.android.phone message when trying to get into mobile network which i cant get into and need to before i go overseas on jan 2nd. Everything else works fine, google wallet, touchwiz was giving me a problem but a factory reset fixed that but not the other 2 issues. I dont know what rom im using or anything like that but i have the files or the thread if you need more 411. So if you can fix this i will pay you via paypal. im available for skype video chat if you need to see the phone and whats going on with it. please help!!!!!!!!
Have you tried wiping davlik, resetting permissions, or just simply finding those apps and wiping their data?
Sent from an Apple killing JellyBean
moparfreak426 said:
Have you tried wiping davlik, resetting permissions, or just simply finding those apps and wiping their data?
Sent from an Apple killing JellyBean
Click to expand...
Click to collapse
ive wiped davlik and fixed permissions a bunch of times as well as wiped battery stats, clearing google wallet and did a factory reset.
i just noticed that the nfc thing pops up also when i use my camera and go into my gallery
Try using the full wipe version in this Thread: http://forum.xda-developers.com/showthread.php?t=1984436.
BigErnM said:
Try using the full wipe version in this Thread: http://forum.xda-developers.com/showthread.php?t=1984436.
Click to expand...
Click to collapse
ive tried the non wipe of that thread, but i need some what dummy instructions to complete this, like i said im a noob
Download ODIN here: http://d-h.st/UO0. It sounds like you may have already done this. Extract it to your desktop. I'm assuming you have already installed the Samsung Drivers here:http://www.samsung.com/us/support/owners/product/SCH-I535MBBVZW. Install those if you haven't already. Download this file from the thread: http://www.androidfilehost.com/?fid=9390214368362234355. Extract it to your desktop. Turn off your phone. Open Odin307 folder on your desktop and run Odin3 v3.07.exe. Put the phone into download mode by following second step in the thread: Put phone into download mode [with phone off, hold vol. down + home + power ], connect to computer.
once in odin click the PDA field and select the root66_VZW_I535VRBLK3.tar.md5 you downloaded.
Leave Auto Reboot and F. Reset Time checked.
click start and
when done let phone reboot.
BigErnM said:
Download ODIN here: http://d-h.st/UO0. It sounds like you may have already done this. Extract it to your desktop. I'm assuming you have already installed the Samsung Drivers here:http://www.samsung.com/us/support/owners/product/SCH-I535MBBVZW. Install those if you haven't already. Download this file from the thread: http://www.androidfilehost.com/?fid=9390214368362234355. Extract it to your desktop. Turn off your phone. Open Odin307 folder on your desktop and run Odin3 v3.07.exe. Put the phone into download mode by following second step in the thread: Put phone into download mode [with phone off, hold vol. down + home + power ], connect to computer.
once in odin click the PDA field and select the root66_VZW_I535VRBLK1.tar.md5 you downloaded.
Leave Auto Reboot and F. Reset Time checked.
click start and
when done let phone reboot.
Click to expand...
Click to collapse
ok so i have odin i have the drivers and downloaded the root66 file both the non wipe and wipe versions and both dont allow me to put it in pda, i get a warning msg basically saying where the file is located followed by the name of the file and then special characters that look like boxes. thats where im stuck with this process.
Do you have 7-zip or WinRAR installed? You have to extract the file out of the root66_VZW_I535VRBLK3.7z that you downloaded. The file you need to put in the PDA section in odin will be called root66_VZW_I535VRBLK3.tar.md5. That is the wipe version that I would recommend you use. The no-wipe verson file to use in odin in the PDA section is called root66_VZW_I535VRBLK3_nowipe.tar.md5.
BigErnM said:
Do you have 7-zip or WinRAR installed? You have to extract the file out of the root66_VZW_I535VRBLK3.7z that you downloaded.
Click to expand...
Click to collapse
i extracted it in my mac using stuff it, im running windows xp on virtual machine
my skype username is jonathan.ofri if you or anybody else wants to make a quick $20, id rather do it through there then the forums, ive been working on this for about 14 hours now, im exhausted!!!!!!
Good luck to you. I've done all I can. If you are still stuck use the factory images in section 5 of this guide to go completely back to stock: http://forum.xda-developers.com/showthread.php?t=1762709.
BigErnM said:
Good luck to you. I've done all I can. If you are still stuck use the factory images in section 5 of this guide to go completely back to stock: http://forum.xda-developers.com/showthread.php?t=1762709.
Click to expand...
Click to collapse
i appreciate the effort, thanks
Could be a possible hardware failure? Nfc gone bad?
Sent from an Apple killing JellyBean
FingerBlastJ said:
i appreciate the effort, thanks
Click to expand...
Click to collapse
Reflash none-wipe root66 is the right approach, you need to download and installed 7zip to your xp. Use 7zip to unzip your root66zip file, then use Odin to flash. Seems like the file is corruppted that's why Odin is not seeing the file name. Once you get this file name issue fixed, you should able to flash the zip.
nfc still works, i got nfc tags everywhere and tested them and are 100% operational.
as for the root file, i downloaded winrar onto xp to unzip the file, there are 10-15 files in it, i dont know which 1 to tack onto pda. what is 7zip? is that an extractor?
7zip is best extractor for. zips...
Sent from an Apple killing JellyBean
Double click the root66_VZW_I535VRBLK3.7z which should open it in WinRAR. If that doesn't do it open WinRAR and then select that file. There should only be one file inside to extract named: root66_VZW_I535VRBLK3.tar.md5. That is the one to use in the PDA section of odin. If WinRAR won't do it (it works fine for me), install 7-zip and extract it with that.
With much embarrassment I have to admit I really thought I was smarter than a tablet and a few simple clicks. Apparently not. So now I am here with issues that I am sure someone can answer because your more advanced than a few clicks and a tablet.
I have briefly looked for a resolve to my issue but it is very overwhelming. So if you can just point me in the right direction and hold my hand at the same time I would be very appreciative :good:
Issues:
I originally downloaded Odin, GT-P5113 4.0.4, CM 12.1, CW Unofficial Touch 6.0.3.3 p5100 zip. I launced Odin and followed the steps from a you-tube video. Well upon my surprise CW was not on the tablet so I was at the Tabs generic recovery screen. I choose the option to delete all user data ( lots of no's to select from and one Yes). Well continuing to be a fool I completed this process. When the tablet rebooted I was stuck at the Samsung logo screen. I decided to get to the download screen and install smt810_cf_autoroot.tar. After loading this tar via Odin I became stuck on the Android man downloading screen. Waited a bit and nothing. Then my tablet shut down and came up with "Firmware upgrade encountered and issue" with the tablet-yellow ! icon and pc icon.
Another issue is when i download these files Odin will not find them in my file. Why? I usually keep them unzipped as a .rar in order for odin to show them so I can select PDA and attempt to install them.
Is there a way to still upgrade the Android system and fix this Firmware error at the same time?
Basically I am so new to this I need specific directions on resolving my issue. So if anyone has a moment please help me out here. I appreciate your time and knowledge
And I can use Odin to install to the tablet. If that helps Just not in the download screen on the tablet.
Learning76 said:
And I can use Odin to install to the tablet. If that helps Just not in the download screen on the tablet.
Click to expand...
Click to collapse
first you should download the stock firmware of your device, if it's p5113 then search and download the same firmware.
http://forum.xda-developers.com/showthread.php?t=2203309 check this thread if it's there, if it's not please google it, if already have it, ignore..
Once you have it, you should get the firmware md5 file (by unzipping the rar.) Odin will take tar file or md5 file. put it in Odin AP/PDA check the thread for all the details on how to flash correctly.
you have to get into download mode by pressing the power and volume up/right to do that once the firmware is successfully flashed and your tab starts running again. first get this part done.
Always use files that are meant only for your device. if your tab say p5113. then make sure the file you are flashing states it is meant for p5113 and not p5100. (maybe not in the rooting case cause it's same
http://forum.xda-developers.com/showthread.php?t=2203309 here for all)
At some places you will find files marked as p51xx. those files are generally safe too and are meant for the p51xx tab series but that is later stage.
I appreciate the feedback and have found I had tried to flash my tablet with GT-P5110 software when i actually have a GT-P5113TS. I have found the firmware but my issue is when I download anything and extract it with using rar. I never get a .tar file or anything Odin can not recognize to select PDA and use.. What would cause that? How do I fix this?
Thank You
Learning76 said:
I appreciate the feedback and have found I had tried to flash my tablet with GT-P5110 software when i actually have a GT-P5113TS. I have found the firmware but my issue is when I download anything and extract it with using rar. I never get a .tar file or anything Odin can not recognize to select PDA and use.. What would cause that? How do I fix this?
Thank You
Click to expand...
Click to collapse
Try winrar or 7zip, it should extract, you need md5 or tar format in pda section. If not what error are you getting? There must be some file when you open the archive?
Basically when I download the zip file I want and then extract it to a specific folder. All I after unzipping is File folders with other file folders inside,Img, File, PROP, and SH. I never extract anything that is a Tar file or anything Odin can recognize when on PDA within Odin. Plus a lot of times I click on a link for a download off this site and it sends me to some watch-movies website. Not a actual download. Or I am just missing it.
Learning76 said:
Basically when I download the zip file I want and then extract it to a specific folder. All I after unzipping is File folders with other file folders inside,Img, File, PROP, and SH. I never extract anything that is a Tar file or anything Odin can recognize when on PDA within Odin. Plus a lot of times I click on a link for a download off this site and it sends me to some watch-movies website. Not a actual download. Or I am just missing it.
Click to expand...
Click to collapse
Maybe it's a bad link to your stock file then. Perhaps someone can give proper file link to the stock firmware. Inside the zip it's basically a md5 file for firmware to flash. Sadly I don't have a proper yoi will have to find of the net.
So, i got a new J320FN, i hard bricked it after trying to flash a custom recovery and root it.
I figured everything out and i unbricked it, and on top of that i installed TWRP and SuperSU.
I made this package, that includes everything that i used to unbrick + root it, and i also made the tutorial:
"THE PACKAGE"
This is what you can find in the package:
Unbrick/Stock Android TAR.MD5 Files (for J320FN).
Multiple Partition PIT files (for every version of the phone).
Hidden.img.tar file (for J320FN).
Hidden.img PIT file (for J320FN).
TWRP Recovery (for every version of the phone - only tested on J320FN).
Odin v3 (for every Samsung Phone).
ADB Drivers, Samsung USB Drivers.
Hit the :good: Thanks button if this helped you <3
And also guys, if you could make a mirror for the package, it would be great.
My internet connection is limited so i can't upload it to another site, and Dropbox is limited, so...
Do u have those files for the j320p?
mr_reaper said:
Do u have those files for the j320p?
Click to expand...
Click to collapse
Nope, i only have the PIT file for it, and i also included it in the package.
To get the ZIP file (that includes the .tar.md5 files) please go to
https://service-gsm.net/Samsung/J320P/J320PVPU1AOL2_SPT1AOL2.zip/
and buy the file for $2, it works (btw, post the files here so other people won't need to pay)
Btw you need to find this file:
ALL_SPT_J320PVPU1AOL2_J320PSPT1AOL2_CL6363917_QB7487813_REV00_user_low_ship_MULTI_CERT.tar.md5
MihailMojsoski said:
So, i got a new J320FN, i hard bricked it after trying to flash a custom recovery and root it.
I figured everything out and i unbricked it, and on top of that i installed TWRP and SuperSU.
I made this package, that includes everything that i used to unbrick + root it, and i also made the tutorial:
"THE PACKAGE"
This is what you can find in the package:
Unbrick/Stock Android TAR.MD5 Files (for J320FN).
Multiple Partition PIT files (for every version of the phone).
Hidden.img.tar file (for J320FN).
Hidden.img PIT file (for J320FN).
TWRP Recovery (for every version of the phone - only tested on J320FN).
Odin v3 (for every Samsung Phone).
ADB Drivers, Samsung USB Drivers.
Hit the :good: Thanks button if this helped you <3
Click to expand...
Click to collapse
hello
can you please attach here only the pit files?
I have a very slow connection and I have already the recovery and the stock firmware, right now only need to get thePIT files.
can you extract it and share just these files?
thanks
So TWRP for J320FN
Please give it to me!!!
hey there, link is not working for me. can you please upload it on google drive?
hi my friend
link is dead
another link please ?
thks
Link broken
Hi,
The link to "THE PACKAGE" is broken Could you post a new link? Thanks a lot!!
As Odin in Windows does not do the trick for me, flashing stock ROM onto the Tab3, 7.0 WiFi device, I'll now want to try using Haimdall on FWUL.
But to make that happen, I seem need seperate .img files as Haimdall works with seperate files instead of that big tar.md5 file like Odin in Windows does.
So the first question would be:
What tools do I need to get all these seperate .img files out of the stock ROM Odin uses??
In Haimdall I managed to detect the Tab3 device and download and save the PIT file successfully.
But when I try to write into 'recovery' partition using a renamed file (TWRP 3.0.0-0.img) recovery.img, the process failed.
The log shows successfull writing of the PIT file, but it failed on recovery.img with this error 'failed to confirm end file transfer sequence'.
Also, there's no progressbar showing on the Tab3 device, while writing.
I already tried other USB cables, same results.
So the second question would be:
What did I do wrong, or did I miss something?
xdausernl said:
As Odin in Windows does not do the trick for me, flashing stock ROM onto the Tab3, 7.0 WiFi device, I'll now want to try using Haimdall on FWUL.
But to make that happen, I seem need seperate .img files as Haimdall works with seperate files instead of that big tar.md5 file like Odin in Windows does.
So the first question would be:
What tools do I need to get all these seperate .img files out of the stock ROM Odin uses??
In Haimdall I managed to detect the Tab3 device and download and save the PIT file successfully.
But when I try to write into 'recovery' partition using a renamed file (TWRP 3.0.0-0.img) recovery.img, the process failed.
The log shows successfull writing of the PIT file, but it failed on recovery.img with this error 'failed to confirm end file transfer sequence'.
Also, there's no progressbar showing on the Tab3 device, while writing.
I already tried other USB cables, same results.
So the second question would be:
What did I do wrong, or did I miss something?
Click to expand...
Click to collapse
To extract the firmware down to the individual .img files, try this thread, it leads to another guide on another site.
https://forum.xda-developers.com/showthread.php?t=2138885
Keep in mind, this guide is a bit old, the basic process is still valid but some things may have changed in how Samsung firmware is put together, there may be some extra steps required for firmware from newer devices.
Sent from my LGL84VL using Tapatalk
Droidriven said:
To extract the firmware down to the individual .img files, try this thread, it leads to another guide on another site.
https://forum.xda-developers.com/showthread.php?t=2138885
Keep in mind, this guide is a bit old, the basic process is still valid but some things may have changed in how Samsung firmware is put together, there may be some extra steps required for firmware from newer devices.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply,
Right after I wrote this text, I came up with another approach ... to just rename the stock ROM extension 'tar.md5' to '.tar' and so I did, then I unzipped the file.
But thanks anyway ...
Inside I found several files and about 6 image files and the PBL.bin file.
For 4 partitions I found an image file, system.img, NVM.img, cache.img and hidden.img.
Guess what ... with Haimdall in FWUL the upload went successfully and there's also a statusbar on Tab3 while at download, where as Odin (any version) in Windows failed on me all the time.
All files needed to upload seperately though, all at the same time gave me this error 'failed to confirm end of file transfer sequence'.
For the boot.img file I couldn't find a partition.
Recovery.img and the PBL.bin file failed to upload using Haimdall with errors 'failed to upload' and 'failed to confirm end of file transfer sequence'.
I also tried to rename a TWRP image to recovery.img, but that upload failed as well.
At this point I only proved the hardware being OK, that is the USB cable and the USB port on the Tab3 device.
It seems like Android operating system crashes after the message windows from antivirus program 'program has stopped', it then shut down and reboot.
After login the same thing happens all over again ... like some sort of boot loop.
And there's just not enough time to change any of the system settings, nor to disable any apps due to all those message windows you have to click first.
Overall status being Android operating system is still faulty.
This means that I just may be able to fix this thing, I only need the right tools to get the job done.
And I can't believe there's no one out there that couldn't help me out ...
xdausernl said:
Thanks for your reply,
Right after I wrote this text, I came up with another approach ... to just rename the stock ROM extension 'tar.md5' to '.tar' and so I did, then I unzipped the file.
But thanks anyway ...
Inside I found several files and about 6 image files and the PBL.bin file.
For 4 partitions I found an image file, system.img, NVM.img, cache.img and hidden.img.
Guess what ... with Haimdall in FWUL the upload went successfully and there's also a statusbar on Tab3 while at download, where as Odin (any version) in Windows failed on me all the time.
All files needed to upload seperately though, all at the same time gave me this error 'failed to confirm end of file transfer sequence'.
For the boot.img file I couldn't find a partition.
Recovery.img and the PBL.bin file failed to upload using Haimdall with errors 'failed to upload' and 'failed to confirm end of file transfer sequence'.
I also tried to rename a TWRP image to recovery.img, but that upload failed as well.
At this point I only proved the hardware being OK, that is the USB cable and the USB port on the Tab3 device.
It seems like Android operating system crashes after the message windows from antivirus program 'program has stopped', it then shut down and reboot.
After login the same thing happens all over again ... like some sort of boot loop.
And there's just not enough time to change any of the system settings, nor to disable any apps due to all those message windows you have to click first.
Overall status being Android operating system is still faulty.
This means that I just may be able to fix this thing, I only need the right tools to get the job done.
And I can't believe there's no one out there that couldn't help me out ...
Click to expand...
Click to collapse
I have to edit the last post, because I can change the stock ROM file name as mentioned before and that did not cause any problems with the md5 hash.
At this point, I can also download all files (10) succesfully from Heimdall with the Samsung tablet.
The only problem is caused by replacing the 'system.img' file, as the tablet immediatly reboots after Heimdall released the device after download was successfully.
It could mean that after the succesfull download, the downloaded system.img file is deleted at immediate reboot of the tablet, which would also explain why there's no changes after tablet reboot.
With all the other 9 downloaded files from Heimdall, it took several seconds until reboot of the tablet.
xdausernl said:
I have to edit the last post, because I can change the stock ROM file name as mentioned before and that did not cause any problems with the md5 hash.
At this point, I can also download all files (10) succesfully from Heimdall with the Samsung tablet.
The only problem is caused by replacing the 'system.img' file, as the tablet immediatly reboots after Heimdall released the device after download was successfully.
It could mean that after the succesfull download, the downloaded system.img file is deleted at immediate reboot of the tablet, which would also explain why there's no changes after tablet reboot.
With all the other 9 downloaded files from Heimdall, it took several seconds until reboot of the tablet.
Click to expand...
Click to collapse
Try a windows PC and try flashing via Odin, it tends to work better than Heimdall.
Also, if you are trying to use a system.img that is different than the system.img in your firmware, your bootloader may not be allowing the different system to flash or boot on your device.
Sent from my SM-S767VL using Tapatalk
xdausernl said:
Thanks for your reply,
Right after I wrote this text, I came up with another approach ... to just rename the stock ROM extension 'tar.md5' to '.tar' and so I did, then I unzipped the file.
But thanks anyway ...
Inside I found several files and about 6 image files and the PBL.bin file.
For 4 partitions I found an image file, system.img, NVM.img, cache.img and hidden.img.
Guess what ... with Haimdall in FWUL the upload went successfully and there's also a statusbar on Tab3 while at download, where as Odin (any version) in Windows failed on me all the time.
All files needed to upload seperately though, all at the same time gave me this error 'failed to confirm end of file transfer sequence'.
For the boot.img file I couldn't find a partition.
Recovery.img and the PBL.bin file failed to upload using Haimdall with errors 'failed to upload' and 'failed to confirm end of file transfer sequence'.
I also tried to rename a TWRP image to recovery.img, but that upload failed as well.
At this point I only proved the hardware being OK, that is the USB cable and the USB port on the Tab3 device.
It seems like Android operating system crashes after the message windows from antivirus program 'program has stopped', it then shut down and reboot.
After login the same thing happens all over again ... like some sort of boot loop.
And there's just not enough time to change any of the system settings, nor to disable any apps due to all those message windows you have to click first.
Overall status being Android operating system is still faulty.
This means that I just may be able to fix this thing, I only need the right tools to get the job done.
And I can't believe there's no one out there that couldn't help me out ...
Click to expand...
Click to collapse
Droidriven said:
Try a windows PC and try flashing via Odin, it tends to work better than Heimdall.
Also, if you are trying to use a system.img that is different than the system.img in your firmware, your bootloader may not be allowing the different system to flash or boot on your device.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply.
But I came to Heimdall because Odin3 in Windows and even JOdin3 in Linux failed.
My guess is that the installed system.img on the system partition the culprit was in this case, because the stock ROM was the correct one for my tablet.
If you don't have the correct software, you either cannot install it or you will get your device bricked.
My device seem to be software bricked, for that matter and that is due to either the root software, anti virus software or an combination of both.
xdausernl said:
Thanks for your reply.
But I came to Heimdall because Odin3 in Windows and even JOdin3 in Linux failed.
My guess is that the installed system.img on the system partition the culprit was in this case, because the stock ROM was the correct one for my tablet.
If you don't have the correct software, you either cannot install it or you will get your device bricked.
My device seem to be software bricked, for that matter and that is due to either the root software, anti virus software or an combination of both.
Click to expand...
Click to collapse
Meanwhile I think I found a possible cause for failure using Heimdall-Frontend.
Heimdall-Frontend uses only extracted content of a stock ROM, in my case that's 10 files.
Although the download of the 'system.img' file completed successfully and Heimdall-Frontend releases the connected device, there's still a slightly different behaviour at reboot of Tab3.
Because after the release of the connected device, Tab3 then immediately goes into reboot.
That's not the case with all other downloaded files.
After releasing the connected device, it then takes a few second until the Tab3 goes into reboot.
So my guess is that at immediate reboot the downloaded 'system.img' file will then be deleted from the Tab3.
That would explain why after reboot nothing has really being changed.