Database Develop

Phone won't boot

I'm not sure what I've done, but I obviously wasn't paying attention. I had RyanZA's 2.3 beta lagfix installed and I decided to uninstall it using the supplied script. At some point I saw my phone reboot and I thought it had finished, but I don't really remember what happened after that.
Anyway, I've got it to the stage where it just shows the i9000 startup screen, goes black, then shows the i9000 screen again. I can get into recovery and I've got clockwork recovery installed as well, so I can get into that. I've used adb, but I can't get a log of it booting because it just says waiting for device and never gets past that stage. I used adb shell to see if I could manually process the scripts, but it looks like all the data and the backups of the data folders are gone.
I've wiped data in both clockwork and stock recovery, but I still can't get the phone to boot. System still looks ok, so I'm not sure why it's not working.
Anyway, my main question is, how can I get my phone back up and running? The mount usb option doesn't seem to be working, so I guess I'll have to use Odin or KIES, but what do I flash? Is there a link for a stock UK i9000 firmware somewhere?
Update:
Ok, I've got the phone working again, but after using Odin to flash the firmware, it reboots into recovery and I get the message can't mount /dev/block/stl11 (invalid argument)
The phone boots ok, but I can't download anything from the market ("download unsuccessful" almost immediately)
Internet works fine, so I don't think that's the problem.
Further update:
After Odin has flashed, the phone boots into recovery with the following messages:
E: Can't mount /dev/block/stl11 (invalid argument)
update media, please wait ...
E: Can't mount /dev/block/stl10 (invalid argument)
E: copy_dbdata_media:Can't mount DBDATA: copy default media content failed
E: Can't mount /dev/block/stl11 (invalid argument)
E: Can't mount /dev/block/stl11 (invalid argument)
This was after flashing WJM6 with .513 pit

You can try this...connect your phone with KIES and update it with the official firmware. I have not tried this so I dont know if it will help you.

Thanks, I eventually got it to work by flashing the WJG5 firmware. It would probably help if I'd known what it was actually running in the first place.
Now I've got it working though, I might try connecting to KIES and seeing if there's an updated version.

hey there, is this resolved? i got mine working after
can't mount /dev/block/stl11 (invalid argument)
but its still there. Do u know how to clean this error?
Update: I Fixed it by reflashing to WJG5 as stated above. BUT when i tryed reflashing with newer rom its still there..

Joans said:
I'm not sure what I've done, but I obviously wasn't paying attention. I had RyanZA's 2.3 beta lagfix installed and I decided to uninstall it using the supplied script. At some point I saw my phone reboot and I thought it had finished, but I don't really remember what happened after that.
Anyway, I've got it to the stage where it just shows the i9000 startup screen, goes black, then shows the i9000 screen again. I can get into recovery and I've got clockwork recovery installed as well, so I can get into that. I've used adb, but I can't get a log of it booting because it just says waiting for device and never gets past that stage. I used adb shell to see if I could manually process the scripts, but it looks like all the data and the backups of the data folders are gone.
I've wiped data in both clockwork and stock recovery, but I still can't get the phone to boot. System still looks ok, so I'm not sure why it's not working.
Anyway, my main question is, how can I get my phone back up and running? The mount usb option doesn't seem to be working, so I guess I'll have to use Odin or KIES, but what do I flash? Is there a link for a stock UK i9000 firmware somewhere?
Update:
Ok, I've got the phone working again, but after using Odin to flash the firmware, it reboots into recovery and I get the message can't mount /dev/block/stl11 (invalid argument)
The phone boots ok, but I can't download anything from the market ("download unsuccessful" almost immediately)
Internet works fine, so I don't think that's the problem.
Further update:
After Odin has flashed, the phone boots into recovery with the following messages:
E: Can't mount /dev/block/stl11 (invalid argument)
update media, please wait ...
E: Can't mount /dev/block/stl10 (invalid argument)
E: copy_dbdata_media:Can't mount DBDATA: copy default media content failed
E: Can't mount /dev/block/stl11 (invalid argument)
E: Can't mount /dev/block/stl11 (invalid argument)
This was after flashing WJM6 with .513 pit
Click to expand...
Click to collapse
Hello
I had the same and i solved through the guide here:
http://briefmobile.com/how-to-android-2-2-on-galaxy-s
But i think the problem really was that i have make an ext2 partition on sd-card.
I removed the sd-card during flashing.

