Database Users

[Q] Stable CyanogenMod for Verizon Note 3

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.

Lollipop Leak for SM-9005

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.

Fix S5 Dev Edition and or root new S5 on Mac

Hello fellow Android community. Recently I ended up bricking my Verizon S5 Dev Edition using Safestrap. I went out and bought a new consumer S5 it's running Kit Kat 4.4.4 NK2. I already know Towelroot doesnt work to root it. I'm using a Mac with Hemidall 1.4.0 installed and can't access Windows XP in Virtual Box no longer as it won't install properly. Is there any way I can fix my Verizon Dev Edition and or root this new Verizon S5 without having access to an actual PC using ODIN? Last summer I flashed the wrong file on my Dev Edition and it locked the bootloader making it a consumer version. Currently Verizon S5 Dev Editions from Samsung are on backorder. I'm setup to be emailed when they are in stock and it will take 4 weeks for them to get the product according to their site. Thanks for the help. This has been cross posted in another forum pertaining to root but less extensive in detail.
I have already towlroot installed on my current S5 and files to downgrade even though im already on NK2 stock.

Droid9684 said:
Hello fellow Android community. Recently I ended up bricking my Verizon S5 Dev Edition using Safestrap. I went out and bought a new consumer S5 it's running Kit Kat 4.4.4 NK2. I already know Towelroot doesnt work to root it. I'm using a Mac with Hemidall 1.4.0 installed and can't access Windows XP in Virtual Box no longer as it won't install properly. Is there any way I can fix my Verizon Dev Edition and or root this new Verizon S5 without having access to an actual PC using ODIN? Last summer I flashed the wrong file on my Dev Edition and it locked the bootloader making it a consumer version. Currently Verizon S5 Dev Editions from Samsung are on backorder. I'm setup to be emailed when they are in stock and it will take 4 weeks for them to get the product according to their site. Thanks for the help. This has been cross posted in another forum pertaining to root but less extensive in detail.
I have already towlroot installed on my current S5 and files to downgrade even though im already on NK2 stock.
Click to expand...
Click to collapse
Did you make a backup of your aboot partition from the Developer Edition? The second you get a new Developer Edition, don't do anything and PM me. I'll walk you through how to backup your Developer Edition bootloader for safekeeping in case you need to unlock your device again. It's very important to make a backup first thing.

UPDATE
ryanbg said:
Did you make a backup of your aboot partition from the Developer Edition? The second you get a new Developer Edition, don't do anything and PM me. I'll walk you through how to backup your Developer Edition bootloader for safekeeping in case you need to unlock your device again. It's very important to make a backup first thing.
Click to expand...
Click to collapse
Hi Ryan thanks for writing me back on my issues with the S5. Ok well yesterday I got Virtual Box to work as I updated the version and installed Windows XP on my Mac. I had used it previously and successfully had used Odin before. However this time I cant get it to recognize any USB devices even after ejecting them from the Mac part. I called Samsung support of the broken Dev S5 and after lengthy talks they refuse to fix it as it's in the system already as "Beyond Economical Repair" from last summer. Another person I reached out to from Brickedmyphone.com got back to me and said he thinks my devices via USB isnt recognized because of emmc failure. When I went to recover my Dev S5 I thought i had a backup in Safestrap but it turned out I didn't. So I did a factory reset thru that then backed out and had it in download mode in which it stayed on. Pulled the battery power on and it stays on Android boot screen now. I never did backup the bootloader of my Dev S5 because no one ever had told me to do so. Never would have thought about doing such a crucial thing. My biggest worry with another Dev S5 is will they be available again as they are on current backorder? And will they still ship out of box with version 4.4.2? When I had the S5 it wouldn't system update at all so my guess is that's the only version it will have unlike the regular S5 that now has 4.4.4? I guess with the Dev Edition weather I flash anything on it or not is that the warranty after 30 days is void. I figured if I didn't flash a custom recovery on that phone I would have been ok but thats not the case. I've had TWRP on my past two Droids and rarely do I run into problems.
As far as the regular S5 from Verizon i plan to return it for majority of my money back by the 17th. But what do you recommend I do for a phone in the mean time? Unless I can get my bricked S5 up and running again. It has a broken Sd card reader anyhow so eventually would have to be replaced.

