Database Users

Samsung Galaxy J3 SM-J320VPP Root help

Hi, and thanks for reading. i would like to know if theres a way of rooting the celphone Samsung Galaxy J3 SM-J320VPP. ive see Threads on sucefully rooting others models but not this one

I agree any dev out there want to let me know what you might possibly need in order to begin to exploit the boot loader. I know that the Samsung n4 fix is for a different chipset but there has to be a way to bypass Verizon's DMV so I can dump the boot loader and system and upload it for the community. I really really like this phone for its price point and I don't feel like that it should be let to the side because it's not a flagship. I'm not a dev but I'm also not new to the capabilities of this community. Any Assistance would be great

My issue is somewhat different, I have a banking app that reports my J3 as rooted (no other apps do) and I need a way to reverse or work around this flaw. The banking app does state for Galaxy S5 model that Android 6 Marshmallow is needed and I know I'm only on 5.1.1, but I'm not sure if the kernel and baseband used are the same.
Any help or advice appreciated. Or if I can root, update to 6 and then unroot to resolve this.

Any news? Just bought this phone on Verizon

No rooting so far. Kingo- and Kingroot APKs and PC versions fail to root, no custom recovery to flash SuperSU, and no vulnerabilities to exploit. I've had this phone for about 5 months now, and nothing sticks. But that's the way it goes with Verizon- branded devices - because the boot loader is locked there isn't much that can be done. The most I've been able to do is "convert" it to a SM-J320V by flashing that firmware via Odin. Still can't use non-Verizon SIMs though.

209pcs said:
No rooting so far. Kingo- and Kingroot APKs and PC versions fail to root, no custom recovery to flash SuperSU, and no vulnerabilities to exploit. I've had this phone for about 5 months now, and nothing sticks. But that's the way it goes with Verizon- branded devices - because the boot loader is locked there isn't much that can be done. The most I've been able to do is "convert" it to a SM-J320V by flashing that firmware via Odin. Still can't use non-Verizon SIMs though.
Click to expand...
Click to collapse
Does converting it allow you to use Verizon MVNO Sims without paying the ransom for a month of verizon prepaid service first to activate the phone ? I know you said no non Verizon sims but nkt sure if you meant MVNO too

G900V CID 11 Running CyanogenMod 14 - Unable to make phone calls/Use sms

Hi, in an attempt to unlock Wifi Tethering capability on my phone, I installed [G900F]CyanogenMod 14.0-20161020-UNOFFICIAL-klte, and now I'm unable to make phone calls or use SMS/MMS.
Is there anything I can try to get service back?
I've tried installing a new modem with no success, using Odin, FlashFire, Terminal Server. I'm not confident I was doing it correctly though, or even if I was using the correct modem files.
I was able to root the phone with Stock firmware, but Mobile Hotspot/Wifi Tether wasn't built-in, and I had no success with any of the apps... FoxFi, Wifi Tether Router, Barnacle Wifi.
Some more information on the phone:
It's the StraightTalk variant made for TotalWireless MVNO. The phone's Stock firmware said it was the S902L Samsung S5 variant, but under the battery FCC ID of the device is actually just a G900V. I took it to the Verizon MVNO PagePlus and they were able to activate the phone, and everything was working perfect, until installing CM14.0.
A roadblock I found out, that might be the root of some of the problems, is the phone may not have the ability to unlock the bootloader, possibly limiting some modding methods. When looking at /sys/block/mmcblk0/device/cid, it starts with 11, designating a Toshiba eMMC chip.
I'll take any suggestions, or alternatives... I don't mind using the stock firmware or any other Roms. The main feature I'd like to have is the ability to use Wifi Tether and the basics, make calls, send sms.
Thank you.

I know this is off topic, but how in the world did you get CM14 running on G900V-CID11?

leotakacs said:
I know this is off topic, but how in the world did you get CM14 running on G900V-CID11?
Click to expand...
Click to collapse
I'm not entirely sure, but someone had an idea they mentioned to me, that it might've been possible to get CM installed from a very outdated Android version, from before CID 11 was locked. The previous stock Android version the phone came installed with was 4.4.2. It was the StraightTalk variant made for TotalWireless MVNO. The phone's Stock firmware said it was the S902L Samsung S5 variant, but under the battery FCC ID of the device is actually just a G900V.

You will not be able to run any version of Cyanogen on your Toshiba S5 properly. Your best course would be to install FlashFire from the play store and use it to install a TouchWiz ROM such as Moar (5.0) or Phoenix (6.0).

