[Q&A] [Script] WiFi Only (great for inactive devices) - Droid Eris Q&A, Help & Troubleshooting

Q&A for [Script] WiFi Only (great for inactive devices)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Script] WiFi Only (great for inactive devices). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Disable cell radio – radiooptions binary
Parent thread here — This forum doesn't allow me to post where my post belongs.
I'm converting an old Galaxy Fame S6810p into a car dashboard navigator; I want to permanently disable the cell radio to save battery, particularly, the car's battery. Full info on my project here.
As indicated in the linked thread, the OP suggests to use the system command radiooptions to deactivate cell radio, and apparently, this works for them. But, my phone didn't come with the binary radiooptions installed by default, so I downloaded an ARM instance of it and placed under /system/bin/radiooptions, using the ADB shell.
Now, issuing the command "radiooptions 1" from an SSH connection effectively disables the cell radio, as indicated in the phone's status bar (no signal icon), but after just a few seconds the phone reconnects to the cell tower and the status bar shows again the usual signal strength icon. So the effect of radiooptions is only temporary for me.
Here's with Android 4.1.x.

Related

[Q&A] [FIX]Enable encryption - Check&Shrink ext4 filesystem

Q&A for [FIX]Enable encryption - Check&Shrink ext4 filesystem
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [FIX]Enable encryption - Check&Shrink ext4 filesystem. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
I had this problem for a looooong time. Thankfully, I seem to have discovered the solution for those still encountering this issue.
Turn off SuperSU (Settings -> More -> Application manager -> All -> SuperSU -> Turn Off)
Reboot into Safe Mode (How to)
Run encryption (Settings -> More -> Security -> Encrypt Device)
Turn on SuperSU after complete (Settings -> More - > Application manager -> Turned Off -> SuperSU -> Turn On)

[Q&A] [App]One Click Unroot[WIP]

Q&A for [App]One Click Unroot[WIP]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [App]One Click Unroot[WIP]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Error
Indirect said:
I am proud to present you with: Nook Tablet Unrooter One click APP!
By Indirect​​
Information?: Well, the way to best unroot the nook tablet (as it's easy to see if you have done mods to it) is to do a factory system restore, so I decided why not exploit that and make it into an application? Well that's exactly what I did and best of all, it's 1 click (technically 3 but i don't count accepting SU permissions as part of the app). You need to grant SU both times it asks for it to automatically reboot.
Code:
//I take no responsibility what happens with this application or your device and assume that any problem during this process if user fault.
//
Download link?:
http://dl.dropbox.com/u/15069134/Nookunrooter.apk
Instructions?:
Install app, open, click button, grant SU permissions (twice), and let it restore. That's about it.
Warnings?:
You WILL lose ALL data on the tablet except the Sdcard. Be sure to back everything up using titanium backup.
Changelog?:
Code:
1.2: Initial release
Credits?:
Code:
Dodgejcr for his code on github so I just had to change a few things as well as his help in IRC. Thanks man
Myself for rewriting parts of the app to be a one click unroot for the nook tablet[/QUOTE]
Every time I try to run the app I get "could not echojava.io.IOException:Error running exec(). Command [su] Working Directory:null Environment:null"
Any recommendations on what i do?
Click to expand...
Click to collapse

