Database Users

DualRomX2 = 4 roms on emmc(V6) 6-9-11

For those with phones other then Incredible...The new app that will replace this system and work with multiple phones is in the market. Check out my sig for our website with more info.
Does not work with CWM2.5...Tested with CWM 3.0.8 ONLY WILL NOT WORK WITH OTHER RECOVERIES
A super big thanks to xda dev drellisdee since he's the one who showed me how to mount the img's at boot time. Check out his modified recovery here http://forum.xda-developers.com/showthread.php?t=758874
Thanks also too:
Team ADX-I used my personal account to post since it has the dev privaliges but consider this a Team ADX endeavor.
Thanks to DHowett for furthering the idea of what we can do with the dualbooting
Thanks to UnCorrupted for giving me the original interest in Dual Booting roms long, long ago!!
Thanks to VZW for taking so much of my paycheck everymonth!!
Thanks to all who tested and gave feedback on my original DualRom project and to all who will do the same with this one.
Thanks to all the Dev's that give us a reason to want to use more then 1 rom.
DRX2 is an upgrade from DualRom. You can fit up to 4 roms on emmc(and one on the phone if you want) It uses the phone as an installer. I decided to go towards DHowetts idea of mounting img files on the emmc. Emmc will stay as fat32 the way it comes on the phone. This system is fairly simple and so far has worked with all rom's tested.
Tested with:
MIUI
CM7
SkyRaider 4.0
GingerSense Remix-B1-INC
Uber-z_RC3-1
Nil's Busines Sense
Leaked GB rom
WarmZ
uber kingdom sense 3.0 (1.0.1)
mikmik's beta 3 (sense 2.1 w/ 3.0 additions)
Incubus's Stock 2.0
mytouch 4g doubleshot rom
stock kingdom 3.0 rom
Post what rom's you boot successfully so they can be added to the list!!!
As you can see that's a good variety and it should work with every rom.
Does not work with CWM2.5...Tested with CWM 3+ Might work with other recoveries.
Installation
Installation is simple. The roms will be stored on emmc in folders labeled rom1, rom2, rom3 and rom4. each folder will need a system.img, data.img and cache.img. You can flash createimageforrom1.zip to setup the folder and img's for rom1 and the the same for the other roms up to rom4. The zip's i included create a 270mb system.img, a 1000mb data.img and a 120mb cache.img. If you would rather manually create these and make your own sizes do:
adb shell
cd emmc
mkdir rom1 (or rom2, rom3, rom4)
cd rom1
dd if=/dev/zero of=system.img bs=1M count=270
dd if=/dev/zero of=data.img bs=1M count=1000
dd if=/dev/zero of=cache.img bs=1M count=120
NOTE: Some rom's the dd command acts differently and your img may come out really small. If that's the case just add busybox to the beginning of the dd command.
the last number on the last three commands is the size of the image it will make. These take a while to make. If you use the zips i included expect to wait at least ten minutes for the img's to be built. Once they are built on the emmc you can flash different rom's to them without deleting/recreating them so you should only need to do this step once.
Once you have the img's setup choose your rom and your kernel or any other ad on's that you want installed. Flash the rom as normal(wipe phone, install zip from sd) NOTE: this will obviously overwrite your existing installation so if you want to keep that you will need to make a nand to restore when you are done. Next flash any ad on's or kernel zips you want installed as normal. Then just flash the zip for rom1installer that i've included. You can use rom1installer or rom2installer, etc to pick which slot you want the rom installed to. They don't have to be installed in any order. You can use just rom4 if you want just make sure you have setup the img's for the rominstaller zip you use. The installer zip will take 5 to 8 minutes to install so be patient. After that reboot your phone and it will boot to the rom you just installed. You can then use the DRX2 app to boot between all installed roms. If you restore your nand to your phone or install another rom to the actuall phone then run the phoneinstaller.zip to set that rom up to use the DRX2 app as well. So to recap and make it simple:
Does not work with CWM2.5...Tested with CWM 3+ Might work with other recoveries.
1. flash createimageforrom1.zip(or rom2, rom3, rom4) or all of them if you want lots of roms(you only need to do this if the img's are not already on your emmc)
2. flash your rom of choice and any add on's you want. (rember to wipe phone first and backup if nescasary) If you want to move the rom your currently have installed on your phone to one of the rom slots on emmc just skip this step.
3. flash rom1installer.zip (or rom2, rom3, rom4) whichever slot you want it installed too.
4. reboot
5. If you are also going to use a rom on your phone normally then flash or restore a nand of the rom you are keeping on phone. Then flash phoneInstaller.zip. This will install the DRX2 app and copy your phone rom's boot.img to emmc so the app can access it when you want to boot back to the phone rom.
Upgrading roms
rom1upgrader.zip(and rom2,rom3,rom4) can be used to upgrade your rom on emmc. These haven't been well tested. I did test with miui and a GB Sense 2.1/3.0 rom. Using these would be considered doing a no wipe update. If you want to wipe use the rom1installer.zip's. Step are as follows:
1. Wipe phone flash update and any add-on's
2. flash rom1upgrader.zip(or rom2,rom3,rom4) Make sure you flash the one where the rom your upgrading is installed
3. Reboot.
These could also be used if you want to flash add-ons. Flash the rom you currently have installed, flash the add-on, then flash the rom1upgrader. Example:
I have cm7 nightly 90 on slot1
I wipe phone, flash cm7 nightly 90 to phone, flash any add-on's i had flashed previously, flash any new add-on's, flash rom1upgrader.zip
Note: There is definitely a possiblity of typo's in one of the many scripts i had to write for this stuff so if you do have a problem that you post about please post which slot you have the rom installed too. Thanks.
DRX2 app
{
"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"
}
DRX2 works similar to DRSettings app. Push the button of the rom you want to boot too!!! simple enough right? Push menu for options to set the names of the rom's you have installed. If you set a name for Rom1 while booted in Rom1 the name will show when you boot to rom2, 3, or 4 so you only have to set the names once. There is also an option under menu to mount or umount emmc to pc. I added this because the one downfall of this system is the emmc does not mount to pc when using the mount disk drive options normally. Remember don't delete or move the img's of the rom your booted too.
Additional Scripts
bootRom1.zip, bootRom2.zip, etc...these zips are for the off chance you get stuck in recovery(i.e boot.img did not flash correctly) This shouldn't happen but I like to be safe especially if your not near a pc to fix it. You can flash these zip to boot into any of the 4 roms you have installed from recovery. Of course they will only work if you have a rom installed in the slot you are trying to boot too.
Downloads
Disclaimer-FLASH AT YOUR OWN RISK. You are responsible for what you do to your phone.
All the files you need are in 1 small package!!
V2 Changelog
DRX2 app installed to data/app instead of system/app so that GB sense rom's install it
V3 Changelog
Fixed app's not installing that i broke in v2
V4 Changelog
Fix for AOSP rom's not mounting as ext3(They should work ok as ext2 so if you already have it installed I wouldn't rush to change it. If you start to experience any data corruption then you can update those roms. These won't really affect the sense based rom's as they were already mounting as ext3.)
MultirominstallersV4.zip --old
V5 Changelog
Added a 5 second sleep on boot to give time for phone to mount the partition.
MultiromInstallersV5.zip --old
V6 Changelog
Added upgrader's in with the main package
Switched to ext2 for system.img and added ext2 datadata.img for lag improvements
Note: V6 Requires you to reflash the createimgforrom.zips because of the changes in the setup of the img's.
MultiromV6.zips --latest
Zip's to switch rom's in recovery--Now inclueds boot phone rom zip(I.E. boot-rom1.zip)
AnyKernelUpdater.zip's for DRX2 courtesy of tiny4579
tiny4579 made up some nice zips to replace the kernel on the emmc rom's. You don't even need to be booted into the rom you want to update the kernel on. Take the zImage from kernel/zImage and the files from system/libs/ in the kernel.zip that you downloaded and drop them in the same folders in these zips. These directions probably suck so if I confused you just ask!!!!
Rom1KernelUpdater
Rom2KernelUpdater
Rom3KernelUpdater
Rom4KernelUpdater
Nothing better then user contributions to a project like this so if you come up with something you'd like to share let me know!!!
Upgraders
Upgrader's now bundled in with the main package
Note: Unzip the multirom.zips to get to the flashable zips.
Does not work with CWM2.5...Tested with CWM 3+ Might work with other recoveries.
UnInstalling DRX2
If you want to install a new rom to a slot already in use then just follow the instructions I gave above. The scripts will wipe the img files at install.
If you want to completely uninstall the system just delete the folders off your emmc storage!!
Make sure your booted into a rom installed normally on the phone first!!
Additional thoughts
If the rom does not boot try installing and booting it on the regular phone first.
Any time your copying data from one place to another corruption can occur. If it doesn't work try it a second time. If you have to try again make sure to wipe the phone and reinstall the rom before re-running the installer scripts.
Install all add-on's, new kernels, flashable themes before running the installer script.
You can run the rom on the phone as normal, set it up, try it out and then move it to the emmc slots at any time by running an installer script. It will copy your data over also. In the case that you might want to check the rom out or see how a flashable them looks before installing it to one of the emmc slots.
If you have questions feel free to ask.

Nice Work im going to try it out

This looks awesome..... ! Now can keep up with all of JoelZ9614's Rom's... lol

has this been tested with sense 3.0 because it seems like .img's are too small

justjayhere said:
This looks awesome..... ! Now can keep up with all of JoelZ9614's Rom's... lol
Click to expand...
Click to collapse
lmao i bet i will have more than 4 roms

