Database Info

[FIRMWARE] <I535VRUCML1> (MODEM/RPM/TZ/SBL) Verizon SGS3 (SCH-I535)

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!

6.0.1 OTA for stock rooted system

Hi, sorry if this is a stupid question, but I just noticed Sprint pushed an OTA for 6.0.1 to my stock rooted device (S-on) and I'm just trying to figure out what the best way to get this OTA is going to be. I'm assuming I shouldn't download and install the OTA as-is due to the TWRP recovery and root.
After looking around a bit, it seems like the only option available is to use a stock 6.0.0 RUU file in the bootloader and basically reset the entire device back to factory settings (losing all apps and data in the process presumably), installing the OTA, then re-flashing TWRP and re-rooting.
I guess what I'm asking is - 1. is this the correct way to go about doing this? and 2. is there any better alternative perhaps that doesn't involve losing my data?
Thanks in advance guys.

Been googling around for the last few days and scouring this board for just as long and still haven't come to a definitive conclusion. From what little I've seen the documentation on this seems kind of spotty and I'm just wondering which direction to head in. Any help on this would be much appreciated.

Safest way.. ruu back to stock everything take ota and re root/download apps etc...

Thanks for the reply, man.. Thats kind of what I had gathered pouring over all these articles and board posts. I went ahead and RUU'd back to 1.10.651.1 for sprint.. Literally just moments ago though I downloaded the OTA and hit install and got presented with an error screen during the update. Phone rebooted back into the system normally, and I went to check the version # only to see it unchanged, along with a prompt to install the OTA for 1.57.651.1 again.
Any idea why this might've happened or how to remedy 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"
}
Wonders_Never_Cease said:
Safest way.. ruu back to stock everything take ota and re root/download apps etc...
Click to expand...
Click to collapse

What was the error? You may have to relock bootloader to accept the ota...unsure of how they are with their device,GSM device I have doesnt need relocked...(S-Off as well so)
---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------
Also the 1.57.651.1 RUU is available... Why not use it?
http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.57.651.1_R2.exe

Thats the weird part, it didnt give an error message, just that icon in the image I added to my last post. forelock the bootloader would be kind of surprising... Might give that a try in the morning after I find out if it can be re-unlocked.
EDIT: Ohhh I just saw your last edit, i didnt see that before, i'll use that then. Thank you!!!
Wonders_Never_Cease said:
What was the error? You may have to relock bootloader to accept the ota...unsure of how they are with their device,GSM device I have doesnt need relocked...(S-Off as well so)
---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------
Also the 1.57.651.1 RUU is available... Why not use it?
http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.57.651.1_R2.exe
Click to expand...
Click to collapse

Download the .651 ruu,reboot phone into download mode and run it... Should be up to date after that for a bit id think
---------- Post added at 12:58 AM ---------- Previous post was at 12:53 AM ----------
How did you unlock it to begin with? HTC Dev site? If so then should be able to use the same unlocktoken.bin from before... Or can resubmit and get another one...
txag2011 said:
Thats the weird part, it didnt give an error message, just that icon in the image I added to my last post. forelock the bootloader would be kind of surprising... Might give that a try in the morning after I find out if it can be re-unlocked.
EDIT: Ohhh I just saw your last edit, i didnt see that before, i'll use that then. Thank you!!!
Click to expand...
Click to collapse

Thats precisely what I did. Unlocked it with the HTC Dev Token. I gotta admit, I was pretty surprised that I had an OTA so soon after getting the phone and unlocking / rooting it. Just when I had everything set up how I liked it
I just finished flashing the 651 RUU and its just optimizing the apps now, but looks like it should do it!
Wonders_Never_Cease said:
Download the .651 ruu,reboot phone into download mode and run it... Should be up to date after that for a bit id think
---------- Post added at 12:58 AM ---------- Previous post was at 12:53 AM ----------
How did you unlock it to begin with? HTC Dev site? If so then should be able to use the same unlocktoken.bin from before... Or can resubmit and get another one...
Click to expand...
Click to collapse

