Related
Hi everyone,
I just rooted yesterday and installed CM6.2. After trying that rom out for a little I didnt like a few things so I tried Aosp 2.2.1. The home button did not work when I tried that rom so being a noob and not knowing how to fix that I wiped and flashed back to CM6.2.
So settling in with CM6.2 I started adding a few things I added gapps and got the market all that good stuff. Then I went to add the Nexus boot screen . That worked fine. Now I went to upgrade the radio and I would get an error when flashing. So I tried Collins Battery Mod, and when flashing I would also get the same error. Something along the lines of error E:/sdcard/...... status (0) aborted. So I said well , Ill just try to start all over wipe everything and flash the newest Nightlies rom. Well I get the same error . So i tried the older version RC2..... same error. So I said to myself I should try Aosp 2.2.1. again to see if that works because it did before. Well what do you know I get the same error.
E:/sdcard/...... status (0) aborted
My recovery version is RA 1.5.
Any help with this would be greatly appreciated guys . Im new to rooting and I dont like the themes that came with CM6.2 so I really want to be able to flash a theme to it, upgrade the radio and battery mod it.
Also CM6.2 did not come with any widgets?? Is that normal? I have no weather widgets, no clock widgets, nothing.
If I have to start all over thats fine because I never really got that far into customizing , but again , I cant because this error.
jumpman23005 said:
My recovery version is RA 1.5.
Click to expand...
Click to collapse
I'm guessing this is your problem. Try updating it to Darch's unofficial RA-> LINK
(the link goes to my dropbox because Darchs pocketdeveloper's site is down afaik and I don't know where it is on this site )
Download the "RA-Darchstar.img and put it on the root of your sdcard.
Boot up into your rom
Open up terminal emulator and enter the following:
Code:
su
flash_image recovery /sdcard/RA-Darchstar.img
reboot
Hopefully this will do the trick
This let me flash the battery mod but after rebooting it would boot loop. So I just restored.
Then I tried flashing the newest nightlie and got my usual error aborted... nothing seems to be able to flash still
jumpman23005 said:
This let me flash the battery mod but after rebooting it would boot loop. So I just restored.
Then I tried flashing the newest nightlie and got my usual error aborted... nothing seems to be able to flash still
Click to expand...
Click to collapse
Are you wiping data/cache/dalvik before you flash a new rom?
yes sir I am.
jumpman23005 said:
yes sir I am.
Click to expand...
Click to collapse
Try using Rom Manager Instead! See If That Works??
Sent from my HERO200 using XDA App
Anyone please i need help!!!!!
so here is the scenario...
i flashed my asian galaxy tab to overcome1.4.4
i followed the pdf version of its install instruction...
i flashed over to JME-stock-safe via odin... ok PASSED!!!
then i flashed the kernel... ok PASSED
then upon installing the Overcome ROM 1.4.4 it stucked up to Installing new system in the CWM...
So i started back to the first step to redo the process
still no luck...
i tried it so many times still no luck...
what should i do now...
please help me out guys....
You say you flashed the overcome Kernel, did you get the sexy robot voice during the EXT4 conversion? What error are you getting IN CWM when it fails?
Sounds to me like you didn't let the system do it's conversion before you tried to flash the new ROM.
My advice would be to reflash the kernel, and let it boot after you have done so. Reboot into recovery and flash the ROM.
@btyork
yes i did hear the sexy robot converting and it even reboots at its own
then i followed the steps in installing the overcome room...
i even get to the point where it says " Installing New system"
then i've waited for it to finish..
but... i've been waiting for about an hour... so then i decided to redo the process to the top ( reinstalling again the JME-stock-safe) .... OK PASSED again
I did install the overcome kernel.... OK PASSED again
heard the sexy robot converting....
but now it didn't boot on its own...
i've been waiting again for about an hour then nothing happens...
its stocked up to " GALAXY TAB" screen
i didn't run the bootloader patch in the first placed though...
is it something connected to a signed bootloader???
what else can i do????
It may indeed be the bootloader, although I doubt it if you got the kernel installed....
Did you repartition with the hidden.pit file when you went back stock?
Sent from my GT-P1000 using XDA Premium App
hey buddy we can help u fix ur problem but u hav to ask it on the thread u got the rom from.... mods close this thread please
Try recovery mode, then wipe all the data and reboot.
Sent from my GT-P1000 using XDA App
If you are still able to enter recovery mode and you were wise enough to create a nandroid backup before you flashed overcome you could just use the recovery to get back to your phones state just before you flashed overcome. Sounds maybe asif your zip file may have been downloaded wrong or something ... that's why its also always a good idea to check the md5 of the Rom before you flash it ...
Sent from my Desire HD using XDA App
you probably tried this but just checking, did you try powering off, for some reason after the install mine just hung...it took 2 or 3 poweroffs to get it to start booting...been fine ever since.
EDIT: Problem solved!
Hi all,
I just tried to install CWM Recovery on a Samsung Galaxy GT-I9000, and it didn't work.
The phone was (originally) running under Android Froyo (2.2), and unrooted. First of all, I used UnlockRoot to root it, and it worked fine. I checked the root access right after using dedicated apps (rootChecker, sdMaid, etc), to confirm.
Then I wanted to install a ClockWorkMod recovery. I followed this guide (on the CyanogenMod wiki). I downloaded and installed Kies to have the USB drivers installed. Then I downloaded Heimdall (my computer is running under Windows 7) + hardcore CMW Kernel. I booted into download mode, then installed the driver. (Step 2 on the tutorial). Then next step was flashing the kernel. It suceeded, and the phone powered off. Turning it on, it just starts to make endless boot loops. The system won't start running, and it is not possible to access to the CWM recovery menu. But the download mode is still available.
So, does anyone have pointers to help me fix this issue ? i would like to have CMW installed, and then install a custom ROM (the latest Jelly Bean based Cyanogenmod release).
Thanks in advance.
Just try again installing stock Rom with odin
See my post Here
http://forum.xda-developers.com/showthread.php?t=1994759
Hi Donovan,
Thanks for the swift answer. And yes, it definitely worked. I downloaded this stock rom, and I flashed it successfully with Odin v3 1.85. I am running now under Android 2.3.6, but I lost the root access. Rooting it won't be a problem, hopefully. I still have access to the download mode, and to the stock recovery. I'll try once again to dive into the ClockWorkMod Recovery, and then install a Jelly Bean rom.
I'm hitting the thanks button right after posting this.
Thanks back at ya. Cf root you can find here
http://forum.xda-developers.com/showthread.php?t=788108
Dont forget the wiping before flashing jb.
Most times u have 2 flash custom twice.
If first time hangs just pull battery out, get in recovery & flash second time or third if its needed.
If it says install completed then its done
Much pleasure flashing the i9000
Actually, I spoke to fast, the problem just got much worse.
Okay, just after flashing the stock rom (2.3.6), everything was fine. Then I downloaded the latest stable CM10 (direct link).
I booted into recovery mode (CWM Recovery,actually) and I did try to install (i din't not forget wiping data/cache, dalvik and batt stats), but it failed, saying the package was incorrect. I tried many times, copying again and again the zip file, same problem.
Then I downloaded a previous version, CM9. I tried to installed it, and i run into a very weird error, saying an assertion failed when trying to install the package.
Something like;
assert failed: getprop("ro.product.device") == "galaxys" || getprop ("ro.build.product") == "galaxys" ... getprop ("ro.build.device") = GT-I9000 etc...
Click to expand...
Click to collapse
And then installation program aborts (error code 7.)
My assumption, is that it looks like my phone is no longer being considered by a samsung gt i9000, according to the installer. Weird, though...
Now, I still have access to the recovery. But the phone can't boot, as everything was wiped. Much worse, I can switch to download mode, but i can't flash back the stock rom, Odin can't detect the phone (I tried with Odin v3 1.82, 1.83 and 1.87).
I'm getting desperate, any pointers ?
Thanks in advance!
Did u try to flash the custom more then 1 time?
Oh yes, I did it like a dozen of times.And I still get the same error.
Sent from my HTC Wildfire S A510e using xda app-developers app
gti9000 rooting
Hi Donovan, could you help me please:fingers-crossed:
I've purchased a unlocked galaxy s gti9000 and I want to root it. Something I've never done on any phone as I'm a complete noob. I managed to install XWJW1 FIRMWARE. I've now got as follows PDA:I9000XWJW6
PHONE: I9000XWJW1
CSC: I9000XSAJV8.
All the links to the file for rooting seem to be dead. I've found some for rooting XXJVU, But that's not right is it? I would really like to try ICS or Jelly Bean. I must admit I'm nervous about this as it's taken me a while to get a phone as good as this one!! Any help would be greatly appreciated. Thanks in advance
@Nooga:There is a very complete and straightforward guide here (http://forum.xda-developers.com/showthread.php?t=1852546). You might want to take a look at it.
Now can we please come back on my topic ? Thanks!
Sent from my HTC Wildfire S A510e using xda app-developers app
Thanks
Roland_Y said:
@Nooga:There is a very complete and straightforward guide here (http://forum.xda-developers.com/showthread.php?t=1852546). You might want to take a look at it.
Now can we please come back on my topic ? Thanks!
Sent from my HTC Wildfire S A510e using xda app-developers app
Click to expand...
Click to collapse
Thanks Roland will give it a try tonight.
Well, that is now solved. I tried something silly that ended up working fine.
As the cm9-smtd update package couldn't run (because of the assertion fail), I just opened the zip package, then edited the file META-INF/com/android/google/updater-script.
I basically removed the assert statement at the top of the file.
CMW recovery installed it properly, without any err. I now have an ICS based rom (Cyanogen Mod 9).
Problem definitely solved now. Going to make a Nandroid backup.
Thanks all, again.
Hello people,
I have a problem, actually more then one.
I tried rooting my s2 mini from a guide, installed clockworkmod-5.0.2.8.tar via Odin and now i'm blocked in the recovery menu.
i know there were people here having the same problem, but... every time i reset i get gt-7500 instead of gt-6500 text, so i'm not sure but i think the phone got screwed up.
i've tried to flash cm version 10.1 for 6500 mini but after some text it says
e:error in /sdcard/ (the cm version name.zip)
(status 7)
Installation aborted.
so i tried to flash a 7500gt rom and the installation worked ( i know , lol.. but i was curious)
even so , i'm still blocked in cwm recovery
After more searches on the forum i found a "cwm-6.0.3.3-jena.tar" so i decided to flash this and get rid of that pesky cwn 7500 messing with the phone but.. odin is stuck at "setup connection"
i did try to remove battery for a while, change usb port, get newest odin, restart pc, sacrifice a chicken on a shrine, yet nothing worked...
any ideas? i'm a noob so... any help would be much appreciated.
First reflash Stock ROM via Odin (find it on SamMobile page and search for appropriate version for example if you have S6500D model than search for that model or if you have S6500 (without D/T/L) than search for that ROM). After installing ROM go back to download mode and flash latest CWM. And after this method you can flash CM10/CM10.1 or any other ROM you want.
Sent from Nuclear Reactor (also known as I9300)
I think you should try sacrificing a pig or sheep. Chicken's aren't so reliable !
Also you might try the old drown'em in a lake then burn them..but it's very hard to get the pig to drown.
Identity86 said:
Hello people,
i've tried to flash cm version 10.1 for 6500 mini but after some text it says
e:error in /sdcard/ (the cm version name.zip)
(status 7)
Installation aborted.
.
Click to expand...
Click to collapse
I Had the same problem with flashing but it didn't say s7500. It say s5570i so I just flashed stock from sammobile.
Sorry for my bad English
Sent from GT-S6500D using XDA premium.
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...