[Q] Force OTA udpate? - Shield Q&A

Hi,
I downloaded and attempted to install OTA update 63, on my Shield running stock system updated to 59, unlocked, rooted and having flashed CWM recovery.
CWM failed to flash the 63 OTA because of the blob flashing issue, as I read on the CWM thread, so I flashed back the stock recovery. However now the system updater always finds that my OS is up-to-date even though I am still on OTA 59. I tried to wipe data for a couple of Nvidia apps (Nvidia services and system updater) to no avail. Any ideas on what to do to force OTA update? I'd rather avoid factory resetting just for that...
Cheers!

Nikojiro said:
Hi,
I downloaded and attempted to install OTA update 63, on my Shield running stock system updated to 59, unlocked, rooted and having flashed CWM recovery.
CWM failed to flash the 63 OTA because of the blob flashing issue, as I read on the CWM thread, so I flashed back the stock recovery. However now the system updater always finds that my OS is up-to-date even though I am still on OTA 59. I tried to wipe data for a couple of Nvidia apps (Nvidia services and system updater) to no avail. Any ideas on what to do to force OTA update? I'd rather avoid factory resetting just for that...
Cheers!
Click to expand...
Click to collapse
I'm having the same issue. No idea, we might just have to wait a while.

Delete Data from Google Framework Apk and then start the Update Checker.

UNCUT88RAW said:
Delete Data from Google Framework Apk and then start the Update Checker.
Click to expand...
Click to collapse
Aah didn't think of that trick, it works, <thank you> pressed :laugh:

Could someone please give me a link to the Stock Recovery and maybe a description what the best way is to flash it instead of the Custom Recovery? Thanks ...

I have had no problems flashing updates with ClockWorkMOD revocery.
However if you have the 1.0 version from http://forum.xda-developers.com/showthread.php?t=2390389 the update will fail with an error.
1.0 had a name wrong that makes it think the update are for a different device.
the command to flash the stock recovery (if every thing is in the correct place) is "fastboot flash recovery recovery.img"

chevyowner said:
1.0 had a name wrong that makes it think the update are for a different device.
Click to expand...
Click to collapse
Ah, maybe this is causing the error! Okay, I will try to flash 1.1 before going back to stock recovery.
Unfortunately the link for v1.1 is down. Would you be able to mirror it for me please?
Thanks!

fquadrat said:
Ah, maybe this is causing the error! Okay, I will try to flash 1.1 before going back to stock recovery.
Unfortunately the link for v1.1 is down. Would you be able to mirror it for me please?
Thanks!
Click to expand...
Click to collapse
When I was checking to see if I had 1.1 I found the naming error is still there.
This brings me to my next point. I had edited the ramdisk on 1.0 to correct the naming error, and not updated to 1.1
Here is a link to 1.1 with the edited ramdisk.
Update
I messed up the link in Google drive i think i fixed it now.

chevyowner said:
Here is a link to 1.1 with the edited ramdisk.
Click to expand...
Click to collapse
Unfortunately I think there is something broken with your attached file. After flashing it, I can't access the recovery anymore. The background light of the screen is constantly turning on and off but nothing appears on the screen. Fortunately I can still access Fastboot and Android.

fquadrat said:
Unfortunately I think there is something broken with your attached file. After flashing it, I can't access the recovery anymore. The background light of the screen is constantly turning on and off but nothing appears on the screen. Fortunately I can still access Fastboot and Android.
Click to expand...
Click to collapse
Try this it "should" be the recovery I currently have flashed
EDIT
It instead of flashing the recovery to test it, use "fastboot boot recovery.img"

chevyowner said:
It instead of flashing the recovery to test it, use "fastboot boot recovery.img"
Click to expand...
Click to collapse
Sorry, I just flashed stock recovery and my Shield is installing Android 4.3 right this second ...

chevyowner said:
Try this it "should" be the recovery I currently have flashed
EDIT
It instead of flashing the recovery to test it, use "fastboot boot recovery.img"
Click to expand...
Click to collapse
I really need that img. Going to test now. Thanks!
This is the one that can install zips without the error right?

desertflame said:
I really need that img. Going to test now. Thanks!
This is the one that can install zips without the error right?
Click to expand...
Click to collapse
should be

Related

Need Stock Recovery image please?