werdna87 said:
has this been tested with sense 3.0 because it seems like .img's are too small
Click to expand...
Click to collapse
I tested with gingersense remix which is sense2.1/3.0 i believe. The system.img i put was 270mb's which is larger then what's on the phone so if it fit's on the phone it will fit on this. That being said you can make the img's whatever size you want but the current install process requires that they be installed to the phone first so you will still have that size restriction.
Edit: If someone wanted to make a rom that was bigger then the phones normal partitions they could just package it in the img and just drop it onto the emmc. If any dev's have a rom that's too large for the phone and want to go that route they can contact me and I can help them make the boot.img for it. My goal was just to make install as universal and simple as possible.

Conap said:
I tested with gingersense remix which is sense2.1/3.0 i believe. The system.img i put was 270mb's which is larger then what's on the phone so if it fit's on the phone it will fit on this. That being said you can make the img's whatever size you want but the current install process requires that they be installed to the phone first so you will still have that size restriction.
Edit: If someone wanted to make a rom that was bigger then the phones normal partitions they could just package it in the img and just drop it onto the emmc. If any dev's have a rom that's too large for the phone and want to go that route they can contact me and I can help them make the boot.img for it. My goal was just to make install as universal and simple as possible.
Click to expand...
Click to collapse
ill definitely be pming you

JoelZ9614 said:
lmao i bet i will have more than 4 roms
Click to expand...
Click to collapse
I'm sure you will!
Sent from my Incredible using XDA Premium App

Fine job sir, fine job!

So does this still essentially use up all the EMMC so it's not usable for anything else? or does it only use up what it needs?

Coupled of questions.. sorry if I missed the answers to these questions:
*Does this erase the EMMC, or just adds the necessary "slots"?
*Does this erase your current Rom.. just trying to wrap my head around this...

todd3835 said:
So does this still essentially use up all the EMMC so it's not usable for anything else? or does it only use up what it needs?
Click to expand...
Click to collapse
Good questions...not this only uses what you put on it. With all 4 rom's installed you will only have about 500mb's left though. but you could install just 1 or 2 rom's and still have a couple gb's left to use. The only "problem" i've seen is that the emmc does not mount to pc correctly but this can be fixed by using the mount emmc options in the app i provided.
justjayhere said:
Coupled of questions.. sorry if I missed the answers to these questions:
*Does this erase the EMMC, or just adds the necessary "slots"?
*Does this erase your current Rom.. just trying to wrap my head around this...
Click to expand...
Click to collapse
No does not erase anything on the emmc...just add's the folders and img's
The rom's do get installed to the phone like a normal install and then are copied into the img's. This is so the different rom's with different updater scripts will all install correctly and then just get moved to the img's. It will erase your current rom but you could either nand the current rom(which you should do anyway) and then restore it or you could just use the rom1instaler.zip (or rom2,rom3,rom4) to move your current rom to the emmc. It will copy all of your data and stuff over too. Then you can continue to install the other roms you want. Then if you want to put a rom back on the phone normally you can do that too.

Okay... one more question: let's say I have a Rom installed in one of the slots and I want to flash a mod to that particular Rom... how is that achieved?

Conap said:
Good questions...not this only uses what you put on it. With all 4 rom's installed you will only have about 500mb's left though. but you could install just 1 or 2 rom's and still have a couple gb's left to use. The only "problem" i've seen is that the emmc does not mount to pc correctly but this can be fixed by using the mount emmc options in the app i provided.
Click to expand...
Click to collapse
Ok, so how much space does each "slot" take, just out of curiosity?
Conap said:
No does not erase anything on the emmc...just add's the folders and img's
The rom's do get installed to the phone like a normal install and then are copied into the img's. This is so the different rom's with different updater scripts will all install correctly and then just get moved to the img's. It will erase your current rom but you could either nand the current rom(which you should do anyway) and then restore it or you could just use the rom1instaler.zip (or rom2,rom3,rom4) to move your current rom to the emmc. It will copy all of your data and stuff over too. Then you can continue to install the other roms you want. Then if you want to put a rom back on the phone normally you can do that too.
Click to expand...
Click to collapse
So basically you could get a rom all customized, then do the rom#installer.zip to take it completely themed and all and move to EMMC? That sounds pretty damn hot IMHO =]

so technically can we have 5 roms?
4 on emmc and 1 on actually phone?
*and to resotre nand backup to phone do we install the phoneinstaller.zip first or after the nand backup/rom we like?

justjayhere said:
Okay... one more question: let's say I have a Rom installed in one of the slots and I want to flash a mod to that particular Rom... how is that achieved?
Click to expand...
Click to collapse
Right now flash all your mods before moving the rom...i'll work on some way to flash it after it's moved.
todd3835 said:
Ok, so how much space does each "slot" take, just out of curiosity?
So basically you could get a rom all customized, then do the rom#installer.zip to take it completely themed and all and move to EMMC? That sounds pretty damn hot IMHO =]
Click to expand...
Click to collapse
data is 1000mb system is 270 cache is 120 so about 1.5Gb...they are adjustable if you really want to save the space. and yes you can customize it and then move it.
Pithism said:
so technically can we have 5 roms?
4 on emmc and 1 on actually phone?
*and to resotre nand backup to phone do we install the phoneinstaller.zip first or after the nand backup/rom we like?
Click to expand...
Click to collapse
yep 5 roms total....install phoneinstaller.zip after restoring the nand. It just dumps the boot.img so it's available to the app and installs the app so it doesn't really do anything to the rom.

So what is the "phoneinstaller.zip" used for? Do I need To install that before moving to slot. . Or only For rom left on phone.
Sent from my SmartQ V7 using XDA App

Conap said:
yep 5 roms total....install phoneinstaller.zip after restoring the nand. It just dumps the boot.img so it's available to the app and installs the app so it doesn't really do anything to the rom.
Click to expand...
Click to collapse
wow this is awesome, one of the reason why i just recently purchased a friends INC.
Cant wait to see what other roms work on this
and do we need to use that modified recovery or is cwm 3.0.0.x good enough?

Conap, sick work
You've been busy since I first met you
Sent from my Transformer TF101 using XDA Premium App

justjayhere said:
So what is the "phoneinstaller.zip" used for? Do I need To install that before moving to slot. . Or only For rom left on phone.
Sent from my SmartQ V7 using XDA App
Click to expand...
Click to collapse
That's only need for the rom left on the phone
Pithism said:
wow this is awesome, one of the reason why i just recently purchased a friends INC.
Cant wait to see what other roms work on this
and do we need to use that modified recovery or is cwm 3.0.0.x good enough?
Click to expand...
Click to collapse
CWM recovery is fine...it's what I tested with...

[ROM]We're Back! [01/17/12] 3.2.1 Honeylicious Flash Glass HC Stock Based Kernel

