Database Develop

No signal on CM7/MIUI

I'm having a major problem with MIUI (or anything based on CM7 for that matter):
- Can't get signal on MIUI or CM7 no matter what I do. I've tried wiping and reflashing, tried reverting to 2.2 and reflashing from there, I've disabled SIM lock, tried flashing without SIM, then WITH SIM and nothing. It seems as if the phone did not recognize the SIM card in it. (SIM works fine in other phones and also on other roms, it's just CM7)
- Random reboots
Anyone experienced anything like this? Or just heard of someone experiencing anything like this? Or anything really, I'd love to use MIUI, but a phone without signal is seriously gimped...

right firstly check that your IMEI number is intact, sometimes this can get corrupted along the way..
if it is fine, boot into recovery, Format /system /cache /dalvik cache - then re flash MIUI in recovery.
if the problem still persists, flash back to froyo again, make sure its a froyo rom - with froyo bootloader (im not sure which)
flash that in odin and start all over again - trust me it will be worth it .
can i just ask what rom did you come from before going to CM7 - MIUI

Thanks for your reply! First I tried flashing from a kitchen-cooked ZSJPK, and after that EZBase JVE. My IMEI is fine, and I followed all instructions correctly, of that I'm positive, but still CM7/MIUI gets no signal.

As above, check IMEI. If corrupt or unknown, flash EZbase froyo then if going to MIUI, flash RC7 stock. You won't get any signal problems then. If you want to move and update from there, you can but just make sure to format etc.

Is RC7 a requirement? The link to it in the MIUI thread seems to be down...

I have this problem also with MIUI (1.12.30). I have checked my IMEI and it's good. However, I don't understand what to do now. I'm very new at this. I would appreciate a lot if I could get more detailed explanation. I really need help.
Thank you very much.

[SOLVED] Backup TA keeps giving black screen and won't boot

Hey all. Quick run down of the situation.
I firstly rooted the phone and ran a TA backup (four times for safety) then unlocked bootloader and loaded up w/ DoomKernel straight after. Works fine like that w/ stock ROM.
I then decided to install CarbonROM (the latest stable, not nightly or beta) and it wouldn't pick up my SIM card at all. I checked my baseband and IMEI and they were both listed as unknown. I then went to run TA Backup but every time I did it it kept saying access denied to backup up my existing partition and integrity failed at the end. It seemed to be a permissions issue but I couldn't figure out how to fix it. Eventually I found I hadn't enabled root access in ADB as well (one of CarbonROMs features). After this the TA backup runs through fine until I need to reboot the phone. When it goes to reboot it will just turn off and stay off. Trying to start it up will make it buzz once after a few seconds but won't turn on. I can still access Flash and Fastboot modes so it's no problem returning back to stock with an .FTF file.
I need to know why my TA backups keep causing my phone to fail at boot and what I can do to change it.
Also, I've noticed that even after flashing DoomLord's root image and CarbonROM I don't actually have SuperSU, SuperUser or Busybox installed. I'm thinking it's not a big issue as the TA backup still runs indicating it has root access but maybe it's something to look in to.
SOLVED
So it seems the entire problem stemmed from the so-called "stable" build of Carbon. I've updated to the latest 4.2 nightly build and it picks up the SIM card fine w/ and w/o my personal TA keys. So happy to finally have a working custom ROM. Thanks to all that helped.

