Database Develop

[Q] checking eMMC

I flashed back to Rocketrom GB V23 after the eMMC HARDBRICK warning.
My previous rom was Criskelo V2 ICS one
Is is possible to check the condition of the eMMC on the Samsung Galaxy NOTE?
I tried in terminal emulator:
su
(to gain root permission)
Than type in
cat /sys/class/block/mmcblk0/device/name
and got result: VYLOOM
I don't know what result i should get on a healty eMMC
anyone?
Thanks in advance

I would also like to know what that means I'll have to do some reading lol

Cyberdutch said:
I flashed back to Rocketrom GB V23 after the eMMC HARDBRICK warning.
My previous rom was Criskelo V2 ICS one
Is is possible to check the condition of the eMMC on the Samsung Galaxy NOTE?
I tried in terminal emulator:
su
(to gain root permission)
Than type in
cat /sys/class/block/mmcblk0/device/name
and got result: VYLOOM
I don't know what result i should get on a healty eMMC
anyone?
Thanks in advance
Click to expand...
Click to collapse
+1

We all have that serial name, the problem isn't that one! Galaxy Nexus also has the same eMMC!

zylor said:
We all have that serial name, the problem isn't that one! Galaxy Nexus also has the same eMMC!
Click to expand...
Click to collapse
So: f we have that name then all is good

I'm interested in this as well. Does anyone know how to run a full-scan of the EMMC to identify any possible bad blocks/sectors that have occurred?

+1 to this thread, also i got that VYL00M. is it possible to check if emmc is broken or not

I'm interested also, but I think we need not worry too much. If there is a bad block, the firmware will mark it as such and it will not be used anymore. The only consequence is a lower available storage space.
Sent from my GT-N7000 using XDA

Latoc said:
I'm interested also, but I think we need not worry too much. If there is a bad block, the firmware will mark it as such and it will not be used anymore. The only consequence is a lower available storage space.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
I've read that typing "dmesg" through the terminal will reveal any bad blocks. I'm not sure if this is dependent on a properly configured kernel or not.
If you want to output it, you can do "dmesg > /sdcard/dmesg.txt".
I found several interesting links for other methods....but so far, here's what my homework gathering has turned up.
http://www.slatedroid.com/topic/29039-rom-12-beta-ics-40x-team-drh-update-042112/page__st__4400
http://forum.xda-developers.com/showpost.php?p=25487137&postcount=22
http://forum.xda-developers.com/showthread.php?t=1284196
I recommend that you only READ through those links and do not attempt to try them as they are for completely different phones.

i think also if you see at cwm recovery this:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
your emmc is broken ^^

EdgaBimbam said:
i think also if you see at cwm recovery this:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
your emmc is broken ^^
Click to expand...
Click to collapse
Nope, if your eMMC is broken your phone won't boot. Something else is amiss if you get those errors in recovery.

mcmaddcatt said:
Nope, if your eMMC is broken your phone won't boot. Something else is amiss if you get those errors in recovery.
Click to expand...
Click to collapse
oh ok thanks for the info. By the way if i have reset binary count, no yellow triangle and if i would fck up emmc, will warranty will be valid or no? ;D

No, they'll have no way of checking. It would just be faulty eMMC from their perspective. With other words: warranty will be valid if phone contains stock rom for your region with no root off course.

EdgaBimbam said:
i think also if you see at cwm recovery this:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
your emmc is broken ^^
Click to expand...
Click to collapse
dam are u sure about that, because i get this message in cwm, but i flashed back to GB and runs fine, are u sure about the above which happens to me when i try to wipe dalvik cache, but when i select dalvik cache it wipes it.
again please can u confirm your statements above

@hykleif, don't worry about it. As long as it boots in gingerbread your Note's fine. I always had to select wipe dalvik twice to get it to wipe even before the ICS repacks. The errors stated in the previous post might as well be an error in CWM included in specific kernels. I've had the errors since i switched to speedmod 2k11-12 wich has khoush's CWM version, unlike Chainfire's CWM version wich is included on most kernels. For example i've never had the error on the Franco versions 3 to 10.

