Related
Ok, let me start off by saying my phone is currently not bricked. I can get into recovery(H+P) or fastboot(C+P) just fine. My problem lies with the last step of rooting when I flash the new ROM. I am currently trying to flash v4.2.15.1 which is apparently the latest Cyanogen Mod.
Now I've tried two different methods and both won't boot after the ROM is flashed.
The first method is "method B" seen over at the AndroidAndMe website. This method works fine and I can get back into the phone all the way to the point of flashing the SPL and then the ROM. It installs fine, but after reboot it gets stuck on the G1 startup screen.
The second method is the wiki guide for updating from original OS to Cyanogen. This one is a bit different using the Android 1.6 base image. The installation on this method goes smooth up untill the last reboot after flashing the ROM just as the other method. The difference here is instead of it hanging at the G1 startup screen, it get's just past that to a blank backlit screen. No images, no android logo, no sound, no nothing.
Like I said before, I can still access recovery and fastboot which seams to be my only way out. I have repeated this process multiple times on both methods with the exact same results. Fastboot keeps bringing me back to the Android 1.0 firmware(RC29) which is atleast giving me access to a phone while I try to figure this out.
Suggestions? Ideas? I really need to get this phone working again.
I am always on AIM "DeathstarsOG" if that is more convienient for those offering up some help.
What steps did you take to flash the rom?
Did you read the steps outlined in his wiki? The most important step is to flash DRC83_base_defanged.zip first, then his rom over the top.
dbl post sorry.
evilkorn said:
What steps did you take to flash the rom?
Did you read the steps outlined in his wiki? The most important step is to flash DRC83_base_defanged.zip first, then his rom over the top.
Click to expand...
Click to collapse
I followed the steps on both writeups exactly how they were written. As far as the wiki one, I already had a few of the files needed from trying the Androidandme method. Also, my phone is basically already downgraded to the RC29 so thats another step i can skip. All needed files are already on my SD card and were installed in the following fashion:
DREAIMG.nbh
cm-recover-1.4.img
DRC83_base_defanged.zip
update-cm-4.2.15.1-signed.zip
ota-radio-2_22_19_26I.zip
My SD card is already formatted to FAT32
I set up the telnet to get access to recovery mode, wipe phone, then install DRC83, then the cm-4.2.15.1 and lastly the radio. I do a Home+Back reset after installing the radio and it goes past the G1 Startup screen, to a black lit screen of nothingness.
If you're looking at the wiki guide named: "Full Update Guide - G1/Dream Firmware to CyanogenMod" you'll see I basically am supposed to be seeing a update screen that loos like a open box with an arrow pointed down toward a phone after I do this reboot. Well, that doesn't happen. It just goes to that black screen.
Now I'm not a whiz when it comes to stuff like this however I can figure things out fairly sufficiently for the most part. But this has got me stumped. It sounds like I may have a corrupted version of Cyanogen as everything else I have been able to install and actually run on the phone(besides the DRC83). Or maybe I need to flash the radio before the DRC83? I haven't even gotten to the SPL, and after all this I may not want to.
I've done this process over and over atleast 8 times and I feel like I basically know every step by heart, but I still don't want to just guess at what it could be and risk a brick. So that's why I'm here. What do you guys think could be the issue?
Do not wipe the phone after istalling RC29. nbh file rewrites everything, and I mean it... everything.
Here's your order:
DREAIMG.nbh
Boot, sign-in, obtain root (telnet, connect to local host, you know the shpill).
Flash recovery (use ra 1.6.2, it's more updated then cm 1.4)
Wipe
Flash DRC83 defanged.zip
Flash ota radio, follow directions on the screen, you will need to reboot at least once
Flash 1.6 rom (cyan's is a good one to start at least)
Fix permissions.
Wipe
Reboot
Do not set-up linux swap or apps2sd at this time, it will complicate the process more then needs to at this point, you can do it all later.
Good luck.
borodin1 said:
Do not wipe the phone after istalling RC29. nbh file rewrites everything, and I mean it... everything.
Here's your order:
DREAIMG.nbh
Boot, sign-in, obtain root (telnet, connect to local host, you know the shpill).
Flash recovery (use ra 1.6.2, it's more updated then cm 1.4)
Wipe
Flash DRC83 defanged.zip
Flash ota radio, follow directions on the screen, you will need to reboot at least once
Flash 1.6 rom (cyan's is a good one to start at least)
Fix permissions.
Wipe
Reboot
Do not set-up linux swap or apps2sd at this time, it will complicate the process more then needs to at this point, you can do it all later.
Good luck.
Click to expand...
Click to collapse
You my friend are a genius!
Maybe the write-ups for rooting should be re-written to follow this as it worked flawlessly.
I started all the way back from step one at the default G1 1.6 Firmware.
Downgraded to the RC29.
DL'd telnet from the market.
Installed the new RA-recovery
Wiped.
Flashed DRC83.
Flashed Radio.(promted me to reboot)
Flashed the ROM.
Fixed Permissions.
Wiped again.
Then reboot.
Process went flawless, no hicups or anything. Thank you very much sir!
Got a VZW Galaxy tab. Rooted and got ROM manager & SGS Kernel Flasher.
1. I flash using SGS and it successfully flashes, as it reboots and I can see from Settings->Device Info that it shows the Developer's version.
2. I then go to CWM (ROM Manager) load ROM from SD, chose the ROM which is in update.zip format, I select to wipe date and casche and then nothing.
It gets stuck at the SAMSUNG boot screen. So i have to use Heimdall to restore back to stock VZW Rom. I have tried several times, even after flash just tried to reboot directly into Recovery mod (Power+Volume Down) and same thing. Goes to SAMSUNG boot screen and freezes.
What am I missing or doing wrong???
First thing i would recommend is : uninstall rom manager. It causes more problems. If you did a search on these forums you would find loads more tales of woe re rom manager.
Second thing is: have look through the dev section, at the instructions for installing clockwork recovery. Then look for the appropriate rom for your device.
But whatever you do, uninstall rom manager
Sent from my thingymajig
Isn't ROM manager ClockworkMod?
I searched Clockworkmod on the market and when installed the icon says ROM Manager though...
o2sys said:
Got a VZW Galaxy tab. Rooted and got ROM manager & SGS Kernel Flasher.
1. I flash using SGS and it successfully flashes, as it reboots and I can see from Settings->Device Info that it shows the Developer's version.
2. I then go to CWM (ROM Manager) load ROM from SD, chose the ROM which is in update.zip format, I select to wipe date and casche and then nothing.
It gets stuck at the SAMSUNG boot screen. So i have to use Heimdall to restore back to stock VZW Rom. I have tried several times, even after flash just tried to reboot directly into Recovery mod (Power+Volume Down) and same thing. Goes to SAMSUNG boot screen and freezes.
What am I missing or doing wrong???
Click to expand...
Click to collapse
Where you went wrong is just jumping in qnd not even bothering to read ANY tutorials here.
Go and read them instead of screwing things up and then asking where you went wrong.
TheATHEiST said:
Where you went wrong is just jumping in qnd not even bothering to read ANY tutorials here.
Go and read them instead of screwing things up and then asking where you went wrong.
Click to expand...
Click to collapse
i did following the tutorials, its how I went that far to begin with. Sorry for being a newb and maybe not fully understanding it thats why I am asking for help, not to spoon feed me...
Followed these steps:
http://forum.xda-developers.com/showthread.php?t=941781
o2sys said:
...
Followed these steps:
http://forum.xda-developers.com/showthread.php?t=941781
Click to expand...
Click to collapse
Have you tried booting into CW Recovery manually and running the KhasMek.Voodoo.Plus.CDMA.Tab.v5.OC.zip (like the instructions say)?
Your thread header says you are using ROM Manager and trying to run the update.zip package.
ROM Manager _should_ work, but maybe stick with instructions especially if you're having issues.
Yes I have tried going into Recovery manually as I stated in my original post.
I always flashed with SGS kernel flasher as it seemed to work well.
Then I tried manually going to Recovery w/o CWM and gets stuck at boot screen as well.
I tried WITH CWM and same stuck at boot screen.
Tried wiping data through Recovery, through the UI (Settings then ect, ect) and several other combos trying to load the custom ROM.
All I am successul is at rooting, then flashing the kernel. Then no matter which step I tried if i reboot it will get stuck at the SAMSUNG boot screen.
Even if I just turn it off and then turn it back on, after the flash, it will get stuck at the boot screen.
I downloaded the kernal flash directly from the link of the first page. And if the kernal file was courrupt i don't think the flash would go successfully.
I've never used the SGS Flasher so can't say what it would do if the file was corrupt.
Maybe flash it using Heimdall to check the file?
Sorry to hear you are having problems. I am also sorry for the rudeness on this forum. Although I seldom post I read it daily. Here is what I would try;
1. The issue may be with the file name update.zip if you can, rename it to anythingyoulike.zip on you computer and then copy it to your SD card. You may even have to take the card out of your tab to do this (delete the update.zip once the file is renamed). Once the renamed file is on the SD card try to reflash.
2. Have you tried to start again using Odin? There is a good clip on you tube about this. As long as the tab at least starts to boot it is not bricked. Feel free to PM me for any additional help.
Good luck.
tigercorp said:
I've never used the SGS Flasher so can't say what it would do if the file was corrupt.
Maybe flash it using Heimdall to check the file?
Click to expand...
Click to collapse
When I use SGS to flash, it reboots and i can see in settings that it has been flashed.
If I use Heimdall, it flashes then gets stuck at the boot screen.
So I've followed all the tutorials I could find. I've rooted, installed busybox (to make sure it really existed), installed safestrap (the official one from the blog) and can get into recovery just fine. I made sure I have the right phone version and I've never done any kind of bootstrap stuff on this phone before this.
However, when I switch to safe mode to try out some roms, it simply will not work. I've tried all three versions of Eclipse and one CM9 version, but once supposedly done flashing and told to reboot, it gets a blackscreen for a few seconds and restarts back to the dual-core pre-recovery screen. I've wiped, wiped, super wiped everything just like the various instructions tell me to, but nothing ever changes the blackscreen.
Switching it back to non-safe and rebooting works just fine, but I cannot get any custom safe-mode roms to boot up. Is there something else I should be doing that I missed?
I occasionally have issues with Safestrap when you choose to reboot, so I just power off and then power on - that always works. Initial boots do take some time, though more than a few minutes without animation is probably too much.
And, just to clarify, this is the Safestrap that I use: http://blog.hash-of-codes.com/downloads/safestrap/
But it's not that it takes time, it reboots the phone itself. It's not locking up like I've seen others say and requiring a battery pull. It just refuses to go on, instead more like a boot loop? But nothing appears to be going wrong and I can easily switch back to the base no-problem.
And yeah, that's the same one I'm using. Droid 3 v1.08 exactly from that site.
It's making me sad that I can't get this going
Edit: I went ahead and tried just powering it off, leaving it for a moment, and turning it back on. Still did the reboot thing
are you installing the rom and then wiping data?
if so try wiping data first then install rom then reboot..
ovelayer said:
are you installing the rom and then wiping data?
if so try wiping data first then install rom then reboot..
Click to expand...
Click to collapse
Yeah, tried both ways. Wipe data/factory and cache numerous times, install, nothing. Install then wipe, nothing. Wipe, install, wipe, nothing.
Is there an easy way to know for sure if it is even installing anything at all, like navigating to it using a root explorer?
Are you sure that the zip files you are loading are complete downloads? Generally you would receive error messages when installing if so, but you can try unzipping on your computer to see if they have errors. I always download ROM zips on my computer and transfer over (usually using the Dropbox app, but only because I don't want to bother with attaching, choosing USB storage mode, copying the files, unmounting the drives, choosing charge only.) But, if you are downloading the zips with your phone, try doing so instead with your computer, check the files sizes, and then transfer them over to the phone.
(Also, most/all/many of the CM9 zips require flashing a Google apps zip after flashing the ROM. That shouldn't prevent the phone from starting if you skip this step, but it will prevent you from having the market. Just FYI.)
I'd also try Maverick ROM to see if it has the same problem.
I've been running the stock 906 based ROM from Q9Nap here (the one marked Safestrap system), debloated by Pete Souza's script: http://forum.xda-developers.com/showthread.php?t=1554916
doogald said:
Are you sure that the zip files you are loading are complete downloads? Generally you would receive error messages when installing if so, but you can try unzipping on your computer to see if they have errors. I always download ROM zips on my computer and transfer over (usually using the Dropbox app, but only because I don't want to bother with attaching, choosing USB storage mode, copying the files, unmounting the drives, choosing charge only.) But, if you are downloading the zips with your phone, try doing so instead with your computer, check the files sizes, and then transfer them over to the phone.
(Also, most/all/many of the CM9 zips require flashing a Google apps zip after flashing the ROM. That shouldn't prevent the phone from starting if you skip this step, but it will prevent you from having the market. Just FYI.)
I'd also try Maverick ROM to see if it has the same problem.
I've been running the stock 906 based ROM from Q9Nap here (the one marked Safestrap system), debloated by Pete Souza's script: "no linkies for me"
Click to expand...
Click to collapse
I did as you suggested and tried unzipping the files on my computer (which was where I original downloaded them). They all unzipped fine without any errors, unfortunately. The chances of 4 full files being that way were slim, but I sorta hoped...
I'll try Maverick and the Safestrap stock after I get done downloading them.
Thanks everyone for trying to help.
Edit: Alright, I tried Maverick and it showed a prettier flash log, symlinked, all that, still reset itself after passing the recovery splash. Same with the 906 stock based. This time I also tried installing from internal and external SD just to test that.
I'll ask again, is there a specific folder I can get to just for my peace of mind where I can see where it is supposed to have installed these? Or is it in a area where a normal root explorer can't get to?
shinseitom said:
I did as you suggested and tried unzipping the files on my computer (which was where I original downloaded them). They all unzipped fine without any errors, unfortunately. The chances of 4 full files being that way were slim, but I sorta hoped...
I'll try Maverick and the Safestrap stock after I get done downloading them.
Thanks everyone for trying to help.
Edit: Alright, I tried Maverick and it showed a prettier flash log, symlinked, all that, still reset itself after passing the recovery splash. Same with the 906 stock based. This time I also tried installing from internal and external SD just to test that.
I'll ask again, is there a specific folder I can get to just for my peace of mind where I can see where it is supposed to have installed these? Or is it in a area where a normal root explorer can't get to?
Click to expand...
Click to collapse
wait a sec..
you unzipped them?
the zip files are not ment to be unzipped..
download the zip to your phone
go into safestrap and choose install zip then choose the zip
oh wait...duh you were just checking to see if they worked lol
use root explorer and navigate to system folder open the build.prop and see if there is a mention of the rom your trying to install..ie..version=mavrick or eclipse
I'm not finding any references to other roms anywhere in it. I did a search by eye, then a search for "version", "cm", and "mav" and didn't come up with anything relevant. Is that bad?
There are two other things that you can try, though I am not sure that they will help:
1. From non-safe, stock, run Safestrap and uninstall recovery. Restart to see that it does not intercept before the boot screen, then go back in and reinstall recovery from safestrap. Restart the phone to see if it is working. Then restart to Safestrap and try toggling safe mode and see if your flashes work.
2. One other thing to try (not sure if this will help, but...) is to (prior to flashing a ROM) go into the Mounts menu and format /system. Maybe the old system isn't being cleared out by the ROMs you are trying to flash? Then go install the zip, do a wipe data/factory reset and see if that works.
Just wondering if there is a benefit to Safestrap or Bootstrap and why?
I went with Safestrap... Is it just a style thing or is one better?
Not trying to be a jerk, but I have been scanning this post.
Any chance you have overlooked the step of "Toggle Safe System" from the recovery menu?
At the top of the menu it should say "Safe System is: Enabled"
Droidlyen said:
Just wondering if there is a benefit to Safestrap or Bootstrap and why?
I went with Safestrap... Is it just a style thing or is one better?
Click to expand...
Click to collapse
Safestrap is supposed to allow you to install a rom onto a safe "partition" of sorts, though that's not really what's going on. Anyway, it doesn't touch your stock rom so if something fails (like my flashing attempts) you're not in trouble.
SteveHebe said:
Not trying to be a jerk, but I have been scanning this post.
Any chance you have overlooked the step of "Toggle Safe System" from the recovery menu?
At the top of the menu it should say "Safe System is: Enabled"
Click to expand...
Click to collapse
Nah, I switch it every time. I'm not quite messing up that bad
Anyway, I might have to resort to bootstrap to see if that works. If not, well, I guess I'll be stuck on stock. Nothing so far mentioned in the thread has worked for me. Kinda sucks, since I have an Infuse that loves being flashed with anything I want to put on it without problems, unlike a friend's Infuse. Maybe its phone karma.
Hi everybody.
In the past I already flashed custom ROM to routers, so I thought I had the skill to undergo the path of flashing ROM to a phone.
Wrong.
I have countless tabs opened tried to solve my stucked phone, and my PC is running out of memory; and I'm running out of hope.
I own a S Plus GT-i9001.
I wanted to get rid of all the bloatware present in the phone, so I gained root privileges.
Like explained here. It worked perfectly.
Since deleting all the unnecessary apps didn't look working, I thought "well, it is a rainy day, you had this device for a while, why don't you flash some ROM?"
So,
1. I followed this guide, but, needless to say, Rom Manager was not fulfilling to its duty. Indeed I backuped everything I needed, but the stock rom
2. I followed then this guide, point 3, to install ClockworkMod Recovery directly. Before, everytime I tried to enter the recovery menu, I was bounced to the original recovery menu, because ROM manager did not succeed.
With this guide, I managed to boot into ClockworkMod Recovery.
I then started backing up the ROM to the external SD, and it seemed working.
It was popping out with a message "E:Can't mount /cache/recovery/command", but since all the operations went successful, I did not care much (fail, I suppose)
3. I tried to boot back into the phone, before installing the new ROM, just to double check I saved everything, and then the drama began. I was just continuously bounced back at CWM Recovery menu, no way to get in the phone.
I tried anyway to install the AOSP 4.0.4. and all the steps went successful, but still nothing, I would always reboot automatically into CWM Recovery.
4. I tried restore from backup in external SD, it ran successfully, but still couldn't load the phone
5. I then googled into the "E:Can't mount /cache/recovery/command" error, so I ended up somewhere that they were advising to flash FeaCore Phoenix Recovery tool. Indeed it did not display anymore such an error
6. I tried again with he AOSP 4.0.4 ROM, but it showed then the following error
Code:
assert failed: getprop("ro.product.device") == "thunderc" || getprop("ro.build.product") == "thunderc"
so I ended up here and changed the zip accordingly.
7. I also tried this instructions here to perform the most ultimate massive wiping.
8. I installed the AOSP 4.0.4, and the update-Gapps-ICS-20712.zip, it worked, no errors.
Still, it reboots into the recovery menu.
I can't get out of this damned recovery menu, it is crazy! I have used so many recovery tools in PCs, you usually are able to leave them, maybe not able to restore the OS, but you never get stuck into a circle of hell like this!
Please, does anyone has some advice for me? I don't want to waste a 6-months old device
thank you!
You should reflash CWM with odin like this then try flashing a rom again.
If that doesn't work flash a stock frimware through Odin also with the AriesVE.ops file active.
All guides tell you to put the "recovery-clockwork-5.5.0.4-ariesve.tar.md5" or the stock firmware file as "one package". Doing that results into large file errors or odin getting stuck on "downloading..."
Putting the file under phone got my phone back to life, after softbricking it by using CWM 6 thouch.
switchboy said:
You should reflash CWM with odin like this then try flashing a rom again.
If that doesn't work flash a stock frimware through Odin also with the AriesVE.ops file active.
All guides tell you to put the "recovery-clockwork-5.5.0.4-ariesve.tar.md5" or the stock firmware file as "one package". Doing that results into large file errors or odin getting stuck on "downloading..."
Putting the file under phone got my phone back to life, after softbricking it by using CWM 6 thouch.
Click to expand...
Click to collapse
man, you saved my life!
you and the powerful, mighty Odin, god of the Valhalla!
oh, it feels so awesome!
but since I never learn (that was enough of a message to tell me to stop messing around)...
how do I install the ROM I'd like, go through the same process (my phone is now as as when I bought it) or can I use somehow Odin?
jv_guano said:
man, you saved my life!
you and the powerful, mighty Odin, god of the Valhalla!
oh, it feels so awesome!
but since I never learn (that was enough of a message to tell me to stop messing around)...
how do I install the ROM I'd like, go through the same process (my phone is now as as when I bought it) or can I use somehow Odin?
Click to expand...
Click to collapse
I realised that, since I flashed the recovery-clockwork-5.5.0.4-ariesve.tar you provided, if I would boot in recovery mode, it would be still there.
and it is.
but still it is showing the error
E:Can't mount /cache/recovery/command and, needless to say, it is not loading the ROM correctly, it stucked again
I don't get which part am I doing wrong!
jv_guano said:
I realised that, since I flashed the recovery-clockwork-5.5.0.4-ariesve.tar you provided, if I would boot in recovery mode, it would be still there.
and it is.
but still it is showing the error
E:Can't mount /cache/recovery/command and, needless to say, it is not loading the ROM correctly, it stucked again
I don't get which part am I doing wrong!
Click to expand...
Click to collapse
Well, I sorted it out (absolutely, in a mysterious way!!! )
I downloaded the recovery-clockwork-6.0.1.2-ancora.tar.md5 from here, and I followed again your instructions for flashing it with Odino (rigorously NOT ticking one package).
When rebooted, I had the AOSP 4.0.4 Stock, shiny and sparkling!
without even entering the recovery menu and reinstalling!
but I guess I will need to do a clean install again, now that seems that CWM 6 is digested by my phone
I'll try and leave out as much of the long stories as possible.
In trying to unlock my phone, I followed the instructions at jz.bz/tar.jz/unlock-samsung-galaxy-ace-gt-s5830d. Installed Clockwork Recovery 5.0.2.6, and XWKT7 Adrenaline Rom from the links on that page. Installations went fine, though in the final step to find the unlock code, when I opened the file I created in the hex editor, it was nearly empty, and the string I was looking for was missing. Moot. But this is background, in case it's relevant.
Learning what I was doing as I went along, I didn't realize that I had already rooted the device. I proceeded to root it again with SuperOneClick v2.3.3. In the process of this, it told me the device was already rooted, but of course, I continued. Still, everything worked fine.
For reasons not relevant here, I want to return it to the stock ROM. I eventually found it on Sammobile, along with the instructions on this site to use Odin in order to install it. Followed them properly, only to have the installation fail, then catching my phone in a boot loop.
The phone wouldn't come out of the bootloop until I went back to the instructions on that page above, and reinstalled Clockwork and Adrenaline. When I did this, the phone returned to working condition, so I tried to reinstall the stock ROM with Odin a couple more times. Same effect. Found another page on this site instructing me to place the ROM's .zip file on the SD card, and flash it from recovery. In the instructions, it told me to first wipe data/factory reset, then go to mounts/storage and wipe system, wipe data, and wipe SD-ext. There was no 'wipe' option, so I assumed that format was what was being referred to, and did that. After some error messages about the SD-ext, I figured out the SD card wasn't partitioned, used the phone to partition it, and tried again. Error messages gone, but still, both Odin, and the SD card method have failed to reinstall the stock ROM. I'm lost, and at this point, I need some help. Badly.
Greylisted said:
I'll try and leave out as much of the long stories as possible.
In trying to unlock my phone, I followed the instructions at jz.bz/tar.jz/unlock-samsung-galaxy-ace-gt-s5830d. Installed Clockwork Recovery 5.0.2.6, and XWKT7 Adrenaline Rom from the links on that page. Installations went fine, though in the final step to find the unlock code, when I opened the file I created in the hex editor, it was nearly empty, and the string I was looking for was missing. Moot. But this is background, in case it's relevant.
Learning what I was doing as I went along, I didn't realize that I had already rooted the device. I proceeded to root it again with SuperOneClick v2.3.3. In the process of this, it told me the device was already rooted, but of course, I continued. Still, everything worked fine.
For reasons not relevant here, I want to return it to the stock ROM. I eventually found it on Sammobile, along with the instructions on this site to use Odin in order to install it. Followed them properly, only to have the installation fail, then catching my phone in a boot loop.
The phone wouldn't come out of the bootloop until I went back to the instructions on that page above, and reinstalled Clockwork and Adrenaline. When I did this, the phone returned to working condition, so I tried to reinstall the stock ROM with Odin a couple more times. Same effect. Found another page on this site instructing me to place the ROM's .zip file on the SD card, and flash it from recovery. In the instructions, it told me to first wipe data/factory reset, then go to mounts/storage and wipe system, wipe data, and wipe SD-ext. There was no 'wipe' option, so I assumed that format was what was being referred to, and did that. After some error messages about the SD-ext, I figured out the SD card wasn't partitioned, used the phone to partition it, and tried again. Error messages gone, but still, both Odin, and the SD card method have failed to reinstall the stock ROM. I'm lost, and at this point, I need some help. Badly.
Click to expand...
Click to collapse
Follow the instruction from this link on how to install the stock rom,
Know your Device:Galaxy Ace GT-S5830 ~Root~Odin~CWM~ROM LIST
If you encounter any error, just post here. I'll be glad to help. Do post the result. Hope I Helped