[SOLVED] SAMSUNG Galaxy Ace s5830 not working after using CWM 6.0.4.6 & ROM Manager

[SlimRock]

Hi Everyone ,

As the title states, my problem is that today I was trying to update my SAMSUNG Galaxy Ace S5830 to Android 4.4.2 KitKat with CyanogenMod 11 ROM using the method http://www.ibtimes.c...install-1430916 , After downloading the Custom CWM, ROM & copy pasting the said zip files to the SD card, tried the CWM in Recovery mode but it didn't worked due to "not a valid update zip" error, Idk whether it was due to either my phone was not rooted or something else. So then went ahead with rooting my phone using SuperOneClick v2.3.3 and renamed the CWM file "ClockworkMod Recovery 6.0.4.6" to update.zip, Voila this time CWM was installed. While performing this step, I have not cleared the cache and not deleted the data but after this Recovery mode stopped working though phone was working without any issues. So I thought the issue might be due to some CWM error & then downloaded & installed the ROM Manager app from the Google play link : https://play.google....utta.rommanager and selected the option Reboot into recovery and since then display is stalled at SAMSUNG LOGO see in the pic : http://i.imgur.com/4k9k5ku.jpg and now I am unable to use the handset.

I did tried the workaround given in this link http://www.droidview...830-using-odin/ with the odin v4.42 but Windows was unable to detect the USB device, although I have installed the latest SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.33.0 Drivers. These are the Windows error screenshots : http://prntscr.com/2s3we4, http://prntscr.com/2s40ni, & after Uninstalling the USB drivers nothing is changed http://prntscr.com/2s40ur, http://prntscr.com/2s41pn

That being said, any help will be highly appreciated.

Edit Note : Topic Title Changed to Solved! :)

Edited February 14, 2014 by slimrock

[PrEzi]

Hi,

I think you just have blown your recovery partition (where receovery is located).

First of all -- if you want KitKat you NEED to have CWM Version 6.0.4.5+

The problem you've had was that you cannot simply "update" from stock recovery to any CMW like you did. You need to have a version with kernel that is compatible with your phone (or else you will "fry" your recovery like you just did)

But let's focus first on recovering your phone from a possible bad flash / bootloop.

Heads up -- Samsung phones are really really hard to brick ;)

I would STRONGLY advise you to use only XDA as Source... This is one of the most known developer sites for Android Phones and is reliable.

Follow this procedure to flash newest STOCK ROM & the old CWM (C. Flashing the newest firmware and E. Flash Custom Recovery, ignore the requirement to install KIES -- never did and have already flashed virtually hundreds of Android phones)

http://forum.xda-developers.com/showthread.php?t=1034145

You NEED to have the proper drivers for odin to work -- you might need to force a different driver (from the list) when the phone is connected and in Download mode.

Just google for "Universal ADB driver" (as I've said - you might need to force the installation of the driver via device manager).

Either way - once the proper driver is there and you open up Odin it should display "Added" message. You can also install full-blown SDK Tools & Platform-tools from Android SDK t-- this will also install the drivers, but you just need the small pack)

Then you can move on with the procedure to re-flash a Stock rom.

Afterwards head here to DL latest CWM 6.0.4.6 that is KitKat compatible :

http://forum.xda-developers.com/showthread.php?t=2583845

You can flash/upgrade to this new CMW from recovery once you have older CWM. Don't do it from stock recovery !

Here are some guides and tutorials :

http://forum.xda-developers.com/showthread.php?t=2188679

and I strongly recommend against CM11 which are unstable for the first Galaxy Aces. BUT if you really want then you might try this one :

http://forum.xda-developers.com/showthread.php?t=2587481

And a stable CM10.2 is here (recommended) :

http://forum.xda-developers.com/showthread.php?t=2635011

or this one

http://forum.xda-developers.com/showthread.php?t=2442024

