Hello.
I own a SM-G920F from Austria, and i tried to update the Android version to 6.0.1 by downloading the United Kingdom ROM. Unfortunately, after flashing it, odin failed, and now my device cannot boot and shows a error.
I have tried the 5.1.1 version from UK, but that failed too just after a second of pressing Odin, i absolutely have no idea what to do now.
Any help would be appreciated, thanks!
Did the Odin failed at flashing hidden.img?
"Take the image file you have and remove the .md5 extension. You should now be able to open the file with Winrar/7zip and see the hidden.img file. Copy it out and rename it as above.
If you're having issues renaming, open up Folder Options, go to View and untick "Hide extensions for known file types". This should allow you to rename it hidden.img.tar. Then add the file to PDA (called AP in Odin 3.10) and start it.
If you get a failure on this, disconnect the phone, then reconnect it."
Thanks though
Thanks.. I used Smart Switch to restore the original ROM and everything is working fine now. I'm not too eager on installing 6.1.1 anymore
I have the similar issue installing the XEF, i got FAIL with odin, then error on startup,
then I did the hidden.img.tar thing and it passed but now it stuck at galaxy s6 logo,
are you sure its a correct method because the hidden file is only 7 mb
I have no idea, and i really don't want to try anymore, but if it's 7mb, then it's bound not to work.
If you want to go back to your original state, open smart switch and reset your original ROM.
Related
Samsung Mesmerize; SCH-i500; Rooted stock 2.3.4 Gingerbread with Busybox!
I really don't know how I got to this point, I've flashed w/ Odin so many times now, that I have no idea if the above is still where I'm at but here goes the problem:
I turn on my phone and it doesn't even show the Samsung logo, just goes directly to the Samsung Recovery Utils with #MANUAL MODE# displayed at the bottom of the screen.
"reboot system now"
again, reboots into the same recovery mode (Samsung...)
"apply sdcard:update.zip"(after returning to the main screen):
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to open /sdcard/update.zip (No such file or directory)
E:signature verification failed
Installation aborted
"wipe data/factory reset":
E:Can't mount /dev/block/mmcblk0p3
(Invalid arguement)
E:install_application_for_customer:Can't mount HIDDENSDCARD:
your storage not prepared yet. please use UI menu for format and reboot actions.
"wipe cache partition": works fine though
I know this has been asked before but I haven't found any other posts about the Samsung Mesmerize SCH i500 & I'm not sure if this is model specific & don't really want to take my chances, sorry.
Ok, update: I just used Odin to reflash to rooted 2.3.4 & it still goes to recovery mode (Samsung) & all the options are the same (w/ the same results) as above, I can't get my sdcard to show on my computer to manually apply the update, unless there is a way I don't know of, the only way I know requires me to be on the phone's Main Menu & use the notification drop-down menu to activate transfer mode on my computer, what am I missing?
Now I used Odin again, this time to put ClockworkMod Recovery v4.0.1.0 on it & now it booted up in CwM Recovery mode but I still get the same error when trying to apply the update (see above)
Trying to "- mount USB storage":
E:Unable to open ums lunfile (No such file or directory)
I just want to format the whole thing, phone & sdcard, & start over from scratch as though I had just bought the phone.
Ok, for future reference, if anyone has a problem like this, unless you find another solution, this is what I did:
I downloaded a rooted stock 2.2 Froyo, ran Odin & just put the SCH-I500_USCC_EA11_REL_ROOT.tar.md5 in the PDA part & flashed it, it went to the recovery screen again at boot up but, after selecting Reboot it went right to the phone splash screen, so, I guess I'm back in business but I haven't tested anything yet, I'll update this post to keep you all in the loop, wish me luck.
It would seem that I can get wifi but I don't have a carrier or 3G, as far as I can tell, its become no more than an iPod Tough (just having wifi access) I can, however, now access the sdcard, when I plug the USB cablein it asks if I want Samsung Kies or Mass storage.
I don't know
Download and unzip the linked file. Place the tar file in the PDA slot and the pit file in the PIT slot. Make sure repartition is checked and the flash. This should get the phone booting again.
http://db.tt/fOG2Lf6
Once this is done download and unzip the linked file. Do the exact same thing. Place the tar file in PDA and the pit file in PIT. Make sure repartition is NOT checked and flash. This should have you booting into EH09 without issue.
http://db.tt/hls4IuhW
scarmon25 said:
Download and unzip the linked file. Place the tar file in the PDA slot and the pit file in the PIT slot. Make sure repartition is checked and the flash. This should get the phone booting again.
http://db.tt/fOG2Lf6
Once this is done download and unzip the linked file. Do the exact same thing. Place the tar file in PDA and the pit file in PIT. Make sure repartition is NOT checked and flash. This should have you booting into EH09 without issue.
http://db.tt/hls4IuhW
Click to expand...
Click to collapse
Worked great, thank u very much, started off w/ the signal bars at full but wouldn't make any outgoing calls or send any messages but I could receive messages (text), every time I tried to make a call it kept giving me a recording, something about "To make a collect call please enter the are code and phone number of the person you are trying to call...." so I type the number & it responds w/ something "....the number you are trying to call cannot be billed..." "...to make a phone call w/ a pre-paid card or a credit card..." so I just entered the US Cellular activation # & I was back in business!
ok so after this!
After i do this (Hopefully it works) then could i use ODIN to flash the pre rooted 2.3 rom? or not?
Once done with those instructions you will be on EH09. Odin a recovery and flash the below linked file. It will root it for you.
http://db.tt/QtScf9AW
scarmon25 said:
Download and unzip the linked file. Place the tar file in the PDA slot and the pit file in the PIT slot. Make sure repartition is checked and the flash. This should get the phone booting again.
Once this is done download and unzip the linked file. Do the exact same thing. Place the tar file in PDA and the pit file in PIT. Make sure repartition is NOT checked and flash. This should have you booting into EH09 without issue.
Click to expand...
Click to collapse
Any chance you could relink those? I'm in the exact same boat.
Is there anyway I can get those links? When I click them it say's they're expired or something...
scarmon25 said:
Download and unzip the linked file. Place the tar file in the PDA slot and the pit file in the PIT slot. Make sure repartition is checked and the flash. This should get the phone booting again.
http://db.tt/fOG2Lf6
Once this is done download and unzip the linked file. Do the exact same thing. Place the tar file in PDA and the pit file in PIT. Make sure repartition is NOT checked and flash. This should have you booting into EH09 without issue.
http://db.tt/hls4IuhW
Click to expand...
Click to collapse
Does anyone know what these two files referenced actually are?
Blahhh
I really needed those files.
Woolvz said:
I really needed those files.
Click to expand...
Click to collapse
Check rootzwiki, there's no development going on here.
Sent from my SCH-I500 using xda premium
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.
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.
Hope this might help someone here.
I rooted my s8+ and basically got stuck with a soft-bricked phone, telling me I could only use official firmware etc etc. I was able to get the phone into download mode (eventually) but I wasn't able to flash anything including the stock Pie rom. I spent all night trying to find a solution to no avail and then found this, which I've edited a bit. And it worked. I've now got my s8+ back with Android 9 on it without any bloatware and it's actually better than ever. Thanks to Krolik301 for your help. I'm just hoping this may help someone.
1. Download the stock ROM and extract it.
2. Make a copy of the CSC file and rename one from the file type .md5 to .rar
3. Extract the PIT file from the CSC .rar file.
4. In Odin v3.13, make sure you add all four files from the extracted ROM (BL, AP, CP and CSC).
5. Click the PIT tab and add the PIT file that you just extracted from the CSC.rar file.
6. I the Options tab of Odin, make sure that Re-Partition, Auto Reboot and F.Reset Time are all ticked.
7. Click Start and hopefully you'll be back to your stock ROM
And please don't hold me responsible for any loss of data or a phone that still won't boot.
Hope this helps someone. Happy Easter
Muddyfunk said:
Hope this might help someone here.
I rooted my s8+ and basically got stuck with a soft-bricked phone, telling me I could only use official firmware etc etc. I was able to get the phone into download mode (eventually) but I wasn't able to flash anything including the stock Pie rom. I spent all night trying to find a solution to no avail and then found this, which I've edited a bit. And it worked. I've now got my s8+ back with Android 9 on it without any bloatware and it's actually better than ever. Thanks to Krolik301 for your help. I'm just hoping this may help someone.
1. Download the stock ROM and extract it.
2. Make a copy of the CSC file and rename one from the file type .md5 to .rar
3. Extract the PIT file from the CSC .rar file.
4. In Odin v3.13, make sure you add all four files from the extracted ROM (BL, AP, CP and CSC).
5. Click the PIT tab and add the PIT file that you just extracted from the CSC.rar file.
6. I the Options tab of Odin, make sure that Re-Partition, Auto Reboot and F.Reset Time are all ticked.
7. Click Start and hopefully you'll be back to your stock ROM
And please don't hold me responsible for any loss of data or a phone that still won't boot.
Hope this helps someone. Happy Easter
Click to expand...
Click to collapse
Hello. I'm helping someone on discord with this exact issue (the error code is "can't open the specified file (line 665)". I extracted the PIT file from CSC and placed it into the PIT file. I also put all of the firmware files in their proper place (except for HOME_CSC, as he wants to keep his files). Do I absolutely have to put the CSC file in place of the HOME_CSC file?
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.