[FIRMWARE 4.4.2] VRUDNE1 full wipe tar + NE1 Update Zip

Search This thread

open1your1eyes0

Senior Member
Dec 13, 2010
2,651
3,671
New York City
Correct me if I am wrong....

But if I flash the SBL partitions but not the aboot partition it will brick phone, correct?

Depends which SBLs you're trying to flash, I would recommend staying on MF1 bootchain (SBLs/TZ/RPM) entirely with the VRALE6 unlocked bootloader, just to stay safe.

EDIT: No matter what, don't update any part of your bootchain beyond MF1.
 
Last edited:
  • Like
Reactions: dlainhart

Scott

Retired Recognized Developer
Depends which SBLs you're trying to flash, I would recommend staying on MF1 bootchain (SBLs/TZ/RPM) entirely with the VRALE6 unlocked bootloader, just to stay safe.

Yeah, thats what I thought...

I got the entire patch to take sans the firmware...

BUT....

It wont boot...

Here is build.prop as proof from recovery...

Just not sure where to go from here

Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KOT49H
ro.build.display.id=KOT49H.I535VRUDNE1
ro.build.version.incremental=I535VRUDNE1
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.date=Tue May 20 00:16:48 KST 2014
ro.build.date.utc=1400512608
ro.build.type=user
ro.build.user=dpi
ro.build.host=SWDD5809
ro.build.tags=release-keys
ro.product.model=SCH-I535
ro.product.brand=Verizon
ro.product.name=d2vzw
ro.product.device=d2vzw
ro.product.board=MSM8960
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8960
# ro.build.product is obsolete; use ro.product.device
ro.build.product=d2vzw
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=d2vzw-user 4.4.2 KOT49H I535VRUDNE1 release-keys
ro.build.fingerprint=Verizon/d2vzw/d2vzw:4.4.2/KOT49H/I535VRUDNE1:user/release-keys
ro.build.characteristics=verizon
# Samsung Specific Properties
ro.build.PDA=I535VRUDNE1
ro.build.hidden_ver=I535VRUDNE1
ro.build.changelist=1542239
ro.product_ship=true
ro.chipname=MSM8960
persist.sys.storage_preload=1
ro.build.knox.container=
# end build properties
#
# from device/samsung/d2vzw/system.prop
#
#
# system.prop for surf
#
# Evolution RIL (8xxx)
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
debug.sf.hw=1
debug.egl.hw=1
debug.composition.type=dyn
persist.hwc.mdpcomp.enable=true
debug.compbypass.enable=1
debug.hwui.render_dirty_regions=true
dalvik.vm.heapsize=36m
debug.enable.wl_log=1
debug.mdpcomp.maxlayer=3

#
# system props for the cne module
#
persist.cne.bat.range.low.med=30
persist.cne.bat.range.med.high=60
persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
persist.cne.bwbased.rat.sel=false
persist.cne.snsr.based.rat.mgt=false
persist.cne.bat.based.rat.mgt=false
persist.cne.rat.acq.time.out=30000
persist.cne.rat.acq.retry.tout=0
persist.cne.feature=0
#
# System prop for Tvout/HDMI
#
persist.sys.camera.connect=0
persist.sys.videomode=0
ro.hdmi.enable=true
lpa.decode=true
lpa.use-stagefright=true

audio.offload.disable=1

#system props for the MM modules

media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-scan=true
mmp.enable.3g2=true

# System props for audio
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
persist.audio.handset.mic=digital

#
# system props for call volume steps
#
ro.config.vc_call_vol_steps=7

# System prop to select audio resampler quality
af.resampler.quality=255
# System prop to select MPQAudioPlayer by default on mpq8064
mpq.audio.decode=true

#
# system prop for opengles version
#
# 131072 is decimal for 0x20000 to report version 2
# 196608 is decimal for 0x30000 to report version 3
ro.opengles.version=196608

#
# system property for Bluetooth Handsfree Profile version
#
ro.bluetooth.hfp.ver=1.6
#
#system prop for Bluetooth hci transport
ro.qualcomm.bt.hci_transport=smd
#
# system prop for requesting Master role in incoming Bluetooth connection.
#
ro.bluetooth.request.master=true
#
# system prop for Bluetooth Auto connect for remote initated connections
#
ro.bluetooth.remote.autoconnect=true
# system property for Bluetooth discoverability time out in seconds
# 0: Always discoverable
#debug.bt.discoverable_time=0

#system prop for switching gps driver to qmi
persist.gps.qmienabled=true

# System property for cabl
ro.qualcomm.cabl=1

#
# System prop for sending transmit power request to RIL during WiFi hotspot on/off
#
ro.ril.transmitpower=true

#
#Simulate sdcard on /data/media
#
persist.fuse_sdcard=true
ro.hwui.text_cache_width=2048

#
# Supports warmboot capabilities
#
ro.warmboot.capability=1

ro.sf.lcd_density=320

# System property for Default touch key light duration - commented out since default is 1500
#ro.button_key_light=6000

# System property for HDMI/WFD
persist.sys.camera.connect=0
persist.sys.camera.transform=0
persist.sys.videomode=0


# Use CDMALTE Phone
telephony.lteOnCdmaDevice=1

# Enable time services daemon
persist.timed.enable=true

# Keep SIM state on LPM mode
persist.radio.apm_sim_not_pwdn=1

# Don't wait the card state for RADIO POWER request
persist.radio.no_wait_for_card=1

# For sys info indication
persist.radio.add_power_save=1

# Snapshot Setting
persist.radio.snapshot_enabled=1
persist.radio.snapshot_timer=22

# Control EONS (true = EONS enabled, false = EONS disabled)
persist.eons.enabled=false

# Data modules
ro.use_data_netmgrd=false

# Use CP SE13 Table
persist.radio.use_se_table_only=1

# Default ECCList
ro.ril.ecclist=911,#911,*911

# Support Global Mode (Global Mode project)
ro.config.multimode_cdma=1
ro.telephony.default_network=10

# Restore delay of the default network - 30 mins (VZW)
android.telephony.apn-restore=1800000

# Restore delay of VZW Apps APN - 1 min (VZW)
vzw.telephony.appsapn-restore=60000

# Use data service state for signal display (Except SPR / USC / BST / VMU / CRI CS devices. PS ONLY devices use this property)
ro.config.combined_signal=true

# Retry Timer (VZW)
ro.gsm.data_retry_config=max_retries=infinite,5000,5000,60000,120000,480000,900000

# system property for vmware hypervisor running
vmware.hypervisor.running=0

#
# ADDITIONAL_BUILD_PROPERTIES
#
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.vendor.extension_library=/vendor/lib/libqc-opt.so
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=1m
dalvik.vm.heapmaxfree=4m
ro.build.scafe=americano
ro.build.scafe.syrup=sugar
ro.build.scafe.size=short
ro.hdcp2.rx=tz
ro.sec.fle.encryption=true
ro.secwvk=144
ro.securestorage.knox=true
ro.monkey=0
ro.config.ringtone=Verizon_Airwaves_1.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Walk_in_the_forest.ogg
ro.config.media_sound=Over_the_horizon_Acoustic.ogg
ro.error.receiver.default=com.samsung.receiver.error
ro.setupwizard.mode=OPTIONAL
ro.com.google.apphider=off
ro.com.google.clientidbase=android-samsung
ro.com.google.clientidbase.ms=android-verizon
ro.com.google.clientidbase.am=android-verizon
ro.com.google.clientidbase.yt=android-verizon
ro.com.google.clientidbase.gmm=android-samsung
ro.com.google.gmsversion=4.4.2_r2
ro.HorizontalVVM=true
persist.sys.dalvik.vm.lib=libdvm.so
ro.kernel.qemu=0
ro.build.selinux=1
ro.config.knox=v30
ro.config.tima=1
ro.config.timaversion=2.0
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.qc.sdk.izat.premium_enabled=0
ro.qc.sdk.izat.service_mask=0x0
persist.gps.qc_nlp_in_use=1
ro.gps.agps_provider=1



