Fix for boot loop - Galaxy Ace S5830 General

Some weeks ago, I decided to overclock my Ace: CyanogenMod-7.1.0-RC1-Cooper-KANG plus ClockWorkMod4. Got the overclocking kernel from ketut.kumajaya and started to play with frequencies while watching CSI Las Vegas.
In general, it's stupid idea to multitask things like this. In my case, I accidentally ticked checkbox "Set at boot", set the frequency to around 870 MHz and my phone rebooted. I have gone into the bootloop, tried almost everything:
-reinstallation of CyanogenMod
-reinstallation of some other ROM i have found on my disk
-cleaning caches, wiping etc
Without sucess of course
I have decided to check, what exactly happened with my phone, so connected it to PC and started logcat. There was a lot of errors related to files on /data partition - it did not mount for some reason. I was able to access shell from Recovery, but it did not helped me too much - /data partition was entirely broken.
I realized that Samsung uses its own filesystem for /data - RFS and I had no tools to work with it - at least did not find them. In such case, I have unpacked one of the older firmwares and found, that it contains files for soome partitions, but not for the /data.
Next steps were fairly simple - go to sammobile.com, download firmwares for my Ace and check, if it contains /data (data.rfs). Eventually found one, flashed it and my phone went back alive.
Don't know if this is best method, but at least it was interesting to investigate

Thnkx for dis info. All d noobs should read dis before flashing d oc kernel.
Sent from GT-S5830 using Grif's Cyanogenmod

domnic79 said:
All d noobs should read dis before flashing d oc kernel.
Click to expand...
Click to collapse
I think, that most of them will read this after the catastrophe...
Regards

SetCPU has a "Safe Mode" flashable zip file
Sent from my GT-S5830 using XDA App

EmoBoiix3 said:
SetCPU has a "Safe Mode" flashable zip file
Click to expand...
Click to collapse
In general, overclocking means that system can work in an undeterministic manner. Especially an overclocked processor can write some garbage to flash - in my case it was /data partition.
Can't belive that any "Safe Mode" could help - if you play with fire, you should be ready for some burns
Regards
Pawel

p.stradowski said:
In general, overclocking means that system can work in an undeterministic manner. Especially an overclocked processor can write some garbage to flash - in my case it was /data partition.
Can't belive that any "Safe Mode" could help - if you play with fire, you should be ready for some burns
Regards
Pawel
Click to expand...
Click to collapse
It reverts the CPU speed back to 787Mhz .
Sent from my GT-S5830 using XDA App

EmoBoiix3 said:
It reverts the CPU speed back to 787Mhz .
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
exactly. it disable/revert the "set on boot" function that cause bootloop

Everyone knows the risks and there are more than enough warning messages floating around highlighting the BLATANT ramifications of over clocking. Call me harsh, but isn't this what we DIDN'T want to see cluttering the forums? Let this be a lesson to anyone else who decides to flash the kernel.
Sent from my GT-S5830 using Tapatalk

well some people need to learn the hard way. some will never learn until the day their devices blown to smithereens on their faces.

jimbo.levy said:
Everyone knows the risks and there are more than enough warning messages floating around highlighting the BLATANT ramifications of over clocking. Call me harsh, but isn't this what we DIDN'T want to see cluttering the forums? Let this be a lesson to anyone else who decides to flash the kernel.
Click to expand...
Click to collapse
completely agrees
an0nym0us_ said:
well some people need to learn the hard way. some will never learn until the day their devices blown to smithereens on their faces.
Click to expand...
Click to collapse
yeah i see LOT OF people just bricking devices and then search for solutions.. but i see that many people search Google and see something and do it on device without confirming that it works or not...
in my opinion rom manager seriously should include warning or some mechanism to warn user that there device is not at all supported.. is there any?? just confirming as i haven't installed that ACE KILLER

madman_amit said:
completely agrees
yeah i see LOT OF people just bricking devices and then search for solutions.. but i see that many people search Google and see something and do it on device without confirming that it works or not...
in my opinion rom manager seriously should include warning or some mechanism to warn user that there device is not at all supported.. is there any?? just confirming as i haven't installed that ACE KILLER
Click to expand...
Click to collapse
Rom manager says ace is supperted in cm7 roms. Bt 99% people bv bricked their fones using this app. So even if it shows samsung galaxy ace in d list, dont use it.
Sent from my GT-S5830 using Grif's CyanogenMod
Dont jus say thanks, use d 'Thanks' button. [XDA-RULE]

EmoBoiix3 said:
It reverts the CPU speed back to 787Mhz .
Click to expand...
Click to collapse
It is good option to have such tool handy, but one can understand, that overclocking can hit the phone in more complex way. This was my case - overclocked system damaged partition /data.
My message is that overclocking is dangerous and one should be prepared for any results including bricking.
Comparing this with usual process of installing new firmware, recovery, bootloaders etc, overclocking is far more dangerous because of uncertainity generated by the unstable processor.
Regards

Hello,
I think I also broke my /data
p.stradowski said:
...
Next steps were fairly simple - go to sammobile.com, download firmwares for my Ace and check, if it contains /data (data.rfs). Eventually found one, flashed it and my phone went back alive...
Click to expand...
Click to collapse
I've tried to download many firmwares, but cannot find any containing that precious data.rfs.
Is there some specific version or link you could give me please ?
Thank you so much !

Hi again,
Answering to myself : S5830XWKPO v2.3.3 makes the trick.
Bye