PoisonWolf said:
I've read that typing "dmesg" through the terminal will reveal any bad blocks. I'm not sure if this is dependent on a properly configured kernel or not.
If you want to output it, you can do "dmesg > /sdcard/dmesg.txt".
I found several interesting links for other methods....but so far, here's what my homework gathering has turned up.
http://www.slatedroid.com/topic/29039-rom-12-beta-ics-40x-team-drh-update-042112/page__st__4400
http://forum.xda-developers.com/showpost.php?p=25487137&postcount=22
http://forum.xda-developers.com/showthread.php?t=1284196
I recommend that you only READ through those links and do not attempt to try them as they are for completely different phones.
Click to expand...
Click to collapse
Thanks, nice research.
Checked dmesg.txt, no bad blocks messages in there. so i recon my eMMC is healthy.

EdgaBimbam said:
i think also if you see at cwm recovery this:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
your emmc is broken ^^
Click to expand...
Click to collapse
nope. imo it has something to do with the external sd card
---------- Post added at 12:55 AM ---------- Previous post was at 12:37 AM ----------
I think I have a solution to see if you have any bad blocks.
When I was a HD2 owner it had a two types of nand memory, one of them was Samsung (yea weird but true). And it was harder to make a bad block on Samsung. I run a test to see if there are ant BBs after flashing hundreds of roms, results - 0 ! So it is a good news for us
Ok guys so here is what you can do to test Note for BBs. I didn't try it myself so I'm not sure if it will work:
-Do a standard procedure of flashing a new rom.
-Do not reboot!
-In cwm menu go into advanced -> error report
-a log txt file will be copied on your sd card
-Mount USB SD
-On your computer navigate to your drive.
-Look for a folder called: clockworkmod. (If you have external sd card look there)
-10) Inside you will find a file called: recovery.log
11) Copy this to your Desktop.
12) Open with Wordpad or Notepad++
If anywhere except "system/xbin/badblocks" you can see something that says "bad blocks" you probably have them.
Hope this will help you.

That test is not representative. It is dependent on how much space the ROM used up. For example, if it only wrote to 250mb out of say the TMOUS HD's 1 GB internal ROM space, it would only report if it had difficulty writing to the 250mb portion of it I think.
I do not think it is a representation of the entire 1 GB. Somebody correct me if I'm wrong on this.
If I'm right, one easy way would be to simply flash a ROM that has been modified to use all of the phone's internal storage (or at least close to it) in terms of app storage. Only then would the test be a good indicator of bad blocks.
Abagnale said:
nope. imo it has something to do with the external sd card
---------- Post added at 12:55 AM ---------- Previous post was at 12:37 AM ----------
I think I have a solution to see if you have any bad blocks.
When I was a HD2 owner it had a two types of nand memory, one of them was Samsung (yea weird but true). And it was harder to make a bad block on Samsung. I run a test to see if there are ant BBs after flashing hundreds of roms, results - 0 ! So it is a good news for us
Ok guys so here is what you can do to test Note for BBs. I didn't try it myself so I'm not sure if it will work:
-Do a standard procedure of flashing a new rom.
-Do not reboot!
-In cwm menu go into advanced -> error report
-a log txt file will be copied on your sd card
-Mount USB SD
-On your computer navigate to your drive.
-Look for a folder called: clockworkmod. (If you have external sd card look there)
-10) Inside you will find a file called: recovery.log
11) Copy this to your Desktop.
12) Open with Wordpad or Notepad++
If anywhere except "system/xbin/badblocks" you can see something that says "bad blocks" you probably have them.
Hope this will help you.
Click to expand...
Click to collapse

Stuck without a OS