Honeylicious 3.2.1 Flash Glass​
Now that the Holidays are over, and worked has slowed down somewhat, I have more time to spend with the thread.
Honeylicious was created for myself, by myself so I wouldn't have to rely on someone else's work.
I got sick of the "stick figure UI" that Google continues to produce, so what you'll see here is something more aesthetically pleasing to the eye. "Beauty is in the eye of the beholder", so if it doesn't please you, you can download
The UI has had a "glass" filter applied through Photoshop to give it a "glassy" finish.
You won't see any custom kernels here, nor revision updates, as these are all tried, tested, and true final releases.
What you will find is one of the fastest, smoothest, most dependable, and stable stock kernel based ROMs out anywhere for the Acer Iconia A500.!
Please read the "Install Instructions" carefully, and/or watch the Video Tutorial on how to flash correctly.
The 3.2.1 Youtube Fix is included in this Rom thanks to Civato.
Special thanks to Civato @ XDA for all his help in getting the camera working properly with this ROM, for the original apks he had given me, which have been changed immensely since that time, although there are a few png files that still remain the same, and all the other help and inspiration he has provided.
When you purchase a new automobile, it doesn't come with free driving lessons, neither does Android, and this ROM doesn't either. There are a few things you'll need to know before flashing a ROM.
If you're unsure of what you need to do, or simply can't follow the explicit directions in the "Install Instructions" (video included), take this link first to get you started. Click Here for the wealth of information in the A500 Wiki.
If you've previously flashed another one of Thor's ROMs with his custom kernel that he refuses to release the source code for, you may have problems flashing other ROMs until you COMPLETELY WIPE AND FORMAT YOUR SDCard. My personal opinion on this matter is, "if you have nothing to hide, then why are you hiding it?"
DO NOT USE ANY MODS FROM ANY OTHER VERSION OF HONEYLICIOUS AS YOU WILL BE MODIFYING YOUR SYSTEMUI.APK, AND FRAMEWORK-RES.APK WITH AN INCORRECT VERSION AND YOU WILL HAVE PROBLEMS!
Now, onto the ROM:
It's built on Stock PB G100W 4.010.05_COM_GEN1 found HERE: Stock base (stock kernel), Honeylicious sweet, rooted, tweaked for speed and stability, superuser and Busybox installed, and Bootloader.blob removed, that you've come to know for it's rock solid dependability, stability, and the most speed you can eek out of a stock based ROM, with an Icey Glass Finish!
What Works:
EVERYTHING!
What Doesn't Work:
NOTHING!
This ROM has had all of the useless stock apps that are constantly in "Running Services" ripped out, to give extra battery life, as well as speed. You'll notice in the "Running Apps Settings" screen shot that only two other apps are running (besides "Settings", and "Screen Shot It" which were needed to take the screen shot).
Apps Ripped Out:
Game Loft
Link to Facebook
Music
Nemo Player
Social Jogger
Sound Hound
Zineo
Replace Ripped out Glass App Pack HERE:All apps in one zip file (unzip main file to find individual apps in their own CWM Flashable zip files). So you can add in whatever you like to slow your system down once again.
What Extra Apps are included:
System Apps Added
Polaris Office
Extra Data Apps Added: (you may uninstall through "Settings", "Applications", "Manage Applications").
Avast Android Mobile Security (you need to open it once in applications to setup your preferences for it to run)
SDRescan
AdFree
HD File Explorer
HD BackGammon
HD Solitaire
HD Spades
Bluetooth File Transfer
Dolphin HD Browser
Fancy Widgets (free version)
Shake Calculator
Adobe Flash 11.1
Google Voice
Fancy Widgets has a battery meter included in the Weather/Clock widget. Go into Fancy Widget settings, "clock settings", "extra information", and tick "show battery level" for 1% increment battery levels. Fancy Widgets is the Weather/Clock widget shown in the screen shots, both weather and clock are "MIUI Inspired" style selected in "appearance" settings.
What's Different:
Ice Blue Glass Themed Rom
Five Extra Ice Blue Themed Wallpapers located in the stock Google Wallpapers.
Five Extra Themed Wallpapers located in the stock Google Wallpapers.
ICS Fonts
ICS Clocks
GPS Tweaks have been added to ensure rapid GPS Lock!
Latest Version of Superuser, and binaries.
All the goodness that 3.2.1 brings with it including the Newest Market. As you can see from the running applications Screen Shot there are only two running apps (aside from "settings", and "ScreenShotIt" which needed to be running to take the screen shot.
If you choose not to follow the explicit Install Instructions, not only do you do so at your own risk, I don't want to hear any whining about ANYTHING not working correctly, and post your questions HERE!
This ROM has been tested EXTENSIVELY with absolutely no problems or glitches whatsoever (hence "final release").
Normal disclaimer about how flashing a rom can be dangerous for your Tablet, blah, blah, blah. Please always perform a backup before flashing this ROM. If you some how screw the pooch, consider it "Pilot Error", and I am not responsible.
If you want to flash another kernel with this ROM, you do so at your own risk. I have no idea who's kernel will work with this ROM. If you do choose to flash a custom kernel with this ROM, please direct all questions regarding problems you are experiencing in the thread that you got your kernel from, as they will not be answered here.
If you are having problems with certain apps, remember this is a Stock Based Rom, so please direct your questions regarding said app to the developer of the app.
I took much of my own time and effort building this ROM, typing up instructions, and creating the install video. If you ask a question in this thread that has OBVIOUSLY already been answered in this OP, the only reply you will receive from me is this:
"See Original Post ".
Home Screen:
{
"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"
}
Apps Screen:
Location Settings Screen:
Running Apps Settings Screen:
Wallpaper Settings Screen:
Dolphin HD Browser Screen:
INSTALL INSTRUCTIONS:
CWM
Wipe Menu:
Wipe cache
Wipe Data (Factory Reset)
Wipe Dalvik Cache
Wipe Battery Stats
Mounts and Storage Menu:
Format System
Format Data
Format Cache
Format Flexrom
Install From Zip File
Choose File From SD Card
Locate "name_of_rom_to_be_flashed_here.zip " on your SD Card and click power button
Highlight "Yes - Install name_of_rom_to_be_flashed_here.zip" and click power button.
YOU WILL GET A RANDOM OFFSET MESSAGE DURING INSTALL. THIS IS NORMAL!
When install is finished, it will tell you so. Return to main CWM menu, and choose "Reboot System" and click power button.
Allow your Tab to continue the setup while guiding you through the prompts that will require user input.
Superuser has latest apk and binaries already installed on Icy Faux 3.2.1.
Install Instruction Video: (video was created before I was made aware that the version of CWM used in this Video has Thor's GPL non-compliant kernel in it). I have since reflashed drellisdee's GPL compliant forked Amon Ra touch screen recovery version 3.14 found HERE: Also added to attachments in this post.
DO NOT INSTALL THIS NEW RECOVERY IF YOU ARE NOT FAMILIAR WITH THE PROCESSES INVOLVED WITH FLASHING A ROM! THIS RECOVERY IS NOT FOR BEGINNERS. STAY WITH CWM!
Install Instruction Video
For those of you experiencing what you believe is low quailty WIFI with HC 3.2.1, watch this video with no wifi signal bars whatsoever! (Honeylicious 3.2.1 Flash Glass with no WiFi Patch)
(please excuse the sound of me clomping down the hall in my untied winter boots lol)

Reserved #3

@kjy2010 - First class job of presentation. I refuse to believe that anybody can screw up flashing your ROM after your ultra clear directions. I'm currently running Kekinash's 3.2 near stock rom but I like the look of your effort and I will flash it to my A500 as soon as I've got a spare minute. Once more thank you.

metpolds said:
@kjy2010 - First class job of presentation. I refuse to believe that anybody can screw up flashing your ROM after your ultra clear directions. I'm currently running Kekinash's 3.2 near stock rom but I like the look of your effort and I will flash it to my A500 as soon as I've got a spare minute. Once more thank you.
Click to expand...
Click to collapse
Thank you.
Post back after install, and let us know what you think!
Edit: I've seen some of your boot animations. If you'd care to create a custom animation for this ROM, I'd be more than happy to give you credit for it.

kjy2010 said:
Thank you.
Post back after install, and let us know what you think!
Edit: I've seen some of your boot animations. If you'd care to create a custom animation for this ROM, I'd be more than happy to give you credit for it.
Click to expand...
Click to collapse
You're very kind I'll give it some thought. I did just complete a small ICS anim, more for fun than anything else but you might like to look at it. I won't bother you by attaching it here but my good friend JaeKar99 has just added a preview gif of my anim to my post which is on the last page of the thread "Publish your A500 Boot Anims......." in the Themes & Apps section.

OP - Thought I'd throw this one at you, it's only a re-hash of what I did before but more specific to your rom. I have to admit that I don't have a single ounce of artistic ability in my body so what you get from me is always pretty simple and uncomplicated. I fear that it might not be "high tech" enough for your needs but worse case it costs neither of us anything and may give you some ideas.
Latest thought.....Should it be of interest to you then the "speed" and "display period" could easily be adjusted to your requirements.

ah, nice work kjy.
No problem on taking it apart and giving it your own twist.
That is why it is there for.
Don't forget it is BigDX is the one that did start this Modding,I changed an modded the ICS stuff into it so it worked on the A500.
I also got settings icones but didn't use them because I think it makes the settings menu out of balance.
If you want some stuff let me know.

3g USB
Hi all, I'm newbie with Iconia A500, I have 16gb wi-fi model, and I want to know if this rom supports 3g USB modem?
I want to know too if can I backup the original ROM before personalize my tablet for don't lose warranty and to recover them if necessary?
Thanks

Remove apps before flash
hi, kjy2010,
As you know, I'm very proud of your previous ROM, which I've flashed before. As I have Quickoffice installed, could be a problem if I remove the Polaris Office apk within the zip file (without winzipping it), before flashing this ROM?
Thanks!

alexrb said:
hi, kjy2010,
As you know, I'm very proud of your previous ROM, which I've flashed before. As I have Quickoffice installed, could be a problem if I remove the Polaris Office apk within the zip file (without winzipping it), before flashing this ROM?
Thanks!
Click to expand...
Click to collapse
This ROM has Polaris Office in it already, but you're free to do with it what you like bro! It's your's to do with as you like once you download it!

civato said:
ah, nice work kjy.
No problem on taking it apart and giving it your own twist.
That is why it is there for.
Don't forget it is BigDX is the one that did start this Modding,I changed an modded the ICS stuff into it so it worked on the A500.
I also got settings icones but didn't use them because I think it makes the settings menu out of balance.
If you want some stuff let me know.
Click to expand...
Click to collapse
Sorry bro, I keep forgetting BigDX. I modified the OP to reflect correct credit! And thanks again for the use of the APKs!

crbdigo said:
Hi all, I'm newbie with Iconia A500, I have 16gb wi-fi model, and I want to know if this rom supports 3g USB modem?
I want to know too if can I backup the original ROM before personalize my tablet for don't lose warranty and to recover them if necessary?
Thanks
Click to expand...
Click to collapse
First, you have to have root access, and CWM installed to flash a ROM. There are plenty of threads in this forum on the subject, please use the search function. They will guide you through root, CWM, and backup.
Second, some people have reported success using Civato's 3gmodem patch located in his thread.
Please take these other questions to the appropriate threads, not here

metpolds said:
OP - Thought I'd throw this one at you, it's only a re-hash of what I did before but more specific to your rom. I have to admit that I don't have a single ounce of artistic ability in my body so what you get from me is always pretty simple and uncomplicated. I fear that it might not be "high tech" enough for your needs but worse case it costs neither of us anything and may give you some ideas.
Latest thought.....Should it be of interest to you then the "speed" and "display period" could easily be adjusted to your requirements.
Click to expand...
Click to collapse
Thanks bro, I appreciate your work!
It's now posted in second post under Mods!

Fresh install after following the instructions above. The only apps i have installed from the Market are Busybox and Busybox Pro.
When I try to install Busybox it tells me 'There seems to be a problem with some of the utilities needed to install busybox'. Any suggestions anyone?

Savok said:
Fresh install after following the instructions above. The only apps i have installed from the Market are Busybox and Busybox Pro.
When I try to install Busybox it tells me 'There seems to be a problem with some of the utilities needed to install busybox'. Any suggestions anyone?
Click to expand...
Click to collapse
There are a few different versions of busybox and pro in the market, which one did you install?

Yeah I now see that STEricson's version is still broken. Ran with JRummy16 and is working correctly now.

Savok said:
Yeah I now see that STEricson's version is still broken. Ran with JRummy16 and is working correctly now.
Click to expand...
Click to collapse
Great! Thanks for the update on which one works!

kjy2010 said:
Thanks bro, I appreciate your work!
It's now posted in second post under Mods!
Click to expand...
Click to collapse
Thanks for your kind words and for your posted credit. I'm glad you could use the animation. By the way I'm not publishing this anim on my Theme thread I would rather it stayed exclusively here. Receiving a credit on your rom thread is almost like having my name up in lights in Holywood...lol

alexrb said:
hi, kjy2010,
As you know, I'm very proud of your previous ROM, which I've flashed before. As I have Quickoffice installed, could be a problem if I remove the Polaris Office apk within the zip file (without winzipping it), before flashing this ROM?
Thanks!
Click to expand...
Click to collapse
Oops, I misread your post, and I apologize. No problem taking out Polaris before install.

metpolds said:
Thanks for your kind words and for your posted credit. I'm glad you could use the animation. By the way I'm not publishing this anim on my Theme thread I would rather it stayed exclusively here. Receiving a credit on your rom thread is almost like having my name up in lights in Holywood...lol
Click to expand...
Click to collapse
lol Hardly the same, but thanks again for your work, and the compliment!

[REF] ★★★Understanding the Android world before rooting your LG Nexus 4★★★

[REF] ★★★Understanding the Android world before rooting your LG Nexus 4★★★
Understanding the Android world before rooting your LG Nexus 4
Here is a *noob friendly* collection of information every user that wants to root their phone should know. Many people blindly follow guides without even knowing what "Rooting" means. Hopefully, this will help new users (and old ones, why not?) understand what is happening with their phone, and what they will put up with.
This may seem as a lot to read, but there are no shortcuts. You either read and learn what you're dealing with, or find out the hard way.
Let's get started, shall we?​
What does rooting mean?
To 'root' your phone means to gain administrative rights on the file system of your phone (in linux, root is the username of the master admin, kind of being an Administrator on Windows). With root access, you can install and uninstall anything you want on the phone.
Most phones come with limited access regarding what you can and can't do on it. This isn't necessarily a bad thing, because it can keep users from accidentally breaking something they shouldn't mess with on the phone, especially in regards to the operating system. However, many manufacturers limit your rights to things that aren't really so mission critical, too, and rooting the phone gets around this.
If you have a few unnecessary applications (bloatware) pre-installed on your phone that you cannot uninstall, rooting will give you this ability. It will also allow you to upgrade to newer versions of Android before your phone's manufacturer and/or cell provider make the updates available to you.
Click to expand...
Click to collapse
So now you know what rooting means. And I bet you are now thinking "Should I do it, or not?" Well, hope this helps you decide:
The advantages of rooting
-De-bloat your phone. Uninstall any unwanted system apps.
-More control over how the CPU acts. This can increase performance or battery life, depends on how you configure it.
-More control over power consumption. This implies undervolting your CPU, giving it less power, so it consumes less.
-More control over how apps start up. Prevent apps from starting up when they don't need to.
-Change your Baseband (Radio). Try different radio versions, with the purpose of reducing battery drain or improving your signal strength. This may also allow you to enable LTE, due to the fact that it's disabled on the latest radios.
-Flash custom ROMs. Bored of the stock ROM and look? Browse through the hundreds of custom ROMs provided by this community, each having different features and looks.
-Backups. The ability to completely backup your phone, and fully restoring it to the time of the backup. This is done with a Nandroid Backup (we'll talk about this later)
-Mods and Inovations. Use many mods, fixes, tweaks or features created by the community!
-Custom Kernels. As a Nexus device, the Nexus 4 has tons of kernels with different features, supporting better performance, or battery life! To see what a kernel is, keep reading.
-Run apps that need Root Permission. These apps can be very useful, like Titanium Backup, Root Explorer, Terminal Emulator and many others!
Click to expand...
Click to collapse
The disadvantages of rooting
-Rooting will void your warranty (Although reverting root is very easy)
-The process a bit dangerous. Something could (99.9% probably not, but still) go wrong, and end up bricking your phone. So, yes, the process is 0.1% risky. You can end up deleting everything on your phone. You'll have to handle this process gently and with care.
-You will be able to do a lot more mistakes. These may cause damage to your phone (But hey, that's why we have these kind of threads, eh?)
-No more over the air official updates. You'll have to update your phone manually, through your recovery. (Which isn't that hard)
Click to expand...
Click to collapse
Now that you fully know what rooting implies, let's continue exploring the Android world.
What about the internal memory? How does that work?
Now, as you might already know, each phone has an internal memory. In the Nexus 4's case, it's either 8GB or 16GB. This internal memory needs to hold a lot of things, not only your personal data. This is why you only have available to use 5.8 GB or 12.9 GB.
An Android's internal memory is partitioned into many chunks that have their separate purposes.
These are all the Nexus 4's partitions, and their names.
modem -> /dev/block/mmcblk0p1
sbl1 -> /dev/block/mmcblk0p2
sbl2 -> /dev/block/mmcblk0p3
sbl3 -> /dev/block/mmcblk0p4
tz -> /dev/block/mmcblk0p5
boot -> /dev/block/mmcblk0p6
recovery -> /dev/block/mmcblk0p7
m9kefs1 -> /dev/block/mmcblk0p8
m9kefs2 -> /dev/block/mmcblk0p9
m9kefs3 -> /dev/block/mmcblk0p10
rpm -> /dev/block/mmcblk0p11
aboot -> /dev/block/mmcblk0p12
sbl2b -> /dev/block/mmcblk0p13
sbl3b -> /dev/block/mmcblk0p14
abootb -> /dev/block/mmcblk0p15
rpmb -> /dev/block/mmcblk0p16
tzb -> /dev/block/mmcblk0p17
metadata -> /dev/block/mmcblk0p18
misc -> /dev/block/mmcblk0p19
persist -> /dev/block/mmcblk0p20
system -> /dev/block/mmcblk0p21
cache -> /dev/block/mmcblk0p22
userdata -> /dev/block/mmcblk0p23
DDR -> /dev/block/mmcblk0p24
grow -> /dev/block/mmcblk0p25
Yes, there are quite a lot. You, as a user, don't need to care about all of them. Here are the ones you will need to know about:
/system- size: about 0.5GB
This partition holds the Android OS itself. Kind of like the C:// disk on your every day Windows PC. This partition has many folders and files you cannot normally get to, due to safety reasons. For example, system/app is where all the system apps are installed.
If something gets deleted from this partition, Android will most probably won't work properly.
/data- size: either 5.8GB, or 12.9GB
This is where all your personal data is kept. This includes apps, sms, contacts, e-mails etc. It also stores your system settings, like wallpaper, and all those stuff you set up when you got your phone. The most important folders on this partition are data/app (where your apps are stored), data/data (where you app data is stored, like highscores and stuff), and data/media.
Data/media might be considered your sd-card. Yes, I know the Nexus 4 doesn't have an sd-card, but this folder works like one. When you connect your phone to your PC, this is the folder that pops up, with all your music, images, videos, and whatever else you keep on your phone.
Click to expand...
Click to collapse
Things are getting a bit more complicated, eh? Just bare with me. Next, I will be explaining the different terms you will be encountering throughout your Android experience.
Things you hear people talk about
Kernel
The kernel is an essential part of any Linux based operating system. It's the program that manages input and output requests of the operating system. Imagine you're at a restaurant. You give your order to a waiter. He takes it to the chef, the chef makes your food, then the waiter brings it back to you, and you enjoy it. In this case, you are the Android system, the waiter is the Kernel, and the chef is the hardware. The system gives the Kernel a request, like firing up another processor core when you play a heavy game, and the Kernel fulfills the request.
Here is an image for better understanding
{
"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"
}
Recovery
This is a secondary, mini operating system that has access to your internal memory. It contains a few commands that would normally help you recover your Android system in case of a failure, like factory resetting. You will see that, for rooting, you will need to install a custom recovery.
The stock recovery does not have the ability to write custom ROMs (I'll explain these later) on your internal memory. A custom recovery has this option, and many more.
Here are some images for you to fully understand:
Stock recovery:
Custom Recovery
You can see that the Custom Recovery has more options, including "Backup and Restore", Advanced, and Install zip from Sd-card.
You can get in Recovery by powering off your phone, then hold Power+Volume Down button until a black screen with colored text appears. Then, use the volume buttons to select 'Recovery", and then press the Power Button to select it.
Bootloader
The bootloader is the first thing that fires up when you open your phone. As the name says (Boot+Loader), this program loads the kernel, which when boots up the Android system.
The same bootloader can also boot in recovery, as explained above.
When you first get the phone, the bootloader is in a locked state. That means that you cannot use fastboot commands like "fastboot flash" or "fastboot boot". With other words, you cannot simply flash a custom recovery. Thankfully, Google gave us the option to unlock the bootloader very easily, and flash a custom recovery of our choice.
Custom ROMs
A custom ROM is a ZIP file that contains an altered version of the Android OS. There are many custom ROMs for the Nexus 4, made by wonderful and skilled devs for the community. You can install a Custom ROM with your Custom Recovery. Custom ROMs contain the following folders and files:
META-INF- This folder holds the installation info and data. A custom recovery does not know on it's own how to install a ROM. In this folder, there's a txt file that contains a script, with the purpose of telling the recovery what to do.
System- This folder contains the stuff that will be installed on the /system partition that we talked earlier about.
boot.img- Among others, this file contains the kernel that comes with the ROM.
Click to expand...
Click to collapse
Ok, so now, after you read all this stuff, you're probably thinking "Ok, I will never get the hang of this". Don't worry. With time, you will know all of these from reflex. And, after you got over that, and manned up again, you probably thought "Ok, let's root this damn thing!". Not quite yet. We aren't done. There are still some crucial things that you need to know. So let's continue.
How to backup your stuff
Before you do anything EVER, you'll always have to backup your stuff, even if you don't feel like it, or your dog died (in which case I'm truly sorry), but, no matter what you're about to do, always have a recent backup sitting around.
There are many ways and things you can and will probably have to backup.
1. Backup your entire phone, by creating a Nandroid Backup.
As you saw in the 'Custom Recovery" picture above, you have a "Backup and Restore" option. Here it is again:
With every occasion, it's best to use it as often as possible. It only takes about 2 minutes, but it could be a life saver.
A Nandroid will backup:
/system
/data (Except /data/media, where your "sd-card" is, because it's too large and not that important)
/cache (Yes, there is a cache partition, and it will be backed up, although not really necesarry)
kernel (The kernel will be backed up too)
***Optional tip: I always keep a recent nandroid backup on my PC, in case I somehow wipe all my phone's contents, and my backup among with them. The Nandroid backup is saved at this location, which can be accest with a root file explorer, like ES File Explorer : mnt/shell/emulated/clockworkmod/backup. If you want to copy it to your storage, just copy the latest backup, and then move it to your PC.
2. Your apps and data only
This can be very useful when changing ROMs. You just got bored of your ROM, and want to move to another one. The only way of taking your apps and data with you is by backing them up with an application like Titanium Backup. The backups will be saved in data/media, and will be restored using the same app with which you backup up on the new ROM.
3. Your SMS, Contacts, MMS etc.
These things can be backed up by special apps on the Play Store. Ok, contacts will be restored by Google Sync ( although not always done properly, that's why I still back them up), but SMS will not be restored. There are many free apps that back them up for you, nice an easily, for them to be restored in case of a ROM change or data loss.
4. Your storage (data/media, sd-card)
You just connect your phone to your PC, select all folders, and copy all over on your PC. This will be useful when you unlock the bootloader. A bootloader unlock will wipe all the stuff on your phone (This can be avoided, read guides). So keeping a copy of your sd-card contents on your PC isn't such a bad idea.
Click to expand...
Click to collapse
Now you know how to keep it safe by creating backups. I will say it again, you are never too safe! Backup when you do a modification, even if it's tiny. Now, after you've finished reading the above, you will probably attempt to root. You will use one of the guides out there ( I will link one at the end of this thread ) to install a custom recovery, and gain root access. But what to do with it? Well, you will most likely end up flashing a custom ROM.
Flashing a custom ROM
You will get bored of the stock ROM, and will decide to flash a custom ROM. But you haven't done it before, and you don't really understand the process.Before you do anything, you must:
-Make sure that the files are for your phone ! If you flash files that were made for another phone, you might end up with a brick!
-Never panic! There is always a way out! That's what backups are for!
-Read all the instructions! Every ROM thread has instructions. Read them!
{By the way, flashing = installing}
Now, let me take you through the whole flashing process. ( Use the steps in the ROM threads if instructed differently than here )
1. You will search far and wide in these forums for a custom ROM that fits your needs. Every ROM comes as a ZIP file. So when you decide on a ROM, download the zip. For copyright reasons, Google Apps (Play Store, Google Now etc) don't come included with the ROM. So you will have to download them too. They are usually linked on the ROM main thread.
Some ROMs might have addons too, so check them out, and download the ones you want.
2. You now downloaded the ROM, Google Apps, and some addons. The next step will be to put them on your sd-card. Connect your phone to your PC, and make an easy access folder, like "Root Stuffs" where you'll put all these zips.
3. Now, let the backup process begin. You first backup your apps, app data , SMS, Contacts etc., like I explained above. I recommend Titanium Backup for apps and SMS, MC Backup for contacts.
4. Now you are ready to go in recovery. Power down your phone. Then, press and hold the Power Button and the Volume Down button at the same time. You will be brought to the Bootloader Screen. Now, with the Volume Buttons, switch through the options until you find "Recovery". Then press the Power Button again.
5. Now you will be booted in your Custom Recovery. Depending on your recovery, you will have the options on your screen.
CWM Recovery:
6. You will go to the Backup and Restore menu, and select "Backup". If you made a backup before, you can select "Delete" first, and delete it, for space consumption purposes.
7. After the backup finished, you will return to the main screen. There, select 'Wipe data/ Factory Reset". This will wipe everything in /data except /media, so your sd-card will remain untouched. Don't worry, you have a Nandroid Backup!
8. After the wipe finished, you will go to "Install zip from sd-card". You'll have to navigate to the folder where you put the ROM, and select it. You'll see it will nicely install.
9. After the ROM finished installing, you will have to flash the Google Apps zip, and the mods. Install them the same way you installed the ROM itself.
10. After you have flashed everything, you can select "Reboot system now" . First boot will take longer to complete. Again, don't panic. You have a Nandoid bakcup . You will end up with the ROM booted, and you'll continue setting it up.
TWRP Recovery:
6. Go to the "Backup" menu, select "Boot", "System", and "Data", then swipe the thing on the bottom on the screen to start backing up.
7. Once you're done, use the home button to get to the main screen. Select "Wipe", and swipe the thing again to Factory Data Reset. This will wipe data, cache and dalvik cache. This will not wipe your internal storage (Music, photos, etc).
8. After the wipe finished, use the home button again to get to the main screen. From there, select the 'Install" option. You'll have to navigate to the folder where you put the ROM, and select it. Then, by using the "Add more zips" option, add the Gapps package, and and then any addons or mods, in this order. Then swipe the bottom thing to flash.
9. After you have flashed everything, you can select "Reboot" . First boot will take longer to complete. Again, don't panic. You have a Nandoid bakcup . You will end up with the ROM booted, and you'll continue setting it up.
***In case something went bad, like your phone doesn't boot for more than 10 minutes, or the animation endlessly repeats itself (Boot Loop), do the following:
11*. Hold down the Power +Volume Buttons until the phone shuts down. Then release them for a second, and immediately press them again. You will be brought to the bootloader screen. Enter recovery.
12*. In recovery, go to the "Backup and Restore" menu, and select "Restore". Then pick the backup you did earlier, and wait for it to complete. Then, select "Reboot system now", and you should be booted back in your original ROM.
Now, let's say that after you flashed a ROM, it either did not boot, or you had some bugs with it. You will go to the thread ROM to report your problem. Here's how to not post:
"This ROM doesn't work"
You will have to be a lot more specific than that. In reporting a problem, you will have to do the following:
-Say what you did (Flashing process)
-What you flashed afterwards
-What you did to reproduce the bug
-What recovery you use
-ROM Version
-even provide a logcat <This is quite advanced> (http://forum.xda-developers.com/showthread.php?t=1726238)
You have to give as many details as possible, so the developer can sort things out.
Click to expand...
Click to collapse
ADB and Fastboot
ADB (Android Debug Bridge)
The Android Debugging Bridge is kind of a toolkit, that has many commands to control your Android from your PC. This is an essential part of your Android experience. With ADB, you can do many stuff that you couldn't normally do, like backup your apps, or push and pull packages from your phone.
ADB is also used by many of the useful tools out there, like toolkits, and all sort of programs that enhance your Android experience.
With ADB, you can also Logcat. Logcatting is creating a log of everything that happens on your Android phone while it's on. This is used to find the sources of bugs.
Example of ADB Commands:
Code:
adb pull /system/app/RANDOM APP = creates a copy of a system app on your PC
adb push app /system/app = Copies an app from your PC to your system partition
adb reboot bootloader/recovery = Reboots the phone in bootloader or recovery
adb logcat = Starts a logcat
Fastboot
Fastboot is also a toolkit of commands, but a bit different from ADB. While with ADB, you can do simple actions, with fastboot, you can do major ones, like flashing a whole partition, or formatting one. Fastboot is usually the preferred method to flash a recovery. Also, Fastboot usually works with .img files.
Example of Fastboot commands:
Code:
fastboot erase boot = Erases the kernel
fastboot erase recovery = Erases the recovery
fastboot flash system system.img = Flashes the System partition with an image
fastboot flash boot boot.img = Flashes kernel
fastboot flash userdata data.img = Flashes Data partition
fastboot flash recovery recovery.img = Flashes a new recovery
fastboot reboot = Reboots the phone
To use ADB and Fastboot, you must first have ADB drivers and Fastboot drivers installed. Here is a very good guide to set up these two useful things:
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Click to expand...
Click to collapse
Tips and Tricks
1. Try to not use toolkits. (I'm not disregarding any toolkit dev. They did a wonderful job)
Due to the fact that people are lazy in nature , toolkits have been made so that users don't struggle with rooting their phone. But there are many reasons for you to not use one:
-->you won't learn anything from using a toolkit, and, if something goes wrong, a toolkit can rarely fix your problem. It's better if you rely on your own forces.
-->you put the fate of your phone in someone else's hands. If a bit of code is wrong, then your phone could get bricked.
-->you miss out all the fun. Why buy a Nexus device if you don't want to explore the depths of the Android OS?
2. Never panic
Whenever you don't know what to do, and you're stuck, don't panic. There are many people here that can help you. Don't try doing anything blindly. Search the forums, or start a thread in the Q&As section, and we will help you.
3. Read everything carefully!! (If you read this, post a cat picture in this thread)
I might have said it a couple of times throuout this post, but always read everything. Someone wrote something for a reason. Usually, if you read everything, and do what you are told, you are bound to be failproof.
Click to expand...
Click to collapse
Ok, so now you know pretty much all a normal user should know. But there are still questions that are very frequently asked that need answering. Here are some questions and answers about popular problems and misconceptions:
Questions and Misconceptions
1. My Nexus 4 is getting very hot. Hardware problem?
Nope. There are many reasons that contribute to your phone getting hot, like
-the fact that glass is a good heat conductor, and the Nexus is covered in it
-the fact that a quad core produces more heat
-etc.
Don't worry. Everything is working as it should. For example, the Ipad gets 3 times hotter than the Nexus.
2. If I am rooted, will I receive OTA updates?
Yes, and no.
You will be able to download the update by having installed the Stock ROM with stock kernel, though it will not be installed automatically, due to the fact that you have a custom recovery. You will need to install it manually.
3. My notifications are delayed. Why?
Well, it due to the fact that Android is doing too much filtering.
To fix, navigate to /system/etc/wifi, and open WCNSS_qcom_cfg.ini. Now find the line McastBcastFilter=3. Change the value to 1, like this: McastBcastFilter=1, save, and exit. Then reboot. Your notifications should not be delayed anymore.
4. The Nexus 4 audio quality is horrible. Why?
It isn't horrible. It's normal, but the max volume isn't as loud as on other devices. I have been a piano player for 12 years. I have quite a sensitive ear, and I can tell you that the audio quality on the Nexus is comparable with that of an Ipod. The only major difference is that, with the Ipod, you can go deaf with the max volume.
5. Which kernel/ ROM should I use?
Don't ever ask this question. What's good for others isn't necessarily good for you. You'll have to try the many kernels and ROMs yourself.
6. My Nexus 4 rattles when I shake it. Why? Something broken?
Nope. There's nothing broken. That rattling is caused my the camera lenses moving. Don't worry about that either.
Click to expand...
Click to collapse
This is all for now. I hope you understand what's up with this Rooting process. If you have any questions, don't be shy to ask in this thread
If there is anything to be added to this thread, please post below
Thank you for the time you allocated to reading this! You are now smarter :good:
Good day, and Happy flashing!!!
For credits, useful links and other stuff, see the posts below.​

Useful links
INDEX of Guides, Tools, Recoveries and more... (By GaboWinter)
Unlocking Bootloader without wiping data
[HOW-TO] How to flash a factory image / return to stock / unlock / root #
Ultimate Nexus 4 Root Guide​

Credits and Thanks!!
@rootSU
For providing me a template and much of the info. His original thread in the S3 forums: (http://forum.xda-developers.com/showthread.php?t=2362743)
@mskip
For providing information on memory partitions
@paxChristos
For the logcat part
@efrant
For pointing out some mistakes
My annoying cat
For continually stepping on my keyboard.​

Thanks for this awesome guide!

ngr.hd said:
Thanks go this awesome guide!
Click to expand...
Click to collapse
Thanks!! No problem. My girlfriend left me, so I have plenty of free time now

abaaaabbbb63 said:
Thanks!! No problem. My girlfriend left me, so I have plenty of free time now
Click to expand...
Click to collapse
O god Nice guide, will be helpful. One thing though:
4. Now you are ready to go in recovery. Power down your phone. Then, press and hold the Power Button and both the Up and Down Volume button at the same time. You will be brought to the Bootloader Screen. Now, with the Volume Buttons, switch through the options until you find "Recovery". Then press the Power Button again.
Click to expand...
Click to collapse
The bootloader can be accessed using just volume down and power. I never have to use both volume buttons.

chromium96 said:
The bootloader can be accessed using just volume down and power. I never have to use both volume buttons.
Click to expand...
Click to collapse
One learns new things every day...

This thread should be stickied IMO.

ohersi intriguing
this thread helped me A LOT!!!
got my Nexus yesterday, and i'm happy that such a thread exists.
@ApriliaM3
U should really consider making this a sticky

Hello!
I bought my Nexus last week, and I kept looking on the internet they can do with it. I've heard of the root, and I was curious. I also found it very interesting forum where I found this thread. Thanks for the information. Very useful.
Sorry for bad English. I used Google Translate.

i JUST realized this was here.. DOH!
THANK YOU

Nexus 4 doubts
Hii i just got a 16gb nexus 4 which is my first android phone last month and now i was thinking of rooting it and getting paranoid android on it...but just wanted to get some doubts clarified...
1. I wont be able to install ota updates when 4.3 or 5.0 android versions are released , so how will i get them ?? By Updating paranoid android ROM ??
2. In case i just root my phone and not install any custom ROMs then will i get otas ??
3. After installing a custom rom , can i revert back to the stock google thing ? I mean make my phone as it was when i first booted it.. ??
Thats all i guess..

Nice guide Andu! :thumbup:
Sent from my Nexus 4 using Tapatalk 2

simms22 said:
i JUST realized this was here.. DOH!
THANK YOU
Click to expand...
Click to collapse
No problem
gamekid94 said:
Hii i just got a 16gb nexus 4 which is my first android phone last month and now i was thinking of rooting it and getting paranoid android on it...but just wanted to get some doubts clarified...
1. I wont be able to install ota updates when 4.3 or 5.0 android versions are released , so how will i get them ?? By Updating paranoid android ROM ??
2. In case i just root my phone and not install any custom ROMs then will i get otas ??
3. After installing a custom rom , can i revert back to the stock google thing ? I mean make my phone as it was when i first booted it.. ??
Thats all i guess..
Click to expand...
Click to collapse
1. Yeah. Paranoid will most probably be updated to the latest android as soon as the source is released.
2. Yes, you will get OTAs, but you will have to install them manually.
3. Yes you can. You can either do a nandroid backup of your stock rom, and keep it, or you can flash a stock rom.
xanthrax said:
Nice guide Andu! :thumbup:
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Thanks!

Added Fastboot and ADB
If I made any mistakes, please correct me

abaaaabbbb63 said:
Added Fastboot and ADB
If I made any mistakes, please correct me
Click to expand...
Click to collapse
Ha. I was considering adb
Sent from my GT-I9300 using Tapatalk 4 Beta

rootSU said:
Ha. I was considering adb
Sent from my GT-I9300 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Nice!
I really like how you styled your thread! Looks awesome!

is there a link you'd recommend to get all google apps and any other important apps
and Thnx for the great guide, really helped me ALOT

M.Zaki said:
is there a link you'd recommend to get all google apps and any other important apps
and Thnx for the great guide, really helped me ALOT
Click to expand...
Click to collapse
Google apps are usually linked in the ROM thread.
Here are the JB 4.2.2 gapps:
http://goo.im/gapps/gapps-jb-20130301-signed.zip

Its worth noting that some roms have specific gapps packages too. Its always good to use these dedicated packages in case they have cool optimisations (eg slim with the dark mode toggles)
Sent from my GT-I9300 using Tapatalk 4 Beta

[ROM] [NIGHTLY] [JB] [4.3] CyanogenMod 10.2 nightlies

{
"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"
}
Welcome to the unofficial CyanogenMod 10.2 nightlies​
The releases will co-inside and the build start time is at 03:01 UTC every night and should be uploaded soon after. If at anytime the builds are not there, then there was a problem building the ROM, and we will have a look at it ASAP.
Buildbot resources are needed for newer builds. Please upgrade to CyanogenMod 11
http://forum.xda-developers.com/showthread.php?t=2542353
These builds are compiled from the latest CyanogenMod repos and device repos on device, kernel and vendor files and are based on the awesome work by jcsullins, Dorregaray, flintman and drmarble.
Attention: REPARTITIONING REQUIRED.
Jellybean 4.3 takes up a tad more space than 400mb. Resizing your system partition to 500mb is advised. Also, this build is a datamedia build - this means that we utilise an emulated sdcard on the data partition and both share the same partition thus space. Yet, the sdcard partition is also mounted and can be used for file usage (deprecated). Resizing the sdcard partition (/dev/media) to a rather small size and allocating the remaining size to /data is recommended.
What is datamedia? Click here.
Advised partition layout:
system - 500mb
cache - 200mb
media - 400mb
data - [remaining space] (i.e. ~11.5gb for 16gb TouchPads)
easiest way to resize partitions is by using tailor in webOS (install with preware et al)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Datamedia CWM required to properly support emulated sdcard storage in 4.3
Download
Click to expand...
Click to collapse
Click to expand...
Click to collapse
And as always: I take no responsibility whatsoever for raging, screaming, crying, frustration, failing, confusion, dead kittens, etc.
Download builds here
Click to expand...
Click to collapse
Download Google Apps
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Changes
Upstream changes
Devicetree commits
Kernel commits
Wifi driver commits
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Issues
Issuetracker
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Thanks/Credits
Click to expand...
Click to collapse
James Sullins (jcsullins) - for his awesome work on the TouchPad
Tomasz Rostanski (Dorregaray) - for his work on many parts on Android for the TouchPad (esp. camera)
David R. Marble (drmarble) - for supporting the CM10.1/CM10.2 port, many great ideas and sdcard partition mounting with the new fstab
William Bellavance (flintman) - for getting around mr2 quirks of audio and wifi, further development and fixes
Arne Coucheron (arco) - for his work on the legacy QC userspace drivers
Erik Hardesty (Erik Hardesty) - for the initial kernel work
eyeballer, verygreen and all other TP Devs - for their innovative and collaborative work
Steve Kondik (cyanogen) - for starting this great project
Google - for an awesome OS
Let me know if i omitted you and i will add you here asap
IRC channel
Click to expand...
Click to collapse
Visit us in #cyanogenmod-touchpad (general) or #cyanogenmod-dev (only dev related talk) on freenode

Known bugs / caveats:
wifi turns off in suspend -> uncheck "wifi optimisation" in advanced wifi settings
camera aspect ratio

Great!
Looking forward for the latest and greatest on our beloved Touchpad :fingers-crossed: !

Maybe it's a silly question but what is the difference between this rom and evervolv ?

Can't wait to give this a shot! Thanks for the continued development
EDIT: Quick question, is it possible to completely remove WebOS and use just this?

maxexcloo said:
Can't wait to give this a shot! Thanks for the continued development
EDIT: Quick question, is it possible to completely remove WebOS and use just this?
Click to expand...
Click to collapse
Are you sure you want to remove WebOS? Cause I think if you'll do this and if your TP will be bricked you won't be able to unbrick it via WebOS Doctor and/or WebOS system.

Awesome!!
Now how does one go about repartitioning?

Is this already Tablet UI, or will it need to be patched?

GnatGoSplat said:
Is this already Tablet UI, or will it need to be patched?
Click to expand...
Click to collapse
Datamedia CWM required
e.g. http://goo.im/devs/milaq/tenderloin/...a_20130903.zip
Located at top..

airtower said:
Awesome!!
Now how does one go about repartitioning?
Click to expand...
Click to collapse
you can boot into webos and use tailor. thats by far the easiest method.
will also include a hint to it in the first post.

Awesome CM10.2 Nightly Builds!
Awesome CM10.2 Nightly Builds! I notice that you are recommending a larger partition size for this Rom. 500MB vs ACME3's 400MB, time for ACME4? I may need to make a little video about using tailor to help get the ball rolling. Perhaps I should try cutting down the size of the gapps package too, hmmmm. Time for testing, Thank you Milaq!

Camera launcher
Focal wouldn't connect to a camera. I tried a NEXUS 7 camera launcher and that wouldn't work. Is there a recommended camera launcher?

the build runs very smooth, much smoother than the 10.1 builds.
i enlarged the partition size as recommended from 400 to 500 mb using webOS' tailor.
what about the other recommendations concerning the datamedia build?
when i open tailor i see the following partitions with their corresponding size:
USB (media): 25.336 GiB
Android (system): 512 MiB
Android (cache): 200 MiB
Android (data): 1.5 GiB
Unused Space: none
do you mean to reallocate the space to Android (data)?

So once we repartition appropriately and flash datamedia CWM (presumably via a dd command?), we're good to flash the build straight away? No ACME necessary?

airtower said:
So once we repartition appropriately and flash datamedia CWM (presumably via a dd command?), we're good to flash the build straight away? No ACME necessary?
Click to expand...
Click to collapse
no acme necessary!
- repartition
- wipe data
- flash datamedia cwm
- flash 10.2
- flash gapps
that's the way it worked for me

Gapps Mod and Media removal
Hey Guys,
So I reduced the size of the gapps package by removing the optional face-lock stuff, Google+ and Quick Search. Both of those apps are rather large and can be installed from the Play Store.
Download update-gapps-jb-lite-20130813-signed.zip(55.52MB):
This leaves me with a System storage size of 22.79/394MB
Then I did this...
How to monitor free System Storage space(Optional):
-You can use a free app,Quick System Info PRO, to check the size of your partitions and remaining free space, it should be = 387MB or 402MB. Either of these is acceptable and indicates that the ACMEInstaller3 worked correctly.
-Having a system size of 387Mib = 400MB and is perfectly normal after using ACME3
-Users report having a size of 394 after flashing to a new Rom. This is also acceptable.
-If your partition is an odd size or you get random reboots,then you may have encountered problems due to flashing you Rom.
Quick System Info PRO Video Link:
Quick System Info PRO Play Store Link:
How to free up System Storage space on the HP TouchPad(Optional):
I believe I have located about 15.89MB of data we can safely delete. Android in space videos and Phone Ring tones are located @
root/system/media/videos & root/system/media/audio/ring tones.
X-plore File Manager, use this app to delete the files:
Note* X-plore needs to be given Root Permissions by clicking the 3 dots in the corner and choosing configuration. Here check your Root Access settings. SuperUser + Mount Writable, this is what it should say. Next you may need to reboot before it takes effect.
Now I have a System storage size of 38.73/394MB.
I hope this helps people get it installed. Its running very well for me. The audio has been playing with the screen off. I have a low battery drain or -6ma with deep sleep so far, Stats still being generated. Looking like a great first build! :good::good:
Note: I just tested attached the TouchPad via the USB cable. It now shows both Internal Storage and the SDcard, very interesting! See the screenshot below.
Note: Here is a great thread that talks about using Tailor
How to guide for changing your system, data, and cache partition sizes(how to use Tailor): (Gradular)

ok but how to resize partitions??? Tailor installed buy no instruction
ok...by myself
1)Mount Android (system) partition
2) Check filesystem
3)resize

milaq said:
Known bugs / caveats:
wifi turns off in suspend -> uncheck "wifi optimisation" in advanced wifi settings
ui sounds not playing
wifi region code does not stick
buzzing noise audio on suspend -> toggle (non-working) bluetooth once
no bluetooth
camera aspect ratio
Click to expand...
Click to collapse
Just a few observations, the WiFi region codes have not stuck since the first CM10 the best I can remember. This is not even available on non-rooted my Samsung GS3 or Asus Infinity. Wonder if it works on rooted ones? I don't believe CM9 or 7 even had that feature.
What are UI sounds?
I don't believe WiFi turning off when one suspends(turns off) the screen is a bug. WiFi optimization is a feature added by the CM guys as a power saving feature. That is why unchecking WiFi optimization corrects the issue, ie. turns off the power saving feature.
I think I read over on Evervolv's thread that he finally got a working Rom that fixed the "buzzing noise audio on suspend ".
Why are you pushing this emulated SD card that requires all this repartitioning and using the datamedia CWM instead of doing it the traditional way it's been done over all the previous versions of CM on the TouchPad? I remember you doing a poll and best I remember, you did not get that much interest in the idea. You might want to consider a traditional build that does not require all the "hoop jumping" to get it installed and save all the fancy stuff for the more technically adept.
It's your Rom and you do it the way you want. But I suspect that you won't get the same interest from the average users with all this technical stuff that has to be done to get it working. I'm also with Roland on his idea for a new ACMEInstaller4 to set the /system partition to the correct size. And just a reminder, sometime in the not too distant future, HP is going to take down the WebOS servers, so unless one is prepared for that eventually, installing Preware and Tailor may not be possible unless one already has it installed or has prepared for life after HP support.
I also seem to remember reading somewhere, either on Evervolv's thread or on Rootzwiki that unless a newer 3.XXX kernel gets finished, that JB 4.3 on the TouchPad may not be completely feasible for various reasons.
Update: Found the post from Dr. Marble:
" I admit that I am not convinced it is worth running cm10.2. It is fun to make it work but I don't really see any advantages over 10.1 for what I do. Our kernel doesn't support fstrim. I don't use or really understand selinux. The sound is still flakey. I will keep working on it but I really think we are maxed out at cm10.1"
Maybe getting BT working on the CM10.1 nightlys and squashing any remaining bugs would be a more fruitful endeavour.
You know the work you guys do is awesome. What you have managed to get running on our lowly HP TouchPad rivals many other dedicated Android tablets in speed and stability. I recently purchased an Asus TF700T Infinity, OTA'ed it to Android 4.2.1(the latest update from Asus) and have been comparing various apps and functions side by side with my TouchPads, yes I have two. And I can honestly say that the Infinity is only marginally faster in certain areas and the TouchPads keep up with it nicely in most others. The only advantages I have with the Infinity is a new device, quad core processor, 12 core video and for now a warranty. I'm not going to unlock or root it for now.
With all that said, we may finally be seeing the sunset of our orphaned device. It's two and one half years old, we don't know how much longer the batteries in them are going to last, they have to be getting worn out. They are a pain it the ass to change. No one seems to be able to get a newer kernel built for it. The A6 firmware and bricking issues are always lurking to jump up and bite when least expected. Of those users that are still hanging on, many are not happy unless there is some kind of bleeding edge development going on and when there isn't, they start whining about ETA's. How much longer can you keep the hounds from nipping at your heels, or even want to?
I hope none of you take this as a negative statement or a big whine. I think I am just stating the obvious. Technology and innovation moves on and the TouchPad is not going to be able to keep up much longer. My hedge against that is my recent purchase of the TF700. I may even eventually sell my TouchPads before they are unsellable, ie. dead battery or something else going wrong. Who knows, they may last a couple of years, or only to next week.
Comments invited, flaming is not.
---------- Post added at 04:19 PM ---------- Previous post was at 04:10 PM ----------
RolandDeschain79 said:
Hey Guys,
So I reduced the size of the gapps package by removing the optional face-lock stuff, Google+ and Quick Search. Both of those apps are rather large and can be installed from the Play Store.
Download update-gapps-jb-lite-20130813-signed.zip(55.52MB):
This leaves me with a System storage size of 22.79/394MB
Then I did this...
How to monitor free System Storage space(Optional):
-You can use a free app,Quick System Info PRO, to check the size of your partitions and remaining free space, it should be = 387MB or 402MB. Either of these is acceptable and indicates that the ACMEInstaller3 worked correctly.
-Having a system size of 387Mib = 400MB and is perfectly normal after using ACME3
-Users report having a size of 394 after flashing to a new Rom. This is also acceptable.
-If your partition is an odd size or you get random reboots,then you may have encountered problems due to flashing you Rom.
Quick System Info PRO Video Link:
Quick System Info PRO Play Store Link:
How to free up System Storage space on the HP TouchPad(Optional):
I believe I have located about 15.89MB of data we can safely delete. Android in space videos and Phone Ring tones are located @
root/system/media/videos & root/system/media/audio/ring tones.
X-plore File Manager, use this app to delete the files:
Note* X-plore needs to be given Root Permissions by clicking the 3 dots in the corner and choosing configuration. Here check your Root Access settings. SuperUser + Mount Writable, this is what it should say. Next you may need to reboot before it takes effect.
Now I have a System storage size of 38.73/394MB.
I hope this helps people get it installed. Its running very well for me. The audio has been playing with the screen off. I have a low battery drain or -6ma with deep sleep so far, Stats still being generated. Looking like a great first build! :good::good:
Note: I just tested attached the TouchPad via the USB cable. It now shows both Internal Storage and the SDcard, very interesting! See the screenshot below.
Note: Here is a great thread that talks about using Tailor
How to guide for changing your system, data, and cache partition sizes(how to use Tailor): (Gradular)
Click to expand...
Click to collapse
Did you resize your partitions using Tailor?

Oooooo, looks like I have something to do tonight. Awesome.

TWRP 3.2.1 for H901

The following is the latest version of TWRP compiled for the T-mobile V10 Model H901.
https://androidfilehost.com/?fid=818070582850501883
MD5SUM: b89d341cd61da31a5348d8f6b3c75c97
The heavy lifting was done by the twrpbuilder project who were generous enough to compile TWRP for our device. They also provide their services to see TWRP is available for devices that don't yet have it. I've personally used this version to do a backup and restore but can't guarantee there won't be issues. If there are while you are still in twrp you should go to the advanced section and copy the log to your external sd card. This log will help them diagnose any issues.
The project is located at: https://twrpbuilder.github.io
Their XDA thread is located here: https://forum.xda-developers.com/android/apps-games/twrpbuilder-t3744253
If you already have TWRP installed installation is as follows: Click Install, choose Image file, navigate to where the TWRP img file is located on your external sdcard and flash that img to the recovery partition. Back out to the root dir and you can select reboot then recovery...it should bounce you right back into recovery and you should see the new version loaded. If you have root in the rom and run into issues the app "flashify" can reflash TWRP 3.0 so make sure you also have it's img available.
This is pretty much only for folks who already have twrp to update to the latest. If you are on nougat you are still stuck until an exploit is released that works for nougat the way dirtycow did for marshmallow and below. *update* an exploit to give root to nougat users is now available thanks to @runningnak3d here: https://forum.xda-developers.com/tmobile-lg-v10/general/root-h901-nougat-t3773942

Reserved Post #1

Reserved Post #2

famewolf said:
The following is the latest version of TWRP compiled for the T-mobile V10 Model H901.
https://www.androidfilehost.com/?fid=8180705828505018
MD5SUM: b89d341cd61da31a5348d8f6b3c75c97
Click to expand...
Click to collapse
Looks to me like that URL should read
https://androidfilehost.com/?fid=818070582850501883
[ EDIT ] Yup, confirmed.. The URL I listed works fine.
Thanks for the file!
:laugh::silly:

NYLimited said:
Looks to me like that URL should read
https://androidfilehost.com/?fid=818070582850501883
[ EDIT ] Yup, confirmed.. The URL I listed works fine.
Thanks for the file!
:laugh::silly:
Click to expand...
Click to collapse
You are correct. For some reason a few characters got truncated. I've corrected the url in post #1.

famewolf said:
The following is the latest version of TWRP compiled for the T-mobile V10 Model H901.
https://androidfilehost.com/?fid=818070582850501883
MD5SUM: b89d341cd61da31a5348d8f6b3c75c97
The heavy lifting was done by the twrpbuilder project who were generous enough to compile TWRP for our device. They also provide their services to see TWRP is available for devices that don't yet have it.
Click to expand...
Click to collapse
Just as an aside, this version seems to correct (mostly) the date issue of previous TWRP versions for the V10. Versions before this one used to generate a default date (folder name) for the backup dating back to the 1970s as I recall.
This one has the correct month and day and time and the year is only 1 off - it showed 2017 on my very quick attempt to play with it.
One additional note to those installing it via TWRP itself - after selecting image flash , MAKE SURE you specify RECOVERY partition, not BOOT! Specifying BOOT will most likely have some less than desirable results.. :laugh:

NYLimited said:
Just as an aside, this version seems to correct (mostly) the date issue of previous TWRP versions for the V10. Versions before this one used to generate a default date (folder name) for the backup dating back to the 1970s as I recall.
This one has the correct month and day and time and the year is only 1 off - it showed 2017 on my very quick attempt to play with it.
One additional note to those installing it via TWRP itself - after selecting image flash , MAKE SURE you specify RECOVERY partition, not BOOT! Specifying BOOT will most likely have some less than desirable results.. :laugh:
Click to expand...
Click to collapse
I've passed on the date issue. Uncertain if he'll generate another build though.

famewolf said:
I've passed on the date issue. Uncertain if he'll generate another build though.
Click to expand...
Click to collapse
Seems that either nobody is using this version or nobody knows about it or they just have nothing to say..
Anyway, as you know, I have spent a fair amount of time recently working with this and installing it. A couple of observations that may be worth noting..
I double checked and I did set a screen timeout on TWRP. Previous versions would first, dim the screen, followed by turning it off completely. If you had the device near you on a desk while backing up the screen lighting up again when TWRP completed was a sure signal that it was finished.
This version of TWRP dims the screen but the screen is never turned off completely. A minor annoyance I suppose but something is different from previous versions.
During the /data partition backup I noted a (to me) new display in yellow: "Backups of data do not include any files in internal storage such as pictures or downloads"
Seriously? Is this something new? Certainly the display is but I always kinda relied on all that being backed up with /data and having the ability to restore them. This is a more serious issue for me which may make me consider going backward..
Thoughts?

NYLimited said:
Seems that either nobody is using this version or nobody knows about it or they just have nothing to say..
Anyway, as you know, I have spent a fair amount of time recently working with this and installing it. A couple of observations that may be worth noting..
I double checked and I did set a screen timeout on TWRP. Previous versions would first, dim the screen, followed by turning it off completely. If you had the device near you on a desk while backing up the screen lighting up again when TWRP completed was a sure signal that it was finished.
This version of TWRP dims the screen but the screen is never turned off completely. A minor annoyance I suppose but something is different from previous versions.
During the /data partition backup I noted a (to me) new display in yellow: "Backups of data do not include any files in internal storage such as pictures or downloads"
Seriously? Is this something new? Certainly the display is but I always kinda relied on all that being backed up with /data and having the ability to restore them. This is a more serious issue for me which may make me consider going backward..
Thoughts?
Click to expand...
Click to collapse
I use my v10 as my backup phone now. On my HTC U11 life when I make a nandroid it shows that it is not backing up files on internal storage. I think this is normal now on the latest version of twrp.

NYLimited said:
Seems that either nobody is using this version or nobody knows about it or they just have nothing to say..
Anyway, as you know, I have spent a fair amount of time recently working with this and installing it. A couple of observations that may be worth noting..
I double checked and I did set a screen timeout on TWRP. Previous versions would first, dim the screen, followed by turning it off completely. If you had the device near you on a desk while backing up the screen lighting up again when TWRP completed was a sure signal that it was finished.
This version of TWRP dims the screen but the screen is never turned off completely. A minor annoyance I suppose but something is different from previous versions.
During the /data partition backup I noted a (to me) new display in yellow: "Backups of data do not include any files in internal storage such as pictures or downloads"
Seriously? Is this something new? Certainly the display is but I always kinda relied on all that being backed up with /data and having the ability to restore them. This is a more serious issue for me which may make me consider going backward..
Thoughts?
Click to expand...
Click to collapse
On your last issue this is business as usual...twrp has NEVER backed up the internal SDCARD unless you selected the sdcard entry in the list of sections to be backed up. DCIM (pictures) and the Downloads folder/dir have never been included.
As to the dimming, you can check in settings to see if something can be configured however each person compiling twrp can set their own options as to how they want it to function. There is no guarantee or expectation that Person B is going to use the same options as Person A. You are of course free to compile your own copy configured the way you would prefer it to behave but the process was enough of a pain in the butt I just requested twrpbuilder to generate one as I kept getting errors. The process to compile it also appears poorly documented.

sabresfan said:
I use my v10 as my backup phone now. On my HTC U11 life when I make a nandroid it shows that it is not backing up files on internal storage. I think this is normal now on the latest version of twrp.
Click to expand...
Click to collapse
I kinda suspected that but that is, at best, a questionable choice since I don't even have the option to check or uncheck a selection for it. Not happy..
famewolf said:
On your last issue this is business as usual...twrp has NEVER backed up the internal SDCARD unless you selected the sdcard entry in the list of sections to be backed up. DCIM (pictures) and the Downloads folder/dir have never been included.
Click to expand...
Click to collapse
Not quite. INTERNAL is not the SD Card. Internal is emulated sd on /0. In TWRP if you tap select storage, for example, you can pick "internal" or "SD" for backup destination, as one example.
I keep a fair number of things in /Download - things I grab in my travels, things I save there for later use.. whatever. I'll have to device a Tasker module or something for copying all those to the actual SD card...

NYLimited said:
I kinda suspected that but that is, at best, a questionable choice since I don't even have the option to check or uncheck a selection for it. Not happy..
Not quite. INTERNAL is not the SD Card. Internal is emulated sd on /0. In TWRP if you tap select storage, for example, you can pick "internal" or "SD" for backup destination, as one example.
I keep a fair number of things in /Download - things I grab in my travels, things I save there for later use.. whatever. I'll have to device a Tasker module or something for copying all those to the actual SD card...
Click to expand...
Click to collapse
A fairly recent app/utility created by @kdrag0n called Tipatch brings a long-needed resolution to the table regarding "full backups" of Data using TWRP. In a nutshell, Tipatch installs to your Android device as a basic APK. Within the simple GUI, once root permissions are granted (In-Place Patching) Tipatch will decompile, patch, recompile and flash the patched TWRP to /recovery, effectively patching your TWRP build to backup the contents of Internal Storage (emulated SD card) as part of Data itself, so that backups will now include those Internal Storage contents such as downloads, photos, videos, game data, and other various files. I've tried it on this particular build of TWRP and it works without any issues. There are options to patch TWRP without root permissions as well. There are Windows, Mac & Linux versions available too. If you are patching TWRP on a device with an A/B partitioning scheme, the patched TWRP can be installed on both A & B using a one-click option. Of course, one insurmountable caveat to patching TWRP with Tipatch is that wiping Data now will also wipe Internal Storage (emulated SD card). In short, the utility works on pretty well all device types and chipset platforms (Exynos, Kirin, Snapdragon, MediaTek, etc.). The latest Tipatch update, v1.6, includes support for TWRP builds that use LZMA compression, and removes the now-misleading notification previously listed when backing up Data -- that Internal Storage (/data/media/ path / emulated SD card) contents are not backed up. Anyway guys, here is a link to the Tipatch Discussion & Support thread: https://forum.xda-developers.com/android/apps-games/app-twrp-tipatch-backup-internal-t3831217
The latest Tipatch v1.6 app is also available on the Play Store and many other app & apk repos for Android. Versions for Windows, Mac and Linux can be downloaded using the above link.