can someone send the stock recovery image for the 16gb wifi version please? cwm is not letting me flash at all for some reason. got my tablet working (not on loop anymore), but wifi stops working every 3 minutes or so (even though it says its still connected). anybody run into this problem ? at any rate hoping to flash via original recovery to the latest update... any help appreciated.
johnnobts said:
can someone send the stock recovery image for the 16gb wifi version please? cwm is not letting me flash at all for some reason. got my tablet working (not on loop anymore), but wifi stops working every 3 minutes or so (even though it says its still connected). anybody run into this problem ? at any rate hoping to flash via original recovery to the latest update... any help appreciated.
Click to expand...
Click to collapse
I have not seen the stock recovery.img posted anywhere. But you can flash the OTAs via CWM. Go to post #20 here > http://forum.xda-developers.com/shi...ery-cwm-recovery-nvidia-shield-t2848064/page2
johnnobts said:
can someone send the stock recovery image for the 16gb wifi version please? cwm is not letting me flash at all for some reason. got my tablet working (not on loop anymore), but wifi stops working every 3 minutes or so (even though it says its still connected). anybody run into this problem ? at any rate hoping to flash via original recovery to the latest update... any help appreciated.
Click to expand...
Click to collapse
Here is the stock recovery, extracted from link in this thread >http://forum.xda-developers.com/nvidia-shield/general/shield-tablet-source-factory-t2840406
Note that I haven't tested it. Try it at your own risk. Fastboot flash....
Edit: tested and found not working. Removed.
I make a back up of the stock recovery in flashify but I don't now how to share in a mesege , some one explain me how please thanks
Sent from my SHIELD Tablet using XDA Free mobile app
rene130313 said:
I make a back up of the stock recovery in flashify but I don't now how to share in a mesege , some one explain me how please thanks
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Use a web browser instead of the XDA app. When you create or reply to a message, you will see several "buttons" at the top. One of them is a paperclip icon. Click on that one to attach a file.
rene130313 said:
I make a back up of the stock recovery in flashify but I don't now how to share in a mesege , some one explain me how please thanks
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Would you mind attaching a copy of your recovery.img?
Looks like they have the stock images up now @ nvidia.
https://developer.nvidia.com/develop4shield#tablet-osr
phobic99 said:
Looks like they have the stock images up now @ nvidia.
https://developer.nvidia.com/develop4shield#tablet-osr
Click to expand...
Click to collapse
Unfortunately, you need to be a registered developer to download.
Stock recovery attached. Confirmed working on my device.
cam30era said:
Stock recovery attached. Confirmed working on my device.
Click to expand...
Click to collapse
Is this recovery compatible with the LTE version?
dgjenkins said:
Is this recovery compatible with the LTE version?
Click to expand...
Click to collapse
I don't know. I wouldn't use it without assurance from someone who knows for sure. Sorry I can't help more.
just register as a developer, no strings attached, just create an account and you can download all os recovery images
i moved up all the way to 2.2.1, then reinstalled 1.2.1 because i wasn't liking lollipop
also unlocked the bootloader, flashed CWM and rooted
now i want to try the BitO kernel, which is only available to 2.2.1, so installed the 2.1 update (through CWM, as i forgot to flash the stock recovery for 1.2.1)
now i try to install 2.2, but recovery gives me an error
flashed CWM again, doesn't want to flash the OTA
flashed the 2.1 stock recovery, it starts the update but almost immediately gives me an error
yes i could flash the 2.2.1 OS recovery image, but then i would lose all my data....
EDIT: never mind, fixed it, flash boot.img, recovery.img, erased system, flashed system img, all from 2.1 update zip file, reboot, now 2.2 is installing through OTA
JarlSX said:
just register as a developer, no strings attached, just create an account and you can download all os recovery images
i moved up all the way to 2.2.1, then reinstalled 1.2.1 because i wasn't liking lollipop
also unlocked the bootloader, flashed CWM and rooted
now i want to try the BitO kernel, which is only available to 2.2.1, so installed the 2.1 update (through CWM, as i forgot to flash the stock recovery for 1.2.1)
now i try to install 2.2, but recovery gives me an error
flashed CWM again, doesn't want to flash the OTA
flashed the 2.1 stock recovery, it starts the update but almost immediately gives me an error
yes i could flash the 2.2.1 OS recovery image, but then i would lose all my data....
EDIT: never mind, fixed it, flash boot.img, recovery.img, erased system, flashed system img, all from 2.1 update zip file, reboot, now 2.2 is installing through OTA
Click to expand...
Click to collapse
Just curious, what was it about 2.2.1 that you didn't like? What was wrong with lolipop?
i prefered the way the notification pulldown worked in KK, some settings were quicker to reach
not too fond of the navigation buttons either
it's weird i know, they're in the same location, have the same function, but they just look wrong
look too much like the symbols on a Playstation controller
and GameGuardian doesn't work on Lollipop (yet), but by going back to KK i managed to fix what i wanted to fix
i hope nvidia gets it right this time with the 5.1 update, disabling swap would be nice
hmm, seems lag isn't gone at all...
was playing a bit of Sky Force 2014 yesterday, holy crap the lag
also noticed other apps were lagging
sure hope 5.1 will fix this

