Related
i downloaded it. installed it with astro. hit reboot. and now the phone wont go past
TMOBILE G1
please help me!!!
oh and im using the newest cyan
trexxcrap2 said:
i downloaded it. installed it with astro. hit reboot. and now the phone wont go past
TMOBILE G1
please help me!!!
oh and im using the newest cyan
Click to expand...
Click to collapse
You're not supposed to use any other apps2sd with cyanogenmod, it says that plainly in the instructions.
I think the easiest thing is to wipe and reflash.
AdamPI said:
You're not supposed to use any other apps2sd with cyanogenmod, it says that plainly in the instructions.
I think the easiest thing is to wipe and reflash.
Click to expand...
Click to collapse
i went to the menu that says restore to factory / wipe and its still not booting. what exactly do i need to do / download. thanks. (sorry for bein dumb)
You need to wipe your ext partition now. Search this forum for the instructions. Then you need to go back to the CyanogenMod thread and memorize all the warnings he has posted.
You better start reading carefully before you brick your phone. There are multiple warnings saying DO NOT USE ANY OTHER APPS2SD METHOD. Just about all roms now are auto when it comes to apps2sd.
i wiped the phone and took out the sd and it still doesnt boot. do i need to root agian? ughhhh
trexxcrap2 said:
i wiped the phone and took out the sd and it still doesnt boot. do i need to root agian? ughhhh
Click to expand...
Click to collapse
Just reflash your rom.
supremeteam256 said:
Just reflash your rom.
Click to expand...
Click to collapse
i searched for "wipe ext partition" and cant find anything. can you point me in the right direction?
and thank you guys so much
go into parted from the recovery console.
use "print" to show your partitions, write down the start and stop locations
use "rm 2" replacing my 2 with your ext partition number but most likely it's 2 anyways
then remake the partition using the start and stop locations from the "print" results.
type "quit" or "exit" (i forget which one.
now type "upgrade_fs"
now type reboot recovery and reflash the rom
mmmmmmmmm yummy, a big ol' bowel of booty loops, the prize in the box is an android
thanks guys! with your help she is up and running
but one more question. since i have the new cyan build and you guys say apps2sd is built in how do i activate it? i have an icon at the top saying memory is low.
last question i promise thank you!!!!
trexxcrap2 said:
thanks guys! with your help she is up and running
but one more question. since i have the new cyan build and you guys say apps2sd is built in how do i activate it? i have an icon at the top saying memory is low.
last question i promise thank you!!!!
Click to expand...
Click to collapse
All you need in order to get the apps to automatically be moved to the SD card, is to have an existing ext3 partition.
As someone said earlier, use Cyan's recovery (which hopefully you flashed to, right?) and use the Parted application to create an ext2 partition. You will then go back to the normal recovery console and run the script "upgrade_fs", which will upgrade the filesystem from ext2 to ext3.
Hi all...
I've been getting a lot of suspicious errors recently (force closes and app shortcut names disappearing) and I'd like to go from apps2sd back to just a normal setup with my apps on the internal phone storage.
Can somebody please verify that the instructions here are up to date? I'm a little nervous about wiping my data (or bricking my phone).
http://wiki.cyanogenmod.com/index.php/Apps2SD
Also, can somebody tell me whether doing this will wipe out the (single) app I paid for from the Marketplace? If so, can I redownload it, or will I need to pay for it a second time?
I originally got apps2sd set up by using the recovery ROM prior to flashing Modaco's custom ROM v1.1.
The easiest thing to do would be to load the new RA 1.5.1 recovery image.
Then boot into it.
Go to Partiton SD
Select FAT EXT3 SWAP
and then set the partition sizes of EXT3 and SWAP to 0
Is there a reason you want to do this???
This runs a very very minimal chances of bricking your phone. The other method on that Wiki page has more potential to get you in trouble.
Did see the market place question.
There is a method laying around somewhere to copy all of your apps back to the phone instead of loosing them. Restoring a Nandroid backup would likly put them all back into the /apps/ directory sd card or not. apps2sd just changes the location of that directory really.
But the market does keep track of your google account and what apps you purchase, you wont have to re purchase (maybe on a totaly new handset).
hope my jiberish has made sense
jashdlfjasdhfjablgjkasgjlkasfhlajshf
At first I was interested in the whole apps2sd process, but have yet to implement it on my rooted, Fresh 1.0 Hero since so far, I haven't really seen a need for it.
But if you were to 'turn on' apps2sd and then decide later that you don't want it, there's a possibility of bricking?? Although I assume you can always reflash the RUU if something like that were to happen? Hopefully?
Think I'll stay away from the whole offloading applications thing for awhile.
mkhopper said:
At first I was interested in the whole apps2sd process, but have yet to implement it on my rooted, Fresh 1.0 Hero since so far, I haven't really seen a need for it.
But if you were to 'turn on' apps2sd and then decide later that you don't want it, there's a possibility of bricking?? Although I assume you can always reflash the RUU if something like that were to happen? Hopefully?
Think I'll stay away from the whole offloading applications thing for awhile.
Click to expand...
Click to collapse
The possibilities of bricking the phone are very slim, but they still exist. If a phone is truly a brick, not even RUU can help. RUU has to be able to detect the phone is there in Windows, so if its beyond that RUU is useless.
Nothing to worry about as long as follow the *usually* very well written step by steps across the interweb.
If it makes you feel any better I have only heard of one or two people to brick the Hero. Most things are recoverable.
Yeah, sorry, I didn't expect it would brick the phone so much as badly mess it up - like if it expects to run apps from the SD card and they aren't there I could see the phone being tough to use as a phone, but it wouldn't really be "bricked" in the sense of not responding to user input at all.
As far as why I want to do this, I haven't really seen a huge need for apps2sd yet, and when I was recently helping an app developer to debug their app it was just one more weird variable that seemed like a possible source of problems. I'm also hoping to start developing apps myself soon, so having a more vanilla phone seems like a good idea. (I also was influenced by the Fresh ROM apps2sd rant, to be honest.)
Anyhow, thanks for your replies. I'll probably repartition the card from RUU and then restore from Nandroid at that point. Will a repartition wipe the card filesystems out, or is the partitioner smart enough to preserve the existing data?
What I did is RUUed back to 1.2, OTA updated to 1.6
Flashed to the 1.5.1 image
(At this point I went to mess with the partitions and there was no ext)
Flashed to Fresh 1.0
Hi Folks.
Just been issued heros at work and wish to update the radio rom...How is this accomplished??
regards
Lohtse
Firstly it needs to have a recovery image installed I recommend Amon-Ra v 1.6.2.
Secondly you need to find the radio rom you wish to flash and put it onto the root of you phones sd card.
Thirdly enter the recovery image you have installed by holding power and home button from the phone being off.
Then select the radio.zip to flash.
Everything I have said here can easily be found how to do via searching this forum or its wiki.
also www.theunlockr.com will help with installing the recovery image.
lohtse said:
Hi Folks.
Just been issued heros at work and wish to update the radio rom...How is this accomplished??
regards
Lohtse
Click to expand...
Click to collapse
First you will need to install the custom recovery console if you haven't done so already.
Then download your updated radio, put it on your SD, load into the recovery, then apply update. DONE!
If that is too brief,... let me know,...
EDIT... Ooops,... too late.
way to complicated...
Too much to do and can screw up..... At least with winmo and symbian was a few clicks...
hmmmmm think will ditch android.....
really? its not complicated at all when you know what your doing. In fact I can say its a damn sight easier (and safer) than modifying blackberry roms and from what I hear also Windows Mobile.
Lennyuk said:
really? its not complicated at all when you know what your doing. In fact I can say its a damn sight easier (and safer) than modifying blackberry roms and from what I hear also Windows Mobile.
Click to expand...
Click to collapse
I came from wimo to android, and as it is said, it's quite hard to catch the thing at the beginning, but after everything seems easier than in wimo !! and more reliable... you have almost no chance to brick your hero after you installed the recovery boot.
radio : boot in recovery then select the good option.
rom : nandroid backup / install whatever rom you want / if you don't like it go for nandroid restore ( all you need is two Sd card.. the good one and the one for the "tests" ).... etc....
But at the beginning i was totally out but with a little time.. reading some posts (here and on the web) ... one day everything was more clear !
Ciao
Fred
lohtse said:
way to complicated...
Too much to do and can screw up..... At least with winmo and symbian was a few clicks...
hmmmmm think will ditch android.....
Click to expand...
Click to collapse
Its not hard at all. You can have the recovery installed and the radio updated in 5 minutes.
For step by step instructions follow the "Installing a recovery image" section in BTDAG's guide linked in my signature.
Then further down the same post, in the second yellow box there are instructions on "Updating your Radio".
Guys, the OP said he was issued the Hero at work, then two hours later said he was going to ditch Android... so what then, he's quitting his job? Troll alert. Don't feed the troll.
As to troll comment(yes offence has been caused)....hmmmmm.... Am going back to the trusty Kaiser... WE DON'T HAVE TO USE THE HERO.... We live in free(ish) world.. And the Phones are issued as an update to our old duty phones... Also I'm not the only one who uses them that feels the same.
Now to updating being easy. Gulp I must be eeer dum!!! Du hu Du HU must be the TROLL in me!
I have tried to install recovery image thing and well just cant get it to work... And now I find I have to root the hero too so things will install to sd card!!!! WTF this should all be standard like winmo and symbian etc...
I have been using smart phones since the Ericsson r380 and so far Android has failed to impress to the degree I am beginning to hate it....
Am far to used to having simply andfull access to everything..
Android is a HUGE learning curve that I suspect I may not have the patience for..
regards The TROLL sorry I mean Lohtse
Now I have finally managed to get recovery image on and updated the radio...Being called a troll did it !!!!!!.....LOL
My final questions are this how do I root so I can install to sd card(just point me in the right direction) And do I have to unlock Phone to any network to have custom roms on..
regards
TROLL
lohtse said:
Now I have finally managed to get recovery image on and updated the radio...Being called a troll did it !!!!!!.....LOL
My final questions are this how do I root so I can install to sd card(just point me in the right direction) And do I have to unlock Phone to any network to have custom roms on..
regards
TROLL
Click to expand...
Click to collapse
Wahey!!!! Good job man.
Ok,... So now you have the recovery image all you need to do is pick a custom ROM. Personally, I highly recommend MCR3.2 (link in signature at botom). It is an Android 1.5 ROM but is stable and fast, what more could you want for a work phone.This ROM is rooted and has apps2SD enabled. Once you have installed the ROM you will need to remember to create an ext2 partition on the SD card (easily done through the recovery). Then you are set to go!!!!
lohtse said:
Now I have finally managed to get recovery image on and updated the radio...Being called a troll did it !!!!!!.....LOL TROLL
Click to expand...
Click to collapse
You're welcome And what ddotpatel said. MCR is fast & clean. By installing a custom recovery you've already done the only tricky bit.
Yep installed 3.2 from modocca. seems nice but how do you know if the apps are installing to sdcard???? I'm not sure they are lol..
lohtse said:
Yep installed 3.2 from modocca. seems nice but how do you know if the apps are installing to sdcard???? I'm not sure they are lol..
Click to expand...
Click to collapse
You need to create an ext2 partition on your SD card through the recovery again. I cant remember the exact wording but something like "create ext2 + fat" or something along those lines.
As far as I know, once that has been done all apps will install to SD.
Someone with more knowhow than me correct me if I am wrong?... CAULI?,... LENNY?
Can someone who knows please answer this question:
Are you 100% sure that flashing the Radio ROM does not affect the phone RF Calibration ?
Thanks!
ddotpatel said:
You need to create an ext2 partition on your SD card through the recovery again. I cant remember the exact wording but something like "create ext2 + fat" or something along those lines.
As far as I know, once that has been done all apps will install to SD.
Click to expand...
Click to collapse
Yup, certainly as far as MCR is concerned. On the first reboot it will move all files from /data/app to /system/sd/app (& similarly for app-private) Nb /sysytem/sd is the mount point for the ext2 partition. All it does is move the files over & then replaces the /data/app (& app-private) directory with a symlink to the new location. That way future installs, updates etc all automatically go to the new location.
You can always check yourself with a terminal emulator & the command ls -l, or using a file manager like Root Explorer, if you're curious. Some people think it's not working because they see available space in internal flash drop as apps are installed, but that's because app data & the dalvik cache remain on internal flash, principally aiui for reasons of access speed. The saving you make just from shifting the apks to sd is more than enough for most people it seems.
cauli said:
Yup, certainly as far as MCR is concerned. On the first reboot it will move all files from /data/app to /system/sd/app (& similarly for app-private) Nb /sysytem/sd is the mount point for the ext2 partition.
All it does is move the files over & then replaces the /data/app (& app-private) directory with a symlink to the new location. That way future installs, updates etc all automatically go to the new location.
You can always check yourself with a terminal emulator & the command ls -l, or using a file manager like Root Explorer.
Some people think it's not working because they see available space in internal flash drop as apps are installed, but that's because app data & the dalvik cache remain on internal flash, principally aiui for reasons of access speed.
Click to expand...
Click to collapse
hmmmm I certainly noticed a drop in available memory on the phone to the degree of only having 54 megs free...
SebHTCHero said:
Are you 100% sure that flashing the Radio ROM does not affect the phone RF Calibration ?
Click to expand...
Click to collapse
what is rf calibration?
What is radio rom used for by phone?
kendong2 said:
what is rf calibration?
Click to expand...
Click to collapse
A set of tables usually stored in NVRAM that takes into account the slight differences in the components used to build your phone. Every single phone is calibrated during manufacturing.
If the calibration is erased, it will look like it works but you can have all sort of problems from poor battery life to random drop from the network or poor sensibility (not to mention the higher than expected radio levels you could be emitting right next to your brain )
I'm posting this in General as I don't have the knowledge to port this or develop a similar version for the Slide and I don't want to clutter up the Development forum.
Team ADX over in the Droid Eris forum came up with this gem; a dual boot Eclair Sense/2.2 AOSP ROM. http://forum.xda-developers.com/showthread.php?t=824072
I don't know if this can be done on our phones, but I thought it possible as you don't need to flash a custom recovery.
man this would awesome... the best of both worlds, run and "stock" ROM so we can still receive updates and still have CM.
i was actually thinking about dual boot just the other day! i dont feel like id be switching back and forth from 2 roms but itd be a great feature for those who do. unfortunately i dont think we have that much developers :/
I was reading the instructions for it and it looks like we'll have to wait for S-OFF before we can try it.
Part of the scripting is telling the phone how to partition the phone, sizes of those partitions, and so on. The slide is, generally speaking, un-brickable and it's the measures used to give us that luxury that also prevent us from doing so much like R/W on the system while in a non-recovery boot and changes we do make while booted are just wiped on reboot *sigh* man I love that ramdisk image.
Once we get S-OFF let's get this project started
KCRic said:
I was reading the instructions for it and it looks like we'll have to wait for S-OFF before we can try it.
Part of the scripting is telling the phone how to partition the phone, sizes of those partitions, and so on. The slide is, generally speaking, un-brickable and it's the measures used to give us that luxury that also prevent us from doing so much like R/W on the system while in a non-recovery boot and changes we do make while booted are just wiped on reboot *sigh* man I love that ramdisk image.
Once we get S-OFF let's get this project started
Click to expand...
Click to collapse
I don't think S-OFF is the issue. The partitioning instructions only refer to sdcard. This command:
Code:
mkpartfs primary fat32 0 3500 (can be adjusted to your needs. This partition will be used by the 2.1 rom and by recovery)
I think is only for the phone ROM storage and the for the recovery to find the boot scripts. According to the instructions, they're only partitioning the sdcard to run the AOSP ROM in it. They install the 2.1 Sense ROM to the phone, get it set up, run the boottosd script to boot into the 2.2 AOSP ROM on the sdcard, then set that up and run the boottophone script to go back to 2.1 Sense. They're running a ROM on the sdcard!
As I said before, I think something like this can work for our phones because it doesn't require flashing a recovery. The problem is we don't have the devs to do it.
heybobitsme said:
I don't think S-OFF is the issue. The partitioning instructions only refer to sdcard. This command:
Code:
mkpartfs primary fat32 0 3500 (can be adjusted to your needs. This partition will be used by the 2.1 rom and by recovery)
I think is only for the phone ROM storage and the for the recovery to find the boot scripts. According to the instructions, they're only partitioning the sdcard to run the AOSP ROM in it. They install the 2.1 Sense ROM to the phone, get it set up, run the boottosd script to boot into the 2.2 AOSP ROM on the sdcard, then set that up and run the boottophone script to go back to 2.1 Sense. They're running a ROM on the sdcard!
As I said before, I think something like this can work for our phones because it doesn't require flashing a recovery. The problem is we don't have the devs to do it.
Click to expand...
Click to collapse
I'll take a look. No promises as I'm an übernoob but I would love to have this.
Sent from my T-Mobile myTouch 3G Slide using XDA App
migueltherocker said:
I'll take a look. No promises as I'm an übernoob but I would love to have this.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
You won't be able to do a simple port. I posted about it more of as a proof of concept. Take the same idea, but obviously using our espresso sense and CM6.
heybobitsme said:
I don't think S-OFF is the issue. The partitioning instructions only refer to sdcard. This command:
Code:
mkpartfs primary fat32 0 3500 (can be adjusted to your needs. This partition will be used by the 2.1 rom and by recovery)
I think is only for the phone ROM storage and the for the recovery to find the boot scripts. According to the instructions, they're only partitioning the sdcard to run the AOSP ROM in it. They install the 2.1 Sense ROM to the phone, get it set up, run the boottosd script to boot into the 2.2 AOSP ROM on the sdcard, then set that up and run the boottophone script to go back to 2.1 Sense. They're running a ROM on the sdcard!
As I said before, I think something like this can work for our phones because it doesn't require flashing a recovery. The problem is we don't have the devs to do it.
Click to expand...
Click to collapse
Ok that makes sense. I thought it was pointing to the partitions on the phone telling it to format to a different size for some reason. Then what's preventing us from doing this? Just a lack of a proper script?
I have not poked around with how they are going about doing everything, but I was the one who got the ball rolling with my dual boot linux script. Conap took the basic setup and made some changes to just install them both on the phone and sdcard. Here is the basic of what it is doing....
The init.rc file found in boot.img has been modified for the froyo rom on the sdcard. The lines where it mounts [email protected] , [email protected], and [email protected] have been changed to the partitions on the sdcard (/dev/block/mcblk0px) The updater-script for froyo has been modified to flash the rom to the partitions on the sdcard. There are some gscripts which are ran from the phone that either modify or replace the boot.img for the rom you want to boot into.
The froyo ROM is running completely off the sdcard and the recovery is left untouched. The script that is required if you are using clockworks is because clockworks sbin and folder locations are setup a little different. I was running into some problems with froyo not recognizing the sdcard after making more than 4 partitions. Several had reported to me that their phones also did not recognize the sdcard, but the Eris phones somehow still did. I am working on something that should run from all android phones and allow you the option of installing whatever ROM you want.
One Last Thing..
Anyone is capable of learning how to do some development work. It just takes some patience and "Google". I had no knowledge of linux or any other scripting languages, except windows batch scripts, until 3 months ago.
There is not much activity on my thread, but once I get a working version finished it will be posted there-----Dual Boot Android
When you get it done and own working, post it in development. I only posted the thread in general because I knew I wasn't going to be the one to develop it. I'm a welder by trade and java and linux are a little beyond me. Although I am trying as I'm using Ubuntu as my main OS and starting reading java tutorials.
Sent from my CM6 Slide
heybobitsme said:
You won't be able to do a simple port. I posted about it more of as a proof of concept. Take the same idea, but obviously using our espresso sense and CM6.
Click to expand...
Click to collapse
If there was ever a reason to get a dev started on a project, this would be it. I would reconsider upgrading from the Slide if we had something this awesome.
unCoRrUpTeD said:
I was running into some problems with froyo not recognizing the sdcard after making more than 4 partitions. Several had reported to me that their phones also did not recognize the sdcard, but the Eris phones somehow still did. [/URL]
Click to expand...
Click to collapse
From what I understand, android can not *see* more than 4 partitions so they had to do something a bit different. Somewhere in the thread that's linked it states what they did to get it to work.
s off is tmobs response to....
KCRic said:
I was reading the instructions for it and it looks like we'll have to wait for S-OFF before we can try it.
Part of the scripting is telling the phone how to partition the phone, sizes of those partitions, and so on. The slide is, generally speaking, un-brickable and it's the measures used to give us that luxury that also prevent us from doing so much like R/W on the system while in a non-recovery boot and changes we do make while booted are just wiped on reboot *sigh* man I love that ramdisk image.
Once we get S-OFF let's get this project started
Click to expand...
Click to collapse
The "companies" wanted s-off due to the large number of brix getting returned for handest exchange and assurion claims, just to figure out somebody pooched sumthin up trying to be a HAXOR, if you haven't done anything like this before. Id suggest peeps get a g1 or some other root & rom-o-matic type for and play with it till you take on your brand new handset trying to install some bleenin edge hack...
You gotta learn to wank off before you can try it with somebody else in the room.
I remember my early days at xda, hacking my mda, xcaliber, and esato hacking SonyEricsson fones before they jumped the shark. People who had the ability to read and follow directions (emphasis on the read part) would study till they were sure they would still have a working fone at the end. Hung out and did great stuff with there handsets. And the noobs were wary enough to investigate before they just started mucking about.
So the handset manu. Had to do sumthin and now we have s-off.
the moral of my high and mighty rant an rave, if you don't know how to do sumthing or if you understand what to do but not the why, then keep reading, read more do less
KCRic said:
From what I understand, android can not *see* more than 4 partitions so they had to do something a bit different. Somewhere in the thread that's linked it states what they did to get it to work.
Click to expand...
Click to collapse
In the newest builds they have 2.1 system on the phones system partition and froyo system on the phones data partition. The data is moved to the SD. 2.1 and previous Rome had no problem with extra partitions on the sdcard.froyo changed the way it mounts the sdcard and could only see 4.
I am actually releasing a dual boot method very shortly that should work on any android phone with very little setup required on your part. I am in the process of finalizing it. Anyone interested in testing please let me know as I want to test on as many devices ad possible
Sent from my HERO200 using XDA App
I understand there's a tips and tricks thread that explains things in more detail but how does somebody go from just getting the phone to installing, or even understanding, things like obsidian, onyx, morphing and learning what the basic functions of such programs are.
The question I currently have is concerning flashing custom roms. In the tips & tricks thread, it talks of froyo builds (ex: bionix & frankin-twiz). What is it exactly? From what I understand, it sounds like a mini os that you install onto your device which helps in applying different functions to it, which makes custom roms possible.
I'm currently trying to get http://forum.xda-developers.com/showthread.php?t=845530 to work on my vibrant. Can anybody help a newbie out?
VibrantUser1 said:
I understand there's a tips and tricks thread that explains things in more detail but how does somebody go from just getting the phone to installing, or even understanding, things like obsidian, onyx, morphing and learning what the basic functions of such programs are.
The question I currently have is concerning flashing custom roms. In the tips & tricks thread, it talks of froyo builds (ex: bionix & frankin-twiz). What is it exactly? From what I understand, it sounds like a mini os that you install onto your device which helps in applying different functions to it, which makes custom roms possible.
I'm currently trying to get http://forum.xda-developers.com/showthread.php?t=845530 to work on my vibrant. Can anybody help a newbie out?
Click to expand...
Click to collapse
the link you posted is just to a theme.
to get the theme to work you'll need to be running obsidian first.
so lets see, the easiest way to explain the different versions 2.2, 2.1 1.6, 1.5 and so forth is this...
its pretty much like going from windows 95 to 98 to 2000 to xp to vista and so forth.
our vibrants come with android 2.1, 2.2 is the next version of the os to come out (basicaly like moving from vista to windows 7)
the different roms like obsidian and Macnut and such are just names that the developers gave their roms.
what happens is a developer starts out with a version of android (in the case of Macnut and Obsidian this is 2.2)
and then they add their own modified tweaks and such to it.
and so in the end they get Obsidian which is a modified 2.2
or Macnut which is also a modified 2.2
they differ a bit though as Obsidian is based almost totaly on a leaked version of 2.2 for the US vibrant, where Macnut is based alot on the 19000 version of 2.2 for the european phones.
so when choosing a rom just choose the base you want first: 2.1 or 2.2
then look through the tweaks on a few roms and read some of the thread for that rom untill you get a feel for what makes it unique
you can also just experiment by flashing a rom for a day or so and then switching to a new one untill you find one you like.
Morphing is a way to apply a theme to a rom, this does not generaly change functionality at all, it only changes apearance.
alot of themes are either morphs (you install them using metamorph, which is an app from the market)
or they also come in zip format (which are installed by flashing from recovery)
for the theme you posted you will need to flash obsidian, and then flash the zip for the theme afterwards.
have you rooted your device yet?
thats the place to start, if you need help just pm me or repost here and I'll do what I can.
also, there is a "newbie's guide":
http://forum.xda-developers.com/showthread.php?t=732458
nearblack said:
also, there is a "newbie's guide":
http://forum.xda-developers.com/showthread.php?t=732458
Click to expand...
Click to collapse
lol true true
Before you even want to start with anything, you have to learn what 'rooting' your phone means.
Without root, you won't be able to do any of the above. You might be able to download the programs necessary, but you won't be able to use them.
For ex. Titanium Backup, ROM Manager, etc.
We use ROM Manager to install different ROMs on our phones.
Much to read, my young grasshopper.
OP, I made the Tips/Tricks sticky... would you PM be exactly what you think it lacks? I want to make sure it is applicable to everyone... I thought it was straight-forward, perhaps not.
my phone is rooted. So how do I go about flashing obsidian?
I thought roms were the same as themes? What's the difference?
And just to clarify I understand the tips and tricks thread is sort of the newbies guide but even then theres a lot of terminology that a new user wouldn't understand. I just wanted some basic information that would allow me to transition into the tips and tricks thread more easily.
I appreciate the responses so far
Have you download Rom Manager from the Market? If not, do so.
Then follow the instructions (in the sticky) to flash the recovery (it's the top of the list when you open Rom Manager).
Assuming you did that, you can reboot into recovery, make a backup of your system.. something you can always come back to (a timestamp of your system at that moment).
Download the ROM you want, put it on your internal memory (sdcard/....) NOT in a folder.
Go to Clockwork recovery, choose to insall a zip from sd card... select the name of the ROM and then click Yes to install it.
It will run it's course, then you can just reboot when done.
The first bootup will take a long time (10 minutes probably)... let it boot.... leave your phone alone for like 10 or so minutes after bootup (suggested by Team Whiskey, I never really do this).
It's that easy.
Think of a ROM as an OS... the developers take Froyo (2.2) or Eclair (2.1) and make a lot of tweaks, remove things, add things... basically anything to enhance the user experience.
THEMES are something you flash over a custom ROM... it can change the icons, graphics, notification bar, etc... they are cosmetic. You see in my signature I have Axura 2.0.3 (amazing rom and there is a newer version out) and then I have BlackFroyo (which is the theme) on top of the ROM to change the look of things. Axura has a steel looking notification bar, I much prefer black (hence the theme I chose).
The ONE thing that can be confusing... if you make a backup right now (you have stock eclair), if you flash a froyo rom... you would need to flash either the stock eclair kernel (the download link is also in the sticky) to restore your nandoid backup.... OR, you could just flash another ROM that has a kernel (most do) and you would be good to go too.
And addition to this is to make sure your phone is NOT hardware locked.
To test it:
1) Take out battery from the phone and put it back in again
2) The USB cable plugged into the computer (not in the phone yet)
3) Push and hold down both of the Volume buttons at the same time
4) Plug in USB cable and it should take you into the Download mode.
If it does you are good to go. Just read some about Odin and Stock Android
If it isn't you need to make sure to flash JI6 to your phone (also Stock) onto your phone using Stock Manager. That should fix your hardware locked. Go over the above steps to make sure that is the case.
At this point, I have rooted my device and downloaded rom manager.I believe I have backed up everything after following the directions and I do have the blackfroyo.zip on my sd card and for some reason it won't "go" (although I'm sure there's a step I am missing here, something with obsidian) so that wasn't much of a surprise.
Edit: I noticed I tried to use a theme on there and not the obsidian "OS" (idiot) when I tried the backup thing with rom manager. Where can I download the most recent version of obsidian and/or is axura an acceptable alternative?
VibrantUser1 said:
Edit: I noticed I tried to use a theme on there and not the obsidian "OS" (idiot) when I tried the backup thing with rom manager. Where can I download the most recent version of obsidian and/or is axura an acceptable alternative?
Click to expand...
Click to collapse
Been working on updating the wiki. Please check out http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs for the different ROMs currently available.
^^ both are solid. I prefer Auxura *no touchwiz*.... download it from the development section. Place in on the internal (sdcard/ ) and flash it, reboot... I would let the phone chill for awhile then reboot again.... THEN if you want, start messing with the theme. You can see from my signature you and I are similar.
to the OP, I started a noob friendly guide in the Q&A section. Please let me know exactly what you want in there.
Here is a video guide, its kinda old but the principles are the same.
http://theunlockr.com/2010/08/02/how-to-load-a-custom-rom-on-the-samsung-captivate-vibrant/
I have been browsing around and reading on XDA since I got my G1 on release day. I have since upgraded to the MYT3G and now to the Vibrant. I have always used XDA as a source of information for rooting, etc. I don't post very often, but, I would like to throw props out to all the individuals in the thread, this is one of the few threads I have read on XDA that no one got flamed for being a "noob" and asking basic info, the information given was clear, accurate and very helpful. No one pointed to using the search function, everyone just gave good answers. AWESOME
I hope to see more threads like this in the future. Bravo and well done to all.
So I tried installing obsidian 5 and this is what happened. I first put the zip file on my sd card, I did all the necessary prerequisites (I think) using rom manager, flash recovery > vibrant yada yada yada and then pressed install rom from sd card and chose the obsidian zip file. Then the phone starts backing itself up and it finally reaches a point where it says (E: Can't open/sdcard/sd/obsidian_v5_beta.zip (no such file or directory) Installation aborted.
I then try to navigate to the file from the menu but whenever I click the sd file, it just exits, I think it says that no zip file is found or something but when I boot it up normally afterwards, the file is still there.
But the file is within the sd file . . . what am I doing wrong? I tried to fix permissions thinking it was that but no luck.
You probably need to move to the rom to the internal sd card. I thought you're able to add it to the external with the recent update but perhaps not
Sent from my GT-I9000 using XDA App
bellrb19 said:
You probably need to move to the rom to the internal sd card. I thought you're able to add it to the external with the recent update but perhaps not
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
the rom IS on the sd card, unless you mean the memory on the actual phone itself
ROMs go on the root of the internal memory (no folder)... drop it in sdcard/
Also, this was mentioned in Post 8, and in team whiskeys install guide. Please pay attention to details.
oh okay, this whole time I've been thinkin the sd card folder was the root folder. Well I have finally put obsidian with success and now I'm having a difficult time implementing http://forum.xda-developers.com/showthread.php?t=845530. I have downloaded the zip file but I don't understand what "flash it through clockwork recovery" means. It kinda sounds like I should use something in rom manager but I'm not sure, I have tried to reboot into recovery through rom manager with no luck.
I've also tried using metamorph but when i choose the blackfroyo.zip file, it says that the file is invalid and that the theme control file could be missing. Am I doing something wrong here as well?
Thanks for all your help so far, I really appreciate you taking time out of your busy life to help an individual with (what may be to you) simple problems
VibrantUser1 said:
oh okay, this whole time I've been thinkin the sd card folder was the root folder. Well I have finally put obsidian with success and now I'm having a difficult time implementing http://forum.xda-developers.com/showthread.php?t=845530. I have downloaded the zip file but I don't understand what "flash it through clockwork recovery" means. It kinda sounds like I should use something in rom manager but I'm not sure, I have tried to reboot into recovery through rom manager with no luck.
I've also tried using metamorph but when i choose the blackfroyo.zip file, it says that the file is invalid and that the theme control file could be missing. Am I doing something wrong here as well?
Thanks for all your help so far, I really appreciate you taking time out of your busy life to help an individual with (what may be to you) simple problems
Click to expand...
Click to collapse
From where you are now. Make sure the zip file is in the internal sd card, Open rom manager go to install rom from sd card then choose the that file then click ok and CW will do its thing. Also this is only for Obsidian v4.2 and Auxura 2.05. Good luck! Also you should make a nandroid back up first just in case.