And once again -- I strongy advise you to head up to XDA, read read read, then read a little bit more, afterwards think for a while and if you still don't know the answer (of course you have searched through the XDA forums ;) ) -- as last resort - ask ;)

Here is a nice place for any technology/IT-related things but the Android gurus are there ;)

[mara-]

Hm, I had same drivers problem with some Prestigio tablet, cheap Chinese copy. Anyway, my solution was to turn on the tablet, wait a little, then turn it off and go to download mode. If I would termite download mode and try to go to it again, without first trying to start the tablet normally, I would get the same error.

[clubhouse]

You could give this hard reset a try,,,,,,

1. Turn off the phone. Remove battery and wait 20 seconds. Replace battery.
2. Press and hold Volume up + Home (center button) + Power button at the same time.
3. When first screen shows up do not release buttons. When second "Samsung Galaxy Ace" will shows up do not release buttons. Keep pressing buttons until you get to recovery menu.
4. Select "wipe data/factory reset"
5. Select "Yes -- delete all user data"
* Allow several minutes for the factory data reset process to complete.
6. Select "reboot system now"
* Allow several minutes for the reboot process to complete.

If that fails, you have been given excellent advice by prEzi....I have the same model and xda is a superb site for s5830 roms and advice....Don't worry you will fix your phone ....It is not bricked.

Edited February 13, 2014 by clubhouse

[PrEzi]

You could give this hard reset a try,,,,,,

1. Turn off the phone. Remove battery and wait 20 seconds. Replace battery.

2. Press and hold Volume up + Home (center button) + Power button at the same time.

3. When first screen shows up do not release buttons. When second "Samsung Galaxy Ace" will shows up do not release buttons. Keep pressing buttons until you get to recovery menu.

4. Select "wipe data/factory reset"

5. Select "Yes -- delete all user data"

* Allow several minutes for the factory data reset process to complete.

6. Select "reboot system now"

* Allow several minutes for the reboot process to complete.

If that fails, you have been given excellent advice by prEzi....I have the same model and xda is a superb site for s5830 roms and advice....Don't worry you will fix your phone ....It is not bricked.

HE CANNOT access the recovery and is stuck in a bootloop ! He cannot do that what you are writing of... He needs to reflash the ROM+Recovery from Odin -- this is the only thing man can do atm. (And believe me - I know what I am talking about ;) )

Edited February 13, 2014 by PrEzi

[clubhouse]

You could give this hard reset a try,,,,,,

1. Turn off the phone. Remove battery and wait 20 seconds. Replace battery.

2. Press and hold Volume up + Home (center button) + Power button at the same time.

3. When first screen shows up do not release buttons. When second "Samsung Galaxy Ace" will shows up do not release buttons. Keep pressing buttons until you get to recovery menu.

4. Select "wipe data/factory reset"

5. Select "Yes -- delete all user data"

* Allow several minutes for the factory data reset process to complete.

6. Select "reboot system now"

* Allow several minutes for the reboot process to complete.

If that fails, you have been given excellent advice by prEzi....I have the same model and xda is a superb site for s5830 roms and advice....Don't worry you will fix your phone ....It is not bricked.

HE CANNOT access the recovery and is stuck in a bootloop ! He cannot do that what you are writing of... He needs to reflash the ROM+Recovery from Odin -- this is the only thing man can do atm. (And believe me - I know what I am talking about ;) )

Have a read here.....

Solutions to Fix Bootloop on Android Devices: Method 1:

http://www.droidviews.com/how-to-recover-when-your-android-device-is-caught-in-bootloop/

[PrEzi]

Hmm....clubhouse --- his recovery is virtually fried.... He has overwritten the recovery partition with an incompatible kernel/recovery.

He cannot access recovery mode at all (stock one is also a recovery)... This link is useless...

Plus he is stuck in a bootloop.

What he needs to do is :

-Flash a Stock ROM (which contains a stock recovery) via ODIN

