ODIN 1.3 Stuck on "cache.rfs" - Vibrant General

been trying forever to fix my phone, finally got it into download mode but odin just hangs? also the phone to PC light goes on when i try to turn it on.. does anyone know what i can do to get my phone back??

Try to odin back to stock and if that doesn't work try a usb jig
Sent from my SGH-T959 using XDA Premium App

odin again on a diff computer. odin can get pissy on some computers. if you can't possibly find another computer to use uninstall the usb drivers, reboot, install usb drivers then try to odin again on a different usb port. also re download the jfd files from here in case of bad d/l's.

Keep trying...Odin likes to be picky sometimes.
Sent from my SGH-T959 using XDA Premium App

And try a newer version of Odin.

k well i went from 1.3 to 1.7 and i was sure it was about to start working because the blue download sign showed up, when it just lagged for a bit.. all of a sudden the screen turned greenish.. and it got stuck at cache.rfs...
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.rfs
what did i do wrong??? is my phone permanantly bricked now?? first time i see this green screen ever

damn now nothing turns onwhen i plug it in, no phone to pc, no download mode.. i think i bricked it for real this time, shieet
edit: so up/down vol plus pluggin in gets me into download mode, but the thing just wont load, the blue status bar just stays on like 5 percent and it hangs on cache.rfs
any suggestions

Try another usb
Unplug other usb devices, reboot
make sure the files are legit by checking the md5
Guide in my signature if needed

s15274n said:
Try another usb
Unplug other usb devices, reboot
make sure the files are legit by checking the md5
Guide in my signature if needed
Click to expand...
Click to collapse
Also try without the sim and micro sd card.
It worked for me before.
Sent from my SGH-T959 using XDA Premium App

If you are using a 64 bits try a 32 i have seen issues with odin and windows 64b
Sent from my GT-I9000 using Tapatalk

happened to me, it turns out its a usb port.
try another if that doesnt work
uninstall the drivers then reboot pc plug in phone then install drivers

Reboot your computer, once it begins starting immediately hold F8.
After a few seconds you will get the Windows Startup Menu.
Select "Disable Driver Signature Enforcement".
Then after computer starts up odin like you're doing and it wont get stuck at cache.rfs.

Sounds like a bad download to me
Beware of angry gingerbread man

try another usb and PC

VeryCoolAlan said:
happened to me, it turns out its a usb port.
try another if that doesnt work
uninstall the drivers then reboot pc plug in phone then install drivers
Click to expand...
Click to collapse
Was a bad USB port!!

Related

FIXED... Cable came unplugged mid ODIN FLASH

Ok.. I was flashing Cognition to my captivate (using ODIN) when the usb cable came unplugged in the middle of flashing factoryfs.rfs.
I can't even get the phone to power on at all... No connect to computer icon, no recovery screen, no download screen, nothing no screen at all.
Any way to recover this? I tried several things
Three Button combo
VOL+ & VOL- while plugging in usb
remove battery and sim
etc...
Here's the ODIN log.
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> Sbl.bin
<ID:0/006> boot.bin
<ID:0/006> cache.rfs
<ID:0/006> dbdata.rfs
<ID:0/006> factoryfs.rfs
<ID:0/006> Removed!!
Please help. Anyone know how to recover from this?
maybe needs to be charged?
try leaving it connected to power for a while..
If it will not turn on you might very well be bricked. As previously suggested, you could leave it plugged in and see if your battery is just drained. However, while you are waiting you can still do your research. Look over this thread: http://forum.xda-developers.com/showthread.php?t=775911 for a discussion on how to unbrick a captivate.
I would also suggest you check this one: http://forum.xda-developers.com/showthread.php?t=731989 as often flashing back to stock will "reset" the errors created while updating roms.
Was >90% battery when i started...
sourkrawt said:
If it will not turn on you might very well be bricked. As previously suggested, you could leave it plugged in and see if your battery is just drained. However, while you are waiting you can still do your research. Look over this thread: http://forum.xda-developers.com/showthread.php?t=775911 for a discussion on how to unbrick a captivate.
I would also suggest you check this one: http://forum.xda-developers.com/showthread.php?t=731989 as often flashing back to stock will "reset" the errors created while updating roms.
Click to expand...
Click to collapse
I can't even boot do download to use ODIN...
FIXED
OK... GOT IT... Here's what I did
1. Remove the battery, external SD card and SIM card.
2. Wait 10 seconds.
3. Open odin3
4. Insert battery.
5. Connect usb cable.
6. HOLD VOL+ and VOL- while plugging in USB
Got download screen and flashed with ODIN..
Could swear I tried that at least twice before posting... also, this varied from http://forum.xda-developers.com/showthread.php?t=775911, but was similar, so may be worth noting.
Yay... I feel better Thanks all.
Don't post things like this in development.
Sent from my Captivate
MikeyMike01 said:
Don't post things like this in development.
Sent from my Captivate
Click to expand...
Click to collapse
Issues that arise while working with a beta ROMS, especially flashing with ODIN (something that is experienced mostly by DEVELOPERS) is not for the development forum...
Anyway, thanks to all that helped
Glad you got it working. Gonna close this up.
I deem this closed

