Related
Hi, I would like to De-Odex the rom I currently have on my phone.
Is there an easy way to do this?
I've read:
http://www.droidforums.net/forum/xeudoxus/47283-release-xultimate.html
and
http://www.droidxforums.com/forum/droid-x-themes/4620-how-manually-deodex-your-phone.html (there is also a post about this on here)
The xUltimate tool will not work for me, so I need another option.
Phone: HTC Evo
ROM: Stock 3.29 OTA
Rooted (ofc)
Thanks for the help.
Sorry if this is no help, but a deodexed version of the 3.29 OTA is posted somewhere in the dev section. Is there a particular reason why you want to deodex it yourself?
Sent from my PC36100 using XDA App
TheMagicalSock said:
Sorry if this is no help, but a deodexed version of the 3.29 OTA is posted somewhere in the dev section. Is there a particular reason why you want to deodex it yourself?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I've been switching between roms but I keep coming back to my original stock one. It's still odex'd and I would like to theme the battery icon on the status bar without having to set everything back up on a fresh rom. Since it reads half when 80% of my battery is remaining.
Thanks for the quick response.
Sent from my Evo using XDA App.
and you said this didnt work for you?
i didnt even know you could deodex your own rom!
going to try this soon!
Max_Pain said:
and you said this didnt work for you?
i didnt even know you could deodex your own rom!
going to try this soon!
Click to expand...
Click to collapse
It wasn't that it didn't work.
I just got an error with Java, not sure how to fix it. Some said to re install java, but i've installed JRE and JDK from 5u20 to 6u21 (32 and 64 bit). Everything I tried gave the same error.
I am going to try asking on their forum and see if they can tell me what I did wrong.
I have a feeling it has to do with the 3.29 OTA update. :-/
Good luck and if you get it to work please let me know your setup.
and if you can't run step 3 let me know... that way I am not the only one to seem that crazy.
option 1 and 2 just adb pulls your /system/apps and your framework.
just got stuck starting option 3:
Starting AccountSyncManager.odex
*Deodexing...
Error occurred while loading boot class path files. Aborting.
org.jf.dexlib.Code.Analysis.ClassPath$ClassNotFoundException....
lower it says
at org.jf.baksmali.baksmali.dissambleDexFile(baksmali.java:103)
and it just gives some more errors until i close it down
i was sooo excited to get this done!
Ahhh! I'll see what I can find out on their forums.
Despite the tutorial saying "Manually De-Odex Your Phone" I think it may be just for droid phones. It was posted in the Moto Droid sections of the forums.
Here is the error I was getting:
Code:
Exception in thread "main" java.lang.ExceptionInInitializerError
Caused by: java.lang.NullPointerException
at java.util.Properties$LineReader.readLine(Unknown Source)
at java.util.Properties.load0(Unknown Source)
at java.util.Properties.load(Unknown Source)
at org.jf.baksmali.main.<clinit>(main.java:69)
Could not find the main class: org.jf.baksmali.main. Program will exit.
Press any key to continue . . .
dang it...
i just updated my java and nothing, still same error. well let me know what they say. i was about to make an account to post over there but i'll let you do it then.
keep me updated!
Max_Pain said:
dang it...
i just updated my java and nothing, still same error. well let me know what they say. i was about to make an account to post over there but i'll let you do it then.
keep me updated!
Click to expand...
Click to collapse
If you want to add anything my post is located:
http://www.droidforums.net/forum/xeudoxus/85223-xultimate-errors.html
Both our problems have "org.jf.baksmali" involved.
Hopefully we'll have some answers soon.
well i ran a test and everything said pass, including the odex and deodex. i installed the latest java, and same problem. i had the phone originally as mass storage, so i tried under charge only, and still same problem.
i really hope we get a solution to this
I did some more reading and it seems that app is designed specifically for droid x phones.
I'm now going to try a more hands on approach using avabox...will update tonight.
Swyped from an HTC Evo on MetroPCS...
Max_Pain said:
I did some more reading and it seems that app is designed specifically for droid x phones.
I'm now going to try a more hands on approach using avabox...will update tonight.
Swyped from an HTC Evo on MetroPCS...
Click to expand...
Click to collapse
Were you able to get it DeOdexed?
I found this after some searching... It seems to be the LONG way to deodex an apk. It was written in 2009 so idk how reliable it will be.
http://androidnetwork.org/forum/viewtopic.php?f=11&t=55
Edit: Link to Avabox: http://forum.xda-developers.com/showthread.php?t=697459
[UPDATE] I tried Avabox and it de-odexed all of the files that I adb pulled. I copied the De-Odexed files back to their respective folder on the /system/, and deleted "rm /system/app/*.odex" (Removing all the .odex files) and rebooted.
I got stuck on the white "HTC Evo 4G" screen and could not get passed it.
I am not sure what I messed up. Maybe I need to resign the files? I'll try that tomorrow.
Let me know how your attempt went. :]
When I left for school I left the script deodexing my app folder...it seems to have done the job and there were no errors. It's doing the process for the framework files now.
Once I move it over to the phone we 'll see if it worked...
I'll update here when I find out...
Swyped from an HTC Evo on MetroPCS...
i just tried that too and i got stock in a bootloop.
the avabox script does deodex all the app files. it doesn't do that for the framework files...it seems it'll only deodex .apk files.
anyways, i deleted everything from my /system/app folder and then pushed over the deodexed apks...i also did this for the two apk files from system/framework and the phone did the bootloop thing. so i put back the original /system/framework files, effectively only leaving changed the contents of /framework/app/ and still, bootlooping.
i'm restoring right now...i'll try it some more at another time.
let me know if you figure it out!
I was reading some of the comments on this thread(http://forum.xda-developers.com/showthread.php?t=598026) They we're saying about problems with de-odexing the framework.
Do we need to resign system apps before we push them back?
I am optimizing my apks now, going to batch resign then try putting just the apks back on.
Well I messages avalaunchmods asking the same thing...if anyone knows it should be him...
Update if you get it working please!
Swyped from an HTC Evo on MetroPCS...
Unfortunately, I still don't have any good news. :[
I tried resigning the de-odexed apk's and replacing the ones on my phone.
This got stuck at the white HTC Evo 4G screen.
This failed
Then I optimized, signed, and zipaligned.
This threw me into an actual boot loop. (I was excited... It's the first boot loop i've gotten.)
This failed.
Here is some semi-less-bad news.
I used http://circle.glx.nl/ to make a flashable update.zip for theme-ing. I Flashed it with success and was able to get to the lock screen. Sense UI along with just about every other system app kept force closing.
But I was able to successfully (even though I got FC's) theme and boot using that kitchen.
I am going to mess around with the different settings there and see if I can atleast theme my phone.
Any luck with your attempts?
i was at school all day - no news from me. this is very discouraging though.
i'm surprised nobody else has chimed in! considering how many people are making and releasing roms, some people must know what's going on here
Good news (kinda)
I was able to theme my framework-res.apk without any errors or FC's.
I didn't do anything to De-Odex it but it accepted the theme when I manually edited it.
There must be an xml that scripts how the battery is displaying %'s
since I have 89% of my battery remaining but the themed battery is showing 80%.
I'll dig around and see where it is and add it to my next framework recompile.
We're you interested in just themeing or the whole de-odexing (apps & framework)
If you want to theme it i'll write up a decent tutorial on what I did.
If not I'll write up a quick tutorial for the next root newbie who wants to theme.
Going to test run it and make sure I didn't mess much up.
Edit3: The bad, it would appear that you can't modify the .xml's of the framework. You can only change the pictures.
So the battery wont be able to have the exact %.
Modifying of any .xml leads me to a boot loop.
Tips are appreciated on fixing this.
I'll keep trying.
so here is what i've learned.
i had modified both .com.htc.resources and framework-res before. those files, at least in my rom, are not odexed. everything else in the framework folder is a mix of files, .jar files and other formats, including services.jar, which is odexed. that's why if we change the services.jar file, without the phone being deodexed, it wont work.
that's why i want to deodex my rom. i have too many changes already and dont want to re-do them in another, deodexed rom.
my main interest in deodexing the rom is to have the working battery percentage on top (which used to work on THIS rom before, without deodexing???) and to have a transparent notification tray.
and from there being able to make any other changes as they come up...
i'll see when i have some more time to try out other options, but chances are you will have time before me, so keep updating!
so a friend of mine basically gave me this mytouch and i have no idea whats wrong with it and how to fix it.
i have some pictures attached below.
it boots up, then when im on the lockscreen and slide down, i get a force close and the my touch logo....then it reboots its self.
please help.
thanks
dapoharoun said:
so a friend of mine basically gave me this mytouch and i have no idea whats wrong with it and how to fix it.
i have some pictures attached below.
it boots up, then when im on the lockscreen and slide down, i get a force close and the my touch logo....then it reboots its self.
please help.
thanks
Click to expand...
Click to collapse
This happened to me when I deleted some widgets that Sense was using, but I was getting an HTC Sense force close. Not this. Are you rooted? If you don't know, download clockworkmod recovery for the slide and put it on the root of your SD card as update.zip and flash it via recovery. (you get to recovery through the bootloader, selecting recovery with the volume down key, and the power key to select it), and if it gives you a signature verification failure, then you are not rooted. If it succeeds, then flash CR_Mod OTA 1.35.xxx (forgot the exact number, it's in the dev section), and that should fix your problem.
MusicMan374 said:
This happened to me when I deleted some widgets that Sense was using, but I was getting an HTC Sense force close. Not this. Are you rooted? If you don't know, download clockworkmod recovery for the slide and put it on the root of your SD card as update.zip and flash it via recovery. (you get to recovery through the bootloader, selecting recovery with the volume down key, and the power key to select it), and if it gives you a signature verification failure, then you are not rooted. If it succeeds, then flash CR_Mod OTA 1.35.xxx (forgot the exact number, it's in the dev section), and that should fix your problem.
Click to expand...
Click to collapse
thanks for the reply sir.
i am about to try that now, just have no clue where to download clockwork recovery from. is there a specific one for just the mytouch?
thanks
dapoharoun said:
thanks for the reply sir.
i am about to try that now, just have no clue where to download clockwork recovery from. is there a specific one for just the mytouch?
thanks
Click to expand...
Click to collapse
Yeah, I attached the file you need, seems the clockwork site is temporarily down.
MusicMan374 said:
Yeah, I attached the file you need, seems the clockwork site is temporarily down.
Click to expand...
Click to collapse
ok so im not rooted, because i got a verification error. picture attached below.
whats next sir?
dapoharoun said:
ok so im not rooted, because i got a verification error. picture attached below.
whats next sir?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=754020
Follow that guide to root your phone, and then flash this: http://forum.xda-developers.com/showthread.php?t=747002
That will give you rooted stock as well as re-update your radio, since rooting downgrades your radio image. Let me know how that all goes
MusicMan374 said:
http://forum.xda-developers.com/showthread.php?t=754020
Follow that guide to root your phone, and then flash this: http://forum.xda-developers.com/showthread.php?t=747002
That will give you rooted stock as well as re-update your radio, since rooting downgrades your radio image. Let me know how that all goes
Click to expand...
Click to collapse
will try, but is it possible to root the phone when it wont turn on?
Any body?
please
dapoharoun said:
will try, but is it possible to root the phone when it wont turn on?
Click to expand...
Click to collapse
No, not that I know of
Sent from my T-Mobile myTouch 3G Slide
so if this beautiful phone broken for good!?!?!?
bump.......
dapoharoun said:
ok so im not rooted, because i got a verification error. picture attached below.
whats next sir?
Click to expand...
Click to collapse
Try the wipe data/factory reset option
agentg1001 said:
Try the wipe data/factory reset option
Click to expand...
Click to collapse
tried that....no luck
Try downloading the original ESPRING and put it on root of SD card the. Update it by turning on the phone using volume down and power
Sent from my T-Mobile myTouch 3G Slide using XDA App
Actually I revise that. It should be possible. Your phone isn't totally screwed, it boots at least. Look through the guide, I can't at the moment, and see if it actually requires your phone to be booted. I think you can do all of it through hboot and recovery, using adb and ESPRIMG.zip. I really don't remember though, read the guide, try to root your phone.
Sent from my T-Mobile myTouch 3G Slide
MusicMan374 said:
Actually I revise that. It should be possible. Your phone isn't totally screwed, it boots at least. Look through the guide, I can't at the moment, and see if it actually requires your phone to be booted. I think you can do all of it through hboot and recovery, using adb and ESPRIMG.zip. I really don't remember though, read the guide, try to root your phone.
Sent from my T-Mobile myTouch 3G Slide
Click to expand...
Click to collapse
yeah ALMOST!!!!!!
i was going thru the steps well, but then adb wont recognize the phone in the command prompt becasue it is on "diskdrive" not "chargeonly"....witch i cant change. if only i could change it
purple1 said:
Try downloading the original ESPRING and put it on root of SD card the. Update it by turning on the phone using volume down and power
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
ESPRIMG.zip... Why does everyone think it's ESPRING?
dapoharoun said:
yeah ALMOST!!!!!!
i was going thru the steps well, but then adb wont recognize the phone in the command prompt becasue it is on "diskdrive" not "chargeonly"....witch i cant change. if only i could change it
Click to expand...
Click to collapse
You can use ADB while in recovery mode, try doing the commands in recovery mode, using clockwork recovery. Although that may not work because it requires toggling wifi. See if you can find and try other rooting methods? There a few different ones out there. Your phone boots into the OS.
I googled around, found that account syncs were causing com.htc.bg to crash. I also noticed that your phone was booting without a sim card in it? Might be a stupid question, but you HAVE tried booting it WITH a sim card right? I also noticed that your hboot date is march 23rd, almost a year ago..?
http://forum.xda-developers.com/showthread.php?t=746577
Do that. Will completely restore your phone.
migueltherocker said:
http://forum.xda-developers.com/showthread.php?t=746577
Do that. Will completely restore your phone.
Click to expand...
Click to collapse
thanks...i tried that but i got and error...pic below
dapoharoun said:
thanks...i tried that but i got and error...pic below
Click to expand...
Click to collapse
That's odd, never seen that one before. My only suggestion would be to try and re-download the zip file, see if it was just a bad download. Otherwise I've got nothing.
I've been trying to root my G2 since last night, and before I start, I have to say I do NOT and WILL NOT have access to adb. Some drama with my father caused him to revoke my administrator privilages on all the computers in my house. So I can't install anything or run any unknown .exe's.
The only way I can go about this is using Visionary so far. However, it's been a piece of crap up to this point. I have +r14, USB debugging enabled. Regardless of whether I check "Set system to r/w after root", I always get the same two results when i hit Temproot.
Sometimes it'll go through a couple of triangle screens w/ "rooting device, please wait" and then go back to the main option screen. However, this seemed to do nothing but install Superuser with NO APPS requesting su permissions. After this I'll try to hit "Attempt Permroot now" and it will say "Please Temproot before attempting Permroot". "Unroot now" just says my device isn't rooted. >_> Going into terminal and typing "su" gives me a "su: Permission denied".
Other times when I hit Temproot, it'll go through a few triangle screens, and then just stop on a black screen with only the status bar visible. I can still Home out and use the notification bar and such though, so it's not a total system freeze.
Can someone please help me out here? I ordered my phone on 2/4/11 and got it maybe a week later if that makes any difference, because I've been hearing some things about people not being able to use Visionary on newer phones.
Try using this GUDIE HERE. No ADB needed.
I've tried that guide and one of the two scenarios I provided always happens. :\
I got my phone brand new from the tmo corp store sat night and I had no problem with rooting via visionary and gfree.
Mine did not have that 1.72 update tho. Maybe that's your problem.
From my permarooted overclocked HTC G2 with cyanogen 7 nightly via XDA app
tackleberry said:
I got my phone brand new from the tmo corp store sat night and I had no problem with rooting via visionary and gfree.
Mine did not have that 1.72 update tho. Maybe that's your problem.
From my permarooted overclocked HTC G2 with cyanogen 7 nightly via XDA app
Click to expand...
Click to collapse
Tmobile phones don't get the 1.72 updates, that's only for the desire Z's, Tmobile G2's only have the 1.19 or the 1.22 OTA roms on it.
Sent from my HTC Vision using XDA App
How do I check what update I have? (I heard having Wifi tethering and Wifi calling affects that, I have both)
legendaryxm90 said:
How do I check what update I have? (I heard having Wifi tethering and Wifi calling affects that, I have both)
Click to expand...
Click to collapse
If you have wifi calling and tethering built-in, then you have the 1.22 OTA update already (I think all of the newer G2's come with it). I'm not sure if it shows up anywhere you can check easily, but I do know the OTA came with a newer radio so you could check in your Settings->About phone. The baseband version should end in something like 26.03.02.08.
The version number is also stored on partition 17, but I don't think you can check that without at least temp root. Not positive though.
I have no idea why Visionary is having problems even temp rooting your phone. One problem may be that you tried the permroot function within it (I don't know what it does, but many users have reported strange behavior when it doesn't work right).
Maybe you can try doing a factory reset and then starting again. Also, you might want to try disabling all of the added functionality in Visionary (such as temp rooting or setting system as R/W on boot), restarting the phone, and then trying the temp root again. Or uninstalling Visionary and then reinstalling it.
If you can just get su to work in terminal, then you should be okay.
joemm said:
Tmobile phones don't get the 1.72 updates, that's only for the desire Z's, Tmobile G2's only have the 1.19 or the 1.22 OTA roms on it.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
me=de de dee! lol. thanks for that info. i didnt know that specific detail.
Ok, so I just factory reset my phone, and I'm going to try this with a fresh downloaded r14. Gonna try with no options checked. Also, is it better to do this with the phone connected to the computer or not?
EDIT: OK here's what I was talking about. -_- Just tried it TWICE. First time it went back to the option screen, Terminal gives me su: permission denied again. Did it a second time. Currently stuck on a black screen w/ only status bar visible. WTF IS GOING ON MAN.
legendaryxm90 said:
Ok, so I just factory reset my phone, and I'm going to try this with a fresh downloaded r14. Gonna try with no options checked. Also, is it better to do this with the phone connected to the computer or not?
EDIT: OK here's what I was talking about. -_- Just tried it TWICE. First time it went back to the option screen, Terminal gives me su: permission denied again. Did it a second time. Currently stuck on a black screen w/ only status bar visible. WTF IS GOING ON MAN.
Click to expand...
Click to collapse
Not sure what's happening. How long are you waiting on the blank screen? I've seen some people say the temp root took a while on their phones. I saw in one of the forums (maybe dev), someone posted another app that can achieve temp root as well. Might be worth taking a look...
I waited 15-20 minutes and nothing. >_> I'll look for that other app because I just read somewhere that VISIONary doesn't work on the latest OTA phones. Is that true?
EDIT: Haven't found anything. Is there ANY hope for me without adb? :<
Here's the other temp root program someone mentioned: http://forum.xda-developers.com/showthread.php?t=951208
Never tried it myself but maybe it'll work for you.
Also, I think the thing about Visionary not being compatible for OTA phones was only for the permroot option. Like I said, people have reported really strange behavior when it doesn't work.
Just thought of another thing to try. Maybe clear the data for the superuser app. Hopefully when you try su in terminal then, it'll pop up with the dialog box asking for permissions again.
ianmcquinn said:
Just thought of another thing to try. Maybe clear the data for the superuser app. Hopefully when you try su in terminal then, it'll pop up with the dialog box asking for permissions again.
Click to expand...
Click to collapse
D'OH. THAT DID IT. Got the superuser popup!
THANK YOU SO MUCH!! +REP
So my USB port on my Epic is messed up. It charges just fine but it wont connect to the computer. So I want to unroot my phone so I can take it into Sprint.
I haven't been able to find a method for unrooting the phone with out using a USB cord though. I was wondering if it was possible or not.
Thanks,
Daniel
Just flash the stock rom in .zip form and you'll be good to go, Sprint reps aren't going to look for a custom recovery.
Well the thing I was worried about is if they noticed that I was on 2.1 still and tried to update it to the latest one. It would obviously fail.
Is this an original ROM that would work? http://forum.xda-developers.com/showthread.php?t=786266
I will give you a link for stock EC05, what are you running now?
Well, actually I guess I am running just the stock 2.1 rom now that I think about it. I never got around to flashing a custom rom (was trying to a few weeks ago and realized the usb stopped working). But I do have several applications installed that require super user. So do you think I could just remove those and no one at sprint would really notice?
Thanks,
Daniel
You should be fine, I'm assuming you don't have a custom kernel, boot animation, or any modification on the stock Rom, right?
Nope never got around to any of that. Okay well I will see how it goes then. Thanks for your help.
edit: dumb question but how do I uninstall the root user application that manages the su permissions? It is only app left that shows it is rooted.
pierce71588 said:
Nope never got around to any of that. Okay well I will see how it goes then. Thanks for your help.
edit: dumb question but how do I uninstall the root user application that manages the su permissions? It is only app left that shows it is rooted.
Click to expand...
Click to collapse
The sdx stock app removal tool should work for that. Superuser.apk is kept in the same place as the other system apps
Sent from my SPH-D700 using XDA Premium App
Sweet! Thanks guys for all of the help! Hopefully I can get the USB fixed now!
Did you try a different cord? Stock sammy cords are known to be crap.
Ya I have tried different cords as well as different computers. Plus I know a few other people with Epics and their's have no issue at all.
Hey everyone I am getting a new phone and would like to use my Inc as a mp3 player. I'm looking for a Wifi only ROM not script. If any roms have a wifi only mode that you can choose when you first pick a Tom that would be great. Thanks for any suggestions
Sent from my ADR6300 using XDA
Bump
Sent from my ADR6300 using XDA
bmx5494 said:
Hey everyone I am getting a new phone and would like to use my Inc as a mp3 player. I'm looking for a Wifi only ROM not script. If any roms have a wifi only mode that you can choose when you first pick a Tom that would be great. Thanks for any suggestions
Click to expand...
Click to collapse
Is there a reason why you don't want the script? The beauty of the script is that you can use any ROM you want and use the script to make it wifi-only. Most people pick a ROM that they like and get good battery life with, and then just apply the script.
Aside from the couple of seconds it takes to flash the script, I cant envision any real benefit of having a ROM designed to be wifi-only vs. a ROM made to become wifi-only.
I'm also not sure what picking a "Tom" means... but it's probably not as important as my first question.
Really I did not know that. So when I flash the script what will change on the Rom? And do I need to wipe everything before I flash the script? Oh and spell correct changed Rom to tom and I didn't catch it...........
Sent from my ADR6300 using XDA
bmx5494 said:
Really I did not know that. So when I flash the script what will change on the Rom? And do I need to wipe everything before I flash the script? Oh and spell correct changed Rom to tom and I didn't catch it...........
Sent from my ADR6300 using XDA
Click to expand...
Click to collapse
As far as I know, it doesn't "change" anything... it just disables the radios (except wifi). Think of it like putting your phone in Airplane mode, but the wifi still works. As for wiping, I'm not sure. I've never used the script before.
demarcmj said:
As far as I know, it doesn't "change" anything... it just disables the radios (except wifi). Think of it like putting your phone in Airplane mode, but the wifi still works. As for wiping, I'm not sure. I've never used the script before.
Click to expand...
Click to collapse
Actually wifi works with airplane mode on you just have to turn wifi back on. However with sense you have to do that every boot, not on aosp though. Because of this and to avoid draining battery, the script sounds better for the op.
Sent from my Galaxy Nexus using Tapatalk 2
demarcmj said:
As far as I know, it doesn't "change" anything... it just disables the radios (except wifi). Think of it like putting your phone in Airplane mode, but the wifi still works. As for wiping, I'm not sure. I've never used the script before.
Click to expand...
Click to collapse
All the script does is install a startup script that runs another system script called "radio_options" in /system/bin with an option of 1, dissabling the radio. No wiping is required, and can be removed at any time.
Thanks this helped a lot!
Sent from my ADR6300 using XDA
does anyone have a link to such a script? I remember seeing one a while back but I can't find it anymore. I have turned my D2G into an mp3 player device so I was hoping for the same outcome. Plus it's cleaner to not have a radio attempting to connect all the time.
EDIT: Nevermind, I was under the impression it was a script one would flash, not something you could do yourself with script manager.
nschiwy said:
does anyone have a link to such a script? I remember seeing one a while back but I can't find it anymore. I have turned my D2G into an mp3 player device so I was hoping for the same outcome. Plus it's cleaner to not have a radio attempting to connect all the time.
EDIT: Nevermind, I was under the impression it was a script one would flash, not something you could do yourself with script manager.
Click to expand...
Click to collapse
You just make a file with no extension and then put this in it
Code:
#!/system/bin/sh
radiooptions 1
Then pop the file in your init.d folder if your rom/kernel supports it, or use an app like script manager or autostart root to run the file at boot. Note if using an app to run at startup, you must set the app to run it with root permission.
cmlusco said:
You just make a file with no extension and then put this in it
Code:
#!/system/bin/sh
radiooptions 1
Then pop the file in your init.d folder if your rom/kernel supports it, or use an app like script manager or autostart root to run the file at boot. Note if using an app to run at startup, you must set the app to run it with root permission.
Click to expand...
Click to collapse
I wrote this script using script manager and gave it root permissions and startup permissions and then ran it (also tried rebooting) and it didn't seem to do anything. Are there any visible changes that would take place when you do it?
nschiwy said:
I wrote this script using script manager and gave it root permissions and startup permissions and then ran it (also tried rebooting) and it didn't seem to do anything. Are there any visible changes that would take place when you do it?
Click to expand...
Click to collapse
Yes, the signal bars will grey out and have a white X over them.
Try using a terminal emulator app and type in
Code:
su - Hit Enter
radiooptions 1 - Hit Enter
You should see the signal bars X'd out.
cmlusco said:
Yes, the signal bars will grey out and have a white X over them.
Try using a terminal emulator app and type in
Code:
su - Hit Enter
radiooptions 1 - Hit Enter
You should see the signal bars X'd out.
Click to expand...
Click to collapse
this is what i got when I tried to do that, it didn't seem to change anything.
it's the same image that shows that it doesn't have any signal because there is no number attached to it anymore.
It looks like it worked, the bars are greyed out and has an X. Even if there is no telephone number associated with the phone, it will still show the signal bars as it will still communicate with verizon just not have service.
cmlusco said:
It looks like it worked, the bars are greyed out and has an X. Even if there is no telephone number associated with the phone, it will still show the signal bars as it will still communicate with verizon just not have service.
Click to expand...
Click to collapse
haha well in that case there might be something wrong with the phone because it has been like that since I flashed the ROM but it doesnt really matter since I don't need it.