Hi Guys, I'm looking for some help for a mate of mine who can't get his Samsung Galaxy S to start up.
The phone is box standard from Vodafone and only a couple of months old. It hasn't been rooted or tampered with in any way.
Today he decided to plug it into kies to check for updates and it showed him that there was an update available for his phone. he followed the on screen prompts and went about updating it. After it updated the phone just died on him. I have spoke to him over the phone to try and explain the 3 button recovery method to him but he still can't get it to boot up. He has sent me a photo of his phone so hopefully that may help for any potential advice. I'm no phone expert but could easily follow any instructions/ guides on flashing etc.
Any advice or help would be most grateful
Cheers, Sean

Pull out the usb cord.
Sent from my GT-I9000 using XDA App

DamianGto said:
Pull out the usb cord.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
He has done that and still no Joy

sean2476 said:
Hi Guys, I'm looking for some help for a mate of mine who can't get his Samsung Galaxy S to start up.
The phone is box standard from Vodafone and only a couple of months old. It hasn't been rooted or tampered with in any way.
Today he decided to plug it into kies to check for updates and it showed him that there was an update available for his phone. he followed the on screen prompts and went about updating it. After it updated the phone just died on him. I have spoke to him over the phone to try and explain the 3 button recovery method to him but he still can't get it to boot up. He has sent me a photo of his phone so hopefully that may help for any potential advice. I'm no phone expert but could easily follow any instructions/ guides on flashing etc.
Any advice or help would be most grateful
Cheers, Sean
Click to expand...
Click to collapse
If the phone can enter download mode, it can be rescued. Otherwise, it was definitely bricked.
Sent from my GT-I9000 using XDA App

Try to pull out the battery for 10 minutes. Then but the batteri back.
Then try to get in download mode.
If you can't, the try to see if odin see it.
If odin can see it try to flash back original firmware.
If you are lucky it can work.
If not then it seems very bad.
Sent from my GT-I9000 using XDA App

Thanks Damian, I will pass this info on to him tomorrow. I wish my mate lived closer so I could have a go at it myself.

i do have the exact same problem but flashing JM8 doesn't solve it.
in odin 1.3 with re-partition enabled I used s1_odin_20100512.pit, CODE_I9000XWJM8.tar.md5 as PDA and MODEM_I9000XXJM4.tar.md5 as phone
on startup I still get "E:Can't mount /dev/block/stl11 (Invalid argument)"
any ideas please?

XlAfbk said:
i do have the exact same problem but flashing JM8 doesn't solve it.
in odin 1.3 with re-partition enabled I used s1_odin_20100512.pit, CODE_I9000XWJM8.tar.md5 as PDA and MODEM_I9000XXJM4.tar.md5 as phone
on startup I still get "E:Can't mount /dev/block/stl11 (Invalid argument)"
any ideas please?
Click to expand...
Click to collapse
Why dont you flash crc also?
Try to do a complete flash.
Then go in recovery more and do wipe catch and a factory reset.
If you manage to get it to boot do format your internal sdcard.
Sent from GT-I9000 Jpm OS kernel with z4mod

factory reset "invalid argument" ?

This SGS had the original O2 ADJM1 firmware without the 3 button combo, which I fixed using the 3 button fix from another thread. SGS was working fine but I thought I'd give in and try a custom Rom.
Installed Darky's 6.0, worked great, but when I tried a factory reset from the settings menu, it kind of semi bricked, so I used Odin to install "GT-I9000_I9000XWJM8_I9000XXJM4_CODE-MODEM" with pit 512 to recover the SGS.
Problem is, Android Market will not download "download unsuccessful" pops up all the time.
The I installed GT-I9000_I9000XWJM9, hoping to fix the problem, while keeping recovery 2e, but Android market still does not download.
When I try the "wipe data/factory" reset using the 3 button combo, I get the following errors:
Appling Multi-csc
installing Muli-csc
mps_dat value: KOR
copy_multi_carrier from : KOR
multicsc : can not access to /system/csc/KOR/system/
copy common_data E:Can't mount /dev/block/stl11 (invalid argument)
E:Can't mount /dev/block/stl11 (invalid argument)
wiping data...
Formatting DATA:...
format_root_device: /dev/block/mmcblk0p2Formatting CACHE:...
format_root_device: /dev/block/stl11Data wipe complete.
E:Can't mount /dev/block/stl11 (invalid argument)
E:Can't mount /dev/block/stl11 (invalid argument)
I'm guessing "E" is the internal SD card, so maybe there's a problem there
Also how do I fix this android market problem ?
I really need a pointer to installing a stock fully working Rom with recovery 2e, then I can move back to Darky's new 7.0 ROM.
Any help would be great.

