Related
Got a VZW Galaxy tab. Rooted and got ROM manager & SGS Kernel Flasher.
1. I flash using SGS and it successfully flashes, as it reboots and I can see from Settings->Device Info that it shows the Developer's version.
2. I then go to CWM (ROM Manager) load ROM from SD, chose the ROM which is in update.zip format, I select to wipe date and casche and then nothing.
It gets stuck at the SAMSUNG boot screen. So i have to use Heimdall to restore back to stock VZW Rom. I have tried several times, even after flash just tried to reboot directly into Recovery mod (Power+Volume Down) and same thing. Goes to SAMSUNG boot screen and freezes.
What am I missing or doing wrong???
First thing i would recommend is : uninstall rom manager. It causes more problems. If you did a search on these forums you would find loads more tales of woe re rom manager.
Second thing is: have look through the dev section, at the instructions for installing clockwork recovery. Then look for the appropriate rom for your device.
But whatever you do, uninstall rom manager
Sent from my thingymajig
Isn't ROM manager ClockworkMod?
I searched Clockworkmod on the market and when installed the icon says ROM Manager though...
o2sys said:
Got a VZW Galaxy tab. Rooted and got ROM manager & SGS Kernel Flasher.
1. I flash using SGS and it successfully flashes, as it reboots and I can see from Settings->Device Info that it shows the Developer's version.
2. I then go to CWM (ROM Manager) load ROM from SD, chose the ROM which is in update.zip format, I select to wipe date and casche and then nothing.
It gets stuck at the SAMSUNG boot screen. So i have to use Heimdall to restore back to stock VZW Rom. I have tried several times, even after flash just tried to reboot directly into Recovery mod (Power+Volume Down) and same thing. Goes to SAMSUNG boot screen and freezes.
What am I missing or doing wrong???
Click to expand...
Click to collapse
Where you went wrong is just jumping in qnd not even bothering to read ANY tutorials here.
Go and read them instead of screwing things up and then asking where you went wrong.
TheATHEiST said:
Where you went wrong is just jumping in qnd not even bothering to read ANY tutorials here.
Go and read them instead of screwing things up and then asking where you went wrong.
Click to expand...
Click to collapse
i did following the tutorials, its how I went that far to begin with. Sorry for being a newb and maybe not fully understanding it thats why I am asking for help, not to spoon feed me...
Followed these steps:
http://forum.xda-developers.com/showthread.php?t=941781
o2sys said:
...
Followed these steps:
http://forum.xda-developers.com/showthread.php?t=941781
Click to expand...
Click to collapse
Have you tried booting into CW Recovery manually and running the KhasMek.Voodoo.Plus.CDMA.Tab.v5.OC.zip (like the instructions say)?
Your thread header says you are using ROM Manager and trying to run the update.zip package.
ROM Manager _should_ work, but maybe stick with instructions especially if you're having issues.
Yes I have tried going into Recovery manually as I stated in my original post.
I always flashed with SGS kernel flasher as it seemed to work well.
Then I tried manually going to Recovery w/o CWM and gets stuck at boot screen as well.
I tried WITH CWM and same stuck at boot screen.
Tried wiping data through Recovery, through the UI (Settings then ect, ect) and several other combos trying to load the custom ROM.
All I am successul is at rooting, then flashing the kernel. Then no matter which step I tried if i reboot it will get stuck at the SAMSUNG boot screen.
Even if I just turn it off and then turn it back on, after the flash, it will get stuck at the boot screen.
I downloaded the kernal flash directly from the link of the first page. And if the kernal file was courrupt i don't think the flash would go successfully.
I've never used the SGS Flasher so can't say what it would do if the file was corrupt.
Maybe flash it using Heimdall to check the file?
Sorry to hear you are having problems. I am also sorry for the rudeness on this forum. Although I seldom post I read it daily. Here is what I would try;
1. The issue may be with the file name update.zip if you can, rename it to anythingyoulike.zip on you computer and then copy it to your SD card. You may even have to take the card out of your tab to do this (delete the update.zip once the file is renamed). Once the renamed file is on the SD card try to reflash.
2. Have you tried to start again using Odin? There is a good clip on you tube about this. As long as the tab at least starts to boot it is not bricked. Feel free to PM me for any additional help.
Good luck.
tigercorp said:
I've never used the SGS Flasher so can't say what it would do if the file was corrupt.
Maybe flash it using Heimdall to check the file?
Click to expand...
Click to collapse
When I use SGS to flash, it reboots and i can see in settings that it has been flashed.
If I use Heimdall, it flashes then gets stuck at the boot screen.
Hi everyone. I'm new to the touch pad, but I have a lot of experience with the Epic4G from Sprint using CWM and flashing zip files. I have preware installed in my webos, and I have CM9 installed as well.
I've spent a few days reading threads here, but haven't been able to flash anything. I think I must be missing something.
Nothing happens when I flash zip files in CWM. I reboot to recovery, flash the zip file, wipe caches, but nothing is changed when I reboot the system. Been trying to install the unofficial with the working camera, and the oc kernel.
Thanks for any help.
sent from a secret underground bunker
mjben said:
Hi everyone. I'm new to the touch pad, but I have a lot of experience with the Epic4G from Sprint using CWM and flashing zip files. I have preware installed in my webos, and I have CM9 installed as well.
I've spent a few days reading threads here, but haven't been able to flash anything. I think I must be missing something.
Nothing happens when I flash zip files in CWM. I reboot to recovery, flash the zip file, wipe caches, but nothing is changed when I reboot the system. Been trying to install the unofficial with the working camera, and the oc kernel.
Thanks for any help.
sent from a secret underground bunker
Click to expand...
Click to collapse
Did you check md5s on the zips? Also, is your recovery updated?
As soon as I post a request for help, it works. Of course. Lol.
Yeah, I'm not sure what worked this time, but since I posted previously I set manual flash override in ROM Manager and installed the CM9 unofficial preview 7, the preview 9 update, and gapps, all went. I also installed the kernel that I mentioned, but it got stuck in a boot loop after and had to do the ROM over again.
sent from a secret underground bunker
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.
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?
Hey guys,
I've got the dreaded "No Connection" error on my Nook HD+. I've tried many things to fix it. I even deleted and reinstalled the store. I tried deleting and reinstalling G-Mail. No luck. One thing I've noticed is that I can't even get G-mail to open. It opens for a couple of seconds and then closes and says "GMail has unfortunately closed".
I'm running CWM 10.2-20131102
Any ideas?
Are you sure you used the right GApps package?
Btw you should really update to the stable version of CM10.2, it works much better for me at least
N0he said:
Are you sure you used the right GApps package?
Btw you should really update to the stable version of CM10.2, it works much better for me at least
Click to expand...
Click to collapse
I tried downloading gapps from another thread I saw and the zip file won't open, (gapps-jb-20130813-signed.zip).
You know I tried updating to 10.2.1 via the update and it doesn't work. It downloaded it but when I try to update, Recovery says that it failed to open /sdcard/0/cmupdater/cm-10.2.1-ovation.zip (No such file or directory). The only option it gives me is to install untrusted zip. That sounds scary to me.
Did you try to download the GApps again? Sometimes downloaded files can be corrupted.
About the Update:
Try to flash it manually then, but do a factory reset first..
You think you already have the right recovery as you are able to boot the CM10.2 Snapshot, so here is the links you need, so that you don't have to search for them again:
http://download.cyanogenmod.org/?device=ovation
http://goo.im/gapps
N0he said:
Did you try to download the GApps again? Sometimes downloaded files can be corrupted.
About the Update:
Try to flash it manually then, but do a factory reset first..
You think you already have the right recovery as you are able to boot the CM10.2 Snapshot, so here is the links you need, so that you don't have to search for them again:
http://download.cyanogenmod.org/?device=ovation
http://goo.im/gapps
Click to expand...
Click to collapse
Thanks for the help. I've downloaded the gapps and CM zips but I don't know what to do with them. I see them in Root Explorer but I don't know which files to run to use them.
EDIT: I think I've got it figured out. I moved the CM and Gapps zips to my SD card and then flashed them from Recovery. I'll see if that works. Unfortunately I don't have Wi-Fi here at work to check. Looks like I at least have the CM working. I have a different boot screen now, (bummer I liked the old one ). I verified that I'm running 10.2.1-ovation but every time I boot up it tells me that Google Play has stopped working.
I'd say you check again if you downloaded the right GApps version this time, but I guess you did that already...Do the other GApps work? Like Gmail, Maps, etc...
If they do, try to clear its cache. Else you could also get an apk for the play store and install it manually, maybe that will work