Develop Bugs

[Q] No Network or IMEI number, :-S

Hi there guys of XDA,
I have a major problem with my NOTE 2, after playing around with some ROMs, Cyanogenmod 11 4.4 NIGHTLY, 10.2 4.3 and Omni 4.4.1 NIGHTLY. I used CWM to load these ROMs with SUPERsu?. This is the first time i have flashed any ROMs onto my phone.
CM 11 was the first ROM i flashed on my NOTE 2 and that's when it started it couldn't detect my sim, It doesn't show me my IMEI number and my Baseband version. I didn't make a back-up of the stock because i didn't need one.
Now i'm stuck with a phone i can only use on Wifi is there anyone that can help? or if its happened to someone else? how did you sort it out?
Also can i restore this through KIES?

shirazi15 said:
Hi there guys of XDA,
I have a major problem with my NOTE 2, after playing around with some ROMs, Cyanogenmod 11 4.4 NIGHTLY, 10.2 4.3 and Omni 4.4.1 NIGHTLY. I used CWM to load these ROMs with SUPERsu?. This is the first time i have flashed any ROMs onto my phone.
CM 11 was the first ROM i flashed on my NOTE 2 and that's when it started it couldn't detect my sim, It doesn't show me my IMEI number and my Baseband version. I didn't make a back-up of the stock because i didn't need one.
Now i'm stuck with a phone i can only use on Wifi is there anyone that can help? or if its happened to someone else? how did you sort it out?
Also can i restore this through KIES?
Click to expand...
Click to collapse
I had this exact issue last week when flashing Kitkat AOSP ROM. Even restoring back to 4.3.1 no network connection was available, except for WiFi. Restoring your EFS will not even work. You just have to re-root your phone.
Not to worry, your phone is OK, perfectly OK. But just quite a bit of work needs to be done. Here: http://forum.xda-developers.com/showthread.php?t=2032849
1. Download original stock firmware for your country and telco
2. Download mode that firmware back to your phone using Odin
3. Download mode to install recovery, this will re-root your phone above steps will un-root your phone
4. Re-flash ROM of your choice, not Kitkat for now
After all i've gone through, and as much as i want to try Kitkat, i think this issue is recovery-related. Both TWRP and CWM needs updating for Android 4.4. I will wait until then.
All the best!

Gandicela said:
I had this exact issue last week when flashing Kitkat AOSP ROM. Even restoring back to 4.3.1 no network connection was available, except for WiFi. Restoring your EFS will not even work. You just have to re-root your phone.
Not to worry, your phone is OK, perfectly OK. But just quite a bit of work needs to be done. Here: http://forum.xda-developers.com/showthread.php?t=2032849
1. Download original stock firmware for your country and telco
2. Download mode that firmware back to your phone using Odin
3. Download mode to install recovery, this will re-root your phone above steps will un-root your phone
4. Re-flash ROM of your choice, not Kitkat for now
After all i've gone through, and as much as i want to try Kitkat, i think this issue is recovery-related. Both TWRP and CWM needs updating for Android 4.4. I will wait until then.
All the best!
Click to expand...
Click to collapse
Thanx for getting back to me at least someone can help. After i followed the things you told me to do. It didn't put the stock ROM back on there so i'm stuck with omni.
After Odin loaded everything to the phone it just keeps going into recovery mode? is that normal or am i doing it wrong because the link you posted up doesn't mention anything about that :-s and i followed everything that link said to do.

shirazi15 said:
Thanx for getting back to me at least someone can help. After i followed the things you told me to do. It didn't put the stock ROM back on there so i'm stuck with omni.
After Odin loaded everything to the phone it just keeps going into recovery mode? is that normal or am i doing it wrong because the link you posted up doesn't mention anything about that :-s and i followed everything that link said to do.
Click to expand...
Click to collapse
Mate, firstly this is the hard way of recovering from "Unknown Baseband" issue. Finally the simple solution was only to download and install an app called SELinux Mode Changer from PlayStore. Then using that app, change SELinux from Enforcing to Permissive resolved everything related to IMEI, EFS, and Unknown Baseband. So hard way I did; i didn't know any better then.
By the way the link is correct. Start from the procedure from the line that says "Installation Instruction [Mobile odin is now have support for NOTE2]"
You must be in download mode (Vol Down, Home, & Power button all pressed together) to flash the Stock ROM using Odin. But where is your status now? If in recovery, can you re-install a ROM? If u r able to reboot back up to OMNI, just install the SELinux app and u will be good to go.
Cheers!

