Related
hi guys,
i am a total noob to android and i just bought a vibrant(used)
it has the firmware version 2.1-update 1 .
i have rooted the phone and now have super user permission(downloaded update.zip and went to recovert mode).
and installed titanium backup then rom manager..
backed up too and flashed the clockworkmod recovery 2.5.1.2 .
then downloaded the custom rom "nero beta 3 with voodoo".
copied it to internal 16 gig storage then went to rom manager then "reboot into recovery"
everything was ok untill that point.
but in recovery,i always get blue screen with 4 options and no matter what i tried nothing happens..
please someone help me with this problem..
thanks
Ok, let me take a shot at it
go to your phone /sdcard/clockworkmod and copy recovery-update.zip into /sdcard as update.zip (you might have a file update.zip in there possibly to root your phone, you don't need it, just rename it and archive it for future use if you need to re-root your phone, etc.).
Now reboot into recovery, and select reinstall packages, it will read the cwr update.zip and will go to a similar screen with green text, from there you can select a zip to install, and flash away.
I would strongly suggest though you download a ROM that is not marked as beta - there are a few options available from different teams.
just hit reinstall packages a couple times
lqaddict said:
Ok, let me take a shot at it
go to your phone /sdcard/clockworkmod and copy recovery-update.zip into /sdcard as update.zip (you might have a file update.zip in there possibly to root your phone, you don't need it, just rename it and archive it for future use if you need to re-root your phone, etc.).
Now reboot into recovery, and select reinstall packages, it will read the cwr update.zip and will go to a similar screen with green text, from there you can select a zip to install, and flash away.
I would strongly suggest though you download a ROM that is not marked as beta - there are a few options available from different teams.
Click to expand...
Click to collapse
hi it worked !!
but new problem.. its in clockworkmod recovery and says
"installing: SDCARD:Nero_3TWE_voodoo.zip
Finding update package... "
its been sometime but nothins changes than that
royalkalana said:
hi it worked !!
but new problem.. its in clockworkmod recovery and says
"installing: SDCARD:Nero_3TWE_voodoo.zip
Finding update package... "
its been sometime but nothins changes than that
Click to expand...
Click to collapse
Wait for it to finish!!! It might take a little long.
P.S. You didn't happen to put your ROM zip file on your external card, did you?
lqaddict said:
Wait for it to finish!!! It might take a little long.
P.S. You didn't happen to put your ROM zip file on your external card, did you?
Click to expand...
Click to collapse
no no i read soo many threads so i know the process(theoretically lol )
i put the file to 16 gig internal.. and i got the green screen as u said then it found the rom too ..
i forced to power on and going to try again
please let me know what i should know
thanks
hi it worked it worked !!
thanks lqaddict and jmcghee1973 for ur help.specially lqaddict thanks alot for ur time mate
royalkalana said:
hi it worked it worked !!
thanks lqaddict and jmcghee1973 for ur help.specially lqaddict thanks alot for ur time mate
Click to expand...
Click to collapse
No problem I am glad to help. Enjoy your new Vibrant!
lqaddict said:
No problem I am glad to help. Enjoy your new Vibrant!
Click to expand...
Click to collapse
and can you recommend some stable and good custom roms for me please ?
royalkalana said:
and can you recommend some stable and good custom roms for me please ?
Click to expand...
Click to collapse
It's all user preference
All the current ROM's in the dev section can be considered at this point stable to a degree that the core functionality of the phone is working properly, there might be some quirks with advanced configurations.
Some of the established ROM's are Eugene's Ginger Clone, Team Whiskey Nero and Master's and his team Axura.
My own preference is TW NeroV3 running Supercurio's Voodoo on JL5 build.
Can't go wrong with the latest Voodoo based ROM's, they are smooth, fast and a pleasure to use.
And whoever says that once you flash a custom ROM you are in for a bag of tweaking for the rest of the phone's life I strongly disagree, I can easily see how I can stay with NeroV3 until a stable ROM based on the current iteration of Android OS - Gingerbread - appears here.
P.S. Just be careful when you flash from ROM to ROM, the current ROM's the incorporate Voodoo infused kernels do not require you to disable Voodoo before flashing a Voodoo based ROM, otherwise you must disable it before you flash another ROM. As a common practice, it is best to disable Voodoo before flashing another ROM anyway, and one of the preferred methods is to flash back to stock JFD via ODIN before you flash another ROM to hunt all the ghosts of the ROM past.
Read, read, read and read some more - the Bible in the dev section is a good place to start.
lqaddict said:
It's all user preference
All the current ROM's in the dev section can be considered at this point stable to a degree that the core functionality of the phone is working properly, there might be some quirks with advanced configurations.
Some of the established ROM's are Eugene's Ginger Clone, Team Whiskey Nero and Master's and his team Axura.
My own preference is TW NeroV3 running Supercurio's Voodoo on JL5 build.
Can't go wrong with the latest Voodoo based ROM's, they are smooth, fast and a pleasure to use.
And whoever says that once you flash a custom ROM you are in for a bag of tweaking for the rest of the phone's life I strongly disagree, I can easily see how I can stay with NeroV3 until a stable ROM based on the current iteration of Android OS - Gingerbread - appears here.
Click to expand...
Click to collapse
thanks alot mate..
i think you are saying about this rom
http://forum.xda-developers.com/showthread.php?t=883379
i installed the same
and it is soo cool..
but i dont know what is the difference between voodoo enable/disable.
and couldnt find that disable lag fix file
""" On your internal sdcard, you will find a voodoo folder containing a file called 'disable-lagfix'. This was pre-installed when you flashed. Find it.
Delete the 'disable-lagfix' file from the voodoo folder """
any idea about it ?
thanks again
royalkalana said:
thanks alot mate..
i think you are saying about this rom
http://forum.xda-developers.com/showthread.php?t=883379
i installed the same
and it is soo cool..
but i dont know what is the difference between voodoo enable/disable.
and couldnt find that disable lag fix file
""" On your internal sdcard, you will find a voodoo folder containing a file called 'disable-lagfix'. This was pre-installed when you flashed. Find it.
Delete the 'disable-lagfix' file from the voodoo folder """
any idea about it ?
thanks again
Click to expand...
Click to collapse
Voodoo converts your phone's filesystem to EXT4 (I am not gonna bore you with the technical details ), it is faster better filesystem than the one Samsung implemented. What it does, it virtually eliminates lag when you scroll/open apps, etc.
Now onto enabling/disabling Voodoo.
While your phone is up and running if you press and hold your power button for a few seconds a menu will appear, choose Recovery, and your phone should reboot into modified clockwork recovery, now all your green texts are now bloody red, navigate to Voodoo lagfix option (i think that what it is called, sorry cannot replicate it on my phone it is currently in use ) and you can enable/disable Voodoo from there.
Just let it do its thing, it will take a bit of time to convert the filesystems, do not touch your phone until the process is completed.
lqaddict said:
Voodoo converts your phone's filesystem to EXT4 (I am not gonna bore you with the technical details ), it is faster better filesystem than the one Samsung implemented. What it does, it virtually eliminates lag when you scroll/open apps, etc.
Now onto enabling/disabling Voodoo.
While your phone is up and running if you press and hold your power button for a few seconds a menu will appear, choose Recovery, and your phone should reboot into modified clockwork recovery, now all your green texts are now bloody red, navigate to Voodoo lagfix option (i think that what it is called, sorry cannot replicate it on my phone it is currently in use ) and you can enable/disable Voodoo from there.
Just let it do its thing, it will take a bit of time to convert the filesystems, do not touch your phone until the process is completed.
Click to expand...
Click to collapse
thanks mate.. you've been a big help for me..
btwn.. how could i know that its enable after i did that process ? is there a way for that ?
royalkalana said:
btwn.. how could i know that its enable after i did that process ? is there a way for that ?
Click to expand...
Click to collapse
The bulletproof way is to use a terminal emulator app or use adb to execute the follwing command
Code:
mount
If you see ext4 next to /data, /system, /cache and /dbdata in the output you are golden
thanks lqaddict
▐▄▀▄▀▌ TUTORIAL CWM roms are the way to go right now!!!
THIS IS A TUTORIAL TO GET CWM ROMS UP AND RUNNING ON UR RHODIUM
SO i felt completely compelled to share my amazing experience and results with my CWM rom!!!!
i almost always try to keep the development process here away from other sites
if you want a REALLY GOOD WORKING version of android on your device without trying NAND ... follow my instructions...
first off i have a ATT Tilt 2 i have been using with this..
to find anything you need to know on android for our phones go HERE
(Neopeek site)
any size card should do for runing CWM builds,,, i however am runnig an 8gb class 4 sdhc and all is well
MY recommended partition sizes... (i set 300mb as all my EXT2 partitions just to make calculating it easier...)
(primary) FAT32 - storage for music videos pics etc... rest of space
(primary) EXT2 - 200-300mb (system) holds rom build... none are over 250mb
(primary) EXT2 - 200-300mb (data) data for android... i believe is the space for app install... so bigger is better..
(primary) EXT2 - 50-100mb (cache) like ram sorta...
with these sizes... worryin about the size of the rom will not matter ..
look on the site link i posted above on how to install and use CWM if you havent before... (dont worry newbs... its easier then everyone makes it seem...)
with CWM builds the standard Gapps are not included...
THIS SITE is the repository to go to... i am using "gapps-hdpi-20101114-signed.zip" but feel free to try others to see if they load...
this is the the most frustrating part of CWM, finding GAPPS that install...
u install them the same way you do a rom... by installing the zip from the sd card...
i do recommend installing gapps zip after you have already installed the rom and booted and restarted android a couple of times
otherwise i recommend THIS ROM as it is the one i use... i know it is only Froyo but it has a themed gingerbread taskbar with black pull down so it still looks nice!!!
lastly
((((technically test kernel.. so not recommended!!... but proven to fix screen not coming on problem...))))
for you crazy tester ppl waiting for the day you brick your phone(im totally kidding dont worry newbs) i use the WIS-Tilt2 kernel the newer test one to be specific...
GO HERE
With this kernel my device goes in to deep sleep with the GReen light and wakes up perfect every time!!!!!
the zip is just modules package and a zImage.. just have to replace and boot...
WARNING... when i updated with the working kernel it looked like it wasnt going to work.. didnt seem to be anywhere enough scrolling text and the boot animation barely played and then the screen went black... i played around with the buttons and found the device to be opperating with out the screen on i kept pressing buttons and the screen finally woke up!!!! be patient!!!! after that it worked perfectly everytime...
other tips... for people experiencing wifi unable to scan problem ..
use the Wifi-nvram.txt trick look it up in xda... once command is entered no need to reboot just turn on wifi and connect!!!
i hope that this has been helpful i couldnt find any where that had all the tips and tutorial in one place to get CWM up and running at least once... had to do it trial and error.. hope my hard work will help you newbs out!!! hahaha
---
Here is the CMW version of the normal FRX06 by arrrghhh. Credits to arrrghhh for the build and to preston74 for making it ready for CMW.
G-apps are already included in this build so you don't have to flash them separate.
http://www.multiupload.com/2VS5ZKUFBA
jellenl said:
Here is the CMW version of the normal FRX06 by arrrghhh. All credits goes to him, I only made it ready for clockwork mod. Gapps are already included so you don't have to flash them seperate with this build.
http://www.multiupload.com/TQSN4TG28U
Click to expand...
Click to collapse
thanks guy...
\
i want to make it as easy on peopl eto get a stable working version of android on their TP2's
Well, i used CWM with an 1GB SD and worked like a charm...
and first time i did it with a 2gb... i just said more cause there is more room for apps... lol
should prolly clarify that...
Trekfan422991 said:
thanks guy...
\
i want to make it as easy on peopl eto get a stable working version of android on their TP2's
Click to expand...
Click to collapse
Yes you are doing a good job
I first made a cmw version of frx06 without gapps, but argghhh told me it was ok if I include the gapps, so I did
You may also integrate my link in your first post, then I'll delete my post.
Forgive me here... I am new to the CWM builds. If I have a CWM build on an SD card, with the appropriate ex2 partitions and all, can I use CWM to put on a different build? That would be a whole lot easier than having to reformat and start over...
Well if you run in to any problems the support here is going to be limited.
On the other hand if you use XDAndroid the support here is maximal.
For testing and dev reasons, I will stay with my current build. I quite like my bluetooth.
For any beginners I would very much recommend that you use 'standard' (see intro to android sticky). Well, at least until you are confident you don't need to be hand-guided through this and know what to do if something goes wrong.
ppcfly said:
Forgive me here... I am new to the CWM builds. If I have a CWM build on an SD card, with the appropriate ex2 partitions and all, can I use CWM to put on a different build? That would be a whole lot easier than having to reformat and start over...
Click to expand...
Click to collapse
It actually is pretty easy - you can backup your current system & data partitions, and throw a new build on - if you don't like it, wipe and revert to the backup.
The only problem is if you have CWM installed, other 'normal' (looped mount) builds will not work - the rootfs will see the partitions and think you want to run from partitions - of course, this results in a failure to boot... I like having many builds on my card at one time so I can flip between them - this also makes testing a heckuva lot easier, so heads up folks!
Nice tutorial and thanks for putting my build in it,but you should put proper credits as Neopeek(and his team) made cwm and i made the build you linked(you can avoid doing this)
And it's gingerbread like themed and the theme name is minimal green..
You can avoid doing 300 mb system as almost all the builds are less than 100 mb,so doing it 150mb is good
CWM and loopmounted builds can co-exist.
arrrghhh said:
The only problem is if you have CWM installed, other 'normal' (looped mount) builds will not work - the rootfs will see the partitions and think you want to run from partitions
Click to expand...
Click to collapse
To avoid this you can just add the "no_partitions" (without the quotes) switch to your cmdline on your startup.txt of the loopmounted build and you should be good to go.
It may depend on your rootfs, but I'm using F22's rootfs and it works like a charm.
i'm trying cwm with frx6 and it keep saying fail rootfs., what am i doing wrong?
Do you followed the tutorial on how to set up your sd-card for cmw? I think you are using a wrong rootfs. As far as I know you need the rootsf from neopeek's cmw.
jellenl said:
Do you followed the tutorial on how to set up your sd-card for cmw? I think you are using a wrong rootfs. As far as I know you need the rootsf from neopeek's cmw.
Click to expand...
Click to collapse
i"ve gotten into CWM but now its telling cand find the zip find even after scroll down to the update. do need to just rename update_frx6 to just plain update. It say installation aborted. I'm using update-frx6
drynaps said:
To avoid this you can just add the "no_partitions" (without the quotes) switch to your cmdline on your startup.txt of the loopmounted build and you should be good to go.
It may depend on your rootfs, but I'm using F22's rootfs and it works like a charm.
Click to expand...
Click to collapse
Damnit, hyc even told me about this - and I forgot about it.
Thanks for mentioning it!
villa15 said:
i"ve gotten into CWM but now its telling cand find the zip find even after scroll down to the update. do need to just rename update_frx6 to just plain update. It say installation aborted. I'm using update-frx6
Click to expand...
Click to collapse
I think you are choosing the wrong item in cmw, you need to choose 'Install zip from sd-cart' and then 'choose zip from sdcard'. Don't choose 'apply sdcart/update.zip' or something like that.
And if that doesn't work, maybe try another build. There is a (really small, because I tested it myself) option that the frx06 cmw build doens't work well.
jellenl said:
I think you are choosing the wrong item in cmw, you need to choose 'Install zip from sd-cart' and then 'choose zip from sdcard'. Don't choose 'apply sdcart/update.zip' or something like that.
And if that doesn't work, maybe try another build. There is a (really small, because I tested it myself) option that the frx06 cmw build doens't work well.
Click to expand...
Click to collapse
No thats not it. i did just just what u are saying. I even tried the CherryPieV3 and it still installation aborted. I'm using CWM 1.8 could that be the problem
If you already have CWM files on your phone, then do not just install the CherryPieV3.zip file. You must extract the zip file which has another zip file inside that you should use to install in CWM.
bleuleon said:
If you already have CWM files on your phone, then do not just install the CherryPieV3.zip file. You must extract the zip file which has another zip file inside that you should use to install in CWM.
Click to expand...
Click to collapse
Yes, you´re right. But he said that he also tried frx06, and that doesn´t worked for him too, and with the frx06.zip bundle, you don´t need to extract it first (if i'm right ;p)
jellenl said:
Here is the CMW version of the normal FRX06 by arrrghhh. All credits goes to him, I only made it ready for clockwork mod. Gapps are already included so you don't have to flash them seperate with this build.
Click to expand...
Click to collapse
I tried to install your CMW version of he Arrghhh FRX06 build but it fails on installing.
I have followed all the steps closely but still can't get it installed.
In the CWM tool when I choose Install zip from SD card and then choosing the FRX06 update the install process starts and within a few seconds aborts.
This is what I see on my screen:
Installing: // sdcard/npkboot/update-frx06.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted
Using the FRX06 CWM build from this thread with the WIS-Tilt2 kernel.
Does anybody have a clue about why this is not working?
Hello you DualBooters and Triplebooters out there!
SDCacheMount for SD-Roms
Well, this idea came to me because many users of my triple-boot SD were getting tired of the rebuilding of system-cache when every time they had to switch between roms. What I have here is a small script that will install to /system/etc/init.d The script will run at boot time and create a 100mb .img file to be used for /cache. This way each rom will have its own dedicated /cache partition so to say. This will also benefit anybody that dualboots (eg. EMMC / SD-Rom). I've prepped two different versions. One for my triplebooters out there and the other for anyone running a rom off an SD card.
Things to note:
-This will dd a 100mb .img file to your /sdcard partition of your sd-rom on first boot. What this means is that before the system progresses any further the img file needs to be created so that the /system can use it as the /cache partition.
-It will sit at a black screen for up to 1 minute possibly. So please be patient!!!
-The dd'ing of the .img only happens on first boot. So once the cache .img is created. Boot time will be normal on successive boots.
-Make sure you have enough space on the /sdcard partition of your sd-rom.
-So for Dualbooters you will need at least 100mb free
-For Triplebooters you will need at least 200mb free
-Now you can switch between EMMC roms and SD roms without having to wait for /cache to rebuild every single time.
DOWNLOAD:
DUALBOOTERS ( EMMC / SD )
**You should be able to flash this from a standard CWM Recovery or rename the .zip file to begin with "update-" for Verygreens method.**
SDCacheMount_DualBooters.zip
Click to expand...
Click to collapse
TRIPLEBOOTERS ( EMMC / DUALBOOT-SD )
**You should only use the CWM Recovery that is included with my Dualboot-SD**
SDCacheMount_TripleBooters.zip
Click to expand...
Click to collapse
Big thanks to:
DizzyDen for helping me out with the script
Shumash for troubleshooting it for me
Inportb for some guidance
HacDan for his sense of humor
Hope this helps a few of you Nookers out there!
Thanks,
Racks
Reserved?!
Great job! gonna have a try on this
So the main advantage of this script is smaller booting time?
And this is the case when you switch Roms only between emmc and sd or also 2 different roms from same sd?
Unleashed from my Nook Color at 1.2G
RASTAVIPER said:
So the main advantage of this script is smaller booting time?
And this is the case when you switch Roms only between emmc and sd or also 2 different roms from same sd?
Unleashed from my Nook Color at 1.2G
Click to expand...
Click to collapse
The advantage of the script is that each AOSP will have its own dedicated cache and not all be utilizing the same space for all the cache.
RASTAVIPER said:
So the main advantage of this script is smaller booting time?
And this is the case when you switch Roms only between emmc and sd or also 2 different roms from same sd?
Unleashed from my Nook Color at 1.2G
Click to expand...
Click to collapse
The most obvious effect is that booting between the various ROM's is seamless (except for the minimal wait at the blank screen) and fast. It makes switching between the AOSP's very easy. The less obvious, behind the scenes effect is as Dizzy describes.
It should be noted that if you flash an updated or newer ROM, you will also need to reflash the SDcacheMount.zip.
shumash said:
The most obvious effect is that booting between the various ROM's is seamless (except for the minimal wait at the blank screen) and fast. It makes switching between the AOSP's very easy. The less obvious, behind the scenes effect is as Dizzy describes.
It should be noted that if you flash an updated or newer ROM, you will also need to reflash the SDcacheMount.zip.
Click to expand...
Click to collapse
Yes correct, thank you. I'll make note of that in the OP. Also note that once the .img cache is created, although you have to reflash the SDCacheMount after flashing a new rom. It won't have to create a new .img. The script will detect if one exist already and if so, proceed to boot. But if you don't flash the SDCacheMount right after flashing the new ROM. /cache will default back to /emmc
-Racks
Hello guys,
I saw a lot of users (also me xD) that frequently have build.prop error when flashing a custom rom from another custom rom.
Well, i created a simple flashable .zip that contains the original build.prop, needed by custom roms like cm.
How to use that:
1. Flash this fix BEFORE installing any custom roms.
2. After it installed, reboot recovery for applying changes.
3. Install your custom rom.
4. Enjoy it!
Hope it helps some users sorry for my bad English
Wouldn't the build.prop be erased when installing a custom ROM as the system partition is formatted?
If that's not the case I'll download and keep this safe in case I have the same problem in the future lol. Thanks.
Sent from my R800i using xda premium
you have to format system partition before flashing this fix or you'll lose build.prop, and you need to reflash them
installing custom rom doesn't make you lose build.prop
sorry for my poor English
Ah.. Makes much more sense then lol...
Although some ROMs do format the system partition before install, so I'm assuming those wont work..
Also - Your English is pretty decent compared to a lot of people!
I think it will work also with that kind of roms, because for fully applying changes you need to reboot recovery, that otherwise views build.prop also if in your /system directory it doesn't exist
Spizzy01 said:
Ah.. Makes much more sense then lol...
Although some ROMs do format the system partition before install, so I'm assuming those wont work..
Also - Your English is pretty decent compared to a lot of people!
Click to expand...
Click to collapse
I hope you're leaving the American and English out of this comparison.
Anyway, nice patch! I'll try this if I run into this error!
Selim873 said:
Anyway, nice patch! I'll try this if I run into this error!
Click to expand...
Click to collapse
Thanks man
Selim873 said:
I hope you're leaving the American and English out of this comparison.
Anyway, nice patch! I'll try this if I run into this error!
Click to expand...
Click to collapse
In some cases.. You'd be surprised... xD
I don't think you know what a status 7 error is. It has NOTHING to do with the build.prop. Status 7 refers to updater-script found in the META-INF file. Delete the get product info lines or something similar to that. This is actually a waste of time to make some zip when it's simpler to delete three lines. Build your "thanks meter'" some other way. Oh, and by the way, changing your build.prop to some random one can really screw your phone up.
Some ROMs do an assert check or something. Does this flash the build.prop for this phone to allow flashing to take place?
That's a very good idea if so. It could be avoided by the build.prop check, but this will do.
Sent from my R800i using xda app-developers app
agraceful said:
I don't think you know what a status 7 error is. It has NOTHING to do with the build.prop. Status 7 refers to updater-script found in the META-INF file. Delete the get product info lines or something similar to that. This is actually a waste of time to make some zip when it's simpler to delete three lines. Build your "thanks meter'" some other way. Oh, and by the way, changing your build.prop to some random one can really screw your phone up.
Click to expand...
Click to collapse
did you try to delete that lines from updater script in roms based on jelly bean?
try and tell me if it's simple
@MilkyJoePD yeah, it allows you to install roms that do an assert check. you still can remove the getprop lines from updater script (the 1st 4 lines), but on jb roms there are some files with the same names especially in /system/etc/terminfo, and that's compromises the good re-zip of your rom. that's what "agraceful" doesn't know, because he never tryed yet
again sorry for my English
Hi people. I've been browsing a lot lately and Reading about roms, kernel, and other stuff related to customization of Android devices. I consider myself enough tech-savvy to understand technical things about hardware on this devices but when it comes to all the thing related to flashing roms and kernels and related things i have no clue of what you're talking about, lol.
However, I'm really interested on "installing" Cyanogenmod 10 on my Galaxy Player 4 just to see what happens and how flashing roms feels like, so i can try different roms later and enhance my device. But no matter how hard I try to find a tutorial about how to begin from total stock (as the device comes from the store) haven't been lucky finding one. As far as I know the first step is flashing a new kernet with CWM, so then i can flash the roms. But I'm stuck on Step One :s
So, if there's a link you can post here to help begin with this flashing trend it'd be great. Or if you can redact a "custom" tutorial for me, a total programming noob but interested as hell about modifying my GP4 that would be a thousand times better.
Also, feel free to recommend me kernels or roms or whatever you feel i could use
Thanks!!!
PD: not native english speaker
I just finished doing this exact thing myself, so its fresh in my mind First, BACK UP!! there are different methods with varying degrees of how much they back up, search the forum for them. Definitely backup the efs. Instructions are in the first post for the CM10 ROM. Then, I began by flashing a custom kernel using Odin. Instructions on how to do this can be found in the Tips and Tricks section of this post:
http://forum.xda-developers.com/showthread.php?p=27615927
Kernels can also be found in the appropriate section of that post. Make sure you get one for your device. All of them include CWM (ClockworkMod) which is what you need to easily flash a full ROM. The kernel won't actually effect your current operating system accept to maybe improve performance.
Next, download the ROM file(s) onto your device. ROMs are also in the above post. Again, make sure you get one for your device. Read the instructions in the ROM thread on how exactly to flash them, but the general procedure is to boot into CWM by holding some set of buttons during start up (probably power + volume up) and navigate the CWM menu to flash the ROM.
Sent from my YP-G1 using xda app-developers app
from stock
download odin: https://docs.google.com/file/d/0B2ZcXCdM0CVJS196MFRtaUhfSUk/edit?usp=sharing
boot into download mode
flash terra silent: http://forum.xda-developers.com/showthread.php?t=1643384
download rom and gapps: rom: http://forum.xda-developers.com/showthread.php?t=2233983 gapps: http://goo.im/gapps/gapps-jb-20121011-signed.zip
put on sdcard
BACKUP!!!
flash rom and gapps
reboot
thanks a lot for the help!
Now a question... When you tell me to make a backup, what exactly should I backup and with what program or app? Installed Titanium BAckup app and all i see is the option to backup individual apps. I expected to find something like "total backup of the device" or a similar thing that bacups the whole thing...
please tell me what to use and what to do
thanks a lot again
kennethac said:
thanks a lot for the help!
Now a question... When you tell me to make a backup, what exactly should I backup and with what program or app? Installed Titanium BAckup app and all i see is the option to backup individual apps. I expected to find something like "total backup of the device" or a similar thing that bacups the whole thing...
please tell me what to use and what to do
thanks a lot again
Click to expand...
Click to collapse
Create a backup in cwm
This is so if anything goes wrong, you can get back
Sent from my Kindle Fire running CM10.1/SGT7
Ok i downloaded both Odin and the Terra Silent kernel. Samsung kies is already installed so Odin is detecting my galaxy player.
But the terra silent kernel is a zip file, if i extract it the extracted file has no extension, only says zlimage and i have no idea what it is. Then, when I open Odin, there are the next options:
PIT
BOOTLOADER
PDA
PHONE
CSC
where should i upload the zlimage?
kennethac said:
Ok i downloaded both Odin and the Terra Silent kernel. Samsung kies is already installed so Odin is detecting my galaxy player.
But the terra silent kernel is a zip file, if i extract it the extracted file has no extension, only says zlimage and i have no idea what it is. Then, when I open Odin, there are the next options:
PIT
BOOTLOADER
PDA
PHONE
CSC
where should i upload the zlimage?
Click to expand...
Click to collapse
That's because you're suppose to flash it via CWM. If it's a tar file, you flash it via Odin. And you're not suppose to extract it, lol.
TheKryptonite said:
That's because you're suppose to flash it via CWM. If it's a tar file, you flash it via Odin. And you're not suppose to extract it, lol.
Click to expand...
Click to collapse
haha ok i'm not extracting it anymore. But from those options that shows Odin, where i have to upload the "TerraSilent_usa-1.3.5" file?
This is what i see...
PIT
BOOTLOADER
PDA
PHONE
CSC
that's where i need help for the moment
kennethac said:
haha ok i'm not extracting it anymore. But from those options that shows Odin, where i have to upload the "TerraSilent_usa-1.3.5" file?
This is what i see...
PIT
BOOTLOADER
PDA
PHONE
CSC
that's where i need help for the moment
Click to expand...
Click to collapse
PDA is the one, I believe.
Is Terra Silent compatible with CM10??? Reading the thread of Terra Silent a user made a comment on this asking the developer (i guess) to make Terra Silent compatible with CM10.... :s
ok now i have some problems...
got to flash the Terra Silent Kernel. After rebooting everything was ok. Installed Rom Manager in order to install CWM. Rom Manager installed CMW and then came back to main menu. There was an option for creating a copy of the stock rom, thought it wolud be a good idea to make a copy. When i did it, phone went black and then reboted. after rebooting came back to the lock screen but changed language (spanish -> english). Algo noticed there was missing the google search bar. When entered to the apps menu there were a lot of icons of the android robot with an SD card symbol over. When clicked them it says that the apps are not installed on the system.
installed rom manager again, and went to recovery boot. flashed both cm9 and cm 10 included in the cm 10 thread. Now my playr is stuck in the recovery screen...
what do i do?
kennethac said:
ok now i have some problems...
got to flash the Terra Silent Kernel. After rebooting everything was ok. Installed Rom Manager in order to install CWM. Rom Manager installed CMW and then came back to main menu. There was an option for creating a copy of the stock rom, thought it wolud be a good idea to make a copy. When i did it, phone went black and then reboted. after rebooting came back to the lock screen but changed language (spanish -> english). Algo noticed there was missing the google search bar. When entered to the apps menu there were a lot of icons of the android robot with an SD card symbol over. When clicked them it says that the apps are not installed on the system.
installed rom manager again, and went to recovery boot. flashed both cm9 and cm 10 included in the cm 10 thread. Now my playr is stuck in the recovery screen...
what do i do?
Click to expand...
Click to collapse
Did you wipe the data, cache, and Davik cache?
TheKryptonite said:
Did you wipe the data, cache, and Davik cache?
Click to expand...
Click to collapse
Sorry. False alarm, i finally found i was doing something wrong so corrected it and now i'm using Jelly Bean in my galaxy player. But now there's another problem: system won't read the external SD card.
How can i fix this?
kennethac said:
Sorry. False alarm, i finally found i was doing something wrong so corrected it and now i'm using Jelly Bean in my galaxy player. But now there's another problem: system won't read the external SD card.
How can i fix this?
Click to expand...
Click to collapse
You internal SD card is probably switched for the external.
Find "vold.fstab. (system/etc)" open it, and change "/mnt/sdcard/sdcard1" to "/mnt/sdcard/sdcard0."
TheKryptonite said:
You internal SD card is probably switched for the external.
Find "vold.fstab. (system/etc)" open it, and change "/mnt/sdcard/sdcard1" to "/mnt/sdcard/sdcard0."
Click to expand...
Click to collapse
This is what the file shows:
#internal sdcard
dev mount sdcard / storage /sdcard0 1 /
devices/platform/s3c-sdhci.0/mmc host/mmco
#external sdcard
dev mount emmc /storage/sdcard1 auto /
devices/platform/s3c-sdhci.2/mmc_host/mmc1
what's the part that i have to edit???
kennethac said:
This is what the file shows:
#internal sdcard
dev mount sdcard / storage /sdcard0 1 /
devices/platform/s3c-sdhci.0/mmc host/mmco
#external sdcard
dev mount emmc /storage/sdcard1 auto /
devices/platform/s3c-sdhci.2/mmc_host/mmc1
what's the part that i have to edit???
Click to expand...
Click to collapse
#internal sdcard
dev mount sdcard / storage /sdcard1
#external sdcard
dev mount emmc /storage/sdcard0
Wait, before doing any changes like this, have you tried on going mnt/emmc or storage/sdcard1? @TheKryptonite he have a 4.0 and the sdcard is working without changing the paths.
Envoyé depuis mon Nexus 7 avec Tapatalk
zaclimon said:
Wait, before doing any changes like this, have you tried on going mnt/emmc or storage/sdcard1? @TheKryptonite he have a 4.0 and the sdcard is working without changing the paths.
Envoyé depuis mon Nexus 7 avec Tapatalk
Click to expand...
Click to collapse
That is the same thing four me. I did not have to switch storages at all
Sent from my Kindle Fire running CM10.1/SGT7
TheKryptonite said:
#internal sdcard
dev mount sdcard / storage /sdcard1
#external sdcard
dev mount emmc /storage/sdcard0
Click to expand...
Click to collapse
I did this change, switched numbers and now i can see the files on the sd card. Only that before flashing CM 10 the access to the sd card was through a folder calles "externa sd", now the sd card files and folders are scattered on the home screen of any file explorer i acess the sd card with. It's not a big ideal but i dont like it.
When i edited the file you told me there was a 1 after where now says sdcard 1. Shoud that number be erased or better keep it?
kennethac said:
I did this change, switched numbers and now i can see the files on the sd card. Only that before flashing CM 10 the access to the sd card was through a folder calles "externa sd", now the sd card files and folders are scattered on the home screen of any file explorer i acess the sd card with. It's not a big ideal but i dont like it.
When i edited the file you told me there was a 1 after where now says sdcard 1. Shoud that number be erased or better keep it?
Click to expand...
Click to collapse
I'd keep it.