[REF][ROM]Recovery Flashable Stock SM-N900V ROMs

[bftb0]

That is the TWRP I was using though (twrp-3.0.2-0-hltevzw-4.4)

Sure about that?

assert(getprop("ro.product.device") == "SM-N900V" || getprop("ro.build.product") == "SM-N900V" || getprop("ro.product.device") == "hltevzw" || getprop("ro.build.product") == "hltevzw" || abort("This package is for device: SM-N900V,hltevzw; this device is " + getprop("ro.product.device") + "."););

I just looked - I used the identical assert() statement in the META-INF/com/google/android/updater-script of every one of those ROM files.

Note that the above assert() only reaches the abort() error message if all of the of the prior conditions have resulted in a "false" (=0) value. I think that (lazy evaluation behavior) is called "logical OR short-circuiting" or something. (The first condition which is true causes the whole thing to be true, so no need to evaluate anything to the right in the chain... so the thing on the end only occurs when everything else has failed.)

In any event, note that when it spews the the error message it does this:

"... this device is " + getprop("ro.product.device") + ...

based on your own report of the error message, that means that the read only init property value of "ro.product.device" was set to "hlte", not "hltevzw" when you got that error message.


If you haven't changed your TWRP, you can boot into it and take a look. Just use the TWRP's Advanced->Terminal and do a

grep device /default.prop

and find out what is in there.

There's other ways of making that check too without booting up in the recovery. Find out how many bytes long the twrp-3.0.2-0-hltevzw-4.4.img file is, and compute it's MD5 checksum ( "md5sum" command )

Then dump the exact same number of bytes out of the recovery partition and pipe that output into the md5sum command to cross-check the hash. If they are different, you've got something else installed in there.

$ ls -ld twrp-3.0.2-0-hltevzw-4.4.img
-rwxr-xr-x 1 user user 10385408 Apr 27 2016 twrp-3.0.2-0-hltevzw-4.4.img

$ md5sum twrp-3.0.2-0-hltevzw-4.4.img
b4c2206bcc5e1f553a239b16940e9d38 twrp-3.0.2-0-hltevzw-4.4.img

dd if=/dev/block/mmcblk0p15 bs=10385408 count=1 | md5sum

good luck and safe travels.

.

 

[pnuker]

Thanks bftb0, I've got it sorted out now. You were right, I somehow managed to get the wrong version of TWRP.

 

[adriascw]

Hi, I'm on the Resurrection Remix 6.0 rom from this forum and I'm not getting 4g lte, only 3g, with my Straight talk sim card ( which uses the exact same towers as Verizon) and was wondering if flashing a modem with Odin could potentially help this issue?

 

[bftb0]

Hi, I'm on the Resurrection Remix 6.0 rom from this forum and I'm not getting 4g lte, only 3g, with my Straight talk sim card ( which uses the exact same towers as Verizon) and was wondering if flashing a modem with Odin could potentially help this issue?

I'm not entirely sure but in the past it has been typical that MVNO subscribers did not have access to "the latest" (i.e. fastest mobile data transfer) technology that are available on the "real" carrier network - even if the phone is identical.

It's a business thing, not a technology issue. Big Red doesn't want you to have identical service to what they offer themselves but at a discount price through their MVNO resellers. Otherwise all their "premium" customers would just bail out for the MVNO.

I doubt that behavior is ever going to go away, but it could manifest itself in other ways - for instance, you could get (e.g.) LTE with a MVNO but only with tiny data caps. The real (as opposed to "virtual") carriers have to retain something for themselves to induce customers to continue to pay for the premium services.

Marketing 101 = Product (or service) differentiation.

 

[golfslicer]

Nice post for downloads. Currently Running EPL1 and I debloated a lot with titanium backup. Too bad the install zip doesn't have the files already extracted so a custom rom can be easily created. EPL works better than previous version as far as phone call quality. To get best results, the EPL modem must also be updated. Thanks for taking the time to upload these so we don't have to lose twrp and root.

 

[bftb0]

@golfslicer

Thanks for the props.

Too bad the install zip doesn't have the files already extracted so a custom rom can be easily created.

Nah, you just need to up your game. See here.

Those tools from @xpirt are the reasons these ROMs exist - they remove the tedious and error-prone process of hand-creating the old style of "updater-script".

These links are also helpful:

mkboot { xiaolu }
img2simg/simg2img { aosp/cm? } e.g. here
img2sdat.py & sdat2img.py { @xpirt - luxi78 - howellzhu}

.

 

[njdan30]

Hi, I'm on the Resurrection Remix 6.0 rom from this forum and I'm not getting 4g lte, only 3g, with my Straight talk sim card ( which uses the exact same towers as Verizon) and was wondering if flashing a modem with Odin could potentially help this issue?

Check your apn for LTE some use Verizon apn and some use the reseller apn vzwentp or something like that. That was my issue with lte but I've moved to another carrier now.

Sent from my SM-G955U using Tapatalk

 

