Database Info

[US996] 100% Stock deODEXd ROM

Do you have a US996, and want to be able to start modding/theming the ROM? FINE! HERE! Lol...
Please know, this is 100% stock, including kernel. Also, I do not own a US996 (but I do own the H918). This ROM has already been tested (thanks @monsieurtalbot !)
No changes on the ROM. SuperSU gets flashed alongside the ROM. Oh, and setenforce=0 is set via init.qcom.post-boot
Before proceeding. It is absolutely necessary for you to be on a stable TWRP build (currently, RC8, 3.0.2-0, and 3.0.2-1). Also, you must have already have had decrypted your ENTIRE phone. If your phone bootloops into TWRP, you probably didn't decrypt, and/or didn't flash no-verity properly, or it could also be that you are on an old TWRP build. . You have been warned.
This is for the Factory Unlocked US Cellular. Untested on the other US996.
Here we have the base NRD90M ROM from LG. The only difference from this, and what came on your phone is, that it is not ODEXd anywhere. DeODEXing basically bundles all parts of an APK together which saves space, allows for modification of the APK (like for System UI and stuff), and ever so slightly increases performance (by the littlest amount possible). This is ONLY for the US996.
Also, no need to wipe, as /system is fully removed (your apps and settings will stay since that is in /data). Since we only have 1 base from LG, ROMs don't need to be wiped, even if coming from ODEX.
Major thanks to @Chainfire for creating SuperSU
Major thanks to @jcadduono for the root exploit, AND for the TWRP image(s), AND for inspiring me to learn to do it. Also, he supplied the stock System.img, boot.img, and sources for a custom kernel!/RealMVP

SUPER happy to say I am using this currently and it is flawless. Fantastic base for our custom unlocked US996 community.
No more systemless root. This is a full root and I was finally able to delete the stupid boot sounds.
Thx for letting me be the test dummy.
Just so everyone knows I dirty flashed in TWRP from stock and I have had 0 issues. I am a heavy power user.
Everything is working as it should be.
Since it's not specified in the OP - let me make sure that everyone understands that this is for the USA Factory Unlocked US996 ONLY.
Super excited for some custom roms. =)
---------- Post added at 10:53 PM ---------- Previous post was at 10:39 PM ----------
Moving this conversation over from the H918 thread...
I would love to see the FM working on our US996 . . .
BUT - I've had no luck flashing the available zips so far that are for the H918.
FM Service crashes - I figure the chip is there - just needs to likely be enabled on the kernel end.
SO - if you are truly looking into making us a kernel, let's put that on a likely very long todo list. lmao <3

monsieurtalbot said:
Since it's not specified in the OP - let me make sure that everyone understands that this is for the USA Factory Unlocked US996 ONLY.
Click to expand...
Click to collapse
I mean, they would have to be to have TWRP
And it does say US996 in title, as well as in OP

Tilde88 said:
I mean, they would have to be to have TWRP
And it does say US996 in title, as well as in OP
Click to expand...
Click to collapse
There's another US996 for US Cellular - as we all know - so as things get released possibly for that model (which holds the same model number for whatever reason) and this thread ages - it might not be a terrible idea to exclusively specify so some poor soul down the road doesn't flash this to the wrong device... :highfive:

monsieurtalbot said:
I would love to see the FM working on our US996 . . .
BUT - I've had no luck flashing the available zips so far that are for the H918.
FM Service crashes - I figure the chip is there - just needs to likely be enabled on the kernel end.
SO - if you are truly looking into making us a kernel, let's put that on a likely very long todo list. lmao <3
Click to expand...
Click to collapse
Shouldn't be too hard to enable in the kernel. And if it isn't in the source, it could added i guess

Tilde88 said:
Shouldn't be too hard to enable in the kernel. And if it isn't in the source, it could added i guess
Click to expand...
Click to collapse
Any chance you could post the md5 sum for the ROM to check that we got a good download? I want to ensure a good file before flashing a new system.

AlkaliV2 said:
Any chance you could post the md5 sum for the ROM to check that we got a good download? I want to ensure a good file before flashing a new system.
Click to expand...
Click to collapse
It would have to be later tonight, getting ready for work now. You can just double click the zip on your pc. If it opens without an error, you are good to go.

