Bought an "unlocked" off-contract SGH-i537 that when installing a SIM of an AT&T MVNO, was discovered to be, in fact, still locked. Rather than buying an unlock code, my eager son showed me via Youtube how to use the *#9090# to get into a service menu, and when selecting the first menu option, the phone rebooted and now has a null EMEI and will not recognize any SIMs. The service menus are now blank. The OS is stock 4.4.2 Kitkat. I can't tell you what the modem version was because it now says the baseband module "UNKNOWN."
The phone is as yet unrooted and unhacked in any other way. No personal information is on it, so I can lose all the data. The EMEI is good.
I'm an electrical engineer and embedded firmware developer, so I have some natural curiosity about phone architecture and such. I also downloaded Odin 3.09 from Android Geeks although I haven't tried anything with it yet. I've read similar threads here of those who met their fate using the *#9090# service menu, but all involve earlier versions of the OS, and I got the feeling that I never was able to piece together the full picture of procedures to reflash the modem, and perhaps even the full ROM, although I understand most of the pieces themselves. The stock ROMs and stock modem firmware for 4.4.2 has evaded me as well--the older threads point to 4.2 OS stuff and images.
Other phone forums point to the use of the z3x box to fix this problem. I'm not opposed to purchasing one, and it seems like that and some nearly trashed phones would provide some interesting educational projects. But, more immediately, because this phone is immaculate, I want to get it up and working.
If I can get some quick professional help, I'd be happy to send token remuneration.
Any pointers, lists, or tutorials on how to get this phone back to its original, post-*#9090# state? I'll leave the unlocking to another thread, or just buy a code, once i get to the original state.
dtmguy said:
Bought an "unlocked" off-contract SGH-i537 that when installing a SIM of an AT&T MVNO, was discovered to be, in fact, still locked. Rather than buying an unlock code, my eager son showed me via Youtube how to use the *#9090# to get into a service menu, and when selecting the first menu option, the phone rebooted and now has a null EMEI and will not recognize any SIMs. The service menus are now blank. The OS is stock 4.4.2 Kitkat. I can't tell you what the modem version was because it now says the baseband module "UNKNOWN."
The phone is as yet unrooted and unhacked in any other way. No personal information is on it, so I can lose all the data. The EMEI is good.
I'm an electrical engineer and embedded firmware developer, so I have some natural curiosity about phone architecture and such. I also downloaded Odin 3.09 from Android Geeks although I haven't tried anything with it yet. I've read similar threads here of those who met their fate using the *#9090# service menu, but all involve earlier versions of the OS, and I got the feeling that I never was able to piece together the full picture of procedures to reflash the modem, and perhaps even the full ROM, although I understand most of the pieces themselves. The stock ROMs and stock modem firmware for 4.4.2 has evaded me as well--the older threads point to 4.2 OS stuff and images.
Other phone forums point to the use of the z3x box to fix this problem. I'm not opposed to purchasing one, and it seems like that and some nearly trashed phones would provide some interesting educational projects. But, more immediately, because this phone is immaculate, I want to get it up and working.
If I can get some quick professional help, I'd be happy to send token remuneration.
Any pointers, lists, or tutorials on how to get this phone back to its original, post-*#9090# state? I'll leave the unlocking to another thread, or just buy a code, once i get to the original state.
Click to expand...
Click to collapse
This thread solves your exact problem without wiping your data. Since you said you have a new phone and don't care about the data, I suggest reflashing your stock ROM, it should fix your problem as well.
Good luck.
Devo7v said:
This thread solves your exact problem without wiping your data. Since you said you have a new phone and don't care about the data, I suggest reflashing your stock ROM, it should fix your problem as well.
Good luck.
Click to expand...
Click to collapse
I'll try the stock ROM reflash, but in other threads on this forum and others, it seems like you also need to flash baseband (modem) as well, and that the version of the modem that works depends on the ROM version installed. I've seen all sorts of mention of ML2 and ML1 baseband, but not the baseband for the 4.4.2 kernel family (I don't have the phone in front of me as I write, but I believe it ends in an N-something-9 ). I noticed in the thread you pointed me to that you were making an appeal for one of the later baseband modules. Did anyone ever come up with one in the meantime? In other threads with my exact problem, albeit v4.2 and v4.3, the reflash of the ROM didn't fix the problem, but flash of the modem did. I don't have a problem with doing both, but I just want to understand the process and make sure I have my files in a row and version-matching. My guess is the ROM security is looking for a specific modem checksum and will only work with a checksum that matches what it expects. I'll root this evening to get prepared for the system ROM flas, but finding the correct Baseband would also be appreciated! Thanks!
dtmguy said:
I'll try the stock ROM reflash, but in other threads on this forum and others, it seems like you also need to flash baseband (modem) as well, and that the version of the modem that works depends on the ROM version installed. I've seen all sorts of mention of ML2 and ML1 baseband, but not the baseband for the 4.4.2 kernel family (I don't have the phone in front of me as I write, but I believe it ends in an N-something-9 ). I noticed in the thread you pointed me to that you were making an appeal for one of the later baseband modules. Did anyone ever come up with one in the meantime? In other threads with my exact problem, albeit v4.2 and v4.3, the reflash of the ROM didn't fix the problem, but flash of the modem did. I don't have a problem with doing both, but I just want to understand the process and make sure I have my files in a row and version-matching. My guess is the ROM security is looking for a specific modem checksum and will only work with a checksum that matches what it expects. I'll root this evening to get prepared for the system ROM flas, but finding the correct Baseband would also be appreciated! Thanks!
Click to expand...
Click to collapse
The first thread I linked to has modems that work with any version on the i537.
I'm not positive, but I'm almost certain that all the i537 firmware packages will reflash your modem. If not, I have most of them extracted so that they can be flashed independently of the ROM. I just need some free time at work to get a proper thread put together.
EDIT: I also just wanted to thank you for doing some research before posting. A lot of people will just post on here asking for a step by step without even searching. It's nice to be able to help somebody who's interested learning.
Devo7v said:
The first thread I linked to has modems that work with any version on the i537.
I'm not positive, but I'm almost certain that all the i537 firmware packages will reflash your modem. If not, I have most of them extracted so that they can be flashed independently of the ROM. I just need some free time at work to get a proper thread put together.
EDIT: I also just wanted to thank you for doing some research before posting. A lot of people will just post on here asking for a step by step without even searching. It's nice to be able to help somebody who's interested learning.
Click to expand...
Click to collapse
I am very interested in learning the architecture and ins and outs of the phone and Android for that matter, and toolkits. My current firmware is KOT49h.i537UCUCNE3. Can't tell about Baseband as the phone now says UNKNOWN. I've downloaded the full ROM from your previous linked threads, and extracted the files within. I'm busy reading all the instructions for Odin and the like, so I understand how to use it and the steps to put my phone in the correct mode and permissions (rooting?) for downloading. I just became an Androider three days ago, so it will take some time to catch up on basics and terminology that most of you know already. As you might guess, putting this all together from thread snippets can be a but confusing for the uninitiated.
Thanks!
dtmguy said:
I am very interested in learning the architecture and ins and outs of the phone and Android for that matter, and toolkits. My current firmware is KOT49h.i537UCUCNE3. Can't tell about Baseband as the phone now says UNKNOWN. I've downloaded the full ROM from your previous linked threads, and extracted the files within. I'm busy reading all the instructions for Odin and the like, so I understand how to use it and the steps to put my phone in the correct mode and permissions (rooting?) for downloading. I just became an Androider three days ago, so it will take some time to catch up on basics and terminology that most of you know already. As you might guess, putting this all together from thread snippets can be a but confusing for the uninitiated.
Thanks!
Click to expand...
Click to collapse
You're doing fine. Just make sure you read about Odin and watch a couple videos because flashing files is one of the few ways you can permanently brick your phone if you do something wrong. Just make sure you understand what you're doing and you'll be fine.
I know it can be confusing, that's why I put the guides together, to make everything as clear as possible since there a lot of information scattered all over site. Just read, read, and read some more and you'll find all the answers you're looking for.
Devo7v said:
You're doing fine. Just make sure you read about Odin and watch a couple videos because flashing files is one of the few ways you can permanently brick your phone if you do something wrong. Just make sure you understand what you're doing and you'll be fine.
I know it can be confusing, that's why I put the guides together, to make everything as clear as possible since there a lot of information scattered all over site. Just read, read, and read some more and you'll find all the answers you're looking for.
Click to expand...
Click to collapse
I'm very curious what the *#9090# command does to soft brick the phone. Did AT&T poison this menu because it was used by consumers to unlock their phones? Someone has to have hacked all the dial code options at some point and reverse assembled the code...
I'll read some more and give stuff a try. The videos out there are somewhat confusing for the uninitiated, as many have poor quality screen grabs, go too fast, don't explain what they're doing and why, and videographers who assume the watcher knows more than they might in terms of terminology and the like. I've done linux and Unix development, but there are unique terms to the phone industry that sometimes need clear definition.
Devo7v said:
You're doing fine. Just make sure you read about Odin and watch a couple videos because flashing files is one of the few ways you can permanently brick your phone if you do something wrong. Just make sure you understand what you're doing and you'll be fine.
I know it can be confusing, that's why I put the guides together, to make everything as clear as possible since there a lot of information scattered all over site. Just read, read, and read some more and you'll find all the answers you're looking for.
Click to expand...
Click to collapse
One additional question: The firmware download link you gave me has 4 files in it when unzipped:
AP_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5
BL_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5
CP_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5
CSC_ATT_I537ATTCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5
I assume the "AP" file is the main ROM, as it is nearly 2 gig and the rest of the files are 50 meg or smaller, but can you give me some insight what the purpose of the remainder of the files are? I've watched several Odin tutorials and am getting ready to give it a try. I don't understand what the remaining 3 files are for. I figure, by the way, that I'll stick with NE3, which is what is in the phone at the moment, as it appears this is the last version that is rootable at this point, correct?
Thanks for your help. If this works for me, I may do a vid specificallly aimed at people with *#9090# bricks like mine is. I know I'm not the only one!
dtmguy said:
One additional question: The firmware download link you gave me has 4 files in it when unzipped:
AP_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5
BL_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5
CP_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5
CSC_ATT_I537ATTCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5
I assume the "AP" file is the main ROM, as it is nearly 2 gig and the rest of the files are 50 meg or smaller, but can you give me some insight what the purpose of the remainder of the files are? I've watched several Odin tutorials and am getting ready to give it a try. I don't understand what the remaining 3 files are for. I figure, by the way, that I'll stick with NE3, which is what is in the phone at the moment, as it appears this is the last version that is rootable at this point, correct?
Thanks for your help. If this works for me, I may do a vid specificallly aimed at people with *#9090# bricks like mine is. I know I'm not the only one!
Click to expand...
Click to collapse
Absolutely, again, thanks for doing a little research first. If you're really curious about exactly what files are in there you can open them with 7-zip and browse around.
AP - this contains most of the OS files, kernel, and firmware. Most importantly it contains the phone's recovery. The recovery makes it possible to flash files directly on the phone and loads up just after the bootloader and TrustZone. The nearest thing I can equate the recovery menu to would be a computer's bios menu.
BL - this is you bootloader. Generally this is required for everything to work properly. With the i537, AT&T has made it impossible to downgrade to a pervious version of the bootloader. It also contains some SELinux stuff in there that is over my head, but the way I understand it these files all you to encrypt you phone. If Odin fails when flashing this file you will most likely end up with a permanently bricked phone.
CP - this contains you modem and LTE modem files. Similar to a computer, without a modem you will not have any communication. This includes 2G/3G/4G, LTE, WiFi, Bluetooth, and GPS.
CSC - these are country specific files. This basically tells your modem how to communicate with your network, in this case it is AT&T/T-Mobile. For this firmware it will have the AT&T APN settings, if you need T-Mobile you'll have to enter them manually. IMPORTANT: it also contains a .pit file which is the partition file. If Odin fails while flashing the .pit file you could brick your phone, but it is still possible to recover it.
You don't have to flash these files all at once, you can flash them individually or mix and match them with files from other versions of the firmware. If you mix and match odds are you will end up with bugs, so it's not recommended unless you know what you're doing. If you are just restoring your NE3 firmware, just flash all the files and you'll be back to the way you started.
I hope this helps, and let me know if you have any other questions.
Devo7v said:
Absolutely, again, thanks for doing a little research first. If you're really curious about exactly what files are in there you can open them with 7-zip and browse around.
AP - this contains most of the OS files, kernel, and firmware. Most importantly it contains the phone's recovery. The recovery makes it possible to flash files directly on the phone and loads up just after the bootloader and TrustZone. The nearest thing I can equate the recovery menu to would be a computer's bios menu.
BL - this is you bootloader. Generally this is required for everything to work properly. With the i537, AT&T has made it impossible to downgrade to a pervious version of the bootloader. It also contains some SELinux stuff in there that is over my head, but the way I understand it these files all you to encrypt you phone. If Odin fails when flashing this file you will most likely end up with a permanently bricked phone.
CP - this contains you modem and LTE modem files. Similar to a computer, without a modem you will not have any communication. This includes 2G/3G/4G, LTE, WiFi, Bluetooth, and GPS.
CSC - these are country specific files. This basically tells your modem how to communicate with your network, in this case it is AT&T/T-Mobile. For this firmware it will have the AT&T APN settings, if you need T-Mobile you'll have to enter them manually. IMPORTANT: it also contains a .pit file which is the partition file. If Odin fails while flashing the .pit file you could brick your phone, but it is still possible to recover it.
You don't have to flash these files all at once, you can flash them individually or mix and match them with files from other versions of the firmware. If you mix and match odds are you will end up with bugs, so it's not recommended unless you know what you're doing. If you are just restoring your NE3 firmware, just flash all the files and you'll be back to the way you started.
I hope this helps, and let me know if you have any other questions.
Click to expand...
Click to collapse
Thanks--I'm a bit embarrassed that I found, after following 3 links this morning, your instructions for an NE3 to NE3 load via Odin. I just logged in to say "I got it!" and you'd just posted this... I'll try flashing tonight, and see if it restores the EMEI and baseband that was lost when I went to the *#9090# menu. I appreciated an explanation of the files by themselves, though, rather than just Odin loading instructions. I've got stock NE3 on the phone now, so I could just try the modem alone (which I assume is referred to as "baseband" in the phone), but I've got no personal data on the phone, so it doesn't hurt me to start from scratch. From reading other forums, some people in my situation have been brought back up by a full flash or a modem flash, and several others needed to use an x3d or Octopus box to recover via a baseband repair to complete repair.
Devo7v said:
Absolutely, again, thanks for doing a little research first. If you're really curious about exactly what files are in there you can open them with 7-zip and browse around.
AP - this contains most of the OS files, kernel, and firmware. Most importantly it contains the phone's recovery. The recovery makes it possible to flash files directly on the phone and loads up just after the bootloader and TrustZone. The nearest thing I can equate the recovery menu to would be a computer's bios menu.
BL - this is you bootloader. Generally this is required for everything to work properly. With the i537, AT&T has made it impossible to downgrade to a pervious version of the bootloader. It also contains some SELinux stuff in there that is over my head, but the way I understand it these files all you to encrypt you phone. If Odin fails when flashing this file you will most likely end up with a permanently bricked phone.
CP - this contains you modem and LTE modem files. Similar to a computer, without a modem you will not have any communication. This includes 2G/3G/4G, LTE, WiFi, Bluetooth, and GPS.
CSC - these are country specific files. This basically tells your modem how to communicate with your network, in this case it is AT&T/T-Mobile. For this firmware it will have the AT&T APN settings, if you need T-Mobile you'll have to enter them manually. IMPORTANT: it also contains a .pit file which is the partition file. If Odin fails while flashing the .pit file you could brick your phone, but it is still possible to recover it.
You don't have to flash these files all at once, you can flash them individually or mix and match them with files from other versions of the firmware. If you mix and match odds are you will end up with bugs, so it's not recommended unless you know what you're doing. If you are just restoring your NE3 firmware, just flash all the files and you'll be back to the way you started.
I hope this helps, and let me know if you have any other questions.
Click to expand...
Click to collapse
Well, the ODIN flash went just fine--flashed all the files with a success status. I was chagrined to find, however, that the phone still reports Baseband "Version Unknown" which is indicative of the *#9090# corruption problem. The IMEI is still NULL/NULL and the Service Menu is still blank. It won't find any SIM. My WiFi does work--don't know about GPS as I haven't tried that.
Any ideas? I've heard the advice to flash a couple of times, but in the threads I've followed on different forums, that doesn't work. It is weird that some people can flash the modem alone and things go back to being fine. but any examples of that are with older modem code (ML1 or ML2). I saw the modem.bin for this ROM getting flashed by Odin, so modem flashing did happen. Just no luck. I wish I could find a resource who'd hacked the phone to the point they could identify what was corrupted during the *#9090# adventure, or what that corrupt menu modified so it could be restored. I know operators of the z3x "box" have reported doing a baseband repair and that fixes the problem. I wish I knew someone who had one of these gadgets, as I may need to plunk $160 to get one if I take that route, and I'm unlikely to use it a lot afterwards.
dtmguy said:
Well, the ODIN flash went just fine--flashed all the files with a success status. I was chagrined to find, however, that the phone still reports Baseband "Version Unknown" which is indicative of the *#9090# corruption problem. The IMEI is still NULL/NULL and the Service Menu is still blank. It won't find any SIM. My WiFi does work--don't know about GPS as I haven't tried that.
Any ideas? I've heard the advice to flash a couple of times, but in the threads I've followed on different forums, that doesn't work. It is weird that some people can flash the modem alone and things go back to being fine. but any examples of that are with older modem code (ML1 or ML2). I saw the modem.bin for this ROM getting flashed by Odin, so modem flashing did happen. Just no luck. I wish I could find a resource who'd hacked the phone to the point they could identify what was corrupted during the *#9090# adventure, or what that corrupt menu modified so it could be restored. I know operators of the z3x "box" have reported doing a baseband repair and that fixes the problem. I wish I knew someone who had one of these gadgets, as I may need to plunk $160 to get one if I take that route, and I'm unlikely to use it a lot afterwards.
Click to expand...
Click to collapse
Have you tried flashing the modems that I sent you in the very first link? Many people have had success using that method.
Devo7v said:
Have you tried flashing the modems that I sent you in the very first link? Many people have had success using that method.
Click to expand...
Click to collapse
I will try that this evening. From reading many other forums, it appears at this time that somehow the *#9090# menu corrupts the /efs file for the phone, which I'm just learning from what little documentation there is on this file. The /efs is supposedly not touched through ROM update. I plan to back it up (what remains of it), then move on with trying older modem flashing and also an online-based /efs repair. I did order a z3x box just for grins, so have the option of a baseband repair attempt, which has worked for others. That's not to say I'm not taking all your advice as well. With the z3x, I also have the option of unlocking my and others' phones which I find attractive.
While I'm in for magic solutions, I'm also in this for the knowledge gained.
Thanks!
Devo7v said:
Have you tried flashing the modems that I sent you in the very first link? Many people have had success using that method.
Click to expand...
Click to collapse
Well, so far I've tried all the suggestions here, and gained more insight in other forums but which do not come with any solution (but may explain the problem). I've tried numerous tools (SA Manager, EFS Professional, and a few online services that purport to perform baseband repair) all to no luck. Some threads say my problem lies in a corrupted /efs folder, while some say it is an NV corruption. Still others say that the *#9090# menu may have locked the phone in field debug mode although how to reverse this situation is not known, and the command menu that is supposed to turn the feature off is blank, so if this is the true problem, I can't turn field debug off. ARRGH!
The problem occurred the minute I tried the first option of *#9090# to unlock. I didn't rebuild nv or anything. Just chose the first menu option which was supposed to bring me to the UMTS configuration menu but instead rebooted the phone to Baseband Unknown.
Clearly flashing the stock ROM doesn't do the deed. Nor does flashing older modem code.
What I haven't tried is backing up my /efs and then gratuitously reinstalling via EFS Professional or Odin.
I feel like I'm a newbie in a room full of blindfolded people trying to describe an elephant to each other by feeling it.
Devo7v said:
Have you tried flashing the modems that I sent you in the very first link? Many people have had success using that method.
Click to expand...
Click to collapse
Halle-gol-dang-lujah!
I was trying a bunch of different Odin versions and modem versions, and viola, MF1 modem code and Odin 3.09 appeared to do the trick. I see baseband again! Now, to see if I can flash back NE3 in its entirety and have things work properly! Then, to back up my NV and /efs using EFS professional ASAP... I think I'm going to puke... I still wish I understood what the mechanism behind this whole fiasco was. I'll post a couple more times on the thread if new info comes along, in the interest of helping others in my same situation.
Devo7v said:
This thread solves your exact problem without wiping your data. Since you said you have a new phone and don't care about the data, I suggest reflashing your stock ROM, it should fix your problem as well.
Good luck.
Click to expand...
Click to collapse
Here's the latest update. I started with NE3 as my main SW and everything was working when I encountered the *#9090# menu debacle. If I flash MF1 modem, everything works again--EMEI is back, the service menu is back, etc. If I then try flashing the whole NE3 stock ROM on top of that, the baseband goes back to UNKNOWN and the EMEI back to null. I wish someone would explain how that works to me and the underlying problem. Although the phone is working, I'd sure like to get the modem up to the same baseband version that was intended to go with the whole ROM.
Did you say that you'd isolated the modem.bin from NE3? Is that wrapped up in one of the tarballs? I'd like to try just flashing this file back and forth to see if modem.bin alone will keep from exciting whatever the problem is. I wish I had more time to deduce what files were being affected so I could advise others on a 100 percent solution that cured the issue at its root.
dtmguy said:
Here's the latest update. I started with NE3 as my main SW and everything was working when I encountered the *#9090# menu debacle. If I flash MF1 modem, everything works again--EMEI is back, the service menu is back, etc. If I then try flashing the whole NE3 stock ROM on top of that, the baseband goes back to UNKNOWN and the EMEI back to null. I wish someone would explain how that works to me and the underlying problem. Although the phone is working, I'd sure like to get the modem up to the same baseband version that was intended to go with the whole ROM.
Did you say that you'd isolated the modem.bin from NE3? Is that wrapped up in one of the tarballs? I'd like to try just flashing this file back and forth to see if modem.bin alone will keep from exciting whatever the problem is. I wish I had more time to deduce what files were being affected so I could advise others on a 100 percent solution that cured the issue at its root.
Click to expand...
Click to collapse
Like I said, the first link I posted works like magic. If you want to know subtle how it works I would PM the OP.
I do have the NE3 Odin files, but so do you. They are in the CP file and you can extract them using 7-zip. One extracted you need to flash both modem.bin and NON-HLOS.bin twice through Odin without restarting the phone. I would try NON-HLOS.bin first since that is your 4G/LTE modem and may work without changing your baseband.
If you do find out how/why the MF1 modem works, please post back here, I'm interested to know.
Devo7v said:
Like I said, the first link I posted works like magic. If you want to know subtle how it works I would PM the OP.
I do have the NE3 Odin files, but so do you. They are in the CP file and you can extract them using 7-zip. One extracted you need to flash both modem.bin and NON-HLOS.bin twice through Odin without restarting the phone. I would try NON-HLOS.bin first since that is your 4G/LTE modem and may work without changing your baseband.
If you do find out how/why the MF1 modem works, please post back here, I'm interested to know.
Click to expand...
Click to collapse
Problem now considered completely solved. This is what happened, and what I had to do, in case it is of use for other people in the same situation, who followed the Youtube video for unlocking using the *#9090# service menu. I'm running the NE3 stock ROM, BTW.
When you follow the video, the author goes into the *#9090# menu, and instructs people to take the top choice to get into the UMTS Service Menu. This top choice is named "DM/DUN over HS-USB[]". Selecting it will make it the default, marked by an asterisk thereafter, reboot your phone, and your baseband will be gone from what appears to be an interruption in the communications path between the main processor and the modem. This setup you changed will NOT go away with reflashing the stock ROM or the modem.bin that matches your stock ROM version. And, until you can get the *#9090# menu back, you can't correct the setting! However, you can flash the MF1 (old) modem, and this will bring Baseband and the *#9090# service menu back. When you get that back, go back into the *#9090# menu and select the SECOND choice from the top named "DM/DUN over HSIC", which was the old default. The phone will now reboot. You can now flash either the current modem.bin, or reflash your stock ROM and everything will work again.
I'm not really sure what the communication selections do that are changed in the *#9090# menu, but I surmise they are for debug only, and anything else poisons the Baseband module in newer modem code. Anyhow, the steps above worked for me to completely recover the problem, and I hope they help others in a panic.
dtmguy said:
Here's the latest update. I started with NE3 as my main SW and everything was working when I encountered the *#9090# menu debacle. If I flash MF1 modem, everything works again--EMEI is back, the service menu is back, etc. If I then try flashing the whole NE3 stock ROM on top of that, the baseband goes back to UNKNOWN and the EMEI back to null. I wish someone would explain how that works to me and the underlying problem. Although the phone is working, I'd sure like to get the modem up to the same baseband version that was intended to go with the whole ROM.
Did you say that you'd isolated the modem.bin from NE3? Is that wrapped up in one of the tarballs? I'd like to try just flashing this file back and forth to see if modem.bin alone will keep from exciting whatever the problem is. I wish I had more time to deduce what files were being affected so I could advise others on a 100 percent solution that cured the issue at its root.
Click to expand...
Click to collapse
hi! ive been reading this thread and followed all the instruction but sad to say nothing works for my samsung active, we have same problem baseband is unknown and imei is unknown, and i have the exact version of firmware that u have... any suggestion pls. i have been researching and working on it for about 3 months already, but i have no luck... need help badly
toffermaramba said:
hi! ive been reading this thread and followed all the instruction but sad to say nothing works for my samsung active, we have same problem baseband is unknown and imei is unknown, and i have the exact version of firmware that u have... any suggestion pls. i have been researching and working on it for about 3 months already, but i have no luck... need help badly
Click to expand...
Click to collapse
I'm a newbie here, so I will help where I can. How did your phone get into the situation of baseband and IMEI unknown, or what happened to put it there? Did you try the *#9090# to unlock your phone like I did, then choosing the first menu option? Did you do anything else to try to solve the problem other than what I did? Do you have Odin downloaded? What version of Odin? What version of ROM do you have downloaded? What version of the modem firmware do you have? Can you go through the steps, in detail, that you followed so far? Detail at this point helps. As I said, I am rather new to the board, but will try to pass along what I did to regain my phone, which I'm using since, with no problems.
Related
Hi, everybody. I have a big problem with my Captivate I897. I bought it on ebay and it appears to be bricked. Just AT&T logo loop.
I have tried a lot of stuf - flashing with odin one click, installing different roms with odin, removing all data in recovery mode. Nothing helps.
Messages that have experienced:
After flashing to stock with odin-one-click: Data wipe failed
After installing custom rom (I897UCJI6-OCD-REV02-Low-designgears_1_.exe): Can't mount SDCARD: copy default media content failed
Removing data in recovery mode completes without errors but nothing changes.
This phone is locked to AT&T, maybe this is the trouble.
I can go to Download mode and recovery mode.
Maybe something wrong with internal sd card. Maybe i can do some hard format or something like that.
Could anybody help?
Thanks
Guys, anybody? i'll appreciate any hints. Please.
I would suggest trying to flash to stock with a non-One-Click Odin version. It's possible that the One-click version doesn't have the right instruction set to get around whatever is causing the issue on the phone (or maybe it just doesn't like the phone).
You could also try this Heimdall-based One-Click to get back to stock. It's possible that ODIN might be incompatible with your current setup.
If that still doesn't work, and you're not averse to trying your hand at soldering, you could give the Unbrickable Mod a try and see if you can go from there.
If you have any questions along the way, just post back here.
I would try flashing I897UCJF6_final_OCD_REV0.zip . That one works great for me every time and it is a one click. You'll find it in DG's stock rom thread in the development section.
I've helped a few people out with their Cappy's and I've noticed that some of the newer ones (model number 1010 and above) don't take too kindly to stock 2.1. You might want to check that. It's written behind the battery.
Have you tried i897UCKB1 (2.2) or maybe even i897UCKH3 (2.3.4)?
Thank all of you for advice. I will try out all that you advised me to.
I found model number it is 1007.
Cheers.
Hi I found a similar article on androidforums.com so I thought id make one here as a lot of people still seem to not know how to flash basebands and go from there. Ill start from the beginning.
For those who don't understand what this is about.
Old Baseband = If you have the Stock Froyo (2.2) Android system on your phone then you have the OLD BASEBAND, and you do not need this unless you updated to past 2.2.2 then continue reading if you wish to root your phone the easy way.
New Baseband = If you updated to the Stock Gingerbread (2.3) Android System on your Optimus One, then you fit this category, Lg have implemented a new baseband in this update which makes any Roms based on the old baseband not function, as well as making it more difficult to root your phone
FLASHING OLD BASEBAND
If you're already on official Gingerbread version you will need to downgrade your version to Froyo 2.2.2 using KDZ Updater. This is because the new Gingerbread contains the new baseband, and the Froyo firmware is the old baseband.
To do this please go onto this link that contains kdz and the stock Froyo 2.2.2 Rom required to flash. The reason you need 2.2.2 is its the easiest and proven version to work with Gingerbreak to root your device.
http://forum.xda-developers.com/showpost.php?p=13396506&postcount=1
Notice: If by some ACCIDENTAL reason, your phone gets stuck in EMERGENCY MODE during flashing, follow the instructions on this link how to use KDZs functions to continue flashing the firmware you downloaded in Emergency mode.
http://forum.xda-developers.com/showthread.php?t=1275523
FLASHING NEW BASEBAND
The Kdz File for new baseband is below, use the same method as above only using the v20G .kdz file instead of the 2.2.2 v10E update.
This will update your phone to the official LG 2.3 firmware, in which the new baseband originated.
csmg.lgmobile.com:9002/swdata/WEBSW/LGP500/ANEUBK/V20g_00/V20G_00.kdz
If then stuck on LG Logo OR boot animation, try pulling and putting in your battery, turning on your phone and holding down volume down and home key, this should reset your phone to factory and then you will be able to boot into the stock gingerbread.
ROOTING
The easiest way to get root privileges on Old Baseband (2.2.2) firmware device is by using Gingerbreak apk. Just download it, install it and run it.
forum.xda-developers.com/attachment.php?attachmentid=600902&d=1305802958
To get Root access on the New Baseband (2.3.3) use SuperOneClick
http://forum.xda-developers.com/showthread.php?t=803682
Or direct link to the latest version
forum.xda-developers.com/attachment.php?attachmentid=778098&d=1320906597
Make sure, after you download the program, you go into your cmd, then go into the ADB folder, drag the ABD exe file into command prompt, delete the .exe part and add devices, so it look like this
OR
Download the ADB.zip attachment on this post, EXTRACT it so cmdXP and cmd7 are located inside the ADB folder in the Superoneclick directory, and run either version, depending on your windows version (This links you directly into ADB app, instead of manually dragging ADB.exe int cmd, really its just for your convinience.)
Then all you have to do is type the following lines.
adb devices
press enter
adb shell
press enter
then type in the following directly after
echo 1 > /data/local/lge_adb.conf
press enter.
Then go into Superoneclick.exe, select auto method and run root, this should then eventually root your device.
***WARNING***
Some Antivirus softwares will detect Superoneclick as a Virus.
IT IS NOT A VIRUS, just the types of exploite code it uses makes some antivirus software think of it as malicious. Just disable your AV for 5 mins before you extract Superoneclick.
RECOVERY
There's two popular custom Recovery versions for O1 - AmonRa and ClockworkMod
The easiest way to flash ClockworkMod Recovery is by downloading ROM Manager app from the Market (free or donate version doesn't matter) and choose to flash the latest recovery version and choose the option to Reboot in Recovery mode.
For Other Recoveries including Amonra there are a few links, but here is the one that has flashable zips
http://forum.xda-developers.com/showthread.php?t=1523050
Just flash the zip files in Clockworkmod recovery menu, after you install that through Rom Manager if you wish to use a different recovery.
Now that you got the right baseband + your device is rooted and loaded with a custom recovery you may install any Rom you wish that is based on the correct baseband such as
Mik_os 6.5.8 Cyanogenmod port (OLD BASEBAND).
http://forum.xda-developers.com/showthread.php?t=946354
[UNOFFICIAL][DEV/GEEKS-ONLY] Cyanogenmod 9 (Android 4.0.3)[BETA][NEW BASEBAND]
http://forum.xda-developers.com/showthread.php?t=1558213
OFFICIAL CYANOGENMOD Rom [NEW BASEBAND]
http://get.cm/?device=p500
Oxygen ROM 2.3.2 (Android 2.3.7)[NEW BASEBAND]
http://forum.xda-developers.com/showthread.php?t=1325386
Next time, search better
Also posted in wrong thread, this is developmentthread...
Don't know how many guides still to come on downgrading baseband.....
People...do search before making a new guide......
MODERATOR...plz look into this thread...
Sent from my LG-P500 using xda premium
fundoozzz said:
Don't know how many guides still to come on downgrading baseband.....
People...do search before making a new guide......
MODERATOR...plz look into this thread...
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Guys i did a search and looked into the sticky how to, and the only thing about downgrading baseband is using LGMDP, and kdz is only "mentioned" as a tool for unbricking your phone and flashing old firmware, new users would not know to use kdz.
Also this is a universal guide to root ANY lg optimus one together with having the old baseband, without having to mess around with SDK or LGMDP.
All members have to do now is look at this thread and all their questions are answered hopefully...
DIfference betweem this and doks.
This uses Official Lg KDZ updater, which means much less likely to brick your phone and if it does, KDZ is what is used to unbrick it anyway,
This option is much simpler to use for anyone.
I hear a lot about the new baseband making ROMs incompatible, but is there any advantage to the new baseband?
its not that they are making roms incompatiable, its that they are not designed for those Roms,
So far there has been no reports of any advantage having a new baseband, Lg engineers obviously decided on it for some reason, but the old baseband is more than fine, and in fact i have read several reports that with the new baseband gsm reception got worse in areas that they used to have fine reception, but thats all speculation.
Your best bet is to try for yourself, but if you want to make use of Roms such as miks cyanogen mod or others you have to use the old baseband.
There are other Roms available on the new baseband, so its upto you.
I suggest what rom you would like to install on your phone first, then pick the baseband it requires, as its only a simple flashing of your firmware.
Also note Gingerbreak.apk doesnt root any stock firmware past the 2.2.2 update.
Personally i pick the functionality and advantage of having a custom rom such as cyanogenmod over an update to the baseband
Does this guide work for Optimus T (LG P509) ? I have got one recently and currently using stock 2.2 on it. I don't know the difference between LG p500 and LG P509. I'm coming from T-Mobile G1 on which I'm using CM 7.1. Thanks for guidance.
Sent from my Dream/Sapphire using xda premium
Hi,
Doing a little search i found this thread
http://forum.xda-developers.com/showthread.php?t=960278
looking at it, i assume you can use this guide for p509, but i can not be 100% sure, try finding the t-mobile 2.2 kdz file, but yes not 100% sure the main difference.
deniso177 said:
DIfference betweem this and doks.
This uses Official Lg KDZ updater, which means much less likely to brick your phone and if it does, KDZ is what is used to unbrick it anyway,
This option is much simpler to use for anyone.
Click to expand...
Click to collapse
KDZ can brick your phone permanently. Dont use KDZ unless there is no other option, and using KDZ just to flash baseband is just dumb since there are better and safer methods. KDZ wipes out everything, so there is a high chance to brick, and it can't be fixed other than by going to the service center. This thread by doktornoktor is safer.
http://forum.xda-developers.com/showthread.php?t=1149530
Thanks anyway for sharing.
Gremaldin said:
KDZ can brick your phone permanently. Dont use KDZ unless there is no other option, and using KDZ just to flash baseband is just dumb since there are better and safer methods. KDZ wipes out everything, so there is a high chance to brick, and it can't be fixed other than by going to the service center. This thread by doktornoktor is safer.
http://forum.xda-developers.com/showthread.php?t=1149530
Thanks anyway for sharing.
Click to expand...
Click to collapse
I think KDZ is quite a safe method, rather than the LGMDP incorrectly backing up your NV2 and losing IMEI etc
Gremaldin said:
KDZ can brick your phone permanently. Dont use KDZ unless there is no other option, and using KDZ just to flash baseband is just dumb since there are better and safer methods. KDZ wipes out everything, so there is a high chance to brick, and it can't be fixed other than by going to the service center. This thread by doktornoktor is safer.
http://forum.xda-developers.com/showthread.php?t=1149530
Thanks anyway for sharing.
Click to expand...
Click to collapse
As you already quoted it, i said that this method is different from Doks.
As for wiping all data completely, so its all brand new and neat, then try to fiddle around with internals and possibly have a bug result from it.
KDZ is what is used to UNBRICK your phone in the first place, so go do some research before posting unnecessary things.
Lastly how about you show some respect and keep your negative and rude comments to yourself, if you dont like this method dont do it, dont abuse people in the process.
terratrix said:
I think KDZ is quite a safe method, rather than the LGMDP incorrectly backing up your NV2 and losing IMEI etc
Click to expand...
Click to collapse
And yep exactly, i personally prefer completely reinstalling something to make it work properly, then doing things dodgy.
tried using gingerbreak to root my device but stuck in rooting and exploit ph0ne does not reboot..
Sent from my LG-P500 using xda premium
ichigo200 said:
tried using gingerbreak to root my device but stuck in rooting and exploit ph0ne does not reboot..
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
it means your phone is past the firmware update that gingerbreak works on,
as it says in the first post, use kdz and the file in the link to flash your phone to that firmware, and then gingerbreak will work
You guys will only learn when you finally end up with a bricked phone. It has happened to several people, including me. I am not a noob, I have used KDZ before and I know very well how to use it. Most of the time, everything goes smoothly. But even if we follow all instructions to the letter, there is a chance of KDZ bricking our phone for good.
http://androidforums.com/lg-optimus...read-2-3-3-official-firmware.html#post3328455
A warning to anyone tempted to do this. Like the original poster, I also have an LG Optimus T. I am technically savvy (15 years IT experience) and I followed the directions to the letter, but the end result is a bricked, unrecoverable phone. Had I known the risks involved, I would have been perfectly content with Froyo and waited for the official upgrade to arrive.
Here is how mine failed: during the kdz update process, while the phone was on the "Emergency Mode" screen, the kdz updater program threw an exception and crashed. This caused the phone to be permanently locked in emergency mode. The buttons are unresponsive and the only way to turn it off is to remove the battery. With the battery in, it immediately goes to the emergency screen. No combination of button presses (eg, hard reset) does anything. The computer will still see the devices but only if I remove the battery and start the phone up by inserting the USB cable.
I have tried every method for recovery I could find including the following. In each case, I tried it with the modem device listed in device manager both disabled and enabled, as instructed in other recovery threads I found.
Flashing the original .kdz ROM in emergency and cs_emergency modes. When I did, it failed with an exception 4008.
Flashing the original .dz ROM with all of the tools I could find. LGMDP and LGDP2 could see the phone's COM port but beyond that, they could not communicate with the phone in any way. I couldn't even retrieve the IMEI number.
Updating the phone with the LG update software. It actually detects that the phone needs an update and starts to do one but it fails at the point where it tries to communicate with the phone.
Based on other posts I found for the same problem, I believe the phone is completely unrecoverable. I spent over six hours trying to solve the problem and I'm kicking myself for even trying this. I have put in a repair claim with LG and I'm waiting for instructions on how to proceed.
I would not recommend you try this unless you are not worried about destroying your phone. I imagine most installs go without a hitch but if the buggy kdz updater software crashes like it did for me, your phone will likely be bricked permanently.
Click to expand...
Click to collapse
http://androidforums.com/optimus-on...y-boots-stuck-emergency-mode.html#post3301128
In short, don't mess with KDZ unless you really have to.
Click to expand...
Click to collapse
IF you still think KDZ is safe, then go ahead, use it. I don't care if you end up with a bricked phone.
EDIT: The guys at the service center favour LGMPD over KDZ too
Gremaldin said:
You guys will only learn when you finally end up with a bricked phone. It has happened to several people, including me. I am not a noob, I have used KDZ before and I know very well how to use it. Most of the time, everything goes smoothly. But even if we follow all instructions to the letter, there is a chance of KDZ bricking our phone for good.
http://androidforums.com/lg-optimus...read-2-3-3-official-firmware.html#post3328455
http://androidforums.com/optimus-on...y-boots-stuck-emergency-mode.html#post3301128
IF you still think KDZ is safe, then go ahead, use it. I don't care if you end up with a bricked phone.
EDIT: The guys at the service center favour LGMPD over KDZ too
Click to expand...
Click to collapse
I have used KDZ more than 2 dozen times -.- Just used it again this morning. I never ended up with a bricked phone mind you. They favour LGMPD since it's more updated, while KDZ is a little old but still very good.
There is a fairly equal share of bricked phones using LGDMPD, eventhough they got it back by using other people's NV2, they need to hope they are lucky to escape the long arm of the law.
Gremaldin said:
You guys will only learn when you finally end up with a bricked phone. It has happened to several people, including me. I am not a noob, I have used KDZ before and I know very well how to use it. Most of the time, everything goes smoothly. But even if we follow all instructions to the letter, there is a chance of KDZ bricking our phone for good.
http://androidforums.com/lg-optimus...read-2-3-3-official-firmware.html#post3328455
http://androidforums.com/optimus-on...y-boots-stuck-emergency-mode.html#post3301128
IF you still think KDZ is safe, then go ahead, use it. I don't care if you end up with a bricked phone.
EDIT: The guys at the service center favour LGMPD over KDZ too
Click to expand...
Click to collapse
Mate your the one who clearly doesnt get it.
And i read your post on androidforums, you even managed to brick your phone installing custom recovery, clearly your phone software is buggy, not kdz, kdz is capable of recovering while in emergency mode as well, but of course there are freak accidents.
EVERYTHING has a WARNING.
Every single Rom, Kernel, Recovery also carry a chance of bricking your phone.
I have used Kdz dozens of times and never had a problem with it, in fact, its what solved my problems in the first place.
And exactly wat terra said, the way LGDMPD works can also cause bricked phoes or taking shortcuts to make things half work.
You have to know what your doing, and follow instructions TO THE WORD, and you should be fine, if your going to skim read then you brick your phone doing the simplest of tasks (such as repeatedly flashing zips without reloading recovery...)
I will always prefer kdz as thats what the firmware comes with originally + i prefer doing clean installs any day.
Please Help...
Guys please help me. everything was running fine until I decided to switch to stock 2.3.3. I was unaware with this baseband thing. I switched to stock 2.3.3. I did not like it, so decided to roll back to cm7, I did, and here i am with no signal in my phone... I did flash the old baseband, but am still stuck with no signal... am in real trouble, and now if I again switch to stock 2.3.3, then also I dont get a network coverage at all. Please help me buddies
---------- Post added at 04:39 PM ---------- Previous post was at 04:28 PM ----------
And yes one more thing, even if I flash back the old stock froyo, via kdz or lgmdp, I cant get the network coverage... the guy at LG service center says there's some problem with the board... but I dont think its the board problem, is there any way to diagnose this issue or am I *ucked?
shreyas.kukde said:
Guys please help me. everything was running fine until I decided to switch to stock 2.3.3. I was unaware with this baseband thing. I switched to stock 2.3.3. I did not like it, so decided to roll back to cm7, I did, and here i am with no signal in my phone... I did flash the old baseband, but am still stuck with no signal... am in real trouble, and now if I again switch to stock 2.3.3, then also I dont get a network coverage at all. Please help me buddies
---------- Post added at 04:39 PM ---------- Previous post was at 04:28 PM ----------
And yes one more thing, even if I flash back the old stock froyo, via kdz or lgmdp, I cant get the network coverage... the guy at LG service center says there's some problem with the board... but I dont think its the board problem, is there any way to diagnose this issue or am I *ucked?
Click to expand...
Click to collapse
Hey mate, well no gsm is normally caused by the wrong baseband, so flashing back to the old one should fix the problem, try to re-flash the stock froyo given in the link on first post and see if that works, and if still no coverage then its a hardware problem and Lg should replace it for you, just dont forget to flash back to stock again if you rooted it, then they should fix it within the warranty.
This is the first time I'm posting on a forum about this problem, thought I could tackle it myself.
Turns out I was wrong.
I bought a Samsung Galaxy Note 3 SM-N900A on eBay a couple weeks ago. I've been having a difficult time getting the phone to consistently read a sim card and provide steady service. I've researched a lot on this forum, droidviews, galaxynote3root, and so on.. and haven't been able to get it working. Though, I have at times been able to get service, including data. It's been intermittent and have repeated steps to try and get it working but they haven't worked. There are a few thing's I came across though that may help give me the right steps to fix this.
After a fresh tar file flash using Odin, the baseband is still unknown. I've tried this with a couple different versions such as NC2 (the one I can flash with), NL1 and OC1. I read somewhere that this means the modem file is corrupt, so I flashed the corresponding modem, and tried different ones. This is where I would sometimes have a working phone and sometimes not.
This is so confusing and there's a lot of information I could right on here but I'm really just looking for someone to help me fix this because its so frustrating. I could return it and I might, but my other phone has a cracked screen and lets not go there..
**The most interesting thing that's happening is after a "successful" flash at times the phone will have service, maybe for a very short time or even overnight.
PLeeeeaaaaasseeeee help
sublim3style3 said:
After a fresh tar file flash using Odin, the baseband is still unknown. I've tried this with a couple different versions such as NC2 (the one I can flash with), NL1 and OC1. I read somewhere that this means the modem file is corrupt, so I flashed the corresponding modem, and tried different ones. This is where I would sometimes have a working phone and sometimes not.
Click to expand...
Click to collapse
When you did the fresh tar file with Odin, was it just the modem? What I would do is Odin the stock NC2 files, this way you would have a clean install and should have no problems. These are the ones I use, BL https://www.androidfilehost.com/?fid=96042739161891602 AP https://www.androidfilehost.com/?fid=96042739161891890 CP https://www.androidfilehost.com/?fid=96042739161891603 CSC https://www.androidfilehost.com/?fid=96042739161891604
I flashed the stock file as one in the AP file section. I have downloaded the individual files of NC2 OC1 and NL1 (just trying get some consistent service before I get started on NC2 and rooting.
Thanks and I'll keep you updated!
I read somewhere that I shouldn't flash a bootloader lower than the one I currently have. Is this true or is it ok to go from OC2 to to NC2?
sublim3style3 said:
I read somewhere that I shouldn't flash a bootloader lower than the one I currently have. Is this true or is it ok to go from OC2 to to NC2?
Click to expand...
Click to collapse
When I go to NC2 from any other (OC2, OC1, NJ5, NL1) I always flash all four BL, A,P CP, and CSC, just so I don't have any problems. Now, do not try to go lower than NC2 bootloader.
What about the pit file and which Odin do you use?
sublim3style3 said:
What about the pit file and which Odin do you use?
Click to expand...
Click to collapse
Don't need a pit file. Odin v.3.10.6 http://forum.xda-developers.com/attachment.php?attachmentid=3109599&d=1420980613
Ok I did what you said and I could tell right away that the phone is more stable. The performance is better and I can make calls and send texts, for now. I'll wait to see if it stays consistent. The only thing is that I can't seem to get the data working. I use straight talk wireless and have changed the APN settings that were given to me by one of their reps.
I'm at a stage where I'd like to root it with towelroot, install busybox and get safestrap recover v3.75 installed to get a stable ROM going.
I've read that some modems work better than others and to try flashing different ones. I have the list of them from Walter White that are recovery flashable but would it be better to go through odin? Are there any boundaries I should be concerned about? I'm pretty confident in trial and error since you provided me with these files.
Thanks!
sublim3style3 said:
Ok I did what you said and I could tell right away that the phone is more stable. It's performance is and I can make calls and send texts, for now. I'll wait to see if it stays consistent. The only thing is that I can't seem to get the data working. I use straight talk wireless and have changed the APN settings that were given to me by one of their reps.
I'm at a stage where I'd like to root it with towelroot, install busybox and get safestrap recover v3.75 installed to get a stable ROM going.
I've read that some modems work better than others and to try flashing different ones. I have the list of them from Walter White that are recovery flashable but would it be better to go through odin? Are there any boundaries I should be concerned about? I'm pretty confident in trial and error since you provided me with these files.
Thanks!
Click to expand...
Click to collapse
I would go with rooting it and busybox, then safestrap. As long as you stick with roms for N900a and the modems for Walter White, you should be good. When I was on straight talk this was the the APN I used, Name: straight talk
APN: tfdata
Proxy: Not Set
Port: Not Set
Username: Not Set
Password: Not Set
Server: Not Set
MMSC: http://mms-tf.net
MMS Proxy: mms3.tracfone.com
MMS Port: 80
Thanks for your help. After running exactly the files you provided for a while, I noticed the same behaviors came back. So I tried flashing modems. Nothing prior to NB4 works. The others are inconsistent and just screwy, though I'm still doing trial and error. I can't seem to get a reliable data connection. Some places I'll just have crappy service where I know I'd have service with my LG G2.
Ok so I figured something out. The phone is sensitive to USB debugging mode. Why? I'd really like to know.. it works at times when it's on, and times when it's off. Though whenever it decides which option it will select, the other option won't work. I've confirmed this yesterday and again today by changing whether USB debugging is on or off and immediately seeing a change.
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....
Is "Copy partitions zip" still needed when prepping for roms with official firmware?
In the following threads and others, I'm seeing the first step listed as crucial, and involving flashing this small zip file in order to populate the B slots of the phone:
https://forum.xda-developers.com/moto-x4/how-to/guide-install-android-9-0-pie-gsi-moto-t3833860
https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265
However, in more recent tutorials as well as the (awesome) videos I've seem floating around from munchy, this step is not shown. In fact, the act of "populating the B slots" now seems tied to flashing a copy of the official firmware in order to prep for custom roms.
I'm a little bit confused about wether the official firmware is now a replacement for this original "copy-partitions-payton.zip" file. Aside from a couple of OP's, I don't see anybody mentioning this file anymore. Also, when instructions are given on "populating the B slots" it seems to now refer to the official firmware flashing process.
Am I getting all of this correct? Is flashing the official firmware a replacement for the step of flashing the copy-partitions-payton.zip file?
I've already unlocked my bootloader.
I really apologize if I'm asking obvious questions, but this is my first android phone in 5 years and I really, REALLY don't want to screw this up. I've had a lot of catching up to do and have been doing a ****-ton of reading in this forum. I think I have the rest of the flashing process figured out... I just want to do the first step right. Thank you so much XDA for being the resource for people like me!!
we still need it. which video doesn't have this step? pretty sure i did mention it in all the videos. if i did not , then my bad.
Hey man thanks so much for replying! I haven't actually seen it in any of the videos - unless I'm missing something incredibly obvious.
(for context - my ultimate goal is to flash LineageOS 15.1 and get root passing SafetyNet to the point where GPay works)
I started here to get the basics:
https://www.youtube.com/watch?v=bkmczD9tvEQ
This video starts right with flashing the stock firmware:
https://www.youtube.com/watch?v=2-Kcwjyk_Ls
This video I didn't understand at first, but eventually got that you're just explaining A/B slots, not necessarily giving a tutorial:
https://www.youtube.com/watch?v=zVwYxp30dps&t=119s
None of these have that specific zip being flashed.
So if I understand correctly the correct process after buying the phone would be...
1) Unlock bootloader
2) push needed zips to phone storage
3) fastboot into TWRP
4) flash copy-partitions-payton.zip
5) reboot into recovery
6) flash stock firmware (I'll be using PAYTON_FI_8.1.0_OPWS28.46-21-8_subsidy-DEFAULT_regulatory-DEFAULT_CFC)
6) ...and basically follow the rest of your video to a T from there.
Hey I was wrong sorry - it's totally in the Android P video. So that was super helpful... and I just finished flashing everything successfully! I did not seem to have to flash the stock firmware at all - I simply flashed copy-partitions-payton.zip, did a factory reset, and moved right on to flashing LineageOS.
So does this mean that copy-partitions-payton.zip and flashing a copy of stock firmware accomplishes the same thing?
This is also missing from the official Lineage documentation, fyi:
https://wiki.lineageos.org/devices/payton/install
Thanks for your videos, they've been super helpful and so far no problems with my flash.
amirite said:
So does this mean that copy-partitions-payton.zip and flashing a copy of stock firmware accomplishes the same thing?
Click to expand...
Click to collapse
What do you mean by flashing a copy of stock firmware? Where is it asking you to flash stock firmware, the guide assumes you are on stock firmware. Also, if you have LOS already running dont bother about it too much. The original instructions explaining all this were in the LOS thread I created, which was transferred to Erfan once LOS was official. Now, the original instructions are no longer there. So, just forget about them and enjoy your custom rom :highfive:
I surely am Everything is running perfectly, except for a couple of minor crashes of the settings app. No biggie. Thanks again for the reply, I'm sure I'm mis-reading a few things pretty badly, but this is helping.
When you use the flash_all.sh script in your videos (at 4:45 in the 2nd video), is that not flashing the stock firmware? Isn't that zip directly from Motorola and flash_all.sh flashes the entire phone back to stock?
I assumed that flashing the stock firmware was a way of putting the phone in a known-good state before continuing with you guide. But then you talk about how Motorola didn't populate the B slots. So I'm just not exactly clear on what the copy-partitions-payton.zip does. I did flash that, but I didn't have to use flash_all.sh at all.
amirite said:
I surely am Everything is running perfectly, except for a couple of minor crashes of the settings app. No biggie. Thanks again for the reply, I'm sure I'm mis-reading a few things pretty badly, but this is helping.
When you use the flash_all.sh script in your videos (at 4:45 in the 2nd video), is that not flashing the stock firmware? Isn't that zip directly from Motorola and flash_all.sh flashes the entire phone back to stock?
I assumed that flashing the stock firmware was a way of putting the phone in a known-good state before continuing with you guide. But then you talk about how Motorola didn't populate the B slots. So I'm just not exactly clear on what the copy-partitions-payton.zip does. I did flash that, but I didn't have to use flash_all.sh at all.
Click to expand...
Click to collapse
What I understand is that Moto does not flash both slots by default, but flashing the flash-all does both slots with the stock firmware. If you are on the default stock setup, copy-partions will just copy your the Moto default to the other slot.
Got it. So basically the main goal with that first step is simply to populate the B slot which can be achieved by either method. Thanks guys, I just wanted to make sure I understood the full scope of what had to be done. Always an adventure catching up to the many months of hard work y'all do to get us here. Much appreciated and I'm enjoying my new setup a bunch!
amirite said:
In the following threads and others, I'm seeing the first step listed as crucial, and involving flashing this small zip file in order to populate the B slots of the phone:
https://forum.xda-developers.com/moto-x4/how-to/guide-install-android-9-0-pie-gsi-moto-t3833860
https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265
However, in more recent tutorials as well as the (awesome) videos I've seem floating around from munchy, this step is not shown. In fact, the act of "populating the B slots" now seems tied to flashing a copy of the official firmware in order to prep for custom roms.
I'm a little bit confused about wether the official firmware is now a replacement for this original "copy-partitions-payton.zip" file. Aside from a couple of OP's, I don't see anybody mentioning this file anymore. Also, when instructions are given on "populating the B slots" it seems to now refer to the official firmware flashing process.
Am I getting all of this correct? Is flashing the official firmware a replacement for the step of flashing the copy-partitions-payton.zip file?
I've already unlocked my bootloader.
I really apologize if I'm asking obvious questions, but this is my first android phone in 5 years and I really, REALLY don't want to screw this up. I've had a lot of catching up to do and have been doing a ****-ton of reading in this forum. I think I have the rest of the flashing process figured out... I just want to do the first step right. Thank you so much XDA for being the resource for people like me!!
Click to expand...
Click to collapse
Well, I did not need it. I just went from stock android 9 to LineageOS 16.