shirazi15 said:
Hi there guys of XDA,
I have a major problem with my NOTE 2, after playing around with some ROMs, Cyanogenmod 11 4.4 NIGHTLY, 10.2 4.3 and Omni 4.4.1 NIGHTLY. I used CWM to load these ROMs with SUPERsu?. This is the first time i have flashed any ROMs onto my phone.
CM 11 was the first ROM i flashed on my NOTE 2 and that's when it started it couldn't detect my sim, It doesn't show me my IMEI number and my Baseband version. I didn't make a back-up of the stock because i didn't need one.
Now i'm stuck with a phone i can only use on Wifi is there anyone that can help? or if its happened to someone else? how did you sort it out?
Also can i restore this through KIES?
Click to expand...
Click to collapse
can you try what i did? http://forum.xda-developers.com/showthread.php?t=2567862&nocache=1
good luck.
"Just sharing my experience in solving this issue. Hopefully it will help solve those who have similar issues.
I flashed a file which messed up my EFS partition. I had a backup and tried to use the available programs to restore my EFS using my backup. None worked. I even brought it to the samsung store, but they said they would change the motherboard and reprogram, and replacement and service would cost more than half the cost of a new N7105. I purchased the phone in another country. The people who had stores to repair phones gave up on my phone. They also offered to replace the motherboard for US$175.00.
My phone was originally under a DMB2 rom (from Singapore I think). I flashed a DMC3 rom, and used this for five months, until i encountered the problem.
I initially gave up and got a note 3. But i could not believe the phone was junk and people in XDA (as I observed) do not seem to give up.
After two weeks, i found the solution below, which brought my phone to working condition.
1. I flashed the stock rom N7105ZHDMI2_N7105ZZHDMI2_TGY from sammobile.
2. I flashed a pit file using Odin. The pit file is found here:
http://forum.xda-developers.com/show....php?t=2137008
This restored the baseband. But IMEI was no longer NULL. However, it was still 0.
3. I downloaded and used the EFS Pro from this link:
http://forum.xda-developers.com/show....php?t=1308546
Before using EFS Pro, make sure you dial *#7284# and change the setting of Qualcomm USB Settings to
"RMNET + DM + MODEM"
I will not hurt your phone if you do, but EFS Pro will just not work. If you don't do this, the EFS Pro will display "Phone not responding" or something similar.
NOTE: I couldn't find the option with RMNET, but i used the option that also had an "RM*** + DM + MODEM".
After the phone is read, change back the IMEI to what it was originally.
Dial *#7284# again to change back to "MTP+ADB".
It's all working now.
Hope this is able to help someone. Now i have two working versions of Note.
Thanks to the authors of the program i used, and the people who uploaded the files used.
Cheers!

shirazi15 said:
Thanx for getting back to me at least someone can help. After i followed the things you told me to do. It didn't put the stock ROM back on there so i'm stuck with omni.
After Odin loaded everything to the phone it just keeps going into recovery mode? is that normal or am i doing it wrong because the link you posted up doesn't mention anything about that :-s and i followed everything that link said to do.
Click to expand...
Click to collapse
karlonicolas said:
can you try what i did? http://forum.xda-developers.com/showthread.php?t=2567862&nocache=1
good luck.
"Just sharing my experience in solving this issue. Hopefully it will help solve those who have similar issues.
I flashed a file which messed up my EFS partition. I had a backup and tried to use the available programs to restore my EFS using my backup. None worked. I even brought it to the samsung store, but they said they would change the motherboard and reprogram, and replacement and service would cost more than half the cost of a new N7105. I purchased the phone in another country. The people who had stores to repair phones gave up on my phone. They also offered to replace the motherboard for US$175.00.
My phone was originally under a DMB2 rom (from Singapore I think). I flashed a DMC3 rom, and used this for five months, until i encountered the problem.
I initially gave up and got a note 3. But i could not believe the phone was junk and people in XDA (as I observed) do not seem to give up.
After two weeks, i found the solution below, which brought my phone to working condition.
1. I flashed the stock rom N7105ZHDMI2_N7105ZZHDMI2_TGY from sammobile.
2. I flashed a pit file using Odin. The pit file is found here:
http://forum.xda-developers.com/show....php?t=2137008
This restored the baseband. But IMEI was no longer NULL. However, it was still 0.
3. I downloaded and used the EFS Pro from this link:
http://forum.xda-developers.com/show....php?t=1308546
Before using EFS Pro, make sure you dial *#7284# and change the setting of Qualcomm USB Settings to
"RMNET + DM + MODEM"
I will not hurt your phone if you do, but EFS Pro will just not work. If you don't do this, the EFS Pro will display "Phone not responding" or something similar.
NOTE: I couldn't find the option with RMNET, but i used the option that also had an "RM*** + DM + MODEM".
After the phone is read, change back the IMEI to what it was originally.
Dial *#7284# again to change back to "MTP+ADB".
It's all working now.
Hope this is able to help someone. Now i have two working versions of Note.
Thanks to the authors of the program i used, and the people who uploaded the files used.
Cheers!
Click to expand...
Click to collapse
Nice, thanks!
For all others that might face "unknown baseband" with 4.3 to 4.4 flashing of ROMS, SELinux Mode Changer app from Playstore will fix that problem. Install the app and set SELinux from Enforcing to Permissive.

