Database Users

4.3 Update Question

Hi,
I've just received the 4.3 JB update notification and I need to know if it's ok to install it bcz my N7's bootloader is unlocked and in recovery mode I get the 'No Command' error. Please tell me if I should put the factory image first (I know, it's a guide but I don't have the link) and then update to 4.3. Also, I read here, on Nexus 7 forums that the 4.3 got some problems/errors after installing. Should I wait for 4.3.x JB or 5.0 KLP ?
Sent from my Nexus 7

bv31top said:
Hi,
I've just received the 4.3 JB update notification and I need to know if it's ok to install it bcz my N7's bootloader is unlocked and in recovery mode I get the 'No Command' error. Please tell me if I should put the factory image first (I know, it's a guide but I don't have the link) and then update to 4.3. Also, I read here, on Nexus 7 forums that the 4.3 got some problems/errors after installing. Should I wait for 4.3.x JB or 5.0 KLP ?
Sent from my Nexus 7
Click to expand...
Click to collapse
First, the "no command" does not prevent the access to the stock recovery. To go to the menu recovery press power and tap volume up.
Your update will still be installed.
Second, it is the safe way to keep the stock recovery - not re-installing the whole factory image - to get a smooth installation of JB 4.3.
Third, some issues are popping up. Some apps do not work, like MX Player, because the devs are still updating their apps for JB 4.3. It's matter of being patient, if such concept still exists in today world.
In addition if your Nexus 7 gets root you will lose it. No panic. You need to update SuperSu. Chainfire offered a temporary fix with the update version 1.43.This version is replaced as of today by version 1.51.

gunner1937 said:
First, the "no command" does not prevent the access to the stock recovery. To go to the menu recovery press power and tap volume up.
Your update will still be installed.
Second, it is the safe way to keep the stock recovery - not re-installing the whole factory image - to get a smooth installation of JB 4.3.
Third, some issues are popping up. Some apps do not work, like MX Player, because the devs are still updating their apps for JB 4.3. It's matter of being patient, if such concept still exists in today world.
In addition if your Nexus 7 gets root you will lose it. No panic. You need to update SuperSu. Chainfire offered a temporary fix with the update version 1.43.This version is replaced as of today by version 1.51.
Click to expand...
Click to collapse
Ok. I understood only the 3rd part.
I don't need root. I tried to acces the recovery mode after the fastboot menu and the result was no command error. I tried volume up + power (within the no command screen) and nothing. And you are wrong there bcz it's press, not tap.
I forgot to mention, I will use the stock 4.2.2 factory image to make it like 'out of the box'. I want to make it like a brand new unit, fresh pulled out of the box.
Sent from my Nexus 7 using xda app-developers app

bv31top said:
Ok. I understood only the 3rd part.
I don't need root. I tried to acces the recovery mode after the fastboot menu and the result was no command error. I tried volume up + power (within the no command screen) and nothing. And you are wrong there bcz it's press, not tap.
I forgot to mention, I will use the stock 4.2.2 factory image to make it like 'out of the box'. I want to make it like a brand new unit, fresh pulled out of the box.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Obviously I misunderstood your case and I do apologise for my mistake.
I wrongfully assumed that your tablet was unlocked and root.Therefore my mention of SuperSu was irrelevant in your case. And you do not have apps which need root to be used.
Since you are still stock including recovery I do not see why the update to JB 4.3 will not installed. In this case there is no need to access the recovery mode.
Depending of the definition of "tap", mine is a brief and quick press, I access the recovery menu by pressing power and then quickly and briefly pressing ( a tap) up volume to get in the recovery menu.
Hope you will get JB 4.3 without an issue

So, is it safe to flash the factory image and then update to 4.3? What is the chance of succes when using the following sticky? (in %)http://forum.xda-developers.com/showthread.php?t=1907796

