Database Users

"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

[Q] S4 Bootloop, Can enter download but not recovery

Hi,
I have been searching and searching. I tried to install a kernel to my phone, its been forever so i don't remember which one.
It just reboots every 5 seconds without any screens coming up. I can not get into recovery mode
I can get into download mode and have flashed stock I337UCUAMDB_ATTAMDB_I337UCUAMDB with odin, but it doesnt fix anything.
What can I do to get to stock recovery and fix my phone?

What happens if you put it on download mode and then cancel with vol down

It falls back into the bootloop of restarting every 5 seconds with no screens coming up. No entry into recovery.

And if you pull the battery and put it back in does it try to boot?

What firmware were you on and was it loki'd if you were on mdl?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

I have taken the battery out and replaced it. It does not automatically try to boot. After pressing power it goes into the same boot cycle. Also, thank you for your quick attention!

megatilter said:
I have taken the battery out and replaced it. It does not automatically try to boot. After pressing power it goes into the same boot cycle. Also, thank you for your quick attention!
Click to expand...
Click to collapse
When did it start doing what's it's going. Did you do anything before hand? Do you know what firmware you where on before you tried odin? Was it mdb?

"What firmware were you on and was it loki'd if you were on mdl?"
Previous to my obvious blunder with the kernel download, I was using goldeneye rom from android develepment, sucessfully.
Dont know if that answers the question but i have also tried to flash AMDL with odin but have the same results.

megatilter said:
"What firmware were you on and was it loki'd if you were on mdl?"
Previous to my obvious blunder with the kernel download, I was using goldeneye rom from android develepment, sucessfully.
Dont know if that answers the question but i have also tried to flash AMDL with odin but have the same results.
Click to expand...
Click to collapse
When you used odin did you only have f.reset and auto-reboot checked and flashed the md5 file in PDA