[Q] Another soft brick problem...

I am sorry if this has been asked and answered, I've been searching the forum board for 4.5 hours trying to find the answer or some sort of point in the right direction. If you know the thread to answer my question, please don't flame me, just point it out...
With that said...
I attempted to upgrade my epic 4G from EB13 to EC05 last night. I did this with Odin3, everything said it passed no problem. Yet, it did not work. It would get to the Samsung screen then vibrate, pause, vibrate, pause, then nothing, just stayed there.
I followed the directions to flash the original EB13 that was on the phone to begin with. I followed the directions exactly, Odin failed, big surprise right? Now, Odin simply verified the MD5 said it was good and stopped. Now my phone just gets the 'phone-!-computer' icon, I can still boot into the downloading screen, but am unable to get Odin to do anything, am I missing something, or is there anything I can do to remedy this?
OK, I just tried the Samsung updater for eb13 and it failed at param.lfs
I am befuddled...
Try downloading the tar file for odin again and see ifthat works u might have a bad tar file
Sent from my SPH-D700 using XDA Premium App
Estewa_619 said:
Try downloading the tar file for odin again and see ifthat works u might have a bad tar file
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
It's worth a try but the Samsung updater has it's own tar already. I think the answer he's looking for is in the Wiki.
I've searched through the wiki. Am I missing something? I find the root/recovery programs, they all say how to root, but I am not finding how to recover. for example, "One Click Root and Recovery", even though I cannot boot my phone, will it still recover? I tried it in the download screen, but it does not connect. How do I use these to recover?
I tried redownloading the tar again, SPH-D700-EB13-8Gb-REL.tar.md5, but I get the same result, Odin checks the file says it's OK then stops doing anything.
Am I using the incorrect tar? is there a tar that's not an MD5?
Are you using your stock samsung cable?
Sent from my SPH-D700 using XDA App
From the Wiki-
"If you get a FAILED error after it writes "param.lfs", try this method:
1. Reboot the phone and reset Odin
2. Load the pit file and place the tar in the Phone section
3. Start the recovery
4. The process will hang while writing "factoryfs.rfs"
5. Reboot the phone and reset Odin
6. Load the pit file, place the tar in the PDA section, and start the recovery again
7. It should now complete in about 3 mins.
8. Congratulations! Thank noobnl
If that doesn't work, take out the battery and reboot into download mode with only the usb cord plugged in."
TimidBull said:
I tried redownloading the tar again, SPH-D700-EB13-8Gb-REL.tar.md5, but I get the same result, Odin checks the file says it's OK then stops doing anything.
Am I using the incorrect tar? is there a tar that's not an MD5?
Click to expand...
Click to collapse
Are u in download mode? (#1 on keyboard + power button) and are u putting the tar file under PDA?
Sent from my SPH-D700 using XDA Premium App
Remove the .md5 extension...it messes up Odin.
Do you BONSAI?
kennyglass123 said:
Remove the .md5 extension...it messes up Odin.
Do you BONSAI?
Click to expand...
Click to collapse
This right here, The tar will be tar.md5, simply remove the .md5 from the end and try it.
Odin gives me problems on certain PCs too, if you have another computer, give that a go.
mattallica76 From the Wiki-
"If you get a FAILED error after it writes "param.lfs", try this method:
1. Reboot the phone and reset Odin
2. Load the pit file and place the tar in the Phone section
3. Start the recovery...
Click to expand...
Click to collapse
I tried this already, same result after 25 attempts.
Are u in download mode? (#1 on keyboard + power button) and are u putting the tar file under PDA?
Click to expand...
Click to collapse
Yes I am in download mode, yellow work sign with digging android, "Downloading... Do not turn off Target.
Also yes, to placing the tar under PDA and using the stock cable, plugged directly into a directly soldered motherboard USB port
I am waiting for the tar to redownload, as soon as it does, I'll remove the .md5 extension.
I was trying to bonsai, that's how I got all screwed up.
Well....that didn't work.
Trying it now with the victory pit, and th eb13 tar. without the .md5 extension.
I got a small blue bar starting to show,
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
Been this way for about 5 minutes so far. **CROSSES FINGERS**
An obvious one seems missed. Try it on a different USB port.
Sent from my SPH-D700 using Tapatalk
I tried a different usb port, as well as a different computer, no change. After last attempt as decribed, Odin reported the following
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008>
<ID:0/008> Re-Partition operation failed.
<ID:0/008> Removed!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I attempted this 10 times with the same result.
Hmmm...progress
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> boot.bin
<ID:0/008> cache.rfs
<ID:0/008> datafs.rfs
Click to expand...
Click to collapse
Damn....phone shut off.
Trying again.
How did the phone shut off with a USB cable plugged in it? That makes no sense unless you have a really really bad cable.
Sent from my SPH-D700 using Tapatalk
I was just reading a post in which the user had used odin to put on d18 and he had no issue. Would this be detrimental to my phone since I started with eb13?
Do I need a different pit file instead of the victory_8G_100528.pit?
This is my first Android, been a Palm guy for years, but after my pre problems, I made the change. Theoretically going to older version shouldn't hurt, but I wanted to be sure.
One last thing, I seem to currently be getting to the datafs and nothing seems to happen after that, it's been about 10 minutes in this state, normal?
Thanks all for the help and assistance so far! it is much appreciated.
no idea how it shut off, it was on download screen, then black. took out battery, set back into downloading mode (#1 and power), now back at the datafs point, waiting...
oh, and the cable is brand new, using my wifes cable from her two day old epic.

I ****ed up my phone

I tried rooting it, It ****ed up Then i tried restoring gingerbread via odin it sat there for 2-3 hours stuck on file so i unplugged it ( dumb idea ) now when ever i turn on my phone i get sent to android system recovery <3e> and when i click wipe data / factory reset nothing happens. and when i press the volume down button it doesn't take me to the download screen it just takes me here. Why must i be so retarded.
It says e: failed to mount /data/fota (no such file or directory ) when i first get to this screen.
Sometimes you might be able to get into Download Mode if you do the following.
1) Remove Media Card, SIM and Battery
2) Have Odin up and running
3) Plug in the USB cable
4) While holding volume down plug in the battery
This might get you into Download Mode. I did this myself and ended up sending it back to Samsung in the end.
I then bought a JIG from MobileTechVideos and thats by "oops" backup now. If those steps dont work to get into Download Mode I'd say go get a JIG
Even when the phone wasn't ****ed up I could never get into download mode unless the battery was in.
Do you know for certain the driver is installed and works/worked at one time? Did you ever transfer files from pc to phone in usb mode?
sfd0124 said:
Do you know for certain the driver is installed and works/worked at one time? Did you ever transfer files from pc to phone in usb mode?
Click to expand...
Click to collapse
Yes, I also tried 12 different usb ports and Now I am getting an un authorized battery error and It wont charge and it's almost dead :/
Do you have a verizon fascinate?
Are you able to get into download mode?
Have you tried heimdall?
Im waiting for FedEx to get here with my GNex... If you want to chat via google talk we can try to get it running again. Send me a pm if interested.
That or if you're willing to wait a couple days, order a USB jig off of eBay. The wait will suck, but it beats buying a new phone
Sent from my Galaxy Nexus using xda premium
vilhjalmr said:
I tried rooting it, It ****ed up Then i tried restoring gingerbread via odin it sat there for 2-3 hours stuck on file so i unplugged it ( dumb idea ) now when ever i turn on my phone i get sent to android system recovery <3e> and when i click wipe data / factory reset nothing happens. and when i press the volume down button it doesn't take me to the download screen it just takes me here. Why must i be so retarded.
Click to expand...
Click to collapse
I've unplugged my phone many times during ODIN when it just hangs....not a deal breaker or phone bricker in anyway. The key is to get to download mode.
Go here: http://forum.xda-developers.com/showthread.php?t=1349895 and get the full gb version and the atlas pit file.
Make sure your drivers are current. Take battery out. Plug USB into phone first, then computer, then hold down volume rocker to get into Download mode.
Open Odin, put the pit file in Pit section, the GB file in the PDA section and hit Start.
Also try a differant usb cable
It my be a bad cable
jmac9 said:
I've unplugged my phone many times during ODIN when it just hangs....not a deal breaker or phone bricker in anyway. The key is to get to download mode.
Go here: http://forum.xda-developers.com/showthread.php?t=1349895 and get the full gb version and the atlas pit file.
Make sure your drivers are current. Take battery out. Plug USB into phone first, then computer, then hold down volume rocker to get into Download mode.
Open Odin, put the pit file in Pit section, the GB file in the PDA section and hit Start.
Click to expand...
Click to collapse
Thanks for the replies I really appreciate it, I cannot get into download mode as when i press the volume down it just goes to android system recovery and no where else so I bought a jigg, hopefully It comes soon
Alright so I got my jig and my new charger + battery's but it's still sitting on the same part where it got bricked before on odin it just says
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI500_VZW_EH03_GB_CM.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> param.lfs
<ID:0/003> Sbl.bin
<ID:0/003> boot.bin
<ID:0/003> recovery.bin
<ID:0/003> zImage
<ID:0/003> factoryfs.rfs
<ID:0/003> dbdata.rfs
<ID:0/003> cache.rfs
<ID:0/003> movinand.bin
<ID:0/003> modem.bin
and it's been at that mode.bin for about 40 minutes now... and when this happened last time the battery fell out of the back and that's how it got bricked... should it be taking this long?
Not sure
Bionic
Which Odin files are you using? Some GB Odin tars don't have everything you need to restore from some bricks. Get a Verizon version. Plus it sounds like your using phone instead of PDA. I've done out beefier and had similar symptoms.
Sent from my SCH-I500 using Tapatalk
Stephen.k.spear said:
Which Odin files are you using? Some GB Odin tars don't have everything you need to restore from some bricks. Get a Verizon version. Plus it sounds like your using phone instead of PDA. I've done out beefier and had similar symptoms.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1238070&page=1
I'm using the GB files from there and i am doing PDA. i've left it for like 4 hours now So i'm just going to try installing VIA sd card.
Try the ed05 ROM found here.
http://forum.xda-developers.com/showthread.php?t=1124391
Also use the pit found there. This always gets me it when things go bad.
If that doesn't work you might be screwed.
Sent from my SCH-I500 using Tapatalk
Stephen.k.spear said:
Try the ed05 ROM found here.
http://forum.xda-developers.com/showthread.php?t=1124391
Also use the pit found there. This always gets me it when things go bad.
If that doesn't work you might be screwed.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
I am installing this now and for the past 15 mins it's been stuck at movinand.bin i'll let it sit there for an hour before I install via sd card, Keep in mind I'm not using the verizon fascinate I'm using the telus fascinate 3g+ which is the SGH-T959D
well now my phone boots up if i try to go to download mode it goes to the system recovery mode how ever if i let it try to start normally it boots up and just sits on a verizon wireless logo for ever
OMG it took about 10 minutes but it loaded!!!!!
vilhjalmr said:
OMG it took about 10 minutes but it loaded!!!!!
Click to expand...
Click to collapse
So you're good?
Sent from my SCH-I500 using Tapatalk