Good Morning
Very ironic,but i came here to ask about rooting my phone a year back and now i'm back in sort of the same situation..
A year back I rooted my froyo 2.2.1 based Galaxy S to a gingerbread version,then i used quite a few of the ICS roms available on this forum,had been using Cyanogen for the past few months.Yesterday i had some free time,so i thought would check out the JB roms available.
So i did the usual,download the JB version of Fishears since i had a iNand.put it in my internal sdcard..but i could not access the memory card from CWM 5.0.2.7..,so i put it in my external memory card and tried to run the zip from there,but the process got aborted in the middle,tried it twice,dint work.
Then i remembered i had faced this internal memory problem before,had to go and switch on the debugging mode in the developer option.[P.S:- i had been facing the encryption successful problem for half a year,was too lazy/busy to fix it,i just took it in my stride and rebooted a lot to get into the homepage]
So,I'm in CWM and i run the usual process and run the zip file from the internal sdcard,it started out fine,them BOOM.my phone reboots all of a sudden.When it restarts,it does not have a OS to boot into,the green android image with a red exclamation mark and a few text appears which happens too fast to read and it keeps rebooting and this process goes on.
I can still access CWM and the download mode,i tried going into CWM but the internal sd doesnt open and the zip file fails to mount from the external sd.
So i thought **** it,i'll do the rooting part again and i run up ODIN,download the semaphore 2.7.4 kernel,and i see it is just 15 mb or so,i remembered i used more than 1 file and used the pit folder also,but i read it on the semaphore website,its only 1 file and have to use it as the PDA.went to download mode and odin recognised it and the process completed without a hitch,it even showed a green PASS..
but the problem came when it had to reboot after the process,it got stuck in the "Galaxy S GT I9000" page and never moved forward.it was there for 30 minutes or so before i pulled out the battery.
Basically
1.I cant get past that page
2.I can access the CWM and Download modes
3.I accepted my mistake and thought of not doing any more mistakes,so icame here
4.When i boot into CWM mode,these errors come
E:failed to open/etc/recovery.fstab (No such file or directory)
E:unknown volume for path[/cache/recovery/command]
E:Can't mount /cache/recovery/command
E:unknown volume for path [/cache/revovery/log]
E:Cant mount /cache/recovery/log
E:Cant open /cache/recovery/log
E:unknown volume for path [/cache/recovery/last_log]
E:Cant mount /cache/recovery/last_log
E:Cant open /cache/recovery/last_log
E:unknown volume for path [/cache/recovery/command]
Click to expand...
Click to collapse
Cant access the external sd from the CWM now
I dont mind any os now,as long as i can take calls.Am leaving college for home by train day after,so i need a working os as soon as possible
Thank you for reading this and thank you in advance for taking your time to help me out