[yenkoPR]

can anyone do a backup of the modem PL1 via twrp and send it to me? i dnt have a pc to flash on odin

 

[seadooman]

NC4 over OF1

So it is possible to flash NC4 with a note 3 that has already had OF1 installed?
Are these to be used with TWRP or Flashify?

 

[bftb0]

So it is possible to flash NC4 with a note 3 that has already had OF1 installed?
Are these to be used with TWRP or Flashify?

These are meant to be used with TWRP. I suppose it is possible that Flashify could work, but I have never tested such a thing. So the usual disclaimer that you are completely on your own to try it.

Along the same lines, the phone that I booted/tested all these on had (and still has) the NC4 bootloader firmware, so I can't answer your first question definitively. It is possible that it would work. Other than the hassle of getting a Note 3 completely backed up and ready for a new ROM install, it shouldn't be dangerous to try it on a phone with a unlocked bootloader. If it doesn't boot, reboot to TWRP and install some other ROM or restore your backups.

Note the boldface above about unlocked bootloader. A device that boots an unsigned custom kernel (e.g. a custom recovery such as TWRP) clearly has an unlocked bootloader; whereas with a Note 3 that is only rooted and not bootloader unlocked, performing an install via something like Flashify would certainly soft-brick the phone, requiring you to Odin back to pure stock and start over with rooting.

That's because in addition to the anti-rollback provisions, a locked-bootloader Note3 will not boot any kernel - even fully signed, stock, Samsung kernels! - if the bootloader and kernel are even slightly version mis-matched.


safe travels.

 

[seadooman]

Flashed OF1 with twrp-3.1.1-0-hlte and getting error 7. I used this version to flash lineage.

Verizon note 3
Unlocked boot loader and rooted
Any ideas?

Found the answer. Right here in the same forum think I must be going cross-eyed reading through here.
Thanks to all. Happy Thanksgiving

 

[seadooman]

Thanks bftb0, I've got it sorted out now. You were right, I somehow managed to get the wrong version of TWRP.

Same error 7 ,what version of twrp did you use?

 

[seadooman]

Version of TWRP?

What version number of TWRP are you using? Tried all weekend and keep getting error 7. Help!

 

[Slenderman8090]

What version number of TWRP are you using? Tried all weekend and keep getting error 7. Help!

You will have to use TWRP 2.8.7.0 AS THAT IS the only fully working version. As you can tell Marshmallow/Lollipop TWRP is laggy and broken is some areas.

 

[donc113]

You will have to use TWRP 2.8.7.0 AS THAT IS the only fully working version. As you can tell Marshmallow/Lollipop TWRP is laggy and broken is some areas.

Not true.

https://forum.xda-developers.com/showthread.php?t=2879345


Make sure you get the 3.0.2-0hltevzw version



Sent from my SM-N900V using Tapatalk

 

[PresidentJason]

E: Footer is wrong E:Signature verification failed

I'm on PL1 and I've tried to flash a few of these ROMs and don't seem to be working because after the phone boots the version is still PL1. Any solutions would be much appreciated.
This is what I see...

# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : VZW
Successfully applied multi-CSC.

-- Install /sdcard/N900VVRUEOF1_flashable_OTAsuppressed_v0.5.zip ...
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong
E:signature verification failed
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong
E:signature verification failed

Install from sdcard complete.
Applying update complete.

 

[seadooman]

I followed the instructions but must have wiped something I should not have. My phone would not boot afterwards, had no recovery. All I could get to was the screen for flashing, so I loaded the oem software,rooted and then unlocked the boot loader. Flashed Lineage but have been having some trouble with the modems. Anyway what did I do wrong when I wiped the system? I followed Wipe system, dalvik, cache, and data (do not wipe /data/media). When I did this it wiped the recovery? Any Ideas?????

 

[seadooman]

Okay how about this. I flashed lineage with the hlte twrp, now I would like to flash back to stock with this file. If I use flashify to install the verizon version of twrp should that be enough?

 

[seadooman]

Can these files be flashed with flashify? Last time I tried changing to the correct recovery for Verizon something went wrong and ended up flashing on software and starting all over.

---------- Post added at 08:19 AM ---------- Previous post was at 08:16 AM ----------

I'm running into an error when flashing the ROM in TWRP:



My phone is a N900V.

---------- Post added at 02:12 PM ---------- Previous post was at 01:29 PM ----------



*Update*
Nevermind, I managed to get it working by editing the \META-INF\com\google\android\updater-script, replacing all 'hltevzw' with 'hlte', and updating the zip.

Any chance you could post the software? I tried renaming and zipping back up and now get. The error invalid zip.

 

[krishaun27]

"These flashable .zip ROMs ONLY modify the "system" and "boot" partitions. No bootloader firmware, modem firmware, or recovery partitions are affected; nor are wipes performed on any other partitions."

So if I flash these stock roms in Odin they won't relock my bootloader?