Dear all,
Before I started a new thread, I just wanted to tell you that I've been awake for over 14 hours Starting to fix issues with my phone and tried alot of things before resorting to starting a new thread,So Please excuse me for starting one
Here's the long one :
Got a Galaxy S as A Present, after an Iphone 3GS, phone is great .. was a branded vodafone one I think from Germany running Android 2.2.1 I think back then.
As am Egyptian I wanted to the phone to read arabic fonts,So I decided it to flash with the Official Android 2.3.3 Arabic version.
Flashing went perfect, everything is smooth and all is very cool started to love the phone.
I dont have an external SDcard this is the internal one btw.
after a few months, a Friend challenged me that he's blackberry would boot faster than an android.
I was intrigued ! So I turned off my phone, turned it back on (I think this was the first time I do it since I flashed it) the phone kept rebooting !
and after like rebooting 10-12 times ... it finally booted correctly (5-6 minutes)
I said something must be wrong with the Firmware I flashed, but Ignored it as the phone worked perfectly after this.
a few days ago it died on battery, charged it ... reboot loop !
I found a hundred of thousands of guides on how to fix that boot loop !
I was getting errors :
e:failed to mount /sdcard (file already exists)
e:copy_dbdata_media:can't mount /sdcard
your storage not prepared yet.please use ui menu for format and reboot actions
meida files copy failed.
after going into recovery mode and trying to wipe data, these above errors always showed.
So I found a guide that suggests flashing with a 3-file ROM (Phone/Modem/CSC) and re-partition would fix this.
So I flashed with the official 2.3.3 (unmodified) and the errors disappeared, phone works perfectly ! although everything is erased of course.
So after setting it up again I thought that I should test restarting it again..
so I did .... and there it goes .. went on Looping again !!!
I went into recovery mode ... same errors appeared again ...
Re flashed 3 files again ... works fine ... restart = loop !
although one time it looped a few times and it did boot at the end, the SDcard (internal one) can be formatted without errors, never had any writing issues so I dont think its corrupted or anything.
But now I can't let the phone reboot or die on battery without flashing it again .. as if its a TETHERED jb iphone !
any suggestions ?
Please try doing as follows:
1. Flash a Kernel with lag-fix support like Voodoo which I can recommend in this case.
2. After flashing the Kernel the phone should boot and the converting of the partitions from RFS to EXT4 will begin, let it be until the phone reboots to the user interface.
3. Turn the phone off and enter Download-mode and re-flash the device using the firmware of your choice and a different pit file of that that is used on your phone (use 512.pit if it's on 803.pit or 803 if it's on 512), you need to use pit and you need to check re-partition.
4. Do a factory reset from recovery after completing the first boot, you need to let the phone boot all the way to user interface then do a factory reset after turning it off.
I hope that this will fix the issue that you are having, good luck and let us know how it goes.
[Ramad] said:
Please try doing as follows:
1. Flash a Kernel with lag-fix support like Voodoo which I can recommend in this case.
2. After flashing the Kernel the phone should boot and the converting of the partitions from RFS to EXT4 will begin, let it be until the phone reboots to the user interface.
3. Turn the phone off and enter Download-mode and re-flash the device using the firmware of your choice and a different pit file of that that is used on your phone (use 512.pit if it's on 803.pit or 803 if it's on 512), you need to use pit and you need to check re-partition.
4. Do a factory reset from recovery after completing the first boot, you need to let the phone boot all the way to user interface then do a factory reset after turning it off.
I hope that this will fix the issue that you are having, good luck and let us know how it goes.
Click to expand...
Click to collapse
I will try it right away, Thanks a lot for your time.
Well I don't know what to do now!
before flashing the kernel you suggested, the phone died on battery so I had to charge it, opened it .. boot looop .. so I said am going to do the same thing I used to do the past few days .. flash with the official 2.3.3 (3 files flash) and repartition.
Apparetly that doesn't cut it anymore, I tried DarkysRom as well, I still get the same error now :
e:failed to mount /sdcard (file already exists)
e:copy_dbdata_media:can't mount /sdcard
your storage not prepared yet.please use ui menu for format and reboot actions
meida files copy failed.
Can't get past it, and of course the phone keeps on boot looping if I ignored it
Am I beyond repair ?
ok after a few reboots, the phone booted correctly, is there's anything to do after it booted ? its on the 2.3.3 now, should I try to update from sdcard thing ?
You don't have a problem with the SD-Card, the problem is with the Kernel not able to mount partitions /data and /dbdata it's why you get those loops, that can happen if there is errors on these spaces and there journals which are located on these partitions.
My advice regarding flashing a costume Kernel and converting to EXT4 is to format these partitions and wipe all these errors, then flashing back to a firmware using pit and reparation should give you a clean firmware install with no errors.
You can try to turn off the phone and power it up again and see if it boots as it should, if not then some of the partitions still does not mount correctly.
You don't have to worry about the device, flashing and re-flashing it will not break it, it's a very solid phone, just be careful and you will be fine.
Always flash when the device has enough battery power (50%-100%)
Ok I've got the voodoo fix but its for 2.2 not 2.3 .. (Vooodo 5.5 ) there's a beta (Voodoo 6.0) for 2.3
I tried flashing 5.5 this morning to the current rom, it still kept on rebooting but it took along time to do so .. (long time between reboots).
So I thought of getting a rom with voodoo built in .. so I got the DarkySrom Resurrection 10.2 and after flashing .. it still went into constant loops..
I have a few things that I didn't try yet, I will post with updates, thanks again for ur time.
Related
Credit goes to Sombionix for this tip, Eugene, and all the others how helped me out when my phone was messed up. This is from the thread for Sombionix's ROM.... Works great!
Did You Flash Something Before Disabling Voodoo? Then This Fix is For You.
So you forgot to disable the voodoo lagfix before you flashed a new rom and now you're getting an error, similar to the one posted below. Even Odin won't allow you to flash back to stock. Well, pay close attention and with some luck, you'll be good as rain...or something like that.
E: Can't mount /dev/block/mmcblk0p2
(File exists)
Error mounting /data/!
Skipping format...
Copying files...
E: Can't mount /dev/block/mmcblk0p2
(File exists)
E: Can't mount DATA:
E: Failure at line 372:
copy_dir PACKAGE:data DATA:
Installation aborted.
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the 'True stock 2.1 firmware for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine! BAM!
how long did it took you to re-partition the SD? i tried to re-partition but it just sits in there and it does not show any indication it is being partitioned.. so i just did evrything except the repartitition part it it works great for me..
My Galaxy S from Bell I9000M, It was installed with JM8 with Voodoo lagfix. Last night phone freeze, i pull the battery, and reboot always stuck in black screen after S log and music. Today, without uninstall Voodoo lagfix (obivious I couldn't), I have been flashing it with all kind of ROM (with repartition), and same issue "always stuck in black screen".
Recovery Mode, it show error message:
E:copy_dbdata_media:Can't mount SDCARD:copy default media content failed.
Looks like Voodoo Ext4 is causing SDCARD not able to be mounted by system.
Do you know if this method will work on Galaxy S? it is safe for me to try it (I guess if I try it, at step #9, I will use I9000M stock ROM)? also where can I download " Eugenes 'Froyo that does not brick' file."?
PLEASE HELP!!
mingqlin said:
My Galaxy S from Bell I9000M, It was installed with JM8 with Voodoo lagfix. Last night phone freeze, i pull the battery, and reboot always stuck in black screen after S log and music. Today, without uninstall Voodoo lagfix (obivious I couldn't), I have been flashing it with all kind of ROM (with repartition), and same issue "always stuck in black screen".
Recovery Mode, it show error message:
E:copy_dbdata_media:Can't mount SDCARD:copy default media content failed.
Looks like Voodoo Ext4 is causing SDCARD not able to be mounted by system.
Do you know if this method will work on Galaxy S? it is safe for me to try it (I guess if I try it, at step #9, I will use I9000M stock ROM)? also where can I download " Eugenes 'Froyo that does not brick' file."?
PLEASE HELP!!
Click to expand...
Click to collapse
Do you guys have an Odin 1-click back to stock rom for the i9000? Does it have a Master Clear button? I have a Captivate so sorry for posting in here folks.
(The usual disclaimer - if this finishes bricking your phone - not my fault - but it worked for my phone )
My buddy just restored my phone by doing the following:
Downloaded Odin 1 Click back to Stock for Captivate
It has a MASTER CLEAR button on it - put the phone into Download Mode and hit the button... and let it ride for 15-20 minutes.
It didn't finish - he just unplugged and pulled the battery and when it came back up it was at the "computer++++" message.
Turned Odin 1 Click back up - put the phone into Download Mode - phone restored as normal.
Back to stock with a the ugly live wallpaper!
Thank you!!! I was screwed!!!!
Edit: Quick question, before I did this, when I was running fine, I had an option at the bottom of the pop up window you get when you hold home and see recent applications - this option would let me go in and kill running apps - it isn't there anymore and I can't remember if it was something I added - any ideas?
this worked for me ..... thank you!
How to unbrick a vibrant without Eugene's Froyo ROM?
I'm new - but searching doesn't seem to help much , i get all dead ends.
I've got a softbricked brant because of voodoo and a rom flash. The vibrant boots past the galaxy S logo and then goes black with all 4 buttons lit up at the bottom.
Everywhere I look seems to indicate I need to reflash with Eugenes Froyo that doesn't brick, but that seems to have been pulled from XDA.
Is there some other way around this or is the ROM stored offsite somewher else still?
Crankycoder said:
I'm new - but searching doesn't seem to help much , i get all dead ends.
I've got a softbricked brant because of voodoo and a rom flash. The vibrant boots past the galaxy S logo and then goes black with all 4 buttons lit up at the bottom.
Everywhere I look seems to indicate I need to reflash with Eugenes Froyo that doesn't brick, but that seems to have been pulled from XDA.
Is there some other way around this or is the ROM stored offsite somewher else still?
Click to expand...
Click to collapse
Froyo that does not brick can be found here:
http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=8
After flashing this via Odin, reboot to download mode again, and flash a stock rom of your choice in Odin, and you'll be up and running in no time.
The instructions in the OP of this thread are the short and sweet of this process, follow it, being sure to check repartition in Odin only at the last flash, ie stock firmware.
Ginger Clone's of the World Unite! Via the XDA App
not good
I hate it when that happens
thank you thank you thank you so much it work again
This should be in the bible sections if it's not yet there.
My internal SD failed about 5 minutes after the latest update and so I started trying to flash new roms/pit combinations like a madman. This led me to the Q&A subforum, where I found this thread:
http://forum.xda-developers.com/showthread.php?t=892534
Where:
Encrypted1024 said:
WOW! I am back up and running. This appears to be a data partition issue.
Can't say exactly what I did but here it goes. I may have done these things more than once today so you may have to run through this procedure a couple of times.
- Flashed JH2 with repartition and pit 512. (Stuck in bootloop)
- Flashed JL2 with Repartition and pit 512. (Boot to S Screen now)
- Flashed with SpeedMod 12
- Boot to recovery mode
- Format every partition
- Flash to JH2 with repartion and 512 pit. (Back to boot loop)
**** Heres where it was different***
- Flash to JL2 without repartion or pit
Booted up and working.
I know, sounds sketchy, but I must have reflashed my phone with 10 different firmwares today.
After I got it booted up I flashed it with Darky's 7.6 ROM. It gave an error at first about the data parittion but it repaired itself after running lagfix and changing to ext partition.
I may recomend to flash with Darky 7.6 and apply lagfix to rebuild the partitions and see if it fixes this issue right away.
Click to expand...
Click to collapse
I did this and followed every instruction, it works perfectly. My phone went from the DBdata recovery error and unable to mount filesystem -> Darky's Rom 7.7 with all the working bands.
I urge everyone with a failed bell phone to try this, it's amazing.
Also, thanks so much to Encrypted1024 for finding this.
Why didn't you just send it back to Bell and get your new phone + $100?
I have a launch Bell i9000m that refuses to die. I've flashed via CWM and Odin many times, but it's still fine. I'd actually be happy if it died so I can get the $100 credit and a new phone....
sr3yas said:
My phone went from the DBdata recovery error and unable to mount filesystem -> Darky's Rom 7.7 with all the working bands.
I urge everyone with a failed bell phone to try this, it's amazing.
Click to expand...
Click to collapse
sorry, but dbdata errors in recovery are not the major sdcard issue that is not recoverable from. dbdata errors are recoverable via flashing, same with st10/11.
unless someone with an mmcblk0p1 issue wants to try this, i highly doubt it will work.
wang1chung said:
sorry, but dbdata errors in recovery are not the major sdcard issue that is not recoverable from. dbdata errors are recoverable via flashing, same with st10/11.
unless someone with an mmcblk0p1 issue wants to try this, i highly doubt it will work.
Click to expand...
Click to collapse
I just tried it with my mmcblk0p1 error, and it doesn't work.
jentech said:
I just tried it with my mmcblk0p1 error, and it doesn't work.
Click to expand...
Click to collapse
Agreed. I just hit my second phone with that error and haven't seen any solution to recover from it. Dead = dead.
We need to get very clear on this board between what is a truly dead phone due to sd card issues vs what is recoverable (no comment on how sucky it is to experience a recoverable issue tho).
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: