Anyone know if they can be ported over to us?
http://forum.xda-developers.com/galaxy-note-3/general/guide-t2983873
Unfortunately not
I'd imagine that unless if we can figure out a way to get this leaked build to work with the NC2/NC4 bootloader/kernel and SafeStrap and what not that it won't work for us as of now. I don't think it's impossible but I'm not 100% sure it could be done...
Edit: What we need at this point is a pure stock flashable version of this leak. Then we can go from there.
Edit 2: Okay I'm silly here. I found a list of ROMs that are out for the SM-9005 so I wonder how hard it would be to port one of them with some of the fixes like WiFi over to our Verizon Note 3?
http://forum.xda-developers.com/gal.../lollipop-android-5-rom-list-updated-t2984365
So I'm thinking here's the challenges we'd have:
1 - Making this work with our NC2/NC4 bootloader and kernel. Now I dunno if that can be done but I've seen stranger things happen.
2 - Keeping KNOX set to 0x0. It looks like at least one ROM has that covered (forgot which one).
3 - Getting this to work with our SafeStrap 3.75. I'd imagine if we can get it to work with our kernel/bootloader then we'd have no issues here but who knows.
4 - We might need to do a few file replacements and edits to get data and what not to work. I remember when I helped port SkyNote 4.3 from AT&T to Verizon on the Note 2 (which was based off a leak for the AT&T Note 2 for 4.3 JellyBean) there was a few file swaps I had to do from the Verizon 4.2 base to get data to work (along with build.prop edits).
this would be awesome, heres hoping!
Okay I used the deodex ROM found here.
http://forum.xda-developers.com/galaxy-note-3/development/rom-t2983506
I replaced the kernel in this with the one from EclipseROM 2.1.1. It'll install and will get past the Samsung logo and that's it. I get a blank screen for several minutes then reboots to Samsung recovery. Thankfully I can still restore back to EclipseROM so nothing really lost on my end except for a slight amount of time in trying. I'm assuming the issue lies in with us not having a proper 5.0 bootloader. There has to be a way to make this work on our NC2/NC4 bootloader.
(And I'm asking out of kindness let's keep the "can't wait for this" and "hope this works" comments off of the thread so we can discuss how to get this working - thanks I'm not trying to be mean but I'd like to keep this thread clean and for discussing how to get this working)
I am wondering if you need a modified kernel for it to work. I am not entirely sure it's a bootloader issue(not saying its not). That being said on my DE I can run 4.4 roms on a 4.3 bootloader with a modified kernel that hashcode made.
That is true. Sadly unless if we can modify the kernel (or get Kexec working) we are stuck waiting for Lollipop to either leak or officially hit our Note 3. And given that the recent 4.4.4 update changed the bootloader (and killed our current root exploit) the signs aren't good for us on Lollipop at this point.
the leak is for the octa core enxyos version so completely different soc verizon, att, sprint and tmobile all use qualcomm 800 quad core soc.
So if your on an international version likely you can use some version of the leak. For us stuck with the US version we have to wait till a carrier specific one leaks.
Related
So taking a look around the net today, I came across an article that states that you can flash Kitkat onto N900 (Galaxy Note 3) using Odin... Does/Would this also include the Verizon version of the Note 3? I was under the belief that Verizon's bootloader didn't allow for KitKat installations because of some kernel compatibility issue or something keeping it from working... But would this allow for a Kitkat working install on (non-dev-edition) Ver-Note3? And if so, would this allow lay the groundwork for devs to be able to create install-able kitkat roms for said device? Any and all info/help on this would be greatly appreciated, as I'm sure there's a great deal of want for people with the Verizon Note 3 to be able to have KitKat, myself included!
TToTT said:
So taking a look around the net today, I came across an article that states that you can flash Kitkat onto N900 (Galaxy Note 3) using Odin... Does/Would this also include the Verizon version of the Note 3? I was under the belief that Verizon's bootloader didn't allow for KitKat installations because of some kernel compatibility issue or something keeping it from working... But would this allow for a Kitkat working install on (non-dev-edition) Ver-Note3? And if so, would this allow lay the groundwork for devs to be able to create install-able kitkat roms for said device? Any and all info/help on this would be greatly appreciated, as I'm sure there's a great deal of want for people with the Verizon Note 3 to be able to have KitKat, myself included!
Click to expand...
Click to collapse
This applies to the international version only sm-900 witch has a unlocked bootloader. I'm almost positive someone here tried it and bricked their phone.
I'm very interested in switching from my stock Verizon Note 3 ROM to CyanogenMod, but after a great deal of research I cannot tell with absolute certainty if http://wiki.cyanogenmod.org/w/Hlte_Info is the correct ROM for use with my Verizon Note 3. Is it the correct ROM?
Additionally, if http://wiki.cyanogenmod.org/w/Hlte_Info is the correct ROM for use with my Verizone Note 3, how do I work around their posted notice as follows? Such as, are there specific instructions for using ODIN?
"If you've applied the 4.4.x update to your hlte device, it is possible heimdall will have communication issues with your device. This is a filed bug already on the heimdall page and this warning will be removed when it is resolved. In the meantime, ODIN still works."
Karine said:
I'm very interested in switching from my stock Verizon Note 3 ROM to CyanogenMod, but after a great deal of research I cannot tell with absolute certainty if http://wiki.cyanogenmod.org/w/Hlte_Info is the correct ROM for use with my Verizon Note 3. Is it the correct ROM?
Additionally, if http://wiki.cyanogenmod.org/w/Hlte_Info is the correct ROM for use with my Verizone Note 3, how do I work around their posted notice as follows? Such as, are there specific instructions for using ODIN?
"If you've applied the 4.4.x update to your hlte device, it is possible heimdall will have communication issues with your device. This is a filed bug already on the heimdall page and this warning will be removed when it is resolved. In the meantime, ODIN still works."
Click to expand...
Click to collapse
If you are on RETAIL VZW N3, there is NO WAY to have anything but a stock or cutsom stock ROM.
If you are on a DEV EDITION VZW N3, check here.
I have the retail Verizon Note 3, and all other resources I've encountered indicate that the link I provided is a universal ROM for all Note 3.
Karine said:
I have the retail Verizon Note 3, and all other resources I've encountered indicate that the link I provided is a universal ROM for all Note 3.
Click to expand...
Click to collapse
That is universal for the international versions, which there are many. Without an unlocked bootloader, we cannot flash aosp, aokp, or cm based roms.
The bootloader issue is what prevents compatibility with the CM installer, but I don't believe it prevents ROM flashes through other means. And I've seen several threads that specifically state that universal covers Sprint, Verizon, etc.
Karine said:
The bootloader issue is what prevents compatibility with the CM installer, but I don't believe it prevents ROM flashes through other means. And I've seen several threads that specifically state that universal covers Sprint, Verizon, etc.
Click to expand...
Click to collapse
Ok. And why isn't this info blowing up the Verizon Note 3 forums? If I'm wrong, I'll admit that. But many smarter people that me have stated time and time again that it's not going to work. And I have seen no information that will lead me to believe otherwise. Can you provide links to where it's being stated we can flash this?
That's why I'm here, to sort whether it will work as all the information available seems unclear and split.
Ok, I got ya. There is info burried here. But as I understand it the ability to install custom roms requires an unlocked bootloader. When we got that leak of kk nc2, we obtained a locked bootloader the had a few "holes" in it (for lack of a better term). With that bootloader, there is the possibility of some exploits that can be applied in order to give us the ability to flash a cm rom amongst other things. But we're not there yet.
Best I can give you is to watch this thread for any news or development:
http://forum.xda-developers.com/showthread.php?t=2812650
Many thanks for the link.
I'm gonna back up Lefty here.
The retail version has a locked bootloader, which means we can't install a custom recovery or an alternate kernel, both of which are required to install non-touchwiz ROMs. (Not the case for the dev edition, which you would know if you had)
This is Verizon's doing. Samsung will provide phones with unlocked bootloaders to cellular companies, but verizon wants them locked down. I believe the only US company that sells bl-unlocked phones is T-Mobile. Lots of international carriers are bl-unlocked.
CM is mostly "universal" across ALL devices, because its based on AOSP straight from Google, and just has to be tweaked slightly for hardware differences. That's why CM builds for a note3 are "universal" -- the hardware is all the same. This comes at a price... last I've heard, the s-pen is just emulated as a mouse input, which is a bastardization of the technology. This is just an example. There are several compromises to running AOSP roms.
Sent from my SM-N900V using Tapatalk
Thanks for the great information. It's a shame that Verizon or anyone else locks the bootloader. It should be no matter to them what ROM I run.
Looking to purchase a Sammy s5 and am not familiar with flashing since my Galaxy nexus days. (those were the days lol) Been in the Motorola boat for some time.
Base band shows G900VVRU1BOCA and according to Samsung's website, I believe this means it's at the LP version at this point. Any problems flashing back to KK to root etc that I need to be aware of?
Thanks in advance.
grnsl2 said:
Looking to purchase a Sammy s5 and am not familiar with flashing since my Galaxy nexus days. (those were the days lol) Been in the Motorola boat for some time.
Base band shows G900VVRU1BOCA and according to Samsung's website, I believe this means it's at the LP version at this point. Any problems flashing back to KK to root etc that I need to be aware of?
Thanks in advance.
Click to expand...
Click to collapse
That was probably OC4. No problem downgrading, rooting, then upgrading again and keeping root.
I had one of those Galaxy Nexus's too. Nothing could be as fun as those were. Flash a different rom and kernel every day for at least a month.
So Ive had this Verizon Note 3 since day one. Finally unlocked my bootloader... What are the rules on what I can and can't do now. Can I install any Android rom? Can I only install note 3 roms from any carrier... Can I install only Verizon note 3 roms? Or is it a hybrid... I can install any rom if I replace the firmware and or modem.
I really want something on 7.1 but I'd rather take 6 and have something custom... Fast and responsive.
Thanks community.
You are in luck. :crying:
There's hardly anything to choose from; maybe 3 or 4 ROMs and about the same number of kernels.
AFAIK, there are no Nougat ROMs and only one Marshmallow ROM (AryaMod6.6).
Normally, when a dev ships a "ROM", there are two important pieces: the /system image (what some folks call "the ROM"), and the boot image. The boot image is what some folks erroneously call "the kernel"; but it is really a combination of kernel + ramdisk. The ramdisk has all the scripts in it that the "init" process reads to start up all the low-level daemons and services... as well as the Android UI as well.
The kernel is very tightly tied to the specific hardware in a given handset - both the processor/gpu and all the sensors/leds/peripherals.
So that's the reason you can't just flash any old ROM. In the least bad case, your device wouldn't boot; in the worst bad case the kernel would boot up far enough go off in the weeds and possibly damage some of your hardware.
You might be tempted to think "we'll, what if I find a boot image for the "hltevzw" SM-N900V device... can I flash that after I have flashed 'any old Android ROM'? Won't that take care of things?"
Well, not really. The system library binaries in /system are possibly compiled with instruction-set optimumization tweaks that are only supported by specific CPU and GPU hardware chips. Moreover, other peripheral chips such as GPS have unique "downloadable" vendor firmware in the system image... so again, there's the issue of hardware dependencies of the /system image.
Beyond that, there's carrier-specific "setup and activation" software that differs between ROMs, so even using ROMs that are from a different carrier's version of the exact same handset hardware might not work fully - specifically in the telephony function areas. Everything else might work fine though. For instance if you wanted to use the device as a WiFi-only unit for kid's games etc.
Note BTW that the "International" Note 3 GSM phones are not the same hardware - they use an Exynos processor.
good luck in your quest
Thanks
That was very helpful... Looks like Araya is my best bet. I'll leave jasmine rom to try it.
I was hoping that I could get another note 3 rom on this forum and flash the CDMA modem for networking... But doesn't seem like that's an option.
If I'm still stuck to Verizon Note 3 rom... What is the purpose or benefit of unlocking the bootloader... Was that really just to avoid Odin so I can flash my couple rom choices easier?
I appreciate your time!
cyberoptics said:
That was very helpful... Looks like Araya is my best bet. I'll leave jasmine rom to try it.
I was hoping that I could get another note 3 rom on this forum and flash the CDMA modem for networking... But doesn't seem like that's an option.
Click to expand...
Click to collapse
I might have very slightly overstated the case for pessimism. There is a "consolidated" Verizon Note 3 Forum which is meant for devs to provide development tools and even ROMs that could potentially be used on devices from more than one carrier. But the world being organized the way it is, that means that you are more likely to find multi-carrier GSM ROMs over there than multi-carrier ROMS which support GSM and oh by the way CDMA and LTE as well.
If you want to fool around over there, I recommend that you proceed with great caution to make sure that the ROMs you choose specifically target Qualcomm MSM8974AB Note 3 handsets, and you should read the developer notes very carefully to see whether you need to flash an "hltevzw" kernel separately. If the dev does not mention "supports hltevzw" or "supports N900V" (for example here) you might be taking chances with your hardware.
I suppose it is possible that the radios are 100% "software defined" in the sense of which bands they can support. Maybe you can get what you want by simply flashing the desired carrier's "modem" firmware, but I have never done that so I can't say for certain whether that works or you are risking a brick (or hardware damage) by doing that. I simply don't know (e.g.) if the chips and antennas in a T-mo version of the Note 3 are identical or different from a Verizon Note 3's hardware
cyberoptics said:
If I'm still stuck to Verizon Note 3 rom... What is the purpose or benefit of unlocking the bootloader... Was that really just to avoid Odin so I can flash my couple rom choices easier?
I appreciate your time!
Click to expand...
Click to collapse
Well, for one - having a custom recovery allows you to make backups - even if you never change ROMs
People don't think of backups as being "sexy", but they allow you something which is really valuable: freedom to mess around and experiment with the knowledge that "if something goes wrong, I'll just restore the backup".
And with Odin, you only had the choice of Stock Roms. Now you have a few more.
cheers
Yes you can install Any rom for note3
Here is my experience with installing roms on note 3 after unlock bootloader
you should Flash twrp-2.8.7.0-hlte-4.4.img by ODIN for the hlte roms or twrp-2.8.7.0-hltevzw-4.4.img if you looking to flash verizon roms ,
im on Phronesis Rom N7 now and i tryed many roms
AryaMod N7 & S7 Edge
MagMa-NX from NXT TEAM
Resurrection Remix Nougat 7.1.1
CM 13 ROM 6.0.1 for Trader418
Purify CM13 6.0.1 ( the best CM13 till now )
and more ...
i have only one problem that i cant get LTE in mobile network always on H+
i tryed to add screenshot but i couldn't its my firist reply :laugh:
@ALPHA85
Pretty informative first post - thanks, and welcome aboard!
Are you on a Verizon SIM? If not, have you been flashing modems from other Note3 devices?
Just curious; I don't have much experience with radio issues or carrier activation issues. Trying to port a carrier-specific ROM elsewhere (esp starting from a VZW ROM) looks like a massive pile of interlocking software dependencies, though. My respect to anyone who can succeed at it.
Feel free to write a brief summary about what's broken in each - any of them have NFC working? I was on CM13 (trader418) for a long time and would have been happy to stay there were it not for all the GPS issues.
Thank you ,:angel:
i dont use Verizon SIM becouse im from egypt, i bought my verizon note 3 by wrong , when i bought it i saw N9005 under the battery and in the boot screen also inside the rom ,it was lollipop 5.0 ,but sinse i did factory rest i surprised it change to N900V even the imei changed , till now i cant understand how they flashed N9005 rom for N900V device with locked bootloader
i'm on OF1 bootloader unlocked and i flashed PL1 Modem i thought maybe it help me to get LTE but still the same H+
about NFC i really didn't try it at all , i always disable it by titanium pro
ALPHA85 said:
when i bought it i saw N9005 under the battery and in the boot screen also inside the rom ,it was lollipop 5.0 ,but sinse i did factory rest i surprised it change to N900V even the imei changed , till now i cant understand how they flashed N9005 rom for N900V device with locked bootloader
Click to expand...
Click to collapse
When you first got it, did it appear to have a Verizon ROM on it? (For instance, the Verizon splash screen?) Or some other carrier's logo?
Actually, that cleared something up for me. Well, except for the part about the IMEI changing
Apparently there were both LTE and GSM models of the "Note 3" that were sold in international markets. I understand the LTE version was originally sold in China, but the GSM model is more common?
The SM-N9005 is an LTE phone (I don't know about CDMA) with the Qualcomm MSM8974 processor
and the N9000 is the GSM model with an Exynos 5420 processor
So that probably explains the binary compatibility of the SM-N900V and the SM-N9005 - same processor, and both phones were designed for LTE service.
But your report should give @cyberoptics a little less pessimistic view of things; thank you for that.
But I wouldn't go so far as to say you can flash ANY Note 3 ROM. Even though both the Exynos and Qualcomm processors use ARM cores, they are fairly different - the Exynos has 8 cores, half of which are Cortex-A15, and the MSM8974 has only four cores which are Krait- something or other. I think they are not quite compatible. Note that in theory, ARM code that was compiled to earlier standards (e.g. thumb, armv5) would certainly work on both devices - but if they compiled ALL the code in ROM libraries that way they would be giving up a lot of performance on either device. So.... to the extent that they target processor specifics for either Cortex-A15 or Krait, they will be incompatible.
cheers.
bftb0 said:
You are in luck. :crying:
There's hardly anything to choose from; maybe 3 or 4 ROMs and about the same number of kernels.
AFAIK, there are no Nougat ROMs and only one Marshmallow ROM (AryaMod6.6).
Click to expand...
Click to collapse
bftb0 I just wanted to thank you once again for your consistently helpful, verbose posts about the N900V. I've been using CM13 thinking it was the best thing going, when, as nice as it was at the time, it doesn't hold water compared to AyraMod, which I switched to yesterday after reading this thread.
Now my GPS won't take me sailing past Easter Island when en route to a noon meeting downtown. Maybe Google Cardboard will even work, now that NFC appears to.
Thanks again, and please don't ever bore of being a great and helpful resource, we need you!
Hello, a few months ago the motherboard died and then I bought a new replacement on aliexpress, the new board has already been updated to the latest QI5 bootloader and now I can not unlock it.
Any suggestions?
The simple answer is no. There may be a way but as far as I am aware of not yet. Generally speaking , aboot is upwared compatible but not downward compatible. Since, there are not official updates for the ageing Note 4 were stuck with the 5DQ15 aboot. The sad part is that all the developers hard work on previous custom roms on marshmallow and kit kat will not be of any use. All there hard work and the donations have been cut away. How sad, Id be really pissed if I had developed a custom rom and Samsung and Sprint cut me off from my possible income. I am not a developer but I enjoy flashing different roms and also had to replace my Note 4 . I lost mine. Then discovered that I could not find one that was not on the 5Dq15 bootloader. Afterwards, I decided to take risks with my new note 4 and mod away. So far so good hotspot mod and many custom mods and ports. I had almost given up on finding a Note 4 on the latest update but I found one on Ebay for $80 Grade A. OMG. Im still waiting on it to arrive. Seems to good to be true so I am keeping it real and will try not to get to optimistic. Time will tell.
Correction
Lollipop and kitkat roms most likely will not work, you will still be able to flash custom roms that are on marshmallow just make sure to keep 5DQ15 bootloader and modern.