Note 4 Dev Edition
I'm considering getting Note 4 Dev Edition even if the S5 Dev is available in weeks to come from now. I read someone posted a custom rooted deoxedized without knox rom for it. Otherwise your not able to root it? I plan to try a Note 4 from the store once i return this here consumer S5 to Verizon next week Friday. @ryanbg

Droid9684 said:
I'm considering getting Note 4 Dev Edition even if the S5 Dev is available in weeks to come from now. I read someone posted a custom rooted deoxedized without knox rom for it. Otherwise your not able to root it? I plan to try a Note 4 from the store once i return this here consumer S5 to Verizon next week Friday. @ryanbg
Click to expand...
Click to collapse
You can most definitely root any Dev edition regardless of ROM. Send me a message when you have the phone in hand and I'll give you a hand. I'll help you back up your bootloader too.

ryanbg said:
You can most definitely root any Dev edition regardless of ROM. Send me a message when you have the phone in hand and I'll give you a hand. I'll help you back up your bootloader too.
Click to expand...
Click to collapse
Thanks for the reply although very late. I ended up going with a rooted Samsung Galaxy S5 off ebay which is new running 4.4.2. By the time I purchased this phone the Note 4 and S5 Dev editions where still on backorder and I needed a phone quickly. I do like the Note 4 and can't wait for the Note 5 this fall to see what it will be like. I also have an inetrest in the LG G4 heard good things about the specs on it.

[Q] Jumping into a S5, root options

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.

Upgrade confusion. Note 3, N900A stock to 7

Trying to update my Note 3 to android 7 but running in circles.
Progress:
Downgrade from 5.0 to 4.5
Rooted device
Uploaded rom to SD card*
Boot recovery mode, select ROM file
Run install
This is where I keep going in circle.
It keeps telling me cannot verify file, verification failed. (does this twice)
Then says update successful, wipe data, format etc.
Reboots back to same old V4.2 again and of course the apps I installed to work on phone gone and have to re-register with Play store to get them back.
How do I solve the error "Unable to verify file"
( also is there a way to stop it wiping data every time if it has failed to update anyway?)
*ROM
lineage-14.1-20180110-nightly-hlte-signed.zip ( this may be wrong rom but the names are often confusing me because the links in upgrade note 3 take me to that rom among others so I assume it is for a note 3)
Any help pin pointing the ACTUAL, CORRECT ROM welcome.
Specs:
Samsung Galaxy Note 3
Qualcom MSM 8974
Snapdragon 800 / 2.27GHZ 4 core cpu.
krait 400
r2p0
Pre-downgrade V 5.0
AP N900AUCSE0C3
CP N900AUCSE0C3
CSC N900AATTE0C3
Below current after downgrade
AP: N900AUCUCNC2
CP: N900AUCUCNC2
CSC: N900AATTCNC2
Bootloader: N900AUCUCNC2

Step one
Post in the forum for your model .This is note AT&T forum .
Phone has locked bootloader .
Links to forum or at the bottom of this forum.
https://forum.xda-developers.com/showthread.php?t=2574886

JJEgan said:
Step one
Post in the forum for your model .This is note AT&T forum .
Phone has locked bootloader .
Links to forum or at the bottom of this forum.
https://forum.xda-developers.com/showthread.php?t=2574886
Click to expand...
Click to collapse
What am I looking for on that post? I have phone rooted.

The AT&T Note 3 sm-n900a has a locked boot loader and can only run custom ROMs created from a stock Samsung lollipop ROM.

