Develop Bugs

[Q] Should I not root? Video + Camera problem

I'm very excited about the 4.04 ICS rom, but before I unlock my bootloader and root (hence voiding my warranty) I wanted the community's opinion on some issues I've been having with video and camera
Video: After downloading one of the loaders that didn't require unlocking, I noticed that only a few mp4's would run on MX Video Player, and even then, the audio and video would not sync up and the audio would quickly die/disappear. When attempted to load on stock video player, it would just say that the file can't be played, no other video player would work either.
I factory reset my phone today in preperation for 4.04, and tried some videos to see if it was the loader's fault, to my surprise, no videos would work. I looked around on the xda forums and reformatted all the files using Freemake Video Converter to 720 HD, and now most videos tested seem to be working, although a few seem to have lost their quality. Thought 720 HD was max ability of the phone, so it seems odd that they would've lost quality from prior.
Camera: For no reason that I've found so far, sometimes I try to open the camera app, and it'll say that "Camera has stopped working", or "Cannot connect to Camera", usually this happens after prolonged stay in my pocket?
I don't know if this is a software issue or maybe my phone is broken, so I'd like to confirm before voiding my warranty

xupru said:
I'm very excited about the 4.04 ICS rom, but before I unlock my bootloader and root (hence voiding my warranty) I wanted the community's opinion on some issues I've been having with video and camera
Video: After downloading one of the loaders that didn't require unlocking, I noticed that only a few mp4's would run on MX Video Player, and even then, the audio and video would not sync up and the audio would quickly die/disappear. When attempted to load on stock video player, it would just say that the file can't be played, no other video player would work either.
I factory reset my phone today in preperation for 4.04, and tried some videos to see if it was the loader's fault, to my surprise, no videos would work. I looked around on the xda forums and reformatted all the files using Freemake Video Converter to 720 HD, and now most videos tested seem to be working, although a few seem to have lost their quality. Thought 720 HD was max ability of the phone, so it seems odd that they would've lost quality from prior.
Camera: For no reason that I've found so far, sometimes I try to open the camera app, and it'll say that "Camera has stopped working", or "Cannot connect to Camera", usually this happens after prolonged stay in my pocket?
I don't know if this is a software issue or maybe my phone is broken, so I'd like to confirm before voiding my warranty
Click to expand...
Click to collapse
Did the problems persist after you did the factory reset? I can only think that some other app, such as Google Talk Video is taking the camera app and not giving it back, even after closing it. Try logging out of Google Talk Video, closing it and doing a clear data. Does the camera problem go away?
Regarding rooting, remember you can always "unroot" and nobody would know you ever rooter. Your warranty is safe. Just make sure you make a Nandroid backup of your stock ROM image, and keep it safe, so you can always go back.
Also, if you are going to 4.0.4, can you confirm you have the CDMA version?

samizad said:
Regarding rooting, remember you can always "unroot" and nobody would know you ever rooted. Your warranty is safe. Just make sure you make a Nandroid backup of your stock ROM image, and keep it safe, so you can always go back.
Also, if you are going to 4.0.4, can you confirm you have the CDMA version?
Click to expand...
Click to collapse
+1 on both points, especially the latter.

Yes, I have the Verizon LTE version.
I've never attempted to use Camera through any other app, but I can see how perhaps some other app is interfering with it, wish there was a way to confirm.
I had actually planned on doing the step by step process for rooting, but I never managed to find the time to finish the process, so I downloaded the toolkit for 1 step rooting. And I now see Samsung Android ADB interface in Device Manager.
I see the option for unlocking, rooting, renaming restore file + flash cwm recovery, as well as relocking below it, but I don't see a mention of Nandroid?
I googled around and Nandroid requires an already unlocked and rooted phone. So I'm not sure what order to do this in.
It seems like in order to root the phone, I just press 7 to unlock root, rename and flash CWM recovery on, and then press 12 to flash 4.0.4 on... and that's it?
Thanks for the help!

First step is to root. Then flash ClockworkMod recovery either via the toolkit or via ROM Manager app (available in Market). Then you can boot into recovery mode and navigate the options to "Backup and Restore". Select the option to backup. This will take a few minutes to write the entire image as a single backup file. This is your "Nandroid Backup". Copy and paste this file onto your PC (or burn it onto CD). Keep it well and truly safe!!!
So, when you need to return to stock image (which will hopefully be never), first you restore this backup image using the same recovery method. Then proceed to unroot.
Job done.
PM me if you're stuck

Le S3 factory image 5.8.020S directly from LeEco!