bv31top said:
So, is it safe to flash the factory image and then update to 4.3? What is the chance of succes when using the following sticky? (in %)http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
That sticky is correct. Make sure that you flash boot BEFORE anything else though, and download the actual Android platform tools (i.e. don't cheat and look for just fastboot or adb). There seems to have been a recent update to fastboot that makes older versions play very badly with 4.3

Rirere said:
That sticky is correct. Make sure that you flash boot BEFORE anything else though, and download the actual Android platform tools (i.e. don't cheat and look for just fastboot or adb). There seems to have been a recent update to fastboot that makes older versions play very badly with 4.3
Click to expand...
Click to collapse
Umm... To flash 'boot'? About the cheating, if I follow the thread correctly it's ok, isn't it? I mean, if I download the latest SDK I'm safe, right?

Up

Please respond... I really need some help on this thing.

Yeah. I finally managed to acces the recovery mode using the power + volume up buttons in the "No Command" screen. I also succesfully locked the bootloader and the white padlock is gone. Right now, I touched on the install update notification and then on the 4.3 system update page I tapped on the "Reboot and Install button". It did the 10 sec countdown for restarting and now it says "Rebooting - 157.5 MB" but nothing happens.

"no command" boot loop
I too was able to enter the bootloader (unlocked) from the "No Command" bootloop by continuously holding down the power and volume down buttons (after about 5 rapidfire reboot attempts). From there I opened Nexus Root Toolkit (v1.7.8) and was able to flash 4.4.0 KRT16S using the button "Flash Stock + Unroot" (current status soft-bricked/Bootloop). Hope this helps with unbricking your device.

W806 (K18, K8 Round) ROM v1.0.3 (06/02/2016)

*ENHANCEMENTS*
Full proper root (still requires remount to edit root level files for added security)
init.d support
Internal Storage Cache tweaks
Governor tweaks
sysctl tweaks
Network tweaks
Dalvik tweaks
Memory usage tweaks
Ram tuning
Improved battery life
Busybox 1.24.1
Custom watchface support
Custom embedded faces (WIP, only one has been changed so far)
*REMOVED*
AdupsFota
AdupsFotaReboot
BasicDreams
Calender
DocumentsUI
FlappyBird
HTMLViewer
MTKLogger.apk
PrintSpooler
*ADDED*
SuperSU
AOSP Calendar
AOSP Email
AOSP Exchange support
Heads-Up Notifications
*Issues*
?? You tell me ???
NOT Issues
Lag and stutter on boot and for the first couple minutes after install. Because there is no source to build from, every core change has to be done by scripting. So that lag is network fixes, memory tweaks and other fixes being implemented.
Firmware Oddities
Weather on watchface vs the app/widget- The data on a watchface updates periodically while the app/widget requires you manually update it.
*Improvements and Changes pending*
Real "OK Google" everywhere support (/system space is the main limiting factor)
Further security checks
Theme fixing
DeODEXed build for themers (DeODEXed should not be a daily driver for average users)
ROM OTA service
Fixing the retina burning brightness level
*INSTRUCTIONS*
(How I write my instructions- If it's not listed, don't do it. If I don't mention it, it not worth thinking about. In short- Turn off brain, follow the steps.)
First time installers:
Extract the "K8 Round v1.0.3.zip" to your desktop
Download and extract the "K8 TWRP Recovery Files.zip" at the bottom of this post to the SP Tool's firmware folder
Turn the K8 on (doesn't matter if it's stock, stock with OTA, or rooted)
Connect the K8 to the computer
Turn on USB Storage on the K8 (check notifications if you don't get a popup)
Copy the folder from the "K8 Round v1.0.3.zip" to the K8 (you should see one folder, "TWRP")
Open SP Tool
Select the "K8_Round_Android_scatter" scatter
Hit the "Download" button
Turn off the K8 without disconnecting it from the computer
(SP Tool will flash TWRP)
Disconnect the K8 from the computer
Press and hold the lower button
Power on the K8
Keep pressing the lower button til TWRP boots
Wipe
"Restore" the backup
Reboot
Updating from previous release:
Extract the "K8 Round v1.0.3.zip" to your desktop
Turn the K8 on (doesn't matter if it's stock, stock with OTA, or rooted)
Connect the K8 to the computer
Turn on USB Storage on the K8 (check notifications if you don't get a popup)
Copy the folder from the "K8 Round v1.0.3.zip" to the K8 (you should see one folder, "TWRP")
Disconnect the K8 from the computer
Power off the K8
Press and hold the lower button
Power on the K8
Keep pressing the lower button til TWRP boots
Wipe
"Restore" the backup
Reboot
Credits:
@cyrux75 (TWRP build)
@pogodancer (edited scatter for TWRP only install)
@pablo11 (community and thread help)
You (for donations to help get this on the roll)

Change log
Change Log
v1.0.0
Initial Release
v1.0.1
Fixes
Fixed data issue
Fixed Weather app issue (adware and malware hosts list blocked the server)
Removed Open Mic+
Changes
Adjusted CPU Governor to step up at 90% load vs the previous 98% (battery life impact is to be expected)
Added Heads-Up Notifications
Additional network and memory tweaks
Added "Wear" boot animation for the lulz
Updated Busybox to 1.24.1
v1.0.2
Fixes
Fixed the poor battery life due to 90% load clock up
Changes
Adjusted CPU Governor to step up at 95% load vs the previous 90%
Adjusted CPU Governor power save bias from 150 to 250
Minor tuning busybox install
v1.0.3
Fixes
Rebuilt for stock to eliminate possible flashing issues. (flashed multiple times before uploading)
Changes
None

This one too!

This is just for k8 right? Mini and D5 is not supported?
Enviado desde mi Letv X500 mediante Tapatalk

great job as always!

negriton said:
This is just for k8 right? Mini and D5 is not supported?
Enviado desde mi Letv X500 mediante Tapatalk
Click to expand...
Click to collapse
That's right. Main reasons are there is no functional TWRP for the D5/Mini right now, merging takes a little time, and per my agreement with the K8 Round folks they get release priority. Now I do have an SP Tools flashable build for the D5/Mini, with all the same changes (and issues), that I'll upload later.

looking forward to Mini's and D5's updates. Nevertheless I take a sit to see how is going this update.
Thanks for your hard work!

Lokifish Marz said:
*ENHANCEMENTS*
Full proper root (still requires remount to edit root level files for added security)
adware and malware hosts list
init.d support
Internal Storage Cache tweaks
Governor tweaks
sysctl tweaks
Network tweaks
Dalvik tweaks
Memory usage tweaks
Ram tuning
Improved battery life
Custom watchface support
*REMOVED*
AdupsFota
HTMLViewer
Basic Daydreams
FotaProvider
MTK Logger
*REPLACED*
K18 launcher replaced with D5 launcher (adds custom watchface support)
*ADDED*
4.4 Open Gapps (pico)
SuperSU
Root Browser
Open Mic (adds "OK Google" support everywhere)
*Issues*
Stock Weather app and widget will not update
?? You tell me ???
*Improvements and Changes pending*
build.prop tweaks
Getting the stupid weather app to work (this is a carry over from the D5/Mini)
Assigning a function to the third button (menu maybe)
Fine tuning
Real "OK Google" everywhere support
Further security checks
AOSP Browser, Calendar, email (maybe)
Theme fixing
Custom boot logo and animation
DeODEXed build for themers (DeODEXed should not be a daily driver for average users)
*INSTRUCTIONS*
Extract zip
Copy contents to internal storage (TWRP and Clockskin folders)
Flash TWRP using SP Tools
Reboot into recovery after flashing (the two lower buttons)
Wipe
Install backup
Reboot
Enjoy
Credits:
@cyrux75 (TWRP build)
@pogodancer (edited scatter for TWRP only install)
@pablo11 (community and thread help)
You (for donations to help get this on the roll)
Click to expand...
Click to collapse
@ lokifish marz, thanks for your work! I would like to ask you if you used the original base band of the k8 or if you changeg it. I am asking because i am experiencig some issue with poor signal using stock ROM.
Tnx

A costume ROM - Nice one!
I am a bit confused, how to install this ROM.
My K8 is stock, without root and with the latest OTA-Update.
Do I have to root my watch first or can I use the SP-Flash tool, like in the attached picture. This doesn't work for me.
MTK Droid Tools shows me:
"ATTENTION! File /system/recovery-from-boot.p which restore factory recovery in case of phone switching on in a normal mode Is Found! "

...this is why we can't get twrp on watch with actually update . Recovery will always change to orginal recovery at start. Or flash more than recovery with SPFlashTools ... but don't do it if you don't know what you do ! ☺

Do I have to install an older stock firmware? Thanks
rockabilly said:
...this is why we can't get twrp on watch with actually update . Recovery will always change to orginal recovery at start. Or flash more than recovery with SPFlashTools ... but don't do it if you don't know what you do !
Click to expand...
Click to collapse

My watch is on the latest OTA and does not boot from custom recovery.
Please wait for confirmation from the thread owner about this procedure !!
Personally - to get around this I will copy the new image from @Lokifish Marz on to SD storage and then flash only the original UBOOT.img (from the stock read-back files linked in the K8 round thread) and the TWRP - recovery.img.
However - I am NOT recommending this approach for everybody as I have not confirmed it yet and @Lokifish Marz may have other ideas about how to flash this rom for users on the latest OTA who cannot boot from custom recovery.
It should work but as I say - but I have not tried it yet.
I would be happy for any comments/feedback about this.

I would root the watch, then use mobileuncle to boot into recovery, then just install everything included above. Easy as that . I hope hahahahahha

cosmospho said:
I would root the watch, then use mobileuncle to boot into recovery, then just install everything included above. Easy as that . I hope hahahahahha
Click to expand...
Click to collapse
Rooting the watch will be an unnecessary challenge - just the way I feel about it....

OK, the installation method is exactly as I listed it. I'll break it down even further in the OP.
I have flashed the ROM multiple times with the OTA, without the OTA, rooted and unrooted. It worked every single time. Why does it work? Because TWRP only gets replaced after the device boots into Android if you accepted the OTA. Why? Because the device has to boot to Android to read the script that replaces custom recovery with stock. So if the script is there, TWRP is still there until you see a watchface when booting the device.
@cosmospho - don't waste your time. Rooting properly, and safely, can only be done by flashing SuperSU in TWRP.

ok so I have the device rooted with kingroot from the past, should I just go back to stock and then TWRP and your rom. Would that be the best way, or since I already have Root with Kingroot can I just boot into recovery and go from there ?
Thanks.

cosmospho said:
ok so I have the device rooted with kingroot from the past, should I just go back to stock and then TWRP and your rom. Would that be the best way, or since I already have Root with Kingroot can I just boot into recovery and go from there ?
Thanks.
Click to expand...
Click to collapse
From the OP;
Lokifish Marz said:
(doesn't matter if it's stock, stock with OTA, or rooted)
Click to expand...
Click to collapse

Thanks @Lokifish Marz
I flashed TWRP on mine and it refused to boot into recovery, even on first boot.
That's the only reason I posted what I said previously.
I'll try again later.
Cheers.

pablo11 said:
Thanks @Lokifish Marz
I flashed TWRP on mine and it refused to boot into recovery, even on first boot.
That's the only reason I posted what I said previously.
I'll try again later.
Cheers.
Click to expand...
Click to collapse
Odd. I know I had to get the button press right to get it to work. The only one that worked consistently was to press and hold both the middle and lower buttons to turn it on, then to continue holding down the lower button until TWRP booted.

Same problem on my watch. I thought, that I am to stupid to press a button.
My watch just simple makes a normal boot.
Fastboot (Upper button) works.
pablo11 said:
Thanks @Lokifish Marz
I flashed TWRP on mine and it refused to boot into recovery, even on first boot.
That's the only reason I posted what I said previously.
I'll try again later.
Cheers.
Click to expand...
Click to collapse

Stock ROMs Factory v6.1 , v8.3 , v8.4 , v8.5 , v8.7, V9.0, V9.2-patch : v21

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.

Nvidia Shield TV Pro 2015 stuck at nvidia logo / any OTA public*.zip file available?

Hi all,
My Shield TV Pro 2015 unit is stuck at the nvidia logo although I can get to bootloader via hardware method and even fastboot boot twrp. I have followed all nvidia recover tutorials with several versions of Recovery OS image, but nothing seems to work.
From all (the many) threads I have read, it seems that it is possible to "unbrick" the unit by flashing an OTA update public*.zip with twrp. This is the only method I have not tried because I cannot find an appropriate version for 2015 PRO version.
There are some versions online (privately uploaded), but refer to other models like here and here and here.
Have I missed the file somehow or is there anyone that could share this version? Even maybe someone that could share your ideas on how to unblock the unit?
Many thanks in advance for all the possible help,
Carlos

Hello again
I just want to update my own post and at the same time again ask for some help.
So far nobody has stepped forward with a PUBLIC*.zip file download link for the Shield 2015 PRO model (codename foster just like the 2015 16GB model - +1 for confusion master to Nvidia on model release naming) but... I found a hosted file today (it has been freshly uploaded on the 12th/06)) on androidfilehost.com named PUBLIC604eab3c209a3f6146de7e1b8b1ff6c3_foster_e.zip posted by a user named linux4all.
It might be the one... or not. Is there a guru that could point to a file inside these OTA PUBLIC*.zip files that might have some more detailed info about the version that it was built for? The best I could get was this text inside the updater-script:
Code:
getprop("ro.product.device") == "foster" || abort("E3004: This package is for \"foster\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Target: NVIDIA/foster_e/foster:8.0.0/OPR6.170623.010/3019194_1155.5338:user/release-keys");
No doubt it's for a Foster device, but which one?
Anyone out there (that means you too "linux4all") that could add a bit more info to my already too long babble?
Thanks in advance!

guardiman said:
Have I missed the file somehow or is there anyone that could share this version? Even maybe someone that could share your ideas on how to unblock the unit?
Click to expand...
Click to collapse
If I understand you correctly you have access to fastboot.
Then why not just register with the Nvidia developer program and download from there:
https://developer.nvidia.com/gameworksdownload
There you can pick any version you'd like to install, they've even got the new 7.0.1 developer images. That would be pre-rooted developer images, but if you install something like 6.0 you can then just follow the normal OTA upgrade path after that.

andersh said:
If I understand you correctly you have access to fastboot.
Then why not just register with the Nvidia developer program and download from there:
https://developer.nvidia.com/gameworksdownload
There you can pick any version you'd like to install, they've even got the new 7.0.1 developer images. That would be pre-rooted developer images, but if you install something like 6.0 you can then just follow the normal OTA upgrade path after that.
Click to expand...
Click to collapse
+1. You can just download a rooted image. Takes just a few minutes to register as a developer.

dk1keith said:
+1. You can just download a rooted image. Takes just a few minutes to register as a developer.
Click to expand...
Click to collapse
Thanks for your help and suggestions.
As I had previously described, I already tried all of this before. I am registered as a developer, I downloaded all the images (recoveryOS and developerOS) for my model (Nvidia Shield 2015 Pro), I followed the restore procedure using fastboot method, the console outputs OKs all the way through the restore procedure and at the end (I understand that it means it has succeeded restoring) but when I reboot the unit nothing has changed (still green nvidia logo, still stuck).
So, as an alternative, I want to try and use the TWRP method that seems to have worked at unblocking units stuck like mine, check this post by pendragon666 https://forum.xda-developers.com/showpost.php?p=72655717&postcount=3.
But this method requires the OTA zip (they are not available for download from nvidia - if I'm wrong, please, link me to my blindness )
Why is it that TWRP only works with OTA zips? I don't know. But from comparing the two zip files, recoveryOS zip and OTA PUBLIC*.zip, the former is like a small number of image files, plus some scripts but no subfolders (if you download the zip from nvidia and open it you can confirm this), whereas the latter his a zip with many subfolders and files than can be read and applied by TWRP as a zip install.
If I can get to confirm that this OTA PUBLIC.*zip file is for my unit (foster pro) I will try to install it with TWRP and see if it works.
I hope it is clearer now.

andersh said:
If I understand you correctly you have access to fastboot.
Then why not just register with the Nvidia developer program and download from there:
https://developer.nvidia.com/gameworksdownload
There you can pick any version you'd like to install, they've even got the new 7.0.1 developer images. That would be pre-rooted developer images, but if you install something like 6.0 you can then just follow the normal OTA upgrade path after that.
Click to expand...
Click to collapse
Yes, I do. Already did download all images but the process produces zero effect, although it finishes successfully. I tried every single recoveryOS and developerOS image but nothing worked...

guardiman said:
Yes, I do. Already did download all images but the process produces zero effect, although it finishes successfully. I tried every single recoveryOS and developerOS image but nothing worked...
Click to expand...
Click to collapse
Just to add a bit more info I digged from the recovery.log after flashbooting twrp on my Shield Pro 2015:
Code:
ro.build.fingerprint=NVIDIA/foster_e_hdd/foster:7.0/NRD90M/1915764_910.7870:user/release-keys
ro.product.name=foster_e_hdd
ro.product.brand=NVIDIA
ro.product.model=SHIELD Android TV
ro.product.device=foster
ro.product.manufacturer=NVIDIA
ro.hardware=foster_e_hdd
In the OTA zip I saw no reference to "foster_e_hdd" and this might proof of mismatch... or not

guardiman said:
Hi all,
My Shield TV Pro 2015 unit is stuck at the nvidia logo although I can get to bootloader via hardware method and even fastboot boot twrp. I have followed all nvidia recover tutorials with several versions of Recovery OS image, but nothing seems to work.
From all (the many) threads I have read, it seems that it is possible to "unbrick" the unit by flashing an OTA update public*.zip with twrp. This is the only method I have not tried because I cannot find an appropriate version for 2015 PRO version.
There are some versions online (privately uploaded), but refer to other models like here and here and here.
Have I missed the file somehow or is there anyone that could share this version? Even maybe someone that could share your ideas on how to unblock the unit?
Many thanks in advance for all the possible help,
Carlos
Click to expand...
Click to collapse
I wanted to downgrade from 7.01 to 6.3. I flashed 6.3 developer image pro via flashfire, flash went well but then when rebooted stuck at splash screen. Plugged in laptop and went back to bootloader hit factory reset and 3 hours later all went well

jionny said:
I wanted to downgrade from 7.01 to 6.3. I flashed 6.3 developer image pro via flashfire, flash went well but then when rebooted stuck at splash screen. Plugged in laptop and went back to bootloader hit factory reset and 3 hours later all went well
Click to expand...
Click to collapse
You mean factory reset inside TWRP or nvidia recovery?

guardiman said:
You mean factory reset inside TWRP or nvidia recovery?
Click to expand...
Click to collapse
inside nvidia shield recovery

jionny said:
inside nvidia shield recovery
Click to expand...
Click to collapse
you mean "force recovery" (last option at the bottom)? There is no factory reset in my nvidia recovery menus (chosing recovery gives a "no command" output and force recovery makes the screen go blank until you unplug it from power.

guardiman said:
you mean "force recovery" (last option at the bottom)? There is no factory reset in my nvidia recovery menus (chosing recovery gives a "no command" output and force recovery makes the screen go blank until you unplug it from power.
Click to expand...
Click to collapse
no not force recovery.... follow these directions http://nvidia.custhelp.com/app/answ...hen-you-are-unable-to-access-android-settings

jionny said:
no not force recovery.... follow these directions http://nvidia.custhelp.com/app/answ...hen-you-are-unable-to-access-android-settings
Click to expand...
Click to collapse
Unfortunately the "boot recovery" option after selected just ends with a black screen and a "no command" message written in white letters in the middle of the screen (no dead android robot)
I got here:
8. You may see the dead Android robot on screen. This is expected behavior.
But no robot

guardiman said:
Unfortunately the "boot recovery" option after selected just ends with a black screen and a "no command" message written in white letters in the middle of the screen (no dead android robot)
Click to expand...
Click to collapse
that is normal just keep trying I had to go through it at last 3-4 times before it took, as long as it says no command follow the instructions

jionny said:
that is normal just keep trying I had to go through it at last 3-4 times before it took, as long as it says no command follow the instructions
Click to expand...
Click to collapse
Managed further to the menu (it was just of question of proper pressing and seconds) let's see what comes now...
Wiping data...

guardiman said:
Managed further to the menu let's see what comes
Wiping...
Click to expand...
Click to collapse
be patient it takes about 3 hours

jionny said:
be patient it takes about 3 hours
Click to expand...
Click to collapse
finally some progress after weeks of waiting... 3 hours is just around the corner
a certainly well deserved thanks for you, sir

guardiman said:
finally some progress after weeks of waiting... 3 hours is just around the corner
a certainly well deserved thanks for you, sir
Click to expand...
Click to collapse
You are welcome, glad I could help.

jionny said:
You are welcome, glad I could help.
Click to expand...
Click to collapse
Well, wipe finished, reboot and.... nvidia logo (same ol' same)
I forgot to say that I had already performed the "fastboot oem unlock" which is said to factory reset the shield. Although the unlock finished successfully the Shield did not boot.
Back to the drawing board....
Any more suggestions? Anyone?

guardiman said:
Well, wipe finished, reboot and.... nvidia logo (same ol' same)
I forgot to say that I had already performed the "fastboot oem unlock" which is said to factory reset the shield. Although the unlock finished successfully the Shield did not boot.
Back to the drawing board....
Any more suggestions? Anyone?
Click to expand...
Click to collapse
What version are you on and did you flash anything and then get stuck on the logo screen?

Newbie-friendly: TWRP and Root for Samsung S3 Tablet

Tested SM-T820, for Android O. It is reported that it works for Android P as well, with small modification (see below).
This post is designed to gather information found across this forum to give a step-by-step guide for obtaining a custom recovery TWRP and Root (via Magisk) for the Samsung S3 tablets running Android O. This process works if you are upgrading or staying with Oreo. [If you wish to run Android N, there is a slightly different process.] This process will wipe the contents of the tablet, so make backups as appropriate.
Credit to the software authors, original post creators (especially ashxy) and all those who contributed to the discussions to clarify all the issues. Most of the specifics below were hammered out in https://forum.xda-developers.com/ga...recovery-twrp-3-1-0-1-samsung-galaxy-t3581359.
WARNING Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on. You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering. [credit: jcadduono]
The below instructions are for Android O (Oreo). User BenG7 reports (I have not verified) that the same process, with slight modification, will work for Android P (Pie). See posts #38 and #39 for those modified instructions.
1. DOWNLOAD
a. ODIN​https://samsungodin.com/ (I used 3.13.1)​b. Samsung USB Drivers​https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows​c. Original firmware​Search for SM-T820 and download latest version 8.X at http://updato.com/firmware-archive-select-model​d. TWRP​At some point, it will likely find an official version at https://twrp.me/Devices/. For now, grab the latest beta version at https://forum.xda-developers.com/ga...recovery-twrp-3-1-0-1-samsung-galaxy-t3581359​e. Magisk​Get the latest stable Magisk version from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445​f. Ashxy's oreo encryption disabler https://androidfilehost.com/?fid=890278863836288163​​
2. PREPERATION
a. While running your tablet in Android, go to Settings -> About device. Tap 7 times on Build number to enable Developer options. [credit: jcadduono]​b. Now go to Settings -> Developer options. You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on. Do not ever turn off Developer Options or OEM unlock. Doing so will cause your device to refuse to boot and require a full factory restore. [credit: jcadduono]​c. Turn off your tablet.​d. Get a micro SD card​e. Copy Magisk and oreo encryption disabler onto microSD card​f. Install microSD card into Tablet​g. Install Samsung USB Drivers on Windows machine​h. Unzip ODIN (1a) and Original firmware (1c) on your Windows computer​i. While tablet is off, plug in usb cable between tablet and Windows computer​​3. REFLASH ORIGINAL FIRMWARE (Optional if your tablet is already running Oreo)
a. Enter Download mode, press and hold Home, Down Vol, and Power until you see the Warning screen of the downloader mode. Press Vol up to continue​b. Open up ODIN, confirm that ODIN can see your tablet. We will fill in three files for flashing. Click AP button on Odin. In popup, select AP_[blah blah].tar.md5 (whatever AP file you downloaded in step 1c). After selecting the file, Odin will check the signature of the file you downloaded and appear to freeze up. Let it finish, and it will report: <OSM> Checking MD5 finished Sucessfully.. <OSM> Leave CS.. In a similar way, fill in the BL and the CSC files. As these are much smaller, the signature checks will go much faster. [Use the CSC file, not the HOME_CSC file, in the CSC slot. This will completely erase your data on the tablet, which minimizes the likelihood of future problems. You will be erasing all of the /data partition later, so there is no point in saving your data now by using the HOME_CSC file.]​c. Make sure that in the options, Auto Reboot is selected. Then click Start. The screen of the tablet should show a progress bar as your tablet is being restored to its original firmware.​d. At this point, your tablet will reboot into the default recovery mode, with a full blue screen and an android figure with the spinning arrows. The tablet will then self reboot again (perhaps more than once). After a while, you will be greeted with the Welcome screen where you can select your language. Be patient.​e. Power off the tablet using the power button​​4. FLASH TWRP
a. Enter Download mode (press and hold Home, Down Vol, and Power) until you see the Warning screen of the downloader mode. Press Vol up to continue​b. (Re) Open up ODIN, confirm that ODIN can see your tablet,​c. Important We do not want the tablet to automatically reboot after installing TWRP. If the tablet does reboot into Android before completing the steps in Section 4 and 5, there is a good chance the stock recovery will overwrite TWRP. So click the Options tab on the left and deselect Auto Reboot. After doing that, click the Log tab so you can monitor progress​d. Click AP button on Odin. In popup, select twrp-[blah blah].img.tar (downloaded in step 1d), but make sure that the BL and CSC slots are unchecked, i.e. we will only be flashing an AP file this time. Then click Start. You will see the progress bar on your tablet. Watch the log window of Odin and wait for the message "<OSM> All threads completed. (succeed 1 / failed 0)"​​5. ENTER TWRP AND CONFIGURE
a. At this point, from the last section, you should still be in Download mode on the tablet. It is important that, after flashing TWRP, to go straight to TWRP without letting the Android System reboot. To do this, Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] (while still holding [Home] + [Power]) when the screen blanks. [credit: jcadduono]​b. In a few secs, you will see the TWRP first screen, you can let go of all the buttons.​c. If you don't see then TWRP boot splash try again from the start of 4. FLASH TWRP.​d. Swipe to Allow Modifications. (For some reason, TWRP has some issues with the touchscreen for some tablets. If you experience this, expect to make several swipes or taps until it properly registers. You have succeeded when you see the classic 8-button main screen of TWRP.)​e. Click Wipe then Format Data (do not just Wipe data), type yes and let it complete. Then click back until you get to the 8-button main screen of TWRP.​f. Click the Mount button. Select Storage button, and confirm that the Internal Storage shows non-zero MB. If it is, you know that the /data partition is now mounted properly. However, since we put the needed install files on the microSD, go ahead and select Micro SD Card as our storage. Click Back until you are back at the 8-button main screen.​g. Click the Install button, install the Magisk zip file you downloaded in step 1e and copied to your microSD. Once finished, click Back to get back to the install screen (do not reboot yet).​h. Install the oreo encryption disabler zip file from step 1f. When it completes, you can press the Reboot System button and let your tablet reboot into Android. You can also disconnect the usb cable connecting the tablet from the computer. The tablet may reboot itself once or twice, let it do its thing, and eventually you will see the Samsung Welcome! Screen, where you can select your language.​​6. CONFIRM DATA ACCESS IN TWRP
a. Before going into configuring your tablet, go ahead and turn off the tablet and re-enter TWRP (Home, Vol up, Power).​b. *Important* Since you will not be changing your system partition, this time, when you get to the "Keep System Read only?" screen, click the Keep Read Only button.​c. In the 8-button screen of TWRP, click Mount, click Select Storage. Confirm that the Internal Storage is greater than zero MB. If it is, congratulations, you have TWRP installed with /data mounted.​d. Reboot to System​​7. FUTURE USE OF TWRP
a. Unless you are planning to make changes to the System, continue to choose the Read Only System when you return to TWRP.​B. [NOT YET TESTED]If you need to make changes to System, e.g. flash a new ROM, go back to Step 5 and install the ROM just before Step 5g​​
8. Click the Thanks button if my guide helped you.

Good guide. In 5, a, at least for the t-820 and if assume other variants, you can hold power, vol up, and home until it boots to recovery. You don't need to hold the keys to boot the bootloader and then quickly switch to the vol up. It's a little easier for me to do it that way.
Sent from my [device_name] using XDA-Developers Legacy app

Good guide and HNY!
klaberte said:
7. FUTURE USE OF TWRP
.....
B. [NOT YET TESTED]If you need to make changes to System, e.g. flash a new ROM, go back to Step 5 and install the ROM just before Step 5h
Click to expand...
Click to collapse
I would flash magisk *after* flashing a new ROM, i.e. install the ROM just before Step 5g.
Btw, I installed TWEAKED for T820 by @rorymc928 which comes already with encryption disabler.

Great guide!
But, anyway to install SuperSU instead of Magisk?

Frunktz said:
Great guide!
But, anyway to install SuperSU instead of Magisk?
Click to expand...
Click to collapse
I'd ask over here: https://forum.xda-developers.com/ga...recovery-twrp-3-1-0-1-samsung-galaxy-t3581359

klaberte said:
I'd ask over here: https://forum.xda-developers.com/ga...recovery-twrp-3-1-0-1-samsung-galaxy-t3581359
Click to expand...
Click to collapse
Already asked but it SEEMS not possible because SuperSu was discountinued. But somebody has successfully installed it on Oreo 8.

I am new to rooting my Tab s3 so pardon me if any of my questions are redundant. I will be following the directions from post "Newbie-friendly: TWRP and Root for Samsung S3 Tablet". Can someone please confirm the following for me before I root -
1. I am running on the most recent firmware T820XXU2BRL1, do I need to complete process #3 REFLASH ORIGINAL FIRMWARE?
2. After I complete root process will my Tab s3 automatically be set to recognize SD Card as internal storage or will I need to complete another setting or process? This is my main reason to rooting.
3. Second reason is to remove bloatware. Does anyone know of a post advising which bloatware on Tab s3 to remove safely and which ones to leave alone?
4. After completing root process following directions from post "Newbie-friendly: TWRP and Root for Samsung S3 Tablet" has anyone experienced any Tab s3 functions or app not working properly? Is USB-OTG working?

my Tab S3 delivered today and followed ur guide and did in first try! send Thanks!

Great post. Im having an issue. With my tab s3. Yesterday i was updating magisk manager and after i did it stopped charging. I thought my charger came unplugged but it didnt. Now the only way i can charge it is to put it in twrp and let it charge. But its unresponsive when its powered on and when its off it just loops the charging screen. But wont charge. I jave tried to revert back to a previous back up but had no luck. I was plannig on flashing stock firmware when i get back to my computer.. but any input would be greatly appreciated..
Sent from my SM-N960U using Tapatalk

cdeitrich00 said:
Great post. Im having an issue. With my tab s3. Yesterday i was updating magisk manager and after i did it stopped charging. I thought my charger came unplugged but it didnt. Now the only way i can charge it is to put it in twrp and let it charge. But its unresponsive when its powered on and when its off it just loops the charging screen. But wont charge. I jave tried to revert back to a previous back up but had no luck. I was plannig on flashing stock firmware when i get back to my computer.. but any input would be greatly appreciated..
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
I don't know why your tab won't charge. Updating magisk should be totally unrelated to charging. Did you have any magisk modules that would have modified charging parameters?

jd1639 said:
I don't know why your tab won't charge. Updating magisk should be totally unrelated to charging. Did you have any magisk modules that would have modified charging parameters?
Click to expand...
Click to collapse
I had the sony framework module installed for ps4 remote play. But that was it. I cant figure it out.
Sent from my SM-N960U using Tapatalk

jd1639 said:
I don't know why your tab won't charge. Updating magisk should be totally unrelated to charging. Did you have any magisk modules that would have modified charging parameters?
Click to expand...
Click to collapse
https://r.tapatalk.com/shareLink?ur...share_tid=3641443&share_fid=3793&share_type=t
This was my issue. I love this forum.
Sent from my SM-N960U using Tapatalk

Quick question. I'm already on the latest firmware, my bootloader is unlocked so can I just run Odin, flash twrp and then any pre-rooted Rom? Or do I need to follow all these steps? It's been awhile since I've flashed anything and just want to make its done properly. TIA

after rooting, the secure folder works or not

jawalexander said:
after rooting, the secure folder works or not
Click to expand...
Click to collapse
That's correct.

Is that the only drawback?

On reboot I got: Verification Failed, Unable to restart your device. The Integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data.
Now what?
UPDATE: Oh I see, I totally skipped e. "Click Wipe then Format Data". Now it's fixed and working properly. Now to remove some bloatware.
David C.

I posted something silly before. Deleted.

THANKS ! Works also for Android PIE
Hi,
thanks,
I did a clean install of Android Pie for my Samsung Galaxy Tab S3, SM-T825.
Altough not yet officially available for my country, I downloaded the version for the Netherlands (PHN-T825XXU3CSH9-20190909091851) from the SamFrew-site [https://samfrew.com/nl/download/Galaxy__Tab__S3__/evss/PHN/T825XXU3CSH9/T825PHN3CSH8/[/URL] . As one can anyway customize languages, etc., no problem.
Then I followed your guide step by step.
I added BusyBox, latest version from XDA developers []https://forum.xda-developers.com/showthread.php?t=1929852 as last step, in 5. g
Altough written for OREO, all this steps work perfectly well on my Android PIE !
Including the use of the Ashxy's oreo encryption disabler of point 1.f
(I didn't find a similar disabler for Android Pie yet... Someone a better idea ?)
Rootchecker confirms that I have Root access and that BusyBox is indeed installed.
Thanks very much - great help !
baudi

baudi said:
Hi,
thanks,
I did a clean install of Android Pie for my Samsung Galaxy Tab S3, SM-T825.
Altough not yet officially available for my country, I downloaded the version for the Netherlands (PHN-T825XXU3CSH9-20190909091851) from the SamFrew-site [https://samfrew.com/nl/download/Galaxy__Tab__S3__/evss/PHN/T825XXU3CSH9/T825PHN3CSH8/[/URL] . As one can anyway customize languages, etc., no problem.
Then I followed your guide step by step.
I added BusyBox, latest version from XDA developers []https://forum.xda-developers.com/showthread.php?t=1929852 as last step, in 5. g
Altough written for OREO, all this steps work perfectly well on my Android PIE !
Including the use of the Ashxy's oreo encryption disabler of point 1.f
(I didn't find a similar disabler for Android Pie yet... Someone a better idea ?)
Rootchecker confirms that I have Root access and that BusyBox is indeed installed.
Thanks very much - great help !
baudi
Click to expand...
Click to collapse
Thanks for the update! Just wondering, why did you add busybox and XDA developers at the end of step 5g? XDA developers could have been installed as a standard app once the tablet is up and running, no?
Why manually installing BusyBox at this point of the setup?