Hey all,
Be careful converting your devices. Due to misreading a response I have no data or phone calls, and I have tonnes of experience with roms/rooting/etc so this CAN happen to anyone, no matter how unlikely..
At any rate, that is my current dilemma. If someone could post an xt-1097 modem or a stock firmware it would be much appreciated!
Just look at: http://motofirmware.com/files/category/8-victara/
Thank you so much ( new to Motorola ). I will check this out. Not seeing my carrier specifically but it is definitely a place to start - and likely solve my problem.
Related
I recently purchased a used droid 4 on ebay. Unfortunately it has been upgraded to the OTA release of ICS 4.04. Anyone working on lifting the simlock associated with the version of the bootlocker included with ICS (I'm assuming the bootloader is the origin of this simlock but technically I could be wrong)? Or is it a lost cause because it is signed? I know it's written to protected ram so any workaround would be nontrivial but does anyone have any possible exploit ideas? Motorola is unlocking a couple other models that they have out. Would petitioning them to include the droid 4 in their list of unlockable devices be a surefire path to getting the simlock lifted? Or should I consider this a lost cause and return my droid 4 to the ebay ether?
If anyone is considering working on this issue I would be more than glad to contribute. While I'm no Android expert I have a decent understanding of the OS and work in command line Linux for a living so I'd be glad to help. The selection of qwerty phones today is beyond attrocious.
One last thought. Is the idea of spoofing the carrier a possibility?
Sent from my SGH-T839 using Tapatalk
Hi blackstar,
So, I recently got a Droid 4 off of CraigsList that I wanted to use on StraightTalk, but found out that what I had perceived (that 2G/Edge was working on GSM North America) was incorrect.
They're not completely sure WHERE it's broken at the moment as far as SIM lock. Some have suggested it might be baked in the ROM -- but more than likely it is built into the modem.
Here have been some stabs at it -- and what to do in regards to getting the modem setup/altered.
http://forum.xda-developers.com/showthread.php?t=1916869
A thought, though -- since we have SafeStrap and Root, doesn't that let us essentially bypass the bootloader in some ways? My understanding is that the bootloader was required to boot the device to a "correct" image and lock the load to Motorola's firmware, but SafeStrap/root gave us access to actually overwrite the RAM/memory and replace the existing kernel with a new one for the chance at custom ROMs. So, I'm not entirely sure it has to do with the bootloader.
To me, it seems like something that's potentially baked into their ROM or in the modem firmware. If it's in the modem firmware, it's a matter of figuring out what keys/values need to be adjusted and then run it. There have been talks about AT&T getting the Photon Q (Asanti) -- rumors that were back around April of this year... but we have yet to see it there and no news about it showing up anytime soon. Not sure if they scrapped the keyboard and then shipped it as a different device.
I would imagine that if we can have the lowest level debug logging enabled and plug in an American SIM, you might be able to figure out what is breaking. Not sure how low logcat can go...
That's my understanding of the current situation, from a programmer's point of view (though I don't code for Android). Spoofing might be interesting -- but if it's locked at the radio firmware, I don't think spoofing can adjust the frequencies. But more power to you if you can figure it out (and force me to find ANOTHER Droid 4, haha).
Good luck! Definitely talk with the OP of the Topic I sent you, since s/he has a pretty deep interest in this as well.
OH, and one more thought -- there was a thought to grab an AT&T version of the Bionic and Verizon version, wherein they had the same radios, but different firmware, and do a diff on them to figure out if some settings had changed, and then potentially patch that into the D4. That might be a good strategy, but that would require us to get dumps from a few different people -- something you might be able to facilitate if you guys all work together.
One final thought -- is there any way we could have a sticky'd topic for people to post their findings, so we don't have to keep scanning and finding this?
Much thanks terinfire.
Let me start off by saying I don't have any definitive information with regards to any of the good questions you posed but if I find out anything I'll be sure to update the thread.
I spent a good chunk of the weekend trying to educate myself on the situation. From what I understand (anyone feel free to correct me or point me to the appropriate thread if I'm completely reinventing the wheel), it seems like it comes down to two most likely scenarios. Either Verizon added an MCC/MCN lock in the baseband when pushing out the OTA ICS release or they placed a restriction in the radio interface layer (RIL) of the ICS ROM. My research hasn't quite enabled me to determine which scenario is more likely. My unscientific intuition (and wishful thinking) is that the restriction is in the ROM somewhere in the RIL (if that makes any sense, still learning the Android OS architecture).
I will post what I've mentioned above in the the forum you mentioned; hopefully I can garner an audience. I will also look into getting a sticky topic created.
Not too sure how to implement any of my intuitions noted above with regards to this problem but I will try and learn as it goes.
One more note - so it is claimed that the Samsung Galaxy III for Verizon can be unlocked to use domestic GSM carriers. I've found no confirmation. (https://plus.google.com/103583939320326217147/posts/b7JbBKjJVSQ)
Pertinent links I came across in my research that may be useful:
MCC/MCN Codes: http://en.wikipedia.org/wiki/Mobile_Network_Code
Radio Interface Layer: http://en.wikipedia.org/wiki/Radio_Interface_Layer, http://www.kandroid.org/online-pdk/guide/telephony.html
RIL Header: https://code.google.com/p/linux-on-android/source/browse/radio/headers/ril.h
Qualcomm MDM660Device Specification: http://www.scribd.com/doc/54154049/...odem-Device-Specification-Advance-Information
There is to my knowledge a 4.4.2 rom out, though it's only available for the non AT&T brand s4 active due to the lack of a bootloader, unless I read it wrong which I may have due to being a bit tired. I know that there is safestrap for AT&T because I have it and have been able to relocate the post, so could someone perhaps explain to me the full issue? I'm fairly knowledgeable to a bit of all this but I'd hardly call myself experienced. Don't feel the need to speak to me as if I were five though, if worse comes to worse I'll ask you to elaborate
Nicknakin said:
There is to my knowledge a 4.4.2 rom out, though it's only available for the non AT&T brand s4 active due to the lack of a bootloader, unless I read it wrong which I may have due to being a bit tired. I know that there is safestrap for AT&T because I have it and have been able to relocate the post, so could someone perhaps explain to me the full issue? I'm fairly knowledgeable to a bit of all this but I'd hardly call myself experienced. Don't feel the need to speak to me as if I were five though, if worse comes to worse I'll ask you to elaborate
Click to expand...
Click to collapse
The issue is that the i537 has a locked bootloader. The bootloader checks the signature of the kernel, so if the signatures don't match, the flash of the new kernel will fail. All of these pieces have been signed by Samsung, so without their key there's nothing we can do. The i9295 does not have this restriction so the can flash anything they want.
Hey everyone,
Just picked up a AT&T note 3 here in Ireland. Phone is practically new but I have straight away noticed some problems.
First of all how can people live with the phone been destroyed by bloatware and all that other stuff..
So I'm looking to see if it's possible for me to root it and flash a standard samsung image?
I see kitkat update is available but when I check for updates it says there is none, is something blocking me receiving the update here in Ireland?
I'm having the gps problem and hope it's not a hardware problem, is there a fix that allows it to lock on to satelites instead of constantly searching for GPS??
Thanks in advance..
28 views and not one comment.... I know theres a time difference but come on lmao
Smokie365 said:
Hey everyone,
Just picked up a AT&T note 3 here in Ireland. Phone is practically new but I have straight away noticed some problems.
First of all how can people live with the phone been destroyed by bloatware and all that other stuff..
So I'm looking to see if it's possible for me to root it and flash a standard samsung image?
I see kitkat update is available but when I check for updates it says there is none, is something blocking me receiving the update here in Ireland?
I'm having the gps problem and hope it's not a hardware problem, is there a fix that allows it to lock on to satelites instead of constantly searching for GPS??
Thanks in advance..
Click to expand...
Click to collapse
It might help if you gave a little more information and also searched. As for information, what ROM does your phone currently have? Are you sure its an AT&T Note and not an international note? What chipset do you have? You may be in the wrong forum as the international note has its own forum and flashing from one to the other can and will cause bad things to happen.
If you are on an AT&T note, there is a 4.4.2 update that only recently was able to be rooted. There are bootloader issues, so if you are on an older ROM, you might not want to update.
In addition, searching might help quite a bit as well. For example, there is a thread on the first page discussing the GPS issues with several suggested fixes. (http://forum.xda-developers.com/showthread.php?t=2612757)
There are also people who say the 4.4.2 update fixed the GPS issues and those who say it didn't. As for debloating, there are several threads talking about apps to freeze (using Titanium if you are rooted) as well as a thread from Walter.white that lists an extensive amount of programs and files to delete.
That's the long answer. The short answer is read and search and then ask questions giving as much information about your software and circumstances as possible. The likelihood of getting an answer is much greater that way.
Congratulations on getting the best phone out there!
ptgptg said:
It might help if you gave a little more information and also searched. As for information, what ROM does your phone currently have? Are you sure its an AT&T Note and not an international note? What chipset do you have? You may be in the wrong forum as the international note has its own forum and flashing from one to the other can and will cause bad things to happen.
If you are on an AT&T note, there is a 4.4.2 update that only recently was able to be rooted. There are bootloader issues, so if you are on an older ROM, you might not want to update.
In addition, searching might help quite a bit as well. For example, there is a thread on the first page discussing the GPS issues with several suggested fixes. (http://forum.xda-developers.com/showthread.php?t=2612757)
There are also people who say the 4.4.2 update fixed the GPS issues and those who say it didn't. As for debloating, there are several threads talking about apps to freeze (using Titanium if you are rooted) as well as a thread from Walter.white that lists an extensive amount of programs and files to delete.
That's the long answer. The short answer is read and search and then ask questions giving as much information about your software and circumstances as possible. The likelihood of getting an answer is much greater that way.
Congratulations on getting the best phone out there!
Click to expand...
Click to collapse
First of all thank you for taking the time to reply with as much info as possible.
It is a at&t phone because it boots up with the at&t logo and I have checked the code ect. I have attached a screen shot with some details if you don't mind having a look. I have successfully rooted the phone and installed supersu so I should be at the stage to flash roms? If I had the international version I don't think I would be asking so many questions as I would just go ahead and do it.
I just don't want to make a mistake as I'm not sure what exactly is the difference between at&t versions of phones. Is the hardware different?
Thanks again
Good evening XDA community!
It's been a while since I've been active on the forums, and I'm back with a couple questions. I've historically been an HTC guy, but my last few phones have been branching out. After my Sensation and Evo3D, my wife and I decided to see what all the Samsung hoopla was about and got S4s. Terrible decision. I bought Oneplus Ones out of pocket to replace the Samsung crap, and they have been great phones. Due to some new geographical and housing circumstances, we are able to once again be Tmo customers and need wifi calling (no signal inside our house). Although our Oneplusses work great on Tmo's network, they do not have the ability to use wifi calling (that I was able to deduce). We opted to go with LG this time, and so here we are. I've done some preliminary searching, however I know that info can become outdated pretty quick in some cases and I'm looking to ensure I'm finding up to date info before I move forward.
Our phones as they are out of the box:
LG-H811
Baseband: MPSS.BO.2.5.c3-00109-M8992FAAAANAZM-1
Kernel: 3.10.84
Build: MRA58K
Software Version: H81120i
1) I've never seen the OEM unlock option in the developer menu before. I see that this is part of the rooting process, but can someone put in simple terms what this does? Is it exactly what it sounds like (carrier unlock)?
2) This thread appears to be the proper (only?) method to unlock the bootloader and root the phone, please confirm or point me in the right direction. http://forum.xda-developers.com/tmobile-g4/general/how-to-unlock-bootloader-flash-twrp-t3344421
3) I don't think rooting and putting a new rom on will break wifi calling, but I'd like to be sure, please confirm.
4) Is the CM13 at this thread stable? (http://forum.xda-developers.com/g4/development/rom-cyanogenmod-13-0-t3243588) I've always preferred Cyanogenmod, but their website says it's still in nightly phase. If stable, does this have Wifi calling capability?
Thanks in advance for all the help.
jdelforge5684 said:
Good evening XDA community!
It's been a while since I've been active on the forums, and I'm back with a couple questions. I've historically been an HTC guy, but my last few phones have been branching out. After my Sensation and Evo3D, my wife and I decided to see what all the Samsung hoopla was about and got S4s. Terrible decision. I bought Oneplus Ones out of pocket to replace the Samsung crap, and they have been great phones. Due to some new geographical and housing circumstances, we are able to once again be Tmo customers and need wifi calling (no signal inside our house). Although our Oneplusses work great on Tmo's network, they do not have the ability to use wifi calling (that I was able to deduce). We opted to go with LG this time, and so here we are. I've done some preliminary searching, however I know that info can become outdated pretty quick in some cases and I'm looking to ensure I'm finding up to date info before I move forward.
Our phones as they are out of the box:
LG-H811
Baseband: MPSS.BO.2.5.c3-00109-M8992FAAAANAZM-1
Kernel: 3.10.84
Build: MRA58K
Software Version: H81120i
1) I've never seen the OEM unlock option in the developer menu before. I see that this is part of the rooting process, but can someone put in simple terms what this does? Is it exactly what it sounds like (carrier unlock)?
2) This thread appears to be the proper (only?) method to unlock the bootloader and root the phone, please confirm or point me in the right direction. http://forum.xda-developers.com/tmobile-g4/general/how-to-unlock-bootloader-flash-twrp-t3344421
3) I don't think rooting and putting a new rom on will break wifi calling, but I'd like to be sure, please confirm.
4) Is the CM13 at this thread stable? (http://forum.xda-developers.com/g4/development/rom-cyanogenmod-13-0-t3243588) I've always preferred Cyanogenmod, but their website says it's still in nightly phase. If stable, does this have Wifi calling capability?
Thanks in advance for all the help.
Click to expand...
Click to collapse
1.to unlock bootloader you need special key lock.bin from LG..
not sure how i got mine locked. ... why. because of the bootloop issue.. and unlocking bootloader will void warranty so says LG on their website..'
2.like i said never tried unlocking. am itching to..
3. i think as long as you are in a stock based rom.. not
aosp or CM youll have wificalling.
4. cm is nice but alot of bugs not good camera quality.. i would only go CM if i ever wanted to try new android version.. why go CM when you get MM.?
jdelforge5684 said:
Good evening XDA community!
It's been a while since I've been active on the forums, and I'm back with a couple questions. I've historically been an HTC guy, but my last few phones have been branching out. After my Sensation and Evo3D, my wife and I decided to see what all the Samsung hoopla was about and got S4s. Terrible decision. I bought Oneplus Ones out of pocket to replace the Samsung crap, and they have been great phones. Due to some new geographical and housing circumstances, we are able to once again be Tmo customers and need wifi calling (no signal inside our house). Although our Oneplusses work great on Tmo's network, they do not have the ability to use wifi calling (that I was able to deduce). We opted to go with LG this time, and so here we are. I've done some preliminary searching, however I know that info can become outdated pretty quick in some cases and I'm looking to ensure I'm finding up to date info before I move forward.
Our phones as they are out of the box:
LG-H811
Baseband: MPSS.BO.2.5.c3-00109-M8992FAAAANAZM-1
Kernel: 3.10.84
Build: MRA58K
Software Version: H81120i
1) I've never seen the OEM unlock option in the developer menu before. I see that this is part of the rooting process, but can someone put in simple terms what this does? Is it exactly what it sounds like (carrier unlock)?
2) This thread appears to be the proper (only?) method to unlock the bootloader and root the phone, please confirm or point me in the right direction. http://forum.xda-developers.com/tmobile-g4/general/how-to-unlock-bootloader-flash-twrp-t3344421
3) I don't think rooting and putting a new rom on will break wifi calling, but I'd like to be sure, please confirm.
4) Is the CM13 at this thread stable? (http://forum.xda-developers.com/g4/development/rom-cyanogenmod-13-0-t3243588) I've always preferred Cyanogenmod, but their website says it's still in nightly phase. If stable, does this have Wifi calling capability?
Thanks in advance for all the help.
Click to expand...
Click to collapse
Follow this guide.you lose wifi calling if not on stock rom.there are custom stock roms that are very good.my favorite is from turbo2012(just my opinion)that are slim and optimized.
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Its the same if you are on 20o.just follow the guide you dont need any special key from lg.
Hey guys! I have been scouting around for Note 8 help but thought it was time to join myself.
Hopefully if I am able to solve my specific problem or get my questions asked it can help someone else.
Specifically, right now, I picked up and refurbished a Samsung Galaxy Note 8 since I have one currently that is phenominal, and wanted one in the back pocket in case anything happens but it is locked to ATT, which isnt the real problem. The real problem is that it is still on Android 7.1.1 and I would like to get it to Android 9 Pie.
I am unsure of a few things like whether I need all updates between 7 and 9, or if I can jump straight to it. But things of that sort.
It sucks that its ATT locked but I feel its worse that its on old Android since I refurbed it, (fixed screen and replaced with fresh samsung battery) but its being held back in certain functional capabilities. Either way, I am a techy, not yet able to solder, but definitely able to troubleshoot my way around a Windows Blue screen of death.
Looking forward to learnin more!
MethudMann said:
Hey guys! I have been scouting around for Note 8 help but thought it was time to join myself.
Hopefully if I am able to solve my specific problem or get my questions asked it can help someone else.
Specifically, right now, I picked up and refurbished a Samsung Galaxy Note 8 since I have one currently that is phenominal, and wanted one in the back pocket in case anything happens but it is locked to ATT, which isnt the real problem. The real problem is that it is still on Android 7.1.1 and I would like to get it to Android 9 Pie.
I am unsure of a few things like whether I need all updates between 7 and 9, or if I can jump straight to it. But things of that sort.
It sucks that its ATT locked but I feel its worse that its on old Android since I refurbed it, (fixed screen and replaced with fresh samsung battery) but its being held back in certain functional capabilities. Either way, I am a techy, not yet able to solder, but definitely able to troubleshoot my way around a Windows Blue screen of death.
Looking forward to learnin more!
Click to expand...
Click to collapse
Welcome to XDA! As for updating your phone, could you please tell me your model number?
ethical_haquer said:
Welcome to XDA! As for updating your phone, could you please tell me your model number?
Click to expand...
Click to collapse
Yeah, sorry for long response time.
For the important info:
Model: SM-N950U
Android. 7.1.1
Build:NMF26X.N950USQU1AQH7
CSC: ATT
I'll monitor more closely so let me know if you need any other info
MethudMann said:
Yeah, sorry for long response time.
For the important info:
Model: SM-N950U
Android. 7.1.1
Build:NMF26X.N950USQU1AQH7
CSC: ATT
Click to expand...
Click to collapse
Alright, there are two versions of firmware available for your device. One is "branded" and has carrier bloat, whereas the other does not have carrier bloat but might have issues with VoLTE (probably not, but there is a chance). What one would you prefer? Let me know if you have any questions regarding the difference.
ethical_haquer said:
Alright, there are two versions of firmware available for your device. One is "branded" and has carrier bloat, whereas the other does not have carrier bloat but might have issues with VoLTE (probably not, but there is a chance). What one would you prefer? Let me know if you have any questions regarding the difference.
Click to expand...
Click to collapse
Thanks for the research and yes I do have questions if its not too much of an issue:
1.) Carrier bloat is like the usual and can just be deleted anyways correct?
2.) In what scenarios (in case everything was working fine with OTA updates) would the phone have downloaded a version without bloat?
3.) Would updating to the non-bloated version cause any issues since the phone is still carrier locked?
4.) Lastly, for the firmware, would I need to download multiple updates until that point or just straight to the firmware?
If not, I can research the answers as I have been on it on and off for a month with research but other than that, you're a god send.
By the way, if #1 is true, I'll just take the bloatware no doubt just to be as safe as possible.
Thanks again for all the help @ethical_haquer
Been busy researching in the Samsung Note 8 ATT threads and I was able to find the answer to number 4 in that using Full ODIN files is a complete flash and different than just an update which requires the previous updates.
The answer to number 3 from what I have seen no. The only thing is that certain features may NOT work such as VoLTE; pretty much you already answered 3 and I was literally too dumb to see that until I started writing this message. *face palm
Question 2 is pretty much inconsequential so don't worry answering that. Its was just curiosity. But for anyone who does see this possibly, my speculation is that NO, the carrier version would never download the non-carrier version. The non-branded update is for those unlocked phones that receive over-the-air (OTA) updates that were not associated with any carrier, in other words buying a phone directly from samsung's website.
For 1, I am guessing it is "Yes" since I was able to do that in the past with all my other phones. But either way it is not a make it or break it so it doesn't matter.
I have been able to find some full ODIN files for the updates I was looking for, so will be attempting my first flash soon. Will be posting all my findings to the thread I was reading just to potentially help anyone else (though rare since this device is getting real old) who has the same questions I had and I can get them up to speed without having to search everything
Just finished flashing the ATT Note 8 to and the Answer to Number 1 is that NO, you cannot Uninstall the bloatware
Again, will post all these findings to the proper thread in after completed
Sorry for the late reply! I would try installing the firmware for the SM-N950U1 (notice the 1). It should work and won't have carrier bloat.
ethical_haquer said:
Sorry for the late reply! I would try installing the firmware for the SM-N950U1 (notice the 1). It should work and won't have carrier bloat.
Click to expand...
Click to collapse
You're all good!
I may but I actually have to find one more update I am looking for (Full ODIN FILES). My daily driver note 8 is on N950USQS7DTE5 and it is a T-Mobile Version (though it bein g TMO is inconsequential at the moment. Just thought I might mention it).
That is the update I would like for ATT just so that I know there wont be any differences (or less differences) between my daily driver and this.This is me being picky at this point but isn't the point of life getting what you want? I found one update above that but different bootloader. So for whatever reason may happen, no going back.
What I currently flashed to was N950USQS3BRA8 so it's still on Android 7.1.1 but I did this just to test to the process (my first flashing). Now I am ready.
So I will look for that then flash it and update as usual
Just found, or couldnt find, that ATT has the same update so will just go with what I have. Close as I can get