Problems with downgrading to KitKat

Hey guys, I'm trying to downgrade to KitKat after all the issues Lollipop is giving me and the incompatible apps I'm trying to run.
I am following instructions here but I came across a problem when flashing the system.img file.
The error it gives me is:
FAILED (remote: Insufficient memory.)
I can't flash over system and can not boot.
What am I missing? I was rooted and my bootloader unlocked prior to starting and I tried with the factory recovery and the 1.2.1 recovery image.
Edit: My issue has been solved. Flashing the Full OTA.zip file will install KitKat over Lollipop. No need to manually flash each file through fastboot. I wish guides would tell you that instead.
BlackDave said:
Hey guys, I'm trying to downgrade to KitKat after all the issues Lollipop is giving me and the incompatible apps I'm trying to run.
I am following instructions here but I came across a problem when flashing the system.img file.
The error it gives me is:
FAILED (remote: Insufficient memory.)
I can't flash over system and can not boot.
What am I missing? I was rooted and my bootloader unlocked prior to starting and I tried with the factory recovery and the 1.2.1 recovery image.
Click to expand...
Click to collapse
I don't know why that wouldn't work. Have you tried just downloading the image from nvidia HERE?
I'm assuming wifi since your sig says 16GB
Keithn said:
I don't know why that wouldn't work. Have you tried just downloading the image from nvidia HERE?
I'm assuming wifi since your sig says 16GB
Click to expand...
Click to collapse
Those are the same files as the ones I downloaded in the other thread.
I got my tablet working again on Lollipop 5.0.1 but that's not where I want to be. I've searched about my error message but most threads I found went unanswered.
Your best bet might just be to try getting a full OTA and flashing it through cwm or something. I'll try with mine when I have some time to backup and flash, probably later tomorrow. If I find anything out I'll post.
Sent from my SHIELD Tablet
BlackDave said:
I got my tablet working again on Lollipop 5.0.1 but that's not where I want to be. I've searched about my error message but most threads I found went unanswered.
Click to expand...
Click to collapse
I just flashed the images and booted.
Did you accidentally try flashing to the wrong place, such as flashing to boot( which would be too small) instead of system? Did you do all of the commands yourself or use the .bat? My shield disconnected after doing the boot.img and system.img for some reason, so I had to select fastboot protocol to reboot the bootloader and continue to flash the userdata.img, blob, and battery.dtb.
was your tablet internal memory full?, try wipping data and chace and you could use the script that the original Nvidia recovery image has zipped. I went up and down like 3 times, im in kitkat right now and not experiencing any problem.
Iams1002 said:
was your tablet internal memory full?, try wipping data and chace and you could use the script that the original Nvidia recovery image has zipped. I went up and down like 3 times, im in kitkat right now and not experiencing any problem.
Click to expand...
Click to collapse
No I wipped internal data since I keep everything on external and it still didn't work.
Keithn said:
I just flashed the images and booted.
Did you accidentally try flashing to the wrong place, such as flashing to boot( which would be too small) instead of system? Did you do all of the commands yourself or use the .bat? My shield disconnected after doing the boot.img and system.img for some reason, so I had to select fastboot protocol to reboot the bootloader and continue to flash the userdata.img, blob, and battery.dtb.
Click to expand...
Click to collapse
So I should just flash the ota.zip?
Also i did everything like the guide. I flashed boot to boot, recovery to recovery. The only thing that gave me an error was system. Userdata, blob, and battery also flashed successfully. After that didn't work, I also tried the .bat and that didn't work either. Flashing the 5.0.1 update got my tablet running again.
BlackDave said:
No I wipped internal data since I keep everything on external and it still didn't work.
So I should just flash the ota.zip?
Also i did everything like the guide. I flashed boot to boot, recovery to recovery. The only thing that gave me an error was system. Userdata, blob, and battery also flashed successfully. After that didn't work, I also tried the .bat and that didn't work either. Flashing the 5.0.1 update got my tablet running again.
Click to expand...
Click to collapse
If you can find a full ota.zip for update 1.2.1 I'd try that. I'm not sure why you would be having this issue. The only other things I can say to try is redownloading and rebooting the boot loader (select fastboot protocol) between images in case something funny is happening there. Let us know how you end up doing.
Sent from my HTC M8
Keithn said:
If you can find a full ota.zip for update 1.2.1 I'd try that. I'm not sure why you would be having this issue. The only other things I can say to try is redownloading and rebooting the boot loader (select fastboot protocol) between images in case something funny is happening there. Let us know how you end up doing.
Sent from my HTC M8
Click to expand...
Click to collapse
I flashed the 1.2.1 OTA update and it worked. The first time I tried, I did using the TWRP recovery but for some reason, that recovery fails to flash OTAs, so I went with CWM and flashed the 2.1 update and all worked again. After a while, I got tired of all the issues lollipop gave me so that's why I tried following that guide to downgrade.
In the end, using CWM and flashing the OTA is the best way to go. Thank you all for you help.