i hope your problem is fixed.
i'm not too familiar with CM roms, as i have been using stock since gingerbread. but you have to first do a full wipe before flashing from CM to stock. did you do that? perhaps you can go to recovery, do a full wipe, include Dalvik and Cache. Then go to bootloader and flash your rom.
by the way, my chipset is qualcomm yours may be exynos. if so, then i'm not confident about this solution because i have tried this several times, but only on note 2 LTE.
good luck!

[INFO] As of 12-24-2015 the latest firmware for LPH-L710 (Sprint) is L710VPUDOH1

So i just spent the last 4+ hours trying to figure out what the latest firmware for the Samsung Galaxy S3 SPH-L710 since google was not my friend tonight.
So i had L710VPUDNJ2 installed on my phone... rooted, TWRP, unlocked bootloader.
I kept getting prompts about an update for the phone, and finally decided i couldn't ignore it anymore, so my journey began to get rid of it.
1st Headache; What is the latest firmware for the phone?
Well according to Sprint's Website for the SPH-L710 the latest version available is L710SPTBMK5.
OK, cool, this should be easy.
Go find a flashable ROM; [ROM][MK5][STOCK][ODEXED/DEODEXED] and flash it to my phone.... Stuck on boot... ****...
2nd Headache; Latest Flashable ROM is CRAP!
Boot back into TWRP and decide to say **** it and do a full wipe.
Wipe System/Data/Dalvik/Cache
Flash MK5 Rom
Reboot phone
Success!
Phone boots up and i can start tweaking it back to my standards... but wait... what's this? No cell signal at all...
Ok this is strange, but it's Samsung after all, so i expect it to be **** and have issues.
I go into Settings and look at the Mobile Networks settings... No Network mode selected.
I choose LTE/CDMA, the phone says it needs to reboot, i tell it OK
Thinking this was the problem and i am smarter than i apparently am, i started to smile and give myself a good pat on the back when the phone booted back up and still no signal.. WTF!?!?
At this point i'm convinced that XDA forums has the dumbest people in the world posting Roms on it and i decide to take on a new approach.
3rd Headache; Finding and downloading everything
So i know that L710VPUDNJ2 is a legit version for the SPH-L710 to work with Sprint.
So i find the ODIN download for it; [STOCK][ODIN][TAR] L710VPUDNJ2 PC Odin Flashable ( Sprint )
I download the latest version of Odin; Odin3 v3.10.7 (this version might change over time just fyi)
I downloaded the latest version of USB drivers for the phone; USB (Driver) ver.1.5.45.0 (this version may also change over time)
And then proceeded with the following
Install Latest drivers
Reboot PC
Put phone into "Download Mode" (Vol Down + Home + Power)
Ran Odin3
Clicked on AP and selected the NJ2 tar file (after extracting it from the .zip file of course)
Connected the phone to my PC
Clicked START after Odin3 recognized the phone
Well, low and behold after 20 mins or so, i have a working phone again! :good:
I go into the phone's settings and force it to check for an update, and wouldn't you know it, it found one!
I download and install the update, wait for it to come back up, and then immediately go to check what version it's on.... L710VPUDOH1
Well that's nice and all, the sprint website did say that was a version after L710VPUDNJ2, but it's not the LATEST version according to Sprint.
So, i go back and force the phone to check for updates.... Nothing!
So there you have it. Don't believe everything you read on the internet.
TL;DR: Sprint website lies. Use the links above to get on the latest version.