potplanty said:
Hey all. Quick run down of the situation.
I firstly rooted the phone and ran a TA backup (four times for safety) then unlocked bootloader and loaded up w/ DoomKernel straight after. Works fine like that w/ stock ROM.
I then decided to install CarbonROM (the latest stable, not nightly or beta) and it wouldn't pick up my SIM card at all. I checked my baseband and IMEI and they were both listed as unknown. I then went to run TA Backup but every time I did it it kept saying access denied to backup up my existing partition and integrity failed at the end. It seemed to be a permissions issue but I couldn't figure out how to fix it. Eventually I found I hadn't enabled root access in ADB as well (one of CarbonROMs features). After this the TA backup runs through fine until I need to reboot the phone. When it goes to reboot it will just turn off and stay off. Trying to start it up will make it buzz once after a few seconds but won't turn on. I can still access Flash and Fastboot modes so it's no problem returning back to stock with an .FTF file.
I need to know why my TA backups keep causing my phone to fail at boot and what I can do to change it.
Also, I've noticed that even after flashing DoomLord's root image and CarbonROM I don't actually have SuperSU, SuperUser or Busybox installed. I'm thinking it's not a big issue as the TA backup still runs indicating it has root access but maybe it's something to look in to.
Click to expand...
Click to collapse
I'm not an expert in this but I'm just offering an opinion.Do the following:
1.Try flashing it back to the stock ROM(the one u were on when u took the TA partition backup)
2.Root it using the appropriate root method
3.Enable USB debugging & use the Backup TA tool to restore TA partition

Thanks for that. It seems to work fine on the stock ROM but on the stable build of Carbon it just won't work for ****. Trying out two different nightlies now. If that doesn't work I'm thinking a different ROM is in order.
Cheers anyway. I'll keep trying.

Don't forget to unlock bootloader again when flashing non-stock based ROMs. When you restored TA (I'm assuming thats what you did seeing as you already had 4 backups), bootloader became relocked, so that's why carbon ROM wouldn't boot anymore.

shoey63 said:
Don't forget to unlock bootloader again when flashing non-stock based ROMs. When you restored TA (I'm assuming thats what you did seeing as you already had 4 backups), bootloader became relocked, so that's why carbon ROM wouldn't boot anymore.
Click to expand...
Click to collapse
Alright so unlocking the bootloader gets it to boot again now only I still have an unknown baseband and IMEI despite the fact I JUST restored my TA partition. I'm flashing a nightly now so I'll see what happens there. I'm starting to think the stable build isn't.

Maybe you should pay a visit to Carbon ROM thread and ask WTF is going on?
Sent from my C6603 using xda app-developers app

EFS folder/IMEI problem

Hi everyone,this is my first post here on xda but i have been observing and following XDA forum for quite a while now,
Now recently I tried to install Origional CM10.2,
Steps i followed were
I had 2.3.4 ( i did installed CM9 almost an year back but then odin back to stock for reasons i dont remember now)
First i Flashed Speedmod kernel via odin 1.7, and then flashed glitch kernel zip using the recovery that came the speedmod kernel,
Wiped devlik cache and went on to install CM10.2,
Everything went fine till i noticed that i was not getting any reception and after googling a bit,identified the problem as efs folder corruption!
I immedietly flashed back to 2.3.4 using oddin and that solved the problem, and my fone was getting the signals on stock 2.3.4,
Following instructions from google, I used EFS recovery softwere to backup my EFS folder,
and then followed the same sequence to flash again to 10.2CM, but here come the tricky part, EFS pro didnt seem to work on CM10.2, i have everything installed perfectly, debugging mode is on, still cant get to restore the efs folder!
I even tried manually copying the backed up EFS folder and putting it in system folder using root explorer etc,but that didnt seem to work, I changed the permission to Read/write aswell, still it says operation failed!
EFS pro was my best hope but it just doesnt work, tried a newer verison of it(newer than the one that i used to backup the efc on GB),that opened but didnt have my device in supported list,and neither was showing any backup!!
This is what i have been doing for past two days
Now I am back to 2.3.4,and IMEI is working fine now.
and additionally just to check whether this happens only on cm10.2 or other versions as well, I flashed Cm10.1 aswell as cm9, same problem there aswell
(As far as i remember ,last year when i flashed CM9,it worked fine but was laggy so i flashed back,only thing i did differently was that i didnt install any kernel)
So any ideas how i should proceed now?
I would thankful if someone can help me ,
and sorry for the long story,i wanted to give as much precise info abt problem as possible!