jd1639 said:
When you used odin did you only have f.reset and auto-reboot checked and flashed the md5 file in PDA
Click to expand...
Click to collapse
I have done it multiple times, perhaps panicking, I checked the re-partition button. I have tried to get a PIT file downloaded and tried to use that.
However, this behavior was happening before I did that. It started boot looping as soon as i tried to use TWRP to flash the kernel (I know i am an idiot, and didn't read first). As soon as this started happening, that's when I immediately tried to flash AMDL (exactly as you described with only those options checked) through odin and it didn't do anything different. That's when i tried other options. I fear i may have broken my phone. Again thank you for your attention.

megatilter said:
I have done it multiple times, perhaps panicking, I checked the re-partition button. I have tried to get a PIT file downloaded and tried to use that.
However, this behavior was happening before I did that. It started boot looping as soon as i tried to use TWRP to flash the kernel (I know i am an idiot, and didn't read first). As soon as this started happening, that's when I immediately tried to flash AMDL (exactly as you described with only those options checked) through odin and it didn't do anything different. That's when i tried other options. I fear i may have broken my phone. Again thank you for your attention.
Click to expand...
Click to collapse
I think you've broken it too. Sounds like you flashed the wrong kernel and at that point you were more or less hosed. Look into jtag, mobiletechvideos.com. They can probably fix it. It'll cost you $60.00 +
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

jd1639 said:
I think you've broken it too. Sounds like you flashed the wrong kernel and at that point you were more or less hosed. Look into jtag, mobiletechvideos.com. They can probably fix it. It'll cost you $60.00 +
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
i've never seen a kernel hard brick a device or corrupt the recovery partition. i also rarely see a user flash a file and not remember what they just flashed. he/she possibly flashed an incompatible kernel or flashed a non-loki'd kernel without flashing loki-doki. either way, recovery would still be accessible to correct this issue. i feel that there is more to this.
OP, see jd's jtag post above.

megatilter said:
I have done it multiple times, perhaps panicking, I checked the re-partition button. I have tried to get a PIT file downloaded and tried to use that.
However, this behavior was happening before I did that. It started boot looping as soon as i tried to use TWRP to flash the kernel (I know i am an idiot, and didn't read first). As soon as this started happening, that's when I immediately tried to flash AMDL (exactly as you described with only those options checked) through odin and it didn't do anything different. That's when i tried other options. I fear i may have broken my phone. Again thank you for your attention.
Click to expand...
Click to collapse
Well I finally was able to get Kies working and did a firmware update. That gave me back regular recovery. Now Im stuck at bootloop att screen.
I then re flashed AMDL stock via odin and VIOLA!
Im back to stock baby!
And from there ill probably go back to Goldeneyes Rom and never think about this ever again. Thanks for your time. My phone is working again!
Also
Thank you for helping me at least by giving this thread attention. So much appreciation to the fine people here at XDA

megatilter said:
Well I finally was able to get Kies working and did a firmware update. That gave me back regular recovery. Now Im stuck at bootloop att screen.
I then re flashed AMDL stock via odin and VIOLA!
Im back to stock baby!
And from there ill probably go back to Goldeneyes Rom and never think about this ever again. Thanks for your time. My phone is working again!
Also
Thank you for helping me at least by giving this thread attention. So much appreciation to the fine people here at XDA
Click to expand...
Click to collapse
Great news! You got lucky, make sure you read and learn on xda. And always know what you flash.

megatilter said:
Well I finally was able to get Kies working and did a firmware update. That gave me back regular recovery. Now Im stuck at bootloop att screen.
I then re flashed AMDL stock via odin and VIOLA!
Im back to stock baby!
And from there ill probably go back to Goldeneyes Rom and never think about this ever again. Thanks for your time. My phone is working again!
Also
Thank you for helping me at least by giving this thread attention. So much appreciation to the fine people here at XDA
Click to expand...
Click to collapse
Care to share how you got Kies working? I have a similar problem and I can't get Kies to recognize my phone.

Fix!
So What you gota do
1. Pull Out Battery Put back in
2.Go To Download Mode
3. Download The TWRP.tar For Your Phone
4.Run Odin as Admin, Tick Pda, for pda select the TWRP.tar
5. Hit Start, Then Pull Out battery put it back in
6.Get A Micro Sd And Put The Cyanogenmod Rom, and the gapps the ones for your phone
7.Insert microsd in phone
8. Boot Recovery and go to mounts and mount the microsd
9, Go Advansed, file manager, ext sd, And Copy the cyanogenmod and the gapps to internal storage
10. Flash the cyanogen mod and the gapps. DO THIS PART CAREFULLY OR MIGHT HARD BRICK!
11. Reboot And youl boot to cyanogenmod! OH yeah! Replay if this helped or if you have any problems

[Q] black screen when booting anything but CM10

I installed CWM and got cyanogenmod onto my phone without any hassle, eventually decided that a rooted stock rom for my sprint phone would be best for the time being.
my method was to pick up the rooted stock from from galaxyS4root (1.40 gb) and install it using CWM after doing a total wipe, the package also performed automatic wipes upon installing. no issues so I went ahead and rebooted, CWM alerted me saying that the package was not rooted and if I wanted to root, my answer was "yes."
the phone gets as far as the "galaxy S4" splash screen, then goes black and stays that way. The phone gets warm when doing this so I know its trying to do something. The only fix is to reboot into CWM and reinstall cyanogenmod.
Anyone else experience this? what can I do to fix it?

phisher177 said:
I installed CWM and got cyanogenmod onto my phone without any hassle, eventually decided that a rooted stock rom for my sprint phone would be best for the time being.
my method was to pick up the rooted stock from from galaxyS4root (1.40 gb) and install it using CWM after doing a total wipe, the package also performed automatic wipes upon installing. no issues so I went ahead and rebooted, CWM alerted me saying that the package was not rooted and if I wanted to root, my answer was "yes."
the phone gets as far as the "galaxy S4" splash screen, then goes black and stays that way. The phone gets warm when doing this so I know its trying to do something. The only fix is to reboot into CWM and reinstall cyanogenmod.
Anyone else experience this? what can I do to fix it?
Click to expand...
Click to collapse
i had this problem after first rooting as well. all i had to do was update the SU binaries and then root sticks. i would also do the wipes yourself just in case the package is missing something. and the obvious....check the MD5 and make sure its right and make sure your downloading the correct file for your phone.

xxaddictedxx said:
i had this problem after first rooting as well. all i had to do was update the SU binaries and then root sticks. i would also do the wipes yourself just in case the package is missing something. and the obvious....check the MD5 and make sure its right and make sure your downloading the correct file for your phone.
Click to expand...
Click to collapse
CM10's built in SU didn't seem to think the binaries needed updated, installed chainfire's SU and it wanted to update CWM.
it asked me about disabling recovery flash, to which i said yes. Its not the root im having an issue with though, its getting stuck at a black screen.
either way, update didn't work.

Ended up using odin to push the latest stock firmware on, then trying to root using the walkthroughs on here which resulted in the same outcome, black screen.
I was getting my deoxed and rooted rom from galaxyS4root.com, so I started checking the MD5, it never matched out of the 5 times I downloaded it. Watch out I guess.

phisher177 said:
Ended up using odin to push the latest stock firmware on, then trying to root using the walkthroughs on here which resulted in the same outcome, black screen.
I was getting my deoxed and rooted rom from galaxyS4root.com, so I started checking the MD5, it never matched out of the 5 times I downloaded it. Watch out I guess.
Click to expand...
Click to collapse
did you try one of the roms on xda? if MD5 dosent match then thats your problem

[Q] Help a noob, cannot boot after trying to flash stock rom

So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.

rmngorelov said:
So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.
Click to expand...
Click to collapse
Restore from nandroid backup. I hope you made one. Try going into recovery do a factory reset and wipe all cache and data and what not and then install a ROM from Odin.

rmngorelov said:
So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.
Click to expand...
Click to collapse
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware): https://mega.co.nz/#F!0JdRkIZR!AqqKdbvba_Hpg5VrCmrbPw

i7vSa7vi7y said:
Restore from nandroid backup. I hope you made one. Try going into recovery do a factory reset and wipe all cache and data and what not and then install a ROM from Odin.
Click to expand...
Click to collapse
I restored to this stock ROM before and everything worked well. Currently I can't boot into recovery, Samsung flashes once and that's it, that's why I'm desperate the only thing I can do is boot in to download mode for odin.

silentdeath631 said:
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware):
Click to expand...
Click to collapse
Does it matter that I can't get into recovery to clear the cache first before trying new roms?

silentdeath631 said:
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware):
Click to expand...
Click to collapse
Maybe I'm doing something foolish but every time I try to download files from the link you gave I get a decryption error so I can't download them zip or original.

