Related
Hi, I was following this guide http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S:_Full_Update_Guide found on http://forum.xda-developers.com/showthread.php?t=1298691.
I got as far as the Installing the ClockworkMod Recovery, when I got to step 8 'Click Start on the Heimdall Frontend. A blue transfer bar will appear on the phone showing the kernel being transferred. The device will reboot automatically.' BUT when the phone tried to reboot it gets stuck on the first Galaxy S screen. I could get in to download mode and recovery mode but nothing else. Does this mean my mobile is bricked? What do I do know?
Thanks in advance
You have flashed a rom, not only root your device. And cyanogenmod is not based on samsung firmware.
Think you shold read some more.
But, how long do you wait on the s logo? It thakes some time to boot up first time when catche is wiped.
If you only want to root you shold search for cf root for your stock rom. If you want to go back, you have to download a stock rom. Found att samfirmware.com
Sent from my GT-I9000 using Tapatalk
No not bricked (nowhere near)............ Reflash...
I have read many times that re-flashing will do the trick. If you have download mode, you can flash any rom onto it, i would use odin as it may be the safest whilst you being in limbo. Then if you want to follow a link for CM 7.1 that is both v.entertaining (my opinion) and clear i suggest you click on the link in my sig...
Robert - Sorry I did mean flash as well as root. I waited around 15-20 minutes, isnt that long enough?
Talon - I have tried to re-flash using the guide method I was originally using but get the same problem. To be honest from looking at Odin information on this forum, it has confused me quite a bit (lot of different advice), not sure if I am doing the right thing.
I did make the mistake of jumping into trying to flash & root my phone. Any help of what to do to get my phone to a working state, would be very much appreciated.
@OP: as long as you can put phone in Download mode - it is not bricked.
ALWAYS, you can restore everything by flashing stock ROM with repartition.
If you will not be able to go to download mode - well... then you have something to worry about
spamtrash said:
@OP: as long as you can put phone in Download mode - it is not bricked.
ALWAYS, you can restore everything by flashing stock ROM with repartition.
If you will not be able to go to download mode - well... then you have something to worry about
Click to expand...
Click to collapse
I'm a bit confused, what would be the best way to do that?
Well find stock FW from below, then flash it using the guides..
Generally now days you get 2 files, Pit either 512 513 or 813 (or something similar). And you get a .tar file or other zip type extension and put that in pda. Then flash
you may get 3 files and a pit file in which case you put it in the appropriate places....
Ive written this guide and telling you it is a GUIDE. Wherever you get your files from there should be instructions as to what to do.
For example you may need to do a factory reset before (unlikely but still) More likely is that you will have to disable lagfix, but you shoudnt have to worry about that. Main thing read the guide and follow the guide from where you get the files. The thread you get it from...read the first and last 5 pages, more if you want to be safe.
Now files, i have links to stock FW below, guide are usually present within them. If not read the thread, but also read the thread and search th thread for answers or the section or the SGS forum.
IF before you were on 2.2.x - try some Froyo from sammfirmware. If you were on Ginger - try Click
Of course, you can search for EAzyBase... but it is more advanced, start from the basics...
OMG, there are tons of tutorials and how to's in here about flashing and rooting phones... who uses heimdall? get Odin for flashing:
1. Install KIES for drivers (you might already have done this).
2. Get a rom from samfirmware/sammobile, I recommend JVP because it has gingerbread bootloaders: http://www.sammobile.com/threads/17-Samsung-I9000-Galaxy-S-Firmwares
3. Get Odin (sorry I coudn't find a link)
4. Get your phone in download mode (VolDown, Home, Power).
5. Connect your phone to PC with USB cable.
6. Set the PDA, CSC and MODEM files in Odin from the firmware you downloaded from step2.
7. Make sure you have "re-partition" enabled and set the .PIT file to use the *512.pit also included in the firmware from step 2.
8. click start.
9. Start your phone and set up the startup wizard.
9. For rooting, get the CF-root for your firmware from here: http://forum.xda-developers.com/showthread.php?t=788108
10. Get your phone into download again.
11. DON'T check repartition in odin, only select the CF-Root file as PDA (you have to use the CF-Root-***.TAR, important to use .TAR and not .ZIP.
12. Flash again, now you are rooted!!
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,
It looks like I got myself in a pickle. I have a GS4 running 4.2.2. I picked up my phone today and successfully rooted it with instructions from DroidView using files from chainfire. I then installed CWM recovery with ROM Manager and backed up my ROM with it. I decided to replace chainfires SU with the one fom CWM like I had on my S3. After rebooting from recovery mode I noticed I had lost root so I used the same method to root it again because I thought it had reset itself. Before the reboot occurred there was option to prevent the possibility of the ROM flashing itself to stock. I went to select the Yes option but bumped the power button which selected No. While trying to reroot and failing, the phone displayed the message "Invalid percent of drawing download progress bar." On reboot the error “Firmware upgrade encountered an issue“ along with a cone and a couple of other pics. I have tried to get into recovery mode several times but repeatedly get this error. I can get into download mode and have tried to flash the stock ROM for this phone but it fails in Odin 3.0.7. Odin sees my phone and verifies the md5 but fails very quickly upon clicking start. I tried this with KiesPDLR running in the background and disabled. I have not tried anything else out of concern for messing it up further. Attached are screenshots and log from ODIN along with the text that is being displayed in download mode. (I will have to post these later as the attachments option will not work properly on my wife's S3).
Two other notes. 1) I used ODIN 1.85 to root as that was what was included in the chainfire download. But I used ODIN 3.0.7 to try and unroot because that's what the DroidView directions said. Would it make any difference to use ODIN 1.85 to try and flash the stock firmware? It sees my phone as well but the F. Reset Time option is unchecked and grayed out and the directions says it needs to be checked. Don't know if that really makes a difference. 2) My phone is actually with US cellular but there is not a forum for this carrier. I chose this forum because my previous phone the Mesmerize had an identical model number as the Fascinate. Please do not pass over my request for help because of this as I am in dire need.
apel69 said:
It looks like I got myself in a pickle. I have a GS4 running 4.2.2. I picked up my phone today and successfully rooted it with instructions from DroidView using files from chainfire. I then installed CWM recovery with ROM Manager and backed up my ROM with it. I decided to replace chainfires SU with the one fom CWM like I had on my S3. After rebooting from recovery mode I noticed I had lost root so I used the same method to root it again because I thought it had reset itself. Before the reboot occurred there was option to prevent the possibility of the ROM flashing itself to stock. I went to select the Yes option but bumped the power button which selected No. While trying to reroot and failing, the phone displayed the message "Invalid percent of drawing download progress bar." On reboot the error “Firmware upgrade encountered an issue“ along with a cone and a couple of other pics. I have tried to get into recovery mode several times but repeatedly get this error. I can get into download mode and have tried to flash the stock ROM for this phone but it fails in Odin 3.0.7. Odin sees my phone and verifies the md5 but fails very quickly upon clicking start. I tried this with KiesPDLR running in the background and disabled. I have not tried anything else out of concern for messing it up further. Attached are screenshots and log from ODIN along with the text that is being displayed in download mode. (I will have to post these later as the attachments option will not work properly on my wife's S3).
Two other notes. 1) I used ODIN 1.85 to root as that was what was included in the chainfire download. But I used ODIN 3.0.7 to try and unroot because that's what the DroidView directions said. Would it make any difference to use ODIN 1.85 to try and flash the stock firmware? It sees my phone as well but the F. Reset Time option is unchecked and grayed out and the directions says it needs to be checked. Don't know if that really makes a difference. 2) My phone is actually with US cellular but there is not a forum for this carrier. I chose this forum because my previous phone the Mesmerize had an identical model number as the Fascinate. Please do not pass over my request for help because of this as I am in dire need.
Click to expand...
Click to collapse
Try odin 1.85 I use that to odin back to stock and dont worry about the other ones just make sure auto reboot is checked.
Also are you sure the phone you have is the sprint gs4 sph l720 jfltespr?? Cause odin a tar file not for the phone could potentially brick the phone.
Sent from my SPH-L720 using xda app-developers app
I would try to download the stock rom from a different source if you can. These tar files are so large for this phone that the possibility of a bad download is pretty high. Also, make sure you don't have to extract the actual .tar file first from the archive you download. Lots of these stock roms are repackaged into a zip file and you need to extract the tar file for use in Odin before installing.
I am back in business. I have my phone and home internet back now. Yeah. I used the same stock ROM I had since it was the same as sammobile which was also a zip file and I already had it on my system. I just used Odin 1.85 instead. I guess I could have done this earlier and prevented a near stoke but everything else I had done seemed to get me deeper in a hole. These large zip files have always made me a bit nervous but I haven't found where to get one otherwise.
I have some follow up questions.
1) Why would it flash with Odin 1.85 and not with 3.0.7?
2) Is CWM's SU not compatible with the S4? Everything was working fine until I switched this from chainfire to CWM using ROM Manager.
3) Is there a good source with unzipped ROM's?
Chainfires SuperSU is much better with JellyBean than cwm SU. For some reason most people that try to switch to SU from SuperSU have the same problem you had.
Sent from my icrap 2 using Tapatalk HD
Okay. I decided to go with chainfires after this fun little ordeal. The few small things I preferred from CWM is not worth it. Besides it looks like chainfire made some upgrades since I last looked at it. I guess I was lucky with my S3 because I converted several times.
Thanks for all the help everyone.
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....
Searched but and found similar posts but with different phones or different firmware, so the file references were of no help.
Basically I had safestrap working, had flashed google play edition ROM and it was working great with the exception of the play store not wanting to connect. I was in the process of messing with that and read (here) that I needed 4.3 edition of that app, I checked and I had 4.2, so I loaded 4.3 to the Sdcard and installed it..
Phone rebooted and just stays on the samsung custom splash screen indefinitely . I can get to ODIN on the phone, soI tried using https://builds.casual-dev.com/jodin3/ to get access and see what I could do, but it keeps telling me to unplug and plug in the phone, and gives an error that it cant mount the device.
So, im kinda stuck, I didn't use ODIN to do anything previously, But considering its the only thing I currently have access to, I guess its my only hope.
Been fighting this a few hours and getting pretty dejected, I had almost everything PERFECT.. and now back to WORSE than where I started.
Wingnutt said:
Searched but and found similar posts but with different phones or different firmware, so the file references were of no help.
Basically I had safestrap working, had flashed google play edition ROM and it was working great with the exception of the play store not wanting to connect. I was in the process of messing with that and read (here) that I needed 4.3 edition of that app, I checked and I had 4.2, so I loaded 4.3 to the Sdcard and installed it..
Phone rebooted and just stays on the samsung custom splash screen indefinitely . I can get to ODIN on the phone, soI tried using https://builds.casual-dev.com/jodin3/ to get access and see what I could do, but it keeps telling me to unplug and plug in the phone, and gives an error that it cant mount the device.
So, im kinda stuck, I didn't use ODIN to do anything previously, But considering its the only thing I currently have access to, I guess its my only hope.
Been fighting this a few hours and getting pretty dejected, I had almost everything PERFECT.. and now back to WORSE than where I started.
Click to expand...
Click to collapse
The 4.3 edition of SS doesn't work on 4.2. Does it stay on the splash or does it go to the actual boot animation? Also, you don't need to boot into the phone to use odin, it's a PC program. You can google "mf3 tar files" and you'll find the thread with the ODIN files, use them to get back to stock.
DeadlySin9 said:
The 4.3 edition of SS doesn't work on 4.2. Does it stay on the splash or does it go to the actual boot animation? Also, you don't need to boot into the phone to use odin, it's a PC program. You can google "mf3 tar files" and you'll find the thread with the ODIN files, use them to get back to stock.
Click to expand...
Click to collapse
It sits on the Samsung custom screen, that's it.
And how do I use the ODIN files.. When the ODIN program won't do anything except tell me over and over to in plug and plug in the phone?
How do I "use the Odin files" ??
Wingnutt said:
It sits on the Samsung custom screen, that's it.
And how do I use the ODIN files.. When the ODIN program won't do anything except tell me over and over to in plug and plug in the phone?
How do I "use the Odin files" ??
Click to expand...
Click to collapse
Did you install the Samsung USB Drivers? Google that and install them, then plug in the phone and run the program.
DeadlySin9 said:
Did you install the Samsung USB Drivers? Google that and install them, then plug in the phone and run the program.
Click to expand...
Click to collapse
I *think* I already have installed them but I'll double check just in case, I have android file transfer installed, it does the same, I'll try it under windows in instead of Mac as well.
Ok, ODIN sees the phone, under windows, Downloading a MF3 TAR file as seen here http://forum.xda-developers.com/showthread.php?t=2504311
(1.5gb?!) once thats done Ill see what we have![/QUOTE]
Well, im a little stuck
I downloaded a the MF3 TAR file from here:http://forum.xda-developers.com/show....php?t=2504311
Flashed the bootloader: BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.mp5
That went through properly, the phone rebooted..
No change..
what am i supposed to do next?
I flashed the CSC file: CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5
That went through as well, after reboot no change.
Tried flashing the phone file: PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5
but nothing happens, no error message... it just doesent do anything :silly:
a little help?
Wingnutt said:
Well, im a little stuck
I downloaded a the MF3 TAR file from here:http://forum.xda-developers.com/show....php?t=2504311
Flashed the bootloader: BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.mp5
That went through properly, the phone rebooted..
No change..
what am i supposed to do next?
I flashed the CSC file: CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5
That went through as well, after reboot no change.
Tried flashing the phone file: PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5
but nothing happens, no error message... it just doesent do anything :silly:
a little help?
Click to expand...
Click to collapse
You put platform tar in the PDA slot right? Also, you might have to restart between flashes or just load them in all at once.
There's a picture on this post with what options you should have: http://forum.xda-developers.com/showpost.php?p=46955352&postcount=7
DeadlySin9 said:
You put platform tar in the PDA slot right? Also, you might have to restart between flashes or just load them in all at once.
There's a picture on this post with what options you should have: http://forum.xda-developers.com/showpost.php?p=46955352&postcount=7
Click to expand...
Click to collapse
Yep, ive read that thread stem to stern, everything is in the correct slots, I can flash everything EXCEPT the platform file
have tried it by itself, and as added with the rest, either way it same result.
Wingnutt said:
Yep, ive read that thread stem to stern, everything is in the correct slots, I can flash everything EXCEPT the platform file
have tried it by itself, and as added with the rest, either way it same result.
Click to expand...
Click to collapse
Make sure the file you download was full and that it extracted the whole platform file. Other than that i'm not sure why it wouldn't work..
DeadlySin9 said:
Make sure the file you download was full and that it extracted the whole platform file. Other than that i'm not sure why it wouldn't work..
Click to expand...
Click to collapse
Ive downloaded it twice, Ive tried flashing it under windows 7 and OSX. Same result.
I would be happy to try a different platform file, but I cant find any others.
One oddity, the ONLY Odin program that can see the phone is Jodin3, the web based version.
Ive downloaded 1.85 and 3.07 (windows) have updated the samsung USB drivers, have updated the heimdall software... they cant see it.
Wingnutt said:
Ive downloaded it twice, Ive tried flashing it under windows 7 and OSX. Same result.
I would be happy to try a different platform file, but I cant find any others.
One oddity, the ONLY Odin program that can see the phone is Jodin3, the web based version.
Ive downloaded 1.85 and 3.07 (windows) have updated the samsung USB drivers, have updated the heimdall software... they cant see it.
Click to expand...
Click to collapse
Seems like it's not installing the drivers right. I'd try installing again: http://forum.xda-developers.com/showthread.php?t=2038555 or just manually go into device manager and point it to where you installed the drivers. Also, you might have to wait a while on any version of ODIN (even the we version) for it to finish checking the file.
OHHHH ****!
You were right, it was the USB drivers, I had to do it via method 3, I.E. manually select them.. for some odd reason the installer DID install the drivers but the device showed up as someting totally different than when doing it manually.
flashing now... will see what happens:laugh:
ITS ALLLLIIIVVVEEEE!!!!!!!
Ok. so, now I cant start over lol!
Thanks for all your help, everyone!!