Hi folks.
I just installed JF's RC33radio_update_testkeys.zip *radio only* update, and now my phone says it's running TC4-RC30 with release keys.
How did that happen? What went wrong?
I still seem to have root, however.
Also, am I now at risk of receiving an automatic OTA update from T-Mobile?
cbrunner said:
Hi folks.
I just installed JF's RC33radio_update_testkeys.zip *radio only* update, and now my phone says it's running TC4-RC30 with release keys.
How did that happen? What went wrong?
I still seem to have root, however.
Click to expand...
Click to collapse
The fingerprint is a lie
cbrunner said:
Hi folks.
I just installed JF's RC33radio_update_testkeys.zip *radio only* update, and now my phone says it's running TC4-RC30 with release keys.
How did that happen? What went wrong?
I still seem to have root, however.
Click to expand...
Click to collapse
The radio update only updates well... the radio. Anyway like JF said above, the RC33 update spoofs the fingerprint (just like nearly every JF update since 1.1... )
JesusFreke said:
The fingerprint is a lie
Click to expand...
Click to collapse
Indeed. It still let me update to RC33 using the file you posted. =]
JesusFreke, I can't thank you enough for doing this for us!
I'm so thrilled.
One last question, if you don't mind. There's no risk of T-Mobile doing an OTA update since it thinks it has release keys, right? I'm sure there's not, I just wanted to double-check.
jashsu said:
The radio update only updates well... the radio. Anyway like JF said above, the RC33 update spoofs the fingerprint (just like nearly every JF update since 1.1... )
Click to expand...
Click to collapse
Yeah, I'm not sure how you managed to quote my post without it sinking in for you that I clearly understood that. See how I made "release keys" bold? That's because I was emphasizing the part the changed...
I hadn't run any JF updates after the vanilla RC30 that gave me root, so I hadn't encountered the spoofed fingerprint yet.
Posted in wrong place. Sorry
cbrunner said:
There's no risk of T-Mobile doing an OTA update since it thinks it has release keys, right?
Click to expand...
Click to collapse
This question has been asked and answered over a dozen times on this very subforum. So let's go ahead and make it a baker's dozen. Based on currently known update method, T-Mo can not differentiate a JF Android with a spoofed fingerprint and an authentic Android. Therefore T-Mo can not selectively target Dreams to update (which would be required as modified Dreams have different signing keys).
jashsu said:
This question has been asked and answered over a dozen times on this very subforum. So let's go ahead and make it a baker's dozen. Based on currently known update method, T-Mo can not differentiate a JF Android with a spoofed fingerprint and an authentic Android. Therefore T-Mo can not selectively target Dreams to update (which would be required as modified Dreams have different signing keys).
Click to expand...
Click to collapse
I understood that they couldn't selectively target them. I just wanted to make sure that it wasn't possible for my G1 to download the next OTA update like all of the others and overwrite the installed JF RC33 firmware.
So, since they're actually signed with different keys, even though it appears to be using the release-keys, I gather that the OTA update from T-Mobile would be rejected.
I understand now. Thank you, jashsu, for clearing this up for me.
Related
My G1, which has been converted to a JF ADP1.1, gave me the following popup message just now:
! A system update is available
-----------------------------
Holiday phone update 2 of 2: This is
a full system update. Your data and
settings will be preserved.
Update now Update later
I'm going to click "Update later" since I don't know exactly what this is.
I searched the XDA Dream forums for "Holiday phone" without finding anything, but if this is something previously discussed I'm sorry for the double post.
I have tried to attach a picture of the screen as well.
~Christopher
I went to Device Info, and clicked "Check for upgrade".
The result was:
Pending upgrade:
signed-holiday_devphone-ota-130444-debug.55489994.zip
Download status:
Completed (200): 45722649 of 45722649 bytes
Check-in status:
CHECKIN_SUCCESS
grenness said:
Pending upgrade:
signed-holiday_devphone-ota-130444-debug.55489994.zip
Download status:
Completed (200): 45722649 of 45722649 bytes
Click to expand...
Click to collapse
Does anyone know where in the phone file system these files go?
If I can find it, I can probably copy it to the SD card and then attach it to this thread.
~Christopher
so this update is only for ADP?
any idea what's new in it yet? or have you not updated?
i imagine it will just be RC33 for ADP, with Latitude etc.
only one way to find out
Meltus said:
so this update is only for ADP?
any idea what's new in it yet? or have you not updated?
Click to expand...
Click to collapse
I'm guessing this is for ADP only, since my phone (as far as Google knows) is an ADP (converted from a G1 using JesusFreke's ADP image) and the name of the .zip contains *devphone*.
No, I haven't proceeeded with the upgrade, I would like some other inputs from the forum first.
~Christopher
hrm, mine is saying its up to date when I hit the update checker. Guess i'll keep checking, as I would much rather stay on adp code and not run the tmobile.
this guy
has the same thing as you
http://andblogs.net/2009/01/new-adp1-images-leaked/
kash04 said:
this guy
has the same thing as you
http://andblogs.net/2009/01/new-adp1-images-leaked/
Click to expand...
Click to collapse
So it has the update for "Check for updates". Looks like it probably is the ADP1's answer to the RC33...
kash04 said:
this guy
has the same thing as you
http://andblogs.net/2009/01/new-adp1-images-leaked/
Click to expand...
Click to collapse
I appreciate the link, but JF-ADP1.1 is based off the images you linked to. Whatever the holiday update is is different.
Can you look in /cache and see if you see an update file? I'd love to get a copy. (Also, run 'logcat' and look for urls.)
I went ahead and accepted the update.
Took two reboots (one was probably the radio upgrade which I had installed several days ago), but now it's stuck on the pulsating android boot screen :-(
~Christopher
grenness said:
I went ahead and accepted the update.
Took two reboots (one was probably the radio upgrade which I had installed several days ago), but now it's stuck on the pulsating android boot screen :-(
~Christopher
Click to expand...
Click to collapse
RC33 takes -forever- to do it's first boot. On the order of 10 mins for some people.
Does 'adb logcat' show anything?
I left it on the table in front of me, I swear it took around 10 minutes before it proceeded with the boot-up, and now it seems to work fine. Has Google voice search and Latitute.
Don't know what's missing - looks like Sansdroid auto-rotate no longer works.
~Christopher
the download url is similar to rc OTA updates , just need to replace filename:
Code:
https://android.clients.google.com/updates/signed-holiday_devphone-ota-130444-debug.55489994.zip
I am the one that made a post on http://andblogs.net/2009/01/new-adp1-images-leaked/
I installed both updates and now have Google Latitude en Voice Search available. I tried to look at logcat but the information was not there anymore.
I made a post on the Google Android forum (http://groups.google.com/group/android-developers/browse_thread/thread/4fc696bd66b988f6#) and got responses from JBQ. But I doesn't make sense to me. I want to know if this update is an official one.
Is it possible to use this update directly on a ADP 1 with 1.0 image?
A friend of mine has not updated his ADP to 1.1 yet.
jcdekoning said:
I am the one that made a post on http://andblogs.net/2009/01/new-adp1-images-leaked/
I installed both updates and now have Google Latitude en Voice Search available. I tried to look at logcat but the information was not there anymore.
I made a post on the Google Android forum (http://groups.google.com/group/android-developers/browse_thread/thread/4fc696bd66b988f6#) and got responses from JBQ. But I doesn't make sense to me. I want to know if this update is an official one.
Click to expand...
Click to collapse
It is, it just might not be released yet.
cannot upgrade from JF1.41 RC33
after verifying update package...
message: failure at line 4
assert getprop ("ro.bootloader") =="0.95.0000"
Installation aborted.
Which image do I need to be able to flash?
endolin said:
after verifying update package...
message: failure at line 4
assert getprop ("ro.bootloader") =="0.95.0000"
Installation aborted.
Which image do I need to be able to flash?
Click to expand...
Click to collapse
It doesn't like the bootloader test. (And you won't be able to go from rc33 to adp1.1 anyway, since the userdata is different.)
If you are comfortable with the signing process, you can unpack it, remove the bootloader line from META-INF/com/google/....../update-script and resign it and it'll work. Alternately, give me a little time and I'll post one with no checks.
thanks for your quick reply.
i'm not familiar with the signing process, therefore I'd be glad to see a modified
release from you.
Disconn3ct said:
It doesn't like the bootloader test. (And you won't be able to go from rc33 to adp1.1 anyway, since the userdata is different.)
If you are comfortable with the signing process, you can unpack it, remove the bootloader line from META-INF/com/google/....../update-script and resign it and it'll work. Alternately, give me a little time and I'll post one with no checks.
Click to expand...
Click to collapse
http://andblogs.net/2009/02/new-adp1-update-official-with-google-voice-and-more/ has the download that does no system checks. So anyone should be able to apply it as update.zip
FYI:
https://android.clients.google.com/updates/partner/signed-kila-ota-148830.de6a94ca.zip
Not 100% sure if this works. I'm running 6.1H and tried to copy over the IM and MyFaves .apk, and they did not install.
Edit 1:
Tried a adb push of the 2 IM .apks, and they didn't install.
mine is coming back: no signature, verification failed, installation aborted
jaaronmoody said:
mine is coming back: no signature, verification failed, installation aborted
Click to expand...
Click to collapse
I think you have to unroot to install an ota update from Google.
jaaronmoody said:
mine is coming back: no signature, verification failed, installation aborted
Click to expand...
Click to collapse
That's because you're using JF's modded version and that zip is the official version.
you need to wait for him to sign and mod it.
everyone else just enjoy the link and stop posting new threads of 'us cupcake found', I've counted at least 3.
thanx guys
So JF will create a modded version of this eventually right?
Confirmed working. Just installed update.zip onto a non-rooted RC30.
Firmware Version 1.5
Baseband version 62.50S.20.17H_2.22.19.26I
Kernel Version 2.6.27-00393-g6607056
Build Number CRB43
I have the JF ADP 1.5 now and I miss the translucent drawer (slide out launcher) from 1.4. Is the official 1.5 drawer opaque or translucent?
revwillie said:
I have the JF ADP 1.5 now and I miss the translucent drawer (slide out launcher) from 1.4. Is the official 1.5 drawer opaque or translucent?
Click to expand...
Click to collapse
That build made me go back to the official version. I Couldn't stand it.
So JF will create a modded version of this eventually right?
Click to expand...
Click to collapse
There's no reason for him to stop now
revwillie said:
I have the JF ADP 1.5 now and I miss the translucent drawer (slide out launcher) from 1.4. Is the official 1.5 drawer opaque or translucent?
Click to expand...
Click to collapse
It's got a carbon fiber background, i go back and forth on whether it looks good or not
stuff said:
So JF will create a modded version of this eventually right?
Click to expand...
Click to collapse
update-jf1.5-usa-unofficial.zip
works fine here
th4r said:
update-jf1.5-usa-unofficial.zip
works fine here
Click to expand...
Click to collapse
What is this?
th4r said:
update-jf1.5-usa-unofficial.zip
works fine here
Click to expand...
Click to collapse
Did JF already mod the T-Mobile Official Release of 1.5????
Asking because JF Updater isn't showing any updates to download at this time
The "Cupcake" that JF modded was the ADP build.
Hmm. It's from here: http://andblogs.net/2009/05/tmobile-usa-cupcake-url/, but it wasn't posted by JF, and JF's blog (http://jf.andblogs.net/) has not been updated.
metallicant said:
Did JF already mod the T-Mobile Official Release of 1.5????
Asking because JF Updater isn't showing any updates to download at this time
Click to expand...
Click to collapse
no .. not JFs work .. someone just signed his initials .. falsely reported .. it should really be named something different
i dont know its not loading for me at all
I have an unrooted phone, but I loaded the us cupcake and its working fine. Only problem I see is the phone isnt as fast
I think it's faster. I've been using JFv1.5 on my white phone. Unrooted my black one to try this out. Seems alright. No new widgets...ala myFavs...which is what I would have liked to see since I've been waiting so darn long. No "spare parts" either. I kind of liked the option to make the text smaller and was looking forward to a working version of it. Obviously, they couldn't figure it out either.
I just bricked my phone.
I follow the root tut.
Then, intead of installing the RC33-signed, I tried to install the OTA Cupcake.
Got the "unsigned," issue.
I think I looked and tried to unroot by way of reflashing RC29, but bricked it.
Stuck at G1 screen.
-bZj
UPDATE: Anyone who broke 4G using unrevoked, there is no fix yet, sorry.
I've been getting alot of questions and comments about this...
Why is this different from others?
Does not flash Recovery
Does not Flash Boot
Radio is a FULL image and not a diff
YOU MUST HAVE ALL THE 1.47.651.1 SYSTEM FILES FOR WIMAX! (Link Removed, Read)
You break your 4G being stupid, not my fault.
This is a full IMG, wont overwrite recovery or anything else, just radio or wimax!
Only requirement is to have the new system files, don't even need the last radio.
RADIO: Torrent or Direct Download
WIMAX: Torrent or Direct Download
*Disclaimer: These files work for me, if you use them properly they should work properly. I'm just not responsible for damage in any form.
If you want to support me, just check out my various websites, and spread word!
On a side note, I say "must" for the new system files as the new WiMax will break without.
I don't know about radio, but even if it does work, it's not good practice to use with older system files.
Baseband Requirement
Does this flash require that you have a certain baseband before flashing? I am running a stock rooted 1.47 rom that Caulkin posted and am still running the stock baseband radio...I have not updated to the 5.31 that toast posted yet.
Do I need to flash 5.31 radio before flashing this? Or I am ok using my stock .24 radio?
Do I need to reflash my recovery_img afterwards?
hecklbrg said:
Does this flash require that you have a certain baseband before flashing? I am running a stock rooted 1.47 rom that Caulkin posted and am still running the stock baseband radio...I have not updated to the 5.31 that toast posted yet.
Do I need to flash 5.31 radio before flashing this? Or I am ok using my stock .24 radio?
Do I need to reflash my recovery_img afterwards?
Click to expand...
Click to collapse
Ah yes, I knew I forgot to say something...you do need to latest radio.
Main post updated!
Like I said, radio may not fully update...but it doesn't break anything and it will update WiMax
I'm guessing that this does NOT require that you use Caulkin's Wimax fix first as well?
hecklbrg said:
I'm guessing that this does NOT require that you use Caulkin's Wimax fix first as well?
Click to expand...
Click to collapse
I'm not aware of any "fix" from Caulkin, but if you referring to his WiMax update, no you don't need it.
I'm honestly surprised nobody posted anything like this before me that didn't include the damn recovery.
It's annoying to have to flash recovery when it's not needed.
So I would have to flash Calkulin's 1.47.651.1 on top of DC 3.2.x then this radio file?
Neotelos_com said:
I'm honestly surprised nobody posted anything like this before me that didn't include the damn recovery.
It's annoying to have to flash recovery when it's not needed.
Click to expand...
Click to collapse
My sentiments exactly.
Anywho has anyone gotten this working yet? I'm not one for subjecting my phone to be a guinea pig when bricking is a possible side effect.
Does any ROM based on the 1.47.651.1 update work with this or does it have to be the stock ROM?
Neotelos_com, did your Baseband version change to reflect this update? Mine hadn't...
good stuff, gonna look into this...
jwegman said:
Neotelos_com, did your Baseband version change to reflect this update? Mine hadn't...
Click to expand...
Click to collapse
I did check and it seems it did not.
I'll look into this, I personally would like the new radio.
I've done it!
I don't know how but I am the first person to have the full new radio image!
WiMax update will be added back in soon!
Neotelos_com said:
I've done it!
I don't know how but I am the first person to have the full new radio image!
WiMax update will be added back in soon!
Click to expand...
Click to collapse
is this based off of the OTA released yesterday which was 21.4 MB or the OTA released today at 30.2 MB ?
im still grabbing the 30.2 MB OTA released today over my slow 3g right now so i haven't had a chance to compare the OTA .zip from yesterday to the one today.
joeykrim said:
is this based off of the OTA released yesterday which was 21.4 MB or the OTA released today at 30.2 MB ?
im still grabbing the 30.2 MB OTA released today over my slow 3g right now so i haven't had a chance to compare the OTA .zip from yesterday to the one today.
Click to expand...
Click to collapse
I wasn't aware of a new OTA today, these would be based off yesterdays.
It's possible Sprint just switched from a diff for the radio, that would cause about 10mb size difference....in witch this will be the same thing.
No guarantees though, until we find out.
why is it a MUST that we use the .47 system files?
KERKEDAGAIN said:
why is it a MUST that we use the .47 system files?
Click to expand...
Click to collapse
It's been said WiMax wont work without.
I don't know about radio...but you can go ahead and try the radio.
It can always be reverted back using toasts old radio update.zip
It's just good practice to use the system files that these were designed for.
I'm still running DamageControl as a base (with .47), it didn't need a clear for me.
ah, ok..i shall report back w/ my findings!
Radio flashed ok. Tried flashing the WiMax zip and it failed and said it couldn't find the radio.diff?
I did notice the wimax zip has the update-script still looking for the radio.diff to update. This probably needs revised?
grkfire said:
Radio flashed ok. Tried flashing the WiMax zip and it failed and said it couldn't find the radio.diff?
Click to expand...
Click to collapse
haha, my bad, I will have it fixed asap
Bought my GS4 yesturday, this morning around 10am i got an OTA that was about 28mb. Not sure what that OTA did because i cant find any change log anywhere or anybody else talking about it...does anybody know anything?
Build Number is JDQ39.I337MVLUAMDL
On Rogers in Canada
You should probably have put down Rogers on the thread title. I didn't receive anything but I am no AT&T. But one more thing, I was talking in this other thread with the Canadian carrier guys. Is your Contacts and phone app white or black / blue?
Even though I'm on AT&T, I am happy for Rogers customers. Can anyone elaborate on what this update does? Hopefully it addresses the lag?
On US AT&T and no OTA. I wouldn't download any OTA's though just in-case they address the hacked bootloader.
@geoldr: The OTA was launched by Samsung globally.
Good to see you again P-Pat! I got the notification, but rooted before installing in case there was patch to stop root. After I tried to install and it said my phone has been modified and updates are not available. I am now searching to figure out how to install this....
For news on the update, see here: http://gadgets.ndtv.com/mobiles/news/samsung-galaxy-s4-receives-first-software-update-362298
David Dee said:
@geoldr: The OTA was launched by Samsung globally.
Good to see you again P-Pat! I got the notification, but rooted before installing in case there was patch to stop root. After I tried to install and it said my phone has been modified and updates are not available. I am now searching to figure out how to install this....
For news on the update, see here: http://gadgets.ndtv.com/mobiles/news/samsung-galaxy-s4-receives-first-software-update-362298
Click to expand...
Click to collapse
I'm a bit confused at this. Even if Samsung releases an update, we won't get it instantly because the carriers have to test it out and everything right? Hasn't this always been the case or am I missing something?
geoldr said:
I'm a bit confused at this. Even if Samsung releases an update, we won't get it instantly because the carriers have to test it out and everything right? Hasn't this always been the case or am I missing something?
Click to expand...
Click to collapse
From what I have read, so far it has been launched on Sprint, Rogers and the international version. I am sure AT&T will come soon. Samsung launches the updates, but the carriers distribute them...that is why Android version updates have different timing for different carriers.
David Dee said:
From what I have read, so far it has been launched on Sprint, Rogers and the international version. I am sure AT&T will come soon. Samsung launches the updates, but the carriers distribute them...that is why Android version updates have different timing for different carriers.
Click to expand...
Click to collapse
I see. Now just to find out what this update does.
For now I will be staying away from it. I don't want anything locking up the chance of unlocking the bootloader.
geoldr said:
I see. Now just to find out what this update does.
For now I will be staying away from it. I don't want anything locking up the chance of unlocking the bootloader.
Click to expand...
Click to collapse
This! I just rooted my phone this morning finally and froze the AT&T Software Update and FWUpdater. Should protect me from the OTA when it comes over to AT&T correct?
Thermalwolf said:
This! I just rooted my phone this morning finally and froze the AT&T Software Update and FWUpdater. Should protect me from the OTA when it comes over to AT&T correct?
Click to expand...
Click to collapse
Yeah. I dont think the firmware installs without the user accepting it anyways.
geoldr said:
Yeah. I dont think the firmware installs without the user accepting it anyways.
Click to expand...
Click to collapse
Somewhere I read they can force push security updates onto the phone without you even having to accept it. This is something I think they would do over the bootloader to prevent people from stopping the patch.
Thermalwolf said:
This! I just rooted my phone this morning finally and froze the AT&T Software Update and FWUpdater. Should protect me from the OTA when it comes over to AT&T correct?
Click to expand...
Click to collapse
It will save you from an annoying notification, but you have to click to initiate the install. Also, if you are are rooted, the ota won't work. You are safe.
Thermalwolf said:
Somewhere I read they can force push security updates onto the phone without you even having to accept it. This is something I think they would do over the bootloader to prevent people from stopping the patch.
Click to expand...
Click to collapse
Really? Well in that case I need to root and block those services. I've been waiting for an unlock and then was gonna root it.
David Dee said:
It will save you from an annoying notification, but you have to click to initiate the install. Also, if you are are rooted, the ota won't work. You are safe.
Click to expand...
Click to collapse
I figured with this method of root it wouldn't effect the update since we weren't messing with the firmware.
Thermalwolf said:
I figured with this method of root it wouldn't effect the update since we weren't messing with the firmware.
Click to expand...
Click to collapse
This is Sammy's doing, seems like they are taking a harder line this time around. I used the exact same method on my TF300 and OTAs work like a charm.
geoldr said:
You should probably have put down Rogers on the thread title. I didn't receive anything but I am no AT&T. But one more thing, I was talking in this other thread with the Canadian carrier guys. Is your Contacts and phone app white or black / blue?
Click to expand...
Click to collapse
its black blue
David Dee said:
@geoldr: The OTA was launched by Samsung globally.
Good to see you again P-Pat! I got the notification, but rooted before installing in case there was patch to stop root. After I tried to install and it said my phone has been modified and updates are not available. I am now searching to figure out how to install this....
For news on the update, see here: http://gadgets.ndtv.com/mobiles/news/samsung-galaxy-s4-receives-first-software-update-362298
Click to expand...
Click to collapse
Thanks Bud!! Nice to see you too. On the screenshot you posted, it doesnt match up to mine. It was 28mb and it didnt have any mention of ''improved stability''. Im really wondering what that was, maybe the canadien version of that european release. Also the build number doesnt match up
geoldr said:
I'm a bit confused at this. Even if Samsung releases an update, we won't get it instantly because the carriers have to test it out and everything right? Hasn't this always been the case or am I missing something?
Click to expand...
Click to collapse
not always, i received 2 updates on the GS3 that were released from sammy and did not go through carrier testing, unless they did it so uniformly that it didnt seem like it, but then again, telus and bell got it the same day rogers did, but those updates were stability and securtiy related, they didnt bring any features, so i guess it really depends on what the updates changes
This link confirms what David Dee was saying, it also matches my build number and size of update
http://www.androidpolice.com/2013/0...iving-its-first-ota-update-build-l720vpuamdl/
I wouldnt worry too much about OTAs anymore since AdamOutler has an Odin flashable current firmware up in the dev forums.
polish_pat said:
its black blue
Click to expand...
Click to collapse
Now see thats weird. AT&T version everything is white. Messaging app is white dialer is white contacts are white.
I wonder why...
David Dee said:
This is Sammy's doing, seems like they are taking a harder line this time around. I used the exact same method on my TF300 and OTAs work like a charm.
Click to expand...
Click to collapse
So what you're saying is I can still install OTA's if I rooted with motochopper? But as long as I have the ota update files frozen I shouldn't have to worry?
Thermalwolf said:
So what you're saying is I can still install OTA's if I rooted with motochopper? But as long as I have the ota update files frozen I shouldn't have to worry?
Click to expand...
Click to collapse
No, once rooted the otas will not work because it detects device modification.
Can anyone provide or point me in the direction of the ODIN files for the sm-f916u/u1? I have an unlocked fold 2 but want to have the AT&T features. There is a thread out there for user data but it seemingly leads to issues after installing. Thanks!!
If you read that thread closely, you can see that it was confirmed that the method does work. The misinformation came from those that improperly flashed or used the wrong file to flash to the phone which was the cause of any issues. The OP's file worked as intended. It was ashame to see others blaming the file as the cause when it was simply their own ignorance. I must note that in order to use "AT&T features", one must have more than to just have the correct software on your device. The line of service must also be correctly provisioned on the network side.
nunyabiziz said:
If you read that thread closely, you can see that it was confirmed that the method does work. The misinformation came from those that improperly flashed or used the wrong file to flash to the phone which was the cause of any issues. The OP's file worked as intended. It was ashame to see others blaming the file as the cause when it was simply their own ignorance. I must note that in order to use "AT&T features", one must make more than to just have the correct software on your device. The line of service must also be correctly provisioned on the network side.
Click to expand...
Click to collapse
Agreed...I did try it and it worked, however the update software function just doesn't seem like it is actually checking. It said checking DM server one time and then it never said it again. It was almost as if the button was mapped to say no software update. I know it wasn't that is just my perception. This was even after a clean wipe.
My Z Fold 2 is an AT&T branded device and I'm having the same issue as you. I would get the "dm initialization not ready check network or sim card" message when checking for updates from time to time. I will wait until the beginning of February and if my device hasn't received the UI 3.0 update, I plan on taking the device to ubreakifix and getting it updated.
Can I use CSC of India on a US Version (SM-F916U1)?
devwest said:
Agreed...I did try it and it worked, however the update software function just doesn't seem like it is actually checking. It said checking DM server one time and then it never said it again. It was almost as if the button was mapped to say no software update. I know it wasn't that is just my perception. This was even after a clean wipe.
Click to expand...
Click to collapse
What is your current firmware version? The reason I asked is because I was on BTK5 which isnt an update path for AT&T. I flashed back to ATHC which was orginally on my phone out of the box. Now my phone just took the last update to UI 3.0. So the phone went from ATHC -> BTJF -> BTK4 -> CTLL.
nunyabiziz said:
What is your current firmware version? The reason I asked is because I was on BTK5 which isnt an update path for AT&T. I flashed back to ATHC which was orginally on my phone out of the box. Now my phone just took the last update to UI 3.0. So the phone went from ATHC -> BTJF -> BTK4 -> CTLL.
Click to expand...
Click to collapse
I actually downloaded the Verizon Android 11 CTLL from samfrew. I did that this morning. For some reason it showed the AT&T flashscreen and I have all of the AT&T bloatware. This was coming from the latest U1 firmware. There were two Version apps on there but I was able to remove them. Everything works just fine even 5G, WIFI calling as well.
Glad to hear that you were able to get to the build that you wanted. Just a note of caution, that doing it this method will not allow you to receive future OTA from AT&T. You will need to continue to manually update to future builds.
nunyabiziz said:
Glad to hear that you were able to get to the build that you wanted. Just a note of caution, that doing it this method will not allow you to receive future OTA from AT&T. You will need to continue to manually update to future builds.
Click to expand...
Click to collapse
Yep totally aware but thanks for the info. My intent is to go back to U1 unbranded when it is released.