MUBASHIR888 said:
Hi everyone,this is my first post here on xda but i have been observing and following XDA forum for quite a while now,
Now recently I tried to install Origional CM10.2,
Steps i followed were
I had 2.3.4 ( i did installed CM9 almost an year back but then odin back to stock for reasons i dont remember now)
First i Flashed Speedmod kernel via odin 1.7, and then flashed glitch kernel zip using the recovery that came the speedmod kernel,
Wiped devlik cache and went on to install CM10.2,
Everything went fine till i noticed that i was not getting any reception and after googling a bit,identified the problem as efs folder corruption!
I immedietly flashed back to 2.3.4 using oddin and that solved the problem, and my fone was getting the signals on stock 2.3.4,
Following instructions from google, I used EFS recovery softwere to backup my EFS folder,
and then followed the same sequence to flash again to 10.2CM, but here come the tricky part, EFS pro didnt seem to work on CM10.2, i have everything installed perfectly, debugging mode is on, still cant get to restore the efs folder!
I even tried manually copying the backed up EFS folder and putting it in system folder using root explorer etc,but that didnt seem to work, I changed the permission to Read/write aswell, still it says operation failed!
EFS pro was my best hope but it just doesnt work, tried a newer verison of it(newer than the one that i used to backup the efc on GB),that opened but didnt have my device in supported list,and neither was showing any backup!!
This is what i have been doing for past two days
Now I am back to 2.3.4,and IMEI is working fine now.
and additionally just to check whether this happens only on cm10.2 or other versions as well, I flashed Cm10.1 aswell as cm9, same problem there aswell
(As far as i remember ,last year when i flashed CM9,it worked fine but was laggy so i flashed back,only thing i did differently was that i didnt install any kernel)
So any ideas how i should proceed now?
I would thankful if someone can help me ,
and sorry for the long story,i wanted to give as much precise info abt problem as possible!
Click to expand...
Click to collapse
Were you rooted when you tried to manually restore your efs folder? It should let you change it if you have the right permissions.
I would try to make a manual backup of your efs folder while you're on stock GB and try it again on the ROM you wanna use if you lose your IMEI again. Perhaps try another ROM as well, see if you get the same issue.

I have had problems with losing my imei after flashing to cm10 variants as well. In the steps that I took in this video I didn't lose it and I haven't had anybody else report that they have in the comments.
https://www.youtube.com/watch?v=_hmck9ES6jM

BWolf56 said:
Were you rooted when you tried to manually restore your efs folder? It should let you change it if you have the right permissions.
I would try to make a manual backup of your efs folder while you're on stock GB and try it again on the ROM you wanna use if you lose your IMEI again. Perhaps try another ROM as well, see if you get the same issue.
Click to expand...
Click to collapse
Arent Cyanogen Mods are already rooted?
I used the File explorer that was included in CM10'.2 and in settings i changed its permissions to ROOT ACCES.
Still i cant copy anything to EFS folder.
To be on the safe side,i tried Rooting Cm10..2 with Vroot,one click softwere and it showed that my phone had root Permissions!
Still I CANT WRITE ANYTHING WITHIN SYSTEM FOLDER,root explorer says that I dont have Root permissions, even after i rooted with Vroot!
I am confused

MUBASHIR888 said:
Arent Cyanogen Mods are already rooted?
I used the File explorer that was included in CM10'.2 and in settings i changed its permissions to ROOT ACCES.
Still i cant copy anything to EFS folder.
To be on the safe side,i tried Rooting Cm10..2 with Vroot,one click softwere and it showed that my phone had root Permissions!
Still I CANT WRITE ANYTHING WITHIN SYSTEM FOLDER,root explorer says that I dont have Root permissions, even after i rooted with Vroot!
I am confused
Click to expand...
Click to collapse
I would suggest trying with another file explorer. There are many on the Play Store (I personally like Root Explorer but there are free options).

[Q] Unknown baseband/imei null after twrp install, ideas?

