Hey guys,
I just messed up my phone pretty bad. I forgot to disable lagfix before flashing a new kernel and now my sd card cannot be mounted. This is the error i get:
Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0p1)
Can't mount SDCARD: copy default media content failed.
I tried flashing using odin but no luck. My phone either goes in a boot loop or a black screen with the menu and back buttons glowing. Please help!
i have the same problem since 40 day i look too much and i dont find any solution and samsung says i had to change the mainbord its coast 250$. i dont know what to do wait more or what?
HI,
Try the following, worked for me
1) Go into recovery mode and wipe both cache and partition data
2) go to samfirmware.com and download the original rom for your phone (the one that came with it)... since you don't say what region you're from, I'll give you an example with mine. Mine is from Bell, and factory comes with UGJH2, so i downloaded that with ODIN and the PIT FILE, make sure to extract the TAR file from inside the RAR file. Put all 3 files in the same folder
3) Enter download mode, when the phone is in that state sometimes it's hard to access download, best way is... remove the battery, put it back in, then hold VOL DN + HOME + POWER until you see a working android bot inside a triangle. When you see that, connect your phone to your PC, double click on ODIN, then load the PIT file (CHECK BOX RE-PARTITION leave the others to default) and Select PDA and find the TAR file you extracted in STEP 2... then click on START, it's gonna take a few mins, and even after it's done, it's going to reboot, and it'll stay at the "S" logo for a bit, leave it, then it'll boot.
At least we hope it will.
Keep us posted,
Thank you,
Rodi.
Tried this on my buddies phone and it wasn't that easy.
It would boot up again, but only with the help of an External SD Card. Also, once you take it out, everything would FC and phone shuts down.
Also, there was a notice in notification bar saying "Unable to mount to External SD. Please remove, Mount point incorrect"
Wasn't able to revive it so buddy got rid of it.
Sad to say, but you're not the only one who has had these problems. Which is why I got rid of my i9000. Its an amazing phone and loved it, but once problems happened out of nowhere, I lost faith in it. Don't want to end up with a lemon. Phones are meant for emergencies afterall. When you start questioning if the screen will turn on, really makes one worry.
I have the internal SD problem too and i tried that..
I get stuck at ODIN where it says "File Analysis.."
It just stays there..
I did try flashing the stock 2.1 firmware using odin but no luck. I'm with Bell too and I'm sure I used the right .tar files, and I did repartition the memory with the right pit file, I'm not that much of a noob . Anyway, after searching every where to find a solution, I was pretty sure there was no easy way of reviving the phone. So I just went to Bell and they shipped it to Samsung to repair it. The problem is that when you don't disable the lagfix, your internal memory card remains partitioned under different formats and the system won't be able to read stuff off it ... or something like that.
i think the pit file couldn't repartition the sdcard we need to find another way to repartition the sdcard, but how we can do this? any suggestions?
sjouni said:
i think the pit file couldn't repartition the sdcard we need to find another way to repartition the sdcard, but how we can do this? any suggestions?
Click to expand...
Click to collapse
Well, in my case the pit file did repartition my sdcard, as odin successfully "past". Did you try other pit files to see if it works?
Yup same thing happened to mine. Its just stuck with buttons lit up but nothing on the screen. Went into recovery and wiped the hell outta everything there, but still nothin.
Im just gonna try to return it and get a diff phone all together. Its been only 3 months since I got the damn thing. So they better take it back.
shaahinjjj said:
Well, in my case the pit file did repartition my sdcard, as odin successfully "past". Did you try other pit files to see if it works?
Click to expand...
Click to collapse
we need a 512 pit other not work, but on my sdcard as your's if the pit repartition the sdcard then no problem, what the lagfix do to sdcard? we need to back it to default state, how?
sjouni said:
we need a 512 pit other not work, but on my sdcard as your's if the pit repartition the sdcard then no problem, what the lagfix do to sdcard? we need to back it to default state, how?
Click to expand...
Click to collapse
If I knew how, i wouldn't have taken my phone to Bell to fix it for me. I don't mean to disappoint you but I don't think there's any easy way of fixing the phone. Our phones are basically bricked! I suggest you do the same I did.
Related
Guys,
I'm in need of help fast.....
Just tried to do the Froyo Upgrade and have hit an almighty problem.
Kies downloaded and went to the next stage 'Upgrade'.
It got about 5% into doing this when the bar stopped moving and the phone switched off.
It's been like this now for over 30mins..... The phone won't power up (it's still connected to the PC).
HELPPPP.
Well you get my sympathy vote! But other then that I think you know yourself what to do. You've been around... Good luck!
Yes..... Bloody Phone, Bloody Kies, Bloody Samsung.
I unplugged the phone in the end and Kies offered to do a Firmware Recovery so I thought why not give it a try.
I went into Download mode, reconnected and Kies started the recovery procedure only for again the bar to stop moving again and it's stopped doing the recovery.
The screen on the phone remained a constant bright Yellow.
I unplugged it again and tried once more... It again stopped about a quarter way into the recovery only this time the screen has turned a constant Green.
Damn.................
The sad thing is that this reminds me so much of my sinclair zx81. 25 years later and we still have to deal with the same problems. Never sure the data gets from point A to point B.
Right.... Now I need to find the address for UK returns.
Don't have my warranty card info with me either so looks like I'll have to Google the returns.... but I'm busy as hell and have an Op to carry out soon.
If anyone comes up with it (or the link) I'll be grateful.
Bugger....
I'm probably teaching the teacher, but are you using the USB lead supplied with the phone? I tried to download some music using another lead and the download stopped halfway.
Sorry if this is too obvious.
Geryatrix said:
I'm probably teaching the teacher, but are you using the USB lead supplied with the phone? I tried to download some music using another lead and the download stopped halfway.
Sorry if this is too obvious.
Click to expand...
Click to collapse
No problem on the 'techer', any advise or assistance is better than nothing.
Yes, I used the cable supplied by Samsung... Nothing seems to sort this out.
As you are thinking of returning it, I conclude you can't get to any recovery/download mode. I don't know if Kies messed up the bootloader or keymappings but there is still the diy jig you might try. Also I have come across many devices in my day that needed repetitive flashing to get to the 100%. It would be bad if this was the case with a 2010 phone but hey its a Samsung.
sargasso said:
As you are thinking of returning it, I conclude you can't get to any recovery/download mode. I don't know if Kies messed up the bootloader or keymappings but there is still the diy jig you might try. Also I have come across many devices in my day that needed repetitive flashing to get to the 100%. It would be bad if this was the case with a 2010 phone but hey its a Samsung.
Click to expand...
Click to collapse
Well I've tried the Firmware Recovery at least a dozen time, each time it starts and stops at different parts.
I nearly got to three-quarters through when the bloody thing hung again.
No problem with the 3 Botton access and getting the Yellow Android Man on screen.. No problems connecting to Kies but as soon as you try the recovery it stops at some point during the process simply saying "An unexpected error has caused firmware upgrade to fail. Do you want to perform firmware recovery now?"....... and that came up whilst doing the firmware recovery.
Doesn't work to flash with odin either?
xExisioNx said:
Doesn't work to flash with odin either?
Click to expand...
Click to collapse
I don't want to use Odin if possible.
With that many different phones and ROMS available I don't want to end up screwing the phone totally.
Well Kies does not have a reputation to be very functional but there are two or three other tools to flash your phone. Although I am not a compulsive flasher, I did use Odin a couple of times. I am not sure exactly why you are having stage fright (referring to your other post on this matter).
Bringing it back to Eclair with a stock rom, using the rom, pit and instructions on http://www.samfirmware.com might help you to restore sanity. Once you are sure you haven't lost your phone you can then retry to use Kies.
The problem for you might be a partialy broken bootloader or incompatibility between the rom mappings and your phones current setup. Flashing a low rom might solve that. (As I understand from heimdall there are high and low packages, the low packages contain a bootloader and are more risky to flash since replacing the bootloader might truly brick your phone)
Also I read about people just flashing a pit file to force a repartition and format of the phone.
Make sure to get it fixed before op, I wouldn't want my doctor to worry about his phone, stiching me up with a pair of siccors stil in me ;D
Don't be scared of Odin. It has recovered my phone a million times
Really, the time and effort of getting a replacement when you can fix it in 2mins with odin in your own home... seems crazy.
You can flash a UK firmware if theres one available, or otherwise flash any firmware and update to UK firmware using kies reg hack, as far as i understand.
sargasso said:
Well Kies does not have a reputation to be very functional but there are two or three other tools to flash your phone. Although I am not a compulsive flasher, I did use Odin a couple of times. I am not sure exactly why you are having stage fright (referring to your other post on this matter).
Bringing it back to Eclair with a stock rom, using the rom, pit and instructions on http://www.samfirmware.com might help you to restore sanity. Once you are sure you haven't lost your phone you can then retry to use Kies.
The problem for you might be a partialy broken bootloader or incompatibility between the rom mappings and your phones current setup. Flashing a low rom might solve that. (As I understand from heimdall there are high and low packages, the low packages contain a bootloader and are more risky to flash since replacing the bootloader might truly brick your phone)
Also I read about people just flashing a pit file to force a repartition and format of the phone.
Make sure to get it fixed before op, I wouldn't want my doctor to worry about his phone, stiching me up with a pair of siccors stil in me ;D
Click to expand...
Click to collapse
Thanks... Need to find out now which is the right PIT to download.
I was on JF3.
God... if only I had more time on my hands.
Okay... got to go guys... Surgery to do.
I'll do the Odin later.
To save me time searching could someone please post below the relevant links I need to get Odin and the procedure....
Cheers.
When you flashed did you remove your sim card? I had that same problem with ki es. Removed the sim card and redid the flash and it continued on it's way.
How this helps.
Sent from my GT-I9000M
Well, if you have an account at samfirmware you can use this link http://www.samfirmware.com/WEBPROTECT-i9000.htm.
Make sure before you do anything to check your phone model is the one I linked to. Making a backup of your efs directory is not possible anymore but normally that should be done also. As a precaution I always remove my external sd card and sim card before flashing and - as you know - have the battery loaded to the max.
It might be an idea to skip jf3 and go to JM8 with a 512 pit and repartition on. This because it seems to be the recommended way of doing things at samfirmware as preparation for the flashing of current froyo releases.
I have never had problems with their way of doing things but opinions differ.
[EDIT]
I downloaded their JF3 package to see if there was a pit file included as there is some discussion what PIT file to use 512 vs 513. The package contains no information on that. It does however contain the word LOW in one of the filenames ...
Beards said:
Okay... got to go guys... Surgery to do.
I'll do the Odin later.
To save me time searching could someone please post below the relevant links I need to get Odin and the procedure....
Cheers.
Click to expand...
Click to collapse
I don't think you need to use a pit, odin should use the information from the phone assuming partitions remain intact. I've flashed a dozen times without one. If you do use one then use 512.
First off, get into recovery try and clear, reset what you can. Remove the sim and external SD as a precaution. Then back to download mode without the phone usb connected.
Grab the JPO firmware > http://www.multiupload.com/MX8XW7BG24
Grab odin 1.3 > http://www.megaupload.com/?d=MADK0XTB
Extract the firmware somewhere, open odin then select JPO_JPO_U_JPP.tar as PDA. Leave everything un-ticked except reboot. Plug the phone into your PC make sure Kies is not running and the battery is charged. In odin you should see a yellow window under ID:COM with a COM port open. If you do hit start, if all goes well a green bar will move across until the phone reboots. Leave it to do its thing at the big S (I usually unplug USB by now, to avoid problems) wait upto 10mins first time. If it hangs try a reset and cache clear and reformat SD. That's all I do, worked with all the firmwares I've downloaded from Samsung's FUD server.
The PIT files are templates for partition information so Odin can manage the size of the internal device partitions. Your standard device should already be on 512 layout, the other PIT's were development hacks. Like I said you shouldn't really need to repartition, but if you do > http://www.multiupload.com/I5WICSBFJ1
Fornowagain said:
I don't think you need to use a pit, odin should use the information from the phone assuming partitions remain intact. I've flashed a dozen times without one. If you do use one then use 512.
First off, get into recovery try and clear, reset what you can. Remove the sim and external SD as a precaution. Then back to download mode without the phone usb connected.
Grab the JPO firmware > http://www.multiupload.com/MX8XW7BG24
Grab odin 1.3 > http://www.megaupload.com/?d=MADK0XTB
Extract the firmware somewhere, open odin then select JPO_JPO_U_JPP.tar as PDA. Leave everything un-ticked except reboot. Plug the phone into your PC make sure Kies is not running and the battery is charged. In odin you should see a yellow window under ID:COM with a COM port open. If you do hit start, if all goes well a green bar will move across until the phone reboots. Leave it to do its thing at the big S (I usually unplug USB by now, to avoid problems) wait upto 10mins first time. If it hangs try a reset and cache clear and reformat SD. That's all I do, worked with all the firmwares I've downloaded from Samsung's FUD server.
The PIT files are templates for partition information so Odin can manage the size of the internal device partitions. Your standard device should already be on 512 layout, the other PIT's were development hacks. Like I said you shouldn't really need to repartition, but if you do > http://www.multiupload.com/I5WICSBFJ1
Click to expand...
Click to collapse
Surgery postponed until tonight so I have some free time.....
Okay, I got Odin 1.3 & JPO Firmware.
I loaded the JPO into Odin (in the PDA section).
Next I put the SGS into Download Mode and connected via USB and sure enough the ID:COM came up yellow with COM7 so I hit Start.
The green line went so far across under KERNAL but just as it was about to finish that box the SGS screen changed to a solid Blue screen and nothing further is happening in Odin.
Any advice??
Odd never seen that before, maybe your root problem. Should have rebooted automatically once the progress bar reached the end assuming you had the reboot option selected. Try a manual reboot, hold the power button down until it restarts. My next step would be the repartition and try again, load the PIT file (as PIT). Same flash procedure as before just using the 512 PIT, reset it all and try again.
ok i recently got a european open to all networks samsung galaxy tab,
now i decided to install a custom rom last night with horrible results, my phone is now stuck on the samsung boot screen and will not load properly,
here are the steps i took that ended me up in this mess,
i installed rom manager from android market,
then installed clockwork mod from inside rom manager, following the exact steps i was given but heres where i think i went wrong,
at some point it asked u back up everything onto an sd card, now i thought i had an sd inside it already but i didnt and thats what i think caused all the trouble,
i backed up all my files anyway onto the internal memory b4 goin into recovery mode, after completely wiping the phone as it saids u shud do, i then proceeded to load the modaco rom that i had installed into the "download" section of my memory and thats where it said the exact following words....
Checking /system...
E: failed to mount /system (invalid argument)
/system may be rfs. checking...
checking /date...
checking /database...
checking /cache...
filesystems need to be converted to ext4.
a backup and restore will now take place.
if anything goes wrong, your backup will be named before-ext4-convert-1297008631. try restoring it incase of error.
E:failed to mount /sdcrard (no such file or directory)
now i've tried restoring it and backing it up but all it repeats is the same thing, i know i messed up but now all i want to know is how can i fix it?
please any help would be much appreciated.
KingofXings said:
ok i recently got a european open to all networks samsung galaxy tab,
now i decided to install a custom rom last night with horrible results, my phone is now stuck on the samsung boot screen and will not load properly,
[..]
now i've tried restoring it and backing it up but all it repeats is the same thing, i know i messed up but now all i want to know is how can i fix it?
please any help would be much appreciated.
Click to expand...
Click to collapse
A brandnew start from scratch with Odin and repartioning with the rom from Rotohammer JMIv1.0 or v2.0 wouldt be my advice. You need the pit-file as well. Can be found on his server.
Heppieboeddah said:
A brandnew start from scratch with Odin and repartioning with the rom from Rotohammer JMIv1.0 or v2.0 wouldt be my advice. You need the pit-file as well. Can be found on his server.
Click to expand...
Click to collapse
ok ive downloaded odin v4.03, downloaded the original samsung firmware version P1000XWJJ3.rar from this website and downloaded the european P1_EUR.pit file also but i'll be honest i'm very new to the android world and dont have a clue what to do from here, how do i repartion the rotohammer rom?
i know i'm gonna sound stupid but if u could please explain it step by step i would be very grateful, thank you
Read the following thread that explains how to flash Rotohammer JMI ROM
http://forum.xda-developers.com/showthread.php?t=939360
Give it a good read and then ask if you have any questions before you start the process again.
KingofXings said:
ok ive downloaded odin v4.03, downloaded the original samsung firmware version P1000XWJJ3.rar from this website and downloaded the european P1_EUR.pit file also but i'll be honest i'm very new to the android world and dont have a clue what to do from here, how do i repartion the rotohammer rom?
i know i'm gonna sound stupid but if u could please explain it step by step i would be very grateful, thank you
Click to expand...
Click to collapse
First extract the P1000XWJJ3.rar. You shouldt be left with a single tar-file?! If so
Well if you have the right files. Start Odin. On the left you see the option 'repartion', tick that box. On the left you see pit. Tick that box and load the pit-file. Tick the box PDA and load the tar.file you extracted.
Start the tablet in download modus and attach it to youre pc. You shouldt see on top left a yellow box. Then just press start in Odin
beware that all on yore tablet will be deleted.
here is a very good guide with pictures.
http://leemn.wordpress.com/2011/01/25/galaxy-tab-flashing-a-new-rom-rotohammer-jme/
Heppieboeddah said:
First extract the P1000XWJJ3.rar. You shouldt be left with a single tar-file?! If so
Well if you have the right files. Start Odin. On the left you see the option 'repartion', tick that box. On the left you see pit. Tick that box and load the pit-file. Tick the box PDA and load the tar.file you extracted.
Start the tablet in download modus and attach it to youre pc. You shouldt see on top left a yellow box. Then just press start in Odin
beware that all on yore tablet will be deleted.
here is a very good guide with pictures.
......ok i followed the steps from above which was to install the Roto JMI Pre-Rooted Firmware v2 it got me pass the boot screen and everything on the tab works except it wont let me make phone calls, everything else works but it picks up no network and when i enter into settings it wont even let me access it?? almost like this is a wifi only rom ive installed??
what do i do from here to get it back to a phone?
Click to expand...
Click to collapse
KingofXings; said:
......ok i followed the steps from above which was to install the Roto JMI Pre-Rooted Firmware v2 it got me pass the boot screen and everything on the tab works except it wont let me make phone calls, everything else works but it picks up no network and when i enter into settings it wont even let me access it?? almost like this is a wifi only rom ive installed??
what do i do from here to get it back to a phone?
Click to expand...
Click to collapse
Ok great. at least you got it working again....
Now you need to flash the baseband-modem that you can find in the download link below. Flash it in Odin. Uncheck repartion. Check 'phone' and load the modemfile you downloaded. Its a tar.file. Leave it as it is. Then press start and the baseband will be installed.
Then you have to set-up the APN from youre telecom-provider and you will be up and running.....
http://forum.xda-developers.com/showpost.php?p=11148313&postcount=129
Heppieboeddah said:
Ok great. at least you got it working again....
Now you need to flash the baseband-modem that you can find in the download link below. Flash it in Odin. Uncheck repartion. Check 'phone' and load the modemfile you downloaded. Its a tar.file. Leave it as it is. Then press start and the baseband will be installed.
Then you have to set-up the APN from youre telecom-provider and you will be up and running.....
ok i downloaded the p100-radio-xxjmf.tar file and followed the instructions u gave but it failed and said this message...
<ID:0/004> set up connection.
<ID:0/004> cant open the serial (COM) port.
OSM All threads completed ( succeeded 0/ failed 1)
i dont understand why it would say that, could it be cos the .tar is xxjmf and the Rom by roto uses jmi? u think u could help? thanks again honestly, you've been a life saver.
Click to expand...
Click to collapse
Ok i just changed the usb ports and it works perfectly, the phone is back online and i didnt even have to fiddle with the apn settings, 3G just works fine,
thank you so much for ur help, i couldnt of done any of this without u, if ur ever around in north west london, u got a drink on me lol
KingofXings said:
Ok i just changed the usb ports and it works perfectly, the phone is back online and i didnt even have to fiddle with the apn settings, 3G just works fine,
thank you so much for ur help, i couldnt of done any of this without u, if ur ever around in north west london, u got a drink on me lol
Click to expand...
Click to collapse
Good to read youre up and running again...
Cheers....
Heppieboeddah said:
Good to read youre up and running again...
Cheers....
Click to expand...
Click to collapse
Hey mate, seems I am in a similar predicament here. Just 2 days back I flashed my Tab to Roto JMI v2 from a stock Asian firmware (DDJK3 I suppose) due to a bad Modaco flash that went really bad. Wiped off my data from god knows what areas. Now I am facing an issue that I am not able to understand or solve.
I was using Titanium Backup to remove a system app without Chuck Norris mode, which meant I had to reboot device and it would delete it OS level and say reboot to system. But once I click on reboot system an Exclamation mark just comes across the screen and NOW I CAN'T BOOT INTO my system. neither to i see the options it was earlier showing me upon Pwer + Vol Key up. The only option left for me is to reflash it using Odin.
Any Ideas mate? Reflashing again and again is not the solution right?
Thanks & Cheers!
sahildeswal said:
Hey mate, seems I am in a similar predicament here. Just 2 days back I flashed my Tab to Roto JMI v2 from a stock Asian firmware (DDJK3 I suppose) due to a bad Modaco flash that went really bad. Wiped off my data from god knows what areas. Now I am facing an issue that I am not able to understand or solve.
I was using Titanium Backup to remove a system app without Chuck Norris mode, which meant I had to reboot device and it would delete it OS level and say reboot to system. But once I click on reboot system an Exclamation mark just comes across the screen and NOW I CAN'T BOOT INTO my system. neither to i see the options it was earlier showing me upon Pwer + Vol Key up. The only option left for me is to reflash it using Odin.
Any Ideas mate? Reflashing again and again is not the solution right?
Thanks & Cheers!
Click to expand...
Click to collapse
Well, first of all. Removing system app ad hoc is not really clever to do. But you cant get into the recovery so you are able to clear cache and do a factory-reset? Volume-up+Power on and holding the volume-upbutton untill you get into the recovery?
If not you have to reflash from scratch with Odin. Use the pit/file and check repartion.
Hi Guys,
Been sent over here as you're the "bees knees" at fixing problems.
I have a Galaxy S which I rooted with Z4root and had the OCL lagfix also.
Was on 2.2 but updated via KIES to 2.2.1 yesterday ( sorry can't remember the last letters).
Phone now sits in boot loop, so tried reflashing stock firmware via Odin3. Phone WILL go into download mode, and WILL accept .PIT files and .TAR files. Odin says successful, but when phone boots, the Galaxy S screen comes up, then recovery screen with the following message
E:Can't mount/dev/block/st110 (invalid argument)
E;copy_dbdata_media:Can't mount DBDATA:
your storage not prepared yet,please use UI menu for format and reboot actions,
copy default media content failed.
Trouble is the phone won't boot so can't get to UI menu to format
Is this bricked big time or is it repairable? I presume the default media is the whole workings of the phone?
I have only limited knowledge of these things, and shouldn't have played with it in the first place.
Just need to know if I ought to claim for a new one on my house insurance?
Thanks
Do you have your stock jpy firmware already downloaded?
Follow the directions in the block 2 section.
http://forum.xda-developers.com/showthread.php?t=818556
presume you did not unroot or disable lagfix .
two different file systems is why it broke .
You need 3 button download mode + stock Firmware + odin
Flash stock firmware .
Or take the phone to Samsung and hope repaired under warranty .
http://forum.xda-developers.com/showthread.php?t=723596
http://forum.xda-developers.com/showthread.php?t=810686
http://forum.xda-developers.com/showthread.php?t=939752
jje
This one is easy to fix so don't panic.
Download this ROM and extract (Odin 1.7 and 512.pit are included), then do as follows:
-Start Odin and load 512.pit, don't connect the phone yet.
-Make sure "Re-Partition" is checked, don't change anything else.
-Load PDA.tar.md5 as PDA, MODEM.tar.md5 as PHONE and CSC.tar.md5 as CSC.
-Put your Phone on download mode and connect it, start flashing.
When flashing is done, the phone will enter recovery mode, if it get stuck at the same error, simply do a wipe/factory reset and reboot the phone, the phone shall boot normally then.
Link: http://www.multiupload.com/PZNPALHVDW
Good luck.
electrotune1200 said:
Do you have your stock jpy firmware already downloaded?
Follow the directions in the block 2 section.
http://forum.xda-developers.com/showthread.php?t=818556
Click to expand...
Click to collapse
Tried all that, loads it but phone won't boot up properly cos it can't write media to internal partition E
[Ramad] said:
This one is easy to fix so don't panic.
Download this ROM and extract (Odin 1.7 and 512.pit are included), then do as follows:
-Start Odin and load 512.pit, don't connect the phone yet.
-Make sure "Re-Partition" is checked, don't change anything else.
-Load PDA.tar.md5 as PDA, MODEM.tar.md5 as PHONE and CSC.tar.md5 as CSC.
-Put your Phone on download mode and connect it, start flashing.
When flashing is done, the phone will enter recovery mode, if it get stuck at the same error, simply do a wipe/factory reset and reboot the phone, the phone shall boot normally then.
Good luck.
Click to expand...
Click to collapse
Thanks for this. Got that file, using Odin and it gets as far as saying "Do not turn off Target" and it has been on that for approx 15 mins now. Is that too long?
tojjer said:
Thanks for this. Got that file, using Odin and it gets as far as saying "Do not turn off Target" and it has been on that for approx 15 mins now. Is that too long?
Click to expand...
Click to collapse
Yes, that is too long. Unplug the cable and take out the battery for 2 min. then put on download mode before you connect the phone and flash again.
When you unplug it now an error will appear, don't worry about it, just take out the battery for 2 min. and you shall be able to enter download mode again.
[Ramad] said:
Yes, that is too long. Unplug the cable and take out the battery for 2 min. then put on download mode before you connect the phone and flash again.
When you unplug it now an error will appear, don't worry about it, just take out the battery for 2 min. and you shall be able to enter download mode again.
Click to expand...
Click to collapse
You are one clever fella, don't know how to thank you enough.
It worked by doing that, and now it's back to stock I presume?
Is it safe for me to root again to use things like setcpu and lagfix?
Again, I can't thank you enough. My wife was in her element nagging me that I'd just cost us a lot of money !!
Tojj
tojjer said:
You are one clever fella, don't know how to thank you enough.
It worked by doing that, and now it's back to stock I presume?
Is it safe for me to root again to use things like setcpu and lagfix?
Again, I can't thank you enough. My wife was in her element nagging me that I'd just cost us a lot of money !!
Tojj
Click to expand...
Click to collapse
You are welcome, yes, it's back to semi-stock now.
In phone dialer enter the following : *#272*your_imei_number_here#
Put the phone IMEI-number in the code above and see if your CSC is XEU, if it's XEU then you are at stock, if not then choose XEU and hit "Install", the phone should reboot and reset and you will be fully at stock.
Root with SuperOneclick: http://forum.xda-developers.com/showthread.php?t=803682 Use 1.5 after enabling USB-debugging mode , and reboot, newer ones tends to hit or miss.
I think that you might need to try using the phone without a lagfix, if you can't live without it then try voodoo http://forum.xda-developers.com/showthread.php?t=774500 which uses EXT4 filesystem, it's way more secure than EXT2 that you were using, and it has a nice audio fix.
You will be good anyway...tell your wife that it's not easy to kill a Galaxy S, unless you use a hammer ofcourse.
I think she'll be saving the hammer for me !!
Hope it doesn't matter which 1.5, gonna try 1.5.5.
I'll take your advice on trying it without lagfix for a while, see how it goes.
Sorry to be a pain, but doesn't Froyo have apps2sd built in, cos at the moment it seems to be saving them to my phones internal memory, not internal/external sdcards?
The applications are always saved to a partition called /data , it's 2GB in size.
The internal SD-card is divided as 2GB /data and 6GB /sdcard.
some applications can be moved to the internal/external SD-cards, you can check that under Settings>Applications>Manage applications and choose an application, if the button "Move to SD card" is highlighted then the application can be moved/run from the SD-card.
Thanks, that explains it.
Phone was a little laggy at first but seems to have speeded up after a reboot.
I'll leave you alone now ( for a while at least )
Thanks again, you've been really helpful, and hopefully shut my Mrs up for a while
And that takes some doin, believe me !!
I have been on this forum for 3 days going through many fixes for this problem.
NONE of them have worked.
I have been able to get into download mode, and the phone is recognized via com3 in odin.
I have re-flashed it with Eugenes no-brick version, then re-flashed it with tons of different stock and non-stock roms. It gets to various stages but does NOT work.
Any ideas or fixes will be a lifesaver!! Thanks in advance!
If you can still get into download mode and Odin recognizes your phone, flash it with these two files, they work:
http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/
DO NOT check the re-partition checkbox in odin.
why not repartition as long as you put pit file in pit field repartitoin like crazy if you like .
and repartition would be required if you coming from vodoo based kernel or if you ran anyother partiton than rfs .
Thanks for the quick response.
I tried these files again (I have tried them before) both with and without checking the re-partition box.
It boots then says Vibrant Samsung, then crashes. When I turn it back on it again crashes and turns itself off after the initial splash screen.
Any other ideas? It says that I passed in Odin
charge your phone ?
bartek25 said:
charge your phone ?
Click to expand...
Click to collapse
Hahaha ya I wish it was something so simple (maybe it is!) but it isn't that!
download this ! http://forum.xda-developers.com/showthread.php?t=734475
put JFD in to PDA
also downlaod PIT from the same lik i gave you and seriously charge your phone , and when you odin with the files i gave you from the link check rapartition . check phone efs clear and f.reset time and auto reboot .
come back report resoults if not we help more .
also by any chance u didnt play with ROM MANAGER when your wibrant was working and didnt play with repartiton while there right ?
The same crashing loop has happened with the latest advice. I checked Phone efs clear, re-partition, auto-reboot, and f.reset.time.
I used tVhe T959UJFD PDA, and the 512 Pit.
This phone has been plugged in for days I really doubt the battery is dead.
It just is a constant loop of crashing,h whether at te "off battery" logo or the vibrant splash screen.
The ONLY flash that has given me any different results is the "eugene no brick froyo" which takes me to the Android Recovery screen but does not allow me actually select any of the options.
I am starting to think there may be a hardware issue.
To be completely honest, I got this phone from a friend who had bricked it. If I can get it working then I have a galaxy on the cheap.
On the downside I have no idea what he did to brick it, and he is not tech-savvy enough to know himself.
I come from an original G1 and Cliq, so this is a tad different then I am used to.
from my point of view your phone is fried (it happends) or you are not doing something right or someone is more tech savy to help more , did you pull battery out for at least a min and let it sit and try again to boot ...
Ohhh i know whats wrong with the phone ........if your friends gave it to you broken i think good advice is ,download a program that can repartition hard drive from windows like any program that can do format of anydrive from windows i recomend PARAGON PARTITION MANAGER , find your phone while in the program and u need some skills lol for it but find the phone and click delete partiton after you do that click apply 2. after deletion and applaying the actions click on the phones formated drive in the program i recomended you and click submenu wher you will see create partiton click FAT32 apply 3. click again on the disk you created and click format . 4 done , its easy just get to hang of it
Good advice, I will work on this and get back to you later tonight.
Thanks again!
sounds like your friend bricked his phone from ROM MANAGER by creating EXT4 partion in phones memmory not on SD thats why phone cant find a drive to install the system , happend to me by my own mistake but i got it to work so if that help you You have free vibrant so try hard if not u have paper weight toy
if u dont want the phone i buy back from you for 20 bucks so i cant smash it against the wall , always want it to do that
Intim said:
The ONLY flash that has given me any different results is the "eugene no brick froyo" which takes me to the Android Recovery screen but does not allow me actually select any of the options.
Click to expand...
Click to collapse
Just so you know when you get to this point you need to make sure you had ADB set up on your pc and then plug in the phone and do adb reboot and that will boot the phone up, then you can shut it down and go into DL and flash back to stock. if you read the directions from Eugene's no brick it stated you need to do a adb reboot to get it to work, so you can fix it if your getting to the recovery of that flash.
Ok so for the paragon partition manager it does not recognize my phone's harddrive. Unsure how to fix that as it is just a wizard type program.
I have been able to recognize the phone in ADB, although I cannot push any files to the phone (access denied) and have not been able to get SU access either as I am assuming he did not have root when he bricked it.
Any ideas?
you dont need to push any files to the phone with the adb, after you flash the eugene rom and it boots into recovery you just need to load up your adb and type this
adb reboot
thats it, and it should reboot your phone and if it does boot up fine then you can flash back to stock with odin from there.
Did you perchance happen to have installed the Team Whiskey DOW kernel on this phone?
Your symptoms match the symptoms of quite a few others.
http://forum.xda-developers.com/showthread.php?p=11704550&posted=1#post11704550
http://forum.xda-developers.com/showthread.php?p=11680374#post11680374
This morning I was attempting to update the firmware on my i9505.
I downloaded and extracted the .tar.md5 file and opened Odin in administrator mode.
Stupidly I then added the downloaded file as Phone and not PDA and pressed start in Odin. Unsurprisingly it failed.
I downloaded and tried other firmware (as Phone) before I realised my error.
When I boot the phone "normally" I get the failed firmware update message and have tried Kies but it can't connect to the phone.
Download mode does work, but when I try with the firmware (stock and pre-rooted) as PDA it always fails.
Can someone please help to recover my phone? I'm feeling pretty stupid just now
floydart said:
This morning I was attempting to update the firmware on my i9505.
I downloaded and extracted the .tar.md5 file and opened Odin in administrator mode.
Stupidly I then added the downloaded file as Phone and not PDA and pressed start in Odin. Unsurprisingly it failed.
I downloaded and tried other firmware (as Phone) before I realised my error.
When I boot the phone "normally" I get the failed firmware update message and have tried Kies but it can't connect to the phone.
Download mode does work, but when I try with the firmware (stock and pre-rooted) as PDA it always fails.
Can someone please help to recover my phone? I'm feeling pretty stupid just now
Click to expand...
Click to collapse
do you have custom recovery that you can boot into it?
samersh72 said:
do you have custom recovery that you can boot into it?
Click to expand...
Click to collapse
djembey sent me a couple of files and a ROM passed in Odin.
I don't think it's loading though as it's stuck on the SAMSUNG logo (and has been for about 15 mins) ....
floydart said:
djembey sent me a couple of files and a ROM passed in Odin.
I don't think it's loading though as it's stuck on the SAMSUNG logo (and has been for about 15 mins) ....
Click to expand...
Click to collapse
remove battery then insert it, boot into recovery, wipe cache and data, reboot
samersh72 said:
remove battery then insert it, boot into recovery, wipe cache and data, reboot
Click to expand...
Click to collapse
I rebooted to recovery and did a wipe data then a wipe cache. Recovery crashed and the phone rebooted.
This time the boot sound played completely and my phone is back to initial setup screen - thank you :good:
floydart said:
I rebooted to recovery and did a wipe data then a wipe cache. Recovery crashed and the phone rebooted.
This time the boot sound played completely and my phone is back to initial setup screen - thank you :good:
Click to expand...
Click to collapse
Did you feel the adrenalin flowing? I thought I bricked mine earlier. We had a mini power cut half way through flashing and it booted up with "Connect to Kies to do emergency firmware upgrade" or something like that. lol
Felt the cheeks of my bum twitch a bit there. lol
Managed to reflash one of the few stock ROMS I have to hand.
artnada said:
Did you feel the adrenalin flowing? I thought I bricked mine earlier. We had a mini power cut half way through flashing and it booted up with "Connect to Kies to do emergency firmware upgrade" or something like that. lol
Felt the cheeks of my bum twitch a bit there. lol
Managed to reflash one of the few stock ROMS I have to hand.
Click to expand...
Click to collapse
Aye, you could say that
I would say that I won't try flashing again after 3 or 4 hours sleep, but knowing me I probably will ....
S4 bricked after freeze during unmount internal sdcard
Dear friends. I need your help!
I did the actualization on my S4 i9500 (I9500XXUAMDK with root) and after this, I was trying to put more space in my SDcard (editing vold fstab files). During this process, appeared a message on phone about one error in sdcard and it suggested me to unmount the sdcard to try solve the problem. So, when I click yes, the phone froze and then I turned it off, but now it dont pass to Sangung Logo and the phone just go in recovery mode. In recovery mode I tryied clear/mount/unmount some file, but return with error to mount any directories.
I think the phone have the files or some partition corrupted!!! I can access it through ODIN and adb shell as well. There is (in adb commands) a command to fix the partition? How can I do?
I can access the phone in ODIN, and I tried to re-install the original FW. It did well (OK for update), but the phone cant finish the instalation after, because it cant mount anything. And returns to recovery mode with many messages about it cant mount directories.
Every thing I try to do, the phones (in recovery mode) returns "cant mount... or error to mount". I as said, I cant clear cache, format /sdcard or other directory or reset to factory data as well (because I think, the system cant mount any directories).
Somebody had this problem or could help me to solve it, please!!!
Tks in advance!
Barros
rgbarros said:
Dear friends. I need your help!
I did the actualization on my S4 i9500 (I9500XXUAMDK with root) and after this, I was trying to put more space in my SDcard (editing vold fstab files). During this process, appeared a message on phone about one error in sdcard and it suggested me to unmount the sdcard to try solve the problem. So, when I click yes, the phone froze and then I turned it off, but now it dont pass to Sangung Logo and the phone just go in recovery mode. In recovery mode I tryied clear/mount/unmount some file, but return with error to mount any directories.
I think the phone have the files or some partition corrupted!!! I can access it through ODIN and adb shell as well. There is (in adb commands) a command to fix the partition? How can I do?
I can access the phone in ODIN, and I tried to re-install the original FW. It did well (OK for update), but the phone cant finish the instalation after, because it cant mount anything. And returns to recovery mode with many messages about it cant mount directories.
Every thing I try to do, the phones (in recovery mode) returns "cant mount... or error to mount". I as said, I cant clear cache, format /sdcard or other directory or reset to factory data as well (because I think, the system cant mount any directories).
Somebody had this problem or could help me to solve it, please!!!
Tks in advance!
Barros
Click to expand...
Click to collapse
Why on Earth would you mess around with stuff like that? I hope you get help here, and next time just flash it and don't mess around. Perhaps get an external SDCard to solve your "space" problem.
artnada said:
Why on Earth would you mess around with stuff like that? I hope you get help here, and next time just flash it and don't mess around. Perhaps get an external SDCard to solve your "space" problem.
Click to expand...
Click to collapse
hehehe... I agree totally with you. But, it wasnt brick because there is some mistake in vold.fstab edition (I suppose). My fault is to accept unmout sugestion in the phone message.
But, it has a soft brick now. I got the access thought adb and odin and I'm trying to find a valid pit to rebuild the partition, that I think is corrupted now (I cant mount anything there. I can access it, but not change anything there).
I found a post here that there is a pit file. I cant ask there because I dont have enough privileges to post in development topic. The links are http://forum.xda-developers.com/showthread.php?t=2217777 and http://forum.xda-developers.com/showthread.php?t=2214865
I´d like to know if this pit (the second link has a file attached), is a valid pit. If yes, I could fix the phone!!!
Tks
rgbarros said:
hehehe... I agree totally with you. But, it wasnt brick because there is some mistake in vold.fstab edition (I suppose). My fault is to accept unmout sugestion in the phone message.
But, it has a soft brick now. I got the access thought adb and odin and I'm trying to find a valid pit to rebuild the partition, that I think is corrupted now (I cant mount anything there. I can access it, but not change anything there).
I found a post here that there is a pit file. I cant ask there because I dont have enough privileges to post in development topic. The links are http://forum.xda-developers.com/showthread.php?t=2217777 and http://forum.xda-developers.com/showthread.php?t=2214865
I´d like to know if this pit (the second link has a file attached), is a valid pit. If yes, I could fix the phone!!!
Tks
Click to expand...
Click to collapse
i think it is the right pit file for I9500 "Adonis.pit"
samersh72 said:
i think it is the right pit file for I9500 "Adonis.pit"
Click to expand...
Click to collapse
+1
@rgbarros: That is for I9500. Do not try it for I9505
stress nsitylf
samersh72 said:
i think it is the right pit file for I9500 "Adonis.pit"
Click to expand...
Click to collapse
Tks samersh72. I'll try it and I'll give the feedback after. :fingers-crossed:
demlasjr said:
+1
@rgbarros: That is for I9500. Do not try it for I9505
Click to expand...
Click to collapse
Tks demlasjr. My phone is a i9500 (not the ...905).
I run the adonis.pit on pit magic and it generated a analisys report (attached). Before I put it to run on ODIN, you (or somebody) could give a feedback about the entry memory below:
----------------------------------------------------------
Entry Memory Address: 0x754
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 12
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 196.608
Block Count: 16.384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CDMA-RADIO
Flash FileName: modem_cdma.bin
FOTA FileName:
My doubt is about the Partition Name CDMA-RADIO. Is this correct for a i9500 S4? I just really confirm and just to avoid to brick totally my phone, because when I run this pit through ODIN, or fix it or break it (no more chances to revive it)!!!
Tks very much!!!
I've seen that you have the 9500 later, but the forum was down and I couldn't edit my post. On that thread is a discussion about it. Somebody days that may be from 9502. I just seen the art you posted there, try adding this info too, including the pit magic report. Kinda hard to get confirmation and a trustful pit yet.
Sent from my GT-I9300 using Tapatalk 2
demlasjr said:
I've seen that you have the 9500 later, but the forum was down and I couldn't edit my post. On that thread is a discussion about it. Somebody days that may be from 9502. I just seen the art you posted there, try adding this info too, including the pit magic report. Kinda hard to get confirmation and a trustful pit yet.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Dear demlasjr, the forum was down and I forgot to attach the pit magic report when the forum goes up. Im attaching the files now (magic pit report and the adonis.pit that I got in other topic about S4 forum).
If you (or somebody) could help me to analyse it and give us a feedback if this pit is a valid pit for samsung S4 i9500, I will thank a lot!!!
Ps.: I´m trying to solve the problem too, looking for a way to mount the files through adb shell, because I got access my phone with this way and I can see all the files inside there. I just cant to mount any drive yet. Is it possible the problem be only a vold.fstab file corruption or missed? And in this case, is only to solve this file (vold.fstab) to revive my phone?
Or there is a some command in adb shell that could repair the structure files (like scandisk for dos?). I'm newbie on linux and I'm trying to use fsck command, but it returns a error message (fsck: not found). I dont know if I'm putting a correct/complete command to scan and repair the system/drives/files (or if there is a error)...
So, I´m trying to solve it using 3 differents ways of thinking (finding a valid pit, edit/restore vold.fstab and find a correct adb command line to scan and repair eventually corrupt files/directories) and if I solve the problem, I'll be happy to post a tuto here to help some other guys in the future.
Until there, Im working to find a solution.
Tks for help me!!!
nothing worse than this feeling. I remember when I did this to my S2, felt a cold sweat instantly... :crying:
crimptool said:
nothing worse than this feeling. I remember when I did this to my S2, felt a cold sweat instantly... :crying:
Click to expand...
Click to collapse
I agree totally with you my friend!!! I put it down in the first day I bought it... Its terrible!!! hehehe I put other phones down too, but how the others were olds phones (more then 6 months in the market), always I found the cfw or pit's to revive...
S4 is a newest phone, so, there is not a consistent or many topics/files/cfw tested yet. I´m looking for 3 full days about this and I found a lot of topics in how to root/unroot the phone, but not yet about pits, commands, etc...
The problem is that phone has a corruption files inside (my first diagnostic) and this is avoid to flash any firmware there until I fix this problem.
I´m trying to keep calm to avoid to worst the situation. I can access the phone yet, so I see a light in the end of tunnel yet!!!
But, the feeling is terrible!!! hahaha
Until Odia or GSMCN came back to you, we can't help you my friend. Only them can confirm the .pit file comparing the one already published with his phone's pit file.
One question....what if you try Emergency recover in KIES. Connect your phone to pc, open KIES, open emergency recover and insert your phone serial number. I read that people messed some times with the partitions and KIES saved their phone. It will not hurt to try, KIES is a putty compared with the repartitioning.
demlasjr said:
Until Odia or GSMCN came back to you, we can't help you my friend. Only them can confirm the .pit file comparing the one already published with his phone's pit file.
One question....what if you try Emergency recover in KIES. Connect your phone to pc, open KIES, open emergency recover and insert your phone serial number. I read that people messed some times with the partitions and KIES saved their phone. It will not hurt to try, KIES is a putty compared with the repartitioning.
Click to expand...
Click to collapse
I tried to connect it in KIES, but KIES didnt recognizes the phone. I'll try once again!!! I think I really discovered what the problem is, reported by adb parted command in /dev/block/mmcblk0: "error: Both the primary and backup GPT tables are corrupt. Try making a fresh table, and using Parted´s rescue feature to recover partitions"
So, probably when the phone froze during unmounting sdcard, the partitions were corrupted. I'm really thinking to use the adonis.pit, due I think there is no other manner to solve the problem.
I'm waiting any reply from Odia, to see if him can help me. Otherwise, I'll cross fingers and press "enter", to see what happen!!!
My friend, tks for all!!! After I´ll post the results!!! :fingers-crossed: