I've been working for the past couple of days on a multiboot/multi-ROM system for the Incredible, based conceptually (no code or implementation has been lifted) on Team ADX's DualRom.
It's a bit of a work in progress, right now, so I'm not entirely comfortable releasing anything (ROM images, the app), but I can give a couple screenshots and a brief technical rundown of how it works.
Screenshots
{
"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"
}
Implementation
ROMs (meh, I don't like calling them that anymore, they're not read-only ) are stored in /emmc as a collection of filesystem images. This is at odds with DualRom, which takes over all of /emmc as a system volume and maintains symlinks for /data and /cache. HBOOT seems too evil to leave well-enough alone, and may try to tinker with the /emmc volume, corrupting certain non-FAT32 partitions.
ROM update.zips need to be modified to create these loopback filesystems and loopmount them. I will be providing reference implementations for these update.zip modifications.
initramfs images will also need to be modified to loopback mount these images from /emmc. I will be providing reference implementations for these modifications, as well.
ROM icons and information are stored next to their images.
Example Filesystem Layout
Code:
$ ls -lh /emmc
----rwxr-x 1 system sdcard_r 45 Apr 19 23:20 CM7.ROM.json
----rwxr-x 1 system sdcard_r 17.4K Apr 20 03:12 CM7.ROM.png
----rwxr-x 1 system sdcard_r 1.9M Apr 19 23:20 CM7.boot.img
----rwxr-x 1 system sdcard_r 128.0M Apr 19 16:27 CM7.cache.img
----rwxr-x 1 system sdcard_r 640.0M Apr 19 16:31 CM7.data.img
----rwxr-x 1 system sdcard_r 200.0M Apr 19 16:31 CM7.system.img
Critique
Super ROM Switcher isn't actually its final name, but I am rather uncreative . I'm open to suggestions and feedback (about names, the interface, etc.)
There are a few rough edges that I plan to work out before release, such as the fact that it clutters /emmc and the interface doesn't display much useful information.
Planned Features
Mount a ROM hierarchy (reconstruct / from the initramfs into tmpfs, loop-mount /system, /data and /cache into it).
Possibly download prebuilt images.
Delete an entire ROM image set.
Release
TBD
Thanks
Team ADX - DualRom as inspiration
jaykresge - Nothing Special (used as Stock-style ROM in my testing)
MIUI devs - MIUI (used in testing)
CyanogenMod Team - CM7 (used in testing, and is awesome )
Looking forward to this!
DHowett said:
ROM update.zips need to be modified to create these loopback filesystems and loopmount them. I will be providing reference implementations for these update.zip modifications.
Click to expand...
Click to collapse
I think this is a great implementation concept, which is quite clean. The only issues I can think of (until I try it) is likely sd-ext, but I stopped using it long ago. I figure once I actually run out of space in data I'll switch.
DHowett said:
ROM update.zips need to be modified to create these loopback filesystems and loopmount them. I will be providing reference implementations for these update.zip modifications.
initramfs images will also need to be modified to loopback mount these images from /emmc. I will be providing reference implementations for these modifications, as well.
Click to expand...
Click to collapse
Now we just need someone to modify the clockwork recovery code to intercept the updates so we can get nightlies and other non dual boot .zip's working
EDIT: Meant to say great work! Looks very promising. As soon as I can use the existing (at least majority of) zips with this set up, would easily switch.
I like this too....now we could boot more than 2 roms
Sent from my ADR6300 using XDA App
DHowett said:
ROMs (meh, I don't like calling them that anymore, they're not read-only ) are stored in /emmc as a collection of filesystem images.
Click to expand...
Click to collapse
How do you feel about calling them "Loads," rather than ROMs? (This might also help with giving some permanent name ideas for this cool project.)
dscribe said:
How do you feel about calling them "Loads," rather than ROMs? (This might also help with giving some permanent name ideas for this cool project.)
Click to expand...
Click to collapse
So how many "loads" can this app take?
davwman said:
So how many "loads" can this app take?
Click to expand...
Click to collapse
Then why don't we call this app "She". How many "Loads" can "She" take.
Oh, and I can't wait to try this. Awesome work!
sd5500 said:
Then why don't we call this app "She". How many "Loads" can "She" take.
Oh, and I can't wait to try this. Awesome work!
Click to expand...
Click to collapse
I don't get itt
Sent from my ADR6300 using XDA App
This looks awesome! Will this let us install ROMs that have system folders larger than 250MB? If so, Sense 3.0 will be here in no time.
corypaul said:
I don't get itt
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Ill tell you when you're older.
Tapatalk Pro Sig. Yep, boring.
ROM Glom?
glom
verb
to take physical control or possession of (something) suddenly or forcibly
Dual boot is great.. it takes less than a minute to push a button to switch from stock sense to cm7 .... aka dual " she " boot
I think this kind of thing would be great as long as both ROMs can actively read each others texts and phone logs and that sort of thing.
Kind of like how I dual boot Ubuntu and Windows. The Ubuntu partition is relatively small, but I've got symlinks for the music, pictures, videos, etc. on the Windows partition. It keeps everything very smooth and convenient. (I know the music stored on the SD card will do this, I'm just using that as an example.)
I'm assuming, though, that since the AOSP and Sense DBs are so different, that it might not be feasible. Either way, I'll definitely be trying this. It's a really cool concept.
Mounting
Code:
localhost / # ls /emmc/SkyRaider4
bootcomplete.inc.rc init sbin
cache init.goldfish.rc shutdown.inc.rc
data init.inc.rc sys
default.prop init.rc system
dev proc
localhost / # ls /emmc/SkyRaider4/data
app dalvik-cache drm misc system
app-private data local property
backup dontpanic lost+found skyraider
localhost / # df -h
...
tmpfs 8.0M 304.0K 7.7M 4% /mnt/emmc/SkyRaider4
/dev/block/loop17 371.9M 235.4M 136.5M 63% /mnt/emmc/SkyRaider4/system
/dev/block/loop18 629.9M 121.9M 476.0M 20% /mnt/emmc/SkyRaider4/data
/dev/block/loop19 124.0M 5.5M 112.0M 5% /mnt/emmc/SkyRaider4/cache
The rootfs simulacrum is in tmpfs and mounted read-only to mimick that the ramdisk can't be modified easily. Everything else is accessible and modifiable.
Research
I looked into a couple means for booting kernels without reflashing boot.img. kexec() doesn't work properly (and most kernels aren't actually built with support for it, so it's a moot point). Meh, oh well.
Addendi
I'm going to open-source the management program once it's ready.
Questions
godsmacked4653 said:
I think this kind of thing would be great as long as both ROMs can actively read each others texts and phone logs and that sort of thing.
Kind of like how I dual boot Ubuntu and Windows. The Ubuntu partition is relatively small, but I've got symlinks for the music, pictures, videos, etc. on the Windows partition. It keeps everything very smooth and convenient. (I know the music stored on the SD card will do this, I'm just using that as an example.)
I'm assuming, though, that since the AOSP and Sense DBs are so different, that it might not be feasible. Either way, I'll definitely be trying this. It's a really cool concept.
Click to expand...
Click to collapse
Sense->Sense and AOSP->AOSP works, but anything else is a little bit iffy. I actually brought mmssms.db through Sense to AOSP but it required a full dump/reimport (with table fixing in between). It's too difficult to allow. However, mounting (as above) might help in copying over some data .
frostincredible said:
This looks awesome! Will this let us install ROMs that have system folders larger than 250MB? If so, Sense 3.0 will be here in no time.
Click to expand...
Click to collapse
Yep! Pretty much any size up to 4GB is supported (FAT32 limitation).
djh816 said:
Now we just need someone to modify the clockwork recovery code to intercept the updates so we can get nightlies and other non dual boot .zip's working
EDIT: Meant to say great work! Looks very promising. As soon as I can use the existing (at least majority of) zips with this set up, would easily switch.
Click to expand...
Click to collapse
I have an edify parser that (with some prodding) will turn an update.zip into ROM.system.img, ROM.data.img (etc)... a recovery modification isn't out-of-the-question, however!
Thanks for the support!
This sounds genius lol, would definitely save a lot of time and stress from flashing, switching, and wiping our phones all over creation lol.
Sent from my ADR6300 using XDA Premium App
Quite excited about this project I have to say.
What theme is on the screen of the OP?
Super excited about this. Is there an irc channel?
--
Sent from my Android phone. Please excuse my brevity/typos.
Blanko6 said:
What theme is on the screen of the OP?
Click to expand...
Click to collapse
Rover, but just the statusbar icons split into a separate theme.
daftlush said:
Super excited about this. Is there an irc channel?
Click to expand...
Click to collapse
irc.saurik.com #superrom
Related
Hello devs and users..i've seen on a website,that htc dream in the future (after android 2.0 eclair),can't be upgraded with new software version,because his internal memory is too small...is really so,or xda developers may create lighter updates?
Excuse for my (bad) english!
thanks everyone
PS:excuse me mods and amins but i've seen the correct section (dream Q&A)only now! =(
To answer the question here in case anybody else reads this thread (you should NEVER leave a thread in this state where it doesn't answer the question), the answer is this;
Those websites that you have read are written by MORONS. There is NO REASON AT ALL why dream can't be upgraded to any future android version. There is *plenty* of space, and a *LOT* that can be done to use storage and ram more efficiently.
iCe87 said:
Hello devs and users..i've seen on a website,that htc dream in the future (after android 2.0 eclair),can't be upgraded with new software version,because his internal memory is too small...is really so,or xda developers may create lighter updates?
Excuse for my (bad) english!
thanks everyone
PS:excuse me mods and amins but i've seen the correct section (dream Q&A)only now! =(
Click to expand...
Click to collapse
I gotta agree, those guys are morons. All the new android phones coming out are all close to the same specs so do you really think they would release phones now that will be obsolete before the contracts are up, nah. The dream has plenty of life in it and plenty of time for it to keep advancing. Plus the devs here work some crazy ass magic on this platform
Ok guys thanks for the answers =) i'm glad to read that!...however i expect to see the price of two android new phones: Motorola Cliq/Dext and Samsung Galaxy i5700..
their should be a low price smartphones (i hope this!)
the cliq looks like a nice peice of hardware coming out. But not be a bad next step, i got the g1 so i could be in on the ground floor of hacking android
but the dream has 256mb of rom memory. while all the other newer android devices have 512mb of rom memory and sources said that the cupcake update almost filled up the available rom memory. i just dont see how update past 2.0 will even fit. besides placing part of the rom on the sd card.
brian_v3ntura said:
but the dream has 256mb of rom memory. while all the other newer android devices have 512mb of rom memory and sources said that the cupcake update almost filled up the available rom memory. i just dont see how update past 2.0 will even fit. besides placing part of the rom on the sd card.
Click to expand...
Click to collapse
Sure 256. Thing is that the android OS DREAM ADP1 build (take a look at cyanogen's latest donut) is sitting at just over 60 MB (in the case of crazy experimental bloatware -- only 52.4 for the official image). And yes, that's already DONUT 1.6 (to prove that it can be done) My math says that we have a flexibility of somewhere in the neighborhood of (taking boot block and other stuff into account) about 140 MB sitting around that *could* be used for system. Very important to think about is the /cache partition, which is WASTING over *SIXTY MEGABYTES*, which means that we can EASILY fit in a system image that is *TWICE AS BIG*, and that is BEFORE compromising the /data partition (which also can be done yielding up to an additional 75MB).
Here's a tip for ROM developers as the /system partition starts to get tight....
mount /dev/block/mtdblock4 at somewhere like /system/block4, create a small (i.e. 5, 10 MB) loop filesystem at /system/block4/cache.img and mount THAT at /cache, then throw a whole bunch of crap from (for example) /system/app into /system/block4/app and create a link /system/app --> /system/block4/app.
Note: there is a WHOLE BUNCH of crap included in current system images that doesn't need to be there, i.e. install as regular apps instead of as system apps. Just as a quick look-through, there is over 10 MB that can be recovered just from the /system/app directory on cyanogen 4.1.10.1, with that, we can get close to 15 MB free on /system on a Donut build. Now put in some more aggressive optimizations...
There are *TONS* of things that can be done to fit in new android versions.
Oh, and did I mention that newer doesn't necessarily mean *bigger*? Who says that éclair (or flan) will be any bigger than 1.0 was?
Now consider this:
The "official" ADP1 v1.5 system image is only TWO MEGABYTES larger than 1.0 at 52.4 MB.. of an available 67.5 hmm.. that leaves plenty of space already = 15 MB. And I'm sure you're aware of how many new features and polishes they added into the 1.5 for only 2 MB.... Just think what they can do with 15! Just think what can be done with 75!!!! (before even compromising /data).
I'll repeat again just to be clear.... We are NOT up against a wall with space. There is *LOTS* of space for new versions.
Thanks to all for the informations!!i'm glad to to read that!!!!...
lbcoder said:
Sure 256. Thing is that the android OS DREAM ADP1 build (take a look at cyanogen's latest donut) is sitting at just over 60 MB (in the case of crazy experimental bloatware -- only 52.4 for the official image). And yes, that's already DONUT 1.6 (to prove that it can be done) My math says that we have a flexibility of somewhere in the neighborhood of (taking boot block and other stuff into account) about 140 MB sitting around that *could* be used for system. Very important to think about is the /cache partition, which is WASTING over *SIXTY MEGABYTES*, which means that we can EASILY fit in a system image that is *TWICE AS BIG*, and that is BEFORE compromising the /data partition (which also can be done yielding up to an additional 75MB).
Here's a tip for ROM developers as the /system partition starts to get tight....
mount /dev/block/mtdblock4 at somewhere like /system/block4, create a small (i.e. 5, 10 MB) loop filesystem at /system/block4/cache.img and mount THAT at /cache, then throw a whole bunch of crap from (for example) /system/app into /system/block4/app and create a link /system/app --> /system/block4/app.
Note: there is a WHOLE BUNCH of crap included in current system images that doesn't need to be there, i.e. install as regular apps instead of as system apps. Just as a quick look-through, there is over 10 MB that can be recovered just from the /system/app directory on cyanogen 4.1.10.1, with that, we can get close to 15 MB free on /system on a Donut build. Now put in some more aggressive optimizations...
There are *TONS* of things that can be done to fit in new android versions.
Oh, and did I mention that newer doesn't necessarily mean *bigger*? Who says that éclair (or flan) will be any bigger than 1.0 was?
Now consider this:
The "official" ADP1 v1.5 system image is only TWO MEGABYTES larger than 1.0 at 52.4 MB.. of an available 67.5 hmm.. that leaves plenty of space already = 15 MB. And I'm sure you're aware of how many new features and polishes they added into the 1.5 for only 2 MB.... Just think what they can do with 15! Just think what can be done with 75!!!! (before even compromising /data).
I'll repeat again just to be clear.... We are NOT up against a wall with space. There is *LOTS* of space for new versions.
Click to expand...
Click to collapse
only time willl tell. becuz i didnt get what u was saying i kinda skimmed. i just want to see the tru successor for the g1 from htc
{
"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"
}
gridlock32404 said:
Click to expand...
Click to collapse
hahahahahahahahahahahahahaha
{
"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"
}
Virtuous Unity is the first custom Sense 3.0 ROM, scaled for WVGA screens, to be based on an official shipping release from HTC (1.35.75.1).
The entire ROM is brand new, taking no application or framework components from any prior Sense 3 releases.
Unity is the result of a collaborative, team effort by the following developers:
Flemmard
Diamondback2010
rmk40
chrisch1974
m-deejay
seo
eViL D:
Screenshots
Features
Based on the official Sensation shipping ROM (1.35.75.1).
Ported for full functionality on each supported devices. Additional device support is being added regularly.
Resized for WVGA (800x480) displays, using a purpose built tool to modify HTC's proprietary m10 binaries, developed by Flemmard and Diamondback.
Heavily optimized for fluid performance and usability.
Overclocked kernels with numerous additional kernel modules.
Built-in screen state frequency scaling (1.2Ghz-245MHz/ondemand screen-on, 806Mhz-245Mz/conservative screen-off), via custom built Virtuous_OC C daemon.
Trackpad wake support (DesireZ/G2 and MT4G only).
WiFi calling (T-Mobile USA only).
Fully functional device hardware, including wifi, bluetooth, camera, camcorder, etc.
Market-sourced applications (Gmail, Maps, Voice, etc) automatically installed on first boot into /data/app for easy removal.
Bloatware and unnecessary applications removed.
Supported Devices
Desire HD
Desire Z
Desire S
Incredible S
Inspire 4G
myTouch 4G
Porting Information and Credits
Virtuous Unity, or any components therein, may not be ported to other devices without explicit email approval from the development team. We will be approving ports, presuming the develop of a given port is ready and willing to follow the same revision control and release processes currently employed existing devices.
hrk - Allowing use of ghostySMS Vision version.
cypis - For his awesome Unity-banner
robocik - Tips regarding APK compression.
Sybregunne - Virtuous Overclock Controller GUI.
HTC/Google- For building such a good base system.
Important Notes
If you are experiencing random freezes and/or reboots, this is likely due to your device being incapable of handling our overclocking defaults. Download and apply this flashable patch, which will reduce the maximum CPU frequency to 1Ghz and likely eliminate this issue.
You must complete a full wipe prior to installing this ROM the first time. We also recommend wiping between upgrades, but you are welcome to try upgrading without a wipe. However, no support will be provided if you file a bug without having wiped prior to submission.
Bugs and Errors
To ease the process of reporting bugs to the team, we made a public bugtracker where you can report the bugs you found. Please make sure you read all the existing entries there to avoid doubling the errors.
The bugtracker is located here.
Device specific information
Support for the Droid Incredible is in BETA status. Some compromises had to be made to support an older device. This includes disabling of the EBook Reader and using the Sense 2.1 Gallery application. Additionally, the custom kernel for this device is not ready yet, so the OC daemon does not function. Everything else should function normally.
*** SD-EXT PARTITION IS REQUIRED (512MB is fine) ***
Download :: Changelog :: More Information(Official Website of Virtuous ROM)
Reserved for future use.
Also reserved for future use.
I haven't used a sense rom in a while (since your other Virtuous ROM), have been using CM7 ever since. This has me tempted to give sense another try.
SD-Ext.
Noticed on virtuousroms that Ext4 journaling is used. Didn't see a way to upgrade the SD partition to 4 in CMR3.0.08. Will the default work? Also any recommendation on the partition size and do we need to specify a swap file? I am figuring with a 378MB file Dinc will need some help, lotsa help
Been waiting for this. Thanks for not forgetting about us old Inc users.
Sent from my ADR6300 using XDA App
flashing now
Only major issue so far has been weather force-closing so unable to change settings to Farenheit. After it settles for a bit the initial sluggishness improved. Very nice Rom...thank you
mcfarlan said:
Noticed on virtuousroms that Ext4 journaling is used. Didn't see a way to upgrade the SD partition to 4 in CMR3.0.08. Will the default work? Also any recommendation on the partition size and do we need to specify a swap file? I am figuring with a 378MB file Dinc will need some help, lotsa help
Click to expand...
Click to collapse
Take a look inside the rom. It actually has the setup for every phone inside it. So i'd imagine the final rom is around 260-270 for our phone. It also has some ebooks inside and a pretty large theme.
Is there any instructions for the sd-ext part? I've never done that.
Thanks
Sent from my ADR6300 using XDA App
i cant get past white htc screen
anyone know why ?????
Would you guys prefer using /data rather than /sd-ext? It's a fairly easy change. It'll mean less room for Market applications but makes it easier on most people also.
We may also be able to detect whether sd-ext is available and use it if it is, otherwise fall back to data.
rmk40 said:
Would you guys prefer using /data rather than /sd-ext? It's a fairly easy change. It'll mean less room for Market applications but makes it easier on most people also.
We may also be able to detect whether sd-ext is available and use it if it is, otherwise fall back to data.
Click to expand...
Click to collapse
i would say either
with complete instructions
is this why i can only get to the white htc screen????
jdog94 said:
i would say either
with complete instructions
is this why i can only get to the white htc screen????
Click to expand...
Click to collapse
Yes, very likely the reason.
rmk40 said:
Yes, very likely the reason.
Click to expand...
Click to collapse
How do you do the Sd-Ext I want to try this rom.....
Yay! Im going to try asap
rmk40 said:
Would you guys prefer using /data rather than /sd-ext? It's a fairly easy change. It'll mean less room for Market applications but makes it easier on most people also.
We may also be able to detect whether sd-ext is available and use it if it is, otherwise fall back to data.
Click to expand...
Click to collapse
Yes, I rather use /data
stick to SD-EXT
IncredibleDoes said:
stick to SD-EXT
Click to expand...
Click to collapse
Could you guys explain how to do the SD-EXT.. Im already giving up on this rom cuz I can get it to install...?? Thanks
1107963 said:
Could you guys explain how to do the SD-EXT.. Im already giving up on this rom cuz I can get it to install...?? Thanks
Click to expand...
Click to collapse
Clockworkmod recovery lets you partition your SD. Backup SD because it will wipe everything.
[RECOVERY] TWRP 2.2.0 with on-screen keyboard! [2012-07-12]
Team Win Recovery Project 2.2, or TWRP2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG (for 2.2.0):
- On-screen keyboard in recovery! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
- Name new backups and rename existing backups
- Rename files and folders in the file manager
- Pseudo-terminal emulator
- Support decrypting an encrypted data partition on Galaxy Nexus (enter password using keyboard)
- Backup archive splitting -- allows backup and restore of data partitions larger than 2GB
- Simplified XML layout support between resolutions
- Added dual storage selection radio buttons to zip install, backup, and restore pages
- Improved zip install compatibility
- Updated update-binary source code
- Numerous small bug fixes and improvements
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Changelog
Changelog:
2012-07-12 v2.2.0
See TeamWin's TWRP page for changelog.
2011-10-07 v1.1.1
See TeamWin's TWRP page for changelog.
2011-08-17 v1.0.3.1
Bug Fixes:
- Fixed issues with efs backup/restore - now fully tested
2011-08-05 v1.0.3
New Features:
- Added timezones that should cover everyone
- Added twrp spam feature (twrp settings)
- Added fix permissions (advanced menu)
- Added wipe cache and dalvik into Flash Zip menu
- Added copy recovery.log to /sdcard (advanced menu)
- Added output spam/no spam to restores
- Added mke2s prebuilt to /sbin
Bug Fixes:
- Fixed SD-EXT issues, (no partition SD-EXT features yet)
- Fixed EFS partition issues
- Changed the way we do backups on mtd devices, which should fix any boot partition issues
(we suggest making new backups if you have an mtd device, EVO4G,NS,NS4G)
2011-08-01 v1.0.2
Bug Fixes:
- Fixed SD-EXT issues
- Added Format SD-EXT into format menu
- Removed GAPPS support, CM7 automatically backsup and restores if you already have GAPPS installed. If you don't, just flash GAPPS zip
- Fixed issue where when flashing a rom, rebooting brings you back to recovery. Auto reboot after successful flash should work great now!
- Rearranged the format menu
2011-07-29 v1.0.1 - Initial release on Nexus S
FAQ:
How to install with Fastboot:
Download the fastboot binary for your computer and OS
Connect your phone and boot it into fastboot
Run fastboot with the command
Code:
fastboot flash recovery path/to/recovery-twrp-shooter-1.0.1.img
What's Fastboot?!
Check here for further information on fastboot and how to obtain it: http://forum.xda-developers.com/showthread.php?t=895545. Thanks to zephiK for directing me to it.
Moar winning...
Sweet. Trying on 4g now
snandlal said:
Sweet. Trying on 4g now
Click to expand...
Click to collapse
This is for the Nexus S, not the 4G. We are still working on making it compatible with the NS4G.
yes i know. Its in the nexus s section. Thanks for this. Seems to work great on 4g model. Can't wait for the full-blown 4g version. Great Job!
snandlal said:
yes i know. Its in the nexus s section. Thanks for this. Seems to work great on 4g model. Can't wait for the full-blown 4g version. Great Job!
Click to expand...
Click to collapse
sweet! thanks for the feedback!
screenshot please..
simms22 said:
screenshot please..
Click to expand...
Click to collapse
but of course! thanks to ffolkes for grabbing these:
{
"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"
}
shift_ said:
but of course! thanks to ffolkes for grabbing these:
Click to expand...
Click to collapse
thank you very much
Very nice to see this come out, looking forward to trying it out. Not to sound ungrateful but I have been hoping for a recovery that lets you name the backups rather than have them time stamped. Call me lazy but I flash back and forth between roms enough that keeping then straight just by the date and time is tough for an old fart like me...and yes I know rom manager can rename them for me but like I said I'm lazy...
Great work guys, thanx for your contributions to android life
Awesome guys, very smooth and much better looking than CWM recovery, a keeper indeed.
Edit: For those curious, it also works fine with the Reboot to Recovery feature build into many custom roms, such as CM7, Oxygen etc.
Thanks shift and teamwin, always good stuff.
Sent from my Nexus S 4G using XDA Premium App
Just tried it out and compared it to Clockwork Recovery. Seems a lot cleaner, definitely love how you can assign a folder for flashable .zips.
I think I'll keep this over my Clockwork Recovery 4.0.0.2 looking forward to future updates.
OK I took the plunge using the other teamwin contribution of the day(you guys rock!), the app for flashing img files like kernels and recoveries and it works fine so far on my ns4g. I especially like how I can mount usb in recovery and get at my files, never had any luck with any previous recoveries allowing it, even ones that had the option. Haven't tried all the options just yet but I am sure to find something to flash around here requiring a backup or two....let me dig around...
I too flashed it looks nice, love the options, thanks teamwin
Sent from my Nexus S 4G using XDA Premium App
raiderep said:
Very nice to see this come out, looking forward to trying it out. Not to sound ungrateful but I have been hoping for a recovery that lets you name the backups rather than have them time stamped. Call me lazy but I flash back and forth between roms enough that keeping then straight just by the date and time is tough for an old fart like me...and yes I know rom manager can rename them for me but like I said I'm lazy...
Great work guys, thanx for your contributions to android life
Click to expand...
Click to collapse
That would mean we'd have to create a software keyboard type interface which might bloat the recovery. As you said you could always use rom manager, or even mount the sdcard as a usb drive and change the folder name manually.
I knew for Shinzul my Ninzul was involved.
Uncle Jimmy says hello
AssassinsLament said:
That would mean we'd have to create a software keyboard type interface which might bloat the recovery. As you said you could always use rom manager, or even mount the sdcard as a usb drive and change the folder name manually.
Click to expand...
Click to collapse
Thats why I'm just a dreamer and not a doer lol...you guys know the limits and I guess I just don't see them...awesome work either way guys
One thing I could use some help with though, I tried to flash deck's latest and it gave me a status 7 error, just wondering if its because this isn't official for the ns4g or not...and I can report that it did a successful backup and restore for me
Avatar Rom
// RazrHD XT925
// Android 4.1.2
{
"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"
}
Attention
Always do a backup before flashing, responsibility lies with the operator of the device ultimately
General Info
Of all the open-sourceish MIUI alternatives this rom wins, It is absolutely fantastic in every regard, I love it.
General Features
-MIUI Security
-MIUI Swipe Keyboard
-MIUI Notes
-MIUI-ish Theme Manager (accessed through CMs themes, requires internet connection to DL and first-time boot)
-MIUI Weather (US only)
-MIUI Status Bar
-MIUI Framework themes
-MIUI Calculator
-MIUI Music
Known Annoyances
- Unknown
- Stock Camera may spout USB related BS, try a 3rd party one
- USB mounting is currently borked but maybe not, some people have no issue with it some do.
Instructions
Do a full wipe and install via the usual method in CWM or touch recovery, whichever you use
Download
3/12/13: AvatarRom
Big thanks to
Specifically every person here that does source work
Waiting patiently for download link
Nice
LG G2X
A few things about this rom, firstly this is a port from a Samsung device, thus it features control panel options not normally found in some CM roms, you MAY need to go to the app store if this has no on-screen navigation buttons.
I have added MIUI apps not normally found to round it off as a MIUI clone, I think this is something you folks will like a lot since your CM10 base is so functional to begin with. : D
To get themes, go to themes in settings like you normally would, It's been replaced with a fully working clone of the MIUI theme manager which can apply themes, and can browse themes online.
you XT925 folks are going to have to inform me of the working status of this in order for progress to happen, if any is needed.
So are the same things that are wrong with CM 10 affecting this ROM too? (i.e. Bluetooth music)?
Have any rogers users tried it yet? does LTE work?
Doesnt work. I used cwm, but stuck in a bootloop
Sent from my XT925 using xda premium
mapleleafz06 said:
Doesnt work. I used cwm, but stuck in a bootloop
Sent from my XT925 using xda premium
Click to expand...
Click to collapse
The same for me. Boot loop every time. I even formatted /system. Erased /data and /cache. Nothing works.
It seems to work, as you can see the start up welcome screen, but before you have a chance to click on the "next" button, the system reboots.
It's an issue with the base, I will upload a working one either tonite or tomorrow.
Ok, for the next revision of this I will need a dedicated tester to confirm the working order before I put a release up, please PM me with some kind of real-time contact info
WORKING BUILD COMIN' TONITE FOLKS. ;o
Working build has arrived!
Can anyone confirm the status of the USB?
Tquetski said:
Can anyone confirm the status of the USB?
Click to expand...
Click to collapse
I can confirm it. I cannot restore my backups because the system cant find an SD. I can write to the internal and external SDs using the built in file manager, but for some strange reason, I cannot write to them using ROM Toolbox, nor any other program. also, for the same reason, I cannot download the Gapps file listed on the update part of the settings.
Thank you for your hard work.
estuardo4 said:
I can confirm it. I cannot restore my backups because the system cant find an SD. I can write to the internal and external SDs using the built in file manager, but for some strange reason, I cannot write to them using ROM Toolbox, nor any other program. also, for the same reason, I cannot download the Gapps file listed on the update part of the settings.
Thank you for your hard work.
Click to expand...
Click to collapse
Don't mess around with any OTA updates or it could mess up your phone; anyway I'm not sure exactly why this is happening, I am going to send a PM to another porter of this rom who is used to Moto Devices and see what they have to say!
Tquetski said:
Can anyone confirm the status of the USB?
Click to expand...
Click to collapse
Thanks for Rom!
Usb works for camera mode (used IP Webcam to stream), but does crash for media, get android.process.media stopped...
Good job man
Sliced by my Razr HD on Tapatalk
Hello Tquetski. Any progress on this ROM? I guess you are really busy now, but I got so frustrated because you ae so close on this one.
I hope you have the time to continue working on this and future ROMs. Your continue support on porting for this phone is really appreciated.
Appreciate it as well. Also same USB problem as previous post about it. Same crash with media but when plugging in the cable or trying to use the gapps I used. Installed twice. First time the crash wouldn't allow adb, second time was with gapps from 20121130 and still crash on cable but adb works. Play store crashes with same media related file but youtube works. Perhaps youtube was already part of the rom....
Am uninstalling for now but can come back to it to test (Not a lot of time of the day for it though, but as much as I can) if you need it.
Also, don't know if it matters but I noticed that symlinks in the ROM don't work as expected, for example sdcard and /mnt/sdcard just return sdcard and /mnt/sdcard when typing ls. putting a trailing slash works, for example /sdcard/
I've noticed some apps rely on /mnt when they look for things.
update from above. Installed gapps from cm site and that went better and the store works. Titanium backups were on external drive and restored fine, as you'de expect. Titanium backup states, upon launch, Media Storage: not mounted but also then displays the correct amount of available storage for it.
So for example it says:
-----------------------------------
Root Acces: ok
Hypershell: yes
...
Media Storage: Not mounted
Backup Directory: /storage/sdcard1/Titanium
Then at the bottom
System Rom: 1.53 gb (1.09 GB Free)
Internal: *looks like the correct amount*
Media: *looks like the correct amount*
Ext. Sd Card: *looks like the correct amount*
-------------------------------------
Internal and Media in the above part are slightly differant than what df at the terminal says but not by much so it seems that Titanium certainly sees the space there in the second part but doesn't see it as the space its supposed to use.
I hope you can fix it. Thanks for getting this far.
One last edit; stock rom behaves the same way with symlinks.
File permissions of mounted internal sd card look the same, from memory, so its not something so simple overlooked at that level.
Happy to have been of no help
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Samsung Galaxy Tab 3 7.0
- SM-T210 WiFi (lt02wifi)
- SM-T211 3G (lt023g)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
credits to @gr8nole and @ketut.kumajaya
Omg thank you so much and for @gr8nole and @ketut.kumajaya for helping
Sent from my SM-T210(R)ocketTab 3.1 $up€[email protected]$T
Thank you so much phil
Sent from my GT-I9105P using xda app-developers app
Phil3759 said:
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
credits to @gr8nole and @ketut.kumajaya
Click to expand...
Click to collapse
Thank you very much for making this for us.
I flashed it and noticed that the external sd does not mount and we can not use it. I repacked your version with my fstab and external sd works correctly.
gr8nole said:
Thank you very much for making this for us.
I flashed it and noticed that the external sd does mount and we can not use it. I repacked your version with my fstab and external sd works correctly.
Click to expand...
Click to collapse
it seems your device tree is lacking needed vold code
gr8nole said:
Thank you very much for making this for us.
I flashed it and noticed that the external sd does mount and we can not use it. I repacked your version with my fstab and external sd works correctly.
Click to expand...
Click to collapse
I am reverting the fstab changes as a quick fix
Also, does mount usb storage work?
Phil3759 said:
I am reverting the fstab changes as a quick fix
Also, does mount usb storage work?
Click to expand...
Click to collapse
We have never had working usb storage in recovery on this device.
I will look into what is needed for the vold.
Thank you again.
Sent from my SCH-I605
gr8nole said:
We have never had working usb storage in recovery on this device.
I will look into what is needed for the vold.
Thank you again.
Sent from my SCH-I605
Click to expand...
Click to collapse
ok
I re-uploaded to goo.im with your recovery.fstab
However, it could be a few advanced functions won't work properly as I am not sure I implemented external_sd support properly everywhere
Phil3759 said:
ok
I re-uploaded to goo.im with your recovery.fstab
However, it could be a few advanced functions won't work properly as I am not sure I implemented external_sd support properly everywhere
Click to expand...
Click to collapse
Thank you, it seems to be working correctly now.
Does this background look correct?
{
"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 SCH-I605
gr8nole said:
Thank you, it seems to be working correctly now.
Does this background look correct?
View attachment 2587308
Sent from my SCH-I605
Click to expand...
Click to collapse
sure no
I used a portrait background
Seems I need a landscape
You really prefer it flipped?
You'll get more menus in portrait
Phil3759 said:
sure no
I used a portrait background
Seems I need a landscape
You really prefer it flipped?
You'll get more menus in portrait
Click to expand...
Click to collapse
All of our recoveries are in landscape. I believe the 7 in version of the Tab 2 is the same way. I do believe it works best this way.
Sent from my SCH-I605
gr8nole said:
All of our recoveries are in landscape. I believe the 7 in version of the Tab 2 is the same way. I do believe it works best this way.
Sent from my SCH-I605
Click to expand...
Click to collapse
Ok, will fix background
Uploaading 6.16.2 with fixed background
Do you need an odin version? Dow you have a download or bootloader mode?
Phil3759 said:
Uploaading 6.16.2 with fixed background
Do you need an odin version? Dow you have a download or bootloader mode?
Click to expand...
Click to collapse
6.16.2 looks much better, thank you.
We do have download mode, so an Odin version would be great.
On a side note, the Reboot to Download option does work.
I don't know how you keep up with so many different devices, but you do a great job.
Sent from my SCH-I605
gr8nole said:
6.16.2 looks much better, thank you.
We do have download mode, so an Odin version would be great.
On a side note, the Reboot to Download option does work.
I don't know how you keep up with so many different devices, but you do a great job.
Sent from my SCH-I605
Click to expand...
Click to collapse
I keep up thanks to people like you, porting their devices trees
:good:
I use scripts to build recoveries and repack them
Compiling, repacking and creating zip + tar files classified in upload path for one or 130 devices is just one command line,
Adding a tar release is just:
Code:
TAR_MD5_FLASH="yes"
However, it is still a huge impressive job mainly to port device trees, kernel sources, bugs...
the scripts must be maintained too, all the time
Hopefully I will soon be able to only focus on recovery sources and selected devices while devs can build full version at their will
Uploaded tar.md5
Let me know when you fix your device tree
By the way, recovery doesn't need all the modules
Also, no need to specify kernel sources and use TARGET_PREBUILT_KERNEL flag
Hope you can fix the vold soon too
Use my minivold binary to have exfat support through kernel modules if you compile it again
Phil3759 said:
Uploaded tar.md5
Let me know when you fix your device tree
By the way, recovery doesn't need all the modules
Also, no need to specify kernel sources and use TARGET_PREBUILT_KERNEL flag
Hope you can fix the vold soon too
Use my minivold binary to have exfat support through kernel modules if you compile it again
Click to expand...
Click to collapse
I have updated my device source on github to fix vold and kernel. https://github.com/gr8nole/android_device_samsung_lt02wifi
The external sd card is listed as /storage/extSdCard in the device vold.fstab, so I used that and it works. No extra.fstab needed.
I also updated the fstab to use the "by name" convention for all other mount points. The usb devices will probably never work for us because the device vold.fstab refers to mount points in "omap" directories which we do not even have.
I commented out the portions pertaining to prebuilt kernel, so it compiles (and uses) the kernel from source now.
I did compile a non-touch version this morning with these changes and everything seems to work great.
Thank you.
gr8nole said:
I have updated my device source on github to fix vold and kernel. https://github.com/gr8nole/android_device_samsung_lt02wifi
The external sd card is listed as /storage/extSdCard in the device vold.fstab, so I used that and it works. No extra.fstab needed.
I also updated the fstab to use the "by name" convention for all other mount points. The usb devices will probably never work for us because the device vold.fstab refers to mount points in "omap" directories which we do not even have.
I commented out the portions pertaining to prebuilt kernel, so it compiles (and uses) the kernel from source now.
I did compile a non-touch version this morning with these changes and everything seems to work great.
Thank you.
Click to expand...
Click to collapse
did you try:
/devices/platform/sdhci-pxav3.0/mmc_host/mmc1 auto auto defaults voldmanaged=extSdCardsdcard1:auto
Click to expand...
Click to collapse
extra.fstab is to add blk_device2 support, that is ability to format external storage to ext2/ext3 and to partition it
Also, it makes it possible to better get partition size for some devices
Phil3759 said:
did you try:
extra.fstab is to add blk_device2 support, that is ability to format external storage to ext2/ext3 and to partition it
Also, it makes it possible to better get partition size for some devices
Click to expand...
Click to collapse
It does work with "sdcard1" as well. I chose to leave it as extSdCard because that is how it is named in our stock roms. Please use whichever works best for you.
Thanks for the info about the extra.fstab. :good:
gr8nole said:
It does work with "sdcard1" as well. I chose to leave it as extSdCard because that is how it is named in our stock roms. Please use whichever works best for you.
Thanks for the info about the extra.fstab. :good:
Click to expand...
Click to collapse
recovery should use sdcard1 to avoid potential issues due to mal-formatted install scripts
That's the new CWM convention
I will go with sdcard1
Thank you again
Probably because you did not use auto as mount point then