This will revert all the damage (and will also result in data loss, but it is lost anyway -- maybe from a custom recovery via adb mount // partitions you could save the data, but this is expert level which I won't cover here).

-Flash CWM recovery

-upgrade CWM to newest Version if not already

-recovery-flash any desired pre-rooted ROM (in his case CM10.2/11, first following the procedure and wiping system, data cache dalvik and android secure (factory reset)).

Edited February 13, 2014 by PrEzi

[clubhouse]

I use xda a lot, I've tried different roms posted there, they don't all work....I've been stuck on bootloops as a result, the hard reset has always worked for me, the only time I've used ODIN is to get back to a stock rom because some of the customised roms will only overwrite stock roms.,,,,Don't be to hasty dismissing other peoples suggestions.

And dismissing the advice of a site that is dedicated to Android is ridiculous.

Edited February 13, 2014 by clubhouse

[PrEzi]

I use xda a lot, I've tried different roms posted there, they don't all work....I've been stuck on bootloops as a result, the hard reset has always worked for me, the only time I've used ODIN is to get back to a stock rom because some of the customised roms will only overwrite stock roms.,,,,Don't be to hasty dismissing other peoples suggestions.

And dismissing the advice of a site that is dedicated to Android is ridiculous.

Mate... I dismiss this advice ONLY because his recovery is not working at all...

By flashing Custom ROMs you DON'T touch the recovery partition (cause for some mobiles the recovery is a separate partition -- not the case with a few models where the recovery comes with the ROM-kernel part etc.).

That is all.. and that is why this kind of information provided in the link only spreads FUD and is in fact - useless.

To make the recovery work you need either to :

Flash Stock ROM with stock recovery then --- several ways to install custom recovery (via a signed update.zip, via ROOT-access // ROM Manager / Nandroid Manager, mobile Odin etc.)

or

If you have a separate recovery partition or a matching ROM/kernel version -- you can flash the recovery from Odin directly (but I haven't described it here just to prevent the mess of dis-information like is happening now...)

And just to add --- "not everything is gold that shines" -- even if it is on XDA I still verify it and test. Droidview -- I've hear about this "dedicated to Android site" for the first time in my life (but on the other way -- one of my sources is XDA, second is androidpolice... so I don't need to dig through the rest of internet).

Edited February 13, 2014 by PrEzi

[SlimRock]

Hi,

I think you just have blown your recovery partition (where receovery is located).

First of all -- if you want KitKat you NEED to have CWM Version 6.0.4.5+

The problem you've had was that you cannot simply "update" from stock recovery to any CMW like you did. You need to have a version with kernel that is compatible with your phone (or else you will "fry" your recovery like you just did)

But let's focus first on recovering your phone from a possible bad flash / bootloop.

Heads up -- Samsung phones are really really hard to brick ;)

I would STRONGLY advise you to use only XDA as Source... This is one of the most known developer sites for Android Phones and is reliable.

Follow this procedure to flash newest STOCK ROM & the old CWM (C. Flashing the newest firmware and E. Flash Custom Recovery, ignore the requirement to install KIES -- never did and have already flashed virtually hundreds of Android phones)

http://forum.xda-developers.com/showthread.php?t=1034145

You NEED to have the proper drivers for odin to work -- you might need to force a different driver (from the list) when the phone is connected and in Download mode.

Just google for "Universal ADB driver" (as I've said - you might need to force the installation of the driver via device manager).

Either way - once the proper driver is there and you open up Odin it should display "Added" message. You can also install full-blown SDK Tools & Platform-tools from Android SDK t-- this will also install the drivers, but you just need the small pack)

Then you can move on with the procedure to re-flash a Stock rom.

Afterwards head here to DL latest CWM 6.0.4.6 that is KitKat compatible :

http://forum.xda-developers.com/showthread.php?t=2583845

You can flash/upgrade to this new CMW from recovery once you have older CWM. Don't do it from stock recovery !

Here are some guides and tutorials :

http://forum.xda-developers.com/showthread.php?t=2188679

and I strongly recommend against CM11 which are unstable for the first Galaxy Aces. BUT if you really want then you might try this one :

http://forum.xda-developers.com/showthread.php?t=2587481

And a stable CM10.2 is here (recommended) :

http://forum.xda-developers.com/showthread.php?t=2635011

or this one

http://forum.xda-developers.com/showthread.php?t=2442024

And once again -- I strongy advise you to head up to XDA, read read read, then read a little bit more, afterwards think for a while and if you still don't know the answer (of course you have searched through the XDA forums ;) ) -- as last resort - ask ;)

Here is a nice place for any technology/IT-related things but the Android gurus are there ;)

