I'm trying to flash Glorious Overdose ROM to my sk4g. Rooted...check.
CWM...check.
Booted the phone into recovery and got the regular recovery screen.
clicked on 'reinstall packages'
Got the orange Clockwork recovery.
clicked on wipe data/factory reset.
following screen shows:
formatting /data
formatting /cache
formatting /sd-ext
E: format_volume make_extfile4fs failed on /dev/block/mmcblk0p2
formatting /sdcard/.android_secure...
And it stopped right there.
It's been like this for the past 15 minutes. I have the phone plugged into my computers usb port to keep it powered up during the flash.
I don't want to pull the battery for fear I might brick the phone. The sk4g has the latest kj2 update. I'm somewhat of a noob. I have rooted and added CWM,but this is my first time flashing a custom ROM. Pls help. CWM version 4.0.0.2
u must heimdall or odin back to stock via download mode n btw wipe cache then wipe data first
Was able to get back to stock rom by pulling battery and rebooting, tried wiping cache first then data, and same problem.
Related
Just bricked my defy last nigh accidentally then flased a full nordic 2.2.2 via rsd lite everything went fibe BUT when i was going to install some roms via nandroid backup I get this errors.
tried flashing a 2.1 eclair but it wont boot up so I reflashed the 2.2.2 nordic for about 10x already
here's what cwm says when restoring
ClockworkMod Recovery v2.5.1.8
Checking MD5 sums...
Restoring System...
Restoring Data...
Restoring ,Android_secure...
Restoring Cache...
Restoring sd-ext
no app2sd partiton found. Skipping format of /sd-ext.
E:Can't mount /dev/block/mmcblk0p2 (file exists)
Can't mount /sd-ext/!
and more when on the stock recovery is says something that it can't mount etc2
please help me out guys this is really important
ive read through some forums and found that I need to repartition.how?what's the easiest way?
tried wiping dalvik cache but it fails too.
cant download from market too.
this sucks.
its my first android phone and now im messed up!!
I will really apreciate your help please
EDIT:now Im using MIUI but still unable to mount sd-ext
and these few errors
E:Can't mount /dev/block/mmcblk0p2
(File exists)
E:Can't mount CACHE:recovery/command
and log
what do O do pls?
sent from my MB525 using XDA Premium App
In stock recovery do factory reset wipe cache and reboot and flash ur SBF....
Sent from my MB525 using XDA App
bricked?
WTH happened?
are u able to go stock recovery? did you do a data & cache wipe?
it should all do it.after u can flash a different & clean SBF.
also try to format sdcard as well..dont bother losing the nand backup...
then just use rsd lite to reflash a different leaked/official 2.2 froyo
hi tnx all for ur help.
yes i am able to go stock recovery and even cwm recovery via 2init 1.4 its a stock clean froyo
im getting this error on stock recovery
it says
E:un able to read cahe/recovery/command and starter
anyone suggestion?
wiping dalvik cant be done due to errors posted above
Sent from my MB525 using XDA Premium App
After wipe and reset just flash SBF...Error is not problem according to me....
Sent from my toilet using my Motorola DEFY
Ok if you heve stock and second init recovery then nothing is lost. What CWM- says is totally OK. And stock recovery always unable to read /cache/recovery/command.
What firmware were you on when installed second init? You sould try to restore the nandroid of that firmware with CWM.
If you wiped your phone with stock recovery then CWM will not work then you should flash your stock sbf with RSD lite.
ok will try when I get back home and will post the results
note: im on cm7 beta 6 b4 this happened.
Sent from my MB525 using XDA Premium App
You have to go back to Nordic, via RSD Lite .
Flash the full rom, since you already flashed the whole sbf one time, you won't be worry about downgradability, it's lost.
Then wipe again, at the end the cwm should work as expected.
Just as a note after i flashed the full Nordic sbf i got stuck so i went into stock recovery and wiped data etc. This let me boot the nordic rom. Then just need to root, install 2nd init and reinstall cm7
yay! now im on cm7 and will check if the errors are still there
and btw how do I go back to 2.2.2 stock in order to install ephunord rom
edit:
custom recovery says
E:unable to read cahe/recovery/command
E:unable to read cahe/recovery/starter
then when wiping dalvik cache on cwm
when pressing wipe dalvik cache
E:unknown volume for path [/sd-ext]
then when I confirm it it says
dalvik cache wiped.
is it normal?
can't install the google apps package too downloaded many times but it always end up on bad installation or something
wew im so stressed with my phone right now
gonemad02 said:
yay! now im on cm7 and will check if the errors are still there
and btw how do I go back to 2.2.2 stock in order to install ephunord rom
edit:
custom recovery says
E:unable to read cahe/recovery/command
E:unable to read cahe/recovery/starter
then when wiping dalvik cache on cwm
when pressing wipe dalvik cache
E:unknown volume for path [/sd-ext]
then when I confirm it it says
dalvik cache wiped.
is it normal?
can't install the google apps package too downloaded many times but it always end up on bad installation or something
wew im so stressed with my phone right now
Click to expand...
Click to collapse
yah that appears on mine too,those unable to read things:i reformat my sdcard clean & i treat it normal since i've been flashing & experimenting a lot,& i dont do a backup of any of my nands i only back up my apps.
since IMO i will never go back to eclair for any warranty,only forward to the developments..
i trust my defy just like i trust the resources i get here in the forums ;D
my thing is i cant do a restore on nands. anyway what's the format of your sd card?is it fat32?
gonemad02 said:
my thing is i cant do a restore on nands. anyway what's the format of your sd card?is it fat32?
Click to expand...
Click to collapse
Have you tried to format your sd card with your phone?(not from pc)
yes tried it a couple of times already
anyone knows how do I wipe dalvik cache using adb?
these are the remaining errors I still have
E:Can't mount /dev/block/mmcblk0p2
(File exists)
E:Can't mount CACHE:recovery/command
Hi. I flashed sbf JRDNEM_U3_3.4.3-11. But my phone is stuck on animated bootlogo (with "blur"). I flashed back my 100% previously worked sbf - U3_3.4.2_155-002. And it stuck on animated "android". When i try to load recovery - green android robot with "!" and nothing. What i do wrong?
bomgavs said:
Hi. I flashed sbf JRDNEM_U3_3.4.3-11. But my phone is stuck on animated bootlogo (with "blur"). I flashed back my 100% previously worked sbf - U3_3.4.2_155-002. And it stuck on animated "android". When i try to load recovery - green android robot with "!" and nothing. What i do wrong?
Click to expand...
Click to collapse
try wiping cache factory and dalvik cache
gonemad02 said:
my thing is i cant do a restore on nands. anyway what's the format of your sd card?is it fat32?
Click to expand...
Click to collapse
most probably yes,my card would be on fat32 on default since its 4gb.
unless i force format it w/ fat16 from my pc.but it shouldnt be an issue.
well i get those kinds of errors too.i cant flash the gapps zip for the cm7
i even get failed write to SD whenever i download an app from the market or an unknown file out of the market.
bomgavs said:
Hi. I flashed sbf JRDNEM_U3_3.4.3-11. But my phone is stuck on animated bootlogo (with "blur"). I flashed back my 100% previously worked sbf - U3_3.4.2_155-002. And it stuck on animated "android". When i try to load recovery - green android robot with "!" and nothing. What i do wrong?
Click to expand...
Click to collapse
when u see the green robot:
press the volume up & down together to enter stock recovery.
use the volume up/down & power button to select.
tap ok button on the left corner to continue the process of wipe.
I see. we do really have the same issue.
Im now on MIUI.shame...can't even try roms via nandroid backups.
will parted work to fix/format my cache including the sd-ext one?
I cant mount it no matter what I do
I believe parted will work.
and whenever I try to root using super one click
it gives some error regarding cant mount etc2 file exists
but in the ened it's successful.
Sent from my MB525 using XDA Premium App
Errors in our sd card
Well yah.thats tthe reason why im back now on stock blur french..everything back to normal & ready to flash again...i dont know,maybe the card gets corrupted whenever im on a custom rom...
Ok so how's miui?any luck on that one? No time to flash now busy w/ my baby.... Im still longing for the cm7,maybe the nxt rel will be complete.
from CWM? I started it 20 min ago and every time I look at the screen it says:
-- Wiping Data...
Formatting /data...
Formatting /cache...
Formatting /sd-ext...
E;format_volume: make extf4fs failed on /dev/block/mmcblk0p2
Formatting /sdcard/.android_secure
Terra27 said:
from CWM? I started it 20 min ago and every time I look at the screen it says:
-- Wiping Data...
Formatting /data...
Formatting /cache...
Formatting /sd-ext...
E;format_volume: make extf4fs failed on /dev/block/mmcblk0p2
Formatting /sdcard/.android_secure
Click to expand...
Click to collapse
It happens in seconds. last time it happened to me i had to odin. i suggest using ayoteddys cmw3xx
How do I acquire that? Sorry I'm very new to phone dev
Terra27 said:
How do I acquire that? Sorry I'm very new to phone dev
Click to expand...
Click to collapse
nahh no problem dude, i know what its like to soft brick your phone so ill help to the best of my knowledge. http://forum.xda-developers.com/showthread.php?t=1126631 it's here. on teddy's first post. so pretty much, you would download it, put it onto your phone which is the /sdcard part, then 'flash it' (fancy word for install) by going into cwm mode, and going to install .zip from sd card, find the cwm3xx file at the bottom, then flash it. THEN it'll pop up a 'new' cwm mode and from there factory reset, reset the cache, go to advance and erace dalvil cahe and check your mounts, then flash the new rom..if your trying to flash a rom that is lol. if you have questions post away!
oh and i think this should go in the general section.
Im stuck on the Sidekick/Tmobile/Samsung screen now and it will vibrate once, then 3 times then wait 3 seconds then vibrate once then 3 times etc.. WHy?? is it bricked now?
Terra27 said:
Im stuck on the Sidekick/Tmobile/Samsung screen now and it will vibrate once, then 3 times then wait 3 seconds then vibrate once then 3 times etc.. WHy?? is it bricked now?
Click to expand...
Click to collapse
its soft bricked you have to odin!
tylermaciaszek said:
its soft bricked you have to odin!
Click to expand...
Click to collapse
Yeahh that happened to me too, and i had to odin, but it wouldnt read the phone so i had to uninstall and reinstall the drivers on my comp. then go into download mode and odin.
Yup, that kept happening to me.. Im gonna try and install this cmw now.. By the way, do i still have to check the mounts and storage because i've successfully installed the maximus rom gingerclone. Do i have to check mounts and storage everytime i need to flash a rom, if so what should they be, as far as Data, sd card, cache, and system etc..?
Blaggah said:
Yup, that kept happening to me.. Im gonna try and install this cmw now.. By the way, do i still have to check the mounts and storage because i've successfully installed the maximus rom gingerclone. Do i have to check mounts and storage everytime i need to flash a rom, if so what should they be, as far as Data, sd card, cache, and system etc..?
Click to expand...
Click to collapse
no you do not have to check!
Yes you do need to check! Not checking is what makes you soft-brick.
it should read:
System: Unmount
Data: Unmount
Cache: Unmount
Anything else isn't an issue.
Don't worry about the errors reading that cache file, they happen to everyone, it's part of the kernel.
sduvick said:
Yes you do need to check! Not checking is what makes you soft-brick.
it should read:
System: Unmount
Data: Unmount
Cache: Unmount
Anything else isn't an issue.
Don't worry about the errors reading that cache file, they happen to everyone, it's part of the kernel.
Click to expand...
Click to collapse
i thought once your on the red recovery you don't need to check! i never check....
terra i'm having the same problem you are. keep this thread in mind http://forum.xda-developers.com/showthread.php?t=1214432 hopefully i'll be getting a response soon. orange cwm is my nightmare
Please help!
I am getting this error on my sidekick 4G
E:format_volume: make extf4fs failed on /dev/block/mmcblk0p2
Formatting /sdcard/.android_secure
i was trying to upgrade to Lite'ning ROM but it gave me this error, i did already ODIN to stock and it did not work and what i mean by it did not worked i did get to stock and started from scratch but still getting the same errror..... any other suggestions?
Don't worry about that error, that just means that you don't have an android secure partition on your sdcard. nothing to worry about.
I don't see why red CWM would be any different from Orange CWM in having to check mounts... I always check my mounts, and have always had to.
well u say not to worry but i can't update the rom to the lightning rom b/c i cannot factory reset, if i don't factory reset, phone bricks
You don't have to factory reset, just make sure you check your mounts. that's why it's bricking.
ok... so what are the mounts?
Please see thread: [RECOVERY] CWM for the SK4G. Enjoy!
therion0 said:
I am getting this error on my sidekick 4G
E:format_volume: make extf4fs failed on /dev/block/mmcblk0p2
Formatting /sdcard/.android_secure
i was trying to upgrade to Lite'ning ROM but it gave me this error, i did already ODIN to stock and it did not work and what i mean by it did not worked i did get to stock and started from scratch but still getting the same errror..... any other suggestions?
Click to expand...
Click to collapse
Please see thread: [RECOVERY] CWM for the SK4G. Enjoy!
You will find in the OP (original post #1) there is a step:
CWM Final
http://www.krylon360.com/file_host/sk4g/update.zip
Place in the root of your SD.
After your in clockwork mod recovery (orange) (and have downloaded the update.zip to sd card) make the selection: -apply sdcard:update.zip (this will load cwm again (red cwm)
Now: reattempt!
Hello everybody,
I just tried flashing FIT Droid to my galaxy fit.
The phone wont boot now. The screen says "FITDroid".
I'm really freaked out.
Pls help.
Before flashing I flashed CM7. In CM7,Wifi was not working.
So went for FITDroid. Before flashing CM7 i had gingerbread 2.3.3(official update from kies).
reboot in recovery mode and wipe data and cache.
If that doesn't work flash a new firmware using ODIN
reboot in recovery mode and wipe data and cache
if not work may be u can try this one
make sure the CWM is installed on the phone
CWM entered then select mount storge
formats / cache
format / data
format / system
format / sdext
then install fitdroid from sdcard
If that doesn't work flash a Stock Rom using Odin
how long does it stay in FitDroid Boot word? in my case it took about 50-10 mins before it reached the home screen...
try to wipe the data and the cache...
Thanks that helped...
Hi all,
hope you can help me with this one...
I came from Beanstalk 4.4.240, rooted it way back, everything worked fine.
Now I wanted to get back to stock 2.3.6.... First I tried Heimdall, but its not detecting the phone, although Windows does (Sound at USB connection).
Therefore I switched to Odin as described here: http://forum.xda-developers.com/showthread.php?t=1613523
I used the Option A, adhered to all the rules (including step 4 of wiping cache and data).
Odin flashed successfully.
After reboot though I get the following error in the red recovery mode (after the update package installed successfully):
"e: format_volume: rfs format failed on dev-block-stl10"
"wipe cache not successful"
I then did the cache wipe manually, and it does it successfully.
Upon rebooting though its stuck on the ATT logo loop...
When I then go into recovery mode, the following message appears:
"e:copy_dbdata_media: cant mount /dbdata your storage not prepared yet, please use UI menu for fomrat and reboot actions
Media files copy failed.
#Manual Mode#
...
Successfully applied multi-CSC"
Any ideas what to do here? I'm thinking it could be a partitioning problem...
I just want to make sure I flash the correct thing to fix this...
Oh and currently I moved on to Option B of the odin pack from above in the hope it could fix it - flash is successful, but error messages are completly the same...
Any help is highly appreciated!!!
Fixed
So I tried a different package with PIT, PDA & Phone (this buddy here: http://forum.xda-developers.com/showthread.php?p=27286083)
...and it worked!! Im back at stock
Hello, thanks for your help.
It seems I bricked my galaxy s7 while trying to format the /data partition.
I installed TWRP 3.2 and a custom rom, and everything went smoothly until then.
I tried installing an audio mod which throwed a " can't mount /data" error, searching for solutions I read that formatting the data partition to fat and back to ext4 should solve the problem, I tried formatting it to fat with TWRP, however on the first try I got a message that it suceeded, followed by a message that /data could not be mounted, TWRP seemed to be still working (there was no reboot button or any other buttons, just a "working" bar). After giving the phone 3 hours I decided to restart it, now I can't access TWRP; it stays on it's "splashcreen", and of course the phone won't boot.
I'm having a rough time with this so I will appreciate it a lot if you can help me.
Thank you.
Boot to download mode, flash stock firmware using Odin, then retry the TWRP installation.
For wiping data, you have to make sure you use the wipe option that makes you type out 'yes' to wipe, the other factory wipe methods don't actually properly wipe the partition.
iirc you also then need to flash the dm no verity zip from the TWRP thread.
Bro you didn't have to do anything but just formating the phone in the first place. Aassuming you're on oreo , it happens to a lot of people and myself, after flashing a kernel twrp was unable to munt data, all i had to do is a data format in twrp that fixed the problem .