Cool glad got it sorted...
txag2011 said:
Thats precisely what I did. Unlocked it with the HTC Dev Token. I gotta admit, I was pretty surprised that I had an OTA so soon after getting the phone and unlocking / rooting it. Just when I had everything set up how I liked it
I just finished flashing the 651 RUU and its just optimizing the apps now, but looks like it should do it!
Click to expand...
Click to collapse

Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Wonders_Never_Cease said:
Cool glad got it sorted...
Click to expand...
Click to collapse

First thing ya need to do is read how to install adb and fastboot and get away from toolkits... Download 2.67 from this thread...copy to device flash through twrp...
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
txag2011 said:
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Click to expand...
Click to collapse

And didnt mean that in a snotty,sarcastic way... Those tools sometimes cause issues that could be avoided is all I was getting at...

I want to join this conversation.
The A9 of my mom got is a Vodaphone UK version (cid: vodap001) and got the update message to version 1.62.161.2
I've rooted the device and installed TWRP.
So now i relocked the bootloader, installed the firmware.zip that was inside the OTA Download which i've copied from Update-App Path.
If i now want to manualy update the OTA-zip with fastboot in download-mode, i got Error 7.
If i want to update with original OTA updater Up, it stops at 25% with the red cross.
So what should i do now?
There is noch previous RUU-file for this firmware-version thats why i've already updated to the recovery from this OTA-update.
I hope someone can help with it.
Thanks,
Bond

txag2011 said:
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Click to expand...
Click to collapse
I have to agree with Wonders_never_cease about the toolkits. I have used many different ones and they are great from a few things but not all things go right using them unlike adb/fastboot. You should have better results from using adb/fastboot here.
That being said.....it would be easier to achieve root by simply going to full stock using RUU or system/boot.img in fastboot, flashing TWRP, format data, reboot into TWRP, flash supersu 2.74 from your SD card either by itself to obtain normal root or follow steps here http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 for systemless root. it's that simple...or at least was for me. I never could get pushing supersu through adb right or to work really.
---------- Post added at 10:12 AM ---------- Previous post was at 09:59 AM ----------
Bond246 said:
I want to join this conversation.
The A9 of my mom got is a Vodaphone UK version (cid: vodap001) and got the update message to version 1.62.161.2
I've rooted the device and installed TWRP.
So now i relocked the bootloader, installed the firmware.zip that was inside the OTA Download which i've copied from Update-App Path.
If i now want to manualy update the OTA-zip with fastboot in download-mode, i got Error 7.
If i want to update with original OTA updater Up, it stops at 25% with the red cross.
So what should i do now?
There is noch previous RUU-file for this firmware-version thats why i've already updated to the recovery from this OTA-update.
I hope someone can help with it.
Thanks,
Bond
Click to expand...
Click to collapse
You will not be able to apply the OTA update if you are not completely stock including being with stock recovery. Having your bootloader unlocked will not be an issue so no need to relock it like you did. Use a system/boot/recovery.img to restore stock completely, or whatever RUU need. Then accept the OTA or flash it manually, then reroot. Thats really the only way you will be able to get that to work.....

mcbright80 said:
You will not be able to apply the OTA update if you are not completely stock including being with stock recovery. Having your bootloader unlocked will not be an issue so no need to relock it like you did. Use a system/boot/recovery.img to restore stock completely, or whatever RUU need. Then accept the OTA or flash it manually, then reroot. Thats really the only way you will be able to get that to work.....
Click to expand...
Click to collapse
Thanks for your answer.
But how to get complete stock without nandroid or RUU?
The Firmware.zip of the 1.62.161.2 OTA Update was installed without Errors. But as i already mentioned i Need stock System/boot-files of my last Version (1.62.161.1) to get this partitions to stock. And they are not available anywhere.