deathstoned said:
Good Morning
Very ironic,but i came here to ask about rooting my phone a year back and now i'm back in sort of the same situation..
A year back I rooted my froyo 2.2.1 based Galaxy S to a gingerbread version,then i used quite a few of the ICS roms available on this forum,had been using Cyanogen for the past few months.Yesterday i had some free time,so i thought would check out the JB roms available.
So i did the usual,download the JB version of Fishears since i had a iNand.put it in my internal sdcard..but i could not access the memory card from CWM 5.0.2.7..,so i put it in my external memory card and tried to run the zip from there,but the process got aborted in the middle,tried it twice,dint work.
Then i remembered i had faced this internal memory problem before,had to go and switch on the debugging mode in the developer option.[P.S:- i had been facing the encryption successful problem for half a year,was too lazy/busy to fix it,i just took it in my stride and rebooted a lot to get into the homepage]
So,I'm in CWM and i run the usual process and run the zip file from the internal sdcard,it started out fine,them BOOM.my phone reboots all of a sudden.When it restarts,it does not have a OS to boot into,the green android image with a red exclamation mark and a few text appears which happens too fast to read and it keeps rebooting and this process goes on.
I can still access CWM and the download mode,i tried going into CWM but the internal sd doesnt open and the zip file fails to mount from the external sd.
So i thought **** it,i'll do the rooting part again and i run up ODIN,download the semaphore 2.7.4 kernel,and i see it is just 15 mb or so,i remembered i used more than 1 file and used the pit folder also,but i read it on the semaphore website,its only 1 file and have to use it as the PDA.went to download mode and odin recognised it and the process completed without a hitch,it even showed a green PASS..
but the problem came when it had to reboot after the process,it got stuck in the "Galaxy S GT I9000" page and never moved forward.it was there for 30 minutes or so before i pulled out the battery.
Basically
1.I cant get past that page
2.I can access the CWM and Download modes
3.I accepted my mistake and thought of not doing any more mistakes,so icame here
4.When i boot into CWM mode,these errors come
Cant access the external sd from the CWM now
I dont mind any os now,as long as i can take calls.Am leaving college for home by train day after,so i need a working os as soon as possible
Thank you for reading this and thank you in advance for taking your time to help me out
Click to expand...
Click to collapse
you may try this, if you can boot to download mode but make sure your is GT-I9000
Before start, please backup all your important data and phones setting. Then,
Step 1:
I) Download Android 2.3.6 Gingerbread Value Pack (XXJVU)
II) Download ODIN http://www.mediafire.com/?nhhhkm5c2j43rhw Extract Odin3 v1.7.zip to get .exe file
also download the pit file, http://www.mediafire.com/?v2rub40k1bvccj4
Step 2: Extract the ROM [password: samfirmware.com]
Step 3: Launch ODIN. (Don’t open Samsung Kies)
Step 4: Turn off your Galaxy S.
Step5: Put your Galaxy S into Download Mode by Press and hold Volume Down + Home + Power buttons to boot into Download Mode.
Step 5: Connect your Galaxy S with your PC using a USB cable. (Before proceed to Next Step, please make sure that ODIN detect your device)
Step 6:
Click on Odin PIT Tab
Select the PIT – s1_odin_20100512.pit
Click on Odin PDA Tab
Select the CODE_I9000XXJVU_CL851880_REV03_user_low_ship.tar.md5 file.
Click on Odin PHONE Tab
Select MODEM_I9000XXJVU_REV_00_CL1092175.tar.md5.
Click on Odin CSC Tab
Select GT-I9000-CSC-MULTI-OXAJVU.tar.md5.
Step 9: Click on START in ODIN to start flash the leaked firmware on your device.
hope this will help.

I had this problem with Paranoid Android before... the zip was corrupt.
If you are able to extract the rom with winrar/winzip/totalcmd or other program, install it, if it is corrupt, download it again again and again...
Sent from my GT-I9000 using xda premium

Samtan4326 said:
you may try this, if you can boot to download mode but make sure your is GT-I9000
Before start, please backup all your important data and phones setting. Then,
Step 2: Extract the ROM [password: samfirmware.com]
Step 3: Launch ODIN. (Don’t open Samsung Kies)
Step 4: Turn off your Galaxy S.
Step5: Put your Galaxy S into Download Mode by Press and hold Volume Down + Home + Power buttons to boot into Download Mode.
Step 5: Connect your Galaxy S with your PC using a USB cable. (Before proceed to Next Step, please make sure that ODIN detect your device)
Step 6:
Click on Odin PIT Tab
Select the PIT – s1_odin_20100512.pit
Click on Odin PDA Tab
Select the CODE_I9000XXJVU_CL851880_REV03_user_low_ship.tar.md5 file.
Click on Odin PHONE Tab
Select MODEM_I9000XXJVU_REV_00_CL1092175.tar.md5.
Click on Odin CSC Tab
Select GT-I9000-CSC-MULTI-OXAJVU.tar.md5.
Step 9: Click on START in ODIN to start flash the leaked firmware on your device.
hope this will help.
Click to expand...
Click to collapse
Did what u said,got past odin,then it went into the setup on the phone and all of a sudden it went into the recovery screen,the message shown is
-- wiping data...
Formatting /data...
E:format_volume: rfs format failed on /dev/block/macblk0p2
Formatting /dbdata...
formatting /cache
Deleting meta data
Data wipe Failed
-- Applying Multi-CSC..
Installing Multi-CSC
APPLIED THE csc-Code "CPW"
Successfully applied multi-CSC
Click to expand...
Click to collapse
I have a option to reboot,its the samsung recovery screen..its still there,i havent touched my phone since then