Well, you can't update with a rom zip. To update, you always have to use a .tar in odin. The .tar files contain the modem and bootloader files, which are required for an updated phone to boot.
You are lucky you didn't try an mk5 tar, you would have a hard brick. That is pre Knox firmware (4.3 jellybean). I heard there was a new mk5 too, I don't know for sure. But the first mk5 was the boost and virgin Mobile version of mk3. But someone posted they got an mk5 update that said stagefright patches, so.... Not sure. But oh1 and oj1 are the newest, I believe, for sprint, and boost/vm. Respectively
That thread you linked for the mk5 flash able zip clearly said jellybean 4.3 and that date was a couple years ago. Clear indication that it was not new.

There is supposedly a new MK5 that is supposed to fix Stagefright completely as opposed to a half fix from OH1.
L710SPTBMK5
Previous was L710VPUDOH1.
However, I suppose at this point, most of the userbase has already upgraded to a new phone or installed a custom ROM, so anything on this forum that's not 2015 and says MK5 is too old.

Stock Rom for Tab Pro 8.4

Good afternoon
About a year ago, I was looking for the stock rom for this tablet (4.2.2). I came across many iterations of it. From the stock roms page in this forum, I flashed a "stock rom" which apparently was for the UK. It was the latest 4.2.2 build and after flashing it I encountered an annoying and (for now) what appears to be an irreversible error. The rom is the listed as the following:
AP_T320XXU1ANB6_597056_REV00_user_low_ship_MULTI_CERT.tar.md5
Along with it came the following CSC and PIT files
CSC_OLB_T320OLB1ANB3_597056_REV00_user_low_ship_MULTI_CERT.tar.md5
MONDRIANWIFI_EUR_OPEN.pit
Since this flash, anytime I try to install a stock rom I got the ext4 failed error (or similar) in ODIN and twrp. I believe it is because of the pit and csc files that I flashed along with the rom.
Is there ANY US version that I can install that will reverse the error bringing the tablet back to it original form?
I downloaded this rom:
T320UEU1AOC1_T320XAR1AOC1_XAR
which I believe is the lastest 4.2.2 that came out for the 8.4.
Does it have a pit and/or csc that can be flashed with it to right any of the ext4 errors? I tried creating it on my after weeks of searching the web with apps that don't appear to work or no longer supported (like samsung full firmware maker etc). Any help in this matter would be greatly appreciated!

SM-N910P bootloop after OTA upgrade...

Hello guys!
I've buyed 910P, which was camuflated to 910F (i checked under battery - sticker there says SM-N910F, but in Odin download I see 910P). There was Lineage OS, celluar part works good, but there was some freezes (with camera/gallery), and pulse/UV sensor on back panel of phone isn't work. So after couple of days I've decided to return it to stock firmware - I wanted that sensor, and fast camera.
So. I maded backup with TWRP, found stock FW with 6.0.1 (N910PVPS4DQH1 if I remember correctly), loaded it with Odin - it works, but only english language (not a big problem), and no celluar networks at all. While I was on stock 6.0.1, it pulls update through OTA, and phone was updated. Nothing seems changed after OTA, celluar part don't works, all other good... I've decided to restore backup from my initial Lineage OS - and I don't maked backup of stock FW - I thinked like "I have firmware for Odin, I can re-flash it, if I'll need it...". But this seems to be critical mistake...
I've recovered Lineage OS backup, but phone don't see celluar network, all other was like before. I've tried several custom ROMs - and there was similar picture everywhere - all good, but no network. I decided that this probably caused by "bad" modem, and I just need to load some other modem firmware... I loaded it - and I've found that any custom ROM rebooting after 35-45 seconds from powering phone up. It can be on load animation on that moment, of If I install fresh lineage OS - it can ever show me a desktop - but it WILL vibrate and reboot after some time from powering up. Looks like watchdog...
I've tried to re-load stock ROM - but Odin fails - aboot in my phone has version 5, and in stock rom there is version 4. So I can't go back to stock state, and every ROM that I tried rebooting shortly after powering phone on.
Today I tried to load all parts of that stock rom, just without aboot - I unpacked tar, and maded tar without aboot (I changed system.ext4 with winhex, altered there version from 0004 to 0003 - there was same version mismatch like with aboot) - but it not helps, phone still reboots...
I think, this is because "new" aboot wants "new" modem...
So, I stuck here. Can't go back to stock, can't make phone just work without reboots...
Did somebody tries to load aboot from stock tar with TWRP? I mean copy aboot to SD, go to TWRP->terminal and try something like dd if=/sdcard/aboot.img of=/dev/block/... ?
I tried KIES, but it don't recognize phone - so I can't do "emergency recovery" there...
Did somebody have phone in stock after last OTA update? If yes - can you please share modem image for TWRP?
Sorry for really long post... I just need an advice, because I totally stucked now...

