Related
[Question] I have been rooting my Streak and installing Busybox pretty much since I got the thing and have always had stability issues. My question is this: could Superuser and/or Busybox be the cause of the instability?
This time around, the only other programs installed are: Angry Birds, ES File Explorer, Go Launcher, Lookout, and Screen Timeout Toggler, which I have downloaded but not actually used yet and is a recent addition to a phone that has had stability issues for a long time.
The setup this time is a Factory reset then install of 354 using the recovery and package from the Wiki. I have the density set to 240. It was unstable at 160 also, so I figured if it is going to shut itself off for no reason, I might as well be able to see the small print on the Maps app. There appears to be no difference in stability between the two density settings. I have also added the AT&T speed tweaks, but these are a recent addition that was begun after I started having the stability problems.
I used ES File Explorer to rename the following apks so far:
amazonmp3
com.facebook.katana (I don't do Facebook)
com.google.android.inputmethod.pinyin-1 (I don't read or write Chinese)
com.twitter.android (I don't Twit either)
EmailStageWidget-release (I use Gmail quite nicely)
HuanYing-Streak-release (again, no knowledge of Chinese)
NeroDellSync (useless app)
SocialStageWidget-release (see Facebook and Twitter)
StageLauncher-release (quite happy with Go)
YouTube (I get better results watching in the browser)
Is there anything I shouldn't have renamed?
Any thoughts on what I might try? This is a very basic kind of setup without a lot of changes from stock. I don't see why I have these stability problems.
Why are you using 354 to begin with?
Having the latest and greatest ROM is not always the best option. So I recommend changing your base ROM to, e.g. 351, assuming of course you have an unlocked Streak. From personal experience I believe you'll have a better result customizing it.
351 and 354 are both 2.2.2, aren't they? I don't understand why one would be better than the other.
Right. However 354 is tweaked for the Asian market, meaning there may be subtle internal differences between the 354 code and 351 code. Differences that may be the source of the instability.
My advice stands. Change the ROM you're using as a base.
Having root is like being the 'normal' vista/win7 user.
(This is assuming UAC is on and working correctly)
You're just a normal user till you hit a UAC prompt, without a prompt you cant modify anything that can seriously change/break the system. Only after passing the prompt will you be able to break/modify stuff, it's not the prompt itself it's whatever is asking for permission. This of course excludes the rare malware that can bypass UAC but that's not the point.
At least on android being rooted is safer as if you have superuser installed malware that tries to secretly gain root by using the standard SU binary will notify superuser and thus the user. While they can likely bypass that it's yet another hurdle just like on pc with UAC vs no UAC. (Though on a pc UAC doesnt give the same equivilent hurdle)
Strephon Alkhalikoi said:
Right. However 354 is tweaked for the Asian market, meaning there may be subtle internal differences between the 354 code and 351 code. Differences that may be the source of the instability.
My advice stands. Change the ROM you're using as a base.
Click to expand...
Click to collapse
I tried it. I did a factory reset, installed the recovery image, installed 351 from the update package, did a factory reset, and with absolutely no changes to the install, nothing installed except a couple of updates it did on its own, I am lucky to keep it running long enough to open a program.
I want to do the most complete uninstall and reload I possibly can. Is there a way to format the internal card and then reload?
I am just not convinced that installing from the the update.pkg is completely scrubbing the system during the install because it seems like the more I do this loading and reloading of roms, the worse the thing runs. The phone has been unusable today.
a reinstall with stock recovery + pkg + optionally a fac reset is as close as you can to getting a fresh install.
If you mess with wiping partitions in fastboot you WILL super-brick your streak and end up with a paperweight.
If a fac reset after rom reinstall doesnt fix everything you might have a hardware issue
One thing to make sure of.....is to update superuser,and busybox installer.....you do have busybox installed.....i had stability issues,untill I updated these.
Sent from my Dell Streak using XDA Premium App
After update su and bb,reboot......if you still have some problems,reboot into streakdroid,and clean delvik cache,and reboot to streakdroid and fix all permissions.
Sent from my Dell Streak using XDA Premium App
hello gentlemen
i bought my viewpad 7 last week. after digging this forum i tried to root my tablet with super one click but i was unable coz it stuck in screen and happen nothing somehow i tried gingerbreak and it worked. as i am totally newbie in android os and i have no idea on programming. but the most important thing is clockwork recovery i saw couple of youtube videos and tried working but ended up with error . i dont know how to setup adb on my pc so i tried terminal emulator but no keyboard.. tried qtadb but show me '' permission denied'' now i am pulling my hair off. i have got rom manager installed on my tablet but whenever i ty to install update.zip it say signature error or somthing (i have got custom rom in my sd and renamed to update zip also i have clockwork recovery img and flash recovery) the only thing i need is a working terminal emulator as i have no idea on comand from pc.
so is there anybody who can give me a easy tutorial or make a video to demonstrate how can i get clockwork recovery installed also custom rom i would be really really greatful
hope someone saves me...
Hello & welcome, there's no need to panic but definitely - very important to be patient, set aside at least half a day or more, and, read - read - read. Take notes as you go along & do NOT rush.
If you have not gone thru this sticky, please do so - http://forum.xda-developers.com/showthread.php?t=1236990
Sticky #1 is mandatory reading to take full advantage of the Vpad7 so that you can understand the basics, describe your Vpad's hardware & build information, etc. and how to press various buttons, go back, reset & get into Recovery and Bootloader. Without knowing it, you are prone to run into problems.
First, you need to check & make sure that your CWM (which verison) is properly installed & working (and, if so) - check under the Advanced submenu to verify "Signature Verification" status.
Do you have an "older" non-ITE or "newer" ITE multi-touch screen device, which determine which custom ROM can be used? Be specific, please ...
Generally speaking, there is no need to rename a downloaded ROM's zip file to update.zip for flashing ... so I suggest that you do more reading first.
Do you have USB debugging turned on? Applications - unkown sources turned ON to allow installation of non-Market apps? A working knowledge is essential to avoid (soft) bricking your device by being able to understand the process for Flashing - start here http://forum.xda-developers.com/wiki/Flashing_Guide_-_Android
There's nothing simple & easy about all these, sorry - time & patience is a requirement to get everything working together. Look under the "Development" section for how to install ROM & the issues involved - there are just a handful of ROMs and you don't need to spend a hundred hours going thru all of them, a few hours of reading will do - a 10 minute Youtube video isn't going to do it. The best person to "save" you is you - YMMV. Regards.
thanks a million i finally made it. i used rom manager to install un official clockwork recovery and did install custom rom however i need one more final solution i was trying to get app2sd but my rom maker said it is built in inside the rom just need to creat ext3 but i guess i cant do that without comand so again is there any manual method to do that i saw an option on rom manager but it offers only 512mb partition but i want more may be 8 gb or 4gb i have 16gb sd card.. so can u help me pls...
and i yes i had usb debug on. unknown source on
big_b0sss said:
... i used rom manager to install un official clockwork recovery ... custom rom however ... app2sd ... is built in inside the rom just need to creat ext3 but ... without comand ... rom manager ... offers only 512mb partition ... may be 8 gb or 4gb i have 16gb sd card..
Click to expand...
Click to collapse
1. Rom manager - I do not use them on my Android devices but if you are comfortable with it and help simplify your tasks & learning curve, good for you. Remember to backup, backup & backup your work & save it to more than one location - those "oops" happened to all of us, sometimes (and, at the worst time - Murphy's Law 101)
2. You only need a few files in its own sub directory or folder to properly run adb and busybox, and, to run the (good old DOS) command prompt from your PC - just need to type the commands carefully. Alternatively, Terminal Emulator (with or without the shell or user interface) can be downloaded from Android Market to the Vpad7 to install & run (it's not pre-loaded) with SU enabled ... (more reading for you on how-to's)
3. Not sure if you are referring to App2SD in Market (quite a few out there) or DT's A2SD and A2SDGUI in some of the custom ROM. Vpad7's custom ROM recommend 1 MB SD ext3/partition in general (ext4 is more advanced and challenging) - there is no need, advantage or benefit in a 2GB or 4GB ext3 with a 16GB mSD card (as you are allocating/reserving unused space that you cannot dynamically changed or reassign later on as you begin to run low on "general" storage space on the card - PLUS, you will have to reformat the card & wipe/lose everything on it, until it's restored from saved backup)
FYI - I keep the last 3 to 5 CWM Backup images/files on the mSD card and it's close to 3GB in size already, not counting pix, mp3's and saved videos.
4. Older version of CWM Recovery worked best for me in repeated ROM flashing & setup to partition/format the mSD, verison 5.0.2.6 can work but the newest one posted 5.0.2.7 did NOT work for me - YMMV, of course. Refer to the one in Cleanviewpad7 V1.0 and its instructions or EU Vapd 7 V1.7b - as I'm guessing from your description that your device is a newer ITE multi-screen hardware build. KWBR V3.2 ROM works with ITE and has the newer kernel and A2SD is easy to use per installation guide - it's lean & stripped of non-essential apps.
Have patience, backup & have run !
thanx again for ur reply but i dont know why i do not get keyboard on my terminal emulator. i tried to put comand through terminal emulator but due to keyboard issue i cant i also tried dos but i have no knowledge on that. can u make a video for me or a tutorial how can i get a2sd work on my vpad 7
thanks again
big_b0sss said:
... dont know why i do not get keyboard on my terminal emulator. i tried to put comand through terminal emulator but due to keyboard issue i cant i also tried dos but i have no knowledge on that.
Click to expand...
Click to collapse
First, as I asked before, we do NOT know which ROM you are trying to use?
But, I'm going to guess - since I've flashed all of the working ITE ones here, and you are using KWBR v3.x - and, if so, please confirm or verify, yes or no.
If so, I had issues with its keyboard not showing up in terminal emulator, and there are different reasons for it - namely, including the OP developer's choice of installed KB. However, as a workaround - by running adB/busybox from Windows Vista's command prompt, I can execute instructions to re/mount, reboot, etc.
By installing a different KB & switching to it, it worked under terminal and I can run command prompts directly. There is a learning curve involved here - not something to rush, rather steps by steps - there are "stickies" in the threads and I do not want to further clutter up excellent guides already written up, 6 to 9 months plus ago - which I took time to read, follow & work with. I encourge you to do so as well.
My advice, the easiest to do, is to install & start with a different ROM - Cleanviewpad ROM is basic, simple & easy to install, virtually "bug" free and I suggest that you start with that. KB worked directly as a toggle, popping up from terminal emulator, and you can run commands from it.
Once you are comfortable & has everything working, you can optimize your A2SD and move apps from internal storage to mSD card, etc. and progress to the next level - EU Vpad 7 V1.7b ITE ROM is nice but from experience and reading the thread's posts, some "beginners" lacking knowledge & skills have trouble with it. By running a # of patches, I get it updated to the latest and it's running optimized to my personal liking - it's not entirely difficult to learn but not for someone completely new to Android OS.
Here's a link that you could've google right here in XDA - guide to ADB - bookmarked the link for you, please search for other guides, thanks
http://forum.xda-developers.com/showthread.php?t=879701
hi there thank you so much for helping me again and yes i am using kwbr rom because i have tried cleanviewpad 7 but stuck at welcome screen doesnt work anything then tried lakehouse froyo enhanced but link disabled so stuck with this rom.. i really wish i cloud post on dev section coz im kinda stuck with this post..
but hey if u dont mind and if u have froyo enhanced rom can u upload that for me or give me a working link...
sorry for bothering u but would appreciate
Still waiting for a ROM for Viewpad 7e. Anyone know of one in development? Even the stock ROM bundled with CWM would be good so that we would have the ability to do a Nandroid backup.
Sent from my SPH D700 using XDA App
Cyanogen Mod 9.4, Shadow kernel, EI22. I like my Ice Cream Sandwich!
big_b0sss said:
... using kwbr rom because i have tried cleanviewpad 7 but stuck at welcome screen doesnt work anything then tried lakehouse froyo enhanced but link disabled ... and if u have froyo enhanced rom can u upload that for me or give me a working link...
Click to expand...
Click to collapse
Are you making good progress after rooting with custom ROM, learning a bit more about using adB and terminal emulator? I searched my storage bins for what I've kept for the Vpad7 - and I have NO luck yet finding the Froyo enhanced ROM. I did uploaded the EU V1.7b ITE custom ROM to Dropbox, along with the a2sd*.zip file (just in case, you are comfortable & ready to try - after backing things up) The A2SDGUI app is available in Market, just search & download & install up once the EU V1.7 ITE ROM is up.
A2SD does NOT need to be working for the ROM to do its basic functions, just that it will soon run low on internal storage/memory and that's where A2SD come in. If you find it useful, do a CWM backup first , then use the earlier version of CWM to reformat the mSD card again (thus, wiping it clean) and setup a 1MB ext3 partition per detailed instructions. Reboot & reconnect USB, and move/restored all of your saved files/folders/settings, etc. back to the mSD drive.
Next, flash the A2SD program by DT again just to be sure from Recovery - and then Restart into Recovery. Wipe cache & dalvik and boot up again - cross your fingers and A2SD should be up & running - check it with A2SDGUI and/or Titanium Backup will display various memory/partition/storage space & usage (used/free & total)
http://dl.dropbox.com/u/64025118/EUViewpad7v1.7b-ITE.zip
http://dl.dropbox.com/u/64025118/apps2sd-2.7.5.3-dt.beta04-signed.zip
Again, I am and will be be responsible for anything if something goes wrong by using & flashing these zip files, they are unchanged or unaltered as I originally downloaded them. I'm simply posting them with the mess created by the multi-upload servers being offline, etc. as many folks are completely at a loss for what to do next. Full credits go to the OP/xda-developers for creating their masterpieces. If you are not comfortable or unsure, please do not proceed or assume the risk - the stock ROM, especially unrooted, isn't bloated by any means at all. There is NO over-clocking at this point for any ITE kernel for the Vpad7, period - none that I know of. Folks, do NOT confuse or try this with Vpad7e (which is a different device, sorry - cannot help at all)
Regards & do post with your results and share, and, if I can help further with the specifics, will be glad to do so.
about the euvpad rom
hi there i am glad that u sugested me that rom but before i try to do anything i just want to ask that which rom is better, im asking u coz u might know as u have tried diffrent rom. i am currently having no issue with kwbr rom however somtimes lag and slowness i know its bocoz vpad has only 600mgh processor so does euvpad rom faster or is there any good thing just wondering...
if euvpad rom is better i will go ahead and intall it.. so kind of waiting on ur reply
big_b0sss said:
hi there i am glad that u sugested me that rom but before i try to do anything i just want to ask that which rom is better, im asking u coz u might know as u have tried diffrent rom. i am currently having no issue with kwbr rom however somtimes lag and slowness i know its bocoz vpad has only 600mgh processor so does euvpad rom faster or is there any good thing just wondering...
if euvpad rom is better i will go ahead and intall it.. so kind of waiting on ur reply
Click to expand...
Click to collapse
Personally, I prefer and continue to use EU V1.7b for ITE, it has support for European languages as well as Asian languages. KWBR only support Euro language and the ROM is more "stripped" down with fewer apps, but it does work nicely "out of the box" with A2SD - downside being that internal memory/storage still seem to run low (once I re-install 50+ apps on my device)
For EU V1.7 - it's using an older version of Android Market, but can be easily updated if one wanted to, and, has a few more "basic" apps pre-installed including Documents To Go - and, by adding "Car Home" - I have a working 7" GPS device in the car when needed (sound volume is low, however due to those tiny stereo speakers) - I have been running it for 5+ months now, very smooth & few, if any, FC or freezes, and, Angry Birds running nicely on it, same with YouTube videos over WiFi connection (my 3G is on Edge network, so speed is SLOW and thus very choppy due to broadband speed, not CPU-related)
If you are running KWBR nicely now, do a Backup from CWM first, wipe cache/dalvik & system next - then flash the EU Rom and setup - to see whether you like it. And, if you do - follow the post's steps that I wrote up a while back and get A2SD running with the earlier verison of CWM for ext3 partition, restore/copy back all the files to the mSD card - and reboot/check for A2SD functionality, hopefully - it works without further tweaks - and I think you will like it.
If not, it's easy enough to get back into Recovery, wipe clean it first (very important to clear all traces) and RESTORE the KWBR image from the mSD, and reboot - and you can continue using it. Set aside 2 or 3 hours to do this slowly & right, and you will find the process educational & informative - and, as I always remind newbies - the rules are simple - Backup, Backup and Backup !!
Cheers & go have fun !
I have the CM10 [skang jellybro] fascinate rom installed, and coming from a cm9 rom, all my apps didn't fit because they switched the partition around [making the app partition only 468MB, and the system partition 1.5 GB].
So anyway I had to move a lot of apps to the sdcard. So I just downloaded a newer version of my rom, and wiped cache/dalvik, nandroid backup, then I installed the new zip.
Then I rebooted, and it had to 'optimize' apps [create dalvik cache?] and after that finished...I only had about 15-20 apps show up in my app drawer. [I have probably around 40] So I clicked on Zedge, on my homescreen, and it said "App isn't installed." I then started to worry..:S I googled apps on sdcard disappearing.. and so I opened titanium backup, and under Batch operations, it said "Restore missing apps (6)," and they were 6 apps that I'd uninstalled but didn't delete the backup. so then I wasn't sure what to do next, because I did not create a fresh titanium backup prior to updating my rom [because I did a nandroid instead..] so then I went to Manage Apps, and then.. for some reason, all my apps showed up again! all the ones on my sdcard.
I tapped Zedge again on my homescreen, and it loaded up! So my question is, what happened? Why did my apps disappear, and then just show up again? was it loading titanium backup? or did the rom just scan the sdcard for apps?
Sounds like it just messed up the media scan of the sdcard which I have heard happens from time to time... not sure if that's related to your issue, but now are all your apps installed or are you still missing some? Next time I would just reboot again and let it re-scan to see if it helps
Crawshayi said:
Sounds like it just messed up the media scan of the sdcard which I have heard happens from time to time... not sure if that's related to your issue, but now are all your apps installed or are you still missing some? Next time I would just reboot again and let it re-scan to see if it helps
Click to expand...
Click to collapse
ah.. yes they are all there, but I was just wondering why did they disappear, and then why did they just show up all of a sudden?
I guess if it is the media scan thing, that would explain it.
Fast Boot option may be the culprit
mvmacd said:
ah.. yes the [apps] are all there, but I was just wondering why did they disappear, and then why did they just show up all of a sudden?
Click to expand...
Click to collapse
CUT TO THE SOLUTION BELOW -- SEARCH FOR ////
Some (not all) of my apps moved to SD (all by Titanium Backup Pro) have begun to disappear and (sometimes) reappear without warning after I began to add and delete large Virtual Machines created in QEMU from my 16GB SanDisc class 10 microSD card on my HTC Droid Incredible running rooted stock Verizon Android Froyo 2.2.3. I know this thread is far from my phone's "home base", but from what I can tell this problem with disappearing apps located on an sdcard is NOT determined by hardware or even Android version.
I also happen to use LauncherPro by Federico Carnales instead of the built-in HTC Sense launcher. I noted elsewhere on XDA that a user had suggested that because at least some (maybe all) launchers start before the SD Card that this may be a problem, especially if changes are made to the sdcard that the launcher did not perform, or was not active during their performance by other apps such as Titanium Backup. That fits my situation, because I unmounted the SD, physically removed it to a PC, and added/deleted large VM files to save (lots) of time. No problems of this sort before I did this, so there must be some connection.
I noted that other users have tried reformatting SD, substituting different brands of SD, using newer/older SD etc. None of these reliably helped. So I skipped these options.
//// The (simple!) solution I tried that SEEMS to work (only time will tell!) is buried in the main Android Settings (accessed from the Menu button while in Home screen). Under "Applications" there is a setting "Fast Boot" that I checked long ago and forgot about (it seemed like a good thing to do at the time). The text warns "Turn off to use some Market apps" (that shows the age of my 2-yr old used phone and Android OS -- ohmygosh!-- because it refers to Market rather than Google Play Store!) Anyway, I unchecked the option and rebooted the phone.
Yes, it took a bit longer to boot (maybe a whole minute!), but after waiting about another minute ALL my home screen apps had normal icons and loaded properly. Titanium Backup Pro batch scenarios confirmed there were no apps in a forced uninstalled state (i.e. I had not done the deed, the system somehow had done it or at least rendered the apps "invisible" to Titanium, which decided they needed reinstallation).
The only odd behaviour was that auto brightness was turned off after I unchecked Fast Boot and rebooted. Going into Android Settings > Display and rechecking "auto brightness" took care of that. No other oddities or strange behaviours thus far (but it has only been about an hour).
I will report back here on this thread only (Samsung Fascinate > Fascinate Q&A > What just happend? apps on sdcard) if anything else requires reporting. Silence implies success!
link: https://www.google.com/url?q=http:/...ds-cse&usg=AFQjCNE3D5NrpiSqCRSof-ou1mn6iyeGVg
(I am copying this original post (without edits) to other relevant threads, but will not post anything further elsewhere -- only here. This is a bit arbitrary (although this thread appears to be the most recent active one on this topic), but I hope this approach pleases the XDA sysops/admins) :angel:
EDIT 2012-12-26-a:
Nearly all of the 100+ apps on my HTC DINC (Droid Incredible) continue to behave normally after the "fast boot OFF" fix. (No disappearing act.) However, I did find one that appeared to be installed but really was not: ASTRO File Manager. I used Titanium Backup Pro to reinstall app+data from a backup. It only took a couple of minutes, and after that all went normally.
The only other noticeable issue right after the fix is that nearly all of my installed, functioning apps were listed as "missing" by Titanium Backup in its Batch scenario list (although they were NOT counted in the total number of apps listed with the scenario -- that number was 61, and it should have been nearly 170 based on the number of apps actually in the physical list). After about a day or so of regular usage, a re-check of the "missing apps" Batch scenario found all the functioning apps no longer listed; the 61 missing apps were valid -- they were all from earlier ROMs belonging to the original HTC setup and another phone (MOTO OG Droid). Since I have kept the MOTO as an emergency backup smartphone, I might conceivably want to revive some of these apps.
EDIT 12-26-b:
Some other potentially useful points I have gathered in my survey of this topic across XDA:
1. This problem happens most often when using the "Disk drive" option in the USB Debugger system app. It also happens after physically returning the sdcard to the phone after removing and inserting it into a PC.
2. Those who have wiped the app data cache also report serious problems.
3. Wiping the dalvic cache while in Recovery mode automatically triggers a rebuild of that cache, which may make apps behave oddly or disappear until the rebuild is complete, which reportedly "takes time"
Personally, I did only #1 myself, and the fast boot removal fix seems to work well for that one.
I cannot confirm the others, but they seem to make sense to me, and I doubt the fast boot removal fix would have any influence on them.
4. There are some signs that apps installed to internal phone storage can behave in the same way. This may mean that the fast boot OFF tweak may prove beneficial to any storage area, since they all come on-line after the OS loads from phone memory.
EXT4ALL (aka Convert2ext4) = final fix for dalvik cache related bugs (?)
Further investigation of the Dalvik cache reveals a significant connection between it and a number of odd and unpleasant behaviours, including Low Disk Space warnings and disappearing apps.
Fortunately, there are some excellent XDA forum threads about dealing with the Dalvik cache.
The best recent place to start seems to be here:
[Q] Incredible running CM7.2 "Low on space" message (launched 2012-12-14)
http://forum.xda-developers.com/showthread.php?t=2047424
It is not because of the focus on the Droid Incredible or CyanoModGen in this thread, but the attention paid to the more universal fix "EXT4 4 ALL" aka "EXT4ALL" or "Convert2Ext4". (Thanks to Senior Member cmlusco for his post #9 on the thread that got me started in the right direction!)
Files can be found at these locations:
Goo.im site http://goo.im/devs/tiny4579/mods
DINC.does-it site http://dinc.does-it.net/EXT4_Mods/
One version of this fix (Convert2Ext4_no_data_limit_normal_dalvik.v2.0.zip) moves the Dalvik cache from the default, limited 150MB internal partition to the "unlimited" (or at least maximum) 750MB internal partition.
Any phone with a kernal installed that supports ext4 can utilise this fix.
[ I personally use gingertiny 2.6.35.14-v2+ (2012-02-13), which has supported ext4 since late 2011]
My own experience has been to flash the "no data limit normal dalvik" zip file using ClockworkMod 5.x Recovery -- this was entirely painless. I just downloaded the file into my phone's downloads folder on the sdcard using a web browser, then ran CM Recovery (with a little assist from ROM Manager), selected "install a zip from sdcard" and navigated to the file. It was all done in 5 minutes. After manually rebooting a second time, everything seems to be working normally after about half a day of regular use.
For those who flash a new or updated ROM sometime in the future, you would need to flash this fix after doing so.
There is plenty of information contained on the main threads of this topic. Links aplenty can be found; just follow the ones provided in the thread I suggest here to get started.
Hopefully, this brings an end to my struggles with my phone's storage issues, and to others of you reading this post and following the links to the threads and downloads.
FYI -- My storage values changed as follows after running the fix:
Total Internal memory: 748MB --> 770MB (22MB increase)
ROM free space: <1MB --> 20MB (close to the value change of total internal memory)
Used internal memory: ~335MB --> 464MB (close to 128MB increase)
Remaining internal memory: ~420MB --> 306MB (close to 128MB decrease)
So, it seems that my ROM was being used to cache app data, which would explain why the value kept declining even though I NEVER added anything to it (using Titanium Backup Pro or anything like it). When free space on my ROM literally ran out, Android OS hit the proverbial panic button and warned me to free 512kb minimum to allow Gmail to download new mail. Now, it has 20MB free (and will hopefully stay that way, since I NEVER intend to transfer anything into the ROM!) -- The internal memory usage jump of 128MB probably indicates the Dalvik cache.
SUMMARY:
1. Turning off "fast boot" in Android settings helps some, but it does not get to the heart of the issue. It will NOT make a Low Disk Storage warning go away.
2. Once you have a Low Disk Storage warning, you MUST uninstall enough apps to make it go away (keep track of what you take away, because you can reinstall them very soon!)
3. With no LDS warnings showing, flash the "Convert2ext4 no data limit normal dalvik" zip file. THIS APPEARS TO BE THE REAL SOLUTION!
4. Reinstall your recently removed apps, and you should be good to go! :fingers-crossed:
PS>>> One last unresolved issue: I am still unclear exactly WHERE the dalvik-cache ends up, since my Astro file browser cannot locate anything containing the word "cache" that does not now report "EMPTY". There are a large number of "com." folders containing software I have installed found in the /mnt/asec/ folder. The total size of the contents of this folder (362 MB) is within 100MB of the amount of internal memory reported in use. Does that 100MB represent the current size of the Dalvik cache files, or at least include them? If so, where are they located? If anyone can help me figure this bit out, I would be grateful! :fingers-crossed:
Hey guys....here's my situation.
I bought a Blu Touch Book 7.0 plus off of Amazon. Got it two nights ago. It's a true phablet. 512 RAM / 512 ROM - I was a little concerned but figured as long as I could root it, I was good to go.
Anyways - no I am not looking for a root. I was able to root it relatively easily after an initial failed attempt which required a factory reset - if anyone is interested, it required PDANET+ & UnlockRoot, SuperOneClick and other methods failed. I threw in a class 10 SD, and modded Android so all apps would be downloaded/installed to my SD card (I did this using the SDK & command prompt in USB debugging mode). I had researched apps previously and began to furiously download and tweak. I threw in a T-Mobile SIM, and everything was going well, I was very happy. It actually seems to be a well made device, though it's a little bulky and the phone function works much better with a bluetooth headset.
Then, I deleted Phone.apk. Despite all apps being downloaded/installed to my SD card, space was still at a premium and I had downloaded a third party dialer. I figured worst case, I could do a factory reset and/or could simply re-download the file (I was actually about to download a good backup program tonight after work, I've been busy the past two days and my anxiety to set up other stuff got the better of me). There was no immediate issue, but shortly later I got the dreaded 'com.android.apk has stopped' (or what not) message popping up constantly. I reset the device, it booted up but it was not reading my sim, and was missing icons. That's when I did something stupid-er. I found a Phone.apk file on the net, downloaded to my device, and copied it to the relevant directory.
Since then, when I boot up, first it shows that Android is upgrading, then it shows the 'unfortunately, the process com.android.apk has stopped.' I click 'Okay,' and it keeps popping up. I wasn't able to delete the wrong Phone.apk as there was not enough time for a longpress between error messages. I was able to initiate a factory reset - I was rather relieved - I had learned a bit the past day or two via trial and error, and I would be able to re-do everything perfectly this time.
But the factory reset did not revert to the right 'Phone.apk' file. So the problem still exists....
If anyone can help me, I would be oh so grateful....thanks...
A factory reset clears all user data & apps. If you deleted the phone app from system, you will have to reflash a stock zip, which I'm assuming you don't have, or find the stock apk and put it back in the right place as a system app.
If you have Titanium Backup you can use that to do it, provided you can find the stock phone apk.
Well, a problem is, I doubt that I will be able to find any ROMs or Phone.apk's for my device. At least not for a little while. There are some ROMs out there I believe for the original Blu Touch Book - but the original has a diff processor and is running Froyo rather than ICS.
Now, if I somehow can find a workable Phone.apk or a workable ROM, how do I go about flashing/copying? I can hook up to a PC (though I'm not aware of any USB storage mode that I can turn on), but the phone itself is just about unusable unless I can manage to delete the wrong Phone.apk file, as long as the file is simply missing it will boot up without the relevant features. And - let me repeat that I did a factory reset to try and fix this - it didn't fix my problem but it erased my apps and my root access....I can probably restore root but it won't stop the warning notification from popping up non-stop.
I was able to boot into safe mode previously - but it didn't help. If there is an applicable recovery mode, I can't figure that out. To my knowledge, there is no USB Mass Storage option that I can turn on.
I purchased from Amazon, so luckily I can return the item, and worst case they review it's condition and charge a restocking fee. Of course, I was looking forward to receiving this device for more than a week and have been obsessed with it since it's arrived...and I am also temporarily back to using Sprint (in Phoenix) on a 3.5" Windows Phone (I am an ex Windows Mobile fan boy, Windows Phone disappoints) after experiencing 6 MB/s 3G speeds on T-Mobile for a day or so (on a 7 inch screen and on a prepaid plan far cheaper than what I pay Sprint). I was about to port my number. Basically I am depressed. An irony here - I'm pretty sure Amazon sold me a used device that was advertised as new. On initial boot, the Android set up program did not launch. Upon my first factory reset, the set up program launched, and the dialer skin was different than what it was out of the box. The 'refuse product if this seal is broken' sticker on the packaging was partially broken, too, although it appeared to be partially in tact. But now if I try to play that angle, I come off like a scam artist...
Anyways thank you very much for your reply...all attempts to help are appreciated quite a bit...
Taking things one step at a time, let me simplify my request:
How can I delete (or replace) a system file from my device (in this case, the incorrect Phone.apk) remotely via a USB connection? I have the sdk installed on my computer, I can connect the device to my computer, but I can't really use the device until the file is deleted. Is it possible to push via ADB? Something to that effect? Will the 'push <local> <remote>' command work even if I do not have root access? What syntax is used to specify the path? Is it possible to simply delete a file without replacing it?
Does the Phone.apk file have to be specific to my device or could it be specific simply to my mobile carrier/frequency bands and/or ICS? I realized the Phone.apk file I copied to the device earlier was for the Huawei m835, a CDMA phone running Froyo...
Or, am I simply SOL?
Thanks....
One of the things about Android devices, as a former Windows Mobile user also, is that factory resets work differently as you've found out the hard way. In WM you could delete any system file you wanted and a hard reset would restore it. On Android if a required /system file is deleted you are SOL unless you have a way of restoring a backed up version. Its highly recommended IMO to have a working recovery like CWM, TWRP and a backup before you go messing around with /system files. But with a generic android device its probably not possible to find a recovery to install. You cannot write to the /system directory without root access, adb will give you an error. You may be able to use a phone.apk from another device with the same version of android.
I did find a Phone.apk from a device with the same manufacturer, on the same frequencies, with the same screen res, running the same version of Android. I have the full System/App folder if needed.
And I may have restored root access using UnlockRoot (I have read iffy things about the program but again it's all that worked for me initially). (EDIT - I do now have root access, I was able to verify the Superuser app on the device)
However when I load the SDK and type in 'adb root,' after the 'daemon started successfully,' I quickly get an 'error: closed.' And then when I try to push the Phone.apk file to the relevant folder, I get 'failed to copy / permission denied' (EDIT as I was warned of)
Is there anything I can load onto my SD card to help? I can run probably install an APK off of my storage card. Although I am very limited in what I can do - between error messages I can only get in one quick touch of the screen (and it usually takes a few tries per touch)...I can't do anything that requires a long-click...and I had also deleted the stock keyboard and the stock browser...limits me further...
Now, if I can delete my current Phone.apk and upload the stock keyboard, I am certain I can figure this out. There has to be some way to do this....
EDIT// I packed it up to return to Amazon. If there was a solution out there, oh well...
Like I said you may have been able to use Titanium to install it as a system app and that may have taken care of things once you set it as the default app and/or removed the faulty one.
^^ Right, but the challenge was installing Titanium Backup, and then using it while the error notification popped up on the screen every split second. Unless I am missing something, only way to download it would have required me to buy a Bluetooth keyboard and struggle to pair it so I could type (I had a USB keyboard that didn't work), maybe reassociate my device with my Google account (struggling to type letter by letter between each 'OK' click), have the apk sent to my device over unsecured wifi, put the .apk on SD (or just delete the wrong apk and reboot), and then hope that I could use Titanium backup to do the trick without the ability to press anything on the screen for longer than a half second or so...
Actually, I guess that could have worked, provided the Bluetooth keyboard worked. Of course, there's the chance that the Phone.apk I found for the similar device, might not have worked. Anyways, late now. I have a new one on the way, and I was shipped a slightly used one to begin with anyways, might be for the better. I kinda feel bad that the phone is now 'defective' as a result of my impatience/etc but then again I didn't do anything that the instruction manual warned against, not to mention the instruction manual says a factory reset restores factory data, which I think infers that it restores essential system components. And as much as I was an idiot, I don't do anything which should have caused a nearly non-recoverable error. That's on Google's end. Google doesn't even really discourage rooting and if you allow Android on a device with 512MB rom...
Learning experience. One of the first things I do when I get my new one, I download a backup program and find out if there is a recovery mode. In any event, I won't make the same mistakes twice. Thanks to those who replied or considered replying. Anybody has tips for the future, that aren't obvious or easily found, feel free...
If u r rooted this is very easy.
Open sdk and type su if u get "#" then u r rooted.
If so let us know
---------- Post added at 10:05 AM ---------- Previous post was at 09:34 AM ----------
as a rethought I see u deleted system app so u were rooted
---------- Post added at 10:21 AM ---------- Previous post was at 10:05 AM ----------
Firstly adb pull the file "/proc/mounts" open it using notepad and see how system is mounted.
then remount system as rw using
"mount -o remount,rw -t yaffs2 /
<path to your system> /
system"
Now u can delete stuff or add new stuff without perm error
---------- Post added at 10:24 AM ---------- Previous post was at 10:21 AM ----------
Or just download this . Maybe it'll work http://www.totalcmd.net/plugring/android_adb.html
caponer said:
Or just download this . Maybe it'll work http://www.totalcmd.net/plugring/android_adb.html
Click to expand...
Click to collapse
Eh, I already sent the phone back to Amazon. This, however, looks like a useful something to have access to in the future. Thank you for the link...
No way. Come on,why did u send it to amazon when u had me right here we could have fixed this so easily.
thref23 said:
Hey guys....here's my situation.
I bought a Blu Touch Book 7.0 plus off of Amazon. Got it two nights ago. It's a true phablet. 512 RAM / 512 ROM - I was a little concerned but figured as long as I could root it, I was good to go.
Anyways - no I am not looking for a root. I was able to root it relatively easily after an initial failed attempt which required a factory reset - if anyone is interested, it required PDANET+ & UnlockRoot, SuperOneClick and other methods failed. I threw in a class 10 SD, and modded Android so all apps would be downloaded/installed to my SD card (I did this using the SDK & command prompt in USB debugging mode). I had researched apps previously and began to furiously download and tweak. I threw in a T-Mobile SIM, and everything was going well, I was very happy. It actually seems to be a well made device, though it's a little bulky and the phone function works much better with a bluetooth headset.
Then, I deleted Phone.apk. Despite all apps being downloaded/installed to my SD card, space was still at a premium and I had downloaded a third party dialer. I figured worst case, I could do a factory reset and/or could simply re-download the file (I was actually about to download a good backup program tonight after work, I've been busy the past two days and my anxiety to set up other stuff got the better of me). There was no immediate issue, but shortly later I got the dreaded 'com.android.apk has stopped' (or what not) message popping up constantly. I reset the device, it booted up but it was not reading my sim, and was missing icons. That's when I did something stupid-er. I found a Phone.apk file on the net, downloaded to my device, and copied it to the relevant directory.
Since then, when I boot up, first it shows that Android is upgrading, then it shows the 'unfortunately, the process com.android.apk has stopped.' I click 'Okay,' and it keeps popping up. I wasn't able to delete the wrong Phone.apk as there was not enough time for a longpress between error messages. I was able to initiate a factory reset - I was rather relieved - I had learned a bit the past day or two via trial and error, and I would be able to re-do everything perfectly this time.
But the factory reset did not revert to the right 'Phone.apk' file. So the problem still exists....
If anyone can help me, I would be oh so grateful....thanks...
Click to expand...
Click to collapse
Could you share how you did a factory reset please?
wizardofkoz said:
Could you share how you did a factory reset please?
Click to expand...
Click to collapse
Settings/Backup & reset/Factory data reset
Rooting Help
"I was able to root it relatively easily after an initial failed attempt which required a factory reset - if anyone is interested, it required PDANET+ & UnlockRoot, SuperOneClick and other methods failed."
Can you tell me how did u root it exactly because i am trying all new ways and nothing is working they just cant pick up this phablet.
androidhelp1234 said:
"I was able to root it relatively easily after an initial failed attempt which required a factory reset - if anyone is interested, it required PDANET+ & UnlockRoot, SuperOneClick and other methods failed."
Can you tell me how did u root it exactly because i am trying all new ways and nothing is working they just cant pick up this phablet.
Click to expand...
Click to collapse
I installed PDAnet+ on my phone & PC (as a means of installing a driver for the TB Plus). Then, I ran a program called 'UnlockRoot,' followed instructions, and I had root. UnlockRoot v3.1 is what is installed on my computer.
I moved on awhile ago to the Galaxy Tab 3 7.0 (Galaxy Tab 4 7.0 would be my best recommendation for a budget phablet). The Touch Book plus only held up so well (though I still have it and it still works albeit with no speaker and a screen that needs to be color-filtered due to a mysterious type of screen damage).
DOH!
thref23 said:
I installed PDAnet+ on my phone & PC (as a means of installing a driver for the TB Plus). Then, I ran a program called 'UnlockRoot,' followed instructions, and I had root. UnlockRoot v3.1 is what is installed on my computer.
I moved on awhile ago to the Galaxy Tab 3 7.0 (Galaxy Tab 4 7.0 would be my best recommendation for a budget phablet). The Touch Book plus only held up so well (though I still have it and it still works albeit with no speaker and a screen that needs to be color-filtered due to a mysterious type of screen damage).
Click to expand...
Click to collapse
After so many weeks of hunting around and asking help on forums *which no one was able to help* i stumbled across this which i hope other will find and find useful to them to!
mobiledriverfree.blogspot.com/2015/09/blu-touchbook-g7-pc-suite-and-usb.html
This not only aloud FULL root access within 3 mins, but also gave full super user, was able to retreive lost files, rebuild the software, and reboot the phone. (not to meantion remove ALL the bloatware freeing up half the phones storage)
Enjoy!!!
LeeMarden said:
After so many weeks of hunting around and asking help on forums *which no one was able to help* i stumbled across this which i hope other will find and find useful to them to!
mobiledriverfree.blogspot.com/2015/09/blu-touchbook-g7-pc-suite-and-usb.html
This not only aloud FULL root access within 3 mins, but also gave full super user, was able to retreive lost files, rebuild the software, and reboot the phone. (not to meantion remove ALL the bloatware freeing up half the phones storage)
Enjoy!!!
Click to expand...
Click to collapse
You do realise that this thread is 3+ Years old , right ?
Been looking around a lot here to find a solution and I see a few with the same problem but have never come across a solution yet.
I had my Kindle HDX 8.9 Apollo (3rd Gen) running fireOS 4.5.5.1. Installed Kingroot, rooted the device fine. I installed safestrap 4.0.1 B03 and it installed fine, was prompted for root access, allowed it and was able to install recovery. However when I either power off and or within safestrap select reboot to recovery i am stuck at the grey fire loading screen. I have to hold power button kill it, turn it back on go through the safestrap loading screen hit continue or just let it load. Then I get back to FireOS. during boot at the sfestrap screen i hit recovery goes to black screen and eventually have to hold power to kill it and reload again.
I read another post with some similar issues. The issue they had was the system folder was out of room and removing some files cleared up the issue. So i uninstalled safestrap, unrooted and uninstalled king root. Loaded in to the kindle recovery mode and reset to default.
I then proceeded to just use kingroot (root successful) loaded safestrap and rebooted ... same exact issue on freshly restored fire HDX.
I have to be missing something, I have been reading all day about different issues and trying to get past this to install CM11 on the device. Just cant get past this issue to backup and continue the process.
More info:
Safestrap boot screen shows safestrap :disabled
I can provide ADB info if needed.
Any suggestions?
Aescher75 said:
Been looking around a lot here to find a solution and I see a few with the same problem but have never come across a solution yet.
I had my Kindle HDX 8.9 Apollo (3rd Gen) running fireOS 4.5.5.1. Installed Kingroot, rooted the device fine. I installed safestrap 4.0.1 B03 and it installed fine, was prompted for root access, allowed it and was able to install recovery. However when I either power off and or within safestrap select reboot to recovery i am stuck at the grey fire loading screen. I have to hold power button kill it, turn it back on go through the safestrap loading screen hit continue or just let it load. Then I get back to FireOS. during boot at the sfestrap screen i hit recovery goes to black screen and eventually have to hold power to kill it and reload again.
I read another post with some similar issues. The issue they had was the system folder was out of room and removing some files cleared up the issue. So i uninstalled safestrap, unrooted and uninstalled king root. Loaded in to the kindle recovery mode and reset to default.
I then proceeded to just use kingroot (root successful) loaded safestrap and rebooted ... same exact issue on freshly restored fire HDX.
I have to be missing something, I have been reading all day about different issues and trying to get past this to install CM11 on the device. Just cant get past this issue to backup and continue the process.
More info:
Safestrap boot screen shows safestrap :disabled
I can provide ADB info if needed.
Any suggestions?
Click to expand...
Click to collapse
A stock factory reset (misnomer) does not touch the system partition; it only flushes the data partition. While I am not sure what is causing the problem with Safestrap recovery insufficient space in the system partition would certainly do it. Once rooted you can use ES File Explorer or similar tool to review the contents and identify potential candidates for removal. IMPORTANT: Don't delete anything without verifying the file is safe to remove. Also don't mess with permissions or try to edit build.prop. As you are probably aware even the slightest abnormally in the system partition can cause FireOS not to boot which is usually fatal on this device.
Davey126 said:
A stock factory reset (misnomer) does not touch the system partition; it only flushes the data partition. While I am not sure what is causing the problem with Safestrap recovery insufficient space in the system partition would certainly do it. Once rooted you can use ES File Explorer or similar tool to review the contents and identify potential candidates for removal. IMPORTANT: Don't delete anything without verifying the file is safe to remove. Also don't mess with permissions or try to edit build.prop. As you are probably aware even the slightest abnormally in the system partition can cause FireOS not to boot which is usually fatal on this device.
Click to expand...
Click to collapse
Ok thanks Davey I will take a look at the system partition and clean anything up I can. Maybe that is the problem I am still fighting with just a space issue. I will give it a try and report back.
Davey126 said:
A stock factory reset (misnomer) does not touch the system partition; it only flushes the data partition. While I am not sure what is causing the problem with Safestrap recovery insufficient space in the system partition would certainly do it. Once rooted you can use ES File Explorer or similar tool to review the contents and identify potential candidates for removal. IMPORTANT: Don't delete anything without verifying the file is safe to remove. Also don't mess with permissions or try to edit build.prop. As you are probably aware even the slightest abnormally in the system partition can cause FireOS not to boot which is usually fatal on this device.
Click to expand...
Click to collapse
Im looking through system using es file explorer any suggestions on what to dump? Is the system "partition" just items under the system folder?
Just trying to be careful on what i get rid of. Is there a list of items published in a stock Fire HDX by chance? Would be nice to have something to look at and compare.
Aescher75 said:
Ok thanks Davey I will take a look at the system partition and clean anything up I can. Maybe that is the problem I am still fighting with just a space issue. I will give it a try and report back.
Click to expand...
Click to collapse
Aescher75 said:
Im looking through system using es file explorer any suggestions on what to dump? Is the system "partition" just items under the system folder?
Just trying to be careful on what i get rid of. Is there a list of items published in a stock Fire HDX by chance? Would be nice to have something to look at and compare.
Click to expand...
Click to collapse
No standard list of folders/files that I am aware of.
Let's verify whether space is really an issue. Recall I'm not sure what is causing the problem w/Safestrap although it has been reported before.
Grab the following app that will help you visualize space in the system partition (apkmirror is a well regarded repository for Android apps):
http://www.apkmirror.com/apk/ivan-volosyuk/diskusage/
Check free space in under /system mount point. Tap and pinch-zoom as needed. If > 100MB you should be fine. Don't delete anything just yet. Just looking ...
Davey126 said:
No standard list of folders/files that I am aware of.
Let's verify whether space is really an issue. Recall I'm not sure what is causing the problem w/Safestrap although it has been reported before.
Grab the following app that will help you visualize space in the system partition (apkmirror is a well regarded repository for Android apps):
http://www.apkmirror.com/apk/ivan-volosyuk/diskusage/
Check free space in under /system mount point. Tap and pinch-zoom as needed. If > 100MB you should be fine. Don't delete anything just yet. Just looking ...
Click to expand...
Click to collapse
Man this app is awesome! I have included some screenshots of the /system mount point ... there is some issues here for sure. All them teeth and no toothbrush .. I have attached a few screenshots to show what the system mount point looks like. I drilled into a few of the more expensive folders to show more detail. Let me know if you can see them ok, or need to drill in deeper to them.
Aescher75 said:
Man this app is awesome! I have included some screenshots of the /system mount point ... there is some issues here for sure. All them teeth and no toothbrush .. I have attached a few screenshots to show what the system mount point looks like. I drilled into a few of the more expensive folders to show more detail. Let me know if you can see them ok, or need to drill in deeper to them.
Click to expand...
Click to collapse
Good stuff; was able to view the images fine. You don't need a ton of free space for Safestrap Recovery. Suggest deleting a couple benign Amazon apks in the priv-app folder such as weather and calculator. Don't go crazy or clobber apks that don't have clear function. Again, you just need enough space for Safestrap. The rest of the clutter in /system will get flushed with the installation of a custom rom.
Davey126 said:
Good stuff; was able to view the images fine. You don't need a ton of free space for Safestrap Recovery. Suggest deleting a couple benign Amazon apks in the priv-app folder such as weather and calculator. Don't go crazy or clobber apks that don't have clear function. Again, you just need enough space for Safestrap. The rest of the clutter in /system will get flushed with the installation of a custom rom.
Click to expand...
Click to collapse
OK few things. I was able to free up 110 MB of /system space these are the apk's i used titanium to backup and then uninstalled:
Weather
Audible
Contacts
Calculator
Maps
Kindle Tutorial
Calendar
Contacts
Goodreads
Nuance Dictation
And the Kindle Office App
I rebooted and the fire came up (shew)
I now have 110 MB free. So I rebooted from safestrap into recovery and same got the grey fire logo and seemed to lock up. So held power rebooted got the safestrap screen (Still showed disabled) Back in fireOS.
I unstalled recovery in safestrap
uninstalled Safestrap
went in to ADB and reinstalled safestrap
Installed recovery inside safestrap
rebooted to recovery
got the grey fire again and presto there is the recovery screen.
So I think I am ready to make a backup and find that awesome walk - through you did and follow it along.
Pretty stoked!! Thanks for the hand with this, I am sure I am just beginning the fun!!
Any suggestions on the ROM?
Aescher75 said:
OK few things. I was able to free up 110 MB of /system space these are the apk's i used titanium to backup and then uninstalled:
Weather
Audible
Contacts
Calculator
Maps
Kindle Tutorial
Calendar
Contacts
Goodreads
Nuance Dictation
And the Kindle Office App
I rebooted and the fire came up (shew)
I now have 110 MB free. So I rebooted from safestrap into recovery and same got the grey fire logo and seemed to lock up. So held power rebooted got the safestrap screen (Still showed disabled) Back in fireOS.
I unstalled recovery in safestrap
uninstalled Safestrap
went in to ADB and reinstalled safestrap
Installed recovery inside safestrap
rebooted to recovery
got the grey fire again and presto there is the recovery screen.
So I think I am ready to make a backup and find that awesome walk - through you did and follow it along.
Pretty stoked!! Thanks for the hand with this, I am sure I am just beginning the fun!!
Any suggestions on the ROM?
Click to expand...
Click to collapse
As you know your choices are limited to HDX Nexus and CM-11. I use both on different devices. Both adaptations are stable KitKat builds with proven track records. I have a slight preference for Nexus on this device as makes best use of hardware resources (IMHO) and has the greatest compatibility with Xposed modules like GravityBox which significantly extends the already excellent UI. Toss in Nova, Google Play Services and Greenify and you have a nice device that rivals Lollipop/Marshmallow equivalents.
Be sure to review the HDX Nexus OP and Safestrap v4 best practices before proceeding. Highlights:
- no need to flash GAaps or SuperSU with this rom; both are built-in
- be sure to backup your current FireOS build from within Safestrap and store the archive on another device
- be sure to perform a factory reset (wipe) from WITHIN Safestrap prior to flashing a *new* rom
- you cannot communicate with the outside world from with Safestrap; all files must be copied to device in advance
- Safestrap is a capable but sensitive environment for hosting custom roms; it is NOT a full recovery, hence ...
- IMPORTANT: never perform a factory reset from the stock recovery menu with Safestrap v4 installed (instant brick)
- IMPORTANT: always keep a copy of the Nexus installation zip on your device for emergency recovery
- IMPORTANT: do not create/use secondary slots; only flash roms to the STOCK slot (overwrites FireOS)
Any questions bounce back. Several respected contributors monitor these forums and more than happy to assist as needed (and keep you out of deep doo-doo).