Related
Hi, I'm running a stock P500 and I'm a bit disappointed with its performance. I'm looking for a ROM which is feature-complete, i.e. no missing features such as Bluetooth calling, etc. and minimal to no deviation from the stock Android UI. Any suggestions?
use megatron ROM it is the closest in my opinion and has very good performance but i would suggest trying the other ROMs that have gingerbread like miks cm7 they are not missing much and what they are missing you can get back
dislplin01 said:
use megatron ROM it is the closest in my opinion and has very good performance but i would suggest trying the other ROMs that have gingerbread like miks cm7 they are not missing much and what they are missing you can get back
Click to expand...
Click to collapse
I just visited the Megatron ROM thread http://forum.xda-developers.com/showthread.php?t=870640. Why is noejn suggesting that people use void instead?
two roms.
OpenOptimus by Ciaox
OR
Nessy Rom
If you want a nice and long battery life
flash Franco kernel
take note* For 2.2 flash with CFS
Do as what you are told on their page.. I or the dev will not be responsilble.
Ok, so this is all kinda new to me so I wanted to make sure that I have the basics covered:
1. I need to root my phone. I'm running Android 2.2.2 so I guess that means I need to use gingerbreak. It's an .apk file that I need to install on my phone and then I run it to gain root access. Are there any command line actions needed for gingerbreak?
2. After rooting, I need to install a ROM manager such as CWM or AmonRA. If I'm not mistaken, the program itself will install the custom recovery, right? And how do I boot into that recovery mode?
3. After booting into recovery mode, I need to do a nandroid (?) backup of my current ROM, right? And the backup of my stock ROM is restored through the same custom recovery, yes? Would restoring the stock ROM unroot my phone and remove the custom recovery as well?
3. After backing up, I need to flash the custom ROM which should be saved as a .zip file on my SD card. Do I need to worry about the kernel as well?
Sorry if I have a lot of questions.
DigitalAnalog said:
Ok, so this is all kinda new to me so I wanted to make sure that I have the basics covered:
1. I need to root my phone. I'm running Android 2.2.2 so I guess that means I need to use gingerbreak. It's an .apk file that I need to install on my phone and then I run it to gain root access. Are there any command line actions needed for gingerbreak?
2. After rooting, I need to install a ROM manager such as CWM or AmonRA. If I'm not mistaken, the program itself will install the custom recovery, right? And how do I boot into that recovery mode?
3. After booting into recovery mode, I need to do a nandroid (?) backup of my current ROM, right? And the backup of my stock ROM is restored through the same custom recovery, yes? Would restoring the stock ROM unroot my phone and remove the custom recovery as well?
3. After backing up, I need to flash the custom ROM which should be saved as a .zip file on my SD card. Do I need to worry about the kernel as well?
Sorry if I have a lot of questions.
Click to expand...
Click to collapse
1. Install it, open it and select "Root"
2. No, the root program won't install the recovery. You need to do that; the easiest way is by Rom Manager (download from market); boot in recovery: turn off the phone and start it by pressing at the same time: home + vol down + power key and release at lg logo to enter custom recovery or just select boot into recovery from ROM Manager
3. Yes, make a backup and to restore it just select "restore" from the same place. No, you will restore the backup you just made so your phone will be exactly the way it was when you created the backup (including apps, settings etc)
4. Yes, you will enter "install zip from sdcard -> choose zip". Don't forget to wipe cache, dalvik cache, data/factory reset and format /system before you flash the rom. Other kernels are not mandatory but highly recommended (the differences are big) - also wipe just cache & dalvik cache before flashing the kernel
22VIN said:
1. Install it, open it and select "Root"
2. No, the root program won't install the recovery. You need to do that; the easiest way is by Rom Manager (download from market); boot in recovery: turn off the phone and start it by pressing at the same time: home + vol down + power key and release at lg logo to enter custom recovery or just select boot into recovery from ROM Manager
3. Yes, make a backup and to restore it just select "restore" from the same place. No, you will restore the backup you just made so your phone will be exactly the way it was when you created the backup (including apps, settings etc)
4. Yes, you will enter "install zip from sdcard -> choose zip". Don't forget to wipe cache, dalvik cache, data/factory reset and format /system before you flash the rom. Other kernels are not mandatory but highly recommended (the differences are big) - also wipe just cache & dalvik cache before flashing the kernel
Click to expand...
Click to collapse
Thank you. What are the precautions that I need to take to make sure I don't brick my phone? Also, what are the chances of my phone getting damaged and at which point during those steps is it most likely to happen?
DigitalAnalog said:
Thank you. What are the precautions that I need to take to make sure I don't brick my phone? Also, what are the chances of my phone getting damaged and at which point during those steps is it most likely to happen?
Click to expand...
Click to collapse
The chaces of bricking the phone are very small.
What can happen:
- some people reported that their phone got bricked when they installed the recovery with ROM Manager (this can be easily undone, there is a thread about this). Never happened to me, everything went smooth & fast. There are other ways to install a recovery if you don't want to use ROM Manager, just check the Development section.
- the ROM you choose can be uncompatible with your recovery (all the new roms are compatible with clockworkmod recovery (this is the recovery you will install via ROM Manager); there are some older roms which are compatible only with AmonRA)
- after flashing a custom kernel the phone might not boot (no panic, just flash the rom again or restore backup); check if your ROM is compatible with the kernel you choose
Flashing with recovery is very safe because everything can be easily undone. As long as the phone boots into recovery there is no panic.
But most of the time if your cautious and do everything as told your fine~~
hahaha.. Enjoy..
Rom manager give Cwm.. So no hassle..
22VIN said:
The chaces of bricking the phone are very small.
What can happen:
- some people reported that their phone got bricked when they installed the recovery with ROM Manager (this can be easily undone, there is a thread about this). Never happened to me, everything went smooth & fast. There are other ways to install a recovery if you don't want to use ROM Manager, just check the Development section.
- the ROM you choose can be uncompatible with your recovery (all the new roms are compatible with clockworkmod recovery (this is the recovery you will install via ROM Manager); there are some older roms which are compatible only with AmonRA)
- after flashing a custom kernel the phone might not boot (no panic, just flash the rom again or restore backup); check if your ROM is compatible with the kernel you choose
Flashing with recovery is very safe because everything can be easily undone. As long as the phone boots into recovery there is no panic.
Click to expand...
Click to collapse
Thank you. When I backup my stock ROM, the output is a .zip file which is no different from how the custom ROM zips are packaged, right? Also, would you know if Gingerbreak supports unrooting? I appreciate all of your help and I'm quite excited to root my Optimus One.
DigitalAnalog said:
Thank you. When I backup my stock ROM, the output is a .zip file which is no different from how the custom ROM zips are packaged, right? Also, would you know if Gingerbreak supports unrooting? I appreciate all of your help and I'm quite excited to root my Optimus One.
Click to expand...
Click to collapse
Your backup will appear as a folder on the root of your sdcard (/clockworkmod/folder with the date of your backup). You need to save that folder on your pc just to be safe.
Yes, gingerbread supports unrooting
No problem Just have fun )
22VIN said:
Your backup will appear as a folder on the root of your sdcard (/clockworkmod/folder with the date of your backup). You need to save that folder on your pc just to be safe.
Yes, gingerbread supports unrooting
No problem Just have fun )
Click to expand...
Click to collapse
Thanks! Is it safe to do all the flashing/work from within ROM Manager? It just seems too easy to be true.
Also, is there a 'compatibility matrix' of some sort for the different ROMS and kernels available? Since I want GB, I'm planning on flashing Mik's CM7 mod. Is Franco's kernel compatible with that?
DigitalAnalog said:
Thanks! Is it safe to do all the flashing/work from within ROM Manager? It just seems too easy to be true.
Also, is there a 'compatibility matrix' of some sort for the different ROMS and kernels available? Since I want GB, I'm planning on flashing Mik's CM7 mod. Is Franco's kernel compatible with that?
Click to expand...
Click to collapse
I say it's pretty safe. As I said, worked like a charm for me.
mik_os's rom is flashable via clockworkmod recovery and compatible with franco.kernel (bfs version).
If you are interested in a froyo stock rom with just the root and a performant kernel like franco's one, I could cook a rom for you...
22VIN said:
I say it's pretty safe. As I said, worked like a charm for me.
mik_os's rom is flashable via clockworkmod recovery and compatible with franco.kernel (bfs version).
Click to expand...
Click to collapse
But now rom manager doesn't let us download any Rom(Only for premium) anymore except for Gapps.
download at the Dev page at XDA is the best. cause it shows all the steps required
22VIN said:
I say it's pretty safe. As I said, worked like a charm for me.
mik_os's rom is flashable via clockworkmod recovery and compatible with franco.kernel (bfs version).
Click to expand...
Click to collapse
Thanks. I was able to gain root as well as install CWM. I'm currently backing up my current ROM. Now I'm not sure if this is a stupid question but when I install a custom ROM, wouldn't that overwrite CWM? How do I go back to recovery then, say, to reflash my original ROM?
Flashing a rom through recovery does not overwrite the recovery.
And you can always boot into recovery by pressing and holding home+volume down+power when the phone is off till the recovery menu boots.
Sent from my LG-P500 using XDA App
I'm just about to flash my first custom ROM. It's all quite clear up to this point. I'm not so sure about the kernel though. Is it all done via the Recovery console? Which options/commands should I take? And what about the ZRAM initializer?
DigitalAnalog said:
I'm just about to flash my first custom ROM. It's all quite clear up to this point. I'm not so sure about the kernel though. Is it all done via the Recovery console? Which options/commands should I take? And what about the ZRAM initializer?
Click to expand...
Click to collapse
For flashing rom : wipe everything, partition SD card only of you want to use a2sd or data2sd (check ciaox's REPO thread for more info about these two) and then choose flash from zip. If you are wiping battery stats then do it when you are fully charged.
For flashing kernel : wipe cache,dalvik cache and battery stats. No need to partition SD card.
EDIT: yes you need to flash zram initialiser. Keep in mind to flash Cfs version for froyo and bfs version for gb roms. Also always reboot between multiple flashes.
Sent from my LG-P500 using XDA App
mihir287 said:
For flashing rom : wipe everything, partition SD card only of you want to use a2sd or data2sd (check ciaox's REPO thread for more info about these two) and then choose flash from zip. If you are wiping battery stats then do it when you are fully charged.
For flashing kernel : wipe cache,dalvik cache and battery stats. No need to partition SD card.
EDIT: yes you need to flash zram initialiser. Keep in mind to flash Cfs version for froyo and bfs version for gb roms. Also always reboot between multiple flashes.
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
Just go to the zip rom. example franco.kernel.v17. click on it. and choose rom manager if prompt and just wipe dalvik cache..
WIPE BATT STAT ONLY WHEN YOU CHARGED AT 100%
Zram is actually up to individual.
just reminding him. Hope im not a pest to you.
Hey everyone,
First of all, i apologize if any of what i'm asking here is stuff that has been covered before. I have been searching myself for answers for the last several days and have found plenty of good info, but i am new to android and i think i need to ask some question to help get a base level understanding of what i need to do. I am a bit nervous about bricking my phone so i maybe haven't been as adventurous trying to get everything running as god intended.
Firstly, i have used and understand Odin, using it to flash roms and such. I have rooted the phone and installed ROM Manager and clockworkmod 4.0.1.5 on the phone, but when i boot into recovery mode, it is still on the android recovery 3e and i cannot do the update.zip, I get signature verification failed. Now i KNOW this is cause of the android recovery 3e, and i have found this issue has been encountered plenty before, but my confusion is in some of the solutions i have found. Mainly the terminology and how the steps directly apply to the phone. For example, I found on another forum thread :
1- Copy the Zimage from your rooted kernel and paste it to SD card of your phone.
2- Flash the Stock kernel via Odin to get rid of Yellow triangle.
3- Flash the Zip file (Zimage) via CWM which you've already pasted in Step 1.
i don't really understand what the zimage is. Why do i need it, what IS it frankly? Where do i get it or a stock kernel for my phone. Does versioning matter much? i read that for the most part the kernels are almost identical to each other, and the fact all i really need is for the android recovery mode to be 2e or whatever it is (so it will not do the signature check on the update.zip file), that i don't really need to pay much attention to the actual kernel version.
What i really need i guess is for someone to break it down for me and either explain the steps or give me a detailed step by step on how to get clockworkmod recovery working so i can proceed with the cyanogen mod running on phone (not enjoying touchwiz at all).
Again, sorry if i am giving anyone spasms at my noobish-ness, but i have been searching for my answers for a day or two now and i haven't been able to find anything that really tells me what i need to know.
Phone : GT-I9100M
Android : 2.3.3
Kernal : 2.6.35.7-I9100XWKDD-CL
Build : GINGERBREAD.UGKG2
Thanks
riccochet said:
Hey everyone,
clockworkmod 4.0.1.5 on the phone, but when i boot into recovery mode, it is still on the android recovery 3e
That means you have not installed it flash CWM and \Root from here .
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
Beware of following instructions from a separate rom to the one you are flashing .
1- Copy the Zimage from your rooted kernel and paste it to SD card of your phone.
2- Flash the Stock kernel via Odin to get rid of Yellow triangle.
3- Flash the Zip file (Zimage) via CWM which you've already pasted in Step 1.
i don't really understand what the zimage is.
ZImage is the kernel .
Why do i need it, what IS it frankly? Where do i get it or a stock kernel for my phone. Does versioning matter much? i read that for the most part the kernels are almost identical to each other, and the fact all i really need is for the android recovery mode to be 2e or whatever it is (so it will not do the signature check on the update.zip file), that i don't really need to pay much attention to the actual kernel version.
You are confusing yourself .
Flash correct CWM from above link .
Choose the custom rom and follow the instructions posted for that rom .
CyanogenMod as the man says
Warning : Not for new users, flash this build only if you know what you are doing !!!
#Followed by his install instructions ~~~
jje
Click to expand...
Click to collapse
Thanks for the reply. I have been doing more reading and i think i am understanding the rooting process a bit better.
I looked at the link you posted (thanks for that, i saw the forum post for the i9000 but i never could find the i9100 post for some reason) and i DO have another question after reading through a good chunk of the posts on it.
There is no CF Root for my kernel, but the reply that was made to someone else with my kernel version was :
"Flash the Stock 2.3.4 ROM (XXKG5, XXKG6 or XXKG7) and root with CF-Root-XXKG6."
I understand that process and how it works but i thought you were only supposed to flash roms based on your firmware version? My KDD kernel version is running on 2.3.3
Will this cause any issues if i flash the stock 2.3.4 ROM?
Download cm7 zip for the newest nightly.
Copy it to internal sd card.
Flash any cf root kernel
Boot into recovery
Wipe data and cache, you will lose all your data on your phone, so backup sms (I recommend sms backup +), also you will lose App data so you might want to back that up first using something like titanium backup.
Wipe dalvik cache (under advanced)
Chose install zip from sd card
Select the cm7 zip
Reboot
If you get stuck at the boot screen go back into recovery and flash the zip again
Sent from my GT-I9100 using XDA Premium App
Thanks Veyka.
I think i'm ok with the CM7 install process. I am probably going to wait until i really feel like i understand the whole process from front to back before i start messing with that though.
I can't get to that point yet however since i haven't been able to get CWM recovery working yet. I have the Android Recovery 3e, which will not install from zip files that aren't digitally signed.
So i'm trying to get CF Root installed and working, however, as mentioned in my previous post there is no CF Root for my kernel. I would like it clarified if it is ok for me to flash to a 2.3.4 stock ROM (i'm running 2.3.3) and then use a CF root for a the new ROM.
I was under the impression that this was not a good idea.
If i should not be doing this, is there a recommended way to upgrade my firmware to 2.3.4 so i can use a newer CF Root?
Thanks
Pick a new stock rom, I would go for kg6, flash it via odin.
Then flash the kg6 CF root kernel via odin and you will have cwm recovery.
Don't put the pit into odin and don't tick repartition or update bootloader.
There is a good thread with all the info you need on flashing stock roms with odin and a list of all avaliable roms.
Sent from my GT-I9100 using XDA Premium App
Thanks for all the help. I was able to make sense of the process (which is actually quite simple, just needed to put it all together in my head to make sense) and get everything done.
Appreciate all the help!
veyka said:
Download cm7 zip for the newest nightly.
Copy it to internal sd card.
Flash any cf root kernel
Boot into recovery
Wipe data and cache, you will lose all your data on your phone, so backup sms (I recommend sms backup +), also you will lose App data so you might want to back that up first using something like titanium backup.
Wipe dalvik cache (under advanced)
Chose install zip from sd card
Select the cm7 zip
Reboot
If you get stuck at the boot screen go back into recovery and flash the zip again
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
Hi,
I have rooted my phone using the quick root guide found here and therefore I have my stock kernel back w/ root. Do I need to install a cf root kernel?
Also, when the new ROM gets flashed how does one recover the apps and data lost?
NABNAP said:
Hi,
I have rooted my phone using the quick root guide found here and therefore I have my stock kernel back w/ root. Do I need to install a cf root kernel?
Also, when the new ROM gets flashed how does one recover the apps and data lost?
Click to expand...
Click to collapse
Use Titanium Backup PRO for your app. You can backup all of them then restore on any rom.
Is there anything that Titanium Backup doesn't back up for which I need to use another application?
Thanks.
NABNAP said:
Is there anything that Titanium Backup doesn't back up for which I need to use another application?
Thanks.
Click to expand...
Click to collapse
sms.. use another app to backup your sms.. for example sms backup as mentioned before..
I have been trying to flash Slim ICS on my SGS2 for over an hour without success.
What happens is that when i choose the base zip it always says no zImage found and simply stops trying.
I've followed the instructions carefully.
Phone is rooted, CWM installed properly, Wipe/Format prior to flashing, files placed in external SD root, downloaded the correct files from Slim ICS website.
After the first failed attempt, i googled and searched all over XDA Forums but nothing worked.
I've tried flashing directly from the CWM Recovery Menu and the APP itself (Flash Kernel).
What i am doing wrong?
Currently my phone has the LPG firmware from the official firmwares thread.
XDA-Noobie said:
I have been trying to flash Slim ICS on my SGS2 for over an hour without success.
What happens is that when i choose the base zip it always says no zImage found and simply stops trying.
I've followed the instructions carefully.
Phone is rooted, CWM installed properly, Wipe/Format prior to flashing, files placed in external SD root, downloaded the correct files from Slim ICS website.
After the first failed attempt, i googled and searched all over XDA Forums but nothing worked.
I've tried flashing directly from the CWM Recovery Menu and the APP itself (Flash Kernel).
What i am doing wrong?
Currently my phone has the LPG firmware from the official firmwares thread.
Click to expand...
Click to collapse
hey dude try placing the Slim ICs zip file on ur internal sdcard then reboot 2 recovery and from there choose install zip from internal sdcard and flash and see
where're u coming from?
I've done successful for my just first ROM flashing experience when upgrading SGS2 from GB 2.3.3 to Official ICS DXLP7 with Odin 1.85 & now i've Slim it by Krarvind Rom..
I dunno if ur phone is coming from GB or ICS
If from GB better flash it w/ Odin 1.85 first w/ official ICS ROM (get it from Sammobile.com), wipe all data (cache, dalvik,factory & battery stat) - format system - then just can flash from CWM w/ Slim ICS
#don't forget2press thanks#
XDA-Noobie said:
I have been trying to flash Slim ICS on my SGS2 for over an hour without success.
What happens is that when i choose the base zip it always says no zImage found and simply stops trying.
I've followed the instructions carefully.
Phone is rooted, CWM installed properly, Wipe/Format prior to flashing, files placed in external SD root, downloaded the correct files from Slim ICS website.
After the first failed attempt, i googled and searched all over XDA Forums but nothing worked.
I've tried flashing directly from the CWM Recovery Menu and the APP itself (Flash Kernel).
What i am doing wrong?
Currently my phone has the LPG firmware from the official firmwares thread.
Click to expand...
Click to collapse
As already stated try placing the base on your internal SD as I don't know what version of CWM you have but some have issues with flashing from the external. You can't use the CWM app to flash the ROM as a kernel as it is not the same and there is no zimage included as AOSP ROM's are different and use boot.img for the kernel.
Once you have the base, I9100 essentials and Slim Gapps on your internal SD, boot into CWM and do the following:
1. Wipe data/factory reset
2. In mounts and storage - format /system
3. In advanced menu - Wipe dalvik
4. Find your base.zip on your internal SD and flash that
5. Repeat step 4 again as it doesn't flash first time
6. Flash essentials.zip
7. Flash Slim Gapps.zip if you want all the important Google apps
8. Reboot to system
That should be it and you shouldn't have any issues. If you do have issues then it may be bootloader related as newer ICS bootloaders sometimes have issues flashing CM9/AOSP ROM's. Hopefully you don't have that issue though.
AvRS said:
As already stated try placing the base on your internal SD as I don't know what version of CWM you have but some have issues with flashing from the external. You can't use the CWM app to flash the ROM as a kernel as it is not the same and there is no zimage included as AOSP ROM's are different and use boot.img for the kernel.
Once you have the base, I9100 essentials and Slim Gapps on your internal SD, boot into CWM and do the following:
1. Wipe data/factory reset
2. In mounts and storage - format /system
3. In advanced menu - Wipe dalvik
4. Find your base.zip on your internal SD and flash that
5. Repeat step 4 again as it doesn't flash first time
6. Flash essentials.zip
7. Flash Slim Gapps.zip if you want all the important Google apps
8. Reboot to system
That should be it and you shouldn't have any issues. If you do have issues then it may be bootloader related as newer ICS bootloaders sometimes have issues flashing CM9/AOSP ROM's. Hopefully you don't have that issue though.
Click to expand...
Click to collapse
Finally a proper guide for newbies.
Ill try it and report back!
Thanks Man!
XDA-Noobie said:
Finally a proper guide for newbies.
Ill try it and report back!
Thanks Man!
Click to expand...
Click to collapse
No worries just happens that I'm the S2 beta tester for Slim ICS hopefully all will go well for you. When you're all set up don't forget to check out the feature guide which gives you an overview of the main features of the current and next version coming soon (link in post 2 of the thread or my sig).
AvRS said:
No worries just happens that I'm the S2 beta tester for Slim ICS hopefully all will go well for you. When you're all set up don't forget to check out the feature guide which gives you an overview of the main features of the current and next version coming soon (link in post 2 of the thread or my sig).
Click to expand...
Click to collapse
Double thanks!
It worked!
XDA-Noobie said:
Double thanks!
It worked!
Click to expand...
Click to collapse
Glad to hear it, you're now ready to flash 4.0 released this morning
I've tried flashing half a dozen roms on 3 versions of CWM and TWRP, and every attempted zip installation fails. I've done this several times before on other phones; is there some special trick I'm missing on the Fascinate?
We'll need some more info to truly help out.
Dou you have sch-i500 Verizon Fascinate?
What current android version/ROM are you on?
Are you rooted?
Which cwm are you trying?
What ROM are you trying to flash?
Have you followed the " guide" from "droidstyle" posted in the general section?
hhp_211 said:
We'll need some more info to truly help out.
Dou you have sch-i500 Verizon Fascinate?
What current android version/ROM are you on?
Are you rooted?
Which cwm are you trying?
What ROM are you trying to flash?
Have you followed the " guide" from "droidstyle" posted in the general section?
Click to expand...
Click to collapse
Yes, it's the sch-i500.
I'm not using the phone right now, but I've been flashing back to this http://forum.xda-developers.com/showthread.php?t=1526488 Eclair. I can't restore from the nandroid backup I made, it fails as well.
I haven't tried flashing Superuser.
Recoveries I've tried are TWRP and 3 CWMs I've found. I just have these in a folder with their default names: cwm_fixed_for_cm7-ODIN.tar, cwm-bml-i500.tar, cwm-recovery-ALL.tar.
I've tried flashing several ROMs, and I've deleted most of them. Right now I'm trying the 7.20 version and CM10 6/18 build from here http://download.cyanogenmod.com/?device=fascinatemtd, this 5/31 build of AOKP http://forum.xda-developers.com/showthread.php?t=2185502, and this http://forum.xda-developers.com/showthread.php?t=1385624.
No, I haven't been following that guide. I've been using Odin to restore back to Eclair, then I flash a recovery, then the ROM. I'll try following that guide when I have time; I've already wasted 6 hours on this.
The guide will give you some missing and critical steps for a generally flawless process to bring you up to a 4.2.x ROM...
Look at section 4
Like making sure to use. pit
'cwm fixed for cm7' is the one to use from stock eclair
Don't forget the gb bootloader file
The biggest thing the guide didn't mention is when in 'cwm fixed for cm7' flashing your news ROM you'll need to flash that ROM 3 times,,, you don't need to wipe everything during those just flash 3 times,,,,
1st time flash, then you do a reboot,,, it will take you into a new updated cwm recovery,,, from there flash ROM again,,, you'll get a warning about partitions with a status error,,, it's normal,,,, go directly back and choose to flash ROM again,,, flash will work and complete process,,, now just flash any needed Google gapps zip file then reboot into your new ROM...
.
hhp_211 said:
The guide will give you some missing and critical steps for a generally flawless process to bring you up to a 4.2.x ROM...
Look at section 4
Like making sure to use. pit
'cwm fixed for cm7' is the one to use from stock eclair
Don't forget the gb bootloader file
The biggest thing the guide didn't mention is when in 'cwm fixed for cm7' flashing your news ROM you'll need to flash that ROM 3 times,,, you don't need to wipe everything during those just flash 3 times,,,,
1st time flash, then you do a reboot,,, it will take you into a new updated cwm recovery,,, from there flash ROM again,,, you'll get a warning about partitions with a status error,,, it's normal,,,, go directly back and choose to flash ROM again,,, flash will work and complete process,,, now just flash any needed Google gapps zip file then reboot into your new ROM...
.
Click to expand...
Click to collapse
It looks like the problem was that I didn't flash the gingerbread bootloader after I flashed CWM. Isn't the bootloader a part of the Gingerbread restore image I'm using in the guide though? And why don't ROM makers put that in their ROMs if it's required for the ROMs to work?
Anyway, it's working now. Thanks!
Hello,
because I have not 10 postings, I can not post directly into http://forum.xda-developers.com/gal...04-googy-max2-kernel-2-3-1-cm-camera-t2517875 but I think my questions in mostly related to this.
I have a stock 4.3 ROM installed on my 1st ROM, and now I want to install a 2nd ROM (also stock rom with different branding) on my phone.
I have installed Googy (newest version, 2.3.1), sTweak and can boot in Googy Recovery Options.
1.) When I click on "install zip to 2nd ROM from external SD" and select the Stock ROM Zip file from Sammobile-Firmware-Donwloads, then it's aborting.
I think I can not install a stock ROM out of Googy CWM directly as 2nd ROM? I am right?
2.) If I am right, and it's not working, my next plan is to clone 1st ROM to 2nd ROM, then I could boot 2nd ROM and then flash the 2nd ROM with Mobile ODIN to my selected 2nd STOCK ROM with different branding. But when I select "Clone 1st ROM to 2nd ROM" in Googy CWM, then error message comes up:
Not enough Space on SD. Available 0MB
But I have lots of free space on internal and external Memory. And 2nd ROM should be empty at the moment, because I try to install 2nd ROM first time. I have tried it with "Format 2nd ROM system" before, and also tried with other Wipes-Selections for 2nd ROM before.
So I end up with 3 questions
- I am correct with 1.) that I can not flash (install) the stock ROM in Googy CWM Boot Menu directly?
- Why I get the "No Space" Error in 2.) "Clone 1st ROM to 2nd ROM"? And how I get rid of it?
- And last but not least the most important question ... is there a better and easier way to get the result I want: Two installed Stock ROMs, only difference in Branding (two different Firmware-files), both same Android Version (4.3), both Stock ROMs (but different ones).
I tried things the whole day, hope somebody can help. Thanks a lot in advance!
Informations:
- Galaxy S3 I9300
- Android 4.3
- Googy already installed, sTweak installed
- Phone rooted
- Last ROM update (standard 1st ROM) to 4.3 with Mobile ODIN, Googy installed after this
- CWM installed also, before installing Googy (both after last update with mobile ODIN)
you can install your second rom by "Stweak" app from google market... open itand Dualboot>Reboot into 2nd Rom UNTILS
then it will take you to special recovery.. dual boot opinion > formate second rom then install the new rom I not think it need a Clone
good luck
shikara13 said:
you can install your second rom by "Stweak" app from google market... open itand Dualboot>Reboot into 2nd Rom UNTILS then it will take you to special recovery.. dual boot opinion > formate second rom then install the new rom I not think it need a Clone good luck
Click to expand...
Click to collapse
Thanks for your advice, but as I described in detail, I tried this also. Would be nice if someone could answer my 3 questions more in detail. Thanks a lot!
Der dicke Baer said:
Hello,
because I have not 10 postings, I can not post directly into http://forum.xda-developers.com/gal...04-googy-max2-kernel-2-3-1-cm-camera-t2517875 but I think my questions in mostly related to this.
I have a stock 4.3 ROM installed on my 1st ROM, and now I want to install a 2nd ROM (also stock rom with different branding) on my phone.
I have installed Googy (newest version, 2.3.1), sTweak and can boot in Googy Recovery Options.
1.) When I click on "install zip to 2nd ROM from external SD" and select the Stock ROM Zip file from Sammobile-Firmware-Donwloads, then it's aborting.
I think I can not install a stock ROM out of Googy CWM directly as 2nd ROM? I am right?
2.) If I am right, and it's not working, my next plan is to clone 1st ROM to 2nd ROM, then I could boot 2nd ROM and then flash the 2nd ROM with Mobile ODIN to my selected 2nd STOCK ROM with different branding. But when I select "Clone 1st ROM to 2nd ROM" in Googy CWM, then error message comes up:
Not enough Space on SD. Available 0MB
But I have lots of free space on internal and external Memory. And 2nd ROM should be empty at the moment, because I try to install 2nd ROM first time. I have tried it with "Format 2nd ROM system" before, and also tried with other Wipes-Selections for 2nd ROM before.
So I end up with 3 questions
- I am correct with 1.) that I can not flash (install) the stock ROM in Googy CWM Boot Menu directly?
- Why I get the "No Space" Error in 2.) "Clone 1st ROM to 2nd ROM"? And how I get rid of it?
- And last but not least the most important question ... is there a better and easier way to get the result I want: Two installed Stock ROMs, only difference in Branding (two different Firmware-files), both same Android Version (4.3), both Stock ROMs (but different ones).
I tried things the whole day, hope somebody can help. Thanks a lot in advance!
Informations:
- Galaxy S3 I9300
- Android 4.3
- Googy already installed, sTweak installed
- Phone rooted
- Last ROM update (standard 1st ROM) to 4.3 with Mobile ODIN, Googy installed after this
- CWM installed also, before installing Googy (both after last update with mobile ODIN)
Click to expand...
Click to collapse
You need to follow procedure from this thread
http://forum.xda-developers.com/gal.../kernel-devil2-2-3-2-f2fs-filesystem-t2528624
quaker1985 said:
You need to follow procedure from this thread
http://forum.xda-developers.com/gal.../kernel-devil2-2-3-2-f2fs-filesystem-t2528624
Click to expand...
Click to collapse
That's a complete other way with different kernel, I read much of How-To's right now, why it don't work with the setup and way I posted with the Googy Kernel and sTweak?
Some more details to my questions and what is wrong in my doing would be really nice to understand.
Der dicke Baer said:
That's a complete other way with different kernel, I read much of How-To's right now, why it don't work with the setup and way I posted with the Googy Kernel and sTweak?
Some more details to my questions and what is wrong in my doing would be really nice to understand.
Click to expand...
Click to collapse
fact is that googy max kernel is based on syah kernel. from there comes the "second roms util" from stweaks which is able to create a temporary recovery for the second rom. unfortunately this is closed source by the syah kernel dev, so it was never possible to update this recovery so it cannot handle newer roms.
Now there are to possibilities: 1) you can use the recovery provided by devil kernel (but not his latest one, but the one which is linked in googy max thread). it will transform your rom.zip so that it will be flashed to second rom. note that this is not posssible with aroma roms. If it is one then option 2)
2) use devil recovery as above. backup primary rom. install the desired second rom as primary, make a nandroid of it. restore it as second rom and restore also your old primary rom.
there is also a how to in googymax thread in the q&a thread: how to install second rom with devil recovery
3) you can use devil kernel with his latest recovery. there you can even flash most of the aroma based roms (and also the normal not aroma based ones) directly as second rom
4) you can use arter97's kernel, there you can use each recovery you want. but there it is more complicated to flash a stock rom as second rom as you have to rewrite yourself the update-script of the zip. (cm based roms can simply be flashed with his multi-boot zip, though)
Thanks for more information in detail Darkened_Sky. I want to flash a normal stock ROM to 2nd ROM, so no Aroma ROM workaround is needed I think. I want to flash it directly, that would be nice, without cloning first and with ROM from sammobile Firmware Download. So I will try this:
Darkened_Sky said:
1) you can use the recovery provided by devil kernel (but not his latest one, but the one which is linked in googy max thread). it will transform your rom.zip so that it will be flashed to second rom. note that this is not posssible with aroma roms. If it is one then option 2)
Click to expand...
Click to collapse
--> In the following Posting out of Googy thread is a instruction, I think that is exactly the recovery source and the doing you mean. That's right? And that is also the (not latest) recovery you mean? (as Posting attachment)
http://forum.xda-developers.com/showpost.php?p=47249482&postcount=2
Darkened_Sky said:
3) you can use devil kernel with his latest recovery. there you can even flash most of the aroma based roms (and also the normal not aroma based ones) directly as second rom
Click to expand...
Click to collapse
--> That also sounds easy, but I don't understand the difference to your suggestion 1.)
Only difference is that I use the latest devil recovery, and not the one out of the linked posting? So I can do it with the same doing (without cloning, and with stock rom from sammobile), but with newest devil kernel out of thread: http://forum.xda-developers.com/gal.../kernel-devil2-2-3-2-f2fs-filesystem-t2528624
(same thread as quaker1985 mentioned before)
If it's the same doing, same result, same possible input file (sammobile stock firmware), then I will take the newest devil kernel. But perhaps I miss a difference in Detail between your suggestion 1.) and 3.)
Thanks a lot!
Der dicke Baer said:
Thanks for more information in detail Darkened_Sky. I want to flash a normal stock ROM to 2nd ROM, so no Aroma ROM workaround is needed I think. I want to flash it directly, that would be nice, without cloning first and with ROM from sammobile Firmware Download[/B
Click to expand...
Click to collapse
sammobile does only provide tar.md5, which has to be flashed with odin with pc (or mobile odin) they cannot directly be flashed within any recovery. therefor you have to use a custom rom of this site or the stock rom provided by justarchi which is in zip format. this is his latest one: http://forum.xda-developers.com/galaxy-s3/general/rom-justarchis-sammy-stock-deodex-root-t2762714
but you can still flash your primary rom with odin and then flash the recovery and then install a recorey rom.zip as second rom
Der dicke Baer said:
--> In the following Posting out of Googy thread is a instruction, I think that is exactly the recovery source and the doing you mean. That's right? And that is also the (not latest) recovery you mean? (as Posting attachment)
http://forum.xda-developers.com/showpost.php?p=47249482&postcount=2
Click to expand...
Click to collapse
yes exactly
Der dicke Baer said:
--> That also sounds easy, but I don't understand the difference to your suggestion 1.)
Only difference is that I use the latest devil recovery, and not the one out of the linked posting? So I can do it with the same doing (without cloning, and with stock rom from sammobile), but with newest devil kernel out of thread: http://forum.xda-developers.com/gal.../kernel-devil2-2-3-2-f2fs-filesystem-t2528624
(same thread as shikara13 mentioned before)
If it's the same doing, same result, same steps, then I will take the newest devil kernel. But perhaps I miss a difference in Detail between your suggestion 1.) and 3.)
Click to expand...
Click to collapse
difference is: older devil recovery transforms your rom.zip so that it will be installed to second rom. after that it can only be flashed as second rom. and it takes some time. latest devil recovery directly flashes it as second rom, and after that the rom.zip can still be used for primary if needed.
Note: if you test devil kernel, that don't uae the kernel in the OP. his newest kernel and recovery are somewhere in his thread, so you have to search a bit
Thanks again, I think I have understand most of the things you write, but not this:
Darkened_Sky said:
but you can still flash your primary rom with odin and then flash the recovery and then install a recovery rom.zip as second rom
Click to expand...
Click to collapse
Would be nice when you explain it more for a newbie.
And I think, the thing that makes my situation a bit more difficult, is that the second ROM must be a also original Stock ROM. So perhaps I try it with Zipped Stock ROMs you have linked from justarchis: http://forum.xda-developers.com/galaxy-s3/general/rom-justarchis-sammy-stock-deodex-root-t2762714
But he writes ROMs are a bit changed. And I need a exact stock ROM with a branding out of germany from german provider, I think justarchis will not provide this. So in the end I think, I can not use this solution.
What's about a solution:
- install latest devil recovery
- Go to Googy CWM Boot menu - 2nd ROM options - Clone 1st to 2nd ROM (Then it works, after update with newest devil recovery? And option for cloning is stil there after install devil recovery? This works also with the "not latest" devil recovery out of the mentioned posting http://forum.xda-developers.com/showpost.php?p=47249482&postcount=2)
- After Cloning Boot the 2nd ROM
- After booting second rom, start mobile odin and flash stock ROM without Kernel and without recovery (Without Kernel/Recovery to stick to kernel and recovery of googy/devil, to be able to switch ROMs without reinstall kernel/recovery).
In this case mobile odin understands to flash correctly the 2nd ROM and not the 1st one? (mobile odin reboot the device, and I don't understand how mobile odin can differ between 1st and 2nd ROM)
Thanks a lot!
Der dicke Baer said:
What's about a solution:
- install latest devil recovery
- Go to Googy CWM Boot menu - 2nd ROM options - Clone 1st to 2nd ROM (Then it works, after update with newest devil recovery? And option for cloning is stil there after install devil recovery? This works also with the "not latest" devil recovery out of the mentioned posting http://forum.xda-developers.com/showpost.php?p=47249482&postcount=2)
- After Cloning Boot the 2nd ROM
- After booting second rom, start mobile odin and flash stock ROM without Kernel and without recovery (Without Kernel/Recovery to stick to kernel and recovery of googy/devil, to be able to switch ROMs without reinstall kernel/recovery).
In this case mobile odin understands to flash correctly the 2nd ROM and not the 1st one? (mobile odin reboot the device, and I don't understand how mobile odin can differ between 1st and 2nd ROM)
]
Click to expand...
Click to collapse
I see now what you want
mobile odin will always flash to primary rom! and it will destroy your second rom if you already have one
I would suggest you the nandroid method:
1) install with mobile odin the rom you want to have later as second rom, and also a custom recovery (latest devil if you want to use devil kernel, older devil recovery if you want to use googy max). if you have the paid version use the keep root option
2) reboot and look how it works
3) (install googy max kernel (or devil) within your custom recovery) edit: not needed
4) maybe reroot your rom within the recovery (there is an option)
5) make a nandroid backup of your primary rom to, if possible, external sd_card
6) reboot your phone and use again mobile odin to flash your other stock rom, and again your needed recovery (and root)
7) reboot, look if it works and reboot to recovery
8) flash your desired kernel and create within the recovery your second rom
9) in the recovery there should be an option to switch to the "second rom mode"
10) restore your first nandroid backup as second rom
11) reboot into second rom and look if it works.
12) voila your configuration :good::good:
What I want is pretty easy to brake describe, but to be sure all is clear, I will describe a bit different to first posting again:
- Dual ROM with two stock ROMs:
- Both Stock ROMs, only difference in Branding (two different Firmware-files, with Branding of two different Companies/Provider. Best if I can use original stock rom firmware file from sammoble),
- both same Android Version (4.3).
- New: My 1st ROM, primary active ROM, is already installed. In the end with dual boot config, this ROM should be the 1st ROM again. The second ROM should be the new ROM, with different firmware branding.
- New: 2nd ROM should be a fresh (clean) ROM or "wiped"
Thanks for your last explanation. I read so much, and thought it would be much easier to get me dual stock ROM configuration. My first ROM, primary and active ROM, is already installed. When I read your last explanation, I have to start with Step (5), because I have already my first active ROM, which should be in the end my 1st ROM again. So I think I have to change the whole steps, because I can not begin with your step 1.)
Your instruction:
Darkened_Sky said:
1) install with mobile odin the rom you want to have later as second rom, and also a custom recovery (latest devil if you want to use devil kernel, older devil recovery if you want to use googy max). if you have the paid version use the keep root option
2) reboot and look how it works
3) (install googy max kernel (or devil) within your custom recovery) edit: not needed
4) maybe reroot your rom within the recovery (there is an option)
5) make a nandroid backup of your primary rom to, if possible, external sd_card
6) reboot your phone and use again mobile odin to flash your other stock rom, and again your needed recovery (and root)
7) reboot, look if it works and reboot to recovery
8) flash your desired kernel and create within the recovery your second rom
9) in the recovery there should be an option to switch to the "second rom mode"
10) restore your first nandroid backup as second rom
11) reboot into second rom and look if it works.
12) voila your configuration :good::good:
Click to expand...
Click to collapse
I will write down the steps as I think how it could work with using your explanation. A review in detail would be nice. Thanks in advance
1) Make a nandroid backup of your actual active primary 1st ROM to, if possible, external sd_card. Need this back up, to reinstall as 1st ROM later.
2) Reboot your phone and use mobile odin to flash your 1st stock ROM now (to the firmware which should be 2nd ROM in the end), with recovery and root
3) Reboot, look if it works and then reboot again to recovery
4) In the recovery there should be an option to switch to the "second ROM mode". Use this to move 1st ROM to 2nd ROM.
5) Also in Recovery menu: Restore your first nandroid backup as 1st ROM (to have the first primary ROM backup as 1st ROm again)
6) Check if both ROMs work.
In your explanation was a step ...
8) flash your desired kernel and create within the recovery your second rom
... I don't know how to integrate it, because don't understand it.
You wrote...
10) restore your first nandroid backup as second rom
... I think you meant "restore your first nandroid backup as first rom", right?
This is really the easiest way to get my configuration? So there is no "direct install stock ROM from sammobile as second ROM" solution?. Because this second stock ROM installation as 2nd ROM is the only part which is missing at the moment.
I also only need a fresh (clean) 2nd ROM installation, not a clone of 1st ROM, this is also a workaround. But I can wipe data for 2nd ROM at the end.
Big thanks!
Der dicke Baer said:
In your explanation was a step ...
8) flash your desired kernel and create within the recovery your second rom
... I don't know how to integrate it, because don't understand it.
You wrote...
10) restore your first nandroid backup as second rom
... I think you meant "restore your first nandroid backup as first rom", right?
Click to expand...
Click to collapse
no I meant it as I said. because my idea was it to first flash your desired second rom as first rom, backup it and later restore it as your second rom. but you can also do your way
with create second rom step i meant that you have to create the second rom partition in which you can restore your nandroid.
Der dicke Baer said:
This is really the easiest way to get my configuration? So there is no "direct install stock ROM from sammobile as second ROM" solution?. Because this second stock ROM installation as 2nd ROM is the only part which is missing at the moment.
I also only need a fresh (clean) 2nd ROM installation, not a clone of 1st ROM, this is also a workaround. But I can wipe data for 2nd ROM at the end.
Click to expand...
Click to collapse
sadly I cannot think of a better way, because there is no possibility to directly install a stock rom in the tar.md5 format as second rom. only ".zips" can be flashed in recovery. Only alternative would be to transform the odin tar.md5 into a flashable zip, but that would be really complicated (there is somewhere a how to thread, but trust me it is way to complicated, if you can still use an alternative instead)
btw. there is no option "move 1st rom to second rom" in devil recovery, if I remember correctly (but not really sure atm). You have to do it manually (make a nandroid backup and restore it as second rom)
otherwise, your steps should work.
Ah, ok. First I have to decide if I want to do it by the "Newest-Full-Devil-Kernel"-way or by the "Googy-with-Not-Latest-Devil-Revovery"-way. Then I hope it's ok to explain the steps in detail in the googy-thread or the devil-thread, to get agreement there that this steps should work.
And I thought it would be easy.
Big Thanks Darkened_Sky!
Of someone has other ideas, please let me know.