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
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
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:
Ive found threads on here that says how its important to back up the IMEI number, but I havent been able to find how to actually do that. I am on a custom Rom right now. Do I need to be on stock to back it up? Can someone point me in the direction of how to backup my IMEI number?
itsLYNDZ said:
Ive found threads on here that says how its important to back up the IMEI number, but I havent been able to find how to actually do that. I am on a custom Rom right now. Do I need to be on stock to back it up? Can someone point me in the direction of how to backup my IMEI number?
Click to expand...
Click to collapse
You are on a custom ROM so I'll assume you are rooted (you need root).
Download a terminal emulator from the play store, like this one: https://play.google.com/store/apps/details?id=jackpal.androidterm
Open it, type:
su <enter>
<grant root access>
reboot nvbackup
The device will immediately reboot. You will see a couple blue lines of text at the top left corner of the screen. This is how you know it worked. There are a thousand ways to back up your IMEI, like Andromizer, and I even made a script that will do it. This way, though, is still the best, because it uses the device's built in functionality to do the backup, and if needed, the automatic restore. No other tool or script can do that.
Aerowinder said:
You are on a custom ROM so I'll assume you are rooted (you need root).
Download a terminal emulator from the play store, like this one: https://play.google.com/store/apps/details?id=jackpal.androidterm
Open it, type:
su <enter>
<grant root access>
reboot nvbackup
The device will immediately reboot. You will see a couple blue lines of text at the top left corner of the screen. This is how you know it worked. There are a thousand ways to back up your IMEI, like Andromizer, and I even made a script that will do it. This way, though, is still the best, because it uses the device's built in functionality to do the backup, and if needed, the automatic restore. No other tool or script can do that.
Click to expand...
Click to collapse
How can I pull it to back it up to my computer or my dropbox? Just to keep a copy of it safe somewhere.
itsLYNDZ said:
How can I pull it to back it up to my computer or my dropbox? Just to keep a copy of it safe somewhere.
Click to expand...
Click to collapse
With this method, you can't. The partitions that get backed up are copied to otherwise unused partitions on your device. They have no other purpose. It's been theorized that this was supposed to be done at the factory before shipping, and Samsung "forgot".
But backup is all about redundancy, so you can grab an app from the play store that can back them up to your sd card.
My phone was working fine before battery drained and it get switched off. But when i restarted the phone imei was null.
I have efs backup of 4.3 ( mj9 modem) but now i am on 4.4.2 . I tried restoring it but did not worked .
any help please..
sachinwadhwa46 said:
My phone was working fine before battery drained and it get switched off. But when i restarted the phone imei was null.
I have efs backup of 4.3 ( mj9 modem) but now i am on 4.4.2 . I tried restoring it but did not worked .
any help please..
Click to expand...
Click to collapse
try what i did here buddy. . post #3512
http://forum.xda-developers.com/showthread.php?p=57661153#post57661153
do it at tour own risk. goodluck!
edong23 said:
try what i did here buddy. . post #3512
http://forum.xda-developers.com/showthread.php?p=57661153#post57661153
do it at tour own risk. goodluck!
Click to expand...
Click to collapse
Thank you for your reply. Please help me to do this step wise
sachinwadhwa46 said:
Thank you for your reply. Please help me to do this step wise
Click to expand...
Click to collapse
this method works for me, but I am not sure if it will work for you. I have to warn you that I am not a dev, I am just a basic android user. I came up with this idea out of desperation because my phone cannot receive and make calls for almost 4 days. so do this at your own risk.
note:
* make sure your phone is rooted.
* make a copy of your old efs backup and all your important files in your computer or in a flash drive.
1. copy and write on a piece of paper your imei # which will be found at the back of your phone. it is 15 digit
2. copy your efs.img (not the folder that contain the efs image) to your internal storage. it is about 20mb. if there are two files then copy both.
3. connect to wifi and go to playstore and then download and install the IMEI Tool N7100 by Dr Ketan
4. download and install xposed installer and make sure to install update.
5. go to this thread and download and install imei changer
http://forum.xda-developers.com/xposed/modules/xposed-imei-changer-t2847187
make sure to activate it in exposed. then reboot your phone.
6. using ES File Explorer or any file manager with root privelege, go to /efs and delete all files
7. open imei changer then input your imei # (the one that you copied at the back of your pbone) then save. to make sure that your imei has changed dial *#06#. check if your imei if its the one you have written. if not go again to imei changer and change then make sure to save.
8. open IMEI tool by dr. ketan and restore efs backup. it will ask for root privelege so click grant.
9. after restoring efs, reboot to recovery and wipe cache and dalvik then reboot. check if you have data connection.
10. if its not working then go to recovery and make a full wipe and install new touchwiz rom (i used DN4 when I did this, but its up to you whatever you like). and repeat the steps.
* that's all I did mate. there is no scientific explanation about the process that I made, but when I did those things, my phone is working fine again. hopefully it will work for you brother. Good luck and God bless!
edong23 said:
this method works for me, but I am not sure if it will work for you. I have to warn you that I am not a dev, I am just a basic android user. I came up with this idea out of desperation because my phone cannot receive and make calls for almost 4 days. so do this at your own risk.
note:
* make sure your phone is rooted.
* make a copy of your old efs backup and all your important files in your computer or in a flash drive.
1. copy and write on a piece of paper your imei # which will be found at the back of your phone. it is 15 digit
2. copy your efs.img (not the folder that contain the efs image) to your internal storage. it is about 20mb. if there are two files then copy both.
3. connect to wifi and go to playstore and then download and install the IMEI Tool N7100 by Dr Ketan
4. download and install xposed installer and make sure to install update.
5. go to this thread and download and install imei changer
http://forum.xda-developers.com/xposed/modules/xposed-imei-changer-t2847187
make sure to activate it in exposed. then reboot your phone.
6. using ES File Explorer or any file manager with root privelege, go to /efs and delete all files
7. open imei changer then input your imei # (the one that you copied at the back of your pbone) then save. to make sure that your imei has changed dial *#06#. check if your imei if its the one you have written. if not go again to imei changer and change then make sure to save.
8. open IMEI tool by dr. ketan and restore efs backup. it will ask for root privelege so click grant.
9. after restoring efs, reboot to recovery and wipe cache and dalvik then reboot. check if you have data connection.
10. if its not working then go to recovery and make a full wipe and install new touchwiz rom (i used DN4 when I did this, but its up to you whatever you like). and repeat the steps.
* that's all I did mate. there is no scientific explanation about the process that I made, but when I did those things, my phone is working fine again. hopefully it will work for you brother. Good luck and God bless!
Click to expand...
Click to collapse
I followed the same procedure but did not worked.
One more thing i would like to mention that in recent past i got my complete pcb replaced by samsung service center but imei was same. and the backup of efs which i did was on previous pcb/motherboard. could that be the reason i am not able to restore imei?
hello everyone,
my device sm-n910a is currently working well with wifi connection, i'm using it in asia, so i need the IMEI to unlock the phone.
But unfortunately my IMEI went null, i don't know what caused it, but since the IMEI is still good, here's what happened :
1. I tried to unlock via *#9090#, i forgot what i've pressed, my phone immediately restarted itself, and it went in bootloop (switched on for about 1-3minutes and the phone restart itself again).
I've realized that the imei and baseband went null (*#06# shows "null")
2. Then i found an article in other forum to fix bootloop problem.
i followed the instructions there without realizing that it's supposed to be supported with a service box (octoplus)
The instructions are :
1. Downgrade to 4.4.4 via Odin. Extract OC4, extract Odin, open Odin, select four files into correct position (BL, AP, CP, CSC) 4.4.4 OC4 Odin 3.09 (Samsung Mobile drivers required)
2. Once on 4.4.4 or below, enable developer options by tapping "build version" several times, enable USB debugging & mock location, and install KingRoot 4.0.0.233 to phone. Caution, newer versions did not work for me.
3. Open "Command Prompt" and type "adb version" should reply with "Android Debug Bridge version x.x.x", if does not, change to the correct directory where adb is installed via "cd" command. Need ADB? Here
4. These next two steps can be a little tricky as the phone often reboots before completed, must work quickly, I suggest copying the long command, then paste when ready.
5. Connect to working WiFi. Turn off your phone, reboot, or wait for it to reboot itself. Soon as phone turns on, open KingRoot, soon as WiFi connected notification appears, touch button in center of KingRoot app, soon as KingRoot reaches 30%, began adb commands.
6. ADB commands: first command "adb shell", second command "su", third command "dd if=/dev/zero of=/dev/block/mmcblk0p10 | dd if=/dev/zero of=/dev/block/mmcblk0p13 | dd if=/dev/zero of=/dev/block/mmcblk0p14 | dd if=/dev/zero of=/dev/block/mmcblk0p15 | dd if=/dev/zero of=/dev/block/mmcblk0p16" phone will reboot or you can reboot and after reboot boot-loop and unknown baseband will be fixed! Can now write new IMEI via "Write Cert" and possibly "Write QCN" if any network troubles, then all good to go!
Click to expand...
Click to collapse
3. After finished all the instructions given, my phone's baseband got fixed, but the imei still unknown (*#06# shows "/01")
4. In the instructions said that it can be fixed by "write cert" from the box.
Unfortunately i can't find any box seller in my country.
And i've brought my phone to Samsung Service Centre, they said that they're going to TRY installing another ROM, and they said that the risk of the process failure is my phone will be dead, and if that happened, i have to bring back to US AT&T to fix the phone (which is very far from my current country).
I didn't want to take the risk, so i currently using my phone only with wifi.
I've checked via Root Explorer and ES Explorer while being rooted, the efs folder is empty.
Unfortunately, i don't have any backups from this phone.
Any solution for this condition?
Thanks before
IMEI
jooo91 said:
hello everyone,
my device sm-n910a is currently working well with wifi connection, i'm using it in asia, so i need the IMEI to unlock the phone.
But unfortunately my IMEI went null, i don't know what caused it, but since the IMEI is still good, here's what happened :
1. I tried to unlock via *#9090#, i forgot what i've pressed, my phone immediately restarted itself, and it went in bootloop (switched on for about 1-3minutes and the phone restart itself again).
I've realized that the imei and baseband went null (*#06# shows "null")
2. Then i found an article in other forum to fix bootloop problem.
i followed the instructions there without realizing that it's supposed to be supported with a service box (octoplus)
The instructions are :
3. After finished all the instructions given, my phone's baseband got fixed, but the imei still unknown (*#06# shows "/01")
4. In the instructions said that it can be fixed by "write cert" from the box.
Unfortunately i can't find any box seller in my country.
And i've brought my phone to Samsung Service Centre, they said that they're going to TRY installing another ROM, and they said that the risk of the process failure is my phone will be dead, and if that happened, i have to bring back to US AT&T to fix the phone (which is very far from my current country).
I didn't want to take the risk, so i currently using my phone only with wifi.
I've checked via Root Explorer and ES Explorer while being rooted, the efs folder is empty.
Unfortunately, i don't have any backups from this phone.
Any solution for this condition?
Thanks before
Click to expand...
Click to collapse
My baseband is ok but my IMEI is "unknown " does this mean there is hope
I had this happen to my note 2 i gave up and it sat for 6 months i bought another device and fogot about it then one day i was bored and decided to try fixing it again. I did fix it by flashing the modem i believe in odin can't remember exactly but when i turned it on everything came back. I deleted a folder i wasn't suppose to google that problem and you should find something ill try and find what i did.
bonebeatz1234 said:
I had this happen to my note 2 i gave up and it sat for 6 months i bought another device and fogot about it then one day i was bored and decided to try fixing it again. I did fix it by flashing the modem i believe in odin can't remember exactly but when i turned it on everything came back. I deleted a folder i wasn't suppose to google that problem and you should find something ill try and find what i did.
Click to expand...
Click to collapse
is it the modem.bin which is extracted from the ROM (tar.md5 file which we put on odin's AP) ?
i've tried it, but no luck :crying: