Related
Hi,
First off I bought my T-mobile branded Streak 7 from Craigslist a week ago before Dell announced that only the WiFi and unlocked Streaks would get 3.2! I was soo MAD!! So i posted my Dell on craigslist for dirt cheap on October 7th at 5:00 p.m. When I got home all on the sudden at 9:00 p.m. California time I got a notification that an update was available!! I proceeded to jump up and down and hit the download the update!! I went through all the steps and I have an official 3.2. streak T-mobile version!! I bought it from someone who stated it was new and I only used it on WiFi, So I thought I would be skipped on the update. Guess only the t-mobile version's that were activated on t-mobile are affected?
Battery life is still the same and most of my apps work, except NetFlix!!
Anyone else rocking the official update on there t-mobile?
What rom version do you have? It was likely updated with a wifi/retail rom and not a tmo one as they dont exist
salgalvan said:
Hi,
First off I bought my T-mobile branded Streak 7 from Craigslist a week ago before Dell announced that only the WiFi and unlocked Streaks would get 3.2! I was soo MAD!! So i posted my Dell on craigslist for dirt cheap on October 7th at 5:00 p.m. When I got home all on the sudden at 9:00 p.m. California time I got a notification that an update was available!! I proceeded to jump up and down and hit the download the update!! I went through all the steps and I have an official 3.2. streak T-mobile version!! I bought it from someone who stated it was new and I only used it on WiFi, So I thought I would be skipped on the update. Guess only the t-mobile version's that were activated on t-mobile are affected?
Battery life is still the same and most of my apps work, except NetFlix!!
Anyone else rocking the official update on there t-mobile?
Click to expand...
Click to collapse
Ok im lost u have a branded tmobile device and you got a official hc up date from dell? How the hell.
does it actually have the Tmo logo on back of device?
even then could be faked... just syaing.. I hope its legit..
if so please PM TheManii.. he will be interested.
This might be great news!
Hi,
Ya I it came in the official T-Mobile box and paper work, and the T-mobile data only sim!! I took my sim outta my Dell Streak 5, which is also on T-mobile and it worked! But when i tried to browse the net I keep being re-directed to the T-mobile site!! It does show the 4g logo and edge too when I'm out of range. (My Dell Streak 5 I bought from Craiglister who bought it in Australia so I have been using a T-Mobile sim for years!
I'm guessing cause I was to lazy to get a t-mobile broadband plan. I was using only with WiFi.. So it was never registered with t-mobile. That's my best guess. I will post a photo of the info tonight.
TheManii said:
What rom version do you have? It was likely updated with a wifi/retail rom and not a tmo one as they dont exist
Click to expand...
Click to collapse
It is 3.2 along with the Dell Stage widgets. Listen guys I have no reason to be pulling anything over on anybody.. I was so Mad when I read on Dell that all but t-mobile streaks would be updated. I promise I'll post more info tonight.. I was No [email protected]#! way when I saw the update notification!
Ya it is the WiFi Retail honeycomb version! Every T-mobile app was missing, like Blockbuster, t-mo tv, but I can download them from the market.
???????????????
this is likely that unbranded update posted on streaksmart. Like you said If the device has never been registered on tmobile... but how would they actually keep track of this for the update... hmmm I dont know. But congratulations buddy, make sure to pm The Manii in case this is something new.
Photos added.
Hey everybody! Well I add some photos, but let me know if I should add more!
That's the unbranded US 4G one, you cant officially flash it from the previous tmo roms
By unbranded, do you mean the one that hasn't the "T-mobile" decal in the back?
because i have one that doesn't have the decal in the back, but it IS branded "t-mobile" (i have the T-mobile SIM and everything).
is the same?
I mean the rom, the Tmo s7 is the only physically branded device dell sells.
I'm talking about the rom as it's region 30 which is "dell" or "US" region
Tmo roms are 33 which is "tmobile" region roms
Isn't the point that it got sent to his tablet in the first place?
Sent from my Nexus S using XDA Premium App
Thanks Smurphjw! My point was only that I got the update and nothing else! So maby T-Mo users might get the update too, with out having to root. I understand that the rom is unbranded, but Dell was clear that only WiFi Streaks would gt the update.
I seriously doubt it was on an unmodified device as the update script in the pkgs only checks two things before installing:
1) If the device is a streak7
2) what region it is (out of either "tmo (33)" "Boss (00)" - which is what the EU regions use" and "US (30)")
The flashable zips I released only did two things: remove those two checks and remove the modem updates
TheManii said:
I seriously doubt it was on an unmodified device as the update script in the pkgs only checks two things before installing:
1) If the device is a streak7
2) what region it is (out of either "tmo (33)" "Boss (00)" - which is what the EU regions use" and "US (30)")
The flashable zips I released only did two things: remove those two checks and remove the modem updates
Click to expand...
Click to collapse
I have a quick question. Since all you did was remove the checks and modems, why can't one just change the zip file to update.pkg and use the stock recover to flash to HC? Why does one have to install CWM and then install the zip?
Or just change the region to (33), and then we can use the package without CWM? (I know, it is probably too simple, or it would have been done this way already).
The stock recovery decrypts pkgs, that's what makes pkgs different.
If you simply renamed the zip to pkg it would try and decrypt that and would end up with garbage. The stock rec has no options, it will only "decrypt the pkg" -> "attempt to flash decrypted pkg". Only way to flash something with the stock one is to first encrypt it correctly so it will decrypt it on it's own
Changing the region requires modifying the recovery image, which has already been done with links on the update guide
TheManii said:
The stock recovery decrypts pkgs, that's what makes pkgs different.
If you simply renamed the zip to pkg it would try and decrypt that and would end up with garbage. The stock rec has no options, it will only "decrypt the pkg" -> "attempt to flash decrypted pkg". Only way to flash something with the stock one is to first encrypt it correctly so it will decrypt it on it's own
Changing the region requires modifying the recovery image, which has already been done with links on the update guide
Click to expand...
Click to collapse
OK, thanks for the explanation. I'm still on Froyo, but I may update at some point. It seems pretty clear, and easy except for having to get CWM on the S7.
I seriously doubt it was on an unmodified device as the update script in the pkgs only checks two things before installing:
1) If the device is a streak7
2) what region it is (out of either "tmo (33)" "Boss (00)" - which is what the EU regions use" and "US (30)")
The flashable zips I released only did two things: remove those two checks and remove the modem updates
If you look at the photos I posted under the firmware it shows I have the US 30. I never posted trying to tick anyone else off. I never modified my Streak, but I give up, because apparently I'm lying according to ThManni. I only wanted to post my good news, and give some hope to others. When I bought my Streak it came in a sealed box with all the plactic on screen and back of unit. Sorry to all who dought me when I say I never modified my streak at all.
Sim Unlock Method 4.4.2/5.0.1
Disclaimer: i AM not resposile for anything that happens to your phone in the unlikely event something does happen.
this has only been tested lightly but it should work all-right. this is for the i537 S4A only.
You Need to start out on either NE3 or NH3. Downgrade now if you need to. Just remember when downgrading don't flash bootloader. This needs Odin and root to succede. Now That thats out of the way you need to download some files to deal with later on.
MF1 Odin flashable
regionlockaway go to the second post and download the apk to install on your phone.
this method uses an old method in a new way.
here is the guide
1. install regionlockaway and reboot to download mode
2. Flash modem.bin with odin in download mode
3.reboot to system and use regionlockaway. follow the instructions in the app.
4. profit?
As far as my understanding after you do this you can update your modem without it reverting back to being locked. I am running oc7 modem on a T-Mobile MVNO without issues( if you want aws unlock you are going to have to use this then the appropriate modem for that and not allow for the modem to update when updating to oc7 by modifying the oc7 installer and removing the modem from it)
I am ready... I have been reading for days about sim unlocking on 4.4 and up..I finally coined up $25 for a code but takes up to 5 days, 2 days ago. my next attempts were going to be with my paid copy of CDMA WS. Either way it is just to experiment with and would love to gain the knowledge. I have a couple different carrier sims ready to go. I would love to give it a shot.....
mateo121212 said:
hey guys i have created an easy sim unlock that should work for 4.4.2 and for 5.0.1
for the 5.0.1 sim unlock you have to do it on 4.4.2 and flash a modified partitions file to upgrade to 5.0.1 while keeping sim unlock.
if you guys are interested in it let me know and i will set up a few beta testers for it. i cant say for certain that it works because i dont have a non ATT sim card to test it with.but it should work. it should also allow you to enable aws for those on T-Mobile by following a secondary guide.
let me know and i will start having people beta test. i only need between 1 and 5 testers
Click to expand...
Click to collapse
nrgyitguy said:
I am ready... I have been reading for days about sim unlocking on 4.4 and up..I finally coined up $25 for a code but takes up to 5 days, 2 days ago. my next attempts were going to be with my paid copy of CDMA WS. Either way it is just to experiment with and would love to gain the knowledge. I have a couple different carrier sims ready to go. I would love to give it a shot.....
Click to expand...
Click to collapse
ok ill pm you with a guide once i have it written up.
EDIT: it should be in your inbox
i was able to test a verizon lte sim and it didnt give me any issues. it regestered the number in the status. so i belive it worked. i would like some more testers to get information about it. i need more testers before i feel ok giving out the method.
Been sooo busy!!!! K, thank you for the guide. I haven't been able to try anything except a Verizon Lte sim. It registers the number and the network lock is gone. However I don't believe we will get data service with a Verizon sim as I don't believe the hardware is capable?...I wasnt able to place a call as I got" Emergency calls only", all I did was swap sims, occasionally I have to call Verizon and have them add the new phone to the plan before it will work and I didn't do that yet. Will try a different carrier sim tonight.
mateo121212 said:
i was able to test a verizon lte sim and it didnt give me any issues. it regestered the number in the status. so i belive it worked. i would like some more testers to get information about it. i need more testers before i feel ok giving out the method.
Click to expand...
Click to collapse
nrgyitguy said:
Been sooo busy!!!! K, thank you for the guide. I haven't been able to try anything except a Verizon Lte sim. It registers the number and the network lock is gone. However I don't believe we will get data service with a Verizon sim as I don't believe the hardware is capable?...I wasnt able to place a call as I got" Emergency calls only", all I did was swap sims, occasionally I have to call Verizon and have them add the new phone to the plan before it will work and I didn't do that yet. Will try a different carrier sim tonight.
Click to expand...
Click to collapse
so before you did the guide did it give you issues with the verizon sim? and now it dosent?
It did give me issues before flashing the mf1 and after the flash and region away no nagging about sim unlock code! Havent gone any further yet. I will report back after using a different carrier sim besides verizon that is.....I think it works....
mateo121212 said:
so before you did the guide did it give you issues with the verizon sim? and now it dosent?
Click to expand...
Click to collapse
nrgyitguy said:
It did give me issues before flashing the mf1 and after the flash and region away no nagging about sim unlock code! Havent gone any further yet. I will report back after using a different carrier sim besides verizon that is.....I think it works....
Click to expand...
Click to collapse
sweet thank you for the feedback man. i did the 5.0.1 upgrade method i detailed in the PM after i finished doing the unlock on my phone and it worked the same as what you described (i only had access to vzw lte sim also) so i belive i made the update file correctly also. im not really getting any bites on more testers so if it pans out well for you i will polish up my guide and post it here to have people test it instead of making them PM me.
thanks again for being my beta tester. if we get this working well we can save alot of people alot of money
ps for voice and sms verizon lte sims are useless because they still use CDMA for those features
Finally put in another sim...Put in a Tomb sim and no nagging about unlock code, I got "Sim not provisioned" as it isn't active at the moment. So I'm thinking it worked. Thank you. I was thinking I'd get voice and edge speeds with a Verizon sim in this phone, (utilizing GSM bands), in my area anyway, but maybe I'm mistaken. I'll post again after using another carrier's sim.....
nrgyitguy said:
Finally put in another sim...Put in a Tomb sim and no nagging about unlock code, I got "Sim not provisioned" as it isn't active at the moment. So I'm thinking it worked. Thank you. I was thinking I'd get voice and edge speeds with a Verizon sim in this phone, (utilizing GSM bands), in my area anyway, but maybe I'm mistaken. I'll post again after using another carrier's sim.....
Click to expand...
Click to collapse
thank you for your work. im glad it worked for you. i will be posting the guide up here soon.
In reference to....
starting at post #327 of http://forum.xda-developers.com/gal...7oc6-5-0-1-t3089355/post61347589#post61347589
I did as instructed and according to flashfire at the end of flashing, it said it was successful and it rebooted (so far) to the lollipop boot animation and am awaiting for it to get past the at&t logo screen. Its at least gotten a lot further than all my earlier attempts...I am assuming its taking a little while for its initial setup of OC6....
more later on its success or failure....
well it was a partial success....it flash and booted into OC6 but sim card is not recognized, no baseband.....now installing updated version of flashfire....should i now flash the MF1 modem again via flashfire?
well i went ahead and did just that flashed the mf1 modem via flashfire and all is up and running successfully (FINALLY!!) with root on deodexed rom OC6...
Kudos and thanks goes out to ya!
jaksback said:
starting at post #327 of http://forum.xda-developers.com/gal...7oc6-5-0-1-t3089355/post61347589#post61347589
I did as instructed and according to flashfire at the end of flashing, it said it was successful and it rebooted (so far) to the lollipop boot animation and am awaiting for it to get past the at&t logo screen. Its at least gotten a lot further than all my earlier attempts...I am assuming its taking a little while for its initial setup of OC6....
more later on its success or failure....
well it was a partial success....it flash and booted into OC6 but sim card is not recognized, no baseband.....now installing updated version of flashfire....should i now flash the MF1 modem again via flashfire?
well i went ahead and did just that flashed the mf1 modem via flashfire and all is up and running successfully (FINALLY!!) with root on deodexed rom OC6...
Kudos and thanks goes out to ya!
Click to expand...
Click to collapse
your welcome man. i figured your problem could be fixed with my method. have fun with 5.0.1
partially completed downloads
Never mind. The downloads on dev-host work from my computer but not from tablet or phone.
I stopped THE INSTALLATION of I537_OC6_Stock_Partitions_mod_sim.zip and the phone is not the most part, dead, solutions?
spyke70 said:
I stopped THE INSTALLATION of I537_OC6_Stock_Partitions_mod_sim.zip and the phone is not the most part, dead, solutions?
Click to expand...
Click to collapse
Odin back to Ne3 and start over
so it didnt work. it stop saying it was an unreconizable sim card and region lock said it took. so i dunno it says (phone not aloud MM#6) right when i start up. but it shows i have a new voice mail? only emergency calls
oh ya and it was at&t and i put a family mobile simcard, (runs off t mobile network)
any ideas??
Jsturg1990 said:
so it didnt work. it stop saying it was an unreconizable sim card and region lock said it took. so i dunno it says (phone not aloud MM#6) right when i start up. but it shows i have a new voice mail? only emergency calls
oh ya and it was at&t and i put a family mobile simcard, (runs off t mobile network)
any ideas??
Click to expand...
Click to collapse
odin ne3
flash mf1 modem with flash fire
make sure you are rooted and have busybox
use region lock away. try with att sim in phone.
Trying to do this for my s4a but flashfire is being uncooperative, it just crashes any chance it gets. Any other flash apps this will work with?
Edit: do I need safestrap for FlashFire?
Edit2: Fixed the issue with flashfire, If anyone runs into this issue you need to flash stock NE3, and re-root.
Rest of tutorial went perfectly. Cannot test unlock status atm, but no errors.
Thanks Matteo, you're a top lad.
Will this same method work with a deodexed OC7 ROM? I only ask because of the I537_OC6_Stock_Partitions_mod_sim.zip - not sure if this still works the same for OC7. Just to clarify, do you know if region lockaway is necessary to get T-Mobile AWS/HSPA bands? I've got a working cell and LTE connection without doing any of this, so I really only needed to do what's necessary to get those bands (which I think the old modem will help enable).
Thanks for the assistance!
sunilbeforezod said:
Will this same method work with a deodexed OC7 ROM? I only ask because of the I537_OC6_Stock_Partitions_mod_sim.zip - not sure if this still works the same for OC7. Just to clarify, do you know if region lockaway is necessary to get T-Mobile AWS/HSPA bands? I've got a working cell and LTE connection without doing any of this, so I really only needed to do what's necessary to get those bands (which I think the old modem will help enable).
Thanks for the assistance!
Click to expand...
Click to collapse
edit to the edit:
go back to NE3 with odin.
then flash mf1 modem
then try this
[GUIDE] AWS Unlock for i537 I537UCUBML2 (4.3)
read the posts to make it work
also check out this post if you have issues with getting qpst to work. dont follow the whole post just qpst part http://forum.xda-developers.com/showpost.php?p=56023258&postcount=68
then follow the guide i posted in my last edit to keep the aws unlocked modem while on 0C7
edit:
you can use the oc7 deodexed rom. you just have to remove the modem from the rom file useing winrar or 7zip. also you have to remove it from the updater script useing a text editor. drag it out of winrar edit it and then drag it back into winrar. that way if you flash in this order you will be fine
partitions mod file
oc7 deodexed rom.
that way you keep the modem
from when you installed and unlocked mf1 modem on 4.4.2
I am usng the idol 4s windows phone of T-Mobile and i want to get rid of the T-Mobile firmware / software.
I saw that t-mobile has a way to install normal firmware on this phone on this page: https://support.t-mobile.com/docs/DOC-33537
Has anyone used it to recover the idol 4s? does it remove the T-Mobile firmware / software?
Update: i'm flashing the normale firmware now using the tool
https://support.microsoft.com/en-US/help/12379/windows-10-mobile-device-recovery-tool-faq
Let's hope it goes well
Yesterday it looks like it wanted to flash but failed at the end. The whole process took around 4 hours. Today i tried it on a different machine and it doesn't work.
It looks like the unlocked version has a newer firmware available on the server than the t-mobile version.
For the ones interested in this topic, on windowscentral there is a very interesting topic about why this device can't be flashed with the open market one. https://forums.windowscentral.com/alcatel-idol-4s/457103-10.htm
mobilemeneer said:
For the ones interested in this topic, on windowscentral there is a very interesting topic about why this device can't be flashed with the open market one. https://forums.windowscentral.com/alcatel-idol-4s/457103-10.htm
Click to expand...
Click to collapse
Interesting. I wonder if it is because of the radio differences between the variants. I'm considering the Idol 4S and would love the unlocked version, but the t-mo one is much cheaper.
I did something really stupid and ended up with a bad flash on my NOTE 9 - the result is that I no onger have an IMEI number on my phone - no data at all - no mobile data.
I know what my IMEI Number is from my GOOGLE account - but I don't know how I can fix my phone to get the IMEI number back into the phone.
Any suggestions are grealy appreciated.
I did a google search which had a few suggested ways using the dialer - but when I attempt to do that, nothing happens - I don't get any result from the dialer codes online.
Your help is greatly appreciated
Find the latest software for your phone and install it with Odin. Or emergency software recovery with Smart Switch.
Geekser said:
I did something really stupid and ended up with a bad flash on my NOTE 9 - the result is that I no onger have an IMEI number on my phone - no data at all - no mobile data.
I know what my IMEI Number is from my GOOGLE account - but I don't know how I can fix my phone to get the IMEI number back into the phone.
Any suggestions are grealy appreciated.
I did a google search which had a few suggested ways using the dialer - but when I attempt to do that, nothing happens - I don't get any result from the dialer codes online.
Your help is greatly appreciated
Click to expand...
Click to collapse
For the benefit of others (to hopefully not make a similar misstep) what did you do to create this issue? Flash a ROM from another region, carrier, etc.? I understand if you prefer not to share... thanks for the consideration.
d.cortez said:
For the benefit of others (to hopefully not make a similar misstep) what did you do to create this issue? Flash a ROM from another region, carrier, etc.? I understand if you prefer not to share... thanks for the consideration.
Click to expand...
Click to collapse
There was a rom in the Custom Roms section that looked like it was meant for our phones - I think it was the WETA ROM - I didn't read the oP very carefully - totally my fault - it was not intended for the N960F - (but that was not really that clear when I first read the OP - or at least I lverlooked it. i will be much more careful next time. - it damn near bricked my phone.
I tried flashing full firmware in ODIN to fix it -no good - the flashes failed. - I tried restoring Nandroids - they restored fine but IMEI was still missing.
The fix I found eventually was to flash the DEV BASE Firmware that was recently added to the Roms section - flashing that fixed my issues and I am now back and working properly. I tried more fixes than I can count - and all of them failed - I was close to thinking I might have to buy a new phone. Dr Ketan suggested I flash the Dev Base sortware and he was absolultely correct. It worked.
michelino159 said:
Find the latest software for your phone and install it with Odin. Or emergency software recovery with Smart Switch.
Click to expand...
Click to collapse
Neither Option worked for me - ODIN Flashes got stuck halfway thru the flash - and Smart Switch just didn't work
Geekser said:
There was a rom in the Custom Roms section that looked like it was meant for our phones - I think it was the WETA ROM - I didn't read the oP very carefully - totally my fault - it was not intended for the N960F - (but that was not really that clear when I first read the OP - or at least I lverlooked it. i will be much more careful next time. - it damn near bricked my phone.
I tried flashing full firmware in ODIN to fix it -no good - the flashes failed. - I tried restoring Nandroids - they restored fine but IMEI was still missing.
The fix I found eventually was to flash the DEV BASE Firmware that was recently added to the Roms section - flashing that fixed my issues and I am now back and working properly. I tried more fixes than I can count - and all of them failed - I was close to thinking I might have to buy a new phone. Dr Ketan suggested I flash the Dev Base sortware and he was absolultely correct. It worked.
Click to expand...
Click to collapse
Glad to know you're good to go... i just received my Dual Sim Note 9 today and got it setup to work with ATT using an ATT CSC and used it for 20 minutes. Popped my T-Mobile SIM in the phone and blam! got an invalid SIM card message followed by a SIM network PIN blocked. Enter SIM network PUK message. Got PUK unlock codes from ATT and T-Mobile and they did not work. off to do more research....
d.cortez said:
Glad to know you're good to go... i just received my Dual Sim Note 9 today and got it setup to work with ATT using an ATT CSC and used it for 20 minutes. Popped my T-Mobile SIM in the phone and blam! got an invalid SIM card message followed by a SIM network PIN blocked. Enter SIM network PUK message. Got PUK unlock codes from ATT and T-Mobile and they did not work. off to do more research....
Click to expand...
Click to collapse
Is that an international varient? Would love to hear if you get ATT CSC working. I am on ATT too in the US but right now using BTU CSC -
Geekser said:
Is that an international varient? Would love to hear if you get ATT CSC working. I am on ATT too in the US but right now using BTU CSC -
Click to expand...
Click to collapse
I was able to get around the PUK code through a master reset. Go figure.
There's a thread in the forums that talks about copying your carrier's CSC to your phone and then making the necessary changes to four files in the /efs/imei folder. It's not hard, but you got to be very careful. Instructions are in the thread mentioned above. I have LTE/HD Voice access during phone calls, but I have not been able to get Wi-Fi calling to work because the IMS service FC's when launching.
I suspect it may have something to do with using a dual-sim phone. I have both my AT&T and T-Mobile SIM in the phone, and I'm loving using one phone for business and personal calls. I also have Google Voice and I can use that for Wifi calling if necessary. As a final note, to get access to AT&T enhanced services on a non AT&T phone, you have to use an IMEI number from an AT&T phone that supports its enhanced services. In my case I've been using the IMEI number from my three-year-old Samsung S6 active. I called support told rep that I was using my S6 active while waiting on a new phone and they associated the IMEI number with my cell number.
d.cortez said:
I was able to get around the PUK code through a master reset. Go figure.
There's a thread in the forums that talks about copying your carrier's CSC to your phone and then making the necessary changes to four files in the /efs/imei folder. It's not hard, but you got to be very careful. Instructions are in the thread mentioned above. I have LTE/HD Voice access during phone calls, but I have not been able to get Wi-Fi calling to work because the IMS service FC's when launching.
I suspect it may have something to do with using a dual-sim phone. I have both my AT&T and T-Mobile SIM in the phone, and I'm loving using one phone for business and personal calls. I also have Google Voice and I can use that for Wifi calling if necessary. As a final note, to get access to AT&T enhanced services on a non AT&T phone, you have to use an IMEI number from an AT&T phone that supports its enhanced services. In my case I've been using the IMEI number from my three-year-old Samsung S6 active. I called support told rep that I was using my S6 active while waiting on a new phone and they associated the IMEI number with my cell number.
Click to expand...
Click to collapse
I have an IMEI number from a Note 9 that was an aTT Phone - I had purchased the snapdragon varient at Best buy and then returned it when I got the N960F . I copied the IMEI number before I turned it in - I suppose I could use that. Can you offer a link to the thread you are referring to?
thanks for the tip my friend.
Geekser said:
There was a rom in the Custom Roms section that looked like it was meant for our phones - I think it was the WETA ROM - I didn't read the oP very carefully - totally my fault - it was not intended for the N960F - (but that was not really that clear when I first read the OP - or at least I lverlooked it. i will be much more careful next time. - it damn near bricked my phone.
I tried flashing full firmware in ODIN to fix it -no good - the flashes failed. - I tried restoring Nandroids - they restored fine but IMEI was still missing.
The fix I found eventually was to flash the DEV BASE Firmware that was recently added to the Roms section - flashing that fixed my issues and I am now back and working properly. I tried more fixes than I can count - and all of them failed - I was close to thinking I might have to buy a new phone. Dr Ketan suggested I flash the Dev Base sortware and he was absolultely correct. It worked.
Click to expand...
Click to collapse
Could you please provide a link to this dev base firmware? Did you need to have twrp and root before installing the dev base?
brusyev2 said:
Could you please provide a link to this dev base firmware? Did you need to have twrp and root before installing the dev base?
Click to expand...
Click to collapse
dev base is Alexander rom in the development section.
brusyev2 said:
Could you please provide a link to this dev base firmware? Did you need to have twrp and root before installing the dev base?
Click to expand...
Click to collapse
If I am not mistaken, it was something like this https://forum.xda-developers.com/galaxy-note-9/development/test-s2arh6-devbase-v5-9-encryption-t3847061
you do need to have TWRP installed in order to flash
hope that helps
still need help
brusyev2 said:
Could you please provide a link to this dev base firmware? Did you need to have twrp and root before installing the dev base?
Click to expand...
Click to collapse
Do you still need help here is the link to the firmware that I used to flash stock ROM make sure you read what and how it is to be done the first time i flashed it i got stuck in bootloop and then i read it again and got it right now my phone works and is fine hope you have your phone working https://forum.xda-developers.com/galaxy-note-9/how-to/u1-note-9-official-firmware-guide-to-t3927478
Hi guys,
I have a question about obtaining Android 10 AT&T firmware for the SM-960U. I'm currently having an issue where I bought the Samsung Galaxy Note 9 N960U1 factory unlocked from Samsung themselves. My current carrier is AT&T. However, I've realized for a while that my area doesn't have a good signal (1 bar to no service) due to the location where I am. I am trying to install AT&T's firmware with the boot logo and its software's bloatware to obtain Wi-Fi calling. However, I am having trouble. Currently, I've flashed my N960U1 with AT&T's U1 Android 10 firmware from the site using Odin. I see that it's been flashed successfully after doing a clean install and see AT&T firmware in the phone. However, it did not give me an AT&T boot logo screen or give me the Wi-Fi calling option. This is carrier unbranded. It's still the same like it's from the factory unlock no carrier firmware. So, after doing some research, I see that what I have to do is: clean flash AT&T's U1 firmware on the device (which I did), then, finally, install the U firmware to bring on the AT&T boot logo screen and WiFi calling. However, I am unable to do the 2nd part, because the only available firmware for U firmware (AT&T's bloatware) is Android 8. Due to the bootloader being version 4 in Android 10 and version 2 in android 8, I cannot downgrade even on a cracked Odin version. The phone gives me a SW REV error and odin gives me a write error. I worked on this for 8 hours, don't try to fight me on this lol. This is because Odin understands that the phone can't be downgraded due to the bootloader version being higher. This can be seen in the firmware names when comparing (Android 8: N960USQU1ARG6. Android 10: N960U1UES4DTD1).
In summary, I need to find the SM-960U AT&T carrier-branded Android 10 firmware. Right now, on Sam Mobile for N960U, the only firmware that comes up is Android 8. Downloading the latest firmware for the SM-N960U1 on Sam Mobile doesn't help me obtain wifi calling and the AT&T boot logo. Any suggestions? I really need help and appreciate it if you guys could help me. I can't find AT&T's U anywhere. Thanks!
You can flash any U firmware they are the same. As long as you have At&t sim it will provision to your sim. Since you are U1 you will need to do factory reset before flashing with Odin. You can use USC..Tmobile..Verizon. Dont use User data when flashing just use BL..AP..CP..CSC. At&t doesnt post their locked firmware for whatever reason.
Sent from my SM-N960U using Tapatalk
butchieboy said:
You can flash any U firmware they are the same. As long as you have At&t sim it will provision to your sim. Since you are U1 you will need to do factory reset before flashing with Odin. You can use USC..Tmobile..Verizon. Dont use User data when flashing just use BL..AP..CP..CSC. At&t doesnt post their locked firmware for whatever reason.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
Awesome. I’m going to try this tomorrow. I’ll update this post with the results! Thanks for the help.
butchieboy said:
You can flash any U firmware they are the same. As long as you have At&t sim it will provision to your sim. Since you are U1 you will need to do factory reset before flashing with Odin. You can use USC..Tmobile..Verizon. Dont use User data when flashing just use BL..AP..CP..CSC. At&t doesnt post their locked firmware for whatever reason.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader. Make sure you do a clean reinstall beforehand. Everything should be off the phone.
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer cable also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet. Do not remove the SIM card during any part of this process. Leave it inserted the entire time.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port labeled in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just apparently did an update.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
robertj51 said:
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader:
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer port also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just updated.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
Click to expand...
Click to collapse
I am really glad I found your post and I'm going to attempt this same procedure today. Quick question, does it matter if / when your SIM is inserted into the phone? Just wondering if I need to leave it in or out during this process or whether that will even have an affect? Is your Wi-Fi calling still working currently, btw?
Carl_Sagan_Cosmos said:
I am really glad I found your post and I'm going to attempt this same procedure today. Quick question, does it matter if / when your SIM is inserted into the phone? Just wondering if I need to leave it in or out during this process or whether that will even have an affect? Is your Wi-Fi calling still working currently, btw?
Click to expand...
Click to collapse
Hey Carl! Sorry for the late response. I'm glad you found my post as well!
I apologize for this, I should've mentioned this in my original post: please leave the AT&T SIM card inserted in the device the entire time during this process! When the phone reboots after Odin flashes, the first thing it searches for is what SIM is inserted so it can flash the appropriate carrier setting. Do not remove the SIM during any part of the process from start to finish.
Secondly, yes! The WiFi calling feature is working great on the phone. I'm glad after two years of having the phone I was able to get the feature this month. Good luck. Please let me know if you were successful in flashing the firmware, I'd really like to hear your results! My notifications are turned back on for this thread.
robertj51 said:
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader. Make sure you do a clean reinstall beforehand. Everything should be off the phone.
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer cable also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet. Do not remove the SIM card during any part of this process. Leave it inserted the entire time.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port labeled in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just apparently did an update.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
Click to expand...
Click to collapse
What to do if i don't have at&t sim card, not even usa sim card, i'm in egypt and brought my n960u from usa, i installed u1 firm but realized that no wifi calling or volte so tried to install tmobile carrier firm and nothing appeared then tried at&t and also nothing appeared, neither the options nor the boot logo for tmobile or at&t.
what to do please help!
Thanks in advance
abulnass said:
What to do if i don't have at&t sim card, not even usa sim card, i'm in egypt and brought my n960u from usa, i installed u1 firm but realized that no wifi calling or volte so tried to install tmobile carrier firm and nothing appeared then tried at&t and also nothing appeared, neither the options nor the boot logo for tmobile or at&t.
what to do please help!
Thanks in advance
Click to expand...
Click to collapse
If you are trying to flash T-Mobile or AT&T bloat ware without a carrier SIM card, it will not work.
Hi. What if I have an AT&T sim card, but I'm also outside US. Not sure if the sim card is active or not.
My biggest worry was, I just had my phone factory unlocked so I can use a local sim card here in the country.
Will this work? And if it will, will my phone go back to being locked by AT&T?
Hi, I tried this process the way you have it listed and it is not working. I keep getting a device info error in Odin. Tried the newest firmware and an older version
robertj51 said:
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader. Make sure you do a clean reinstall beforehand. Everything should be off the phone.
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer cable also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet. Do not remove the SIM card during any part of this process. Leave it inserted the entire time.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port labeled in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just apparently did an update.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
Click to expand...
Click to collapse
right at the beginning using odin it threw me an error, but it's probably because I used CSC home ...? How can I verify on Samsung Note 9 if I have an unlocked bootloader ..?
Edit: He used CSC not CSC home and an older version of odin. And I have a sim from Europe and it works great.
I need help, i have a sm n960u factory unlocked at&t branded using straight talk at&t sim. I have no volte or wifi calling settings. With special code they are greyed out and provisioned. Is there any way i can fix this issue?