[Q&A] [TOOLS] Create unlock.img, fix boot.img, repack update.bin (for aboot <=.3.2.

[Q&A] [TOOLS] Create unlock.img, fix boot.img, repack update.bin (for aboot <=.3.2.
Q&A for [TOOLS] Create unlock.img, fix boot.img, repack update.bin (for aboot <=.3.2.3.2)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [TOOLS] Create unlock.img, fix boot.img, repack update.bin (for aboot <=.3.2.3.2). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
kindle fire hdx 7 root
draxie said:
The attached archive includes 3 tools for those of you with .3.2.3.2 (or earlier) bootloaders.
Since other tools (and earlier version of these very tools) are available and working well,
this is mostly meant as an entry to an imaginary beauty contest. (JOKING!!!)
cuber.py
a generic gmpy2-free reimplementation of @vortox's signature.py
use this to generate your unlock.img
cuboot.py (uses cuber.py)
a Python-only reimplementation of @vortox's cuber
includes fixes to the kernel command-line and the device-tree
use this to convert a standard Amazon boot.img (>=.4.x.x)
upHDX (uses cuboot.py)
bash script to repack Amazon updates for TWRP
could be DANGEROUS, use with care
tested on Apollo for both 14.4.5.2 and 14.4.5.3
my unit is fully 14.4.5.3 now, except for aboot (which is 3.2.3.2)
should work on Thor as well
Those with bootloader .3.2.6 and lower can downgrade to .3.1.0
and upgrade the bootloader to the latest vulnerable version .3.2.3.2.
Those with .3.2.7 and higher appear to be out of luck with forged signatures, but I hear there's progress on rooting .4.5.2.
The python scripts have been tested on the following OS / Python combinations:
Windows: 2.7.9 and 3.4.3
Linux: 2.7.9 and 3.3.4
OSX: 2.6.? (cannot quite remember)
In addition to the tools themselves, I also included "educational" examples
(examples.sh for Linux/OSX, examples.bat for Windows).
These make use of the split.py script, which is otherwise unnecessary.
(The Windows example also shows that simply echoing your manfid/serial
combo to cuber.py -the way one does in Linux/OSX- won't work due to
the carriage-return character introduced by the echo command.
You'll need to handcraft a file matching the '0x%02x%08x\n' format...)
Another batch file py..bat is meant as an extra aid for Windows users
to avoid trouble with setting paths and such. You should be able to simply
download and install your preferred Python version.
Open a command shell (cmd.exe), navigate to wherever you extracted the
archives, and type 'py PYTHON-SCRIPT ARGS' to run the Python scripts.
(This handholding intentionally does NOT work for the upHDX script.)
Hopefully, someone will find these simple tools useful.
EDIT: To unlock your bootloader (<=.3.2.3.2), you'll need adb and fastboot.
On Linux, most distributions package these separately. Look for android-tools-{adb,fastboot} or some such.
For Windows, you can get these from the official Android SDK (which is a **large** download,
with a lot more tools you won't need, if you don't already use them, but it's safe).
Alternatively, there's a very legit-looking project here an XDA, with a much smaller
download, fast install, and exactly the tools you need. I haven't used either... (-;
The actual unlock procedure is described here and here.
EDIT#2: I added another script 'cublock.py' to make unlock.img generation super easy both on Windows and Linux.
MD5( tools.zip) = c17fc91344bd3b4b040129a79a39741f
Click to expand...
Click to collapse
i boung today the kindle and it come woth this version 13.3.0.2 and i cant find anything to root i use the make it rain app and say that i was root but i dont know how to verify can you help me and tell me what to do you can send me inbox
---------- Post added at 08:49 PM ---------- Previous post was at 07:50 PM ----------
sorry for my mistake ... I'm not use to forums the link you give me doesn't work stay in black and again sorry for my mistake
Sent from my HTC One_M8 using XDA Free mobile app

[Q&A] [GUIDE] Install the Bq phone's scopes on any Ubuntu Phone

Q&A for [GUIDE] Install the Bq phone's scopes on any Ubuntu Phone
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE] Install the Bq phone's scopes on any Ubuntu Phone. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
nikwen said:
[GUIDE] Install the Bq phone's scopes on any Ubuntu Phone
This hack installs all apps and scopes which come preinstalled on the Bq and Meizu phones on any ARM based Ubuntu Phone.
Disclaimer
Proceed at your own risk. I am not responsible for any damage, including but not limited to loss of data, bricked devices, thermonuclear war or you getting fired because the alarm app failed.
Please note that these scopes are currently unsupported on any phone other than the BQ Aquaris E4.5 Ubuntu Edition. Things may break when you install these scopes. Specifically, it looks like this disables OTA updates, so you will have to reflash in order to update your phone.
Also be aware that this will not work with MultiROM!
This has only been tested on a Nexus 4.
Installation
Let's get started. First of all, download the firmware for the Bq phone on your Ubuntu desktop machine:
Code:
ubuntu-device-flash --download-only touch --device=krillin --channel=ubuntu-touch/stable
After that has finished, find out the exact file name of the file "custom-*.tar.xz" in ~/.cache/ubuntuimages/pool/. If there are multiple files which match that pattern, choose the most recent one.
Then run the following command, where you replace CUSTOM-FILE by the file name you just found out and CHANNEL by the name of the channel which you installed on your phone.
Code:
ubuntu-device-flash touch --custom-tarball=.cache/ubuntuimages/pool/CUSTOM-FILE --channel=CHANNEL
That will take a while but then you should have the apps and scopes installed on your device. But remember, this is still an unofficial and unsupported hack!
Click to expand...
Click to collapse
Niklas, this hack worked for me few months ago, but today it doesn't work. What is your suggestion?
turan.mahmudov said:
Niklas, this hack worked for me few months ago, but today it doesn't work. What is your suggestion?
Click to expand...
Click to collapse
If it really doesn't work anymore (I didn't test it again), you could try extracting the zip and running
Code:
click build .
in all relevant app folders and installing the resulting click packages using
Code:
pkcon install-local app.click
on your device. That would also be a much nicer way of doing it compared to what we currently have.

[Q&A] exFAT and NTFS fuse drivers easy build for any platform

Q&A for exFAT and NTFS fuse drivers easy build for any platform
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for exFAT and NTFS fuse drivers easy build for any platform. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Trying on 4.2.1.... It does not work. I got "volume operation failed" after manually run "recovery-update2.sh."
DeepInSleep said:
Trying on 4.2.1.... It does not work. I got "volume operation failed" after manually run "recovery-update2.sh."
Click to expand...
Click to collapse
If you manually run the script, be sure you run it as su, and provide it any parameter, e.g.
/system/etc/recovery-update2.sh test
For troubleshooting, edit the script to uncomment the logging and try to figure out the problem from the log file.
Lurker0 said:
If you manually run the script, be sure you run it as su, and provide it any parameter, e.g.
/system/etc/recovery-update2.sh test
For troubleshooting, edit the script to uncomment the logging and try to figure out the problem from the log file.
Click to expand...
Click to collapse
Problem solved I deleted this part (the script does not run with him. I do not know why)
Code:
#!/system/bin/sh
logfile0=/data/local/tmp/exfat_mount.log
#logfile=$logfile0
logfile=/dev/null
if [ -e $logfile0 ]; then
logfile=$logfile0
I also changed the mount point from the /mnt/media_rw/sdcard1 to /mnt/sdcard2. With a device=/dev/block/mmcblk1p1 some programs have not seen hardware sdcard, only storage/sdcard1 patch. Then I replaced it on device=/dev/block/vold/179:97. Now it works fine for me
UPDATE: crashing with multiple read/write operations. Tested in bittorrent app

Categories

Resources