Update:
It was my understanding (perhaps wrong) that Safestrap was a way to work around the locked bootloader (ATT) The video on the main topic on this talks about a Verizon phone even though the topic is specific to the ATT note 3. Are they identical with regard to Safestrap etc?
As of now I have Safestrap installed and working. Boots with open lock/Custom on boot screen.
My confusion arises from conflicting videos at YouTube one suggesting Safestrap won't install a custom ROM followed by another that says it will?!?
If it won't exactly what is the purpose of even installing Safestrap if you are still stuck with the exact same android version and all the ATT bloat?
-edit-
FYI currently phone no SIM not provisioned but was used on ATT then switched T_Mobile service (consumer cellular so I can switch between those two. ATT and T-Mobile service suck here but at least with T-Mobile I have WiFi calling on my J2 which avoids poor signal issue at home. Hoping to move back to Note 3 if a good update can make it Wifi Calling enabled )
So far the only reply here has been to tell my my bootloader is locked. Since instructions include using Safestrap as a work around that really does not help me.
At the start the guide was to upgrade the phone to Android 7. Things seem to break down for my understanding of all this if the only work around is Safestrap and if that cannot install a custom ROM how do I get from here to 7/Nougat?
SIDE QUESTION but important.
Having downgraded from 5.0 to root device, I am not getting a request to accept update from ATT ( back to 5.0 I assume ) which I deferred for now. The question regarding this is, if I permit the ATT push back to 5.0 on my rooted device will I lose that root access and have to start all over again? (Darn I don't want that)
Sigh...so confused.

EDIT
I'm reposting an edit to last because I can't figure out how to get the edit/addition to appear. LOL
-edit-
FYI currently phone no SIM not provisioned but was used on ATT then switched T_Mobile service (consumer cellular so I can switch between those two. ATT and T-Mobile service suck here but at least with T-Mobile I have WiFi calling on my J2 which avoids poor signal issue at home. Hoping to move back to Note 3 if a good update can make it Wifi Calling enabled )

ROMS
audit13 said:
The AT&T Note 3 sm-n900a has a locked boot loader and can only run custom ROMs created from a stock Samsung lollipop ROM.
Click to expand...
Click to collapse
So the whole topic of upgrading Note 3 to V.7 is a dead end? I'm stuck with a phone downgraded to KitKat from 5.0 after having rooted etc? Will a custom ROM for lollipop let me delete bloat then upgrade to Nougat?
The whole topic of upgrade to v.7 for note 3 is confusing because after two days of reading and trying options I seem to get no where and cannot even find a definitive answer regarding actually upgrading this phone?

There are no nougat ROMs for the n900a.
Safestrap is only good for certain roms and twrp can't be installed on an n900a with a locked bootloader.

Useless phone?
audit13 said:
There are no nougat ROMs for the n900a.
Safestrap is only good for certain roms and twrp can't be installed on an n900a with a locked bootloader.
Click to expand...
Click to collapse
Okay so I wish the whole topic on installing V7 on Note three just started saying if you have an ATT Note 3
READ NO MORE, all hope is lost!
I read numerous posts on numerous sites telling me I can upgrade this phone and none stated up front ( Does not apply to ATT versions ) leaving me to saving a text file full of instructions, links, a folder of downloaded files etc. all aimed at my N900 phone...none of which is valid.
I guess I will just restore to factory and sell in eBay if it is a useless phone other than to put on ATT or T Mobile as a plain old phone full of bloatware.
That or just load my music library on it and bluetooth it to my stereo as a juke box.
*sigh*

You are on the wrong forum.
Ask your question In the AT&T forum.

update
JJEgan said:
You are on the wrong forum.
Ask your question In the AT&T forum.
Click to expand...
Click to collapse
Actually I believe I posted this topic under the forum for the phone in question, Note 3? I was inquiring about the actual device not about ATT per-se.

how about a link?
JJEgan said:
You are on the wrong forum.
Ask your question In the AT&T forum.
Click to expand...
Click to collapse
How about a link...cannot find such forum.
Search gives me a google result all over the web.
ALL FORMS gives me hundred of specific phone models but did not find a forum for AT&T here?

paulckruger said:
Actually I believe I posted this topic under the forum for the phone in question, Note 3? I was inquiring about the actual device not about ATT per-se.
Click to expand...
Click to collapse
As AT&T has a locked bootloader it has little relevance to Note 3 International model.
---------- Post added at 07:04 PM ---------- Previous post was at 07:02 PM ----------
paulckruger said:
How about a link...cannot find such forum.
https://forum.xda-developers.com/galaxy-note-3
Bottom of the page or the link i posted earlier .
OR Direct link ,
https://forum.xda-developers.com/note-3-att
Click to expand...
Click to collapse

update
JJEgan said:
As AT&T has a locked bootloader it has little relevance to Note 3 International model.
Click to expand...
Click to collapse
So if I obtain an international GSM version I should be able to update ROM?

I don't think the international version supports LTE in North America.