Moto G (1st gen) OTA to Lollipop fails

Hi folks, so, I received OTA update for my Moto G (XT1032).
Phone was rooted (I did unroot from SuperSU). Also, I've re-installed Stock recovery (to make sure) and wiped cache/dalvik.
But, update still fails.
I don't have much root-related soft (like Xposed etc) installed - so pretty sure this should not cause an issue.
But still, update fails.
Any ideas how to troubleshoot/make it work? Maybe installing OTA somehow from recovery (custom one, TWRP)?
Any comments - much appreciated. I guess I'm not alone in this, but still...
Thanks
Same problem here
Ulverinho said:
Hi folks, so, I received OTA update for my Moto G (XT1032).
Phone was rooted (I did unroot from SuperSU). Also, I've re-installed Stock recovery (to make sure) and wiped cache/dalvik.
But, update still fails.
I don't have much root-related soft (like Xposed etc) installed - so pretty sure this should not cause an issue.
But still, update fails.
Any ideas how to troubleshoot/make it work? Maybe installing OTA somehow from recovery (custom one, TWRP)?
Any comments - much appreciated. I guess I'm not alone in this, but still...
Thanks
Click to expand...
Click to collapse
Have to install stock ROM again then update it via ota. Could also try flashing an ota update file via the official recovery of your phone.
A_Bunny said:
Have to install stock ROM again then update it via ota. Could also try flashing an ota update file via the official recovery of your phone.
Click to expand...
Click to collapse
Yep, my guess was the same. As per official recovery - I'll try adb sideload, but first time it couldn't find phone (all drivers installed and up-to-date).
http://forum.xda-developers.com/moto-g/help/driver-fastboot-falcon-s-t2820848
This error pops up - I can't find solution also...
Ulverinho said:
Yep, my guess was the same. As per official recovery - I'll try adb sideload, but first time it couldn't find phone (all drivers installed and up-to-date).
http://forum.xda-developers.com/moto-g/help/driver-fastboot-falcon-s-t2820848
This error pops up - I can't find solution also...
Click to expand...
Click to collapse
Install the recovery with fastboot not adb.
A_Bunny said:
Install the recovery with fastboot not adb.
Click to expand...
Click to collapse
Well, I might misunderstood, but:
I have official recovery (fastboot is mode of it, I guess, when U press Power+volume key?)
I've read about adb sideload zip_name_of_OTA.zip
I don't know any other way to install OTA apart from let phone handle it OR adb sideload.
Ulverinho said:
Well, I might misunderstood, but:
I have official recovery (fastboot is mode of it, I guess, when U press Power+volume key?)
I've read about adb sideload zip_name_of_OTA.zip
I don't know any other way to install OTA apart from let phone handle it OR adb sideload.
Click to expand...
Click to collapse
Just load it onto your phone before you flash it. Your ROM does work.
A_Bunny said:
Just load it onto your phone before you flash it. Your ROM does work.
Click to expand...
Click to collapse
Load ZIP of OTA on SD Card and install it from Recovery? Will it work?
Ulverinho said:
Load ZIP of OTA on SD Card and install it from Recovery? Will it work?
Click to expand...
Click to collapse
It may work if it is the stock recovery.
A_Bunny said:
It may work if it is the stock recovery.
Click to expand...
Click to collapse
Got this, screenshot in attachment.
Fingerprints are wrong. In build.prop - I can see it's fine, fingerprint of current 4.4.4. - matches expected.
But as soon as update starts - it says that 4.4.2 is fingerprint of my OS. Bollocks.
Edited OTA zip, edited some metadata file...
Why it won't install on pretty clean phone - I can't understand...Previous installs of OTA went fine with root etc.
Ulverinho said:
Got this, screenshot in attachment.
Fingerprints are wrong. In build.prop - I can see it's fine, fingerprint of current 4.4.4. - matches expected.
But as soon as update starts - it says that 4.4.2 is fingerprint of my OS. Bollocks.
Edited OTA zip, edited some metadata file...
Why it won't install on pretty clean phone - I can't understand...Previous installs of OTA went fine with root etc.
Click to expand...
Click to collapse
Well the only thing I would recommend would be to install the stock system though fastboot manualy.
Ulverinho said:
Hi folks, so, I received OTA update for my Moto G (XT1032).
Phone was rooted (I did unroot from SuperSU). Also, I've re-installed Stock recovery (to make sure) and wiped cache/dalvik.
But, update still fails.
I don't have much root-related soft (like Xposed etc) installed - so pretty sure this should not cause an issue.
But still, update fails.
Any ideas how to troubleshoot/make it work? Maybe installing OTA somehow from recovery (custom one, TWRP)?
Any comments - much appreciated. I guess I'm not alone in this, but still...
Thanks
Click to expand...
Click to collapse
i feel ya same thing here, than i tryed installing a stock lollipop from here via twrp witch ended up messing my phone with failing the procedure wondered around couldnt revert to stock since im a noob and didnt even backed up the rom,but at the and of the day thank god for the cm12.1 finally menaged to make my phone running again at least
Greetings, I have the same problem, it is the last screen that appears when you install the update, and then restarts it goes off the screen update error ...
To anyone having issues:
1. Make sure you're on completely stock 4.4.4 (Refer to http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and use only untouched 4.4.4 version for your phone if you have to reflash before continuing)
2. Make sure you're on stock recovery (Refer to http://forum.xda-developers.com/showthread.php?t=2649763)
*Uninstall XPOSED if using it
3. I personally let update run on its own after reverting everything to stock.
fusionice said:
To anyone having issues:
1. Make sure you're on completely stock 4.4.4 (Refer to http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and use only untouched 4.4.4 version for your phone if you have to reflash before continuing)
2. Make sure you're on stock recovery (Refer to http://forum.xda-developers.com/showthread.php?t=2649763)
*Uninstall XPOSED if using it
3. I personally let update run on its own after reverting everything to stock.
Click to expand...
Click to collapse
Yeah, that's the better way.
But I guess, I can install Stock 5.* straight away after wiping? Why bother about OTA, if there is ROM available?
fusionice said:
To anyone having issues:
1. Make sure you're on completely stock 4.4.4 (Refer to http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and use only untouched 4.4.4 version for your phone if you have to reflash before continuing)
2. Make sure you're on stock recovery (Refer to http://forum.xda-developers.com/showthread.php?t=2649763)
*Uninstall XPOSED if using it
3. I personally let update run on its own after reverting everything to stock.
Click to expand...
Click to collapse
Yep.
The solution is backup data, restore stock last firmware using fastboot guide posted in this forum and not even update apps (cancel gmail registration and everything it asks when it first starts) ONLY update motorola update services so you can get the ota again an install it. If you have the ota downloaded you can flash it through recovery but using the last recovery version (.61) and of course last firmware version. If you guys flash it all through fastboot, it should install w/o any problems.