Here it is as promised. This is only for the x522 Le S3 (Le 2 variants for US Market)! Download here: http://www.mediafire.com/file/55m4m5of3uvmef5/S2_X522-NA-OP-IFXNAOP5802012141S-5.8.020S.zip
I couldn't figure how to install this aside from using TWRP so this is what I did from stock unrooted 5.8.019S (which I had root prior, then restored via a back up from someone but could not take OTA):
1. adb reboot bootloader
2. fastboot oem unlock-go
3. fastboot boot twrp.img (has to be the chinese ydss twrp, the official twrp will not let you flash the stock image). Chose read-only instead of swipe to allow modification.
4. wipe factory reset, and format data.
5. go to mount, and enable mtp, and drag the stock image into the root directory of the phone.
6. go to install, and flash the stock rom. This will take a bit of time 5-10 minute or so, the progress bar doesn't move properly so don't panic if you see it "freezing" up.
7. once it is completed, it will tell you it's done. Before reboot, wipe dalvik and cache only, then reboot system.
You should be on stock recovery from this image, and unrooted. In theory, this should still allow you to take OTA. I might be wrong though, I don't know how LeEco does their firmwares and checks. I hope a mod on here make a forum for the Le S3 so we don't keep posting in Le 2 forum. Hopefully someone can cook this factory image to a nice working rom that we can flash, and hopefully figure a way so that we can use flashfire app to update ota even when rooted.
Enjoy It took me a pretty long time to drag this out of LeEco. Please rep if I helped ya'll.

xterminater07 said:
Here it is as promised. This is only for the x522 Le S3 (Le 2 variants for US Market)! Download here: http://www.mediafire.com/file/55m4m5of3uvmef5/S2_X522-NA-OP-IFXNAOP5802012141S-5.8.020S.zip
I couldn't figure how to install this aside from using TWRP so this is what I did from stock unrooted 5.8.019S (which I had root prior, then restored via a back up from someone but could not take OTA):
1. adb reboot bootloader
2. fastboot oem unlock-go
3. fastboot boot twrp.img (has to be the chinese ydss twrp, the official twrp will not let you flash the stock image). Chose read-only instead of swipe to allow modification.
4. wipe factory reset, and format data.
5. go to mount, and enable mtp, and drag the stock image into the root directory of the phone.
6. go to install, and flash the stock rom. This will take a bit of time 5-10 minute or so, the progress bar doesn't move properly so don't panic if you see it "freezing" up.
7. once it is completed, it will tell you it's done. Before reboot, wipe dalvik and cache only, then reboot system.
You should be on stock recovery from this image, and unrooted. In theory, this should still allow you to take OTA. I might be wrong though, I don't know how LeEco does their firmwares and checks. I hope a mod on here make a forum for the Le S3 so we don't keep posting in Le 2 forum. Hopefully someone can cook this factory image to a nice working rom that we can flash, and hopefully figure a way so that we can use flashfire app to update ota even when rooted.
Enjoy It took me a pretty long time to drag this out of LeEco. Please rep if I helped ya'll.
Click to expand...
Click to collapse
I use this with a Thumb Drive, makes life easier
https://www.amazon.com/dp/B017XARUKC/ref=cfb_at_prodpg

How will that help in my post? Which part can it cut down?

Thanks a lot. Worked like a charm and I'm now on 5.8.020s. How did you obtain the file?

xterminater07 said:
How will that help in my post? Which part can it cut down?
Click to expand...
Click to collapse
just for people who are not sure of the mtp part in step 5..
its not a necessary item, i just find it quicker to write files to thumb drive while i am setting up into TWRP,
might not need to format data then either,as only doing that to write file to phone
Its just my personal preference , not a must have item
But thankyou again for your persistence with LeEco and getting this file..

For whats its worth, i restrored 19s , let it run a few mins, then went back to TWRP and without wiping data or anything else and leaving it read only i let the 20s file install, and all is running well..
As of yet i have not tried to load TWRP on the 20s system, but having the full backup will give us OTA's hopefully

Y even use 19s when the image is 20s. The problem with restoring is the backup was done by read and write twrp. This kills ota righ?

They also gave me 19s image but I'm like why use it. Oh by the way guys, LeEco's camera app sucks balls. I ended up using "A better camera unlocked" app and it's ten times better! HDR is amazing but it takes about 1-2 second so hold your hands still! Hehe... If anyone got better camera reccommendation let us know. I tried open camera as well, not good.

I don't know if you can find it and if you do, I have always liked the snapdragon camera.
I am lost, can someone point me were the Chinese TWRP is located, I currently have the official version on the phone.

Charles Broccoli said:
I don't know if you can find it and if you do, I have always liked the snapdragon camera.
I am lost, can someone point me were the Chinese TWRP is located, I currently have the official version on the phone.
Click to expand...
Click to collapse
Snapdragon camera 2.2 was ported for all marshmallow but it requires flashing via twrp. I will try that later in read only mode. The chinese twrp is here https://mega.nz/#!XhYznTzA!z-XfbrIaVrKWAC-OaW86NFj1EAvZs68GmSchedQ-vhI.
Also, after reading around I found out the Le S3 has the exact camera as the Le 2 instead of the Le pro 3 . It uses the omnivision ov 16880, which is decent but nowhere near the sony imx298 which is seen on the one plus 3. LeEco has confirmed to enable camera2api in their EUI 6.0 coming in 2017. However, can any developer tell us how is this any difference from us rooting the device ourselves and enabling camera2api via build.prop? Or does enabling it, just basically turns it on but if LeEco has not build it to their rom, it won't work right?

Will this work on le 2 X526?
Sent from my SM-G935F using Tapatalk

xterminater07 said:
Snapdragon camera 2.2 was ported for all marshmallow but it requires flashing via twrp. I will try that later in read only mode. The chinese twrp is here https://mega.nz/#!XhYznTzA!z-XfbrIaVrKWAC-OaW86NFj1EAvZs68GmSchedQ-vhI.
Also, after reading around I found out the Le S3 has the exact camera as the Le 2 instead of the Le pro 3 . It uses the omnivision ov 16880, which is decent but nowhere near the sony imx298 which is seen on the one plus 3. LeEco has confirmed to enable camera2api in their EUI 6.0 coming in 2017. However, can any developer tell us how is this any difference from us rooting the device ourselves and enabling camera2api via build.prop? Or does enabling it, just basically turns it on but if LeEco has not build it to their rom, it won't work right?
Click to expand...
Click to collapse
You can enable camera api 2 on eui I'm using it by enbling it through build.prop
It works great

Charles Broccoli said:
I don't know if you can find it and if you do, I have always liked the snapdragon camera.
I am lost, can someone point me were the Chinese TWRP is located, I currently have the official version on the phone.
Click to expand...
Click to collapse
rohansalunkhe71 said:
You can enable camera api 2 on eui I'm using it by enbling it through build.prop
It works great
Click to expand...
Click to collapse
Right, but does that improve picture quality or enabling it just allow you to do manual mode while the pic still look crappy? I had a le max 2, and while the imx230 is a good sensor, eui software sucks compared to using a third party camera app.

xterminater07 said:
Right, but does that improve picture quality or enabling it just allow you to do manual mode while the pic still look crappy? I had a le max 2, and while the imx230 is a good sensor, eui software sucks compared to using a third party camera app.
Click to expand...
Click to collapse
well personally I prefer raw image editing thats why I enabled camera api 2.
Yes image quality is still ****y but due to manual settings it enables to take good images, focus on closer objects. But it doesn't give image quality as sony imx230 sensor.

rohansalunkhe71 said:
well personally I prefer raw image editing thats why I enabled camera api 2.
Yes image quality is still ****y but due to manual settings it enables to take good images, focus on closer objects. But it doesn't give image quality as sony imx230 sensor.
Click to expand...
Click to collapse
That's what I thought. That was my concern bc I want to know if doing camera2api in build prop just enables it or does it actually makes it useless since leeco algorithm is shiet.

xterminater07 said:
Here it is as promised. This is only for the x522 Le S3 (Le 2 variants for US Market)! Download here: http://www.mediafire.com/file/55m4m5of3uvmef5/S2_X522-NA-OP-IFXNAOP5802012141S-5.8.020S.zip
I couldn't figure how to install this aside from using TWRP so this is what I did from stock unrooted 5.8.019S (which I had root prior, then restored via a back up from someone but could not take OTA):
1. adb reboot bootloader
2. fastboot oem unlock-go
3. fastboot boot twrp.img (has to be the chinese ydss twrp, the official twrp will not let you flash the stock image). Chose read-only instead of swipe to allow modification.
4. wipe factory reset, and format data.
5. go to mount, and enable mtp, and drag the stock image into the root directory of the phone.
6. go to install, and flash the stock rom. This will take a bit of time 5-10 minute or so, the progress bar doesn't move properly so don't panic if you see it "freezing" up.
7. once it is completed, it will tell you it's done. Before reboot, wipe dalvik and cache only, then reboot system.
You should be on stock recovery from this image, and unrooted. In theory, this should still allow you to take OTA. I might be wrong though, I don't know how LeEco does their firmwares and checks. I hope a mod on here make a forum for the Le S3 so we don't keep posting in Le 2 forum. Hopefully someone can cook this factory image to a nice working rom that we can flash, and hopefully figure a way so that we can use flashfire app to update ota even when rooted.
Enjoy It took me a pretty long time to drag this out of LeEco. Please rep if I helped ya'll.
Click to expand...
Click to collapse
xterminater07 said:
Y even use 19s when the image is 20s. The problem with restoring is the backup was done by read and write twrp. This kills ota righ?
Click to expand...
Click to collapse
Its not the fact read/write was used in TWRP, as i also when i got my replacement phone used it read only and still no OTA was taking...
I put 19s on just to see if 20s would go on without all the cleaning of the encrypted data and the such, cuts down on a step or two maybe..
hey any chance you can throw 19s full rom up somewhere..id like to play and try find out what will and wont work when using twrp and ota's