Bond246 said:
Thanks for your answer.
But how to get complete stock without nandroid or RUU?
The Firmware.zip of the 1.62.161.2 OTA Update was installed without Errors. But as i already mentioned i Need stock System/boot-files of my last Version (1.62.161.1) to get this partitions to stock. And they are not available anywhere.
Click to expand...
Click to collapse
Ah so sorry, it was 4 am when i was replying so i missed that part on it installing correct, or confused it with the other question i was replying to at that same time haha......anyhoo....i looked for you as well and nothing was found on my end as well so I think you may be in the exact situation i was in when i bought the sprint variant of the A9. HTC has faults like all companies but the one that really pisses me off is their lack of proper support on ALL variants especially concerning firmware. The phone was released and i found NO RUU on their site or anywhere online and of course not many people had my specific variant which meant no one on here or anywhere had the means to get me the stock firmware i too needed to restore my phone.
The ONLY reason anyone here, who has SPRINT US VERSION, is able to then and NOW get the RUU on the HTC website is directly due to my incessant badgering and yelling at HTC damn near daily about having a handset on the market for sale but no firmware for it in case of tech service needs. You may have to do the same thing sadly.
I assume you have checked htc UK site for the rom downloads......contact their tech support and see whats up. Till then, like i had to when the sprint version came out....you'll have to just keep checking back on here and anywhere online for someone else who may post what you need or some other kind of solution.

Thanks mcbright80,
as you already said, HTC resists and says RUUs are only available in the US. I'm excited on their reaction that there are still lower RUU-versions of my UK-edition.
It is an annoying mess with all these different versions for tons of carriers, countrys and so on.

Root?

Is the zs551kl officially bootloader-unlockable and able to be rooted?
If that's the case, it would mean it's a much better phone than many of the latest flagships: sdcard, jack, FM radio, dual SIM, larger battery, stereo speakers, more complete GPS, good resolution screen, etc.

I haven't seen anything yet, but I assume it's coming. I don't think there will be a lot of roms though.

Let's pray that someone popup with that

rblanca said:
Let's pray that someone popup with that
Click to expand...
Click to collapse
Have you got this device? There is aTWRP available, but I'm not sure if anyone has successfully rooted, etc.

temporarium said:
Have you got this device? There is aTWRP available, but I'm not sure if anyone has successfully rooted, etc.
Click to expand...
Click to collapse
Yes I have it....but currently there isnt any modded kernel with root enabled or any rom...so there is no point on unlock the bootloader....but ASUS has made public the app to unlock the bootloader.
---------- Post added at 11:41 PM ---------- Previous post was at 11:33 PM ----------
temporarium said:
Have you got this device? There is aTWRP available, but I'm not sure if anyone has successfully rooted, etc.
Click to expand...
Click to collapse
Yes I have it....but currently there isnt any modded kernel with root enabled or any rom...so there is no point on unlock the bootloader neither install TWRP ....but ASUS has made public the app to unlock it.

rblanca said:
Yes I have it....but currently there isnt any modded kernel with root enabled or any rom...so there is no point on unlock the bootloader....but ASUS has made public the app to unlock the bootloader.
Click to expand...
Click to collapse
Have you tried this?
https://forum.xda-developers.com/zenfone-4-pro/development/recovery-twrp-3-1-1-0-zs551kl-t3692186
All you need is a way to flash root.

rblanca said:
Yes I have it....but currently there isnt any modded kernel with root enabled or any rom...so there is no point on unlock the bootloader....but ASUS has made public the app to unlock the bootloader.
Click to expand...
Click to collapse
Out of curiosity, what made you choose this phone over all the others? How do you like it so far? Pros\cons?

temporarium said:
Have you tried this?
https://forum.xda-developers.com/zenfone-4-pro/development/recovery-twrp-3-1-1-0-zs551kl-t3692186
All you need is a way to flash root.
Click to expand...
Click to collapse
No, because , like I said before...until we have a Rooted kernel available to download or a custom rom to install there is no point on install TWRP or unlock the bootloader....I'm pretty sure that in the next months there are going to be Roms and Custom Kernels (Rooted), it's too soon the phone was released on October (the past month).
About what made me chose this phone...it was
- Unlockeable Bootloader
- Snapdragon 835 as CPU
- 6 GB of Ram
- Good camera
- ASUS it's a good brand.
- FM raido
The phone its pretty damn fast...multitasking is amaizing...the battery dont seems so well like my, now broken, LG G5 but at least it runs for 1 day and a few hours but maybe its due the "new phone effect" (you play with it more the first days of use XD)

