Related
Hey guys.
I've been using CM10 M2 for a while now and I decided I should reflash it.
So I made a wipe ( cleared all cache and everything ), installed cm10 m2 and Tantrum's Aroma Gapps installer to install my gapps and other stuff, and rebooted.
Problem is, once I reboot my phone will not boot and it is stuck on a black screen with LED's flashing.
Tried a few times and it the problem persists.
Any word of advice for me?
-Anton
EDIT: Tried flashing latest nightly with tantrums gapps, same problem.
EDIT V2: Flashed same nightly WITHOUT Tantrums gapps ( regular gapps ), everything boots normally. Problem was with Tantrums gapps.
Antonnzr said:
Hey guys.
I've been using CM10 M2 for a while now and I decided I should reflash it.
So I made a wipe ( cleared all cache and everything ), installed cm10 m2 and Tantrum's Aroma Gapps installer to install my gapps and other stuff, and rebooted.
Problem is, once I reboot my phone will not boot and it is stuck on a black screen with LED's flashing.
Tried a few times and it the problem persists.
Any word of advice for me?
-Anton
EDIT: Tried flashing latest nightly with tantrums gapps, same problem.
EDIT V2: Flashed same nightly WITHOUT Tantrums gapps ( regular gapps ), everything boots normally. Problem was with Tantrums gapps.
Click to expand...
Click to collapse
I'm not any pro user, but I think that the CM10 is too heavy for LGOB. I use the CM7.2 and works like a charm.
DFornazari said:
I'm not any pro user, but I think that the CM10 is too heavy for LGOB. I use the CM7.2 and works like a charm.
Click to expand...
Click to collapse
I have used nightly builds of CM10 from October 15 onwards with a problen
only on the 19th release when I couldn't install anything due to an issue with
the version of Clockworkmod Recovery. Once I found out how to downgrade
that version, it's all fine (touch wood).
Sam
@Antonnzr
Rather just use normal GAPPS. There was a release by tantrums that caused bootloop, but he fixed it now.
Use ADB to go back to recovery.
@DFornazari
CM10 isn't heavy at all. rmcc committed a lot of changes from TI's branch and I think it caused some instability with the some of the newer releases. I based that speculation from a comparison between nightlies before the changes was made and after the changes was made. I didn't look at the code so I can't be 100% certain since I don't know what they changed. rmmc is a great dev and should have all the device specif bugs sorted soon.
Yes its all working fine now with cm10 m2 and regualr gapps but I have a new issue.
Whenever I try to download an app from the Play Market ( nova launcher, for example ) it pops up with an error reading:
"Error: 'Nova launcher' could not be downloaded due to an error (927)"
or alternatively:
"Error: 'Nova launcher' could not be downloaded due to an error ( error retrieving information from the server )"
Tried to install apps via online Play Store both on my phone and my laptop but the download never starts. Help?
Disregard that, fixed after reflash.
Hello to whoever is reading this, I appreciate your help.
I recently saw Cyanogen Mod 10 on lifehacker.com and decided to change my ROM to CM 10. Its was working fine until I wasn't able to open the System Settings. I though I did something wrong and I reinstall CM 10. The first notification popped up was 'Unfortunately, the process com.google.process.gapps has stopped.' and next another one pops up, 'Unfortunately, Android Keyboard (AOSP) has stopped.' It keep crashing the stock keyboard and I only have the stock keyboard.
Next I try to uninstall CM 10 back to stock ROM, I opened ROM Manager and another notification pops up, 'Unfortunately, ROM Manager has stopped.'
So right now, I have a phone that has no system setting, no keyboard and I can't access ROM Manager.
Phone Model : LG OPTIMUS BLACK P970
ROM : CyanogenMod 10
Carrier : Starhub
iReaper said:
Hello to whoever is reading this, I appreciate your help.
I recently saw Cyanogen Mod 10 on lifehacker.com and decided to change my ROM to CM 10. Its was working fine until I wasn't able to open the System Settings. I though I did something wrong and I reinstall CM 10. The first notification popped up was 'Unfortunately, the process com.google.process.gapps has stopped.' and next another one pops up, 'Unfortunately, Android Keyboard (AOSP) has stopped.' It keep crashing the stock keyboard and I only have the stock keyboard.
Next I try to uninstall CM 10 back to stock ROM, I opened ROM Manager and another notification pops up, 'Unfortunately, ROM Manager has stopped.'
So right now, I have a phone that has no system setting, no keyboard and I can't access ROM Manager.
Phone Model : LG OPTIMUS BLACK P970
ROM : CyanogenMod 10
Carrier : Starhub
Click to expand...
Click to collapse
Use recovery. (Not ROM Manager the actual Recovery.)
Sent from my LG-P970
use smart flash tool again to flash patched firmware
do full 3 wipes
I can't boot into recovery and I don't have smart flash installed.
search for smartflashtool in the p970 forum
install a stock rom with ot and cwm recovery
DON'T USE ROM MANAGER WITH OUR PHONE damn people...read...don't just take any advice on youtube
How do you want me to install it? Sorry but I'm a bit confused.
HEY!A FELLOW SINGAPOREAN!Anyways best is to dwnload the bin and fls stock rom files and use smartflashtool to flash it.I recommend v20o or v20s firmware(though there's not much difference).But your FC problem should not happen if you do all wipes b4 flashing:Wipe Data/factory reset,Wipe cache,Wipe Dalvik Cache.
Sent from my LG-P970 using xda app-developers app
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.
Just rooted my phone and tried to instal CM10.1 but now the phone wont start,its stucked at the LG logo.
The only thing thats working is the CWM.
I have tried another version of CM10.1 but still wont start.
SirIntegra said:
Just rooted my phone and tried to instal CM10.1 but now the phone wont start,its stucked at the LG logo.
The only thing thats working is the CWM.
I have tried another version of CM10.1 but still wont start.
Click to expand...
Click to collapse
Are you on new bootloader when you tried to install CM10.1? (New Bootloader = LG with Red splash, Old Bootloader = Pure White LG letters with Icon) You must be on old Bootloader (For Gingerbread) before doing so.... I recommend you clean first the bootloader and partition using WKPARK's file and guide here: http://forum.xda-developers.com/showthread.php?t=1968280, APX Drivers can be grabbed here: https://www.box.com/s/c5d0e911cz9jhz3ab9y1 Credits to umar for reuploading. After that you will have to mount cleaned system on CWM and format your internal SD, then flash nightly rom patched by Wkpark's CM10 patcher so that buttons would work, and flash su660ics' provided kernel by a vietnamese developer here.
Well,thank you verry much for the info!
Anyway,now i`m back tt the stock ROM (GB 2.3.4).
But i still wanna instal CM10.1,or at least CM10 and i`m still wondering why the installation didnt work ??
I mean,i have followed 100% a tutorial on how to install CM10.1.
I tried once but the phone booted with the same ICS 4.0.4,then i tried again,the same result,and the last time when i tried i got stuck at that LG logo,but now its ok.
But how can i install CM10.1 or another version ?? I didnt do anything wrong...i think it didnt work because there are some problems that i`m not aware of...
Hi everyone,
I'm new here and this is my first post. First of all I would like to thanks pawitp and kasper_h for giving new life for our old device SGS i9000. I just wanted to share my experience installing Mackay ROM and wanted to know why my device freeze upon boot after flashing this ROM.
Steps done:
1. Coming from SlimBean (4.3), flashed CM 10.2
2. Do a factory data reset, wipe system/data/dalvik/cache
3. Flash Mackay ROM and GApps
4. Upon restart; freeze on Samsung device logo, waited for a long time but did not continue to kernel/boot/anim.
5. Tried to boot recovery, but still just freeze on Samsung device logo
6. Boot into Download Mode and flash Semaphore kernel from Cyanogen using heimdal tool
7. Flash Mackay ROM then Mackay Kernel then GApps
8. Successful boot!
I've been following Mackay ROM development and very satisfied with it, but every time I will flash/update Mackay ROM, I must remember to flash also the corresponding Mackay Kernel over it, otherwise I'll have to go through steps 4 to 7 above to fix the boot freeze.
Now, my question is, why my device freeze on boot? Isn't Mackay ROM already include the kernel?
I wanted to help in development even by just testing the ROM, but newbies are not allowed to post on development tread...
c-droid said:
Hi everyone,
I'm new here and this is my first post. First of all I would like to thanks pawitp and kasper_h for giving new life for our old device SGS i9000. I just wanted to share my experience installing Mackay ROM and wanted to know why my device freeze upon boot after flashing this ROM.
Steps done:
1. Coming from SlimBean (4.3), flashed CM 10.2
2. Do a factory data reset, wipe system/data/dalvik/cache
3. Flash Mackay ROM and GApps
4. Upon restart; freeze on Samsung device logo, waited for a long time but did not continue to kernel/boot/anim.
5. Tried to boot recovery, but still just freeze on Samsung device logo
6. Boot into Download Mode and flash Semaphore kernel from Cyanogen using heimdal tool
7. Flash Mackay ROM then Mackay Kernel then GApps
8. Successful boot!
I've been following Mackay ROM development and very satisfied with it, but every time I will flash/update Mackay ROM, I must remember to flash also the corresponding Mackay Kernel over it, otherwise I'll have to go through steps 4 to 7 above to fix the boot freeze.
Now, my question is, why my device freeze on boot? Isn't Mackay ROM already include the kernel?
I wanted to help in development even by just testing the ROM, but newbies are not allowed to post on development tread...
Click to expand...
Click to collapse
Hi, im new too
Which Mackay ROM are you taling about? Because i had the same problem flashing Mackay rom 3.99-the last one and i couldnt had flashed it unless i did a dirty flash but even then i had many problems. So i dont know. Currently im using OMNI Mackay -the latest build-and im very satisfied with it, there are only few issues... but in the end its way fastest rom for me before it i had been using Gamerzrom 4.0 for half a year and it was way the best for android 4.2.2
lulek01 said:
Hi, im new too
Which Mackay ROM are you taling about? Because i had the same problem flashing Mackay rom 3.99-the last one and i couldnt had flashed it unless i did a dirty flash but even then i had many problems. So i dont know. Currently im using OMNI Mackay -the latest build-and im very satisfied with it, there are only few issues... but in the end its way fastest rom for me before it i had been using Gamerzrom 4.0 for half a year and it was way the best for android 4.2.2
Click to expand...
Click to collapse
I'm using this Mackay ROM 4.1.7
I also wanted to try the OMNI build, but there's no separate kernel for it yet.
I've only successfully using Mackay ROM 4.1.7 by flashing the ROM then before I reboot I also flash the corresponding Mackay kernel 0.605, if I don't flash the separate kernel then when I restart, my phone freeze on Samsung device boot logo, which I'm wondering since as far as I know Mackay ROM package is already complete, I'm also sure that the ZIP file I downloaded is not corrupted cause I already downloaded it twice and tested it on WinRAR.
c-droid said:
I'm using this Mackay ROM 4.1.7
I also wanted to try the OMNI build, but there's no separate kernel for it yet.
I've only successfully using Mackay ROM 4.1.7 by flashing the ROM then before I reboot I also flash the corresponding Mackay kernel 0.605, if I don't flash the separate kernel then when I restart, my phone freeze on Samsung device boot logo, which I'm wondering since as far as I know Mackay ROM package is already complete, I'm also sure that the ZIP file I downloaded is not corrupted cause I already downloaded it twice and tested it on WinRAR.
Click to expand...
Click to collapse
Have you tried going back to stock android 2.3.6? Maybe that would work for you
@c-droid
@lulek01
Guys, which was your last stock ROM installed before using custom ROMs?
Froyo or Gingerbread?
As I've said on my OP, step no.1 I came from SlimBean, then since its recommended on Mackay ROM development thread I flashed CM 10.2 first before finally going to Mackay ROM.
Even now that I'm on Mackay ROM, when updating to new version using Mackay's TWRP, I still have to flash the separate Mackay kernel after Mackay ROM before restarting, otherwise my phone will freeze on Samsung device logo upon boot.
tetakpatak said:
@c-droid
@lulek01
Guys, which was your last stock ROM installed before using custom ROMs?
Froyo or Gingerbread?
Click to expand...
Click to collapse
My last stock ROM was GB
lulek01 said:
My last stock ROM was GB
Click to expand...
Click to collapse
OK, then we know at least that your phone has a proper bootloader.
For people who upgrade directly from Froyo is very important to flash a GB bootloader, as all newer custom ROMs suppose that GB bootloader was already installed.
---------- Post added at 07:57 PM ---------- Previous post was at 07:55 PM ----------
c-droid said:
As I've said on my OP, step no.1 I came from SlimBean, then since its recommended on Mackay ROM development thread I flashed CM 10.2 first before finally going to Mackay ROM.
Even now that I'm on Mackay ROM, when updating to new version using Mackay's TWRP, I still have to flash the separate Mackay kernel after Mackay ROM before restarting, otherwise my phone will freeze on Samsung device logo upon boot.
Click to expand...
Click to collapse
You didn't get it mate.... I meant: which was your last stock ROM.... Froyo or Gingerbread?
Oh... sorry...
so... before I've flash the custom ROM SlimBean...
damn... I've already forgot, all I remember was I've waited for the phone's warranty to end before trying out custom ROMs, but I knew I've downloaded and installed all the OTAs before, just forgot the last version I've received...
Anyway, do you know how can I update ONLY the bootloader? without doing a factory data reset / wiping system/data...
c-droid said:
Oh... sorry...
Click to expand...
Click to collapse
no problem
so... before I've flash the custom ROM SlimBean...
I knew I've downloaded and installed all the OTAs before, just forgot the last version I've received...
Anyway, do you know how can I update ONLY the bootloader? without doing a factory data reset / wiping system/data...
Click to expand...
Click to collapse
Yep, probably you do have a Gingerbread bootloader then (2.3.x), after all the updates.
Froyo firmweres were 2.2.x
If not sure, here you can see it in my i9000 thread (also with video) how to flash only a bootloader and there you can download all the files.
Make sure to read whole the step-by-step guide for flashing with Odin under section 2 as flashing a bootloader shouldn't go wrong.
Thanks tetakpatak,
I've read your thread, specially the warning regarding flashing bootloader that one mistake could hard brick the phone.
So, I wanted to clarify some things before I proceed on flashing the bootloader...
1. The baseband of the bootloader attached on your thread is XWJVU while my phone is XXJVK, should I search for bootloader the same as mine or the one on your thread is fine?
2. On your thread, the text guide says to choose the bootloader file under "PDA", but on the video, you choose it under "BOOTLOADER", I assume the video is correct as I can see the phone successfully boots...
3. I couldn't see clearly on the video and also not specifically stated on your text guide if I have to choose on Odin the "i9000Boot_XWJVU.zip" file or I have to extract first the "i9000Boot_XWJVU.tar" inside it and choose that one...
Sorry if I asked too much, not that I'm skeptical with your giude, just following your warning...
I was about to try tetakpatak guide on flashing only the bootloader, but I don't know why my phone was not detected by Odin?
I run Odin as administrator, choose the bootloader file, tick the "Phone Bootloader Update" and uncheck "Auto Reboot", then turn-on the phone to download mode, connect to PC, Windows detected the phone as "Gadget Serial device", but did not appear on Odin...