I've recently flashed the devil kernel to mess around with the JB roms. I'm wanting to go back to ICS roms while the JB roms mature. I booted into devil recovery, wipe then installed the CWM zip but says "status 0" aborted.
I've tried doing it through ROM manager but gives me errors that way also.
What am I doing wrong??
blackinches said:
I've recently flashed the devil kernel to mess around with the JB roms. I'm wanting to go back to ICS roms while the JB roms mature. I booted into devil recovery, wipe then installed the CWM zip but says "status 0" aborted.
I've tried doing it through ROM manager but gives me errors that way also.
What am I doing wrong??
Click to expand...
Click to collapse
Your mistake
1) Using Rom manager
2)Devil kernel uses both cwm and twrp recovery no need to "flash recovery" anyways.
If you can still get in to recover just flash what ever ICS rom you want. I'd advice full wipe and formating /system.
Sent from my SGH-I897 using Tapatalk 2
Same Problem, but i tried to flash with devil recovery. First, with cm10 it says installation aborted. Second time with cm9 he rebooted after 5 sec. and now it's in a boot loop.
What can I do to flash cm9 or cm10?
Pad10 said:
Same Problem, but i tried to flash with devil recovery. First, with cm10 it says installation aborted. Second time with cm9 he rebooted after 5 sec. and now it's in a boot loop.
What can I do to flash cm9 or cm10?
Click to expand...
Click to collapse
CM10 and devil kernel don't always get along. Something about the partition layout with devil. Anyway when you tried CM9 and it rebooted it just means it succeeded in flashing the kernel that CM9 comes with. Pull and replace the battery and 3 button combo back into recovery which will probably not be devil anymore. I don't think you have to but I typically go through the wipe procedure again and then you should be able to reflash CM9 without trouble.
m1batt1 said:
CM10 and devil kernel don't always get along. Something about the partition layout with devil. Anyway when you tried CM9 and it rebooted it just means it succeeded in flashing the kernel that CM9 comes with. Pull and replace the battery and 3 button combo back into recovery which will probably not be devil anymore. I don't think you have to but I typically go through the wipe procedure again and then you should be able to reflash CM9 without trouble.
Click to expand...
Click to collapse
I just flashed the cm9 and it didn't work, so I flashed cm10 and it worked apart from the google apps. It says Installation aborted. I tried to install it once again but it didn't help out.
What can I do now?
Pad10 said:
I just flashed the cm9 and it didn't work, so I flashed cm10 and it worked apart from the google apps. It says Installation aborted. I tried to install it once again but it didn't help out.
What can I do now?
Click to expand...
Click to collapse
the google apps package you have... is it the one for JellyBean?
m1batt1 said:
the google apps package you have... is it the one for JellyBean?
Click to expand...
Click to collapse
It's called "gaps-jb-20120726". The link is in the description of the cm10 thread.
Any help?
Help
Those ROMS use a different partition layout. You have to flash an older ROM via ODIN and then you'll be able to go back.
PantherZA said:
Those ROMS use a different partition layout. You have to flash an older ROM via ODIN and then you'll be able to go back.
Click to expand...
Click to collapse
Okay and how can I do that?
:laugh:
Any help?
Pad10 said:
Okay and how can I do that?
:laugh:
Click to expand...
Click to collapse
By utilizing the sticky threads that have all the information you need.
Pad10 said:
Any help?
Click to expand...
Click to collapse
http://forum.xda-developers.com/forumdisplay.php?f=746
Related
Hi
After using CM9 for some time, I decided to upgrade to the new stable release. I am not sure what happened, but the flash was unsuccessful. Using ODIN I restored my phone back to stock.
When I try to install CM9 I now end up in a recovery loop, where the phone will only boot into recovery.
What am I doing wrong? How can I fix this?
Many thanks
Harry
morseharry said:
When I try to install CM9 I now end up in a recovery loop, where the phone will only boot into recovery.
Click to expand...
Click to collapse
Do you install cm9 through cwm recovery?
Freddie_X said:
Do you install cm9 through cwm recovery?
Click to expand...
Click to collapse
Yes I did, using the CWM that comes with the speedmod kernel. The CWM that the phone boots to after this, however, is an updated one, I assume the one that comes with CM9. From here I have tried reflashing CM9 but still have the recovery bootloop
Harry
Hey
Is your phone rooted??
and try flashing the rom twice..
Hi
It has Cwm but I didn't root before flashing. Thought it didn't make a difference?
I have tried flashing twice, still has me booting into recovery
Harry
morseharry said:
Hi
It has Cwm but I didn't root before flashing. Thought it didn't make a difference?
I have tried flashing twice, still has me booting into recovery
Harry
Click to expand...
Click to collapse
For installing CM9 your phones needs to be on 2.3.6 and rooted...click here for my guide...
After I follow your guide will I have cwm and do i then just flash as usual?
Harry
Yup..
After rooting 2.3.6 you can follow the regular steps for CM9...
Sent from my GT-I9000
tchindalia said:
Yup..
After rooting 2.3.6 you can follow the regular steps for CM9...
Sent from my GT-I9000
Click to expand...
Click to collapse
Ok I have upgraded, then when I try to flash CM9 it starts the process then quickly enters a bootloop where I get to the cyanogenmod kernel screen. I know I need to flash twice but I cannot see how to do so?
Thanks
Harry
Hey
Remove the battery...put it back after atleast 10 sec..then boot into recovery using 3 Button Combo...then flash the rom again...
This time it'll take a few min..then it'll re-boot itself..
Enjoy..
Got it all working perfectly now, thank you so much
hello all. I just started diving into the world of rooting (and android for that matter) with a friends old captivate. In the process of installing Jelly bean, I messed things up pretty bad.
I had a corn kernel installed (which I later found out wasnt usable for CM10) and when I then found a devil kernal to use, i found myself getting stuck in a boot loop. Trying to get out of it, I flashed back (using odin) to the corn kernel, which then get stuck on the boot screen with the loading bar at 100%. I then flashed around to a few different kernels i had downloaded in the process of trying to figure all of this out and now I cannot get the phone to boot back into the OS.
What should I do?? Where can I find the proper kernels for CM10 (everything I follow is always dead)? and most importantly, how can I get this phone back up and running. This forum seems to be filled with all sorts of smart people, so hopefully we can figure out a solution quickly.
Thanks
With Cornkernel 705 installed I can access the CWM5 recovery screen if that makes a difference
sjorge3442 said:
With Cornkernel 705 installed I can access the CWM5 recovery screen if that makes a difference
Click to expand...
Click to collapse
If you can get in cwm, factory reset and re-flash CM10 (as per their process). CM10 will flash with it's own kernel so you don't have to bother with flashing a kernel after.
If that doesn't work, get stock KK4 and flash with Odin (or Heimdall). Then flash Corn kernel with Odin 1.85 and finaly flash your ROM.
BWolf56 said:
If you can get in cwm, factory reset and re-flash CM10 (as per their process). CM10 will flash with it's own kernel so you don't have to bother with flashing a kernel after.
If that doesn't work, get stock KK4 and flash with Odin (or Heimdall). Then flash Corn kernel with Odin 1.85 and finaly flash your ROM.
Click to expand...
Click to collapse
.
Well, when I get into CWM since i'm running corn, I cannot locate CM10. Flashing back to stock didnt even allow me to reboot into the phone either.
sjorge3442 said:
.
Well, when I get into CWM since i'm running corn, I cannot locate CM10. Flashing back to stock didnt even allow me to reboot into the phone either.
Click to expand...
Click to collapse
Mount your SD through recovery, make sure CM10 is still on it and go from there.
BWolf56 said:
Mount your SD through recovery, make sure CM10 is still on it and go from there.
Click to expand...
Click to collapse
Just logged back into CwM to try to do this and after I mount the SD, I still cannot find any option for CM10 and I am positive it is still on the card.
sjorge3442 said:
Just logged back into CwM to try to do this and after I mount the SD, I still cannot find any option for CM10 and I am positive it is still on the card.
Click to expand...
Click to collapse
Mount the SD card to your PC to make sure it's still there, is what I meant.
well since Im really impatient, I ended up using Odin3 one-click downloader which allowed me to revert back to eclair. phone is working and I plan on starting back to getting CM10 running. Which kernel do you suggest I flash for that?
sjorge3442 said:
well since Im really impatient, I ended up using Odin3 one-click downloader which allowed me to revert back to eclair. phone is working and I plan on starting back to getting CM10 running. Which kernel do you suggest I flash for that?
Click to expand...
Click to collapse
Probably a good idea to clean flash anyway.
Corn is the kernel you'll want to get root.
BWolf56 said:
Probably a good idea to clean flash anyway.
Corn is the kernel you'll want to get root.
Click to expand...
Click to collapse
Yeah, but from what I've read and experienced, Corn cannot be used for CM10 purposes. After flashing to corn using odin (I can both 705 and 706 saved on my computer) there is no option in CwM to install CM10. I read that corn isnt able to boot CM10, but maybe I read something wrong. We're getting off topic for the post, but i'm sure others are having the same problem
sjorge3442 said:
Yeah, but from what I've read and experienced, Corn cannot be used for CM10 purposes. After flashing to corn using odin (I can both 705 and 706 saved on my computer) there is no option in CwM to install CM10. I read that corn isnt able to boot CM10, but maybe I read something wrong. We're getting off topic for the post, but i'm sure others are having the same problem
Click to expand...
Click to collapse
Maybe I'm missing something here but I'm not sure I understand.. The usual process to flashing looks like this (as you probably know):
Odin KK4 stock
Odin 1.85 corn kernel
Flash your ROM through cwm as per their instructions
Flash Gapps
Enjoy
Corn will give you root and from there, you should be able to go get your CM10.zip that is on your internal SD and flash it.
Corn will be wiped as you flash CM10 cause it flashes it's own kernel so it is only to get root when you're on stock.
BWolf56 said:
Maybe I'm missing something here but I'm not sure I understand.. The usual process to flashing looks like this (as you probably know):
Odin KK4 stock
Odin 1.85 corn kernel
Flash your ROM through cwm as per their instructions
Flash Gapps
Enjoy
Corn will give you root and from there, you should be able to go get your CM10.zip that is on your internal SD and flash it.
Corn will be wiped as you flash CM10 cause it flashes it's own kernel so it is only to get root when you're on stock.
Click to expand...
Click to collapse
This is exactly what I thought too, but using corn v706, no matter what I do, I cannot located CM10 OR Gapps....
sjorge3442 said:
This is exactly what I thought too, but using corn v706, no matter what I do, I cannot located CM10 OR Gapps....
Click to expand...
Click to collapse
That's why I said to mount your SD to your PC, make sure where you've put them (in which folder) and also make sure they're actually on it. The kernel won't hide files.. eh
If you wanna make it easy, create a folder for them (and of course, move them in). Folder: CM10. That way you won't be searching all through your phone for them.
so I placed the CM10 in the root of the SD card. On Corn 706, im unable to locate it. I flashed over to Semaphore and was actually able to find the CM10 file, but for whatever reason, when I try to install it, it begins the process and then aborts it.
That would be the norm...just select to install the Rom again from that cwm recovery that pops up.
Sent from my SGH-I897 using xda premium
4-2ndtwin said:
That would be the norm...just select to install the Rom again from that cwm recovery that pops up.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
I tried doing that, but it just continues to abort it.I get status 7 error
sjorge3442 said:
I tried doing that, but it just continues to abort it.I get status 7 error
Click to expand...
Click to collapse
Wait.. When you flashed to stock, what Odin did you use?? There's a GB stock (KK4). If you flashed back with the old one click and you're back on eclair you probably don't have the GB bootloaders so you'll have to get them. Corn kernel is meant for GB, not eclair so would make sense if it doesn't work.
Well, I am currently sitting on CM9 with Semaphore. Phone is working, just need to find the correct Gapps, since thats where I store my contact info. I'll mess around with getting CM10 in a few days. I was tired of using my blackberry for the past two days while I have been trying to get this damn phone up and running. I'll do my research to ensure that I use the correct kernels and bootloaders. If you know of a guide for getting to CM10 from CM9, that would be great.
sjorge3442 said:
Well, I am currently sitting on CM9 with Semaphore. Phone is working, just need to find the correct Gapps, since thats where I store my contact info. I'll mess around with getting CM10 in a few days. I was tired of using my blackberry for the past two days while I have been trying to get this damn phone up and running. I'll do my research to ensure that I use the correct kernels and bootloaders. If you know of a guide for getting to CM10 from CM9, that would be great.
Click to expand...
Click to collapse
The instructions are in the CM10 thread. I believe they're quite basics, don't need to go back to stock.
Also, if I were you, I'd redownload CM10 ROM. Could be getting those errors from a bad download.
sjorge3442 said:
I tried doing that, but it just continues to abort it.I get status 7 error
Click to expand...
Click to collapse
...and just a friendly fyi, if u get the Status 7 error again, when u try flashing to CM10 another day, it is because of the assert script in the updater-script, of what ur wanting to flash, is looking at what the build.prop says of ur phone. (that is even hard to type, lol...someone plz correct me if i'm wrong).
U can search and read up a little probably better than i could type and try to explain it. --- But in the end it is more of a fail safe so that u don't flash something that is not for ur phone.
It will be more clear once u read up on it a little. :thumbup:
The asserts can be edited/removed, build.prop edited, or u could use a different kernel, etc. --- several options as a work around to the error.
Sent from my SGH-I897 using xda premium
Hello everyone. I used to work out most problems myself but seems like i ran into a problem i dont understand.. so would be nice if someone could help.
I like to try different roms. After staying with paranoid android. I went to a miui rom and then tw based again. Tried most of tw based jb roms am on sva now. Now the problem is:
When i tried to go back to paranoid flash in cwm installation stopps... tried utacka and standard several times even downloafed each again. I get error sth. Like ...emmc.. status 7 install abort. This isnt good hm ?
Can anybody tell what ....?
Also i get booting even before cwm a green message in left upper corner ...jpg. draw image failed. The same message i get when phone is off and i plug it in to load. Well dont know if its related.
as there are lots of clever people out there i hope someone could tell me what to do or if i messed it up. Btw. I can still flash any tw based rom. Thanks
status 7 is usally a bad download / corrupted file, I think you should redownload it and check the md5 before flashing.
Also, flash over a full wipe (safe kernel obviously ) and see how it goes, As for the green jpg message, I believe thats the charging animation, So long as the phone is charging i wouldnt worry too much, Its probably been corrupted inside the ROM, so flashing a new one *could* replace the dodgy jpg image. :good:
what is the name of the file you downloaded for PA? are you getting this error ? assert failed: getprop("ro.product.device")
try a different kernel. The phone might not boot with that but you can install a new rom from recovery
Hello
I had your problem before, I found out it is a bad download (corrupted file)
First, I would like to explain that (EMMC) means the zip files i located on your internal storage
Status 7 can mean either you're using a version not optimized for your phone (so be sure you're downloading from N7000 forums) or it is a corrupted file
To conclude that, do a checksum on the zip file on your phone (There's a free app on play store called Checksum) and compare the checksum that is generated by the app to the checmsum on Utacka thread.. if they differ, then re-download the file from the forum (& repeat the checksum check before you flash it)
Best of luck
irgendeinname said:
Hello everyone. I used to work out most problems myself but seems like i ran into a problem i dont understand.. so would be nice if someone could help.
I like to try different roms. After staying with paranoid android. I went to a miui rom and then tw based again. Tried most of tw based jb roms am on sva now. Now the problem is:
When i tried to go back to paranoid flash in cwm installation stopps... tried utacka and standard several times even downloafed each again. I get error sth. Like ...emmc.. status 7 install abort. This isnt good hm ?
Can anybody tell what ....?
Also i get booting even before cwm a green message in left upper corner ...jpg. draw image failed. The same message i get when phone is off and i plug it in to load. Well dont know if its related.
as there are lots of clever people out there i hope someone could tell me what to do or if i messed it up. Btw. I can still flash any tw based rom. Thanks
Click to expand...
Click to collapse
Try flash Abyss kernel first and from Abyss kernel flash the paranoid android. It happened to me and it turns out not the rom is not corrected but I cannot flash directly from the Phil kernel.
irgendeinname said:
...emmc.. status 7 install abort.
Click to expand...
Click to collapse
That's a known issue of some of the new PhilZ kernels/recoveries, nothing to get worried about.
Flash either a CM10 or HydraCore kernel, reboot recovery, do the wipes and flash away.
Hello,
I've the same problem like u.
Currently I'm still on ultimate 4.1.2 v5 which based on LSA. Everytime I tried to flash another ROM...the emmc status 7 error will appear.
So I guess we have similar problem.
To all expert guys here,
So if I installed the hydracore kernel and reboot to recovery, I can directly flash any new ROM that I want to flash?
Coz, last night my friend said by opening the zip file and edit the updater script on ro.build prop will help me to solved this status 7 error..but after i tried to reedit that script. It won't work. I still got that issue.
Let me try this method by flashing this HC kernel tonight..n i'll update u what I get. Btw I can use any kind of HC kernel right? Or I must use the latest version...which mean the version 7...
Regards
Sent from my GT-N7000 using Tapatalk 2
Any version can be used. Just keep in mind that the phone won't boot after installing hydracore. Only recovery and download mode. So make sure to have all the necessary files preloaded before installing HC
nokiamodeln91 said:
Any version can be used. Just keep in mind that the phone won't boot after installing hydracore. Only recovery and download mode. So make sure to have all the necessary files preloaded before installing HC
Click to expand...
Click to collapse
What do u mean with preload files?
Is it these one?
- zip rom file
- hc kernel
Are there any other files do i need to prepare before flashing that kernel?
Sent from my GT-N7000 using Tapatalk 2
Yes. Rom file and gapps file of cm rom. And hydracore
nokiamodeln91 said:
Yes. Rom file and gapps file of cm rom. And hydracore
Click to expand...
Click to collapse
Ok
Thx for ur help
Sent from my GT-N7000 using Tapatalk 2
Thanks
chasmodo said:
That's a known issue of some of the new PhilZ kernels/recoveries, nothing to get worried about.
Flash either a CM10 or HydraCore kernel, reboot recovery, do the wipes and flash away.
Click to expand...
Click to collapse
Worked for me. Your a reassuring voice in forums. Now off to try CM10.1!
Thanks
I've installed a number of ROMs on my phone without a hitch ever since rooting it last year.. until now. I did admittedly do one thing different this time around, and that was formatting both the emmc and preload, too, which I'm for some reason now beginning to believe was a bad move. I don't even know why I did that knowing full well that I have absolutely zero technical know-how of these things lol.. Should've just stuck with the fool proof "safe kernel > full wipe > wipe caches > rom and gapps (if required)" formula.
Anyway, I was on a CM10.1 ROM before this happened (vanilla rootbox). I rebooted to recovery, did a full wipe, wiped caches, formatted system, data, preload and emmc, flashed hydracore 7.0 standard and rebooted to recovery again. I then tried installing beerbong's AOSPA PA3.56 ROM which failed with an error that read something like "installation failed, filename.zip (bad)". Even the ROMS that previously installed without an issue won't install now, including vanilla rootbox (returns a status 7 error)..
The f*** have I done ? Please help.
download and copy onto your phone any Philz kernel for JB. After you have flashed that then you can install the other ROMs.
XxPixX said:
download and copy onto your phone any Philz kernel for JB. After you have flashed that then you can install the other ROMs.
Click to expand...
Click to collapse
Cheers! I'll try the latest PhilZ kernel and report back.
Edit:
Right. So, umm, it's not even letting me install the kernel now -- getting the same error. Hmm :/
Ok, download the TAR version of Philz kernel and flash it with odin.
XxPixX said:
Ok, download the TAR version of Philz kernel and flash it with odin.
Click to expand...
Click to collapse
Lol, I have the yellow triangle now. Bahhh
ultrono said:
Lol, I have the yellow triangle now. Bahhh
Click to expand...
Click to collapse
Go to the android development forum. The triangle away procedure right there in the stickies.
Varad297 said:
Go to the android development forum. The triangle away procedure right there in the stickies.
Click to expand...
Click to collapse
Yeah I've already checked that out -- the problem, however, is that I don't have soldering equipment required for the procedure mentioned :/
I am able to put the phone in download and recovery mode, though (if that can in any way mean that an alternative method to get rid of the yellow triangle can also be used).
ultrono said:
Yeah I've already checked that out -- the problem, however, is that I don't have soldering equipment required for the procedure mentioned :/
I am able to put the phone in download and recovery mode, though (if that can in any way mean that an alternative method to get rid of the yellow triangle can also be used).
Click to expand...
Click to collapse
have you tried flashing stock rom in download mode using pc odin?
treacherous_hawk said:
have you tried flashing stock rom in download mode using pc odin?
Click to expand...
Click to collapse
That I haven't. I'll try that and report back. Cheers!
Edit:
Dude! That worked (for the yellow triangle)! Haha, thanks
The system 7 error on trying to install custom roms is still there, though (even with the latest Philz kernel).
ultrono said:
That I haven't. I'll try that and report back. Cheers!
Edit:
Dude! That worked (for the yellow triangle)! Haha, thanks
The system 7 error on trying to install custom roms is still there, though (even with the latest Philz kernel).
Click to expand...
Click to collapse
try to install CM 10 kernel first and then flash the CM rom.
i have been flashing roms now since january this year. I've already flashed a lot for both the Gio and the Ace.
Now I'm running into this same problem again with several roms:
when I want to flash the rom, it returns me a status 7 error. Why? I don't know. I've tried already so much: md5 checksum, downloading again, formatting my sdcard partition
I have it with many roms (cm 7 blackhawk / firekernel, cm 10.1.1 mardon, cm10 maclaw etc etc).
I would like to find out what the problem is and possibly how I can solve it.
Maybe there is a problem with your recovery install. You could try to install that again.
Try to toggle signature verification in cwm. Or just reflash the recovery.
Sent from my Galaxy Ace GT-S5830 using xda premium
Venomous Viper 119 said:
Try to toggle signature verification in cwm. Or just reflash the recovery.
Sent from my Galaxy Ace GT-S5830 using xda premium
Click to expand...
Click to collapse
should i download a new recovery or the same i already had? (file name: recovery-clockwork-5.0.2.6-galaxyace-fix.zip)
DutchArjo said:
should i download a new recovery or the same i already had? (file name: recovery-clockwork-5.0.2.6-galaxyace-fix.zip)
Click to expand...
Click to collapse
Just download the same file again. I use the same one.
nikwen said:
Just download the same file again. I use the same one.
Click to expand...
Click to collapse
thanks. I've tried this but even reflashing my cwm file returns a status 7 error
but flashing my px-cwm v2.zip recovery completed.
I managed to install cwm 6.0.3.2 (although it still says 5.0.2.6) and still i'm getting all these status 7 errors.
the error is " assert failed". Is it possible that cwm isn't able to "read" the several getprop requests from my phone?
Or should the line in script update be changed with removing the spaces between the getprop for cooper and the getprop for gt-s5830?
DutchArjo said:
thanks. I've tried this but even reflashing my cwm file returns a status 7 error
Click to expand...
Click to collapse
Ok. In that case there is an error with your recovery.
@The Others: Would it help to flash a Samsung Firmware via Odin? Would that replace the recovery?
I managed to install cwm 6.0.3.2 and still i'm getting all these status 7 errors.
the error is " assert failed". Is it possible that cwm isn't able to "read" the several getprop requests from my phone?
Or should the line in script update be changed with removing the spaces between the getprop for cooper and the getprop for gt-s5830?
DutchArjo said:
I managed to install cwm 6.0.3.2 and still i'm getting all these status 7 errors.
the error is " assert failed". Is it possible that cwm isn't able to "read" the several getprop requests from my phone?
Or should the line in script update be changed with removing the spaces between the getprop for cooper and the getprop for gt-s5830?
Click to expand...
Click to collapse
Try it if you know what you are doing.
nikwen said:
Ok. In that case there is an error with your recovery.
@The Others: Would it help to flash a Samsung Firmware via Odin? Would that replace the recovery?
Click to expand...
Click to collapse
Hi nikwen, yes, to flash via Odin will replace the recovery with the stock recovery. Cheers.
Sent from my GT-S5830 with TouchWiz UX 5.0 by NaTHaN
BajoPrimate said:
Hi nikwen, yes, to flash via Odin will replace the recovery with the stock recovery. Cheers.
Sent from my GT-S5830 with TouchWiz UX 5.0 by NaTHaN
Click to expand...
Click to collapse
i've flashed a stock rom with mobile odin.
After that: i've tried to flash the cm10.1.3 rom from mardon. It returned a status 0 error. After that, I've flashed cwm 6.0.3.2 and tried to flash the rom again. Still a status 7 error.
Is it possible that maclaw's cm9 or cm10 have changed something in my Phone which causes that i'm unable to flash anything anymore? I only get status 7 errors. When i follow the suggested steps at XDA to get rid of these errors (read: delete the assert lines in updater script) the status 7 errors are replaced by status 6 errors.
when i'm in cm9 and execute getprop in terminal, the ro.product.build / devide / model = cooper (no gt-s5830).
the label on my Phone (which is located underneath the battery) says gt-s5830.
How do I get rid of the maclaw history and return to the completely Original rom to see if I can flash from there?
DutchArjo said:
i've flashed a stock rom with mobile odin.
After that: i've tried to flash the cm10.1.3 rom from mardon. It returned a status 0 error. After that, I've flashed cwm 6.0.3.2 and tried to flash the rom again. Still a status 7 error.
Is it possible that maclaw's cm9 or cm10 have changed something in my Phone which causes that i'm unable to flash anything anymore? I only get status 7 errors. When i follow the suggested steps at XDA to get rid of these errors (read: delete the assert lines in updater script) the status 7 errors are replaced by status 6 errors.
when i'm in cm9 and execute getprop in terminal, the ro.product.build / devide / model = cooper (no gt-s5830).
the label on my Phone (which is located underneath the battery) says gt-s5830.
How do I get rid of the maclaw history and return to the completely Original rom to see if I can flash from there?
Click to expand...
Click to collapse
Are there differences between Odin and Mobile Odin? If there are some, flashing using the desktop one might help.
Cooper is the codename for our Ace. So that is ok.
I've tried 2 stock roms now. Neither can boot. I've reflashed the 5.0.2.6 cwm recovery because that one is the only one that can restore my cm9 backup. I'm lost... I don't know what to do now because there is simply no way of getting a different rom on this Phone and i would really like to know why.
What did maclaws rom do that f*ck*d up my Phone?
DutchArjo said:
I've tried 2 stock roms now. Neither can boot. I've reflashed the 5.0.2.6 cwm recovery because that one is the only one that can restore my cm9 backup. I'm lost... I don't know what to do now because there is simply no way of getting a different rom on this Phone and i would really like to know why.
What did maclaws rom do that f*ck*d up my Phone?
Click to expand...
Click to collapse
You could send them an email.
Flash stock via PC using odin. You will be stuck in a bootloop. Reboot into recovery & factory reset. Reboot & phone boots. Now, important , you cannot flash custom Roms via stock recovery. Place the cwm 5.0.2.6 zip on sd card. Reboot into recovery , select " install update from sd card ", select the zip file, select yes & reboot. Again reboot into recovery, do full wipes & select " install zip from sd card " & NOT " install update from sd card " & flash any stock based Rom like Touchwiz 5 by Nathan. If you follow this, everything must be fine.
Sent from my Galaxy Ace GT-S5830 using xda premium
nikwen said:
You could send them an email.
Click to expand...
Click to collapse
YEs... I managed to flash px recovery 0.4 (again: I still had to delete the assert lines from updater script). Now I was able to flash the cm 10.1.3 rom from Mardon. Just booted for the first time. Hopefully my status 7 errors are now history... (i don't know if I can restore my cm9 backup from maclaw but we will see).
DutchArjo said:
YEs... I managed to flash px recovery 0.4 (again: I still had to delete the assert lines from updater script). Now I was able to flash the cm 10.1.3 rom from Mardon. Just booted for the first time. Hopefully my status 7 errors are now history... (i don't know if I can restore my cm9 backup from maclaw but we will see).
Click to expand...
Click to collapse
Great.
Do you want to restore it? I prefer 4.2.2.
i prefer not. But it depends on how satisfied I am on this cm 10.1.3 rom. And how many bugs / errors I experience, How smooth/fast it is etc.
When I'm not satisfied, I can Always return to this rom I was most satistied off so far. But I wanted another rom because I have a lot spontaneous reboots when turning on Wifi again....
DutchArjo said:
i prefer not. But it depends on how satisfied I am on this cm 10.1.3 rom. And how many bugs / errors I experience, How smooth/fast it is etc.
When I'm not satisfied, I can Always return to this rom I was most satistied off so far. But I wanted another rom because I have a lot spontaneous reboots when turning on Wifi again....
Click to expand...
Click to collapse
In case like yours a fresh often install helps, too.
nikwen said:
In case like yours a fresh often install helps, too.
Click to expand...
Click to collapse
it might, but it also means reinstalling all my apps again. And I do not want to do that
hopefully, this cm10 rom is satisfying enough. I will then stick to it...