update to latest OTA and recovery issue

HI all, I have CM12 installed on my rooted phone and this morning when I switched it on, I got a message saying:
"WARNING: Update Cyanogen recovery is disabled. This may cause issues with updating your device. Please enable Update Cyanogen recovery in developer options"
Now, that option is off because I have my custom recovery TWRP installed on the phone, I'd like to keep that and I don't want to reinstall it after the update, so I believe I should ignore the message, but what I wanted to check with you guys is whether ignoring it will in fact cause any issues as this is the first time ever I've seen this message (this update by the way I think is the first one after installing CM12).
Any idea?
thanks
Disregard the message.
Thanks Heisenberg,
I did that but when the phone restarts trying to install the update, it goes straight into recovery mode (TWRP) and from there I don't think I can install the update, as none of the options seem to allow me to do so, see screenshot http://s23.postimg.org/6d6s7wyq3/IMG_20150625_135453.jpg
All right, I downloaded the zip from here http://cyanogen-ota-bacon.somee.com/ and tried to flash it from TWRP, but I get an error, screenshot here http://s28.postimg.org/zb06wtcpp/OTA_error.jpg, any idea why?
Same here, got an error in TWRP logs that prevented the update to install.
I'd like to avoid reflashing stock recovery only to install the update...
Heres the log: http://s29.postimg.org/njqqqlfc7/Screenshot_2015_06_25_08_49_42.png
Seems something related to outdated "build fingerprint" my device has currently 12.0-YNG1TAS17L
I guess the alternative would be to do it thru Cyanogen Recovery, but let's see what more knowledgeable members have to say as, like you, I don't want to have to reinstall TWRP and SU just for the sake of the update
Looks like you cant use the official update with TWRP. Either flash it via cyanogen recovery then flash back TWRP, or use a differnt zip for update not the official
Thanks for clarifying that davebugyi, then so be it, I'll do it thru cyanogen recovery and then reflash TWRP and probably SU as well
thanks
davebugyi said:
Looks like you cant use the official update with TWRP. Either flash it via cyanogen recovery then flash back TWRP, or use a differnt zip for update not the official
Click to expand...
Click to collapse
Ah, sorry forgot to ask, is there an unofficial update? If so where do I get it from?
davebugyi said:
Looks like you cant use the official update with TWRP. Either flash it via cyanogen recovery then flash back TWRP, or use a differnt zip for update not the official
Click to expand...
Click to collapse
duratto said:
Ah, sorry forgot to ask, is there an unofficial update? If so where do I get it from?
Click to expand...
Click to collapse
For example here: http://forum.xda-developers.com/showthread.php?t=2810365
thanks! Ah OK I see so that's the whole ROM there as opposed to just an update
davebugyi said:
For example here: http://forum.xda-developers.com/showthread.php?t=2810365
Click to expand...
Click to collapse
Do you mean flashing only this update found at the end of the first post?
YNG1TAS2I3 Radio, etc - Mirror - Same as YNG1TAS0YL
md5 - 6d5db5af6c92b814b9a0ebd18341dd8e
Click to expand...
Click to collapse
Is it safe to flash only that zip from TWRP over the stock Cyanogen OS?
Yes, but if I'm not mistaken, judging from the file size, that's the whole ROM
tsnake said:
Do you mean flashing only this update found at the end of the first post?
Is it safe to flash only that zip from TWRP over the stock Cyanogen OS?
Click to expand...
Click to collapse
The file I quoted is not a whole ROM, it's 31 MB.
AH OK, sorry I thught you referred to the 500mb file
Apparently even by enabling cyanogen recovery, I still can't get the updated installed as the phone keeps rebooting in the TWRP recovery, which is very odd.
I'm having the same issue. Anyone?
Got the same problem. Any idea?
duratto said:
Apparently even by enabling cyanogen recovery, I still can't get the updated installed as the phone keeps rebooting in the TWRP recovery, which is very odd.
Click to expand...
Click to collapse
Bump for a fix?
Juergen1337 said:
Got the same problem. Any idea?
Click to expand...
Click to collapse
The solution seems to be installing the new ROM provided. Related problem here http://forum.xda-developers.com/oneplus-one/help/twrp-cm-android-version-mismatch-t3147658