TechFellow1 said:
I'm not entirely sure, but someone had an idea they mentioned to me, that it might've been possible to get CM installed from a very outdated Android version, from before CID 11 was locked. The previous stock Android version the phone came installed with was 4.4.2. It was the StraightTalk variant made for TotalWireless MVNO. The phone's Stock firmware said it was the S902L Samsung S5 variant, but under the battery FCC ID of the device is actually just a G900V.
Click to expand...
Click to collapse
no, no, no. don't listen to any of these other people. if your phone boots CM14 then your bootloader is unlocked. this has nothing to do with bootloaders. you installed the wrong ROM for your phone. CM14-kltevzw is the correct variant for your phone, not CM14-klte.
see here:
https://archive.org/download/cmarchive_nighlies/cm-14.1-20161225-NIGHTLY-kltevzw.zip

Hariiiii said:
no, no, no. don't listen to any of these other people. if your phone boots CM14 then your bootloader is unlocked. this has nothing to do with bootloaders. you installed the wrong ROM for your phone. CM14-kltevzw is the correct variant for your phone, not CM14-klte.
see here:
https://archive.org/download/cmarchive_nighlies/cm-14.1-20161225-NIGHTLY-kltevzw.zip
Click to expand...
Click to collapse
He said his phone has a CID11 Toshiba chip. @OP, are you positive you have a Toshiba chip (11)?

leotakacs said:
He said his phone has a CID11 Toshiba chip. @OP, are you positive you have a Toshiba chip (11)?
Click to expand...
Click to collapse
It doesn't matter. He is on a straight talk phone. The bootloader is unlocked by default. The firmware is different.

Hariiiii said:
It doesn't matter. He is on a straight talk phone. The bootloader is unlocked by default. The firmware is different.
Click to expand...
Click to collapse
generally correct. best way to know would be to take a cid 11 based device, and flash twrp same way you would cid 15.
as far as i know though, most straight talk phones i see at work that i've repaired software wise have had unlocked bootloaders... which makes recovering/backing up files a breeze lol

KaptinBoxxi said:
generally correct. best way to know would be to take a cid 11 based device, and flash twrp same way you would cid 15.
as far as i know though, most straight talk phones i see at work that i've repaired software wise have had unlocked bootloaders... which makes recovering/backing up files a breeze lol
Click to expand...
Click to collapse
I think that is correct. Here's the final solution I came up with and everything's working perfectly now.
I flashed the kltevzw 14 version with TWRP and had no luck getting service, then I tried flashing the kitkat factory ROM with ODIN to see if that would fix it, but ODIN failed after many attempts. Finally I flashed with the lower but stable release kltevzw CM13, instead of the nightly, and everything worked again. I'm thinking I must be extremely lucky to have gotten a Straight Talk S5 variant with an unlocked bootloader, but it's interesting that even though my CID definitely starts with 11, the bootloader is unlocked. Not all hope is lost on CID 11 S5's.

TechFellow1 said:
I think that is correct. Here's the final solution I came up with and everything's working perfectly now.
I flashed the kltevzw 14 version with TWRP and had no luck getting service, then I tried flashing the kitkat factory ROM with ODIN to see if that would fix it, but ODIN failed after many attempts. Finally I flashed with the lower but stable release kltevzw CM13, instead of the nightly, and everything worked again. I'm thinking I must be extremely lucky to have gotten a Straight Talk S5 variant with an unlocked bootloader, but it's interesting that even though my CID definitely starts with 11, the bootloader is unlocked. Not all hope is lost on CID 11 S5's.
Click to expand...
Click to collapse
Are you able to dump your boot and bootloader partitions somehow? The "dd" command from adb shell somehow?
Couldnt we just use a diff program to compare yours with one of the Locked 11's?

TechFellow1 said:
I think that is correct. Here's the final solution I came up with and everything's working perfectly now.
I flashed the kltevzw 14 version with TWRP and had no luck getting service, then I tried flashing the kitkat factory ROM with ODIN to see if that would fix it, but ODIN failed after many attempts. Finally I flashed with the lower but stable release kltevzw CM13, instead of the nightly, and everything worked again. I'm thinking I must be extremely lucky to have gotten a Straight Talk S5 variant with an unlocked bootloader, but it's interesting that even though my CID definitely starts with 11, the bootloader is unlocked. Not all hope is lost on CID 11 S5's.
Click to expand...
Click to collapse
Delgoth said:
Are you able to dump your boot and bootloader partitions somehow? The "dd" command from adb shell somehow?
Couldnt we just use a diff program to compare yours with one of the Locked 11's?
Click to expand...
Click to collapse
No, all hope IS lost on CID 11's. You have a different phone provided by a different company. It is loaded with a different software and hardware configuration. There is no bootloader signature verification. Yes, the configuration is very similar to that of a G900V, but the bootloader comes unlocked. This is phone specific. This has no value for an actual G900V.

