Android 5.1 out now - Shield Tablet General

Downloads now Available
Full rom for wifi variant
http://ota.nvidia.com/ota/data/post...d-signed-wx_na_wf-full_ota-32256_546.1774.zip
Full rom for LTE variant
http://ota.nvidia.com/ota/data/post...d-signed-wx_na_do-full_ota-32256_546.1774.zip
Instructions :
Have a custom recovery installed preferably TWRP here:https://docs.google.com/file/d/0B3qCG4HlT_xFY0R3RFIxV0YzZTg/edit?usp=docslist_api
Flash full rom image from above
Then supersu for root here: http://download.chainfire.eu/supersu
The install flashify app from here to reinstall TWRP IMG as it rewrites upon flashing firmware https://play.google.com/store/apps/...app&pcampaignid=APPU_1_HrtfVbPRFsvT7AaC84DoAQ
Changeling for 3.0 lollipop 5.1

Yep. Seeing it on my rooted ST. Has anyone found the full update for US LTE yet?

I've just downloaded it. I'll test it tomorrow!

Just got the notification but wont install on twrp so need full ROM to flash

Ok, I have it installed now. I can't say anything about speed yet, but the controller connected pretty fast and updated itself

Just popped up, but I'm rooted with unlocked bl, so waiting for the right version.

Can anyone that's installed it post the build number?
Sent from my SHIELD Tablet using XDA Free mobile app

Installed and first tests are positive. Need more testing though nut will be for tomorrow. Nice birthday present ? !
Sent from my SHIELD Tablet using XDA Free mobile app
---------- Post added at 11:19 PM ---------- Previous post was at 11:05 PM ----------
Here i have LMY47H.32256_546.1774
Sent from my SHIELD Tablet using XDA Free mobile app

I tried downloading Full OTA by replacing build number in link, but it seems its down...

What did you try?