Phone is working fine, but Odin says "There is no PIT partition" when I try to flash.

Phone is working fine, but Odin says "There is no PIT partition" when I try to flash.
I have a GT-I9505 with the MDA version firmware, region EVR.
I've flashed it previously, successfully, to the latest ME2 firmware, but then I installed Chainfire3D which soft-bricked it.
I recovered using Kies firmware recovery, did a factory reset/cache wipe, have rooted the phone again... but now Odin won't flash the phone!
It says "There is no PIT partition", and when I try to re-partition using the PIT file from this thread, it just says "complete(write) operation failed".
I've tried Odin 1.8, 3.04, 3.07... all the same.
The phone is currently working fine and is rooted! I just want to flash to a newer firmware, is all.
Any thoughts?
Flash .pit file with the firmware, not alone make sure re-partition is ticked
Sent from my Galaxy using xda premium
samersh72 said:
Flash .pit file with the firmware, not alone make sure re-partition is ticked
Sent from my Galaxy using xda premium
Click to expand...
Click to collapse
I was doing both those things. Strangely, it worked when I used another computer! Thanks anyway.
I am having similar problems. Any other suggestions?
I'm trying to root my S4 for the first time. Just had the S4 factory reset itself before starting this attempt.
Seems like the USB connection keeps resetting. I don't have this problem on any other device and I've tried swapping USB cords as well as USB ports. Tried both USB 2.0 and 3.0 ports. I keep getting the same problems. I've even tried including the PIT file for re-partitioning. Even the Kies connection keeps resetting. Kies trouble shooting the USB connection resulting in reloading some drivers but that didn't have any effect.
ODIN output below:
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Removed!!
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Added!!
<ID:0/010> Removed!!
<ID:0/011> Added!!
<ID:0/011> Removed!!
<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Removed!!
<ID:0/011> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/011> Added!!
Now, searching lead me to a thread for I think the S3 and they were saying these kinds of problems were defective motherboards on the phone. Do I need to take my phone back to Verizon for warranty replacement? It's not even a week old yet.
0reo said:
I am having similar problems. Any other suggestions?
I'm trying to root my S4 for the first time. Just had the S4 factory reset itself before starting this attempt.
Seems like the USB connection keeps resetting. I don't have this problem on any other device and I've tried swapping USB cords as well as USB ports. Tried both USB 2.0 and 3.0 ports. I keep getting the same problems. I've even tried including the PIT file for re-partitioning. Even the Kies connection keeps resetting. Kies trouble shooting the USB connection resulting in reloading some drivers but that didn't have any effect.
ODIN output below:
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Removed!!
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Added!!
<ID:0/010> Removed!!
<ID:0/011> Added!!
<ID:0/011> Removed!!
<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Removed!!
<ID:0/011> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/011> Added!!
Now, searching lead me to a thread for I think the S3 and they were saying these kinds of problems were defective motherboards on the phone. Do I need to take my phone back to Verizon for warranty replacement? It's not even a week old yet.
Click to expand...
Click to collapse
uninstall driver then re-install it. make sure kies is not running. flash pit file with the firmware in odin
samersh72 said:
uninstall driver then re-install it. make sure kies is not running. flash pit file with the firmware in odin
Click to expand...
Click to collapse
For the record, I just convinced the local VZW store to swap me a NIB S4 as a warranty replacement. The new S4 is giving me the exact same problem so in all likelihood the phone is not my problem.
Going to try removing and reinstalling the drivers on the PC again.
Does USB debugging need to be checked / unchecked for ODIN to work?
0reo said:
For the record, I just convinced the local VZW store to swap me a NIB S4 as a warranty replacement. The new S4 is giving me the exact same problem so in all likelihood the phone is not my problem.
Going to try removing and reinstalling the drivers on the PC again.
Does USB debugging need to be checked / unchecked for ODIN to work?
Click to expand...
Click to collapse
NO NEED to check it. a lot of users brick their phones and can not boot to check usb debugging. so they went directly to odin flash and it was good to go :good:
0reo said:
For the record, I just convinced the local VZW store to swap me a NIB S4 as a warranty replacement. The new S4 is giving me the exact same problem so in all likelihood the phone is not my problem.
Going to try removing and reinstalling the drivers on the PC again.
Does USB debugging need to be checked / unchecked for ODIN to work?
Click to expand...
Click to collapse
Hi,
USB debugging needs to be ticked.
OK, I uninstalled and reinstalled the drivers and still get the same problems. Any other ideas?
0reo said:
OK, I uninstalled and reinstalled the drivers and still get the same problems. Any other ideas?
Click to expand...
Click to collapse
Hi,
Did you reboot your PC?
malybru said:
Hi,
Did you reboot your PC?
Click to expand...
Click to collapse
Yes, a number of times at every stage one would think it would make any difference. It didn't make any difference.
I did finally get my phone rooted. While I can't say for certain, it seems like the S4 needed to be booted normally, then connected via USB, then let Win7 auto install several drivers, then I initiated bhp090808's all-in-one root tool which rebooted the phone into ODIN mode. ODIN was then successful.
Contrast that with having the S4 disconnected from USB and manually booting into ODIN mode, then connect USB, then let Win7 install drivers, then initiate ODIN to start. That sequence gave me all the problems.
Thanks for the replies though. I do appreciate your willingness to help.
Solved same problem this way:
1) Connected phone by original cable directly to rear USB port
2) Turn off Kies (no need to uninstall)
3) Stopped 2 kies processes which still run even if kies is off.
4) There must be item "Samsung Android Phone" and cascaded item "Samsung android ADB interface" in device manager.
5) Enable USB Debugging in phone.
6) I had unchecked item "Check installed apps from ADB by USB" - Not sure if it is necessary.
7) When you connect phone there has to be popup with question: "Allow USB debugging from this computer?" followed by computer signature.
Check always, answer yes.
8) Use old Odin 3 V. 1.85
i9505+stock firmware+win7sp1
On pit partition found
samersh72 said:
I flashed cm 10.1 on my SAMSUNG Galaxy Ace Plus.Now I want to come back to my stock rom . I downloaded the stock rom and I am trying to flash it using ODIN.But I get the message that ON PIT PARTITION FOUND.
Click to expand...
Click to collapse
aa
---------- Post added at 08:53 AM ---------- Previous post was at 08:48 AM ----------
samersh72 said:
Flash .pit file with the firmware, not alone make sure re-partition is ticked
Sent from my Galaxy using xda premium
Click to expand...
Click to collapse
mpalka said:
Solved same problem this way:
1) Connected phone by original cable directly to rear USB port
2) Turn off Kies (no need to uninstall)
3) Stopped 2 kies processes which still run even if kies is off.
4) There must be item "Samsung Android Phone" and cascaded item "Samsung android ADB interface" in device manager.
5) Enable USB Debugging in phone.
6) I had unchecked item "Check installed apps from ADB by USB" - Not sure if it is necessary.
7) When you connect phone there has to be popup with question: "Allow USB debugging from this computer?" followed by computer signature.
Check always, answer yes.
8) Use old Odin 3 V. 1.85
i9505+stock firmware+win7sp1
Click to expand...
Click to collapse
]I flashed cm 10.1 on my SAMSUNG Galaxy Ace Plus.Now I want to come back to my stock rom . I downloaded the stock rom and I am trying to flash it using ODIN.But I get the message that ON PIT PARTITION FOUND
Sagar6699 said:
I flashed cm 10.1 on my SAMSUNG Galaxy Ace Plus.Now I want to come back to my stock rom . I downloaded the stock rom and I am trying to flash it using ODIN.But I get the message that ON PIT PARTITION FOUND
Click to expand...
Click to collapse
flash pit with the firmware http://forum.xda-developers.com/showthread.php?t=2065046
Re-Partition
samersh72 said:
flash pit with the firmware http://forum.xda-developers.com/showthread.php?t=2065046
Click to expand...
Click to collapse
Thanks!!
But now there is another problem........
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S7500DDLD1_S7500ODDLD2_S7500DDLD1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
<ID:0/009>
<ID:0/009> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
PLZ HELP!!!!!!!!
probably solve with this
Well I did thgis ... searched another firmware mewer same carrier .. and I rebooted the Pc ..Nothing
But on a forum external some dude sayd ok .. If you use front USB ports theese are coted as external USB and they don't are recognized as internal USB hubs so change to a back side usb and will work I did and now after waiting like 5 minutes the process started my phone is under process restarting now ... And Voloa .. the new firmware,
Thanks for that suggestion. Switching to the back USB ports worked for me.
pisicutumic said:
Well I did thgis ... searched another firmware mewer same carrier .. and I rebooted the Pc ..Nothing
But on a forum external some dude sayd ok .. If you use front USB ports theese are coted as external USB and they don't are recognized as internal USB hubs so change to a back side usb and will work I did and now after waiting like 5 minutes the process started my phone is under process restarting now ... And Voloa .. the new firmware,
Click to expand...
Click to collapse
Moritzio said:
Thanks for that suggestion. Switching to the back USB ports worked for me.
Click to expand...
Click to collapse
and me as well!
thanks alot! :laugh::laugh:
yanivnn said:
and me as well!
thanks alot! :laugh::laugh:
Click to expand...
Click to collapse
And me too!
Moritzio said:
Thanks for that suggestion. Switching to the back USB ports worked for me.
Click to expand...
Click to collapse
For me too, you are genious!