Would you happen to have a stock ODEXed rom for US996 to post as you did for the H918?
Also, are you planning to build anything off the US996 stock deODEXed rom or is it for safety net purposes?

I was thinking about diving into the v20 world to do some dev work, though am I reading this right? Each ROM has to be based off of the system.img for each model number? That makes it hard to decide which device model to buy
--->

Mentalmuso said:
I was thinking about diving into the v20 world to do some dev work, though am I reading this right? Each ROM has to be based off of the system.img for each model number? That makes it hard to decide which device model to buy
--->
Click to expand...
Click to collapse
I honestly am not sure, but I did this just to be safe. As it turns out, FM is not included in the US996 ROM or kernel. I don't know of any other discrepancies, but that was enough for me.
IMO the H918 is the way to go, and just Unlock it from Tmobile. But that's just my opinion.

papashex said:
Would you happen to have a stock ODEXed rom for US996 to post as you did for the H918?
Also, are you planning to build anything off the US996 stock deODEXed rom or is it for safety net purposes?
Click to expand...
Click to collapse
I suppose I could upload a stock ODEXd, but, I don't see the point. :cyclops:

You're right, no point. It's early in the game, hopefully there will be a .tot or .kdz (lg equivalent of ruu) for the eventual 7.1 update.
Thanks for your efforts to date.

Can this ROM be flashed on a sprint 997 that was unlocked and rooted using the dirty Santa method?
The reason I'm asking is because that process seems to change my phone to an unlocked 996 and I want to start fresh with a stock ROM.

Well this is weird. I went to install this and TWRP is telling me I have the wrong device. It is telling me i have a 918 when I know for a fact its a 996....

bryancotton84 said:
Well this is weird. I went to install this and TWRP is telling me I have the wrong device. It is telling me i have a 918 when I know for a fact its a 996....
Click to expand...
Click to collapse
It detects your model from build.prop I believe.
Can you change your model in your build.prop and retry?

Would anyone be willing on trying out a custom kernel? FM might be working. Plus other things and stuff .
I don't have a US996, so I can't test it. So be sure to have a stock boot.img and your stock /system/lib/modules folder. If this fails, you can simply flash your stock boot.img right within twrp, and then push the modules folder into /system/lib/modules. Or you can reflash the ROM.

i was able to dirty flash this straight onto my stock VS995 with the konverge kernel flashed as well and the only problem i have is the static boot but that's easily fixed

Get Ur Noob On said:
i was able to dirty flash this straight onto my stock VS995 with the konverge kernel flashed as well and the only problem i have is the static boot but that's easily fixed
Click to expand...
Click to collapse
What is static boot?
Anyone willing to test the custom kernel, be sure to read what I wrote in the post above. You can find it here

Tilde88 said:
What is static boot?
Anyone willing to test the custom kernel, be sure to read what I wrote in the post above. You can find it here
Click to expand...
Click to collapse
basically until the phone actually boots into the os it looks like a messed up tv showing only static colors and you cant see anything, what you do is you wait until it boots into the os and shut the screen off then hold your finger over the front camera and it fixes it and everything is normal.

Tilde88 said:
I suppose I could upload a stock ODEXd, but, I don't see the point. :cyclops:
Click to expand...
Click to collapse
Any chance you could do it, If it's not too much trouble? I'd like to install it on my F800L, if I can, and I seem to be having issues with the current deodex'd version.
If I'm honest, I have no idea if it will make any difference whatsoever, and the issue could be something completely unrelated (ihavenoideawhatimdoing), but I'd just like to try it, anyway. I got an odex'd H918 working, so It has me wondering if it makes any difference?

Stock Bootloader

