Database Users

[Q] Issue flashing to stock

I am flashing my epic back to stock and I am having some issues. I am using Odin3 v1.61 and Odin3 v1.3. They both seem to freeze almost half way through, it stops at factoryfs.rfs. Does anyone have any ideas? I am using SPH-D700-DI18-8Gb-REL.tar in my phone spot and s1_odin_20100512 in my pit spot.

I got it.. I am just dumb. I didn't put the .tar file in the pda spot. Not sure what I was thinking.

"E:/ Can't mount dev/block/stl10"

I am getting the following message:
"E:/ Can't mount dev/block/stl10"
...while in CWM Recovery i'm trying to do a restore and i'm getting this message.
This is all after doing the ##786# and resetting RTN data to fix GPS. My GPS works great, but i'm trying to restore my ROM/data back and getting this error. I'm worried my partitions might be hosed. Anyone have any ideas?
Google searching leads me to a lot of i9000 threads, most people saying "you're screwed, time to get a replacement" or referencing an i9000 specific flash to attempt to fix. I've seen some saying Odin will not fix this problem.
Does anyone know what exactly happend or caused this error and is there a way to recover?

gmorf33 said:
I am getting the following message:
"E:/ Can't mount dev/block/stl10"
...while in CWM Recovery i'm trying to do a restore and i'm getting this message.
This is all after doing the ##786# and resetting RTN data to fix GPS. My GPS works great, but i'm trying to restore my ROM/data back and getting this error. I'm worried my partitions might be hosed. Anyone have any ideas?
Google searching leads me to a lot of i9000 threads, most people saying "you're screwed, time to get a replacement" or referencing an i9000 specific flash to attempt to fix. I've seen some saying Odin will not fix this problem.
Does anyone know what exactly happend or caused this error and is there a way to recover?
Click to expand...
Click to collapse
Which versions of CWM do you have installed, and which version are you using to try and restore?

When i boot up into CWM its 2.5.1.0. I can "reboot recovery" to boot up into 3.0.0.5. I am using latest version of Bonsai, which puts everything onto EXT4.
After you asked that.. i had a "dur lightbulb" moment and tried doing the restore from CWM3, and it seems to be working as we speak... hopefully that gets me back up and running.

gmorf33 said:
When i boot up into CWM its 2.5.1.0. I can "reboot recovery" to boot up into 3.0.0.5. I am using latest version of Bonsai, which puts everything onto EXT4.
After you asked that.. i had a "dur lightbulb" moment and tried doing the restore from CWM3, and it seems to be working as we speak... hopefully that gets me back up and running.
Click to expand...
Click to collapse
Hmm.. maybe not... stuck @ Samsung boot screen for about 5 minutes now. *ponders a battery pull*
Edit: Kept hanging at boot screen, so tryign to reflash Bonsai over the top to see if i can get past boot screen. Hopefully the scripted bonsai install will carry over the restored data and i'll be back to where i was..

gmorf33 said:
Hmm.. maybe not... stuck @ Samsung boot screen for about 5 minutes now. *ponders a battery pull*
Click to expand...
Click to collapse
I recommend reflashing the latest version Bonsai. Just Make sure you are in CWM 3 when you do it.

mattallica76 said:
I recommend reflashing the latest version Bonsai. Just Make sure you are in CWM 3 when you do it.
Click to expand...
Click to collapse
Yeah tried... but when i tried to reboot recovery back into 3, it hung up at Samsung boot screen. Figuring "what the hell" i just tried flashing Bonsai from 2.5.1.0, which appeared to completely successfully, but still hanging up @ sammy boot screen.
Factory resetting isn't getting me anywhere either now. Looks like Odin is in my near future. Hopefully that works.

Yep! Odin and then redo your 3.0.0.5 cwm and then bonsai. Not very complicated. I've had to do this several times especially when we had the first method for ext4. Cwm 2.5.1.2...
Sent from my SPH-D700 using XDA App

I can't believe there's. Thread about this. Odin and try again. If it doesn't work, use odin and try again. Maybe do that one more time, then start a thread.
Sent from my SPH-D700 using XDA App

austin420 said:
I can't believe there's. Thread about this. Odin and try again. If it doesn't work, use odin and try again. Maybe do that one more time, then start a thread.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Not sure what your getting at. The OP already knew he could use Odin to fix it. He was looking for a way to fix it without Odin, which I don't blame him for.

