Do not ask me or anyone else on these forums about how to change your ESN! It is highly illegal! Don't do it! I will not discuss that at all in this thread.
If you have activated your Optimus V on Verizon's network, and you have any of the Optimus V Froyo roms installed, the following will show you how to mod the rom to run on Verizon smoothly. Otherwise, you won't be able to send and receive sms/mms messages, and the phone will constantly complain that it is roaming. The scope of this thread is how to mod the rom once you have already activated your phone.
Always do a backup before doing anything on this page. You will need to use root explorer or adb to install these files onto the system partition. Or you can build/mod your own rom and install it.
Using adb, you would first mount system as write-able:
Code:
adb remount
Then you would push the files to the phones with the push command:
Code:
adb push file.ext /path/file.ext
Step 1: download this file pack
Step 2: Extract the files into the same folder as adb or onto your sdcard if you are using root explorer.
Step 3:
Place apns-conf.xml inside /system/etc/
Place Phone.apk inside /system/app/
Place telephony.db inside /data/data/com.android.providers.telephony/databases/
Step 4: I've included a modded framework-res.apk from the reborn rom. If you use a different rom or if the included one does not work for you, extract the original framework-res.apk from your rom located in /system/framework/. Using winrar or 7zip, add the included eri.xml to /res/xml/. Replace the original framework-res.apk on your rom.
Step 5: Using QPST, flash the included PRL file, 52299.prl
I've been using this setup for a week now without problems. I thought I would share. I tried using the LG Vortex rom on the Optimus V, but the hardware was too different. This method should also work on the Optimus S, M, and C, but I have not confirmed.
For the CM7 roms, check here: http://forum.xda-developers.com/showpost.php?p=19992286&postcount=11
nice <3 it looks awesome
I really need to find a way to repair my esn. it reads all zeros .. please help
if it truely is all zeros,then it would not be illegal to write the phone's own esn/meid back in,but it MUST be the one on the sticker of the phone. the way to do that would be to flash a rom that lets the phone show up in diag mode. I know aospCMOD does,I don't think IHO does though. experiment and you should end up with the phone showing up as a modem. then install qxdm,if you google for it its easy to find. you need qpst also,they are both on the same page if you google for them together. once you have all that,launch qxdm,go through the menus and find communication,pick the lge diag port,then in the command box,type "spc ______"<enter>where the ______ is your SPC/MSL. you can get these using cdma workshop 2.7 which is also illegal to link here,but is easy to find,just pick the diag port,click connect,then go to the security tab and pick lg method and hit read. now back in qxdm,type "RequestNVItemWrite meid 0x_______________"<enter> where the ____ is your meid from the phone's sticker. DO NOT USE THE MEID FROM ANY OTHER PHONE OR THIS IS ILLEGAL.once that is done,which should be instant,then type "mode reset"<enter> the phone should now reboot.
Message to mods: Please do not remove this post as it does not show anyone how to change an esn/meid,it only allows them to write one in if the phone does not already have one. If the phone does already have one,this method will not work to change it,it will stay at its original.
msnuser111 said:
if it truely is all zeros,then it would not be illegal to write the phone's own esn/meid back in,but it MUST be the one on the sticker of the phone. the way to do that would be to flash a rom that lets the phone show up in diag mode. I know aospCMOD does,I don't think IHO does though. experiment and you should end up with the phone showing up as a modem. then install qxdm,if you google for it its easy to find. you need qpst also,they are both on the same page if you google for them together. once you have all that,launch qxdm,go through the menus and find communication,pick the lge diag port,then in the command box,type "spc ______"<enter>where the ______ is your SPC/MSL. you can get these using cdma workshop 2.7 which is also illegal to link here,but is easy to find,just pick the diag port,click connect,then go to the security tab and pick lg method and hit read. now back in qxdm,type "RequestNVItemWrite meid 0x_______________"<enter> where the ____ is your meid from the phone's sticker. DO NOT USE THE MEID FROM ANY OTHER PHONE OR THIS IS ILLEGAL.once that is done,which should be instant,then type "mode reset"<enter> the phone should now reboot.
Message to mods: Please do not remove this post as it does not show anyone how to change an esn/meid,it only allows them to write one in if the phone does not already have one. If the phone does already have one,this method will not work to change it,it will stay at its original.
Click to expand...
Click to collapse
thanks I will try this on my brick phone as soon as I get home.
thanks it work. thanks a billion.
how do I get M.Ip settings in QPST Service programming to stick. they always revert back to original.
not working on bumblebee rom
mereed1977 said:
not working on bumblebee rom
Click to expand...
Click to collapse
if you're having problems connecting with qxdm/qpst, try booting into recovery first.
you can also restore your first stock backup and the pst's can talk while it's turned off but still plugged into the pc.
freddysam has been a God-send..He has helped me with SOOO much pertaining to all of this..I just wanted to publicly let it be known that this guy is AWESOME and SUCH A HUGE HELP!!! Thanks again bro!!!
Thanks to freddysam, I found that this was possible and I now have another Optimus V but it is on the Verizon network via Page Plus Cellular. However, instead of using the package freddysam posted here, I have built an up-to-date ROM from the IHO/CM repo hybridized for OV on the Verizon network. It is working fine for me without any issues. Instead of going through steps 1-4, you can just flash the following ROM (updated 02/22/2012)
http://www.mediafire.com/?emblkx8bb2bcoc1
MD5sum: ab4290cdccc249a5766458841d6e2565
You can check the MiRaGe build at IHO Wiki. This is the same build with VZW mods. If you also want the theme for MiRaGe ROM for VZW, it is here. Don't use the theme on the Wiki.
You still need step 5 to flash the PRL using QPST. But after that, you can update to the latest PRL by dialing to *228 and choosing option 2.
Thanks especially to Blarf and BobZhome for creating the IHO repo and VM670, VS660 ROMs.
I am attempting to get an Optimus V on Page Plus but am having trouble with Step 4.
I keep getting a boot loop or frozen flash screen after I repack and load framework-res.apk
Here is where I am at:
1)Rooted stock ROM using Gingerbreak
2)Flashed Xionia Recovery
3)Made backup of stock ROM
4)Flashed the Mirage ROM posted above after clearing caches and formatting the appropriate partitions
5)Get stuck at splash screen during boot. Sometimes it goes into a loop if I wait long enough
6)Tried using Xionia to fix boot loop, does not work
7)Tried installing the Mirage ROM in this thread using IHO_Recovery (BobZHome update for new Optimus V), still loops.
Alternatives I have tried:
1)Flashed IHO_Recovery
2)Installed BobZHome CM7 ROM. It works fine.
3)Replaced files in BobZHome CM7 ROM with the files in this thread. Everything went fine until step 4, then I would freeze at splash screen on boot.
4)Attempted to unpack/replace eri.xml/repack framework-res.apk from BobZHome CM7 ROM. Again freezes/loops at splash screen.
Any suggestions?
depthsounder said:
I am attempting to get an Optimus V on Page Plus but am having trouble with Step 4.
I keep getting a boot loop or frozen flash screen after I repack and load framework-res.apk
Here is where I am at:
1)Rooted stock ROM using Gingerbreak
2)Flashed Xionia Recovery
3)Made backup of stock ROM
4)Flashed the Mirage ROM posted above after clearing caches and formatting the appropriate partitions
5)Get stuck at splash screen during boot. Sometimes it goes into a loop if I wait long enough
6)Tried using Xionia to fix boot loop, does not work
7)Tried installing the Mirage ROM in this thread using IHO_Recovery (BobZHome update for new Optimus V), still loops.
Alternatives I have tried:
1)Flashed IHO_Recovery
2)Installed BobZHome CM7 ROM. It works fine.
3)Replaced files in BobZHome CM7 ROM with the files in this thread. Everything went fine until step 4, then I would freeze at splash screen on boot.
4)Attempted to unpack/replace eri.xml/repack framework-res.apk from BobZHome CM7 ROM. Again freezes/loops at splash screen.
Any suggestions?
Click to expand...
Click to collapse
Try wiping the partitions several times more and flashing the MiRaGe ROM over again. I had the same trouble with a new OV and it worked after trying three-four times. I have an OV with new screen and used BobZhome's recovery, see under the heading "Alternatives" in the IHO Wiki.
Success! (Sort of )
The files in this thread do work on CM7, I just could not just copy them into the respective folders without errors. Here is how I got them to work.
Warning, it took alot of rebooting and reflashing backups to figure this stuff out, make a nandroid backup before you attempt to replace the system files.
1. Follow steps 1 and 2 in OP
2. Download NinjaMorph or other app that can unpack/repack apk files. These instructions were written for NinjaMorph.
3. Copy files from Step 3 onto phone memory (I used /system), change permissions to rw-r--r--:
- Read:User,Group,Others
- Write:User
- Execute:None
If these files are not set to the correct permissions then apps will start force closing when the files are replaced.
4.MOVE (not copy) files to the folders in OP
- Place apns-conf.xml inside /system/etc/
- Place Phone.apk inside /system/app/
- Place telephony.db inside /data/data/com.android.providers.telephony/databases/
This method would not work for framework-res.apk for me, I had to rebuild the framework-res.apk that came on CM7 with the eri.xml file from the framework-res.apk in the OP. Instructions for doing so follow.
5. Rename the framework-res.apk from the OP to something else, I used VZWframework-res.apk. Open Ninjamorph, start new project and point it to the file you just renamed. It will unpack the apk into a folder on your sdcard called /sdcard/AndroidThemes/workspace. It will ask you to select a file you want to change, back out because we will do that in the next step.
6. Create a new project in Ninjamorph, this time point it to /system/framework/framework-res.apk, it will unpack this apk and ask you to select a file you want to change. Select res/xml/eri.xml, it will then ask you which file to replace it with. Point it to /sdcard/AndroidThemes/workspace/VZWframework-res/res/xml/eri.xml, note that i used VZWframework-res, your folder will be whatever name you chose in Step 5 above.
7. Select finish project, it will repack framework-res.apk and overwrite the existing framework-res.apk in your phone.
8. Reboot Phone. If your phone reboots fine and apps don't start force closing it worked! You should see a change in the taskbar, roaming should not show when the network is Verizon Wireless if you have installed the prl as described by the OP.
I still did not have MMS working at this point and even though my phone didn't say it was roaming, Cell Connectivity Tracker indicated that it was in a roaming state and data would not work without enabling roaming data. The following steps fixed these issues:
9. Move the attached Mms.apk file to /system/app Ensure that the permissions are rw-r--r-- on the file before you move it.
10. Make a copy of your original build.prop and save it on your sdcard (you are making backups this whole time right?) Rename the build.prop.txt in this post to build.prop and move it into /system/ Ensure that permissions are rwxr-xr-x
Both of the files in this post came from the VZW MiRaGe ROM that mrg666 posted above, I did not alter them and full credit goes to him for creating them, I just made them easier to access.
edited out the following due to the help from bigsupersquid and BobZHome (thanks!)
Some Notes:
-While this method got the files onto my Optimus V running CM7.2_RC0 by BobZHome without crashing it, I still do not have mms working.
-I replaced the Mms.apk in my system/app/ directory with the one from the MiRaGe VZW in hopes to fix my mms issues, but no luck.
-Even though the taskbar does not show roaming, if I go into the phone status menu it still says roaming even though I am on the Verizon Wireless network.
-I believe the above issue can be traced to the fact that my phone still thinks it is a Virgin Mobile device. If I run STMurray Cell Connectivity Tracker it gives me "Sim provider name (MCC+MNC): Virgin Mobile" in the log results.
Does anyone know which system file holds the provider information? I never activated this phone on Virgin Mobile, so I can only assume that the setting came from the CM7 ROM I installed.
/system/build.prop
thanks for the pointer to Ninjamorph.
Add/change the following in system/build.prop
ro.cdma.home.operator.alpha=Verizon
ro.cdma.home.operator.numeric=310004
ro.HorizontalVVM=true
Thanks so much for your help guys. I have everything working now including mms and data without roaming.
The tip about build.prop seemed to be the last piece of the puzzle.
I changed the settings above, but still had indications of roaming; I ended up using the entire build.prop from the MiRaGe VZW ROM and it works fine now.
I also noticed that my data usage was dominated by "dialer and dialer storage" before I fixed this roaming issue. Dialer still uses an uncomfortably large amount of data, but it isn't the 20Mb/day that it used yesterday, more like 1Mb/day now. The dialer data usage issue doesn't seem to be fully understood from what I could find; maybe my experience above is a clue.
So I am going to try and switch my optimus v details over to a samsung epic 4g, which will leave my optimus v useless. I was wondering if I could use an old verizon lg flip phone as a donor to the optimus v just for talk and text no data (i am aware mms wont work..)
My youngest brother is on my parents verizon plan and wants a smartphone but they wont pay for the data. I was thinking I could give my phone to him and make the optimus v appear as a dumbphone on the verizon network with just talk and text w/ wifi for internet. I am not asking help on HOW to do it, just do you guys think it would work?
brooksyx said:
So I am going to try and switch my optimus v details over to a samsung epic 4g, which will leave my optimus v useless. I was wondering if I could use an old verizon lg flip phone as a donor to the optimus v just for talk and text no data (i am aware mms wont work..)
My youngest brother is on my parents verizon plan and wants a smartphone but they wont pay for the data. I was thinking I could give my phone to him and make the optimus v appear as a dumbphone on the verizon network with just talk and text w/ wifi for internet. I am not asking help on HOW to do it, just do you guys think it would work?
Click to expand...
Click to collapse
I use one OV on Verizon through Page Plus Cellular prepaid plan. Everything works (data, mms ...). I just disable data since it eats all of the money quickly. I went to Canada two weeks ago, it was also roaming there and I could call back US.
mrg666 said:
I use one OV on Verizon through Page Plus Cellular prepaid plan. Everything works (data, mms ...). I just disable data since it eats all of the money quickly. I went to Canada two weeks ago, it was also roaming there and I could call back US.
Click to expand...
Click to collapse
Good to know that it can work without data. But what I am wondering is if can i switch it with the esn and meid of my old dumbphone and not put in any of the data password/settings. All I want is talk and text on it so my brother won't get charged data and verizon would think he was using the dumbphone not a smartphone. He is part of my parents family plan.
Related
DISCLAIMER: I AM NOT RESPONSIBLE FOR YOUR ACTIONS. IF YOU BRICK OR DAMAGE YOUR DEVICE IN SOME WAY, IT IS YOUR RESPONSIBILITY. THERE ARE SOME STEPS THAT MIGHT NOT BE LEGAL IN SOME COUNTRIES (CHANGING IMEI NUMBERS), AND I WILL NOT BE HELD RESPONSIBLE FOR THAT EITHER. EVERYTHING YOU DO WITH YOUR DEVICE IS YOUR OWN RESPONSIBILITY AND IF YOU FOLLOW ALL THESE STEPS YOU ARE AGREEING TO THAT. THIS TUTORIAL IS DONE FOR EDUCATIONAL PURPOSES.
Thanks to clubtech, rotohammer, koush, ayman07 and everyone in xda that has worked hard to make this possible. I did not come up with any of this, I only gathered it all from different sources and smashed it all together in an easy-to-read guide. Credit is due to all of those listed above, if I missed anyone please do let me know and I'll gladly add you here.
You will need
- P1000XWJJ4 firmware (pass: samfirmware.com)
- P1000XXJK5 firmware (pass: samfirmware.com)
- Odin 1.3
- Koush's zImage for T-Mobile Galaxy Tab
- flash_image
- I900AOJP3.bin Modem from HERE
1) Put you tab into download mode (Turn it off, when it's off, Press VolDown+Power until you see a yellow android and it says downloading...) (WARNING: All your data will be lost in the next step! Everything, INCLUDING the internal memory! Make sure to back everything up to your computer!)
2) Use Odin: Flash P1000XWJJ4 (PDA button) with P1_add_hidden.pit and make sure "Re-partition" is SELECTED, press Start and wait for it to finish. The device will reboot and it will turn on again, probably in russian.
3) Turn it off and put it on download mode again.
4) Use Odin: Press the reset button, then make sure "Re-partition" is UNSELECTED and there's NO PIT file, then flash P1000XXJK5 under "PDA".
5) The device will reboot with the latest euro firmware in english. The modem will probably be undetected, the device will be working kinda crazy (It might be slow and whenever you use something that uses the vibrator it'll get worse, the vibrator won't probably work, don't worry about this, it will be fixed in the next few steps)
6) Make sure you have flash_image and the tmobile_zImage in hand and issue these commands:
Code:
adb push flash_image /data/local/bin/flash_image
adb push tmobile_zImage /sdcard/
adb shell
su (make sure to select "Allow" when the Superuser dialog pops up on the tab)
chmod 755 /data/local/bin/flash_image
/data/local/bin/flash_image boot /sdcard/tmobile_zImage
sync
exit
7) Now, the kernel should be flashed, a reboot should fix all the weirdness. However, instead of rebooting, turn it off, and put it on download mode again (VolDown+Power)
8) Use Odin: Press reset on Odin, make sure "Re-partition" is UNSELECTED, and on the Phone button, flash the modem I900AOJP3.bin.
11) Wait for it to reboot. At this point, the tab should work fine, and the modem should be detected by the system. However, you won't be able to make calls or use the internet because T-Mobile is blocking data. Now, we need to change the IMEI number (READ DISCLAIMER ABOVE!)
12) Now, we need to backup all the contents in the /efs folder, that way, the IMEI will be corrupted, we want this to happen because T-Mobile is blocking the IMEIs on all T-Mo Galaxy Tabs so that data doesn't work unless you have the right plan/contract (BAD MOVE T-MO! WE DIDN'T EXPECT THAT FROM YOU, AT&T MAYBE, BUT NOT YOU!)
13) Backup the /efs folder (Notice: you must have busybox installed, get busybox installer from the market)
Code:
adb shell
su
busybox tar zcvf /sdcard/efs-backup.tar.gz /efs
busybox cat /dev/block/stl3 > /sdcard/efs_dev-block-stl3.img
exit
back to the shell in your computer, now use these commands to put those files in your computer, and save them somewhere safe.
Code:
adb pull /sdcard/efs-backup.tar.gz .
adb pull /sdcard/efs_dev-block-stl3.img .
14) Delete all contents from /efs and reboot. Easiest way to do it is using root explorer from the market. DO NOT DELETE THE ACTUAL FOLDER, JUST IT'S CONTENTS.
15) Done, you will be able to browse the web, send/receive SMS, and send/receive voice calls. The only issue at this moment is that it will only work on EDGE, 3G is not possible, YET.
Enjoy.
This method was posted earlier and is much easier i'd say. Thanks.
LordLugard said:
This method was posted earlier and is much easier i'd say. Thanks.
Click to expand...
Click to collapse
Where exactly? Please link me to the post that makes your T-Mo Tab make calls, using the Euro firmware and vibrator works and the tab doesn't go crazy.
As I said, all the guides I found were missing a few pieces. One was for AT&T Tabs, but I didn't find one that was for T-Mo tabs in a single piece, everything was scattered all around.
Sent from my mobile
velazcod said:
Where exactly? Please link me to the post that makes your T-Mo Tab make calls, using the Euro firmware and vibrator works and the tab doesn't go crazy.
As I said, all the guides I found were missing a few pieces. One was for AT&T Tabs, but I didn't find one that was for T-Mo tabs in a single piece, everything was scattered all around.
Sent from my mobile
Click to expand...
Click to collapse
The exact link i posted is how i got my Tmo Tab flashed to Euro firmware with calls and 2G data. Much easier steps. Not berating your method.
http://forum.xda-developers.com/showthread.php?t=886714
EDIT** Didn't realize i didn't post link in first reply.
LordLugard said:
The exact link i posted is how i got my Tmo Tab flashed to Euro firmware with calls and 2G data. Much easier steps. Not berating your method.
http://forum.xda-developers.com/showthread.php?t=886714
EDIT** Didn't realize i didn't post link in first reply.
Click to expand...
Click to collapse
Oh ok, didn't notice that also works for T-Mo tabs. Oh well.
Thanks.
Thanks for posting this guide. I followed the instructions and still cannot make phone calls. It seems to dial but the T-Mobile automated voice operator says "The phone you are using does not allow outgoing calls."
I removed all /efs files and rebooted, then verified that the IMEI was corrupt afterwards.
Any ideas? Maybe T-Mobile is blocking the corrupt IMEI number now?
Thanks in advance!
Are you able to use the market ok with your imei corrupted?
droooid said:
Thanks for posting this guide. I followed the instructions and still cannot make phone calls. It seems to dial but the T-Mobile automated voice operator says "The phone you are using does not allow outgoing calls."
I removed all /efs files and rebooted, then verified that the IMEI was corrupt afterwards.
Any ideas? Maybe T-Mobile is blocking the corrupt IMEI number now?
Thanks in advance!
Click to expand...
Click to collapse
I don't think so. Are you using a SIM card with a plan that has phone calls or are you using the same SIM card? Your Tab has a webConnect plan that does not allow phone calls, so you need to put in a SIM card that has data and calling plan.
They are blocking the IMEI for data, as far as I know, so if you use your tab to go online (without using Wifi), and it goes to my.t-mobile.com even if you try to go to xda-developers.com then they are blocking it, but in your case, it's just probably the calling plan.
calebchosen said:
Are you able to use the market ok with your imei corrupted?
Click to expand...
Click to collapse
Yes sir, Market works, it even updated itself to the latest version.
T-Mobile usa modem
sorry voice failed 3 times. sorry again will update if i can figure out why I lost voice after getting it to work.
the attached file is the original t-mobile galaxy tab modem. NO VOICE but 3G on EUROFIRMWARE
hi zdentist now m use Tmobile with EURO ver all work fine
but i can get 3G data what can i do Enable 3G service ??
this MODEM.BIN work my Tmobile euro ver?
Why make this so difficult? Just flash modaco's custom rom and kernel for Tab with Odin and its done...
USED TMOBILE TAB WITH EURO VER CALLING WORK FI9 BUT CANT USE INTERNET WITH SIM DATA
AND ALSO CONFORM THAT THIS IS POSSIABLE I USE 3G DATA IN TMOBILE?
m using this tab ver
fahadz said:
USED TMOBILE TAB WITH EURO VER CALLING WORK FI9 BUT CANT USE INTERNET WITH SIM DATA
AND ALSO CONFORM THAT THIS IS POSSIABLE I USE 3G DATA IN TMOBILE?
m using this tab ver
Click to expand...
Click to collapse
Did you get your answer from the modem switcher thread? PM me if you're still stuck.
fahadz said:
hi zdentist now m use Tmobile with EURO ver all work fine
but i can get 3G data what can i do Enable 3G service ??
this MODEM.BIN work my Tmobile euro ver?
Click to expand...
Click to collapse
sorry for the late reply. yes but you won't be able to make voice calls with this modem.bin file only DATA unfortunatley
Standard disclaimer:
This tutorial is for people who have bricked their phone due to messing about with important files/partitions on their Nitro HD and found that it won't boot up afterward. Prior to attempting this, see if you can access your phone while booting with adb in order to fix your problem. The method used in this tutorial should only be used as a last resort. Don't hold me responsible if this method somehow makes your problem worse (although, really, how much worse can it get than a phone that won't boot?).
Now that's out of the way, let's move on...
Things you'll need:
1) ADB: You can get this in the Android Developer SDK <-Once installed, install platform-tools and add the directory containing ADB to your PATH. Alternately, you can just grab the ADB folder from your SuperOneClick folder, copy it to C:/, and then add that directory to your PATH. Hell, you could even run all the commands from wherever you have the ADB folder, just make sure you have it.
2) LG P930 drivers: http://s3.amazonaws.com/lgforum.com/resources/assets/680/original/LGP930.zip
3) LG Mobile Software Update Tool: http://csmg.lgmobile.com:9002/client/app/B2CAppSetup.exe
4) UpTestEX_mod2_marwin/KDZ_FW_UPD_EN: http://www.filesonic.com/file/2255759914/KDZ_FW_UPD_EN.zip
5) LG SU-640 firmware V10F_00.kdz: http://www.megaupload.com/?d=31XABWWJ
6) A method of rooting your phone. My preferred method is the latest SuperOneClick due to its simplicity. I won't really cover how to root your phone in this tutorial as it's covered elsewhere.
The following should only need to be downloaded if you were stupid like me and bricked your device before you made backups of the necessary partitions (This will be explained elsewhere, but needless to say it's as simple as switching the "if=" argument and "of=" argument in the dd commands toward the bottom):
7) boot.img: http://fileape.com/dl/OCowIxMnbDUMiPW6
8) recovery.img: http://fileape.com/dl/jFMlB8I3kkSMOYWN
9) firmware.img: http://fileape.com/dl/4gHHDDUhODLiJGHM
10) baseband.img: http://fileape.com/dl/TMsvdaKOa7VG4mVT
11) system.img: http://depositfiles.com/files/f0ke241ew
Alright, now that you have everything you need, let's move on to fixing your phone. I'm going to assume you are competent enough to install ADB (Android SDK or folder included to with SuperOneClick) to your system PATH. Go ahead and install the LG Mobile Software Tool and then install the drivers for LG P930 if you haven't already. Extract the KDZ_FW_EN.zip file. Note, in my case, I didn't have to do anything with the mfc42.dll or run WindowsEnabler as mentioned in similar tutorials elsewhere, but your mileage may vary.
Flashing the SU-640 rom:
1) Put your phone in download mode: power off the phone if it's not already, unplug the usb charging cable, and simultaneously hold the volume up button and plug the usb charging cable back in.
2) Open up UpTestEX_mod2_marwin. (If you know what you're doing, I've been told you can use KDZ_FW_UPD_EN as well, but since I didn't use it, I'm not going to discuss it)
3) Hit the folder icon next to the "Select kdz file" line and browse to the SU-640 v10f_00.kdz
4) Select "CSE web upgrade test", a new window with some options including an "Upgrade Start" button should appear.
5) Take a deep breath...there's no going back Press "Upgrade Start".
6) At this point in time another dialog box will appear asking what country and language the LG Mobile Upgrade tool should use. Since this guide is written in English, I assume you'll want to change it from Republic of Korea to All other countries and Korean to English. This affects the language that output messages are displayed in in the LG Update tool only, it doesn't affect anything with the rom (that'll be all Korean on initial startup lol).
7) The update tool will proceed to flash your phone, but it should never complete "normally" (mine never made it past 4% according to the tool and other users have reported similar behavior). However, your phone should reboot once or a couple of times and then just be sitting idle waiting for you to go through the setup wizard. At this point, just kill the LG update tool process in task manager, don't wait for it to complete because it won't.
Rooting your phone:
1) Now, on your phone you should see the standard Android startup wizard...in Korean. Hit the left button confirming you want to go through it, and on the next screen should be an option to switch the language to English. Ah, much better.
2) Go through the rest of the setup wizard if you want, but it's not necessary and you won't be able to set up accounts anyway unless you somehow have wifi.
3) Put the phone in USB debug mode and allow 3rd party sources. Don't freak out if the phone spontaneously reboots when you do this. It rebooted on me every single time I put it into debug mode for the first time (I flashed it several times lol).
4) Once it's rebooted itself, you should be able to connect in debug mode and connect via PC mode. Go ahead and root it using your preferred method. We're almost there!
Restoring Nitro HD partition images:
1) Open up a command prompt and navigate to the folder you saved your recovery images to (hopefully you put them in the same folder, it'll make your job easier)
2) Push all the image files to the phone's sdcard using the command:
Code:
adb push filename.img /sdcard
Alternately, you can just mount up your phone in My Computer and copy and paste the files over.
3) Now the real fun begins! Use the following commands:
Code:
adb shell
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
dd if=/sdcard/firmware.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p27
dd if=/sdcard/baseband.img of=/dev/block/mmcblk0p14
4) You won't be able to issue a reboot command, so just hold power down on your phone til it's off and hold the volume down button so that it comes back up in factory data reset mode. You will want to pull your sdcard at this time if you don't want your data erased.
5) Hit power twice and your phone should go through its reset process and (hopefully!) come back up in a working (and rooted) AT&T "stock" rom
If you have any issues, it's possible I've forgotten some steps, so I'll address them in this thread. At this point, I'd like to thank specific people who helped me immensely getting a working phone again: bytecode64, gordec, schwin97, belth219, sukudos, and ziiljuks. (If I've missed you, I'm sorry, I'm thankful to this entire forum!)
Original post:
So I was messing with fonts (actually trying to get the "look of disapproval" from Reddit to display) and substituted DroidSansFallback with a kannada font using Font Installer *Root*. Well, long story short, it was causing issues with other non-english characters so I tried to restore *all* my fonts using the "stock" option that comes with Font Installer.
When I rebooted, my phone only got to the LG Screen and that's as far as it has gotten since. I can't do anything with it, but I can get to Factory Data Reset mode and Download mode. I tried plugging the phone into my computer, but it doesn't appear to get far enough to mount the disk. Odin recognizes it's attached when I put it in download mode, but obviously Odin doesn't work with our phones.
Does anyone know if there will ever be hope for my phone or should I pursue getting a replacement? I'm actually completely shocked that simply replacing fonts has bricked my phone to the point where it doesn't even boot. This has seriously made me reconsider tinkering with Android at all until recovery methods are possible. I'm more than willing to be a guinea pig at this point until I try to send it in for a replacement (within the next few days probably).
Click to expand...
Click to collapse
do a factory data reset ? my phone gets stuck on LG logo too when i try to move all my apps to SD using titanium backup . factory data reset option resolves it however . see if that works ?
Unfortunately factory reset won't help in this case, the app messed up something in the system.
But as long as it gets to the point when you can use adb (it comes with SuperOneClick if you don't have it installed), then yes, there still a chance
To make it easier, can you contact the app's author and ask what exactly that app changes in the system, which files, so if necessary we can provide you with these files.
[email protected],
I have adb from SuperOneClick, how would I know if I can use adb?
Edit, I guess what I'm asking is do you have a quick guide to connecting a phone using adb and pushing files that you can hit me with a link to?
open CMD window and type:
adb devices
It should show you your phone.
adb devices
If that comes back with a device listed you can still save your system. Good luck...
Okay, I'm at work now, but I'll check when I get home. I do believe I tried that command and it didn't show any connected devices, but I can't remember if I only tried that while I had it in Download mode or also while I was trying to boot it. I'm keeping my fingers crossed lol.
You should searching for the file named KDZ_FW_UPD_EN,and install LGMobile Support Tool which can be downloaded on the LG Official website.And then you should download the *.kdz file that matches your phone.
Finally launch the KDZ_FW_UPD_EN flash your phone with the kdz file.
I use the tool bring my bricked device back.
Good luck.
belth219,
Problem is I can't find a .kdz for my P930. This seems like it'd be really easy to do otherwise.
Alright, I've created a tutorial in the first post describing how I unbricked my phone. I don't think it's quite back to "stock", but I don't think anybody who bricks their phone will care about that.
You have done the great job.Thanks for the baseband.img.It made my SU640 closer to PERFECT!EDGE enabled!!
Sent from my LG-SU640 using XDA App
I can't claim credit (or blame lol) for creating any of the images in this tutorial. Gordec is responsible for 3/5 including the baseband and I am so glad he responded quickly with each image correctly copied!
Sent from my LG-P930 using xda premium
my 4g lte isn't working.
My 4G wasn't working until I did a factory data reset (a second one, actually). Is it just your LTE that's not working or 4G in general?
Sent from my LG-P930 using xda premium
Will this give a version that has wifi and regular calling available right off the bat? I messed up my nitro to the point that i can only sometimes make phone calls and my market / browser won't function at all. Force close immediately.
Think I should try this as an option?
AT&T LG Nitro HD P930 is my make
Also, I use it on TMobiles prepaid network. I only get edge. I checked the bands, I think im right but wanted reassurance that edge is all i can get. Thx
To the best of my knowledge, prepaid service providers only allow maximum 4G, but vary by provider. No prepaid that i know of allows access to the LTE network, only on a post-paid plan.
If you have a AT&T unit unlocked for use on another carrier, then there's not much you can do in this case. sorry.
basically my att data itself.
att goofed up on my data plan. The thing is great thanks a lot!
csmg.lgmobile.com:9002/swdata/WEBSW/LGSU640/ASKTBK/V10i_00/V10i_00.kdz
I couldn't get the version with the f's in the original post to work. Will this one do? It's 460 mb.
nope because you cant root the ...i version thus making it worthless.
Sandpapers,
I'm uploading the V10f_00.kdz to megaupload right now. I'll update my tutorial as soon as it's done. Sorry I didn't do this sooner.
Sent from my LG-P930 using xda premium
*************************SOLVED*****************************************************************************************************************************
Hi everyone!
I'm a noob. I got my Galaxy S3 T999V rooted and the boot (recovery?) runs clockworkmod. CyanogenMod 10 is running smoothly, except:
The camera doesn't work! Getting a "cannot connect to camera" error instantly upon launching the camera app (stock).
So from perusing the internet a little more, there are other phone models also suffering from this "can't connect to camera" error.
The fix involves: Booting into rooted stock. extracting the folder "cameradata" in system using a file explorer (AndroZip). Put them on the external sdcard or your computer. Then overwrite your CM10 flashed system/cameradata folder's .bin(s) and setting the permissions a certain way.
Does anyone have the stock Galaxy S3 cameradata files? And I have no idea how to change permissions!! HELP!!
*************************SOLVED*****************************I*TAKE*NO*RESPONSIBILITY*FOR*ANY*DAMAGES*OR*BRICKING*THAT*MAY*OCCUR***********
http://forum.xda-developers.com/showthread.php?t=2102981&page=2#post39859973
THOSE ARE THE FILES (or click here?)
1. Download the files, unzip them and place them somewhere on the phone (sdcard0 or sdcard1, in some separate, user-made folder)
2. Make sure you have CyanogenMod's built-in File Manager set to allow ROOT access
3. Using CyanogenMod's built-in File Manager, click the "parent folder" at the top until the top reader line says /
4. Look for a folder called system, enter it
5. Look for a folder called cameradata, enter it
6. With nothing selected, press the :: button in the bottom left, on-screen. Select "properties" and choose 'permissions', grant all properties to everything (except the S column). This allows you to copy the downloaded files into this folder.
7. Browse to where you have the files. On the left is a tick-box, tick them all.
8. Browse back to the /system/cameradata/
9. Select the :: again. Select "paste all items here". SELECT OVERWRITE.
10. Individually long-press each item and change it's properties. Select permissions and permit all except the S column again. This allows the app to be accessed, the user to change the app, and the app to save files.
11. Attempt to run the STOCK camera app. CHANGE THE SCENE "SCN" TO 'ACTION'. I've been told this keeps it from crashing again...
12. If the camera app is a bit laggy, try rebooting. If it persists (but camera app is functioning) may want to restore permissions using Recovery Boot (I use CWM).
The difference MAY be adding that one extra file (_ZH), but I recommend moving and overwriting all just to be safe.
Malumen said:
Hi everyone!
I'm new to the whole modding/cyanogen/clockwork thing. I got my Galaxy S3 T999V rooted and the boot (recovery?) runs clockworkmod. CyanogenMod 10 is running smoothly, except a few issues:
- The WiFi and mobile network connections fly between 20% and 60% (with the WiFi signal reaching 98%) when I am just sitting in my room and the phone is motionless. Do I need to update the radios to get better reception? (And how do I do that? I am on Mobilicity in Canada)
- What steps do I take to perform a restore? I've made a backup in the CWM boot/recovery of Cyanogen after I got everything working fine. If I messed some things up, what steps do I take to restore back to that point? Do I press Wipe Data/Factory Reset and Wipe Cache, or do I just select Restore and the file to restore using?
- THIS IS MY BIGGEST ISSUE: The camera doesn't work! None of the camera apps work in my CM10. Skype and Hangout using the front camera works, but no photo-taking apps work (they do not even run, just black then they back out to the Apps screen)
So how do I:
> Get more stable reception? Do I update the radios? If so, how?
> Perform a restore? What steps do I take to return to a backup I have of Cyanogen?
> Get my camera working?
Click to expand...
Click to collapse
try to reflash. wipe everything and make sure you didnt download nightly. nightlies can have some problems. are you sure you download the stable version?
KingKostas said:
try to reflash. wipe everything and make sure you didnt download nightly. nightlies can have some problems. are you sure you download the stable version?
Click to expand...
Click to collapse
May I ask quickly what steps are involved in "reflashing"? Just to make sure I don't do some extra step or miss something.
As far as the stable version goes, I looked for the d2tmo file on get.cm under the Stable tab. I'm assuming that would be the most stable build?
(Perhaps a nightly might fix it??)
Question: Is there not a way I can just install/add this "4.2" camera? I've seen videos and read that people are using that just fine on CM10. Alternately if I boot into recovery would "fix permissions" be any help?
re: odin flash
Malumen said:
Hi everyone!
I'm new to the whole modding/cyanogen/clockwork thing. I got my Galaxy S3 T999V rooted and the boot (recovery?) runs clockworkmod. CyanogenMod 10 is running smoothly, except a few issues:
- The WiFi and mobile network connections fly between 20% and 60% (with the WiFi signal reaching 98%) when I am just sitting in my room and the phone is motionless. Do I need to update the radios to get better reception? (And how do I do that? I am on Mobilicity in Canada)
- What steps do I take to perform a restore? I've made a backup in the CWM boot/recovery of Cyanogen after I got everything working fine. If I messed some things up, what steps do I take to restore back to that point? Do I press Wipe Data/Factory Reset and Wipe Cache, or do I just select Restore and the file to restore using?
- THIS IS MY BIGGEST ISSUE: The camera doesn't work! None of the camera apps work in my CM10. Skype and Hangout using the front camera works, but no photo-taking apps work (they do not even run, just black then they back out to the Apps screen)
So how do I:
> Get more stable reception? Do I update the radios? If so, how?
> Perform a restore? What steps do I take to return to a backup I have of Cyanogen?
> Get my camera working?
Click to expand...
Click to collapse
The very best advise is to do the following, doing anything else will most likely prolong
the problems you are having or making them even more difficult to resolve.
First thing you need to do is to install the stock Tmobile T999 rooted firmware.
Here are the exact step by step instructions with the download link for the firmware.
After you have followed these instructions your phone will be working properly and if
you like you will be able to flash any custom roms made for the Tmobile T999 phone
or restore any backups unless the the backup is corrupted in some way or another.
Here is the link to the Tmobile Stock & Rooted firmware you need:
http://www.androidfilehost.com/?fid=9390169635556426451
After downloading it make a folder on your desktop and unzip the file
using Winzip or 7zip so the .TAR file is in the new folder you just made.
Here is a link for ODIN which is required for flashing the stock rooted firmware
(a windows app) http://d-h.st/Q14
Download and extract Odin into the same folder you made containing the TAR file.
Here is a step by step guide for you.
Download the firmware of your choosing (use the root66 version if you want root)
Run Odin by double clicking the Odin.exe within the folder you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
Click on the PDA button in the middle-right area of Odin.
Browse to and select the FW you downloaded (TAR file)
Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash. This will take a while, so be patient!
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
Wait at least 5-10 minutes for the system to boot the first time and then build its cache! (It may seem to hang during boot, this is normal and you must be patient!!!)
Misterjunky said:
The very best advise is to do the following, doing anything else will most likely prolong
the problems you are having or making them even more difficult to resolve.
Click to expand...
Click to collapse
I followed most of these directions the first time, using the guide from High On Android:
http://www.youtube.com/watch?v=QPeIZZVYHbY
I used Odin, got root, wiped and got CM10 working.
This seems to be a bit of a problem that has cropped up in other models (i747). The fix that was used was to get back to the Stock ROM, while rooted, and browse to the system folder /cameradata/. In there are files for permissions for the camera. Copy those to the external SD card or your computer, then get back into CM10. Replace the CyanogenMod system folder /cameradata/ with the files you got from the Stock ROM. Then change the permissions for these new files.
So does anyone have the Stock /cameradata/ files? I'd greatly appreciate it!
re: camera issue
Malumen said:
I followed most of these directions the first time, using the guide from High On Android:
http://www.youtube.com/watch?v=QPeIZZVYHbY
I used Odin, got root, wiped and got CM10 working.
This seems to be a bit of a problem that has cropped up in other models (i747). The fix that was used was to get back to the Stock ROM, while rooted, and browse to the system folder /cameradata/. In there are files for permissions for the camera. Copy those to the external SD card or your computer, then get back into CM10. Replace the CyanogenMod system folder /cameradata/ with the files you got from the Stock ROM. Then change the permissions for these new files.
So does anyone have the Stock /cameradata/ files? I'd greatly appreciate it!
Click to expand...
Click to collapse
Just download any of the custom rom zip files based on the jellybean v4.1.1 stock rom.
All of those custom roms will have the files you are looking for.
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
d2vzw
This also works on the sch-i535 as well. Thank you so much.
kingsugar said:
This also works on the sch-i535 as well. Thank you so much.
Click to expand...
Click to collapse
Yes, I tried all the other options for getting my camera back on track, but only going back to a full stock (rooted) ROM got my camera up and running again. FWIW, I was running an AOSP ROM for months without issue. What kicked my camera offline (the dreaded can't connect to camera) for some strange reason was when I updated to the most recent firmware VRBMF1. Now its straight back to AOSP for me! Thanks for creating this post! Very helpful!
My fix
I'm going around posting my fix to all the camera threads in hopes of helping people find a solution sooner. I created a thread over in d2vzw http://forum.xda-developers.com/showthread.php?t=2492304
fix camera error on i9300 with cm 9 (4.0.4)
Malumen said:
*************************SOLVED*****************************************************************************************************************************
Hi everyone!
I'm a noob. I got my Galaxy S3 T999V rooted and the boot (recovery?) runs clockworkmod. CyanogenMod 10 is running smoothly, except:
The camera doesn't work! Getting a "cannot connect to camera" error instantly upon launching the camera app (stock).
So from perusing the internet a little more, there are other phone models also suffering from this "can't connect to camera" error.
The fix involves: Booting into rooted stock. extracting the folder "cameradata" in system using a file explorer (AndroZip). Put them on the external sdcard or your computer. Then overwrite your CM10 flashed system/cameradata folder's .bin(s) and setting the permissions a certain way.
Does anyone have the stock Galaxy S3 cameradata files? And I have no idea how to change permissions!! HELP!!
*************************SOLVED*****************************I*TAKE*NO*RESPONSIBILITY*FOR*ANY*DAMAGES*OR*BRICKING*THAT*MAY*OCCUR***********
http://forum.xda-developers.com/showthread.php?t=2102981&page=2#post39859973
THOSE ARE THE FILES (or click here?)
1. Download the files, unzip them and place them somewhere on the phone (sdcard0 or sdcard1, in some separate, user-made folder)
2. Make sure you have CyanogenMod's built-in File Manager set to allow ROOT access
3. Using CyanogenMod's built-in File Manager, click the "parent folder" at the top until the top reader line says /
4. Look for a folder called system, enter it
5. Look for a folder called cameradata, enter it
6. With nothing selected, press the :: button in the bottom left, on-screen. Select "properties" and choose 'permissions', grant all properties to everything (except the S column). This allows you to copy the downloaded files into this folder.
7. Browse to where you have the files. On the left is a tick-box, tick them all.
8. Browse back to the /system/cameradata/
9. Select the :: again. Select "paste all items here". SELECT OVERWRITE.
10. Individually long-press each item and change it's properties. Select permissions and permit all except the S column again. This allows the app to be accessed, the user to change the app, and the app to save files.
11. Attempt to run the STOCK camera app. CHANGE THE SCENE "SCN" TO 'ACTION'. I've been told this keeps it from crashing again...
12. If the camera app is a bit laggy, try rebooting. If it persists (but camera app is functioning) may want to restore permissions using Recovery Boot (I use CWM).
The difference MAY be adding that one extra file (_ZH), but I recommend moving and overwriting all just to be safe.
Click to expand...
Click to collapse
thanks a lot, i read your post, i take your advice to copy "SlimISP" to built in (cm system) folder, its work for me perfectly.
Thanks a lottttttttttttttttttttttt, have a nice day.
Hello everyone !
As some of you probably know, to be able to send and receive mms in japan (sms are not used most of the time, lots of phone are not even able to use them), you need to modify the mms.apk, to make your phone a fake iphone.
After some research and tests, I have been able to find a way to modify any mms.apk of any rom, as long as the phone is rooted.
But as I update my phone really often with CM, I didn't wanted to do the all process over and over again.
Then I created some little batch files, which I share to you now, for the ones who want the same things.
Those batch files should work on any rom and phones, as long as they are rooted, with adb right.
I have no credit for the tools used by those scripts, I only created the batch files which use them.
And I am not responsible of any damage those scripts could do to your phone !!
/!\ This script is available for windows only /!\
Installation process :
1.unzip the file somewhere (if updating, delete everything and unzip again)
2.connect your phone to your computer and check if you can access to your phone in adb root mode. For JB roms, I saw that changing the usb mode to PTP helps sometime.
3.launch "mms_mod.bat" in admin mode
4.if at the end of the process your phone doesn't reboot and you sms icon doesn't disappear from your android home, which happens most of the time, launch the "put_mms_again.bat" in admin mode.
5(a).if everything work, your phone should reboot, and your sms icon should disappear from your android home. It is normal, don't panic, just take it back from your applications launcher.
5(b).if everything work except pushing the file inside your phone (inside /system/app), do it manually with root explorer for example (don't forget to change the Mms.apk file permission after copying it), you can find the modded Mms.apk in "Output\[device model]\[date&time]\Modded_file\". Then reboot your phone.
Now it's ok, your phone should now works on softbank network!!
Don't forget to use mms mode when you want to send something to a japanese phone!
Please note that if anything goes wrong, you can find a backup of your Mms.apk in "Output\[device model]\[date&time]\Backup_file\"
Oh, and if it is not done already, don't forget to setup the softbank's APN.
For that, just download the program named "Tweakker" on google play, it is perfect for that. But be careful, the default APN to use depends of your phone plan.
Tell me if you have any suggestion or bug !
Change log :
2013/09/20 - release 0.2
- cleaning code and adding a backup feature which keeps the original and modded Mms.apk for each operation
2013/09/20 - initial release
Stremon said:
Hello everyone !
As some of you probably know, to be able to send and receive mms in japan (sms are not used most of the time, lots of phone are not even able to use them), you need to modify the mms.apk, to make your phone a fake iphone.
After some research and tests, I have been able to find a way to modify any mms.apk of any rom, as long as the phone is rooted.
But as I update my phone really often with CM, I didn't wanted to do the all process over and over again.
Then I created some little batch files, which I share to you now, for the ones who want the same things.
Those batch files should work on any rom and phones, as long as they are rooted, with adb right.
I have no credit for the tools used by those scripts, I only created the batch files which use them.
And I am not responsible of any damage those scripts could do to your phone !!
/!\ This script is available for windows only /!\
Installation process :
1.unzip the file somewhere
2.connect your phone to your computer and check if you can access to your phone in adb root mode. For JB roms, I saw that changing the usb mode to PTP helps sometime.
3.launch "mms_mod.bat" in admin mode
4.if at the end of the process your phone doesn't reboot and you sms icon doesn't disappear from your android home, which happens most of the time, launch the "put_mms_again.bat" in admin mode.
5.if everything work, your phone should reboot, and your sms icon should disappear from your android home. It is normal, don't panic, just take it back from your applications launcher.
Now it's ok, your phone should now works on softbank network!!
Don't forget to use mms mode when you want to send something to a japanese phone!
Oh, and if it is not done already, don't forget to setup the softbank's APN.
For that, just download the program named "Tweakker" on google play, it is perfect for that. But be careful, the default APN to use depends of your phone plan.
Tell me if you have any suggestion or bug !
Click to expand...
Click to collapse
I get the error message "adbd cannot run as root in production builds" on step after I run adb root.
Doug_74 said:
I get the error message "adbd cannot run as root in production builds" on step after I run adb root.
Click to expand...
Click to collapse
this is because your rom doesn't allow adb to run in root mode
was the Mms-signed.apk created successfully inside the script folder ?
if there was no error before, it should be the case.
in that case, rename Mms-signed.apk to Mms.apk, and put it manually to your /system/app/ phone folder.
Don't forget to save your Mms.apk before, and to change the access rights of Mms.apk after copying it to system folder.
Stremon said:
this is because your rom doesn't allow adb to run in root mode
was the Mms-signed.apk created successfully inside the script folder ?
if there was no error before, it should be the case.
in that case, rename Mms-signed.apk to Mms.apk, and put it manually to your /system/app/ phone folder.
Don't forget to save your Mms.apk before, and to change the access rights of Mms.apk after copying it to system folder.
Click to expand...
Click to collapse
No error and the file shows up, but is very small only 1.69kb. Shouldn't the file be closer to the original which is 8.56mb? I have s Samsung GS4 and the original file is SecMms.apk. I noticed the twframework-res did not run on the script just framework-res does this matter?
After messing with this for sometime I can see where the script is looking for Mmm.apk, but since I have a Samsung phone the file is SecMms.apk, so this is the problem I believe. Looks like you would need to have additional script just for Samsung to include twframework-res and framework-res, also to look for SecMms.apk. This is a nice script you built, BTW.
Doug_74 said:
No error and the file shows up, but is very small only 1.69kb. Shouldn't the file be closer to the original which is 8.56mb? I have s Samsung GS4 and the original file is SecMms.apk. I noticed the twframework-res did not run on the script just framework-res does this matter?
After messing with this for sometime I can see where the script is looking for Mmm.apk, but since I have a Samsung phone the file is SecMms.apk, so this is the problem I believe. Looks like you would need to have additional script just for Samsung to include twframework-res and framework-res, also to look for SecMms.apk. This is a nice script you built, BTW.
Click to expand...
Click to collapse
Be careful, if your GS4 use a special samsung mms program, this script will not work with it anyway, because the script modify some file inside the Mm.apk, which are probably not the same inside your SecMms.apk.
I have scoured the internet and tried several solutions.
I'm on an AT&T HTC One currently running a 4.3 GPe ROM, and it's rooted, unlocked, and S-ON.
I'm trying to add on screen buttons like a nexus by adding qemu.hw.mainkeys=0 to the build prop.
I've tried ES File explorer, which flat out didn't do anything. I've mounted the system folder using the mount system rw/ro app, then edited it using Root Explorer and build.prop editor, which either immediately reverted to what was before, reverted after reboot, or caused the phone to reboot itself, also reverting the build.prop to what it was before. I've also tried this in MoDaCo Switch (currently my favorite) in both the Sense and GPe sides.
Am I missing something obvious?
Has anyone else tried anything like this or edited the HTC One build.prop in general?
Thanks!
Sent from my HTC One using xda app-developers app
The same problem
Also interested in this. Been trying different methods with no luck.
build.prop
Im trying to figure out the build.prop also. i know on past devices it was easy. im trying to enable my wifi hotspot on a Sprint HTC ONE. ill keep looking and let you know what i find.
Possible fix
I wanted to come back to this thread and let everyone know that it is now (Somewhat) possible to get the stock navbar to work in the Google Play Edition of the HTC One m7 rom. Here's what I did and remember, do this at your own risk:
1) Download either stock HTC One GPe rom or ARHD GPe rom (i did this on the ARHD rom)
2) Download either the stock GPe of the NEW HTC One M8 rom, or there is a port that is posted on the M7 thread called tiKtaK.
4) View the contents of the M7 rom and delete SystemUI.apk ==> /system/priv-app/SystemUI.apk
3) Take the SystemUI.apk file from inside the M8 rom and insert it into the M7 rom. I didn't extract the roms.zip files though, since i wasn't sure if that would prevent the rom from installing correctly. I'm using Ubuntu and the default compression manager allowed me to view the contents of the zip file and add / delete files without extracting them. I'm sure this is possible in windows or in mac.
5) Transfer newly modified rom to your device.
6) MAKE A NANDROID BACKUP (if you don't know what that is, please Google it before continuing... you have been warned)
7) Once you have a backup to fall back on if things go wrong, flash the new rom.
8) Aroma does its thing, and in my case as the installation finishes in aroma but then reboots and gets stuck in the Google logo. Not sure why, but it could be because of my version of TWRP. Who knows.
9) (Optional depending if your phones locks up in boot) I then hard reset my phone back into recovery (hold power for about 15seconds until the phone resets, and when you see the screen go black while still holding the power button, press and hold the volume down button and release the power button after 2 seconds. Select recovery in the menu and hit the power button to confirm). Once you are back in recovery, clear cache and dalvik and reboot.
10) Should be good to go. If not then restore back to your Nandroid, and I'm all out of ideas lol.
I'm fairly certain this wouldn't work if you took the systemui file from say an AOSP rom, or from CM rom, since the two files need to be almost identical. I just figured i'd give this a shot since the two files are probably very similar. And its working so far. No weird bugs or glitches. very pleased. I will update this if i run into any problems.
Another option you could try would be the M8 GPe port from tiKtaK. Its a solid rom with a few hiccups from what i've experienced. The camera will FC if you switch into Panorama or Photosphere, and the data connection can be a little quirky. Had to restart my phone to get it to reconnect on more than one occasion.
If you get this working and want to turn off the capacitive buttons, You can either download an app to turn off the backlight to them or if you're using gravitybox [kk] there is an option in the Display section to turn off the button backlight. If you want to prevent them from doing any actions, there is a file you need to delete the contents of... /system/usr/keylayout/synaptics-rmi-touchscreen.kl just use a file explorer with text editing capabilities and delete the text inside this file. Then save and reboot. g2g.
Hope this helps.
Remember, do this at your own risk.