Does anyone know where I can get just the stock bootloader image to flash via TWRP?
Long story short I F'd up my bootloader and now Odin will not flash a stock BL file do to a version mismatch and to make matters worse I can't find a way to restore to stock baseband so my network isn't working. If someone can share a backup that'd be super
EDIT: Forgot to specify I need it from a TMobile variant (J700T) for firmware APK6 or APK3 (Odin doesn't seem to want to flash the stock BL from my Odin ROMs perhaps because there is a version mismatch in the phone?)

NullaVisus said:
Does anyone know where I can get just the stock bootloader image to flash via TWRP?
Long story short I F'd up my bootloader and now Odin will not flash a stock BL file do to a version mismatch and to make matters worse I can't find a way to restore to stock baseband so my network isn't working. If someone can share a backup that'd be super
EDIT: Forgot to specify I need it from a TMobile variant (J700T) for firmware APK6 or APK3 (Odin doesn't seem to want to flash the stock BL from my Odin ROMs perhaps because there is a version mismatch in the phone?)
Click to expand...
Click to collapse
download latest stock rom at sammy..

Already tried. Looks like I am officially a victim of a partial brick (Odin wont flash BL because it thinks I'm downgrading and I have no Baseband/network) I'll try and see what I can do through TWRP since I can still flash that through Download mode. I made no backups myself but would restoring another TWRP backup solve it perhaps?

NullaVisus said:
Already tried. Looks like I am officially a victim of a partial brick (Odin wont flash BL because it thinks I'm downgrading and I have no Baseband/network) I'll try and see what I can do through TWRP since I can still flash that through Download mode. I made no backups myself but would restoring another TWRP backup solve it perhaps?
Click to expand...
Click to collapse
try flash custom rom after that flash stock rom..

khaisttj92 said:
try flash custom rom after that flash stock rom..
Click to expand...
Click to collapse
No dice my dude. However, I did find something else
Turns out when I check the bootloader version it reads J700T1UVU3AQC3. Sure enough there was a baseband update and security update a few days ago and my device must've installed it while I was asleep. This would explain why my baseband is broken AND why Odin doesn't want me to flash the APK6 Bootloader.
So there's good news and bad news. The good news is there is hope but the bad news is I am currently at the mercy of whenever someone decides to upload this firmware on the internet (if anyone does that is)

NullaVisus said:
No dice my dude. However, I did find something else
Turns out when I check the bootloader version it reads J700T1UVU3AQC3. Sure enough there was a baseband update and security update a few days ago and my device must've installed it while I was asleep. This would explain why my baseband is broken AND why Odin doesn't want me to flash the APK6 Bootloader.
So there's good news and bad news. The good news is there is hope but the bad news is I am currently at the mercy of whenever someone decides to upload this firmware on the internet (if anyone does that is)
Click to expand...
Click to collapse
sorry dude i cant help u because im using f variant..

khaisttj92 said:
sorry dude i cant help u because im using f variant..
Click to expand...
Click to collapse
Thanks anyways my dude

NullaVisus said:
Thanks anyways my dude
Click to expand...
Click to collapse
your welcome..

NullaVisus said:
No dice my dude. However, I did find something else
Turns out when I check the bootloader version it reads J700T1UVU3AQC3. Sure enough there was a baseband update and security update a few days ago and my device must've installed it while I was asleep. This would explain why my baseband is broken AND why Odin doesn't want me to flash the APK6 Bootloader.
So there's good news and bad news. The good news is there is hope but the bad news is I am currently at the mercy of whenever someone decides to upload this firmware on the internet (if anyone does that is)
Click to expand...
Click to collapse
You are lucky because you at least have a functioning bootloader and a working TWRP. You are unlucky because AQC3 firmware is not available publicly yet. In any case, bootloader cannot be flashed in TWRP as far as I know. Your only option is to get your missing ACQ3 partitions from someone else's back up. IF you have messed up your EFS partition though you are out of luck.
So exactly what partitions do you need? I may be able to give you those partitions if I have a personal backup of those from the past. Right now I have modified so many things that a current copy of my partitions will probably do you more harm than good.

najoor said:
You are lucky because you at least have a functioning bootloader and a working TWRP. You are unlucky because AQC3 firmware is not available publicly yet. In any case, bootloader cannot be flashed in TWRP as far as I know. Your only option is to get your missing ACQ3 partitions from someone else's back up. IF you have messed up your EFS partition though you are out of luck.
So exactly what partitions do you need? I may be able to give you those partitions if I have a personal backup of those from the past. Right now I have modified so many things that a current copy of my partitions will probably do you more harm than good.
Click to expand...
Click to collapse
As far as I know I just need a main system.img backup
Edit; to specify, if I was flashing with Odin it would be what I would put in the AP slot
The phone in its current state is extremely slow and buggy. My intuition tells me that the older Android version does NOT like the new fiirmware (The bootloader is also where the firmware/device config info is stored IIRC)

NullaVisus said:
As far as I know I just need a main system.img backup
Edit; to specify, if I was flashing with Odin it would be what I would put in the AP slot
The phone in its current state is extremely slow and buggy. My intuition tells me that the older Android version does NOT like the new fiirmware (The bootloader is also where the firmware/device config info is stored IIRC)
Click to expand...
Click to collapse
I can give you a system image but you will have to flash it in TWRP.

najoor said:
I can give you a system image but you will have to flash it in TWRP.
Click to expand...
Click to collapse
Thats fine. I already know how

NullaVisus said:
Thats fine. I already know how
Click to expand...
Click to collapse
Well lucky me Ive got a similar situation though I reflashed with a 3-part HOME file from sammobile to unroot/unTWRP, but did so not realizing the darn BL wasnt included. Lucky for me my build versions matched, so Odin flashed flawlessly, the device boots as if it were brand new, stock recovery and all, everything functions/boots as it should, splash, factory setup, TMobile network works fine etc - only problem is both SafetyNet tests fail, so Google wont let me use use Android Pay and every other payment app that hooks into their API shuts me out. I also noticed a lightning-fast error right before going into the bootloader if you boot from the stock recovery (its so fast I need to capture the log to see what it is).
Any suggestions on where to find a BL to go with my J700T & assuming I find one, any nuances I should be aware of when flashing so as to avoid a potential brick situation?
FYI I flashed with the below from sammobile (and yes I was already at AQF1).
J700TUVS3AQF1_J700TTMB3AQF1_J700TUVS3AQF1_HOME.tar

rawkahn said:
Well lucky me Ive got a similar situation though I reflashed with a 3-part HOME file from sammobile to unroot/unTWRP, but did so not realizing the darn BL wasnt included. Lucky for me my build versions matched, so Odin flashed flawlessly, the device boots as if it were brand new, stock recovery and all, everything functions/boots as it should, splash, factory setup, TMobile network works fine etc - only problem is both SafetyNet tests fail, so Google wont let me use use Android Pay and every other payment app that hooks into their API shuts me out. I also noticed a lightning-fast error right before going into the bootloader if you boot from the stock recovery (its so fast I need to capture the log to see what it is).
Any suggestions on where to find a BL to go with my J700T & assuming I find one, any nuances I should be aware of when flashing so as to avoid a potential brick situation?
FYI I flashed with the below from sammobile (and yes I was already at AQF1).
J700TUVS3AQF1_J700TTMB3AQF1_J700TUVS3AQF1_HOME.tar
Click to expand...
Click to collapse
The bootloader is always included with the firmware and is most certainly included with the firmware you posted.
Safetynet probably fails because you need to factory reset.

Flash Stock Firmware Galaxy Note5 N920G to a Galaxy Note5 N920T

Hello, I was wondering if there is a chance I can flash the Stock firmware from the N920G to my N920T. Why???, the reason is that here, in my country, my carrier is deploying a new band for LTE, B28 700, but even when I select that band, the handset won't use it. How do I know that???, because when I dial the code *#2263# and select the mentioned band, it won't get any signal at all. So, the baseband for the N920G uses the LTE bands I need, B2 (saturated and sharing bandwidth with 3.5G), B28 (6 months old and the one I want to use) and B7 (not officially deployed). As in this moment I'm using the QC6 Baseband with TWRP. If there is another way that I can get those signals to work on the phone, I'm open to suggestions.
Thank you for your time, hopefully there is a solution for my need and there is a really smart guy who can help my with this.
Thank you in advance for you kind help to this community.
Any other questions I'll be happy to answer them all.
Cheers mates.
:good:

Nothing?, no insights whatsoever?

ebisetti said:
Nothing?, no insights whatsoever?
Click to expand...
Click to collapse
Not possible to do that, the phone will just not accept the firmware when you try to do it.

MrMike2182 said:
Not possible to do that, the phone will just not accept the firmware when you try to do it.
Click to expand...
Click to collapse
Hey!, thanks for your advice, I really thought there was a workaround to enable the band I need, bummer .

ebisetti said:
Hey!, thanks for your advice, I really thought there was a workaround to enable the band I need, bummer .
Click to expand...
Click to collapse
As a work around, and I don't even know if this will work because I've never had a reason to do what you want to do but if I did, since you have TWRP what I would do is download the firmware of which you need and unzip it and try flashing JUST the modem and then select the band's you need if it even accepts the modem.bin (which you'll probably have to rezip to modem.tar otherwise it may not flash) if it doesn't work just put the phone back in download mode and reflash just the modem that you're currently using don't flash the entire firmware or it might erase everything you have.. That's really all I can think of after trying to search if that's possible..

MrMike2182 said:
As a work around, and I don't even know if this will work because I've never had a reason to do what you want to do but if I did, since you have TWRP what I would do is download the firmware of which you need and unzip it and try flashing JUST the modem and then select the band's you need if it even accepts the modem.bin (which you'll probably have to rezip to modem.tar otherwise it may not flash) if it doesn't work just put the phone back in download mode and reflash just the modem that you're currently using don't flash the entire firmware or it might erase everything you have.. That's really all I can think of after trying to search if that's possible..
Click to expand...
Click to collapse
Hello @MrMike2182:
Thank you very much for your advice. I'm gonna try this later this week, most likely on the 29th, there is a holy day here in my country. I'll let you know how it goes or any extra comments.
Have a good one.
KR.
EB.

Rooted S8+ on Verizon lost all mobile networks

I rooted last night using SamPwn and everything was working well until today... After one of the reboots I did today my phone stopped showing service, my sim card, network operators, and it wont hold an apn.
I have tried power cycling, removing the sim, resetting network settings, and wiping all cache.
Is there any way to only reflash the network portion? I have rooted and flashed quite a few things but havent bothered going into the intricacies and I feel as though this phone has less wiggle room for error. Hopefully you guys can get me a swift answer.
Thanks in advance!

BumpinPanda said:
I rooted last night using SamPwn and everything was working well until today... After one of the reboots I did today my phone stopped showing service, my sim card, network operators, and it wont hold an apn.
I have tried power cycling, removing the sim, resetting network settings, and wiping all cache.
Is there any way to only reflash the network portion? I have rooted and flashed quite a few things but havent bothered going into the intricacies and I feel as though this phone has less wiggle room for error. Hopefully you guys can get me a swift answer.
Thanks in advance!
Click to expand...
Click to collapse
Searching the SamPWND thread should net you a literal ton of solutions, but I'll try to sum it up for you.
Extract the stock firmware for whatever version you're running (QGL,QH3, ETC), and be sure to use 7zip for all of these extraction/archiving steps, then extract the modem.bin from the CP file and NON_HLOS.bin from the BL file. Now, highlight modem and non_hlos files and use 7zip to add to archive, you'll want to keep everything default, and the end result should be a tar file with whatever name you chose for the archive. Use Odin to flash this archive in the AP slot, it should work fine, but if not, you can try using the modified Odin (all default options for both). Once done, be sure to reboot to recovery and clear the cache and also a Network factory reset from settings if you're still unable to gain signal. If you're still not getting signal, you can try flashing the entire CP file and Home_CSC file (be sure to use the HOME_CSC, as regular CSC will overwrite root and start you over from scratch) using their respective slots in odin, though if modem and non_hlos doesn't get it up and running, that may be a redundant step.
Good luck!

instead you can flash combination file COMBINATION_FA70_G955USQU1AQD8 , just google for it. that will help to get Network Signal again

IJoxer said:
Searching the SamPWND thread should net you a literal ton of solutions, but I'll try to sum it up for you.
Extract the stock firmware for whatever version you're running (QGL,QH3, ETC), and be sure to use 7zip for all of these extraction/archiving steps, then extract the modem.bin from the CP file and NON_HLOS.bin from the BL file. Now, highlight modem and non_hlos files and use 7zip to add to archive, you'll want to keep everything default, and the end result should be a tar file with whatever name you chose for the archive. Use Odin to flash this archive in the AP slot, it should work fine, but if not, you can try using the modified Odin (all default options for both). Once done, be sure to reboot to recovery and clear the cache and also a Network factory reset from settings if you're still unable to gain signal. If you're still not getting signal, you can try flashing the entire CP file and Home_CSC file (be sure to use the HOME_CSC, as regular CSC will overwrite root and start you over from scratch) using their respective slots in odin, though if modem and non_hlos doesn't get it up and running, that may be a redundant step.
Good luck!
Click to expand...
Click to collapse
Thank you for this. I did a few queries in there and didn't come up with much but that could be due to my lack of optimized searching.
I ended up reflashing the csc and it wiped all my data but restored my data. I was at work when this happened and, being that I work in a Verizon, I need my phone quite a lot. I have since backed up my EFS and noted the suggestions in this thread so it will not happen again.
Once again I appreciate the help and I am sure it will save me in the near future!

012345678 said:
instead you can flash combination file COMBINATION_FA70_G955USQU1AQD8 , just google for it. that will help to get Network Signal again
Click to expand...
Click to collapse
I will try this next time this happens, thanks!

BumpinPanda said:
I will try this next time this happens, thanks!
Click to expand...
Click to collapse
Just note that the combination firmware he referenced is a universal firmware, and if you use a vzw firmware (ie QGL), it tends to cause issues with data/connectivity. Mixing carrier firmware and universal firmware has always cause me to start fresh, after 20+ roots using SamPWND, we finally came to that consensus.
Just something to keep in mind, 955U1 and 955U do not mix, regardless of version.

IJoxer said:
Just note that the combination firmware he referenced is a universal firmware, and if you use a vzw firmware (ie QGL), it tends to cause issues with data/connectivity. Mixing carrier firmware and universal firmware has always cause me to start fresh, after 20+ roots using SamPWND, we finally came to that consensus.
Just something to keep in mind, 955U1 and 955U do not mix, regardless of version.
Click to expand...
Click to collapse
Funnily enough, besides this issue, my service improved over stock with the root.
But even if that's the case doesn't the U1 simply signify an unlocked firmware version? Why does that cause an issue?

BumpinPanda said:
Funnily enough, besides this issue, my service improved over stock with the root.
But even if that's the case doesn't the U1 simply signify an unlocked firmware version? Why does that cause an issue?
Click to expand...
Click to collapse
Well, technically, it stands for a universal firmware, but I knew what you meant. 955U firmware is carrier specific, while U1 is Universal, as in it should apply to whichever carrier you have, so long as your sim card is in working order and tells the firmware which CSC to use correctly.
For whatever reason, when rooted and flashing the U1 firmware, the csc doesn't quite stick as it should, at least in my observations. Obviously flashing the modem and non_hlos is supposed to cure this issue (no data/connectivity/modem crashes), but I find it doesn't do much but change it in prop settings. My theory is that it's something to do with the efs partition superceding the csc flashed to system after using Ufirmware for root.
Regardless, I'm still trying to find a way to alleviate this issue, but it's a known bug that should be noted when rooting and using a mixture of U and U1 firmware.

IJoxer said:
Well, technically, it stands for a universal firmware, but I knew what you meant. 955U firmware is carrier specific, while U1 is Universal, as in it should apply to whichever carrier you have, so long as your sim card is in working order and tells the firmware which CSC to use correctly.
For whatever reason, when rooted and flashing the U1 firmware, the csc doesn't quite stick as it should, at least in my observations. Obviously flashing the modem and non_hlos is supposed to cure this issue (no data/connectivity/modem crashes), but I find it doesn't do much but change it in prop settings. My theory is that it's something to do with the efs partition superceding the csc flashed to system after using Ufirmware for root.
Regardless, I'm still trying to find a way to alleviate this issue, but it's a known bug that should be noted when rooting and using a mixture of U and U1 firmware.
Click to expand...
Click to collapse
Are you staying on root or stock? The root has helped my data issue slightly over stock and apparently the update for the stock firmware to fix my issue is in the works (but not yet released).
If you do find a stable solution let me know, it's working for now but I still drop to 1x frequently (which happened before root as well).
Thanks again for your help

BumpinPanda said:
Are you staying on root or stock? The root has helped my data issue slightly over stock and apparently the update for the stock firmware to fix my issue is in the works (but not yet released).
If you do find a stable solution let me know, it's working for now but I still drop to 1x frequently (which happened before root as well).
Thanks again for your help
Click to expand...
Click to collapse
Root does seem to help if, like I said, you don't mix and match firmwares, I'm on stock at the moment but will be rerooting tonight. There is a new carrier firmware for vzw and TMO, I'll be using vzw to accomplish the second part of the root method and updating to it (QI6). I'll update with how it goes later tonight or tomorrow, but here the link for the newest vzw firmware.
http://updato.com/firmware-archive-select-model?record=E15BA006A8B211E7963AFA163EE8F90B

IJoxer said:
Root does seem to help if, like I said, you don't mix and match firmwares, I'm on stock at the moment but will be rerooting tonight. There is a new carrier firmware for vzw and TMO, I'll be using vzw to accomplish the second part of the root method and updating to it (QI6). I'll update with how it goes later tonight or tomorrow, but here the link for the newest vzw firmware.
http://updato.com/firmware-archive-select-model?record=E15BA006A8B211E7963AFA163EE8F90B
Click to expand...
Click to collapse
Ah, I see. Root helped even though I used the universal firmware in the SamPWND thread (that could just be an individual issue regarding my area/device).
I'd love to see the results of the new firmware so I am looking forward to your update! Was that the main reason you chose to remove root? That and the 80% situation are the only things bothering me so far. Appreciate the link, you saved me a search

J727R4 Stock firmware nonexistent?

Hmm, so I'm going to try and bring root to these devices but first I need current stock firmware. So the issue I've run into, and this is the first time I've come across something like this... is that there doesn't seem to be any stock fw downloads available online. There are some extremely sketchy websites that try to get you to pay for low_ship firmwares but I don't like that.
How do we get current stock downloads for our devices if nothing has been released? I need SM-J727R4 J727R4TYU1AQD4 stock firmware for Galaxy J7 US Cellular...
EDIT:
Managed to get this phone rooted and everything was working great. Flashfire may have borked my System partition when I was doing backups, don't know how. But now I'm bricked until I can get firmware. Sent an email to Samsung, we'll see what they say.

Do you if the phone it comes unlocked ? Im interested in getting one

Sorry, Im on US Cellular but Im not sure that it is. I dont even know how to find out.
By the way, the firmware thankfully has been released. You can find it at SAMMOBILE and samsung-firmware.

Hi. Please, if root will be done - will it also work on European languages? Well thank you.

What is your exact model number, is it SM-J727R4?

LeviathaninWaves said:
What is your exact model number, is it SM-J727R4?
Click to expand...
Click to collapse
J727R4 US Cellular Check ESN A

tono4224 said:
Hi. Please, if root will be done - will it also work on European languages? Well thank you.
Click to expand...
Click to collapse
tono4224 said:
J727R4 US Cellular Check ESN A
Click to expand...
Click to collapse
Root should work great for you.

Stock stock ROM J727R4TYU1AQD4_J727R4USC1AQD4_USC Precisely J727R4TYU1AQJ3_USC1AQJ3_USC_U.S_Cellular_7.0. Please, can anyone use TWRP and superSU to root? Well thank you.

tono4224 said:
Stock stock ROM J727R4TYU1AQD4_J727R4USC1AQD4_USC Precisely J727R4TYU1AQJ3_USC1AQJ3_USC_U.S_Cellular_7.0. Please, can anyone use TWRP and superSU to root? Well thank you.
Click to expand...
Click to collapse
There isn't an official TWRP release for this phone, but the SMJ727P is an exact match to the SMJ727R4 in hardware. Use the TWRP for that device, wipe your data partition to remove encryption, then without rebooting flash the Magisk 14 zip for root. SuperSU works but has some problems. You will lose all your data but this is what I did and it works well.
Now that goes without saying, if things go wrong I'm not responsible.

Please help. Everything is like me, but after the SuperSU v.2.79-SR3 is introduced and the following restart is still running: Verification failed. Well thank you.

Prize. J727R4 works on the Slovak and on the network. I want to share my experience.
1. Start uninstall without restart, all 5 items (Odin3_v3.12.10) Build number: NRD90M. J727R4TYU1AQJ3. After the restart process, we select a flashlight.
2. Release the rest without restart, insert twrp_3.0.3-1_sm-j727p_17517. After we start without restart, we select the flashlight.
3.Downloads without reboot. insert J727P-SR3-SuperSU-v2.79-SR3_rooted_boot_AQB9. after we pick the flashlight.
4. Trojhmat home, power, + set wipe-Gawlik.chase.data and select restart system in the menu. After the ratcheting and learning is the phone root and unlock.

Maybe I have to close this topic.