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.
Related
Trying to install the Cynogen ICS ROM, and when installing the .zip, it loads the Samsung flash screen with Cynogen, then get the green guy and loads of text for about half a second, then it just reboots. Over and over for about 10 mins. WHat went wrong? What should I do?
It happend the same to me.
I just removed the battery and put it back, entered in CWM and reinstalled the ROM.
Good luck!
I somehow got into a recovery mode, but with the assumption it would all go wrong again, tried to install the .zip Darky rom instead, went through the process and said it worked but then it just went back to the Cynogen loop problem!? I just tried a Restore instead, but I haven't rebooted yet, should I wipe everything again, and try the ICM .zip again?
Yep, just go with the whipe. I hope you did a backup.
OK turns out the Restore failed, so now trying to reinstall ICS .zip again. fingers crossed!
yep backed it up, not that its seems to have helped.
Well now it's stuck in the Galaxy S bootscreen...
that really sucks....did you deactivated the lagfix before running the rom?
If the problem persists you have to run a basic ROM using ODIN.
Yes deactivated the lagfixI can't get into recovery or anything now, except download mode.
Download mode is all you need to run a ROM with Odin.
I recommend Amestris, it is a good ROM, good battery life but the thread in not complete, there are some files missing...for now.
I've put some older ROM on I had, then tried to install ICS again but now when I use Clockwork, and select the file it goes to recovery but I can't select any zip files, just reboot back to this awful old ROM!
I had same issue when I installed ics, what I did that worked was pull battery and go back into cwm, reflashed ics zip and it fully installed that time. Had same experience when flashing cm7 before.
Not getting anywhere with this. I get an option to install zip from sdcard which is where the update is (an where the darky update also is which worked), but there is an option to update from internal SD, which is not where the file is. Is it in the wrong place?
I think you would be best to use Odin 1.3 to flash DarkyROM Ficeto JVT base rom.
are you sure those files are still on your sd card?
The reason you need to pull the battery and reflash the ICS rom a few times is because Samsung ROM (most) have a different partition layout to CM7 based roms (which the ICS port is one).
GL.
Hi,
I'm having a major issue with not being able to flash roms using clockworkmod for some strange reason.
I decided to move from MIUI rom because every time I gave it a chance when new versions came out, it constantly let me down with countless bugs and such. So, I've decided to go back to modified stock ROMs as they seem more reliable.
When I attempted to flash using clockworkmod (that comes with MIUI) it failed to apply the new (non-MIUI) ROM and forced it to go into a bootloop which knackered up going into recovery, so my only other option was to go into download mode and flash a stock ROM (I chose the latest, I9000XXJW4), root it, flash cyanogenmod and try again.
But unfortunately this did not work and now I'm stuck on the stock ROM.
I've taken a video of the exact moment it all goes wrong. Also, below is each step taken of the process.
youtube.com/watch?v=EmZAZ3DeL2U
1) Download Samsung Value Pack (I9000XXJW4) and CF-Root-XX_OXA_JW4-v4.4-CWM3RFS
2) Galaxy S rebooted to download mode
3) Used Odin3 1.85 to apply JW4_JW4_JW4.TAR file to the PDA section. Re-Partition is not checked.
4) Allowed the device to reboot to the home screen.
5) Powered off the device and booted back to download mode
6) Used Odin3 1.85 to apply CF-Root-XX_OXA_JW4-v4.4-CWM3RFS.TAR to the PDA section. Re-Partition is not checked.
7) Allowed the device to reboot to the home screen (The video begins now).
8) Launched the CWM application (with root permissions) and rebooted to Recovery.
9) Wipe data/factory reset selected and confirmed
10) Wipe Dalvik Cache selected and confirmed
11) Format /system selected and confirmed
12) Install zip from SD Card, Choose Zip from sdcard and update-cm-7.1.0-GalaxyS-signed.zip selected and confirmed.
13) Here is an extract from the log that follows before rebooting:
- Finding update package...
- Opening update package...
- Installing update...
- Checking state of BML/MTD...
14) Self-Rebooted
15) Boot-loop
Any help is greatly appreciated!
Thanks,
Andy
when it bootloops it does it cause it just flashed the kernel and its trying to run the stock rom on the cynogen kernel. so pull the battery, put it back in. reboot into recovery and flash the rom again. it should work the second time cause its using the cynogen mods version of cwm recovery. let it boot it will take a while. but that should work.
dont forget to hit thanks!
taz0697 said:
when it bootloops it does it cause it just flashed the kernel and its trying to run the stock rom on the cynogen kernel. so pull the battery, put it back in. reboot into recovery and flash the rom again. it should work the second time cause its using the cynogen mods version of cwm recovery. let it boot it will take a while. but that should work.
dont forget to hit thanks!
Click to expand...
Click to collapse
Genius!
Thank You!
Cannot believe the solution was staring at me the entire time!!
Hi,
I flashed my GT-i9000 (Firmware was Gingerbread BUJVY) using CF Root (CF-Root-XW_NEE_JVH-v3.2-CWM3RFS.tar) through ODIN.
All worked fine and I was able to boot into Recovery using the regular Volume Up+Home+Power.
I then proceeded to flash CM10 nightly (23/9/12) (from my external Micro SD card) by wiping data, wiping cache and wiping Dalvik Cache.
I then navigated to the zip file for CM10 and run it. It started ok then qiuckly the phone rebooted and rebooted into a newer version of CWM (6.0.1.4).
From here I cannot do anything at all!! It won't recognise my Micro SD now to even run the installation again
I'm hoping someone may be able to help, I would really appreciate it!
TIA!
zim_zimmer said:
It started ok then qiuckly the phone rebooted and rebooted into a newer version of CWM (6.0.1.4). From here I cannot do anything at all!! It won't recognise my Micro SD now to even run the installation again
Click to expand...
Click to collapse
Do you know what version is your Firmware? is it 2.3.3 or 2.3.6?, IF its 2.3.3 your boot loader needs to be updated to 2.3.6 for you use , If its already 2.3.6, than you should be able to use CWM recovery to reinstall the CM 10 from your SD card. (But by doing this you may lose your IMEI as you should do a progressive upgrade , like from GB 2.3.6>ICS CM9>JB) or flash a semaphore JB kernel
Easiest way out would be for you to use a JVU ROM to recover, safe your EFS, than proceed to CM 9 and than to CM 10...
you can get a rescue kit or JVU+CFRoot from My Android Collections and or a solution from My Android Solutions
Hi there,
I was on Gingerbread 2.3.6 before I ran the above.
I have gotten a bit further than the above. I managed to mount the phone as a USB whilst in CWM and put the CM10 zip file on the actual phone memory. I then wiped data/cache/dalvik and rerun the install. It installed but didn’t reboot itself, so I rebooted manually and then the Cyanogenmod logo started up and it booted into CM10. Looked ok apart from the Home Button didn’t work!!
Do you think I should still run the above??
Rooting this phone and flashing ROMS is more difficult than my Galaxy S3!!
Cheers
zim_zimmer said:
Looked ok apart from the Home Button didn’t work!!
Do you think I should still run the above??
Click to expand...
Click to collapse
Since you are already on CM 10, you need to solve your home button problem, try doing a wipe in recovery, if fails, flash again the CM 10
Hmmm, it didn’t work.
What I’ve done since though is try to flash another ROM.
I’ve flashed the ‘xBean’ ROM with success, however, I did encounter the exact same problem when flashing the ROM as mentioned above
I wiped data/cache/dalvik and run the install for xBean. It stopped after the first install attempt and rebooted itself, however it just brought me back to the CWM screen (although this time different from the CM CWM).
So I wiped data/cache/dalvik, then run the install again. This time it went through the full install but again (like with CM) it didn’t rebooted automatically. I manually rebooted and then the xBean logo came up and booted in.
This time the home button is working, and pretty much everything else is too by the looks of it. So far so good!
I guess my question would be, why does the ‘ghost installs’ keep happening???
Hi fellows,
I need your guidance and expert advice in resolving a situation, I have ran into recently. I was trying to install CM10.1 on my brother's galaxy Note GT-N7000 international version which was running official ICS 4.0.4.
Since, I had experience in installing different ROMs on my Galaxy S2, Nexus 7 and Xperia Arc so I was not worried about it being a big deal. So, I followed the procedure described in this page http://techgoneinsane.blogspot.com/2012/08/installing-cm10-on-galaxy-note-n7000.html?m=1 and used Odin and file from 'speedmod' to gain root access and flash CWM which was successful. Then, as planned, I tried update zip in the CWM recovery for CM10.1 nightly. But, I came across error 'Status 7' installation aborted. This was new to me, so I tried few things like 'factory reset', wipe data etc and even tried installing stock ROM ICS XXLRK which was previously installed but no avail. I tried several other ROMs like stable CM9 and other nightlies but no success. The phone is stuck on the boot Samsung logo with yellow triangle. However, I'm able to go in the recovery and download mode.
Upon doing couple of Google searches, I came to know, quite a number of people have faced this error by I couldn't understand the fix properly so can anyone of you please guide me for the solution. Thanks.
Your help will be greatly appreciated.
perceptorz said:
Hi fellows,
I need your guidance and expert advice in resolving a situation, I have ran into recently. I was trying to install CM10.1 on my brother's galaxy Note GT-N7000 international version which was running official ICS 4.0.4.
Since, I had experience in installing different ROMs on my Galaxy S2, Nexus 7 and Xperia Arc so I was not worried about it being a big deal. So, I followed the procedure described in this page http://techgoneinsane.blogspot.com/2012/08/installing-cm10-on-galaxy-note-n7000.html?m=1 and used Odin and file from 'speedmod' to gain root access and flash CWM which was successful. Then, as planned, I tried update zip in the CWM recovery for CM10.1 nightly. But, I came across error 'Status 7' installation aborted. This was new to me, so I tried few things like 'factory reset', wipe data etc and even tried installing stock ROM ICS XXLRK which was previously installed but no avail. I tried several other ROMs like stable CM9 and other nightlies but no success. The phone is stuck on the boot Samsung logo with yellow triangle. However, I'm able to go in the recovery and download mode.
Upon doing couple of Google searches, I came to know, quite a number of people have faced this error by I couldn't understand the fix properly so can anyone of you please guide me for the solution. Thanks.
Your help will be greatly appreciated.
Click to expand...
Click to collapse
If you are on Speedmod's recovery (which is safe), you can try this:
1) Download the latest CM10.1 kernel and save it to your SD card.
2) Flash it in Recovery (Install zip from sdcard > choose zip from sdcard), then reboot in the new Recovery (advanced > reboot recovery).
3) Do a full wipe (even format preload and system in "mounts")
3) Flash the latest CM10.1 build
4) Flash the 4.2.2 Gapps
5) Do a data wipe / factory reset
6) Reboot
You got a yellow triangle because you flashed an unofficial kernel through Odin. To get rid of it, use TriangleAway.
Good luck!
Solved
Kortxero said:
If you are on Speedmod's recovery (which is safe), you can try this:
1) Download the latest CM10.1 kernel and save it to your SD card.
2) Flash it in Recovery (Install zip from sdcard > choose zip from sdcard), then reboot in the new Recovery (advanced > reboot recovery).
3) Do a full wipe (even format preload and system in "mounts")
3) Flash the latest CM10.1 build
4) Flash the 4.2.2 Gapps
5) Do a data wipe / factory reset
6) Reboot
You got a yellow triangle because you flashed an unofficial kernel through Odin. To get rid of it, use TriangleAway.
Good luck!
Click to expand...
Click to collapse
Thanks a lot man. Issue has been resolved by following your procedure and phone is working all fine with CM10.1 on it. Xda rocks!!!
perceptorz said:
Thanks a lot man. Issue has been resolved by following your procedure and phone is working all fine with CM10.1 on it. Xda rocks!!!
Click to expand...
Click to collapse
You're welcome. Glad I could help . If you feel like it, hit the Thanks button on Chasmodo's first message in the repository (where you downloaded your CM10.1 kernel). He really deserves it. You may also want to do the same on Entropy's first post in the unofficial CM10.1 thread :good: That way, you'll show your support and appreciation :angel:.
Hello!
I'm new to Android, still learning how to use it. I'ved got an GT-I9000 with 2.3.6, it works fine excepting the battery. For example, the another night I tried to drain it by turning it on even due it was 0%. Left it to charge the hole night. And about 4 hours ago unpluged it, played 40 min. and the battey was at 40%. I don't think that's normal.
I thought I'd give a try at the Jelly Bean 4.2.2 I saw it is the latest. But the I saw the many roms Cyanogen, Slimbean, Mackay, etc. Which one do I need?
And a good tutorial is welcomed 'cuz I don't know ####.
Thanks!
Maybe it is problem with your battery, bad charging, weared etc. In my opinion 4.2.2 versions gives better battery live. No one will say which custom ROM is best - you have to try it itself. As a new user you can use latest CyanogenMod 10.1.3 (Android 4.2.2)
If you want try custom ROMs on your phone you have to install custom recovery (CWM).
1) Check your baseband version of the phone (for instance XWJV) and find appropriate kernel:
Code:
www.semaphore.gr/downloads/i9000
. Check 'USB Debugging' in Applications -> Development.
2) Install it via Odin as PDA file: http://forum.xda-developers.com/showthread.php?t=1102881 (Download Mode = Volume Down+Home+Power)
2*) If there isn't your version you can try installing 3-file JVZ ROM with Re-Partition and PIT file - then use Semaphore JVZ kernel (but be careful with it, i made it with this version and someone other may give you safer way). Download from http://forum.xda-developers.com/showthread.php?t=1102881 or
Code:
hotfile. com/dl/136940891/b232b26/I9000XWJVZ_I9000OXAJVT_OXA.rar.html
3) After you got your custom recovery and root you should make EFS backup (IMEI) and copy it into PC - you can use SGS Toolbox for Google Play.
4) Download and copy ROM files and GAPPS into your internal SD - (cm-10.1.3-RC1-galaxysmtd.zip) download from http://get.cm/?device=galaxysmtd. You can install CM9 first, because going directly to 10.x may lead to loosing your IMEI (i didn't lost it ). You can find Gapps for JB4.2 here: http://goo.im/gapps
5) Turn off phone, go to recovery (Volume Up+Home+Power). Up/Down = Volume button, Accept = Home. Use full wipe (Wipe Data/Factory reset, Wipe /cache, Advanced -> Wipe /dalvik cache). Now 'install zip from sdcard -> choose zip from sdcard' and seek for CM .zip file. After installation do same with GAPPS.
6) Reboot system now - all done. First boot takes a while.
Thanks for nothinh. I don't have a clue. Why doesn't exist a easy tutorial for installing from a stock 2.3.6 to 4.2.2?
UNHleaSHD said:
Thanks for nothinh. I don't have a clue. Why doesn't exist a easy tutorial for installing from a stock 2.3.6 to 4.2.2?
Click to expand...
Click to collapse
Actually guide posted by AreXe isn't that hard. Just ask what part you cant understand instead of being rude
It's preety straightforward - you download kernel with built-in cwm that suits your current software (rom), you flash it via Odin, download ROM that you like the most, put it on SD and install from CWM recovery mode - doing all of those things while following instructions posted in their respective topics made by creators of those roms/kernels/guides - most of them are in "Galaxy S I9000 Android Development" section, you just have to look and do some reading.
I don;t get it because he says "after geting that, after installing that" and I don;t know If I already have it or no.
Now I'm in trouble and I need HELP!!
While tring to root the phone I opened zadiag.exe, hit install and it never got out of Download Mode. I'ved pulled out the battery and tried to start the phone... nothing hapened. After that I tried to flash with PITT 512 on Odin, at first it sayed Failed so I unninstalled the Composite USB Samsung device mobile and reinstalled the Samsung Drivers. Tried again to reflash with Odin and sayed Succesful! But it still doens't start. I can't enter in recovery mode, only download mode.
What do to?
UNHleaSHD said:
While tring to root the phone I opened zadiag.exe, hit install and it never got out of Download Mode. I'ved pulled out the battery and tried to start the phone... nothing hapened. After that I tried to flash with PITT 512 on Odin, at first it sayed Failed so I unninstalled the Composite USB Samsung device mobile and reinstalled the Samsung Drivers. Tried again to reflash with Odin and sayed Succesful! But it still doens't start. I can't enter in recovery mode, only download mode.
What do to?
Click to expand...
Click to collapse
How you tried to root the phone? And what zadiag.exe? If you not read all procedured carefully you can mess up your phone. I provided you link with tutorial, if thats too hard try using this clear method: http://forum.xda-developers.com/showpost.php?p=44480332&postcount=31
AreXe said:
How you tried to root the phone? And what zadiag.exe? If you not read all procedured carefully you can mess up your phone. I provided you link with tutorial, if thats too hard try using this clear method: http://forum.xda-developers.com/showpost.php?p=44480332&postcount=31
Click to expand...
Click to collapse
I'd just opened zadiag.exe and hit install Samsung COmposite.... in Download Mode, after that it stayed there.
Now I'ved flashed Semaphore_kernel_JVU_2.5.0beta.tar and it's stuck in Recovery mode, tried Wipe data and after that cache, but I still have errors
Can;t mount /cache/recovery/last_log
Can't open same thing
Unknown volume for path recovery.command
And at the Wiping cache the same thing.
L.E. I'ved fixed it with this tutorial: http://www.theandroidsoul.com/xxjvu/ - that's what I call a well explained tutorial.
Thanks for the help. I'm going to try again to root it with the tutorial you gave me.
L.E.2. So it wasn;t my fault. After waiting 2.30 hours to download the rom I'ved began to flash it. Good. All things going nice. Going to step two: flashing CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS, hit start wait. At restart it enteret in Recover mode with the same errors "can't find ..."
So I'ved flashd it again to repair it. I guess my phone ain't made for rooting
UNHleaSHD said:
I guess my phone ain't made for rooting
Click to expand...
Click to collapse
Can't be true. Maybe someone other know good kernel file with root for JVU version. I used the JVZ with Semaphore kernel on 3 phones (mine and two from friends) and everything was fine - this is the best base for modding this phone in my opinion.
Then I'll dare to say that I ain't lucky in rooting.
Something's wrong. Why can't I flash custom roms?