Related
Thanks:
Scary Alien for helping with some of my brainstorms
CPCookieMan for pointing me in the right direction with my initial thoughts for this project
MongooseHelix for the idea of the script vs a flashable zip
This is a very simple script that utilizes the radiooptions command to disable the radio but still allow use of WiFi. I wanted to make it to be run in init.d on startup but haven't successfully got it working that way yet so for now it can be run with script manager. This script can be run as follows:
1. Download the script and place it somewhere on your SD Card. (Maybe make a folder named Scripts to keep things organized)
2. Download Script Manager from the market.
3. Open Script Manager and navigate to where you saved the script then select the script.
4. Check the options for run as root and if you always use wifi only because you don't have service on your device check off Run at boot as well.
5. When prompted by superuser allow superuser permissions.
I have tested this script on my Incredible and my Eris as well and should be universal to run on any android device.
Download Here
If you are using this on an inactive device and don't want the activation screen coming up after reboot and new ROM flash follow these simple steps.
*NOTE: you need to be using a ROM that has EPST.apk (Sense or stock based) in it for this procedure to work.
1. Select emergency call and dial ##778.
2. Select edit and enter service password 000000.
3. Select NAM Settings.
4. Change Mobile Directory number to 0000000000 (Ten digits).
5. Change MIN1 to 0000000 (Seven digits).
6. Change Mobile Country Code to 000 (Three digits).
7. As you back out "Commit the Change".
The guy that made super charger script has a script that can be ran with gscript and used to modify the init file which is supposed to change it so you can run scripts on boot. I think its only for stock roms tho.
Sent from my Exodus Sense using XDA App
Interesting.... this means once my daughter gets her upgrade I can retire my fabulous old Eris and turn it into a PDA and no longer use it as a phone? Sweet! Now I have to strip it all down to be a good mp3 player+.
Izeltokatl said:
Interesting.... this means once my daughter gets her upgrade I can retire my fabulous old Eris and turn it into a PDA and no longer use it as a phone? Sweet! Now I have to strip it all down to be a good mp3 player+.
Click to expand...
Click to collapse
You don't have to... but you can
anubis2k3 said:
The guy that made super charger script has a script that can be ran with gscript and used to modify the init file which is supposed to change it so you can run scripts on boot. I think its only for stock roms tho.
Sent from my Exodus Sense using XDA App
Click to expand...
Click to collapse
I'm wondering if it could be done by adding the commands in the init.rc file inside the boot image instead of an int.d script. I think the reason it's not working the way I have it setup so far is that it requires su permissions in order for the command to take effect. I'm still researching other ways but for now this method does work
CS - That is awesome!
gersto said:
CS - That is awesome!
Click to expand...
Click to collapse
Thanks I just hope people find it useful!
CondemnedSoul said:
Thanks I just hope people find it useful!
Click to expand...
Click to collapse
I think so, especially for those of us wanting to build ROMs that give our Eris's a second life as a non-phone touch device.
I know i've been wanting to try my hand at building a ROM like that, just waiting to upgrade in a month as my cell is the only phone i've got, just in case something bad happens to it
Hey, just wanted to say thanks. I don't have a use for this at this time but I can definitely imagine I'll have a use for it eventually!
Whenever I take advantage of my upgrade, I'll be sure to give this a try on my Eris. Right now it's my primary device though. Still, great idea CS!
Works great on my rebuilt Eris ..Thanks CS
Added procedure to permanately disable activation screen for non-activated phones to OP.
Just what i was looking for after i activate the new incredible 2! Awesome work!
Sent from my MacRom MR8 using XDA Premium App
Scary Alien!!!
there's a name i haven't herd in a while. i'm sure glad he is still around.
Hey cs, congrats on the xda article on your script. I know i'm a few days late...
Sent from my ERIS using XDA App
klobkelosh said:
Hey cs, congrats on the xda article on your script. I know i'm a few days late...
Sent from my ERIS using XDA App
Click to expand...
Click to collapse
Thanks klob..... article?? Didn't know about it though lol
CondemnedSoul said:
Thanks klob..... article?? Didn't know about it though lol
Click to expand...
Click to collapse
http://www.xda-developers.com/android/script-to-allow-wifi-with-radio-disabled/
I saw it too and then kept forgetting to mention it so I'm glad someone did lol.
so exactly what might happen if i run this script on ancm7 rom that does not have the EPST.apk file?
a.mcdear said:
so exactly what might happen if i run this script on ancm7 rom that does not have the EPST.apk file?
Click to expand...
Click to collapse
It will work fine without EPST. EPST is needed for ##778 to work for disabling the activation screen. The script itself does not require that apk, it uses the radiooptions command.
Sent from my ADR6300
I don't have radiooptions in my /system/bin...
But you said it should be universal on any Android device? Do I need a certain version of busybox installed?
If you have received errors like
Set ISCAN for wl_iw_combined_scan_set failed with -22
or your wifi turn on switch hangs, this is the solution for you
its appear that ICS is unable to set right frequency when your sim card country isnt US or EU, odd thing, but common thing about us (people who have wifi issue with ics) is that we don't live in us or eu.
fix is fairly simple, you need sqlite (which i got from http://forum.xda-developers.com/showthread.php?t=1067944)
and all you need is to run
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO secure (name, value) VALUES ('wifi_country_code', 'EU');"
turn wifi on and off, then you are good to go until next reboot.
the thing is i wonder where i should put this command to make it run *at right time* on next login, /system/etc/init.d/99nexusinit didn't did the trick, any idea?
Sql you used is just for one session, use the one i added 1 line to and it should stick on reboot.
INSERT INTO secure (name, value) VALUES ('wifi_country_code', 'EU');
Commit;
Sent from my Nexus S using xda premium
i received this error
SQL error: cannot commit - no transaction is active
Can read out of the database with
Select * from secure;
If not then there might be somethin wrong with the connection.
In this case add commit; to the original code you used.
Sent from my Nexus S using xda premium
can you give a step by step instruction how to do this?
thanks
Thanks a lot dude , worked for me
can you tell me how you did it? step by step please..
just get the mentioned file from the link and run it , thats it , but you need to make sure you have a root access first !
raminchit said:
just get the mentioned file from the link and run it , thats it , but you need to make sure you have a root access first !
Click to expand...
Click to collapse
ok so i plug in my phone with wifi not working and run the .bat file?
thats is?
yeap , thats what I did , with usb debugging enabled
raminchit said:
yeap , thats what I did , with usb debugging enabled
Click to expand...
Click to collapse
it didnt work for me. i ran the tool it says succes but wifi doesnt work.
OP, can you please inform kernel developers about possible solution for us (with wifi iasues) so they incorporate it in their kernel's next versions?
Sent from my Nexus S using XDA App
thegtfusion said:
it didnt work for me. i ran the tool it says succes but wifi doesnt work.
Click to expand...
Click to collapse
emm
use adb push to upload sqlite3 to /mnt/sdcard, run the sqlite command under the adb shell.
lio02 said:
OP, can you please inform kernel developers about possible solution for us (with wifi iasues) so they incorporate it in their kernel's next versions?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I don't know many developers around here, feel free to contact them on your own, fix is really simply enough.
arminzoup said:
emm
use adb push to upload sqlite3 to /mnt/sdcard, run the sqlite command under the adb shell.
Click to expand...
Click to collapse
Can you give a step by step instructiom? Plz plz im a noob at adb..
Sent from my Nexus S using xda premium
thegtfusion said:
Can you give a step by step instructiom? Plz plz im a noob at adb..
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Same here - did not work for me
amangoenka said:
Same here - did not work for me
Click to expand...
Click to collapse
try this one: http://forum.xda-developers.com/showthread.php?t=1403801
Little tutorial to help everyone out
download: https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Some pictures, step by sptep to help!
PUT YOUR PHONE ON FASTBOOT MODE AND PLUG IT TO YOUR PC! (truned off, press vol+ and power button)
READ THIS:
- at step 5 you have to browse your files and select the "usb_drivers" folder that you just downloaded then choose "Let me pick...".
- at step 6 it appear "asus android device" in my case but DONT care about that. Select "all devices". The next step is the important part.
- at step 7 click on have disk and browse to your usb_drivers folder and select "android_winusb.inf"
After this you can use commands to root, flash new recoveries, and go back to completly stock using bootloader mode on your device.
http://forum.xda-developers.com/showthread.php?t=895545 (FULL TUTORIAL)
http://forum.xda-developers.com/showthread.php?t=882815 (BIG FAQ)
Maybe all noobs need to read the BIG FAQ
kwibis said:
http://forum.xda-developers.com/showthread.php?t=895545 (FULL TUTORIAL)
http://forum.xda-developers.com/showthread.php?t=882815 (BIG FAQ)
Maybe all noobs need to read the BIG FAQ
Click to expand...
Click to collapse
dont be hater, i just wanted to make a thread more specific to this problem cuz sometimes its hard to find the awnser on those large thread
or you could just boot your device into download mode and plug it in....no downloading from any SHADY file hosts that force you to use their downloader, and no confusing instructions....boot to download mode, plug your phone in, then wait.
Thats a good ideia too, but anyways... u can wathever drivers u want from who u want. This tutorial was mainly fpcused on new people arriving to our world!
sent from my Nyan NeXus S
"You're either NEXUS or against us!"
Sorry, didn't mean to be a hater lol. But there is that faq with all the stuff you need to know to start up.
Sent from my Nexus S
Hi I am getting trouble moving beyond step 5 this is what i get :
Windows 8 is not able to install Android 1.0 as it was not able to find the drivers. I also included the subfolders but its still giving me the same error.
Any suggestions to go around this?
After chosing the folder did u downloaded the all zip file? Did u unzip it after?
sent from my Nyan NeXus S
"You're either NEXUS or against us!"
EDIT
just click let me pick instead of next
Cascabreu said:
After chosing the folder did u downloaded the all zip file? Did u unzip it after?
sent from my Nyan NeXus S
"You're either NEXUS or against us!"
EDIT
just click let me pick instead of next
Click to expand...
Click to collapse
Hello, I have the same problem as eddyed911, I get the same message when trying to install the drivers by following your procedure: "Windows could not find the driver software for your device."
To answer your question for him, I did unzip the file. Any ideas?
radinfinitum said:
Hello, I have the same problem as eddyed911, I get the same message when trying to install the drivers by following your procedure: "Windows could not find the driver software for your device."
To answer your question for him, I did unzip the file. Any ideas?
Click to expand...
Click to collapse
Choose let me pick and select the drivers folder
Sent from my GT-I9100 using xda app-developers app
kwibis said:
http://forum.xda-developers.com/showthread.php?t=895545 (FULL TUTORIAL)
http://forum.xda-developers.com/showthread.php?t=882815 (BIG FAQ)
Maybe all noobs need to read the BIG FAQ
Click to expand...
Click to collapse
thanks pals for that, i need that tutoreial so much!
I don't know if this is because it was already installed or what (I've had to work with several other Android phones for a project I'm involved with) but I couldn't get the zip to install either (are they Win8 drivers C4SCA? Didn't work on Win7 64bit). What I did do was select the device driver manually. Once in the driver list select Android Phone and then Android Bootloader Interface. In my case it listed Acer and Google so be sure to select Google if you have any options. Worked fine after that.
updated OP with google's nexus drivers download link
redmi note hmw 1 bootloader unlock tool required
hi all can any one help me in unlocking boot loader redmi note HM W1 fastboot symbol not comming
hero75 said:
hi all can any one help me in unlocking boot loader redmi note HM W1 fastboot symbol not comming
Click to expand...
Click to collapse
Better ask on a redmi note thread/forum
Has anyone successfully unlocked their bootloader using the above described method. Would like to hear feedback ...Thank You
Hi all
Im trying to compile OmniRom for Galaxy Note 2 N7100.
Did everything as instructed.
When running "brunch n7100" I have an error:
=============================================
build/core/product_config.mk:227: *** _nic.PRODUCTS.[[device/samsung/n7100/omni_n7100.mk]]: "vendor/samsung/smdk4412-common/common-vendor.mk" does not exist. Stop.
WARNING: Trying to fetch a device that's already there
build/core/product_config.mk:227: *** _nic.PRODUCTS.[[device/samsung/n7100/omni_n7100.mk]]: "vendor/samsung/smdk4412-common/common-vendor.mk" does not exist. Stop.
** Don't have a product spec for: 'omni_n7100'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
=============================================
What should I do to fix it?
Thanks
EDIT: OK, "The Muppets", of cause. Not it builds...
sms2000 said:
EDIT: OK, "The Muppets", of cause. Not it builds...
Click to expand...
Click to collapse
First off, I'd use DonkeyCoyote instead of TheMuppets. Entropy said TheMuppets wouldn't work, but he might have been speaking about only one device. Still I'd use DonkeyCoyote instead.
Still not building?
PonsAsinorem said:
First off, I'd use DonkeyCoyote instead of TheMuppets. Entropy said TheMuppets wouldn't work, but he might have been speaking about only one device. Still I'd use DonkeyCoyote instead.
Still not building?
Click to expand...
Click to collapse
I'm using VM on Win7 8Gb machine so it's slow. Last time it stopped on Email right after successfully building boot.img.
Attempting to rebuild.
I'll try my next with DonkeyCoyote.
sms2000 said:
I'm using VM on Win7 8Gb machine so it's slow. Last time it stopped on Email right after successfully building boot.img.
Attempting to rebuild.
I'll try my next with DonkeyCoyote.
Click to expand...
Click to collapse
It didn't not stop...
Actually it is compiling libchromodium.so (forget how it spell), which is 1.2GB in size.
Just let it run for few hours, it will completed eventually.
PS: I'm using VM on Win8.1 4GB, no complain here.
Sent from Windows 98
Yep, it fails again and again on 'libwebviewchromium.so'. The well known 'Error 1' aka not enough RAM.
I recently built a dedicated computer (8Gb + Haswell 3220) just for ROM compiler but have no time to install it properly. Dealing with VMs is not good.
My VM has 4Gb RAM of total 8Gb installed. I know I need 8+ but have to wait till new RAM received.
For now the thread is on hold.
Thanks for all your help.
EDIT: Just for the small experiment I added a 8Gb 'swap' partition to VM and the following build succeeded using no more than 450Mb of it.
I think we need 6 to 8Gb of RAM for good.
Now the question is would it boot and run for good? But we will see...
Ya I did set the swap partition to 8gb... And it will boot nicely.
If it didn't boot, jus replace/delete the media_profiles.xml
Another note, my Bluetooth and hardware decoding /encoding fail... Pls test it on ur system too.
Sent from Windows 98
dynomist said:
Ya I did set the swap partition to 8gb... And it will boot nicely.
If it didn't boot, jus replace/delete the media_profiles.xml
Another note, my Bluetooth and hardware decoding /encoding fail... Pls test it on ur system too.
Sent from Windows 98
Click to expand...
Click to collapse
I indeed failed to boot. Just the black screen with nothing. I think it was a very bad idea to use TheMuppets with "jallybean".
And what is "media_profiles.xml" for? And where?
U r using jb blob?
i think OmniRom hv all the stuff u need
http://docs.omnirom.org/Samsung_Galaxy_Note_II
___
Btw did ur screen show omnirom animation?
If yes u r lucky, u need to enabled the ro.adb.secure=0 in ur build.prop, then only you can use adb without authorization to troubleshoot.
Type# adb logcat > logcat.txt
___
Google media profile...
Sent from Windows 98
dynomist said:
U r using jb blob?
i think OmniRom hv all the stuff u need
http://docs.omnirom.org/Samsung_Galaxy_Note_II
___
Btw did ur screen show omnirom animation?
If yes u r lucky, u need to enabled the ro.adb.secure=0 in ur build.prop, then only you can use adb without authorization to troubleshoot.
Type# adb logcat > logcat.txt
___
Google media profile...
Sent from Windows 98
Click to expand...
Click to collapse
Yes, if you can download the closed source parts from the phone itself. I cannot. Something wrong with switching 'adbd' to 'root'. It switches sort of but locks at the downloading (never finishes).
Currently I'm recompiling with 'DonkeyCoyote'.
'Nightly' build fails to pass boot animation
I downloaded and installed OmniRom Nightly. Not good.
It cannot pass the boot animation. The OMNI BA just loops across different colors for 15 minutes already.
As I remember the same problem I have with any AOSP or CM ROM. I suspect the problem is the boot loader related.
When I installed my first 4.3 ROM it required the latest BL and I flashed it. Should I downgrade now? Which version of BL works for sure and where can I find it?
Thanks.
EDIT: I verified. My Bootloader - MJ5. Is it OK?
EDIT 2: Downgraded to DMF2 and succeeded installing OmniRom Nightly. Testing...
glad that you able to solve the booting prob...
pls update the roms status after u done with your testing
I have the N7 2012 rooted with wugfresh's program. Worked perfectly. Now, when I try to "install" the grouper ROM from TWRP, asks if the directory is correct. The directory is very long, and I have no idea if it is correct or not. I chose "xbin" at the end of the wugfresh rooting if that makes a difference.
Also, when I chose "Backup" in TWRP, it rebooted and showed the dead android. After a while, 5-7 minutes, it rebooted fine, but said backup failed.
Any help or complete walk throughs on these things?
Thank you so much for your time.
christoria said:
I have the N7 2012 rooted with wugfresh's program. Worked perfectly..
Click to expand...
Click to collapse
First of all, hello and congratulations on rooting your N7!
christoria said:
Now, when I try to "install" the grouper ROM from TWRP, asks if the directory is correct. The directory is very long, and I have no idea if it is correct or not..
Click to expand...
Click to collapse
What ROM are you talking about? Grouper is the Nexus 7's codename. It is used in all Android custom firmware to specify which Android device the firmware was made for. Therefore, you could be talking about any ROM from a reader's view.
e.g. pa_grouper-4.43-20140715.zip tells you that this Paranoid Android custom firmware was made for the Nexus 7 (2012)
Here is another example: omni-4.4.4-20140719-i9100-NIGHTLY.zip - Looking at this OmniROM custom firmware .zip, the codename tells us that the firmware was not designed for the Nexus 7 (2012), but for the i9100 - the Samsung Galaxy S II.
christoria said:
I chose "xbin" at the end of the wugfresh rooting if that makes a difference.
Click to expand...
Click to collapse
Could you explain more?
Thanks for the "grats", but the program did it - all I had to do was sweat for 3 minutes.
TWRP seems to give a list of code names when you install the recovery ROM. I believe mine is the "grouper" one. then it downloads it and tells me the directory it thinks it should go into - with a warning that I may brick the device if it's the wrong directory. the directory string is so long I don't know what is right. I would hope the program knew, but maybe not.
As far as "xbin" - at the end of wugfresh's rooting program, there is an option to select "bin" or "xbin" for something - "xbin" was recommended by the program, so I chose that.
Hope this helps - I really want to get the recovery ROM setup.
The su binaries can go into /bin or /xbin
Sent from my Le Pan TC1020 using Tapatalk