[Kernel is not Seandroid Enforcing] bootloop

I really messed up my phone :/
Hi, so about one month ago I decided to root my phone, but I did not know what I was doing since it was my first time and I was VERY confused. I ended up causing my phone to go into a bootloop, I'd first to even get it to work make it I'd make it go into download mode then restart from there. It'd just say in the top right corner "kernel is not seandroid enforcing" then afterwords it'd flicker the bottom buttons to just turn off completely. Any advice or help would be amazing , I won't mind spending time just to fix this so I'm all open
I recomend to flash the stock firmware on your phone.
Get the firmware file from fw.updato.com(fast but sometimes website is down)
Or
sammobile.com(slow but reliable)
Since you already sayd you tryed to root ur phone i suppose you know where to get odin3
Extract the firmware zip file y downloaded inside should be a .tar file put that in AP in odin and click start
Also i recomend a wipe but in theory it should* start working without.
Hope this helped you
Rainbow_Dash said:
I recomend to flash the stock firmware on your phone.
Get the firmware file from fw.updato.com(fast but sometimes website is down)
Or
sammobile.com(slow but reliable)
Since you already sayd you tryed to root ur phone i suppose you know where to get odin3
Extract the firmware zip file y downloaded inside should be a .tar file put that in AP in odin and click start
Also i recomend a wipe but in theory it should* start working without.
Hope this helped you
Click to expand...
Click to collapse
I've tried it before but I'll try it again, nothing really happens when I do it but mabey It'll work this time. I'll tell you whether it work or not
Nooooxa said:
I've tried it before but I'll try it again, nothing really happens when I do it but mabey It'll work this time. I'll tell you whether it work or not
Click to expand...
Click to collapse
Quick edit, my phone doesn't show up on the ID:COM area at all, I've tried other cables but it just won't work at all. I'm pretty sure it's from my phone itself and not the program
Nooooxa said:
Quick edit, my phone doesn't show up on the ID:COM area at all, I've tried other cables but it just won't work at all. I'm pretty sure it's from my phone itself and not the program
Click to expand...
Click to collapse
Oh no I forgot y need to have installed special drivers otherwise in some cases it won't show up. Get it from here în my experience first time it can take up to 1 hour for phone to be recognized. Also make sure ur phone is well enterd in download mode (volume down+home+volume up+power) a blueish screen appears and volume up again) there is no way it's bcuz of the phone. Also use the cable that came with the device and if it still doesn't work (for some reason) try in another pc (or mac)
Rainbow_Dash said:
Oh no I forgot y need to have installed special drivers otherwise in some cases it won't show up. Get it from here în my experience first time it can take up to 1 hour for phone to be recognized. Also make sure ur phone is well enterd in download mode (volume down+home+volume up+power) a blueish screen appears and volume up again) there is no way it's bcuz of the phone. Also use the cable that came with the device and if it still doesn't work (for some reason) try in another pc (or mac)
Click to expand...
Click to collapse
I got the driver installed and so far it's actually being able to connect ! but I have no luck at all, I put it in downloading mode, opened up oden then at a certain point my phone randomly went black then said "An error occurred while updating the device software. Use the Emergency recovery function in the smart switch PC software" Which I did end up doing but even while using that it will randomly shut off :/. Here's the oden log
"<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)"
Nooooxa said:
I got the driver installed and so far it's actually being able to connect ! but I have no luck at all, I put it in downloading mode, opened up oden then at a certain point my phone randomly went black then said "An error occurred while updating the device software. Use the Emergency recovery function in the smart switch PC software" Which I did end up doing but even while using that it will randomly shut off :/. Here's the oden log
"<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)"
Click to expand...
Click to collapse
Nevermind I found the issue! For some reason, my phone wasn't charged and my computer couldn't charge it enough. Dude, I can't thank you enough, I've been at this for a month now and never thought of going onto a forum. I was about to pay some guy $30 to fix it for me.
Nooooxa said:
I really messed up my phone :/
Hi, so about one month ago I decided to root my phone, but I did not know what I was doing since it was my first time and I was VERY confused. I ended up causing my phone to go into a bootloop, I'd first to even get it to work make it I'd make it go into download mode then restart from there. It'd just say in the top right corner "kernel is not seandroid enforcing" then afterwords it'd flicker the bottom buttons to just turn off completely. Any advice or help would be amazing , I won't mind spending time just to fix this so I'm all open
Click to expand...
Click to collapse
do you have flahed a custom rom?
or flash custom kernel? like audax kernel?

Categories

Resources