Before I get started, I had originally installed the official TWRP.img as recovery instead of only booting from the twrp.img.
Should I first install the original stock recovery.img before getting started or will the act of flashing the stock rom overwrite the installed twrp.img?
I think I already know to first install the stock recovery.img then just boot into the Chinese twrp.img afterwards to flash the stock rom or will it matter?
I am also on 18s firmware, I don't think it would matter to flash it straight to 20s

You should be OK to just install it .I believe it will ask you if you want to allow TWRP to replace recovery at the end when you go to reboot system and you say no....The ROM should install le eco recovery ...

@codeworkx can you help us identified why OTA does not work even when backing up from twrp? I dont have the 19s full image as leeco only gave me the latest one.

xterminater07 said:
@codeworkx can you help us identified why OTA does not work even when backing up from twrp? I dont have the 19s full image as leeco only gave me the latest one.
Click to expand...
Click to collapse
I thought in earlier post you said they gave you 19s also...Would of been a useful tool
---------- Post added at 08:29 PM ---------- Previous post was at 08:06 PM ----------
xterminater07 said:
They also gave me 19s image but I'm like why use it. Oh by the way guys, LeEco's camera app sucks balls. I ended up using "A better camera unlocked" app and it's ten times better! HDR is amazing but it takes about 1-2 second so hold your hands still! Hehe... If anyone got better camera reccommendation let us know. I tried open camera as well, not good.
Click to expand...
Click to collapse
here i thought ya got 19s also

Nvidia Experience 5.2 ROM

I have not been able to update my shield tv 2015 16gb device to 5.2.
The device is rooted with latest 3.1.1 TWRP recovery. Each time I select upgrade with the stock settings it will reboot into recovery and won't update.
Does anyone have a link to the latest ROM or know where Nvidia stores the OTA file? I would rather flash the image my self if I can find get the ROM.
I'm sure this we'll help a few other people I can't be the only one with this issue. Need the 5.2 image not the 5.0.2 which is the previous version of Shield experience update.

you should not flash TWRP to your device reflash original recovery and remove su then try update again

BTDTGTTS Simply unrooting, and replacing TWRP with a Stock Recovery. Will not sadly be enough. The only way out is to Factory Reset. Which, in my case (Pro Owner), means a Two Hours of down time. While the Shield is busy away at nuking the /data Partition. Only after that will you be fully unrooted. Of course if you are using TWRP as your Recovery, you WILL have to replace it with a Stock Recovery for your Update to work.
It's a real PItA for just some extra (Non-working) Plex Channels, and making the needed edits to settings.db to prevent it from kicking iPlayer off after each Power Cycle / IP Address reset. (Though that last one... Has more legs on it then just the Plex Channels.)

Ichijoe said:
BTDTGTTS Simply unrooting, and replacing TWRP with a Stock Recovery. Will not sadly be enough. The only way out is to Factory Reset. Which, in my case (Pro Owner), means a Two Hours of down time. While the Shield is busy away at nuking the /data Partition. Only after that will you be fully unrooted. Of course if you are using TWRP as your Recovery, you WILL have to replace it with a Stock Recovery for your Update to work.
.)
Click to expand...
Click to collapse
i didnt know that :good:
but if he has TWRP installed couldnt he format data pation from TWRP thus saving hours of thumb twiddling

Ichijoe said:
BTDTGTTS Simply unrooting, and replacing TWRP with a Stock Recovery. Will not sadly be enough. The only way out is to Factory Reset. Which, in my case (Pro Owner), means a Two Hours of down time. While the Shield is busy away at nuking the /data Partition. Only after that will you be fully unrooted. Of course if you are using TWRP as your Recovery, you WILL have to replace it with a Stock Recovery for your Update to work.
It's a real PItA for just some extra (Non-working) Plex Channels, and making the needed edits to settings.db to prevent it from kicking iPlayer off after each Power Cycle / IP Address reset. (Though that last one... Has more legs on it then just the Plex Channels.)
Click to expand...
Click to collapse
Obviously thats a much longer and worse route.
afgok said:
you should not flash TWRP to your device reflash original recovery and remove su then try update again
Click to expand...
Click to collapse
I have upgraded the shield tv many times with OTA updates. Shouldn't need to be stock just to do this. So your saying root has more restrictions....
TWRP is much better than stock recovery, now it might not be finding the OTA update when it gets pushed to recovery.
The other option I mentioned in the original post was for manually selecting the OTA image with TWRP and flashing.
Does anyone one know where the temp folder is for OTA files or a direct link online?

