Related
I read in a thread that someone lost their imei and it was suggested for them to use *2767*3855# to restore everything back to factory and reactivate the sim. I know this won't update oyur baseband to the newer editions, but it made me think about if someone bought a new phone that has the updated firmware, or somehow got their baseband/radios/kernel updated to the new version (whether through OTA or through getting a new phone), would it be possible to downgrade baseband/radio/firmware back to the previous edition since the VRLF2 version is also signed and authentic?
If it is possible to downgrade, does anyone have the dump files needed from an "older" version to do this? How would it be done, through odin or recovery, or terminal/adb (like backing up and restoring /efs partition)?
Thanks
newuser134 said:
If it is possible to downgrade, does anyone have the dump files needed from an "older" version to do this? How would it be done, through odin or recovery, or terminal/adb (like backing up and restoring /efs partition)?
Click to expand...
Click to collapse
Yep, see http://forum.xda-developers.com/showthread.php?t=1788313 for details.
The forum post has links to both the old and new modem, and full flashing instructions.
yes and I would only use the VLRF2 since it does not have the dumbed down search...the update is a downgrade!! If you like you can upgrade to the VRLG1 radio/modem and stay on the VRLF2 software.
droidstyle said:
yes and I would only use the VLRF2 since it does not have the dumbed down search...the update is a downgrade!! If you like you can upgrade to the VRLG1 radio/modem and stay on the VRLF2 software.
Click to expand...
Click to collapse
True, although you can just get the full featured googlequicksearchbox APK and replace the new one with it.
pjamv5 said:
True, although you can just get the full featured googlequicksearchbox APK and replace the new one with it.
Click to expand...
Click to collapse
indeed...more than one way to skin a cat.
Is there a general concensus yet on the newer modem? seems the posts go both ways... a lot of people saying it's better, others saying it's not.
I guess the only way to be sure is to try it out
Desterly said:
Is there a general concensus yet on the newer modem? seems the posts go both ways... a lot of people saying it's better, others saying it's not.
Click to expand...
Click to collapse
I used the Phone Info app to shut off 4g, and made a number of before/after test of the 3g signal.
It seems to be consistantly 2 or 3 db better with the new modem.
For example, sitting at my desk, I would show -82 dBm with the old modem, and -79 dBm with the new modem.
Can't say if there is any difference in 4g performance, it's nice and fast both before and after.
One change that I noticed, with the new modem, when switching from 3g to 4g, it changes over almost instantly. Before the modem upgrade, it would take maybe 30 seconds or so to pick up the 4g signal.
I535VRLG1 update
I also wondered this. Is there a reason except for the search function to go back to the first radio?
Also on a side note, I never accepted an OTA update! Was this pushed without the user's consent?
excelsisba said:
I also wondered this. Is there a reason except for the search function to go back to the first radio?
Click to expand...
Click to collapse
Updating the radio has nothing to do with the search function. If you currently have the VRLF2 build, you can update the radio (also the kernel) to the newer version without changing the build version.
If you purchased an updated phone, or take an OTA update, then you will have the downgraded google search. As pointed out by pjamv5, that's easy enough to fix if you want the old google search.
I've updated the kernel and radio, here's the end result:
Desterly said:
Is there a general concensus yet on the newer modem? seems the posts go both ways... a lot of people saying it's better, others saying it's not.
I guess the only way to be sure is to try it out
Click to expand...
Click to collapse
I first flashed the G1 radio firmware and kept the F2 ROM. I didn't notice much of a difference. Went ahead and flashed BeanTown R2 ROM which is based on the G1 rom but customized. It all works well for me.
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.
I was wondering now that djrbliss has released the vulnerability for AT&T SGS4 do we have to wait for devs to do something with it? For Loki tools it seems as if you have to have a recovery already made. Will a current one work?
https://github.com/djrbliss/loki
this seems more like a user made htc dev, not what true s-off "bootloader unlocked" would be. non the less it should work fine. this probably wont touch the write enabled protection on the device. the only issues i see is until we are truly unlocked we will always have that "samsung custom" on out bootscreens.
spyz88 said:
I was wondering now that djrbliss has released the vulnerability for AT&T SGS4 do we have to wait for devs to do something with it? For Loki tools it seems as if you have to have a recovery already made. Will a current one work?
https://github.com/djrbliss/loki
Click to expand...
Click to collapse
He released his source code and such so we need to have someone compile it into a .bat or .exe so we can flash a custom recovery/rom
its linux only, and devs need to use/make teh loki_patch.
someone could make a windows/android app to interface with loki_flash for end users though...
shabbypenguin said:
its linux only, and devs need to use/make teh loki_patch.
someone could make a windows/android app to interface with loki_flash for end users though...
Click to expand...
Click to collapse
well i cant use it as i don't use linux lol.
Everyone - if you don't know what to do with those files without asking, don't try it yourself. There's already one in process in the development thread, and there will be cleaner and simpler ones out within just a few hours, I'm sure - with complete instructions.
Until you can nandroid the phone, this is not something to screw around with
fix-this! said:
well i cant use it as i don't use linux lol.
Click to expand...
Click to collapse
well if you dont use linux you cant make kernels or recoveries
luckily the loki_flash utility that is used to actually put the patched img onto the device works on android so it doenst matter what kind of computer you have
alacrify said:
Everyone - if you don't know what to do with those files without asking, don't try it yourself. There's already one in process in the development thread, and there will be cleaner and simpler ones out within just a few hours, I'm sure - with complete instructions.
Until you can nandroid the phone, this is not something to screw around with
Click to expand...
Click to collapse
A mod should put that up as a temp announcement in these forums. Seriously. Can't wait for the noobs to start crying in the Q&A area.... haha.
just means soon we will have bootloader unlocked.... patience
lorijuan1024 said:
just means soon we will have bootloader unlocked.... patience
Click to expand...
Click to collapse
i thought that's what this tool did. maybe this is why adam is still working on a bootloader unlock thats permanent. this should tide us over though.
Bjray said:
A mod should put that up as a temp announcement in these forums. Seriously. Can't wait for the noobs to start crying in the Q&A area.... haha.
Click to expand...
Click to collapse
Exactly, I have one phone booting to recovery now, no issues. YET! better know what you are doing, or you will have a serious paperweight.
I re-booted out of successful, so will see.
Update: nand backup was successful. Good start for us, just need the perm fix, but for now, it rocks, it was so nice to see the recovery screen. SWEET
TheAxman said:
Exactly, I have one phone booting to recovery now, no issues. YET! better know what you are doing, or you will have a serious paperweight.
I re-booted out of successful, so will see.
Click to expand...
Click to collapse
im not going to try the method yet, at least for a few days. i also see alot of soft bricked devices tonight.
fix-this! said:
i thought that's what this tool did. maybe this is why adam is still working on a bootloader unlock thats permanent. this should tide us over though.
Click to expand...
Click to collapse
what i meant was a tool that us people that aren't good with the programming language can use.
fix-this! said:
im not going to try the method yet, at least for a few days. i also see alot of soft bricked devices tonight.
Click to expand...
Click to collapse
Agreed, but I do have a jtag box here in hand, and there is no fix for that either, I might have one phone down soon..:
Incoming update from Samsung in 3....2....1.....
I flashed what shabbypenguin provided in his recovery thread and now have a working recovery on my ATT i337!!! :laugh::good::highfive::fingers-crossed:
Thanks to djrbliss for his awesome work!
mr_blanket said:
Incoming update from Samsung in 3....2....1.....
Click to expand...
Click to collapse
simple solution is to not take the OTA. but yes, i see one coming to.
fix-this! said:
simple solution is to not take the OTA. but yes, i see one coming to.
Click to expand...
Click to collapse
Yes, everyone needs to keep the OTA .apk's frozen from now on. Or use a custom rom that doesn't have them.
mattdm said:
Yes, everyone needs to keep the OTA .apk's frozen from now on. Or use a custom rom that doesn't have them.
Click to expand...
Click to collapse
hopefully adam can get us a more permanent solution. but props to dan for his tool.
Couldn't be happier after I get home from watching the hangover I get to unlock this bad boy
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
So I'm curious- when flashing OEM images from Google, which version is the "Verizon" version? The reason I ask is that I've had a Pixel that I purchased from Google direct and have been running it on VZW.
Recently, due to some odd malfunctioning, I tried and tried to re-flash the phone with the standard image (not Europe and not Verizon because I bought the phone directly from Google), but since it still didn't correct the problem, Google has now sent me a new, replacement phone.
So upon receiving the new Pixel, it was way out of date - running 7.1.1 and a February build, so I updated the os only to find that it has installed the May - Verizon build (aka NHG47L). That blew me away because I always assumed the "Verizon" images were for when you bought the phone from Verizon...NO?
Thanks for clearing the air here-
Questions go in the Q&A section. Report your post to a moderator by clicking the exclamation point in the triangle /!\ in the lower left corner of your post and ask them to move the thread to Q&A.
When you're running stock on the Pixel no matter where you got the Pixel, after you put a Verizon SIM in it, the phone will download and install the Verizon version of the stock Pixel ROM.
The site https://developers.google.com/android/images says which versions are Verizon specific.
Understand.
If you are re-flashing a Pixel to stock though, and that Pixel came from Google but has a VZW sim card installed, is it advised to flash the Verizon stock image or the non-designated image or does it matter? I had assumed it was best to flash the non-VZW image due to the added issues involved with unlocking a VZW phone, but after I had done that, I was having some phone app malfunction issues and so I'm wondering if the fact that I had not flashed the VZW image was causing my issues or not.
Thanks
pstgh said:
Understand.
If you are re-flashing a Pixel to stock though, and that Pixel came from Google but has a VZW sim card installed, is it advised to flash the Verizon stock image or the non-designated image or does it matter? I had assumed it was best to flash the non-VZW image due to the added issues involved with unlocking a VZW phone, but after I had done that, I was having some phone app malfunction issues and so I'm wondering if the fact that I had not flashed the VZW image was causing my issues or not.
Thanks
Click to expand...
Click to collapse
If Verizon is your carrier, then you should flash the Verizon build which is at this time NHG47L. If your Pixel came from the Google Store, then you don't have to worry about the bootloader, you will be able to unlock, and lock it at will.
jmartin72 said:
If Verizon is your carrier, then you should flash the Verizon build which is at this time NHG47L. If your Pixel came from the Google Store, then you don't have to worry about the bootloader, you will be able to unlock, and lock it at will.
Click to expand...
Click to collapse
Would it affect rooting?
Tulsadiver said:
Would it affect rooting?
Click to expand...
Click to collapse
Again, as long as it's a pixel direct from Google, then no I've rooted mine before, but I usually stay stock
Tulsadiver said:
Would it affect rooting?
Click to expand...
Click to collapse
no. definitely not...
if it was purchased from the google store then you can flash anything..
reyscott said:
no. definitely not...
if it was purchased from the google store then you can flash anything..
Click to expand...
Click to collapse
Thanks, I like their reception but nothing else. I'll never buy another phone from them. I've been using Google version with no problems. Could the difference be just bloat ware?
Tulsadiver said:
Thanks, I like their reception but nothing else. I'll never buy another phone from them. I've been using Google version with no problems. Could the difference be just bloat ware?
Click to expand...
Click to collapse
havent used any carrier specific devices. so cant really tell
Tulsadiver said:
Thanks, I like their reception but nothing else. I'll never buy another phone from them. I've been using Google version with no problems. Could the difference be just bloat ware?
Click to expand...
Click to collapse
no. It apparently has improvements in it for their network. It doesn't include extra applications.
Would it be possible to modify the .bin in an OTA sideload for a root? Am I missing a key point in how this works? Or is it just, no one's done it yet?
Edit: I guess it just took a passion and a situation. See thread for unlock.
Edit Part 2: Electric Boogaloo: Just a quick recap of what's happened here. From the bootloader screen on my Pixel 2 (Walleye) I ran the
Code:
Fastboot flashing lock_critical
command, which then gave me a menu asking if I really want to lock it, or unlock it, I clicked unlock, and here we are. So far, only @zinchalk has confirmed this working. I would love for more people to try this out on their Verizon Pixel 2's and come back with the results. This was either the weirdest fluke of all time, or the best mistake Verizon has ever made. Either way, I hope it works for you
Edit 3: Well there's the January Patch This looks like it 'fixes' the bypass.
Correction: Nevermind, nothing is confirmed yet. And the people have decided there is no way this could be patched that quickly.
Edit 4: I'm seeing way too many people posting about bricked phones. Please don't do this UNLESS YOU KNOW WHAT YOU ARE DOING. I cannot live knowing that someone ruined their phone with this method. Please be safe.
@SoloTSi97 has confirmed this does work on the January 5th security patch!
Edit 5: There it is, we have people confirming the Verizon OTA being pushed this late January is patching the fastboot unlock method. Keep this in mind down the road guys.
D3RP_ said:
Would it be possible to modify the .bin in an OTA sideload for a root? Am I missing a key point in how this works? Or is it just, no one's done it yet?
Click to expand...
Click to collapse
Have you found a way to unlock the bootloader on a Verizon phone?
Or are you thinking modify the .bin would achieve unlocking the bootloader?
As far as I've read, no one has bothered since you can purchase direct from Google and OEM unlock the bootloader. Then root through Magisk is simple.
Sent from my Pixel 2 using Tapatalk
Diesel_Jeremiah said:
Have you found a way to unlock the bootloader on a Verizon phone?
Or are you thinking modify the .bin would achieve unlocking the bootloader?
As far as I've read, no one has bothered since you can purchase direct from Google and OEM unlock the bootloader. Then root through Magisk is simple.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
lmao not that I know of. But I know it's possible to update any android through adb sideload. I'm really just grasping for straws. But because of my current situation I have a Pixel 2 from Verizon, and i'm gonna have it for a while.
I've been out of the android game for a long time; just switched back from iPhone 7, to a Pixel 2 used with Verizon. Am I correct in assuming that the device is unable to be unlocked, etc.?
tailsthecat3 said:
I've been out of the android game for a long time; just switched back from iPhone 7, to a Pixel 2 used with Verizon. Am I correct in assuming that the device is unable to be unlocked, etc.?
Click to expand...
Click to collapse
Unless you know some magic way, it is locked. I don't even know where to start with this thing.
Sell the Verizon one to someone who doesn't care for root and buy one from Google?
I used Sunshine Root for my HTC m8 years ago. They might be an option in the future. Yet again, since the Google version is easily unlocked & rooted, I don't think anyone has even tried.
Sent from my Pixel 2 using Tapatalk
Thanks. Glad I didn't try using the method I saw on YouTube, etc.
tailsthecat3 said:
Thanks. Glad I didn't try using the method I saw on YouTube, etc.
Click to expand...
Click to collapse
Just a small update. From the fastboot menu, I did
Code:
Fastboot flashing lock_critical
Which gave me the option to ''unlock bootloader'. It can't be this easy, but uhhh. I'll keep this thread updated...
Surely it can't be that easy. I'd say start a thread if this hasn't been noted.
---------- Post added at 18:55 ---------- Previous post was at 18:54 ----------
D3RP_ said:
Just a small update. From the fastboot menu, I did
Code:
Fastboot flashing lock_critical
Which gave me the option to ''unlock bootloader'. It can't be this easy, but uhhh. I'll keep this thread updated...
Click to expand...
Click to collapse
^^
tailsthecat3 said:
Surely it can't be that easy. I'd say start a thread if this hasn't been noted.
---------- Post added at 18:55 ---------- Previous post was at 18:54 ----------
^^
Click to expand...
Click to collapse
OEM unlocking says Bootloader is unlocked. So uh, it was that easy... Gonna root and install TWRP in a second.
Final Update
So that worked. Currently rooted with TWRP on my Verizon Pixel 2. Spread the word, or don't.
D3RP_ said:
So that worked. Currently rooted with TWRP on my Verizon Pixel 2. Spread the word, or don't.
Click to expand...
Click to collapse
Can you give some screenshot proof on this?
Interesting. I've been watching to see if someone gets the bootloader unlocked for the Verizon Pixel 2. In looking at the manpage for the fastboot commands, all you've really done is tell the system to lock the critical partitions (bootloader) during flashing. Pretty cool that it brought up the unlock menu.
What happens if you run `fastboot flashing get_unlock_ability`?
lps1014 said:
Can you give some screenshot proof on this?
Click to expand...
Click to collapse
Does that prove anything?
D3RP_ said:
Does that prove anything?
Click to expand...
Click to collapse
This doesn't prove anything. Show us the bootloader screen with your phone's info. There will be a baseband number and the status of the bootloader. Cover your serial number.
[Edit]
You do have a custom kernel flashed though.. so I guess.
xtacocorex said:
Interesting. I've been watching to see if someone gets the bootloader unlocked for the Verizon Pixel 2. In looking at the manpage for the fastboot commands, all you've really done is tell the system to lock the critical partitions (bootloader) during flashing. Pretty cool that it brought up the unlock menu.
What happens if you run `fastboot flashing get_unlock_ability`?
Click to expand...
Click to collapse
Sorry for the late reply. When I do that, I get
Code:
(bootloader) get_unlock_ability: 0
I made a thread about this in the original Pixel XL section. In the OP I quickly jolted down what you did, can you go and explain in detail as it might also work with the OG Pixel's.
Thanks in advance :
https://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-bootloader-unlocked-t3726672
How did the OP pass the cert check and update checks?
TonikJDK said:
How did the OP pass the cert check and update checks?
Click to expand...
Click to collapse
edit
lps1014 said:
Can you give some screenshot proof on this?
Click to expand...
Click to collapse
I just ran the command like OP said and the "unlock bootloader prompt" appeared. I ran this from a stock verizon on 8.0. I now flashed twrp, magisk and have the current google 8.1 ota. I will give proof if you tell me what will suffice.