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.
Is it even remotely possible to unlock the bootloader? I would love to install a custom recovery and a custom ROM.
Thanks.
Not possible currently, probably never will.
Until someone at Samsung decides to give the keys to the bootloader, it will remain locked.
(Pssst, hey Samsung Developer, there is a fame and fortune for your leak. :angel: )
I vouch 400$ for unlocked bootloader and emotion/lineage os
If S6 is anything to judge by, the chances for an unlocked bootloader are slim at best.
The only reason I would love an unlocked bootloader is to be able to root the stock OS and not have to use an engineering kernel. Otherwise, I tend to run rooted stock on my devices until they get too out of date.
Unfortunately, that means when this S7 Edge becomes obsolete, that will be the end of the line.
No one is even attempting it. With most phones now root / unlocked bootloader is a thing of the past. If you want those feature it'd be best to get a Pixel or a 1+. The rest of the phone will kill all of that in the next year.
The last good for rooting phone from Samsung was the Note 4 and even that was only the Tmobile variant. As Samsung and Android pay roll out internationally it will get killed off over seas too.
Unless a new crop of Android hackers pop-up to replace all the devs who used to roit/unlock the phones rooting and flashing is dying
ShrekOpher said:
No one is even attempting it. With most phones now root / unlocked bootloader is a thing of the past. If you want those feature it'd be best to get a Pixel or a 1+. The rest of the phone will kill all of that in the next year.
The last good for rooting phone from Samsung was the Note 4 and even that was only the Tmobile variant. As Samsung and Android pay roll out internationally it will get killed off over seas too.
Unless a new crop of Android hackers pop-up to replace all the devs who used to roit/unlock the phones rooting and flashing is dying
Click to expand...
Click to collapse
I'm not sure I would go that far. Sure, Samsung has locked their phones down like nuts, but there are still plenty of developments on other devices. The Sunshine team has managed to S-off every HTC flagship from the M8 on, along with a reasonably sold list of Moto devices. If you aren't on Verizon/AT&T you can skip the hack by going to HTCDev. Too bad HTC has gone absolutely bonkers on their own devices...
The LG V20 folks got "lucky" with Dirty Santa (though I wouldn't touch that mess with a 10 foot pole since your warranty is going to be void at the same time LG is getting sued over boot looping phones). Still, if you manage to get lucky, you can load custom ROMs on that device, and it's a true flagship.
Other devices seem to either have unlockable (through a web-site) bootloaders or have proven relatively easy to mod/root.
One day root may be a thing of the past unless you can find a dev phone, but I don't think we are quite there yet. That, and there will always likely be leaked dev kernels.
Few things:
-Is there any work still being done to get the bootloader unlocked? This dev thread no longer seems to be only devs, rather a bunch of "+1s", "thanks", and "tweet posts". All great posts, but not dev related.
- All devs on this thread are without a doubt better than I regarding android roms, unlocking, etc, but thought id throw a few ideas it here. (Im new to this type of dev). Maybe i can provide new hope? I just recently got the s7 and found out the hard way the current status woth no way to get custom roms. I know the chain of trust, verity, etc are a major buzzkill, but parts have all been hacked before so we can't Judy throw in the towel, can we?!
- http://newandroidbook.com this has a lot of good material, this guy is a genius, too bag he isn't working on this! (Download the book there & supplements).
Couple of actual ideas:
-He mentions in the book, with root you should be able to modify parts of partitions. Add long as you don't modify the entire partition it wont check for integrity on startup. Now that root exists, is Amy of this possible, to modify three partitions and unlock the bootloader?
- He also talks about how the chain of trust works using signed keys, and where to find these keys in the actual image file; since we know exactly where the keys are, and what's expected, can't we fake it with a custom image using a binary editor? He (in that link) also refers to his free tools to inspect, etc.
Remember when wet push via odin the phone isn't online so had no way to verify via internet if something is in fact legit. Hacks happen all the time with fake digital signatures and keys, certs, etc.
- In other words, now that root exists in the engineering kernel, Im thinking new doors have opened.
Thoughts? Hope?!
It's not happening.
diligent7771 said:
Few things:
-Is there any work still being done to get the bootloader unlocked? This dev thread no longer seems to be only devs, rather a bunch of "+1s", "thanks", and "tweet posts". All great posts, but not dev related.
- All devs on this thread are without a doubt better than I regarding android roms, unlocking, etc, but thought id throw a few ideas it here. (Im new to this type of dev). Maybe i can provide new hope? I just recently got the s7 and found out the hard way the current status woth no way to get custom roms. I know the chain of trust, verity, etc are a major buzzkill, but parts have all been hacked before so we can't Judy throw in the towel, can we?!
- http://newandroidbook.com this has a lot of good material, this guy is a genius, too bag he isn't working on this! (Download the book there & supplements).
Couple of actual ideas:
-He mentions in the book, with root you should be able to modify parts of partitions. Add long as you don't modify the entire partition it wont check for integrity on startup. Now that root exists, is Amy of this possible, to modify three partitions and unlock the bootloader?
- He also talks about how the chain of trust works using signed keys, and where to find these keys in the actual image file; since we know exactly where the keys are, and what's expected, can't we fake it with a custom image using a binary editor? He (in that link) also refers to his free tools to inspect, etc.
Remember when wet push via odin the phone isn't online so had no way to verify via internet if something is in fact legit. Hacks happen all the time with fake digital signatures and keys, certs, etc.
- In other words, now that root exists in the engineering kernel, Im thinking new doors have opened.
Thoughts? Hope?!
Click to expand...
Click to collapse
I have to agree with Kcodya. With the S8 coming out very soon, I am sure the Devs are not really that concerned with the S7 and unlocking the bootloader. I have read a lot of posts about the very issue and anyone and everyone that has been working on this has dropped it or no longer working on it. Look at the S6. It is still without an unlocked bootloader.
I agree with you about the EngImg and I guess at the present time, that is about all we have to work with. I have settled with it and am happy at least to have root privileges.
But we can still hope...
If Samsung ever gets off their hindquarters and updates the unlocked version of the S7/S7 Edge to Nougat, rooted stock will probably be optimal anyway. I know this is XDA, and people love to mod with whole ROMs, but OEM ROMs have improved dramatically over the years. This isn't the era of requiring CM (or LineageOS now) just to have a functional device like it was during the Gingerbread era.
Unfortunately, Samsung isn't likely to ever sell developer friendly phones again, so if you are a developer or like beta testing ROMs, this isn't your device. There are too many options that are trivial to unlock and develop on for anyone to spend too much effort bucking Samsung on their lockdown strategy.
diligent7771 said:
Few things:
-Is there any work still being done to get the bootloader unlocked? This dev thread no longer seems to be only devs, rather a bunch of "+1s", "thanks", and "tweet posts". All great posts, but not dev related.
- All devs on this thread are without a doubt better than I regarding android roms, unlocking, etc, but thought id throw a few ideas it here. (Im new to this type of dev). Maybe i can provide new hope? I just recently got the s7 and found out the hard way the current status woth no way to get custom roms. I know the chain of trust, verity, etc are a major buzzkill, but parts have all been hacked before so we can't Judy throw in the towel, can we?!
- http://newandroidbook.com this has a lot of good material, this guy is a genius, too bag he isn't working on this! (Download the book there & supplements).
Couple of actual ideas:
-He mentions in the book, with root you should be able to modify parts of partitions. Add long as you don't modify the entire partition it wont check for integrity on startup. Now that root exists, is Amy of this possible, to modify three partitions and unlock the bootloader?
- He also talks about how the chain of trust works using signed keys, and where to find these keys in the actual image file; since we know exactly where the keys are, and what's expected, can't we fake it with a custom image using a binary editor? He (in that link) also refers to his free tools to inspect, etc.
Remember when wet push via odin the phone isn't online so had no way to verify via internet if something is in fact legit. Hacks happen all the time with fake digital signatures and keys, certs, etc.
- In other words, now that root exists in the engineering kernel, Im thinking new doors have opened.
Thoughts? Hope?!
Click to expand...
Click to collapse
WTF? Did you literally copy and paste my post from another thread?! https://forum.xda-developers.com/showpost.php?p=71604183 lol I know your intentions are great, but you should probably indicate this is a quote from the original author (me), otherwise it appears you were the one that wrote this post. Carry on...
locked bootloader
jshamlet said:
The only reason I would love an unlocked bootloader is to be able to root the stock OS and not have to use an engineering kernel. Otherwise, I tend to run rooted stock on my devices until they get too out of date.
Unfortunately, that means when this S7 Edge becomes obsolete, that will be the end of the line.
Click to expand...
Click to collapse
Hey man,i saw you online and i need help with something.
Is locked bootloader affects radio gsm,on unlocked phone by at&t if i upgraded fw and changed version of bootloader from v2 to v4?
Thank you in advance!
Man, this stinks
TomatoesOnBluRay said:
Is it even remotely possible to unlock the bootloader? I would love to install a custom recovery and a custom ROM.
Thanks.
Click to expand...
Click to collapse
It's strange that this device never got a stable root. The type of root I was looking for 7 months ago is never going to exist. Development on the root of this phone was forgotten when the S8 came out. I wish I could say the opposite, but unfortunately we couldn't develop a proper root fast enough for the inevitable growth of interest in the newest device.
TomatoesOnBluRay said:
It's strange that this device never got a stable root. The type of root I was looking for 7 months ago is never going to exist. Development on the root of this phone was forgotten when the S8 came out. I wish I could say the opposite, but unfortunately we couldn't develop a proper root fast enough for the inevitable growth of interest in the newest device.
Click to expand...
Click to collapse
It's not just that, Samsung also offers some fairly nice bonuses for not rooting and root just isn't what it used to be. The days of "this phone is completely unusable without root to fix all the broken crap" are gone.
I found that simply switching to the unlocked firmware solved 90% of the things I wanted root for in the first place, and probably another 8% were solved by judicious use of ADB and NetGuard. What little was left just wasn't enticing enough to put up with the irritations and work-arounds required for the eng-boot root. I already run Nova launcher exclusively, but even at that, the stock launcher isn't total crap anymore. On the plus side, the eng-boot root doesn't trip Knox, so you can always go back if you want.
Yeah, it's going to suck when updates for the S7 stop due to age, and it would be nice if Samsung would offer a bootloader unlock when that happens, but I suspect it will live the rest of its life with nothing more than the engineering root method.
jshamlet said:
It's not just that, Samsung also offers some fairly nice bonuses for not rooting and root just isn't what it used to be. The days of "this phone is completely unusable without root to fix all the broken crap" are gone.
I found that simply switching to the unlocked firmware solved 90% of the things I wanted root for in the first place, and probably another 8% were solved by judicious use of ADB and NetGuard. What little was left just wasn't enticing enough to put up with the irritations and work-arounds required for the eng-boot root. I already run Nova launcher exclusively, but even at that, the stock launcher isn't total crap anymore. On the plus side, the eng-boot root doesn't trip Knox, so you can always go back if you want.
Yeah, it's going to suck when updates for the S7 stop due to age, and it would be nice if Samsung would offer a bootloader unlock when that happens, but I suspect it will live the rest of its life with nothing more than the engineering root method.
Click to expand...
Click to collapse
I entirely agree with you. I haven't rooted my S7 since I tried the engineer boot, and it has been completely and totally usable. I also agree with you about installing the unlocked firmware as it removes most of the bloat that comes with the stock firmware. Root is nice, but not entirely necessary on this device.
TomatoesOnBluRay said:
I entirely agree with you. I haven't rooted my S7 since I tried the engineer boot, and it has been completely and totally usable. I also agree with you about installing the unlocked firmware as it removes most of the bloat that comes with the stock firmware. Root is nice, but not entirely necessary on this device.
Click to expand...
Click to collapse
So, where might one obtain an unlocked firmware for a G930A? I've searched high and low and have found several different f/w but they all seem to be for other versions of the G930, not the A. Tried to flash mine with one of those and got caught in an endless boot cycle, so had to go back to stock - still locked - and AT&T says the IMEI doesn't belong to them even though it plays their little tune and shows their logo and flashes their name on startup. Pretty useless to me without being able to unlock it. Thoughts or ideas?
Many thanks in advance.
Havdaddy said:
So, where might one obtain an unlocked firmware for a G930A? I've searched high and low and have found several different f/w but they all seem to be for other versions of the G930, not the A. Tried to flash mine with one of those and got caught in an endless boot cycle, so had to go back to stock - still locked - and AT&T says the IMEI doesn't belong to them even though it plays their little tune and shows their logo and flashes their name on startup. Pretty useless to me without being able to unlock it. Thoughts or ideas?
Many thanks in advance.
Click to expand...
Click to collapse
All US/Snapdragon S7s and S7 Edges are hardware identical. You can run any of the 5 variants on them with zero issue (even going between V/S and A/T). This means you can run the unbranded/unlocked firmware on any US/Snapdragon based device as long as the model number matches.
Now, SIM locks are a separate issue. You still have to go to the carrier that locked it (or one of the paid services) to get the unlock code even if you are running the U firmware because the modem firmware is entirely separate.
Havdaddy said:
So, where might one obtain an unlocked firmware for a G930A? I've searched high and low and have found several different f/w but they all seem to be for other versions of the G930, not the A. Tried to flash mine with one of those and got caught in an endless boot cycle, so had to go back to stock - still locked - and AT&T says the IMEI doesn't belong to them even though it plays their little tune and shows their logo and flashes their name on startup. Pretty useless to me without being able to unlock it. Thoughts or ideas?
Many thanks in advance.
Click to expand...
Click to collapse
The firmware for all G930 and G935 variants are interchangeable. When I refer to the unlocked firmware, I'm referring to G930U and G935U. This version can be found on the AT&T Samsung Galaxy S7 and S7 Edge forums on this site. When you install the unlocked firmware, you are not unlocking the device, just the firmware associated with the unlocked version of the phone. This means less bloatware, faster speeds, and no AT&T boot logo. Sorry for the confusion my previous comment may have caused!
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!