Related
So I decided to root my phone, following everything here (I am completely noob at this):
http://forum.xda-developers.com/showthread.php?t=694572
I did screw up on step 10 where instead of doing a "Flash zip from sdcard" I did a reboot and it booted into the original system. So I went through the process again from step one and did everything right this time.
I don't know if that broke the root or not, but I cannot flash anything on the phone, mainly new ROM.
When I try to wipe it will give me this error:
"error wipe dalvik via adb"
"error wipe ext via adb"
If I go and flash the ROM anyway, it will get stuck at the splash screen forever...
Fresh Rom 2.3.3 will give me the endless droid dance
Cyanogenmod 6.0.0 Test 4 For Hero CDMA will be stuck at the "X" animation
I can pull out the battery stuff and it still doesn't work. I am able to just restore my nandroid backup and the phone will work then.
Does anyone knows what did wrong? Or how I can get this to work?
PS: I have the "Superuser Permission" ninja is my apptray so I assume I rooted it correctly...
Make sure your battery its charged when flashing. Re-download whatever files you want to flash, sometimes they get corrupted during download. Which recovery are you using?
Sent from my Hero CDMA using XDA App
also if when your in the recovery image for the first time or you have been in there for awhile i get those errors but usually a shut down and the boot back into recovery works for me
I managed to get this working with Rom Manager after restoring the nandroid to the Sprint ROM. Running on Fresh 2.3.3 now, thanks for the reply!
Using Clockwork, I was able to get Cyan6 on my phone but whenever I opted to include Froyo GApps in the download ROM part, I got "corrupt zip" error multiple times. Now I am running Cyan6 just fine , minus the Market et al. Any ideas?
You can get the current version of the Gapps add-on here:
http://forum.cyanogenmod.com/files/file/119-google-addon-hdpi-20101008/
Flash the downloaded zip either from ROM Manager or from custom recovery.
cmstlist said:
You can get the current version of the Gapps add-on here:
http://forum.cyanogenmod.com/files/file/119-google-addon-hdpi-20101008/
Flash the downloaded zip either from ROM Manager or from custom recovery.
Click to expand...
Click to collapse
ROM Manager / Custom Recovery, unable to recognize zip. Says (bad). However, on going back to ROM Manager, was able to download and flash. Thanks for the lead though
I did notice that reboots .... haphazard I should say are happening on device now. It's fast too, {compared to stock} esp when I try to download certain apps from market....will download fine, but when the installing dialogue appears on the menu bar, it reboots. Thoughts..
No idea, sounds like something is amiss. Is it possible you have an HBOOT version that isn't playing nice with the method you used to flash custom recovery and CM6? Are you running a Froyo radio version that is compatible with CM6?
OH - and I almost forgot - did you wipe data/cache when you installed CM6? If you didn't then you may find that CM6 boots up but acts very strange and would give you a world of problems.
Wiped data and cache and that did it. Thanks.
Sent from my Nexus One using XDA App
A few weeks ago I flashed the Cognition V2.2 ROM and everything was fine until it started getting twitchy a few days ago. I tried to use the ROM Manager to restore the backup that was created during the flash but I keep getting the same error message and the phone does not seem to go into the Clockwork Mod Recovery but stays in the Android system recovery. The message says that the whole-file signature has failed to verify and that the installation was aborted. Does anyone have any idea how I can get my phone back to normal?
gtcochran said:
A few weeks ago I flashed the Cognition V2.2 ROM and everything was fine until it started getting twitchy a few days ago. I tried to use the ROM Manager to restore the backup that was created during the flash but I keep getting the same error message and the phone does not seem to go into the Clockwork Mod Recovery but stays in the Android system recovery. The message says that the whole-file signature has failed to verify and that the installation was aborted. Does anyone have any idea how I can get my phone back to normal?
Click to expand...
Click to collapse
Common knowledge that the version of Cognition you are running is not supported by ROM Manager, it is 3e recovery and Clockwork needs 2e. You can update to the newer Cognition which has 2e recovery. I recommend you read the facts sheet befor flashing, the method you should use is Odin one click back to stock http://forum.xda-developers.com/showthread.php?t=731989, then master clear so that nothing is lingering from your previous setup, backup everything from your internal storage to your pc first, this will wipe everything from your internal, replace it after you finish Master clear. you should only replace the update.zip, ClockworkMod and your music, photo's and that stuff. Backup your apps using Titanium Backup.
Here's the link for the new Cognition http://forum.xda-developers.com/showthread.php?t=786532
So I tried what you recommended and got my phone back to the stock condition but I'm still not able to use ROM manager or flash another ROM. After I root the phone I install ROM Manager, flash it to the current edition and then try to reboot into recovery but when it gets to recovery it gives the following error message...
--Installing from package...
Finding update package...
Opening update package...
E:Can't open /cache/update.zip
(bad)
Installation aborted
Also the header of the screen states that I am in Android system recovery <2e>. If I am not mistaken, shouldn't I be in recovery <3e>? If so how do I get there? I've tried flashing the stock Kernel but that didn't work and I even installed the internal betas correctly but no cigar.
gtcochran said:
Also the header of the screen states that I am in Android system recovery <2e>. If I am not mistaken, shouldn't I be in recovery <3e>? If so how do I get there? I've tried flashing the stock Kernel but that didn't work and I even installed the internal betas correctly but no cigar.
Click to expand...
Click to collapse
did you really read Rhi's post?
in order to use rom manager (clockwork mod) you must be using 2e!
my brain hurts from all the lack of searching people in this forum seem to have a problem with
Pirateghost said:
did you really read Rhi's post?
in order to use rom manager (clockwork mod) you must be using 2e!
my brain hurts from all the lack of searching people in this forum seem to have a problem with
Click to expand...
Click to collapse
LOL, +1
Touche, but the error still remains. Does anyone have any positive ideas? Like I stated before, I still cannot put my phone into clockwork mod recovery.
gtcochran said:
Touche, but the error still remains. Does anyone have any positive ideas? Like I stated before, I still cannot put my phone into clockwork mod recovery.
Click to expand...
Click to collapse
so put it in download mode, and use ODIN one click back to stock...then leave it the hell alone....
Like I said, I've already used Odin. Everything is back to stock except for the Kernel and a stock kernel install with Odin doesn't seem to work. Odin says that the install passed but nothing changes on the phone itself. All things considered, the phone is stock but not capable of going into Clockwork Mod recovery.
gtcochran said:
Like I said, I've already used Odin. Everything is back to stock except for the Kernel and a stock kernel install with Odin doesn't seem to work. Odin says that the install passed but nothing changes on the phone itself. All things considered, the phone is stock but not capable of going into Clockwork Mod recovery.
Click to expand...
Click to collapse
When you go into stock recovery now is it version 2e or 3e?
gtcochran said:
Like I said, I've already used Odin. Everything is back to stock except for the Kernel and a stock kernel install with Odin doesn't seem to work. Odin says that the install passed but nothing changes on the phone itself. All things considered, the phone is stock but not capable of going into Clockwork Mod recovery.
Click to expand...
Click to collapse
if you used the one click back to stock then you are on the stock kernel.....what makes you think you are not on the stock kernel?
The recovery is 2e
I believe that the kernel is not stock because when I look at the phone information it says that the kernel is
2.6.29
[email protected] #2
I'm not sure that it is stock or not but my gut tells me that it isn't.
gtcochran said:
The recovery is 2e
I believe that the kernel is not stock because when I look at the phone information it says that the kernel is
2.6.29
[email protected] #2
I'm not sure that it is stock or not but my gut tells me that it isn't.
Click to expand...
Click to collapse
Rom manager will work just fine with 2e recovery. Just delete any update.zip files you have in your home directory - then open rom manager and reflash clockworkmod the cappy - then you should be good to go.
As for whether or not that is the stock kernel I am not sure, but how can you tell just by looking at it if you don't know which kernel is the stock one?
I've mounted my internal and external sd cards and removed any updates but it still gives the same error. After I used the odin one-click to flash the stock rom I used the master clear as recommended. Now, if I am not mistaken, shouldn't that erase all of my user data? I reinstalled my espn app so I could follow my football team and the app still remembered my preferences and favorites. This makes me think that the master clear did not finish the job. Thoughts?
gtcochran said:
I've mounted my internal and external sd cards and removed any updates but it still gives the same error. After I used the odin one-click to flash the stock rom I used the master clear as recommended. Now, if I am not mistaken, shouldn't that erase all of my user data? I reinstalled my espn app so I could follow my football team and the app still remembered my preferences and favorites. This makes me think that the master clear did not finish the job. Thoughts?
Click to expand...
Click to collapse
Master clear should've done that. If you are restoring your apps and settings using Titanium Backup then you are restoring user data which you should not do.
When you Master Clear is your device on and on the home screen, it needs to be. Don't Master Clear in Recovery mode or Download mode or it does nothing. Also you need to have debugging on.
2.6.29
[email protected] #2
That is the stock kernel. Just so you know if you are running stock with root you can simply place the update.zip from the Clockwork folder, you should have backed up before flashing and Master clear, back into your internal. ClockworkMod does fail on first attempt to flash sometimes, it happenned to me the first time I flashed it, the second time worked like a charm. Are you rooted? You need root to use ROM Manager and debugging should be on.
gtcochran said:
I've mounted my internal and external sd cards and removed any updates but it still gives the same error. After I used the odin one-click to flash the stock rom I used the master clear as recommended. Now, if I am not mistaken, shouldn't that erase all of my user data? I reinstalled my espn app so I could follow my football team and the app still remembered my preferences and favorites. This makes me think that the master clear did not finish the job. Thoughts?
Click to expand...
Click to collapse
After you deleted the update.zip then opened rom manager and flashed clockworkmod it should of put a new update.zip on your phone in your home directory - can you confirm that this is the case?
Also you may not have had a successful master clear - you may want to do it again then redo odin3 one click. Also if I am remembering correctly I believe you have the option to clear cache or user data or both in stock recovery you may want to try that as well.
It all works now. The issue was with the master clear. I guess that I did try to run it in the download mode. Thanks a million guys, i really appreciate it.
Maybe I was a bit premature on that. ROM Manager works beautifully but I cannot install updates or flash a custom ROM. The Manager was able to backup the system correctly and enter clockwork mod recovery but it cannot install the update. If the update is on the internal SD it says that...
E:Can't open /sdcard/update.zip
(bad)
and if the update is on the external SD it says that there is no such file or directory. Am I doing it wrong or is there still an underlying issue?
gtcochran said:
Maybe I was a bit premature on that. ROM Manager works beautifully but I cannot install updates or flash a custom ROM. The Manager was able to backup the system correctly and enter clockwork mod recovery but it cannot install the update. If the update is on the internal SD it says that...
E:Can't open /sdcard/update.zip
(bad)
and if the update is on the external SD it says that there is no such file or directory. Am I doing it wrong or is there still an underlying issue?
Click to expand...
Click to collapse
/sdcard/update.zip should only boot into clockwork recovery from stock recovery or boot to stock recovery from clockwork recovery if you flashed clockworkmod correctly from rom manager - and so long as you are not renaming any other files as update.zip after you flash clockworkmod recovery.
Which custom rom are you attempting to install?
I got it. The zip file was corrupted. Now, should I be able to boot into normal clockwork mod recovery with the Cognition 2.2 Beta 7 cuz when I try clockwork recovery it boots into normal recovery? I'm still a little hazy about all this.
gtcochran said:
I got it. The zip file was corrupted. Now, should I be able to boot into normal clockwork mod recovery with the Cognition 2.2 Beta 7 cuz when I try clockwork recovery it boots into normal recovery? I'm still a little hazy about all this.
Click to expand...
Click to collapse
When you first boot into recovery it should be stock recovery. While in stock recovery when you select reinstall packages it will reboot into clockwork recovery - if you flashed clockworkmod recovery correctly from rom manager and it put the appropriate update.zip into your home directory.
And just to note: don't be renaming any files as update.zip if you are using clockwork recovery to flash something.
Hello Folks,
First I have to say that I watched the noob video and read everything about E:Error in /mnt/sdcard/cm-10.0.0.-galaxysmtd.zip (Status 7) on this forum and what google gave me.
My situation:
PC OS is Windows 7 64bit (if someone needs to know)
Phone:
Samsung Galaxy S GT-I9000
SSN: I9000GSMH
What happend:
I bought a used phone about two months ago with latest installed stock rom 2.3.5 it is. Then i downloaded cm-10-20121126-NIGHTLY-galaxysmtd and followed the instructions on wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Full_Update_Guide. I installed CWM with Heimdall Suite. Everything worked well.
Today I decided to install a newer version of CM, I downloaded the cm-10-20121210-NIGHTLY-galaxysmtd and cm-10.0.0-galaxysmtd and copied them both on the phone memory. I turned off the phone and turned it on in recovery mod, and I got the recovery mode that was on cm-10-20121126-NIGHTLY-galaxysmtd installed. It wasn't the standard CWM that I installed with Heimdall Suite. I wiped with it data and cache and installed cm-10-20121210-NIGHTLY-galaxysmtd and then rebooted the phone. But the phone got stuck and didn't want to reboot. So i tried to go to recovery mod again to reinstall the cm-10.0.0-galaxysmtd but the phone couldn't access the recovery mod anymore.
After that I reinstalled with Heimdall Suite the ClockwordMod Recovery v2.5.1.0 SpeedMod Kernel like the first time I did. and successfully booted to recovery mod and again wiped cache and data and tried to install cm-10.0.0-galaxysmtd when i got the error
This is the image, just copy/paste in address bar.
imageshack.us/f/685/07032008448.jpg
So, now my phone has no OS installed.
There are some other issues too, I can't mount my external sd card in CWM, why, I don't know, so I only have cm-10-20121210-NIGHTLY-galaxysmtd and cm-10.0.0-galaxysmtd on my phone memory to install.
I would really really like if someone could help me to solve my problem, I have no other phone. And please when you tell to install something give me the needed link because I really downloaded a lot of things that didn't work.
adobih said:
Hello Folks,
First I have to say that I watched the noob video and read everything about E:Error in /mnt/sdcard/cm-10.0.0.-galaxysmtd.zip (Status 7) on this forum and what google gave me.
My situation:
PC OS is Windows 7 64bit (if someone needs to know)
Phone:
Samsung Galaxy S GT-I9000
SSN: I9000GSMH
What happend:
I bought a used phone about two months ago with latest installed stock rom 2.3.5 it is. Then i downloaded cm-10-20121126-NIGHTLY-galaxysmtd and followed the instructions on wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Full_Update_Guide. I installed CWM with Heimdall Suite. Everything worked well.
Today I decided to install a newer version of CM, I downloaded the cm-10-20121210-NIGHTLY-galaxysmtd and cm-10.0.0-galaxysmtd and copied them both on the phone memory. I turned off the phone and turned it on in recovery mod, and I got the recovery mode that was on cm-10-20121126-NIGHTLY-galaxysmtd installed. It wasn't the standard CWM that I installed with Heimdall Suite. I wiped with it data and cache and installed cm-10-20121210-NIGHTLY-galaxysmtd and then rebooted the phone. But the phone got stuck and didn't want to reboot. So i tried to go to recovery mod again to reinstall the cm-10.0.0-galaxysmtd but the phone couldn't access the recovery mod anymore.
After that I reinstalled with Heimdall Suite the ClockwordMod Recovery v2.5.1.0 SpeedMod Kernel like the first time I did. and successfully booted to recovery mod and again wiped cache and data and tried to install cm-10.0.0-galaxysmtd when i got the error
This is the image, just copy/paste in address bar.
imageshack.us/f/685/07032008448.jpg
So, now my phone has no OS installed.
There are some other issues too, I can't mount my external sd card in CWM, why, I don't know, so I only have cm-10-20121210-NIGHTLY-galaxysmtd and cm-10.0.0-galaxysmtd on my phone memory to install.
I would really really like if someone could help me to solve my problem, I have no other phone. And please when you tell to install something give me the needed link because I really downloaded a lot of things that didn't work.
Click to expand...
Click to collapse
you having the wrong CWm installed, you can go to this link to download the cf-root kernel. http://forum.xda-developers.com/showthread.php?t=788108 hope this will help .
BTW when flashing JB from GB you need to flash CM9 then follow by CM10, if you can try flash it from GB 2.3.6 (E.g xxjvu)
i try flashing JB from GB is work if i flash twice but i got missing IMEI. so i suggest you following this step to flash.
GB(stock rom with ROOT) - ICS(CM7) - JB(CM10)
Samtan4326 said:
you having the wrong CWm installed, you can go to this link to download the cf-root kernel. http://forum.xda-developers.com/showthread.php?t=788108 hope this will help .
BTW when flashing JB from GB you need to flash CM9 then follow by CM10, if you can try flash it from GB 2.3.6 (E.g xxjvu)
i try flashing JB from GB is work if i flash twice but i got missing IMEI. so i suggest you following this step to flash.
GB(stock rom with ROOT) - ICS(CM7) - JB(CM10)
Click to expand...
Click to collapse
First off all thanks for helping.
I tried this one:
CF-ROOT-4.4-I9000BGJW5-1187857
CF-Root-4.4-I9000BOJW6-CL1177078
CF-Root-JP6-v1.2-Busybox-1.17.1 (this one didn't want to start recovery at all)
CF-Root-XX_OXA_JW4-v4.4-CWM3RFS
all I got from all of them is this
imageshack.us/f/805/08032008449.jpg (copy link to address bar )
Member Chainfire said "THIS IS NOT A ROM - it is only a kernel. You need to have a firmware already on your device"
I don't know really what that means. Probably that I have to install something else too, but what ?
Please can you tell me ?
And which of these CF-Roots is the right one, or the newest one, or how do recognize that ?
Thanks everyone who helps me.
eba
Well, I solved my problem, now i have cm-10.0.0-galaxysmtd ROM installed. If someone has this problem, this is one way how to solve it (but doesn't mean it's the best one).
If you have no ROM installed on your I9000 and don't know which kernel to use, try this way:
Watch this video on YouTube that user "Puggered UK" uploaded:
youtube.com/watch?v=iRnH13sRAIc
- You can skip to 1.52 because you don't have any ROM on your phone, and download the EZ Odin package from the link in the About section (4shared.com/archive/TuHUfVjA/EZOdin.html).
- Start EZ Odin, put the PIT, PDA, PHONE and CSC file in the right box, connect your phone in download mode to the PC and press START, and wait till the process is complete.
- After a while you should have Android 2.3.? installed on your phone.
- Update Google market to Google play, then update ROM Manager, and start ROM Manager. Choose to Flash Clockwork Mod Recovery, choose your phone and flash it.
- Copy on your internal sd memory cm-10.0.0-galaxysmtd that you downloaded from CyanogenMod web site.
- Restart your phone in Recovery mod, wipe data/cache, and install cm-10.0.0-galaxysmtd from internal sd card.
- Then, when it's done restart the phone, and do the last step again in Cyanogen CW recovery.
- After it's done, restart the phone and you will have CM 10 on your phone installed.
Or just watch the video and you will se what to do.
adobih said:
Well, I solved my problem, now i have cm-10.0.0-galaxysmtd ROM installed. If someone has this problem, this is one way how to solve it (but doesn't mean it's the best one).
If you have no ROM installed on your I9000 and don't know which kernel to use, try this way:
Watch this video on YouTube that user "Puggered UK" uploaded:
youtube.com/watch?v=iRnH13sRAIc
- You can skip to 1.52 because you don't have any ROM on your phone, and download the EZ Odin package from the link in the About section (4shared.com/archive/TuHUfVjA/EZOdin.html).
- Start EZ Odin, put the PIT, PDA, PHONE and CSC file in the right box, connect your phone in download mode to the PC and press START, and wait till the process is complete.
- After a while you should have Android 2.3.? installed on your phone.
- Update Google market to Google play, then update ROM Manager, and start ROM Manager. Choose to Flash Clockwork Mod Recovery, choose your phone and flash it.
- Copy on your internal sd memory cm-10.0.0-galaxysmtd that you downloaded from CyanogenMod web site.
- Restart your phone in Recovery mod, wipe data/cache, and install cm-10.0.0-galaxysmtd from internal sd card.
- Then, when it's done restart the phone, and do the last step again in Cyanogen CW recovery.
- After is done, restart the phone and you will have CM 10 on your phone installed.
Or just watch the video and you will se what to do.
Click to expand...
Click to collapse
hey,
had that problem too, yesterday. will try your suggestions later and report back!
hope it helps...
Grz
beckzz said:
hey,
had that problem too, yesterday. will try your suggestions later and report back!
hope it helps...
Grz
Click to expand...
Click to collapse
Well, I help you as much as I can and know, just write me where you stuck. And if you have some difficulties explaining it in English, dann kannst du mir auch auf deutsch schreiben, das verstehe ich auch
I had this status 7 thing 2 yesterday while installing cm10. It also seemed I couldnt get into recovery. What I had to do is flash the zip 4 times. First time it got stuck at boot.
So I took battery out & try to get in to recovery (volume up+home button+power button & -->release buttons the moment u see bootanimation<--) but it started bootlooping/got stuck again.
So I took battery out again, did the 3 button combo for the second time & I waited a little longer, a minute maybe 2 & it went to recovery. (I guess the first time it didnt went straight to recovery like it normally does, I wasnt patient enough). If not getting into recovery with waiting the first time just try to keep getting in recovery with 3 button combo & wait a couple of minutes. Eventually it does. I had the same thing 2 months ago coming from jb-->ics-->cm10, thats how I remembered.
Didnt wipe a thing just went straight to the zipfile & flashed it in total 4 or 5 times till it said install completed on the screen. Didnt wipe nothing in between the flashing
Then flashed gapps & voila
Donovan662 said:
I had this status 7 thing 2 yesterday while installing cm10. It also seemed I couldnt get into recovery. What I had to do is flash the zip 4 times. First time it got stuck at boot.
So I took battery out & try to get in to recovery (volume up+home button+power button & release buttons the moment u see bootanimation) but it started bootlooping/got stuck again.
So I took battery out again, did the 3 button combo for the second time & I waited a little longer, a minute maybe 2 & it went to recovery. (I guess the first time it didnt went straight to recovery like it normally does, I wasnt patient enough)
Didnt wipe a thing just went straight to the zipfile & flashed it in total 4 or 5 times till it said install completed on the screen
Then flashed gapps & voila
Click to expand...
Click to collapse
I tried like hundred times or more, but every time with the same result and I also tried with different kernels without success. Maybe some other error caused your status 7 error than mine. But anyway, it's always good to try all possibilities to resolve the problem.
Haha I went crazy not getting into recovery 2 months ago I did it at least 15 times till it eventually got into recovery. Weird cuz I released it the moment I saw cyanogen boot animation. I had to wait a lil longer after releasing so it seems & better timing maybe but only with flashing cm10 from stock. The error was the same tho I saw your picture
Donovan662 said:
Haha I went crazy not getting into recovery 2 months ago I did it at least 15 times till it eventually got into recovery. Weird cuz I released it the moment I saw cyanogen boot animation. I had to wait a lil longer after releasing so it seems & better timing maybe but only with flashing cm10 from stock. The error was the same tho I saw your picture
Click to expand...
Click to collapse
Unfortunately I wasn't that lucky, but I tell you something else. Now I know that no matter what I do and how badly i brick my phone I can always use that method to bring it to life back. So it's kind of final help that works if nothing else works
by the way did you apply sdcard:update zip? Or choose zip from sd card?
Donovan662 said:
by the way did you apply sdcard:update zip? Or choose zip from sd card?
Click to expand...
Click to collapse
I choose zip from sd card because I forgot to rename the file before copying to sd card, and when I lost my bricked my phone it was already to late to rename it. But i don't think that that was the problem, I mean it's just a name string that has no meaning after all.
hey guys,
finally i made it...
thx adobih for your offer, but i'll try to do it in english...think(hope) my english is not that bad
so my problem was the following, slightly different from yours:
i bought a used Galaxy S I9000 for my girlfried as a christmas present cause her Galaxy Ace is the worst Android-phone i ever saw ^^
this "new" Galaxy S has never been rooted before, it never enjoyed a custom ROM - completely stock with 2.2.1 froyo ^^
Here is, what i did to get cm10 stable to work:
1. Updated android to latest official android 2.3.6 with Samsung Kies
2. then i followed the step "Installing the ClockworkMod Recovery" from here
--- ATTENTION: Heimdall 1.3.2 screwed things up (due to a bug i think, only download-mode was available afterwards), use Heimdall 1.3.1 to be safe
3. then i pushed cm 9.1 stable, cm 10.0 stable and latest gapps for 10.0 to the device
4. then i flashed cm 9.1 stable via CWM - an Error occured
5. then i selected "reboot system" in CWM (NOT "reboot recovery"!!)
6. device reboots and starts to install CM 9.1 Stable on its own
7. booted to the now "new" CWM installed by cm 9.1 zip
8. flashed cm 9.1 zip again
8. booted cm 9.1 normally, everything was working fine
9. booted into cwm
10. flashed cm 10.0 zip - an error occured
11. then i selected "reboot system" in CWM (NOT "reboot recovery"!!)
12. device reboots and starts to install CM 10.0 Stable on its own
13. booted to the now "new" CWM installed by cm 10.0 zip
14. flashed cm 10.0 zip again
15. a warning occured "incompatible filesystem, flash again to confirm"
16. flashed cm 10.0 zip again
17. booted cm 10.0 normally, everything was working fine
18. booted CWM again, flashed gapps
19. booted cm 10.0 normally, everything was working fine
I was not able to flash cm 10.0 directly after flashing codeworxs kernel with heimdall. think this is related to changed partition sizes and stuff...
device only booted to CWM again, i was not able to boot the system - bootloop. Once i tried to flash cm10, there was no success when trying to flash cm 9 after that.
i tried it 3-4 times to flash cm 10 directly with no success. i checked md5 sums of the downloaded files, but everything was fine.
the detour with cm 9.1 was the only way to get it to work.
after trying to flash cm10 directly it always screwed something and was not able to get any further.
to start again, i had to go back to stock with odin. For that i used these instructions and files. (its in german, but very well illustrated, so all of you should be able to follow the steps).
When starting from stock, you can follow the steps above and everything should be fine.
took me some hours to figure out the correct order of the steps....
this is a slightly different problem as the one in op, so i decided to provide my solution here.
the heimdall 1.3.2-bug occured with the i9000 of a friend of mine, too. only heimdall 1.3.1 did what it was supposed to.
for all people interested: i decided to flash semaphore kernel for better customization options....running pretty well
EDIT: thx to everybody in this thread posting your experiences, all together it pointed me to the solution.. THX!
Grz
beckzz said:
hey guys,
finally i made it...
thx adobih for your offer, but i'll try to do it in english...think(hope) my english is not that bad
so my problem was the following, slightly different from yours:
i bought a used Galaxy S I9000 for my girlfried as a christmas present cause her Galaxy Ace is the worst Android-phone i ever saw ^^
this "new" Galaxy S has never been rooted before, it never enjoyed a custom ROM - completely stock with 2.2.1 froyo ^^
Here is, what i did to get cm10 stable to work:
1. Updated android to latest official android 2.3.6 with Samsung Kies
2. then i followed the step "Installing the ClockworkMod Recovery" from here
--- ATTENTION: Heimdall 1.3.2 screwed things up (due to a bug i think, only download-mode was available afterwards), use Heimdall 1.3.1 to be safe
3. then i pushed cm 9.1 stable, cm 10.0 stable and latest gapps for 10.0 to the device
4. then i flashed cm 9.1 stable via CWM - an Error occured
5. then i selected "reboot system" in CWM (NOT "reboot recovery"!!)
6. device reboots and starts to install CM 9.1 Stable on its own
7. booted to the now "new" CWM installed by cm 9.1 zip
8. flashed cm 9.1 zip again
8. booted cm 9.1 normally, everything was working fine
9. booted into cwm
10. flashed cm 10.0 zip - an error occured
11. then i selected "reboot system" in CWM (NOT "reboot recovery"!!)
12. device reboots and starts to install CM 10.0 Stable on its own
13. booted to the now "new" CWM installed by cm 10.0 zip
14. flashed cm 10.0 zip again
15. a warning occured "incompatible filesystem, flash again to confirm"
16. flashed cm 10.0 zip again
17. booted cm 10.0 normally, everything was working fine
18. booted CWM again, flashed gapps
19. booted cm 10.0 normally, everything was working fine
I was not able to flash cm 10.0 directly after flashing codeworxs kernel with heimdall. think this is related to changed partition sizes and stuff...
device only booted to CWM again, i was not able to boot the system - bootloop. Once i tried to flash cm10, there was no success when trying to flash cm 9 after that.
i tried it 3-4 times to flash cm 10 directly with no success. i checked md5 sums of the downloaded files, but everything was fine.
the detour with cm 9.1 was the only way to get it to work.
after trying to flash cm10 directly it always screwed something and was not able to get any further.
to start again, i had to go back to stock with odin. For that i used these instructions and files. (its in german, but very well illustrated, so all of you should be able to follow the steps).
When starting from stock, you can follow the steps above and everything should be fine.
took me some hours to figure out the correct order of the steps....
this is a slightly different problem as the one in op, so i decided to provide my solution here.
the heimdall 1.3.2-bug occured with the i9000 of a friend of mine, too. only heimdall 1.3.1 did what it was supposed to.
for all people interested: i decided to flash semaphore kernel for better customization options....running pretty well
EDIT: thx to everybody in this thread posting your experiences, all together it pointed me to the solution.. THX!
Grz
Click to expand...
Click to collapse
More or less I think we both had the same problem, because I also used this link wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Full_Update_Guide and heimdall 1.3.2 for flashing my phone. Just it always finished successfully so I didn't realize it was the root of all problems. I used also then Odin from the youtube video that I posted in a few posts earlier, installed Android 2.3.6 and then installed ROM Manager from Google play, and used the app to flash to ClockworkMod Recovery. After that I installed directly CM10 stable with success, and without CM9 detour.
Hi all, my name is Daniel.
I am using a motorola Milestone A853 for the past one year and never faced any issue while rooting or installing custom roms right upto cm10.
from last two months the milestone has not been working properly. It so happened i had installed CM 9.0.1d and everything worked fine. but once the battery died the phone did not boot up and was stuck on moto boot logo and kept restarting from there. I tried to go into open recovery (fufu minimod) using the X+power key and it goes into recovery but after loading recovery it did not display any options and the other text was red in color and it showed the error failed to load menu.init. I replaced the update.zip file along with the open recovery folder, but still nothing worked. I then tried another open recovery but still open recovery never loaded. Then i SBF'ed the device and went back to stock and was able to use my phone again. But then when i try to root the device again i am not able to root using vulnerable SBF as it does not install though RSDLite shows pass. Then i used superoneclick to root and that did the trick. But still open recovery never installed or load. Luckily androidiani recovery which displayed an error cannot mount but still created the menu and i was able to install custom OS but only cm 7.2.4e and not cm9 nor cm10. I cannot reboot the phone as the phone never starts up. only after clearing dalvik and wiping cache phone boots up. After a certain time now i still cannot install cm7.2.4e as it does not load and gets stuck on custom bootscreen, so i installed MIUI rom which works and starts up but i still can never reboot my phone.
Errors Seen E: cant mount /cache/recovery/command
Kindly help as the phone is just barely working.
Your phone has some serious issues...
How stable it is with stock rom? Maybe You should flash a stock 2.2 and see if you have any issues.
If not, then flash vulnerable recovery and so on, step-by-step.
Maybe it will be easier to locate the source of the problem this way.
Tried Everything
Erovia said:
Your phone has some serious issues...
How stable it is with stock rom? Maybe You should flash a stock 2.2 and see if you have any issues.
If not, then flash vulnerable recovery and so on, step-by-step.
Maybe it will be easier to locate the source of the problem this way.
Click to expand...
Click to collapse
Thank you for your reply. I have tried flashing stock 2.2 and still I cannot reboot the phone without wiping cache and using the reset factory option in stock recovery. Using superoneclick I can root it and install androidiani recovery but I cannot use cm10 or cm 9. after installing cm9 the phone just restarts after cm9 boot screen and after installing cm10 the phone shows the stock android boot screen. cm 7.2.4e installs as well as miui but if battery dies or if I have to restart the phone if it gets sluggish and slow then I cannot...everytime for the phone to boot I have to wipe dalvik and cache for custom roms and for stock roms I have to wipe cache and factory reset.
SO basically I am stuck...have tried changing the sd card, repartitioning the sd card, but nothing worked
Open recovery cannot be used only andoidiani works after popping up some errors.
Kindly help.