Hariiiii said:
No, all hope IS lost on CID 11's. You have a different phone provided by a different company. It is loaded with a different software and hardware configuration. There is no bootloader signature verification. Yes, the configuration is very similar to that of a G900V, but the bootloader comes unlocked. This is phone specific. This has no value for an actual G900V.
Click to expand...
Click to collapse
well if that's correct, then why does the dev edition bootloader work on the non-dev edition? Sure, its still a g900v, but never hurts to find a way and try
a little optimism can go a long way in life. don't think so negatively

KaptinBoxxi said:
well if that's correct, then why does the dev edition bootloader work on the non-dev edition? Sure, its still a g900v, but never hurts to find a way and try
a little optimism can go a long way in life. don't think so negatively
Click to expand...
Click to collapse
I say this because I have tried it and I know how it works. A bootloader needs to have the right signature that is recognized by the hardware. The reason the dev edition bootloader works on non dev edition is because they are the same phone, but with different bootloaders installed. The signature of the straight talk bootloader will not be recognized by the G900V hardware. Again, I have confirmed this personally. The straight talk is almost the same hardware as the verizon G900V, but it does not have bootloader signature verification enabled (and the bootloader that comes installed is unsecured).

Hariiiii said:
I say this because I have tried it and I know how it works. A bootloader needs to have the right signature that is recognized by the hardware. The reason the dev edition bootloader works on non dev edition is because they are the same phone, but with different bootloaders installed. The signature of the straight talk bootloader will not be recognized by the G900V hardware. Again, I have confirmed this personally. The straight talk is almost the same hardware as the verizon G900V, but it does not have bootloader signature verification enabled (and the bootloader that comes installed is unsecured).
Click to expand...
Click to collapse
alright, that makes sense. Thanks for explaining. Always interested in these things since i don't QUITE understand exploits at that level. I do mainly apk modifications and software dev

KaptinBoxxi said:
well if that's correct, then why does the dev edition bootloader work on the non-dev edition? Sure, its still a g900v, but never hurts to find a way and try
a little optimism can go a long way in life. don't think so negatively
Click to expand...
Click to collapse
because you don't have a clue about how the CID exploit works
the reason you can flash the dev aboot on a CID15 is because you can change the CID to match that of a dev edtion aboot checks the CID to see if a device as a dev edtion or not
the CID is a sort of serial number for the flash-chip and normally its write once and then read only value ,but because samsung was sloppy we can use some custom Samsung NAND vendor commands to change it so secure-boot thinks you have a dev editon and permits the flashing of a unsigned image
this is flat not possible on CID11 devices(toshiba NAND) there is no hope for cid11 devices with this method the commands needed simply do not exist PERIOD

Legitsu said:
because you don't have a clue about how the CID exploit works
the reason you can flash the dev aboot on a CID15 is because you can change the CID to match that of a dev edtion aboot checks the CID to see if a device as a dev edtion or not
the CID is a sort of serial number for the flash-chip and normally its write once and then read only value ,but because samsung was sloppy we can use some custom Samsung NAND vendor commands to change it so secure-boot thinks you have a dev editon and permits the flashing of a unsigned image
this is flat not possible on CID11 devices(toshiba NAND) there is no hope for cid11 devices with this method the commands needed simply do not exist PERIOD
Click to expand...
Click to collapse
I understand plenty enough to know the difference in the flash chips cid's with such like that... The fact of the matter i was trying to get at is that most Straight Talk phones are unlocked entirely without a care in the world, regardless of their CID/branding. Without the proper commands and 3rd party support, I get that there won't be a way. That's why I check my CID's first before buying S5's or Note 4's

Galaxy S4 variant confusion

Hello! I have a project that I am working on that involves a handful of Galaxy S4 devices. They were all purchased on ebay, so they are all different models with different versions of android. The goal is to get them running as close to the same software as possible.
The models that i have - as shown in the about phone settings - are
GT-I9505
GT-I9500
SGH-I337
SGH-M9194N
SGH-M919N
SGH-M919
From my understanding, all of these other than I9500 are qualcomm based and should therefore be able to run the unified jfltexx build from lineageOS. IF this is the case - and i am not ENTIRELY sure i understood all of that correctly - I am still out a build for the I9500. Are there any CM or lineageOS builds that will run on this hardware?

The i337 cannot run lineage if the bootloader is locked. I believe att locked the bootloader with the ota update for android 4.3.