rmngorelov said:
I restored to this stock ROM before and everything worked well. Currently I can't boot into recovery, Samsung flashes once and that's it, that's why I'm desperate the only thing I can do is boot in to download mode for odin.
Click to expand...
Click to collapse
Just hold home power and volume up. Right when you see text at the top left let go. You have to have the right timing

i7vSa7vi7y said:
Just hold home power and volume up. Right when you see text at the top left let go. You have to have the right timing
Click to expand...
Click to collapse
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.

rmngorelov said:
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.
Click to expand...
Click to collapse
Depends what recovery you had and what version. I personally like Philz touch recovery but TWRP is good. Now wipe and flash a ROM my friend or restore a backup

rmngorelov said:
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.
Click to expand...
Click to collapse
im having similar issues. which version of TWRP worked for you?
thank you

fearthemarchx said:
im having similar issues. which version of TWRP worked for you?
thank you
Click to expand...
Click to collapse
I recommend flashing the newest one here using odin
http://teamw.in/project/twrp2
Then once you are able to boot into recovery go to wipe and perform both factory reset and format data. Then install whatever rom you like, I used Sprint Galaxy S4 SPH-L720 VPUFNAE (Androdi 4.4.2) found here
http://galaxys4root.com/galaxy-s4-stock-firmware/ (or maybe find a newer stock rom if this one gives you errors)
Just copy the zip file to the phone, boot into twrp, do wipe factory reset again, select install then select the zip in whatever directory and you should be good to go. Make sure you do a back up in twrp once you get the phone to boot so you can always revert to stock.
I hope I was thorough enough that some of the information was useful. Let me know if you need any more help.

only certain recoveries will stick. ive tried the most recent twrp, with no luck. only a few versions of philztouch work.
Sent from my LGL34C using XDA Free mobile app