On another thread looks like others are having this same issue with only this version 5.2.. ill just wait for the Dev Images to show up hopefully soon.

I unrooted but still got the same issue, it wont install. But I also have another issue, i can't restore my 2015 shield 16gb by using official recovery rom and official tutorials. It consistently fails to flash system.img and vendor.img by saying that the data is too large. The only way I got my system back was by flashing this file https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-ota-5-1-feb-17-zip-file-t3559062 through twrp

Diehardshorty said:
Obviously thats a much longer and worse route.
I have upgraded the shield tv many times with OTA updates. Shouldn't need to be stock just to do this. So your saying root has more restrictions....
TWRP is much better than stock recovery, now it might not be finding the OTA update when it gets pushed to recovery.
The other option I mentioned in the original post was for manually selecting the OTA image with TWRP and flashing.
Does anyone one know where the temp folder is for OTA files or a direct link online?
Click to expand...
Click to collapse
Again TWRP can not be used to flash an OTA Update. I mean sure feel free to knock yourself out. But, in the end it will fail. (Error 7 IIRC), As it is it seems that it will only work on a stock Recovery, and not on TWRP. I mean if it were this easy, everyone would be doing it. And again if the Update were working over TWRP, we wouldn't have a constant update loop. (e.g. Download Update, restart Shield, wait forever for the Shield to try (and, fail!) at applying said Update, rebooting, and wash rinse, repeat).
BTW: I never said that my way* was the 'best' way, or indeed the 'only' way. Its just the only way I know of to Nuke it from orbit all the time, everytime. And, yes it is a huge PITA. If you count a /system root as being more restrictive. In the case of Netflix making active noises about blocking rooted Devices. Then yes slowly I would say that rooting has more restrictions than stock.
*My way being to Factory wipe the Shield (Pro) which in the case of the Pro most likely means a Two plus Hours of dead time. I would assume it's much MUCH quicker for our 16GB eMMC Cousins though. But, not having One, I'm unable to confirm it.
P.s. You have also mentioned the fact that you have managed to update your rooted Shield TV on multiple occasions. Would you care to share this info with us? I for One would love to know how to do this. As having to Factory Reset the Device is a real time waster. Because after the reset, comes the rebuild. And, thats an even bigger *****.

Ichijoe said:
Again TWRP can not be used to flash an OTA Update. I mean sure feel free to knock yourself out. But, in the end it will fail. (Error 7 IIRC), As it is it seems that it will only work on a stock Recovery, and not on TWRP. I mean if it were this easy, everyone would be doing it. And again if the Update were working over TWRP, we wouldn't have a constant update loop. (e.g. Download Update, restart Shield, wait forever for the Shield to try (and, fail!) at applying said Update, rebooting, and wash rinse, repeat).
BTW: I never said that my way* was the 'best' way, or indeed the 'only' way. Its just the only way I know of to Nuke it from orbit all the time, everytime. And, yes it is a huge PITA. If you count a /system root as being more restrictive. In the case of Netflix making active noises about blocking rooted Devices. Then yes slowly I would say that rooting has more restrictions than stock.
*My way being to Factory wipe the Shield (Pro) which in the case of the Pro most likely means a Two plus Hours of dead time. I would assume it's much MUCH quicker for our 16GB eMMC Cousins though. But, not having One, I'm unable to confirm it.
P.s. You have also mentioned the fact that you have managed to update your rooted Shield TV on multiple occasions. Would you care to share this info with us? I for One would love to know how to do this. As having to Factory Reset the Device is a real time waster. Because after the reset, comes the rebuild. And, thats an even bigger *****.
Click to expand...
Click to collapse
Dirty flashing a dev image is they way I have managed to update my shield but right now the dev images are not updated, still the 5.1.0

If you're rooted, the right answer is to wait for Nvidia to release the 5.2 image.
If you absolutely need 5.2 right now for some reason, several people said that doing a factory restore worked. Just unrooting and restoring stock recovery won't do it, you need to do a full restore.

