Related
Is it possible to switch from CyanogenMOD 4.0.4 to a JACxHeroROM without a computer because my laptop isnt working and I can't download the ROM's.
G1BRICKED said:
Is it possible to switch from CyanogenMOD 4.0.4 to a JACxHeroROM without a computer because my laptop isnt working and I can't download the ROM's.
Click to expand...
Click to collapse
Download Linda File manager (which allows you to download any file) and download which ever ROM you want. (For hero roms make sure you have the lastest Radio & SPL) Then copy and paste that rom to the root of your SD card and then boot into recovery and flash away!
nolimit78 said:
Download Linda File manager (which allows you to download any file) and download which ever ROM you want. (For hero roms make sure you have the lastest Radio & SPL) Then copy and paste that rom to the root of your SD card and then boot into recovery and flash away!
Click to expand...
Click to collapse
I got Linda File Manager and I'm about to download the ROM. How do I get it on to the SDCard? And I have another file named Update, do I delete that one?
G1BRICKED said:
I got Linda File Manager and I'm about to download the ROM. How do I get it on to the SDCard? And I have another file named Update, do I delete that one?
Click to expand...
Click to collapse
When you download the rom it automatically goes to /sdcard/download
Yeah if you're not using Cyan1.4 recovery. Cyan1.4 can update from any zip.
nolimit78 said:
When you download the rom it automatically goes to /sdcard/download
Yeah if you're not using Cyan1.4 recovery. Cyan1.4 can update from any zip.
Click to expand...
Click to collapse
Oh well I'm on Cyanogen Recovery Image 1.3.1 so what do I name it to? And also, what's the difference between JACxHero and JACHeroSki and JACHeroSkiLite and everything? Its confusing! And I'm thinking about getting the MiniHeroROM, do I just download the file to the SDCard and Wipe and Flash and that's all or do I have to type stuff into the Console?
Might want to make sure you have your sdcard partitioned for Hero.
http://forum.xda-developers.com/showthread.php?t=533731
I havent used any Hero builds, and I doubt I will. A bird told me that Flash 10 is coming next month to android.
All of the commands should be in the above link.
I would go the CM 1.4 Recovery, so everything in the future is easier to update with the "Any Zip" feature. Just helps to make sure your updating the right file. great for themes etc... no more hassles with renaming stuff.
Astro you can select a file>edit>move then use the up arrow to go back to the root of your sdcard, then menu>edit>paste ... something like that.
Hope this helps.
http://forum.xda-developers.com/showthread.php?t=533731
This link will help answer all of your questions.
i flash this way about 90% make sure u do back up before u flash. case u get get stuck in loop pretty easy flashing to hero. and if don't have radio and spl it maks things harder but u can partition easily from the phone search and u will find it.
nolimit78 said:
http://forum.xda-developers.com/showthread.php?t=533731
This link will help answer all of your questions.
Click to expand...
Click to collapse
Ha! Beat you to the punch lol jk
If you want you can check out the MicroHero build. One of the builds doesnt require the SPL update, just a partitioned sdcard.
http://forum.xda-developers.com/showthread.php?t=561179
From what I read they are pretty fast roms. Theres also the Tiny builds, idk the requirements for those yet.
I'm no longer keeping up with NAND on the vogue. So if anyone would like to keep me informed and email me or post me on any changes with NAND, ill be happy to add the news on the first post. The lock up issue with NAND has been fixed!
This is simply for any noobs or others who are having issues with Android and NAND.
IMPORTANT!!!
FOR VOGUE USERS ONLY
I am not responsible for any bricked or messed up devices. By continuing you are agreeing to my simple rule.
MY SIMPLE RULE: I owe you nothing.
I will help you through the way though if you bricked or need any sort of help.
How-to Video up NOW!!!
http://www.youtube.com/watch?v=3gTkJkOc7m4
First off, What is NAND?
To keep it simple...its your phones internal memory. Up untill recently we (Vogue Users) had to run Android off our SD cards using HARET. But thats another story.
What are the benefits of running from NAND? (based on what I have seen)
-Runs faster
-Longer Battery life
-faster boot up
-can be faster to put together.
-Easier to connect your vogue with android to your pc and sync
-Much more convenient.
So how do I start?
STEP1:
The Build
First you need to find a Build that is usable with NAND. Most Hero builds at this moment are not. Here are some links:
Donut 1.6
http://forum.xda-developers.com/showthread.php?t=591104
Hero
http://forum.xda-developers.com/showthread.php?t=603028
Cupcake 1.5
Method 1 from http://forum.xda-developers.com/showthread.php?t=593786
DO NOT DOWNLOAD ANYTHING JUST YET! I WILL TELL YOU WHEN A GOOD TIME WOULD BE
You may want to consider reading the rest...
STEP2:
Base Files (Most builds will supply these)
For all builds (Except the Link in Cupcake "instructions are givin in the download.) you will need a basic set of base files. The link below contains the 3 basic empty files for all builds and Systems.
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/Androidstuff.rar
IF
You are using Hero make sure you download hero.user.conf too:
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/hero.user.conf
-create a new folder called conf
-and place hero.user.conf in your new folder.
STEP3:
Rootfs
After you have the Base files you will need a rootfs. Depending on your Build, you may need a different type then the one I am going to supply you. Most builds will supply you with one. This one is DZO's rootfs.
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/rootfs.img
STEP4:
Prepare
-You need to clean out your storage on your SD. Make sure you delete everything.
-Create a file called android on your desktop.
-Download the base files, unzip, open folder, and place all 3 in your android folder
-Download the rootfs and place them in your android folder. Make sure you either download DZO's or the one your Build provides.
-Download a System.img. When you download a System most likely it will have a different name such as system-hero-123.img. You need to rename it system. So it should look like system.img . Then place it in your android folder.
-If you are using Hero place your conf folder in your android folder.
-Depending on your Build (mostly Hero) you may also need a Data file. The build you select should supply one. Download it and place it in your Android Folder
STEP5
Placing
Open up your android folder of all your collected files and select all, copy, and paste into your empty SD card.
STEP6
Unlocking
If you have never flashed a ROM before than you don't have HardSPL installed. So unlock your phone with...
http://forum.ppcgeeks.com/showthread.php?t=20370
Make sure you follow the forums directions.
STEP7
Method
Method1: The way I do it.
Download ROMUpdateUtility.rar
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/ROMUpdateUtility.rar
Extract to a newfolder
Download a kernel with your screen size
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
Don't know your screen size...check this out
http://forum.xda-developers.com/showthread.php?t=544906
After you have have gotten the kernel:
rename it to RUU_signed and place it in the ROMUpdateUtility folder you created.
NOW you need to plug your phone into your computer. Establish active sync. And run ROMUpdateUtility.
-Follow the Instructions on the screen.
Method 2 and 3 can be found here:
http://forum.xda-developers.com/showthread.php?t=593786
This also shows my method...but a little less detail. You can also find many other helpful things there.
If you fail OR think your bricked your phone.
You will need to download one of these depending on your carrier...Make sure you download the shipped gps rom. (If you are Verizon skip down)
http://forum.ppcgeeks.com/showthread.php?p=191607
Than you will put your phone in boot mode. Hold the Camera and Power button. While holding both of them...get a pen or something small and hit the little restart button on the bottom of your phone. You may have to hold it for like a second.
-you will see three color bars on your phone
-plug your phone into your computer
-run the backup
After your phone is all back to normal. Make sure you run internet explore on your phone. It will enable you to get data.
For Verizon follow the instructions here.
http://wiki.ppchaven.com/index.php?title=Pocket_PC_WIki:FIX_VERIZON_GPS
That is about it. I'm sure I forgot some stuff and will add on to this. Make sure you donate to the Devs for all their hard work.
DZO
http://forum.xda-developers.com/showthread.php?t=593786
jamezelle
http://forum.xda-developers.com/showthread.php?t=603028
plemen
http://forum.xda-developers.com/showthread.php?t=591104
vilord
http://forum.xda-developers.com/showthread.php?t=523692
They deserve it.
thank you this was very helpful
inphin1ty said:
thank you this was very helpful
Click to expand...
Click to collapse
No problem...
yea here is the md5sum: 9b08971e7f23619b6a9a4db9d52d857a
jamezelle said:
yea here is the md5sum: 9b08971e7f23619b6a9a4db9d52d857a
Click to expand...
Click to collapse
Whats that?
staud8469 said:
What are the benefits of running from NAND? (based on what I have seen)
1 Runs faster
2 Longer Battery life
3 faster boot up
4 can be faster to put together.
5 Easier to connect your vogue with android to your pc and sync
6 Much more convenient.
Click to expand...
Click to collapse
great thread. I've run both from nand and sdcard. i have not messed with ext2 on the sdcard.
I agree with 3 for sure. I would also add that there is a deep gratification in wiping win mo off the sdcard
6 is debatable, depends on which conveniences you want. changing lcd.density, changing resolution are all much faster running from the sdcard - no flashing or messing with build.prop, just edit default.txt and reboot (aside - if you have a non-sdhc card you can flash on the fly from the sdcard, but changing lcd.density still requires pulling and pushing files from the system, which is not as easy as changing the default.txt). also more convenient to back-up or revert to a data.img when running from sdcard. definitely booting straight into android is convenient, as is the new mass storage on boot method, as well as having a re-writable system (which you also have using ext2).
1 and 2, I honestly have not noted a significant difference in battery life. With a fast sdcard, I don't think there is a significant difference in speed either - dzo has said this in one of the non-vogue forums as well. i have not tried any sense builds from the sdcard though, and that's where you would notice the greatest difference in speed if there is any.
4 I agree with in general.
I think running from the nand is a huge advance, and great for everyone to try. but, running from the sdcard is still a decent way to use android. choosing between the two comes down to choosing which conveniences suit your usage style the most.
One last thing - please add vilord to your donate links (his google ion on vogue thread), he has been instrumental in developing the ril and advancing android on the vogue. srwalter also deserves mention for his reverse engineering of the libgps.so to bring gps first to cupcake and now to donut as well. jamezelle, plemen, mssmison, zenulator, enatefox, f00bar (no specific order) have all worked hard porting roms and working on things like compcache, swap, modem, etc, which has all been invaluable (zenulator and mssmison deserve special credit for spearheading the porting business). however the gruntwork of porting to the vogue has been done mainly by dzo who brought us the kernel and initial ril and now nand (he's just frickin amazing, he singlehandedly got the first functioning port to the vogue and others helped from there), then vilord who took the ril and really refined it. I guess suffice to say, there have been a lot of people involved along the way, thanks to all of them.
when i try to run android from both nand and haret i always get an error about not being able to mount sd card. does this mean i need to reformat the card? if so how do i do this?
Barogi44 said:
when i try to run android from both nand and haret i always get an error about not being able to mount sd card. does this mean i need to reformat the card? if so how do i do this?
Click to expand...
Click to collapse
When do you get this error? During linux kernel bootup?
Verizon users.
I just update a fix for Verizon users. Shows you how to get GPS too!
Also...there will be a video up soon. It seems that there are so many people having issues. So I will create a video from start to finish. Will be posted up late tonight/ tomorrow morning.
staud8469 said:
When do you get this error? During linux kernel bootup?
Click to expand...
Click to collapse
Yea.. i think i may need a new sd card. Can android boot from a 4gb card or is 2 the max?
Barogi44 said:
Yea.. i think i may need a new sd card. Can android boot from a 4gb card or is 2 the max?
Click to expand...
Click to collapse
i running with a 8gig PNY sdcard
it could theoretically run off of a 512, but you would be a little cramped on space
i guess android doesnt like some of them
so really it doesn't matter how big the card is? do they all have to be formatted to fat32?
Barogi44 said:
so really it doesn't matter how big the card is? do they all have to be formatted to fat32?
Click to expand...
Click to collapse
short answer, yes.
Hey guys...I will try my best to get that video up today. I am about to start recording it.
Am I correct in assuming that step 4-b is create a FOLDER name android on the desktop?
Can I delete those files from the SD when flashing is done?
THANK YOU for the N00B instruction, works great.
stopthebus said:
Am I correct in assuming that step 4-b is create a FOLDER name android on the desktop?
Can I delete those files from the SD when flashing is done?
THANK YOU for the N00B instruction, works great.
Click to expand...
Click to collapse
Yes that is correct, as for deleting the files...I would assume you could. But im not sure. Maybe they are still needed on boot. Never hurts to try though.
im not getting access to the internet after i flashed, am i suppose to edit anything?
im running the donut flash on my sprint vogue.
gigermunit said:
im not getting access to the internet after i flashed, am i suppose to edit anything?
im running the donut flash on my sprint vogue.
Click to expand...
Click to collapse
Wait...NVM you want data to work right?
If you are using donut...try to restart your phone one time. After it boots back up you should see a 3g symbol appear on the notification bar.
If that does not work...go to your apps and open modem. Click once on disconnect and then once more. Then click connect.
Tell me if that works...
HTC Legend build for the Vogue
As always, I take no responsibility for what this may or may not do to your phone. Do it at your own risk. This Build Overclocks your phone to 500, we've found that to be the fastest and most stable, however it may overheat and kill your cpu.
INSTRUCTIONS- YOU MUST FOLLOW!
Start by installing the androidinstall.tar to your sd or img file, (not nand)
Boot and wait a long time, there is no boot animation at all so the screen is blank., go through the setup.
After you've gotten rosie to load the first time, reboot and install the update.tar
This is going to set your lowmemoryparameters (androids build in taskkilller) to some very aggressive settings, as well it overclocks to 500. (I don't love it but it's the only way to run this rom nicely). Also the userinit sets compache with 96MB.
On reboot the phone/ril seems to be the last thing to kick in. (that or it just takes the png a bit to update) Don't worry about it, just be patient and it will enable your radio and connect.
For best results
Use system on sdcard partition, data on nand put a swap parition on your sdcard and edit the userinit.conf to use the swap parition as backing for compache. (this is how I'm running this build and it's good)
What doesn't work;
Bluetooth
Camera
What's cool;
The friend feed is actually cool
Hold the camera button for 2 seconds to view all the rosie screens.
Youtube works
Try something in flash, some works, some doesn't..
Notes
I don't expect to put alot of time into updating and tweaking this build as it is not my primary build that I work with. It is very hard to make 200MB nandable, but I may work on it in the future.
Tweaking;
If you want to play with the memory settings or the overclock just adjust the /system/bin/clock.sh or the /system/sysinit in the androidupdate.tar and re update.
Put your system on SDCARD partition, but put your data on nand. There's definitly a performance increase there.
New Version 03-20
Added LWP if using non rosie launcher
More speed tweaks.
Added HelixLauncher as a good alternative to rosie, to use clear defaults in settings -> manage applications -> HTC Sense. Than hold the cam button for 2 seconds to select different home app.
Next version
More space on /data
More speed tweaks
VogueSense Parts app
DOWNLOAD Works on Nand and Regular
https://sourceforge.net/projects/androidhtc/files/2010-03-20/legendnand.rar/download
Downloading! (37mn left ><)
Thank you for giving us an alternative to "standard" Eclair builds
Kiiv said:
Downloading! (37mn left ><)
Thank you for giving us an alternative to "standard" Eclair builds
Click to expand...
Click to collapse
a.) slow internet?
b.) need to use a different sourceforge mirror (cause I get 1MB/sec on sourceforge)?
mssmison said:
a.) slow internet?
b.) need to use a different sourceforge mirror (cause I get 1MB/sec on sourceforge)?
Click to expand...
Click to collapse
a.) slow internet
I have Darch's Legend on my Hero and LOVE it. Im tryin this on my son's vouge now!
edit...does it have the cool weather home screen animations?
Yes it does!!
Ahh ive recently switched back to windows mobile for speed and stability reasons..
but your builds and your reputation is the driving force for me to try this one.
Ill chime in on what i think.
screenshots?
It looks a little better than every other legend build.. lol seriously just google htc legend it looks the same as whatever pics and videos you'll see Except of course it's that tiny tiny bit blurry that everyone complains about with 320x480 on the vogue
k I've got a build done that should be fully nandable. but to be completely honest I don't really feel like wiping/testing today. I'll give it a shot this weekend and post if it works.
Otherwise the next update will include the ability to use livewallpapers (if your using a launcher other than rosie). and some other speed tweaks.
This is a nice build to play with it has the apps i need in the market I hope somebody can help speed it up
nand added.
Read first post.
is it possible to use it on polaris? not sure if the overclocking would suit the polaris
iseeka said:
is it possible to use it on polaris? not sure if the overclocking would suit the polaris
Click to expand...
Click to collapse
yeah sure, just open the update tar and in /system/bin delete the clock.sh file.
I haven't tried to put in wifi yet though
mssmison said:
HTC Legend build for the Vogue
For best results
Use system on sdcard partition, data on nand put a swap parition on your sdcard and edit the userinit.conf to use the swap parition as backing for compache. (this is how I'm running this build and it's good)
Click to expand...
Click to collapse
I would like to run this from ext2 partitions with Haret. Could someone please describe what partitions I should put on my sd card? (I know HOW to partition, just need some guidance as to sizes needed, especially if putting on a Linux swap.) Also, please describe what options to select on booting the first time. Running from Haret, do I really install data to NAND?! And, if so, without unlocking and flashing? Mssmison also mentions editing the userinit.conf, if using a swap partition. Please tell me which values need to be edited.
I am used to NoMoRootfs and the old sqsh running from Haret.
TIA.
I can't get this release to mount on my sd card I keep getting the wake up errors
sak211l said:
I can't get this release to mount on my sd card I keep getting the wake up errors
Click to expand...
Click to collapse
Me too. I tried to install the latest 3/20 nand builds into my sd, but failed. I will try the 3/29 builds
Can anyone tell me how fast this build runs?
I had the old SenseHero build from Jamezelle, but most of the time when the phone rang my phone was too slow to pick it up, and I missed the call.
I hope this one is faster
Deodex
Theres a way to make this build smaller
Deodex apps. This build has 21.8MB of .odex files.
tiagoclc said:
Theres a way to make this build smaller
Deodex apps. This build has 21.8MB of .odex files.
Click to expand...
Click to collapse
the files being odex'ed makes them faster. That's why I've left them like that
kiwilime said:
Can anyone tell me how fast this build runs?
I had the old SenseHero build from Jamezelle, but most of the time when the phone rang my phone was too slow to pick it up, and I missed the call.
I hope this one is faster
Click to expand...
Click to collapse
It's not atleast on my tilt its probably the worst sense build I have run yet props to mssmison on getting it ported though. Good job, it looks good but way too slow for me to run even on nand. back to playing with the other sense build on SDcard ext2 img, for some reason I cannot get any build installed to partitions I have tried with both cards
A Noobs Guide to Getting Started with a Custom Rom on the Nook Color
So you heard about the nook color. How it's a cheap e-reader that can be pushed to the limit and you are wondering how you can enable this power for yourself. Well you came to the right place!
Table of Contents
1. Why you should NOT use Honeycomb
2. SD or Internal instal
a. SD install
b. internal install
3. Restoring to Stock
4. Other Cool Stuff
5.Issues
6. Conclusion
7. Changelog (Last update 1/10/12)
1. Why you should NOT use Honeycomb
So you've heard about how the Nook Color can run Honeycomb and you are thinking that you want to try it. I mean why not? It's a tablet OS and the Nook is supposed to be turned into a tablet right? Well here's how it is. Honeycomb unlike other versions of Android is not an open source release. That means that developers cannot see how it works and have to reverse engineer basically the entire thing. This leaves you will something that barley runt because of countless missing drivers and many bugs from the SDK simulator. Honeycomb is a very painful and unstable experience. Do not use it. Wait for the next version of Android codename Ice Cream Sandwich to come out. For now use CM7. To check on the progress of CM9 (AKA ICS) check out this thread where you can find the first alpha builds.
2. SD or Internal install
The first decision you need to make is if you want to install CM7 (Android) over your current stock firmware or to run from an SD card.
a. SD Install
The benefit of running from an SD card is that you get to keep your Nook's current stock rom along side your Android install. The downside is that Android will run terribly if you do not use the correct SD card.
When running from an SD card use ONLY a SANDISK CLASS 2 or 4!
Take a look at this thread here for why you need to use a Sandisk:
Instructions for installing to an SD card
b. Internal Install
I recommend you do an internal install just because it is more stable and a lot easier to troubleshoot and upgrade to a newer CM version. If you ever need to return to stock it is very easy (see part 3).
To install to your internal memory follow this guide
Remember if you have a newer Nook that came with stock version 1.2 or above you may want to follow the repartitioning instructions here to have more space available to save files.
3. Restoring to Stock
So something happened and you need to return to stock. You need to make a warranty claim, register you device with BN, or whatever.
Here is what you need to do
When you are done you will have a complete stock Nook to do whatever you want with.
4. Other Cool Stuff
Watch Hulu with a hacked flash app
Make your Nook more Honeycomb like with TransformerBread
5. Issues
Help Facebook keeps force closing!!!!!
Solutions:
1. Use Facebook 1.6 or lower
2. Use tetherGPS lite
3. Use a third party app
Use this thread for help
N64oid won't work!!!!
Starting with N64oid 2.0 and above the new .32 Nook kernel used in CM7 does not work with N64oid.
Solutions:
Use a version of N64oid before 2.0
Use an older version of CM7 without the .32 kernel
Use this thread for help:
6. Conclusion
I hope this guide helped you out. If you think there is anything I should add or you have any questions feel free to comment.
7. Changelog
1/14/11
Restoring to stock guide updated for 1.4.1 zip that will work for people with new touchscreens.
1/10/12
New Guide for restoring to Stock that uses 1.3 and the new clockwork to work on the newer blue dot Nooks.
Removed 1.2 zip as it is no longer needed
Removed "Guide" from Changelog
Changed "Guide Changes" to Changelog in Table of Contents
Added link to CM9 dev thread
12/23/11
Added 1.2 restore zip link
Added Conclusion to table of contents
Good work, kookid,
Comment on 2.b. about re-partition. It is an option, not a must so saying "you need to follow ...." might confuse others.
votinh said:
Good work, kookid,
Comment on 2.b. about re-partition. It is an option, not a must so saying "you need to follow ...." might confuse others.
Click to expand...
Click to collapse
Oh good point. Will change.
---------------------------------
Sent from my LG Optimus V using Tapatalk
Good overview for newcomers.
Will return here when I get my NC in November.
Two thumbs up, maybe this should get stickied.
What about overclocking/undervolting kernels?
OrganizedFellow said:
What about overclocking/undervolting kernels?
Click to expand...
Click to collapse
Overclock/undervolt is included in the CM7.1 kernel.
Overclocking is built in to the CM settings. To undervolt you need to use the Nook Tweaks app.
---------------------------------
Sent from my LG Optimus V using Tapatalk
Reverting to the factory original ROM can be done much easier than the link provided. I would post the link but I have not yet posted enough to provide a link.
BASIC! said:
Reverting to the factory original ROM can be done much easier than the link provided. I would post the link but I have not yet posted enough to provide a link.
Click to expand...
Click to collapse
Could you at least post the name of the thread? I'm always looking for better ways to do things.
---------------------------------
Sent from my LG Optimus V using Tapatalk
BASIC! said:
Reverting to the factory original ROM can be done much easier than the link provided. I would post the link but I have not yet posted enough to provide a link.
Click to expand...
Click to collapse
Link provided by koolkid was for 1.0.1 but I think it was the standard procedure for any other version.
I'm eager to learn a new, better way.
I just substitute the full 1.3 .zip for the CM7 and gaaps .zips when booting with the original install image and it works fine. I recommend everyone who installs CM7 to the eMMC save their original install SD card for future needs and buy a 2nd one for use with CM7. The 1.3 .zip now seems to be missing from the drop box site though so someone will need to repost it. It was linked in this thread: http://forum.xda-developers.com/showthread.php?t=914690&page=29
Thanks for a very useful thread ... even though I already have mine running on CM7 since last month, really grateful for the info regarding the Facebook FC.
I'm still very much a noob at this.
One suggestion for more info regarding an issue which many noobs like me may have: How to expand the partition to use the rest of the SD card. On my 16Gb card, it now has four partitions: Boot, 2x unallocated, and Storage. Using EASUS PartitionMaster, how do I expand the fourth partition ? Do I have to delete the two unallocated ? Any further info regarding this would be very much appreciated !!
If I use App2SD, which partition would those programs go to ? Seeing that I already booted from SD, the Apps are already on the SD, right ? No need to "move to SD" ?
Thanks ahead for the schooling !!
vn33 said:
Thanks for a very useful thread ... even though I already have mine running on CM7 since last month, really grateful for the info regarding the Facebook FC.
I'm still very much a noob at this.
One suggestion for more info regarding an issue which many noobs like me may have: How to expand the partition to use the rest of the SD card. On my 16Gb card, it now has four partitions: Boot, 2x unallocated, and Storage. Using EASUS PartitionMaster, how do I expand the fourth partition ? Do I have to delete the two unallocated ? Any further info regarding this would be very much appreciated !!
If I use App2SD, which partition would those programs go to ? Seeing that I already booted from SD, the Apps are already on the SD, right ? No need to "move to SD" ?
Thanks ahead for the schooling !!
Click to expand...
Click to collapse
For your first question: just right click the 4th partition, select resize and then make sure everything is selected.
For your 2nd question: I'm not exactly sure as I do not use an SD install. Maybe someone else with more SD booting experience can help but what I am thinking is that all of your apps are on the 2nd or 3rd partition but when you use app2SD they get moved to the 4th partition.
---------------------------------
Sent from my LG Optimus V using Tapatalk
votinh said:
Link provided by koolkid was for 1.0.1 but I think it was the standard procedure for any other version.
I'm eager to learn a new, better way.
Click to expand...
Click to collapse
I found a link that I could post:
http://forum.xda-developers.com/showthread.php?t=1054027
The simple complete wipe is near the bottom of the first post.
BASIC! said:
I found a link that I could post:
http://forum.xda-developers.com/showthread.php?t=1054027
The simple complete wipe is near the bottom of the first post.
Click to expand...
Click to collapse
Unfortunately you cannot use the 8 failed boot method if you replace the stock recovery which most do when installing CM. That is why I used the method I did with this guide. It works no matter what is on your internal memory.
---------------------------------
Sent from my LG Optimus V using Tapatalk
BASIC! said:
I found a link that I could post:
http://forum.xda-developers.com/showthread.php?t=1054027
The simple complete wipe is near the bottom of the first post.
Click to expand...
Click to collapse
I'm probably slow but your provided link is for rooting the 1.2/1.3 NC using ManualNooter. It has nothing to do with reverse back to stock ROM.
And, the complete wipe near the bottom of the first post, again, has nothing to do with reversing if currently running custom ROM on eMMC.
A mod should definitely sticky this...most helpful thread I've read in the general forum yet.
Thank you so much
I just got a refurbished Nook Color and after hours of searching and reading I came across your post. This guide is a like a mother-load of good links and clear instructions. Thank you for taking the time to put it together. It has really helped me understand what was needed to get my NC up and running.
This is a really helpful guide for beginner.
I want to ask some thing about the whole workflow. I've used other Android phones to play with rooting and flashing new roms, but NC is quite new to me. So still need to make sure about something.
In this guide, there is nothing about rooting. And when I use CM7 from a SD card, I don't have to do that and already got the su in terminal. So I suppose if I just flash CM onto the eMMC, I'll get root access anyway. I don't have to root it right now in its stock system, right?
-Updated the Restoring to stock guide to use a 1.3 and the newest clockwork it's on Android Central for now but I might move it over here if I get some time.
zhourj said:
This is a really helpful guide for beginner.
I want to ask some thing about the whole workflow. I've used other Android phones to play with rooting and flashing new roms, but NC is quite new to me. So still need to make sure about something.
In this guide, there is nothing about rooting. And when I use CM7 from a SD card, I don't have to do that and already got the su in terminal. So I suppose if I just flash CM onto the eMMC, I'll get root access anyway. I don't have to root it right now in its stock system, right?
Click to expand...
Click to collapse
Nope, no need to root if you are going to flash CM7 because of the ability to boot a custom recovery from an SD card.
Hello everybody. After spending hours trying to figure out what I could delete from the system to make room for Gapps on CM10, I even tried to resize partitions, I came to the conclusion that the Gapps will have to be stored elsewhere. So, I came up with a solution, by installing the apps to /data/Gapps and then symlinking the files to /system. So since there are so many people trying to get Goggle Now on CM9, I figured I would make modified Gapps zips for both CM9 and CM10.
These are complete Gapp packages, they actually free up space on the /system partition, and are completely functional. Most of the files are installed to data/Gapps, this way the devs will not have to worry about trimming the ROMs, except to fit on the partition.
I'm sure this will help a bunch of other devices that have smaller system partitions also.
Note: Facelock requires you to log in to an account, to even show up in lockscreen options.
I don't think Google should have any issues with this as I haven't changed any files that where in the zip just moved them around and modified the updater-script.
Installation for fresh install:
1. Boot to your favorite custom recovery
2. Factory reset, wipe cache and dalvik cache
3. Flash CM9/CM10
4. Flash these Gapps
5. Reboot
Installation for previous install:
If you are already setup , you will need to wipe the cache and reinstall the ROM to format system to remove any Gapps already installed. As long as you don't wipe data/factory reset you should be right back where you started.
1. Boot to your favorite custom recovery
2. Wipe cache and dalvik cache
3. Flash CM9/CM10
4. Flash these Gapps
5. Reboot
Google Now Installation for CM9:
Google Now Installation for CM9 (fresh install):
1. Boot to your favorite custom recovery
2. Factory reset, wipe cache and dalvik cache
3. Flash CM9
4. Flash Google Now (online)
5. Flash these Gapps
6. Reboot
Google Now Installation for CM9 (previous install):
1. Boot to your favorite custom recovery
2. Wipe cache and dalvik cache
3. Flash CM9
4. Flash Google Now (online)
5. Flash these Gapps
6. Reboot
[MOD][ICS] The Google Now for ICS Project [ARMv6 & v7]
Symlinked Gapps for ICS Ver3:
Fixed Facelock.
Note: Facelock requires you to log in to an account, to even show up in lockscreen options.
Had to add placeholders in system/vendor for the symlinks to be created, but vendor is still 0 bytes
symlinked-gapps-ics-20120429-signed-Ver3.zip
Symlinked Gapps for JB Ver2:
Fixed Facelock.
Note: Facelock requires you to log in to an account, to even show up in lockscreen options.
Had to add placeholders in system/vendor for the symlinks to be created, but vendor is still 0 bytes.
symlinked-gapps-jb-20121011-Ver2.zip
thank you very much
this reduces the pain while trimming the rom for matching system partition
in this same way can we get google offline voice..?
reversegear said:
thank you very much
this reduces the pain while trimming the rom for matching system partition
in this same way can we get google offline voice..?
Click to expand...
Click to collapse
GNow offline for ICS still requires about 60mb. So it will depend on the ROM. But, it works with our Triumph ICS ROMs. And they should be almost identical, as far as I've seen. I use GNow offline with my PA ICS ROM, with no issues. I haven't spent much time on any of the X6 ROMs, as we can't use the newer kernel and still use our phone service.
Let me know how it goes.
Sent from my WX435 using Tapatalk 2
This is great way of freeing up system partition..! So can our device be repartitioned? And make some internal memory available as internal sdcard?
bandukia said:
This is great way of freeing up system partition..! So can our device be repartitioned? And make some internal memory available as internal sdcard?
Click to expand...
Click to collapse
Already we have a enough internal memory 1gb. What we need is system partition which is 245 mb needs expansion may be additional 100 mb from internal memory. that is where the pain area.
"Fixed Facelock.
Note: Facelock requires you to log in to an
account, to even show up in lockscreen
options."
what do you mean by this sir?
thanks.
^_^
It is okey to flash this gapps when already some gapps (gmail, voice etc) in our rom? ....
Or we just force to uninstall before flash this? ..
Btw thx dude, great job.... :thumbup:
Ps:im using jb rom by dr.rush
Sent from my Andro-Id using Pulsa
reversegear said:
Already we have a enough internal memory 1gb. What we need is system partition which is 245 mb needs expansion may be additional 100 mb from internal memory. that is where the pain area.
Click to expand...
Click to collapse
thats not what i meant.. i was saying that partitioning our phone with what u said and also with some 100-200 mb to make internal memory detect it as sdcard?
bandukia said:
This is great way of freeing up system partition..! So can our device be repartitioned? And make some internal memory available as internal sdcard?
Click to expand...
Click to collapse
Thanks, our partitions can not be repartitioned/resized, I tried everything except deleting the extended partition(4) that holds 5 - 17. That is why I made these.
This is the breakdown of the partitions on our phone:
BSydz said:
So, this is what I have found so far about the partitions on the Triumph, I can't guarantee that this is all correct, but if anybody has any input feel free to chime in.
WARNING, THE INFORMATION PROVIDED BELOW IS SPECULATIVE AND COMES WITH NO WARRANTY. IF YOU MESS WITH THIS STUFF, I AM NOT RESPONSIBLE IF YOU DAMAGE YOUR PHONE.
Partitions:
1 (FAT) Mobile Partition containing image folder, which is very well documented around the forums.
2 (crypt/QNX4.x) Primary Boot Loader (PBL) I believe that this is what the SOC uses to boot.
3 (crypt) Secondary Boot Loader I believe this is where the hardware layout is contained, as it changes button configuration and was key to getting back to normal after I flashed the wrong nb0. It is linked to the mobile partition, as the phone will not boot properly without the correct amss.mbn
4 (extended) Just an extended partition containing partitions 5 - 17.
5 (Boot) This is where the boot img is extracted.
6 (OnTrack DM) I think this manages and verifies integrity of partitions 13-17.
7 (ext3) This is where the system/rom is located. This is what you see in root explorer as "system", containing the build.prop and other stuff.
8 (ext3) This is the "data" folder .
9 (ext) This partition holds CDA info, with OEM apks, ringtones, and wallpapers, it seems to be mounted inside partition 10 (hidden) when the phone is on you can find the information merged into "hidden/data" using root explorer.
10 (ext3) This is the hidden partition containing boot images and CDA info. This can be found in "hidden" using root explorer.
11 (ext3) This is the cache partition.
12 (ext3) This is the Caivs, can't find too much info on this.
13-17 (unknown) I believe this is where the phone specific data is stored, including but not limited to MEID, ESN, and PRL.
Click to expand...
Click to collapse
reversegear said:
bandukia said:
This is great way of freeing up system partition..! So can our device be repartitioned? And make some internal memory available as internal sdcard?
Click to expand...
Click to collapse
Already we have a enough internal memory 1gb. What we need is system partition which is 245 mb needs expansion may be additional 100 mb from internal memory. that is where the pain area.
Click to expand...
Click to collapse
Since there is no way to resize any partitions, that is why I made these. Data is the only partition that we can really use that won't require us to heavily modify the phone and be user friendly. Because not everybody who installs custom ROMs is gonna be able to do those types of modifications. This is the simplest way to fix the issue and won't impact anybody who wants to change ROMs.
aeoi said:
"Fixed Facelock.
Note: Facelock requires you to log in to an
account, to even show up in lockscreen
options."
what do you mean by this sir?
thanks.
^_^
Click to expand...
Click to collapse
I have had this posted in another forum for a while, the original tread is below. We (Triumph users) did not have camera working in ICS, and still don't on JB, So when I first released these, the optional script that installs facelock was not correct. Now that I have fixed the front camera, I got feedback that facelock was not working. While trying to fix it, I spent a few hours, never even getting the option in lockscreen settings, and finally added an acount one time so I could get some apps from google to figure out what was happening. Then I went in to the settings and it was there. So the hours I wasted was because I hadn't added an account. So face lock will not even show up in lockscreen settings until an account has been added to the phone. I think it has to do with having to have a second unlock option if facelock can't work, like low light situations.
http://androidforums.com/triumph-al...-w-google-now-ics-instructions-09may2013.html
adonwenas said:
It is okey to flash this gapps when already some gapps (gmail, voice etc) in our rom? ....
Or we just force to uninstall before flash this? ..
Btw thx dude, great job.... :thumbup:
Ps:im using jb rom by dr.rush
Sent from my Andro-Id using Pulsa
Click to expand...
Click to collapse
It may work, one of the issues I had was the script was putting the optional files in system (the wrong place) and then the symlinks would overwrite the files. So this leads me to believe it may work, but I can't promise anything. If it doesn't work I can add some stuff to delete specific files in the updater-script, or you can remove the files from the ROM zip before flashing. You will want to at least wipe cache before you try these. I hate to say it, but you may have to be the tester.
Now that you guys are aware of these Gapps, you should ask your dev to remove Gapps from the ROM if possible. That would probably be the best route to go.
bandukia said:
reversegear said:
Already we have a enough internal memory 1gb. What we need is system partition which is 245 mb needs expansion may be additional 100 mb from internal memory. that is where the pain area.
Click to expand...
Click to collapse
thats not what i meant.. i was saying that partitioning our phone with what u said and also with some 100-200 mb to make internal memory detect it as sdcard?
Click to expand...
Click to collapse
Sorry, as I explained above, this is not an option. Big SD cards are cheap now, and how would a couple hundred MB help anyway? If it is for swap, then it would be better to wear out your SD rather than your internal HD. Plus a good SD would be faster.
If anybody has any other questions feel free to ask.;
Thank you Bsydz for throwing light on the so far untouched topic in our forum
Lots of useful information.
Off topic question
Can you please let us know how do we port JB ROMs from triumph to ideos x6. Especially PA Rom
reversegear said:
Thank you Bsydz for throwing light on the so far untouched topic in our forum
Lots of useful information.
Off topic question
Can you please let us know how do we port JB ROMs from triumph to ideos x6. Especially PA Rom
Click to expand...
Click to collapse
Thanks. If I had another dev phone I would just build one for you guys. It is a pain switching over cause we never got an nb0, I have to manually swap out the partitions to get it back. That's where I got the info about the partitions. My PA JB is built on CM10, so it would be just like any other CM port except the headphones and most everything else should work. It is older since PA went to aosp instead of CM based. Are any of your CM10 ROMs built from source or just ports? It would be nice to see some of the edits made for our phone. The only thing that's not working on ours is 3G, video/camera preview, and HDMI. But you guys use sim cards so I don't think you would have 3G issues and your kernel should fix the previews.
I'll build a PA JB ROM if you are willing to test it. I have the device files and the kernels except ck's kernel. Let me know, cause I hate releasing something I can't test first.
Sent from my WX435 using Tapatalk 2
im ready to test the rom.
we have both the CM10. I.e built from source and port rom
This one built from source by master abenaigle
http://forum.xda-developers.com/showthread.php?t=2158624
This one is stable CM10 by Dr.Rush
http://forum.xda-developers.com/showthread.php?t=2160913
V0.2 is stable ROM presently.
I've uploaded my modded kernel source, sorry... not in github.
reversegear said:
im ready to test the rom.
we have both the CM10. I.e built from source and port rom
This one built from source by master abenaigle
http://forum.xda-developers.com/showthread.php?t=2158624
This one is stable CM10 by Dr.Rush
http://forum.xda-developers.com/showthread.php?t=2160913
V0.2 is stable ROM presently.
Click to expand...
Click to collapse
CacingKalung said:
I've uploaded my modded kernel source, sorry... not in github.
Click to expand...
Click to collapse
Thank you, I am building it right now, just working through the errors from the ICS device files. CK, I got your kernel source, so we will see how it goes. I'll start new thread when it is done building.
BSydz said:
Thank you, I am building it right now, just working through the errors from the ICS device files. CK, I got your kernel source, so we will see how it goes. I'll start new thread when it is done building.
Click to expand...
Click to collapse
Ready to test your ROM.. All the best.
visit Techlions.in for latest tech news..
reversegear said:
im ready to test the rom.
we have both the CM10. I.e built from source and port rom
This one built from source by master abenaigle
http://forum.xda-developers.com/showthread.php?t=2158624
This one is stable CM10 by Dr.Rush
http://forum.xda-developers.com/showthread.php?t=2160913
V0.2 is stable ROM presently.
Click to expand...
Click to collapse
Firmware and kernel of our devices are compatible, I checked when flashing CM 9 from Motorola TRIUMPH, running everything except the data and the camera upside down
Sory for my english
Dr. Rush said:
Firmware and kernel of our devices are compatible, I checked when flashing CM 9 from Motorola TRIUMPH, running everything except the data and the camera upside down
Sory for my english
Click to expand...
Click to collapse
No need to apologize for language barriers. Do you think, you could put together a zip of the files in /lib and /bin that are for fb0? I just need the files that you put in to get it working, not all of them. It will make it easier to setup a device files for building from source. I have built the ROM and it boots, but no display, with copybit errors. I think I can get past those errors but once it fully boots, I'm sure things will have to be fixed.
Also, yes our phones are almost identical. Our amss.mbn is not compatible with the new kernel so we can't use our phone after the update. Just like you can't install the newer ROMs unless you flash the sharp nb0. I have it installed on my dev phone right now so i can get this working. I can install the nb0 and everything works perfectly except phone and 3g. It sucks, cause we are stuck.
Sent from my WX435 using Tapatalk 2
How much, I realized you're talking about the incompatibility of your phone with our 35 kernel, 32 kernel but your compatible with our device, in MTDEV M9 worked even mobile network, except 3g that prevents replace the kernel to fix the library and enjoy the new firmware
BSydz said:
Thank you, I am building it right now, just working through the errors from the ICS device files. CK, I got your kernel source, so we will see how it goes. I'll start new thread when it is done building.
Click to expand...
Click to collapse
any update on status...?