Database Develop

Sprint SGT - E:Can't mount /dev/block/mmcblk0p1

Hi there Galaxy Tab community!
I'm having trouble fixing a Sprint Galaxy Tab (SPH-P100, CDMA).
I have tried a lot of different solutions and none of them are working for me.
Maybe someone can point out what the issue with my SGT is.
Current status: will get stuck at the "glowing" Samsung Logo (have let it sit for 15-20 minutes after reflashes but still stays there)
I don't really know how to explain this issue so I'm hoping one of you kind members can explain this to me. In Android system recovery <3e> mode before I did any flashing I get this error notice:
# MANUAL MODE #
E:Can't mount /dev/block/mmcblk0p1
(no such file or directory)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p1
(no such file or directory)
Is E: the SD card?
I do not have an SD card put in. And when I do, the above error message still appears. There is no SD card mounting error notice. And attempting to do an SD card update.zip does attempt successfully.
Now after trying to ODIN flash back to stock firmware (EA24, DJ30, stock with no modem) they all flash successfully, but all of them still get stuck at glowing samsung logo. And I still get the above mounting error message in recovery.
I did not tick "re-partition" yet, would this make a difference? (I tried searching for what it does but couldn't find any explanation)
Would flashing with Heimdall be any different than ODIN?
And the other solution I read was to reformat the internal SD to rfs format using roto JME (but I think that's only for GSM support?)
ANy help/suggestions would be appreciated!
UPDATE!!!: FIXED!!
Followed this step by step carefully and exactly from step 1 - 7: posted by emieczko (THANK YOU!!!!)
http://forum.xda-developers.com/showpost.php?p=13113921&postcount=21
so now I have to figure out if I still get the above error about E:.. but im scared if its really fixed for good. I will keep this updated! I love this forum!
UPDATE 2: shoot.. spoke too soon haha, tried to do a reflash of EA24 through heimdall and now in original situation. Only attempted another flash because each time i shutdown and restarted it would get stuck, until i would go into recovery and do a factory wipe/ clear cache, which would allow it to then boot to android.
UPDATE3: humm interesting, the OP http://forum.xda-developers.com/showpost.php?p=11650984&postcount=1 actually worked and booted right after a successful flash of the no_modem stock firmware using ODIN and the pit file supplied. and the crazy part is, it still had my gmail account info saved even after i had 'factory reset' a few times when it wouldnt boot up correctly.
UPDATE 4: Okay managed to update from stock no modem (tab_sprint_noModem_20101226) using odin 1.3, then ODIN the EA24 (Sprint Galaxy Tab EA24 Flasher) successfully with first boot attempt! Then since this was more of an official flash, EB25 was downloaded and installed with first boot success! Then the next update before Gingerbread, and then gingerbread OTA was installed successfully with first boot success!!! So now under gingerbread rom everything seems to be working smoothly. no problems with the market, wifi issues seem to be fixed.. only last real thing to make it an officially fixed tab is rebooting and seeing if it boots okay and booting into recovery and seeing if the E: errors still occur.. both which I don't want to face atm haha.\
UPDATE 5: So I was able to successfully reboot 3 times in a row. The method I used was the tablet plugged in with charger the entire time. I noticed upon removal of charger, apps would force close within minutes if i attempt to open even more apps system reboot and hang would occur. The only solution to get it up and working again is to plug the charger back in, then factory reset/ wipe cache and reboot. (FYI: first boot after a factory reset, the tab should vibrate on the 3rd-8th "glow" cycle of the samsung logo. if you see the logo loop.. then yea its boot loop haha). Attemping to boot the tab up without charger plugged in, causes a boot logo hang.. I'm starting to suspect defective tablet :-\
UPDATE 6: Looks like this tablet functions 100% normal when plugged in via USB to PC or Charger. Booting into recovery does not show any failed mounts (reboot into recovery 3 tmies) UNTIL i unplug it and try to reboot into recovery again. ACCIDENTALLY flashed the DK28 (epic 4g) modem! ahhhh after reading all the warnings .. fortunately I was able to ODIN the pit and EA24 rom successfully and the GPS still works. AT the moment I am letting the tablet incrementally update itself to gingerbread (while it is plugged in via usb to pc). And done.. now to do more unorthodox tests to see why its failing with no usb plugged
UPDATE 7: I think this is a hardware issue.. seems to only work normal when plugged in. doh.

So even after flashing the stock EA24 rar in Odin, it just sits at the boot logo and won't do anything? That is odd. In the stock recovery did you do a factory data wipe?

pvtjoker42 said:
So even after flashing the stock EA24 rar in Odin, it just sits at the boot logo and won't do anything? That is odd. In the stock recovery did you do a factory data wipe?
Click to expand...
Click to collapse
Correct! This is the ODIN log after a successful flash of the SPH-P100.EA24.SECURE.REV07-FULL_CL871413
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> Sbl.bin
<ID:0/003> param.lfs
<ID:0/003> zImage
<ID:0/003> recovery.bin
<ID:0/003> factoryfs.rfs
<ID:0/003> cache.rfs
<ID:0/003> dbdata.rfs
<ID:0/003> modem.bin
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Added!!
<ID:0/004> Removed!!
Does anybody the average time ti takes to stay on that glowing Samsung Logo after a factory reset/ flash?
edit: nevermind, its less than 10 glowing logo cycles.

Here is the best way to sovle the problem.
if your TAB stuck in the logo ,and recovery got the tips, the IC sandisk "sdin5d2-2g" on the mainboard is broblem .I let some body who is good at repairing mobile phone to use tools to take the IC out ,and throw it into bin. I go back home unpack the zImage kernel ,modify the file in it ,such as fota.rc,recovery.fstab , (in Ubuntu , grep mmblk * */* */*/* ) ,let the mmcblk0p1 for sdcard ,mmcblk0p3 for cache mmcblk0p4 for data , and repack the kernel . Then I repartition my kingston 8g C6 TF card to four primary partition,5.4 for the 1st ,180m for the 2nd ,190m for the 3th ,2G for the 4th. At last I use heimdall to reflash zhe new zImage into kernel and recovery .When the tab reboot ,let it into recovery and wipe the data and cache and reboot . After 10mins ,you will get the first setting for the tab.
here is my new zImage: /115。com/file/dnm9n22m#
the links: /www。diypda。com/forum.php?mod=viewthread&tid=336743
I am a new man in XDA, I can't post the outside link ,so please use " . " to replace " 。 " and add "http:/ " the links ,sorry !
My email is [email protected], you are welcome !

Phone won't boot

Long story short, I messed some stuff up on my phone. I'm pretty surre it's not completely bricked, but I have no idea what to do. I'm able to boot into recovery and download mode. But in CWM I can't do anything. If I try to restore one of my Nandroids, it goes fine until restoring data, at which point it hangs and then reboots, but gets stuck at the initial boot logo. The same thing happens if I do a wipe. I booted into download mode and connected to PC Odin and flashed the SGN_XX_OXA_KJ1_FACTORYFS.tar from dr ketan's guide, but then when it rebooted, it got stuck at the boot logo again. And now when I connect to Odin and try to flash anything, it doesn't flash.
Obviously it's not completely bricked, but is there anything I can do to restore it?

Did your SGN_XX_OXA_KJ1_FACTORYFS.tar flash went all the way through? Did
you see succeeded: 1/failed: 0 message in PC Odin?
If you did, all you had to do when stuck in bootloop afterwards was to pull out your
battery, wait a bit, put it back in, boot into stock recovery and do a factory reset and
cache wipe.

freedomispopular said:
Long story short, I messed some stuff up on my phone. I'm pretty surre it's not completely bricked, but I have no idea what to do. I'm able to boot into recovery and download mode. But in CWM I can't do anything. If I try to restore one of my Nandroids, it goes fine until restoring data, at which point it hangs and then reboots, but gets stuck at the initial boot logo. The same thing happens if I do a wipe. I booted into download mode and connected to PC Odin and flashed the SGN_XX_OXA_KJ1_FACTORYFS.tar from dr ketan's guide, but then when it rebooted, it got stuck at the boot logo again. And now when I connect to Odin and try to flash anything, it doesn't flash.
Obviously it's not completely bricked, but is there anything I can do to restore it?
Click to expand...
Click to collapse
Does the Odin get stuck at datafs???and in cwm at /data???

chasmodo said:
Did your SGN_XX_OXA_KJ1_FACTORYFS.tar flash went all the way through? Did
you see succeeded: 1/failed: 0 message in PC Odin?
If you did, all you had to do when stuck in bootloop afterwards was to pull out your
battery, wait a bit, put it back in, boot into stock recovery and do a factory reset and
cache wipe.
Click to expand...
Click to collapse
Yes, that's the message I got. And then I went to flash it again (I guess that was the wrong thing?) and then it didn't work, like it wouldn't even connect, it would get stuck at SetupConnection. But I'm trying it again right now and it's working so I'll try what you said.
vijai2011 said:
Does the Odin get stuck at datafs???and in cwm at /data???
Click to expand...
Click to collapse
Yes, cwm gets stuck at /data.

Ok, it successfully flashed again. And I got this:
<ID:0/013> Added!!
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> factoryfs.img
<ID:0/013> NAND Write Start!!
<ID:0/013> RQT_CLOSE !!
<ID:0/013> RES OK !!
<ID:0/013> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/013> Removed!!
Click to expand...
Click to collapse
It bootlooped again, and with the USB cord still plugged in, Windows said something like there was a malfunction and it couldn't read the device, or something like that. Does that mean anything?

Ok, chasmodo, I did what you said and booted into recovery, but it boots into cwm, not stock. Still do a factory reset/cache wipe?

Yes, and reboot.

Ok so I did that, and it got stuck at "Formatting /data" and rebooted/bootlooped again.

That's odd, factory reset/cache wipe usually help to remove bootloops after PC Odin flash.

Any idea where to go from here? I really messed this up bad, didn't I?

It is time for any wannabe-flasher to make up your mind where to belong:
- to be a experienced flasher and not to cry about bricked phone;
- or to be USER of that phone and stop using any advice from devs. That means going back to GB and from there full wipe and continue using stock and wait for stock (ICS) for your region.
From what I see:
1) devs make contradictory statements;
2) devs deny that the problem seems to be only CWM related (incompatibility between stock ICS kernel and great works of devs);
3) devs are 100% glueless about what to do in practical terms.

I'm not crying about a bricked phone, and I'd consider myself to be a fairly experienced flasher. I've run into a seemingly serious problem that I've never had before, and that's why I'm here asking for help. I'm trying to go back to GB, but it's just not working. I've reflashed SGN_XX_OXA_KJ1_FACTORYFS.tar via Odin multiple times without problem, but now when I do it, it doesn't reboot. If you can help me in any way, I'd greatly appreciate it.

Ok, so I decided to try flashing the original firmware that it came with (N7000XXLA6_N7000XXLA4_N7000XEULA1_HOME.tar.md5). It actually worked, and it rebooted, and then went through the whole "Installing update package" or whatever it says. At one point it said "Can't access to '/system/csc/XEU/system/'." Does that mean anything? So it finished installing and rebooted but then bootlooped again. So I went into recovery, and this time it was stock recovery, did a factory reset/cache wipe, and it actually worked. But then when I rebooted, it still ended up bootlooping.

[Q] help!!my i1890 is dead,reboot again and again

This device is strange.
first,I use odin to try to flash recovery.I can flash success,but always enter the 3e recovery..I tried lots of recovery version...and always can flash success ,and always enter the 3e recovery , It's can't enter my recovery.
and than I try to use ROM MANAGER to flash CWM RECOVERY. It's success to flash and it's can enter.
And than I use this CWM RECOVERY to flash a "DMod V6" ROM(http://forum.xda-developers.com/showthread.php?t=2165575)
...And than ..after finish and reboot,the trobble is coming.....
can not enter system , always show "Samsung Galaxy S III mini", and reboot,it's reboot again and again.
I try to use odin to flash a original rom and it's not useful , it'is always reboot again and again.
I try to use samsung kies to fix it , but not useful.
I try to flash PARAM_I8190.tar.md5 and PARAM.tar , it's not useful.
I try to flash a pit file to repartition but it cannot flash into device:
<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>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now , I can enter odin mode and CWM RECOVERY.
What can I do ? What should I do ?
Thanks!

and than I flash "cm10.1_golden.maclaw.20130712.zip"(bbs.gfan.com/forum.php?mod=viewthread&tid=6366912&extra=page%3D1)
It's can enter system.but i saw it not IMEI .
so i try to flash "GT-I8190_modem.bin-XXAMG1-update.zip"(bbs.gfan.com/forum.php?mod=viewthread&tid=6120250&extra=page%3D1)
and now ...It reboot and reboot again ...
I try to flash back to cm10.1 ...it's not useful...
..:crying::crying: what is the matter?
Now I also can enter CWM RECOVERY and odin mode

Try factory reset /wipe data then flash stock
Sent from my GT-I8190 using xda app-developers app

serophia said:
Try factory reset /wipe data then flash stock
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
I done everything I can do .....
Someone flash a new rom it's can enter system but cant enter desktop , it's can wipe data to fix ..
but now I cant enter system......

Try to flash stock rom via odin, but i don't know how bad a missing IMEI is, don't know if it comes back..

No IMEI means no RIL no calls, no messages, no 3G network...
The only way to get it back is to take it back to Sammy's, but first try in any way you can to flash the original Samsung's ROM.

tux95 said:
Try to flash stock rom via odin, but i don't know how bad a missing IMEI is, don't know if it comes back..
Click to expand...
Click to collapse
I tried many many stock rom via odin...but all is not useful...it is still reboot again and again......
and now it's still can enter CWM RECOVERY and odin and can flash.
I think can use "dd if" backup a normal i8190 /dev/block/xxxx and use CWM RECOVERY to flash to my dead i1890.
It's can do ?

A few days ago my phone was on an endless boot loop.
Nothing worked (stock or custom rom) until someone suggested "La Fleur", a russian firmware from this post: Link

slowdyve said:
A few days ago my phone was on an endless boot loop.
Nothing worked (stock or custom rom) until someone suggested "La Fleur", a russian firmware from this post: Link
Click to expand...
Click to collapse
On thanks! It's may useful...but I have sent the phone back to the store...

thakns for this thread,im planning to flash my S3 mini with CM11 right now hope wont be needing this

Soft-bricked Phone

Hello guys!
I got a new galaxy s3 mini (i8200) today so I tried to install a custom ROM since the installed android version was pretty old. I chose cyanogenmod 11.0 from novafusion and I tried to install it using odin. During the setup I got an error:
Code:
<ID:0/011> NAND Write Start!
<ID:0/011> FAIL!
<ID:0/011>
<ID:0/011> Complete (Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So I ended up with the phone soft-bricked and I decided to try to use KIES for firmware recovery but without success. So now I have two problems:
- The phone is soft-bricked
- I guess it ran out of battery and whenever I connect the phone to the computer (or even try to charge it) it ends up restarting itself.
Video -- the problem:
[ LINK ]
What should I do now?

icewavedesign said:
Hello guys!
I got a new galaxy s3 mini (i8200) today so I tried to install a custom ROM since the installed android version was pretty old. I chose cyanogenmod 11.0 from novafusion and I tried to install it using odin. During the setup I got an error:
Code:
<ID:0/011> NAND Write Start!
<ID:0/011> FAIL!
<ID:0/011>
<ID:0/011> Complete (Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So I ended up with the phone soft-bricked and I decided to try to use KIES for firmware recovery but without success. So now I have two problems:
- The phone is soft-bricked
- I guess it ran out of battery and whenever I connect the phone to the computer (or even try to charge it) it ends up restarting itself.
Video -- the problem:
[ LINK ]
What should I do now?
Click to expand...
Click to collapse
http://www.gsmarena.com/samsung_i8200_galaxy_s_iii_mini_ve-6190.php
CPU: 1.2 GHz dual-core Cortex-A9
NovaFusion is based on NovaThor.
You can cry now...
... And good luck !

There is a sticky unbrick thread here:
http://forum.xda-developers.com/showthread.php?t=2159660
For the charge problem, I think it works in download mode, try to enter that and leave it for a while.
EDIT: missed that this is an i8200... Do you have a backup of stock? If not, I guess you will need to hunt one down...

Forget. My bad.

jakot said:
There is a sticky unbrick thread here:
http://forum.xda-developers.com/showthread.php?t=2159660
For the charge problem, I think it works in download mode, try to enter that and leave it for a while.
EDIT: missed that this is an i8200... Do you have a backup of stock? If not, I guess you will need to hunt one down...
Click to expand...
Click to collapse
I'm trying but I only found few options available and it's so annoying to download 600+ mb when the speed is limited to 30 kbps by the file host.
LE: Is stuck in download mode (Odin Mode) and when is charging the same thing as in the video happens.
Let's say I will be able to charge it, should I flash the stock rom image using odin or there are any other steps that I need to do in order to un-brick it?
.

icewavedesign said:
I'm trying but I only found few options available and it's so annoying to download 600+ mb when the speed is limited to 30 kbps by the file host.
Let's say I will be able to charge it, should I flash the stock rom image using odin or there are any other steps that I need to do in order to un-brick it?
.
Click to expand...
Click to collapse
Your system or boot (kernel) partition is corrupt because you tried to flash a ROM for GT-i8190/N/L model only. You should flash a stock firmware for GT-i8200 model (available on sammobile.com/firmware) if you want a working phone

xXPR0T0TYPEXx said:
Your system or boot (kernel) partition is corrupt because you tried to flash a ROM for GT-i8190/N/L model only. You should flash a stock firmware for GT-i8200 model (available on sammobile.com/firmware) if you want a working phone
Click to expand...
Click to collapse
That's true, it was my bad and I realized that later when the phone was already bricked. Do I also need "PIT" file (repartition) or flashing the stock firmware would solve the problem?

icewavedesign said:
That's true, it was my bad and I realized that later when the phone was already bricked. Do I also need "PIT" file (repartition) or flashing the stock firmware would solve the problem?
Click to expand...
Click to collapse
You don't need a PIT file. Just flash a stock firmware for your phone model and everything will be ok

SW REV Check Failed device 3 binary 2 and sboot HELP

I tried to ROOT my phone and now its bricked. I can get to TWRP and reboot but it does nothing it just loops. I really need help. Thank you if advance.

Can you get to download mode? If so, Odin to stock. The error in the title of this post usually happens when you try to Odin an older firmware than what's already on the device. Be sure to Odin to the latest firmware.

have the same issue. Tried Odin to stock and got the following:
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any help will be appreciated.

same issue here

this error happen when i want to try installing new rom for s6
sw rev. check fail. device:3, binary:2
i search hole internet i couldnt find any solution
can any body suggest anything or help me in any way?
i broke sb elses phone and now i cant do anything help me pls guys

ALWAYS make a backup in TWRP before you try to flash a ROM. If something goes wrong you can restore and you should be okay.
IF you can still access TWRP then try to download and flash another ROM (Sick as Hell ROM is one suggestion). You may also try restoring to out of the box status using Smartswitch or Samsung Kies. I personally have used Kies with success on an Tmobile S6 several times (once after even wiping the system in TWRP).