Diehardshorty said:
Dirty flashing a dev image is they way I have managed to update my shield but right now the dev images are not updated, still the 5.1.0
Click to expand...
Click to collapse
The Dev images are quite a bit different, and are also on an entirely different timeline to either the Preview, (Which I'm on), or the most current version.
But, yeah I could see how those would work. Alas mores the pitty that the rooted asspects of those Dev Images, only go as far as ADB, and not say a full /system wide root. Than again... It's probably for the best that way.
But, that doesn't really change the answer if you want / need to update (From root), than you are going to have to bite the big One, and run a Factory Reset. Which again, on the Pro, means a 2h+ reformating (zeroing out), of the /data Partition.

16gb version doesn't take as long to format but I've always remember flashing SuperSU.zip after ROM just incase. Short response for now at work.

Diehardshorty said:
The other option I mentioned in the original post was for manually selecting the OTA image with TWRP and flashing.
Does anyone one know where the temp folder is for OTA files or a direct link online?
Click to expand...
Click to collapse
Use to be here:
/data/data/com.nvidia.ota/app_download
You obviously need root to reach that folder...
If i have time i will upload later this small OTA update to MEGA.

I uploaded the 5.2 small update OTA for Shield TV 2015 (NON-PRO):
https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-small-update-ota-5-2-t3621886

sammarbella said:
I uploaded the 5.2 small update OTA for Shield TV 2015 (NON-PRO):
https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-small-update-ota-5-2-t3621886
Click to expand...
Click to collapse
Sweet thanks I'll give that a try from the sounds of it it might not work but I'll give a shot after work. Thanks

No luck flashing my own OTA zip I took it out of data\data\com.nvidia.ota flashed it with TWRT 3.1.1.
I might end up doing the factory restore then updating and root. Wouldn't mind a new clean OS

Diehardshorty said:
No luck flashing my own OTA zip I took it out of data\data\com.nvidia.ota flashed it with TWRT 3.1.1.
I might end up doing the factory restore then updating and root. Wouldn't mind a new clean OS
Click to expand...
Click to collapse
Check out https://forum.xda-developers.com/shield-tv/general/how-to-update-ota-5-2-2017-update-t3622540 just posted a guide on how to update

Cameron581 said:
Check out https://forum.xda-developers.com/shield-tv/general/how-to-update-ota-5-2-2017-update-t3622540 just posted a guide on how to update
Click to expand...
Click to collapse
Only difference there is that your using flashfire instead of TWRP. I can't see how that may work but worth a shot.

Diehardshorty said:
Only difference there is that your using flashfire instead of TWRP. I can't see how that may work but worth a shot.
Click to expand...
Click to collapse
Just make sure you flash the right update, and it's because the ota provided by the devs don't support ota due to device fingerprint issues along with partition finding stuff found inside the meta-inf, the reason you can't sideload the room via stock is because there is a check for modified system tables. Granted you could take out that comment and rezip it then it will fail for zip verification, after that I had tried to sign the package to regain that but then it failed due to it only signed the packages not the entire system. Long story short it's super duper picky and ChainFire made one that pleases all of the variables or ignores then.

Cameron581 said:
Just make sure you flash the right update, and it's because the ota provided by the devs don't support ota due to device fingerprint issues along with partition finding stuff found inside the meta-inf, the reason you can't sideload the room via stock is because there is a check for modified system tables. Granted you could take out that comment and rezip it then it will fail for zip verification, after that I had tried to sign the package to regain that but then it failed due to it only signed the packages not the entire system. Long story short it's super duper picky and ChainFire made one that pleases all of the variables or ignores then.
Click to expand...
Click to collapse
Ahhhhh that missing point for "error 7".
So the new app bypass that problem!
Thanks for posting it. :good:

Use TWRP to flash 8.1 update

I feel like I should know how to do this and I just can't think right now...
I have 8.0 and the latest TWRP installed. Root with Magisk as well. I want to update to 8.1 but I don't want to have to factory reset the phone by flashing 8.1 to it and then reflashing root & TWRP. There's a way to do this that I'm not thinking of, right?
I read another post about using FlashFire but regardless of where I put the factory image, the app doesn't see it. So I feel like I'm at a loss right now.
Am I missing something? Thanks in advance!

WyldOne91 said:
I feel like I should know how to do this and I just can't think right now...
I have 8.0 and the latest TWRP installed. Root with Magisk as well. I want to update to 8.1 but I don't want to have to factory reset the phone by flashing 8.1 to it and then reflashing root & TWRP. There's a way to do this that I'm not thinking of, right?
I read another post about using FlashFire but regardless of where I put the factory image, the app doesn't see it. So I feel like I'm at a loss right now.
Am I missing something? Thanks in advance!
Click to expand...
Click to collapse
This is how I upgraded to 8.1, my setup before I upgraded was the same as yours.
1. Bootloader and unlock_critical both unlocked?
2. Download and extract the factory image, and place all contents in your SDK platform tools folder.
3. Edit the flash-all.bat file and remove the -w in the last line of code. (This prevents your data from being wiped)
4. Double click the flash-all.bat file to start the process. It'll take a little while, so be patient.
5. Once it's done, get back to bootloader mode.
6. Flash the twrp.img file. This will take you to temporary twrp.
7. Once in twrp, flash the twrp.zip, then flash custom kernel.zip(optional) then flash your magisk.zip.
8. Reboot and done.
Couple of caveats, make sure your using a good USB transfer cable, and it's recommended to remove your finger print and/or password/pin, and uninstall any themes you have installed. Hope all goes well for you :good:

Badger50 said:
This is how I upgraded to 8.1, my setup before I upgraded was the same as yours.
1. Bootloader and unlock_critical both unlocked?
2. Download and extract the factory image, and place all contents in your SDK platform tools folder.
3. Edit the flash-all.bat file and remove the -w in the last line of code. (This prevents your data from being wiped)
4. Double click the flash-all.bat file to start the process. It'll take a little while, so be patient.
5. Once it's done, get back to bootloader mode.
6. Flash the twrp.img file. This will take you to temporary twrp.
7. Once in twrp, flash the twrp.zip, then flash custom kernel.zip(optional) then flash your magisk.zip.
8. Reboot and done.
Couple of caveats, make sure your using a good USB transfer cable, and it's recommended to remove your finger print and/or password/pin, and uninstall any themes you have installed. Hope all goes well for you :good:
Click to expand...
Click to collapse
Cool thank you I will give this a shot later tonight! One question, what is "unlock_critical?" I haven't seen that mentioned anywhere else before.

WyldOne91 said:
Cool thank you I will give this a shot later tonight! One question, what is "unlock_critical?" I haven't seen that mentioned anywhere else before.
Click to expand...
Click to collapse
The pic is from the Google factory image page. Unlock_critical must be performed on the P2XL to allow the bootloader to be updated with future monthly security or software updates. This does not apply to the standard P2. Be advised, this WILL wipe your phone. However, you really don't have much choice if you want to flash monthly factory images.

Badger50 said:
The pic is from the Google factory image page. Unlock_critical must be performed on the P2XL to allow the bootloader to be updated with future monthly security or software updates. This does not apply to the standard P2. Be advised, this WILL wipe your phone. However, you really don't have much choice if you want to flash monthly factory images.
Click to expand...
Click to collapse
Oh crap... I only ran the OEM unlock. Welp, looks like I'm going to end up wiping anyways. Thanks for the info though. This is definitely one of those situations where I assumed I knew what I was doing and ran with it without actually reading the process.

WyldOne91 said:
Oh crap... I only ran the OEM unlock. Welp, looks like I'm going to end up wiping anyways. Thanks for the info though. This is definitely one of those situations where I assumed I knew what I was doing and ran with it without actually reading the process.
Click to expand...
Click to collapse
No problem my friend. There's a lot to learn on these new pixel devices. There are plenty threads on these forum with tons of info on whatever topic you may have questions about. Just takes time, patience, lots of reading, and a willingness to learn :good:

WyldOne91 said:
Oh crap... I only ran the OEM unlock. Welp, looks like I'm going to end up wiping anyways. Thanks for the info though. This is definitely one of those situations where I assumed I knew what I was doing and ran with it without actually reading the process.
Click to expand...
Click to collapse
Since you are rooted, and already have the mindset that all is or will be lost you have the opportunity to try a couple options that if fail nothing lost...
After doing away with screen security and any themes, do Full backup in TWRP and also use TiBu to back up all your apps and then move them off the phone until after you do your thing.
After you do the critical unlock and get 8.1 installed and rooted you could try restoring the TWRP data partition and see what happens. Worst case it's either not booting or just acting funky. Do a factory wipe and not much lost.
Or... Use TiBu to save some time restoring all your apps. While I have had pretty good luck with restoring data on most apps, a few either won't restore or are boned in some way. Some other folks had a really hard time with restoring data so maybe just restore the apps without data. I run over 100 apps and have been through some version of this many times while playing around. With my crappy internet out here in the boonies it took 4 hours for google to restore all my apps and that's with hardly no data. It took about 20 minutes to restore most everything through TiBu. I would not restore data in the big initial bulk restore but instead go back and cherry pick the data restore on the things you need.
Again worst case all lost but you assumed that anyway and maybe you can save some time and effort if either option works.

Badger50 said:
No problem my friend. There's a lot to learn on these new pixel devices. There are plenty threads on these forum with tons of info on whatever topic you may have questions about. Just takes time, patience, lots of reading, and a willingness to learn :good:
Click to expand...
Click to collapse
Yeah for sure. I'm always willing to learn!
CyberpodS2 said:
Since you are rooted, and already have the mindset that all is or will be lost you have the opportunity to try a couple options that if fail nothing lost...
After doing away with screen security and any themes, do Full backup in TWRP and also use TiBu to back up all your apps and then move them off the phone until after you do your thing.
After you do the critical unlock and get 8.1 installed and rooted you could try restoring the TWRP data partition and see what happens. Worst case it's either not booting or just acting funky. Do a factory wipe and not much lost.
Or... Use TiBu to save some time restoring all your apps. While I have had pretty good luck with restoring data on most apps, a few either won't restore or are boned in some way. Some other folks had a really hard time with restoring data so maybe just restore the apps without data. I run over 100 apps and have been through some version of this many times while playing around. With my crappy internet out here in the boonies it took 4 hours for google to restore all my apps and that's with hardly no data. It took about 20 minutes to restore most everything through TiBu. I would not restore data in the big initial bulk restore but instead go back and cherry pick the data restore on the things you need.
Again worst case all lost but you assumed that anyway and maybe you can save some time and effort if either option works.
Click to expand...
Click to collapse
Yeah I actually already ran a backup with Titanium Backup and moved it to my PC last night just in case I did something stupid haha but I appreciate the tips!

Camera won't open; YouTube doesn't load

My Pixel 2XL is acting up starting this morning
- The camera app won't open, it crashes instantly. Other apps can't access the camera. I tried clearing the data, cache and restarting. Nothing has worked so far.
- YouTube is stuck in a load loop, all is see is the loading circle to infinity. I attempted to clear cache and data and install an older version. Again, nothing works.
- Restarting didn't solve anything.
- Both issues linger in safe mode.
Any ideas on wtf could be going on?

boeder9 said:
My Pixel 2XL is acting up starting this morning
- The camera app won't open, it crashes instantly. Other apps can't access the camera. I tried clearing the data, cache and restarting. Nothing has worked so far.
- YouTube is stuck in a load loop, all is see is the loading circle to infinity. I attempted to clear cache and data and install an older version. Again, nothing works.
- Restarting didn't solve anything.
Any ideas on wtf could be going on?
Click to expand...
Click to collapse
Sounds like you've got an unexplained, interesting and unwanted glitch! Are you full stock, or rooted?
Your only solution will likely be a factory reset, or possibly a dirty fastboot flash of the factory image so as not to wipe your data. You might even get by with just fastbooting the vendor image as well.

Badger50 said:
Sounds like you've got an unexplained, interesting and unwanted glitch! Are you full stock, or rooted?
Your only solution will likely be a factory reset, or possibly a dirty fastboot flash of the factory image so as not to wipe your data. You might even get by with just fastbooting the vendor image as well.
Click to expand...
Click to collapse
Full stock.
I want to avoid any resets tbh.
Could the OTA Monthly Update solve anything?

boeder9 said:
Full stock.
I want to avoid any resets tbh.
Could the OTA Monthly Update solve anything?
Click to expand...
Click to collapse
It's definitely worth a try. Just like fastbooting the factory image without the -w :good:

Badger50 said:
It's definitely worth a try. Just like fastbooting the factory image without the -w :good:
Click to expand...
Click to collapse
I guess I'll wait for the Sept update, if that doesn't work, I'll try the manual flashing
Sent from my Pixel 2 XL using Tapatalk

boeder9 said:
I guess I'll wait for the Sept update, if that doesn't work, I'll try the manual flashing
Click to expand...
Click to collapse
The job of flashing the factory image while saving data is super easy. If you have a pc and a half hour your golden. If you wanna give it a go, let us know and one of us can walk you through it if you have any concerns...
Sent from my Pixel 2 XL using XDA Labs

Even i have the same camera issue. It suddenly stopped working. Some times it does start after a few tries if i hold it in landscape mode. But mostly it keeps crashing and doesn't even allow other apps to access camera.

So a quick follow-up. Here is what i've done so far:
- Cleared storage/cache and uninstalled the camera updates
- Installed Android 10
- Updated to Camera 7.0 Beta
- Booted into safe mode.
None of these actions solved the issue.
I then resetted my phone (2 days ago) and that seemed to have solved the problem. However, starting a few minutes ago and while I was taking photos, I again lost focus in the lens and the app crashed.
What could be the issue? It seems its the focus is problematic though it worked for a good while. Surely it isn't hardware as the camera worked for ~40 hours after resetting.

boeder9 said:
What could be the issue? It seems its the focus is problematic though it worked for a good while. Surely it isn't hardware as the camera worked for ~40 hours after resetting.
Click to expand...
Click to collapse
Just because it worked correctly for around 40 hours after a reset doesn't mean that you can rule out hardware issues as a culprit. Especially since you have done everything you possibly could on the software end and it hasn't helped.

Strephon Alkhalikoi said:
Just because it worked correctly for around 40 hours after a reset doesn't mean that you can rule out hardware issues as a culprit. Especially since you have done everything you possibly could on the software end and it hasn't helped.
Click to expand...
Click to collapse
You're absolutely right. I did another reset (this time without restoring from backup) and the camera doesn't open at all. I'm hoping its a OS bug.
Thank god the Pixel 4 will be released in 4 weeks.

CyberpodS2 said:
The job of flashing the factory image while saving data is super easy. If you have a pc and a half hour your golden. If you wanna give it a go, let us know and one of us can walk you through it if you have any concerns...
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
I have exactly the same problem that they report, it does not open cameras or YouTube.
Can you give me the steps to upload a factory image?
Regards