I have the zip file if anyone has a way for me to get it posted here for devs to get to work on it.
chetqwerty said:
I have the zip file if anyone has a way for me to get it posted here for devs to get to work on it.
Click to expand...
Click to collapse
Upload it to android file host if you have dev status but if not you can upload it to google drive or any other hosting site.
EDIT: If you can get it uploaded somewhere, I'm sure @muniz_ri wouldn't mind looking at it and since it sounds like it prevents downgrading, we may be able to make a ROM out of it using the OD5 bootloader like what was done with the VZW S4 Lollipop update.
No not a dev, uploaded it to a free service http://www.fileconvoy.com/dfl.php?id=g71d4dc928ae33b36999687091905b660934562bab don't know why eset said it was unsafe, it downloaded fine when i allowed it. so just allow its fine.
Tried another service, FileDropper for those who have a problem
http://www.filedropper.com/update_3
ESET Antivirus didn't have a problem with this one
Shotty the first release @muniz_ri LOL
This is a OC4 to OE1 update.
timeToy said:
This is a OC4 to OE1 update.
Click to expand...
Click to collapse
Someone in another thread said they took the OTA and can't downgrage back to kikkat or lollipop via odin.
Sent from my SM-G900V using XDA Free mobile app
aholeinthewor1d said:
Someone in another thread said they took the OTA and can't downgrage back to kikkat or lollipop via odin.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
I personally have a Dev. Ed. S5, so I don't mind, as long as I don't flash the bootloader (aboot.mbn), so I am still interested in this.
It's been confirmed by muniz_ri that the qfuse counter was updated. If you update to OE1, there's no going back.
Guess i don't care about going back as long as i can have root and tether. I deleted the file from cache just have to get rid of this nagging install update message.
@Dudash
Here is the G900V_OE1_Stock_Rooted_ROM for testing.
For safety reasons it does not include any bootloader, however I expect that it will require the G900V_OD5_Bootloader in order to run.
Warning! Do not flash if you have taken the OE1 ota update and kept root. The ROM may work but there currently is no proven unbrick method, until the OE1 full .tar is available, in case something goes wrong.
Once the OE1 .tar is available we can try repackaging the NCG .tar without the bootloader as a way to downgrade/unbrick and re-root.
muniz_ri said:
@Dudash
Here is the G900V_OE1_Stock_Rooted_ROM for testing.
For safety reasons it does not include any bootloader, however I expect that it will require the G900V_OD5_Bootloader in order to run.
Warning! Do not flash if you have taken the OE1 ota update and kept root. The ROM may work but there currently is no proven unbrick method, until the OE1 full .tar is available, in case something goes wrong.
Once the OE1 .tar is available we can try repackaging the NCG .tar without the bootloader as a way to downgrade/unbrick and re-root.
Click to expand...
Click to collapse
Awesome. Downloading now.
muniz_ri said:
@Dudash
Here is the G900V_OE1_Stock_Rooted_ROM for testing.
For safety reasons it does not include any bootloader, however I expect that it will require the G900V_OD5_Bootloader in order to run.
Warning! Do not flash if you have taken the OE1 ota update and kept root. The ROM may work but there currently is no proven unbrick method, until the OE1 full .tar is available, in case something goes wrong.
Once the OE1 .tar is available we can try repackaging the NCG .tar without the bootloader as a way to downgrade/unbrick and re-root.
Click to expand...
Click to collapse
And here is a deodexed version for testing: G900V_OE1_Stock_Rooted_Deodexed_ROM
muniz_ri said:
And here is a deodexed version for testing: G900V_OE1_Stock_Rooted_Deodexed_ROM
Click to expand...
Click to collapse
I see that you say "if you've taken the ota and kept root" does that mean that you will retain root or is it hit or miss? any reports either way? also, have you done ay tweaks to this? enabled tether or anything besides deodexing? Thanks
I have a dev. ed. and it worked for me, including Advanced Calling, but I also flashed the rest of the firmware from the update file(sbl1.mbn sdi.mbn rpm.mbn and tz.mbn)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
awesome, Thanks !
muniz_ri said:
@Dudash
Here is the G900V_OE1_Stock_Rooted_ROM for testing.
For safety reasons it does not include any bootloader, however I expect that it will require the G900V_OD5_Bootloader in order to run.
Warning! Do not flash if you have taken the OE1 ota update and kept root. The ROM may work but there currently is no proven unbrick method, until the OE1 full .tar is available, in case something goes wrong.
Once the OE1 .tar is available we can try repackaging the NCG .tar without the bootloader as a way to downgrade/unbrick and re-root.
Click to expand...
Click to collapse
muniz_ri said:
And here is a deodexed version for testing: G900V_OE1_Stock_Rooted_Deodexed_ROM
Click to expand...
Click to collapse
Sorry it's taken so long to reply. I was at a party when I replied and downloaded the ROMs and didn't want to test them without having my computer in case of an Odin emergency. lol.
I'll be testing them shortly.
timeToy said:
I have a dev. ed. and it worked for me, including Advanced Calling, but I also flashed the rest of the firmware from the update file(sbl1.mbn sdi.mbn rpm.mbn and tz.mbn)
awesome, Thanks !
Click to expand...
Click to collapse
Thanks, which ROM did you test or both?
muniz_ri said:
Thanks, which ROM did you test or both?
Click to expand...
Click to collapse
I tried Odexed only, I'm not necessarily interested in deodexed until Xposed is more stable in Lollipop and TW. I also modified your script to avoid wiping. All good
timeToy said:
I tried Odexed only, I'm not necessarily interested in deodexed until Xposed is more stable in Lollipop and TW
Click to expand...
Click to collapse
Thanks, created new thread for the ROM's here: http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
---------- Post added at 11:56 PM ---------- Previous post was at 11:24 PM ----------
chetqwerty said:
I see that you say "if you've taken the ota and kept root" does that mean that you will retain root or is it hit or miss? any reports either way? also, have you done ay tweaks to this? enabled tether or anything besides deodexing? Thanks
Click to expand...
Click to collapse
After reviewing the ota zip I have confirmed that it checks for stock /bin/ddexe which is modified when a device is rooted, therefore the official OC4-to-OE1 ota will fail on all rooted devices. I have not seen an OD5-to-OE1 ota update.zip in order to review.
chetqwerty said:
Guess i don't care about going back as long as i can have root and tether. I deleted the file from cache just have to get rid of this nagging install update message.
Click to expand...
Click to collapse
Confirming, if I'm not rooted, there's no way to disable the annoying update nag? I'm on BOC4 and I can't use the phone without the stupid msg popping up!
I'm a bit of a noob, so apologies if this question has an obvious answer:
Does any of this thread mean there's now a way to downgrade or root a non-rooted OE1?
equazcion said:
I'm a bit of a noob, so apologies if this question has an obvious answer:
Does any of this thread mean there's now a way to downgrade or root a non-rooted OE1?
Click to expand...
Click to collapse
No
Related
No, I do not have a full I535VRUCML1 firmware package for you.
Yes, I somewhat lied in the title of this thread. But I did it for a good reason: to get your attention.
Mods - I'm sure you'll understand.
You should NOT flash the I535VRUCML1 firmware (or any subsequent releases for that matter). You will brick. This is what vzw/samsung did on the first OTA for the Galaxy S4. They changed the keys they sign the firmware with. This prevents us from 'mis-matching' our firmware like we've been doing all along. We've been leaving aboot (VRUAME6, the african-canadian sock-monkey leaked bootloader) alone and updating everything else. Since they're signing with different keys now, doing this will brick your device. If you update the ENTIRE bootchain (including aboot) you shouldn't brick, but will be stuck with a locked bootloader and any attempt to downgrade (via dd, etc) will brick you as well. Even if you manage to flash an ENTIRE old bootchain over VRUCML1, you'll brick because they trip a qfuse that prevents it from working. More info about qfuse by djrbliss here: http://t.co/myb0LIrN6e
Just stick with VRUBMF1, trust me.
These firmware updates have, up until now, consisted of several partitions that we update:
- tz (trustzone)
- rpm (resource/power management)
- sbl[1,2,3] (secure bootloaders)
- NON-HLOS (modem/baseband)
Due to the way Samsung and Verizon have chosen to proceed with future updates (following what they do for the Galaxy S4) we cannot flash all these partitions anymore (see above) and retain our unlocked bootloader. We CAN, however, update the baseband as it's not signed.
Latest firmware: NE1 modem with MF1 firmware: http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip (md5sum: 7a49bb13c1160f4d4a89488127684b5b)
This will be the final zip I make. MF1 was the last firmware that allowed us to use the old bootloader, and NE1 is likely to be the last modem we'll ever receive.
How would we measure objectively, coverage/speed differences between what we have the old and new radios?
I guess bandwidth speed test app? Anything else?
Sweet. Maybe I'll get better signal. My voice/1x reception has been worse than my old dx. I'm dropping calls left and right. I also live in the middle of BFE.
how is baseband/radio affected when we flash something else with cwm or with Odin? I mean, I have stock rooted w. b00stedv.002, but if I flash aokp or cm, will it replace this new radio with whatever one is included with them?
Slightly OT, I remember on the dx, if you wanted to sbf without the radio you did it with Linux, otherwise with moto's rsdlite.
Will this wipe data/swap us back to a stockish rom?
invisiblek said:
I've always liked having a thread dedicated to keeping links for the most updated modems for a device. Just easier to find that way.
These are packaged for flashing with Odin. Flash in the PDA section.
I will not promise anything as far as faster speeds or better coverage.
IMPORTANT:
Do not unplug while this is happening, unless you are in dire need of a paperweight.
Odin tends to seem like it hangs for a short bit toward the end of the flash. Be patient, it will finish and automatically reboot.
Latest one on top.
VRLG1 - http://goo.im/devs/invisiblek/i535/VRLG1.modem.tar.md5
This is the first OTA
VRLF2 - http://goo.im/devs/invisiblek/i535/VRLF2.modem.tar.md5
This is the original shipped modem
Click to expand...
Click to collapse
very good idea these are amaazing.. any idea if the new radio plays nicer with installs etc.. as the old one has more or less everyone with no service here and there.. or globally roaming :/
beanstown106 said:
very good idea these are amaazing.. any idea if the new radio plays nicer with installs etc.. as the old one has more or less everyone with no service here and there.. or globally roaming :/
Click to expand...
Click to collapse
no idea, i'm still rocking a stock rom
would be nice though if this fixed some of the aosp problems
MOD: please sticky this thread
invisiblek said:
no idea, i'm still rocking a stock rom
would be nice though if this fixed some of the aosp problems
MOD: please sticky this thread
Click to expand...
Click to collapse
im on cm10 after all the audio commits etc it seems like the most stable rom other than stock, beats aokp or cm9 right now imho, no data drops etc
So...This is just the new baseband right?
So should be able to flash with custom recovery/rom etc?
this is my first samsung device so not looking for a brick.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm stuck at this screen, its been doing it for about 10 min. is it ok to unplug and start over?
burkett375 said:
I'm stuck at this screen, its been doing it for about 10 min. is it ok to unplug and start over?
Click to expand...
Click to collapse
Did you verify the MD5 before flashing?
nosympathy said:
Did you verify the MD5 before flashing?
Click to expand...
Click to collapse
doesn't it get verified in odin?
burkett375 said:
doesn't it get verified in odin?
Click to expand...
Click to collapse
I don't have any idea. I have always had HTC phones which are very different.
I have built the habit to check MD5 always, regardless of what it is, just so as to not have something happen where I can't say I did everything I could to prevent it.
burkett375 said:
I'm stuck at this screen, its been doing it for about 10 min. is it ok to unplug and start over?
Click to expand...
Click to collapse
yes, if its stuck on SetupConnection unplug and replug
this goes for more than just flashing modems
invisiblek said:
yes, if its stuck on SetupConnection unplug and replug
this goes for more than just flashing modems
Click to expand...
Click to collapse
hmmm...no matter what I do, I can't get past that part
burkett375 said:
hmmm...no matter what I do, I can't get past that part
Click to expand...
Click to collapse
you have the drivers installed?
burkett375 said:
hmmm...no matter what I do, I can't get past that part
Click to expand...
Click to collapse
You are in download mode correct? I literally just flashed this first try.
invisiblek said:
you have the drivers installed?
Click to expand...
Click to collapse
yup, i'm running CM10 right now and working good.
---------- Post added at 01:20 AM ---------- Previous post was at 01:19 AM ----------
nosympathy said:
You are in download mode correct? I literally just flashed this first try.
Click to expand...
Click to collapse
Nope, didn't know it was supposed to be in download mode...i'm a dummy
Edit: all set now...Thanks!
burkett375 said:
yup, i'm running CM10 right now and working good.
---------- Post added at 01:20 AM ---------- Previous post was at 01:19 AM ----------
Nope, didn't know it was supposed to be in download mode...i'm a dummy
Edit: all set now...Thanks!
Click to expand...
Click to collapse
haha no biggie. It happens.
nosympathy said:
I don't have any idea. I have always had HTC phones which are very different.
I have built the habit to check MD5 always, regardless of what it is, just so as to not have something happen where I can't say I did everything I could to prevent it.
Click to expand...
Click to collapse
tar.md5 files have the md5 appended to the end, and I think Odin checks before flashing. Not 100% sure on that though. Checking it yourself is never a bad idea of course.
This newer modem might of improved data throughput. Not entirely sure though, seems like I'm getting faster speed on Speedtest.net but that could be entirely subjective. Thank you invisiblek as always, for your awesome work!
I am downloading an update that is 568.3 mb. GO GRAB IT!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Me too!
Manually went to update...
Update finally
AT LAST
Got it!!
5.1.1?
Pump your brakes
If this is the 5.1.1 update and you are rooted and enjoy a custom device. Please understand what this update means before flashing it.
http://forum.xda-developers.com/sprint-galaxy-s6-edge/help/dont-odin-5-1-1-t3136671
wildjeep said:
Pump your brakes
If this is the 5.1.1 update and you are rooted and enjoy a custom device. Please understand what this update means before flashing it.
http://forum.xda-developers.com/sprint-galaxy-s6-edge/help/dont-odin-5-1-1-t3136671
Click to expand...
Click to collapse
You are 100% correct my friend... I hate when people hurry up and jump on the update, then complain non stop they lost root and can't get it back....
Sent from my SM-G925V using Xparent Green Tapatalk 2
Soooperstar said:
5.1.1?
Click to expand...
Click to collapse
+1
If you upgrade to 5.1.1, you will not be able to root at this time
DO NOT ATTEMPT TO ROOT
I have been unsuccessful to go back to OE2 via odin, does someone have the recovery image for 5.1.1
If anyone has taken the update, please report back on whether TWRP and/or Cf autoroot works
Sent from my SM-G925P using Tapatalk
dhonzik said:
If you upgrade to 5.1.1, you will not be able to root at this time
DO NOT ATTEMPT TO ROOT
I have been unsuccessful to go back to OE2 via odin, does someone have the recovery image for 5.1.1
Click to expand...
Click to collapse
This is one of the compilations that has been warned for a few weeks now. It will take some time to achieve a stable Root/Recovery.
So if anyone is satisfied with stock. Unroot and flash away.
Or sit tight and wait for the custom development to catch up to the current stock software :highfive:
I will say, however, the device seems to run much smoother and early signs show battery improvement as well. Obviously it's early but it seems promising. Just wanted to share my stock experience as I chose to not root for the future payment platform
I updated but I am not root
no ram management .
If you take this update, you cannot root for the time being and certainly cannot Safe root (not tripping knox) with PingPoint root. In addition, you cant downgrade kernel, etc.
So the question becomes, what is the best course of action here. Can we PingPong root prior build, then update to OF7 kernel and rom once someone repacks them? Flash with FlashFire and maintain root? Then again, I guess we could accept the OTA and stay stock until CF-Auto Root is updated to work with it.
Either way, I'm holding for a bit here to see what shakes out...
UPDATE: thought about this a second. Sprint doesnt typically lock boot loader like AT&T, verizon. So this locked boot loader is whats preventing people from downgrading kernel once they update right? So this should not be an issue with Sprint if the boot loader is not locked?
Alpine- said:
If you take this update, you cannot root for the time being and certainly cannot Safe root (not tripping knox) with PingPoint root. In addition, you cant downgrade kernel, etc.
So the question becomes, what is the best course of action here. Can we PingPong root prior build, then update to OF7 kernel and rom once someone repacks them? Flash with FlashFire and maintain root? Then again, I guess we could accept the OTA and stay stock until CF-Auto Root is updated to work with it.
Either way, I'm holding for a bit here to see what shakes out...
UPDATE: thought about this a second. Sprint doesnt typically lock boot loader like AT&T, verizon. So this locked boot loader is whats preventing people from downgrading kernel once they update right? So this should not be an issue with Sprint if the boot loader is not locked?
Click to expand...
Click to collapse
Take a look at this thread: http://forum.xda-developers.com/sprint-galaxy-s6-edge/help/dont-odin-5-1-1-t3136671
It is not a looked boot loader that is the problem. T-Mobile solved it so I am sure it will be solved for us very soon.
wildjeep said:
This is one of the compilations that has been warned for a few weeks now. It will take some time to achieve a stable Root/Recovery.
So if anyone is satisfied with stock. Unroot and flash away.
Or sit tight and wait for the custom development to catch up to the current stock software :highfive:
Click to expand...
Click to collapse
Heads up the t-mobile TWRP recovery does get my bricked phone to the recovery, but the buttons do not work. If it did I had a backup I would have tried. Heading to the Sprint Store Tech Center to hopefully get a working phone or a replacement.
dhonzik said:
Heads up the t-mobile TWRP recovery does get my bricked phone to the recovery, but the buttons do not work. If it did I had a backup I would have tried. Heading to the Sprint Store Tech Center to hopefully get a working phone or a replacement.
Click to expand...
Click to collapse
So did the Sprint recovery not work?
How did you brick?
Sprint may not mess with it once the see the wrong recovery
Soooperstar said:
So did the Sprint recovery not work?
How did you brick?
Sprint may not mess with it once the see the wrong recovery
Click to expand...
Click to collapse
It was attempt to see if the CF Auto-Root would work after the update. I went back to other recovery that doesn't open up, if the tech center has the complete firmware maybe it will be to flash it back on. I opened a thread to see if someone can pull the stock recovery from the update. Trying to reflash back to OE2 fails.
dhonzik said:
It was attempt to see if the CF Auto-Root would work after the update. I went back to other recovery that doesn't open up, if the tech center has the complete firmware maybe it will be to flash it back on. I opened a thread to see if someone can pull the stock recovery from the update. Trying to reflash back to OE2 fails.
Click to expand...
Click to collapse
Did you try to Odin our twrp?
Soooperstar said:
Did you try to Odin our twrp?
Click to expand...
Click to collapse
Yes, it was a no go, $75 later I'll have a new phone in a week
I just got a prompt for a new OTA update, but being rooted and running a ROM I couldn't install it. It gave no new information about the update such as size or fixes. Anyone else get this? I'm on an OC3 based ROM by the way.
yea i got it
Seanbest said:
I just got a prompt for a new OTA update, but being rooted and running a ROM I couldn't install it. It gave no new information about the update such as size or fixes. Anyone else get this? I'm on an OC3 based ROM by the way.
Click to expand...
Click to collapse
It is the stage fright update
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Will we be able to flash it some other way?
ClearD said:
Will we be able to flash it some other way?
Click to expand...
Click to collapse
I'm sure there will be soon
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Well, on second thought, I just went ahead and let the update run. It completed. Everything appears normal.
I confirm, it is a fix for Stagefright. Baseband version went from I337UCUFNJ4 to I337UCUFNJ5
+ SuperSU is working properly.
Below: Before & After the update
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
New Update Came ..
https://www.att.com/esupport/softwareUpdateArticle.jsp?sid=KB419415&cv=820
ClearD said:
Well, on second thought, I just went ahead and let the update run. It completed. Everything appears normal.
Click to expand...
Click to collapse
Were you rooted with the Flashfire method?
Anytime AT&T or Samsung offer a "security" update FOTA, I cringe. I'm on rooted Lollipop and absolutely have to remain rooted to use Total Recall call recorder (you can't imagine how many times it's saved my ass with baseless promises from AT&T and other utility vendors), so I'm always hesitant to upgrade to any FOTA's that may make it more difficult to either flash a better ROM, or other utilities that it might block. Call me paranoid, but I'm going to hold off and try to find a better solution to threats to my OS. Belarc Security Advisor (Free) is highly respected, and a non-conventional system scan that identifies real threats. Running it yesterday and just now; show no threats. I realize that Stagefright is a threat, but I'm running antivirus software that I trust and keep my phone backed up locally on a regular basis.
billbillw said:
Were you rooted with the Flashfire method?
Click to expand...
Click to collapse
Well, I also let it run. Figured worst case, it would be rejected due to root. It ran, no errors, still on root (using Flashfire method). Stagefright detector now shows my device is safe.
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
nukesnooper said:
Anytime AT&T or Samsung offer a "security" update FOTA, I cringe. I'm on rooted Lollipop and absolutely have to remain rooted to use Total Recall call recorder (you can't imagine how many times it's saved my ass with baseless promises from AT&T and other utility vendors), so I'm always hesitant to upgrade to any FOTA's that may make it more difficult to either flash a better ROM, or other utilities that it might block. Call me paranoid, but I'm going to hold off and try to find a better solution to threats to my OS. Belarc Security Advisor (Free) is highly respected, and a non-conventional system scan that identifies real threats. Running it yesterday and just now; show no threats. I realize that Stagefright is a threat, but I'm running antivirus software that I trust and keep my phone backed up locally on a regular basis.
Click to expand...
Click to collapse
If you're using the Stock AT&T Lolipop, and Flashfire method for rooting, you will be OK to let the update run. It ran with no issues for me and it kept root.
billbillw said:
Well, I also let it run. Figured worst case, it would be rejected due to root. It ran, no errors, still on root (using Flashfire method). Stagefright detector now shows my device is safe.
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
If you're using the Stock AT&T Lolipop, and Flashfire method for rooting, you will be OK to let the update run. It ran with no issues for me and it kept root.
Click to expand...
Click to collapse
That's exactly how I did it. My only concern is that it may install patches that could further restrict future modifications.
I also just completed running Lookout and it found no threats or vulnerabilities. I'm staying where I am until I hear more feedback.
Thanks for your advice. I'll be keeping an eye on it.
It's coming in as a 280mb download, I'm going to see what happens with root (previously used Flashfire)
sim_pl said:
It's coming in as a 280mb download, I'm going to see what happens with root (previously used Flashfire)
Click to expand...
Click to collapse
Please Upload .cfg File For Update My Device .. That OTA File /cache .. Check It And Upload It Please And Check fota Folder
UPDATED POST:
I upgraded with the install stock but "keep root" method, using flashfire...
The update failed at 29%.
I did a factory reset, and it still failed at 29%...
What are my options now?
Update:
I used Flashfire to install the tethering addon... I wonder if that is the culprit.
Installing without thethering... will update with results.
And It's a pain to download that ATT update each time. --- Their servers are SLOW!
Same story here. Update stops and phone reboots about a third of the way through. Defrosted all Samsung/AT&T bloat and tried again. Same story. Bummer.
I rooted my wife's 0C3 with Kingroot and tried to take the update. It failed.
Maybe I should try again since I just used triangle away to get rid of the "custom" nag at boot.
Rockin' a l337 with Goldeneye v49.1 + Wanam Xposed and loving life on AT&T's 4G LTE network
billbillw said:
Were you rooted with the Flashfire method?
Click to expand...
Click to collapse
Yes. Rooted with flashfire, on oc3 bootloader. I ran the update through the normal OTA method, not trying to install it through flashfire. It worked fine and root stayed normal. Verified when titanium backup ran last night on its normal schedule.
Well, it updated fine, using just the straight rooted rom, no additional flashes. No more fails at 29%...
It appears that adding in anything extra, de-bloat, hotspot enable, etc. will cause the update to fail.
/sk
Reinstalled the rooted stock ROM and the update worked fine. Still have root. All is groovy.
Alright, so I downloaded that KDZ, and unpacked it all and merged the system file. I believe this is yes, a working KDZ file and safe to use after examining boot.img and some other partitions. So ya, safe to flash. We got root on Lolipop by simply injecting SuperSU into the TOT, but that will not work. We need Systemless root by flashing a modified boot.img. How one creates a modified boot.img for it I will look into. Good luck flashing!
This also came from LG's website so it's official.
Here's the link to the download. https://drive.google.com/open?id=0B7FrzLAFlRrvd2N2bU5BSjljRGs
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks for the kdz. Can't wait for the modified boot.img. Keep up the good work!
yeah.. i too successfully upgraded my ATT h900 from the same kdz.. though downloaded it from another link
http://www.mylgphones.com/att-lg-v1...tock-kdz-firmware-available-for-download.html
everything went smooth & error free although my phone was rooted on 5.1. i used LG UP & used the "Upgrade" option..
nothing was deleted or overwrite either.. everything remained intact.. i say go for it..
sadly.. no change in interface at all..ditto same as 5.1.1... all behind the scene upgrades apart from Wifi calling
Should we not try this if already on MM?
Never mind this question, I found the answer in the TOT thread started by tung
P05TMAN said:
Should we not try this if already on MM?
Never mind this question, I found the answer in the TOT thread started by tung
Click to expand...
Click to collapse
It won't matter. Since it's marshmallow the tot rollback values remain the same
Flash at will
This might be a dumb question but does it have all the at&t bloatware? If not it would still be worth flashing just to rid my phone of at&t.
serdoch said:
This might be a dumb question but does it have all the at&t bloatware? If not it would still be worth flashing just to rid my phone of at&t.
Click to expand...
Click to collapse
Yes it will still have the AT&T bloat.
serdoch said:
This might be a dumb question but does it have all the at&t bloatware? If not it would still be worth flashing just to rid my phone of at&t.
Click to expand...
Click to collapse
ZVNexus said:
Yes it will still have the AT&T bloat.
Click to expand...
Click to collapse
@serdoch I think at this stage, the main test-point is to validate that we can flash and run a kdz file. If it's good (which so far it is) then we can move forward in trying to root by modifying the boot.img (or some other wizardry...)
P05TMAN said:
@serdoch I think at this stage, the main test-point is to validate that we can flash and run a kdz file. If it's good (which so far it is) then we can move forward in trying to root by modifying the boot.img (or some other wizardry...)
Click to expand...
Click to collapse
Ok thank you. Hopefully it goes well.
P05TMAN said:
@serdoch I think at this stage, the main test-point is to validate that we can flash and run a kdz file. If it's good (which so far it is) then we can move forward in trying to root by modifying the boot.img (or some other wizardry...)
Click to expand...
Click to collapse
I flashed it. Success. KDZ now OFFICIALY works. Anyone who wants to, feel free to flash it, we finally have a working firmware image on our hands .
ZVNexus said:
I flashed it. Success. KDZ now OFFICIALY works. Anyone who wants to, feel free to flash it, we finally have a working firmware image on our hands .
Click to expand...
Click to collapse
Works for me as well
What can I do to help?
P05TMAN said:
Works for me as well
What can I do to help?
Click to expand...
Click to collapse
Grab a beer? idk. I don't usually go this far in depth, I used to just hunt for system firmware on the internet and once I did I would inject supersu and flash, but thats not how it works with 6.0 sadly. I do know that it requires a modified boot.img, which I also, do not know how to do lol. Being the crafty person I am, I will research more. Not quite sure you want something though from someone who hasn't got the first clue of what to do, so I assume you would want a more trusted Dev such as... Chainfire? I will try to contact him. Doubt hes intrested.
P05TMAN said:
Works for me as well
What can I do to help?
Click to expand...
Click to collapse
And what version did you come off when you flashed? 6.0.1 as well?
P05TMAN said:
@serdoch I think at this stage, the main test-point is to validate that we can flash and run a kdz file. If it's good (which so far it is) then we can move forward in trying to root by modifying the boot.img (or some other wizardry...)
Click to expand...
Click to collapse
Oh heres something else thats important, as to my knowledge, we have a way to unpack a KDZ, but not reassemble. If you find anything, let me know.
ZVNexus said:
And what version did you come off when you flashed? 6.0.1 as well?
Click to expand...
Click to collapse
6.0
ZVNexus said:
Oh heres something else thats important, as to my knowledge, we have a way to unpack a KDZ, but not reassemble. If you find anything, let me know.
Click to expand...
Click to collapse
Researching
P05TMAN said:
6.0
Researching
Click to expand...
Click to collapse
Hm. It should work for my version though, since I am on H90021w. I think Anti-TOT rollback is just for rolling back, I think you can still flash your current version or upgrade. This firmware is also GREAT news for people who want to upgrade to 6.1 from 5.1.1 (Why would you want to tho root <3) lets say you have a other carrier phone that runs through AT&T, but its prepaid. This is GREAT for those people. The purposes are limitless.
ZVNexus said:
Oh heres something else thats important, as to my knowledge, we have a way to unpack a KDZ, but not reassemble. If you find anything, let me know.
Click to expand...
Click to collapse
The more I'm researching, the more unsure how a systemless root can be achieved without first being able to unlock the bootloader of the device first on marshmallow. How was this done on Lollipop? @tungkick do you have any info that may help?
P05TMAN said:
The more I'm researching, the more unsure how a systemless root can be achieved without first being able to unlock the bootloader of the device first on marshmallow. How was this done on Lollipop? @tungkick do you have any info that may help?
Click to expand...
Click to collapse
That is what I was saying. We need to modify the boot.img to unlock the bootloader, and obtain systemless root.
ZVNexus said:
That is what I was saying. We need to modify the boot.img to unlock the bootloader, and obtain systemless root.
Click to expand...
Click to collapse
<snip>
found this: http://forum.xda-developers.com/showthread.php?t=2600575
Maybe it can be used to compress again
---------- Post added at 05:50 PM ---------- Previous post was at 04:55 PM ----------
P05TMAN said:
<snip>
found this: http://forum.xda-developers.com/showthread.php?t=2600575
Maybe it can be used to compress again
Click to expand...
Click to collapse
Extraction doesn't really work well with that.
P05TMAN said:
<snip>
found this: http://forum.xda-developers.com/showthread.php?t=2600575
Maybe it can be used to compress again
---------- Post added at 05:50 PM ---------- Previous post was at 04:55 PM ----------
Extraction doesn't really work well with that.
Click to expand...
Click to collapse
Thats the tool I used to extract the KDZ, and DZ file, and to merge the system partition into one .img.
Great tool for extraction, 10/10, dont know if its capable of patching it back up.
THE OFFICIAL BASEBAND
FIRMWARE MODEM UPDATES
Verizon Samsung Galaxy S5
{SM-G900V/KLTEVZW}
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
{The above image is a refrence of all the Stock Firmware, Release Dates, etc...}
CLICK HERE TO EXPANDED THE ABOVE IMAGE
***INFORMATION REGARDING***
***NEW/REWORKED UPDATES***
The Modem packages were recently reworked to include the "much needed" Baseband files (of course) pulled from the Official Samsung Stock Firmware.
This is ONLY because the following list of files are ALL of the Baseband/Modem files that are actually the part of the Firmware that controls ALL the radio devices within the GS5 to include (but, not limited to) the GPS, WiFi, Bluetooth, NFC, Cellular Data/Voice, etc...
MODEM.BIN
NON-HLOS.BIN
RPM.MBN
SBL1.MBN
SDI.MBN
TZ.MBN
Please keep in mind that, because these functions are Highly Regulated & Certified, they are actually Separate from the Android Operating System (aka the Firmware ROM installed like AOSP, LineageOS, etc...).
This is the reason that, after flashing the "Baseband Firmware Modem Update", it DOESN'T DIRECTLY AFFECT the Android Firmware installed on your devide. Your Android Firmware (basically) takes note of the update and updates itself to reflect those said changes (simply put without getting too deep).
DISCLAIMER/FYI
- Any process (like updating your modem) via Odin and/or Custom Recovery is simple/easy to do but, as always, if your not sure of what your doing and don't do your research (ie... searching, asking questions, etc... FIRST), then you take the risk of damaging your device.
- I take no responsibility for any unexpected results or damage that may happen but, we are always willing to provide assistance to help you out.
- Also keep in mind that when performing any unconventional updates, unlocking, rooting, etc... you may end up "voiding your warranty"!
INSTRUCTIONS
1. If not already done, be sure your PC/LPTP has the latest "Samsung USB Driver for Mobile Phones" installed.
2. Download the ".tar.md5" Baseband Firmware Modem file you need from any of the Download Links provided (below).
3. Power off your device and then enter Download Mode (aka Odin Mode) by using the required key combination ("Home" & "Volume Down" then "Power").
4. Connect the USB cable to the Device and PC.
5. Open Odin and select the PDA/AP and choose the ".tar.md5" Modem file you downloaded.
{Please Note: It's typically reccomended to use Odin v3.07-v3.12 but, other versions may also work.
6. In Odin, please be sure not to make any additional selections than the default that was already selected when you opened Odin.
7. Select the Odin "Start" button at the bottom & be patient for the process to complete and Odin should reflect a Green "PASS" when completed (The device will reboot automatically when done).
PRIMARY DOWNLOAD LINK
(NEW UPLOADS BEING WORKED ON. PLEASE USE)
(THE BELOW ALTERNATIVE DOWNLOAD LINK)
Baseband Firmware Modem Updates {Odin Flashable} - XDA DevDB Downloads
ALTERNATIVE DOWNLOAD LINK
Baseband Firmware Modem Updates {Odin Flashable} - Android File Host
PLEASE NOTE: It has been decided not to pursue the Recovery Flashable (aka TWRP, CWM, etc...) Modem Updates at the present time. We apologize for the inconvenience...
Special Mentions/Credits
Samsung - For the Device.
Sammobile - For the Software/Firmware.
The XDA fAMILY - For Valuable Member Feedback.
Let's not forget - To All The Girls We've Loved Before... (LOL!)
Click Here If You Would Like To Donate To My Developements
~{Donations Are Appreciated, but Never Necessary...}~
PLEASE NO MIRRORS!
.
XDA:DevDB Information
[BASEBAND-FIRMWARE-MODEMS]Verizon Samsung Galaxy S5 {SM-G900V/KLTEVZW}[ODIN], Tool/Utility for the Verizon Samsung Galaxy S5
Contributors
Ibuprophen, klabit87
Version Information
Status: Stable
Current Stable Version: G900VVRU2DQL1
Stable Release Date: 2018-01-17
Created 2019-05-02
Last Updated 2019-06-20
Reserved
Reserved
Can i flash them on KK?
What are the differences between them ?
thanks
HazeMC said:
Can i flash them on KK?
What are the differences between them ?
thanks
Click to expand...
Click to collapse
I don't see why not. I know we can on the Verizon S4. @Stupifier may be able to tell you for sure though.
These are all modems from the lollipop releases.
Zips are ss and ff flashable.
And some people prefer Odin so I posted those too.
Thank you for this.
Anyone have the OG5 and OK3 modems? This thread would be the perfect place to add them.
painiac said:
Thank you for this.
Anyone have the OG5 and OK3 modems? This thread would be the perfect place to add them.
Click to expand...
Click to collapse
I will add them tonight. Sorry I lost track of things.
klabit87 said:
I will add them tonight. Sorry I lost track of things.
Click to expand...
Click to collapse
Nothing to apologize for!
painiac said:
Nothing to apologize for!
Click to expand...
Click to collapse
Safestrap flashables are added for OG5 and OK3.
klabit87 said:
Safestrap flashables are added for OG5 and OK3.
Click to expand...
Click to collapse
Very much appreciated!
I have G900V but I'm outside US and my provider does not suport lte band 4, 13.
Can you flash G900F moden on G900V? Would that give my phone access to diferent lte band?
Thanks.
Looking for the PB1 modem for CM13
Nandr0idC0nsumer said:
Looking for the PB1 modem for CM13
Click to expand...
Click to collapse
this one?
https://www.androidfilehost.com/?fid=24459283995308895
Actually this one caused me bootloops. not sure if it works. had to flash back to NCG
thaijunk said:
this one?
https://www.androidfilehost.com/?fid=24459283995308895
Actually this one caused me bootloops. not sure if it works. had to flash back to NCG
Click to expand...
Click to collapse
Thanks. I flashed the full stock PB1 tar to get it (big mistake) and went through hell and back to unlock the bootloader and go back to CM xD
I was wondering if there is a PF4 modem zip file for our phones?
Sorry everybody. PB1, PD1, and PF4 have been added.
If you need/prefer odin tar files let me know.
i dont feel anybody uses them based on the downloads of previous tar files.
I flashed the modem but never changed
Sent from my SM-G900V using XDA-Developers mobile app
ozz200127 said:
I flashed the modem but never changed
Sent from my SM-G900V using XDA-Developers mobile app
Click to expand...
Click to collapse
That does not tell me much.
Did you use FlashFire? Safestrap? or TWRP?
As far as I know they have only been flashed with SafeStrap.
I have not had the chance to test with TWRP.
I can upload others that will work for TWRP if that is the issue.
Might be a day or 2 but I will.
I use twrp...the flash went through but it didn't change
Sent from my SM-G900V using XDA-Developers mobile app
ozz200127 said:
I use twrp...the flash went through but it didn't change
Sent from my SM-G900V using XDA-Developers mobile app
Click to expand...
Click to collapse
ok. I will update them for twrp in the next day or 2.
Sorry. these were started before the bl unlock exploit was developed.
and I never thought to test it myself until you brought it to my attention.