Related
I've considered rooting and installing a custom ROM dozens of times ever since I got my Droid X back in August and I've finally decided I'm just going to do it, but i just want to double check a few things before I root my phone and install Fission:
1. I know that rooting voids your warranty, but if I have problems with my phone and I end up needing repairs, can I just unroot my phone back to stock and still have my phone be covered under the warranty?
2. Will my phone be secure rooted with a custom ROM? I don't want people having access to my personal info contact data, and my passwords.
3. If I Overclock to say 1.2 or 1.3 Ghz with ULV, will I have stability problems with demanding 3D games or other demanding apps?
4. After I root and install my Custom Rom, will I need to reactivate my phone or need to re-add my phone contacts/apps?
5. Will Z4Root work on system version 2.3.340?
I have unrooted and exchanged under warranty with no problems. Your phone will be just as secure. 1.2-1.3 are very stable on my phone. If you do have to reactivate it's as easy as dialing *228 and following the prompts. If your contacts are "google" contacts they'll return to your phonebook. Your apps from the market shall return without a problem. And yes, z4root will work with your system version.
Sent from my DROIDX using Tapatalk
I am having difficulty rooting my droid x. I am an android noob, but am a pretty savvy user. I used z4 (permanant) and it says it has been rooted when i launch the app. However i see no appreciable difference in access. My terminal still shows a $ prompt and i cannot uninstall verizons crapware. I used rage against the cage prior to z4 with similar results, but i was able to at least get temporary su access and install the bootstrap recovery and perform a system level backup. It reverted to user access after rebooting. Please help.
Superuser confirmation
alright, if you want super user privileges in terminal type "su", then once you hit enter, you get "#" instead of "$" To test if you have root access, first check app drawer for "Superuser" if its there, open an app that requires it, (wifi teather, root explorer, rom manager to name a few) you should get a pop up similar to this
http://www.google.com/imgres?imgurl...=1&ndsp=12&ved=1t:429,r:8,s:0&biw=888&bih=638
that would be a diffinitive confirmation that you have superuser permissions.
The way I remove verizons crap once rooted, is to use root explorer, go to system/app and find the .apk files you want to remove. There are lists around the forums what is safe to remove. I highly recommend simply renaming the files. For example, the 3g hotspot app is called mynet.apk, so I would just rename it to mynet.bak, or mynet.apk.bak, really anything that lets you know what it is, but removes the .apk extension.
Ok, I have confirmed su access, but am unable to rename any of the offending .apk's. I am simply told that the operation was unsuccessful. I have tried a couple of different file managers, as well as trying from a terminal, still no luck. I like 2.2.1 alright, but if i can't control what apps are running on my phone with root access, I may want another ROM. Any suggestions are appreciated, aswell as any links to a rom installer that is pc-less.
I usually rename apk's from Root Explorer, just prefer the graphical interface, so I can't really help you on the terminal process.
Rom manager is "pc-less" although most roms are posted in forums first it is often the easiest route, also lets you make backups and restore. There are a few posts around on how to install a rom you might want to read first. Also, you should find the thread for the rom before you flash it, in favor of size and speed, some developers go down to bare minimum and may remove something you need/want.
I have not used it, but I hear Titanium Backup allows you to "Freeze" apps, so that is a possible route also.
2.2.1 is not exclusive to people running official vzw builds, many of the roms on the forum (and rom manager) are running 2.2.1, so you will not be taking a step back to an earlier release.
SharkBaitDave said:
I usually rename apk's from Root Explorer, just prefer the graphical interface, so I can't really help you on the terminal process.
Rom manager is "pc-less" although most roms are posted in forums first it is often the easiest route, also lets you make backups and restore. There are a few posts around on how to install a rom you might want to read first. Also, you should find the thread for the rom before you flash it, in favor of size and speed, some developers go down to bare minimum and may remove something you need/want.
I have not used it, but I hear Titanium Backup allows you to "Freeze" apps, so that is a possible route also.
2.2.1 is not exclusive to people running official vzw builds, many of the roms on the forum (and rom manager) are running 2.2.1, so you will not be taking a step back to an earlier release.
Click to expand...
Click to collapse
If you are trying to rename apps in the /system/app portion of the OS, you will need to mount /system as RW first.
from terminal: mount -o rw,remount /dev/block/mtdblock4 /system
After it has been mounted read-write, you should be able to rename...
to remount as read-only: mount -o ro,remount /dev/block/mtdblock4 /system
zwade01 said:
I have unrooted and exchanged under warranty with no problems. Your phone will be just as secure. 1.2-1.3 are very stable on my phone. If you do have to reactivate it's as easy as dialing *228 and following the prompts. If your contacts are "google" contacts they'll return to your phonebook. Your apps from the market shall return without a problem. And yes, z4root will work with your system version.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Thank you for your response. Just out of curiosity, did you (or anyone else for that matter) have to reactivate your phone after rooting and installing a custom ROM? I'd rather not have to re-activate my phone every time I want to update a ROM or change to a different ROM.
Thank all of you for the great info. Here's what I've learned after a day of rooting and romming: titanium freezes apps only in the paid version, z4 was the most user friendly app for rooting noobs, milestone overclock works well if you have the patience to lock up your phone several times finding the right settings, and I'm digging apeX 1.3.1. Thx to everyone for your help, i will definately be checking here frequently. One last question: where might i find a side by side comparo of roms with things like features and memory footprint, etc.? Or am I asking for too much. Im not scared of the search button, but i will defer to the more experienced of you. Thanks again.
galaga4991 said:
Thank you for your response. Just out of curiosity, did you (or anyone else for that matter) have to reactivate your phone after rooting and installing a custom ROM? I'd rather not have to re-activate my phone every time I want to update a ROM or change to a different ROM.
Click to expand...
Click to collapse
I used rom manager to load apeX 1.3.1 and did not need to #228. I did not clear the user data or cache, but I do not know if that affected my results or not. Your mileage may vary.
stpvapor said:
Thank all of you for the great info. Here's what I've learned after a day of rooting and romming: titanium freezes apps only in the paid version, z4 was the most user friendly app for rooting noobs, milestone overclock works well if you have the patience to lock up your phone several times finding the right settings, and I'm digging apeX 1.3.1. Thx to everyone for your help, i will definately be checking here frequently. One last question: where might i find a side by side comparo of roms with things like features and memory footprint, etc.? Or am I asking for too much. Im not scared of the search button, but i will defer to the more experienced of you. Thanks again.
Click to expand...
Click to collapse
I don't know that anyone has really done a side by side per say. Since you say you are apeX, then if you are looking for more ROM's that contain blur features, then I would recommend looking into ZapX Bazinga, or Fusion (from the same creator as Fission, but just with blur). I have not worked with any of the Blur ROM's so far...
If you are looking for ROM's that do not have blur, then the big ones are Liberty, Fission 2.5.7, GummyJar 2.5, and Rubix Focused 1.9.5. Liberty is the big one right now, because it just came out and combines the great talents of Kejar31 and Jrummy. Most others I believe are using Fission. All are great choices, as the dev's do some AMAZING work.
Each has their owns unique feel...so I woudl recommend just digging through each thread for their respective ROM's as they usually include what components are built into each ROM on the original post of each thread.
Hope this helps somewhat =)
another ROM to try is DarkSlide. It comes in both flavors, Blurred & Blurless. It's fast, stable & well supported. You only have to re-activate if you wind up bricking your phone & have to flash an SBF. My advice it to spend the $$ on DroidXBootstrapper (available in the market) to make a nandroid backup prior to flashing your new ROM. This way you have a base to go back to in the event you run into problems, or want to try multiple ROMS. One other suggestion is to rename each backup into something that will let you know what the backup actually is, like StockROMBU or the like.
I have seen all the threads about apk`s that can be renamed or removed froyo 2.2 on a few different websites.
could someone make a current one for GingerBread 4.5.602 now that we have a working root?
would very much appreciate it as i dont think all the files are the same as they used to be in froyo 2.2
there are so many threads on what to remove and what not to remove from all around...
no one has made a thread about .apk`s for 4.5.602....so someone has a chance to be the first.
make a new thread or use this one i dont care...in the end i just want to know what we can remove and what we cant.
the names that root uninstaller shows would be great if someone could cross refrence to what the actual .apk is.
thanks
Bloatware .602 APk's that can be removed...
I would be THRILLED to be able to get a list of bloatware .602 APk's that can be removed without affecting the OS or any 'tangential' functionality. I prefer to stick with the rooted stock .602 ROM...
Anybody have any ideas?
a first-must-know
* preventing subsequent OTA "upgrades"
lest they kill this new root
How to stop OTA upgrades
I use Titanium Backup Pro - it's not perfect, but darn good. I started getting the OTA upgrade from Verison in a popup message, with a timer on it. I could click yes to do the upgrade or no to not do it, and the time was counting down in seconds at which point when it reached 0 it was going to do the upgrade if it did not get a response. I got this repeatedly.
I saw another thread that explained that if you 'freeze' (within Titanium Backup Pro) the application named "Updater 2.3.3" then this would not happen any more. That resolved my issue. This did not have any effect on the upgrades for which I got notices and could check on from the Amazon App Market or the Google Marketplace.
What bloatware can be removed? I have removed "City ID" and it has not seemed to affect me.... anybody know what else can be removed safely?
When I first looked around on the internet (and I'm good at doing search) I didn't find any lists of applications you can "freeze" (rename or move to another folder until you need them to update) specific to Droid X Gingerbread. Then while researching other issues I bumped into a fairly complete list (hope mods here don't mind me posting link!)
http://androidforums.com/droid-x-all-things-root/319383-apks-files-safe-remove-gingerbread-gingerblur.html
One issue I've run into is that if you use Titanium Pro you have to translate the actual .apk file name into what it displays. The Titanium devs should add the underlying apk file name to their list. I just upgraded to Pro because I've been using the product for backup/restore and was tired of renaming .apks to .apk.bak to freeze them. I like being able to have a freeze list I can save for the next time I upgrade. I suppose I should learn a bit more linux and create a script but...
Hi guys, I just got my Kindle Fire for xmas today. I want to root, but I've been reading the forum and see that a recent OTA update came out and there's been problems. I'm not super computer savy and I really don't want to mess it up. Do I have to wait for a new method to root? If someone wants to take a newb under their wing and tell me what roms etc I should get it would be much appreciated! Just a little overwhelmed with all the posts, not sure where to get consolidated current info.
I haven't even turned it on yet, I'm not sure if I should wait to turn it on, so that if it doesn't have the OTA update it doesn't send through as soon as I turn it on... whatever advice anyone can give would be much appreciated!
For Windows, Use this http://forum.xda-developers.com/showthread.php?t=1399889
Tired that version today works wel..
I haven't turned my Kindle on yet, can I avoid all the complications by somehow keeping it from getting the OTA update when it turns on? (I'm assuming it's not running 6.2.1 yet because that just came out?) I'm afraid to turn it on and I really want to play with it so if someone can let me know that would be great!
And if anyone wants to talk me through it, my screenname is Insidious Lily on aim, I need moral support/help, lol.
Just keep WiFi off until you are done... no issues.
Okay.. I'm a little overwhelmed by all the stuff in that post but I'll do my best. I'm in that IRC chat with another newb if you want to come help us, haha.
And high five, I have a HTC incredible too.
How about current method for Mac users?
ty!
So here's what I did...
(I have a Mac running snow leopard).
I downloaded the KindleFireRootMacLinux folder referenced in the old Mac root thread. This gets adb running on the mac. Use whatever system you need to get adb running on your PC. The command adb on the PC is replaced by ./adb-mac on the Mac.
Then I used the burrito root method and pushed super user to the kindle fire. using the adb commands from terminal.
Finally, I downloaded the google apps folder, installed Googleservicesframework *FIRST* and rebooted.
Then I installled the remainder of the apps EXCEPT market.
Then I used the ES Folder program with root explorer etc enabled to copy the market.apk file to system/app and changed permissions and ran it.
Everything worked fine.
THEN I installed DroidWall to take away the internet communication capabilities of all the Amazon apps (and browser) to try and keep another stealth push from Amazon from breaking root.
Someone else will have to link to the files because I haven't posted enough to include links.
Current root is BurritoRoot http://forum.xda-developers.com/showthread.php?t=1410223
if your particularly lazy Vashypooh's utility has been updated to use it here http://forum.xda-developers.com/showthread.php?t=1399889
I'll just join in to mention something the OP may not realize. Although I'm basically a newbie rooting the KF also, the current root method works with the new update from Amazon, so you don't have to worry about preventing the update to download. In fact, it's probably best to let it update first, otherwise you'll just have to repeat rooting it.
Anyone feel free to correct me if I have that wrong.
leebo said:
I'll just join in to mention something the OP may not realize. Although I'm basically a newbie rooting the KF also, the current root method works with the new update from Amazon, so you don't have to worry about preventing the update to download. In fact, it's probably best to let it update first, otherwise you'll just have to repeat rooting it.
Anyone feel free to correct me if I have that wrong.
Click to expand...
Click to collapse
Yep, but we did discover it doesnt work with 6.0 this morning. Seems what I used wasn't fully introduced until after 6.0
Ever since getting my Razr Maxx HD (XT926) three months ago I've been trying to get rid of the Navigation Bar on the bottom of the screen. I use Button Savior so I'm fine with having the NavBar controls disappear.
Among the most reliable remedies seemed to be upgrading to 4.1.2, at which point many people said that you could simply add the line "qemu.hw.mainkeys=1" to the end of your build.prop file in /system, reboot, and *poof* the NavBar would be gone. My phone, which I bought used, was running a leaked 4.1.1 so, once root for OTA 4.1.2 was discovered, I downgraded to 4.0.4, did the updates to that, then took the OTA upgrade to 4.1.1 (no problem), then took the OTA upgrade to 4.1.2 (no problem). So now I had the latest JB version offered for Verizon XT926 in the US. I know that I'd wiped data at least once along the way. The SafeStrap installation that I used to have was gone, as I expected. I assumed that my phone was as stock as it could be and thus ready for the build.prop edit.
I used the new procedure to root my XT926. At that point all I did was to download and install Root Explorer (needed to do the build.prop edit) and Button Savior (needed for navigation once NavBar was gone). In Root Explorer I navigated to /system, made it R/W, opened build.prop in the stock text editor, added qemu.hw.mainkeys=1 at the end, saved (which backed up the older version as expected), and rebooted.
The first thing I get when my phone boots up is the "SystemUI has crashed" error message. My NavBar is gone but so is my System Bar (a/k/a Notification Bar), which I need and want to be visible. I've read a TON about this and I'm pretty sure I've followed the instructions. Why is this not working for me?
I am just not smart enough to decompile and edit my framework-res.apk file (or whatever the name is) so I'm stuck trying to make the build.prop edit work. What could I be doing wrong?
(also, if I use one of the apps like FullScreen or BottomBar they produce the EXACT SAME result -- SystemUI crashes, NavBar disappears but so does System Bar).
cant help
it works for me as experted
Are you positive you entered it correctly?
Sent from my JokerMATRIX HD MAXX
deeje00 said:
Are you positive you entered it correctly?
Sent from my JokerMATRIX HD MAXX
Click to expand...
Click to collapse
He also tried an app which writes the line to the build.prop and got same results.
AFAIK I had crashes on ICS but since I'm on JB 4.1.2 I never had any issues...
Sent from my XT925 using xda app-developers app
Yes, the edit is entered correctly. I've checked that more times than you can imagine. And I've tried nearly every variation that's been suggested anywhere: with spaces before and after the "=", adding the line ending with "0" first then rebooting then changing the end to "1" then rebooting, putting an empty line at the end of build.prop before adding the edit. No change. Is there any history of an app interfering with this edit? I don't have anything exotic installed I don't think but I use a third party launcher (Go Launcher EX) and then a variety of apps, mostly audio/video, social media and a few basic games. I believe that changes to build.prop take place "below" that kind of activity, though, right? And besides, I made the edit before I installed any of that stuff. I may try a hard reset or something like that but if this works for everyone else then I must just be missing something.
I have had the exact same issue and done the same troubleshooting...sucks!
did you happen to check file properties after you saved, i remember back in the early days of Android if you edited a file, you had to change the properties back to the defaults, not sure if that is still the case, but worth a look.
It can't be done on any stock via build.prop only, and framework edits require a deodexed rom.
I recommend you install CM10 or 10.1. If you prefer safestrap over CWM, then you can use CM10, but without a camera. Fullscreen toggle works perfectly, and I'm able to use PDroid : )
I suppose I should be glad that at least *one* other person is having this problem. Means it's slightly less likely that I'm just incompetent.
As for changing file properties, I didn't change any properties to do the edit other than making /system "RW" in order to be able to edit the file. Could someone tell me what the default values are for build.prop? The most recent edit I've made always shows up correctly when I go back into build.prop, by the way, so I know I'm actually changing the file.
If a rooted stock 4.1.2 can't hide the NavBar with a build.prop edit then this is the first I've read about it, and I've read just about everything that I can find on this subject (including translations of non-English discussions, just in case I could get a new lead from them). Not saying that's not true, just not consistent with what I've read so far.
I'd love to install a CM ROM on my XT926. I've admired Cyanogenmod since I first started fiddling with my Nook Color some years ago. Their crew does some spectacular work. But -- no camera? No Bluetooth? Sometimes wifi or phone call problems? That's too much lost functionality for me. If those remaining few obstacles are someday overcome I'll be all over it though.
ONE LAST QUESTION -- I assumed that, if I "scrubbed" my phone down to the lowest level possible (wipe cache, wipe dalvic, wipe data) I would eliminate whatever weird impediment I have to getting the build.prop edit to work. Is there something else I can do to wipe the phone even MORE thoroughly?
The permissions are RW-R-R, I have had the issue with stock and custom roms (running Foot Through the Floor right now). I wasn't surprised when it didn't work with stock (silly Moto) and I was a little surprised when it didn't work with and of the custom roms I tried, I have no doubt it would work in CM.
I tried it out, it works but you need to reboot after edit, I hot booted and nothing changed, full reboot and it works. hope it helps you.
Just in case this makes the difference, can you tell me what distinguishes a "hot boot" from a "full reboot"?
Having issues myself. Have 4.1.2 rooted, RAZR HD. Added the line above to build . prop with "=0" first shutdown, started back up. Then changed to "=1" saved, shutdown and started back up. System UI FC's.
Wonder if it matters what launcher is being used. I am on GO Launcher. I say this since on home screen I see the GO Launcher menu show up just below bottom of my wallpaper but behind it. I can swipe up to bring up full menu but it is weird how it comes up in background on its own.
Anyone get it to work with GO Launcher?
Sent from my DROID RAZR HD using xda app-developers app
---------- Post added at 10:56 AM ---------- Previous post was at 10:54 AM ----------
Oh and does it matter where in build.prop the line goes? I just added to bottom. Thx.
Sent from my DROID RAZR HD using xda app-developers app
---------- Post added at 11:29 AM ---------- Previous post was at 10:56 AM ----------
lesdense said:
Yes, the edit is entered correctly. I've checked that more times than you can imagine. And I've tried nearly every variation that's been suggested anywhere: with spaces before and after the "=", adding the line ending with "0" first then rebooting then changing the end to "1" then rebooting, putting an empty line at the end of build.prop before adding the edit. No change. Is there any history of an app interfering with this edit? I don't have anything exotic installed I don't think but I use a third party launcher (Go Launcher EX) and then a variety of apps, mostly audio/video, social media and a few basic games. I believe that changes to build.prop take place "below" that kind of activity, though, right? And besides, I made the edit before I installed any of that stuff. I may try a hard reset or something like that but if this works for everyone else then I must just be missing something.
Click to expand...
Click to collapse
I just noticed this (missed it first scan through) that you use Go Launcher as well. I do also and am having same issue. I am going to try switching to Apex, Nova or other to see if that is the culprit. If so, I can most likely get used to another custom launcher to gain the extra space.
BUT if anyone doesn't have issues AND is using Go Launcher, please let us know so we can rule that out.
Thanks
I use nova pro and have the issues.
Sent from a non-apple device.
coolloser said:
I use nova pro and have the issues.
Sent from a non-apple device.
Click to expand...
Click to collapse
I just tried Apex Launcher and had same FC issue. So guess it isn't specific to any of the launchers (was a long shot anyway). This is just really weird. Some folks swear they have it running on stock 4.1.2 (OTA update) rooted, but many of us have the same and can't get it to work.
I saw one thread where someone mentioned you needed to make sure everything is stock, meaning using TB to unfreeze anything you had frozen, and then give it a go. Problem is I'll want to refreeze much of that bloatware from VZW so not sure if that helps or not.
So frustrating......
At this stage in the trail and error I wonder what other variables could be the key. It's not the version (4.1.2). It's not launcher (problems with Go, Apex and Nova plus the stock launcher). Making everything stock didn't help me -- I flashed a brand new version of 4.1.2, installed ONLY Button Savior (for navigation) and Root Explorer (to edit build.prop). Same problems as usual. I assume it's not the rooting utility as I believe only one exists.
OK, how about some weirder ideas. Has everyone done the build.prop edit with Root Explorer? Maybe there's a flaw in that tool. I just tried editing the build.prop to put IN the qemu.hw.mainkeys=1 line, then temporarily suspended root with VooDoo, then rebooted to see if it would behave if it thought it wasn't rooted. Same result. Maybe the guy saying you can't make this work on rooted stock ROMs was right Still, I'll keep looking, and sharing.
lesdense said:
At this stage in the trail and error I wonder what other variables could be the key. It's not the version (4.1.2). It's not launcher (problems with Go, Apex and Nova plus the stock launcher). Making everything stock didn't help me -- I flashed a brand new version of 4.1.2, installed ONLY Button Savior (for navigation) and Root Explorer (to edit build.prop). Same problems as usual. I assume it's not the rooting utility as I believe only one exists.
OK, how about some weirder ideas. Has everyone done the build.prop edit with Root Explorer? Maybe there's a flaw in that tool. I just tried editing the build.prop to put IN the qemu.hw.mainkeys=1 line, then temporarily suspended root with VooDoo, then rebooted to see if it would behave if it thought it wasn't rooted. Same result. Maybe the guy saying you can't make this work on rooted stock ROMs was right Still, I'll keep looking, and sharing.
Click to expand...
Click to collapse
Root Explorer is what I used.
For the other guy having trouble, it hasn't been mentioned yet; did you set the owner and group for the file to root? If the file was ever stored on the sdcard or pushed there then moved, those permissions might make a difference as well. Its a good security measure in the case that it isn't relevant in any case... don't want a wild website writing to your build.prop file, for example.
PantsDownJedi said:
Root Explorer is what I used.
For the other guy having trouble, it hasn't been mentioned yet; did you set the owner and group for the file to root? If the file was ever stored on the sdcard or pushed there then moved, those permissions might make a difference as well. Its a good security measure in the case that it isn't relevant in any case... don't want a wild website writing to your build.prop file, for example.
Click to expand...
Click to collapse
I used ES File Explorer (and then you have to use Root Explorer menu option to set r/w prior to opening build.prop).
Regarding the rest of the post above. Not sure what the question is. I never did anything to the build.prop file other than set ES File Explorer to r/w on everything, then edited the build.prop file, saved, checked to ensure it was edited right, then rebooted. So the 'file' has never been anywhere other than in /system. When I check the properties on the build.prop file I see rw- r-- r-- (this the same whether or not /system is set to RW or just RO). I believe these are correct (default) settings, but let me know if that is not correct.
Anyone out there that has this working on Stock 4.1.2 it would be nice to know more (i.e. is 4.1.2 the OTA or leaked version, did they use motochopper root method (only one I thought), persmissions on file, where did they place the qemu line in the file, etc, etc).
---------- Post added at 11:33 AM ---------- Previous post was at 11:21 AM ----------
PantsDownJedi said:
Root Explorer is what I used.
For the other guy having trouble, it hasn't been mentioned yet; did you set the owner and group for the file to root? If the file was ever stored on the sdcard or pushed there then moved, those permissions might make a difference as well. Its a good security measure in the case that it isn't relevant in any case... don't want a wild website writing to your build.prop file, for example.
Click to expand...
Click to collapse
BTW... anyone look into testing the framework-res.apk option? Sounds in-depth and much more work (not to mention chance of screwing things up). It would be new to me to decompile, etc, etc, but am not scared to try, just thought I would ask if anyone else already has. Also, not sure if that option is for the 4.1.2 OTA version (verizon in my case).
Thanks.
surfmly said:
I used ES File Explorer (and then you have to use Root Explorer menu option to set r/w prior to opening build.prop).
Regarding the rest of the post above. Not sure what the question is. I never did anything to the build.prop file other than set ES File Explorer to r/w on everything, then edited the build.prop file, saved, checked to ensure it was edited right, then rebooted. So the 'file' has never been anywhere other than in /system. When I check the properties on the build.prop file I see rw- r-- r-- (this the same whether or not /system is set to RW or just RO). I believe these are correct (default) settings, but let me know if that is not correct.
Anyone out there that has this working on Stock 4.1.2 it would be nice to know more (i.e. is 4.1.2 the OTA or leaked version, did they use motochopper root method (only one I thought), persmissions on file, where did they place the qemu line in the file, etc, etc).
---------- Post added at 11:33 AM ---------- Previous post was at 11:21 AM ----------
BTW... anyone look into testing the framework-res.apk option? Sounds in-depth and much more work (not to mention chance of screwing things up). It would be new to me to decompile, etc, etc, but am not scared to try, just thought I would ask if anyone else already has. Also, not sure if that option is for the 4.1.2 OTA version (verizon in my case).
Thanks.
Click to expand...
Click to collapse
I was kind of just pulling at straws, and trying to answer two posts at the same time, sorry for the confusion. My habit, especially before unlocking the bootloader, is to push things to the sdcard then moving them and setting the right permissions and assingining the correct group and user.
As you've explained things, I don't know why it shouldn't work. Mine is a 4.1.2 OTA. It was originally rooted before upgrading and using Voodoo root keeper but between that and Supersu paid version I was able to reinsert root again after a factory reset, which was a stroke of luck as others lost it. I don't think it would matter which root method is used but I could be wrong; esentially its just allowing us to access the build.prop file to edit at all. I don't remember if I had modified the build.prop before or after the reset. I know that it was working both before and after I unlocked the bootloader though. As for the placement of the line, I put it at the end. I also, out of habit, hit enter for a new line for this type of thing. Afterwards, though, there is now new things that Pimp My Rom has inserted (Some of the tweaks in that package are old and I'd advise people to stick with close to stock as possible when using it unless they know what those lines mean; and there's some build.prop myths still floating around XDA that are not good ones, one of which I know Pimp My Rom uses and looks pretty apealing to select). So, now I have some stuff after it. If there were other things added to your build.prop, then perhaps moving the line to the end of where the default configuration ended... grabbing at straws again with this last sentance but in the lack of information I'm just trying to be helpful
Perhaps if people also with this problem, in addition to answering your question about the root method they used, also posted which carrier branding they had it might reveal something, or rule it out. <-Put that in bold for you
I am VZW with Nova Pro, and I get the systemUI FC as well. After much research, I haven't heard of too many people with PHONES that have been successful in this hack, so I tried it on my GTab 2, and same thing.
After spending entirely too much time looking into this, I purchased Full!Screen+, set the apps that I wanted full screen, and I'm set (oddly enough, this didn't work on my GTab, so I also purchased Hide Bar for that device. I prefer FullScreen+ because the truth is, there's only certain apps that I care about being full screen (Netflix, games, youtube...).
The biggest problem with FS+ is that it hides the notifications. Honestly, I don't really care about that either when I'm doing one of these other activities. After all, we have a notification light.
I searched and could easily find stock build.props but I'm pretty sure than CM's is tweaked. Whilst messing with Android Tuner (just got the app, am more familiar with ROM Toolbox) and tapped one click optimization without thinking. Well, I've tried again and again (yes after a reboot too) to reset everything, but the build.prop just won't reset. I'm guessing for some reason it never backed up properly. Perhaps it was a mistake to kill the app when it was acting up and stuck on modifying the build.prop. Device boots fine, and works fine, but I wish to undo whatever was done. I like it the way it was with CyanogenMod originally anyhow. i don't want any unexpected surprises tweaking the build.prop. I have tweaked build.props before and actually do it with a zip to enable LTE, but no other tweaks. Like hiding notifications. So I am simply requesting an unmodified Cyanogenmod build.prop I can download and apply to my Nexus 4 to undo any unwanted changes. Preferably one from the 6/14/13 CM 10.1 Nightly (the latest one). Thanks!
MikeRL100 said:
I searched and could easily find stock build.props but I'm pretty sure than CM's is tweaked. Whilst messing with Android Tuner (just got the app, am more familiar with ROM Toolbox) and tapped one click optimization without thinking. Well, I've tried again and again (yes after a reboot too) to reset everything, but the build.prop just won't reset. I'm guessing for some reason it never backed up properly. Perhaps it was a mistake to kill the app when it was acting up and stuck on modifying the build.prop. Device boots fine, and works fine, but I wish to undo whatever was done. I like it the way it was with CyanogenMod originally anyhow. i don't want any unexpected surprises tweaking the build.prop. I have tweaked build.props before and actually do it with a zip to enable LTE, but no other tweaks. Like hiding notifications. So I am simply requesting an unmodified Cyanogenmod build.prop I can download and apply to my Nexus 4 to undo any unwanted changes. Preferably one from the 6/14/13 CM 10.1 Nightly (the latest one). Thanks!
Click to expand...
Click to collapse
Why not just download the CM zip that you would flash via recovery, unzip it, and look at the build.prop there?
kbeezie said:
Why not just download the CM zip that you would flash via recovery, unzip it, and look at the build.prop there?
Click to expand...
Click to collapse
I can do that too. Thanks. I will however upload it to Dropbox and share it here in case anyone runs into a similar issue I did. That way nobody has to download the entire thing for a single thing and add more stress to CyanogenMod's servers.
Build.prop for 6/14/13 CM 10.1 Nightly
Here. This is for future reference in case anyone else runs into the same issue.