deathstoned said:
Did what u said,got past odin,then it went into the setup on the phone and all of a sudden it went into the recovery screen,the message shown is
I have a option to reboot,its the samsung recovery screen..its still there,i havent touched my phone since then
Click to expand...
Click to collapse
flash CF-root for xxjuv with a pit512 (repartition ticked) cf-root can download from here http://download.chainfire.eu/132/CF-Root/SGS/CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS.zip
Once rooted with CWM, enter CWM using combo keys and enter "mounts and storage" and format everything except Boot and also do the full wipes one more time
Finally Flash the JVU+Root again one more time with PIT (repartition) to resolve this issue ...you may need flashing twice or more to solve this
issued.
http://forum.xda-developers.com/showthread.php?t=1841250 <--- this is very useful link for new user from xsenman

Samtan4326 said:
flash CF-root for xxjuv with a pit512 (repartition ticked) cf-root can download from here http://download.chainfire.eu/132/CF-Root/SGS/CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS.zip
Once rooted with CWM, enter CWM using combo keys and enter "mounts and storage" and format everything except Boot and also do the full wipes one more time
Finally Flash the JVU+Root again one more time with PIT (repartition) to resolve this issue ...you may need flashing twice or more to solve this
issued.
http://forum.xda-developers.com/showthread.php?t=1841250 <--- this is very useful link for new user from xsenman
Click to expand...
Click to collapse
flashed it with CWM,went into it and in Mounts and storage there is only 1 option- "mount USB storage"
Nothing else
Below that in the CWM message area,there is
E:unknown volume for path [/system]
E:unable process volume! Skipping...
Checking /data...
E:unknown volume for path [/data]
E:unable process volume! Skipping...
checking /cache...
E:unknown volume for path [/cache]
E:unable process volume! Skipping...
Done!
E:unknown volume for path [/cache/recovery/command]
E;Cant mount /cache/recovery/command
E:unknown volume for path [/cache/recovery/log]
E:Cant mount /cache/recovery/log
and the same for last_log
Click to expand...
Click to collapse

deathstoned said:
flashed it with CWM,went into it and in Mounts and storage there is only 1 option- "mount USB storage"
Nothing else
Below that in the CWM message area,there is
Click to expand...
Click to collapse
select mounts and storage format everything except Boot and also do the full wipes one more time and power off your phone
reboot to download mode follow by Flash the JVU+Root again one more time with PIT (repartition) to resolve this issue ...you may need flashing twice or more to solve this.

Samtan4326 said:
select mounts and storage format everything except Boot and also do the full wipes one more time and power off your phone
reboot to download mode follow by Flash the JVU+Root again one more time with PIT (repartition) to resolve this issue ...you may need flashing twice or more to solve this.
Click to expand...
Click to collapse
I dont think you got what i said.I installed CFW and went into the recovery,there under Mounts and storage ,there was nothing apart from "mount USB storage"..not even Mount BOOT..nothing apart from that 1 option..when i tried to do a wipe "data/factory reset or cache" it showed me that message which i posted above.still i installed the jvu+root again (Twice actually),it was the same result,the error i posted 2 posts above.
I'm in no mans land now and cant do anything apart from my phone apart from go into download and recovery mode

Please someone help me,i've to go on a 33 hr train journey tmrw and without a phone,it'll be really troublesome

Have you tried the EZ Recovery kit by Slaphead20?
http://forum.xda-developers.com/showthread.php?p=29114573
Sent from my GT-I9000

amerkiller1995 said:
Have you tried the EZ Recovery kit by Slaphead20?
http://forum.xda-developers.com/showthread.php?p=29114573
Sent from my GT-I9000
Click to expand...
Click to collapse
New developments now
I followed the steps given in the EZ recovery mode,it crashed into the same e3 recovery mode,for the heck of it i flashed the CFROOT which was provided and it worked fine..all disks were mounted fine and no errors in cwm,
went into Mounts and storage and formatted everything apart from boot and followed the rest of samtans advice
It crashed into the same e3 Rec mode again with the same meta data error message
any suggestions guys,atleast now i'm hopeful after seeing that CWM screen without any errors