forcedv said:
This SGS had the original O2 ADJM1 firmware without the 3 button combo, which I fixed using the 3 button fix from another thread. SGS was working fine but I thought I'd give in and try a custom Rom.
Installed Darky's 6.0, worked great, but when I tried a factory reset from the settings menu, it kind of semi bricked, so I used Odin to install "GT-I9000_I9000XWJM8_I9000XXJM4_CODE-MODEM" with pit 512 to recover the SGS.
Problem is, Android Market will not download "download unsuccessful" pops up all the time.
The I installed GT-I9000_I9000XWJM9, hoping to fix the problem, while keeping recovery 2e, but Android market still does not download.
When I try the "wipe data/factory" reset using the 3 button combo, I get the following errors:
Appling Multi-csc
installing Muli-csc
mps_dat value: KOR
copy_multi_carrier from : KOR
multicsc : can not access to /system/csc/KOR/system/
copy common_data E:Can't mount /dev/block/stl11 (invalid argument)
E:Can't mount /dev/block/stl11 (invalid argument)
wiping data...
Formatting DATA:...
format_root_device: /dev/block/mmcblk0p2Formatting CACHE:...
format_root_device: /dev/block/stl11Data wipe complete.
E:Can't mount /dev/block/stl11 (invalid argument)
E:Can't mount /dev/block/stl11 (invalid argument)
I'm guessing "E" is the internal SD card, so maybe there's a problem there
Also how do I fix this android market problem ?
I really need a pointer to installing a stock fully working Rom with recovery 2e, then I can move back to Darky's new 7.0 ROM.
Any help would be great.
Click to expand...
Click to collapse
Hi, i have exactly the same problem.
With the invalid argument problems on data/factory reset, and the download unsucessfull problem! i have reflashed 4times JM1 on my phone !!!
i give 25$ for someone who solve the problem !

