So right now I'm staring at the bootloader of my phone and trying to figure out how to get it up to Android 4.3... and beginning to wonder if I should just give up and go with some other Android derivative, because this phone is turning out to be a very... special... little snowflake. Here are its stats as follows:
PRODUCT NAME: tuna
VARIANT: maguro
BOOTLOADER VERSION: PRIMEKK15
BASEBAND VERSION: I9250XXLH1
CARRIER INFO: none
SIGNING: production
LOCK STATE: UNLOCKED
Android Version: 4.2.1
ROM Build Number: JOP40D.I9250ZSMA1
As can be seen in this list, my bootloader doesn't match my baseband version and build, while I can't even spot my build number in the list. If possible, I would like to upgrade this thing to 4.3. My questions are: How does this kind of thing happen? Can I even update it? If so, how should I do this on a Linux box?
Relevant background information:
-> Got the phone in a wonky, broken state for a song. It was stuck on 4.02 and would reboot every 2 minutes. I did some sort of recovery on it with a Windows box, got it hooked up to wifi, and let it update until it was un-broken.
-> When I got it up to 4.2.1, it came up with the language initially set to Chinese, but it has worked for me in English for the past couple months.
-> I'm used to flashing ROMs onto pre-production devices that are set up to make the task easy, and doing it on a Windows box set up for that particular process. I'm new to messing around with the Galaxy Nexus, and I don't want to brick it because it's been a nice phone so far, and I want to keep using it.
-> Be gentle... I'm also fairly new to running Linux on my box at home.
Related
Good for everyone!!
Sorry for my google's traductor english
I mention my case to see if with the help of all I can restore the phone.
After spending hours tinkering with the phone, turn it into a paperweight and reliving me realize I can not find a way to make the phone work properly.
The phone lights up, root access and the latest Cyanogen rom installed with the corresponding recovery.
The problem is that once you put on the sim that puts you never recognized. It asks me the pin and when I try to enter the dialpad to put a sequence to know, for example, if you have a lock on (step I made when the phone had the movistar rom) or simply to know the imei, it is trying to call and not open the menus.
I do not know if discovered and can serve as something that if I go into Settings - About Phone ANRO I have the version 2.3.5, 2.6.35.7 Kernel Version-perf-CL591990root @ dell126 # 1 and build number GINGERBREAD.XWKS3 . What baffles me and maybe come around the problem is that in the field puts Base Band Version Unknown. The same if I go into state gives me no information network, imei, network status, etc..
I tried also to urge a new modem, but not for that.
Has anyone had or has the same problem?
I appreciate your help in trying to help solve the problem.
If you need any additional information, be alert to tell you.
Greetings!
I purchased a iPhone 5s clone from China a month ago. Out-of-the box i could make and receive calls, but i didn't get the mobile internet working.
Anyway, I tried rooting the device using MTK Droid Root & Tools, but the program told me it couldn't do it and linked me to this guide: hxxp://forum.china-iphone.ru/viewtopic.php?p=502084#p502084 (It's in russian, but Google Translate does a good job).
I followed the guide and successfully installed CWM and rooted, but when I booted up the phone I got nothing but "No service", and when I tried to register the phone on any mobile network it always said "Unable to connect to this network at this time".
Now this sounds like an IMEI issue to me, and stupid as I am, i didn't check the IMEI of the phone before I started the root process. If I now enter *#06# in the dialer, it displays what looks like a correct IMEI. Since it is a clone there is no physical IMEI on the device. There is one on the box and I tried changing to that but still got "No service". Again, since it's a clone, the one on the box might no be correct.
Is the problem I'm experiencing an IMEI issue, and if so, is there anything I can do?
Device information:
Hardware: Alps Mediatek MT6575
Display size: 480x800
Model: sanstar15_s006_p5_gb2
Android version: Gingerbread (It says 4.1.2, but I can tell it's Gingerbread)
You should flash modem using cwm. Search the forum for flashable modem file for your device.
Galaxy Note 2 - rooted and customized leaked 4.3 stock
At&t Galaxy note 2 - rooted stock 4.1.2
Xperia Neo L - Bootloader unlocked, rooted and customized 4.0.4 stock.
Hi all.
This is my first post and will try and make it really quick.
I recently got a Galaxy Note 5 (because their just amazing) It came with Android 6.0.1 installed and the "Software Update" section of the settings menu does nothing. I mean literally nothing. I tap "About Device" then "Software Update" and nothing happens no new screen loads or anything.
so I was looking for the OEM ROM's and this is where I ran into so much confusion. The current details the phone gives me is.
Galaxy Note 5 SM-N920F (There are no F rom's)
Build Number MMB29K.N920FTMB4DPH2
Bootloader N920TUVS6ERH1
Which lead me to believe even though their is no "F" variant, That its a T-Mobile model (No Rom's really give 100% functionality to these except the standard 7.1 from T-Mobile)
So I went to Sammobile.com to download the latest official firmware released, But the the CSC numbers don't match my device. they are all starting N920TT***** and mine starts N920FT*****. However the PDA numbers match my bootloader. So will any Note 5 T-Mobile ROM work even if the CSC numbers are different? as long as the PDA numbers are the same?
I get more confusing info from Samsung as well. The "Samsung Members" app shows my Model number as : SM-N920TZKATMB (Which again has no "F" in it, The sticker on the back of the device with the IMEI even states it as SM-N920F)
Am I making this weirdly complicated for myself? Will the US T-Mobile ROM's for android 7.1 work find I flash them with this device? (I live in the UK and the device has 100% compatibility with my network)
Also will flashing the stock 7.1 US ROM from T-Mobile re-lock the SIM ? I'm pretty sure it doesn't/Cant relock SIM to T-Mobile only, But nothings better than a professional confirming.
There is also another issue. according to "Root Checker" I have a Rooted device. But their is no Super User apps on it at all (Cant seem to even find Binaries for SuperSU when using Root File Manager), Pokémon GO fails to load which I have read could be because of the "Root Check" throwing up a positive. But no other apps fail to work at all. their all perfect even banking never even so much as an error. it is just Pokémon GO. Or has someone previously messed up rooting so it looks like it is but the files are missing and isn't really? I tried using Magisk Manager but it did nothing and I don't get any prompts for Root access when installing apps.
So Please Help Me! Thank You.
Hello,
I have an interesting case which never happened before. I have got a smartphone Alcatel 5 with Android 7.0. Sometimes when my phone is connected to the wifi the whole network stop working with the message "No internet connection" (on all connected devices). I was thinking that the problem is from the ISP, but the internet access is back when I disconnect and connect my phone and also this happened at 3 different places with 3 different routers. The solution is always the same - to reconnect my phone. The phone is with the stock build with the latest system update and not rooted.
Model number: 5086D
Android version: 7.0
Baseband version: MT6750
Kernel version: 3.18.35+
Build number: 01003
Custom build version: alps-mp-n0.mp7-V1.54.1_jhz6750.66.a.n_P72
Well it is not that big kind of issue, but I am really interested in how is that possible?
Thanks in advance!
I bought a s9+ from swappa around February. I bought my mom one from the same supplier a week ago. At first I was concerned that her's had ATT logo until I realized it would change once a tmobile sim was put in. Her's is now SW ver Tmb/Tmb/Tmb. Then I noticed she is at Android 10.0 UI ver 2.0. I am stuck at Android 9 UI ver 1.0
So It seems I was worried about the wrong phone. It is MY phone that can't get updates. My baseband is:
G965USQU7CSK6 which I believe is an ATT baseband. my SW ver is Tmb/Tmb/Att
I tried connecting to smart switch and it says I am up to date. I tried putting in an at&t sim card (that no longer is in service) and smart switch doesn't complain about anything but it still says it is up to date. Doing OTA while using At&t sim card also says I am up to date. I am CLEARLY not up to date. My last update says Nov.1, 2019.
I have used Odin before...mostly for rooting phone. I haven't rooted since the s5 ( where I could take the battery out ). Little paranoid to use Odin considering I can't take the battery out, but with good instructions I will proceed.
Any help on how to update and especially update on tmobile network would be extremely appreciated.
btw I'm in the US and my model is SM-G965U
-Craig
--UPDATE
I have researched a bit and found that it IS possible to change the firmware over to Tmobile using a patched version of Odin.
I downloaded from
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
the 3.13.3_3B_PatcheD.zip
I downloaded G965USQS7CSK3_G965UOYN7CSK3_TMB.zip
from sammobile, which is for Android 9
I would love to be able to use HOME_CSC but that may not work. I could really use some hand holding going through this process.
Is this the correct firmware? Should I be using Android 10 firmware if that is ultimately what I want? HOME_CSC or no? I notice they have the 10 version:
PDA G965USQS7DTB1
CSC G965UOYN7DTB1
as well, which is Android 10 for Tmobile. Also, knox ? will this trip the knox counter thing-a-ma-jig?
Thanks
SOLVED
cw9002 said:
I bought a s9+ from swappa around February. I bought my mom one from the same supplier a week ago. At first I was concerned that her's had ATT logo until I realized it would change once a tmobile sim was put in. Her's is now SW ver Tmb/Tmb/Tmb. Then I noticed she is at Android 10.0 UI ver 2.0. I am stuck at Android 9 UI ver 1.0
So It seems I was worried about the wrong phone. It is MY phone that can't get updates. My baseband is:
G965USQU7CSK6 which I believe is an ATT baseband. my SW ver is Tmb/Tmb/Att
I tried connecting to smart switch and it says I am up to date. I tried putting in an at&t sim card (that no longer is in service) and smart switch doesn't complain about anything but it still says it is up to date. Doing OTA while using At&t sim card also says I am up to date. I am CLEARLY not up to date. My last update says Nov.1, 2019.
I have used Odin before...mostly for rooting phone. I haven't rooted since the s5 ( where I could take the battery out ). Little paranoid to use Odin considering I can't take the battery out, but with good instructions I will proceed.
Any help on how to update and especially update on tmobile network would be extremely appreciated.
btw I'm in the US and my model is SM-G965U
-Craig
--UPDATE
I have researched a bit and found that it IS possible to change the firmware over to Tmobile using a patched version of Odin.
I downloaded from
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
the 3.13.3_3B_PatcheD.zip
I downloaded G965USQS7CSK3_G965UOYN7CSK3_TMB.zip
from sammobile, which is for Android 9
I would love to be able to use HOME_CSC but that may not work. I could really use some hand holding going through this process.
Is this the correct firmware? Should I be using Android 10 firmware if that is ultimately what I want? HOME_CSC or no? I notice they have the 10 version:
PDA G965USQS7DTB1
CSC G965UOYN7DTB1
as well, which is Android 10 for Tmobile. Also, knox ? will this trip the knox counter thing-a-ma-jig?
Thanks
Click to expand...
Click to collapse
ok, so I bit the bullet and decided to go ahead. I used
odin 3.14.1_3B_PatcheD.zip just to be sure
I made sure my phone was unlocked: yes it changes carriers if I put in different sim. When in Tmobile sim Settings->Connections->Mobile Networks->Network operators , yes it has a search networks button and it eventually comes up with other carriers so....safe to say I had unlocked phone ( but not samsung unlocked ie. SM-G965U not SM-G965U1)
I used the latest android 9 firmware. and I used HOME_CSC ( even though I did a backup with smart switch b4) Everything went smoothly, and I still have my apps and now I can get an ota security patch for it. Will write back once I am up to Android 10. oh, btw I am still at SW ver Tmb/Tmb/Att , but I've got ota updates so I don't care
cw9002 said:
ok, so I bit the bullet and decided to go ahead. I used
odin 3.14.1_3B_PatcheD.zip just to be sure
I made sure my phone was unlocked: yes it changes carriers if I put in different sim. When in Tmobile sim Settings->Connections->Mobile Networks->Network operators , yes it has a search networks button and it eventually comes up with other carriers so....safe to say I had unlocked phone ( but not samsung unlocked ie. SM-G965U not SM-G965U1)
I used the latest android 9 firmware. and I used HOME_CSC ( even though I did a backup with smart switch b4) Everything went smoothly, and I still have my apps and now I can get an ota security patch for it. Will write back once I am up to Android 10. oh, btw I am still at SW ver Tmb/Tmb/Att , but I've got ota updates so I don't care
Click to expand...
Click to collapse
I am now at the same baseband version as my mom. Everything worked perfectly. I suggest you go with the least change possible to get to the point that you are able to do OTA updates. For me this was going to the latest Android 9 that they had at sammobile since I was on Android 9 and going with the Tmobile version. I hear the carrier doesn't even matter these days, but I decided I wanted to make sure it was Tmobile compatible so I chose the Tmobile version from sammobile. Happy trails to you in your endeavors. Hopefully you can learn something from mine.
Hey, I really want to thank you for this! I had the same issue and was exploring similar solutions. After several days of researching alternate plans, I was about to give it up as too risky until I found your post - by googling for hints: "SW ver. TMB/TMB/ATT"! You helped me take the dive, and I'm now happily past having a second-hand S9 (sm-g960u) that wouldn't do an OTA update. After a flawless flash, my first OTA request got me to Android 10, (UI 2). now I have a follow-up update scheduled for the wee hours. (And, yes, I'm still at "TMB/TMB/ATT".)
Perhaps like you, I started by investigating the possibility of flashing the UNLOCKED ("U1") firmware. After learning it was possible with the _patchedD Odin, it still scared me enough that I decided on a more conservative approach and followed your exact advice. I especially appreciated your plan to flash NOT the latest update, but the last Android 9 TMB update. That turned out to correspond to the ATT version on my phone, making TMobile either unable or unwilling to offer an OTA update.
History: This is my third used S9. While all were sold as UNLOCKED, only the first had the "U1" model suffix (SM-g960u1). When the second one booted up as a TMobile phone, I felt tricked - but also lucky that I got the right carrier. That's when I learned about the difference in model numbers. As you noted the U1 firmware is factory unlocked - attached to no carrier. When my third phone booted up with a Verizon greeting I figured I could be facing trouble - even though it accepted my TMB sim card.
The seller explained to me that my phone was part of a batch of ATT phones, all "SIM unlocked" using a Verizon sim card. I think sellers of phones with claims to be unlocked should be required to specify whether FACTORY or SIM unlocked.
Hope this great contribution of yours will continue to help others.