fearthemarchx said:
only certain recoveries will stick. ive tried the most recent twrp, with no luck. only a few versions of philztouch work.
Sent from my LGL34C using XDA Free mobile app
Click to expand...
Click to collapse
Format with philztouch that works then try flashing a new stock rom with odin. That should bring everything back to stock including the recovery.

ive tried. when i flash rom via odin i only get a blue "recovery booting" at the top of boot screen. even when i only power on, not into recovery. im going to attempt to flash rom provided in previous post via philz.
Sent from my LGL34C using XDA Free mobile app

fearthemarchx said:
ive tried. when i flash rom via odin i only get a blue "recovery booting" at the top of boot screen. even when i only power on, not into recovery. im going to attempt to flash rom provided in previous post via philz.
Sent from my LGL34C using XDA Free mobile app
Click to expand...
Click to collapse
You're in download mode when you flash from odin right? If you your getting an error flashing, try a different stock rom after reformating/resetting to factory (it's crucial to clear the cache before trying a different rom). I had to try a few roms before I found one that worked.

N910C stuck in frustrating bootloop

Hey wassup. So yesterday I rooted my phone and tried to install CM13 on it. Took a few tries since the rom I got was corrupted but I got it to work. Then I noticed it was guzzling the battery like lemonade (this EXACT same thing happened on my previous S4 too) so I gave up on it and decided to revert back to the stock rom. Everything went well... NOT. I downloaded the stock firmware (3gigs... zzz) and I flashed it with Odin and the phone restarted. The little android robot from the default unrooted recovery popped up and it had below it this: "Installing system update..." and then out of the blue it said "Erasing" and it's gear started rotating backwards. THEN, when it finished the normal Samsung Galaxy Note 4 logo popped up, went away and then CAME BACK AGAIN FOR LIKE 500 TIMES AND COUNTING. AOSP roms work just fine, it's just that touchwiz ones won't work whatsoever (even tried sixperience, no luck)... What should I do? I already lost my S4 due to this...

install TWRP custom recovery, boot up in recovery format system dalvik cache and internal storage then try flashing stock with odin hopefully it will work.

Try to remove battery first.from tsoch recovery wipe data cache and see if it works

dork997 said:
install TWRP custom recovery, boot up in recovery format system dalvik cache and internal storage then try flashing stock with odin hopefully it will work.
Click to expand...
Click to collapse
Been there, done that. Nope, still refuses to work :/

bumpity bump bump

Did you backup your efs partition before you flashed cm13? If not you corrupted your efs and your phone is a wifi tablet now because you cant use your modem.

travis82 said:
Did you backup your efs partition before you flashed cm13? If not you corrupted your efs and your phone is a wifi tablet now because you cant use your modem.
Click to expand...
Click to collapse
this never happened to me with my old s2 or s4
why is it happening now ?

Didn't backup. Now it just won't even work with odin. Whenever I try to just flash anything with it goes off and says 0 successes and 0 fails. What I did notice though was that whenever I installed a stock rom it starts this "Installing system update" with the android robot twingling it's antennaes and then out of nowhere it's blue bar goes away and it says "Erasing" then... bootloop. Now odin won't even work (explained above). Should I just give up and send it in for repairing? Or can ANYONE send me the twrp restore file, please...

Peontikos_Desmos said:
Didn't backup. Now it just won't even work with odin. Whenever I try to just flash anything with it goes off and says 0 successes and 0 fails. What I did notice though was that whenever I installed a stock rom it starts this "Installing system update" with the android robot twingling it's antennaes and then out of nowhere it's blue bar goes away and it says "Erasing" then... bootloop. Now odin won't even work (explained above). Should I just give up and send it in for repairing? Or can ANYONE send me the twrp restore file, please...
Click to expand...
Click to collapse
Hi
Same problem
Any ideas !!!