Today I made a first step towards custom ROM by installing the latest TWRP with Odin and taking a backup of all partitions. Rebooted and unfortunately now I have IMEI null and baseband null (it was originally I9305XXUFOA1 I believe)
Nothing else has been touched, I am still using stock ROM, and reset to factory default did not solve it...
I still have the IMEI number and a backup of the EFS partition. But when I restored this partition with TWRP, I still have No Signal.
I searched the forums and only thing closest is a post about the S4: http://forum.xda-developers.com/showthread.php?t=2370699
Is there any suggestion on what I can try to recover this problem?
If I type *#1234#, I get
AP I9305XXUFOB2
CSC I9305PHNFOB2
But no CP?

Now I did a total restore of the backup made with TWRP, but still "unknown baseband"

In case it helps others, here is what I learned
When flashing TWRP 2.8.7.0 on my 9305 with Odin, my modem becomes unusable every time.
It can be easily restored if you have the modem firmware, so that solved it. But it seems TWRP is very unreliable until I downgraded to an older version of it, 2.7.0.0. Now everything is working, although it can be tricky to get into the recovery mode (holding buttons for up to 30 seconds). I suppose this is normal behaviour...

Help please
cpct said:
In case it helps others, here is what I learned
When flashing TWRP 2.8.7.0 on my 9305 with Odin, my modem becomes unusable every time.
It can be easily restored if you have the modem firmware, so that solved it. But it seems TWRP is very unreliable until I downgraded to an older version of it, 2.7.0.0. Now everything is working, although it can be tricky to get into the recovery mode (holding buttons for up to 30 seconds). I suppose this is normal behaviour...
Click to expand...
Click to collapse
Hi, I'm going nuts reading for the past 5 hours all the info about this issue and the multiple solutions i have tried with no success, i just stumbled in your post which describes exactly my problem, after flashing twrp bam!!
I have no backups, i bought this phone yesterday, unrooted this morning , spent some hours customizing stuff, got to the point to install a recovery to do a nand backup as the phone had all the apps and settings i wanted and this just happened, i am now going to do a complete stock flash, will it repair my modem? If not can you please provide me with a link to the modem firmware? Is it country associated, will i need a specific for my country/operator?
Thanks,
Bruno

bpi_pt said:
Hi, I'm going nuts reading for the past 5 hours all the info about this issue and the multiple solutions i have tried with no success, i just stumbled in your post which describes exactly my problem, after flashing twrp bam!!
I have no backups, i bought this phone yesterday, unrooted this morning , spent some hours customizing stuff, got to the point to install a recovery to do a nand backup as the phone had all the apps and settings i wanted and this just happened, i am now going to do a complete stock flash, will it repair my modem? If not can you please provide me with a link to the modem firmware? Is it country associated, will i need a specific for my country/operator?
Thanks,
Bruno
Click to expand...
Click to collapse
Hi Bruno,
You should try to (re)flash only the modem with Odin. It's not so difficult, just take your time to familiarize with the steps.
To get a modem.bin, either you extract it yourself from a stock rom zip (see http://www.sammobile.com/firmwares/) or get one from the topics at xda (for the 9305 I got XXALK2 from http://forum.xda-developers.com/gal...05/modems-i9305-cwm-flashable-modems-t2010116).
I suppose you have no access to TWRP right now? If so, reflash it with Odin too. I recommend version 2.7.0; it works for me very well. Then immediately take backup of everything (EFS etc) and transfer it to your PC
Let us know how it goes,

SOLVED: Null IMEI and baseband
Hi all,
My problem is solved, after flashing the latest stock ROM for my model (I9300) I got my IMEI back and everything back to normal, as told I could have just the modem.bin flashed but I went for the full re-image.
Then i unrooted using cf-autoroot and flashed twrp version 2.8.6.0 instead of 2.8.7.0, rebooted and everything ok. I already performed a full nand backup and learned various lessons from this. I think guys at TWRP should know that their latest version for the galaxy s3 is causing this problem, i believe most people will send their phones for repair because there are so many possible causes for this problem and so many xdifferent possible solutions that most people will quit solving the problem and will try to return the phone for repair.
Thanks for your reply and for the help. I will send an email to twrp linking to this thread.
Melhores cumprimentos ( portuguese for Best regards)

Aye Aye Aye, I CAN NOT get the finger print scanner to work...+

Long story shorter. Phone stolen. Phone had nandroid stored on my computer. Phone replaced by another Note 4 (PS, thief go pound sand). Didn't mess around, stock rom to Note 4 (ANK). Root. Recovery. Old image from lost phone used as recovery. (Yeah I didn't make a backup of original from new phone). Flashed over. Everything works fine. Now ready to put finger prints in. Error page pops up saying fingerprint scanner error. 72 hours of scouring this forum, internet, MULTIPLE stock rom flashes from the oldest to NJK to ANK and COG6. Clean flash, dirty flash NOTHING works. Makes no difference what I do, cannot get the fingerprint scanner to perform. Common problem, complaints all over the internet about it but NO SOLUTIONS. I have tried everything down to deleting directories and I cannot get the damn thing to work. Seriously doubt hardware issue. *#0*# sensor heading shows finger print scanner as Null and 0.0.0.0. Deleted cache. Deleted data from TIBU and now after three days I give up. Seems everyone has the problem but nobody knows why and when they do you get a half assed or worse answer as to how to fix it. Does anybody know how to get this thing working again. Do I need to flash an apk. Where can I find it. Do I need to rebuild. ? Can anyone flash that section fingerprint free and send it to me. I am just guessing. I know crap about how stuff works, I just know how to follow directions but this one has got me stumped.
Any help would be GREATLY APPRECIATED!
Regards,
Freddie did not get fingered but he needs it.

