Related
The Motorola Flipout is fairly easy to root, at least now. Universal Androot (get it here) works.
I am thinking about moving apps to the sd card. However, since I haven't reflashed the phone, and I don't have a ROM for it, I'd like to do it without reflashing. Is that possible?
If I partition an SD card correctly (ext3), copy all of /data onto that partition, and then mount that partition over /data, will that work? Or do I have to mount the card before the phone boots?
Or is it better to just copy /data/data, and mount the partition over /data/data?
It seems to me that mounting over a directory, as opposed to creating a link is least invasive, because on reboot the phone is as it was before. Is this right?
If I have to mount the sdcard before the phone boots, can I just edit one of the init scripts, or is that more complicated? I read about editing init.rc and repacking boot.img
Oh, HOWTO unpack edit and repack boot images seems to give good instructions. On the Flipout, boot is mtd4, and recovery is mtd5.
If I only modify boot, I can't brick my phone too badly? Since I haven't changed recovery, I should be able to recover (?). Can I create an update.zip that flashes the old boot.img and undoes my changes in case something goes wrong?
I just got the flipout from rogers.. Is there anyplace that has a development forum for it? And does it have the efuse ? If it does, is it possible to do what was done with the droid X to it?
How did go so far ghostwheel? I'm eager to hear what else you have figured out.
You use App2Card.apk at below for app2sd without flash:
http://www.tinhte.vn/f280/app2card-2-4-4-20-9-cai-dat-ung-dung-len-nho-phan-vung-456586/
Requires: just a rooted phone
Steps:
- install app
- click Menu / Partition button then use slide bars to create ext2 for your sd card if it hasn't been splited yet
- click Install App2card button
- phone will be rebooted and you just taste app on sd after then
Note: above page has further instruction but it is vietnamese, you must use google translate to get it. This app runs perfectly on my Milestone.
Sent from my Milestone using XDA App
ghostwheel said:
The Motorola Flipout is fairly easy to root, at least now. Universal Androot (get it here) works.
I am thinking about moving apps to the sd card. However, since I haven't reflashed the phone, and I don't have a ROM for it, I'd like to do it without reflashing. Is that possible?
If I partition an SD card correctly (ext3), copy all of /data onto that partition, and then mount that partition over /data, will that work? Or do I have to mount the card before the phone boots?
Or is it better to just copy /data/data, and mount the partition over /data/data?
It seems to me that mounting over a directory, as opposed to creating a link is least invasive, because on reboot the phone is as it was before. Is this right?
If I have to mount the sdcard before the phone boots, can I just edit one of the init scripts, or is that more complicated? I read about editing init.rc and repacking boot.img
Oh, HOWTO unpack edit and repack boot images seems to give good instructions. On the Flipout, boot is mtd4, and recovery is mtd5.
If I only modify boot, I can't brick my phone too badly? Since I haven't changed recovery, I should be able to recover (?). Can I create an update.zip that flashes the old boot.img and undoes my changes in case something goes wrong?
Click to expand...
Click to collapse
Hi,
I'd really like to help with that (I'm a confirm dev. for Cliq and CliqXT phones).
Hopefully we can do great things like we did for Cliq and CLiqXT (upgrade to 2.1!). (check my work at http://bit.ly/adlxmod).
First thing would be to generate a system dump (a dump of all the files in the /system partition). Hopefully we then could generate a custom recovery to flash on the phone, and then custom roms, either base on the dump you provide or other roms from other files. Contact me on twitter @adumont (say it's for Flipout) and I'll guide you to generate the dump!
Looking forward to do great things for that litle phone!
I'm in touch with adlxdum to give him my dump but I think we should start a separated thread like "Custom rom, modding (work in progress)" so that we can follow adlxdum work.
And...thx in advance ;-)
flusshd said:
You use App2Card.apk at below for app2sd without flash:
http://www.tinhte.vn/f280/app2card-2-4-4-20-9-cai-dat-ung-dung-len-nho-phan-vung-456586/
Requires: just a rooted phone
Steps:
- install app
- click Menu / Partition button then use slide bars to create ext2 for your sd card if it hasn't been splited yet
- click Install App2card button
- phone will be rebooted and you just taste app on sd after then
Note: above page has further instruction but it is vietnamese, you must use google translate to get it. This app runs perfectly on my Milestone.
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
Worked!
I couldn't repartition the SD card with the program, so I had to partition it myself. But once that was done, thing seem to work well. A bit slower...
I'm not totally sure how to use the app. Internal seems to still be full, but ext2 on the SD is quite empty. I can't seem to be able to tell if an app is installed to internal or external.
I have to try and install some more apps to see if I run out of memory.
Thanks!!
I'm guessing the flipout and charm are almost identical phones?
My wife has a charm and i'm one of those "i'm not a developer, but I'd like to help" guys.
MrShides said:
I'm guessing the flipout and charm are almost identical phones?
My wife has a charm and i'm one of those "i'm not a developer, but I'd like to help" guys.
Click to expand...
Click to collapse
Yes, I think they are very similar.
One thing that I'm interested in is the accelerometer. On the Flipout, most apps that use it are twisted - for example wikitude, and many games (labyrinth lite works!) I wonder if things work on the charm...
the charm has the same issue.
MrShides said:
the charm has the same issue.
Click to expand...
Click to collapse
thanks! Too bad....
Hi ghostwheel
I've tried installing app2card, but I'm having some problems. I got the new version 2.7.2.
As you said, the partition doesnt work. For me it says sd card is full but its empty...
How did you manually partition it?
I've found some tutorials but it was for other phones and they required a custom rom...
I partitioned the card using a linux computer, with the program fdisk.
I allocated 2GB to a partition of type ext2. But, I think there are many alternatives for partitioning a disk, see this page:
http://androidcommunity.com/forums/f9/how-to-create-ext2-partition-14232/
Wow great link! Many different options! Will try this as soon as I get a micro sd card adapter. Thanks!
You mentioned in your old post that you were having problems using app2card, That you weren't sure if it was working. Have you been able to use it since? Is it working well? and if not have you found an alternative?
I just started using this phone and I'm almost running out of memory... this is quite annoying!
longlife_01 said:
You mentioned in your old post that you were having problems using app2card, That you weren't sure if it was working. Have you been able to use it since? Is it working well? and if not have you found an alternative?
!
Click to expand...
Click to collapse
Yes, I was having problems. Mainly when restarting the phone, sometimes oodles of apps don't work, including launcher pro, and app2card. You have to remember that when the phone reboots and seems to have FC problems, don't chose any home screen as the default, in case it crashes, and keep a spare app2card to reinstall on the sdcard. I think "severe" problems I had only twice, or so.
So, I have almost no problems. Most of the time it works really well. So well, in fact, that I'm a bit afraid to upgrade it, in case something breaks. And, I totally forgot what it is like to have to delete apps to install another one.
I have more of the opposite problem - finding an app among all those installed takes a realllly long time if you forgot its name. Apps organizer helps.
hello, i am new and i have flipout to test in poland orange network, i just root him using 1st post in this forum, great job! thanks
OK, I am having some problems with the current version of app2card. As I said, sometimes when I turn the device off and back on, app2card fails, and many apps give a FC which starting. Then one needs to fix the apps from app2card. It seems that once that is done, some apps lose some of their data. So, for example, droidwall (excellent program!!), lost all firewall data. I'll have to check if newer versions of app2card don't have this problem. It doesn't happen very often.
Instructions to root Flipout
Hi - I'd consider myself a newbie regarding rooting. I just got the AT&T Flipout - I really like the form factor. I just tried running the Universal Androot from my phone but got the security warning message about only being able to install from trusted sources.
Can someone point me in the right direction please?
Many thanks!
it says that with a lot of apps installed like that, including gmote that I downloaded from the developers site. Just look at what you're downloading like you would on any machine
go to settings > Application and tick on unknown sources to be able to install it.
In a conversation with enatefox recently he asked if it was possible to dualboot an android phone, I thought it was and set out to make that happen. This is that work.
This is a VERY EARLY BETA! It does function, but its rough. Don't expect this to be smooth or easy yet.
This image is based on Amon-RA-v1.6.2
What you need to do:
This hack will boot a rom from SDCard. It expects to see system.img and data.img on the sdcard as well as init.rc.
System.img needs to be a disk image of a filesystem that the kernel can read(I've been using ext3) around 170MB(Thats the Eris's NAND size for system)
data.img needs to be a disk image of a filesystem that the kernel can read(I've been using ext3) as big as you'd like your data partition to be(This holds your apps etc, so a couple hundred megs is good)
init.rc needs to be the init.rc of your rom with two changes
You need to remove the lines where it mounts /system and /data.
Once you have those three files on your sdcard, and have flashed this recovery you're ready to try your first boot.
Reboot into recovery, you'll see the normal usual recovery menu(I'll add an item eventually)
connect to the recovery console with adb
run 'adb shell /bootfromsd'
It will APPEAR to have done nothing for a bit, this is normal. Its booting your rom now. Once it gets to the place in the rom where it would display the splash screen, you'll get a splash as usual. You can watch it with logcat if you like.
I've personally booted the following roms from SD.
KaosFroyo
KaosLegendary
CELBFroyo
MR4
PlainJane
Good luck!
V1: http://www.multiupload.com/UJNJLQWL17
If you like my work, think about donating to my coffee fund.
So do the roms you load from SD run just as smooth as a normal one?
tjthebest said:
So do the roms you load from SD run just as smooth as a normal one?
Click to expand...
Click to collapse
depends on the speed of your SD. Theres a tiny bit of lag on the class 2 I tried it on, but it would likely be fine on a faster card.
Sounds freaking awesome! Can't wait to try
This is freaking awesome kaos sir you did it again +1 tyvm
Ill be trying this tonight!
Thx
Btw i love u kaos
Sent from my ERIS using XDA App
this as well as the herculean update schedule of KaosFroyo convinces me that Punk.Kaos should have his own kids show.
"But Punk.Kaos! that's impossible!"
Punk.Kaos appears in a superhero outfit with a silvered cape, poses and says,
"No little Jenny. Impossible is only what we have yet to try."
This reminds me of trying XDAndroid on my Diamond.
MrObvious said:
This reminds me of trying XDAndroid on my Diamond.
Click to expand...
Click to collapse
Heh, kinda the same idea
Class 4 16GB =)
[ Sent from my HTC Droid Eris | KaosFroyo v34 ]
I didn't understand all that stuff...but I like it!
Kaos rules.
Say Hi to enatefox for me, he used to handle the kaiser back in the vogue android days....
Damn this dudes smart as hell
quick question kaos, so when i want to boot to a different rom i have to adb it on recovery every time??
rrem said:
quick question kaos, so when i want to boot to a different rom i have to adb it on recovery every time??
Click to expand...
Click to collapse
Right now. Im working on making it a bit more user friendly.
I bow to you sir, you make the Eris world go 'round! (Amongst other worlds I'm sure
Thank You.
punk.kaos said:
Right now. Im working on making it a bit more user friendly.
Click to expand...
Click to collapse
Oh, alright Thanks for all your hard work even at this state this is so awesome
This is some incredible work. I wish I could donate. .I'm kind of speechless....just some ill work being done by you kaos.
Sent from my FroyoEris using XDA App
not getting time to try to night kaos, maybe tomorrow. or i may wait till a newer release.
if you need a tester for a newer build. let me know ill be glad to lend a phone out to ya.
just pm me if you want that i test for you.
thanks again kaos.
Very excited to try this out... thanks Kaos!!!
Question though, do we need to generate the .img files ourselves, or do we get the .img files from a nand back up of the ROM we want to be able to boot from?
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.
First off I'd like to apologize if this is in the wrong place or if it is perceived as advertising, I simply want to contribute to the dev community and this site, and in particular the Nexus 9 forum that has been the centre of my learning as I took up the hobby of AOSP.
I have been back and forth with AOSP, I've contributed a little bit here and there on the Android development forums but would like to properly document how to build AOSP and more importantly (because it is even less well documented) how to add features, change existing features and generally customize the operating system to your liking. I am by no means an expert but I feel I have enough knowledge that I can share it with others who may be in the position I was a number of months ago. I always found it very difficult to find a centralized location for the information I needed.
To this end I have started a site to do just that. I am using a Nexus 9 for my AOSP development but most (if not all) of the tutorials and information should be applicable to basically any AOSP/Nexus device. I have started things off by creating a tutorial on how to build AOSP from 'scratch' so to speak and a tutorial on how to add items to the power menu such as 'reboot', 'airplane mode' etc.
If anybody would like certain topics covered or just have any feedback or comments please reply here or leave them on the articles themselves. I'll do my best to accommodate / respond.
The link is: http://littlelostandroid.wordpress.com
From tomorrow the following (nicer) link should also work: www.alittlelostandroid.com
I should also add that the blog will be ongoing about all things android device but this initial series will be about also and implementing features.
wow this is a real good guide/blog u put together please do continue
Dreamlogix said:
wow this is a real good guide/blog u put together please do continue
Click to expand...
Click to collapse
Thanks! The next post should be up in a day or two, its been a busy week.
New post up about flashing the build to a device!
www.alittlelostandroid.com
This is a great website. Lol i'm gonna have to learn to use ubuntu(was gonna do it anyway on my old computer but motherboard died and i got lazy). Can you make this in chronological order? or better add each section to a sitemap? Just a suggestion:cyclops:
whowatchlist said:
This is a great website. Lol i'm gonna have to learn to use ubuntu(was gonna do it anyway on my old computer but motherboard died and i got lazy). Can you make this in chronological order? or better add each section to a sitemap? Just a suggestion:cyclops:
Click to expand...
Click to collapse
So I changed the theme so that you can see the most recent posts on the side and work from that. I'm still getting to grips with WordPress to be honest but hopefully that's better now.
Another post about setting up and storing your code on GIT repos:
https://littlelostandroid.wordpress...-open-source-project-part-4-git-repositories/
Thanks for this
Do you have any insight to share on your site about building the LTE variants at all?
THX for your work !
There are plans to continue this great guide?
scoobydu said:
Thanks for this
Do you have any insight to share on your site about building the LTE variants at all?
Click to expand...
Click to collapse
Sadly I won't be able to do any work around the LTE version as I don't have the hardware to test it on. I don't want to release advice I haven't tested and potentially end up inadvertently damaging someones tablet for example
Topse said:
THX for your work !
There are plans to continue this great guide?
Click to expand...
Click to collapse
Sorry for the late reply, I don't get any emails when someone posts on this thread, I need to subscribe to it. I do plan on doing more, in fact I think I may have some written already, just a matter of getting time to do it. I'll get to work on the next section of the tutorials and post here when it's up. Is there anything in particular you would like covered?
seanashmore said:
Sadly I won't be able to do any work around the LTE version as I don't have the hardware to test it on. I don't want to release advice I haven't tested and potentially end up inadvertently damaging someones tablet for example
Sorry for the late reply, I don't get any emails when someone posts on this thread, I need to subscribe to it. I do plan on doing more, in fact I think I may have some written already, just a matter of getting time to do it. I'll get to work on the next section of the tutorials and post here when it's up. Is there anything in particular you would like covered?
Click to expand...
Click to collapse
I m actually try to make my own little aosp rom.
I have some probs with gapps flashing.
Wrong api level error.
I tried different commits.
With pure nexus gapps it works .I need to flash it twice.
I do "make otapackage", this is different to your guide.
When I flash a custom kernel I don't have this gapps problems.?
Next thing I will integrate is that reboot option.
But with reboot recovery.
Once after flashing I was surprised with stock recovery..
How can I disable that?
At the moment I build only for my bullhead.
But if that recovery and gapps problem is solved.
I will try for my flounder and shamu too.
Actually I use n7 r 15 as source. But will will switch to 7.1*
When it is evaluable.
Topse said:
I m actually try to make my own little aosp rom.
I have some probs with gapps flashing.
Wrong api level error.
I tried different commits.
With pure nexus gapps it works .I need to flash it twice.
I do "make otapackage", this is different to your guide.
When I flash a custom kernel I don't have this gapps problems.?
Next thing I will integrate is that reboot option.
But with reboot recovery.
Once after flashing I was surprised with stock recovery..
How can I disable that?
At the moment I build only for my bullhead.
But if that recovery and gapps problem is solved.
I will try for my flounder and shamu too.
Actually I use n7 r 15 as source. But will will switch to 7.1*
When it is evaluable.
Click to expand...
Click to collapse
I'm not 100% sure about the GAPPS issue, maybe try http://opengapps.org/, it lets you choose your android version, architecture etc.
In terms of the recovery; You'll see in my tutorials that I am using the stock Google factory images as a base. In that image is a recovery.img file; You should be able to replace this file with TWRP or any other custom recovery and flash it as part of your ROM.
Hope this helps.
seanashmore said:
I'm not 100% sure about the GAPPS issue, maybe try http://opengapps.org/, it lets you choose your android version, architecture etc.
In terms of the recovery; You'll see in my tutorials that I am using the stock Google factory images as a base. In that image is a recovery.img file; You should be able to replace this file with TWRP or any other custom recovery and flash it as part of your ROM.
Hope this helps.
Click to expand...
Click to collapse
I tried opengapps. But i run in an error. Opengapps say my ROM has the wrong api level.
I tried this commit (and other like that)
https://github.com/Cardinal-AOSP/frameworks_base/commit/6c8322f3ad221ea2092e82b99ece537b85ec996f
And with pure nexus dynamic gapps . it works when I flash the gapps two times. First I get the error and the second try works.
Change recovery to twrp sounds good. But with more devices its a dangers thing. Cause ever device needs special twrp.
I think there is a way to disable this flashing recovery.
But till now I didn't find it.
Topse said:
I tried opengapps. But i run in an error. Opengapps say my ROM has the wrong api level.
I tried this commit (and other like that)
https://github.com/Cardinal-AOSP/frameworks_base/commit/6c8322f3ad221ea2092e82b99ece537b85ec996f
And with pure nexus dynamic gapps . it works when I flash the gapps two times. First I get the error and the second try works.
Change recovery to twrp sounds good. But with more devices its a dangers thing. Cause ever device needs special twrp.
I think there is a way to disable this flashing recovery.
But till now I didn't find it.
Click to expand...
Click to collapse
If it's just the case of not flashing the recovery img then just remove that line/command from the script. However you will have to assume that the device already has a recovery img (which to be honest is a fairly safe assumption).
[/STRIKE]
seanashmore said:
If it's just the case of not flashing the recovery img then just remove that line/command from the script. However you will have to assume that the device already has a recovery img (which to be honest is a fairly safe assumption).
Click to expand...
Click to collapse
I try this for recovery https://github.com/peteralfonso/platform_build/commit/9b3a020058b84fb1f9cfba600f4a958572a805c3
edit: i think this is to old...
seanashmore said:
I'm not 100% sure about the GAPPS issue, maybe try http://opengapps.org/, it lets you choose your android version, architecture etc.
In terms of the recovery; You'll see in my tutorials that I am using the stock Google factory images as a base. In that image is a recovery.img file; You should be able to replace this file with TWRP or any other custom recovery and flash it as part of your ROM.
Hope this helps.
Click to expand...
Click to collapse
I use this way to build:
cd ~/aosp/kernel/lge/bullhead
make clean
export ARCH=arm64
export CROSS_COMPILE=~/aosp/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-
export USE_CCACHE=1
make bullhead_defconfig
make -j6
cd ~/aosp
mkdir ~/aosp/device/lge/bullhead-kernel
rm ~/aosp/device/lge/bullhead-kernel/Image.gz-dtb
cp ~/aosp/kernel/lge/bullhead/arch/arm64/boot/Image.gz-dtb ~/aosp/device/lge/bullhead-kernel
source build/envsetup.sh
make clobber
lunch aosp_bullhead-userdebug
export USE_CCACHE=1
make -j6 otapackage
Topse said:
I use this way to build:
cd ~/aosp/kernel/lge/bullhead
make clean
export ARCH=arm64
export CROSS_COMPILE=~/aosp/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-
export USE_CCACHE=1
make bullhead_defconfig
make -j6
cd ~/aosp
mkdir ~/aosp/device/lge/bullhead-kernel
rm ~/aosp/device/lge/bullhead-kernel/Image.gz-dtb
cp ~/aosp/kernel/lge/bullhead/arch/arm64/boot/Image.gz-dtb ~/aosp/device/lge/bullhead-kernel
source build/envsetup.sh
make clobber
lunch aosp_bullhead-userdebug
export USE_CCACHE=1
make -j6 otapackage
Click to expand...
Click to collapse
Ah ok, see the way I build gives me separate .img files, and I write a script similar to the flash-all script you get with the factory images. This allows me to pretty easily change what i want to do and what i want to flash or not.
seanashmore said:
Ah ok, see the way I build gives me separate .img files, and I write a script similar to the flash-all script you get with the factory images. This allows me to pretty easily change what i want to do and what i want to flash or not.
Click to expand...
Click to collapse
Year , but zip is easier to use/share.
Topse said:
Year , but zip is easier to use/share.
Click to expand...
Click to collapse
Definitely, though you can always put your script and .img files inside a zip just like the factory images. so users would download your zip, unzip it and run your script. Its all down to personal taste i guess, there are many ways to skin a cat.
seanashmore said:
Definitely, though you can always put your script and .img files inside a zip just like the factory images. so users would download your zip, unzip it and run your script. Its all down to personal taste i guess, there are many ways to skin a cat.
Click to expand...
Click to collapse
:good:
I like it to try different ways.Good for learning and deeper understanding.
For my personal use is this way no problem.
But for sharing with other people is a flashable zip file the most used way.