Magisk should give you root as long as bootloader can be unlocked.
I'll watch this space for root as I'm about to go get one myself because Snapdragon 835, then I have 15 days to test it on one game to decide whether to keep or return, lol.

motopig said:
Magisk should give you root as long as bootloader can be unlocked.
I'll watch this space for root as I'm about to go get one myself because Snapdragon 835, then I have 15 days to test it on one game to decide whether to keep or return, lol.
Click to expand...
Click to collapse
That's what I thought: once you unlock the bootloader and ADB-flash TWRP, you should be able to install SuperSU or Magisk (with corresponding manager app) and be good to go. So please test and let us know if you can.

temporarium said:
That's what I thought: once you unlock the bootloader and ADB-flash TWRP, you should be able to install SuperSU or Magisk (with corresponding manager app) and be good to go. So please test and let us know if you can.
Click to expand...
Click to collapse
Sorry to disappoint you but I'm not going to unlock my bootloader right now....the reason the phone its new (and expensive), there isn't a single rom to install or kernel to flash (on my LG G5 you have to flash another kernel in order to have root, but maybe that has change).
More importante there isnt any unbrick guide yet if something fails plus my phone it's not being selled on my country so there isn't any kind of warranty or repair service if something fails. WIth 6gb of ram I can deal with some ASUS apps pre installed so I dont need to root it right now.
But like a said before...its a great phone...damn faster one! i'll recommend it.

Even if one wanted to unlock the bootloader to try things out, it is not possible right now anyway.
Tried it with Asus' official unlock app (just got the phone today! :victory, and the app simply crashes before it even gets to talk to the bootloader, so there is currently no way to do it. Fastboot still reports the device as locked.
Maybe I should have tried it before applying the latest OTA update, but oh well!
rblanca has a point though, with no way to restore the phone should something go seriously wrong, I won't try any more exotic methods to try to crack open that bootloader at the moment either. The various guides that float around on the web look dangerous at best.

rblanca said:
Sorry to disappoint you but I'm not going to unlock my bootloader right now....the reason the phone its new (and expensive), there isn't a single rom to install or kernel to flash (on my LG G5 you have to flash another kernel in order to have root, but maybe that has change).
More importante there isnt any unbrick guide yet if something fails plus my phone it's not being selled on my country so there isn't any kind of warranty or repair service if something fails. WIth 6gb of ram I can deal with some ASUS apps pre installed so I dont need to root it right now.
But like a said before...its a great phone...damn faster one! i'll recommend it.
Click to expand...
Click to collapse
I understand your concern. No worries!

damnaliens said:
Even if one wanted to unlock the bootloader to try things out, it is not possible right now anyway.
Tried it with Asus' official unlock app (just got the phone today! :victory, and the app simply crashes before it even gets to talk to the bootloader, so there is currently no way to do it. Fastboot still reports the device as locked.
Maybe I should have tried it before applying the latest OTA update, but oh well!
rblanca has a point though, with no way to restore the phone should something go seriously wrong, I won't try any more exotic methods to try to crack open that bootloader at the moment either. The various guides that float around on the web look dangerous at best.
Click to expand...
Click to collapse
We'll just have to sit tight.