deathstoned said:
New developments now
I followed the steps given in the EZ recovery mode,it crashed into the same e3 recovery mode,for the heck of it i flashed the CFROOT which was provided and it worked fine..all disks were mounted fine and no errors in cwm,
went into Mounts and storage and formatted everything apart from boot and followed the rest of samtans advice
It crashed into the same e3 Rec mode again with the same meta data error message
any suggestions guys,atleast now i'm hopeful after seeing that CWM screen without any errors
Click to expand...
Click to collapse
After flashing ez base, flash Cm9 and then if you want cm10
Sent from my GT-I9000

amerkiller1995 said:
After flashing ez base, flash Cm9 and then if you want cm10
Sent from my GT-I9000
Click to expand...
Click to collapse
Ok dont know whether this is good or bad
I installed CM9 from the external sd as the internal sd was inaccesible in any way..the installation showed info like
"the internal sd card marker could not be found
Going ahead with installation"
the installation continues and restarts once and updates but it does not boot into the main page,it directly goes into the Encryption Unsuccessful page.When i try Reset Phone,it goes into the CWM recovery screen with some errors,
when i try to install CM10 from this recvery screen,it initially stops the installation saying the data partition layout is different and all my data will be wiped.run the .zip to go ahead with the progress.I run this it goes directly into the CWM 6.0._._ and it doesnt show any errors,i try to reboot it gets stuck on the galaxy s screen.
this situation is better than the previous condition as i know a OS can still run on my Phone..Just need to get this thing rectified now

Please if anyone could help me right now,i would be really grateful..not able to contact anyone without my phone

It might be a hardware problem... I had something similar
http://forum.xda-developers.com/showthread.php?t=1895224
But for now go to Ez recovery and then try Darky's Resuruction ROM.
Sent from my GT-I9000

amerkiller1995 said:
It might be a hardware problem...
But for now go to Ez recovery and then try Darky's Resuruction ROM.
Sent from my GT-I9000
Click to expand...
Click to collapse
I installed Cyanogen 9 and got through tht EU page by restarting abut 20 times or so,now i'm trying to install a working version of gapps in it.Tried 1 but the setup failed,so i flashed back to Cyanogen 9 and am not touching it till i reach home.a device capable of making and taking calls is better than nothing..
Is there a way to download contacts from gmail without gapps,the play store is not included in the original rom and i'm hesitant to go into CWM recovery mode as i will have to tackle the EU page again
Anyways thanks for your help,will have to fix this problem once and for all after i reach home

I don't know about contacts from gmail. When you're home look at my updated post above
Sent from my GT-I9000

basically
just reflash gingerbread

Problem with kernel (2.6.32.61 and 2.6.32.60)

My goal was to install the ROM JB-4.1.2.
I've rooted my phone with flashtool, uncloked the bootloader also with flashtool and since then everything went great.Next step which wasn't hard at all was to flash the kernel via flashtool and it also happened with great result.The problem appeared when I was turning phone on, the system haven't turned up and my phone had showed only CWM Recovery.I knew that something went wrong but I made full wipe, cache and dalvik cache and installed JB-4.1.2. The CWM has said that system has been installed but when I've tried to boot phone JB didn't show up; again there was only CWM.
I've tried few times the procedure ( installing stock 2.1 android from Update Service, rooting phone with Flashtool, and flashing the kernel) but I'm facing the same problem with CWM.
Maybe I did something wrong, but don't know exactly what; or maybe my phone is not suitable for kernel?
I'm waiting for help!

Did you format the partitions before flashing the rom?

Yes, I did and nothing has changed.I again saw a screen with CWM and under options to choose at CWM I had a message from CWM like that:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log

Can anybody help with that odd problem?

S3 mini gt-i8190l problem

i try to flash one rom to my s3 mini but but i dont know what happens cuz it didnt works i have this problem my phone turn on in recovery mode and it says E:failed to open last_install:no such file or directori
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/log
can some body help me plz
sorry for my english