Hey,
I have the same problem it turns out after flashing, i cant remember, maybe dytto note 4 rom, it got stuck in continous bootloops and the only way it is working for me is when its charging. I know it sounds crazy but its the only way for me, ive tried installing stock different countries firmware and bunch of custom rom with no luck. I sent it to the place where i bought the phone and made myself look dumb asking why it is like that and i told them i had not do anything. After only a week they phoned me and said it was rooted (i did get the root out when i gave it but they somehow knew it was... later i understood that it is all about that stupid Know thing) and refused to cover my warranty. They said that the only way i can get it to work is to pay 300$ for new chip :,(

senon said:
Hey,
I have the same problem it turns out after flashing, i cant remember, maybe dytto note 4 rom, it got stuck in continous bootloops and the only way it is working for me is when its charging. I know it sounds crazy but its the only way for me, ive tried installing stock different countries firmware and bunch of custom rom with no luck. I sent it to the place where i bought the phone and made myself look dumb asking why it is like that and i told them i had not do anything. After only a week they phoned me and said it was rooted (i did get the root out when i gave it but they somehow knew it was... later i understood that it is all about that stupid Know thing) and refused to cover my warranty. They said that the only way i can get it to work is to pay 300$ for new chip :,(
Click to expand...
Click to collapse
ffs i'm not paying another phone's worth in a ****ing motherboard. I tried:
-Flashing the stock bootloader, fails at sboot.img:NAND Write start fail
-Flashing the PIT file, just... wont flash. Successes 0/Fails 0
-Flashing the stock AP file, bootloop
-Flashing the CP and the CSC stock files, serial(com) port cannot be opened.
****ing garbage. For some reason my phone's the only exception to the rule that phones able to boot into download mode are salvageable. It's going in for a repair and if it's more than $50 I'm not rooting again even at gunpoint.

Quick update:
I found a toolkit that has a flash stock boot image option. Had to recover to my cm13 backup to enable usb debugging. Will post results

Nothing of course...

try this step by step,
1. Download stock firmware THE LATEST ONE (n910c v5.1.1) from sammobile.com
2. Download newest Odin and Samsung USB; installed Samsung USB
3. I am assuming you have installed twrp recovery. Boot to twrp recovery and do a full wipe; wipe all!
4. Boot to downloading mode and install stock via odin. That is it.
Ps.... in case of failure, make sure you have installed Samsung USB! Or just reconnect usb cable with other usb ports untill it is working.

Never flach cm if doesn'T HAVE a efs backup if not you will stuck with cm

Oliva.raiders said:
1. Download stock firmware THE LATEST ONE (n910c v5.1.1) from sammobile.com
2. Download newest Odin and Samsung USB; installed Samsung USB
3. I am assuming you have installed twrp recovery. Boot to twrp recovery and do a full wipe; wipe all!
4. Boot to downloading mode and install stock via odin. That is it.
Ps.... in case of failure, make sure you have installed Samsung USB! Or just reconnect usb cable with other usb ports untill it is working.
Click to expand...
Click to collapse
Well, crap I already sent it in for repairing but if the fuqing robbers decide to change the motherboard instead of doing anything to it and charge me 500$ to do so I'm getting it back and I'm trying this one. Already did but it wouldn't hurt retrying... BTW FOR THE LOVE OF GOD DOES SOMEONE HAVE A TWRP BACKUP FILE ON STOCK TOUCHWIZ? JESUS

radium56ad said:
Never flach cm if doesn'T HAVE a efs backup if not you will stuck with cm
Click to expand...
Click to collapse
Is there absolutely NO workaround?

i had the same issue, this is how i solved this (you won't like it):
-deleted efs partition
-restored 5.1.1 coj5 via odin
-then took it to a samsung repair center to restore the imei
paid them like 50 bucks...that sucks. after this im backing up efs folder before flashing a rom.

radium56ad said:
Never flach cm if doesn'T HAVE a efs backup if not you will stuck with cm
Click to expand...
Click to collapse
JuanWilliman said:
i had the same issue, this is how i solved this (you won't like it):
-deleted efs partition
-restored 5.1.1 coj5 via odin
-then took it to a samsung repair center to restore the imei
paid them like 50 bucks...that sucks. after this im backing up efs folder before flashing a rom.
Click to expand...
Click to collapse
Oh that's nothing man. The fuqing scammers told me the whole freaking board had to be replaced...

There's one thing I've noticed though that's PROBABLY gotta be the culprit. Whenever I install a touchwiz rom, the phone boots up fine for once, shows the robot with the "Installing system update" and then it goes off with "Erasing" followed by the bootloop. Could anyone please elaborate on this? I have a feeling this is what's causing this ****fest