austin420 said:
I can't believe there's. Thread about this. Odin and try again. If it doesn't work, use odin and try again. Maybe do that one more time, then start a thread.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I'm mostly wondering what caused this as I would like to try to avoid the mistake in the future. And yes, I was trying to fix this without having to resort to Odin. After trying several other things, I believe that's my last option (which may or may not work from other posts i've found on google). Hearing that Odin won't always work to fix this error is the main reason I created this post. To find out what exactly might cause it and why Odin wouldn't fix it. Yes, I can just skip straight to Odin, but then I wouldn't have learned anything if it worked.
I'm guessing something with the /data partition got hosed?
Has anyone else doing the GPS fix from "General" with the ##786# method experienced what i have, after Advanced Restoring data back in?

He could always try reformating.
There are flashable zips out there to format back to rfs (well fat32) or to format to ext4.
Or he could adb in while in clockworkmod and do it manually. However, if he isn't able to pull open those zips and figure out what commands he needs to format on his own, then he probably doesn't have the technical knowledge necessary to safely do it that way.

Hmm.. no bueno. Cannot get either PC i have access to here at work (both win7) to recognize the USB device. I can boot into download mode on the phone at least... so there's still some hope.
I tried uninstalling drivers, redownloading from samsung, and installing. Used different cable and PC as well.. keep getting a code 10 error when trying to load the device driver when i plug it in. I'll have to try it on my WinXP box when i get home.. i think that's my last option unless anyone can think of something else.

gmorf33 said:
Hmm.. no bueno. Cannot get either PC i have access to here at work (both win7) to recognize the USB device. I can boot into download mode on the phone at least... so there's still some hope.
I tried uninstalling drivers, redownloading from samsung, and installing. Used different cable and PC as well.. keep getting a code 10 error when trying to load the device driver when i plug it in. I'll have to try it on my WinXP box when i get home.. i think that's my last option unless anyone can think of something else.
Click to expand...
Click to collapse
I don't think you will be able to load drivers while your phone is in it's current state. You will need to use a pc that already has them installed.

mattallica76 said:
I don't think you will be able to load drivers while your phone is in it's current state. You will need to use a pc that already has them installed.
Click to expand...
Click to collapse
Loading drivers on his pc has nothing to do with the state of his phone.

DiGi760 said:
Loading drivers on his pc has nothing to do with the state of his phone.
Click to expand...
Click to collapse
Even after loading the drivers onto a pc, you have to plug the phone into a usb port and let it find it in Android mode and download mode. He has already done this on his home pc and that is why it works there and not on the other computers he has tried. I and many others have encountered this same issue.

Yeah, PC at home recognized it without a hitch. If only the Odin process went as smoothly
On my 3rd attempt right now.. here's where it hangs up everytime so far:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> param.lfs
<ID:0/005> Sbl.bin
<ID:0/005> boot.bin
<ID:0/005> recovery.bin
<ID:0/005> zImage
<ID:0/005> factoryfs.rfs
<ID:0/005> datafs.rfs
<ID:0/005> cache.rfs
<ID:0/005> modem.bin
This time my screen is a blank green. Before it was just stuck at full progress bar on both the download mode on phone, and in odin.
Not sure if i should try the last method Noobnl has in the wiki (putting tar in phone section, resetting after it hangs, then doing it again with the tar in pda). Mine isn't failing where he mentions in that blip though... Actually mine isn't getting any failure messages. It just sits there looking like its 100% done.
Auto Reboot and F. Reset Time are both checked (nothing else is).
After this current attempt I'm going to try and Odin the DI18, if that fails, hopefully it gets it as close to stock as possible and see if sprint will replace it. *shrug*
Edit: Ah, decided to try -one- more time with DK28. It was hung at the green screen of doom again, but i pulled the plug, reset odin, pulled battery, and then rebooted phone. This time it actually booted up. Looks like stock DK28, and radio and GPS is working. Yay. I'm still a little concerned though why it didn't cleanly finish. There should still be these steps in the log:
<ID:0/005> cache.rfs
<ID:0/005> Removed!!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
None of which are there.. I'm wondering if the issues w/ the /data and the cache are still present, since it seems cache.rfs is the step it couldn't finish. Would running any fsck or tune2fs commands help in trouble shooting these partitions? I'd like to resolve any core underlying issues before going through the trouble of reinstalling Bonsai and reloading all my apps, etc.
I think one step i should do regardless, is to backup my sdcard and reformat it (is the best way to do this through CWM?)