First things first - are you sure you are downloading the correct file for your s3 mini?
Second - do you have the latest recovery?
Finally, try to Re-download the zip file, you may have a bad download.
Hope this helps.

varianceness said:
First things first - are you sure you are downloading the correct file for your s3 mini?
Second - do you have the latest recovery?
Finally, try to Re-download the zip file, you may have a bad download.
Hope this helps.
Click to expand...
Click to collapse
i try but nothing happens i dont know what to do

I think you should flash official stock rom via Odin.

[Q] Bricked, no download mode, odin won't see phone

Hi, I hope some can help me
Here´s my story, the phone is a Galaxy Ace GT-S5830m, that had GingerBread 2x, I wanted to take it to Kit kat 4x, then I downloaded the CWM 6.0.4.6, but, because of my ignorance, I didn't downloaded the KitKat rom file at the same time, I successfully installed the CWM file, but after this the phone won't boot. The only thing it does is:
Enter recovery mode by pressing Volume Up+Home+Power
Show the Samsung logo
But I cannot make it enter download mode, if I hit VolumeDown+Home+Power it just shows the Samsung logo
If I connect it to the PC via USB cable, the PC won't recognize the phone on the USB drivers list. I already downloaded the Samsung USB drivers
When I enter recovery mode I see the four options for
rebbot system now
apply update from sdcard
wipe date/factory reset
wipe cache partition
And below that I see --Appling Multi-CSC --
E:failed to mount /system (Invalid argument)
E:failed to mount /system (Invalid argument)
What can I do? I'm I done? Please help! Thanks!

egomezmx said:
Hi, I hope some can help me
Here´s my story, the phone is a Galaxy Ace GT-S5830m, that had GingerBread 2x, I wanted to take it to Kit kat 4x, then I downloaded the CWM 6.0.4.6, but, because of my ignorance, I didn't downloaded the KitKat rom file at the same time, I successfully installed the CWM file, but after this the phone won't boot. The only thing it does is:
Enter recovery mode by pressing Volume Up+Home+Power
Show the Samsung logo
But I cannot make it enter download mode, if I hit VolumeDown+Home+Power it just shows the Samsung logo
If I connect it to the PC via USB cable, the PC won't recognize the phone on the USB drivers list. I already downloaded the Samsung USB drivers
When I enter recovery mode I see the four options for
rebbot system now
apply update from sdcard
wipe date/factory reset
wipe cache partition
And below that I see --Appling Multi-CSC --
E:failed to mount /system (Invalid argument)
E:failed to mount /system (Invalid argument)
What can I do? I'm I done? Please help! Thanks!
Click to expand...
Click to collapse
Hi
Flash a custom recovery like cwm v5 n then erase all like data sytem etc then download the .zip file that roots ur fone n flash it n then do a wipe data n thn place any custom rom of ur device n flash. . . If dsnt wrk do tl me
Hit Thanks

more questions
Raakib Zargar said:
Hi
Flash a custom recovery like cwm v5 n then erase all like data sytem etc then download the .zip file that roots ur fone n flash it n then do a wipe data n thn place any custom rom of ur device n flash. . . If dsnt wrk do tl me
Hit Thanks
Click to expand...
Click to collapse
Hi Raakib, thanks for taking the time to answer! But how can I put the cwm v5 in the phone if the PC doesn't see the phone? Sorry for the basic questions? I'm new in this things. The first time I did this I pluged the phone to the PC and I was able to see the memory card in the windows explorer so I only did a drag and drop, but that doesn't work any more, please advice, thanks!

just do 1 thing download the recovery file on your pc and then plug your sd card using any sort of card reader and then copy the file to memory card . Then insert the memory card in the phone and go to recovery and flash it. Hit thanks.
---------- Post added at 03:30 AM ---------- Previous post was at 03:28 AM ----------
if u want that your pc should recognize your phone, take it to download mode and see it gets detected in odin or not , if not then swap the drivers maybe upgrade or downgrade.

