Related
If you've flashed anything other than a direct from the factory flash, and are not yet aware of the dangers that may be faced when flashing to the eventual release of CYAN, then please read the next posting.....
Be aware, this is "Technically" a I9000 firmware. But with a few changes and a dash of Guru and, BAM, we got 2.2 on our Vibrants. A direct flash of the current I9000 Froyo blend won't work, so don't try it. But this will. Its running smooth and clean so far, with the only issues being a reversed volume key, and a I9000 boot screen. But there's no boot sounds or Tmobile flash for that mater.
Update: Currently no data. But should be an easy fix. Fixed
Flash at your own risk, yada yada.....
Flashing is identical to my other posting. So a copy and a paste I shall go....
Using Oden, you'll first need to put your device into Download Mode. From a device still on Vibrant firmware, you'll need to hold down the "volume down" button while booting. If you've been playing with I9000 firmware's like I was, your volume has been reversed and the reverse applies to you, "up volume". If you still can't enter download mode, you may want to try holding down the volume key + the power button. Plugging in your USB cable may also aid your efforts to enter download mode.
Once in download mode, use the attached files below to flash your device. I'll give you a quick run through of Odin, but for detailed information I'd suggest this YouTube video. Keep in mind that in this video the poster is actually flashing an I9000. But the process is similar in all respects with the only difference being the key combination used to enter Download Mode.
A system wipe beforehand is recommended. If your having Market issues after flashing, this is more than likely the culprit.
1. Open Oden.
2. Extract the .pit file, click the PIT button in Oden and load the file.
3. Extract the three .tar files from the firmware file, load each into the three fields directly beneath PIT. These being PDA, PHONE, and CSC.
4. Under Options, be sure the following three boxes are checked. Re-Partition, Auto Reboot, and F. Reset Time.
5. Put your device in download mode and plug it in. Pay attention to the "COM" number that's detected in Oden. Your going to want to work on "COM7". If your receiving messages that the driver failed to install, or couldn't be found, extract the attached drivers file and direct windows to search for the driver there. I've seen better results using this manual approach, versus the installer.
6. Now press start, sit back, and be patient. In my case, the install only took around a minute.
After installation has finished your sent to recovery, just hit the power button, which should be on reboot, and your done.
FYI; I stopped and rebooted my phone at every sequence during this flash process, and I never bricked. Not necessarily intentionally, but I am very rough on my toys. Even after freezing or stalling partway through cache setup, factoryfs, you name it, no paper weight. This phone is stout!
Please keep me apprised of your results.
Required Tools:
Odin3 v1.00...
depositfiles
Hotfile Mirror
Pit file, as mentioned in other threads, the 512 seems to work best...
Pit file
Hotfile Mirror
I located the following files on Softpedia. I'd recommend manually installing your drivers. My results using the installer weren't great...
Windows x64 Drivers on Softpedia
Windows x86 Drivers on Softpedia
Firmware:
Model number: GT-I9000 (We'll fix this)
Firmware version: 2.2
Baseband version: T959UVJE8 Updated to T959UVJFD
Kernel version: 2.6.32.9
Build number: GT-I9000-eng 2.2 MASTER 332 test-keys.332
Froyo By MS_Guru:
I'm glad I didn't release this, but I will keep it maintained in the event that its needed for brick explorations. Any Devs interested in any part of it, lemme know.
Reserved...
Firstly I'm glad someones finished this, its the end of the month, and the time when my business shifts into high gear. Which is why I've been MIA the past few days. But I have made a few observations which seem worthy of mention.
Firstly, to those of us who have been flashing I9000 builds, it is in fact true. Flashing directly to the coming release of Cyans Froyo with anything but a Factory T959 boot, will more than likely brick your phone. But now that we know this, something can be done about it. As it turns out, people like myself, who started flashing alien firmware right off the bat, were actually giving our devices what could be thought of as flu shots. So much so, that when I eventually went and flashed I9000 Froyo directly, my device had enough of an immunity to weather the storm and eventually thrive. Which I think is pretty interesting.
So if your in this boat, don't worry your not screwed, you should just be a little cautious until a clean fix is found. Don't take this to the bank, but through my own I9000 Froyo build, and spending time playing with the brick, I've made a few discoveries.
1. If you've flashed anything that's reversed your volume keys at any point, you have the brick potential.
2. You can have flashed a few different firmwares and still walk away clean. If you remember exactly what you've flashed, go back and look for a file named "boot.bin". Its almost always in the PDA section of the flash. So just open the "PDA.tar" file with "Winrar". In all seriousness folks, don't take this to the bank until more people can verify this. If the firmwares you flashed didn't contain this file, you may actually be clean.
One thing I did see a good deal of, am but with what little time I've had the past few days, this file was more often than not in the PDA when someone bricked. I thought about after recalling the following....
User fykick mentioned...
I can confirm that jm1 and jm2 also brick phones.
Click to expand...
Click to collapse
A review of those Firmwares does in fact reveal a boot.bin file. This should also be verified by someone else. But I believe this to be either a core part of, or the actual Recovery and Downloader in the raw, and the cause of most headaches. Another sign of trouble would be red lettering in the upper left corner of your Downloader page?
So to summarize, flashing other Firmwares, and never having inverted your volume keys. As well as the lack of the "boot.bin" file in those same Firmwares, and the lack of red lettering on the downloader page, MAY in fact mean you've caused no harm and can flash the pending Cyan. But wait til others have chimed in, these are only my observations at the moment.
So there's still more to come from all this, both from myself, and other devs. But just so you know it wasn't a total wash. I've been keeping track of apps as I went though all these firmwares, and let me say, I'm gonna be able to contribute some first class apps to our impending firmwares.
Notable apps...
1. Very clean Samsung factory direct WPA/WPA2 tether, and we're talking easy enough for a retarded monkey to use. No clue if we'll see it directly in our providers flash, as most American providers are against tethering.
2. Video codecs that integrated into the existing video player, but only seem to be included in European Firmwares. Found that one out accidentally when a few music videos got included in a transfer. The same files wouldn't play on a stock Vibrant.
3. More than one lockscreen, all super clean, and some with amazing media, and notification integrations.
And many more...
That's it for now. Look for more to come though.
it's been strongly advised by the programmers working on CM6 to not flash to 2.2
7/28 9:25AM
Scepterr:
"Vibrant and Captivate users do not flash the i9000 JP1 & JP2 Froyo release it does not work correctly and you can not revert back." I would suggest to stay away from all that is I9000 for now.
Wesgarner has started work on the Galaxy S and it is going "fine".
designerfx said:
it's been strongly advised by the programmers working on CM6 to not flash to 2.2
7/28 9:25AM
Scepterr:
"Vibrant and Captivate users do not flash the i9000 JP1 & JP2 Froyo release it does not work correctly and you can not revert back." I would suggest to stay away from all that is I9000 for now.
Wesgarner has started work on the Galaxy S and it is going "fine".
Click to expand...
Click to collapse
I can co-sign this. You WILL brick your phone. I will wait.....
Talk about giving someone just enough rope to hang themselves. . .
I want to try this out so badly, but I can't risk screwing up my Vibrant. I'm a huge follower of CyanogenMod, so I'll wait.
Makes me laugh...
I think they just wanted to be first... Almost there guys. It really is running nicely. And honestly, there's no hope in hell of brickin this phone, I've been trying. Shes a stout little B..
MS_Guru said:
I think they just wanted to be first... Almost there guys. It really is running nicely. And honestly, there's no hope in hell of brickin this phone, I've been trying. Shes a stout little B..
Click to expand...
Click to collapse
I doubt they were going for first. CM is more about being the best than being the first.
MS_Guru said:
I think they just wanted to be first... Almost there guys. It really is running nicely. And honestly, there's no hope in hell of brickin this phone, I've been trying. Shes a stout little B..
Click to expand...
Click to collapse
Cool. If you can get data working, I'll give it a go when I get home so I can run Odin. No winders with me right now.
Oh, and verify that we can revert to a prior backup.
No...its true. These methods will brick your phone. I thought it was just something i was doing wrong but after going back from xjm1 and 2 i have bricked two phones....so im gonna delete my post as this is now a somewhat verified fact for me.
I warned you guys last night to not flash this. Wait for the real thing. Not like our phones are not already amazing.
Well I'm not sure what to tell ya, but I'm bookin right along here. And when I say I've tried to brick, I'm not joking. When I first got this thing I tried shoehorning every ROM, Flash, Recovery, I could get my hands on to this phone.
Can someone do me a favor, go into clockworkmod and give me a breakdown of the keys and there associated numbers? I've got clockworkmod on already, but without a home key you get stuck in recovery. A quickie remap, and I'll be done.
IE.. Volume up is 164, I think? Volume down, Power, and each touch key. Theress a key feature in there, but don't wanna flash back just for that.
s15274n said:
I warned you guys last night to not flash this. Wait for the real thing. Not like our phones are not already amazing.
Click to expand...
Click to collapse
I flashed mine before this firmware. But it was an overseas firmware and when i tried to revert back my phone went totally dead.
i'm pretty sure with this you would have to go back to a stock kernel and then do a nandroid to stock 2.1 you made w/ nandroid...i could be wrong tho..but i don't wanna mess with my kernel unless i have to so i'm going to wait till this is an rom version of the .zip flavor and it's ported for the vibrant. or just wait for CM6, but the only thing i'm worried w/ cm6 about is, are we going to lose allshare/tv out/ 5.1 headphone simulatioin / the music player / dialer / phonebook / things i actually like from the samsung rom... but yeah i will flash this puppy once ported.
MS_Guru said:
Well I'm not sure what to tell ya, but I'm bookin right along here. And when I say I've tried to brick, I'm not joking. When I first got this thing I tried shoehorning every ROM, Flash, Recovery, I could get my hands on to this phone.
Can someone do me a favor, go into clockworkmod and give me a breakdown of the keys and there associated numbers? I've got clockworkmod on already, but without a home key you get stuck in recovery. A quickie remap, and I'll be done.
IE.. Volume up is 164, I think? Volume down, Power, and each touch key. Theress a key feature in there, but don't wanna flash back just for that.
Click to expand...
Click to collapse
Vol Up - 42
Vol Down - 58
Power - 26
Menu - 158
Home - 139
Search - 107
Back - 28
Well it is pretty well done, just need the key numbers. Hint hint... Go to recovery and click the option for key... something or other. Its really really easy.
Thank you ttabbal ...
sounds like MS_guru is more then the average user.
Good luck in your modding. Hope to hear more great news soon!
@ MS_Guru,
Hope you get it all figured out
Man...I'll pass I did the other "stock" "pre release firmware" and I damned the moment I did it. I'm back to stock with 3g and camera working thanks to scepterr but still with euro baseband. No thanks!
Well If it is just a fluke, Time will tell. As more people are willing to flash a foreign rom for Froyo than just a faster kernel. So we will see if its just an unlucky few who have bricked their phones or when all the people who flashed to this revert back and brick their phones. I know for a fact I have bricked 2 phones, reverting back to US firmware from any firmware after JG5...IE: jm1 and jm2. The first brick I assumed was a fluke...but then when the second one from the same method...I stopped testing my luck. I know before when using JG5 and before, I was having success, but something in JM1 and after are causing bricks. There is no guarantee that this bug is not present in the XP1 and XP2, but after two bricks, Ima hold off til CM6.
pychobj2001 said:
but the only thing i'm worried w/ cm6 about is, are we going to lose allshare/tv out/ 5.1 headphone simulatioin / the music player / dialer / phonebook / things i actually like from the samsung rom... but yeah i will flash this puppy once ported.
Click to expand...
Click to collapse
I hear ya. There is plenty I don't like on the phone, but there are some things I would like to keep.
Good afternoon all,
I have an HTC One PN072. I've flashed the phone from Sprint to Cricket. They were very adamant about me not "resetting" the phone as it will remove the information, or flash they've added.
I've done several searches and can't seem to find a thread indicating 1) if this is possible and 2) a guide to doing so. The phone already is rooted and has TWRP on it as well.
If anyone knows of a thread I would love a link to a guide.
heartspains88 said:
Good afternoon all,
I have an HTC One PN072. I've flashed the phone from Sprint to Cricket. They were very adamant about me not "resetting" the phone as it will remove the information, or flash they've added.
I've done several searches and can't seem to find a thread indicating 1) if this is possible and 2) a guide to doing so. The phone already is rooted and has TWRP on it as well.
If anyone knows of a thread I would love a link to a guide.
Click to expand...
Click to collapse
I have a Sprint One fully flashed to Verizon and I flash custom ROMs all the time without any problems. I have never lost any settings and I don't even have to re-activate my phone. I would think that as long as you dont use Bootloader to flash a complete RUU image you should be fine. Goin s-off if your not already might cause issues here as well. (If someone knows for sure please correct me) I would say just download a ROM and install it with TWRP. I have updated firmware as well with no issues as well, however the firmware I upgraded with did not contain a radio update, which I am hesitant to do since I imagine that will effect my flash. I did my flash myself but it seems like a headache re-doing it.
electroblood said:
I have a Sprint One fully flashed to Verizon and I flash custom ROMs all the time without any problems. I have never lost any settings and I don't even have to re-activate my phone. I would think that as long as you dont use Bootloader to flash a complete RUU image you should be fine. Goin s-off if your not already might cause issues here as well. (If someone knows for sure please correct me) I would say just download a ROM and install it with TWRP. I have updated firmware as well with no issues as well, however the firmware I upgraded with did not contain a radio update, which I am hesitant to do since I imagine that will effect my flash. I did my flash myself but it seems like a headache re-doing it.
Click to expand...
Click to collapse
The wipes in TWRP usually recommended before flashing a custom rom don't remove their flashed data?
heartspains88 said:
The wipes in TWRP usually recommended before flashing a custom rom don't remove their flashed data?
Click to expand...
Click to collapse
Not that I have ever experienced. That was true on my EVO LTE and has so far been true on my One. I have the newest TWRP and in the past two days I have flashed EclipticOne, Elegencia and Insert Coin. On my old Droids Clockwork recoveries reset worked fine as well. DONT do a factory reset from inside the ROM. I have not tried it on my One, but on my EVO and my Droid 1/2/3 phones that would undo parts of a flash and I would have to reactivate. If I were you I would just work within my current firmware and flash what was available.
It is possible for you to flash your phone back to Cricket for free but its requires a lot of setup and can be a real pain in the ass. Getting 3G on Verizon was particularly painful and I have many screen shots and pages of notes on the actual procedure. When I upgraded from my EVO to the One I managed to get it right the first time by following my notes but it was still a serious hassle.
electroblood said:
Not that I have ever experienced. That was true on my EVO LTE and has so far been true on my One. I have the newest TWRP and in the past two days I have flashed EclipticOne, Elegencia and Insert Coin. On my old Droids Clockwork recoveries reset worked fine as well. DONT do a factory reset from inside the ROM. I have not tried it on my One, but on my EVO and my Droid 1/2/3 phones that would undo parts of a flash and I would have to reactivate. If I were you I would just work within my current firmware and flash what was available.
It is possible for you to flash your phone back to Cricket for free but its requires a lot of setup and can be a real pain in the ass. Getting 3G on Verizon was particularly painful and I have many screen shots and pages of notes on the actual procedure. When I upgraded from my EVO to the One I managed to get it right the first time by following my notes but it was still a serious hassle.
Click to expand...
Click to collapse
i was thinking about getting my one flashed to verizon but how does it work?? say i get my phone flashed.. is it verizon pre paid?? does that come with unlimited data?? text & talk?? how much would my bill be a month? sorry for all the questions
I apologize, so just to be as clear as possible, if you follow all of the wipes that roms usually ask you to perform in TWRP then you should be fine? However, do not perform a factory reset in the rom itself once loaded?
Doing a wipe through TWRP's wipe feature is fine as long as you dont go into 'Advanced' and mess with settings. Do not do the factory reset within the ROM once the ROM is loaded. If, while installing a ROM, the installer wants to do a wipe, that is fine as well.
After towelrooting and adding safestrap, I found that Sammy's TW os is cemented into any of the roms I may want to use. So, I am returning my rooted phone to ATT and getting my money back. Getting a Nexus 5.
I need to factory image this *****. Is there a factory Kitkat image available that I can use with Odin?
Any chance of it not being detected?
Thanks for the help.:good:
The image for KK for the Note 3 has been posted here. It's rooted, so you'll have to unroot (remove busybox first) after you install it. Oh - uninstall Safestrap first. (You'll have to read threads to find the 4.4.2 file - I don't keep links to threads I don't need, but try the Odexed version at this thread. Aside from being rooted, it should look exactly like stock. You can't back up an image of the ROM without being rooted, so any image you find will be a rooted one. But SuperSU will remove most signs of root. [If Samsung wants to investigate every byte of internal memory, they might be able to detect that you once did something. But if your luck is that bad never get out of bed. The stores will turn the phone on, look around a bit and accept it as stock, even if you've put your name and email address in it, although you SHOULD do a factory reset before returning any phone.
As far as your original post, yes, you'll find the original ROM in the stock slot in Safestrap after you install it. That doesn't mean that you can't successfully run some ROMs in other slots (no guaranties yet, Hashcode is still working on the problem) or you can back up the stock slot, wipe it, install any ROM there that you like (the "plain vanilla" method of using Safestrap in Kit Kat right now).
If you can't wipe the stock slot, uninstall Safestrap, reboot to recovery, do a factory wipe, reboot normally and reinstall Safestrap. (Make sure you're using 3.75, or even 3.72. 3.71 is for 4.3, and it won't work on Kit Kat.)
The Nexus is a nice phone, but Safestrap has saved me from a few stupid blunders that normally would have required that I buy a new phone. (Try flashing a keyboard in recovery. Then boot. If you boot to the slot you flashed the keyboard in you have a pretty good soft brick. With Safestrap, just reboot into Safestrap and reflash a real ROM. Total panic - 5 minutes of my life I'll never get back, instead of $700, due to my own inattention.) I actually don't want a phone without Safetstrap or something equivalent any more. It's like a desktop you can't install an OS to that comes with multi-boot. If you screw one up, just boot into another one. Even if you only ever run one ROM, it's worth it for the safety alone.
Thread Cleaned. The childish trolling has gone far enough. An honest question was asked, honest answers should be given. Any further trolling will be met with moderator actions.
Thank you for the updates. This will be great. Just need to sit down and make sure it's done right. I appreciate the cleanup and trolling wasnt my intention.
I'm beginning to understand how good safestrap is for me. I did a little checking on how to use it further and yes, it is a good safeguard against blunders.
I'm thinking if I can get a working rom that I like that isnt so touchwiz based but still gives me good s-pen functionality, maybe the phone is worth keeping. I just hate samsung and how they've really f-ed up the os in general, not to mention the amount of crapware that comes with it.
cwis said:
I'm beginning to understand how good safestrap is for me. I did a little checking on how to use it further and yes, it is a good safeguard against blunders.
I'm thinking if I can get a working rom that I like that isnt so touchwiz based but still gives me good s-pen functionality, maybe the phone is worth keeping. I just hate samsung and how they've really f-ed up the os in general, not to mention the amount of crapware that comes with it.
Click to expand...
Click to collapse
Don't blame Samsung for the bloat. Blame at&t! You can also blame at&t for locking the bootloader and not allowing us to have an factory image restore. Praise to the almighty safestrap!
Finding a non touchwiz rom with good s-pen integration is going to be hard. You can blame Samsung for that!
Digital Kat Extreme is good but the s-pen sucks. I may try this one instead: http://galaxynote3root.com/att-gala...r-att-galaxy-note-3-download-booster-working/
Tested the S5 rom works beautifully.
Tested the Note 3 rooted rom works slow, but so did the factory image. WTF???
cwis said:
Tested the S5 rom works beautifully.
Tested the Note 3 rooted rom works slow, but so did the factory image. WTF???
Click to expand...
Click to collapse
So is it fast with S5 ROM? I agree with you that our AT&T Note3 is POS.
I tried many different ROMs. After installing everything I normally use, it's always a dog. Taking 1 second to turn on the screen from sleep should not happen on a Snapdragon 800. I tried removing xposed mod, it becomes bit faster but still found it lagging a little time by time.
I'm going to try the S5 ROM now that you suggest it.
edit: S5 ROM is really fast! I hate touchwiz to death, but this one is fast for real. Instant on from standby. I might actually stick with touchwiz on this instead of Nova Launcher.
edit2: Because the bootloader is locked, there is a bug where the phone never goes into deep sleep mode. I don't really mind because the battery still lasts 24 hours with 1:30 screen-on time. No lag turning on the screen is the thing I really like. I did experience another bug where the screen won't turn on for more than 30 seconds, and I had to force reboot.
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.
Going back to stock from my rooted PopRocksV14. Haven't flashed ROMs in a while, so super rusty. Input welcome. TIA!
Questions:
1 Any faster mirror for N910TUVU2EQI2 than https://www.sammobile.com/firmwares/galaxy-note4/SM-N910T/TMB/?
2 How is the latest stock FW? Any reason not to upgrade? I'm just looking to get a stable phone and decent battery life, don't care about bloat
3 I'm looking to overwrite any Kernel and partition changes that PopRocks might have made, so is flashing back to stock rom going to do this?
Steps:
1 Make sure Samsung drivers installed
2 Download Odin 3.13 - https://odindownload.com/download/#.WyvXuCAnbAQ
3 Download EQI2 rom
4 Factory reset N910T
5 Run Odin as Admin
6 Start N910T in Download mode
7 Connect phone to PC via USB cable
8 Check Odin that COM is connected
9 Click PDA and select EQI2 tar file
10 Make sure Auto Reboot and F.Reset Time are checked, all other options disabled
11 Click start and wait for update to complete and phone to reboot
12 Factory reset N910T
I went ahead and tried it after the Sammobile download completed and it worked!
sfsilicon said:
I went ahead and tried it after the Sammobile download completed and it worked!
Click to expand...
Click to collapse
@sfsilicon - hope you're still monitoring this old thread. I'm trying to revive my old Note 4 I found in a junk drawer - for my 6yo boy. It had some custom rom on it, and I've now attempted with Odin to restore the image EQ12 you had listed - it appears to be the most recent.
Oden gets about 99% done then fails and now the phone is stuck in some sort of emergency mode. I can get into download, but not recovery. I assume I hosed it - maybe the bootloader was the wrong kind from the prior custom rom (and I didn't take note of what it was since I was just wiping it out).
Bummer.
Sorry to hear about your problems. It has been a while since I reflashed back to stock. Did it on two note 4s. From your description only thing I can think of would be that you flashed from a rom that was from an earlier Android version to the latest and it is missing some files or partitions that would normally be part of that type of transition. E.g. if you had done all the updates via OTA vs gone from your custom rom to the latest stock TMO release.
So try to figure out what Android revision your custom rom was before this latest flash. Then check the posts about moving from that revision to the next latest one and see if there is anything special in between. You can then look for the stock TMO rom that matches your custom ROM then flash back to that. Once you have a ROM working, even an older you can flash the next updates till you reach the final/latest TMO version or just OTA it.
One other thing to check is if your custom ROM did any changes to the kernel files or other stuff. Then check with the old custom ROM how to reverse them. Not sure if flashing a stock TMO rom undos all this. Its been a while but would think so but its still a step to check.
Hope this helps and good luck! I'm actually using my N4 currently. I use it to hold a foreign SIM when I am travelling. Sort of a glorified hotspot. Gave my 2nd one to my mom where the large screen helps with reading text. Its still a nice phone.
Thanks for getting back with me. I was under the impression that regardless of what custom rom may have been on the phone, Odin was a way to wipe the slate clean and put it back to day-1 state. I have no idea what OS was on there, but I do recall a warning about the bootloader being modified and it may be impossible to roll back. That's going off of memory (which has a very low confidence level).
Now I can't even get it to power up at all. I think I'm going to bail and just get a cheap Chinese android phablet - don't need cell service. It's getting to the point that my time and patience is worth more than what I'm spending to rehab this thing. Sucks too... When I first got the N4, I was pretty proficient at swapping roms... But since I've not played with them in years, I've all but forgotten the basics.
Thanks for the suggestions, tho...
E