I'm having a similar problem mounting anything to A:\. can you guys tell me how I can load this 1.44mb of data?
Sent from my SPH-D700 using XDA App

Nope, I've done it before, the computer will read the phone in download mode just fine.
Also, just be sure to try all the usb ports on your computer, my epic only works on one side of my laptop...
Sent from my SPH-D700 using XDA App

Okay so I'm kinda stuck on JM8...

I was initially on CM7. Then decided to use a ROM i cooked using Doc's Kitchen. Then it went into the crazy vibrating loop and I've tried many fixes and finally got my phone to boot on JM8.
Then I tried flashing stock JPY with 512 pit and it goes back to the vibrating loop.
I'm on JM8 again.
It's almost 4am over here and I need some sleep so can anyone tell me what to do next? My goal is to actually install the ROM i cooked up.

okay got it working now...
no pit and uncheck re-partition
nothing to see here now !

ODIN DL09 --> reboots to recovery

Not really sure why it keeps doing this but after an ODIN to DL09 with re-partition, my phone just boots to stock recovery no matter what I do...cannot get Android to boot...A CM7 install went bad earlier during the install and since the reinstall has a reboot in it, it was stuck in a bootloop trying to install it...Anyway why isn't ODIN taking care of all of this? Do I need to ADB and clear something? Thanks for any help guys

dmasjz45 said:
Not really sure why it keeps doing this but after an ODIN to DL09 with re-partition, my phone just boots to stock recovery no matter what I do...cannot get Android to boot...A CM7 install went bad earlier during the install and since the reinstall has a reboot in it, it was stuck in a bootloop trying to install it...Anyway why isn't ODIN taking care of all of this? Do I need to ADB and clear something? Thanks for any help guys
Click to expand...
Click to collapse
I never used a pit when odining DL09 and it worked fine for me, maybe try it without it...
blazing through on my VZ Droid Charge

