Well title says it all I did a search on this and what is a deodex and it came up with a bunch of nonsense and not the answer.
Also got two other questions is a about the ruu. Okay so I know that we can make our own release keys and what not to make a ruu but can we (there's a mouse on my shoulder) change the name of an hboot so that it is higher than the previous one so that you could run it on top of any other. What I'm getting at is when we get an official update someone will try for days or weeks to root when if we had a "homemade" ruu signed with release keys and higher build than they come out with than no one would have to worry about attaining root on a new build.
last question for now if my phone is the same build with the same processor as a mytouch why can't I just run a mytouch ruu to get it to run on tmo.
I can answer the last question.
T-Mo is GSM. Totally different radio hardware inside the phone.
An .odex file is an optimized dex file.
gunnyman said:
I can answer the last question.
T-Mo is GSM. Totally different radio hardware inside the phone.
Click to expand...
Click to collapse
see to me it doesn't make sense because we use the same towers as them but is it because the frequency maybe too much of a question
VinceOB said:
An .odex file is an optimized dex file.
Click to expand...
Click to collapse
wwhat role does it play with the apk though. Actually why do some apks need it and others don't
an odex is an optimized dex file. tru. its used to not clutter the dalvik-cache with extracted classes.dex's from said apks. thus it saves more system space, and also decreases boot time because packagemanager doesn't need to scan dalvik-cache every boot for respective classes.dex
darchstar said:
an odex is an optimized dex file. tru. its used to not clutter the dalvik-cache with extracted classes.dex's from said apks. thus it saves more system space, and also decreases boot time because packagemanager doesn't need to scan dalvik-cache every boot for respective classes.dex
Click to expand...
Click to collapse
okay in a not so technical way their used to save space and speed up the application
thatguythatdid said:
okay in a not so technical way their used to save space and speed up the application
Click to expand...
Click to collapse
i never said they speed up the application
darchstar said:
an odex is an optimized dex file. tru. its used to not clutter the dalvik-cache with extracted classes.dex's from said apks. thus it saves more system space, and also decreases boot time because packagemanager doesn't need to scan dalvik-cache every boot for respective classes.dex
Click to expand...
Click to collapse
So what's the down side?
Aside from having fewer files to deal with what do we gain by going to the trouble of deodexing?
nebenezer said:
So what's the down side?
Aside from having fewer files to deal with what do we gain by going to the trouble of deodexing?
Click to expand...
Click to collapse
the ability to modify framework dex's without borking your system. thats all. imo, odex'ing roms are the way to go. the only reason i don't is because a lot (not all) of the "devs" on these forums are really only extensive themers and they like to change font colors
So alot of this is greek to me but would an odex file change the way someone themes a rom (instead of the old replace a png with another png)
Thanks for the answers
darchstar said:
the ability to modify framework dex's without borking your system. thats all. imo, odex'ing roms are the way to go. the only reason i don't is because a lot (not all) of the "devs" on these forums are really only extensive themers and they like to change font colors
Click to expand...
Click to collapse
Interesting. Thank you
Is it only the .dex that do the borking?
Can you swap out .png's in odex'd apk's?
nebenezer said:
Interesting. Thank you
Is it only the .dex that do the borking?
Can you swap out .png's in odex'd apk's?
Click to expand...
Click to collapse
yes, you can theme odex'd apps just as you would an unodex'd app. the only restrictions are hardcoded stuff such as font color
thatguythatdid said:
we use the same towers as them
Click to expand...
Click to collapse
WHAT?!?!
Kcarpenter said:
WHAT?!?!
Click to expand...
Click to collapse
am i wrong? I never did to much research on this but I just read an article and it says that cell phone companies will lease their towers to other companies.
To answer the question about making an RUU... you can't.
We can make our own update.zip style updates, but we have to use a custom recovery to flash them because otherwise they won't pass the checks put in place by our current hboot. Now updating your hboot through RA is possible, but if you are already in RA then you are already rooted and you have no reason to need to mess with hboot to try and make it do something else.
The 1.56 RUU that I had modified was only modifying the exe file itself. The actual rom.zip contained in the RUU was totally legit and signed by HTC themselves. They are the only ones that can sign a .zip that will flash on our hboot without assistance (assistance meaning a custom recovery).
flipzmode said:
To answer the question about making an RUU... you can't.
We can make our own update.zip style updates, but we have to use a custom recovery to flash them because otherwise they won't pass the checks put in place by our current hboot. Now updating your hboot through RA is possible, but if you are already in RA then you are already rooted and you have no reason to need to mess with hboot to try and make it do something else.
The 1.56 RUU that I had modified was only modifying the exe file itself. The actual rom.zip contained in the RUU was totally legit and signed by HTC themselves. They are the only ones that can sign a .zip that will flash on our hboot without assistance (assistance meaning a custom recovery).
Click to expand...
Click to collapse
Thanks so why do they allow you the option of flashing update zips but dont ever give you one. So can a ruu be changed to downgrade the phone that can downgrade the phone
thatguythatdid said:
Thanks so why do they allow you the option of flashing update zips but dont ever give you one
Click to expand...
Click to collapse
Technically you could grab the rom.zip from an RUU and flash that via fasboot because it's signed by them. But that's no different than running the RUU itself.
My assumption is it's there more so for Sprint tech support for when you take your phone in, and not for us.
For example... our 1.56 MR update (before the RUU showed up) was an OTA update that it downloaded. That update was in update.zip format. It downloaded it to your phone and then rebooted in to recovery (had to be on the stock recovery) and flashed itself.
flipzmode said:
Technically you could grab the rom.zip from an RUU and flash that via fasboot because it's signed by them. But that's no different than running the RUU itself.
My assumption is it's there more so for Sprint tech support for when you take your phone in, and not for us.
For example... our 1.56 MR update (before the RUU showed up) was an OTA update that it downloaded. That update was in update.zip format. It downloaded it to your phone and then rebooted in to recovery (had to be on the stock recovery) and flashed itself.
Click to expand...
Click to collapse
Thanks and now i know
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG]
thatguythatdid said:
am i wrong? I never did to much research on this but I just read an article and it says that cell phone companies will lease their towers to other companies.
Click to expand...
Click to collapse
They rent out the physical tower structures, not the transmitter/receiver hardware. The radios run on completely different frequencies and protocols. Verizon and Sprint both use the CDMA protocol(although there are some differences). AT&T and T-Mobile both use GSM, which is more common internationally. Also, I have heard that Sprint will not activate a non-Sprint phone, even if it is compatible with their network. An easy differentiator is GSM phones require SIM cards, CDMA does not. Flashing a GSM radio to a CDMA phone is the absolute worst thing you could do and will most likely cause permanent damage.
so knowing that you can change png files in odex roms can you edit xml files as well. Im guessing you cant use smali and backsmali to get to the classes.dex file to change things in there so how would we change things back to get the vanilla and rotery lockscreens. All that was said was that you couldnt change font colors. But there are multiple ways to do that so which way cant you do it. thanks
Related
I partitioned my SD card
went to reflash the cyanogen rom, but i guess i forgot to rename the file to just updatezip, now its stuck on the finding update package
none of the keys reboot.
Im not sure if i should pull the batt out or what
i didnt really see anything in any threads
thanks for any help
Spoo76 said:
I partitioned my SD card
went to reflash the cyanogen rom, but i guess i forgot to rename the file to just updatezip, now its stuck on the finding update package
none of the keys reboot.
Im not sure if i should pull the batt out or what
i didnt really see anything in any threads
thanks for any help
Click to expand...
Click to collapse
you don't have cyanogen's 1.4 recovery image why? as long as it hasn't started to actually flash anything you should be fine yanking the battery
I'm not sure what you mean about not having the cyanogen recovery image, i do
this is the 2nd time I had the phone freeze up and you have come to the rescue both times. thats 2 beers i owe you lol
how about yuengling?
Pulled the batt, renamed the zip file
going to reflash the rom again thanks again
Spoo76 said:
I'm not sure what you mean about not having the cyanogen recovery image, i do
this is the 2nd time I had the phone freeze up and you have come to the rescue both times. thats 2 beers i owe you lol
how about yuengling?
Pulled the batt, renamed the zip file
going to reflash the rom again thanks again
Click to expand...
Click to collapse
what do you mean renaming lol and thanks for the beer but im 19 so newports it is lol thanks a lot man
ahh, i thought what locked it up was the fact i forgot to change the filename to update.zip
even though i thought it should look for any zip
so now that all seems well i can just reboot my phone and reflash the rom just like the first time i flashed it correct?
move to root of SD and reboot to recovery?
just 19 huh? you just made me feel old, I'm 31 lol
Spoo76 said:
ahh, i thought what locked it up was the fact i forgot to change the filename to update.zip
even though i thought it should look for any zip
so now that all seems well i can just reboot my phone and reflash the rom just like the first time i flashed it correct?
move to root of SD and reboot to recovery?
just 19 huh? you just made me feel old, I'm 31 lol
Click to expand...
Click to collapse
yeah 19 lol. there is an option to flash any zip do i need to post my recovery screen picture lol.
Not at all, that's what I've used every time...but i have fat thumbs and a quirky trackball.. I'm not sure but i think i may have rolled it to the other option.
doesn't seem to matter now
BTW i sent a dough nation your way lol
Spoo76 said:
Not at all, that's what I've used every time...but i have fat thumbs and a quirky trackball.. I'm not sure but i think i may have rolled it to the other option.
doesn't seem to matter now
BTW i sent a dough nation your way lol
Click to expand...
Click to collapse
just because i am an ass
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and i got it. thanks man. i like dough. and it looks cyanogen will be given us a ll donuts soon
yup, thats the one
in fact ive started to use ALT A because the trackball is a pain
I just wish you could use enter on the keypad to select the file rather than the trackball again
because it always double clicks and thats when i should hit home to confirm, yet it backs me out because its "any key"
so anyway the rom has been reflashed
and i see the other partion under the storage menu under settings but it shows up as only 61mb free internal phone storage
Spoo76 said:
yup, thats the one
in fact ive started to use ALT A because the trackball is a pain
I just wish you could use enter on the keypad to select the file rather than the trackball again
because it always double clicks and thats when i should hit home to confirm, yet it backs me out because its "any key"
so anyway the rom has been reflashed
and i see the other partion under the storage menu under settings but it shows up as only 61mb free internal phone storage
Click to expand...
Click to collapse
do you have the hard spl or the danger spl? also don't forget that cache still stays on internal memory so if you want that number to go up clear your browser cache
like right now my browser cache is 6.19mb's
hard SPL,
ahh ok I thought the number not changing was a sign it didnt work
Spoo76 said:
hard SPL,
ahh ok I thought the number not changing was a sign it didnt work
Click to expand...
Click to collapse
what number? did you not have apps2sd before or something?
I thought i read it wasnt needed for CyanogenMod v4.0.4
I guess i should add the info to my sig like everyone else
and the browser cache is already cleared
Spoo76 said:
I thought i read it wasnt needed for CyanogenMod v4.0.4
I guess i should add the info to my sig like everyone else
and the browser cache is already cleared
Click to expand...
Click to collapse
i meant did you previously have the partitions or did you just make them? cyanogen's rom will do it automatically for you if you have the correct partitioning setup which is fat32-ext2/3/4-linux-swap(optional).
and about the sig. it lets people know about ninjas(at least in my case)
Ninjas > pirates
as far as the partion yes, i just did the partion on my 8g sd card
all went well till the snafu flashing the rom again
now its flashed, but everything seems the same
double post
Spoo76 said:
Ninjas > pirates
as far as the partion yes, i just did the partion on my 8g sd card
all went well till the snafu flashing the rom again
now its flashed, but everything seems the same
Click to expand...
Click to collapse
does the secondary space on sdcard and storage show up?
yup, under the phones settings
Spoo76 said:
yup, under the phones settings
Click to expand...
Click to collapse
then it is working if you don't think so, download a lot of apps then look at internal memory or go to terminal and type
Code:
su
ls /system/sd/app
if a lot of app names appear then you are set
woot!
side note, I was hanging out with some Iphone friends all with the 3Gs and they are jealous lol
Since MrPippy no longer seems to be maintaining the thread over here, I figured I'd bring the latest way to properly run xdandroid on Touch Diamond CDMA devices. This has been tested on my Sprint Touch Diamond (DIAM500), your device may vary.
Android 2.2.2 (Froyo) for CDMA Diamond
Instructions:
From this xda post, download the XDANDROID build (currently 7/05/11).
From the XDANDROID zip file, extract AndroidApps/, conf/, media/, zImage, haret.exe, system.ext2, initrd.gz, modules-*.tar.gz, and rootfs.img into a directory called /andboot/ directory of your Internal Storage. If you extract the folder FRXnn/ (where the nn is the build) you can rename the folder to andboot/.
If you are using DIAM500 (Sprint's CDMA), navigate to FRXnn/STARTUPS/DIAM/DIAM500 inside the zip file, and extract the file called startup.txt into /andboot/ of your Internal Storage. These contain the necessary instructions for Haret to start Android on the Diamond. There are several other types of Diamond config file to try inside the zip file if you are not using Sprint's Touch Diamond, and should be renamed startup.txt if named differently.
The list of files you should have inside the Internal Storage should now look like:
/andboot/AndroidApps/*
/andboot/conf/froyo.user.conf
/andboot/media/*
/andboot/zImage
/andboot/haret.exe
/andboot/system.ext2
/andboot/initrd.gz
/andboot/modules-*.tar.gz
/andboot/rootfs.img
/andboot/startup.txt
Click to expand...
Click to collapse
If you want the older way of having everything in / (root) of the Internal Storage, just move everything from /andboot/ and also delete the argument rel_path=andboot from startup.txt.
Unplug the Diamond from the computer, and run /Internal Storage/andboot/haret.exe to start XDANDROID. If you have not done the calibration, there will be a white square with a cross that you will have to click on a few times. On first boot, it will take time for the system to set up the correct APN for data (usually a few minutes). If you get an error saying that no connection can be made, wait until the 3G icon appears on top before doing anything that requires data (Marketplace, etc.)
---
Optional: Download the latest rootfs Zip file from here.
Extract and rename the file rootfs-*.img to rootfs.img, and replace the one already in your Internal Storage.
Optional: Download the latest kernel bzip file from the links in the xdandroid post (several are provided) using 7Zip. Extract the modules-*.tar.gz and zImage.* file to your Internal Storage. You must then rename the zImage-* file to zImage after renaming/deleting the existing one. If you do not do this, Haret will not use the latest kernel file.
Caveats:
If you are running any previous versions of XDANDROID, it is highly recommended that you delete your data.img. This will wipe all your existing apps and data, but you can save your downloaded apps by going into /data/app and/or /data/app-private and copying it to /sdcard, but you need a root-capable file explorer.
GPS takes a while to get a position fix. It is working, but since there seems to be no AGPS support, it may take up to 15 min for the AGPS chip to get a fix on ephemeral data. Running QuickGPS from WM and keeping it updated seems to help a lot.
If you enable smart backlighting in WM, XDANDROID is unable to set the backlight level. Hopefully this will be addressed soon, since other devices (Rhodium, etc.) now has backlight support working.
If you still have trouble running XDANDROID, then make sure you post at least the following: What type of Diamond you have (model #), the startup.txt you are using (open it in Notepad to see the mtype), the build of XDANDROID you are using (along with any rootfs/kernel updates if applicable), and the last thing it does that you can see (ie. Haret reboots WM instead of running XDANDROID). Without this information, it isn't helping you or the person trying to help in order to figure out what may be going wrong.
A lot of information that applied to Andriod 2.1 (Eclair) also applies to 2.2 (Froyo), with the exception of where the files are located (/ vs. /andboot on the Internal Storage). I've kept Eclair-related instructions below.
Android 2.1 (Eclair) for CDMA Diamond Instructions: (for historic reasons)
From this xda post, download the latest XDANDROID build (currently 6/21/10).
From the XDANDROID 7z file, extract AndroidApps/, media/, zImage, haret.exe, system.ext2, initrd.gz, modules-*.tar.gz, and rootfs.img into the root of your Internal Storage. You must use a computer to extract this, none of the WM/Android apps have enough memory to extract the 7z file correctly!
Create (don't copy) a directory called conf/ on the root of your Internal Storage. Now navigate to conf/Diamond inside the 7z file, and extract the file called eclair.user.conf into the conf/ directory. This is important, you should have a file named conf/eclair.user.conf, not conf/Diamond/eclair.user.conf.
If you are using DIAM500 (Sprint's CDMA), navigate to STARTUP CONFIG/DIAM500 inside the 7z file, and extract the file called STARTUP.TXT into the root of your Internal Storage. If you are having problems with Haret restarting WM instead of booting, you can try the one inside CONFIG/DIAMOND100 or rename CONFIG/DIAM-STARTUP.TXT to STARTUP.TXT. Each file has a different MTYPE, and is most likely the cause of failure to boot into XDANDROID. (DIAM500 mtype 2040, DIAM100 mtype 1805, the unknown DIAM-STARTUP one uses mtype 1910)
Unplug the Diamond from the computer, and run haret.exe to start XDANDROID. On first boot, you cannot connect to Google's server until you have entered an APN (regression bug from 6/12/10.) Skip the account stuff for now, go into Settings→Wireless&Networks→Mobile Networks→APN, and create an APN with Name: Internet and APN: Internet. Press the Home key (to bring up the menu), Save, and then select the APN. You should get the 3G icon in a few seconds.
-- Starfox
Hello, I followed instructions, but there is a loading bar saying booting linux and my diamond reboot, what can i do ?
Thanks
Daedelus87 said:
Hello, I followed instructions, but there is a loading bar saying booting linux and my diamond reboot, what can i do ?
Thanks
Click to expand...
Click to collapse
your not the only one im working on this myself im trying to recreate a zip with it working for diam 500 and the touch pro no matter where i get the files from haret has become a problem and i dont know why so i remaking the files using old haret
ok so i got it working tho got stuck at the sign in part entered my info and then it kept looping back asking for it again and again found the if you restart it youre all set as for gps got a fix in under 30 secs going to repack the files for anyone who wants it this will work for the sprint touch and touch pro if you want the files let me know be more than happy to email them
Good call on starting the new thread. Kind of strange that Mr. Pippy never said anything before he took off.
For pure convenience, it may be best for the OP to compile a weekly build with all necessary files. Noobs might fare better if babied along and that would also assist in keeping this thread focused on more pressing issues.
I keep running into: "failed to mount the Sd card"
Edit: NVM, found the solution
so ran the new droid all night no hiccups but noticed that the time isnt synced it was off by ten minutes tried out the nav. drove to work looked at the time again it was now off by almost 15 mins maybe someone can enlighten me on this issue or is it just me
The only error I am getting is a keyboard error.
I did all steps as described above but if I run on haret.exe it says something like starting linux... but it just restarts the mobile and windows is starting again...
do you have any glue whats wrong?
psg190 said:
Good call on starting the new thread. Kind of strange that Mr. Pippy never said anything before he took off.
Click to expand...
Click to collapse
I think I saw something about him getting an android phone so he wasn't gonna be continuing it, i might be wrong though.
beepme2479 said:
so ran the new droid all night no hiccups but noticed that the time isnt synced it was off by ten minutes tried out the nav. drove to work looked at the time again it was now off by almost 15 mins maybe someone can enlighten me on this issue or is it just me
Click to expand...
Click to collapse
This seems to be an issue check the xdandroid thread and search for "clock" (i think theres an app called ClockSync or something)
NoLeftHere said:
The only error I am getting is a keyboard error.
Click to expand...
Click to collapse
apparently this is common and its due to the lag at startup of transferring files from the sd card... just press wait and it shouldnt be an issue
Flohman said:
I did all steps as described above but if I run on haret.exe it says something like starting linux... but it just restarts the mobile and windows is starting again...
do you have any glue whats wrong?
Click to expand...
Click to collapse
wrong startup.txt? you'll needa post more info about the error probably
Fail?
i think its cuz its only diam 500 not all the other cdma´s like diam 100??
(i mean that fail about startup)
Has there been any progress on metro data yet? This is the only reason why i uninstalled it from my phone. There was progress porting the us cellular data which uses proxies like metropcs for the touch with the android. There have also been native droid devices ported to work on metro as well so in theory it should be possible if anyone wants to work on this drop me a pm or discuss it here.
ok there is a issue with haret i for one can vouch for it the new haret.exe does not boot properly i dont know why or what is wrong but i know the issue is around i have a old haret that i use and works great even the new build has the same problem now if i can only fix my clock sync issue ill be happy
Seannoxious said:
Has there been any progress on metro data yet? This is the only reason why i uninstalled it from my phone. There was progress porting the us cellular data which uses proxies like metropcs for the touch with the android. There have also been native droid devices ported to work on metro as well so in theory it should be possible if anyone wants to work on this drop me a pm or discuss it here.
Click to expand...
Click to collapse
this is all i'm waiting for too.
ok found a fix for the clock still no reboots up and running for 26 hours now been unplugs for 7 hours and im at 34 % battery talk time 27 mins and lets say 5 text messages id say thats damn good
Great How-To post, got it working on my Diamond without any issues at all. Learning how to actually use Android is another matter.
notes:
mapping doesn't work, I presume it's because the GPS stuff is not functional
some of the hardware buttons are a bit confusing, just a matter of experience but it will take some getting used to
the device EATS battery power, and gets crazy hot when you start playing with the browser and other Android apps'
lack of any USB connectivity (beyond charging) is sort of limiting, hopefully it will be improved
so far I'm so impressed with XDANDROID, not that I hate Windows mobile but it is a great way to preview Android, especially for people like me who've only use WM.
[*]mapping doesn't work, I presume it's because the GPS stuff is not functional
Click to expand...
Click to collapse
It works with the latest updates and navigation with sattelite view is awesome but yea battery is a big drawback... keep a charger handy lol
-------------------------------------
Sent via the XDA Tapatalk App
Ps. And I mean xda on your phone is great
How loud is everyone's in-call volume? Mine is so quiet I can barely hear the other person.
RE-alive xandroid HTC DIAMOND 500 CDMA
Starfox said:
Since MrPippy no longer seems to be maintaining the thread over here, I figured I'd bring the latest way to properly run xdandroid on Touch Diamond CDMA devices. This has been tested on my Sprint Touch Diamond (DIAM500), your device may vary.
Android 2.1 (Eclair) for CDMA Diamond
Click to expand...
Click to collapse
Thanks Starfox for taking again this development,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I will try again Xandroid and this forum seems to be the only resource for our HTC diamonds CDMA. Thanks a lot and thanks all the people helping each other here.
APN Setup: http://forum.xda-developers.com/showpost.php?p=6799315&postcount=8296
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After asking around, I determined there was some interest in a simple, mostly-stock ROM based on the official HTC Sense/Froyo v3.26.605.1 release with only essential changes made; so I decided to go ahead and create one.
ROM Details:
Based entirely off the off the the official HTC Sense/Froyo v3.26.605.1 release (pulled from signed RUU); which is being rolled out by Verizon via OTA as the final build.
Moved some stock applications to /data/app, so they can easily be removed. To be clear, these apps remain enabled but can now be optionally removed using any Android uninstaller, rather than having to do it manually. This includes: App Sharing, Adobe Flashplayer, Car Panel, Flashlight, GenieWidget, PDFViewer, Quickoffice, Teeter, My Verizon, 3G Hotspot and YouTube.
All apps placed in /data/app by the ROM will be automatically restored after a date wipe or factory reset (a special feature of this ROM). These apps can be freely uninstalled via Settings->Applications or the uninstaller of your choice. Note: They will return when the ROM is re-installed or upgraded.
Disabled applications which the majority seems to agree are bloat, unneeded or can installed from the Market. This includes: Amazon MP3, City ID, HTC Footprints/Widget, VZ Navigator, Skype. If you decide you would like to use any of these apps, the APKs are available in the "system/virtuous" directory.
Numerous customization options via ROM Manager, such as Virtuous' EZ-Customizer which allows removal of more stock apps without the use of adb or shell, status bar mods provided by pmf, Incredible Revolution theme and more.
Automatic Virtuous OTA upgrade notification and installation via ROM Manager.
Minor theme modifications to remove GPS locator icon in the status bar and add transparency to the notification pull down menu. Thanks to pardonmyfreedom (aka pmf) and aiccucs for doing the work.
Added the Busybox installer application to allow upgrades as they become available. When running the installer, make sure to select /system/xbin as the destination.
Updated Adobe Flash to the official release provided to N1 users via the Market.
Updated Google Search and Google Voice Search to the latest Market versions.
Updated Gmail 2.2.1. The default ROM includes 2.2, so this is a minor upgrade to the latest version available.
Audio fixes to correct slow playback ("devil voices") of Flash videos on certain sites.
Removed startup "Drooooooid" sound. It was annoying.
Added the bash shell for those who work in adb or ssh into their phones. Just run "bash" to use it (it is not the default shell for compatibility reasons).
Removed cdrom.iso to avoid being prompted to install Verzion/HTC hardware when the device is connected via USB.
Installation:
You must be rooted, have nand unlocked and be running a 2.x radio. Follow dadicus' guide for details on how to perform these steps.
Perform a nandroid backup of your current ROM, in case you change your mind or encounter issues.
If you are coming from another completely stock ROM (i.e. Sense 2.1 or 2.2), you may not have to wipe data. I obviously recommend wiping data (since it will eliminate any possibly bad/stale configuration), but the update script will not do so automatically during installation. Use your best judgement to determine what works best for you.
Wipes are NOT required for any upgrade to/from any 2.x version of the ROM; downgrades are a different story.
Apply the zip via Clockwork Recovery. It has not been tested with any other recovery.
Expect the first boot to take anywhere from 6-10 minutes. Subsequent reboots should be significantly quicker.
Disclaimer
As with any modification (ROM, patch, etc), you run the risk of damaging your device. While unlikely, it is important to consider this possibility before proceeding. I take no responsibility for any such damage, data loss or otherwise.
Download ROM Here
(Changelog)
Hboot Upgrade Instructions
As of Virtuous 3.2.0, hboot 0.92 is now required. This hboot shipped with the original Froyo OTA for the Incredible.
Download this file and place it at root of your sdcard.
Boot into the bootloader. There are several ways to do this. If you are already booted into Android, use Quickboot and select the Bootloader option. You can also use adb by typing "adb reboot bootloader". Or, simply power down the device. Once it is off, hold the volume down button and then press power.
Once in the bootloader, select the first option from the menu "bootloader". You should see a progress bar on the right side of the screen. If you do not, you did not perform step #1 correctly or your sdcard is not formatted FAT32.
You will then be prompted to confirm flashing boot, bootloader and recovery. Hit volume up to confirm and then reboot.
At this point hboot is upgraded. I recommend reinstalling Virtuous (either via ROM Manager or manually) just to be safe.
Frequently Asked Questions
Visit the FAQ section of our website.
Recommended Extras
[Theme] INCredble REVOlution (SoCalMiles)
[MOD] Rotary Lock Screen w/ Music Controls for Sense (ihtfp69)
[MOD] Remove Status Bar Icons (Loc/Battery/Clock/Alarm) (pmf)
[MOD] Sexy Rosie (brucekey)
Special Thanks
Several folks have been helping with the ROM and I would like to acknowledge them all here in no particular order.
Unrevoked Team - For enabling customization to begin with.
ihtfp69 - Numerous tips on how to fix bugs. Check out his SkyRaider ROMs (Sense / Vanilla)
Adrynalyne -Custom Kernel, ROM collaboration and testing.
pardonmyfreedom - Location icon modification.
brucekey - Suggestions and testing.
Berzerker - Suggestions, testing and comedic relief.
Donations
Truth is I do this work because I enjoy it and it is a hobby. I am just pleased that people find what I am providing to be of value.
That being said, several folks have asked me about how to donate. If you would like to buy me a beer and help with hosting hosts, I've put up a link. No obligations whatsoever; you can also contribute by sticking around on this this thread and helping others work through any issues they encounter.
Thanks for trying my ROM!
Sweet thx man
Pics of rom please ?
Sent from my ADR6300 using XDA App
IIDIncII said:
Pics of rom please ?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Lol its the stock leak.
Add Footprints?
Thanks for this rom! I want to install footprints. I've tried with root explorer r/w on and off as well as astro. I've put the files in sytem/app, tried from disabled folder and even the sd card. It always goes through the install process correctley but always ends with
"application not installed". Any suggestions? Thanks
s-off
Thank you very much for this rom!
This looks great. I'm mildly sure this is sort of what jdkeclipse was trying to accomplish. This is how the OP is done well and done right. Thanks rmk40
You should just throw some screenshots in there regardless of the fact that it's a stock rom.
kentoe said:
This looks great. I'm mildly sure this is sort of what jdkeclipse was trying to accomplish. This is how the OP is done well and done right. Thanks rmk40
You should just throw some screenshots in there regardless of the fact that it's a stock rom.
Click to expand...
Click to collapse
you will be surprised what my next release will bring.....
and good to rmk for this rom!
Sent from my ADR6300 using XDA App
Thanks for writing a proper write-up/install guide; I am going to actually make the leap I've been avoiding for so long and try this one out =).
thom2k said:
Thanks for this rom! I want to install footprints. I've tried with root explorer r/w on and off as well as astro. I've put the files in sytem/app, tried from disabled folder and even the sd card. It always goes through the install process correctley but always ends with
"application not installed". Any suggestions? Thanks
s-off
Click to expand...
Click to collapse
you will probably have to push it through recovery with adb. I have noticed that if I use root explorer to add things to system/app they usually will not work for some reason, and the only way it will is through recovery or if I make a small flashable zip file.
Thank you! The app works but the widget does not?
Rmk, you just released it and a newer leak showed up today. Are you by chance going to mod the new one as well with your touches?
Haha, this awesome. Right after u get done with the work A new leak is released. Regardless this is very much appreciated.
Sent from my ADR6300 using XDA App
thom2k said:
Thanks for this rom! I want to install footprints. I've tried with root explorer r/w on and off as well as astro. I've put the files in sytem/app, tried from disabled folder and even the sd card. It always goes through the install process correctley but always ends with
"application not installed". Any suggestions? Thanks
s-off
Click to expand...
Click to collapse
Since that's an HTC app, you'll need to do that via recovery. Boot into recovery, adb shell, mount /system and go ahead and copy/move the files.
tats_06 said:
Rmk, you just released it and a newer leak showed up today. Are you by chance going to mod the new one as well with your touches?
Click to expand...
Click to collapse
I just saw it. Yes, that's definitely the plan.
We need to get it deodexed, figure out which bugs are present in the new leak, etc. As soon as I have something I feel confident works well, I'll go ahead and put it up.
thom2k said:
Thank you! The app works but the widget does not?
Click to expand...
Click to collapse
you will need to do the same thing with the footprintswidget apk.
Updated to base on today's 3.21.605.1 OTA.
Got home to a pleasant surprise! Got 2.0 flashed, and got a quadrant score of ~1300. Flashed KiNgxKernel BFS #1 and jumped my quadrant up to ~1600 running at 1113mhz. Also got solid 36s in linpack.
Ty for throwing this together. Was exactly what I was looking for! Even down to the boot animation sound. Gotta figure out how to change the boot animation still... kinda new to this.
Anyway, solid work. Keep us posted if anything new shows up.
Is bump charging still needed or does the phone finally charge properly?
With this application you can:
download and edit latest nbh
download latest zImage and configure your default.txt
Install system, install updates, backup data, backup system, clean data, partition sd card (only if there is only fat32 partition on it)
Change keymapping for vogue/Polaris/kaiser (still on develop)
And much more
Using dzo's kernel and initrd is deprecated so use the update version of 2.6.32 and 2.6.25
Atools is a multiplatform tool so it works on ALL systems!
If you are a stupid windows user read before posting!
For all clever user (Linux/Mac/Windows):
Prerequisites:
You must have python 2.6 or 2.7 installed.
(3.0 is not supported yet)
Download it from HERE
NBH Editor
NAND:
Download the latest nbh using the editor, and then select which settings you want.
This will only produce the nbh file.
This goes on the root of your device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HARET:
Select Haret and click on the download button to download the latest zImage.
You can also select what settings you want in your default.txt and then click the save button to create the default.txt file.
Click the box button (next to quit)to download the initrd.lzma.
All of these files go into the andboot folder.
Boot Script Generator
Makes installing and updating builds much easier!
No more holding buttons to get to install menus. Takes care of all the work for you.
Select where you want to install system and data and alter sizes(for SD).
Most settings are self explanatory, ask if you have any issues.
Can now partition SD during boot!
Produces an install-seq.sh file.
This needs to be placed in the andboot folder.
Key Mapper
Change the layout of your devices buttons.
Choose what you want and then click save.
Produces an androidupdate.tar file.
Place in the andboot folder.
You can use the "Apply update" option in Boot Script Generator to install.
GREAT THANKS TO LOOSERSKATE FOR CODING NBH AND WRITE GUIDE
Download atools here
old deprecated version here (right click -> save as) 0.1.1
Two guides added:
nand
haret
Sd partition tool works only with latest initrd.lzma
nand user need this download directly from the "net" button.
The sd card partition must have only one partition fat32 formatted
Also this post
Couldn't have been better timing. Glad to see you're takin over as you have a MUCH better idea of what you're doing. I still have a few more days with my kaiser so I'll try to help with anything while I can.
I know it's a lot easier to just use python, but it seems that everybody likes the .exe version of the nbh editor so here's an exe version of atools.
EDIT: Removed. Not updating exe anymore.
anyway you could build in the ability to flash the kernel too like the RUU does im on a Mac and having to flash via a PC kind of stinks
Vibrate while boot and shutdown
I hope there's an option to eliminate the vibrate while boot and shutdown too.
Thanks for this tools, very helpfull...
Looks awesome. Good work. Appreciate the inclusion of zImages and editing. Should be useful.
thoughtlesskyle said:
anyway you could build in the ability to flash the kernel too like the RUU does im on a Mac and having to flash via a PC kind of stinks
Click to expand...
Click to collapse
Does htcflasher not work on Mac?
Sent from my Full Android on Vogue using XDA App
Ive got a sad message for U. When I tick a GPU OC for kaiser, then my phone dont want to boot. Its writing a list of "bad blocks" on the screen and hangs, I cant even reinstall android cuz i get a message about "bad blocks, cant format" or something like that. After flash NBH without GPU OC it seems to be fine...
mrkite38 said:
Does htcflasher not work on Mac?
Sent from my Full Android on Vogue using XDA App
Click to expand...
Click to collapse
i wasn't aware of that program until now i just looked for a download for mac all i found was linux and windows downloads, can you point me in a direction i should look for it?
also having everything in one place would still be really awesome, think about it you can adjust a .nbh then flash it without even having to leave 1 program
The problem is that there isn't a cross platform tool and i don't know if it is possible to write it in python.
Python is cross platform and it's way i use it for these tools.
pentagramII said:
Ive got a sad message for U. When I tick a GPU OC for kaiser, then my phone dont want to boot. Its writing a list of "bad blocks" on the screen and hangs, I cant even reinstall android cuz i get a message about "bad blocks, cant format" or something like that. After flash NBH without GPU OC it seems to be fine...
Click to expand...
Click to collapse
Kaiser gpu overclock isn't working in this version. I just fixed it last night so it should work in the next release.
loserskater but i downloaded that version from sourceforge git repo... so I think it has a GPU OC patch for kaiser...
thoughtlesskyle said:
i wasn't aware of that program until now i just looked for a download for mac all i found was linux and windows downloads, can you point me in a direction i should look for it?
also having everything in one place would still be really awesome, think about it you can adjust a .nbh then flash it without even having to leave 1 program
Click to expand...
Click to collapse
Try the linux version? Not sure, never done it. I know we have a few other mac users, wonder what they use...
http://forum.xda-developers.com/showthread.php?t=399762
pentagramII said:
loserskater but i downloaded that version from sourceforge git repo... so I think it has a GPU OC patch for kaiser...
Click to expand...
Click to collapse
I'm not sure if kaiser supports the gpu overlook. I'll look into it tonight though.
EDIT: realized I had the vogue mtdparts set on Kaiser. Haven't tested but it should be working now.
For Alter System and Data Partition, how big the /system will be expand after install ? Can I assume, it would be the same for every builds ?
Or it won't expand at all after install, so I can determine the size just by looking the 'system' folder size ( unpack the .tar ) ?
Thanks.
It depends on distro, so expand the tar file an left some space.
l1q1d - was the atools pulled down? i receive: "Invalid Attachment specified. If you followed a valid link, please notify the administrator"
i've been trying to get this running for some time, and after losing a couple days - i put it to rest... but the wife it out of town this week, so it will keep me out of trouble!
i forgot to updat the link ...
Hi guys,
I recently upgraded from 4.1 using TWRP 2.6.3.0
It was my understanding that this latest TWRP supported the newer Android file system. After the upgrade, I can see that my SDCARD has moved to the '0' directory, great.
But, now when I make new backups in TWRP, I can't see them anywhere, but from within recovery. I have searched the whole file system for "2013-12" but see only the last backup before the upgrade.
Any help would be appreciated!
ccs86 said:
Hi guys,
I recently upgraded from 4.1 using TWRP 2.6.3.0
It was my understanding that this latest TWRP supported the newer Android file system. After the upgrade, I can see that my SDCARD has moved to the '0' directory, great.
But, now when I make new backups in TWRP, I can't see them anywhere, but from within recovery. I have searched the whole file system for "2013-12" but see only the last backup before the upgrade.
Any help would be appreciated!
Click to expand...
Click to collapse
Using Root Explorer, go from root to data/media/0 and scroll down to TWRP. Your new backups should be in place there.
Same vein. Why do I also have a TWRP folder with a backup under Main Storage? Can I delete one folder and gain 3gb back?
BMP7777 said:
Using Root Explorer, go from root to data/media/0 and scroll down to TWRP. Your new backups should be in place there.
Click to expand...
Click to collapse
Weird, so TWRP actually created a directory here: \data\media\TWRP
In the \data\media\0\TWRP directory, are my old backups.
Should I move the stuff from the later, to the former?
Are there any other steps to take to consolidate data, and make sure there are no duplicate files? My free space seems very low, compared to what it should be.
Bikegeek said:
Same vein. Why do I also have a TWRP folder with a backup under Main Storage? Can I delete one folder and gain 3gb back?
Click to expand...
Click to collapse
Check that folder before deleting, it may have backups from a previous ROM setup, such as a 4.2 or 4.1 set up. Don't want to delete stuff you may decide you want later.
ccs86 said:
Weird, so TWRP actually created a directory here: \data\media\TWRP
In the \data\media\0\TWRP directory, are my old backups.
Should I move the stuff from the later, to the former?
Are there any other steps to take to consolidate data, and make sure there are no duplicate files? My free space seems very low, compared to what it should be.
Click to expand...
Click to collapse
It depends on what you are running now(4.1, 4.2, 4.3, 4.4) and whether or not your 'old' backups would have any use for you. For example, I always keep a duplicate of my stock setup (out of the box stock) in that old folder just in case. If you decide to run an out-of the-box stock ROM i.e. 4.1.2, you will access your 'old' TWRP location. If you dump everything there, you'll be unable to access your current backups. Also, if you get yourself into a situation where you have either on purpose or by accident booted recovery to a former version, you won't be able to access your 'new' location. In that case, you'd be stuck sideloading or RUU-ing. Neither option is the end of the world, but to me convenience is everything. So, plan accordingly. If none of this makes any difference to you, and the extra space is important, do whatcha gotta do. :highfive:
BMP7777 said:
Check that folder before deleting, it may have backups from a previous ROM setup, such as a 4.2 or 4.1 set up. Don't want to delete stuff you may decide you want later.
It depends on what you are running now(4.1, 4.2, 4.3, 4.4) and whether or not your 'old' backups would have any use for you. For example, I always keep a duplicate of my stock setup (out of the box stock) in that old folder just in case. If you decide to run an out-of the-box stock ROM i.e. 4.1.2, you will access your 'old' TWRP location. If you dump everything there, you'll be unable to access your current backups. Also, if you get yourself into a situation where you have either on purpose or by accident booted recovery to a former version, you won't be able to access your 'new' location. In that case, you'd be stuck sideloading or RUU-ing. Neither option is the end of the world, but to me convenience is everything. So, plan accordingly. If none of this makes any difference to you, and the extra space is important, do whatcha gotta do. :highfive:
Click to expand...
Click to collapse
Thanks BMP.
I'm on 4.4 at the moment, with the CM11 nightlies. I may go back to a Sense ROM, but probably sticking to 4.3+.
I'm really not a fan of how the built-in storage is handled on these phones. Having windows mount it as a "media device" instead of a proper removable drive, really limits how you can interact with it. I've had all sorts of issues just trying to copy all the "SD card" data to my computer.
Is there any way to get windows to see this space? I'd like to at least be able to back up these new backups.
For me, whichever file structure I'm in for that rom shows up on my 7setup. I ve never had a problem getting at the current one,only the one not in use.
Sent from my BNTV400 using XDA Premium 4 mobile app
Shoot, still can't figure out how to get these backups dumped to the computer.
It seems very strange that TWRP created its directory in limbo here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my One using Tapatalk
Doesn't this storage usage seem odd
?
These two folders show duplicate size and file numbers. Neither appear to be a SIM link. Can't one be deleted?
Sent from my HTCONE using Tapatalk
Anyone?
Sent from my HTC Butterfly s using Tapatalk
Still haven't found a solution.