attachment.php
 

Attachments

  • IMAG0003.jpg
    IMAG0003.jpg
    94.5 KB · Views: 2,732

open1your1eyes0

Senior Member
Dec 13, 2010
2,651
3,671
New York City
Yeah, thats what I thought...

I got the entire patch to take sans the firmware...

BUT....

It wont boot...

Here is build.prop as proof from recovery...

Just not sure where to go from here

Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KOT49H
ro.build.display.id=KOT49H.I535VRUDNE1
ro.build.version.incremental=I535VRUDNE1
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.date=Tue May 20 00:16:48 KST 2014
ro.build.date.utc=1400512608
ro.build.type=user
ro.build.user=dpi
ro.build.host=SWDD5809
ro.build.tags=release-keys
ro.product.model=SCH-I535
ro.product.brand=Verizon
ro.product.name=d2vzw
ro.product.device=d2vzw
ro.product.board=MSM8960
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8960
# ro.build.product is obsolete; use ro.product.device
ro.build.product=d2vzw
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=d2vzw-user 4.4.2 KOT49H I535VRUDNE1 release-keys
ro.build.fingerprint=Verizon/d2vzw/d2vzw:4.4.2/KOT49H/I535VRUDNE1:user/release-keys
ro.build.characteristics=verizon
# Samsung Specific Properties
ro.build.PDA=I535VRUDNE1
ro.build.hidden_ver=I535VRUDNE1
ro.build.changelist=1542239
ro.product_ship=true
ro.chipname=MSM8960
persist.sys.storage_preload=1
ro.build.knox.container=
# end build properties
#
# from device/samsung/d2vzw/system.prop
#
#
# system.prop for surf
#
# Evolution RIL (8xxx)
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
debug.sf.hw=1
debug.egl.hw=1
debug.composition.type=dyn
persist.hwc.mdpcomp.enable=true
debug.compbypass.enable=1
debug.hwui.render_dirty_regions=true
dalvik.vm.heapsize=36m
debug.enable.wl_log=1
debug.mdpcomp.maxlayer=3

#
# system props for the cne module
#
persist.cne.bat.range.low.med=30
persist.cne.bat.range.med.high=60
persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
persist.cne.bwbased.rat.sel=false
persist.cne.snsr.based.rat.mgt=false
persist.cne.bat.based.rat.mgt=false
persist.cne.rat.acq.time.out=30000
persist.cne.rat.acq.retry.tout=0
persist.cne.feature=0
#
# System prop for Tvout/HDMI
#
persist.sys.camera.connect=0
persist.sys.videomode=0
ro.hdmi.enable=true
lpa.decode=true
lpa.use-stagefright=true

audio.offload.disable=1

#system props for the MM modules

media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-scan=true
mmp.enable.3g2=true

# System props for audio
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
persist.audio.handset.mic=digital

#
# system props for call volume steps
#
ro.config.vc_call_vol_steps=7

# System prop to select audio resampler quality
af.resampler.quality=255
# System prop to select MPQAudioPlayer by default on mpq8064
mpq.audio.decode=true

#
# system prop for opengles version
#
# 131072 is decimal for 0x20000 to report version 2
# 196608 is decimal for 0x30000 to report version 3
ro.opengles.version=196608

#
# system property for Bluetooth Handsfree Profile version
#
ro.bluetooth.hfp.ver=1.6
#
#system prop for Bluetooth hci transport
ro.qualcomm.bt.hci_transport=smd
#
# system prop for requesting Master role in incoming Bluetooth connection.
#
ro.bluetooth.request.master=true
#
# system prop for Bluetooth Auto connect for remote initated connections
#
ro.bluetooth.remote.autoconnect=true
# system property for Bluetooth discoverability time out in seconds
# 0: Always discoverable
#debug.bt.discoverable_time=0