Here's the OTA link since nobody posted it yet:
http://ota.nvidia.com/ota/data/post...ota-from-29979_515.3274-to-32256_546.1774.zip
(For the record, that's for the wireless version)
Anybody remember what was the link format for the full ROMs?
Edit: Never mind.
This should be the full ROM for wireless version:
http://ota.nvidia.com/ota/data/post...d-signed-wx_na_wf-full_ota-32256_546.1774.zip

OM*G just this afernoon i rooted my shield with kingroot andere ofcourse OTA fails .. Grmbl
Sent from my Nexus 5 using XDA Free mobile app

If you're currently rooted, the FULL version is what you'll need to flash in your custom recovery (TWRP, CWM, Phils) - don't forget to ALSO re-flash the latest stable SuperSU.zip in recovery AFTER flashing the full ota .zip and BEFORE rebooting if you want to keep root!
This is the FULL rom for the 16GB Wi-Fi model (says NA, but it's the same for all Wi-Fi models worldwide):
http://ota.nvidia.com/ota/data/post...d-signed-wx_na_wf-full_ota-32256_546.1774.zip
I've downloaded and successfully updated...(755MB). FWIW, my TWRP custom recovery survived the update.
Link to the 32GB LTE model for North America has been updated in the OP above.
32GB LTE ROW (Rest Of World) version is:
http://ota.nvidia.com/ota/data/post...d-signed-wx_un_do-full_ota-32256_546.1774.zip
Sent from my SHIELD Tablet using XDA Free mobile app

An Droid said:
This may be the full rom for North America Wi-Fi:
http://ota.nvidia.com/ota/data/post...d-signed-wx_na_wf-full_ota-32256_546.1774.zip
Downloading now, so can't confirm...
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
I ninja edited at the same time
It's also still downloading for me (relatively slow speed), but judging by the size it should be the correct file.

Didn't flash for me. In twrp

gavin-phelan said:
Didn't flash for me. In twrp
Click to expand...
Click to collapse
I'm guessing you flashed the OTA not full ROM (because there's no way you've already downloaded it), and probably over a rooted system, right?

Sorry your right lol downloading full ROM now

Replacing wf with do seems to get the LTE NA version. Downloading now and will give it a try.
http://ota.nvidia.com/ota/data/post...d-signed-wx_na_do-full_ota-32256_546.1774.zip
Finished flashing. Works perfectly.

An Droid said:
This may be the full rom for North America Wi-Fi (if you're rooted, this is the version you'll need to flash in recovery - don't forget to re-flash SuperSU in recovery after flashing the .zip and before rebooting if you want to keep root):
Downloading now, so can't confirm...(755MB)
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the link! Wish they had a faster server (going between 350-450KBps).
I only rooted after the last update, so let me make sure I have this straight. Flashing this from CWM should update my Shield just like the OTA update would done the way nVidia intended it right (i.e. leave my data and apps in tact)? It's my understanding it will leave the bootloader unlocked but otherwise remove everything that made my phone rooted (CWM and SuperSU). If I didn't reflash the recovery or SuperSU right away, I could do it later, right?

full ota for wifi US flashes fine inTWRP booting now.
Thanks for the links buds

Related

Pure AOSP for Locked Bootloader?

I was wondering if there was any work being done with a pure AOSP rom or any other roms that will theme with a locked bootloader.
The answer is sort-of...
No, you cannot unlock the boot loader if you the latest ota.
Yes, you can root and install safestrap, then look for a desirable ROM.
The third option I played with is replace as many of the Motorola apps as you can with the aosp versions. It is dangerous, I only tried it with email and that worked great, but I moved on to contacts and totally screwed up the ROM forcing me to flash back to stock and redo everything.
Sent from my Nexus 10 using Tapatalk 2
There is a work around for the latest OTA hehehe
Flash the stock.IMG in fastboot with the toolkit. It will flash a compatible version where you can unlock and root from there.
If you want AOSP... Carbon ROM is the closest in my opinion so far...
Sent from my Nexus 7 using XDA Premium 4 mobile app
Can you elaborate more on this process? What do you mean unlock, I thought that was impossible now? Which toolkit? So confused.
Sent from my Nexus 10 using Tapatalk 2
lukkypuggy said:
There is a work around for the latest OTA hehehe
Flash the stock.IMG in fastboot with the toolkit. It will flash a compatible version where you can unlock and root from there.
If you want AOSP... Carbon ROM is the closest in my opinion so far...
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Has this method been tested and confirmed?
CrocadileUT78 said:
Can you elaborate more on this process? What do you mean unlock, I thought that was impossible now? Which toolkit? So confused.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
There is a Root Toolkit here in one of the forums, look for version 1.20
By unlock I mean unlocking the bootloader. It is only impossible if you don't flash an earlier version of the stock.img.
Yes it is confirmed, that is how I am running Carbon right now
Sent from my XT907 using XDA Premium 4 mobile app
So you had the 78 update, and downgraded, then unlocked bootloader? Everything else I read said that doesn't work. I'm so confused.
Sent from my XT907 using Tapatalk 4
I didnt think one could downgrade if they had a locked boot loader?! Anyone who had actually achieved this please chime in here.
lukkypuggy said:
There is a Root Toolkit here in one of the forums, look for version 1.20
By unlock I mean unlocking the bootloader. It is only impossible if you don't flash an earlier version of the stock.img.
Yes it is confirmed, that is how I am running Carbon right now
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Curious as well how did you go about this? I thought it was impossible to unlock on latest ota. If this is the case, why has this not been brought up earlier?
Sent from my XT907 using Tapatalk 2
CrocadileUT78 said:
So you had the 78 update, and downgraded, then unlocked bootloader? Everything else I read said that doesn't work. I'm so confused.
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
Yes, I had the .78 OTA and then I downgraded to a compatible version to get root then unlock and flash a custom ROM.
I don't know if my case was for some reason special but I also never got the "Boot loader is unlocked warning" either.
Sent from my XT907 using XDA Premium 4 mobile app
lukkypuggy said:
Yes, I had the .78 OTA and then I downgraded to a compatible version to get root then unlock and flash a custom ROM.
I don't know if my case was for some reason special but I also never got the "Boot loader is unlocked warning" either.
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I might be able to test this, but can you explain, by steps, how you did this?
Sent from my XT907 using Tapatalk 2
lukkypuggy said:
Yes, I had the .78 OTA and then I downgraded to a compatible version to get root then unlock and flash a custom ROM.
I don't know if my case was for some reason special but I also never got the "Boot loader is unlocked warning" either.
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Did you buy it used? If so, when? If you did, it may have already been unlocked...
Sent from my XT907 using Tapatalk 4
Here is the kit I use: http://forum.xda-developers.com/showthread.php?t=2249773
"Number 1 Explained -- This option requires your phone be in AP Fastboot mode. It will flash the official 4.1.2 System, Kernel, and Radio as well we wipe your data.
Number 2 Explained -- This option requires your phone be in AP Fastboot mode. It will flash the official 4.1.2 Stock Recovery.
Number 3 Explained -- This option requires your phone to be booted normally with USB Debugging enabled, and be already Rooted. This will flash TWRP Recovery by Hashcode.
Number 4 Explained -- This option requires your phone to be booted normally with USB Debugging enabled, and be already Rooted. This will flash CWM Recovery by Hashcode.
Number 5 Explained -- This is Dan Rosenberg's root exploit called 'Motochopper'. This option requires your phone to be booted normally, with USB Debugging enabled.
Number 6 Explained -- This option requires your phone to be booted normally, with USB Debugging enabled. It will install an App version of Dan Rosenberg's Motopocalypse exploit for unlocking the bootloader.
Remember, do not run this utility unless your phone is at 100% battery OR you have bought yourself one of Team Black Hat's Factory-Style Programming Adapters."
Click to expand...
Click to collapse
First backup your data and im not responsible if you cause the apocalypse
OK. chose option #1. It will flash a rootable version.
Next to root, choose option #5.
Next chose option #6 to ULOCK your bootloader.
Next chose either option 3 or 4 for a custom recovery. (I like CWM)
Have fun. that is exactly What I Did.
lukkypuggy said:
Here is the kit I use: http://forum.xda-developers.com/showthread.php?t=2249773
First backup your data and im not responsible if you cause the apocalypse
OK. chose option #1. It will flash a rootable version.
Next to root, choose option #5.
Next chose option #6 to ULOCK your bootloader.
Next chose either option 3 or 4 for a custom recovery. (I like CWM)
Have fun. that is exactly What I Did.
Click to expand...
Click to collapse
So just making sure, you were on the 4.1.2 ota prior to doing this right? Based on the notice posted on that utility thread, you are not suppose to use it if you were on the latest ota, which is the same one that locked the bootloader (unless stood corrected). So did you take a leap of faith and went ahead and did it even though it was warned to not do it, and did you ended up succeeding?
Was your phone bought new, or do you know if it's previous owner unlocked it before you got a hold of it, which would explain how you were able to, IF it wasn't used and modified prior?
Also, when you flashed the "compatible version" was it that you flashed the 4.1.2 update found in the utility or did you change it out to another image found here: http://sbf.droid-developers.org/scorpion_mini_xt907/list.php
Just wandering, because if so, this is phenomenal news for those who have do not possess the ability to unlock normally because they took the recent ota. I am sure that like everyone else, including myself, we just want to know if this is safe to follow or not, no pointing fingers or bad accusations.
Thanks
MistPhoenix said:
So just making sure, you were on the 4.1.2 ota prior to doing this right? Based on the notice posted on that utility thread, you are not suppose to use it if you were on the latest ota, which is the same one that locked the bootloader (unless stood corrected). So did you take a leap of faith and went ahead and did it even though it was warned to not do it, and did you ended up succeeding?
Was your phone bought new, or do you know if it's previous owner unlocked it before you got a hold of it, which would explain how you were able to, IF it wasn't used and modified prior?
Also, when you flashed the "compatible version" was it that you flashed the 4.1.2 update found in the utility or did you change it out to another image found here: http://sbf.droid-developers.org/scorpion_mini_xt907/list.php
Just wandering, because if so, this is phenomenal news for those who have do not possess the ability to unlock normally because they took the recent ota. I am sure that like everyone else, including myself, we just want to know if this is safe to follow or not, no pointing fingers or bad accusations.
Thanks
Click to expand...
Click to collapse
Yes, I did indeed took a leap of faith.
The phone was brand spanking new from Best Buy.
I flashed the one found in the utility.
If you dont trust it I TOTALY understand. I just wanted it so bad that I really didnt care.
lukkypuggy said:
Yes, I did indeed took a leap of faith.
The phone was brand spanking new from Best Buy.
I flashed the one found in the utility.
If you dont trust it I TOTALY understand. I just wanted it so bad that I really didnt care.
Click to expand...
Click to collapse
I believe you... Now the question is who is brave enough to take a leap of faith? I would love to unlock by boot loader to ensure I will get the latest Android versions moving forward. I don't trust Verizon to let an upgrade thru beyond 4.1.2. I would test your procedure myself, but I'm too dependent on my phone for work right now.
So... Anyone? Anyone? Be a hero folks, somebody take the plunge! Pretty please?
Sent from my Nexus 10 using Tapatalk 2
---------- Post added at 01:06 AM ---------- Previous post was at 12:51 AM ----------
Also, I feel obligated to mention this, and i do it with a heavy heart... A few weeks ago I seriously screwed up my phone playing with the contacts apk, breaking my ability to view my contacts or dial a number. I got desperate enough that even though I was on .78, used the utility and stock image to revert back everything fresh. I was so relieved when I saw it worked despite the warnings and being a slightly older rom version. Once I did that, I'm 75% sure I did trying unlocking the BL before installing .78 OTA, and it did not work. I figured I had nothing to lose at that point, and when it failed I just shrugged and continued getting my phone back to normal. Sorry if this discourages any brave souls, but again I am not 100% sure I followed the same steps Mentioned in this thread.
Sent from my Nexus 10 using Tapatalk 2
lukkypuggy said:
Yes, I did indeed took a leap of faith.
The phone was brand spanking new from Best Buy.
I flashed the one found in the utility.
If you dont trust it I TOTALY understand. I just wanted it so bad that I really didnt care.
Click to expand...
Click to collapse
Thank you for the response. I do plan on testing this later on today on a locked, new M so I will be able to verify completely. Everyone sit tight
Sent from my XT907 using Tapatalk 2
CrocadileUT78 said:
I believe you... Now the question is who is brave enough to take a leap of faith? I would love to unlock by boot loader to ensure I will get the latest Android versions moving forward. I don't trust Verizon to let an upgrade thru beyond 4.1.2. I would test your procedure myself, but I'm too dependent on my phone for work right now.
So... Anyone? Anyone? Be a hero folks, somebody take the plunge! Pretty please?
Sent from my Nexus 10 using Tapatalk 2
---------- Post added at 01:06 AM ---------- Previous post was at 12:51 AM ----------
Also, I feel obligated to mention this, and i do it with a heavy heart... A few weeks ago I seriously screwed up my phone playing with the contacts apk, breaking my ability to view my contacts or dial a number. I got desperate enough that even though I was on .78, used the utility and stock image to revert back everything fresh. I was so relieved when I saw it worked despite the warnings and being a slightly older rom version. Once I did that, I'm 75% sure I did trying unlocking the BL before installing .78 OTA, and it did not work. I figured I had nothing to lose at that point, and when it failed I just shrugged and continued getting my phone back to normal. Sorry if this discourages any brave souls, but again I am not 100% sure I followed the same steps Mentioned in this thread.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
BTW I never did get the unlock app to actually work (just remembered).
http://forum.xda-developers.com/showthread.php?t=2226729
http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
Download this .zip file once you have flashed the compatible stock version and have root.
As long as it says status code: 3 in the bootloader you are unlocked
Ok guys here are the results, sadly I could not achieve unlock with a unmodified, unrooted Razr M :
1. Turned off and started AP Fastboot mode. Used mattlgroff's Razr M Utility to flash to Android 4.1.2 98.15.66.XT907.Verizon.en.US system image. The flash worked perfectly I was able to downgrade to ota prior before the locked bootloader.
2. Used mattlgroff's Utility to root my device (step 5). I was able to root the device with SuperSU.
3. Used the seperate motopocalypse program by Dan Rosenberg found here http://forum.xda-developers.com/showthread.php?t=2226729. It ran and rebooted to AP fastboot mode. I received the folowing errors:
"TrustZone target address resolved to 2a020a02"
"TrustZone write failed: -11"
This indicated that the bootloader TrustZone which is needed to unlock, was still locked and that it couldn't make changes to properly unlock the device.
So for the time being, this method to unlock the bootloader does not work. I am thinking about trying the 4.1.1 system image instead, but I fear that since the bootloader is its own entity, that those that took the recent OTA had the TrustZone patched to the point where it cannot be written to period, even on a lower firmware. The best thing that could happen is for a miracle to occur and an exploit to be found to write to the TrustZone again.
MistPhoenix said:
Ok guys here are the results, sadly I could not achieve unlock with a unmodified, unrooted Razr M :
1. Turned off and started AP Fastboot mode. Used mattlgroff's Razr M Utility to flash to Android 4.1.2 98.15.66.XT907.Verizon.en.US system image. The flash worked perfectly I was able to downgrade to ota prior before the locked bootloader.
2. Used mattlgroff's Utility to root my device (step 5). I was able to root the device with SuperSU.
3. Used the seperate motopocalypse program by Dan Rosenberg found here http://forum.xda-developers.com/showthread.php?t=2226729. It ran and rebooted to AP fastboot mode. I received the folowing errors:
"TrustZone target address resolved to 2a020a02"
"TrustZone write failed: -11"
This indicated that the bootloader TrustZone which is needed to unlock, was still locked and that it couldn't make changes to properly unlock the device.
So for the time being, this method to unlock the bootloader does not work. I am thinking about trying the 4.1.1 system image instead, but I fear that since the bootloader is its own entity, that those that took the recent OTA had the TrustZone patched to the point where it cannot be written to period, even on a lower firmware. The best thing that could happen is for a miracle to occur and an exploit to be found to write to the TrustZone again.
Click to expand...
Click to collapse
Mine had the -11 error also but it also said status code 3 in the actually bootloader, Then I flashed CWM and that was it, now I have CM10.1.3 STABLE.
Maybe double check?

How to root (SGP561) Z2 Tablet Verizon, new update 23.0.1.E.0.208 (4.4.4)

Hi guys, finally I've found a way to get the latest update 23.0.1.E.0.208 (4.4.4) without losing root on this tablet.
The method is the same as the method here (http://forum.xda-developers.com/xperia-z2/general/4-4-4-creating-rooted-update-package-t2933155), but we will use the files for Xperia Z2 Tablet Verizon instead of files for Xperia Z2.
First, you MUST BE on an older version (17.1.D.0.437) with root and XZDualRecovery
You need these files:
1. New 23.0.1.E.0.208 update FTF file (you can use XperiFirm to get it)
2. PRFCreator v0.5.zip (I tried the later version v0.8 but it didn't work, so better to use v0.5)
3. Latest stable SuperSU update package
4. XZDualRecovery flashable patched version (in the attachment) (note that the original version from [NUT] will not allow you to mount system rw)
Then follows step 4 to 11 in the instructions in the above thread for Xperia Z2 and replace all the files for Xperia Z2 with the files you've just got.
Good luck!
thanks for this, will try it this week...
noticed any issues with this update on the verizon tab?
Is it possible to flash back to 4.4.2, to root? Sadly, mine came with the newest update.
Sent from my SGP561 using XDA Free mobile app
https://mega.co.nz/#!VZYHRAKT!wky8U_6G9aB4XctdfKMIaJQZtdlnWTtNv0pNLlgh0AM here is the ftf file for the older version.
Worked like a charm! Thank you for posting this.
How come this cannot be posted as a flashable zip? Why do we need to create our own file? Just curious.
Sent from my SGP561 using XDA Premium HD app
smarcisin said:
How come this cannot be posted as a flashable zip? Why do we need to create our own file? Just curious.
Sent from my SGP561 using XDA Premium HD app
Click to expand...
Click to collapse
My internet connection sucks. It takes long to upload large files.
Trying to do this, however it seems we need a custom recovery already installed. Trying to install the XZDualRecovery from the installer file I downloaded but it just hangs at libdvm opened. Any other way to install a custom recovery so I can follow the rest of the guide to get my replacement tab rooted?
Varekai said:
Trying to do this, however it seems we need a custom recovery already installed. Trying to install the XZDualRecovery from the installer file I downloaded but it just hangs at libdvm opened. Any other way to install a custom recovery so I can follow the rest of the guide to get my replacement tab rooted?
Click to expand...
Click to collapse
Sounds to me like you need to flash the old ftf first, then root and then install the custom recovery. Root only works on the older firmware linked above.
Sent from my SGP561 using XDA Premium HD app
Thanks, I thought you had to have a recovery already installed for that. Downloaded everything I need plus old FTF file, can't seem to get it to work right. Think I am having driver problems even tho it works fine in fastboot mode through ADB. Can't get Sony PC companion to work either even tho I've downloaded pretty much every driver I can find for it. I'm on Windows 8.1
I never managed to get it to work on windows 8.1 by had a windows 7 laptop laying around and that worked fine. I would recommend finding a non 8.1 computer. Good luck.
Sent from my SM-G900V using XDA Premium HD app
Got it working. I didn't know I had to have the unknown sources checked. Also I didn't realize I was plugged into a 3.0 port in the back of my PC, so that didn't help.
Now that I'm on the old version and rooted, I saw some people had success with updating to the newest update for VZW and keeping root. Can anyone else confirm this? I have TWRP and everything on my HTC, but my tablet I would rather not mess with it as much. The steps in this guide are pretty involved.
Varekai said:
Got it working. I didn't know I had to have the unknown sources checked. Also I didn't realize I was plugged into a 3.0 port in the back of my PC, so that didn't help.
Now that I'm on the old version and rooted, I saw some people had success with updating to the newest update for VZW and keeping root. Can anyone else confirm this? I have TWRP and everything on my HTC, but my tablet I would rather not mess with it as much. The steps in this guide are pretty involved.
Click to expand...
Click to collapse
I am on the newest firmware and rooted, so I can confirm that it works.
It's not as bad as it seems. Just follow the steps and you will be a better human for it! Happy hacking and debloating.
Sent from my SGP561 using XDA Premium HD app
Yup just did this, everything is working great, thanks!
My camera doesn't work after updating. Every time I hit the capture button it just freezes. I'd like to just wipe and do a clean install. Can I just do it in TRWP? Will I lose root?
Sent from my SGP561 using XDA Premium HD app
smarcisin said:
My camera doesn't work after updating. Every time I hit the capture button it just freezes. I'd like to just wipe and do a clean install. Can I just do it in TRWP? Will I lose root?
Sent from my SGP561 using XDA Premium HD app
Click to expand...
Click to collapse
Should be fine, I wiped mine after the whole process and had no problems at all.
Sent from my SM-G900V using XDA Premium HD app
There was a leaked Lollipop update I saw today on XperiaBlog. Could this method be used to update?
Update: worked like a charm. Running lollipop with root and nuts dualboot
tmkhoa said:
https://mega.co.nz/#!VZYHRAKT!wky8U_6G9aB4XctdfKMIaJQZtdlnWTtNv0pNLlgh0AM here is the ftf file for the older version.
Click to expand...
Click to collapse
Is it possible to have this uploaded again since it's no longer available. ftf file for 17.1.D.0.437
Also PRFCreator v0.5.zip since the earliest one available is v0.7.
Thanks!
Anybody...
AddictedToGlass said:
Anybody...
Click to expand...
Click to collapse
How about this one:
https://mega.nz/#!lAQFQZ7R!wky8U_6G9aB4XctdfKMIaJQZtdlnWTtNv0pNLlgh0AM
Why PRFCreator v0,5?
freealta said:
Is it possible to have this uploaded again since it's no longer available. ftf file for 17.1.D.0.437
Also PRFCreator v0.5.zip since the earliest one available is v0.7.
Thanks!
Click to expand...
Click to collapse

[Q&A] [BS_FREE_Lollipop_5.0_Rom_BOG5_Based]

Q&A for [BS_FREE_Lollipop_5.0_Rom_BOG5_Based]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [BS_FREE_Lollipop_5.0_Rom_BOG5_Based]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
After installing Google Photos, should it be moved to /system/priv-app?
Two requests
First off I just want to thank you for your hard and excellent work. I have been using MOAR for quite some time and it has been great. I am switching to the BS free ROM - it's almost exactly what I want. I was curious if you could add back the Samsung Email App with Exchange Support and also the S6 Keyboard. I have to run the standard email app for work, and could not find a seperate source to successfully install on BOG5. I was able to get the S6 Keyboard sepererately and installed, but who wants the ugly S5 KB preinstalled anyway?
Thanks!
airwalker1 said:
First off I just want to thank you for your hard and excellent work. I have been using MOAR for quite some time and it has been great. I am switching to the BS free ROM - it's almost exactly what I want. I was curious if you could add back the Samsung Email App with Exchange Support and also the S6 Keyboard. I have to run the standard email app for work, and could not find a seperate source to successfully install on BOG5. I was able to get the S6 Keyboard sepererately and installed, but who wants the ugly S5 KB preinstalled anyway?
Thanks!
Click to expand...
Click to collapse
Have you tried installing Android Exchange Services? It integrates Exchange into the gmail app. I use it and am very happy.
http://www.apkmirror.com/apk/google...ge-services-6-5-1791555-android-apk-download/
stock ncg to no bs 0g5 issues
Hey how you guys doing? Thanks for all your hard work jkruse.
I'm having issues. I flashed back to stock NCG, I've rooted, installed busybox, installed safestrap, installed flashfire v0.21, when I go to install the no BS 0G5 deodexed rom using flashfire. I do the following steps I select the firmware first then the rom finally the kernel. Once it flashes and finishes it just freezes at black galaxy s5 boot screen it stays there and doesn't do anything. I've checked all md5 checksums verified them again just to be sure they checked out correctly. I'm no noob I've been flashing roms and rooting since I had my Droid X back in the day. If you could point me in the right direction, your help would be greatly appreciated and thank your time.
Are you flashing the firmware as a zip or firmware package? The firmware flashable file includes the kernel, and it needs to be flashed as a zip, not a firmware package.
Sent from my SM-G900V using XDA Free mobile app
---------- Post added at 04:49 PM ---------- Previous post was at 04:44 PM ----------
Try flashing the NCG kernel with Odin and see if you can boot into safe strap. If you can get into safe strap, then install the BOG5 kernal.zip.
Sent from my SM-G900V using XDA Free mobile app
I've been flashing the firmware as is, I'm not to sure how to select flash as a zip or package. I'm new to flashfire, I've always used odin.
MykR0xda said:
I've been flashing the firmware as is, I'm not to sure how to select flash as a zip or package. I'm new to flashfire, I've always used odin.
Click to expand...
Click to collapse
Do you tap "Flash firmware package" or "Flash ZIP or OTA" when you select the firmware?
I select firmware for the firmware part
CVertigo1 said:
Do you tap "Flash firmware package" or "Flash ZIP or OTA" when you select the firmware?
Click to expand...
Click to collapse
flashing back to stock yet again, this time i did the ota flash zip on each i selected rom first, firmware, kernel, lastly theme. it flashed everything but refuses to get past the black galaxy s5 logo it did something new this time it hangs and boots to recovery.
Your phone keeps bootlooping every time because you keep flashing it incorrectly. DO NOT flash it as a firmware package. DO flash it as a ZIP or OTA.
I will make it much more simple. Boot into safe strap, then tap install. Install BOG5 firmware, then install the BS free ROM. When the install is complete, tap wipe Dalvik/cache, then tap reboot. Then wait 7 minutes for your phone to boot into awesomeness.
Sent from my SM-G900V using XDA Free mobile app
CVertigo1 said:
Your phone keeps bootlooping every time because you keep flashing it incorrectly. DO NOT flash it as a firmware package. DO flash it as a ZIP or OTA.
I will make it much more simple. Boot into safe strap, then tap install. Install BOG5 firmware, then install the BS free ROM. When the install is complete, tap wipe Dalvik/cache, then tap reboot. Then wait 7 minutes for your phone to boot into awesomeness.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
Alright I'll do that now, thanks for your time. I really appreciate the help.
I've never had issues flashing the way I have been until earlier today.
Forgive me, I misread your last post. I see that you flashed as OTA last time. I haven't had any issues flashing with FlashFire, but I have heard of some people running into problems. Try using safestrap and following the steps I just posted. Also, you do not need to flash the kernel, because it is included with the firmware.
CVertigo1 said:
Forgive me, I misread your last post. I see that you flashed as OTA last time. I haven't had any issues flashing with FlashFire, but I have heard of some people running into problems. Try using safestrap and following the steps I just posted. Also, you do not need to flash the kernel, because it is included with the firmware.
Click to expand...
Click to collapse
Alright I'm doing so now, I'll report back, thanks again!
I may know why you are running into issues now that you hadn't before. On previous builds, JK would use an actual firmware package and separate kernel. The BOE1 firmware contained a bootloader update that prevented downgrading, so it needed to be modified, and was no longer an official firmware package. Since then, he has made the firmwares flashable as a zip. You are probably familiar with the older method of upgrading the firmware, which is why you've never had an issue before.
CVertigo1 said:
I may know why you are running into issues now that you hadn't before. On previous builds, JK would use an actual firmware package and separate kernel. The BOE1 firmware contained a bootloader update that prevented downgrading, so it needed to be modified, and was no longer an official firmware package. Since then, he has made the firmwares flashable as a zip. You are probably familiar with the older method of upgrading the firmware, which is why you've never had an issue before.
Click to expand...
Click to collapse
It worked man, thanks again for helping. I'm sure I might have missed something somewhere. I'm gonna try to flash it again just did what you said to ensure it was working now, typing from my phone right now.
Glad to hear it!
Sent from my SM-G900V using XDA Free mobile app
CVertigo1 said:
Glad to hear it!
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
Just reflashed and started fresh, now it's working and also the themes are aswell. No more issue's.
Looks like I've ran into another problem, wifi tether keeps getting force closes when trying to use foxfi tether app. Maybe i have to copy some files from a stock 0g5 ROM? Using the google deodexed version.
airwalker1 said:
First off I just want to thank you for your hard and excellent work. I have been using MOAR for quite some time and it has been great. I am switching to the BS free ROM - it's almost exactly what I want. I was curious if you could add back the Samsung Email App with Exchange Support and also the S6 Keyboard. I have to run the standard email app for work, and could not find a seperate source to successfully install on BOG5. I was able to get the S6 Keyboard sepererately and installed, but who wants the ugly S5 KB preinstalled anyway?
Thanks!
Click to expand...
Click to collapse
How and what exactly did you do to get the S6 keyboard installed and working? I've tried and haven't had any luck. Also, it is the one with the emoji to the left of the spacebar right? Thank you in advance

[BUSTED] Pyro got killed after flashing recovery Image!

why the heck well yeas it happened to me 2 Finally I recieved my killswitch. I never had TegraOTA update active...it happened just right after a regular reset with an recovery Image. .I am really sad now I have to apologize! I LOVED MY PYRO!....
This is just a warning keep on the custom side with your pyros! **** that stock Mellow!
Ill try my best to not cry..but heck...
cheers guys maybe someday I'll be back with another pyro!
love
bencozzy said:
My Pyro is stock I asked nvidia to whitelist the serial because it's a development device.
Click to expand...
Click to collapse
U had luck with your request?
bencozzy said:
They told me they did when I requested the Vulkan api build. I also never requested a replacement not sure if that plays into their decision making.
Click to expand...
Click to collapse
Uh, yeah. The whole killswitch process only starts when you fire up your replacement tablet for the first time & set up an internet connection.
That is the ultimate reason why you put your radios to Airplane before flashing, and even before booting, you flash the remove TegraOTA zip file in TWRP.... heck, even a clean flash would be good too.
deleted
daniyo27 said:
That is the ultimate reason why you put your radios to Airplane before flashing, and even before booting, you flash the remove TegraOTA zip file in TWRP.... heck, even a clean flash would be good too.
Click to expand...
Click to collapse
Removing the SIM if you've got the LTE version, clean flashing if using stock images & skipping the WiFi setup. Imo that's the best way to do it, you get all the time in the world to remove TegraOTA whichever way you're comfortable with.
It's honestly a bit sad that some people don't take the time to do this stuff properly.
Here is what I think happened: i had Recovery erased..you know why. So I were on stock with nethunter and suffered from random reboots. That's why I tried reflash it. Once the regular Recovery was installed i got Killswitch es ???*
NVM, just realized he did it through a manual flash, not OTA.
NVM again, I am bad at reading. So he flashed a recovery image then got the OTA after he rebooted. So again, why is Nvidia still pushing this update if they have known it was bricking devices since January.
deleted
Can you explain please all the steps you did until the kill? Ibinstalled 4.1 stock update from.nvidia site on my pyro. Before booting the os i deleted tegraota with the zip and erased recovery with fastboot. But i havent turned on the wifi yet.
Sent from my LG-E975 using XDA Free mobile app
deleted
So now you have the pyro on stock with the original update and connected to internet. But is killed?
Sent from my LG-E975 using XDA Free mobile app
---------- Post added at 08:29 AM ---------- Previous post was at 08:18 AM ----------
The problem is that i cant install a custom rom
Sent from my LG-E975 using XDA Free mobile app
deleted
Can you tell me please which version of xposed? Id like to unstall it. I also freezed with titanium almost all nvidia apps and services. If the kill switch is an update sent by nvidia servers, deleting tegra ota would be safe, and also the recovery, so nothing can be flashed. Did you check if the kill is triggered for your pyro?
Sent from my LG-E975 using XDA Free mobile app
---------- Post added at 08:55 AM ---------- Previous post was at 08:53 AM ----------
So, if the kill is contained in the stock images and you were connected to internet while using the stock image, you would have been affected by the kill switch. But youbsay its working, so i think theres no kill in.the stocks
Sent from my LG-E975 using XDA Free mobile app
deleted
I installed 4.0.1 before the 4.1 and tablet worked (but never cinnected). Can you "system update" on your settings after flashing the nomoreota zip?
Sent from my LG-E975 using XDA Free mobile app
deleted
Its not green. Its the nirmal g updater. When.i.was stock 5.1.2 i deleted manually tegraota apk and "system update" on settings was disappeared. Maybe the g updater is another way to kill the tablet?
Sent from my LG-E975 using XDA Free mobile app
Is your pyro working now?
Sent from my LG-E975 using XDA Free mobile app
Yes?

Android 7.0 for SM-T817W is out

The latest Android 7 Nougat firmware for SM-T817w, a Canadian version of the Tab S2, is out.
I did an OTA yesterday morning and it is now on firmware T817WVLU3CQDA. There was an update right after and now it is on NRD90M.T817WVLU3CQDA.DM.
I odined the TWRP (twrp_3.1.0-1_sm-t810_13317.tar) and twrp flashed the SuperSU (SuperSU-2.79-201612051815.aip) right after. It has TRWP recovery and root without even a glitch.
It probably takes a few week before Sammobile posts this official firmware.
Is this compatible with the T817T T-Mobile version?
I don't think so. You have to wait till that for t817t is released.
Hey man can you post a nandroid backup so us other users can try to go this route until the OTA is posted?
thanks
Sure, here it is, a link to the nandroid backup for those who need it. Restore it with TWRP.
https://drive.google.com/drive/folders/0B5aAz5mBnQAaczRVcXdtS3JPX3M?usp=sharing
Thank you man!!!
Thanks, running good n sexy
Sent from my SM-T817W using XDA Premium HD app
How does one install this?
I have TWRP, Rooted - installed rom manager, nandroid manager, busy box, all the dependencies - booted into recovery and when I click on restore, regardless of where it is (internal sd, external sd, external usb) no files are shown.. i've unzipped it to a folder etc..
Do I have to wipe out twrp and install clockwork mod instead?
myeepad said:
The latest Android 7 Nougat firmware for SM-T817w, a Canadian version of the Tab S2, is out.
I did an OTA yesterday morning and it is now on firmware T817WVLU3CQDA. There was an update right after and now it is on NRD90M.T817WVLU3CQDA.DM.
I odined the TWRP (twrp_3.1.0-1_sm-t810_13317.tar) and twrp flashed the SuperSU (SuperSU-2.79-201612051815.aip) right after. It has TRWP recovery and root without even a glitch.
It probably takes a few week before Sammobile posts this official firmware.
Click to expand...
Click to collapse
Just extract the directory and restore from TWRP.
MastahOnetrack said:
How does one install this?
I have TWRP, Rooted - installed rom manager, nandroid manager, busy box, all the dependencies - booted into recovery and when I click on restore, regardless of where it is (internal sd, external sd, external usb) no files are shown.. i've unzipped it to a folder etc..
Do I have to wipe out twrp and install clockwork mod instead?
Click to expand...
Click to collapse
Do this if you have room and time. This way you will know what to put where and how:
Do a backup in TWRP then look at the folder it created and you will have an epiphany
Sent from my SM-T817W using XDA Premium HD app
iggut said:
Do this if you have room and time. This way you will know what to put where and how:
Do a backup in TWRP then look at the folder it created and you will have an epiphany
Sent from my SM-T817W using XDA Premium HD app
Click to expand...
Click to collapse
Lol thanks.. yes.. makes a bit of sense which is better than no sense.. who knew it had to be in TWRP/[long string of random numbers]/Backups
Its working now, except for a few things - I cannot transfer any files to the tablet via USB, there doesn't seem to be a developers option anywhere, I've lost the unified storage (damnit samsung..) and seems to have lost root.
Other than that, we're all good.
I flashed Magisk to root and you get dev option the same way... Just tap build 5 times. It is in a sub menu this time... Thank Samsung
myeepad said:
The latest Android 7 Nougat firmware for SM-T817w, a Canadian version of the Tab S2, is out.
I did an OTA yesterday morning and it is now on firmware T817WVLU3CQDA. There was an update right after and now it is on NRD90M.T817WVLU3CQDA.DM.
Click to expand...
Click to collapse
Really! I also have a T-817w (here in Canada)... and I still haven't got the update. I'm full stock / never rooted, eh.
Any idea why I'm not seeing it, even when manually checking for the update? (Sammobile still doesn't have the update either.)
On Rogers still no Nougat as of today
jgoedhard said:
On Rogers still no Nougat as of today
Click to expand...
Click to collapse
Hmmm. I'm wondering where in the world the OP found this ROM update. I haven't seen it posted anywhere.
Got the ota this morning build is now NRD90M.T817WYLU3CQE4
Sent from my SM-T817W using XDA-Developers Legacy app
DAE1964 said:
Got the ota this morning build is now NRD90M.T817WYLU3CQE4
Sent from my SM-T817W using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thanks for the info. Now I have to unroot and get this OTA all over again.
DAE1964 said:
Got the ota this morning build is now NRD90M.T817WYLU3CQE4
Sent from my SM-T817W using XDA-Developers Legacy app
Click to expand...
Click to collapse
I gave it a day and battery life is similar to MM during sleep. Screen on is more demanding though. No noticeable lag. So far so good.
Sent from my SM-T817W using XDA-Developers Legacy app
Anyone noticied a bug in brightness and auto brightness?
Edit:Bug fixed After a reflash with smart switch
Yorgo1982 said:
Anyone noticied a bug in brightness and auto brightness?
Click to expand...
Click to collapse
Screen seems good but I set it to reading mode.
Sent from my SM-T817W using XDA-Developers Legacy app

Categories

Resources