Okay this is my first thread and post on this site. This is a great place to learn and I'm loving it. Hello all.
I've been pretty succesful so far at flashing roms on my captivate for the past couple months and this is the first problem I've ran into.
So I was coming from a CM7 nightly and I flashed the Beta 1 ICSSGS rom from this thread:
http://forum.xda-developers.com/showthread.php?t=1362092
Obviously I flashed the Beta 1 kernel that came along with it. It works well, it's beta so I know it's not perfect.
Now I'm trying to flash the teamhacksung build 3 ICS rom since it is to be CM9 later, but I get a message that basically says
assert failed: getprop("ro.product.device") == "captivate"
(status 7)
Installation aborted.
I then tried to flash back to the CM7 nightly and got the same error.
When I go to about phone in setting its says my device is an i9000. I know this has something do with the first ICS rom I flashed. Possibly the errors have something to do with my kernel or bootloader??
I know roms pretty well, but I have a very vague knowledge of kernels and bootloaders. I know, I know, I shouldn't be playing around with this stuff if I don't know 100% what I'm doing, but hey I got learn somehow. My apologies if there is already a solution to this posted in this forum, I tried to search but I'm not exactly sure what I'm looking for.
Any Help? Thanks!
I would suggest doing a full wipe and installing the latest nightly of CM7. Once installed reboot but not all the way. Pull the battery on the kernel splash screen and reboot into recovery and flash CM7 again. Reboot fully into the rom this time.Once you get that far restart the phone in CWM and flash build 3 of the pre CM9 rom. Do the same as above and flash it twice. After flashing the second time flash GAPPS. Then reboot. You should be all set. This is the process that worked for me.
Sent from my SGH-I897 using xda premium
I did the wipe data/factory reset, wiped the cache partition and the dalvik cache. I try to flash the CM7 nightly and I get the same getprop error and installation aborted everytime.
Am I missing something?
Ok I think I figured it out. I have to one-click back to stock, flash CM7, then flash teamhacksung's build.
Or I believe you can go into your build.prop and change everything to i897 and or captivatemtd. Part of the issue I think is that the other ics does not use the datadata partition because that is also part of the issue I had when switching either back to my nandroid backup of cm7 or to team hack sung ICS. I COULD BE WRONG HERE.
I went into cwm, advanced, formatted system, data,cache, and also tried to format datadata. Then i went back and ran wipe data/factory reset. Next flashed team hacksungs ICS twice before trying to boot it up.
Sent from My KickAss CM7 Captivate
Ok, so I edited build.prop and changed it all to SGH-I897 and captivatemtd. Now when I look at about phone it shows that I have a SGH-I897, but I still get the same getprop error when I attempt to flash teamhacksungs rom or CM7.
When I go to the advanced menu of my recovery (which is CWM-based Recovery v5.5.0.0), the only options available are: Reboot recovery, wipe dalvik cache, wipe battery stats, report error, key test, show log, partition SD card, and fix permissions.
There are no options for formatting system or datadata in my advanced menu.
So I guess that means I have one-click back to stock. I was trying to avoid that but oh well.
Unless someone has another idea maybe?
Related
Hi all,
So after I flash a new ROM (MIUI MGv2/RC8vC/MGv1) I always hang at the Galaxy S GT-I9000 screen - the first boot screen.
I am wondering what this means? is it a corrupt file, something wrong with my internal sdcard, ROM not installed properly?
Please help,
Thanks.
some times a wipe from recovery will help and goes back to normal boot
many issues may cause this problem for instance if framework.jar or android.policy.jar or... have some bugs , will happen like that
Hi,
By wipe you mean clearing the formatting system, data, cache, dalvik cache and a factory reset? I ask this because the MIUI roms are not are non-wipe and the instructions recommend you to format those places before install (which I did).
I mean wipe cache partition from recovery. just try it and ley us know if it works
Well I just tried again but it doesn't work because I can't access recovery mode. It hangs at the Galaxy S screen and doesn't move from there so I'm wondering why because if I can't fix the bad install then I can't access the recovery mode and can only flash.
if recovery dont work BUT download mode does,
start the whole process again, flash back to stock froyo with froyo bootloader.
did you come to MIUI from Gingerbread ??
Well i've done the process like 10 times, nearly every single time from froyo (JPU,JS5,Ezbase 2.0) and I also went from 2.1 to 2.2 and then to MIUI. The other times I have tried coming from CM7 as CM7 works.
well i have a similar issue but in my case i just wiped my data thru cwm on darky v8 xxjpy..
now i get boot loops,any idea what should i do??
i know this is not exactly the thread but if i get my answer it'll save me from starting a new one..
When I got bootloops i normally reflashed. If you don't have data it will probably work?
I assume you have data as your on Dark v8 when V9 is out?
i dont understand by have data??
i flashed v9.5 but went back to v 8 few months ago..
today i just wiped/factory reset my phone using cwm and it was succesful but now its bootloops and vibrations..
i never wiped my phone before and only have flashed using cwm,never used odin for flashing roms!!
OH I see, by data i meant personal data that you might want to back up...I'm not to most knowledgeable but I know how to flash roms. I reckon you should try to flash V8 it again if you can enter recovery.
Greetings fellowmen!!
Recently i thought of rooting my nexus 1. So i did some research and found out that the easiest way to do it was by unlocking the bootloader installing a custom recovery (I did Amon Ra) and then wiping the data\factory settings and flashing the cm 7.1 zip. So i did all the above and there you go....I had an n1 running cm 7.1 smoothly but then after a few hours it starts to piss me of. The problem is that whenever i lock the homescreen with the power button and wake it up again it just displays the main homescreen and does nothing i cannot navigate to the left or right homescreen cannot open app drawer in short it just hung up there doing nothing. I had to take out the battery atleast 15 times. I rebooted my device and it kept on giving me the same problem.
So then i reflashed cm 7.1 by wiping the data and factory settings and installing it again. But still it gave me the same problem. So then i thought of flashing 7.0.3 version instead and surprisingly that works like a charm. So is it the mod thats buggy or is it my phone.
One more question. I have the stock 2.3.4 gingerbread rom which i got from here!!
Code:
http://forum.xda-developers.com/showthread.php?t=1061648
This one in particular-
GRK39F OTA (stock vanilla - odexed, unrooted):
MD5: 35C8B4B9FD22DD4CA19C5D026E74411D
So to install this rom do i have to install it the same way i did cm by wiping data/factory settings and then installing flash from zip or is there any other way to do it ?
Thanks in advance for taking out valuable time and reading my long problem!!
I am running the latest version of CM 7.1 that was released within the last week or so without any issues. Got it from here. http://download.cyanogenmod.com/?type=stable&device=passion
Before that I was running the RC for 7.1. One thing to try it wiping multiple times before flashing. I assume you are running Amon RA 2.2.1, which is the latest. I have never had a problem with that recovery, however I flashed my ROM with this recovery. So far I think I like it better than Clockwork and Amon.
http://forum.xda-developers.com/showthread.php?t=1291970
As for installing other ROMs yes you do flash them the same way you flashed CM.
So are you saying that it was the recovery that was causing the problem?
Yes I am using the latest Amon Ra 2.2.1 version.
I also got the rom from that link.
And can you explain whats the difference between all these recoveries?
Thanks for replying!
I am not saying it is the recovery, I highly doubt that is the problem. I was just comparing differences. There does not seem to be much difference in the recoveries for what you are trying to do. The recovery I am running is a fairly new one that I just wanted to test out. I do think I like it better than the others.
First thing I would do is wipe 3, 4 or 5 times before flashing. I have had rare occasions where a single wipe would not do it for me. Also have you verified the Checksum of the CM download? Does recovery say it installed successfully? I have also had error installing a ROM in recovery but then had the phone still load the ROM.
Yes i did check the md5 checksums and they match perfectly. Though i did wipe it out only one time so maybe that could be the problem. I think i should get clockworkmod and wipe it through that and then flash cm 7.1. Amon RA doesnt really give us the option of wiping the system partition. right?
Correct Amon Ra does not have an option to format system partition. It's recommend you also wipe system when coming from a different ROM.
Try this file by temasek's, format-signed.zip
http://www.mediafire.com/?8vbd13b440coxx6
just flash it in recovery and it will clean everything, now you can flash CM7.1 again
Are you sure you can't wipe the system with Amon? I remember having that option, but it's been several months since I have used that recovery. Kind of makes me want to flash it to find out.
Before flashing a different ROM I always wipe system, cache and dalvik cache. It is definitely important to wipe the system before flashing a new ROM. I'm sure that is where your problem lies.
No, ClockworkMod has it, but Amon_RA doesn't. Supposedly it is in the works for the next version, but that was a long time ago when I heard that (probably back when v3 for clockworkmod came out).
I did a nandroid backup and flashed the format zip file and then flashed cm 7.1 and its giving me the same problem!!
I had to restore and go back to 7.0.3
Why is this happening
Edit: I also wiped the dalvik cache and factory reset it also but still it just freezes!!
Any advise?
Have you tried downloading the file again maybe form another location I doubt this is the problem but sometimes it's something you don't expect.
You could try from here http://wiki.cyanogenmod.com/index.php?title=Latest_Version
But how does it matter I checked the md5 checksum and it matches!!
Why not stay on CM7.0.3 theres not much difference between the 2
if you dont want to i suggest to try to flash Clockwork recovery and do a full wipe then reflash CM7.1
But still I want to see how 7.1 is!
The main point here is to upgrade and not taking the alternative of staying at the older version!
Please guys any help would be appreciated!!
Doesn't CM7 need clockworkmod 3.x?? Try to flash CWM3.x over Amon if you can get your hands on the flashable zip or if you can get into a working rom, use romManager to switch from amon.
thealphamale05 said:
Doesn't CM7 need clockworkmod 3.x?? Try to flash CWM3.x over Amon if you can get your hands on the flashable zip or if you can get into a working rom, use romManager to switch from amon.
Click to expand...
Click to collapse
Make no different if you use amon Ra or CWM. I would definitely stay away from cwm 3.x or higher if you're using sd-ext
Looks like Ill have to stay with 7.0.3 there doesnt seem to be a solution!!
Hi,
I have many times tried to flash CM7, but always happens weird thing.
I have stock 2.3.5 XXJVS with Semaphore 2.5.0 kernel
1.I boot into CWM
2.I wipe cache then wipe data/factory reset then i go advanced and choose wipe Dalvik cache
3.Choose .zip from sd card
4.I choose update-cm7.1.0-GalaxyS-signed.zip
5.My phone flashes it
6.It reboots
7.Normal Galaxy S GT-i9000 then Galaxy S
Cyanogen Mod
8.It goes to recovery and posts text very fast then reboots again
9.It repeats everything what it does from section 7.
Im very confused so please help!
Have you tried flashing it again?
redo step 3 and onwards,
sometimes you just need to flash twice.
It seems like a corrupted download... Are you flashing from internal or external? Have you mounted before?
i tried to flash from internal
What version of CWM recovery do you have? Maybe flash a different ROM just to update CWM, and then flash the rom you want?
I had the same, or atleast a similar problem whilst trying to flash CM9. I fixed it by flashing the rom again.
You also might want to redownload the file incase it's corrupt.
i have CWM 5.0.2.7 and i downloaded the CyanogenMod file again so i try to flash it again
Any luck with your efforts this far?
yes, i succesfully installed CM9 about 3 months ago.
I'm not sure which build it was but it was the newest build
Hello all,
I have an issue with latest CWM 5.5.0.4 recovery. It says the following error:
E:Error in /cache/recovery/last_log
(Read-only file system)
and other similar errors:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
and I'm unable to reflash GalaxianSoup ROM nor restore the original backed up 3.2 factory rom.
What actually happened ?
Once bought, I managed to root, flash CWM 5.5.0.4 recovery and install the latest GalaxianSoup ROM. Everything based on the guides in development forum and successful (all latest versions). All cool! System was working fine.
Yesterday, I was using tablet, installed few apps, nothing special and later left tablet turned on and charging. When I came back, it was turned off. Okay, tried to turned on, but the system never booted and always looped (seeing only Google logo and moving gears). I rebooted into recovery and noticed the error (see above).
Now, I'm basically unable to do anything. I tried to wipe data, cache and Dalvik cache several times, and reflash GalaxianSoup again (Galaxian + Gapps) or also restore the 3.2 system backup that I've made (always fails).
I've read on some other forums that it might have something to do with damaged SD card partition or something.
I'm out of ideas. Can anyone help me pleeeeease?
EDIT: I've got european Samsung Galaxy Tab 8.9 16GB WIFI version.
EDIT: I must correct myself. After rolling back to factory rom, I was experiencing the same issues, seems there some hardware issue. I sent the tablet back for repair, seems now it had nothing to do with GalaxianSoup. No need to worry, keep up the good work.
whiplash84 said:
Hello all,
I have an issue with latest CWM 5.5.0.4 recovery. It says the following error:
E:Error in /cache/recovery/last_log
(Read-only file system)
and other similar errors:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
and I'm unable to reflash GalaxianSoup ROM nor restore the original backed up 3.2 factory rom.
What actually happened ?
Once bought, I managed to root, flash CWM 5.5.0.4 recovery and install the latest GalaxianSoup ROM. Everything based on the guides in development forum and successful (all latest versions). All cool! System was working fine.
Yesterday, I was using tablet, installed few apps, nothing special and later left tablet turned on and charging. When I came back, it was turned off. Okay, tried to turned on, but the system never booted and always looped (seeing only Google logo and moving gears). I rebooted into recovery and noticed the error (see above).
Now, I'm basically unable to do anything. I tried to wipe data, cache and Dalvik cache several times, and reflash GalaxianSoup again (Galaxian + Gapps) or also restore the 3.2 system backup that I've made (always fails).
I've read on some other forums that it might have something to do with damaged SD card partition or something.
I'm out of ideas. Can anyone help me pleeeeease?
EDIT: I've got european Samsung Galaxy Tab 8.9 16GB WIFI version.
Click to expand...
Click to collapse
Flash your recovery again through odin..
Then reflash your galaxian soup..
If not success, use odin and flash stock rom..
Dont forget backup your file from sdcard just in case if you need reset factory..
suwandiapr said:
Flash your recovery again through odin..
Then reflash your galaxian soup..
If not success, use odin and flash stock rom..
Dont forget backup your file from sdcard just in case if you need reset factory..
Click to expand...
Click to collapse
Flashing of CWM didn't help to fix the issue, installing of GalaxianSoup didnt work at all (corrupted ZIP file error...)
Thanks God, reflashing of stock ROM via Odin did work, tablet is up and running. GalaxianSoup is definitely not stable enough yet, I'll stick to the stock rom fora while. Thank you!
whiplash84 said:
Flashing of CWM didn't help to fix the issue, installing of GalaxianSoup didnt work at all (corrupted ZIP file error...)
Thanks God, reflashing of stock ROM via Odin did work, tablet is up and running. GalaxianSoup is definitely not stable enough yet, I'll stick to the stock rom fora while. Thank you!
Click to expand...
Click to collapse
Galaxian Soup is more then stable enough. Bad flashes happen and you just said you had it up and running.
bdfull3r said:
Galaxian Soup is more then stable enough. Bad flashes happen and you just said you had it up and running.
Click to expand...
Click to collapse
To be honest, it is kind of stable, but not enough, hence the beta label. Some further optimizing will be done once the team has ICS source. In my experience, it was stable, but sometimes it would turn off when in fell into Deep Sleep state. Now, the AOKP milestone 5 is giving me issues with the screen rotation. I've experienced both sides, AOSP and AOKP in their latest versions. Obviously there is more room for improvement, but I'm afraid the team is kinda stuck without source. They've done miracles without source though.
Hi everybody, I'm quite scary about what I've done today with my tab.
1. I was running under CM 9.1 stable and everything was fine.
2. I backed up my data using ROM Manager and tried today a nightly build of CM 10 from get.cm. I installed it from CWM as written in Cyanogen wiki. Before install I was warned about partition format that wasn't the same as previsouly, and I was asked to choose the update.zip again to enable the ROM flashing to start. CM 10 booted correctly, and it ran very well at first. Then I chose to install Gapps through CWM, the same I did for CM 10.
3. After rebooting, I experienced a bug: the included keyboard kept crashing and was then unusable. I decided then to restore my backup of CM 9 through CWM.
4. I did not encounter any trouble restoring the backup to my old CM 9. But I had no radio, no IMEI, no baseband etc.. in "settings/about the device" and at this point I didn't know that this was because "/radio" wasn't mounted.
5. Now I don't remember what I exactly did but I try wiping caches, restoring again, reinstalling CM 9 stable, reinstalling CM 10 stable, restoring my backup again, flashing the Kernel using Hemsfall but what I remember is:
- I first had problems with /cache
- After that I had the "E:format_volume: "make_ext4fs failed on /cache" message
- My tab reboots if I try to install CM9 stable
- I tried to install a fresh firmware through http://forum.xda-developers.com/showthread.php?t=1133590 but I get stuck at hidden.fs
Now my tab can only boot to CWM or download mode, and whether I choose to flash to CM9 or CM10 I get the message:
assert failed: getprop("ro.product.device")== "galaxtab"...
E: Error in /sdcard/cm-10-nightly....zip
(Status 7)
Installation aborted
I don't know what to do now, and I'm quite desperate right now, please help me to get rid of that "make_ext4fs" error. I'm really afraid.:crying:
When you update to cm10, the mtd partition scheme changed to a new one. Nandroid restore won't work until the partition is made back to the same as when backup was taken.
To be able to run cm again, you need to restock to GB using Odin,
then flash overcome kernel to get cwm.
Only the kernel, not the ROM.
Then use cwm to install cm,
then restore from nandroid.
Follow my signature for overcome guide.
Get GB stock safe v5, the PDF guide, and the overcome kernel.
Jump to page 7.
Sent from my GT-P1000 using xda app-developers app
Thanks you very much, be blessed, it works perfectly using your solution. I felt really really bad, thank you so much!
you are welcome.
You may want to try CM10 again.
Make sure you flash gapps for cm10 only, not gapps for cm9 or cm10.1
It shouldn't be as unstable as you said.