The way I fixed this problem was in two steps.
I used the Kies registry hack (someone here has created a program (which I can't find a link to right now) for windows that fools Kies to recognize your SGS as requiring an official firmware update).
Once your SGS is back on your official carrier firmware, Android market will work again.
From there, I was able to do a proper factory reset, followed by installing Draky's 7 Rom, using the 3 button combo and update zip method......and till now it's all good.
My SGS went from being a useless paper weight, to a kick ass device.
Good luck.
*You mentioned JM1* you may not need to go back to that firmware, but whatever official carrier firmware that Kies updates your SGS to, should fix the market problem.

With the Internal SD Corrupted Fix, i have formated my internal SD and there is no invalid argument when i do a data/factory reset.
but i think this is another problem, i have tried anything.
The hang on installing/unistalling problem come when i add my Google Account on the Android Market.
After this, i can't install or unistall anything.. that show installing.... at the infinite.
(sry for my english)
i have created a new google account for re-downloading again applications on the market, but i'm really sad because i have bought a lot of with my other account! wtf...
can't someone have any ideas or can help me?
thanks!

[Q] Tab stuck on Samsung logo

Samsung Galaxy Tab SPH-P100
Carrier: Sprint
Tab is stuck on Samsung boot screen, I am able to go in to download mode, and tried multiple times to do a factory reset but keep Showing up (E:can't open/cache/recovery/last_log)
I tried to flash it with a SPH-P100 Rom but no luck.
Tried putting EA24 modem no luck
Ive been looking but all threads are old can not access links
Any type of help would be appreciated.
Thanks in advanced

probably same as this thread just a few below your.
Have you tried?
Including my post that link to the Mega development thread on Sprint tab, that has a live link of downloads?

priyana said:
probably same as this thread just a few below your.
Have you tried?
Including my post that link to the Mega development thread on Sprint tab, that has a live link of downloads?
Click to expand...
Click to collapse
Thanks for the fast response to tell you the truth I am a noob on android Ive been searching how to fix but can't If I could get a link to instructions and updated files to resolve my problem?
Thank You!!!

This one
http://forum.xda-developers.com/showthread.php?t=2373340
and the thread I linked to near the end before the user got his fixed.

Heeeellpppp
I have this Samsung Galaxy tab GT-p1000 whose applications are getting error message of "force close", I tried to delete all the installed applications, restored factory settings but It doesnt seem to uninstall all the applications, So I decided to
upgrade it from Gingerbread 2.3.6 to ICS after installing it I got an error message of "Encryption Unsuccessful", So tried resetting it, rebooting, wiping factory settings, wiping cache but nothing happened, I even removed the sdcard before rebooting it but still I got the same error message.
I got frustrated and made a stupid mistake, I formatted everything thru recovery mode, format /data, format /sdcard, format /system and all. Yes every possible format. Here comes the problem when I rebooted the system, I only got the "Galaxy Tab, Samsung" screen. I can't enter recovery mode anymore, I can still enter download mode but my pc won't recognize it, so Odin can't recognize it too. What should I do now? HEEEELPPPP pleassseeeee :crying:

If Odin can't recognise it, use a new PC.
Many have done so, even one last week.
Sent from my GT-P1000 using xda app-developers app

priyana said:
This one
http://forum.xda-developers.com/showthread.php?t=2373340
and the thread I linked to near the end before the user got his fixed.
Click to expand...
Click to collapse
I tried the process but after usig the tar file on odin I get this message
--botmode7=7 from cmdline...
E:failed to mount /cache (no such file or directory)
E:can't mount /cache /recovery/comand
--wiping data...
formatting data...
E:formating_volume: rfs format faild on /dev/block/mmcblk0p2
formatting /dbdata...
formatting /cache...
E:format_volume: rfs format failed on /dev/block/mmcblk0p1
data wipe faild.
E:failed to mount /cache (no such file or directory)
E:can't mount /cache/recovery_kernel_log
E:copy_kernel_file :: can't open /cache/recovery/recovery_kernel_log
E:failed to mount /cache (no such file or directory)
E:can't mount /cache /recovery/log
E:can't open /cache /recovery/comand
E:failed to mount /cache (no such file or directory)
E:can't mount /cache /recovery/log
E:can't open /cache /recovery/comand
E:failed to mount /cache (no such file or directory)
Any solution for this after this I try to reboot but The TaB is still bricked.:S
Thanks for your Help.

same comment here as in there.
It is either the partition is screwed up or the NAND chip is bad.
If you did Odin with PIT file and repartition ticked, and didn't come back alive like the other forumer there, then your internal NAND chip is bad.
There are several threads dealing with how to use external SD only and on damaged internal SD.

priyana said:
same comment here as in there.
It is either the partition is screwed up or the NAND chip is bad.
If you did Odin with PIT file and repartition ticked, and didn't come back alive like the other forumer there, then your internal NAND chip is bad.
There are several threads dealing with how to use external SD only and on damaged internal SD.
Click to expand...
Click to collapse
Sir, it seems that this internal chip problem is a huge problem for gtab7 users.. is it better if someone make the tutorial on how to use the external sd to stickies so ppl can notice it? Thanks..
Sent from my Galaxy Nexus using xda app-developers app

There is already one such thread
http://forum.xda-developers.com/showthread.php?t=1463756
Sent from my GT-P1000 using xda app-developers app

[Q] Reinstalling stock firmware - stuck in boot loop

I had my rooted Galaxy S running well on CyanogenMod 10.1, but wanted to unroot so as to use my bank's app. While flashing Android 2.3.6 with Odin 1.87, I got various error messages and the phone boot looped. I tried to follow the instructions here , but the stock ROM I9000XXJVU_I9000OXAJVU_OXA.zip doesn't seem to be available now. Installing Semaphore CWM went OK, but of course the stock ROM has overwritten that. The stock recovery says:
E: failed to mount /dbdata (Invalid argument)
Copying media files...
E:failed to mount /dbdata (File exists)
E:cope_dbdatamedia:Can't mount /dbdata
your storage not prepared yet. Please use UI menu for format and reboot actions.
What stock ROM should I use that will deal with this? Or is there another solution?

Amphibian59 said:
I had my rooted Galaxy S running well on CyanogenMod 10.1, but wanted to unroot so as to use my bank's app. While flashing Android 2.3.6 with Odin 1.87, I got various error messages and the phone boot looped. I tried to follow the instructions here , but the stock ROM I9000XXJVU_I9000OXAJVU_OXA.zip doesn't seem to be available now. Installing Semaphore CWM went OK, but of course the stock ROM has overwritten that. The stock recovery says:
E: failed to mount /dbdata (Invalid argument)
Copying media files...
E:failed to mount /dbdata (File exists)
E:cope_dbdatamedia:Can't mount /dbdata
your storage not prepared yet. Please use UI menu for format and reboot actions.
What stock ROM should I use that will deal with this? Or is there another solution?
Click to expand...
Click to collapse
try this http://forum.xda-developers.com/showthread.php?t=1640906

Amphibian59 said:
I had my rooted Galaxy S running well on CyanogenMod 10.1, but wanted to unroot so as to use my bank's app. While flashing Android 2.3.6 with Odin 1.87, I got various error messages and the phone boot looped. I tried to follow the instructions here , but the stock ROM I9000XXJVU_I9000OXAJVU_OXA.zip doesn't seem to be available now. Installing Semaphore CWM went OK, but of course the stock ROM has overwritten that. The stock recovery says:
E: failed to mount /dbdata (Invalid argument)
Copying media files...
E:failed to mount /dbdata (File exists)
E:cope_dbdatamedia:Can't mount /dbdata
your storage not prepared yet. Please use UI menu for format and reboot actions.
What stock ROM should I use that will deal with this? Or is there another solution?
Click to expand...
Click to collapse
You should factory reset and wipe cache and dalvik cache partitions. If else fails, try flashing a different stock ROM.

gsstudios said:
You should factory reset and wipe cache and dalvik cache partitions. If else fails, try flashing a different stock ROM.
Click to expand...
Click to collapse
Thanks guys. Meanwhile I managed to track down the XXJVU ROM and now have the phone up and running again on Cyanogenmod 10.2.1. But despite wiping cache and Dalvik cache, and factory resetting, it is still rooted! There is no Superuser app but #Superuser is still in the settings menu, and my bank's app reports that it won't work because the phone is rooted. Very odd. I suppose I'll have to try a different stock ROM, but why doesn't root disappear when flashing a stock ROM?

[Help] I'm having /cache mounting errors; how can it be fixed (no Windows)?

Hello!
I was going to clear the cache partition (ROM was acting strange) one night (night before New Year's 2017 of all the times) when these errors came up:
Code:
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
Attempting to mount /cache fails with this error:
Code:
E: Error mounting cache!
I did find a thread showing this exact phenomenon: https://forum.xda-developers.com/crossdevice-dev/android-one-general/bricked-phone-cache-img-canvas-a1-t3307290
However, it's not helping me too much since the main solution there is using SP Flash Tool; it is (to my knowledge) a Windows-only tool, but I don't have a Windows install on any of my computers (all Linux units). Are there any alternate methods to resolving this issue?
EDIT: Originally intended to be a Q&A thread, but I forgot to check the box for it;oh well!

Same problem, not able to flash any ROM, clear any partition, or reboot.
As for SP flash tool, it hard bricked my friend's phone ( wiped everything but didn't download...
Searched many threads for this , but no solution..
Any help would be greatly appreciated.

Rupesh diwakar said:
Same problem, not able to flash any ROM, clear any partition, or reboot.
As for SP flash tool, it hard bricked my friend's phone ( wiped everything but didn't download...
Searched many threads for this , but no solution..
Any help would be greatly appreciated.
Click to expand...
Click to collapse
A backup might be able to solve the issue. That won't work for me though since I had previously deleted mine due to a prior SD card failure.