Related
Warning:I am not responisible for any damage to your phone and rooting usually nullifies the warranty. so please procede with your own risk
I tried to root my karbonn A2 for 2 weeks and finally i got it. so im gonna share the steps involved in rooting and also provoide the tools for it.
NOTE: I do not take credit for any tool since all the tools were already available online, so credit goes to whoever programmed them. only thing i did was to alter the method slightly to get my phone rooted.
Lets begin. Before we start rooting our phone, most important thing is the drivers. so u need two types of drivers one is ADB (android debugging bridge) drivers and the other is preloader drivers. i have attached both of these drivers in the attachments u can download it.
Step1[only for beginners]: Go to setting>applications>development>enable USB debugging in the phone, then connect your phone to ur pc (remove all previous drivers if u have installed) then go to device manager>devices, right click on the usb device and click update driver and browse to folder containing the SPdrvers (u need to extract the folder from the attachment first).If driver is successfully installed then u should see "android phone" in ur device manager. to confirm it just run adb devices from the command line by chagning the directory to where adb.exe is, u should see the list of devices attached to ur pc. (usually adb.exe will be in android sdk tools folder or if u dont have one then check in ADB folder from superoneclick in the attachment).
Step2: ok, now that u have installed adb drivers, u need to install preloader driver (also known as downloading mode in some devices). to do this, disconnect ur phone from the pc, then switch off the phone, remove the battery and then connect ur phone to pc again (without the battery). then u should see windows trying to install drivers and fails. then go to device manager again and browse to folder containing USB VCOM drivers (see attachment). after it successfully installs procede to step 3.
Step3:: download, extract the files MTKROM and SPflash tool to ur pc. then put the battery inside ur phone then switch it on, connect it to pc (enable debugging all the time). then open command line then go to adb folder then type :adb devices- u should see the list of device attached (u will get some long numbers so dont worry). then type "adb shell" (without the quotes). u will get a $ sign, then type "cat proc/mtd > /sdcard/firmware.info" if its successful then a file named firmware.info will be created in ur sdcard root. then copy that file to ur pc.
Step 4: Now open that firmware.info in MTKROM.exe u should see a list tables and address like in the image below. then click save scatter and rename the filename to MT6575 instead of MT6573 (and leave everthing else as it is). so a file named "MT6575_Android_scatter.txt" will be created.
Step 5: Now open Spflash tool and load the scatter file in that. u should see something like this in the image below.
STEPS TO BACKUP ORIGINAL BOOT AND RECOVERY
Step 6: Before we actually begin to root its important to make a backup of current images. so to do that, go to READ BACK tab in sp flash tool. click on Add>double click on the page file and save as "Boot.img" somewhere safe. then click on "Read Page only", this is very important. then look at the address side by side from MTKROM and enter into sptool. the start address is the address in which the boot.img begins and length is the length of boot.img. so final address will be startaddress+length =start address of next image (recovery.img). In MTKROM the start address is given as "PART ADDRESS". after entering those carefully click ok. if u want to be sure then use programmer calculator and add the address.
Note :the address will be in hexadecimal format not decimal.
Step7: In order to read the firmware from the phone, disconnect the phone from your pc, remove the battery, dont connect it yet. now click on "Read back" button in the sptool (its after Add,remove button). now the software starts searching for the device. now connect the device to the pc (without battery ofcourse). now if have installed USB VCOM drivers correctly then the sp tool should detect ur device and start reading from it. u will see Red colour in the
task bar when it detects then blue colour while the tool is reading the phone. wait untill the reading is complete. A green circle will pop up after it successfully reads from the device. (refer the images below)
Step 8: repeat step seven as described above for recovery.img (save the file as recovery.img) then select "read page only" option, enter start address as 0x0980000 and length as 0x0500000. (please enter the address carefully cross check with MTKROM image addresses.)
Note: You have to disconnect the device first then click read back button after entering the addresses then connect the device, otherwise the sptool wont detect your device!.
Actual Rooting Procedure
Step 9: Now that you have backed up both boot and recovery images its time to start the actual rooting. download the boot.img file from the attachment and save to your pc (dont replace it with your backup image that you saved earlier). go to download tab in the sp tool and tick only boot.img and uncheck all others (if any of them has been checked already) and click on Bootimg and browse for the folder where u downloaded boot.img from the attachment and NOT THE BACKUP! after that disconnect your device, then click download button above( after format->upgrade button) or f9 from keyboard. the tool will start searching the usb com ports. now connect your device and wait till it downloads fully. Note: In downloading your will get RED colour first, then YELLOW colour while flashing, and finally a GREEN circle after flashing is complete).
Step 10: The most important and complicates steps are over. now all you have to do is put your battery to your phone and switch it on. now after it sucessfully boots up, open superonclick.exe (you will get this software online and its very popular tool for rooting) and connect the device to your pc (enable debugging of course), then click Root button in superoneclick and Voila! your phone is rooted. enjoy and dont forget to press thanks button if ive helped
Note: u will need .NET framework 3.5 to run superoneclick.
Method To Unroot
For unrooting your mobile all you have to do is flash the original, backup boot image back to your phone. just open sptool and load the scatter file, then click on bootimg then browse to wherever u have stored backup boot.img then click download button then connect your device without the battery and thats it. you will get back original firmware without the root!.
Clockwork mod recovery for A2
There is no official cwm recovery for A2, but i ported cwm for other MT65xx devices to A2. so here are the steps to flash.
step 1: download recovery.img from the attachment.
step 2: open sp flash tool and load scatter.txt (for detailed description refer rooting steps). then tick recoveryimg and browse and set the path of the recovery.img you just downloaded from attachment.
step3: click on download button at the top or press f9. then take out the battery from the phone and connect it to the pc. the tool will detect your phone and start flashing cwm recovery.wait untill the green circle pops up.
step 4: now put in the battery and press power button+volume up and hold it for few seconds and voila!! cwm recovery boots up. And to revert back to original recovery just flash the recovery.img that you backed up during rooting process using the above steps.
Note: Do Not factory reset your phone without backing up the IMEI number. After rooting your device please backup your phones IMEI number which is stored in data/nvram/md/NVRAM/NVD_IMEI/MP0B_001 to a safe place. or there is an application called mobileuncletools (a chinese app) which helps to backup your IMEI to sdcard and restore it back. if u loose your IMEI and reset your phone then you cannot call or recieve sms etc
No service and invalid IMEI solution
explanation:
In case u did factory reset of the phone, then all your data will be wiped including the imei number. it will be reverted to factory imei number, hence you cannot connect to any mobile networks in india or anywhere else because most network operators wont allow to use the network with dupicate or invalid imei numbers. every device has a specific imei number. in this device your original imei numbers (15 digits) will be on the back of your battery.
Restoring is tough very simple procedure, creating the required files is a major headache. At first i thought it was impossible to restore the imei back (trust me i tried all the available solutions that u get in the internet, infact there are 5 different types of solutions, none of which worked for this device). luckily one day i found a chinese software which actually did create a imei file that is compatible with this device (phew !, yeah i know) and so i did successully restored my imei back and i can once again connect to mobile network and make calls..:victory: so here it goes.
How to restore IMEI number? (MUST BE A ROOTED PHONE)
1) if u have made the backup of MP0B_001 file in /data/nvram/md/NVRAM/NVD_IMEI/MP0B_001 , then install root explorer and simply replace your current file with the backed up MP0B_001 and set the permissions to rw-rw---- and restart.
2) if u havent backed it up (too bad), then download the chinese software sn_gen.zip from the attachments and enter both imei numbers that is found in the back of your battery (enter the numbers correctly and cross check it again, its 15 digit number). then the software generates a new MP0B_001 file, copy and paste in the above mentioned directory and set the permissions to rw-rw---- and restart.:fingers-crossed:
dont forget to press thanks button if ive helped you :good:
Download Links:
Drivers: http://www.4shared.com/rar/XLiLMsG3/sp_drivers_v14.html?
SP flsah tool: http://www.4shared.com/archive/bjTXvBtd/sp_flash_tool_v3122401.html?
scatter txt: http://www.4shared.com/office/W7Fk6VOm/MT6575_Android_scatter.html?
I need to root my A2 too,can you tell me how?
thanks but I want to put ICS in my device karbonn a2 can u help more
thanx in advance
Sent from my Karbonn A2 using xda app-developers app
vickykeeth said:
thanks but I want to put ICS in my device karbonn a2 can u help more
thanx in advance
Click to expand...
Click to collapse
its not possible to put ICS in A2 (since its officially not supported to our device), although cyanogenmod 9 can be installed but its very difficult to build it since most of the drivers are properitery and they wont release the sources. so its almost impossible to run cm9 and even if someone did build cm9 it wont run smoothly because of very low amount ram in our device (<256MB and ICS needs more than that to work smoothly). however im working to build cm7 (based on gingerbread) for our device and even that is really difficult since there is no device tree in github for this device. so i need build cm7 from scratch and that is not an easy job. so if any developers are working on building cm7 for A2 please pm me so that we can work together..
cm10
abhiatreyas said:
its not possible to put ICS in A2 (since its officially not supported to our device), although cyanogenmod 9 can be installed but its very difficult to build it since most of the drivers are properitery and they wont release the sources. so its almost impossible to run cm9 and even if someone did build cm9 it wont run smoothly because of very low amount ram in our device (<256MB and ICS needs more than that to work smoothly). however im working to build cm7 (based on gingerbread) for our device and even that is really difficult since there is no device tree in github for this device. so i need build cm7 from scratch and that is not an easy job. so if any developers are working on building cm7 for A2 please pm me so that we can work together..
Click to expand...
Click to collapse
if we create any partion sd memory for our internal memory can it run cm10 b'cuz galaxy ace can run cm10 it has just 256MB ram and some wat 800MHZ speed only but our device has 256MD ram with 1GHZ processor speed so i think it can also run cm10 if we create a partition memory from ous sd card thats wat i think so........
waiting for reply from ur side thanks in advance.......
urgent help
i tried to reset my karbonn a2 and done it after reboot it shows no service and also no network wat to do pls tell me thanx in advance..........
vickykeeth said:
if we create any partion sd memory for our internal memory can it run cm10 b'cuz galaxy ace can run cm10 it has just 256MB ram and some wat 800MHZ speed only but our device has 256MD ram with 1GHZ processor speed so i think it can also run cm10 if we create a partition memory from ous sd card thats wat i think so........
waiting for reply from ur side thanks in advance.......
Click to expand...
Click to collapse
lol i was a galaxy ace user untill last dec. (its touch digitizer got broke, so i temporarily bought karbonn). anyway i do know ace can run cm10 and pretty much any device can, even ours can run it. i did not say our device doesnt run at all. i said it wont run smoothly and developing cm other than stock os version is very very difficult since our device is a local device and threre is no lot of support for it. so if anything goes wrong we may permanently brick our devices and may not find solution at all.
on the other hand, since i was a former ace user, i know that even though ace can run cm9 and cm10 there were a lot of problem in getting camera, video recording, and other applications because of unavialablity of their sources. so furthermore most of extra features that arent available in gingerbread cannot be used ex: face recognition, google now,otg usb etc( they are built for high end devices). u wont notice the difference in optimizations and performance of jelly bean in low end devices because they need sufficient hardware to utilize the os to full extent. so only thing u get out of installing cm is user interface (which u can change using of launchers, oh yes there are big bunches of launchers out there) and some features of cm (deodexd rom,custom kernel with overclocking features and some tweaks.)
coming back to our device, ive been trying to build cm7 for our device and its really difficult without a device tree and some good prior experience in building cm for atleast 2 devices. so my advice is that first we will build a fully working cm7 for our device and later if possible we will port cm10.
vickykeeth said:
i tried to reset my karbonn a2 and done it after reboot it shows no service and also no network wat to do pls tell me thanx in advance..........
Click to expand...
Click to collapse
what do u mean by reset? did u do factory reset from recovery or did u clear flash from by holding power+down? (oh btw recovery is power+up in our device).
either way ur imei number has been erased and it will be reset to factory number . i spent 1 week day and night searching for a solution and that is exactly why i told u to backup your MB0P_001 file.
in order to repair it u need to root ur phone. follow above steps and paste ur imei number (dial *#06#).
Nothing in SuperOneClick
I am successful in doing everything, but when I open SuperOneClick, it does not show any device, and clicking "Root" greys off the button for a few seconds, and everything is back to normal again. Nothing happens to the phone.
What is wrong?
shyamsn00 said:
I am successful in doing everything, but when I open SuperOneClick, it does not show any device, and clicking "Root" greys off the button for a few seconds, and everything is back to normal again. Nothing happens to the phone.
What is wrong?
Click to expand...
Click to collapse
ru sure u replaced boot.img which was attached in attachments to your phone? if it was successful then u have unlocked the bootloader. the problem here seems to be like superonclick isnt detecting ur phone when connected to pc. In case if the usb debugging is turned off enable it and check if ur device is listed in adb devices command as explained above. if it does and still rooting doesnt work, then maybe you are using wrong version of superoneclick. because some of the loopholes which is used to root your phone (by gaining temporary access to shell) is not available in older versions. the version must be compatible with gingerbread. try downloading superonclick 2.3.3 version.
also, after u root with superonclick, restart it and please check if u have superuser app in ur phone(it will be automatically installed by superoneclick, dont install it manually since the app should be in /system/app and su command should be in /system/bin directory, which u cannot do by installing it manually). if its installed then u have root access, if u still want to confirm just download root checker app from google play and run it.
CM10 means Jelly Bean Which has minimum Requirement of 512MB ram... device cant even Support Cm9(ics)...And generally cynogenmods are not developed for local Indian Brands.....Instead Try this making your phone look like XPERIA:
http://forum.xda-developers.com/show....php?t=2095956
abhiatreyas said:
ru sure u replaced boot.img which was attached in attachments to your phone? if it was successful then u have unlocked the bootloader. the problem here seems to be like superonclick isnt detecting ur phone when connected to pc. In case if the usb debugging is turned off enable it and check if ur device is listed in adb devices command as explained above. if it does and still rooting doesnt work, then maybe you are using wrong version of superoneclick. because some of the loopholes which is used to root your phone (by gaining temporary access to shell) is not available in older versions. the version must be compatible with gingerbread. try downloading superonclick 2.3.3 version.
Click to expand...
Click to collapse
I have indeed replaced the boot.img file and am using the latest version of S1C [ 2.3.3, I guess ]. Can the problem be because of Win8? Should I try doing this in W7?
hi there thanks for sharing that
But i can't find the way to do anythings that u said .....
i cant updated my phone driver, when i do it says up to date ....
can u please help me
thanks
Mr1010ass said:
hi there thanks for sharing that
But i can't find the way to do anythings that u said .....
i cant updated my phone driver, when i do it says up to date ....
can u please help me
thanks
Click to expand...
Click to collapse
im sorry, im not able to understand your problem. please give more information about your issue.
shyamsn00 said:
I have indeed replaced the boot.img file and am using the latest version of S1C [ 2.3.3, I guess ]. Can the problem be because of Win8? Should I try doing this in W7?
Click to expand...
Click to collapse
ok try it once in win7 and check if the issue is resolved, if not please explain clearly what is the problem and what error message you are getting.
need ua help
hey with your help i rooted my phone successfully.. Thanxx alot,,
Bt please invent custom for karbonn A2.. please
Waiting for your reply..
First 3 steps problem
I already downloaded everything and it seems like even before I started I already encountered a problem. When I try step 2 my KArbonn A2 device cannot be found on the list of devices on the cmd.... No "Android Phone" is found on my device manager but only "Karbonn - A2MS USB Device". When I update the driver it says that it is already the best driver for my device.... I need help pls.....:crying:
BOOTLOOP????????
I cannot boot up after flashing the boot.img,you provides...I've been able to flash cwm recovery successfully and make backups of my recoveries and boot.img...But when I flash the provided boot.img,My phone goess inot a bootloop It shows Karbonn A2 splash and shuts down and restarts,doing the same thing over and over again...Please tell me whether it is a problem with the boot.img or have I done something wrong in the flashing procedure???
Thank you..... finally found out where I went wrong... now my phone is rooted..... A hundred thanks....:victory:
Hello, this is really weird. In fact, when I insert the SIM to my Note 2 N7100 and turn it on, it allows me to make emergency call, but I cannot use it to make any others and it doesn't show the carrier name (it shows Emergency call only). And when I try to use it to make normal phone calls, it says that I am not registered to a mobile network. I try to factory reset my phone, but the problem remains. I then try to remove the SIM card, and it says that I need to insert a SIM card (that means that it is not a hardware problem since it recognizes the card). I then try to go to the mobile network setting to try to connect to the network manually, it connects me but it shows me a warning which says that the mobile network service is not available (and the Emergency call only label remains). However, I am sure that this is not the problem of the card neither since when I insert the card to my Moto MB860, I can make calls as usual. So, what is the problem ??? It seems to me that the problem happens spontaneously since it works perfectly until yesterday. And all other wireless function works fine including wifi , Bluetooth and GPS and the only thing goes wrong is 3g and 2g.
Additional information:
ROM: Omega v.16
Carrier: Fido Canada (as you can see)
Thanks.
First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...
Noob 1st post......have had similar problems with koodo CDN
Not gonna give such an in depth suggestion as above.....he's something simple to try.
I live in a dead zone and often my phone ( galaxyAce) will switch to no service. Even after refreshing and selecting network under settings, it says it's connected, but isn't. A simple apk that always fixes the problem for me is Network Signal Booster @ theplaystore
jabrif said:
First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...
Click to expand...
Click to collapse
I tried a simple way which is format everything and flash another ROM but the problem remains.
TRS_80 said:
Noob 1st post......have had similar problems with koodo CDN
Not gonna give such an in depth suggestion as above.....he's something simple to try.
I live in a dead zone and often my phone ( galaxyAce) will switch to no service. Even after refreshing and selecting network under settings, it says it's connected, but isn't. A simple apk that always fixes the problem for me is Network Signal Booster @ theplaystore
Click to expand...
Click to collapse
I don't know that we are in the same situation since at home I often got a good signal and this happened to me only since yesterday.
jabrif said:
First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...
Click to expand...
Click to collapse
Some updates;
- IMEI is checked.
- I do not have any efs backup
- nv_data.bin has been deleted and recreated
- trying to register for the firmware
- My phone is always rooted.
Dan Law 001 said:
Some updates;
- IMEI is checked.
- I do not have any efs backup
- nv_data.bin has been deleted and recreated
- trying to register for the firmware
- My phone is always rooted.
Click to expand...
Click to collapse
Results..??
Sent from my GT-I9001 using xda premium
jabrif said:
Results..??
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
I need to get the firmware first... since I already passed the download quota for today... need to wait until tomorrow...
Mmm... I heard that you mentioned clearing the EFS in your given procedure, but I do not think that I modified that folder... However, about few days ago, since I want to gain better control on the volume on my headphone remotes, I did modify the file called Generic.kl in system/usr/keylayout, but I restore it after since it didn't work. However, I don't think that this modification will trigger something in the efs folder since it has different directory. By the way, I did some research online and they say that the efs contains information about the carrier on the phone, so will there's a greater chance that the problem is caused by the possible modification on the efs than any other factor and will there also something else that possibly trigger the similar effects?
Sent from my GT-N7100 using xda premium
Still nothing
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 bought an unlocked samsung captivate glide. At first it worked normally but then the sim card was not recognized any more.
I started studying what the causes of this could be.
Baseband is shown as "unknown" and when i put *#06# IMEI says "null/null".
Now I suppose it is a problem with the files in the EFS folder.
When i open nav_bin file with hex editor it is all blank, all the fields have "ff" and the last ones "00"
I need to restore the EFS folder in order to have at least a generic IMEI, isn't it wright? How can i manage to do this?
I don’t have any backup of the original files; anyway i don’t care having a generic IMEI to begin with.
Any help is appreciated
Any way of restoring baseband and/or IMEI ??
margram said:
Any way of restoring baseband and/or IMEI ??
Click to expand...
Click to collapse
You can try flashing the phone to stock with Odin...
I need experts review and help to resolve my issue last night i am update my phone s20 ultra G988B/ds to its original software everything working fine except network i was using root phone it was fine on all networks but after updating my imei status goes to NG(not good) sim accepted phone but shows emergency calls both imei shoes but network not working plz give me suggestions and issue solution. I am again root my phone but still not working networks plz help
S20 ultra imei status NG
Why you experts not solving my issue no comments at all?
Bro i've posted same kind of post just now i hope someone replies soon otherwise i'll try z3x software or chimera and let you know about the results, i think if your imei is not corrupted then cert file will do the wonder.
well hey everyone same issue i have s20 plus phone was rooted and i flash the firmware and now imei is NG i trid the chimera tool but no luck if u find any fix please help me.
did you guys resolve it ?
i may have an idea
Any fix
do you guys even search before asking?
First, do a TWRP backup, all partitions including efs & modem.
Open the root explorer app, open the efs folder, delete the files named nv_data.bin
, nv_data.bin.md5 & the folder called imei. Then open twrp, wipe all partitions. Flash the latest firmware with Odin.
That solution work???
juda iskariotsky said:
do you guys even search before asking?
First, do a TWRP backup, all partitions including efs & modem.
Open the root explorer app, open the efs folder, delete the files named nv_data.bin
, nv_data.bin.md5 & the folder called imei. Then open twrp, wipe all partitions. Flash the latest firmware with Odin
Click to expand...
Click to collapse