dmasjz45 said:
Not really sure why it keeps doing this but after an ODIN to DL09 with re-partition, my phone just boots to stock recovery no matter what I do...cannot get Android to boot...A CM7 install went bad earlier during the install and since the reinstall has a reboot in it, it was stuck in a bootloop trying to install it...Anyway why isn't ODIN taking care of all of this? Do I need to ADB and clear something? Thanks for any help guys
Click to expand...
Click to collapse
I had this happen to me the other day, you likely downloaded the wrong DL09 odin files. This is the DL09 you want (I bet it's several dozen megs larger than the one you have, if you did the same thing as me).
Flash that with the re-partition PIT and then you should be good.

Not sure what the issue was, but heimdall fixed it, thanks, will go back and odin DL09 now

KitsuneKnight said:
I had this happen to me the other day, you likely downloaded the wrong DL09 odin files. This is the DL09 you want (I bet it's several dozen megs larger than the one you have, if you did the same thing as me).
Flash that with the re-partition PIT and then you should be good.
Click to expand...
Click to collapse
Yes you're right, the DL09.tar.md5 I had is about 308 megs.......Weird....Thanks!!!!

Stuck on boot after installing custom roms

hello to everyone.
to make it quick and simple, I have an ATT Samsung s4 i337, i had CleanRom 1.0 installed via twrp 2.5.0.2 since scott released it. but its been a while so i tried installing a different more updated rom today, and i went with SHOsock... i factory reset my phone, installed it, it booted just fine. then i tried to reboot my phone and it got stuck on the samsung boot logo. tried to reflash it wiping dalvic and factory reseting,worked again, but every time i reset it, it stays stuck. i tried flasing Aplha Infamous s4 rom, same thing. tried flashing a custom rom and ktoonsez kernel nothing.
tried to recover from my nandroid back up and nothing happens.
then i read that it might be twrp. so i insalled OUDHS CWM tried flashing. samething.
so im basically stuck.
PLEASE if anyone has any idea or solution i'd appreciate it.
update!
i have found the only possible solution that i may know of as today. the only thing you can do if your phone is stuck on boot after trying to flash different roms, is to flash the stock ATT UCUAMDB or UCUAMDL firmware via ODIN.
you will lose your custom recovery but at least you can use your phone again.

If you've got everything backed up, perhaps use oudhs or even cwm and completely wipe everything. System, data and all. Then reflash your loki'd ROM, kernel, etc. See if that gets you straightened out.

So if you do a clean flash, it's boots fine the first time. But if you reboot it hangs at the logo? And a nandroid won't restore properly. I think you might have some hardware memory issues. But let's see if anyone else has any ideas.

xBeerdroiDx said:
If you've got everything backed up, perhaps use oudhs or even cwm and completely wipe everything. System, data and all. Then reflash your loki'd ROM, kernel, etc. See if that gets you straightened out.
Click to expand...
Click to collapse
i try wiping data through recovery but it gives me an error. system/data not available(found)

I guess you can give formatting everything a shot. Did you unmount anything by accident?
Sent from my GT-S7560M using xda app-developers app

xBeerdroiDx said:
If you've got everything backed up, perhaps use oudhs or even cwm and completely wipe everything. System, data and all. Then reflash your loki'd ROM, kernel, etc. See if that gets you straightened out.
Click to expand...
Click to collapse
OP the post I quoted will more than likely fix your issue. Please try it and let us know!

agent929 said:
OP the post I quoted will more than likely fix your issue. Please try it and let us know!
Click to expand...
Click to collapse
i have tried that with custom roms loki-ed already, loki-ing after, flashing kernels, everything.
the only solution i was able to find is to download the stock ATT UCUAMDB firmware, and using ODIN to flash it. after that it boots fine. i did lose everything though, my custom recovery and root. at least its not looping on boot...gonna flash MDL now.

rickymh19 said:
i have tried that with custom roms loki-ed already, loki-ing after, flashing kernels, everything.
the only solution i was able to find is to download the stock ATT UCUAMDB firmware, and using ODIN to flash it. after that it boots fine. i did lose everything though, my custom recovery and root. at least its not looping on boot...gonna flash MDL now.
Click to expand...
Click to collapse
You do know if you don't hurry and flash a custom rom since you went back to Factory AT&T and is not rooted your phone is gonna upgrade on it's own to MF3 and if that happens you won't be able to flash custom Roms just thought i let you know!

I've got almost this same exact problem, but for me it only boot loops every now and then. When it does boot loop, sometimes, battery pulls will work, but most of the time, I have to go into TWRP and do a factory Reset to even get it to boot.
I am running CM10.2-20130908-Nightly-jflteatt with cronic kernel installed. It has been doing this since I got the phone and rooted it a few days ago (Thankfully, the phone came loaded with MDL instead of MF3 from what I have been reading).
Since mine only does it randomly, would you recommend to install something else and try to see what happens? Or go the route of doing a ODIN flash with no SimCard and WiFi access to keep the phone from updating? Or just leave it like it is?
P.S. None of this stuff is new to me, I flashed so much stuff on my SGS3 that I got a hang of it, but can't find the issue for these boot loops. I thought it had something to do with Google Apps because it would boot all day, everyday fine without Google Apps installed (tried it all day today). I would randomly restart it to see what it did, and it booted fine, no problems.

firepong said:
I've got almost this same exact problem, but for me it only boot loops every now and then. When it does boot loop, sometimes, battery pulls will work, but most of the time, I have to go into TWRP and do a factory Reset to even get it to boot.
I am running CM10.2-20130908-Nightly-jflteatt with cronic kernel installed. It has been doing this since I got the phone and rooted it a few days ago (Thankfully, the phone came loaded with MDL instead of MF3 from what I have been reading).
Since mine only does it randomly, would you recommend to install something else and try to see what happens? Or go the route of doing a ODIN flash with no SimCard and WiFi access to keep the phone from updating? Or just leave it like it is?
P.S. None of this stuff is new to me, I flashed so much stuff on my SGS3 that I got a hang of it, but can't find the issue for these boot loops. I thought it had something to do with Google Apps because it would boot all day, everyday fine without Google Apps installed (tried it all day today). I would randomly restart it to see what it did, and it booted fine, no problems.
Click to expand...
Click to collapse
I'd try a different rom. It sounds like it boot loops on reboot? And not random reboots?

jd1639 said:
I'd try a different rom. It sounds like it boot loops on reboot? And not random reboots?
Click to expand...
Click to collapse
Yeah, its not random reboots. Have yet to have that problem yet. It just gets stuck at the Samsung logo when I need to restart the phone every now and then for whatever reason. After it gets past the Samsung logo, I have yet to have it get locked on the custom Rom boot screen.

firepong said:
Yeah, its not random reboots. Have yet to have that problem yet. It just gets stuck at the Samsung logo when I need to restart the phone every now and then for whatever reason. After it gets past the Samsung logo, I have yet to have it get locked on the custom Rom boot screen.
Click to expand...
Click to collapse
Ok, here's something new after installing a new Rom (This is doing a complete Install. Cleared System, Data and Wiped all Cache). On boot now, it still get stuck every now and then on the Galaxy S4 screen, but when I pull the Battery and re-insert it, it somehow resets my phone back to Default for that Rom. For example, on Slim Bean, with Gapps installed, it will make me go through the whole process of setting of Gmail again as well as make me redownload all my apps again. It's like the stuff isn't sticking after reboots.
Has this ever happened to anyone?
EDIT* Like I said, if nothing is suggested, after the stock ODIN files are downloaded and I try a few more things out, I'll just do a stock flash and redo my Root then see what happens with a Custom Rom then.

This is a kernel issue period, you need to find a loki kernel and flash that....and if that one doesn't work try another...

rickymh19 said:
i try wiping data through recovery but it gives me an error. system/data not available(found)
Click to expand...
Click to collapse
I just had this problem last night. Then went to restore ROM and it failed when trying to restore data. I was in the process of testing new ROMs. I have had problems previously even flashing Odin MDL with stock s4 cable. Also have the random boot loop issue. Could it be a hardware memory issue?

rickymh19 said:
hello to everyone.
to make it quick and simple, I have an ATT Samsung s4 i337, i had CleanRom 1.0 installed via twrp 2.5.0.2 since scott released it. but its been a while so i tried installing a different more updated rom today, and i went with SHOsock... i factory reset my phone, installed it, it booted just fine. then i tried to reboot my phone and it got stuck on the samsung boot logo. tried to reflash it wiping dalvic and factory reseting,worked again, but every time i reset it, it stays stuck. i tried flasing Aplha Infamous s4 rom, same thing. tried flashing a custom rom and ktoonsez kernel nothing.
tried to recover from my nandroid back up and nothing happens.
then i read that it might be twrp. so i insalled OUDHS CWM tried flashing. samething.
so im basically stuck.
PLEASE if anyone has any idea or solution i'd appreciate it.
update!
i have found the only possible solution that i may know of as today. the only thing you can do if your phone is stuck on boot after trying to flash different roms, is to flash the stock ATT UCUAMDB or UCUAMDL firmware via ODIN.
you will lose your custom recovery but at least you can use your phone again.
Click to expand...
Click to collapse
Hey!, I saw this post when searching for answers to the same issue I have right now. I have tried to flash I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar but Odin is getting a Failed results. I tried flashing back again to NB1 rootable rom from other threads here, then Tried flashing back to stock rom AMDB, still no luck. Could you tell me how did you managed to go back to AMDB?.. Thanks so much..

jobpvill said:
Hey!, I saw this post when searching for answers to the same issue I have right now. I have tried to flash I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar but Odin is getting a Failed results. I tried flashing back again to NB1 rootable rom from other threads here, then Tried flashing back to stock rom AMDB, still no luck. Could you tell me how did you managed to go back to AMDB?.. Thanks so much..
Click to expand...
Click to collapse
What is the error in Odin? What bootloader is currently on the phone?

audit13 said:
What is the error in Odin? What bootloader is currently on the phone?
Click to expand...
Click to collapse
thanks so much for responding.. I really dunno what to do with this phone.. Ever since I patched custom rom it started to hanged after restarting. The initial start is fine, but after I restart the phone It only reached the welcome screen. The only way I can get in is to do a factory reset. zzz
Bootloader: I337UCUFNB1 (that's what I saw using CPU Z)
Below is the error just now again.. ( I tried to flash it again.. )
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Odin will not flash the rom because the rom being flashed has an older bootloader than the rom on the phone. This is evidenced by the fact that Odin stops after trying to flash aboot.mbn.

audit13 said:
Odin will not flash the rom because the rom being flashed has an older bootloader than the rom on the phone. This is evidenced by the fact that Odin stops after trying to flash aboot.mbn.
Click to expand...
Click to collapse
Anything else I can do to put this At&T s4 back to that stock rom?.. so that I can use it again?. Please help :'(

This may help : http://forum.xda-developers.com/showthread.php?t=2616221