installed the Universal adb driver and android SDK Tools package but still phone is not getting detected in the odin. I dont care about the data loss & at this moment is not thinking about using CWM/ Kitkat Cyanogenmod. It would be great if anyhow the stock ROM can be installed. is there any way to fix the device? :huh:

Hm, I had same drivers problem with some Prestigio tablet, cheap Chinese copy. Anyway, my solution was to turn on the tablet, wait a little, then turn it off and go to download mode. If I would termite download mode and try to go to it again, without first trying to start the tablet normally, I would get the same error.

dear, this method is not working. :(

You could give this hard reset a try,,,,,,

1. Turn off the phone. Remove battery and wait 20 seconds. Replace battery.

2. Press and hold Volume up + Home (center button) + Power button at the same time.

3. When first screen shows up do not release buttons. When second "Samsung Galaxy Ace" will shows up do not release buttons. Keep pressing buttons until you get to recovery menu.

4. Select "wipe data/factory reset"

5. Select "Yes -- delete all user data"

* Allow several minutes for the factory data reset process to complete.

6. Select "reboot system now"

* Allow several minutes for the reboot process to complete.

If that fails, you have been given excellent advice by prEzi....I have the same model and xda is a superb site for s5830 roms and advice....Don't worry you will fix your phone ....It is not bricked.

As stated in the OP, I am unable to access the recovery mode and is stuck in a bootloop. So there is no workarund to use this method.

[SlimRock]

Update : So tried the odin mode instructions on my friends Windows 7 system and this time Windows detected the USB device and afterwards automatically downloaded the SAMSUNG USB Composite Device & odin drivers. :yes: idk why Windows 8.1 failed to do so on my system! Finally H/S is now fully working including the Recovery mode using Stock ROM! :dance:

Thanks to @Geeteam for suggesting the Windows 7 option & @PrEzi, @clubhouse,@mara- for helping me out in this thread & @Dodel, @peter.pan in the ChatBox!

[PrEzi]

Glad it works for you now. What is weird - I've had a few driver-problems but always managed to install them properly - no matter if XP, 7 or 8/8.1.

Anyway - if you have CWM then you can start playing with custom ROMs ;)

[geeteam]

hehehe thanks @slimrock so what actually happened. didnt know you created a thread for it.

[SlimRock]

hehehe thanks @slimrock so what actually happened. didnt know you created a thread for it.

@Dodel asked me to create this thread! :yes:

#error & #resolution! Windows 7 trick worked! ^:cheers:

[SlimRock]

Glad it works for you now. What is weird - I've had a few driver-problems but always managed to install them properly - no matter if XP, 7 or 8/8.1.

Anyway - if you have CWM then you can start playing with custom ROMs ;)

Thanks for the help! Now I am bit afraid to use the CWM OR the So called Kitkat update! :huh:

[Dodel]

I expect the drivers didn't work on 8., as the original drivers would been built on an Win 7 machine, so not fully compatible with 8.1.

Glad you got it sorted, though, I'd make a Nandroid backup now also, which you should have done already :p

[geeteam]

this are some of the reasons why I prefer to stay on Windows 7. a lot of drivers issues... especially with Android and if you are a tweaker like me. always wanted to try some new.