You need to flash stock firmware and verify that all is stock, sometimes after returning to stock you may have a miss matching error like bootloader or modem.
After running stock run smartswitch.
Pp.

PanchoPlanet said:
You need to flash stock firmware and verify that all is stock, sometimes after returning to stock you may have a miss matching error like bootloader or modem.
After running stock run smartswitch.
Pp.
Click to expand...
Click to collapse
Ok forgive me for my ignorance but if I run a stock firmware straight from Sammy shouldn't the bootloader and modem be part of the rom? It seems to me that doing a wipe should be like reinstalling windows, you format the drive and install the OS. There is nothing left and a complete rebuild of the file system occurs. Is this not what happens when you do a wipe in the recovery and then Odin the stock firmware? How can I be sure that when I install a stock rom everything is wiped and there is no hangers and the OS on the phone is rebuilt completely? When you say smartswitch I assume you mean the Sammy program.

jackler1 said:
Ok forgive me for my ignorance but if I run a stock firmware straight from Sammy shouldn't the bootloader and modem be part of the rom? It seems to me that doing a wipe should be like reinstalling windows, you format the drive and install the OS. There is nothing left and a complete rebuild of the file system occurs. Is this not what happens when you do a wipe in the recovery and then Odin the stock firmware? How can I be sure that when I install a stock rom everything is wiped and there is no hangers and the OS on the phone is rebuilt completely? When you say smartswitch I assume you mean the Sammy program.
Click to expand...
Click to collapse
Ok, I think I have found it but now I need to know how to fix it. Currently I have as follows in the about device screen:
Model SN-N910T
AHHA ------!!!!! - ANDROID VERSION 5.0
Baseband - N910TU1ANK4
Kernal version - 3.10.0-2796035 [email protected] #1 Thu Nov 13 18:01:07 KST 2014
Build number - KTU84P.N910TUVU1ANK4
So it seems the android version is wrong. Again forgive my stupidity but what exactly IS the android version. Meaning is that the baseband, the modem, what part of the stock rom is flashed wrong and where do I find that part to flash it correctly. I think I am making some progress just need input. Thanks Pp for getting me on track, now I just need a little shove to get this train rolling and maybe learn something in the process. If I fix it I then intend to write a proper write up for those lost souls out there who don't have to spend days....
So why does it say my android version is 5.0 when it should say 4.4.4?
Thank,
Freddy is getting nervous

