Auto-Rotate - G1 Android Development

Is there a way to manually enable Auto-Rotate (via Terminal Emulator, etc). For some reason Droidsans isn't working right now. It gives me "Operation Failed" whenever I try to enable it, before and after a reboot.
I had to re-root my phone after I semi-bricked it yesterday.
|Spike|

AGx-07_162 said:
Is there a way to manually enable Auto-Rotate (via Terminal Emulator, etc). For some reason Droidsans isn't working right now. It gives me "Operation Failed" whenever I try to enable it, before and after a reboot.
I had to re-root my phone after I semi-bricked it yesterday.
|Spike|
Click to expand...
Click to collapse
Did you make sure you hit the Mount Read/Write button first?

1 - Mount Read/Write
2 - Disable auto-rotate
3 - restart g1
4 - Mount Read/Write
5 - enable auto-rotate

Trying that now.....
Edit: No good. Still gives me the operation failed..
|Spike|

i encountered that problem the when i first installed DroidSans
i disabled auto rotate on browser then tried to reboot then enable autorotate on DroidSans.

AGx-07_162 said:
Trying that now.....
Edit: No good. Still gives me the operation failed..
|Spike|
Click to expand...
Click to collapse
Everytime I enable auto-rotate it fails the first time I hit enable, but if u hit enable a second time then it should work then hit reboot. hope that helps.

Same thing happened to me. What works for me is to hit disable (even if it's disabled), then hit enable and reboot, works like a charm every time for me!

That usually happens to me, and that reminded me to turn Auto-Rotate back on. So, let's go about how I do it:
1) I open up DroidSans.
2) I check Auto-Rotate status. Current: Disabled.
3) I press "Enable Auto Rotate." Operation Failed
4) Okay, let's try "Disable Auto Rotate." Operation Completed; Please reboot your phone WTF?
5) Now let's try to enable it again. Operation Completed; Please reboot your phone Again, WTF?
6) Now I reboot just to see if it works. SUCCESS!
To disable Auto Rotation, just swap around "Enable" and "Disable" in the above tutorial.

Bah that's not working either. I know I'm rooted. I have themes, I use tether wifi, I can even use driodsans reboot feature. I don't get it. Does anyone know a command I can use to enable it?
|Spike|

blackknightavalon said:
That usually happens to me, and that reminded me to turn Auto-Rotate back on. So, let's go about how I do it:
1) I open up DroidSans.
2) I check Auto-Rotate status. Current: Disabled.
3) I press "Enable Auto Rotate." Operation Failed
4) Okay, let's try "Disable Auto Rotate." Operation Completed; Please reboot your phone WTF?
5) Now let's try to enable it again. Operation Completed; Please reboot your phone Again, WTF?
6) Now I reboot just to see if it works. SUCCESS!
To disable Auto Rotation, just swap around "Enable" and "Disable" in the above tutorial.
Click to expand...
Click to collapse
What I was trying to say is that you need to keep hitting Enable Auto-rotate till it says enabled... It takes me 2 times. DON"T HIT DISABLE unless auto rotate is on and u want it off and DON'T REBOOT till it says enabled.
Oh Yeah! I just remembered that There used to b two dif. copies of Driodsans on the market so if they still have two copies up try the other with the same steps. If that don't help. Then try re rooting your G1 maybe.

umm
the gallery application does not autorotate, does it?

Disable Operation Failed
On JF1.41 Rooted..
Having the opposite problem. I had used this to enable auto-rotate but it's annoying me by being too sensitive and switching back and forth when I don't want it to. I've tried to disable and it fails. I mounted R/W first, and still no success. But if I click Enable AR it works. I've tried rebooting, even got so annoyed with the Force Close error during phone calls, that I just did a wipe. I was surprised that did not kill the auto-rotate. So I re-downloaded Droid Sans 0.87 and it still won't allow me to disable the feature! Anyone have any ideas?
Thanks!

Just a simple thought. I had the same problem when I accidentally installed jf adp1 instead of jf33. There are two different versions of droidsans last I checked for the different versions. Might check to make sure you've got the right one.

The two different versions of Droid Sans are: Droid Sans Tweak Tools, which is for root users and includes remount r/w, autorotate, and reboot functions...the other is Droid Sans Tweak Tools LITE and it is for users WITHOUT root, no autorotate included...

Related

[SOLVED] UPDATE Bypass Mobileiron and Root Detection ICS, JellyBean

Disclaimer: This is for testing purposes only. I do not condone breaking company policy, or breaking any laws. I am not responsible for you getting fired as a result of you making these modifications. You should always read and abide by company policies and any laws pertaining to such modifications. Use of this tutorial is at your own risk.
Preface: I have tested the new method on multiple devices and it has been flawless so far.
UPDATE: I have found a new method that so far has been flawless across multiple devices so far for me. With this new method you won't even have MobileIron installed when you're done! I have tested this on my Galaxy Nexus, My Nexus 7 and my Galaxy Note II and believe it should work regardless of device. Your company may have different security policies than mine so it's possible this may not work for you.
The easiest way to do this is with one of mskip's toolkits, but it can also be done manually with adb (must have the latest sdk).
Toolkit Method
0. Make sure you have MobileIron and Touchdown installed, configured and syncing. Your phone does NOT have to be rooted to do this.
1. Download mskip's Toolkit Here and install.
2. Make sure you have the adb drivers for your phone installed on your computer and android debugging is turned on in the developer settings on your phone.
3. Open the toolkit and connect your phone to your computer
4. It shouldn't matter what model phone you choose for the purpose of what we're doing, and the options may be slightly different based on which toolkit you download
5. Choose the option backup and restore your device
6. Choose backup all installed apps
7. Choose do NOT include system apps in the backup
8. Choose backup apk's AND respective app data
9. Choose do NOT back up internal storage data in backup
10. Wake your phone and it will ask you to start the backup, choose to do so
Once it is finished you will need to wipe your phone. It may work without wiping and just uninstalling touchdown and Mobileiron before proceeding to the next section, but I haven't tested this.
11. Connect your phone to your computer and enable android debugging
12. Browse to C:\Galaxy Nexus Toolkit (or whatever the name of your toolkit is under c:\)
13. Open the folder backups and rename the backup file to backup.bak. (if you don't see the file extension just name it backup)
14. Open the toolkit and choose a model
15. Choose Backup and Restore
16. Choose Restore apps from a backup file
17. type backup.bak and press enter
18. Wake your phone and choose to begin the restore
19. When it's finished, uninstall mobileiron, open touchdown and see if it's syncs!
ADB Method
adb backup -all -system -shared -apk
recovery> backup, wipe, flash rom, flash gapps, reboot
adb restore backup.ab
Requirements For ICS:
1. Rooted Android Phone running ICS based ROM
2. Titanium Backup (app installed)
3. Hide my Root (app installed)
4. Mobileiron (app installed but never run)
5. Touchdown (app installed but never run)
Instructions for ICS:
0. Make a Nandroid backup
1. Open Hide my Root
2. Choose hide SU binary
3. Press home
4. Menu, settings, apps, all apps
5. Choose Superuser.apk
6. Choose disable
7. Now open mobileiron and configure the settings per your company's instruction.
8. Set up your email in the Touchdown application and let it sync everything.
9. Open Hide my Root and choose restore SU Binary
10. Go back to menu, settings, apps, superser.apk and choose enable. (Its at the bottom when disabled)
11. Open Titanium Backup
12. Choose backup/restore from the top
13. Scroll to Mobileiron and tap it and choose freeze.
14. Profit
Now restore your nandroid backup before you get in trouble.
**Update** for Jelly Bean
It seems the builds out there for Jelly Bean use a new version of SuperUser that as of yet isn't compatible with Hide My Root. I wrote the developer of Hide My Root and he is looking into this but currently doesn't have a device running Jelly Bean to test on, so I took it upon myself to figure this out once again. I tested this and it does work. Again this was tested on a VZW Galaxy Nexus only.
Instructions for Jelly Bean:
0. Make a Nandroid backup!
1. Download MobileIron (App installed but never run)
2. Download Touchdown (or any apps that depend on MobileIron and do not launch them)
3. Download Titanium Backup (You may need the premium version to freeze apps)
4. Download SuperSU flashable zip from HERE and place on your SDcard.
5. From the app drawer launch SuperSU (that app already installed, not the zip you just downloaded)
7. Swipe 2 screens to the right to Settings
8. Choose Full unroot.
9. Install and configure MobileIron and dependent apps and let them fully sync.
10. Enable Airplane Mode
11. Reboot to recovery and flash the SuperSU zip you downloaded
12. Boot into Android, open Titanium Backup and freeze MobileIron
13. Turn off Airplane Mode
14. Profit
Now restore your nandroid backup before you get in trouble.
After a reboot all of the lockscreen options will reappear allowing you to have an insecure lockscreen.
This is great
You just saved me hours of frustration.
Thanks!
Thanks - this is a huge help!!
Question: does this work only with Touchdown, or any Android email client? (I prefer the app Enhanced Email).
SoCalNewb said:
Thanks - this is a huge help!!
Question: does this work only with Touchdown, or any Android email client? (I prefer the app Enhanced Email).
Click to expand...
Click to collapse
I have only tested this as posted. Make a nandroid backup and play around with it
How to re-enable superuser?
Made a nandroid backup. Followed instructions below. Works great, now I can synch email with MobileIron fortified corp server AND change the PIN lock requirement that MobileIron required! Thank you
Only one issue: I couldn't complete step 10 ("Go back to menu, settings, apps, superser.apk and choose enable"). Superuser was no longer in the "All" list under menu, settings, apps. As a result, I seem to have lost the ability to grant root access to new applications.
QUESTION: How do I re-enable superuser?
Notes:
- ADB: I can connect to device via ADB, but if I type "adb shell", and then type "su" at the "sh-3.2#" promot, no $ access is granted).
- Terminal Emulator: TE cannot get root (I type "su" at the "sh-3.2$" command, and TE says "Permission denied")
- Root Access - Old Apps: Any apps that previously had root privileges still do (Root Explorer can navigate to "/" and enable "Mount R/W", Wifi Tether still works, etc).
- Root Access - New Apps: New apps requiring root are not able to get root (no superuser prompt comes up)
- Re-Installing Superuser.apk: I tried using root installer to re-install superuser.apk (in the "/system/app" directory). It said it installed successfully, but still no superuser in the "All" list under menu, settings, apps.
- Re-Rooting: I tried re-rooting (using mskip's exceelend GNEX toolkit HERE), to no avail (process completes, but no superuser access).
If anyone can help me troubleshoot I would be extremely appreciative. I've tried to not be a helpless newb and to try a few fixes (above), but I would be ecstatic if one of XDA's Android ninjas could tell me how to re-enable superuser. Hoping to avoid comments of "restore nandroid backup and give up"
bhilgeman said:
1. Open Hide my Root
2. Choose hide SU binary
3. Press home
4. Menu, settings, apps, all apps
5. Choose Superuser.apk
6. Choose disable
7. Now open mobileiron and configure the settings per your company's instruction.
8. Set up your email in the Touchdown application and let it sync everything.
9. Open Hide my Root and choose restore SU Binary
10. Go back to menu, settings, apps, superser.apk and choose enable.
11. Open Titanium Backup
12. Choose backup/restore from the top
13. Scroll to Mobileiron and tap it and choose freeze.
Click to expand...
Click to collapse
SoCalNewb said:
Made a nandroid backup. Followed instructions below. Works great, now I can synch email with MobileIron fortified corp server AND change the PIN lock requirement that MobileIron required! Thank you
Only one issue: I couldn't complete step 10 ("Go back to menu, settings, apps, superser.apk and choose enable"). Superuser was no longer in the "All" list under menu, settings, apps. As a result, I seem to have lost the ability to grant root access to new applications.
QUESTION: How do I re-enable superuser?
Notes:
- ADB: I can connect to device via ADB, but if I type "adb shell", and then type "su" at the "sh-3.2#" promot, no $ access is granted).
- Terminal Emulator: TE cannot get root (I type "su" at the "sh-3.2$" command, and TE says "Permission denied")
- Root Access - Old Apps: Any apps that previously had root privileges still do (Root Explorer can navigate to "/" and enable "Mount R/W", Wifi Tether still works, etc).
- Root Access - New Apps: New apps requiring root are not able to get root (no superuser prompt comes up)
- Re-Installing Superuser.apk: I tried using root installer to re-install superuser.apk (in the "/system/app" directory). It said it installed successfully, but still no superuser in the "All" list under menu, settings, apps.
- Re-Rooting: I tried re-rooting (using mskip's exceelend GNEX toolkit HERE), to no avail (process completes, but no superuser access).
If anyone can help me troubleshoot I would be extremely appreciative. I've tried to not be a helpless newb and to try a few fixes (above), but I would be ecstatic if one of XDA's Android ninjas could tell me how to re-enable superuser. Hoping to avoid comments of "restore nandroid backup and give up"
Click to expand...
Click to collapse
When you disable superuser.apk in the apps list it moves it from the alphabetical order to the bottom of the apps list. Look there and see if its at the bottom of your apps list.
bhilgeman said:
When you disable superuser.apk in the apps list it moves it from the alphabetical order to the bottom of the apps list. Look there and see if its at the bottom of your apps list.
Click to expand...
Click to collapse
YOU ARE THE MAN.
That was so simple, but I spent an hour trying stuff and still missed it
My Android experience is back to awesome despite Mobile Iron - THANK YOU!!!!
Thanks for that. Great idea.
I followed your instructions but I had to switch 9 and 10 because Hide my root cannot restore a deactivated app.
But my TouchDown says "Synchronization Error" --> access denied (update your password). Maybe too strong policies?
And by the way: you have to use tintanium backup PRO to enable or disable apps
---------------------
Edit: I made a system application of "Hide my root" with TI Backup - works. I had to uninstall TI Backup now - currently TouchDown is syncing again. We will see if it works, next: I try to use LBE Privacy Guard... will report. Disabling "MobileIron" seems not working for me...
Hey, is not possible solve it on 2.X version of Andriod? Thanks...
OP Updated to reflect Changes for those running JellyBean. Long live the Android experience!
bhilgeman said:
The SU change needed for JellyBean makes this previous method unusable. I did however figure out how to still get to the same result if you're running JellyBean.
I will so an update to the OP soon to reflect this.
Click to expand...
Click to collapse
Looking forward to the instructions for making this work on JB
SoCalNewb said:
Looking forward to the instructions for making this work on JB
Click to expand...
Click to collapse
OP updated for JB instructions.
Sorry, I haven't tested this on a 2.x build so I'm not sure. If I get time I'll try to test this for you, I'm just super slammed with projects right now...
Will we appear "normal" on the Server that the app links us to our Corp acct??
Yes, you will appear as a non rooted phone. I just updated the JB instructions again. Realized I left out a step.
Anyone test this for Airwatch yet?
FWIW.....my experience has shown this to be merely a temporary solution, by itself. Yes...following the JB instructions will allow you to sync up just fine. But.....when mobileiron does not report back as device administrator, the red flags go up. My solution, thus far, has been to suspend root access on the phone, after reactivating mobileiron. In my case, after re-activating mobileiron, the app, itself, now FC's, which may be helping me out....not sure. At this point I seem to be able to continue remaining synced, without root access. As long as I use airplane mode before enabling root access to do root-type stuff, I seem to be fine. Word of caution, though....disabling root, seems screw up TB when I re-enable root. Specificaly...even though I have TB pro, it does not register after re-enabling root, so freezing and unfreezing mobileiron at will has not been possible. Could just be my system though.I recommend using airplane mode liberally if there is any doubt regarding your recognized root/non-root status. This definitely changes how I use the device, though, for sure.
makelegs said:
FWIW.....my experience has shown this to be merely a temporary solution, by itself. Yes...following the JB instructions will allow you to sync up just fine. But.....when mobileiron does not report back as device administrator, the red flags go up. My solution, thus far, has been to suspend root access on the phone, after reactivating mobileiron. In my case, after re-activating mobileiron, the app, itself, now FC's, which may be helping me out....not sure. At this point I seem to be able to continue remaining synced, without root access. As long as I use airplane mode before enabling root access to do root-type stuff, I seem to be fine. Word of caution, though....disabling root, seems screw up TB when I re-enable root. Specificaly...even though I have TB pro, it does not register after re-enabling root, so freezing and unfreezing mobileiron at will has not been possible. Could just be my system though.I recommend using airplane mode liberally if there is any doubt regarding your recognized root/non-root status. This definitely changes how I use the device, though, for sure.
Click to expand...
Click to collapse
I run your CM10 build on my nex7 and love it. Great to have navbar mods.
On my nex7 it took me a few tries to get it to stick but I finally got it. I hadn't updated a nightly for a couple weeks and when I did Mobileiron got me. I decided I don't care about getting work email on my tablet as much as I do my phone so no big deal. I freaking hate Mobileiron and touchdown nearly as bad.
On my galaxy nexus (running fitsnugly cm10) I don't have any issues. I flash the nightlies every day and I've gone a couple months without Mobileiron flagging me.
Sent from my Nexus 7 using xda app-developers app
bhilgeman said:
I run your CM10 build on my nex7 and love it. Great to have navbar mods.
On my nex7 it took me a few tries to get it to stick but I finally got it. I hadn't updated a nightly for a couple weeks and when I did Mobileiron got me. I decided I don't care about getting work email on my tablet as much as I do my phone so no big deal. I freaking hate Mobileiron and touchdown nearly as bad.
On my galaxy nexus (running fitsnugly cm10) I don't have any issues. I flash the nightlies every day and I've gone a couple months without Mobileiron flagging me.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Skanklove!
I was completely under the radar, due to some corporate user configs, until I screwed up and raised the red flag. Then I had to encrypt, and install mobileiron. I was perfectly happy with touchdown until mobileiron got involved. I don't want work email on any device other than my work phone (toro). I can still run email without mobileiron, but no activesync and no email attachments......meh
Steps on ICS
Hello,
I am new to using mobileiron, as my corporation just started to use this program. Can I use your steps on ICS and keep my root undetected or will I eventually have issues. Last question, why is it necessary to restore your nandroid backup at the end?

Tasker Secure Settings Not Working

Hi Everyone.
I'm having issues trying to get secure settings set up with tasker. When I attempt to enable System+ Module it initializes forever. The one time I got it to work, it was operational for about five minutes, before it disabled itself on its own. I have SuperSU set to allow all apps that request root. Its still not working.
Any ideas? Thanks!
I have it running fine on my device. What steps have you tried to get it working? Rebooted the device? Cleared data and cache? Uninstalled and reinstalled?
curry101 said:
Hi Everyone.
I'm having issues trying to get secure settings set up with tasker. When I attempt to enable System+ Module it initializes forever. The one time I got it to work, it was operational for about five minutes, before it disabled itself on its own. I have SuperSU set to allow all apps that request root. Its still not working.
Any ideas? Thanks!
Click to expand...
Click to collapse
Make sure you activate the system+ module prior to granting administrative access. Also make sure you have root.

Need help please. Disabled System.UI on accident with Package Disabler Pro

Hello any help and advice will be greatly appreciated. I accidentally disabled system.ui with Package Disabler Pro and now lost touch on the phone. The touch screen is still active because when the phone dims it lights back up when I touch it. However, I can't access any applications, menu's and the volume keys also appear to be disabled. I also can't scroll between home screens. The power button does work, I have not tried to restart the phone as of yet.
Is there anything I can do to re-enable the system.ui from Package Disabler?
I think that if you wipe your phone by recovery it should be right even if you will lose all your data file. Try and wait for another solution... it could be you will save your data file
fabiok81 said:
I think that if you wipe your phone by recovery it should be right even if you will lose all your data file. Try and wait for another solution... it could be you will save your data file
Click to expand...
Click to collapse
I was able to fix it by going into safe mode and disabling the administrative permissions to package disabler pro. Thank you the thread can be locked.
???
chungdae said:
I was able to fix it by going into safe mode and disabling the administrative permissions to package disabler pro. Thank you the thread can be locked.
Click to expand...
Click to collapse
I just did the same thing. I'm in safe mode, how do you disable admin permissions for that app?
berfles said:
I just did the same thing. I'm in safe mode, how do you disable admin permissions for that app?
Click to expand...
Click to collapse
Settings > Lock screen and security > (scroll to bottom) Other security settings > Device Administrators > Toggle the switch for PDP

Xperia E4g Root method FOUND

as far as i know, no-one has managed to root on new firmware. Here's how i did it:
1. Get into developer mode by going to Settings -> About phone and keep on tapping 'Build number' until it says 'Congratulations, you are a developer'
2. exit 'About phone' and go to the new tab 'Developer options' and click 'USB debugging.' Press okay.
3. exit 'Developer options' and go to security, allow 'Unknown sources.'
4. Goto www(dot)kingroot(dot)net (can't do URLs. Srry). download the apk. if you downloaded it to your phone just install. if you downloaded it to pc use a usb to transfer or something- your choice on how it gets there- and install it on the phone.
5. run it and attempt root 2 times. both times should fail. straight after the second fail exit the app, shutdown and turn on. Do not reboot, as this doesn't work if you reboot.
6. Device should be rooted. Use Purify to check. If purify isn't installed, the process failed. If purify cant get root access, the process failed. Try an app that uses root. if a tab doesn't come up, the process failed.
this is how i rooted mine. not sure if it works generically or if it was one-time for me.
I posted it here, as there is no E4g forums, and this seemed like a popular place for the E4g posts.
Stay away from kingroot
Why must stay away from kingroot?
mie_shariff said:
Why must stay away from kingroot?
Click to expand...
Click to collapse
Kingroot dosent root the phone fully its an online root so you information can get access by the app, you phone can unroot any time etc..

Your device is corrupted -HELP-

Hi, i have a oneplus 6 rooted with magisk running twrp recovery and last night i was messing around with a mock location spoofer and everything was going okay but after a reboot my phone started only going into safe mode and i couldnt access anything basically my phone screen would flash on then off then on and off again constantly.
i Followed this tutorial https://www.reddit.com/r/PokemonGoSpoofing/comments/8ytjz5/expert_mode_for_fake_gps_and_routes/
then after that i had trouble using systemizer to make the app a system app so i used lucky patcher instead.
after all this my phone was working fine
the final thing i done what wasnt on the tutorial was used a package manager app to disable all location services from a very low software level. after that the safe mode thing started happening.
what i have tried so far -
i have tried going into the root and deleteing the app folder for the APK MANAGER app hoping that this would remove any changes it caused.
i have also tried using the magisk uninstaller to try and remove root.
now my phone wont even boot. i get a screen on start up saying my phone is corrupt and it just loops on this screen.
Before i do a full reflash and loose everything i thought id put my last hope on here and see if anyone can help me resolve this without a reflash.
Thanks for any help i'm stupid and didn't back up before hand
https://forum.xda-developers.com/oneplus-6t/how-to/guide-how-to-fix-red-boot-screen-device-t3891479
mauronofrio said:
https://forum.xda-developers.com/oneplus-6t/how-to/guide-how-to-fix-red-boot-screen-device-t3891479
Click to expand...
Click to collapse
thanks when i follow instructions it says too many symbolic links. can you help?
Shaun98 said:
thanks when i follow instructions it says too many symbolic links. can you help?
Click to expand...
Click to collapse
If you are root, install terminal app from playstore
open terminal, type : su, hit enter > grant root permission
then type : reboot "dm-verity enforcing", hit enter

Categories

Resources