#system prop for switching gps driver to qmi
persist.gps.qmienabled=true

# System property for cabl
ro.qualcomm.cabl=1

#
# System prop for sending transmit power request to RIL during WiFi hotspot on/off
#
ro.ril.transmitpower=true

#
#Simulate sdcard on /data/media
#
persist.fuse_sdcard=true
ro.hwui.text_cache_width=2048

#
# Supports warmboot capabilities
#
ro.warmboot.capability=1

ro.sf.lcd_density=320

# System property for Default touch key light duration - commented out since default is 1500
#ro.button_key_light=6000

# System property for HDMI/WFD
persist.sys.camera.connect=0
persist.sys.camera.transform=0
persist.sys.videomode=0


# Use CDMALTE Phone
telephony.lteOnCdmaDevice=1

# Enable time services daemon
persist.timed.enable=true

# Keep SIM state on LPM mode
persist.radio.apm_sim_not_pwdn=1

# Don't wait the card state for RADIO POWER request
persist.radio.no_wait_for_card=1

# For sys info indication
persist.radio.add_power_save=1

# Snapshot Setting
persist.radio.snapshot_enabled=1
persist.radio.snapshot_timer=22

# Control EONS (true = EONS enabled, false = EONS disabled)
persist.eons.enabled=false

# Data modules
ro.use_data_netmgrd=false

# Use CP SE13 Table
persist.radio.use_se_table_only=1

# Default ECCList
ro.ril.ecclist=911,#911,*911

# Support Global Mode (Global Mode project)
ro.config.multimode_cdma=1
ro.telephony.default_network=10

# Restore delay of the default network - 30 mins (VZW)
android.telephony.apn-restore=1800000

# Restore delay of VZW Apps APN - 1 min (VZW)
vzw.telephony.appsapn-restore=60000

# Use data service state for signal display (Except SPR / USC / BST / VMU / CRI CS devices. PS ONLY devices use this property)
ro.config.combined_signal=true

# Retry Timer (VZW)
ro.gsm.data_retry_config=max_retries=infinite,5000,5000,60000,120000,480000,900000

# system property for vmware hypervisor running
vmware.hypervisor.running=0

#
# ADDITIONAL_BUILD_PROPERTIES
#
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.vendor.extension_library=/vendor/lib/libqc-opt.so
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=1m
dalvik.vm.heapmaxfree=4m
ro.build.scafe=americano
ro.build.scafe.syrup=sugar
ro.build.scafe.size=short
ro.hdcp2.rx=tz
ro.sec.fle.encryption=true
ro.secwvk=144
ro.securestorage.knox=true
ro.monkey=0
ro.config.ringtone=Verizon_Airwaves_1.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Walk_in_the_forest.ogg
ro.config.media_sound=Over_the_horizon_Acoustic.ogg
ro.error.receiver.default=com.samsung.receiver.error
ro.setupwizard.mode=OPTIONAL
ro.com.google.apphider=off
ro.com.google.clientidbase=android-samsung
ro.com.google.clientidbase.ms=android-verizon
ro.com.google.clientidbase.am=android-verizon
ro.com.google.clientidbase.yt=android-verizon
ro.com.google.clientidbase.gmm=android-samsung
ro.com.google.gmsversion=4.4.2_r2
ro.HorizontalVVM=true
persist.sys.dalvik.vm.lib=libdvm.so
ro.kernel.qemu=0
ro.build.selinux=1
ro.config.knox=v30
ro.config.tima=1
ro.config.timaversion=2.0
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.qc.sdk.izat.premium_enabled=0
ro.qc.sdk.izat.service_mask=0x0
persist.gps.qc_nlp_in_use=1
ro.gps.agps_provider=1

Hmm...maybe @BeansTown106 or @invisiblek can throw in some input here.
 

invisiblek