Update received - flashing via TWRP?

Hey there fellow U11 Users,
I just received the update concerning 60fps HD-Video etc. I use TWRP so the update can't be installed by itself. So I have two questions:
A
Where do I find the update file. I looked around a lot but couldn't locate it.
B
Once found, can I just flash it with TWRP?
Thanks in advance!
Dito13 said:
Hey there fellow U11 Users,
I just received the update concerning 60fps HD-Video etc. I use TWRP so the update can't be installed by itself. So I have two questions:
A
Where do I find the update file. I looked around a lot but couldn't locate it.
B
Once found, can I just flash it with TWRP?
Thanks in advance!
Click to expand...
Click to collapse
See here: https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048/page63
Alright, thanks! :good: That only leaves the first question unanswered.
Dito13 said:
Alright, thanks! :good: That only leaves the first question unanswered.
Click to expand...
Click to collapse
/data/data/com.htc.updater/files
btw...twrp can install the update but you need to flash the firmware.zip inside the ota manually
Thank you kindly!
OMJ said:
/data/data/com.htc.updater/files
btw...twrp can install the update but you need to flash the firmware.zip inside the ota manually
Click to expand...
Click to collapse
Just to be clear: I only flash the firmware.zip manually via TWRP or do I need to flash the whole ota?
Sorry for the question. I mostly handled Nexus devices...
Dito13 said:
Just to be clear: I only flash the firmware.zip manually via TWRP or do I need to flash the whole ota?
Sorry for the question. I mostly handled Nexus devices...
Click to expand...
Click to collapse
twrp will install the ota zip but it wont install the firmware.zip inside, you have to extract & manually install from download mode
grrr.... I tried following your suggestions, but recieved error 7 in TWRP. Can you help me in the right direction?
Dito13 said:
grrr.... I tried following your suggestions, but recieved error 7 in TWRP. Can you help me in the right direction?
Click to expand...
Click to collapse
list your steps your using to install the ota via twrp....personally, I let the system initiate the install (booted into OS) as if I was 100% stock, once twrp loads, it automatically installs except for the firmware.zip
more details here...
OK, I am a Noob to the HTC world. I am used to easy flashing/rooting/etc. on Nexus devices.
TWRP doesn't do anything after accepting the ota. When I try to install the OTA via TWRP I receive Error 7. I worked my way through a lot of guides here on XDA concerning manual OTA installing. One thing I tried was flashing back to stock recovery which I found in the firmware.zip of the OTA in bootloader mode. That failed also ("FAILED (remote: not allowed on PRODUCTION device).
Edit: The device has obviously an unlocked bootloader, s-on, rooted via magisk and is a DGLU device, software number 1.16.400.5
Are you on an Untouched System Image? Completely stock ROM? While it is great we can flash the OTA in TWRP, the system stills needs to be stock, and of course will still have to fastboot firmware.
schmeggy929 said:
Are you on an Untouched System Image? Completely stock ROM? While it is great we can flash the OTA in TWRP, the system stills needs to be stock, and of course will still have to fastboot firmware.
Click to expand...
Click to collapse
Yes, everything is stock.
I managed to flash the stock recovery now. I didn't remember to use the download mode /sorry. Then Then I checked for the ota again, downloaded it and tried to apply but I landed in the stock recovery with the red exclamation mark and then nothing happened.
Dito13 said:
Yes, everything is stock.
I managed to flash the stock recovery now. I didn't remember to use the download mode /sorry. Then Then I checked for the ota again, downloaded it and tried to apply but I landed in the stock recovery with the red exclamation mark and then nothing happened.
Click to expand...
Click to collapse
re-flash twrp and try it again.
schmeggy929 said:
re-flash twrp and try it again.
Click to expand...
Click to collapse
Same result unfortunately. TWRP hands out Error 7 and "system partition has unexpected contents" or something like that although I didn't do any tinkering with the stock rom. I flashed Magisk and did a backup before and that was all.
Dito13 said:
Same result unfortunately. TWRP hands out Error 7 and "system partition has unexpected contents" or something like that although I didn't do any tinkering with the stock rom. I flashed Magisk and did a backup before and that was all.
Click to expand...
Click to collapse
Only thing I would say is start fresh. Backup all the data for your apps first. Flash the RUU, Take the OTA and reinstall all your apps.
schmeggy929 said:
Only thing I would say is start fresh. Backup all the data for your apps first. Flash the RUU, Take the OTA and reinstall all your apps.
Click to expand...
Click to collapse
Thanks again - seems to have worked. It will be interesting to see which problems occur with the Android Oreo update which was announced till the end of the year by HTC

Categories

Resources