The question about the I9500 and LineageOS has been seemingly asked at least once a week for the last several weeks. Unless you can provide an I9500 to a developer to develop upon, you will not see a properly functioning LineageOS build on the device.

Strephon Alkhalikoi said:
The question about the I9500 and LineageOS has been seemingly asked at least once a week for the last several weeks. Unless you can provide an I9500 to a developer to develop upon, you will not see a properly functioning LineageOS build on the device.
Click to expand...
Click to collapse
I do not have access to the devices, I just have a client who asked me some questions about the devices, and I admit that these Samsung devices confuse the hell out of me. This wasnt a "Damnit, gimme lineage now!" post, but more just me trying to get a handle on all the different models and their differences.

audit13 said:
The i337 cannot run lineage if the bootloader is locked. I believe att locked the bootloader with the ota update for android 4.3.
Click to expand...
Click to collapse
Samsung still has not provided an OEM bootloader unlock? I havent dealt with a non unlocked phone for years, so im actually asking. Is there no bootloader hacks, even a third party exploit that allows the bootloader to be reflashed?
As for the other models, if they all run a unified lineage build, how does that work with all the various carriers supported? do you have to reflash the correct radio after, or does lineage just not touch that when flashing?

I believe AT&T requested the bootloader lock as they have with the note 3, G2, etc. and there is no hack or way to unlock the AT&T s4 bootloader.

audit13 said:
I believe AT&T requested the bootloader lock as they have with the note 3, G2, etc. and there is no hack or way to unlock the AT&T s4 bootloader.
Click to expand...
Click to collapse
Great, thank you.

S7 edge (SM-G935P) rootable?

Update: There's still no clear answer on this. What's the difference in what Chainfire says is impossible, vs, what people are doing in colormedroid's SM-G935P Root thread?
I've been reading all day and I've still no confirmation on this: Is the S7 Edge (SM-G935P) still unrootable as of Sept. 2017?
Thank you

Following up for the long-weekend.

Searching and searching and finding:
This post from May of 2017 says the device is not rootable without disabling encryption:
https://forum.xda-developers.com/showpost.php?p=72204306&postcount=978
This post from July of 2016 has very clear steps for rooting the SM-935P (snapdragon, even):
https://forum.xda-developers.com/sprint-s7-edge/how-to/root-t3410424
What is the difference? Is it just that this process involves the disabling of encryption as Chainfire mentioned in his later post? Is root possible on the snapdragon variant of the s7 edge? I see dozens of posts from people who claim to have successfully rooted, and then entire articles at a later date by renowned developers who say "nope".
This might be a pain for people to continually answer these basic questions, but I've been reading for hours and have no better confirmation one way or the other.
Thanks for your time.

Bonus question-
Many posts report no custom recovery because of the locked bootloader on the s7 edge devices, however the LineageOS installation instructs the user to use Heimdall to install TWRP-
https://wiki.lineageos.org/devices/hero2lte/install
How the what now?

artician said:
Bonus question-
Many posts report no custom recovery because of the locked bootloader on the s7 edge devices, however the LineageOS installation instructs the user to use Heimdall to install TWRP-
https://wiki.lineageos.org/devices/hero2lte/install
How the what now?
Click to expand...
Click to collapse
I have same phone as you. So you can install TWRP then?

girn26 said:
I have same phone as you. So you can install TWRP then?
Click to expand...
Click to collapse
I have not yet tried. I picked up an S7 friday, having seen posts about successful root/twrp/lineageOS. I followed the Lineage steps as far as setting up Heimdall, installing libusb drivers, and connecting the device, but found the conflicting information about the process before I attempted to flash TWRP.
I stopped everything after that point, because if I can't get root/twrp/etc, it's going back to the store.
It's the second (and last) Samsung I'll be returning. I already returned a J7 because it wasn't supported either. I don't have time to follow the scene as closely as I did before, and wasn't aware how bad the situation was for device ownership these days.

It is bad but I'm fine with how it is to be honest

All I want to do is be able to install zero camera mod. Pissing me off that I can't

I believe the difference that I've been failing to get an answer for regarding the rooting of some snapdragon-model S7 Edges, is that the device compatible with TWRP and Lineage OS are the chinese-only variants, known as hero2ltechn (which I'm probably misspelling, but I can't even find it via a google search now to check).
I'm still not even sure if that's accurate. This is after hours of reading and having to draw my own conclusions. Tons of wasted time, and wasted money (returned the S7 to the store this morning, albeit for a restock fee and nonrefundable connection charge). Very frustrating and sad!

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.