Related
When the official German ICS ROM LPY was released I decided to flash it using Odin rather than wait for the official UK ROM for my UK Note. I thought because it was an official ROM there would be little risk and I would be able to replace it with the UK ROM when that was released.
However, now that the official UK ROM is available I find that I cannot flash it with Odin because Odin no longer detects the Note in download mode. I also found that I could not use Kies because although it could detect the Note, it did not recognise it for updates.
I have never rooted my Note or flashed anything other than the official ICS ROM LPY using Odin.
So I had a working Note but no way of returning to a UK ROM or updating the installed German ROM. So I decided to change the CRC code to the German one ODT to match the German ROM and that seems to have fixed the Kies problem. Changing the CRC code does a factory reset but at least I now might be able to use Kies or OTA for future German ICS updates.
If you search using Google you will find loads of people who can no longer use Odin because it no longer detects their phone. Many reasons have been suggested such as bad USB cable, wrong or corrupt drivers, interference from Kies running in the background etc and I have tried those solutions without success. But I believe that in some cases it is the result of flashing the wrong firmware as I did
Some people have then tried to use recovery mode to solve the problem and ended up not being able to use their phone at all. There are others who are stuck on a buggy custom ROM and cannot use Odin to escape.
I am hoping that there will eventually be an official German ICS update that I can flash using Kies or OTA that will replace my current German ROM and allow me to use Odin again to flash the correct UK ROM.
I'm lucky that at least I can still use my Note normally even though it has German firmware. But if I eventually manage to get the UK firmware installed and running again then I will wait for the correct official updates for my Note in future.
You sure have a weird problem. Did you try on a different computer?
Maybe mobile odin could be helping you out, it's in play store.
i know that you really need the correct drivers to let Odin detect your device, installing kies takes care of that, but i know there are separate drivers around here somewhere to so you won't need kies on your PC (it highly interferes with Odin).
I would give you the link but am on my Note now.
Sent from my GT-N7000 using xda premium
Hi, uninstall Kies and reboot your PC. Then download the latest version of kies and install it again. Connect your Note via USB cable and wait for the drivers to get installed. Then put your phone in download mode, close kies and connect the Note to the PC. Wait for Windows to automatically download and install the drivers. Once the drivers are installed, open ODIN. It should detect your phone in Download Mode.
Nirak said:
You sure have a weird problem. Did you try on a different computer?
Maybe mobile odin could be helping you out, it's in play store.
i know that you really need the correct drivers to let Odin detect your device, installing kies takes care of that, but i know there are separate drivers around here somewhere to so you won't need kies on your PC (it highly interferes with Odin).
I would give you the link but am on my Note now.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
If you read some of the many posts by people who cannot use Odin to flash any more then you will see people have tried different computers, separate drivers, Kies drivers, starting Odin in administrator mode, several cables including official Samsung USB cable, trying Kies Mini, using Task Manager to stop any Kies software running whilst using Odin etc. but to no avail. Which is why I believe the problem for some people is within the Note and not the PC.
Unfortunately, in order to use Mobile Odin you need to be rooted and you need to use Odin get root. Although I read a post here recently where someone had developed a way to root without using Odin. It would be interesting to hear from anyone who has used that non-Odin root method to use Odin Mobile to flash a new ROM.
lifehijack said:
Hi, uninstall Kies and reboot your PC. Then download the latest version of kies and install it again. Connect your Note via USB cable and wait for the drivers to get installed. Then put your phone in download mode, close kies and connect the Note to the PC. Wait for Windows to automatically download and install the drivers. Once the drivers are installed, open ODIN. It should detect your phone in Download Mode.
Click to expand...
Click to collapse
I tried your method but to no avail because I think my problem and many others is within the phone rather than the PC.
Gaugerer said:
If you read some of the many posts by people who cannot use Odin to flash any more then you will see people have tried different computers, separate drivers, Kies drivers, starting Odin in administrator mode, several cables including official Samsung USB cable, trying Kies Mini, using Task Manager to stop any Kies software running whilst using Odin etc. but to no avail. Which is why I believe the problem for some people is within the Note and not the PC.
Unfortunately, in order to use Mobile Odin you need to be rooted and you need to use Odin get root. Although I read a post here recently where someone had developed a way to root without using Odin. It would be interesting to hear from anyone who has used that non-Odin root method to use Odin Mobile to flash a new ROM.
Click to expand...
Click to collapse
I've rooted my stock ICS following this thread:
http://forum.xda-developers.com/showthread.php?t=1647148
no odin involved.
But i never used MobileOdin.
Nirak said:
I've rooted my stock ICS following this thread:
http://forum.xda-developers.com/showthread.php?t=1647148
no odin involved.
But i never used MobileOdin.
Click to expand...
Click to collapse
Yes, that is the method I was talking about. You could try MobileOdin available in Google Play to see if you can run it and perhaps flash a rom. That would be interesting for it would eliminate all the PC problems.
Gaugerer said:
Yes, that is the method I was talking about. You could try MobileOdin available in Google Play to see if you can run it and perhaps flash a rom. That would be interesting for it would eliminate all the PC problems.
Click to expand...
Click to collapse
Why don't you give it a go yourself:
http://forum.xda-developers.com/showthread.php?t=1347899
I've just set up my device as i wish and have no intention of flashing it again..sorry
I am on LPY and was able to flash SpeedMod via PC Odin with no problems.
Try different USB port and use the original Samsung USB cable. I never used Kies before, so I am not sure about this part. I used to setup the driver installer only.
Hope it helps..
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,
I tried installing Cyanogen Mod but it didn't work, I just got stuck at the boot screen and when I tired to flash back to stock something really went wrong.
Now all I see is an error saying "Firmware upgrade encountered an issue. Pleas select recovery mode in Kies & try again."
But I can still access download mode so from what I can tell I can fix this with the right files and right settings in Odin3.
I have the Sprint Galaxy S4 SPH-L720. I am currently running Odin3 v3.07.
I was trying to flash this in Odin3, qbking77.com/development/how-to-unroot-and-unbrick-the-samsung-galaxy-s4. I got as far as system.img.ext4 before it failed.
Any help would be greatly appreciated. I am still somewhat new to hacking my phone but an very tech savvy and feel comfortable following any directions you have for what to flash with odin3 and what options to use.
Thanks in advance.
Ryan990 said:
I tried installing Cyanogen Mod but it didn't work, I just got stuck at the boot screen and when I tired to flash back to stock something really went wrong.
Now all I see is an error saying "Firmware upgrade encountered an issue. Pleas select recovery mode in Kies & try again."
But I can still access download mode so from what I can tell I can fix this with the right files and right settings in Odin3.
I have the Sprint Galaxy S4 SPH-L720. I am currently running Odin3 v3.07.
I was trying to flash this in Odin3, qbking77.com/development/how-to-unroot-and-unbrick-the-samsung-galaxy-s4. I got as far as system.img.ext4 before it failed.
Any help would be greatly appreciated. I am still somewhat new to hacking my phone but an very tech savvy and feel comfortable following any directions you have for what to flash with odin3 and what options to use.
Thanks in advance.
Click to expand...
Click to collapse
Try these links from this post buddy
http://forum.xda-developers.com/showthread.php?p=46273175
The #1 misfit
of my crew of misfits
Ryan990 said:
I tried installing Cyanogen Mod but it didn't work, I just got stuck at the boot screen and when I tired to flash back to stock something really went wrong.
Now all I see is an error saying "Firmware upgrade encountered an issue. Pleas select recovery mode in Kies & try again."
But I can still access download mode so from what I can tell I can fix this with the right files and right settings in Odin3.
I have the Sprint Galaxy S4 SPH-L720. I am currently running Odin3 v3.07.
I was trying to flash this in Odin3, qbking77.com/development/how-to-unroot-and-unbrick-the-samsung-galaxy-s4. I got as far as system.img.ext4 before it failed.
Any help would be greatly appreciated. I am still somewhat new to hacking my phone but an very tech savvy and feel comfortable following any directions you have for what to flash with odin3 and what options to use.
Thanks in advance.
Click to expand...
Click to collapse
Been there (that screen is still odin mode). Should be recoverable through odin still. In my case, the problem was that I had a bad tar file. I'd start there, make sure you have the right file for your phone. If you have the right file, it may be a bad download. So I would try to re-download, or naybe try a different version.
Cheers.
Sent from my SGH-M919 using xda app-developers app
Oscar_david said:
Been there (that screen is still odin mode). Should be recoverable through odin still. In my case, the problem was that I had a bad tar file. I'd start there, make sure you have the right file for your phone. If you have the right file, it may be a bad download. So I would try to re-download, or naybe try a different version.
Cheers.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
I had used the exact file before so I know its correct and uncorrupted. I did figure it out.
Successfully flashed using another computer. Best I can figure, following the CM installation instructions have a step "Run the included zadig.exe in the drivers folder of the Heimdall Suite."
That does something with drivers that odin must not like. I tried uninstalling, restarting my computer than reinstalling the Samsung drivers but that was not enough. A new computer was the answer.
Ryan990 said:
I had used the exact file before so I know its correct and uncorrupted. I did figure it out.
Successfully flashed using another computer. Best I can figure, following the CM installation instructions have a step "Run the included zadig.exe in the drivers folder of the Heimdall Suite."
That does something with drivers that odin must not like. I tried uninstalling, restarting my computer than reinstalling the Samsung drivers but that was not enough. A new computer was the answer.
Click to expand...
Click to collapse
Wow what one file can do to mess everything up and glad you got it working again buddy
The #1 misfit
of my crew of misfits
Bigger question here is:
Why are some phones experiencing corrupt partitions after flashing AOSP-based ROMs? Myself included....
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
Hi,
Currently there is not much on the phone, at least nothing to start up. I had CM, but had to go back so I tried the guide posted on this forum. With little success. So now im not sure where I stand as the phone is in a state without a ROM. When I try to start up normally i get "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Anyone can help me with installing fresh stock Samsung ROM?
Thanks in advance!
Sincerely,
Tho_kva2
Which was your last stock rom bevor you installed cm?
And which stock rom did you try to flash after cm?
Did they had the same product key?
Was the flashing process successful or did odin say "fail"?
And how is your current knox status? 0x1?
Send from my Galaxy S4 using Tapatalk
Not sure, but my phone was up to date with the latest update from Samsung.
I first tried to use "Norway (telenor)" first as, and when that failed I tried "Norway 4.4.2" Both found in the second post of the Guide.
Product key?
Odin said Fail. I tried multiple times with different odin versions and with PIT file.
Is it the "Knox warranty void" is so 0x1
And the latest original firmware running on your phone was it a Norway (telenor) firmware?
With product key i meant the csc.
The old firmware and the one you want to flash now have to have the same csc, i guess.
You can also flash a custom recovery and try to wipe and then flash again.
Send from my Galaxy S4 using Tapatalk
I'm not sure what the original firmware was, but it was the stock firmware i got with the phone when i bought it + updates.
CSC is TEN (Norway)
I do not know how to do a custom recovery, im a total noob on this subject of flashing and modding phones. Got any kind of guide or directrions to point me in? Sorry for not knowing squat, but hope you or someone else here can help me!
Hi,
okay, before you flash a recovery, you can try to flash another firmware but it have to be android 4.4.2 norway TEN
Did you also follow this note here?
"Odin troubleshooting:*If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Use pit file.
- Try another computer."
When odin will continue failing then try this.
http://www.usp-forum.de/downloads.php?do=file&id=1531
This is a 4 part open Europe firmware. Try to flash it...First time without pit,when odin failed try with pit...
If nothing helped, then you can install a custom recovery.
You once installed a recovery, before you flashed CM, remember?
But I will look for a guide and the right files.
Send from my Galaxy S4 using Tapatalk
It worked with the European version! Cheers mate Oh, it was without the pit.
Atleast android is installed hehe. but keyboard keeps crashing so cant type anything, and I cant turn on wifi; I get "Security notice, your device's security has blocked an action that is not permitted. No further action is required" -Knox Notification Manager.?
Oh and I got no SIM card to try at the phone atm. will get it later
So waht should be the next step?
Did you rooted this firmware already?
Try to fullwipe again. I thought this message only pops up, when the devise is rooted and Knox still not deleted... mysterious
Send from my Galaxy S4 using Tapatalk
I did not root it. I will try to wipe
Edit:
****ed up. Tried flashing the same again, and it failed lol.. so now im back to where I was before the phone "worked" again.
So I think I should get a recovery. Any thought?
Lol that's crazy. Also tried 4 part with pit?
And when you flash a Norway firmware again? Maybe it will work now, i don't know what's going on there
http://forum.xda-developers.com/showthread.php?t=2397108
This is CWM recovery for i9505, you have to flash the .tar file with odin in PDA or AP. It's your choice, whether you install the touch or non touch version.
Edit: anything new?
Send from my Galaxy S4 using Tapatalk