Related
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
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
Hello guys, I'm posting this for first time.
My girlfriend is having a Samsung S5 from AT&T and I want to root it as she told me system apps from AT&T are taking too much space on her phone and so I was thinking can I flash any custom rom on it?
As I see the AT&T thread separate, I want to ask some things
Does Network provider has to do something with it ?
I can flash custom rom on her phone or not?
And same odin thing works ? Like unlocking bootloader and fishing custom recovery
I have never rooted any Samsung phone ever
I'm having a oneplus and HTC.
If anyone can tell me what all do I need to do, I would appreciate it a lot .
Att version has locked bootloader .... Root is possible and there a few roms but they are all based off the stock rom just tweaked a bit ...
cpt.macp said:
Hello guys, I'm posting this for first time.
My girlfriend is having a Samsung S5 from AT&T and I want to root it as she told me system apps from AT&T are taking too much space on her phone and so I was thinking can I flash any custom rom on it?
As I see the AT&T thread separate, I want to ask some things
Does Network provider has to do something with it ?
I can flash custom rom on her phone or not?
And same odin thing works ? Like unlocking bootloader and fishing custom recovery
I have never rooted any Samsung phone ever
I'm having a oneplus and HTC.
If anyone can tell me what all do I need to do, I would appreciate it a lot .
Click to expand...
Click to collapse
You should consider two things:
1. ATT phone may be sim-locked (locked to their network), but it has nothing to do with custom firmware. This problem may be solved more or less easily.
2. ATT phone (SM-G900A) does have a locked bootloader. This is a real problem.
That's why you're limited to touchwiz-based ROMs and stock kernels.
This means, in it's turn, that you cannot have root on 6.0 and above, you cannot have custom recovery, LOS, etc.
If it was my device and I was going to use it as a smartphone (to communicate with others) on a GSM network, I'd install this ROM in unrooted variant and the latest firmware (boot, modem, kernel).
bbsc said:
You should consider two things:
1. ATT phone may be sim-locked (locked to their network), but it has nothing to do with custom firmware. This problem may be solved more or less easily.
2. ATT phone (SM-G900A) does have a locked bootloader. This is a real problem.
That's why you're limited to touchwiz-based ROMs and stock kernels.
This means, in it's turn, that you cannot have root on 6.0 and above, you cannot have custom recovery, LOS, etc.
If it was my device and I was going to use it as a smartphone (to communicate with others) on a GSM network, I'd install this ROM in unrooted variant and the latest firmware (boot, modem, kernel).
Click to expand...
Click to collapse
It's been over 2 years for her phone, unlocking bootloader won't be an issue ( we can unlock it right?) . And she will be using AT&T only because she is using family plan.
If you dare saying the real problem is locked bootloader then we can just unlock it , or I understood it wrong
cpt.macp said:
It's been over 2 years for her phone, unlocking bootloader won't be an issue ( we can unlock it right?) . And she will be using AT&T only because she is using family plan. If you dare saying the real problem is locked bootloader then we can just unlock it , or I understood it wrong
Click to expand...
Click to collapse
I believe that the following thread may help you out with this. It's S5 AT&T device specific.
https://forum.xda-developers.com/showthread.php?t=3516196
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
So I have been following XDA for the past 5 years and this is my very first post. Have some experience with flashing custom roms on different phones and most recently a T-mobile S7-edge (SM-G935T). I flashed a (SM-G935U) firmware on it for the sake of debloating and fully unlocking the device. It worked like a charm, now am tinkering around with a Verizon Note 4 and am unable to find the answers I seek. The problems with this stock firmware is that it is heavily bloated with carrier apps , gets slow at times , unable to use data, hotspot and other such functionalities making me search the internet to flash it with a stock rom which solves all these problems. My question is that what things should i keep in my mind to find a compatible rom and secondly , are these roms for Note-4 (snapdragon variants) interchangeable as done with S7-edge mentioned above. And if it is then what rom will be best to flash for use in Asia. Necessary Information will be provided upon demand. Replies and comments will be appreciated. :fingers-crossed: . P.S I dont wanna flash any unofficial builds.
Yes you can. I have a Verizon Note 4 and I used this method in order to first unlock the bootloader, then flash Magisk for systemless root.
Unlock bootloader and root VZ galaxy note 4: https://forum.xda-developers.com/no...asy-guide-how-to-root-verizon-galaxy-t3454593.
Install Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
changing SM-N910v firmware with SM-N910c
SO i just Went thru the internet and found out that Asian Versions of Note 4 had SM-N910c firmware variant flashed to them, should I flash it? any suggestions?
As an experienced flasher of over 20 Note 4 devices (plus a few more), be careful flashing firmware for other Note 4 devices on a Verizon Note 4 unit. They usually will not work. Several varieties of the device are Snapdragon processors. However the C model is an Exynos processor. This would be like installing IOS software on an Android device. They are not interchangeable. You'd be best to stick with something designed for your N device.
Even then ... using a different ROM (maybe for T or F) can lead to only partial usability of that device. Your data may not work, your cell service may not work, your wifi may not work, etc... Or it won't even boot at all.
Thankfully, Samsung has provided us with ODIN, which is a software program to reflash a device that's been hosed by a malformed ROM. If you want your phone to work, remember the following:
1. Only flash COMPATIBLE software for the processor.
2. Only flash the same variant of ROM to that device (VZW in this case). This is to prevent data carrier problems. An F ROM may boot, but not be fully functional.
3. If you want to try a new unofficial ROM, get one for that device and processor. Be aware that compatibility is not always guaranteed, but Lineage OS 9 ROMS are better than Android 8 as for compatibility. I've tried them all.
4. A stock ROM will have bloatware. If you are rooted, you can remove most of that (if you know how).
5. Last but not least... if you want to stick close to stock, use ModestROM. You'll get 6.01 and some bloatware, but it will be closest to stock as possible with root. Other ROMS might work, but for full functionality, stick with a ROM designed for your device. Otherwise you will experience problems, or worse. You could have a new paperweight!
HI, after reading numerous posts it appears I may be better off getting a different version Samsung Galaxy S5 than the one I have. I have the Verizon Samsung Galaxy S5 SM-G900V, 6.0.1 Marshmallow, with the CID 11 Toshiba eMMC chip. I want to end up with the Lineage OS installed and running Android 10 (or similar). To achieve that I would need to root the phone, unlock bootloader, install TWRP Recovery, flash ROM, etc. To do this on my phone is very complex and may not even be possible. My research has found that this may be done a lot easier on phones by different carriers (T-Mobile, U.S. Cellular, Sprint, AT&T) of the Samsung Galaxy S5, and/or with versions earlier than Marshmallow. My question is which carrier(s) do you think would be easier than the Verizon that I have? What versions/models of the Samsung Galaxy S5 have you successfully rooted, unlocked bootloader, installed TWRP Recovery? Thanks in advance for your advice.
The first 3 you listed have an unlocked bootloader. ATT has a locked bootloader.
dave678 said:
The first 3 you listed have an unlocked bootloader. ATT has a locked bootloader.
Click to expand...
Click to collapse
dave678 said:
I decided to give it a try on my Verizon Samsung Galaxy S5 SM-G900V, 6.0.1 Marshmallow, with the CID 11 Toshiba eMMC chip. Following the instructions for the CID 11 chip found in this Forum (https://forum.xda-developers.com/t/guide-root-bootloader-unlocks-and-more.3561529/#post-71202995) , I was able to root , unlock the bootloader, and install TWRP Recovery. Next I'll attempt to install a Lineage OS and current Android version.
Click to expand...
Click to collapse
?
After reading the above posts, I am more confused than ever. The EMMC apk does nothing when ran on my S5.
I don't know if I have an 11 or a 15 EMMC chip.
I read that an 11 cannot have lineageOS installed as the bootloader is locked. Then read the linked post 71202995 where 11 is allowing LineageOS.
I don't understand the chunks of code/programs that are used when the phone boots. I have looked for an explain of the Andriod boot process unsuccessfully. There is a sequence of events that happen, and TWRP and Odin must get plopped into the sequence in place of other things in order to intercept and take over to do the functions.
Is there any place that explains that? Or that can say "Nope, no good, you can't use Linage on your phone" or "Yup, you're good. Just follow this procedure"
I was all ready to try this and found the post saying the EMMC is key and blocks from any change. Locks you into Android 6.0.1(I think) ...
so already cooked/bricked a Fire 7 where there are comments eleventeen pages in that say "it won't work with 5.6.7.8... brick, read the OP" I read the OP and ten pages in and got nothing warning of a brick. Still got one. This is so confusing.
Where to start?
tom
Use the EMMC BrickBug app to check