similar bootloop for CM7.2 perhaps with similar solution?
Hi,
I am having a similar bootloop problem for CM7.2.
I have Odin installed, but I don't think sammobile firmware page currently stocks the appropriate files. Clicking on the links for the files just links to mediafire, invalid or deleted files. for some of those files.
I do however have some backups I made with nandroid which may be incomplete: These are all of the files generated.
cache.rfs.tar data.rfs.tar nandroid.md5 system.rfs.tar
I also just installed Android Developer Tools for Linux.
Can I use any of these things especially data.rfs.tar in Odin to fix my phone.
I just interested in how you loaded the data.rfs.tar into Odin, because I have read it is very sensitive to file order, and Odin is a good canditate mechanism for bricking my phone.
I have CW5 installed. My phone can go into download mode, and I can see corresponding COM ports in Odin.
Sorry I have not posted on the most appropriate topic, but I am interested in the way you solved your problem with logcat, and then flashing data.rfs.tar
BTW: I also found this package somewhere: I think its the whole gingerbread stock rom. Simply adding the zip to the SDCARD and trying to install from SDCARD, after clearing cache etc. wont do anything. Yet on the other hand none of these files are any good for Odin either.
~/Desktop/android_device_samsung_cooper-gingerbread$ ls
AndroidBoard.mk BoardConfig.mk init.gt-s5830.rc liblight recovery sec_key.kl ueventd.gt-s5830.rc
Android.mk camerashutter kernel overlay recovery.fstab sec_touchscreen.kl unzip-files.sh
AndroidProducts.mk device_cooper.mk libaudio prebuilt recovery_kernel setup_fs UsbController.cpp
bdaddr_read egl.cfg libcopybit qwerty.kl recovery.rc setup-makefiles.sh vendor
bluedroid extract-files.sh libgralloc ReadMe sec_jack.kl system.prop vendorsetup.sh
I wonder if anyone knows the best way to get this format of ginger bread to unzip and expand off the sdcard?
Thanks so much for any help, It would be much appreciated (even if the help is just the suggestion that I should repost under a different forum topic).
p.stradowski said:
Some weeks ago, I decided to overclock my Ace: CyanogenMod-7.1.0-RC1-Cooper-KANG plus ClockWorkMod4. Got the overclocking kernel from ketut.kumajaya and started to play with frequencies while watching CSI Las Vegas.
In general, it's stupid idea to multitask things like this. In my case, I accidentally ticked checkbox "Set at boot", set the frequency to around 870 MHz and my phone rebooted. I have gone into the bootloop, tried almost everything:
-reinstallation of CyanogenMod
-reinstallation of some other ROM i have found on my disk
-cleaning caches, wiping etc
Without sucess of course
I have decided to check, what exactly happened with my phone, so connected it to PC and started logcat. There was a lot of errors related to files on /data partition - it did not mount for some reason. I was able to access shell from Recovery, but it did not helped me too much - /data partition was entirely broken.
I realized that Samsung uses its own filesystem for /data - RFS and I had no tools to work with it - at least did not find them. In such case, I have unpacked one of the older firmwares and found, that it contains files for soome partitions, but not for the /data.
Next steps were fairly simple - go to sammobile.com, download firmwares for my Ace and check, if it contains /data (data.rfs). Eventually found one, flashed it and my phone went back alive.
Don't know if this is best method, but at least it was interesting to investigate
Click to expand...
Click to collapse

hello! i had your problem with my ace and i could not find a solution at first but after a while i had worked out a solution. i find this one a bit easier to follow for noobs NOT guaranteed to work. also you will lose ALL DATA
1.flash stock through odin (2.3.5 reccomended)
2.wipe/factory reset
3.flash this: https://docs.google.com/file/d/0B-eHBmC1vSXGc1BRSWlqRW1Nc28/edit - this will root your device
4.afterwards flash this: https://docs.google.com/file/d/0B-eHBmC1vSXGeWNBOXhCVjZTRkk/edit - this will give you cwm
5.turn off then boot into recovery again.
6.wipe data/factory reset, cache, dalvik cache, mount and format system
7. install this ROM: https://docs.google.com/file/d/0B-eHBmC1vSXGVU1TSjdpUlF4MDg/edit
8.boot up your phone. it will take about 5 minutes to boot again, and you will have xperiatized rom. you can now flash whatever rom you like or go back to stock. i hope i have helped you and if i have please hit thanks

Hi,
Thanks for your help and interest.There is no chance that that will work in my situation since I have never succeeded in flashing the stock android from the samsung website. In fact, I have never been able to flash anything with Odin at all. I tried uninstalling and reinstalling Samsung drivers. Uninstalling Kies etc, using specific Samsung data cable. No measure I took was able to satisfy the condition that Odin could flash a ROM onto my Samsung gts-5830, which made me sad for a while.
Also thanks for granting permission to share googledocs files. Unfortunately I was unable to download Root.zip from google docs. Due to following error, but given I can't flash stock Android, the downloading the files will not help anyway. (Browser gives error message
###
# corresponding URL for that Root.zip:
# has resulted in too many redirects. Clearing your cookies for this site or allowing third-party cookies may fix the problem. If not, it is possibly # a server configuration issue and not a problem with your computer.
###

Related

[Q] (Partitions Jacked)-Woke up to a bricked phone