still no luck
Raakib Zargar said:
just do 1 thing download the recovery file on your pc and then plug your sd card using any sort of card reader and then copy the file to memory card . Then insert the memory card in the phone and go to recovery and flash it. Hit thanks.
---------- Post added at 03:30 AM ---------- Previous post was at 03:28 AM ----------
if u want that your pc should recognize your phone, take it to download mode and see it gets detected in odin or not , if not then swap the drivers maybe upgrade or downgrade.
Click to expand...
Click to collapse
Hi Raakib, just to let you know that I haven't had any luck with this, this is what I have tried, with a memory card reader connect to my PC, because the PC still doesn't see the phone
Using CWM v5.0.2.6 and with that version trying to install the original rom I get this
-- Installing: /sdcard/Downloads/S5830MUMnD1_S5830MTCEND1_TCE.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
So my attempt to recover gingerbread was unsuccessful, now, in all honesty I have no idea if I'm using the correct zip file of gingerbread, I mean, I downloaded from the sammobile page and choose the one for my country, but the instructions call for odin and to unzip the fiel, so I don't know if this zip file can just be copied to the SDcard and be unziped with CWM. So CMW needs special rom files different from the ones odin uses?
On my second attempt using CWM 6.0.4.6 to try to install kit kat 4.4 using the instructions from the androidcure website called "How to install Android KitKat on Samsung Galaxy Ace S5830", it mentions that I must use cwm v6 and the rom file called cm-11.0.0-RC4-GT-S5830-cooper-PS.zip I get this
-- Install /sdcard/Downloads ...
Finding update package...
Opening update package...
This package is for "cooper.GT-S5830" devices: this is a "".
E:Error in /tmp/sideload/package.zip
(status 7)
Installation aborted
If I use cwm v5 to try to mount /system (which is permanently un-mounted) I get this
mount: mounting /dev/block/stl9 on /system failed: Invalid argument
W:failed to mount /dev/block/stl9 (File exists)
W:failed to mount /dev/blockstl9 (no such device)
Error mounting system!
The phone still won't go in download mode and is still not visible by the PC
Any other suggestion? Thanks!!!!

egomezmx said:
Hi Raakib, just to let you know that I haven't had any luck with this, this is what I have tried, with a memory card reader connect to my PC, because the PC still doesn't see the phone
Using CWM v5.0.2.6 and with that version trying to install the original rom I get this
-- Installing: /sdcard/Downloads/S5830MUMnD1_S5830MTCEND1_TCE.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
So my attempt to recover gingerbread was unsuccessful, now, in all honesty I have no idea if I'm using the correct zip file of gingerbread, I mean, I downloaded from the sammobile page and choose the one for my country, but the instructions call for odin and to unzip the fiel, so I don't know if this zip file can just be copied to the SDcard and be unziped with CWM. So CMW needs special rom files different from the ones odin uses?
On my second attempt using CWM 6.0.4.6 to try to install kit kat 4.4 using the instructions from the androidcure website called "How to install Android KitKat on Samsung Galaxy Ace S5830", it mentions that I must use cwm v6 and the rom file called cm-11.0.0-RC4-GT-S5830-cooper-PS.zip I get this
-- Install /sdcard/Downloads ...
Finding update package...
Opening update package...
This package is for "cooper.GT-S5830" devices: this is a "".
E:Error in /tmp/sideload/package.zip
(status 7)
Installation aborted
If I use cwm v5 to try to mount /system (which is permanently un-mounted) I get this
mount: mounting /dev/block/stl9 on /system failed: Invalid argument
W:failed to mount /dev/block/stl9 (File exists)
W:failed to mount /dev/blockstl9 (no such device)
Error mounting system!
The phone still won't go in download mode and is still not visible by the PC
Any other suggestion? Thanks!!!!
Click to expand...
Click to collapse
the stock/original rom wont flash in the recovery. try to flash some other custom rom in CWM 5 and before flahing any rom you need to do a full factory reset and whether in cwm5 or 6 i m nt sure go into advance and wipe efs etc there then flash a rom. If still nothing then contact me i will tell you some great thing +918715031141. (my personal number)