Dmitry_Sysoletin said:
Hello guys!
I've buyed 910P, which was camuflated to 910F (i checked under battery - sticker there says SM-N910F, but in Odin download I see 910P). There was Lineage OS, celluar part works good, but there was some freezes (with camera/gallery), and pulse/UV sensor on back panel of phone isn't work. So after couple of days I've decided to return it to stock firmware - I wanted that sensor, and fast camera.
So. I maded backup with TWRP, found stock FW with 6.0.1 (N910PVPS4DQH1 if I remember correctly), loaded it with Odin - it works, but only english language (not a big problem), and no celluar networks at all. While I was on stock 6.0.1, it pulls update through OTA, and phone was updated. Nothing seems changed after OTA, celluar part don't works, all other good... I've decided to restore backup from my initial Lineage OS - and I don't maked backup of stock FW - I thinked like "I have firmware for Odin, I can re-flash it, if I'll need it...". But this seems to be critical mistake...
I've recovered Lineage OS backup, but phone don't see celluar network, all other was like before. I've tried several custom ROMs - and there was similar picture everywhere - all good, but no network. I decided that this probably caused by "bad" modem, and I just need to load some other modem firmware... I loaded it - and I've found that any custom ROM rebooting after 35-45 seconds from powering phone up. It can be on load animation on that moment, of If I install fresh lineage OS - it can ever show me a desktop - but it WILL vibrate and reboot after some time from powering up. Looks like watchdog...
I've tried to re-load stock ROM - but Odin fails - aboot in my phone has version 5, and in stock rom there is version 4. So I can't go back to stock state, and every ROM that I tried rebooting shortly after powering phone on.
Today I tried to load all parts of that stock rom, just without aboot - I unpacked tar, and maded tar without aboot (I changed system.ext4 with winhex, altered there version from 0004 to 0003 - there was same version mismatch like with aboot) - but it not helps, phone still reboots...
I think, this is because "new" aboot wants "new" modem...
So, I stuck here. Can't go back to stock, can't make phone just work without reboots...
Did somebody tries to load aboot from stock tar with TWRP? I mean copy aboot to SD, go to TWRP->terminal and try something like dd if=/sdcard/aboot.img of=/dev/block/... ?
I tried KIES, but it don't recognize phone - so I can't do "emergency recovery" there...
Did somebody have phone in stock after last OTA update? If yes - can you please share modem image for TWRP?
Sorry for really long post... I just need an advice, because I totally stucked now...
Click to expand...
Click to collapse
Check this post, at the end you'll find link for the latest QI5 build, try to flash your phone by using odin, it may fix it.
https://drive.google.com/open?...d=0B1blPsoKK5taRk5SZ3NwdmUtTzA
Sent from my SM-N910P using Tapatalk

jam97 said:
Check this post, at the end you'll find link for the latest QI5 build, try to flash your phone by using odin, it may fix it.
https://drive.google.com/open?...d=0B1blPsoKK5taRk5SZ3NwdmUtTzA
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Actually, that post is mine too
But thanks anyway!

Sm-N975f back from custom rom ? Or ?

Is there actually a possibility in the meantime. a samsung Note 10+ (SM-N975F EXYNOS) from a custom rom N975FXXS5CTFA_DR.KETAM_Q08 to come back to stock firmeware? or stock firmeware with root? or newer firmware android 11 or what is more powerful dr.ketan is something to performance unstable.
back then had used instructions with magisk manager patched root instructions. no matter how it worked not as described. even in the videos everything made the same but nothing worked. I could almost swear that they had manipulated it on purpose (video) that nux went more, I felt so pissed off. in the end nothing worked on the cell phone. It took me 2 weeks to get it to work

Use Odin to flash original firmware (android 10 for the moment).
Download the latest stock firmware, put the phone in download mode and flash with Odin.
Stock with root is possible, you need Magisk to patch the boot image.
Search on the web "how to..."
Because the knox is tripped you will not receive OTA updates, but you can flash them with Odin.

then i really got the stupidest cell phone of the models. the only thing that can be flashed is the rom that is on it. with stock there are always problems with flashing around the middle. then i have to restart then an error message comes up that everything is broken and i have to do an emergency recovery. of course not possible. then I have to flash again bl first then individually rest except for ap that I come back into the download mode at all

I miss the good Android 5 .0 more and more because I could do everything wrong and the Samsung Note 3 didn't care. even went to reset Knox

Maybe better to ask in the thread related to Dr. Ketan ROM...