First verify what version of the note 4 you have, Sm-N910T or Sm-N910T3 and flash proper firmware. Look under your battery.
Once you root you jumble up the phones ability to install firmware properly, and flashing stock firmware once with odin does not always secure components thus leaving you with unofficial status, "custom" and you think you went back to stock with no root but not official yet.
You need to make sure everything flashes and sticks, Model nunber, Android version, Basedand version, Kernel version, Build number.
Any of the modified components can stick and not be overwritten by stock odin flash.
Sometimes multiple flashes, or individual component flashes are required to go back to "official" stock form.
At this point you can verify that your fingerprint scanner works properly and leave it alone or proceed cautiously if root is really required ??? .
I only run stock and save myself all the headaches, I used to root back when Samsung phones where simple and less complicated without kernel security from Samsung.
I suggest latest 5.1.1 lollipop update, kitkat is primitive and outdated, you will be amazed at how well your note will run with latest firmware (with junk apps disabled).
Pp.

Here's a sample of my stock Note 4 running latest update.
Pp.

PanchoPlanet said:
Here's a sample of my stock Note 4 running latest update.
Pp.
Click to expand...
Click to collapse
Nope, I have wiped this phone a million times, reinstalled factory rom over the top of itself a dozen times, installed the baseband and bootloader separately after that and NOTHING changes it still will not work. I have read the complete internet from front to back and it seems nobody knows but the shadow.....Thanks for taking the time for trying to help me out though...

When you say wipe, do you mean factory reset?
Several resets in a row should wipe it clean. Something is stuck, could be the kernel, that will prevent a clean install.
You need to find a way to wipe partitions individually using ADB on the PC, that should allow for a clean install.
Pp.

jackler1 said:
Long story shorter. Phone stolen. Phone had nandroid stored on my computer. Phone replaced by another Note 4 (PS, thief go pound sand). Didn't mess around, stock rom to Note 4 (ANK). Root. Recovery. Old image from lost phone used as recovery. (Yeah I didn't make a backup of original from new phone). Flashed over. Everything works fine. Now ready to put finger prints in. Error page pops up saying fingerprint scanner error. 72 hours of scouring this forum, internet, MULTIPLE stock rom flashes from the oldest to NJK to ANK and COG6. Clean flash, dirty flash NOTHING works. Makes no difference what I do, cannot get the fingerprint scanner to perform. Common problem, complaints all over the internet about it but NO SOLUTIONS. I have tried everything down to deleting directories and I cannot get the damn thing to work. Seriously doubt hardware issue. *#0*# sensor heading shows finger print scanner as Null and 0.0.0.0. Deleted cache. Deleted data from TIBU and now after three days I give up. Seems everyone has the problem but nobody knows why and when they do you get a half assed or worse answer as to how to fix it. Does anybody know how to get this thing working again. Do I need to flash an apk. Where can I find it. Do I need to rebuild. ? Can anyone flash that section fingerprint free and send it to me. I am just guessing. I know crap about how stuff works, I just know how to follow directions but this one has got me stumped.
Any help would be GREATLY APPRECIATED!
Regards,
Freddie did not get fingered but he needs it.
Click to expand...
Click to collapse
try doing this...
1st - run chainfire triangle away v3.26
2nd - boot into recovery and wipe everything 3 times except external sdcard.. especially data...
3rd - boot in download mode and ODIN whatever firmware u wanna use... 2 times...
happened to me when the note 4 first came out... I had to exchange to a new note 4...
also whenever u do a nandroid.. U MUST REMOVE ANY SAVED FINGERPRINTS... so u can use that backup again..
if u restore a nandroid with a saved frintprints, it won't work, u must delete data and start fresh..
I don't know if u messed it up by restoring a nandroid from a previous phone and with saved fingerprints stored...

will do thanks for the advice will advise

Nope, nothing I do including stock or otherwise works. When you hit +#0*# it says null and 0.0.0.0 unless someone knows something I don't, it's borked. The thing is even if I used a nandroid and it overwrote my fingerprints where the ones in the nandroid so you would think it would work. Chalk it up to who knows....thanks anyway. Still looking if anyone finds solution....