Recognized Developer
Feb 24, 2010
1,580
5,833
Minnesota
www.invisiblek.org
Yea, these days mismatching firmware is a bad idea. Samsung has been signing using different keys on their releases (hence the old d2vzw aboot not working anymore). I'd highly recommend flashing the entire chain (sbls, aboot, tz, rpm) unless you are pre-4.3.

Sent from my One M8 using Tapatalk
 

open1your1eyes0

Senior Member
Dec 13, 2010
2,651
3,671
New York City
Im certainly open to suggestions but I have a stinking feeling about this build requiring the firmware to boot up 100%

Wasn't ML1 and NC1 able to work on the MF1 bootchain, just needed the Wifi kernel fix? I would be surprised (but not shocked of course) if NE1 would require the new bootchain to even boot.

Yea, these days mismatching firmware is a bad idea. Samsung has been signing using different keys on their releases (hence the old d2vzw aboot not working anymore). I'd highly recommend flashing the entire chain (sbls, aboot, tz, rpm) unless you are pre-4.3.

Sent from my One M8 using Tapatalk

If I'm not mistaken I believe he is still pre-4.3 (noted by the screenshot of TWRP on there).

FWIW, I currently have MF1 bootchain (SBLs/TZ/RPM), ML1 radio, and LE6 (unlocked) aboot, running CM11 no issues. I don't think it gets anymore mismatched than that. :p
 
Last edited:

invisiblek

Recognized Developer
Feb 24, 2010
1,580
5,833
Minnesota
www.invisiblek.org
If I'm not mistaken I believe he is still pre-4.3 (noted by the screenshot of TWRP on there).

FWIW, I currently have MF1 bootchain (SBLs/TZ/RPM), ML1 radio, and LE6 (unlocked) aboot, running CM11 no issues. I don't think it gets anymore mismatched than that. :p
Yea, modem isn't signed, so we can continue to update that. The switched the keys after MF1, so don't mismatch beyond that, or you're not going to be compatible with the LE6 aboot.

Sent from my One M8 using Tapatalk
 
  • Like
Reactions: Scott

Scott

Retired Recognized Developer
Yea, modem isn't signed, so we can continue to update that. The switched the keys after MF1, so don't mismatch beyond that, or you're not going to be compatible with the LE6 aboot.

Sent from my One M8 using Tapatalk

Ok, makes sense then...


Also, here is what I found... I flashed my own 4.3 kerenel and it starts to boot.

Does that give any indication of anything at all?
 

open1your1eyes0

Senior Member
Dec 13, 2010
2,651
3,671
New York City
Yea, modem isn't signed, so we can continue to update that. The switched the keys after MF1, so don't mismatch beyond that, or you're not going to be compatible with the LE6 aboot.

Sent from my One M8 using Tapatalk

Makes sense. Hopefully @scrosler can figure out why NE1 is not booting for him on MF1 bootchain.

---------- Post added at 01:32 AM ---------- Previous post was at 01:31 AM ----------

Ok, makes sense then...


Also, here is what I found... I flashed my own 4.3 kerenel and it starts to boot.

Does that give any indication of anything at all?

4.3 kernel on NE1? It actually boots?
 

Scott

Retired Recognized Developer
Makes sense. Hopefully @scrosler can figure out why NE1 is not booting for him on MF1 bootchain.

---------- Post added at 01:32 AM ---------- Previous post was at 01:31 AM ----------



4.3 kernel on NE1? It actually boots?

No no... With the stock kernel, it would not get to the Samsung Splash screen...

With my ML1 Kernel on MF1 bootchain it gets to the Splash screen but no further.

I am going to upload this dump if anyone wants to play with it.
 

open1your1eyes0

Senior Member
Dec 13, 2010
2,651
3,671
New York City
No no... With the stock kernel, it would not get to the Samsung Splash screen...

With my ML1 Kernel on MF1 bootchain it gets to the Splash screen but no further.

I am going to upload this dump if anyone wants to play with it.