I am at a loss, i am at a point where my phone is no longer bound by the laws of logic.
I was running Passion 13.1 ICS
two days ago for some reason i woke up and my phone was asking for a password to decrypt the phone, i though this was weird being that i didnt encrypt the phone.
so i setup ODIN and flashed back to Eugene's Froyo that doesn't brick pre rooted w/re-partition checked.
it passes and reboots after reboot i get
Code:
"E:Cant mount /dev/block/mmcblkop1 (or /dev/block/mmcblk0)
(no such file or directory)
but it will reboot into android
so i booted into android setup adb and copied over the fs tools (Parted, e2fsck, mke2fs, resize2fs tune2fs, and sdparted)
i found that in /dev/block/ the partition files were missing completely so i created them using
Code:
mknod /dev/block/mmcblk0 b 179 0
mknod /dev/block/mmcblk0p1 b 179 1
mknod /dev/block/mmcblk0p2 b 179 2
i can see them there but when i try to partition them using
Code:
parted /dev/block/mmcblk0 mkfs ext2
it returns
Code:
Error: Error opening /dev/block/mmcblk0: No such device or address
so i tried a shot in the dark i tried to write zero's to it
Code:
dd if=/dev/zero of=/dev/block/mmcblk0
it returns
Code:
/dev/block/mmcblk0: cannot open for write: No such device or address
so i rebooted my phone, when it came back up i opened an adb shell and to my surprise the fs tools and the files i created in /dev/block were gone it was like it factory reset it self on reboot.
were i am at now is hardware failure unless the collective minds here can see something that i missed?
i really really REALLY want to save her she has been an awesome phone.
any help would be appreciated
Dude that sucks. You are I think the 3rd or 4th person to have this happen to. I do also believe that most of whom this happened to (at least in our forum) were running Passion (different variants though). In the Cappy threads, it was CM9 or Doc's. Seems it is totally random when it happens, but I am seriously considering going back to something else unless I get another phone.
Might want to check here for a workable solution.
Sorry for your loss.
Instead of the froyo build, you should try 2.1 jfd odin package
Woodrube said:
Dude that sucks. You are I think the 3rd or 4th person to have this happen to. I do also believe that most of whom this happened to (at least in our forum) were running Passion (different variants though). In the Cappy threads, it was CM9 or Doc's. Seems it is totally random when it happens, but I am seriously considering going back to something else unless I get another phone.
Might want to check here for a workable solution.
Sorry for your loss.
Click to expand...
Click to collapse
I was thinking about doing this, but wouldn't it make my phone incredibly slow because of the sd latency?
Dougfresh said:
Instead of the froyo build, you should try 2.1 jfd odin package
Click to expand...
Click to collapse
i tried looking for this but i cant find it do you have a link or a copy of the files?
I'm sure it will slow down but it should boot up and you can load another ROM on there. You do lose your entire internal since it is essentially swapped out for the external. Can't hurt to try with a higher class card maybe.
It seems this is happening to everyone running ICS Passion.
Ya but on the Cappy threads it is happening to people on CM9 and Doc's too.
So I am wondering if anyone on AOKP builds are getting these. I posted in the other two threads about this (the one that you were helping that guy yesterday with and the other one) to see what ROMs/kernels they were running, JIC.
Might be a problem with the port of the AOSP code since it is essentially from NS and GNex, both Sammy products though. Anyone in your NS fora reporting this problem?
Nope, nobody. And I just flashed from 2.3.6 to 4.0.4 2 days ago
I flashed GBBOOT-T959UVJFD in an effort to fix my problem, but its just stuck in a boot loop now. is there a chance that the actual physical memory is damaged?
Chances are your internal is completely locked up and without the encryption "key" you won't be able to use it. Since you know ADB, you still might be able to pull some stuff off it and mount to your PC.
Looks to be that you may need to repartition your external in the thread I posted above.
What Bootloader were you on before this all started?
The file I sent you had GB bootloaders included. So to get into recovery Vol- and Power. To get into download Vol+ and Power.
Woodrube said:
Chances are your internal is completely locked up and without the encryption "key" you won't be able to use it. Since you know ADB, you still might be able to pull some stuff off it and mount to your PC.
Looks to be that you may need to repartition your external in the thread I posted above.
What Bootloader were you on before this all started?
The file I sent you had GB bootloaders included. So to get into recovery Vol- and Power. To get into download Vol+ and Power.
Click to expand...
Click to collapse
at this point i don't even care about recovering the internal partition i would like to just format it and start over clean.
It had a GB boot loader on it.
This is what is confusing me, in my mind if a partition is locked and i forget the key or in this case it encrypts itself shouldn't i be able to just fdisk or dd the partition back to cleanliness and format it?
When I installed some of the ICS roms (Cant remember which ones, Too many out now) I remember at the very beginning of the post flash setup screens that I needed to Agree to Googles update rules.
I have read that The galaxy nexus and the Nexus S is getting 4.0.? upgrades re-pushed to their phones as the First update in December had a major battery drain bug in it and was stopped.
I have also read that some members reported that They got a "Welcome to your new Nexus....." e-mails.
Could this be caused by an update being pushed to the phone and sense it is a vibrant and not a nexus it is causing these problems??
Big Dog KMc said:
When I installed some of the ICS roms (Cant remember which ones, Too many out now) I remember at the very beginning of the post flash setup screens that I needed to Agree to Googles update rules.
I have read that The galaxy nexus and the Nexus S is getting 4.0.? upgrades re-pushed to their phones as the First update in December had a major battery drain bug in it and was stopped.
I have also read that some members reported that They got a "Welcome to your new Nexus....." e-mails.
Could this be caused by an update being pushed to the phone and sense it is a vibrant and not a nexus it is causing these problems??
Click to expand...
Click to collapse
I thought the Nexus had ICS already, so i don't think that was what happened. plus i would think it would prompt the user to apply the update or restart the device.
at this point after reading this thread, i think its hardware failure in my case. otherwise why would it clear everything after a reboot?
TheGioDoodlesII said:
Flash the original stock rom , wipe cache and do a factory reset before and after flashing
Hope i helped :beer:
Sent from my GT-S5660 using xda premium
Click to expand...
Click to collapse
I tried that sans the beer LOL i think i am going to need something stronger.
Anythoughts on the SGS 2? HERE
or the NEXUS HERE

[Q] Android Crash on boot and red exclamation mark

