hi all.. i have a g1 ,cgmod 4.2.1 flashed with a sigle_update method. now i'm trying to update with cgm updater to a 4.2.4 , but after update download, when i choose to apply the new rom, the g1 reboots in recovery mode, and shows this error :
E:cant mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (no such file or directory)
e:cant mount sdcard :cm-updates/update-cm-4.2.4-signed.zip
installation aborted
if i rename the 4.2.4-cgm file, in "update" and then try to install in recovery mode (alt+s ??) WITHOUT performing a wipe, i will lost google apps?
thanks in advance!!
Something maybe wrong with your SDcard
You can still move the update file to the root of your SD and be able to flash it. No you wont lose google apps
thanks a lot!!! yes i think there is someting wrong with my new sdcard.. maybe wrong partition method... thank you for the reply..
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
Hi all,
I just bought a Milestone, after reading this thread
http://forum.xda-developers.com/showthread.php?t=932196&page=13
I managed to run bootloader and install the UK vulnerable recovery as linked above (2.2). But the step after that: flash update.zip, I cannot apply it, the errors keep pumping out:
"E: Can't mount /dev/block/mmcblk0p1 (No such file or directory)
E: Can't mount SDCARD:update.zip
Installation aborted"
And the sdcard works randomly, most of the time android cannot recognize it, sometimes I just leave the phone blacked out for 1 minute and sdcard appears again T_T
Please help me out T_T, thank you
Bump !
replace the card
I replaced it with 2 other cards but apply update.zip still not working, errors changed to:
"E: Can't mount /dev/block/mmcblk0p1 (Invalid argument)
I've seen something fairly similar before. Make sure you try different brand cards if at all possible, and it wouldn't hurt to format them on a regular computer as well. I'll see if I can't dig up an article on the formatting type that was generally considered best for our phones....
Pretty basic I have the T849 and the screen is shattered so I haven't used it in quite a while, long story short pulled it out of a drawer today and charged up. Cant access email or the play store so i decided to do a factory wipe, factory wipe does not work is just reboots into cwm and these are the errors I see:
ClockworkMod Recovery v2.5.1.8
E: Can't mount /dev/block/stl11
(No such file or directory)
E:Can't mount CACHE:recovery/command
E:Can't mount /dev/block/stl11
(No such file or directory)
E:Can't mount CACHE:recovery/log
E:Can't open CACHE:recovery/log
E:Can't mount /dev/block/stl11
(No such file or directory)
I have also tried mounting my /data partition with no luck
E:Can't mount /dev/block/mmcblk0p2
(No such file or directory)
Error mounting DATA:!
I have also tried wiping the /data partition with no luck
Formatting DATA:...
E:Can't mount /dev/block/mmcblk0p2
(No such file or directory)
Error mounting /data/!
Skipping format...
Done.
I have also tried to flash a diff rom with no luck.
any advice is gladly appreciated, Namaste friends.
restock again and try overcome rom
See my signature.
My tab is a T849 T-Mobile one too, BTW.
priyana said:
restock again and try overcome rom
See my signature.
My tab is a T849 T-Mobile one too, BTW.
Click to expand...
Click to collapse
Do you have a link to the stock firmware? I have searched on this and google and most or all of the links are dead.
No, I don't have the stock.
I don't see the point though. GB-stock-safe-v5 works better than the stock T-mobile froyo anyway.
priyana said:
No, I don't have the stock.
I don't see the point though. GB-stock-safe-v5 works better than the stock T-mobile froyo anyway.
Click to expand...
Click to collapse
I got the gb stock safe flashed now im on the step where you are supposed to flash the -Overcome_Kernel_v4.0.0.tar but for some reason i dont seem to be able to find it in the zip file that was provided.
Great I have it fixed and it is working perfectly (as far as I can tell) now. Tommorow I will post the step by step and links that i used to get it fixed to save others the time and frustration of doing this, thanks for all the help. Namaste Friends
overcome rom works great only problem that I have ran into is the fact that wifi drops alot and hardly seems to work at all. And yes I have flashed the wi-fi fix, twice, and still no luck.
Have to go run some errands but afterwards I will post what I did step by step for those in the future that encounter the very problem that I had( the no factory reset or able to mount /data problem).
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.