Related
laymil has posted a much better script for this. As such I will be discontinuing my work on this for now. Not for any hard feelings, but because it is now beyond me to help any further.
As always I am glad to have helped the community in some small way. Thank you all
CHEERS
Geniusdog254 Posted the exact lines in the build prop that needed to be changed. This is a pretty common fix for problems like this between versions of Android. There was some concern however that you may miss some of the newer apps released only for Froyo. I wrote some simple scripts that will fix this for us.
Simply: One puts the Froyo build.prop on your phone. The other puts the modded build.prop on your phone.
Prerequisites
YOU MUST HAVE GSCRIPT INSTALLED
YOU MUST HAVE BUSYBOX INSTALLED
(IF YOU ARE USING PAULS FROYO ROM FROM HERE
http://forum.xda-developers.com/showthread.php?t=686631
IT DOES NOT HAVE BUSYBOX INSTALLED
Also--
There are now 2 downloads.
One will reboot your phone automatically
One will not!
(I recommend this one for anyone that has problems, or doesn't know ADB well.)
Installation
Code:
Download the attached .zip file
Place the "buildprop" folder in the root of your sdcard
Place both "Normal_Froyo.sh" and "Modded_Froyo" files in the gscript folder on your sdcard
Code:
Open Gscript
Press menu and select Add Script
Press Load File button
Select Normal_Froyo file
Press Save button at bottom
Repeat for Modded_Froyo file
After that all you have to do is open gscript and select which one to run.
Normal_Froyo will give you stock froyo build.prop and let you see froyo only apps
Modded_Froyo will give you the market fix build.prop
You can also create shortcuts directly on your homescreen for each script if you wish
-----------------------------------------------
I've decided to skip the update.zip, I've found no way to copy the scripts to the gscript folder on the sdcard this way.
I'm going for an app instead.
P.S. I've never written an app before, java looks like russian to me lol. So if anyone has any tips, or knows any good tut's let PM me and let me know.
------------------------------------------------
fixed no buildprop folder
added NON-autoreboot download.
buildprop switcher v0.3.zip ORIGINAL
buildprop_switcher_no_rebootv0.3.zip NO REBOOT
buildprop swticher v0.3.1.zip DOWNLOAD THIS ONE
When the file is unzipped, there are 4 files - No Buildprop folder. Now I get the part about putting the two .sh files into Gscript folder.
Do I make another folder called buildprop and put build.2.1 and build.2.2 inside?
OR
Do I put build.2.1 and build.2.2 onto the root of the SDCARD?
Dayz xx
Dayzee said:
When the file is unzipped, there are 4 files - No Buildprop folder. Now I get the part about putting the two .sh files into Gscript folder.
Do I make another folder called buildprop and put build.2.1 and build.2.2 inside?
OR
Do I put build.2.1 and build.2.2 onto the root of the SDCARD?
Dayz xx
Click to expand...
Click to collapse
So sorry lol Didn't notice until I was making the update.zip that I didn't put the other files in a folder IN the zip. Just make a folder on your sdcard called buildprop. and put them in there.
BTW testing the flashable update.zip method right now
thx, seems to work
so no more *#*#etc.. afterwards?
watercool said:
thx, seems to work
so no more *#*#etc.. afterwards?
Click to expand...
Click to collapse
Right.. the checkin service runs on each reboot. So it is not needed.
Worked just fine, but I did have to do the checkin thing. Possibly had poor signal but checkin hadn't done on reboot. Worked fine after that...
Dayz xx
followinginsanity said:
Right.. the checkin service runs on each reboot. So it is not needed.
Click to expand...
Click to collapse
Can the checkin method be used, instead of rebooting? I'd much rather switch back and forth via checkin rather than having to reboot.
Thanks.
Namuna said:
Can the checkin method be used, instead of rebooting? I'd much rather switch back and forth via checkin rather than having to reboot.
Thanks.
Click to expand...
Click to collapse
The reboot is built into the script. On my phone, if I checkin, the apps still don't show till I reboot. But show if I only reboot. If checkin alone works for you though, you can remove the reboot command from the script.
I'm not sure what happened, but after following the instructions exactly, my phone crapped. It got as far as the first nexus logo (non-animated), then the buttons lit up and I got a black screen. And that's how it stayed.
Any ideas?
This worked great for me I also solved my (unrelated) prob with SlideIt by forcing the dictionary to save in the settings, so I'm no longer bothered about losing shortcuts stuff on a reboot.
Dandy!!
tested again with a second n1. works perfect! automated checkin works perfect.
Can you please post what changed in the .prop file.
Also you didn't add the video codecs in the "new" prop file
InGeNeTiCs said:
I'm not sure what happened, but after following the instructions exactly, my phone crapped. It got as far as the first nexus logo (non-animated), then the buttons lit up and I got a black screen. And that's how it stayed.
Any ideas?
Click to expand...
Click to collapse
Mine did this as well, though I am unsure why just yet. Been busy all day.
Mikey1022 said:
Can you please post what changed in the .prop file.
Also you didn't add the video codecs in the "new" prop file
Click to expand...
Click to collapse
The only thing I changed from the stock to the "modded" build.prop were these 2 lines
from this
ro.build.description=passion-user 2.2 FRF50 38042 release-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF50/38042:user/release-keys
to this
ro.build.description=passion-user 2.1-update1 ERE27 24178 release-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.1-update1/ERE27/24178:user/release-keys
I didn't add anything else to these. If you would like other things added to the build.prop files. You are welcome to edit them yourselves, or let me know what things you want changed, and I can include them.
I can make it user friendly. With descriptions for each modded line, then you can simply un-comment the options that you want.
PS: I thought I had the flashable update ready, but the update-script is giving me problems. ANYONE that wants to help please let me know. I'd really like to get this out to everyone.
InGeNeTiCs said:
I'm not sure what happened, but after following the instructions exactly, my phone crapped. It got as far as the first nexus logo (non-animated), then the buttons lit up and I got a black screen. And that's how it stayed.
Any ideas?
Click to expand...
Click to collapse
same thing here....ANY IDEAS????????????
This is a great find, inductions were perfect and easy to follow. Not one issue getting all my paid apps back! Thank again!
JDMSirEK4 said:
same thing here....ANY IDEAS????????????
Click to expand...
Click to collapse
To anyone that can't get thier phone to boot all the way after doing this
Its not a big deal. Your phone booted. But the build.prop didn't get copied before the reboot.
If you did a nandroid before you tried it. Restore that!
If you didn't, OR you know how to use adb. Do this
Code:
adb remount
adb push [COLOR="red"]/path/to/build.2.1(or)build.2.2[/COLOR] /system/build.prop
adb reboot
I hope to have this fixed quickly.
ANYONE WHO'S PHONE WILL NOT BOOT AFTERWARDS!
Check and make sure you put the files in the right place.
build.2.2
&
build.2.1
go in
build.prop FOLDER ON YOUR SDCARD
that was the only reason I got the error, i deleted the files off my card when i was testing the flashable update.
If you still get an error. open both files in the gscript folder, and remove or comment out the reboot line. Then tell me what error you get in gscript.
So I did this and am able to see the new apps. When I reboot the phone I cannot see a bunch of old apps in my launcher. I revert to the normal script and reboot again and still cannot see a bunch of my apps. Appbrain says theyre installed and I can open them from there but no widgets or shortcuts for them Any Ideas?
r0adki111 said:
So I did this and am able to see the new apps. When I reboot the phone I cannot see a bunch of old apps in my launcher. I revert to the normal script and reboot again and still cannot see a bunch of my apps. Appbrain says theyre installed and I can open them from there but no widgets or shortcuts for them Any Ideas?
Click to expand...
Click to collapse
Are those apps moved to the SD by any chance? If so, best bet is to go to Settings>Applications>Manage Applications>Find your launcher, and force stop it. Should work after that.
dictionary said:
Are those apps moved to the SD by any chance? If so, best bet is to go to Settings>Applications>Manage Applications>Find your launcher, and force stop it. Should work after that.
Click to expand...
Click to collapse
Nope they're not on SD. I'll try the fc of launcher.
Ok it worked thank you! but my xiia widget still is not back and I'm assuming others. Anything I can do for the widgets?
Ok installed and reinstated the app. Works great thx again.
Update:
Ok after another reboot, apps don't show again. FC the launcher they come back but not the widgets.. Grrrrrr...
Here is the correct way to use root explorer for manually replacing system files:
1. Mount the system as r/w (read/write) per the top right corner. Navigate to the file that you plan to replace (e.g., system/framework/framework.jar).
2. Copy (not move) the file and paste it somewhere on your SD card (internal or external, doesn't matter - as long as you can locate it in case you need to put it back). Rename the file you just pasted, but very subtly. For example, when renaming framework.jar, I would only throw something in front of the file name, such as "Backup - framework.jar", so I can easily distinguish it from the new file if I put them in the same spot.
3. NANDROID BACKUP!
4. Download/put on your sd card (whatever you do) the new file that you want to replace the old one with.
5. Move the new file to /system (not in a subfolder yet). Here you will change the permissions, which is crucial to avoid FCs and problems. In root explorer, you would long press the file, press permissions, and set them to whatever the old file's permissions are. This may require going to verify what they are before starting this step. For example, in a lot of cases, the permissions will be RW-R-R. In Root Explorer, this would mean checking the first two boxes on the first line and only the first box on the next two lines. In any situation, confirm that the permissions you see after you've changed them (right below the file name) match exactly what you're replacing.
6. Ensure that your new file is correctly named to exactly what it is replacing (case actually matters) and double check the permissions.
7. Move your new file to the folder, root explorer will ask if you want to replace the file. Confirm.
8. Back out of root explorer and immediately reboot.
No force closes, no problems .
It may seem like a lot to someone who doesn't do it often but for me, I actually do this method faster than any other and fly through it every time. I got tired of seeing people explain ways to use Root Explorer which result in bootloops, FCs, etc. without fail. So, I decided to put an end to it.
Great post Simba501! Thank you for this...
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Audiochild said:
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Click to expand...
Click to collapse
Toggle "Mount R/W" button at the top.
Audiochild said:
Great post Simba501! Thank you for this...
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Click to expand...
Click to collapse
Sounds like you need to mount \system as read-write. There is a button in the upper right corner of root explorer to mount
Sent from my SGH-I777 using XDA App
Thanks wonner and kbilly70! That was the issue
Awsome. Bookmarked!
thanks for the awesome guide. worked great for me!
Thanks, that clears things up.
I'm still wondering, though, how does one handle certificate files etc? For example, the ones found in this fix provided by zdzihu, in the META-INF folder.
kZard said:
Thanks, that clears things up.
I'm still wondering, though, how does one handle certificate files etc? For example, the ones found in this fix provided by zdzihu, in the META-INF folder.
Click to expand...
Click to collapse
Those are only for flashing purposes. Not needed if you're not flashing it. You only need to pull everything besides that folder and place them appropriately.
Using this method resulted in "app not installed" tried it with black Google search box, and just now with Mms.apk rw-r--r-- backed up old one, but method didn't work... had to nandroid last time because phone wouldn't let me install backup or market version. Looks like I'm in for it again. fudge. what went wrong?
System folder was r/w and moved apk into system/app said OK to overwrite and used hard key back button to exit root explorer. Hard key power button and selected reboot within 1-4 seconds of moving apk over system app.
Edgarhighman said:
Using this method resulted in "app not installed" tried it with black Google search box, and just now with Mms.apk rw-r--r-- backed up old one, but method didn't work... had to nandroid last time because phone wouldn't let me install backup or market version. Looks like I'm in for it again. fudge. what went wrong?
System folder was r/w and moved apk into system/app said OK to overwrite and used hard key back button to exit root explorer. Hard key power button and selected reboot within 1-4 seconds of moving apk over system app.
Click to expand...
Click to collapse
You don't install it after placing it. Placing it in the folder does install it. If you put it there, ensure the permissions are correct, and reboot, it should work.
EDIT: I don't see any mention of setting the permissions, so that was probably the issue. Again, no need to "install" it; just put it in the appropriate folder and set the permissions.
Simba501 said:
You don't install it after placing it. Placing it in the folder does install it. If you put it there, ensure the permissions are correct, and reboot, it should work.
EDIT: I don't see any mention of setting the permissions, so that was probably the issue. Again, no need to "install" it; just put it in the appropriate folder and set the permissions.
Click to expand...
Click to collapse
I did state the permissions. It's in your quote lol. Your method caused my phone to say app not installed. I had trouble getting the default app back after your method failed. Why didn't it work? I'm telling you I followed it to a T.
Sgs2, android 2.3.6, unnamed rom, December 2011 entropy kernel
Edgarhighman said:
I did state the permissions. It's in your quote lol. Your method caused my phone to say app not installed. I had trouble getting the default app back after your method failed. Why didn't it work? I'm telling you I followed it to a T.
Sgs2, android 2.3.6, unnamed rom, December 2011 entropy kernel
Click to expand...
Click to collapse
If the apk is compatible, it will work. At no point should you get an "application not installed" prompt, unless you attempted to manually install it at some point. If it wouldn't work, it just wouldn't appear in the app drawer: no prompt.
I guess this should be mentioned in the OP, but some times, clearing data of the application may be necessary after finishing. Usually a force stop at the most will allow you to see changes (which is why the steps include a reboot). You've piqued my interest. Post the files of question and I'll see if they work on my device. There was a similar issue someone else was having; I told him to redownload the apk and that was the problem. Some kind of botched file/download.
Sent from my Galaxy S II (i777)
can you edit or create new folders in the /sys directory?
mikoal said:
can you edit or create new folders in the /sys directory?
Click to expand...
Click to collapse
No. Why would you want to?
Sent from my Galaxy Tab 10.1
Simba501 said:
No. Why would you want to?
Sent from my Galaxy Tab 10.1
Click to expand...
Click to collapse
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
mikoal said:
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
Click to expand...
Click to collapse
You can edit and create new folders in that directory, but there's just no need to, unless you want to break the functionality of your phone.
mikoal said:
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
Click to expand...
Click to collapse
Idk: that's the only one I've seen. I've created folders in other directories. At any rate, virtually every modification you'll ever make will be in /data or /system.
dsmboost said:
You can edit and create new folders in that directory, but there's just no need to, unless you want to break the functionality of your phone.
Click to expand...
Click to collapse
It fails if attempting to create it within Root Explorer. You could use other means though (on a PC, an edited ROM zip, or potentially another root file manager). But again, no real reason to: other than for development purposes, perhaps. I'm no developer though, so I can't say.
Sent from my Galaxy Tab 10.1
Simba501 said:
Idk: that's the only one I've seen. I've created folders in other directories. At any rate, virtually every modification you'll ever make will be in /data or /system.
It fails if attempting to create it within Root Explorer. You could use other means though (on a PC, an edited ROM zip, or potentially another root file manager). But again, no real reason to: other than for development purposes, perhaps. I'm no developer though, so I can't say.
Sent from my Galaxy Tab 10.1
Click to expand...
Click to collapse
Ah okay, I was referring to ES file explorer, which can modify other files in that directory.
thanks to you both!
Ok (after rooting) here is how I installed GApps (Market, Google Framework, etc) on the Nook Tablet, as well as the steps I took to stabilize everything...
1. Downloaded GApps package from goo-inside.me and extracted files.
2. Deleted the setupwizard.apk file from the set of extracted files (in the system\app folder).
3. Copied "system" folder from extracted files to tablet via USB.
4. Used Root Explorer to remount /system and copy files into their designated locations, and also set permissions (644) on all copied apk's in /system/app folder.
5. Rebooted.
6. Ran the market, signed in with my Google account, and downloaded/installed Superuser. Ran the binary update within the app.
7. Install any additional apps from Android Market.
8. Profit.
Known issues...
1. If setupwizard.apk ends up on your tablet you will not be happy.
2. A factory reset is recommended after installing GApps (though probably not necessary).
3. Not all apps show in the Market. Perhaps a build.prop tweak will fix this???
Enjoy!!!
this is a second good news after rooting!
anlong:
Use either wireless adb found here: https://market.android.com/details?id=siir.es.adbWireless
or use debugging toggle found here: http://code.google.com/p/secure-set.../detail?name=ADBWidget-0.2-alpha.apk&can=2&q=
^ instructions for that:
Download ADBWidget.apk
Copy ADBWidget.apk to /system/app (you can use root explorer or something.)
Add ADBWidget to your home screen
Anlog,
I was able to get SuperUser installed following the directions on the other discussion! Thanks for much for all your hard work.
Working on getting Google Apps installed right now.
Update: Well I have SuperUser on my Nook, but whenever I try to copy anything to \system\app it tells me I don't have permissions. Looks like I can't get root to actually run.
run chmod 4755 /system/bin/su
which version of Gapps do I need Cyanogen 6 MDPI?
Make sure root is fully working before you try to install GApps. Use the latest ones for CM7 (I think its from August). You need to remount /system as RW before copying the files and setting permissions. Root Explorer lets you do all of that.
All of this could be done with an ADB script as well, but I won't have time to write one today. Anyone?
anlog said:
3. Not all apps show in the Market. Perhaps a build.prop tweak will fix this???
Enjoy!!!
Click to expand...
Click to collapse
Chainfire should fix it too, and youll be able to run all the tegra 2 also.
Drewmungus said:
Chainfire should fix it too, and youll be able to run all the tegra 2 also.
Click to expand...
Click to collapse
Do not install chainfire! I just tried it and it boot-looped, had to force factory restore.
Finally figured out what was wrong initially, root does not seem to work unless you manually enter commands. Attempted market setup, for some reason it is still force closing every time. Any chance someone who got it working could upload exact files they used.
bkerk25 said:
Finally figured out what was wrong initially, root does not seem to work unless you manually enter commands. Attempted market setup, for some reason it is still force closing every time. Any chance someone who got it working could upload exact files they used.
Click to expand...
Click to collapse
What gapps did you use?
I used the cyanogen 7 universal gapps.
Well, I may have royally screwed up. I followed this tutorial, and I copied over the entire Apps folder from the gapps download. Now I get numerous force closes, and I have no keyboard! Any suggestion?
theundeadelvis said:
Well, I may have royally screwed up. I followed this tutorial, and I copied over the entire Apps folder from the gapps download. Now I get numerous force closes, and I have no keyboard! Any suggestion?
Click to expand...
Click to collapse
I ran into issues copying the whole folder over. I am currently running the google market though.
do everything one step at a time, install the googleframework first (from the directions on the kindle page), then do the market. I ran into the first time through the market would not actually connect so I rebooted the NT.
*note*
each time you reboot your NT you need to go in and what appears is toggle the usb debugging off then on, same with the "auto mount", and I did the unknown sources as well (not sure if this is necessary). It appears a reboot resets the flags and our menu isn't actually writing the settings so you have to toggle it.
Push comes to shove, start over with fresh reboot. It took me a few times (as it probably did others as well).
ok, so can someone who is patient tell me where I need to copy the system folder? help the feeble minded, please.....
JoeM01 said:
ok, so can someone who is patient tell me where I need to copy the system folder? help the feeble minded, please.....
Click to expand...
Click to collapse
lol, i have been struggling with this exact same thing. for those of us who cant fill in the blanks of the brief instructions we need an exact step by step please
suicideclown said:
lol, i have been struggling with this exact same thing. for those of us who cant fill in the blanks of the brief instructions we need an exact step by step please
Click to expand...
Click to collapse
It needs go in system/apps
Drewmungus said:
It needs go in system/apps
Click to expand...
Click to collapse
i'm copying from the system/apps directory (unzipped gapps files), to where on the nook?
I tried copying the files into several locations, but nada.
this is literally the last thing need to knock out for me to be set until the days of ported roms.
please. halp (lelu dallas, multipass).
Drewmungus said:
It needs go in system/apps
Click to expand...
Click to collapse
that part is clearly stated but using root explorer and getting it to mount doesnt seem to work properly on my device. I have root and superuser. titanium backup works fine. for some reason root explorer on es explorer says it fails every time
-1 Go download latest Gapps and extract the contents to your HD. There will be two folders, one of which is "system."
-2 In the system folder there will be more folders, one of which is "app." Inside of app are all the system APKs.
-3 Detele SetupWizard.apk
-4 Now copy the app folder to the root of your NT SD card via USB.
-5 Next step you need to use ADB or Root Explorer...I used Root Explorer.
-6 Open root explorer, then go to sdcard and you should see the APP folder you copied.
-7 Once there, hit menu -> multi select > then put a check mark to what you want copied then hit the copy button.
-6 now hit back untill you're back in the root
-8 Then navigate to system, and at the top you should see button "Mount RW" hit that button.
-9 Then go into the App folder, and hit paste.
-10 All the selected APKs are now in the system/app folder.
-11 Now you need to give each of the copied apps permission by long-clicking on it till a menu comes up, hit permissions, then check all the check boxes next to "Owner"
-12 After you did that to all the apps hit the "mount RO" button on top of the screen
-13 Reboot the NT.
That should do it...hopefully I havent missed anything.
Hello,
I have a rooted Gtablet running the latest ICS DRH Beta2(fixed) ROM. I surely have NOTHING against the boot animation zip file that comes loaded with the rom, but I just want to flash a different image there instead of seeing the 'Team DRH' boot image all the time. Has anyone tried doing so ?
Thanks,
David
Davy49 said:
Hello,
I have a rooted Gtablet running the latest ICS DRH Beta2(fixed) ROM. I surely have NOTHING against the boot animation zip file that comes loaded with the rom, but I just want to flash a different image there instead of seeing the 'Team DRH' boot image all the time. Has anyone tried doing so ?
Thanks,
David
Click to expand...
Click to collapse
Since you are already running a Custom ROM you have options.
1st. Download and install ES File Explorer from the Market and go into the settings and grant it Superuser permmision and mark the System as RW. All that found on the bottom of the settings in the ES File Explorer settings.
2nd. Find a Custom bootanimation that you like. There is allot of them around so after downloading them you can open them up in ES and view the pictures to see which one that you like. I change the names just so that I know which one it is. Example: if it downloads with name bootanimation.zip rename it (xxxxxx)bootanimation.zip. The x is the name that you perferr.
3rd. Here is where it gets a bit tricky. After finding the one you like guide your way using ES to the system files. Upper corner says favorites and (/) means system. So the bootanimation would be found in ./system/media. Make backup if you need it by long press until option menu pops up and select Copy to. Now go back to Favorite/sdcard to where you store your new bootanimation. Rename just bootanimation.zip and then Copy to the ./system/media folder that you were in earilier. You will get a overright messeage just allow it and reboot and enjoy.
Dear nobe1976,
Thanks so much for your very informative reply, I already have the ES File Explorer software you mentioned installed on my gtablet. Also I have the Ghost Commander app installed, it also works well. Is there a certain place that has a good selection of boot animation files?
Thanks,
David
A quick question. How does one disable the CD ROM pop-up that appears when connecting the phone? I tried using the same code as on the original Incredible (##7764726), and while it does take me to the same feature editor and I can select CD ROM option and do "disable", it reverts to "enabled" immediately.
Thanks in advance!
PS If anyone knows how to move apps onto an external SD Card?
Boris1M said:
A quick question. How does one disable the CD ROM pop-up that appears when connecting the phone? I tried using the same code as on the original Incredible (##7764726), and while it does take me to the same feature editor and I can select CD ROM option and do "disable", it reverts to "enabled" immediately.
Thanks in advance!
PS If anyone knows how to move apps onto an external SD Card?
Click to expand...
Click to collapse
you ll need root and access to /system/
nitsuj17 said:
you ll need root and access to /system/
Click to expand...
Click to collapse
I do have that. Would you happen to have instructions how to get rid of it?
Thanks!
Don't have the phone in front of me right now, but i believe you navigate to \system\etc and cdrom.iso is in there, just delete it, or rename it (your choice).
If you don't have an app like rootexplorer you can also do it in TWRP's file manager. Just make sure you mount "system" first or you wont see the folder.
*Madmoose* said:
Don't have the phone in front of me right now, but i believe you navigate to \system\etc and cdrom.iso is in there, just delete it, or rename it (your choice).
If you don't have an app like rootexplorer you can also do it in TWRP's file manager. Just make sure you mount "system" first or you wont see the folder.
Click to expand...
Click to collapse
This worked for me:
Dial ##PROGRAM#
Press Call
Enter six zeros for the password
Go to Feature Settings
Disable CD ROM
Back out
ceayuso said:
This worked for me:
Dial ##PROGRAM#
Press Call
Enter six zeros for the password
Go to Feature Settings
Disable CD ROM
Back out
Click to expand...
Click to collapse
hmmm ##PROGRAM# does nothing for me.
The ##PROGRAM## worked for me and gave me the menu, but no matter how many times i set the cdrom to disabled it never changes, just remains enabled.
Void4ever
ceayuso said:
This worked for me:
Dial ##PROGRAM#
Press Call
Enter six zeros for the password
Go to Feature Settings
Disable CD ROM
Back out
Click to expand...
Click to collapse
I'm with void4ever. Dialing the ## code was the first thing I did, just like on old Inc. I see the menu, but the change to CD ROM setting does not stick. It reverts to Enabled as soon as I hit OK on the selector...
you go to system/etc/ and remove (or re-name to .bak) CDROM.ISO
*Madmoose* said:
Don't have the phone in front of me right now, but i believe you navigate to \system\etc and cdrom.iso is in there, just delete it, or rename it (your choice).
If you don't have an app like rootexplorer you can also do it in TWRP's file manager. Just make sure you mount "system" first or you wont see the folder.
Click to expand...
Click to collapse
Thanks! That worked. Not quite the way I like to make config changes, but as long as it works.