Root!
Good news!
Asus fixed the unlock app ( https://www.asus.com/de/Phone/ZenFone-4-Pro-ZS551KL/HelpDesk_Download/ ) and bumped it to version 9.1.0.0
It now successfully unlocks the device's bootloader. I went ahead and did it since I already voided my warranty when trying to unlock it with the previous, bugged version anyway.
Works fine, fastboot reports the bootloader as unlocked. Device contents got factory-wiped as per announced in the app, so make sure to back up your things if you wanna do it. :silly:
Edit:
Aaaaand rooted with Magisk.
{
"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"
}
After installing TWRP I just followed this guide here: https://forum.xda-developers.com/ze...ide-how-to-root-acces-magisk-manager-t3678678
Applies 1:1 to the Zenfone 4 Pro as well and worked flawlessly. :fingers-crossed:

Nice work! Does Android Pay work with magisk on this phone?

@bahua78
Android Pay isn't available in my country yet, so I can't test this. Maybe somebody else can find out. :0

Is it possible to update firmware via a memory card with root?

[BASEBAND-FIRMWARE-MODEMS]Verizon Samsung Galaxy S5 {SM-G900V/KLTEVZW}[ODIN]

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.

How To Guide [CLOSED] Bypass the region check in Lenovo p12 pro 12.6(CN version)

Having had a long research after I bricked my lenovo p12 pro 12.6(the CN version) ,I thought I finally figured out what is happening when boot ROW firmware on my tablet and a method to bypass such region check. Here is detail procedure:
First of all ,you DO NOT need to return your bricked tablet back to the seller or manufactures, any of which costs time and patience.
1、Download the super partition image file Mod edit: Links removed ,and extract super.img from it using 7z x ... command.
2、You can choose to use my bash shell script (flash_stock_firmware.sh)or your manual instructions: to flash the stock firmware
Bash:
bash 'flash_stock_firmware.sh' 'PATH/TO/THE/STOCK/FIRMWARE/FOLDER'
,it takes about 5 minutes to end.
{
"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"
}
After it booted to framework ,the init process will play a bootanimation ,in my case it shows :
This is exactly what we should to remove.And now you could reboot the tablet into fastboot mode
Code:
fastboot flash super PATH/TO/EXTRACTED/SUPER/IMAGE
fastboot erase userdata
fastboot erase metadata
fastboot reboot
In my case ,my tablet successfully launches the SetupWizard for registering device to google:

Wow fantastic work? Any chance you can elaborate anymore in your instructions for the more novice users? I've not used ADB before. When I tried and the tablet was broke ADB couldn't see the tablet where as QFIL could.
Does the boot loader have to be unlocked?
I'm still waiting for mine back from china but depending on the stability of the Global ROM I may move across.
Is the above doable only with ADB or can it also be done in QFIL?
Does the Global ROM successfully OTA for you or does it fail after download? Can you search from the settings menu?
Going forward are you able to use the Lenovo Recovery Centre to flash updates Global ROM's without having to do the steps above again?

mardon85 said:
Wow fantastic work? Any chance you can elaborate anymore in your instructions for the more novice users? I've not used ADB before. When I tried and the tablet was broke ADB couldn't see the tablet where as QFIL could.
Does the boot loader have to be unlocked?
I'm still waiting for mine back from china but depending on the stability of the Global ROM I may move across.
Is the above doable only with ADB or can it also be done in QFIL?
Does the Global ROM successfully OTA for you or does it fail after download? Can you search from the settings menu?
Going forward are you able to use the Lenovo Recovery Centre to flash updates Global ROM's without having to do the steps above again?
Click to expand...
Click to collapse
Edited

ZTE AXON 7 said:
otloader
2、fastboot boot rec/recovery.img(Here you should wait for about thirty seconds before initialization completed)
3、adb push systemrw_1.32_flashable.zip /sdcard
4、Go to Install->/sdcard/ and choo
Click to expand...
Click to collapse
ZTE AXON 7 said:
Edited
Click to expand...
Click to collapse
Thanks for this. Its the info I think a lot of us have been waiting for.
Did you find the following issues with your global ROM the same as the video below @ 27:14

That is some really good news, great work!

Thanks for sharing your work. However, could you kindly make the link available without requesting permission asking to share our gmail address with you?

Thanks!

ZTE AXON 7 said:
h costs time and patience.
1、Download the super partition image file Mod edit: Link removed ,and extract super.img from it using 7z x ... command.
Click to expand...
Click to collapse
famaTV said:
Thanks for sharing your work. However, could you kindly make the link available without requesting permission asking to share our gmail address with you?
Click to expand...
Click to collapse
Download link was updated

Thanks for updating download links.
Once these changes have been updated can we simply download and flash newer ROW ROM's?
How is your device performing, any glitches?

ZTE AXON 7 said:
Download link was updated
Click to expand...
Click to collapse
Thanks … but even the other website requests mobile number or email address to download.
Too much work and privacy exposure to take. I would wait for someone else to re-upload the file to a more straight forward user friendly site.
Meanwhile, what have you changed to the super.img to make it bypass the region check? Do you have the CN full firmware file?
On the other hand, with your fix, will the tablet update firmware OTA without any issues?
Thanks again.

ZTE AXON 7 said:
EXTRAC
Click to expand...
Click to collapse
mardon85 said:
Thanks for updating download links.
Once these changes have been updated can we simply download and flash newer ROW ROM's?
How is your device performing, any glitches?
Click to expand...
Click to collapse
So far so good, all works fine ,120hz refresh rate,precision 3 pencil ,precisicion keyboard,fast charging,etc...

There is a brand new ROM out today. Are you able to flash that now? Have you tried changing the region code via a hex editor?
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com

famaTV said:
Thanks … but even the other website requests mobile number or email address to download.
Too much work and privacy exposure to take. I would wait for someone else to re-upload the file to a more straight forward user friendly site.
Meanwhile, what have you changed to the super.img to make it bypass the region check? Do you have the CN full firmware file?
On the other hand, with your fix, will the tablet update firmware OTA without any issues?
Thanks again.
Click to expand...
Click to collapse
I updated to S212017 with this super image ,no problem:

ZTE AXON 7 said:
I updated to S212017 with this super image ,no problem:
View attachment 5506983
Click to expand...
Click to collapse
Is that via QFIL or OTA and also can you check if the search box works within the settings menu.

mardon85 said:
Is that via QFIL or OTA and also can you check if the search box works within the settings menu.
Click to expand...
Click to collapse
OTA,I changed the original ota update logic from aosp.

ZTE AXON 7 said:
OTA,I changed the original ota update logic from aosp.
Click to expand...
Click to collapse
Wow it seems you've cracked it even better than the Ali Express sellers. Most of the reports are that it can't OTA and the issue with the Settings search bar.
If mine ever clears Chinese customs (been stick there for 12days now) I'll get mine back and be able to play.

Ok I'm looking at your instructions.
The flashing of the stock firmware is the easy bit.
Once you do that you get the not compatible message as per your original instructions.
At this point the tablet is stuck in a screen similar to below. It does not matter which option you chose the tablet will reset back to the same screen.
What exactly do you do from this point to flash these instructions and your Super Image.
fastboot flash super PATH/TO/EXTRACTED/SUPER/IMAGE
fastboot erase userdata
fastboot erase metadata
fastboot reboot
If I try and run abd I get the following:
Sorry these are probably a no brainer with your capabilities but this is all quite new to me.
Basically I can see the tablet when Android is up and running but not from fastboot mode?

mardon85 said:
Ok I'm looking at your instructions.
The flashing of the stock firmware is the easy bit.
Once you do that you get the not compatible message as per your original instructions.
At this point the tablet is stuck in a screen similar to below. It does not matter which option you chose the tablet will reset back to the same screen.
View attachment 5507019
What exactly do you do from this point to flash these instructions and your Super Image.
fastboot flash super PATH/TO/EXTRACTED/SUPER/IMAGE
fastboot erase userdata
fastboot erase metadata
fastboot reboot
If I try and run abd I get the following:
View attachment 5507027
Sorry these are probably a no brainer with your capabilities but this is all quite new to me.
Basically I can see the tablet when Android is up and running but not from fastboot mode?
Click to expand...
Click to collapse
UPDATE... Fast boot commands do actually work. Even though it wont list devices commands like reboot work fine.
Did you have to unlock your bootloader for this? Have you kept widevine L1?

@ZTE AXON 7 you seem to be using Linux like me, mostly. I've used QFIL to flash the ROW ROMs but never did it from Linux. Do you have instructions on how to do that?
Oh wait, I reread your post. That script is for flashing the stock ROM, just like you said. Sorry about that.

Thank you for your work
I don't understand this very well. Do you have detailed operation steps?