Hmm...I'm guessing most likely we'll need source to get this safely figured out.

The way I see it, this is likely our final update from Samsung so a little patience to work out all the kinks is worth it. :)

But Sammy definitely needs to hurry up with that source. :p
 
  • Like
Reactions: suchavibrantthang

Scott

Retired Recognized Developer
Hmm...I'm guessing most likely we'll need source to get this safely figured out.

The way I see it, this is likely our final update from Samsung so a little patience to work out all the kinks is worth it. :)

But Sammy definitely needs to hurry up with that source. :p

Im pretty sure its going to come down to kernel to...

I got the dump uploading to goo.im. I will post it for everyone in a little while
 

reno218

Member
Dec 13, 2010
37
1
Okay so i was a little drunk wihle trying to do this... I accidently odin s3vzw_4.4.2.tar while I was still on 4.3 I think that's whats screwed me over. I think once I can odin 4.4.2 Itll be fine I just can't find a file to do that yet,
 

ThePagel

Senior Member
Jul 6, 2012
1,479
839
Minneapolis
Okay so i was a little drunk wihle trying to do this... I accidently odin s3vzw_4.4.2.tar while I was still on 4.3 I think that's whats screwed me over. I think once I can odin 4.4.2 Itll be fine I just can't find a file to do that yet,

I'm right about to check to see if I can snatch it from Verizon so cross your fingers

*edit*
no suck luck so I'm assuming you didn't cross your fingers
 
Last edited:
  • Like
Reactions: old&slow

bchi49

Senior Member
Feb 6, 2008
136
4
This is FUD. You've been misled. Custom roms do not touch unlocked bootloaders or require exotic engineering to keep things that way.

If you've unlocked your bootloader anytime within the past 2 years, you're set. You don't need to do anything. Just don't take the damn OTA. You should be on a custom rom or have already disabled such OTA functionality manually. If you take the OTA, you are screwed no matter what.

There's no frankenkernels or frankenroms. If you want to make a rom based on the update for normal folks who were smart enough to keep their bootloader unlocked, you simply remove the bootloader files altogether from the OTA tar/zip and begin customizing. You can use the stock kernel or compile your own using the source Samsung provided. For the poor souls who are locked down, they are stuck with the stock kernel and SafeStrap. Only thing they can modify is the system partitions they create.

There's nothing "franken" about either approach.

The only people with weird bootloader configurations are those who dipped in and out of OTA sequencing. Maybe their SBL or RPM/TZ partitions are stuck at LF2 or something just as ancient.

Ideally, every binary partition should be at firmware MF1 except for the aboot at LE6. My modem is at ML1 for the hell of it since flashing modems (even from the locked down 4.3 OTA) is safe.

tl;dr The unlocked rom scene is not impacted by Knox or anything OTAs lock down. It exists outside of the walled garden Verizon and Samsung are trying to create.


I'm on 4.3 ROM, had MF1 modem, then updated the modem to to ML1. I was able to update the bootloader. But when I came from Hong Kong to USA, and swap back the SIM I realized my boot loader is locked, e.g. security kernel failed. I had to use stock bootloader. I guess the bootloader is locked? Something must have triggered it....

I have problem updating to NC1 via settings, I wanted it to update to 4.4.2 if my bootloader is truely locked. How do I tell if it's t ruely locked?

Seems like I need to Odin to 4.3. If I odin to 4.1.2 will it just be soft brick if it fails? Thanks.

Sent from my SCH-I535 using XDA Free mobile app
 

SlimSnoopOS

Senior Member
Jan 29, 2011
8,052
3,348
I'm on 4.3 ROM, had MF1 modem, then updated the modem to to ML1. I was able to update the bootloader. But when I came from Hong Kong to USA, and swap back the SIM I realized my boot loader is locked, e.g. security kernel failed. I had to use stock bootloader. I guess the bootloader is locked? Something must have triggered it....

