Related
I have been at this for a week now. I've tried Heimdall 1.1.1, 1.3.2, AND Odin3 v1.83, v1.85, to reflash the stock Verizon firmware on my Galaxy Tab SCH-i800. I was an idiot and flashed U.S. Cellular firmware, which changed the boot animation and the cell service text. I've scoured the internet on how to do this and everything I've tried has failed. With Heimdall, whenever I plug in the stock files to the program (in 1.1.1 only, I can't figure out 1.3.2 for the life of me) and hit Start, I get "Failed to access device. Error: -12" I'm getting my files from SCH-I800_VZW_stock.zip, it's been extracted. When trying to flash a .tar file with Odin, it works successfully, then my phone goes into bootloop. I can get back to Download mode, but every time I try flashing a stock .tar, I get the same results. I'm starting to go crazy. Anyone help?
maybe you have missed with your partions? if so, i think you need a specific pit file for this stock rom, i dont know where it is, but you might start looking for it.
edit : look in this thread, you might find it useful http://forum.xda-developers.com/archive/index.php/t-940046.html
and this is also important http://theunlockr.com/2012/06/28/ho...axy-tab-sch-i800-back-to-stock-and-unroot-it/
last one http://gizmoninja.com/2011/04/how-to-root-latest-samsung-galaxytab-verizon-update-ec02/
best regards ^_^
Sifou
chrispysaid said:
....With Heimdall, whenever I plug in the stock files to the program (in 1.1.1 only, I can't figure out 1.3.2 for the life of me) and hit Start, I get "Failed to access device. Error: -12"
Anyone help?
Click to expand...
Click to collapse
Did you properly install the Samsung drivers on your PC using the heimdall utility? And you put your Tab in download mode?
The Problem may lie with youe Heimdall setup.
Make sure you have Keis installed. Then make sure you activate the drivers for Heimdall.
This is a great rom to flash to your VZW Tab. follow this thread http://forum.xda-developers.com/showthread.php?t=1325469
Kind of a niche guide, but at least non-Japanese people owning an SC-01C have some sort of guidelines.
Before we begin
The SC-01C is the rebranded Japanese version of the P1000, locked exclusively to NTT DoCoMo. If you have this model and want to upgrade and/or flash custom ROMs with it, this guide may be able to help you.
Before beginning, you have to check your firmware version. What you'll have to download will depend on it. If you have Android 2.2 Froyo, read on, otherwise, if you're already running Android 2.3 Gingerbread skip to the Gingerbread Users section.
Also, based on experience, if you want to upgrade to other ROMs in the future you will have to keep your stock GB ROM file, your gt-p1000_mr.pit, the dbdata.tar and the entire Overcome kit (kernel and ROM). You will need all of them in the future because I've found that to install a new ROM you have to repeat the entire process of restocking to GB, then installing Overcome Kernel and ROM, then installing whatever ROM you want. It sucks, but it's the only way I've seen so far.
Froyo Users
If you're planning to install a custom ROM, you can't do it on Froyo straight away, at least not on a stock ROM with a protected bootloader. If you don't know if your bootloader is protected or not, the safest thing to do is to first upgrade your firmware to the stock Japanese Android 2.3 Gingerbread. Then you can follow the Gingerbread guide afterwards.
Froyo Users Will Need
Stock Japanese GB ROM (you can get it from here or from SamFirmware.com). The ROM is a .tar archive file, so you will also need 7-Zip or another file extracting utility to extract files from the tar file.
Odin 1.7 (higher versions will likely not hurt either)
Heimdall (in case Odin doesn't work or you aren't running Windows)
Upgrading to Gingerbread
Make sure your PC has the drivers for your Tab. If you've already connected your PC to the Tab before, you already have them. Otherwise, plug your Tab into your PC and let the drivers install automatically. This works even if you're in Download Mode. If they don't install automatically, you might need to download Samsung Kies or just the Samsung USB Driver for Mobile Phones to get the driver to install.
[FOR HEIMDALL USERS]
You will need to plug in your Tab and run zadig.exe for your drivers, which is found either in the same folder as your Heimdall.exe or in the Drivers folder in that same folder, depending on which version you have. From there, select Options -> List All Devices, then select Gadget Serial or Android USB Composite Interface, then click Install Driver.
After getting the drivers, unplug your Tab (you can keep the PC end plugged in). Turn off your Tab and plug your USB Interface cord into your PC (not the Tab just yet), then put your Tab into Download Mode. You can do this by either holding down the Power and Volume Down keys while the Tab is off, or simply holding down the Volume Down key while plugging in the cord to your Tab. If done correctly, you should see a screen with a yellow Android with a shovel, together with the words "DOWNLOAD MODE, DO NOT TURN OFF TARGET!"
If you're running Windows and using Odin, extract the gt-p1000_mr.pit from the .tar archive into the same folder as the archive. Otherwise, if you're running Heimdall, extract the entire archive into the same folder as your Heimdall.exe.
Plug your Tab back in if you haven't already. The next step will vary for Odin and Heimdall users.
[FOR ODIN USERS]
Open Odin and check if there is a yellow box amongst all the white ones which says [COM4] or something like that, it doesn't matter as long as the box is yellow.
Click PIT and select the gt-p1000_mr.pit you extracted from the stock Japanese GB .tar file, then click Start. This will re-partition the device, and it is absolutely critical that this is done first, as missing this step can cause a brick.
After the PIT flashing is successful, click Reset, then click PDA and select the stock Japanese GB .tar file, and click Start. You will have to wait for a few minutes while the ROM flashes. Progress bars will appear both on the Tab screen and Odin.
NOTE: If after flashing you boot into Recovery Mode and you get the following error:
Code:
E: part(1) DATA Checksum Error
E: part(1) Checksum Error
Internal MMC checksum verify failed.
Then you will have to download and flash dbdata.tar as PDA (Google "P1000 dbdata.tar"; it's about 1.25MB or so). That should solve it.
[FOR HEIMDALL USERS]
Since you already extracted the contents of the stock Japanese GB .tar file into the same folder as your Heimdall.exe, all you have to do is run the following command from a Terminal window (or Command Prompt if you're running Windows):
Code:
heimdall flash --repartition --primary-boot boot.bin --cache cache.rfs --dbdata dbdata.rfs --factoryfs factoryfs.rfs --pit gt-p1000_mr.pit --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage --verbose
Wait a few minutes while Heimdall flashes the ROM. It should inform you when the flashing is successful.
After the flashing is successful, you should now be running stock Android 2.3 Gingerbread. You can stop here or continue on to the Gingerbread Users section for flashing a custom ROM.
Gingerbread Users
Since you're already on Gingerbread, which is the latest stock Android version you have, you're probably reading this guide to find out how to install custom ROMs. Personally I've found, after bricking my Tab a couple of times, that trying to flash custom ROMs from the stock Japanese GB ROM doesn't work unless you flash the Overcome kernel and ROM first.
Hence, the first step to getting a custom ROM running on an SC-01C is to flash the Overcome kernel. For instructions on how to do this, go to the guide thread at the end of the paragraph. You can skip the restocking part, as you're already running stock GB. Instead, follow the instructions from Step 7 of the guide, found on Page 10. After following the instructions there and flashing the Overcome kernel and ROM, you should now be able to flash any other custom ROM you want, following the instructions for the regular P1000.
Getting the Overcome kernel and ROM: http://forum.xda-developers.com/showthread.php?t=1881981
Questions, Answers and Possible Issues
My SC-01C is stuck at boot logo after trying (and failing) to flash custom ROM.
Solving this issue depends on your firmware version and whether or not you can still get into Download Mode. If you can, just follow the instructions in this guide exactly and the problem should be solved.
My SC-01C is stuck at phone-exclamation mark!-computer screen.
This is also likely because of a failed ROM flashing or firmware upgrade. In that case, you can use Heimdall OneClickUnbrick to fix it. A guide to do so can be found here.
My SC-01C isn't detected by Odin, and/or Heimdall produces a "Claiming interface failed" error.
Your drivers aren't being detected and either need to be installed or reinstalled. To force a driver reinstall on Windows, plug in your Tab, go to the System Tray, right-click Safely Remove Hardware and Eject Media, then select Open Devices and Printers. Find your Tab's device name from there, then right-click it and select Remove Device, then unplug your Tab and plug it in again. The drivers should reinstall automatically. If they still don't reinstall, download Samsung Kies or the Samsung USB Driver for Mobile Phones and try again.
For other possible questions or concerns, please reply to this thread.
After successful repair, No Network/ No service
I followed the first method and recovered a bricked P1000 docomo
But No network/service
Any ideas ?
dannyogolo said:
I followed the first method and recovered a bricked P1000 docomo
But No network/service
Any ideas ?
Click to expand...
Click to collapse
You'll need to modify it further to get it to work with other providers. I'm personally not sure if it's a hardware or a software hack, because I paid someone to unlock my Tab back when I didn't know jack **** about modding. If it was already unlocked prior to being bricked, try to flash a new ROM over it. Either way, please hit back if you find the answer so I can add it to the FAQ section.
Hi! I just got the SC-01C & it was already loaded with a custom ICS firmware. Would it be ok to flash another custom firmware DIRECTLY? or Do I still need to flash the GB first?
only root
how to root without change stock rom?
It is possible ?
Thank you
zmeus said:
how to root without change stock rom?
It is possible ?
Thank you
Click to expand...
Click to collapse
Yes it's possible, just Google "how to root galaxy tab". There's a few methods, so just pick one.
Sent from my GT-P1000 using xda app-developers app
Thank you
This it will help me for sure.
Sent from my GT-I9100 using Tapatalk 4
"Hi im a noob and i hate myself"
finally found a thread that that covers japanese p1000.
I have a one it was given to me and still on android froyo 2.2 it is been unlocked by software and i don't know if its been rooted or not.
for the past days i've been looking over the net for this particular device to be upgrade to the latest jellybean rom.this will be very helpful for me since i dont know anything about flashing. been reading threads over and over bec i dont want to brick this device for i use it as a secondary phone
Will flashing to the original docomo GB 2.3... stock firmware make the tab in an locked state again? and is the new rom like the cyanogenmod 10.1 or 10.2 have a built in unlock?
joevinz said:
"Hi im a noob and i hate myself"
finally found a thread that that covers japanese p1000.
I have a one it was given to me and still on android froyo 2.2 it is been unlocked by software and i don't know if its been rooted or not.
for the past days i've been looking over the net for this particular device to be upgrade to the latest jellybean rom.this will be very helpful for me since i dont know anything about flashing. been reading threads over and over bec i dont want to brick this device for i use it as a secondary phone
Will flashing to the original docomo GB 2.3... stock firmware make the tab in an locked state again? and is the new rom like the cyanogenmod 10.1 or 10.2 have a built in unlock?
Click to expand...
Click to collapse
No, 2,3 has an unlocked bootloader. Just follow the guide carefully step by step and you should be fine.
geno93n0 said:
No, 2,3 has an unlocked bootloader. Just follow the guide carefully step by step and you should be fine.
Click to expand...
Click to collapse
ok that's good to know, i'll prep up first before having a go. just be patient with me pls. bec from time to time i'll be asking you alot if i mess up. . thank in advance. thank button has been used.:good:
joevinz said:
ok that's good to know, i'll prep up first before having a go. just be patient with me pls. bec from time to time i'll be asking you alot if i mess up. . thank in advance. thank button has been used.:good:
Click to expand...
Click to collapse
No problem, ask away. I made a lot of mistakes by experimenting on my own, so I made this guide to make the process easier for people with our model.
Hi i have a problem with SC-01C Gingerbread OMKE2, ive been stuck in boot.bin and it fails to flash the overcome using ODIN, what should i do? pls help
Help I think I am bricked
I have a sc-01c bought in japan...I tried flashing and now all i get is the docomo screen...I think i may have deleted everything on the tab...I can get into dl mode but whether flashing with odin or heimdall i get errors...Is there a way to wipe totally and reinstall from scratch....
WILLIEFRANCE said:
I have a sc-01c bought in japan...I tried flashing and now all i get is the docomo screen...I think i may have deleted everything on the tab...I can get into dl mode but whether flashing with odin or heimdall i get errors...Is there a way to wipe totally and reinstall from scratch....
Click to expand...
Click to collapse
What are you Trying to do? and what errors?
SC-01C
rence.slvdr said:
What are you Trying to do? and what errors?
Click to expand...
Click to collapse
I am trying to install the stock rom using odin. I flash the pit then reboot go back to dl mode and flash the tar(stock) i think i hosed the device...Odin says it passed and it reset...but all i get is docommo screen then after the samsung galaxy screen and it keeps blinking ever few minutes like it cant reboot...I ALSO tried flashing the newer Stock 2.3? and the same issue...
I think I may have mucked up the software but can get into DL mode...any ideas?
I followed the directions but still no joy....Perhaps I am dense...
But basically
Flash pit
reboot
Flash stock
Blinking samsung
Odin says reset and no errors...
WILLIEFRANCE said:
I am trying to install the stock rom using odin. I flash the pit then reboot go back to dl mode and flash the tar(stock) i think i hosed the device...Odin says it passed and it reset...but all i get is docommo screen then after the samsung galaxy screen and it keeps blinking ever few minutes like it cant reboot...I ALSO tried flashing the newer Stock 2.3? and the same issue...
I think I may have mucked up the software but can get into DL mode...any ideas?
I followed the directions but still no joy....Perhaps I am dense...
But basically
Flash pit
reboot
Flash stock
Blinking samsung
Odin says reset and no errors...
Click to expand...
Click to collapse
This happened to me as well, it's why I wrote this guide. Try the Overcome method that I posted in the guide, or search for it in this forum. Also, are you using the stock Japanese GB ROM or just a normal stock ROM? You need to use the stock Japanese Gingerbread ROM. I provided links in the guide.
rence.slvdr said:
Hi i have a problem with SC-01C Gingerbread OMKE2, ive been stuck in boot.bin and it fails to flash the overcome using ODIN, what should i do? pls help
Click to expand...
Click to collapse
Don't flash them all at once. Look at the Overcome guide carefully.
pls help
hi.. im new here and i have a problem with modding my sc01c tab. im already running on official gingerbread SC01COMKE2 firmware and im also rooted. i followed all the steps but always ended up with a soft brick. heres what i did.. i downloaded overcome files from http://forum.xda-developers.com/showthread.php?t=1881981 and followed step by step guide. i flashed Overcome_Kernel_v4.0.0.tar and boot into recovery mode.. then flashed Overcome_7_Series_v4.1.0_Wipe.. but it says cannot open BAD FILE. i redownload even the no wipe version but same happens. i tried to restock using GB-Stock-Safe-v5 but it failed in odin.. whats weird is that when i flashed my tab with official firmware it succeeded without a problem.. can you guys help me here? what did i miss or do wrong? pls dont hate me much im just a noob.
geno93n0 said:
No problem, ask away. I made a lot of mistakes by experimenting on my own, so I made this guide to make the process easier for people with our model.
Click to expand...
Click to collapse
ah finally had the time to modd my docomo tab, heres what happened, fashing the pit file went ok, but flashing the rom went haywire ended up brick. i did everything to the letter but to no success. i manage to unbrick the tab and redo the whole thing but i always end up bricking it. rom fails to flash. any ideas? should i be rooted in froyo before doing this?
ah finally after countless trial and error finally updated my tab to gingerbread, now next step is to root and install clockwork recovery mod. i will not rst until my tab gets the lates jellybean rom hahahah,
Hi all,
I am really hoping someone can help me. I have a Sprint Samsung Galaxy S4 (Non T version) that appears to be soft bricked. My phone was hanging on the yellow Sprint screen so after other procedures, I decided to try and ODIN a stock version. What I had before all this happened was MK2 (knox) stock with only CF Auto Root. I downloaded the MK2 stock ROM from XDA and tried to ODIN. It failed. It got through the majority of the process and then at the very end it said FAILED. Now if I try and boot the phone, it automatically goes into the firmware error screen. So I still have the ability to ODIN but it always fails. I have also downloaded the NAE stock ROM from XDA and tried that too. I have tried using Odin 3.07, 3.09, and even 1.85. All fail. On the screen I sometimes get these messages as the ODIN process fails. Either a start [2xx, 1440] and next line BAR [2xx, 1440], or I get a start and then a sw rev check fail fused 5 binary 4. These are all in red letters just underneath the download mode details. I really don't know what to do. Please help me recover my phone. Any help is greatly appreciated. Thanks so much!
IF your phnone was on an NAE firmware you will probably have problems going back to MK2.
Search for the NAE firmware .tar and try that.
@SuperG03
So great to see you posting back after asking for help.
So cool when people contribute to what worked and didn't so that others can be helped and help to contribute to the community at large.....
Oh, wait you didn't.
Guess all is good.
smmmeeesh.
leaderbuilder said:
IF your phnone was on an NAE firmware you will probably have problems going back to MK2.
Search for the NAE firmware .tar and try that.
Click to expand...
Click to collapse
As I mentioned in my OP, I tried the NAE firmware with multiple attempts on various editions of Odin. All without success.
leaderbuilder said:
@SuperG03
So great to see you posting back after asking for help.
So cool when people contribute to what worked and didn't so that others can be helped and help to contribute to the community at large.....
Oh, wait you didn't.
Guess all is good.
smmmeeesh.
Click to expand...
Click to collapse
I'm sorry, it's been like a day and a half and I've been trying like crazy to figure out how to fix this thing... Not sure how fast you expect me to reply, but I do appreciate any and all help.
SuperG03
Just really wondering if you attempted the suggestions. And or what you've done to get it to work.
It gets old trying to assist people, especially when they make it sound so urgent, and then never hearing back.
Hope you get it working.
Good luck!
leaderbuilder said:
Just really wondering if you attempted the suggestions. And or what you've done to get it to work.
It gets old trying to assist people, especially when they make it sound so urgent, and then never hearing back.
Hope you get it working.
Good luck!
Click to expand...
Click to collapse
I definitely understand trying to help and not ever hearing back would get annoying... However, for the first like half a day I checked back at this thread every hour or 2 and it had a lot of views but not any replies. Even as of now, there hasn't been a reply with a suggestion of what to do that I haven't already stated I did try in my OP (you suggested NAE and I had been trying that already). I do appreciate you at least trying though.
SuperG03
SuperG03 said:
Hi all,
I am really hoping someone can help me. I have a Sprint Samsung Galaxy S4 (Non T version) that appears to be soft bricked. My phone was hanging on the yellow Sprint screen so after other procedures, I decided to try and ODIN a stock version. What I had before all this happened was MK2 (knox) stock with only CF Auto Root. I downloaded the MK2 stock ROM from XDA and tried to ODIN. It failed. It got through the majority of the process and then at the very end it said FAILED. Now if I try and boot the phone, it automatically goes into the firmware error screen. So I still have the ability to ODIN but it always fails. I have also downloaded the NAE stock ROM from XDA and tried that too. I have tried using Odin 3.07, 3.09, and even 1.85. All fail. On the screen I sometimes get these messages as the ODIN process fails. Either a start [2xx, 1440] and next line BAR [2xx, 1440], or I get a start and then a sw rev check fail fused 5 binary 4. These are all in red letters just underneath the download mode details. I really don't know what to do. Please help me recover my phone. Any help is greatly appreciated. Thanks so much!
Click to expand...
Click to collapse
So now I would like to reply as to try and help anyone else that might have had something similar to this happen to their phone. I DID FIX my phone but using a CRAZY method that I have no good idea of why it worked. So here goes...
LONG VERSION (Short Version below for those that don't want to read about all my trials and efforts):
So as I mentioned I was on MK2 before the problem started. I tried to ODIN the MK2 Stock ROM I downloaded here but it failed. So then I decided ok maybe the issue was the older ROM, so I downloaded the NAE Stock ROM and tried to ODIN that. Again, failed. Now both of these 2 tries got far into the process before they failed. So again, through reading various posts here and on other forums it was suggested to try with other version of ODIN (I had been trying 3.07). I then tried the MK2 ROM again but with ODIN 3.09 but it failed almost immediately. That is when I noticed the lines "SW Rev Check Fail Fused 5 Binary X" every time it tried and failed. My guess is that this has something to do with the whole not being able to downgrade ROMs at any point and since I had almost completed the NAE stock ROM ODIN flash, it was stuck only with the option for NAE. So then onto trying NAE with ODIN 3.09. Once again, got most of the way done but failed toward the end of the system.img.ext4 part. I kept noticing that on the screen, almost as soon as I started the ODIN process it would output a line saying Start [220, 1440] and then soon after a line saying BAR [224, 1440]. Now I still have no idea what any of that means, but it was always failing, mostly toward the end of the flash. I then tried other ODIN versions including 1.85. All with the same results. I was at a loss. At that point I got desperate and decided I wasn't even going to try and save my DATA and thought maybe the partitions got corrupted so I found the NAE PIT file from these forums and attempted to ODIN both the PIT and the PDA with re-partition option. Once again, all attempts with all ODIN versions failed, with the same START and BAR messages showing up. I then broke down and decided to post here for help. I kept reading but everyone kept just saying in other threads about maybe KIES interfering if it was active in anyway, etc. so I check my processes and there were no KIES ones running. At that moment something occurred to me about another process by which to flash that I remember from my Galaxy S2 days. That was Heimdall. So, I decided to go on a mission to learn how to use Heimdall myself without a ready package. I finally learned how and decided to try it. I had to extract out all the .bin and .ext4, etc files out of the NAE tar and load them up manually. I started to flash and it looked to be working but then alas, it failed similarly to how ODIN did. I was at my wits end by this point. However, something occurred to me when I realized that the .tar had all these independent files in it that ODIN just tried to do all together. So here is what I did that finally WORKED. I used ODIN 3.09 with the NAE PIT file and the NAE ROM PDA file. I checked only Re-Partition and unchecked all others. I then watched exactly what ODINs log said was being flashed to the phone and what failed. I kept re-flashing until I got passed the system.img.ext4 file and the it failed on one of the others. I made note at which files out of the 13 that came from the .tar file were sent by ODIN successfully before it failed. I then closed ODIN and restarted phone in download mode and went to Heimdall. I used Heimdall to manually select only the remaining files left of the 13 that DID not go through successfully. I then flashed those I think 3 or 4 files and it said it was successful. I then rebooted my phone and to my SHOCK the phone booted up successfully and went into the OS as if it was factory wiped and ready for first time use. I was a bit bummed about having to redo all my settings, etc again and losing my old Text Messages, etc, but was so happy to have my phone back up and running. Thanks for reading this whole thing (I know it was quite long) and I hope it helps someone else out of a similar jam.
SHORT VERSION:
GET NAE Stock ROM
GET NAE PIT File
GET ODIN 3.09
GET Heimdall
YOU WILL LOSE YOUR DATA
Step 1) Use ODIN 3.09 (Run as Admin) and load up PIT file and PDA. Uncheck everything but RE-Partition
Step 2) (Hard Part) Keep flashing over and over again until you get at least the system.img.ext4 part to go through before ODIN says FAIL (It should fail on another file, like hidden.img.ext4 or NON-HLOS.bin
Step 3) Scroll through the ODIN log on the left and note every file that was successful. Basically any files it says was successful until the last one that it stops at and says FAIL
Step 4) You will need to extract out the contents of the NAE Stock ROM tar file to another directory
Step 5) Use Heimdall frontend (Run as Admin) and use the flash tab
Step 6) Load the PIT file into Heimdall as that is required for anything. But DO NOT use RE-Partition option
Step 7) Click Add and select each of the remaining files with their appropriate Partition Name and browse for those files from the ones you extracted from the tar. There are 13 files total from the tar file. Just load up (Add) starting with the file that failed in ODIN and then load up whichever ones that did not show up on the ODIN log at all. Click Start and cross your fingers
Step 8) If all went well, the phone should reboot and be up and running. If not you might have to start at Step 1 and try again
Step 9) Jump For Joy that your phone is Alive and working again!!!
Once again, I wanted to share my experience with everyone in hopes that it will help someone else out. I have no idea why I had to go to such great lengths of combining 2 versions of FLASHING and doing it piece by piece, but that is for greater minds then me to either know or figure out. I'm just happy my phone is working again! Good luck to anyone else having a similar issue.
SuperG03
hi xda guys this is my story
i have an at&t samsung s4 on android 4.2 i have tried to update it via wifi to 4.4
but no use. a message appear say's " your device is up to date "
i have tied "loki way" it failed
i have tried "odin tool way' it failed it won't complete the process
i have tried samsung kais it fail's too a message says no update for this device
***** i managed to root the device
and then i found the safestrap apk i have insert the TWRP recovery
i have made a backup in case something go's wrong
and i have tries to flash a clean google s4 4.4.4 rom
**** and then the the phone stuck of samsung logo and vibrate often .the TWRP is lost
**** i have tried to recover the the via samsung kias it made it wors
now it have message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
i have tried via odin using the official firmware that i have downloaded. but did not work also
i have tried the kais recovery mode but i did not get the recovery code
help my friend what should i do
nead you help desperately
When you try Odin what fails? Are you using the mdl firmware? I assume you're on MDL? You haven't updated the firmware?
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
jd1639 said:
When you try Odin what fails? Are you using the mdl firmware? I assume you're on MDL? You haven't updated the firmware?
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Click to expand...
Click to collapse
Every time I have had and issue with a ROM or forget to flash loki I have no issues just ODIN back to 4.2.2 MDL. I say try it again.
MF3
jd1639 said:
When you try Odin what fails? Are you using the mdl firmware? I assume you're on MDL? You haven't updated the firmware?
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Click to expand...
Click to collapse
yes my friend
the device firmware ends with MF3
i think it's MDL
it had a 4.2.2 official firmware
but i tried ti flash this rom using safestrap recovery : "GalaxyS4-CWM-6.0.4.4-GT-i9505.tar"
after that my device stuck in samsung logo screen with vibration
i hop hear from you soon
myounis said:
yes my friend
the device firmware ends with MF3
i think it's MDL
it had a 4.2.2 official firmware
but i tried ti flash this rom using safestrap recovery : "GalaxyS4-CWM-6.0.4.4-GT-i9505.tar"
after that my device stuck in samsung logo screen with vibration
i hop hear from you soon
Click to expand...
Click to collapse
YOU DONT FLASH .tar files in recovery ........... i9505 is not your device i337 is yours .. No wonder it bricked ...
this will unbrick your phone FOLLOW INSTRUCTIONS Exactly ... If you are on MF3 your bootloader is locked
http://forum.xda-developers.com/showthread.php?t=2663545
It in the second post ..Full Nb1 update .. Or Mk2 which ever you desire
GalaxyS4-CWM-6.0.4.4-GT-i9505.tar This is not a ROM its a recovery .. I suggest reading a lot more before proceeding .. Your device has a locked bootloader if firmware is MF3 ... Read the Q/A and much more it will save you a ton of time .. You need to flash device specific roms and recoveries else you are gonna crash and burn
If you are on MF3 like you said then you can only flash Safestrap compatible roms .. I need a little more info ???
myounis said:
yes my friend
the device firmware ends with MF3
i think it's MDL
it had a 4.2.2 official firmware
but i tried ti flash this rom using safestrap recovery : "GalaxyS4-CWM-6.0.4.4-GT-i9505.tar"
after that my device stuck in samsung logo screen with vibration
i hop hear from you soon
Click to expand...
Click to collapse
You are on mf3 firmware. Flashing the mdl firmware won't work. That's the problem you're having. I would recommend you upgrade and flash the nb1 tar file. Read this http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 5 using XDA Free mobile app
spirodave said:
YOU DONT FLASH .tar files in recovery ........... i9505 is not your device i337 is yours .. No wonder it bricked ...
this will unbrick your phone FOLLOW INSTRUCTIONS Exactly ... If you are on MF3 your bootloader is locked
http://forum.xda-developers.com/showthread.php?t=2663545
It in the second post ..Full Nb1 update .. Or Mk2 which ever you desire
GalaxyS4-CWM-6.0.4.4-GT-i9505.tar This is not a ROM its a recovery .. I suggest reading a lot more before proceeding .. Your device has a locked bootloader if firmware is MF3 ... Read the Q/A and much more it will save you a ton of time .. You need to flash device specific roms and recoveries else you are gonna crash and burn
If you are on MF3 like you said then you can only flash Safestrap compatible roms .. I need a little more info ???
Click to expand...
Click to collapse
yes my friend
sorry my misstake i have flashed this room : Danvdh-GE-4.4.4-07172014.zip
And it works--
rugmankc said:
And it works--
Click to expand...
Click to collapse
no my friend this rom made my device bootloop / brick
samsung logo only with vibration
***
i think onid is the answer
can any one link me an MF3 stock rom
to try??!!
i can't not find any
I think you missed something--
You can't run aosp roms at all
On MF3 only 4.3 afaik
As mentioned do a lot of reading in those threads before going on--saves headaches--:good:
Best would be to upgrade to NB1, those instructions are in those threads too--:good:
myounis said:
no my friend this rom made my device bootloop / brick
samsung logo only with vibration
***
i think onid is the answer
can any one link me an MF3 stock rom
to try??!!
i can't not find any
Click to expand...
Click to collapse
Im gonna save you a bunch of time ................You are on MF3 ...Your BootLoader is locked ... You can only flash Safe Strap Roms aka HyperDrive or GoldenEye based off stock .. You can only use safestrap to install recovery ... Anything else will render your device useless.
Check the General Section ... Send you a link isn't gonna help ... You need to read multiple threads ...CHECK THE GENERAL SECTION
LOCKED BOOTLOADER= NO AOSP ROMS = ONLY ROMS BASED OFF STOCK
LOOK FOR A THREAD IN THE GENERAL SECTION CALLED DEBRICK
thank for you help all
i have fix it
i have download this link :
https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE
from
http://forum.xda-developers.com/showthread.php?t=2502003
and flash it with oden
what a relief
:highfive:
myounis said:
thank for you help all
i have fix it
i have download this link :
https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE
from
http://forum.xda-developers.com/showthread.php?t=2502003
and flash it with oden
what a relief
:highfive:
Click to expand...
Click to collapse
:good::good::good:
Same issue but mk2 has me struggling
Sorry to hijack, but I didn't want to start a new thread on this same issue.
I have the AT&T S4 i337 , running MK2. I bought it used, and every time it boots up it shows "safestrap disabled" with 2 buttons below: recovery or system. Recovery button takes you to the TWRP recovery, the other button boots the phone. The phone worked well but the stock rom and bloat were killing me (my previous phones were rooted Epic and Relay). I wanted to root and flash a custom ROM but I wasn't aware of the locked bootloader and mk2/mf3 issues with this phone. Now I am soft bricked, and I've tried many ways to fix (odin, recovery flash,adb ), but it always fails. Here is my path, and what I've tried:
1. I rooted using Saferoot.
2. Tried to flash Philz Touch CWM from SD card in recovery (1st BIG mistake). Didn't work, but didn't brick either.
3. I saw guut13's index and ran backups on twrp recovery and on kies.
4. decided to update (before proceeding with a new rom). tried to OTA update, but it failed.
5. tried to install nb1 (stock odin tar) using heimdall (it couldn't find pit file) and odin (failed to complete write).
6. unrooted (hoping to fix update issues) and then tried Kies firmware upgrade. This process hung and I had to force quit. And thus began the soft brick.
This pattern repeated a few times:
7. flash stock mf3 tar with odin [Complete(Write) operation failed]
8. odin'd mk2 tar , then md1, then mf3 again, all fail to complete write.
9. Phone freezes and will only go into download mode (or bootloop).
10. the ONLY thing that odin can flash is a mj9 recovery file (sometimes). then recovery comes up, I wipe dalvik/cache/system (everything but the sd card) and fix permissions.
11. rinse and repeat. lol
12. I find a jflte pit file that will flash by odin.
13. I start trying stock tars again in odin, hoping the pit helps. same failure.
14. tried to odin an entire mf3 package (bootloader, modem, csc, the works). still same write fail.
15. the only file that flashes other than the pit, is a stock mk2 recovery file.
16. tried to slip a stock mk2 rom zip on my sd and flash from there... failed.
17. installed sdk and tried to sideload, but my computer won't recognize my S4. also can't run adb shell. (yes, i installed the platform tools, and opened prompt window from inside the platform tools folder). {perhaps my vmware fusion (Win8) running on my mac (OS 10.9) is causing a port id issue, but odin connects easily every time....hmm....}
18. Tried rubbing the phone against my head and laughing while trying not to cry, softly whispering "I hate your soul...."
19. Tried 5 different usb cables, including 2 blackberry cables that always connect other samsungs to odin.
20. tried factory reset thru stock recovery , which I can still reach by booting and holding volume up. odd note, this recovery says "i337ucufnb1".
So, I have tried odin-flashing every stock rom for i337 (mdl-nc1), but odin fails to write complete, and my phone says "bar 240, 400" or "sw rev check fail".
What can I try next? I can only think maybe to try using a different PC (not easy since I don't know anyone here but mac users) or smashing the phone under my tire..... would uninstalling safestrap help? I feel like theres a confilct between the stock nb1 recovery and safestrap..... but I can't get in the adb shell to delete it.
anyone had these write fails with odin before? I have always thought no matter what happens, I could always factory wipe and start over with a stock rom in odin, but now, the locksmith says no dice.
Thanks for any advice, I am sure I've forgotten a few details, but I hope I gave enough info for those who wish to assist. Thanks.
I would try to find a Windows pc and flash the nb1 tar in Odin
I'm assuming you're using this but if not it's what you want http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I would try to find a Windows pc and flash the nb1 tar in Odin
Click to expand...
Click to collapse
yeah, 4 years ago I had trouble getting virtual pc's to let my mac and epic both speak odin. But I thought now that they connect easily (and flash pits and some recovery with no prob) it was a better match (as in , vmware's Windows 8, running on a 2.8ghz macbook pro).
What stinks is I have a real pc (old tower running xp) for exactly this purpose, but I never got a licensed version of windows on it and the crap I got off torrents doesnt work anymore. I hate the thought of buying a crap PC OS that I will only use once every 3 years.
Epiclectic said:
yeah, 4 years ago I had trouble getting virtual pc's to let my mac and epic both speak odin. But I thought now that they connect easily (and flash pits and some recovery with no prob) it was a better match (as in , vmware's Windows 8, running on a 2.8ghz macbook pro).
What stinks is I have a real pc (old tower running xp) for exactly this purpose, but I never got a licensed version of windows on it and the crap I got off torrents doesnt work anymore. I hate the thought of buying a crap PC OS that I will only use once every 3 years.
Click to expand...
Click to collapse
Yea, my 16 year old has a crap Mac now all he ever uses is my crap Windows pc to play his games. Go figure.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Yea, my 16 year old has a crap Mac now all he ever uses is my crap Windows pc to play his games. Go figure.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
For a wide selection of games (and upgradable graphics), PC has a definite edge over Mac. PC also has the advantage of being cheaper to buy and upgrade. If I were going to game all day or outfit 50+ employee workstations, PC would be the obvious choice. But for day to day, I still like the way Mac works, hands down. (Tho as PC improves, and Mac continues dumbing down for the masses, this gap is starting to shrink, much like the import vs domestic car market.)
If my old PC tower could run Win8, I would just buy a licensed copy and use that for Odin. But I'm pretty sure it's maxed out at xp, tho it might run vista really slowly, lol. My other option is to try bootcamp to boot up my macbook as an actual Win8 PC, but if that doesnt solve the Odin issues, then I've spent money on a microsoft product I can't even use. I like android phones' customizing options and layout better than iphone (no back button? wtf? lol), so unless android starts making latop OS, I guess I'm stuck in this Mac/android limbo...
Epiclectic said:
Sorry to hijack, but I didn't want to start a new thread on this same issue.
I have the AT&T S4 i337 , running MK2. I bought it used, and every time it boots up it shows "safestrap disabled" with 2 buttons below: recovery or system. Recovery button takes you to the TWRP recovery, the other button boots the phone. The phone worked well but the stock rom and bloat were killing me (my previous phones were rooted Epic and Relay). I wanted to root and flash a custom ROM but I wasn't aware of the locked bootloader and mk2/mf3 issues with this phone. Now I am soft bricked, and I've tried many ways to fix (odin, recovery flash,adb ), but it always fails. Here is my path, and what I've tried:
1. I rooted using Saferoot.
2. Tried to flash Philz Touch CWM from SD card in recovery (1st BIG mistake). Didn't work, but didn't brick either.
3. I saw guut13's index and ran backups on twrp recovery and on kies.
4. decided to update (before proceeding with a new rom). tried to OTA update, but it failed.
5. tried to install nb1 (stock odin tar) using heimdall (it couldn't find pit file) and odin (failed to complete write).
6. unrooted (hoping to fix update issues) and then tried Kies firmware upgrade. This process hung and I had to force quit. And thus began the soft brick.
This pattern repeated a few times:
7. flash stock mf3 tar with odin [Complete(Write) operation failed]
8. odin'd mk2 tar , then md1, then mf3 again, all fail to complete write.
9. Phone freezes and will only go into download mode (or bootloop).
10. the ONLY thing that odin can flash is a mj9 recovery file (sometimes). then recovery comes up, I wipe dalvik/cache/system (everything but the sd card) and fix permissions.
11. rinse and repeat. lol
12. I find a jflte pit file that will flash by odin.
13. I start trying stock tars again in odin, hoping the pit helps. same failure.
14. tried to odin an entire mf3 package (bootloader, modem, csc, the works). still same write fail.
15. the only file that flashes other than the pit, is a stock mk2 recovery file.
16. tried to slip a stock mk2 rom zip on my sd and flash from there... failed.
17. installed sdk and tried to sideload, but my computer won't recognize my S4. also can't run adb shell. (yes, i installed the platform tools, and opened prompt window from inside the platform tools folder). {perhaps my vmware fusion (Win8) running on my mac (OS 10.9) is causing a port id issue, but odin connects easily every time....hmm....}
18. Tried rubbing the phone against my head and laughing while trying not to cry, softly whispering "I hate your soul...."
19. Tried 5 different usb cables, including 2 blackberry cables that always connect other samsungs to odin.
20. tried factory reset thru stock recovery , which I can still reach by booting and holding volume up. odd note, this recovery says "i337ucufnb1".
So, I have tried odin-flashing every stock rom for i337 (mdl-nc1), but odin fails to write complete, and my phone says "bar 240, 400" or "sw rev check fail".
What can I try next? I can only think maybe to try using a different PC (not easy since I don't know anyone here but mac users) or smashing the phone under my tire..... would uninstalling safestrap help? I feel like theres a confilct between the stock nb1 recovery and safestrap..... but I can't get in the adb shell to delete it.
anyone had these write fails with odin before? I have always thought no matter what happens, I could always factory wipe and start over with a stock rom in odin, but now, the locksmith says no dice.
Thanks for any advice, I am sure I've forgotten a few details, but I hope I gave enough info for those who wish to assist. Thanks.
Click to expand...
Click to collapse
my friend
if the mk2 is the same mf3
then download this link : https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE
more details here : http://forum.xda-developers.com/showthread.php?t=2502003
place the 4 files in to odin
and flash them... it worked for me
and if not the same as mf3
look for mk2 ota update build from 4 files
it will reset you phone to factory firmware
i hop it will work for you
Epiclectic said:
For a wide selection of games (and upgradable graphics), PC has a definite edge over Mac. PC also has the advantage of being cheaper to buy and upgrade. If I were going to game all day or outfit 50+ employee workstations, PC would be the obvious choice. But for day to day, I still like the way Mac works, hands down. (Tho as PC improves, and Mac continues dumbing down for the masses, this gap is starting to shrink, much like the import vs domestic car market.)
If my old PC tower could run Win8, I would just buy a licensed copy and use that for Odin. But I'm pretty sure it's maxed out at xp, tho it might run vista really slowly, lol. My other option is to try bootcamp to boot up my macbook as an actual Win8 PC, but if that doesnt solve the Odin issues, then I've spent money on a microsoft product I can't even use. I like android phones' customizing options and layout better than iphone (no back button? wtf? lol), so unless android starts making latop OS, I guess I'm stuck in this Mac/android limbo...
Click to expand...
Click to collapse
Consider installing Win7. Licenses can be had cheaply or just install, use for couple days for Odin (before it license locks) then wipe...
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Hello there,
I recently tried to get Android 10 onto my old phone. But i already got stuck on trying to root it. First I could not install new firmware because of FAP lock.
Then when I tried to get around the lock, I tried to root the phone with this tutorial. But Odin failed at hidden.img. Several times. And now I am stuck with "Firmware upgrade encountered an issue Select recovery mode in Kies".
I tried flashing with deleted hidden.img - it does not work. When I add an .md5 extension, Odin says binary invalid. When I remove the ".md5", Odin just crashes.
Any ideas?
If it is somehow important: I once rooted this device, but for some update or app, idk, i went back to normal, I dont really remember. I use Windows 10.
Thanks
tHr4sh3R said:
Hello there,
I recently tried to get Android 10 onto my old phone. But i already got stuck on trying to root it. First I could not install new firmware because of FAP lock.
Then when I tried to get around the lock, I tried to root the phone with this tutorial. But Odin failed at hidden.img. Several times. And now I am stuck with "Firmware upgrade encountered an issue Select recovery mode in Kies".
I tried flashing with deleted hidden.img - it does not work. When I add an .md5 extension, Odin says binary invalid. When I remove the ".md5", Odin just crashes.
Any ideas?
If it is somehow important: I once rooted this device, but for some update or app, idk, i went back to normal, I dont really remember. I use Windows 10.
Thanks
Click to expand...
Click to collapse
there is no Android 10 available for this phone
2gg1 said:
there is no Android 10 available for this phone
Click to expand...
Click to collapse
Well thank you, but that not helping with the issue that i cannot flash my phone with stock rom via odin.
tHr4sh3R said:
Well thank you, but that not helping with the issue that i cannot flash my phone with stock rom via odin.
Click to expand...
Click to collapse
So you have download the samsung drivers? Unzipped the file with result of a .md5 file? connected your phone to the pc with download mode? And then putted the file on the AP section? And clicked start?
Everything i just mentioned (except the .md5) can you find on HighOnAndroid website. Try to get the odin from there.
Please reply if it worked
2gg1 said:
So you have download the samsung drivers? Unzipped the file with result of a .md5 file? connected your phone to the pc with download mode? And then putted the file on the AP section? And clicked start?
Everything i just mentioned (except the .md5) can you find on HighOnAndroid website. Try to get the odin from there.
Please reply if it worked
Click to expand...
Click to collapse
Well yes, I already did all you described, but did not get it from HighOnAndroid (I also tried, but the "samsung drivers" are Malware which is blocked by Windows, so...).
I know how to flash a phone. It just does not work because of some weird Error with the hidden.img. I also saw a ton of other people trying to flash their phone with this Error, but their solutions do not work. So I need someone with another solution.
tHr4sh3R said:
Well yes, I already did all you described, but did not get it from HighOnAndroid (I also tried, but the "samsung drivers" are Malware which is blocked by Windows, so...).
I know how to flash a phone. It just does not work because of some weird Error with the hidden.img. I also saw a ton of other people trying to flash their phone with this Error, but their solutions do not work. So I need someone with another solution.
Click to expand...
Click to collapse
Try get the samsung drivers from samsungs official website
I once again tried it with these drivers. No change.
I just want to tell you, that I am no idiot and I know how to flash a phone. It just is a very specific problem, that occurs a lot apparently: https://www.youtube.com/results?search_query=flash+galaxy+hidden.img+stuck
The problem is, that the solutions posted on Youtube and other places do. not. work. As I explained in my starting post.