Related
First time smartphone owner and first experience with android, so forgive my basic questions.
1) Can one view the important operating system directories, like System, without rooting? If so, how? And can you get write access?
2) What is the difference between firmware and baseband? Can they be updated independently? Can they be updated without rooting?
3) What is the general term for software like TouchWiz? Can you replace it without rooting? What happens to is when you install a different type?
Thanks in advance for your help.
to answer your first question, you can download an app called astro file manager from the market that will give you access to the directories you want, but i don't think you can have write access without root, but i could be wrong
second, not sure what the difference between firmware and baseband. pretty sure you need root to update the firmware though since there hasn't been an official release.
lastly, i think the term you're looking for is 'launcher'...you can download alternative launchers from the market. ADW launcher and Launcher Pro are probably the most popular. you can have them installed without actually replacing the Touchwiz launcher, but you won't have access to the Samsung widgets. you can also download an app called 'home switcher' to switch between the different launchers you have installed.
hope this helps. and, anyone feel free to correct me if i'm wrong
Thanks for the reply.
I have Astro File Manager, but I can't see the System dir. Any idea what I might need to do?
Are Launcher and Home Switcher Synonymous?
Home Switcher is an app that lets you move from LauncherPro, ADW and TouchWiz more easily.
DLarva said:
Thanks for the reply.
I have Astro File Manager, but I can't see the System dir. Any idea what I might need to do?
Are Launcher and Home Switcher Synonymous?
Click to expand...
Click to collapse
You won't be able to see the System dir without rooting. You might as well root if you want access to the System dir. I've had the G1, the Nexus One, the MyTouch Slide, and now the Vibrant and this phone is by far the easiest to root so far AND its reversible just in case you need to un-root to send it in for repairs or warranty claim. You can learn how to root here in xda but here's a link with step-by-step instructions.
http://tinyurl.com/2arangz
Thanks for the replies, this is clearing up a lot of things in my head. I'll be sure to check out that link. I was hoping to hold of rooting until we got froyo, but I'm guessing that won't be for a while.
DLarva said:
Thanks for the replies, this is clearing up a lot of things in my head. I'll be sure to check out that link. I was hoping to hold of rooting until we got froyo, but I'm guessing that won't be for a while.
Click to expand...
Click to collapse
I'm hearing Sept for froyo for us but if you root and keep the stock rom like I'm doing you should get the OTA update for froyo when they decide to send it out.
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.
New method.
I have figured out a safer way to install a custom launcher. Your device still needs to be rooted.
1- Download the launcher of your choice from the Play Store.
2- With a file manager of your choice navigate to data/app folder, this will have all the apk's you've downloaded from the Play Store. (the name of the apk will look different ie: nova launcher is named "com.teslacoilsw.launcher.apk" )
3- Move launcher apk to system/app folder install or reboot(the permissions should already be set to rw-r--r-- so no need to change them)
Personally I like using Rom Toolbox Pro/Lite(can be found in play store, i bought the pro version for more options), I have no affiliation but this app is great and you should check it out. It has every different tool for root users you can think of. In the App Manager section if you long press on any app there is an option to "convert to system app", no moving, cut/paste, or installing.
This should help avoid getting some screwed up apk file from an alternate source and messing up your device.
As always try at your own RISK.
I would recommend checking out this thread before messing around with your device:
http://forum.xda-developers.com/show....php?t=1930656
Can you specify which version of Go Launcher you used and where you obtained the apk from?
After having a near-brick experience attempting to install Go Launcher on my original Kindle Fire last year, I'd like to try it with something known to work.
Thanks in advance.
WillysJeepMan said:
Can you specify which version of Go Launcher you used and where you obtained the apk from?
After having a near-brick experience attempting to install Go Launcher on my original Kindle Fire last year, I'd like to try it with something known to work.
Thanks in advance.
Click to expand...
Click to collapse
I just googled go launcher ex apk. Dont think its ok to specify exactly which site i used(3rd maybe..) but I downloaded v3.13.
I completely feel ya, try at your own risk but definitely worked with mine.
I didn't need to restart but I can confirm go launcher and Nova are working. I'm sure any launcher will
Well maybe some of these other launchers are better but all I want is the android look to tell the truth with icons so ADW Launcher EX without rooting is fine by me to get away from the carousel.
Works great. Thank you.
robertc88 said:
Well maybe some of these other launchers are better but all I want is the android look to tell the truth with icons so ADW Launcher EX without rooting is fine by me to get away from the carousel.
Click to expand...
Click to collapse
For me its not even about which launcher is better they all have pros and cons, but i personally like to use my home button. With this process you can set the launcher as default. Not be bounced back to the stock launcher every time you use the home button and have to reload a custom launcher. Too much of a hassle for me and takes away from the experience.
This method also worked with Go Launcher HD, it looks better then then regular Go Launcher imho.
migjr415 said:
This method also worked with Go Launcher HD, it looks better then then regular Go Launcher imho.
Click to expand...
Click to collapse
It does i agree, but is there a way to hide the notification bar and action bar on hd version?
I didn't find the way to hide NAV bar. All works perfect with Go launcher HD. I am sure that nobody want to try removing NAV bar, cause it is a high risk of breaking your KFHD. Auto-hide in this case would be great, but i can't understand when NAV bar hides. I suppose it hides when there is in exit button, or return button in running apk. IMHO.
How do you change permission on a non rooted device. I downloaded the go launcher hd all v1.17. I tried rebooting and nothing. Can I do this on a stock fire. If so can you provide a step by step. I tried moving the apk to system/apps but says the apk cannot be moved. Thanks
Sent from my Kindle Fire HD using Tapatalk.
Melodycd said:
I didn't find the way to hide NAV bar. All works perfect with Go launcher HD. I am sure that nobody want to try removing NAV bar, cause it is a high risk of breaking your KFHD. Auto-hide in this case would be great, but i can't understand when NAV bar hides. I suppose it hides when there is in exit button, or return button in running apk. IMHO.
Click to expand...
Click to collapse
There is a setting in go launcher ex that allows you to hide nav and notification bars, the little tab is still visible at the bottom or side of screen so you can open them with ease. Gives the tablet a full screen. I love the look of the hd version but would rather have the full screen, wish the would put this option on the hd version
petes67bird said:
How do you change permission on a non rooted device. I downloaded the go launcher hd all v1.17. I tried rebooting and nothing. Can I do this on a stock fire. If so can you provide a step by step. I tried moving the apk to system/apps but says the apk cannot be moved. Thanks
Sent from my Kindle Fire HD using Tapatalk.
Click to expand...
Click to collapse
you cannot change permissions of system files or anything about them unless the device is rooted. This keeps the average person from screwing up there device.
Lockscreen?
Guys, have any of you had luck with the lockscreen for GoLauncher? I tried GoLocker and i had to go through the original Amazon Kindle Fire HD lockscreen and then to the GoLauncher Lockscreen. SO, basically, i had two lockscreens going on at once. Is there a fix for this?
klass
caponea6 said:
Guys, have any of you had luck with the lockscreen for GoLauncher? I tried GoLocker and i had to go through the original Amazon Kindle Fire HD lockscreen and then to the GoLauncher Lockscreen. SO, basically, i had two lockscreens going on at once. Is there a fix for this?
Click to expand...
Click to collapse
Happens with the KF 1st gen also but I never bothered with it. Might want to look into the KF 1st gen and see if anyone found a way around it.
onemeila said:
To get go launcher ex working on the KFHD I took these steps.(On rooted device)
1- download the Go launcher ex.apk from a third party (from play store will not work)
3- change permissions to rw-r--r--
2- using a file manager find the apk and move to system/app folder.
4- reboot the device.
When it reboots there should be a message saying "kindle is upgrading".
Then it should prompt you to pick which launcher you want to use.
If you did not get the latest version you can now go to play store and update.
I assume this will work for other launchers though i have not tried it.
Finally I feel like im using more of an android interface(at least until someone figures out this bootloader problem and i can flash cm10)
I just downloaded go launcher hd and did not change permissions, still worked. Could someone tell me if this is necessary. I just copied the permissions of the stock launcher when i loaded the ex version so i assumed it was necessary they were the same
Click to expand...
Click to collapse
I did step by step like you, but after restarted my KFHD freezing at KF logo, please help me to fix it.
First question, did you install this app in the /system/app folder, AFTER you placed it in there? You must install the launcher after it is placed and permissions are changed. It appears you may have a soft brick if that KFHD isnt booting at all.
caponea6 said:
First question, did you install this app in the /system/app folder, AFTER you placed it in there? You must install the launcher after it is placed and permissions are changed. It appears you may have a soft brick if that KFHD isnt booting at all.
Click to expand...
Click to collapse
yup, i copied it to /system/app folder,changed permission then installed from there,but when i restarted my KF, it just stop at logo kindle fire.so have any way to fix it?
probb said:
yup, i copied it to /system/app folder,changed permission then installed from there,but when i restarted my KF, it just stop at logo kindle fire.so have any way to fix it?
Click to expand...
Click to collapse
WELP! That doesn't seem like a great scenario to be in. If this was me, I would connect it to my PC and pray that while you're stuck in that logo limbo it would still give you connectivity. I would then go into the /system/app through your PC (on your KFHD directory) and physically remove the launcher files. Then try a restart.
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.
Hello to everyone,
as promised in my old thread, here is a first version of the automatic script to replace the launcher.
For now, firelauncher will be replaced with cyanogenmod's trebuchet.
If you want to use a different launcher, just replace the apk in the folder. (Remember to rename your new file to trebuchet.apk.)
No root is required for this to work.
This will not work with regular updates to 5.1.1!
Only for those who kept the old bootloader.
I will update the script to work with 5.1.1 later today
Remember to enable usb-debugging before running the script and make sure your PC is authorized.
There are automatic delays in the script, but check the necessary points when asked to do so, because boot-time can be really long sometimes.
As no one complained about the original script, I do believe that the basic steps are working properly.
However: I'm not responsible if anything goes wrong, please keep that in mind.
Credits go to @csolanol for finding root, @Awesomeslayerg for summing up the manual steps (If you don't like scripts, just take a look at his thread, it's good too), and to all those other people that were involved in working on boot.img and root.
Trebuchet is a cyanogenmod app, please refer to their website and xda-posts for further information.
Changelog:
V1.1:
Added some automatic delays and reduced the "pause"-commands, runs with a little less user-interaction.
Let's sum it up as more one.click.
V1.0:
Initial release
Planned features:
Allow the user to choose between trebuchet and any other launcher he copies into a special folder.
Make it easier, more documentation, clean up
Thanks for the package could come in handy for me with my daughters fire I did mine the longer way
Sent from my HTC One_M8 using Tapatalk
Okay good, should work for you as you already know the steps
If anything goes wrong booting the boot-firelauncher.img again and copying firelauncher.apk back in place will fix it.
But that should only be needed if connection is lost or any other unusual thing happens.
Hi, I'm new here. How can you write to the system folder and replace/rename a system launcher APK without root? I will try this on my fresh Ford running 5.0.1 later tonight.
cryophil said:
Hi, I'm new here. How can you write to the system folder and replace/rename a system launcher APK without root? I will try this on my fresh Ford running 5.0.1 later tonight.
Click to expand...
Click to collapse
With a custom boot.img that makes the system r/w.
Sent from my KFFOWI using Tapatalk
Vlasp said:
With a custom boot.img that makes the system r/w.
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
Thanks. If I use the custom boot.img to replace the launcher, Can I later recover my factory/standard tablet setup by erasing and resetting in the settings? Does the custom boot.img change the tablet permanently?
cryophil said:
Thanks. If I use the custom boot.img to replace the launcher, Can I later recover my factory/standard tablet setup by erasing and resetting in the settings? Does the custom boot.img change the tablet permanently?
Click to expand...
Click to collapse
You can reset it, by just ADB sideloading the firmware.bin through recovery. The custom Boot.img is temporary and only lasts for 1 boot, and will reset after you reboot.
Sent from my KFFOWI using Tapatalk
Vlasp said:
You can reset it, by just ADB sideloading the firmware.bin through recovery. The custom Boot.img is temporary and only lasts for 1 boot, and will reset after you reboot.
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
Ah, okay. I think I am learning. I read that a boot.img was also used to root the device. I assumed that changes were permanent. I think the difference is, the changes made after the boot.img can be made permanent using SU/root. But in this launcher replacement case, it is just a boot difference for that one boot-up.
It's a great way to test if I like the setup, then if so, I can root and change to that launcher/setup permanently using the root method discovered last weekend.
Thank you very much to all involved. I bought the five-pack+1 to give as gifts for the holidays, anticipating that developers would root and hack. I probably don't even need a custom recovery/boot-loader. Just being able to permanently replace the launcher and getting around the Firelauncher is good enough for my gift recipients.
Thanks mucho!
cryophil said:
Ah, okay. I think I am learning. I read that a boot.img was also used to root the device. I assumed that changes were permanent. I think the difference is, the changes made after the boot.img can be made permanent using SU/root. But in this launcher replacement case, it is just a boot difference for that one boot-up.
It's a great way to test if I like the setup, then if so, I can root and change to that launcher/setup permanently using the root method discovered last weekend.
Thank you very much to all involved. I bought the five-pack+1 to give as gifts for the holidays, anticipating that developers would root and hack. I probably don't even need a custom recovery/boot-loader. Just being able to permanently replace the launcher and getting around the Firelauncher is good enough for my gift recipients.
Thanks mucho!
Click to expand...
Click to collapse
No problem, and good luck!
Sent from my KFFOWI using Tapatalk
cryophil said:
Ah, okay. I think I am learning. I read that a boot.img was also used to root the device. I assumed that changes were permanent. I think the difference is, the changes made after the boot.img can be made permanent using SU/root. But in this launcher replacement case, it is just a boot difference for that one boot-up.
It's a great way to test if I like the setup, then if so, I can root and change to that launcher/setup permanently using the root method discovered last weekend.
Thank you very much to all involved. I bought the five-pack+1 to give as gifts for the holidays, anticipating that developers would root and hack. I probably don't even need a custom recovery/boot-loader. Just being able to permanently replace the launcher and getting around the Firelauncher is good enough for my gift recipients.
Thanks mucho!
Click to expand...
Click to collapse
Just to clarify, for the launcher replacement, the boot.img is used just to make the system partition r/w so that the changes can be made to replace the launcher. So the r/w mounting of the system partition will only last for that one boot, but the replacement of the launcher will be "permanent," in that it will persist after reboot. The rooting procedure uses the same method to copy the necessary su binaries to the device and set permissions.
So if you follow this procedure for replacing the launcher, it will be permanent with no need to then also root the device in order to make it permanent. Of course, you can also then root the device if you want, but you don't need to in order to replace the launcher.
Will the home button work after running this? I had read in some other threads about replacing the home screen messing up the home button.
Yes, the home button will work after using this.
Even widgets should work.
Maybe I'm missing something, but I don't see the script anywhere.
Was due to updating, you can find the new version 1.1 in the first post.
I replace firelauncher by Google Now as default launcher with the script posted in this forum. Could it be a problem for your Trebuchet script?
Enviado desde mi KFFOWI mediante Tapatalk
Darkside1984 said:
I replace firelauncher by Google Now as default launcher with the script posted in this forum. Could it be a problem for your Trebuchet script?
Click to expand...
Click to collapse
So you want to replace the trebuchet.apk with google now launcher and use that as your default?
If you rename your apk file to trebuchet.apk that will work.
But google now launcher is reported to be rather unstable as default one somewhere else in this forum, so it might be a better idea to install trebuchet using the script and then google now launcher from play store.
That should allow you to choose between the two and set now launcher as default one, but with a fallback to trebuchet.
Live wallpaper does not work
example
https://play.google.com/store/apps/details?id=com.style_7.analogclocklivewallpaper_7&hl=en
starts to open then crashes
....................................................................
below seems to be "USER ERROR"
....................................................................
videos in google play-store dont work gives error
"The requested action is not permitted. check Parental controls settings and retry"
example
https://play.google.com/store/apps/details?id=ch.bitspin.timely&hl=en
.
a1yet said:
Live wallpaper does not work
example
https://play.google.com/store/apps/details?id=com.style_7.analogclocklivewallpaper_7&hl=en
starts to open then crashes
....................................................................
videos in google play-store dont work gives error
"The requested action is not permitted. check Parental controls settings and retry"
example
https://play.google.com/store/apps/details?id=ch.bitspin.timely&hl=en
.
Click to expand...
Click to collapse
I can confirm the first issue, but it also exists if you replace the launcher manually (as I did), will look at were it comes from tomorrow.
The second one appears like you ran pm hide on the default video player and should not be related to the script.
ChrBeck said:
you ran pm hide on the default video player
Click to expand...
Click to collapse
thank you
i installed VLC after hide should it not use it as my default video player ?
or do i have to unhide the default one ?