Hello,
Last night, I tried to modify the Screen DPI on my tablet ASD Digital MID 162... After the device restart, splash screen not ending... I reset my build.prop to the default value, and make a wipe cache with Adb and instead of write wipe /cache, I write wipe only... And my device don't boot and I can't use adb shell... The error is : "Permission denied (13)"
Someonee can help me ? Please ><
(Sorry for my bad english, I'm french)
How did you modify the DPI exactly?
Through an app?
Editing the build.prop?
Laughing at you while eating Jellybeans
Sounds like a messed up build prop and the device is bricked..
Yes I've modify the DPI in build.prop file...
What can I do for repair the boot ?
One help ?
Gonna have to reflash. You pretty much wiped your device so you will need to reinstall the os
Wayne Tech S-III
I know that, I have to reinstall the OS.. But I don't have recovery mod on my tablet... The only one I have it's an recovery stock (I think, I'm not sure).. I can do "adb ls/", "adb pull and push" , that's all... One idea ?
[I've tried to push a shell in /system/bin in recovery mode, but I've got a error (permission denied), I want to push a shell for execute "flash_image" tools with an new OS .img file for solve the problem ]
I've had similar problems with my myTouch when I've done things it didn't like. Providing that you can boot to the stock recovery that gives you the options to reboot or apply update then your almost saved. Because if that's the case then ya can
copy the custom recovery.zip file over to the root of your sdcard (I used a computer for that as when I killed my phone it wouldn't boot past sock recovery or boot-looping)
rename it to update.zip then boot into stock recovery,
apply the update from sd and your device should, hopefully, temporarily start the custom recovery so that you can
wipe re-flash or restore from backup.
This all assumes that your device has a way for you to access the sdcard without your device.
Hope this helps/use at your own risk
Sent from either my SPH-D700 or myTouch3Gs
I go to make a meditation on this idea... The problem is that I can't do anythings with the "stock recovery", It's just a screen with an open [dead] droid with red exclamation mark, and that's all. Nothing to do when I push one touch like Volume - or +, but when I boot with another key as Power Up, A black screen appeared, and it's all... (I want to show a photo with a screenshot, but I'm a new user, I can't :'( , I've no luck !!!! >< )
SteakFrite said:
I go to make a meditation on this idea... The problem is that I can't do anythings with the "stock recovery", It's just a screen with an open [dead] droid with red exclamation mark, and that's all. Nothing to do when I push one touch like Volume - or +, but when I boot with another key as Power Up, A black screen appeared, and it's all... (I want to show a photo with a screenshot, but I'm a new user, I can't :'( , I've no luck !!!! >< )
Click to expand...
Click to collapse
That is not recovery that is the kernel panic screen. Only option is an Odin install of stock
SteakFrite said:
I go to make a meditation on this idea... The problem is that I can't do anythings with the "stock recovery", It's just a screen with an open [dead] droid with red exclamation mark, and that's all. Nothing to do when I push one touch like Volume - or +, but when I boot with another key as Power Up, A black screen appeared, and it's all... (I want to show a photo with a screenshot, but I'm a new user, I can't :'( , I've no luck !!!! >< )
Click to expand...
Click to collapse
Ok so I read the post about kernel panic screen and agree mostly, however, I've seen the panic screen and gotten past it with a combo of volume + and power button at the same time, it then returns an error message on how recovery wasn't able to be read from its expected source, it then blanks out for a moment and boots the stock recovery, from there I apply the update.zip that I renamed and placed there with a computer, and then everything is good again.
Note: I don't have the specific device you do, or know the method that you usually used to use to boot into recovery.
Usually, its a combo of two or three buttons like on my htc product it's volume up and power button and on my Samsung its volume down and power and camera button. Note: when I do actually get into a custom recovery on my htc the power button then changes to turning the screen off and on instead of selecting things, which made it a hair pulling experience until I figured out that the directional pad on my device was the select button. (Moral of the story, power button sometimes controls the power to the screen, sometimes its used for selecting things, odd but be persistent and try combos because I thought my phone was killed till I hit the power button a second time and the screen came right back on.)
Odin should resolve the issue though for sure if fiddling around with your devices' buttons get to be frustrating, I just figure that any time I touch a computer to re-root my phone I've not done enough trouble shooting.
One other thing you can try is a targeted google search
Eg: 'solved [device name] [issue with device] site:[address of site to search]
So for example when I had a problem with my Samsung I used
'Solved epic 4g bootloop site:xda
Note I had to shorten the site as I'm not allowed just yet to post links but you'll want to include the .com
You can also replace the site: with similar: to search sites that are like xda with similar results.
What's the name and manufacture of your device? I'll see what I can dig up for you.
Sent from either my SPH-D700 or myTouch3Gs
Good ! Thank's youuuuu !! I've can access recovery mod with combo of Volume + and Power... My device is "ASD Digital 162"... Tonight, I go to make an update.zip with an android OS img file... Thank's !!
Where I can find an image file of my Rom ?
This device don't have many popularity on google, and he have no constructor website... Where can I find a ROM or Custom Rom ?
For information, I've one another tablet (Exactely same device) arround of me.. Can I extract the ROM or a backup that could me restore the Android OS ? I don't want do stupid things with the other tablet also like I do this time...
(I want to precise... On my SdCard, a folder named "nandroid" has apparead , he content kernel file, system .img file, cache .img file, etc etc.., if you have any suggest on what can I do with it )
SteakFrite said:
This device don't have many popularity on google, and he have no constructor website... Where can I find a ROM or Custom Rom ?
Click to expand...
Click to collapse
I'll be seeing what I can dig up in the next day or so. Have you any links to shair; such as the guide(s) you've used?
SteakFrite said:
For information, I've one another tablet (Exactely same device) arround of me.. Can I extract the ROM or a backup that could me restore the Android OS ? I don't want do stupid things with the other tablet also like I do this time...
Click to expand...
Click to collapse
You could try it, though I wouldn't as internal hardware can differ inside identical devices, you could end up 'super' bricking your device which I don't think is a real term it just sounds less scary than 'muten' bricking. The phonomonon can be observed when someone flashes an epic 4g touch rom on to an epic 4g and things are never the same. Not saying that's the case just my perinoa speeking up here.
Actually I think there are guides floting around on how to make and scrub your own custom rom, maybe you could do a full copy of the working device though the usb debug bridge, scrub the user data and dependencies from the copy and push it to the not-yet working device... or you could blase the path allready well troden.
SteakFrite;40339439 said:
(I want to precise... On my SdCard, a folder named "nandroid" has apparead , he content kernel file, system .img file, cache .img file, etc etc.., if you have any suggest on what can I do with it )
Click to expand...
Click to collapse
now when you're going to your sd card are you talking removable sd or internal?
Some devices don't have an external or its inaccessible,
other devices make it confusing by also having a partition on the internall memory labled sdcard which looks a lot like the sd card that can be un mounted and re mounted (I believe it to be confusing because the sdcard is also lables sdcard),
And yet others are really easy to spot because its the only thing labled and removeable as an sdcard
Any who if your talking about viewing your sdcard with prisice then likely what your viewing is the old contents of the card (what ever you had on it before this learning experieance snuck up on you) and I would treat it like pizza from last night's party. Meaning that the backed up apps could be used and there could very well be a good backup in there if you made one in the before time, but I wouldn't force my device to choke down leftovers when I could start anew.
SteakFrite said:
Good ! Thank's youuuuu !! I've can access recovery mod with combo of Volume + and Power... My device is "ASD Digital 162"... Tonight, I go to make an update.zip with an android OS img file... Thank's !!
Click to expand...
Click to collapse
You're Welcome; knew you weren't out of options.
Make sure to reroot from the start of what ever guide you used (as a gard against myself and the decisions I make I always keep my costom recovery flash zip for all my devices in the root of my sdcard and labled as update.zip or whatever the manufacture's recovery software by defaults to looking for. That way I can always reinstall if the device still turns on.) as you'll likely want to flash and mod with furver, I know I always do, keep a clear head and it should all work out.
Sent from either my SPH-D700 or myTouch3Gs using XDA app
"it never hurts to help"
...
It's a external sd card... And the file and folder are lost.
Exist an universal Custom ROM Android 4.2 ? I didn't found any official rom for this tablet...
SteakFrite said:
It's a external sd card... And the file and folder are lost.
Exist an universal Custom ROM Android 4.2 ? I didn't found any official rom for this tablet...
Click to expand...
Click to collapse
Yeah just spent the last hour or so looking for asd mid 162 tablet in google, tried a few modifide search quaries, and such to no avail. Saw your question on a few other boards too. I've a feeling that you've run into the same problem with low popularity and lack of documentation. If you got any other discripters I can use for searching I'll be back on the case after work today
Sent from either my SPH-D700 or myTouch3Gs using XDA app
"it never hurts to help"
S0AndS0 said:
Yeah just spent the last hour or so looking for asd mid 162 tablet in google, tried a few modifide search quaries, and such to no avail. Saw your question on a few other boards too. I've a feeling that you've run into the same problem with low popularity and lack of documentation. If you got any other discripters I can use for searching I'll be back on the case after work today
Sent from either my SPH-D700 or myTouch3Gs using XDA app
"it never hurts to help"
Click to expand...
Click to collapse
On recovery screen, is marked "SDK : MID-A13-Android4.2-V1.0-20130121"...
This tablet is the 9' inch model of ASD Digital 142...
Looks like that's the rom, could try flashing it again, just google the 'a13 9 inch tablet' and you'll find info on allwinner.
Happen to know what the ASD stands for? All I'm getting is autism results. (Which putting the word autism in this thread and adding '[minus sine]autism' might help)
Sent from either my SPH-D700 or myTouch3Gs
I haven't understand...
I don't understand what you say... :/
Can you use easiest word or terms ? (If possible)
Sorry about that.
The first part of last post was discribing a search quary I used to find info on the rom you may be using. Looks like a cross platform compatible rom on the face of it but I'm still looking into it.
The second part of last post was stating that when I search for your devices' model 'asd digital' I'm getting results for human medical problems and not hardware related information. So I put the main word that was triggering that into this thread so that I can then search 'asd digital -autizem' and cut those results automaticly from the google search results.
Still working on this with you, just have split atention with trying to finish my first guide for android/linux dulebooting (unrelated to the issuess that curently plage you but still may be worth a look at when you've a system up and running again.)
At this point doing a restore from a working device's backup like you where saying might be the best bet on reviving the simi-bricked device, but I'll have to do some more reading before I really feel comfortible sugesting that you go though all that.
Now that you where able to boot a recovery screen; have you tried anything to get it back up and running? Such as restoring from a backup created after rooting the first time around?
Sent from either my SPH-D700 or myTouch3Gs using XDA app
"it never hurts to help"
link to guide for Debian Kit I'm working on for you.
https://docs.google.com/document/d/1ssVeIhdBuuy8CtpBP1lWgUkG6fR6oHxP20ToYPPw6zI/edit?usp=sharing

Cannot Copying large files to my Android

Lately while using AOSP Roms (Android 4.2) i am having problems with copying large files ( generally more than 200 MB in size to my ext/int sdcard. however this problem doesn't happen when i go back to Stock android 4.1.2 .
EDIT: While copying large files to AOSP Roms the phone just restarts all of a sudden and copying is obviously halted.
I am not looking for any alternate method for copying files to my phone as i am using adb push/pull to copy files between my PC and my phone.
I thought this might be a problem with my PC OS but when i copying using both windows 7 and ubuntu 13.04 and found that the problem still exists i concluded the problem may be because of rom/kernel. Although i am not still sure of this.
Is anyone else having problem copying large files to their android .. if so has anyone found any practical solution for this bug/error ?
P.S. dont suggest any apps for copying files as it defeats the basic purpose of this post ! Also I always Google and i post a question here only if im not getting a satisfactory answer.
am i ignored because no one knows a solution or is it just me having this issue ?
MoonBlade said:
am i ignored because no one knows a solution or is it just me having this issue ?
Click to expand...
Click to collapse
Ignored this is a forum not a service centre if someone has an answer and crucially are online and read your post .
You are breaking the rules by bumping .
jje
JJEgan said:
Ignored this is a forum not a service centre if someone has an answer and crucially are online and read your post .
You are breaking the rules by bumping .
jje
Click to expand...
Click to collapse
i thought this was a Q&A forum not a Q only forum !
And didnt mean it as a bump. I was just curious to know if anyone else was facing the same problem.
If only i am facing the problem then i can know it was me who did something wrong with flashing etc.
MB
The rules you signed up to .
5. Post a message only once.
As a large forum we don't need unnecessary clutter, You're free to edit your message as you like, so if you do not receive an answer revisit your message and see if you can describe your problem better. Not everyone is online at the same time, it might take a while before you receive an answer.
MoonBlade said:
i thought this was a Q&A forum not a Q only forum !
And didnt mean it as a bump. I was just curious to know if anyone else was facing the same problem.
If only i am facing the problem then i can know it was me who did something wrong with flashing etc.
MB
Click to expand...
Click to collapse
No, no, no. You've got it all wrong. While there is a Q&A section. We are NOT a support forum, although, people think it is and lately, that's what its been. This is a developers forum. We are here to share, use, and talk with others that share the same phone(s) as us. While the senior members who read, experience, and know stuff, provide answers to users who don't do anything for them self's. We're not a support forum. And no I am not flaming you. I am explaining how things are.
Sent from my GT-I9300 using xda premium
Do you get an error while copying large files? Does it happen with specific file types? Does it happen when trying to copy to any location inside your phone or specific addresses?
Sorry about earlier. It wasn't meant to hurtful. Just informative. And I don't use AOSP Roms. But I don't think they mount the SD cards (int/ext) using the standard MTP protocol that stock uses. So I don't see why there'd be any problem. Is the cable the stock cable? What's the card formatted to?
Sent from my GT-I9300 using xda premium
dxppxd said:
Do you get an error while copying large files? Does it happen with specific file types? Does it happen when trying to copy to any location inside your phone or specific addresses?[/QUOTE
Fix permissions in recovery mode. If that doesn't help, relfash the rom with full wipe
Click to expand...
Click to collapse
dxppxd said:
Do you get an error while copying large files? Does it happen with specific file types? Does it happen when trying to copy to any location inside your phone or specific addresses?
Click to expand...
Click to collapse
One thing i forgot to mention in OP. When i copy the large file the phone just restarts all of a sudden and this stops the copying. but when i use stock ROM its fine.
No this happens only while i copy to the phone not to any other location.. as i said in OP bot a problem of OS
b-eock said:
Sorry about earlier. It wasn't meant to hurtful. Just informative. And I don't use AOSP Roms. But I don't think they mount the SD cards (int/ext) using the standard MTP protocol that stock uses. So I don't see why there'd be any problem. Is the cable the stock cable? What's the card formatted to?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
the problem is not with the cable and yes its stock cable. and i didnt format the card neither external nor internal. problem arises only in aosp roms. and as i said in op there is no problem while adb pushing the large files.
7wajahat7 said:
Fix permissions in recovery mode. If that doesn't help, relfash the rom with full wipe
Click to expand...
Click to collapse
I did try fix permissions and i always do fullwipe before installing/updating any ROM. Still no success.
MoonBlade said:
Lately while using AOSP Roms (Android 4.2) i am having problems with copying large files ( generally more than 200 MB in size to my ext/int sdcard. however this problem doesn't happen when i go back to Stock android 4.1.2 .
EDIT: While copying large files to AOSP Roms the phone just restarts all of a sudden and copying is obviously halted.
I am not looking for any alternate method for copying files to my phone as i am using adb push/pull to copy files between my PC and my phone.
I thought this might be a problem with my PC OS but when i copying using both windows 7 and ubuntu 13.04 and found that the problem still exists i concluded the problem may be because of rom/kernel. Although i am not still sure of this.
Is anyone else having problem copying large files to their android .. if so has anyone found any practical solution for this bug/error ?
P.S. dont suggest any apps for copying files as it defeats the basic purpose of this post ! Also I always Google and i post a question here only if im not getting a satisfactory answer.
Click to expand...
Click to collapse
You might have found a bug in either AOSP / CM ROMs and/or kernels.
Other things you might need to test in order to make that very, very clear:
- does it always happen on BOTH internal and external ?
- from what you say it seems to never happen on stock - have you tested with stock ROM + Siyah kernel? CM/AOSP ROM + Siyah kernel?
- just to completely eliminate the issue of bad eMMC and/or any MTP problems - can you try (from all types of ROM, and using an USB cable known to be perfect) with the external SD mounted using not normal MTP but instead UMS (there is an easyUMS app for that, it can be a little tricky sometimes since you might need to restart without any USB cable between modes)?
xclub_101 said:
You might have found a bug in either AOSP / CM ROMs and/or kernels.
Other things you might need to test in order to make that very, very clear:
- does it always happen on BOTH internal and external ?
- from what you say it seems to never happen on stock - have you tested with stock ROM + Siyah kernel? CM/AOSP ROM + Siyah kernel?
- just to completely eliminate the issue of bad eMMC and/or any MTP problems - can you try (from all types of ROM, and using an USB cable known to be perfect) with the external SD mounted using not normal MTP but instead UMS (there is an easyUMS app for that, it can be a little tricky sometimes since you might need to restart without any USB cable between modes)?
Click to expand...
Click to collapse
yes it happens on both int/ext sd card its mentioned in OP
Yes it hasn't happened on Stock. I have tried using Googy max as well as Devil Kernel latest versions
i tried mounting as UMS still the problem exists
MoonBlade said:
...
Yes it hasn't happened on Stock. I have tried using Googy max as well as Devil Kernel latest versions
...
Click to expand...
Click to collapse
You mean the problem exists with Googy Max but not with stock? I would still try once more with Siyah 1.9.1 but that is really, really weird - since Siyah and Googy Max are very much Samsung sources recompiled (with two different compilers in the above case). The only other logical explanation that I can somehow think of would be that you somehow get different buffers in the kernel and then you hit some sort of timeout, but that sounds a little far-fetched.
xclub_101 said:
You mean the problem exists with Googy Max but not with stock? I would still try once more with Siyah 1.9.1 but that is really, really weird - since Siyah and Googy Max are very much Samsung sources recompiled (with two different compilers in the above case). The only other logical explanation that I can somehow think of would be that you somehow get different buffers in the kernel and then you hit some sort of timeout, but that sounds a little far-fetched.
Click to expand...
Click to collapse
Solved..
I tried UMS mounting on Windows 7 instead of Linux and problem was partially solved ( i got an error while copying a 400mb file but phone did not reboot this time). i am satisfied with the current progress.
Thanks for helping..

[Q] Trouble getting custom rom on 5839i

Hi all,
After spending many hours trawling the internet, and especially this forum I still am having problems getting ANY custom rom I've tried booting on this phone
I know it's old, but it's just a phone I had lying around and want to use it as a small tablet for my 6yo daughter.
I can flash any "stock" rom I've found with odin, but when flashing using an install from an SD card through CWM, it just hangs on the Samsung bootscreen.
CWM installs as the default recovery console, so something is going on the phone, but it won't boot to android.
Oh I'm also using a 5830I rom, but my research has shown this is basically the same phone?
I've used CM7 and tried lots of other custom roms with the same outcome - please can anyone help!?
My daughter is dying to use her new games machine, but the stock rom is sooooo laggy and slow it's no good at all!
Thanks in advance.
@macsbig, "About device" information from settings of your device please < home+power button for screenshots > or kindly state the full details here.
Your original CSC/PDA/MODEM parts of your device <Dial *#1234# >
Your Region /Country/ carrier you are staying please.
Thanks for the reply ehsanotaku!
PDA : S5830iXXLA4
PHONE : S5830iXXLA2
CSC : S5830iOXXLA2
I'm in the uk. This is not the original rom (that got stuck in a bootlock) and the only way to get the 'phone working again was to flash with a stock rom from the internet.
The original rom was from "Three".
During my various attempts at flashing a rom I have ticked the "re-partition" box and tried both "cooperve_0623.pit" and totoro_0623.pit
I've flashed my P5110 tablet, and a Galaxy S1 for my son with no problems - odd!
@macsbig, How come you are ended up with outdated ( 2012 ) s5830i in the first place ? Any particular problems with your s5839i original firmware ( do you know your original CSC/PDA/MODEM parts ) ? Are you absolutely sure this is not re-branded version ( "About Device" info of the original phone would be nice to see though ) Did you take any Nandroid back up of all of the original partitions of your s5839i through temporary CWM zip file ( files will be stored inside your Clockworkmod directory inside the root of the SD card )
Do you still have access to Recovery stock e3 console and Download mode ?
Another important subject in need of clarification are ".pit" files ( partition table info ) and Re-partition option. Playing around with wrong .pit file such as totoro and incorrect usage of Re-partition will lead into hard bricking of your device .
Since you already did modify partition table couple of time partially without success , I would suggest the following process :
1. Download one of the newest non wipe xxx.tar.md5 s5830i firmware from here < It is free, but registration is required > Probably 2013 xxMD1 is the right one for our experiment.
2. Make your wipe flash able zip package through splitfus2 tutorial provided here, my comment @ post 9 or simply you may use European/Russian pre-made package from here , your choice though ( I would advise the first method , but the latter also will work ) .
3.Get the following files:
3.1 - Odin3.v3.07.Cooperve.exe from either places would be fine : 1 , or any sticky post in general/development section will do ( correct cooperVe .pit file will be resided inside the package )
3.2- Get the Temp-CWM 5.0.2.6 or 5.0.2.8 zip file from here or here < put the zip file inside the root of your SD card for flashing later >
3.3- Boot loader <DefaultCalDataWithBoot_S5830iXXLB1_REV00.tar.rar from post#27 , my attachment .
3.4 - SLIM_CM7.2_Cooperve #4 Rom < put it inside the root of SD card >
3.5- This kernel is also goes into Root of SD card for later usage .
3.6- EXT4 Formatter Tool , into the root of SD card again.
4- Now , if you don't have proper drivers installed inside your Windows PC , you can get then form here .
Ok, assuming you have at least access to Download mode , provided the combo keys work (pressing Vol(+) + Vol(-) + Power Keys) Go there according to manual :
-Power off your Phone.
-Get into "Download mode" by pressing Vol(+) + Vol(-) + Power Keys.
-press volume up
-Open Odin3.v3.07.Cooperve.exe
-Connect your phone to PC via USB cable.
-Make sure that your phone is detected in "ID:COM" area.
- Put your wipe PDA/CSC/MODEM/ boot loader/pit files into their proper places , Re-partition is ticked , Factory reset and reboot selected by default >> push the START !
- DO NOT disconnected nor disturb the flashing Nand process , until the process being terminated . Now you must be out of boot loop .
For completing our partition conversion and also put some cm7.2 custom Rom into the test at the same time , do the following :
- Boot into stock e3 recovery >> wipe data and flash your Temp CWM
- CWM > wipe data > wipe cache > wipe Dalvik cache
- Flash the EXT4 Formatter tool, so whole system will be converted to EXT4. (Stock filesystem is RFS).
- Flash kernel_CM7_v4.0_cooperVe .
- When the Kernel is installed, go to the advanced menu --> "reboot recovery" (this will reboot the device, thus you will be directed into your new CWM built-in, which is implanted inside Kernel ).
- Wipe data, cache and Dalvik
- Go to "mounts and storage", and make sure /system partition is mounted (will show -unmounted ; it is like ON/OFF switch)
- Main menu > "Install zip from SD Card" > choose "zip from SD card" and install the ROM, you have already got inside your SD <SLIM_CM7.2_Cooperve #4>
- Reboot
waiting for some good news ............
It's a long story, but here goes!
I had a couple of old phones we no longer use hanging around the house, so I thought it would be good to let my (young) children use them as simple games playing deivices. It doesn't matter too much if the phone is dropped and damaged etc, as I probrably wont use them for anything else as we have new phones.
Within a couple of days - and I'm not sure what happened, my daughters phone was stuck in a boot loop (samsung and "Three" logos repeatedly). Having no experiance of "unbricking" phones I immediately reached for google, and set out on my quest to sort out her phone for her (as we had lots, and lots of tears over her new toy!). The phone has no sim card in and is on wifi for installs etc.
After searching I found a rom that would load on and make the phone good again, this one: S5839iXXLK2_S5839iH3GLC2_S5839iNELK1_HOME.tar.md5
This worked ok, but was very laggy, and irritated me imensely as I was sorting games etc for her, so I decided to to instal a custom rom. After 3 roms refused to load (just stuck on the "Samaung GALAXY Ace GT-S5839i boot screen) I decided to try flashing it to 5380i firmware and Pit file - as nearly all custom roms for the ace seem to be for the 5830i variant - I wondered if this would sort my problem!
It didn't! But now it has become a challenge, and a chance to learn something of Android and how it works - as I said in my last post I have successfully flashed an I9000 with carbon and my P5110 with CM11, I learnt how to do this by what I've learnt from reaserching about this phone, so it has been a worthwhile excercise!
But back to the point. No I don't have any back-ups of the original phone, I neither had the knowlege, or know how of having or needing to do this - it's only now I'm finding my phones/tablets so facinanting!!
Yes I am now back to the stock (e3) recovery, which I can get into.
Many thanks for your help so far - I will try your ideas and repeort back!
@macsbig, Yes do that please and after resolving your initial problems , here is a confirmed list of the games compatible with your GPU/CPU of your child's legacy device . Also you can use chainfire 3d only under stock firmware/rooted phone for the games required plugin(s) and app being activate for proper almost lag free experience . You may read theses links as well for some insight : 1 , 2 .
The ext4 formatter link doesnt work my friend
macsbig said:
The ext4 formatter link doesnt work my friend
Click to expand...
Click to collapse
Just cross-linking it ( wasn't my links to begin though ^:^ )
Attached the flash able zip file to the post body .
I will try you solution(s) later. Working late today! But wow this seems quite complicated! ! Hehe.
Sent from my GT-I9300 using XDA Free mobile app
macsbig said:
I will try you solution(s) later. Working late today! But wow this seems quite complicated! ! Hehe.
Click to expand...
Click to collapse
Well , researching a new area of knowledge ( in this case customization/rooting/bricking/moding and many more technical things inside XDA) can be a bit overwhelming.I do agree with you that the sheer wealth of material means that it can be overwhelming, but more you read and spend time @ XDA, more you will get the hang of the material presented here .
Nevertheless we are here to share/help all of the possible/working solution mate. Just ask anything you can not understand very well . I will try to depict even more detailed walk-through guidelines.
Regards
Right, I now have a custom rom on the 5839i!
I didn't have too much time last night, so what I did was flashed the phone with Odin, using the bootloader and pit file you specified. I then rebooted into the stock revovery, wiped the Data, Cache and Delvic partitions, then booted into CMW 5.0.2.6 and flashed the EXT4 Formatter tool. I then installed the kernel you specified
After that I rebooted into the CMW recovery from the new kernel and followed your instructions - and Voila! It booted into the slim rom you linked me too
Just to test it wasn't a fluke, I then installed CM9, and that went on fine too - with just the normal steps.
I now have to decide after your other advice, whether I go for a stock rom, and try and get rid of the lag, use chainfire 3D etc or go for a custom mod!
Is there a similar app for modded roms's like chainfire 3D to help game perfomance on this limited hardware? I'd really prefer to use a modded rom and build up from there, but as I stated earlier in the post, this will be used only for games and listening to music from youtube, so i'll maybe have to research some more to find out what would work the best.
Many, many thanks for your help, I've learnt alot during this project!!
Oh as a bit of an aside, got a bit worried when downloading some of the links, some of the "download managers" were causing my anti-virus and anti-malware software to give me warnings!
Thanks again
@macsbig, Glad everything worked out for you mate . To address your concerns I must say that I did not come across any working solution for accelerating your GPU with reduction [email protected] custom Roms unfortunately ( only works on stock fw/rooted device) .
For CM9 beta Rom available @ development sub forum , this is an unstable Rom with some serious problems , because of ICS bugs an other things( Read this troubleshooting session and links provided there ).
For malware's concerns they are mostly false positives . Even virus total wold miss lead you in many cases, due to nature of advertising agent implanted inside some of the app inside system directory of custom Roms . You can simply replace the app in question with another one free of adverts. However they are harmless mostly. Please read this discussion (post #472-475) (post#291-298) between me and moderators team for more information about advertisement policies. Basically we have a very good control over materials presented here , thanks to mod teams .
Hope I did help you with your quest
My apologies, when I said that I was getting anti-virus/malware warnings, that was aimed at when I was trying to download the files on "mediafire(?)" and such like. They want you to install a stupid downloader etc., which then installs some crap on your pc.
Had it when downloading splitfus2 if I recall correctly (it was late 12am!).
That's why in the end I decided to use a pre - split (is that what you mean by wiped?) rom in the end.
I'm gonna have a play with the 'phone again later when I finish work.

Softbrick: Can't format system partition

Hi all,
to make it plain and short: I messed up.
I have a GT-S5830i which I unrooted according to the Sticky Note in the forum, installed CWM Recovery and then 'installed from ZIP' a CM9_cooperve_Beta_05.zip that I found in one of the posts in the forum. The installation went on without error message but since then the phone does not make it beyond the initial screen "Samsung Galaxy Ace GT-S5830i". I can start recovery mode and Download mode. In reovery mode I can format cache, data, sdcard, sd-ext but *not* system. Error Message: "E: format_volume: make_ext4fs failed on /dev/block/st19"
I have tried already several methods according to the forum, e.g.
1) 'install from ZIP' older Cyanogenmod
2) the tool ext4_formatter.zip
3) re-flash with ODIN with several tar-ROMs, all failed. Odin finds the phone (since I start Odin as Admin now), but after I hit 'start' it tries to establish a connection to the phone and ends after a while with 'Failed'
I'm basically lost now, don't know what else to do. Any advise is appreciated (it's my mom's phone, she is getting impatient )
Thx, cheers!
Xala
Hi @xalarsk , So you can't format your /system partition , which is required for installation of your rom ,, you need to try this method from here mate . Follow my instruction from the line @post#4 :"1. Download one of the newest ,,," to the end of the post and please do not use CM9 beta , because it is unstable and will wreak havoc with your system eventually . ( either cm7 or cm11 is the place you should go for CyanogenMod experience for cooperVe device ).
If you fail at any level please give us your logcat ( error massage ) for better support for your Odin process you mentioned .
Cygwin not working
Hi @ehsanotaku,
thank you for your quick reply, it's appreciated!
Unfortunately I couldn't get cygwin to install all necessary packets. The ZIP-test always failed. I have a Linux system running (Linux Mint 17) though, and hope that might help. In the meantime I tried to download the already split packages as described in another of your forum posts, but the website provides only exe-files instead of zip-files. Is there another location to download them?
#UPDATE: It seems there is a SplitFUS2 version for linux somewhere but couldn't find links to download. Anybody can help? I'll also PM Doky73
Cheers, Holger
xalarsk said:
Hi @ehsanotaku,
thank you for your quick reply, it's appreciated!
Unfortunately I couldn't get cygwin to install all necessary packets. The ZIP-test always failed. I have a Linux system running (Linux Mint 17) though, and hope that might help. In the meantime I tried to download the already split packages as described in another of your forum posts, but the website provides only exe-files instead of zip-files. Is there another location to download them?
#UPDATE: It seems there is a SplitFUS2 version for linux somewhere but couldn't find links to download. Anybody can help? I'll also PM Doky73
Cheers, Holger
Click to expand...
Click to collapse
Cygwin was meant for windows platform to get the native Linux environment/command line you already got there . You can create a virtual instance of the windows 7 inside virtualbox or any kind of apps you are preferring such as Vmware/Parallel etc etc to get the job done .
Splitfus2 only supports windows platform as far as i know mate,,, either vitalization as i said or the pre-made zip package ( which is clearly not .exe file ,, push the download now and get yourself a descent downland manager,, tested and zip packaged delivered ) from here is the feasible approach for your problem .
Ok, had all the files ready, just the Boot loader <DefaultCalDataWithBoot_S5830iXXLB1_REV00.tar.rar seems to be broken. I downloaded the link provided in your post #8 several times with several download managers, also uses 7-zip and several online unrar services..result always the same: The archive is broken. Is that possible? Would you mind to check yourself?
xalarsk said:
Ok, had all the files ready, just the Boot loader <DefaultCalDataWithBoot_S5830iXXLB1_REV00.tar.rar seems to be broken. I downloaded the link provided in your post #8 several times with several download managers, also uses 7-zip and several online unrar services..result always the same: The archive is broken. Is that possible? Would you mind to check yourself?
Click to expand...
Click to collapse
Another fellow had similar issue with my attachment that was corrected here @ post#27
Unbricked, SD card not recognized
Update: Phone has been unbricked, many thanks for that!
Currently I have still issues with the external SD card, which also holds the ZIP files. Phone won't recognize it, not even format it properly. Still working on that.
Cheers, Xala
xalarsk said:
Update: Phone has been unbricked, many thanks for that!
Currently I have still issues with the external SD card, which also holds the ZIP files. Phone won't recognize it, not even format it properly. Still working on that.
Cheers, Xala
Click to expand...
Click to collapse
Mostly this happened because of the bug inside CM9 beta you used . Study this topic mate i troubleshooted while ago for a sample of the symptoms external SD card would show after unstable ICS usage .
Also as an alternative to the method i instructed there , you can format/Re-partition your SD card by putting it inside card reader and using app such as free MiniTool Partition Wizard "Gparted" tool for Linux users Or "iPartiton" for Mac users etc etc ,, to get the job done . You can find several tutorials inside XDA for this matter mate.
Phone works with CM7.2, can I upgrade to CM9?
Hi again,
first of all, props to @ehsanotaku, I will hit the 'Thanks' buttons.
Now, this is a bit beyond the topic, but I'd like to ask anyway for recommendations of CM9 roms. The one I picked from a post inside this forum bricked my phone and made me start this thread, I don't want to go down this road again. So I'd be glad for any recommendation of a stable ROM that will put my phone beyond Android 4.0.
Cheers again,
Xala
So i have a similar issue. I used to have CM11 installed, but i figured thats too slow for me. Then i went back to stock rom (XXMJ2) which works fine. But now i have a problem.
Everytime i want to flash a stock based or cm7 based rom on my phone, it gets messed up. Today i wanted to flash this
http://forum.xda-developers.com/galaxy-ace/s5830i-develop/cm-7-2-kitkat-smart-r2-t3075267
i naturally downloaded clockwork mod recovery (5.0.2.6) and tried to flash it. Flashing was done pretty quickly (10 seconds or so) and when i rebooted, i obviously got stuck at sammy logo. Now booting back to the recovery (first e3 then cwm) i got bunch of error about partritions not being able to be mounted (happens the same if i want to manually mout them or format them)...
So, what to do ?
I have a suspicion, that flashing CM11 and the latest cwm recovery for it somehow messed up partritions.
hojnikb said:
So i have a similar issue. I used to have CM11 installed, but i figured thats too slow for me. Then i went back to stock rom (XXMJ2) which works fine. But now i have a problem.
Everytime i want to flash a stock based or cm7 based rom on my phone, it gets messed up. Today i wanted to flash this
http://forum.xda-developers.com/galaxy-ace/s5830i-develop/cm-7-2-kitkat-smart-r2-t3075267
i naturally downloaded clockwork mod recovery (5.0.2.6) and tried to flash it. Flashing was done pretty quickly (10 seconds or so) and when i rebooted, i obviously got stuck at sammy logo. Now booting back to the recovery (first e3 then cwm) i got bunch of error about partritions not being able to be mounted (happens the same if i want to manually mout them or format them)...
So, what to do ?
I have a suspicion, that flashing CM11 and the latest cwm recovery for it somehow messed up partritions.
Click to expand...
Click to collapse
ok not going to excruciating details of symptoms and explaining all of your errors for now just please read my advice @ post2 of this topic and follow the procedures accordingly and finished it with formatter tools and cm7 instructions you will find there ., after that you can install Kitkat Smart R2 like you are coming from another CM7 build instruction . btw some problem regarding super user privileges and play store 492-498 infamous bug was reported for this fairly new development .

Categories

Resources