Some of you may have seen my post in the Original Shield Tablet MM 4.0 Update thread, but now I'm finally making a new thread for these to help people out.
DISCLAIMER: I'm not responsible for your tablet. You own it, be smart about what you do with it. Not my problem if you screw something up.
This is an all-in-one MM update for the specific version of your Shield (select the right link at the bottom).
If you have already used my first zip, this will remote TegraOTA and upgrade TWRP to 3.0.
If you're already on MM, rooted, removed TegraOTA, and on TWRP 3.0, this won't add anything.
What does this contain?
Stock Rooted MM - Full Nvidia Update
TWRP 3.0.0 (thanks to @romracer)
TegraOTA Removed (Nobody needs that nonsense anyway)
SuperSU
What does this not contain?
Anything else - Read: Stock. Rooted.
What's broken?
OTA. You won't get any OTA updates (You don't want them if you're rooted anyway)
What do I need to do?
Be Unlocked
Have TWRP installed
Drop correct zip to device, then flash (if you need me to explain this, you shouldn't be doing it)
You CAN dirty flash this and not wipe /data partition (except the RoW LTE if flashing on a US LTE tab).
You also need to have a little patience. First boot takes some time. Chill. It's not hanging.
IGNORE the message in TWRP stating that the device isn't rooted. It is. TWRP just doesn't believe me. IGNORE IT.
Links Below:
(Be sure to download the one that you need. Not my problem if you can't handle that yourself.)
**RoW means Rest of World. Not my terminology, but that's what you use if you have anything other than a US tablet**
US WiFi Shield Tablet: Temporarily Removed
RoW WiFi Shield Tablet: Temporarily Removed
Flashing RoW LTE on US LTE tablet will cause you to be missing some buttons. Follow the instructions below to get them back.
RoW LTE Shield Tablet: Temporarily Removed
For US LTE on RoW LTE rom:
* Flash the rom
* Reboot to system
* Connect to PC (or maybe open Terminal Emulator if you have it installed)
* Run the following in adb if on PC
Code:
adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity
* Do what you can, reboot, and finish if it fails or crashes on the first attempt.
* Reboot
Thanks to @bill0405 for button fix when using the RoW LTE rom on a US LTE device.
**Note: I put this in General instead of Dev, because I didn't really do any dev work. Just some scripting to have it flash the way I want and do what I want.
I'll add International WiFi in a bit. I'm going to be downloading it when I get home. :highfive:
Hello, I haven't looked in your other threads but will these files automatically install the MM firmware?? Or will I need to do that separately??
Thanks.
Mojar7070 said:
Hello, I haven't looked in your other threads but will these files automatically install the MM firmware?? Or will I need to do that separately??
Click to expand...
Click to collapse
All-in-one install. No need to flash anything else. Just need to be unlocked and running TWRP recovery.
RoW WiFi model is added.
Install went well, thank you.
Just a heads up, first boot will take some time. There are no boot animations. Just the stock Nvidia splash screen. It will look like the boot hangs on the splash screen but be patient, it will get to the set up screen with time.
Edit: All is working well. Multi window option is not present on dev option, will modify in build prop. Thanks again.
Are any of these safe to install on a US LTE model? I never have and never will use the LTE modem, so it doesn't matter to me if it doesn't work as long as everything else does.
I heard the RoW LTE works fine on the US LTE and connects to Tmobile... I'm going to try it out now.
Awe, man. I was all excited and then I was ready and thought I'd boot into fastboot and...Ugh, I am still locked. If I just flash this it won't work right? Should I just unlock and then push everything over or is there a better way now? I am on 5.1.1 LP rooted with TWRP. Thanks for your help.
I'm currently on stock rooted 5.1.1, with TWRP installed, and Bit-O-Kernel. If I install this 6.0 update, will it wipe my tablet? I'm really not up for reinstalling and setting up everything all over again right now... I know I'll lose the kernel during the install, I'm ok with that as it's an easy quick reinstall.
That's what nandroids are for.
bluegizmo83 said:
I'm currently on stock rooted 5.1.1, with TWRP installed, and Bit-O-Kernel. If I install this 6.0 update, will it wipe my tablet? I'm really not up for reinstalling and setting up everything all over again right now... I know I'll lose the kernel during the install, I'm ok with that as it's an easy quick reinstall.
Click to expand...
Click to collapse
Dirty flash is fine. Just make sure the kernel you want to use supports M.
Installation worked but weird things happening.
This flashed perfectly on my US Wifi coming from a rooted stock LP.
TWRP 3.0.0 is very sluggish and behaves strangely. Also, trying to flash Xposed framework results in errors regarding "read only" even though the Mount System As Read Only option is unchecked.
I've tried all day to figure out a solution but I've found nothing.
As anyone else ran into these issues.
2kool2Bcruel said:
Also, trying to flash Xposed framework results in errors regarding "read only" even though the Mount System As Read Only option is unchecked.
Click to expand...
Click to collapse
What zip are you using to flash xposed? I bet I can fix the issue.
Any word from anyone who flashed one of these onto a US LTE model? Also, why isn't there a US LTE version available?
great stuff Harfainx, I was lazy so just sideloaded over the top of LP - worked an absolute charm :good:
Is it safe for OG tablet? Anyone confirm it's working without be killed.
Sent from my SHIELD Tablet using Tapatalk
I flashed the LP stock rooted and I was still locked. Can I flash this MM stock rooted and not be unlocked? Just was hoping I didn't have to unlock and loose everything and start over.
quangv said:
Is it safe for OG tablet? Anyone confirm it's working without be killed.
Sent from my SHIELD Tablet using Tapatalk
Click to expand...
Click to collapse
Yes, working good on OG shield. Been for 2 days now, still functional.
Device doesn't seem to be rooted? I downloaded SuperSU, but it complains. Is there a better binary?
Related
Hey guys, thought I would make a discussion thread about the new update today for the Sprint S5's. Looks like todays update was just over 200 MB. I don't know if it affects the latest chainfire root yet or not.
But yeah, make your stock S5 search for a update and you should find one waiting.
I've noticed:
The Android Security Patch Level is now December 1, 2016
Software version is now G900PVPU3CPL2
Do we know how long Samsung will continue to update our phone OTA? I appreciate that we still have support. It's not so bad being 1 month behind in security updates since even with security updates we are still vulnerable to 0-day exploits anyway.
Does anyone have a copy or link to this update? I want to see if it helps with signal on nougat based roms.
Thanks in advance
KIES
The~Skater~187 said:
Does anyone have a copy or link to this update? I want to see if it helps with signal on nougat based roms.
Thanks in advance
Click to expand...
Click to collapse
The best way to actually try and get this is through Kies or SmartSwitch apps. Sam Mobile does not have this, and it would be, about another month from now, till they even have it... Been there too many times looking for this so call update.
I know that is does state 01dec2016 security update. I also know, that Knox is added to (at least, all Knox is added data (Kbs, not Mbs) I also believe, they (Samsung, tech side phone updates) have added more apps for Knox. However, we don't have anything that is related to these new updates. heck 2 of them, state they have DATA. Through the stock app manager, you have an option, to erase this, because it is not installed....
not sure if this helps you find what you are looking for. ...
( me 2cents on this),... Why extra apps and data../. Why do we have to download a complete new Stock Rom, when we already were stock anyway ???) (Me dog did a real number on the phone. had to be a good eBay and Amazon shopper... Completely rebuild my S5.
Wondering if the S5 will be having A real update, such as 7.1... ??? !!!) we S5, was not on or in the press release early this month, regard the Samsung, Android updates... 7.0, 7.1 NOUGAT !!!
I certainly believe that they will in time update the S5 to 71 Nougat
This may just be a hunch but I have a feeling that if the Note 8's don't blow peoples faces off that the S5 probably won't be seeing Nougat officially (from Sammy).
Well there's a new update today for me anyways. This one is just over 27 MB's. 2 new updates in one month!
The new software version is called G900PVPS3CQA2
New antutu score updated.
It's very unlikely that S5 will receive an official N OTA from any carrier(or any msm8974, for that matter) as Qualcomm had planned 'no official support' for msm8974 past M. It was already very late in the cycle for M, and may not have made it onto the list for M had the msm8994 sucked less.
Does anybody know if we are still able to root our phone model with this new update?
LEN671 said:
Does anybody know if we are still able to root our phone model with this new update?
Click to expand...
Click to collapse
I don't know for sure myself, as I have not gotten the update bring on aftermarket firmware. But I would imagine if you flash twrp and apply the latest supersu, it should work. I know that's how I did it with the cpk1 update.
Someone please correct me if I am wrong. I don't want anyone bricking their device based on what I've said.
LEN671 said:
Does anybody know if we are still able to root our phone model with this new update?
Click to expand...
Click to collapse
Yes.. I did
I ran into some issues and factory reset, deleted my Internal Storage, and then ODined PK1 Stock onto my Sprint S5. I then got a prompt that G900PVPU3CPL2 update was available. After the phone restarted I was then prompted to update to G900PVPS3CQA2 After that one installed and restarted.. I successfully rooted using CFAutoroot and then put the latest TWRP Recovery on.
Now.. what screwed me up is me trying to put a 7.1.1 Rom on (LOS and even Resurrection Remix). Phone froze and would not allow me to enter any info in or select Wifi. When it did.. I had ZERO signal/data. I then re-odined.. PK1.. without the updates, rooted, and Twrped, then flashed the 7.1.1 (LOS and RR) with no problems. Made back-ups of both (within TWRP) and was able to Restore all three at will. I am currently back on the STOCK/ROOTED w/all updates including the QA2.. as I didn't feel like doing the customization of the 7.1.1. Roms with the game (SuperBowl) getting ready to come on.
Personally I like the Stock- Rooted -Updated- Twrp config as the only thing that bothers me is the heading theme being that Samsung Aqua blue. If I could theme it.. I might stay with it
Cmicasa the Great XvX said:
Yes.. I did
I ran into some issues and factory reset, deleted my Internal Storage, and then ODined PK1 Stock onto my Sprint S5. I then got a prompt that G900PVPU3CPL2 update was available. After the phone restarted I was then prompted to update to G900PVPS3CQA2 After that one installed and restarted.. I successfully rooted using CFAutoroot and then put the latest TWRP Recovery on.
Now.. what screwed me up is me trying to put a 7.1.1 Rom on (LOS and even Resurrection Remix). Phone froze and would not allow me to enter any info in or select Wifi. When it did.. I had ZERO signal/data. I then re-odined.. PK1.. without the updates, rooted, and Twrped, then flashed the 7.1.1 (LOS and RR) with no problems. Made back-ups of both (within TWRP) and was able to Restore all three at will. I am currently back on the STOCK/ROOTED w/all updates including the QA2.. as I didn't feel like doing the customization of the 7.1.1. Roms with the game (SuperBowl) getting ready to come on.
Personally I like the Stock- Rooted -Updated- Twrp config as the only thing that bothers me is the heading theme being that Samsung Aqua blue. If I could theme it.. I might stay with it
Click to expand...
Click to collapse
Thank you for the info!! This is what I wanted to hear!! Someone who had the newest update and then went into detail of what they encountered. Thank you again!! Much appreciated!!
You can always see the latest official stuff for our phones here: https://www.sammobile.com/firmwares/database/SM-G900P/SPR/
The only way we'll ever see Nougat on the S5 is via rom ports, or CM14/CM14.1 Official, which is supporting the S5.
LEN671 said:
Thank you for the info!! This is what I wanted to hear!! Someone who had the newest update and then went into detail of what they encountered. Thank you again!! Much appreciated!!
Click to expand...
Click to collapse
No problem. After using the STOCK/ROOTED MM version with all the updates , I have decided that I really am just gonna stay on it. It is smooth, fast, and has all the things I need. I killed Bloatware so outside of the pull-down bar being aqua blue.. and background being white I'm very content.
Anyone know of an app for rooted phones that will allow me to rectify those things?
Cmicasa the Great XvX said:
No problem. After using the STOCK/ROOTED MM version with all the updates , I have decided that I really am just gonna stay on it. It is smooth, fast, and has all the things I need. I killed Bloatware so outside of the pull-down bar being aqua blue.. and background being white I'm very content.
Anyone know of an app for rooted phones that will allow me to rectify those things?
Click to expand...
Click to collapse
@cmicasa the Great, I keep getting a failed when using Odin, CFAutoroot, KingoRoot, KingRoot, and even when I try to use TWRP. I also read somewhere that I would have to unlock the Bootloader in order for this to work? Do you mind sending me a message in PM about how you did your rooting? If you don't mind sir. Thank you again for your time and assistance.
LEN671 said:
@cmicasa the Great, I keep getting a failed when using Odin, CFAutoroot, KingoRoot, KingRoot, and even when I try to use TWRP. I also read somewhere that I would have to unlock the Bootloader in order for this to work? Do you mind sending me a message in PM about how you did your rooting? If you don't mind sir. Thank you again for your time and assistance.
Click to expand...
Click to collapse
This is everything I did including putting PK1 on my phone, letting it then upgrade to G900PVPU3CPL2 and then update to G900PVPS3CQA2 After that one installed and restarted.. I proceeded to Root and put custom recovery on. Because U will not get the OTA updates once U root
Here are my steps Len:
1) First make sure U have the ODIN 3.10 or above> Links are here SamsungOdin or here Odin Download
2) Then go into Download Mode by pressing the "Volume down +home and then Power buttons" Once device boots hit the volume up button and Android dude should appear
3) open ODIN (I used 3.10) and plug phone to computer.
Load the PK1 tar in the PDA Slot, put your phone in Download Mode (power off, hold Vol Down, Home, and Power), and connect your phone to the PC. (I checked F.Reset and Auto Reboot)
Then after that is successful run CF Auto Root or whatever root injector you have in the PDA slot again. Once that finishes (wait until Odin tells you it was a Success before doing anything), get ROM Toolbox or something of that nature and remove any app with Knox in the title or that has the Knox symbol.
Load your phone into Download Mode one last time and then put whatever recovery you have (I use TWRP, make sure you grab the .tar format instead of the zip) and put that in the Bootloader slot in Odin. Then you're good to go, rooted and custom recovery, sky's the limit.
-I found a perfect site that does exactly what I did using CFAUTOROOT. It explains everything including TWRP
then for Root http://www.stechguide.com/root-samsung-galaxy-s5-android-marshmallow/
then for Recovery http://www.stechguide.com/install-twrp-recovery-samsung-galaxy-s5/
Cmicasa the Great XvX said:
This is everything I did including putting PK1 on my phone, letting it then upgrade to G900PVPU3CPL2 and then update to G900PVPS3CQA2 After that one installed and restarted.. I proceeded to Root and put custom recovery on. Because U will not get the OTA updates once U root
Here are my steps Len:
1) First make sure U have the ODIN 3.10 or above> Links are here SamsungOdin or here Odin Download
2) Then go into Download Mode by pressing the "Volume down +home and then Power buttons" Once device boots hit the volume up button and Android dude should appear
3) open ODIN (I used 3.10) and plug phone to computer.
Load the PK1 tar in the PDA Slot, put your phone in Download Mode (power off, hold Vol Down, Home, and Power), and connect your phone to the PC. (I checked F.Reset and Auto Reboot)
Then after that is successful run CF Auto Root or whatever root injector you have in the PDA slot again. Once that finishes (wait until Odin tells you it was a Success before doing anything), get ROM Toolbox or something of that nature and remove any app with Knox in the title or that has the Knox symbol.
Load your phone into Download Mode one last time and then put whatever recovery you have (I use TWRP, make sure you grab the .tar format instead of the zip) and put that in the Bootloader slot in Odin. Then you're good to go, rooted and custom recovery, sky's the limit.
-I found a perfect site that does exactly what I did using CFAUTOROOT. It explains everything including TWRP
then for Root http://www.stechguide.com/root-samsung-galaxy-s5-android-marshmallow/
then for Recovery http://www.stechguide.com/install-twrp-recovery-samsung-galaxy-s5/
Click to expand...
Click to collapse
Thank you very much for breaking it down dummy style. Haha. It definitely helps. I will try it out when I get to my house and PC.
LEN671 said:
Thank you very much for breaking it down dummy style. Haha. It definitely helps. I will try it out when I get to my house and PC.
Click to expand...
Click to collapse
LOL.. no issues. Definitely go to those bottom links. They even have pictures. Be careful though.. I tried to experiment and see what checking the "Nand and Erase" in odin.. and damn near bricked my phone. Had to get PIT file and rebuild. Working smoother than ever now.. and like I said.. I'm sticking to Stock/Rooted and Xposed
Cmicasa the Great XvX said:
LOL.. no issues. Definitely go to those bottom links. They even have pictures. Be careful though.. I tried to experiment and see what checking the "Nand and Erase" in odin.. and damn near bricked my phone. Had to get PIT file and rebuild. Working smoother than ever now.. and like I said.. I'm sticking to Stock/Rooted and Xposed
Click to expand...
Click to collapse
So just to clear, there is no need to unlock the Bootloader? Also, if my phone has a password, does it need to be disabled? I.e. lock security feature such as creating a pattern in order to unlock the device to use.
LEN671 said:
So just to clear, there is no need to unlock the Bootloader? Also, if my phone has a password, does it need to be disabled? I.e. lock security feature such as creating a pattern in order to unlock the device to use.
Click to expand...
Click to collapse
I'm confused on that. Your phone will be booted into DOWNLOAD mode during the time of ODIN. Your Password will be inconsiquential
Cmicasa the Great XvX said:
I'm confused on that. Your phone will be booted into DOWNLOAD mode during the time of ODIN. Your Password will be inconsiquential
Click to expand...
Click to collapse
Okay, I am just making sure as I am not sure if that was one of reasons why Odin came back saying "FAIL". Thank you again.
CAUTION TO NOT LOOSE TWRP
I read two posts that say v21, now again on V8.5, put the stock recovery back instead of twrp. This is probably a side effect of a fresh stock /system and wipe of /data.
As a preventive step, when done flashing and wiping reboot to recovery FIRST, before booting the system It will allow recovery to handle removing the recovery-from-boot.p that flashes stock recovery.
I just patched the modified V7.4.2 up to the newly released 8.3 now 8.4. 8.5, 8.7,9.0 -V9.2 Patch
New update has been made from V17 to V21 of the non prime version of R1-HD, Non prime is behind on security patch (2017-05-05)
Copied ROM from phone and made twrp install ROM from it.
* No preloader change (official updates change the preloader to block your ability to use sp flash tools for rom flashing)
* No lk.bin change __ this part is what allows you to choose boot options(boot menu when power and volume pressed together)
* No "FOTA" app Fota has now been left in to make it easier to get next update, if that ever happens.
* No opera browser
* No adds (removed in the modified 7.4.2)
* Custom boot logo (only done on v8.3, there was no interest in this so abandoned)
--Newer versions of rom left stock, Leaving mods up to user.
** while it is not necessary to do a wipe with this ROM, I still recommend it.
**Thanks:
** @vampirefo needed his patched v7.4.2 in order to apply this new 8.3 patch and again for 8.4
** @ColtonDRG OR @jasonmerc I do not remember which one made it: For the image used in the custom logo
and the modified zip is here .
Roms are rootable with SuperSU, flashed in twrp after install. Must be done in systemless mode. In order to patch system veridy in boot.img
Logo update did not work on original rom changing link to updated version
BLU rolled v8.3 back to v7.4.2 because of app compatability issues. V8.4 is there fixed release. Both 8.3 and 8.4 are modified prime roms with ads stripped
V21 is the non prime update.
Unmodified V6.1
==>NON-ROOTED-logo-not-replaced-modified-V8.3
==>Fixed Logo modified NON_ROOTED V8.3
==>>modified V8.4
==>>modified V8.5
==>>Full with Ads V8.7
==>>Full with Ads V9.0
==>>Patch For V9.2 must be flashed on top of fresh V9.0
****Run debloat ==>script to remove ads if you need/ want to, or remove from zip before flashing ****
alt. manual example: before reboot, while still in twrp. Select mount and put checkmark next to system. Then run these two commands in adb terminal
Code:
adb shell rm /system/priv-app/com.amazon.*/com.amazon.*.apk
adb shell rm /system/app/Adups*/*.apk
==>>Modified V21
** stand alone logo installs
I flashed this but I didn't get the custom boot logo.
mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
I had that happen to my second phone too.
I don't have an explanation yet.
I even made a separate update.zip , that one didn't make the logo change either. I did eventually change it with sp flash tool.
I tried with both recoveries.
and multiple /dev location formats. and for whatever reason my one phone did not accept the logo change from recovery.
And the other test phone it worked.
mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
Neither did I but it all seems to be working fine
Been using this for about a day now, likewise no custom boot logo, but that's fine. Otherwise, it's been running super well. A lot better than the previous mostly stock version did for me with the bloatware APKs removed after the install. A lot of the general idiosyncrasies of the previous version of the stock rom seem to have gone away for me. It seemed to have weird storage management issues, errors moving to SD, broken symlinks that prevent apps from moving or being reinstalled, and a lot of other little non-storage issues, but so far, none off that here.
Long story short, good work! I hope we eventually see proper 7.x roms through some of the efforts going on, but in the meanwhile, your work here has made life a little bit better on 6.
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
**logo-update is same as composite but with alt updater-binary
**composite-logo screenshot is in op
**stock logo will return to original BLU logo
mrmazak said:
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
Click to expand...
Click to collapse
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Serenitybs said:
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Click to expand...
Click to collapse
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
Somebody already tried this out
linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
It was just wishful thinking. I have no idea how all of this is done. All I know is @mrmazak has helped me to fall in love with my phone again with this V8.3. The 7.4.2 did seem a bit buggy for my phone but this update works beautifully and I didn't even root it. If this remains true I will be happy with this phone for awhile even on 6.0
Really confused right now.
I was browsing through the settings menus. And found in the Settings-security- menu a toggle labeled "quick boot" ( not to be confused with "fastboot") . I enabled it then rebooted to see if it booted quicker. Didn't seem to make much if any difference. So I went back to turn it back off. And it wasn't there. I checked in my other phone , it wasn't there on that one either.
Did any body see this menu item, and if so where is is it?
Edit 1:
Few more power off , power on cycles to compare times. With other phone and defiantly seems to have turned on some faster boot option.
This phone goes from off to on in 5-6 seconds other phone takes about 20.
Edit 2:
OK , I panicked for a minute.
Couldn't find the setting and thought that it was another way to block sp flash tool by preventing you from ever being fully powered off.
But the setting was in accessibility not security.
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
detroitredwings said:
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
Click to expand...
Click to collapse
The mode changer app is technically a security issue. I did have that warning a few times when using mode changer app from the XDA thread of the developer, then when I used the app downloaded from f-droid it worked with systemless root and didn't give the security warning.
The app downloaded from f-droid worked for me as well, many thanks!
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Letitride said:
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Click to expand...
Click to collapse
I also had an app that previously work, say is not compatible now.
Maybe has to do with apps that have links to pay accounts. And that has something to do with trustzone. (Tee1 & tee2)
Those sections I left out of the update. I will add it back in and test. Update when I do. It is also possible this problem is why Blu rolled back there update.
**EDIT**
well that didn't go well at all.
I flashed the new trustzone.bin files from the official update. Now phone no longer turns on and no longer connects to flash tool
**EDIT 2**
After much persistence and many failed attempts to get phone recognized in pc again. Finnaly got to a point that phone was cycling between "preloader" driver and "usb serial device", and with careful timing was able to start sp flash tool at just right time and the flashing back to original trustzone files seems to have recovered phone.
for the record i am not sure what steps made it work. But I was shifting back and forth between leaving phone sit on charge, then on charge with rubber band wrapped around power button, then not plugged in , and not plugged in with rubber band on power button.
Okay... persistence is key in customization, i guess! I am getting somewhere here!
mrmazak said:
The first link is needed to get phone unlocked so you can install twrp.
Click to expand...
Click to collapse
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
OldSkewler said:
Okay... persistence is key in customization, i guess! I am getting somewhere here!
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
Click to expand...
Click to collapse
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Many ways to do that.
Easiest is to copy to phone while phone is connected to PC.
Cam also download file from internet with your phone.
Bottom line is get zip file to the phone boot to recovery and install
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
mrmazak said:
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Easiest is to copy to phone while phone is connected to PC.
Bottom line is get zip file to the phone boot to recovery and install
Click to expand...
Click to collapse
Right on man! I am officially running 8.3 ROM with April 5th 2017 Security Patch Level! Geez.. it was not easy but I got this working!
MrMazak, I followed all your instructions on both links, so could you tell me what exactly I have on my phone? Is it rooted? Bootloader Unlocked? The phone seems to be working fine but I don't know what level of access I have. Honestly I don't even know exactly what the differences between all these terms are.
Also, do I have or not SU? One of the steps under the .bat I believe install it. How do I access it?
Thanks again!
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Weasel0 said:
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
Click to expand...
Click to collapse
My install is pretty fresh, couple of hours, but as far as I can tell all is working fine with Wifi, As a matter of fact this is a new device only connected with Wifi and no SIM Card.... internet works fine.
Tracfone version
I'm having no luck with Kingroot. It says no root available for device.
According to 'one-click-root' website, the device has no way of rooting it.
Is there any updated information?
.
device specifics:
model: SM-S920LZAATFN
android: 5.0.2
build: LRX22G.S920LUDU1APK2
hardware version: S920L.03
.
[edit: was hoping to change the title to reflect that this post is about the tracfone version]
TWRP recovery method?
TWRP recovery method?
I've read that a phone may possibly be able to be rooted by using odin to download a TWRP recovery, then booting into that new recovery using hardware keys, instead of rebooting normally. And this results in a rooted phone?
I think I have seen a TWRP that may work with this phone. Any help is appreciated. I'd like to be able to update this thread to include a step by step approach to this and other versions of the same model 920.
I'll continue to post updates as I discover more information.
DIY time : crash course in brain surgery
Ok, so I've read a bit of stuff in the forums on the SM-S920L, mostly about the StraightTalk variant, which apparently uses the same system rom, though I'm not so sure.
At any rate, rather than just throw carp at the phone and hope it sticks, I'm going to teach myself how to do it all myself, a-z, 1,2,3... etc., starting with making stock images of the various components, for recovery purposes. Perhaps the phone can be used as a TracFone again someday, though I have no desire to do so, having already bought another for cheaper that even works better, though not as fancy, just newer.
So, I'll leave it here for now and just update the primary with new information as I discover it, starting with the extraction of the stock images, hopefully without goofing up the phone, lol.
This is an unpopular phone, at least for hackers. But it will be a good tool for expanding my knowledge.
Any help appreciated, such as, 'Is this even necessary? There are files here here and here that will do it all'.
(lol, nope... so far I've discovered there is no root option, kingroot no work, etc. There seems to be no posts with information specifically regarding the TracFone 'variant' of this model. It suggests that i can use the StraightTalk files for it, which may work, but there are many questionable unanswered problems.)
friimynd said:
Ok, so I've read a bit of stuff in the forums on the SM-S920L, mostly about the StraightTalk variant, which apparently uses the same system rom, though I'm not so sure.
At any rate, rather than just throw carp at the phone and hope it sticks, I'm going to teach myself how to do it all myself, a-z, 1,2,3... etc., starting with making stock images of the various components, for recovery purposes. Perhaps the phone can be used as a TracFone again someday, though I have no desire to do so, having already bought another for cheaper that even works better, though not as fancy, just newer.
So, I'll leave it here for now and just update the primary with new information as I discover it, starting with the extraction of the stock images, hopefully without goofing up the phone, lol.
This is an unpopular phone, at least for hackers. But it will be a good tool for expanding my knowledge.
Any help appreciated, such as, 'Is this even necessary? There are files here here and here that will do it all'.
(lol, nope... so far I've discovered there is no root option, kingroot no work, etc. There seems to be no posts with information specifically regarding the TracFone 'variant' of this model. It suggests that i can use the StraightTalk files for it, which may work, but there are many questionable unanswered problems.)
Click to expand...
Click to collapse
Definitely don't use kingroot.
Do you have a laptop or pc? If so I can help you out. I have the same phone. Mine is straight talk, but it's sm-s920l a tracefone just through straight talk.
c3p0u812 said:
Definitely don't use kingroot.
Do you have a laptop or pc? If so I can help you out. I have the same phone. Mine is straight talk, but it's sm-s920l a tracefone just through straight talk.
Click to expand...
Click to collapse
Ya I got the straight talk, I have been using king root but I totally bricked and wiped my phone on purpose because I wanted to start fresh and let it update. Having a problem though I used twrp and nuked all my ****, or so I thought. I'm trying to OTA update I'm currently on 5.0.2 and it's saying I have a system update and even after I checked everything to be deleted it still says error and one of my files is modified or some**** like that. I think it's like admin.prop so **** it. I do however want to go systemless root. What do you suggest is the best root and rom for our device?
To answer op question yes your phone is the same as ours. Mine even shows tracphone on boot.
Inuyashian said:
Ya I got the straight talk, I have been using king root but I totally bricked and wiped my phone on purpose because I wanted to start fresh and let it update. Having a problem though I used twrp and nuked all my ****, or so I thought. I'm trying to OTA update I'm currently on 5.0.2 and it's saying I have a system update and even after I checked everything to be deleted it still says error and one of my files is modified or some**** like that. I think it's like admin.prop so **** it. I do however want to go systemless root. What do you suggest is the best root and rom for our device?
To answer op question yes your phone is the same as ours. Mine even shows tracphone on boot.
Click to expand...
Click to collapse
Well for our phone there is only one custom ROM and it's LineageOS 13.0 https://forum.xda-developers.com/grand-prime/development/unofficial-cyanogenmod-13-0-galaxy-t3491494 It's android 6.0 and it can be rooted too. It's not being updated anymore for our device as far as I know. There is Lineage 14.* but not for our variant.
For systemless root you'll want to go with Magisk. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 I had Lineage, and don't get me wrong it's worth checking out, but I downgraded back to stock and went with Magisk. You can even get Xposed throughMagisk.
If I was you, I would flash back to stock. You can go to this thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 and download the first two, Stock Boot and Stock Recovery. Make sure to unzip them because you need the md5 files they extract. I'd wipe everything again and then get into download mode. On your PC fire up Odin, I'm using version 3.10 http://odindownload.com/download/clean/Odin_3.10.0.zip Click BL use the stick boot md5 and then under ap use the stock recovery md5. When it reboots and you set it up do not turn reactivation lock on.
If you don't already have Magisk on your sd card get it on there and install through twrp. It will ask if you want to root. Might make a back up after. I always make backups and then transfer from sd to my pc. I can restore to like 6 different versions of my phone right now lol I'm no expert, I haven't been messing around with all this for long so I hope that all makes sense. :fingers-crossed:
c3p0u812 said:
Well for our phone there is only one custom ROM and it's LineageOS 13.0 https://forum.xda-developers.com/grand-prime/development/unofficial-cyanogenmod-13-0-galaxy-t3491494 It's android 6.0 and it can be rooted too. It's not being updated anymore for our device as far as I know. There is Lineage 14.* but not for our variant.
For systemless root you'll want to go with Magisk. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 I had Lineage, and don't get me wrong it's worth checking out, but I downgraded back to stock and went with Magisk. You can even get Xposed throughMagisk.
If I was you, I would flash back to stock. You can go to this thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 and download the first two, Stock Boot and Stock Recovery. Make sure to unzip them because you need the md5 files they extract. I'd wipe everything again and then get into download mode. On your PC fire up Odin, I'm using version 3.10 http://odindownload.com/download/clean/Odin_3.10.0.zip Click BL use the stick boot md5 and then under ap use the stock recovery md5. When it reboots and you set it up do not turn reactivation lock on.
If you don't already have Magisk on your sd card get it on there and install through twrp. It will ask if you want to root. Might make a back up after. I always make backups and then transfer from sd to my pc. I can restore to like 6 different versions of my phone right now lol I'm no expert, I haven't been messing around with all this for long so I hope that all makes sense. :fingers-crossed:
Click to expand...
Click to collapse
Haha ya it does I just wish they didn't treat our phone like it has Ebola or some****. All kinds of **** for the other ones. I agree on the magisk because I really want to try that out. Alright thanks for all the helpful links I come to this site to find **** for ours and I end up looking at a bunch of cool stuff I can't have.
I'm waiting on the pixel 2 XL before I upgrade. We just missing out on too much stuff. I think magisk will keep me busy in the meantime though. Thanks again man I'm Soo add once I get here on all the stuff then I wonder well will this work or this work and by then just like awwww **** it.
Inuyashian said:
Haha ya it does I just wish they didn't treat our phone like it has Ebola or some****. All kinds of **** for the other ones. I agree on the magisk because I really want to try that out. Alright thanks for all the helpful links I come to this site to find **** for ours and I end up looking at a bunch of cool stuff I can't have.
I'm waiting on the pixel 2 XL before I upgrade. We just missing out on too much stuff. I think magisk will keep me busy in the meantime though. Thanks again man I'm Soo add once I get here on all the stuff then I wonder well will this work or this work and by then just like awwww **** it.
Click to expand...
Click to collapse
Hey, I thought I'd let you know LineageOS 14.1 is available to us now. I can't find a specific thread on it, but you can download it from http://grandprime.ddns.net/jenkins/job/LOS_Builds/# Flash it with twrp. You will want to flash that and then flash open gapps [ARM - 7.1] and then whichever from here http://opengapps.org/ I did all that first, set it up rebooted and then installed Magisk.
It has Substratum pre-installed and it let's you theme it nicely. There is only an unofficial xposed version so far.
Anywho, thought I'd throw that out there.
thanks for the replies, gives me inspiration to keep on trying; the phone is pretty ho-hum with default stuff and the general blah blah of social media, etc.;
thanks for the tips, feel free to post more details as they come in
My Turn
I'm about to try and put 14.1 and Magisk on mine. Wish me luck!
downloading twrp recovery and rooting
in google search up twrp click on the first link then click on devices on the top right corner then search up your phone download the twrp.img.tar file
power off your phone and press volume down + home button + power button to boot into download mode
in odin select AP then select the twrp.img.tar you downloaded then press start
your phone will reboot then download the SuperSU zip file
then go to settings then go to find my mobile you have to get a samsung account then you will see reactivation lock option turn that off
then power off your phone then press volume up + home button + power button to reboot into twrp recovery
once booted tap the install option then select where you downloaded the supersu zip file swipe to flash it once done flashing you will see the reboot system option to reboot your phone
then your phone should be rooted!
I have a Galaxy J3 (2016) J320ZN.
I have rooted it, and would like to install TWRP then xsposed, maybe even another ROM if there is any that will work.
Will the TWRP posted here for other models work on my phone?
How about ROMs? Thank you.:silly:
azlemad said:
I have a Galaxy J3 (2016) J320ZN.
I have rooted it, and would like to install TWRP then xsposed, maybe even another ROM if there is any that will work.
Will the TWRP posted here for other models work on my phone?
How about ROMs? Thank you.:silly:
Click to expand...
Click to collapse
I've only just worked this out myself and was going back to update my post...did a search and that's how I found your question.
I've had so much trouble with this... either, you couldn't get root using SuperSU.zip through TWRP (there's another thread on this)... because you'd get stuck in a bootloop and my "solution" was to flash CF-Auto-Root again... without realizing that CF-Auto-Root wipes to stock recovery XD. Through this, though I lost my phone re-set up and TWRP.... I saw that there was a dm-verity error which I don't understand but know there is a patch.... and maybe that's why people were getting bootloops? I'm really not an expert at all. I just try until something works.
SO, you could just first try flashing TWRP for J3lte from the link I provided and then the latest SuperSU and see if that works now.....(earlier versions did not) if it doesn't work and you get stuck in a bootloop then flash CF-Auto-Root (available at: https://download.chainfire.eu/986/C...3lteusc-j3lteusc-smj320r4.zip?retrieve_file=1) and start again. I PERSONALLY only had success without a bootloop ONCE I added the dm-verity patch to my install procedure:
The TWRP that will work for the J320ZN is j3lte: https://dl.twrp.me/j3lte/
I used the latest version twrp-3.2.1-0-j3lte.img.
If you need in-depth help look for a tutorial or quote me and I'll respond & try walk you through it. I know that model J320YZ uses the same TWRP and there is a tutorial on XDA for the basics.....
Once TWRP is installed and you've booted into TWRP recovery and you've formatted, Install SuperSU.zip through the "Install" button on TWRP. You must have SuperSU.zip on your external SD card (click "Select Storage" to select it).
https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
I used v.2.82 SR5
Finally, BEFORE REBOOTING, I installed no-verity-opt-encrypt-6.0.zip using the same TWRP "Install" button method - which was also on my external SD card
https://androidfilebox.com/miscellaneous/dm-verity-and-forced-encryption-disabler/
Then you can reboot, and set up your phone. Xposed works. If you already ran the fixes using Apps2SD to fix security measures that prevntd Link2SD from creating mountscripts, that stays fixed after all of this.
BACK UP YOUR PHONE FIRST 'cos you'll have to reset it all up again. Samsung Smart Switch (on your PC) helps, as will Titanium Backup.
Now.... as I said I'm not an expert. I don't understand why things are the way they are. Nor am I responsible if the dm-verity wasn't needed, which is why maybe you should just try TWRP then latest SuperSU first. BUT for me, I had bootloop and needed the 3rd step of dm-verity patch.
As for Custom ROMS... I have no real interest in those, so that's something you'll have to experiment with yourself, or ask someone else
IMPORTANT: I thought I'd better add that once you've got TWRP and root installed... and want to install Xposed, you cannot use the official version for Android 5.1.1. It will not work on our Samsung Touchwiz Stock ROMS. You can either install a custom ROM first, or you will have to use the Unofficial version by wanam that will work on device.
Here's a tutorial: https://www.tricksfolks.com/install-xposed-framework-samsung-lollipop-marshmallow/
Make sure to select from the download links the file for 5.1.1 and our hardware is arm so download that file, not arm64 version or x86 version. Should be xposed-v87.1-sdk22-arm-custom-build-by-wanam.zip
Also note, I had some issues with the Xposed Installer (apk) - latest one 3.2. Didn't want to register the wanam framework that I flashed in TWRP. So, I rolled back to 3.1.5 and that works OK. You'll have a big red warning telling you not to update THEIR framework... but ignore that and just go to Downloads and install away.
The article I linked above with the tutorial and download links has an earlier version of the Xposed Installer so you could try that if you can't find v.3.1.5. Just don't use v.3.2
ALSO ANYBODY PLEASE UPDATE ME IF YOU GOT TWRP AND ROOT WITH OR WITHOUT DM-VERITY PATCH. I'd like to know so I can learn more about this stuff. Still a novice.
Annnnnd I just realized you were the one that PMed me a few weeks ago to get me working on this and that you'd broken your phone hehehehe.
Well, I'm just updating it on all the J320ZN threads now for future folk.
Winston Churchill said:
Annnnnd I just realized you were the one that PMed me a few weeks ago to get me working on this and that you'd broken your phone hehehehe.
Well, I'm just updating it on all the J320ZN threads now for future folk.
Click to expand...
Click to collapse
lol
yeah, that was me sadly -_-
But thank you very much anyway, for taking the time and effort to post this, I'm sure it'd be useful to somebody out there
Winston Churchill said:
I've only just worked this out myself and was going back to update my post...did a search and that's how I found your question.
I've had so much trouble with this... either, you couldn't get root using SuperSU.zip through TWRP (there's another thread on this)... because you'd get stuck in a bootloop and my "solution" was to flash CF-Auto-Root again... without realizing that CF-Auto-Root wipes to stock recovery XD. Through this, though I lost my phone re-set up and TWRP.... I saw that there was a dm-verity error which ...
As for Custom ROMS... I have no real interest in those, so that's something you'll have to experiment with yourself, or ask someone else
Click to expand...
Click to collapse
Wow, thanks for going through the pain so I may not have to go through so much. Would you be able & willing to help me get my wife's SM J320ZN rooted so I can get the sd card used for apps? She doesn't need too much on there but the bloody thing goes to low memory way too soon. I'd love to know if I can get a better os on there too if you can make any suggestions.
I've got enough knowledge to be able to install lineageOS onto my crappy moto e & get that working ok but I'm still on the steep learning curve.
If you can, please provide a step-by-step guide to do this? I know you've said most of what needs to happen in your posts, but when I see "Once TWRP is installed and you've booted into TWRP recovery and you've formatted,..." I'm wondering what should get formatted, what shouldn't, etc
Warm regards
Hi guys,
So, this is a last resort. I've followed a number of different guides and methods, but nothing has worked. The closest "success" I've had is with a Chainfire auto root; it flashes, it breaks Knox, but I still don't have SU. Could it be because I don't have an SD card? I saw it as a prerequisite in some guide but didn't really put much stock in it as that was a single mention which also involved loading it with verity, which I'm more interested in removing.
I've also tried twrp, which that looked like it had bricked my device, though I managed to recover it by flashing the auto root again. I'm speculating that it's something to do with the latest updates, but really I'm just clueless and frazzled after 4+ hours of wracking my brains. I'm not sure what other info you'd find helpful anymore without going full splurge, so I'll keep it sweet and let you question me or berate me for my vile, witholding ways as you see fit. Any help is greatly appreciated!
Edit:
My SU checker says that I've not got the binaries or root user account. The .tar from firmware.mobi is only 54mb. I tried turning off suhide, but changed no other options. Trying to use fastboot straight up fails, the device isn't recognised after adb booting (despite having tried the correct drivers and some random others multiple times over.) I've been unable to locate a release for the T585 on twrp site, though a version is out there on these forums from a year or so back.
Smellfungus said:
Hi guys,
So, this is a last resort. I've followed a number of different guides and methods, but nothing has worked. The closest "success" I've had is with a Chainfire auto root; it flashes, it breaks Knox, but I still don't have SU. Could it be because I don't have an SD card? I saw it as a prerequisite in some guide but didn't really put much stock in it as that was a single mention which also involved loading it with verity, which I'm more interested in removing.
I've also tried twrp, which that looked like it had bricked my device, though I managed to recover it by flashing the auto root again. I'm speculating that it's something to do with the latest updates, but really I'm just clueless and frazzled after 4+ hours of wracking my brains. I'm not sure what other info you'd find helpful anymore without going full splurge, so I'll keep it sweet and let you question me or berate me for my vile, witholding ways as you see fit. Any help is greatly appreciated!
Edit:
My SU checker says that I've not got the binaries or root user account. The .tar from firmware.mobi is only 54mb. I tried turning off suhide, but changed no other options. Trying to use fastboot straight up fails, the device isn't recognised after adb booting (despite having tried the correct drivers and some random others multiple times over.) I've been unable to locate a release for the T585 on twrp site, though a version is out there on these forums from a year or so back.
Click to expand...
Click to collapse
The only way I know of to successfully root a Tab A is by flashing TWRP and then using it to flash SU or Magisk. What version of TWRP are you using and what version of Odin? Using the correct ones won't brick a T585.
When I got my Tab A a couple of weeks ago I did a LOT of reading first ... but then it took less than 24 hrs from receiving it to having it rooted + running RR Oreo
Following the guide HERE I enabled OEM Unlocking and installed Odin.
Using Odin I flashed twrp-3.2.3-4-gtaxllte-OMNI6.tar from HERE.
Using the freshly installed TWRP I flashed RR-O-v6.2.1-20181210-gtaxllte-Unofficial.zip from HERE, Gapps from HERE and the latest Magisk from HERE.
That was it - rooted and ready to go :victory:
The first guide pretty much covers all the steps you need, I simply used a different TWRP version. You can't brick your device flashing TWRP unless you flash something that's not for your device. Make SURE to enable OEM Unlock first - and don't use SuperSU but Magisk.
Good luck :fingers-crossed:
Nimueh said:
When I got my Tab A a couple of weeks ago I did a LOT of reading first ... but then it took less than 24 hrs from receiving it to having it rooted + running RR Oreo
Following the guide HERE I enabled OEM Unlocking and installed Odin.
Using Odin I flashed twrp-3.2.3-4-gtaxllte-OMNI6.tar from HERE.
Using the freshly installed TWRP I flashed RR-O-v6.2.1-20181210-gtaxllte-Unofficial.zip from HERE, Gapps from HERE and the latest Magisk from HERE.
That was it - rooted and ready to go :victory:
The first guide pretty much covers all the steps you need, I simply used a different TWRP version. You can't brick your device flashing TWRP unless you flash something that's not for your device. Make SURE to enable OEM Unlock first - and don't use SuperSU but Magisk.
Good luck :fingers-crossed:
Click to expand...
Click to collapse
I am about to try this.... was you device on Android 7 (nougat) or Android 8 (Oreo) when you did this?
Thanks for your time.
webzo said:
I am about to try this.... was you device on Android 7 (nougat) or Android 8 (Oreo) when you did this?
Thanks for your time.
Click to expand...
Click to collapse
I honestly don't remember
But it should work on either one - only difference now is that we have an official recovery that can be downloaded from twrp.me directly :highfive:
Nimueh said:
When I got my Tab A a couple of weeks ago I did a LOT of reading first ... but then it took less than 24 hrs from receiving it to having it rooted + running RR Oreo
Following the guide HERE I enabled OEM Unlocking and installed Odin.
Using Odin I flashed twrp-3.2.3-4-gtaxllte-OMNI6.tar from HERE.
Using the freshly installed TWRP I flashed RR-O-v6.2.1-20181210-gtaxllte-Unofficial.zip from HERE, Gapps from HERE and the latest Magisk from HERE.
That was it - rooted and ready to go :victory:
The first guide pretty much covers all the steps you need, I simply used a different TWRP version. You can't brick your device flashing TWRP unless you flash something that's not for your device. Make SURE to enable OEM Unlock first - and don't use SuperSU but Magisk.
Good luck :fingers-crossed:
Click to expand...
Click to collapse
Does this need twrp-3.2.3-4-gtaxllte-OMNI6.tar to go from Oreo to Pie?
I am not finding -OMNI.tar anywhere. All links are dead.
Can I use a newer version of TWRP?
Thanks.
webzo said:
Does this need twrp-3.2.3-4-gtaxllte-OMNI6.tar to go from Oreo to Pie?
I am not finding -OMNI.tar anywhere. All links are dead.
Can I use a newer version of TWRP?
Thanks.
Click to expand...
Click to collapse
Ok, so I went ahead and tried with the latest TWRP (3.3.1.1), RR (v7.0.2).
Everything seemed to go well..... except, tablet is now stuck in boot animation. It won't startup.
I double checked and I don't think I missed any steps.... Any ideas on what I can try?
Thanks.
webzo said:
Ok, so I went ahead and tried with the latest TWRP (3.3.1.1), RR (v7.0.2).
Everything seemed to go well..... except, tablet is now stuck in boot animation. It won't startup.
I double checked and I don't think I missed any steps.... Any ideas on what I can try?
Thanks.
Click to expand...
Click to collapse
Update:
I tried to restore the backup via TWRP and ended up with a "unable to mount /system" error.
My /system partition was showing zero size.
Many wipes and restores didn't help.
Eventually, what seemed to help was to choose repair the system partition, change file system to FAT, change file system back to ext4. Saw it in a youtube video- https://www.youtube.com/watch?v=T-7neHzSIvc
After /system error was fixed, I did an install of RR again and it went smooth.
All is well now.
Hope this helps someone.
webzo said:
Does this need twrp-3.2.3-4-gtaxllte-OMNI6.tar to go from Oreo to Pie?
I am not finding -OMNI.tar anywhere. All links are dead.
Can I use a newer version of TWRP?
Thanks.
Click to expand...
Click to collapse
Back then we had no working official version and the Omni6 one was the only one without issues. Now we have the official and it should work just fine.
No idea why you had those problems, but I'm glad you got it all sorted