I have problem updating to NC1 via settings, I wanted it to update to 4.4.2 if my bootloader is truely locked. How do I tell if it's t ruely locked?

Seems like I need to Odin to 4.3. If I odin to 4.1.2 will it just be soft brick if it fails? Thanks.

Sent from my SCH-I535 using XDA Free mobile app

Easiest way to tell, boot into download mode and post what is displayed on the screen. If you see "Warranty Bit RP SWERV" towards the bottom then that is at least JB 4.3 which comes with a locked bootloader. You'll want to Odin flash VRUCML1. Do not Odin flash anything before JB 4.3, if you see Warranty bit in download mode.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 19
    If I were everyone in this thread...

    I would just chill out for a while... ;)
    14
    For d2vzw SCH-I535 ONLY


    This is the official tar ball for VRUDNE1. DO NOT DOWNLOAD THIS FILE UNLESS YOU ARE 100% SURE YOU KNOW WHAT YOU ARE DOING. Any locked bootloaders are not my fault.


    THIS WILL LOCK YOUR BOOTLOADER FOREVER


    4.4.2 VRUDNE1 full wipe tar download HERE





    4.4.2 Update Zip
    For reasons that should be obvious I recommend not to update yet unless you really cant wait. This zip was ripped out of the ota download folder I have not applied it myself so use at your own risk.

    There has been successful upgrades using this update zip.


    I am assuming you must be on a untouched version of nc1 for this to work (no root) apply update zip in stock recovery.

    Download the 4.4 update zip from HERE
    5
    i played the stupid card and softbricked my S3. i was in a curious mood and wanted to go back to a fresh 4.3 to get to a fresh 4.4.2. is there anyway for me to unbrick it with or without losing my data (preferrably losing because i want a fresh start). Does anybody know when a tar will be ready or when the file will be available through the Verizon Repair Assistant?

    flash this via odin if you bricked your bootloader!
    contain: tz.mbn sbl3.mbn sbl2.mbn rbm.mbn aboot.mbn

    flash on VRUDNE1 kitkat tw only
    5
    My understanding is that this is going to be similar to the gs4 where there are frankenkernels and frankenroms hacked together to keep our bootloader unlocked. This isn't as reliable as the straight kernel. Correct me if I'm wrong that was just the impression I got.

    Sent from my SCH-I535 using XDA Premium 4 mobile app

    This is FUD. You've been misled. Custom roms do not touch unlocked bootloaders or require exotic engineering to keep things that way.

    If you've unlocked your bootloader anytime within the past 2 years, you're set. You don't need to do anything. Just don't take the damn OTA. You should be on a custom rom or have already disabled such OTA functionality manually. If you take the OTA, you are screwed no matter what.

    There's no frankenkernels or frankenroms. If you want to make a rom based on the update for normal folks who were smart enough to keep their bootloader unlocked, you simply remove the bootloader files altogether from the OTA tar/zip and begin customizing. You can use the stock kernel or compile your own using the source Samsung provided. For the poor souls who are locked down, they are stuck with the stock kernel and SafeStrap. Only thing they can modify is the system partitions they create.

    There's nothing "franken" about either approach.

    The only people with weird bootloader configurations are those who dipped in and out of OTA sequencing. Maybe their SBL or RPM/TZ partitions are stuck at LF2 or something just as ancient.

    Ideally, every binary partition should be at firmware MF1 except for the aboot at LE6. My modem is at ML1 for the hell of it since flashing modems (even from the locked down 4.3 OTA) is safe.

    tl;dr The unlocked rom scene is not impacted by Knox or anything OTAs lock down. It exists outside of the walled garden Verizon and Samsung are trying to create.
    4
    I'm not going to be able to upload it to a faster place to download until around ten tonight so instead of Sam mobile you guys should use kies or the Verizon tool. The Verizon tool might be implementing it right now if that's so it will tell you there was a connection error.

    FYI for a faster download: http://xdaforums.com/showthread.php?t=2795659