Related
I've got stock, odexed....am rooted. That's it. Got the update, trying to flash with TWRP and get "system/build.prop has unexpected contents" error. Can't install the update.
WHY????? It's killin' me!
Thanks.
velveteen71 said:
I've got stock, odexed....am rooted. That's it. Got the update, trying to flash with TWRP and get "system/build.prop has unexpected contents" error. Can't install the update.
WHY????? It's killin' me!
Thanks.
Click to expand...
Click to collapse
you apparently have a modified build.prop. You probably will have to re-flash system.img to apply the OTA.
or find what was changed in build.prop and revert the change.
If you installed ANY modifications (dalvik mod, camera mod, center clock, dpi changes, ANYTHING) than it will not flash.
Synyster06Gates said:
If you installed ANY modifications (dalvik mod, camera mod, center clock, dpi changes, ANYTHING) than it will not flash.
Click to expand...
Click to collapse
Hey guys, got (what I believe is) a similar issue.
the error message I'm getting when I try to flash the update (or sideload it) is "EMMC:/dev/block/platform/msm_sdcc.1/by-name/bootand a huge string of characters ending with the end quote that follows)" has unexpected contents.
I've flashed back to stock krt16m, bootloader is still unlocked with cwm recovery, and I still get this error. The only modifications I had made were flashing the bricked-kernel hammerhead and enabling doubletap to wake, also installed xposed framework with gravitybox and advanced power options.
I flashed the uninstall file for bricked-kernel hammerhead (which was a boot.img so assuming it was this and not xposed?) but I'm still unable to flash the update to 4.4.1
suggestions? is there a way to flash a new boot.img? I'm a relative beginner.. I'm unable to track down a link that has a stock boot.img, I'm not sure if this is part of the factory image but I'm assuming not if I'm still having this issue..
thank you for any input!
desucca said:
Hey guys, got (what I believe is) a similar issue.
the error message I'm getting when I try to flash the update (or sideload it) is "EMMC:/dev/block/platform/msm_sdcc.1/by-name/bootand a huge string of characters ending with the end quote that follows)" has unexpected contents.
I've flashed back to stock krt16m, bootloader is still unlocked with cwm recovery, and I still get this error. The only modifications I had made were flashing the bricked-kernel hammerhead and enabling doubletap to wake, also installed xposed framework with gravitybox and advanced power options.
I flashed the uninstall file for bricked-kernel hammerhead (which was a boot.img so assuming it was this and not xposed?) but I'm still unable to flash the update to 4.4.1
suggestions? is there a way to flash a new boot.img? I'm a relative beginner.. I'm unable to track down a link that has a stock boot.img, I'm not sure if this is part of the factory image but I'm assuming not if I'm still having this issue..
thank you for any input!
Click to expand...
Click to collapse
Is Bricked the only kernel you've used? Or did you try Franco as well? Francos modifies a few files that need to be fixed before you can flash the update - even if you flashed a stock boot.img.
If you haven't, try the stock boot.img from http://forum.xda-developers.com/showthread.php?t=2513701
Got the same message. Flash the stock 4.4 (not 4.4.1) boot.img from the factory zip.
Synyster06Gates said:
Is Bricked the only kernel you've used? Or did you try Franco as well? Francos modifies a few files that need to be fixed before you can flash the update - even if you flashed a stock boot.img.
If you haven't, try the stock boot.img from http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
yep, bricked was the only one I've tried so far. I'll try this and report back, thank you
*update* worked! thanks very much, it's updating right now.
desucca said:
yep, bricked was the only one I've tried so far. I'll try this and report back, thank you
Click to expand...
Click to collapse
I was the same as you. I had to flash stock boot.img and system.img for it to work. I only tried Bricked but went back to stock and at one point I tried Xposed. Guess one of them left a trace.
Sent from my Nexus 5 using xda app-developers app
david23c said:
you apparently have a modified build.prop. You probably will have to re-flash system.img to apply the OTA.
or find what was changed in build.prop and revert the change.
Click to expand...
Click to collapse
This. What did you modify in your build.prop? Revert to your backed up original build.prop (.bak), install a new stock build.prop, or flash system.img.
Nitemare3219 said:
Got the same message. Flash the stock 4.4 (not 4.4.1) boot.img from the factory zip.
Click to expand...
Click to collapse
you should flash boot.img and system.img to make sure you have a stock system partition.
david23c said:
you should flash boot.img and system.img to make sure you have a stock system partition.
Click to expand...
Click to collapse
i have the same problem, does flashing these files affect any of my data or configuration?
cannot update rooted nexus?
so in short can we say we just cannot update to 4.4.1 without reverting back to and losing all app data ?
Guys,
Please help me out here. I rooted my Nex5 because I could not stand the DPI (icons/text were ridiculously big)
Because an app I use a lot cannot function on a rooted phone, I unrooted my phone.
I guess this means the following: my bootloader is NOT stock (because I see the 'unlock' icon), I am NOT rooted and my OS is stock.
In the end I just want to get 4.4.1 the easiest way and of course still have my DPI still modified.
Thanks in advance!!!
gaurishmhatre said:
so in short can we say we just cannot update to 4.4.1 without reverting back to and losing all app data ?
Click to expand...
Click to collapse
Yes you can. I flashed the OTA in CWM after undoing the changes I'd made and it flashed fine without losing data
lowlow2 said:
Guys,
Please help me out here. I rooted my Nex5 because I could not stand the DPI (icons/text were ridiculously big)
Because an app I use a lot cannot function on a rooted phone, I unrooted my phone.
I guess this means the following: my bootloader is NOT stock (because I see the 'unlock' icon), I am NOT rooted and my OS is stock.
In the end I just want to get 4.4.1 the easiest way and of course still have my DPI still modified.
Thanks in advance!!!
Click to expand...
Click to collapse
You can't install the update. You need to revert all system settings to stock (including what ever changed your DPI) before you can update. After that, you can install it, re root and change your DPI;
---------- Post added at 06:10 AM ---------- Previous post was at 06:09 AM ----------
chucky8 said:
i have the same problem, does flashing these files affect any of my data or configuration?
Click to expand...
Click to collapse
No, your data and configuration will be fine.
Synyster06Gates said:
You can't install the update. You need to revert all system settings to stock (including what ever changed your DPI) before you can update. After that, you can install it, re root and change your DPI;
---------- Post added at 06:10 AM ---------- Previous post was at 06:09 AM ----------
No, your data and configuration will be fine.
Click to expand...
Click to collapse
Thank you, I encountered in fact the problem because I changed my build.prop.
I tried adb sideload, but it gave an error on build.prop.
I see what I need to do now, thank you!!
---------- Post added at 01:25 PM ---------- Previous post was at 01:19 PM ----------
lowlow2 said:
Thank you, I encountered in fact the problem because I changed my build.prop.
I tried adb sideload, but it gave an error on build.prop.
I see what I need to do now, thank you!!
Click to expand...
Click to collapse
One last question, can I just adjust (revert) the DPI setting ? Or will it detect I fuzzled with my build.prop and never work without replacing ? Thanks
lowlow2 said:
Thank you, I encountered in fact the problem because I changed my build.prop.
I tried adb sideload, but it gave an error on build.prop.
I see what I need to do now, thank you!!
---------- Post added at 01:25 PM ---------- Previous post was at 01:19 PM ----------
One last question, can I just adjust (revert) the DPI setting ? Or will it detect I fuzzled with my build.prop and never work without replacing ? Thanks
Click to expand...
Click to collapse
You should be able to just edit it back to original configuration.
Synyster06Gates said:
You should be able to just edit it back to original configuration.
Click to expand...
Click to collapse
Tried this but unfortunately not working. I have the original system.img (+-600MB)
Can you tell me how I flash this with ADB (weirdly couldn't find it on xda via search!)
Thanks!
lowlow2 said:
Tried this but unfortunately not working. I have the original system.img (+-600MB)
Can you tell me how I flash this with ADB (weirdly couldn't find it on xda via search!)
Thanks!
Click to expand...
Click to collapse
Here ya go. Make sure the drivers are installed correctly. This guide has it all. You will only be flashing system.img, not the entire bat
http://forum.xda-developers.com/showthread.php?t=2513701
Synyster06Gates said:
Here ya go. Make sure the drivers are installed correctly. This guide has it all. You will only be flashing system.img, not the entire bat
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
thanks!!
I've had the OPO for over a year, and just now had the need to root it. An OTA happened to come in the next day, and the update process didn't work as I expected. So I'd like to know if I did something wrong, a random problem occurred, or this is the way it's supposed to work.
Until a couple days ago, the OPO was stock + all OTAs that had been released. I unlocked the bootloader, installed TWRP recovery, and installed SuperSU. All that went as expected. When the OTA notification arrived the next day, I tried to install it with "Update Cyanogen recovery" still unchecked (because original reports with CM 11S said you could keep your custom recovery with an OTA).
When I tried to install the update, the phone just rebooted to TWRP and the update was not stored anywhere on /sdcard. I then checked "Update Cyanogen recovery" and tried to install the OTA again. It did not install, and TWRP was still my recovery. Several repeats of this had no different result.
Then I flashed the stock CM recovery with fastboot. After verifying I had the CM recovery, I installed the OTA again, and it failed again, reboting to recovery and doing nothing else. Then I downloaded the incremental update and tried to flash that via CM recovery, and that failed too. I checked the file /System/build.opt, and line "ro.build.version.incremental" said 49d90510ef, which meant I should have been able to install the cm-bacon-49d90510ef-to-d91bf047f5-signed.zip file. But it failed and said the current build number was not as expected. The number it gave me was not anything that made sense looking at the list of recent incremental updates.
So at that point I bailed out and installed via recovery the full flashable zip file, and that worked.
If this is what I have to do each time, it's certainly doable, but I don't think this is how it's supposed to go. I'm surprised the OTA didn't work with the custom recovery installed, and I'm even more surprised that the incremental installation failed. Maybe trying to install the OTA without updating the CM recovery messed things up, but that doesn't seem likely either. When the next OTA comes out, I'll see if any of these troubles are repeated. But I'd like to know how the OTA was supposed to work after installing a custom recovery.
I am still yet to figure this one out also, my friend I'm sure with time someone will respond who had better experience with this; just be patient
Have you been able to root yet? I can't seem to be able to on the new incremental yet.
@MidnightJava
Looks like I'm not the only one with this problem.
I'm trying to find now the link for Cyanogen Recovery flashable to see it that fix the OTAs
Check the CyanogenMod website, @distante
vince.lupe said:
Have you been able to root yet? I can't seem to be able to on the new incremental yet.
@MidnightJava
Click to expand...
Click to collapse
After installing the latest CM 12.1 ROM, I had to re-flash SuperSU. After doing that, root access is working fine. If you're having trouble rooting after installing the incremental, then my experience is perhaps not applIcable—since I was not able to do an incremental installation and had to re-flash the entire ROM.
distante said:
Looks like I'm not the only one with this problem.
I'm trying to find now the link for Cyanogen Recovery flashable to see it that fix the OTAs
Click to expand...
Click to collapse
This thread with Cyanogen mirrors and info has exactly what you need.
MidnightJava said:
After installing the latest CM 12.1 ROM, I had to re-flash SuperSU. After doing that, root access is working fine. If you're having trouble rooting after installing the incremental, then my experience is perhaps not applIcable—since I was not able to do an incremental installation and had to re-flash the entire ROM.
Click to expand...
Click to collapse
I had to completely re-flash stock 3JL full also, but this time root doesn't work. Tried to use WugFresh's Bacon Root Toolkit - didn't work - then, I tried to flash SuperSu via TWRP recovery (after unlocking bootloader), and that didn't work either? In other words, I have bootloader unlock, custom recovery installed, but no root :/
vince.lupe said:
I had to completely re-flash stock 3JL full also, but this time root doesn't work. Tried to use WugFresh's Bacon Root Toolkit - didn't work - then, I tried to flash SuperSu via TWRP recovery (after unlocking bootloader), and that didn't work either? In other words, I have bootloader unlock, custom recovery installed, but no root :/
Click to expand...
Click to collapse
What happens when you try to root? Does it seem successful, but then you don't actually have root access? Or do you get some failure indication when you flash SuperSU? I've rooted a few phones in the last few years, but I'm far from an expert. Hopefully someone else will jump in with some idea of what went wrong. Shooting somewhat in the dark, I'd say look at the version of SuperSU and make sure it's the latest and the right one for the ROM, look at read-write permissions on your storage (if you can, you may need root access to check it properly). Of course wiping cache is always a good step, and if nothing else works, maybe factory reset, re-lock the bootloader, and then unlock and flash custom recovery again, and see if root can be successful then.
Once on custom recovery ( TWRP ) OTAs will NOT not install, unless you revert back to CM stock recovery. If you don't want to do that, wait for a signed flashable version to come out, which is normally 1-2 days after. Everytime you flash an update you will have to reinstall TWRP and SuperSU.
---------- Post added at 03:31 PM ---------- Previous post was at 03:25 PM ----------
vince.lupe said:
I had to completely re-flash stock 3JL full also, but this time root doesn't work. Tried to use WugFresh's Bacon Root Toolkit - didn't work - then, I tried to flash SuperSu via TWRP recovery (after unlocking bootloader), and that didn't work either? In other words, I have bootloader unlock, custom recovery installed, but no root :/
Click to expand...
Click to collapse
Did you guys remove the " Update Cyanogen recovery" in Dev options and "respect CM root settings " In SuperSU settings ?
Cholerabob said:
Once on custom recovery ( TWRP ) OTAs will NOT not install, unless you revert back to CM stock recovery. If you don't want to do that, wait for a signed flashable version to come out, which is normally 1-2 days after. Everytime you flash an update you will have to reinstall TWRP and SuperSU.
Click to expand...
Click to collapse
I figured that was the case when it failed. What seems anomalous in my case is that even after reverting to the stock recovery and verifying that it was installed, OTAs would not succeed. I didn't know about the "respect CM root settings " In SuperSU settings that you mentioned. Maybe that was the problem? Either that or the fact that I tried to install the OTA first with the custom recovery. Certainly the fact that the incremental installation reported I was at a different build number than what was listed in /System/build.opts indicates something was out of whack on my phone.
Temporarily reverting to the stock recovery and installing the OTA, then going back to custom recovery, seems a bit simpler than flashing the signed zip file and then re-installing recovery and SuperSU, but either way is not too bad. But being an engineer, I always have to find the optimum path and understand why things don't work the way I thought they should.
MidnightJava said:
What happens when you try to root? Does it seem successful, but then you don't actually have root access? Or do you get some failure indication when you flash SuperSU? I've rooted a few phones in the last few years, but I'm far from an expert. Hopefully someone else will jump in with some idea of what went wrong. Shooting somewhat in the dark, I'd say look at the version of SuperSU and make sure it's the latest and the right one for the ROM, look at read-write permissions on your storage (if you can, you may need root access to check it properly). Of course wiping cache is always a good step, and if nothing else works, maybe factory reset, re-lock the bootloader, and then unlock and flash custom recovery again, and see if root can be successful then.
Click to expand...
Click to collapse
It just tells me that I don't have access :/ Everything flashes perfectly fine, but then when I boot up and try to access root, it tells me that I don't have access. I've tried everything already :/
---------- Post added at 06:51 PM ---------- Previous post was at 06:47 PM ----------
Cholerabob said:
Did you guys remove the " Update Cyanogen recovery" in Dev options and "respect CM root settings " In SuperSU settings ?
Click to expand...
Click to collapse
I did do both :/
MidnightJava said:
I figured that was the case when it failed. What seems anomalous in my case is that even after reverting to the stock recovery and verifying that it was installed, OTAs would not succeed. I didn't know about the "respect CM root settings " In SuperSU settings that you mentioned. Maybe that was the problem? Either that or the fact that I tried to install the OTA first with the custom recovery. Certainly the fact that the incremental installation reported I was at a different build number than what was listed in /System/build.opts indicates something was out of whack on my phone.
Temporarily reverting to the stock recovery and installing the OTA, then going back to custom recovery, seems a bit simpler than flashing the signed zip file and then re-installing recovery and SuperSU, but either way is not too bad. But being an engineer, I always have to find the optimum path and understand why things don't work the way I thought they should.
Click to expand...
Click to collapse
Not really since the signed zip file come with superSU, after the install it will ask you if you want to install superSU automatically, and TWRP will too when you start your TWRP app on your phone after reboot. But to each his own
---------- Post added at 08:22 PM ---------- Previous post was at 08:19 PM ----------
vince.lupe said:
It just tells me that I don't have access :/ Everything flashes perfectly fine, but then when I boot up and try to access root, it tells me that I don't have access. I've tried everything already :/
---------- Post added at 06:51 PM ---------- Previous post was at 06:47 PM ----------
I did do both :/
Click to expand...
Click to collapse
Is your bootloader unlocked ? Reinstalled superSU ? Did you check with the fastboot command ? If you don't know how, look at Heisenberg's guide.
Cholerabob said:
Not really since the signed zip file come with superSU, after the install it will ask you if you want to install superSU automatically, and TWRP will too when you start your TWRP app on your phone after reboot. But to each his own
---------- Post added at 08:22 PM ---------- Previous post was at 08:19 PM ----------
Is your bootloader unlocked ? Reinstalled superSU ? Did you check with the fastboot command ? If you don't know how, look at Heisenberg's guide.
Click to expand...
Click to collapse
Yes, bootloader is unlocked and SuperSu was reinstalled :/
I just received notification for OTA update. (134MB)
BLU_p0010UU_V11_GENERIC_5.1_20151123-0956
1. Stagefright patch
2. google security patches
3. Mcafee security 2015
4.Other bug fixes
Anyone tried it ?
i want to know if it is going to try and stick me with mcafee. . . happy to see an update, though!
you can remove mcafee after the update.
Can anyone upload ota?
Yes please. I'm rooted and it won't let me download the update. If someone could even offer a system dump that would be helpful.
---------- Post added at 02:29 PM ---------- Previous post was at 02:28 PM ----------
If only for the stage fright patch
---------- Post added at 02:32 PM ---------- Previous post was at 02:29 PM ----------
Also if someone could offer a system dump of the newest upgrade I'd be more than willing to cook up a rooted stock rom. I know I haven't been on the forums much lately at all but I remember working on stuff back in the t-mobile g1 days
Rooting after the update
I only first tried to root my Blu Pure XL after the update was installed. I find that the boot loader is locked and I can not find a way to gain access. I am not sure if the update added this major inconvenience but I suspect it did as the rooting method as described will not work for me at all. Any thoughts or suggestions?
blacksmithjk said:
I only first tried to root my Blu Pure XL after the update was installed. I find that the boot loader is locked and I can not find a way to gain access. I am not sure if the update added this major inconvenience but I suspect it did as the rooting method as described will not work for me at all. Any thoughts or suggestions?
Click to expand...
Click to collapse
ive updated with every ota and root works fine... boot loader isnt locked... try to flash twrp via fastboot, and if that doesnt work enable developer options in settings and "Enable OEM unlock"
but like i said Ive flashed back to stock FW with SP tool (compete stock boot, recovery, and system ver .11) so if any update would have locked BL it would have locked mine... but it didnt, doesnt, and hasnt...
Follow the thread about twrp... it gives you very easy to follow directions.
Yeah, I did the OTA update before rooting, and it didn't want to allow me after the OTA update.
I downloaded multiple files from all over the place, placed them in a "root" subfolder and it still seemed impossible.
Got it done AFTER 3 days
so...
using flashboot to flash twrp, after the OTA,
then using twrp to flash the SU.zip took 3 days?
what files and "root folder" are you referring to?
Sounds like sever case of lack of reading or lack or user error;
But Im glad you stuck with it long enough to get it working...
ArconHadron said:
Yeah, I did the OTA update before rooting, and it didn't want to allow me after the OTA update.
I downloaded multiple files from all over the place, placed them in a "root" subfolder and it still seemed impossible.
Got it done AFTER 3 days
Click to expand...
Click to collapse
tbirdguy said:
ive updated with every ota and root works fine... boot loader isnt locked... try to flash twrp via fastboot, and if that doesnt work enable developer options in settings and "Enable OEM unlock"
but like i said Ive flashed back to stock FW with SP tool (compete stock boot, recovery, and system ver .11) so if any update would have locked BL it would have locked mine... but it didnt, doesnt, and hasnt...
Follow the thread about twrp... it gives you very easy to follow directions.
Click to expand...
Click to collapse
tbirdguy said:
so...
using flashboot to flash twrp, after the OTA,
then using twrp to flash the SU.zip took 3 days?
what files and "root folder" are you referring to?
Sounds like sever case of lack of reading or lack or user error;
But Im glad you stuck with it long enough to get it working...
Click to expand...
Click to collapse
Thanks, hardest part was actually getting phone to boot into flash mode.
Specifically, holding Power plus Volume+ is fine, but you have to let go of the power button first, then the Volume+.
Plus, I had to adb reboot before getting the TWRP rom to flash properly....
Not my best effort, but findintg SPECIFIC instructions were difficult, and had to manually search for latest fastflash and TWRP......v2.8.6.0
ArconHadron said:
Thanks, hardest part was actually getting phone to boot into flash mode.
Specifically, holding Power plus Volume+ is fine, but you have to let go of the power button first, then the Volume+.
Plus, I had to adb reboot before getting the TWRP rom to flash properly....
Not my best effort, but findintg SPECIFIC instructions were difficult, and had to manually search for latest fastflash and TWRP......v2.8.6.0
Click to expand...
Click to collapse
Fastflash?
Manually search?
Under the Development heading there are 5 topics, 2 of which are for TWRP recoveries (3.0.2 is buggy but works, just takes long time to wipe and restore; and theres SOOOOO many posts about how to flash them and how to use SP Flash Tool... so once again; glad you stuck with it, but Im still going with user error due to fail to RTFM
New update arrive to me, unfortunately i can't flash cause my system partition was modified, anybody tried and flashed it for those on stock?
Edit: a little dismayed, july 1 security patch? Its almost the middle of September now
Same situation here. Can flash the ota.
I rooted and changed to twrp.
I think it's because of the recovery. Don't you?
Is there a way to flash back to the stock recovery without a complete flash to stock?
zagzag99 said:
Same situation here. Can flash the ota.
I rooted and changed to twrp.
I think it's because of the recovery. Don't you?
Is there a way to flash back to the stock recovery without a complete flash to stock?
Click to expand...
Click to collapse
Nope, im on stock recovery, but i must have made a mistake in one of my mods, i used systemless root and systemless xposed so system partition doesn't get touched but it errors in stock recovery, i was able to flash systemless root by booting twrp directly from fastboot and made sure to keep system as read only
thirdzcee said:
Nope, im on stock recovery, but i must have made a mistake in one of my mods, i used systemless root and systemless xposed so system partition doesn't get touched but it errors in stock recovery, i was able to flash systemless root by booting twrp directly from fastboot and made sure to keep system as read only
Click to expand...
Click to collapse
I had OTAs until 1.3
Then flashed TWRP
Now it fails claiming of fingerprints mismatch.
It expects sub reversion 726.6502 and somehow I'm on 700.6952
Is that how it fails at your end?
---------- Post added at 08:41 PM ---------- Previous post was at 08:40 PM ----------
Is there a easy twrp flashable stock?
zagzag99 said:
Is there a easy twrp flashable stock?
Click to expand...
Click to collapse
Yes, with the Full OTA. Settings -> About tablet -> System upgrade -> 3 dots (upper right) -> Advanced -> Check full upgrade. After flashing, you'll need to reflash TWRP and root.
zagzag99 said:
I had OTAs until 1.3
Then flashed TWRP
Now it fails claiming of fingerprints mismatch.
It expects sub reversion 726.6502 and somehow I'm on 700.6952
Is that how it fails at your end?
---------- Post added at 08:41 PM ---------- Previous post was at 08:40 PM ----------
Is there a easy twrp flashable stock?
Click to expand...
Click to collapse
Mine is a little different
Verifying update package...
I:comment is 1547 bytes; signature 1529 bytes from end
I:whole-file signature verified against RSA key 0
I:verify_file returned 0
Installing update...
sysutil: mmapped 4 ranges
Source: nvidia/sb_na_wf/shieldtablet:6.0.1/MRA58K/40827_726.6502:user/release-keys
Target: nvidia/sb_na_wf/shieldtablet:6.0.1/MRA58K/49349_766.5399:user/release-keys
Verifying current system...
contents of partition "/dev/block/platform/sdhci-tegra.3/by-name/LNX" didn't match EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:6707200:862bcf55773c989cdbbd825be96f070c7e2c3462:6715392:a817ba108d1571790ab6a6eb6750e1566dc0a32e
file "EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:6707200:862bcf55773c989cdbbd825be96f070c7e2c3462:6715392:a817ba108d1571790ab6a6eb6750e1566dc0a32e" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: "EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:6707200:862bcf55773c989cdbbd825be96f070c7e2c3462:6715392:a817ba108d1571790ab6a6eb6750e1566dc0a32e" has unexpected contents.
"EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:6707200:862bcf55773c989cdbbd825be96f070c7e2c3462:6715392:a817ba108d1571790ab6a6eb6750e1566dc0a32e" has unexpected contents.
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
I:Saving locale "en_US"
thirdzcee said:
Nope, im on stock recovery, but i must have made a mistake in one of my mods, i used systemless root and systemless xposed so system partition doesn't get touched but it errors in stock recovery, i was able to flash systemless root by booting twrp directly from fastboot and made sure to keep system as read only
Click to expand...
Click to collapse
I suspect it has to do with the fact that systemless root modifies the bootloader and the delta OTA checks that. Try uninstalling root from SuperSU (it does say uninstallation is required for OTA to proceed) and see if OTA proceeds.
Isira said:
Yes, with the Full OTA. Settings -> About tablet -> System upgrade -> 3 dots (upper right) -> Advanced -> Check full upgrade. After flashing, you'll need to reflash TWRP and root.
Click to expand...
Click to collapse
Thanks, i just did the full ota flash... Waiting for the art pre compile of all my apps now.
Isira said:
I suspect it has to do with the fact that systemless root modifies the bootloader and the delta OTA checks that. Try uninstalling root from SuperSU (it does say uninstallation is required for OTA to proceed) and see if OTA proceeds.
Click to expand...
Click to collapse
Thank you, uninstalled magisk OTA went fine for me, now ill have to wait to go back home to root again, systemlessly
where is the OTA file located? I tried data/data/com.nvidia.ota/files/rom but it's not there.
*edit nvm, found it, under app_download folder and not the files/rom folder
Full OTA k1 1.4 for recovery
https://mega.nz/#!Q1VUVBrR!v40m3Q4s-rqcfCYQmEqIw0MzEJTI897Sd7ZousmhcKU
Hi folks, I'm having an issue with the update; I have rooted my Shield K1, have attempted to update to 1.4 using FlashFire app on Stock recovery, I have a 64GB Samsung EVO SD card and my storage was on adoptive. The update/flash started fine, but on reboot the error message "Unfortunately, Setup Wizard has stopped" comes up, I click OK and nothing happens. Does anyone know how I can rectify this issue please?
I found that by downloading the full image (which you can do via the built in updater on the tablet via Settings), I could use Flashfire to install and root it, no data lost. Didn't work with the smaller OTA file, but the full file worked flawless.
Thanks, but I can't get past the error message. I have seen another way to flash the update and have found out I did one of the steps wrong, if I can get it working again I'll post.
chewdiggy said:
Thanks, but I can't get past the error message. I have seen another way to flash the update and have found out I did one of the steps wrong, if I can get it working again I'll post.
Click to expand...
Click to collapse
You tried wiping cache?
Isira said:
Yes, with the Full OTA. Settings -> About tablet -> System upgrade -> 3 dots (upper right) -> Advanced -> Check full upgrade. After flashing, you'll need to reflash TWRP and root.
Click to expand...
Click to collapse
Hey mate what is the best version of supersu to flash?
Sent from my SHIELD Tablet K1 using Tapatalk
thirdzcee said:
You tried wiping cache?
Click to expand...
Click to collapse
I have now wiped the cache and it is back to defaults. Thank you thirdzcee. Will not make that mistake again, I assure you.
robgee789 said:
Hey mate what is the best version of supersu to flash?
Click to expand...
Click to collapse
Use Flashfire, it'll do it all for you. (although it does appears to come with 2.76 instead of 2.78 of SuperSU, but updates itself anyway).
I have been having issues on my k1 since the 1.4 firmware I tried doing the toggle able system-less root and xposed but i lose touch and the tablet just doesn't work and i end up having to reinstall the 1.4 update at this point i'm sitting at fresh wiped tablet i dont yet.
I have narrowed my issues down to bad SD card as adopted storage.
i just downloaded the update by accident but i dont want to flash it because i have root and twrp so i moved the ota and restarted my tablet, but the notification is still there, any ideas on how to remove the notification?
Hello,
i need your help with my htc u 12+., please (
What happened
While I was happily using the phone a pop up from Magisk manager showed up, asking if I wanted to update. I said ok.
Magisk manager updated. Then it asked to update Magisk itself to 17.1. Checked on XDA if it was stable. It was. I chose the suggested method and tapped ok.
Here's where the nightmare begins. The installation seemed successful but the phone couldn't boot properly. The HTC animation stopped suddenly on the three green dots and the phone didn't react at all. It was not really a bootloop, it was like it couldn't boot any more.
What I did
Tried not to freak out and managed to boot into bootloader and then recovery. Tried to uninstall magisk through the magisk uninstaller, couldn't do it.
I didn't know if I could install Magisk 16.0 over a newer version, and I preferred not to try by luck. So I decided to restore a previous NAND Back up I had made. The NAND backup could restore everything but the /vendor partition.
Now, the phone successfully reboots but:
- I have no root (Magisk is gone)
- when I plug my USB cable, it only charges. No communication between the phone and the PC, unless I boot into bootloader (then the connection is there again and I can use fastboot commands). When I go to Developer options, no matter what communication protocol I choose for USB, it sticks to "Charge". Debug USB is ON, of course.
Tried to install Magisk again through a temporary TWRP, but the issue is still there: I can't mount /vendor partition and it fails.
I've looked for a solution here and there; what I found out is that I should use a treble-enabled TWRP, but my limited knowledge doesn't help me with that.
Please could you help me? It's crazy how messy can be just tapping ok on a notification :crying:
EDIT - FIXED:
To restore the USB communication, flashing the RUU solved the problem.
Using the patched boot.img method to install Magisk could succesfully work around the /vendor issue.
Huge thanks to the guys who helped, that was essential.
Easy fix. Flash the RUU and be on your marry way.
Thatll flash EVERYTHING back to stock. Then restore your data via TWRP that you had saved on a USB or microsdcard.
I also updated to the latest magisk, but everything is working just fine for me. (64Gig US unlocked version)
---------- Post added at 10:38 PM ---------- Previous post was at 10:35 PM ----------
https://www.htc.com/us/support/updates.aspx
I had the same issue this morning and finally figured it out. Just use the new uninstaller from the magisk thread. Once you flash that in twrp you will be able to install the new magisk without any problems!
MNoisy said:
I had the same issue this morning and finally figured it out. Just use the new uninstaller from the magisk thread. Once you flash that in twrp you will be able to install the new magisk without any problems!
Click to expand...
Click to collapse
Unfortunately, the new uninstaller is the one that doesn't work for me due to the /vendor partition, that my TWRP is not able to mount..
Tachi91 said:
Easy fix. Flash the RUU and be on your marry way.
Thatll flash EVERYTHING back to stock. Then restore your data via TWRP that you had saved on a USB or microsdcard.
I also updated to the latest magisk, but everything is working just fine for me. (64Gig US unlocked version)
---------- Post added at 10:38 PM ---------- Previous post was at 10:35 PM ----------
https://www.htc.com/us/support/updates.aspx
Click to expand...
Click to collapse
Thank you, maybe this one will help me.
Should I check something before trying ? (like CID.. or.. something else?)
And can I launch the RUU when I'm in bootloader mode? It's the only way I have to make the PC recognize the device.
EDIT: trying to launch the RUU, but after a few clicks it closes.. maybe my PC can't find a device, even in bootloader mode, and the software is shut down.
Tachi91 said:
Easy fix. Flash the RUU and be on your marry way.
Thatll flash EVERYTHING back to stock. Then restore your data via TWRP that you had saved on a USB or microsdcard.
I also updated to the latest magisk, but everything is working just fine for me. (64Gig US unlocked version)
---------- Post added at 10:38 PM ---------- Previous post was at 10:35 PM ----------
https://www.htc.com/us/support/updates.aspx
Click to expand...
Click to collapse
[canceled]
sbiricuda said:
Unfortunately, the new uninstaller is the one that doesn't work for me due to the /vendor partition, that my TWRP is not able to mount..
Click to expand...
Click to collapse
I was having the same issue with error 2 and 255 (Maybe 225?) with the vendor mount problem. I think I rebooted/changed from slot a to slot b then back again. Then I was able to run uninstaller and the new installer. System and vendor were both unchecked and automatically mounted with the magisk script during the new install.
I actually recommend flashing the stock boot image before you do any of this to. You should not have to RUU. I had the identical problems today.
MNoisy said:
I was having the same issue with error 2 and 255 (Maybe 225?) with the vendor mount problem. I think I rebooted/changed from slot a to slot b then back again. Then I was able to run uninstaller and the new installer. System and vendor were both unchecked and automatically mounted with the magisk script during the new install.
I actually recommend flashing the stock boot image before you do any of this to. You should not have to RUU. I had the identical problems today.
Click to expand...
Click to collapse
So basically I should give:
fastboot --set-active=a
fastboot --set-active=b
(or vice versa if i'm on A)
right?
And where can i get the stock boot? The NAND-restore restored the /boot I had just after unlocking the bootloader, it's a very early nand-backup. Should I still flash the stock boot image?
Anyway, if only I could connect my phone stuck on "just charge" USB option, I wouldn't mind to RUU and start over again. The phone only has two days, it won't take long to set it up again.
sbiricuda said:
So basically I should give:
fastboot --set-active=a
fastboot --set-active=b
(or vice versa if i'm on A)
right?
And where can i get the stock boot? The NAND-restore restored the /boot I had just after unlocking the bootloader, it's a very early nand-backup. Should I still flash the stock boot image?
Anyway, if only I could connect my phone stuck on "just charge" USB option, I wouldn't mind to RUU and start over again. The phone only has two days, it won't take long to set it up again.
Click to expand...
Click to collapse
I did mine through a temporary boot of twrp
Stock boot images can be found in the spreadsheet linked in the second post of the image/firmware/boot/OTA thread here
Boot to download mode
temporary boot twrp
install stock boot image only (From thread linked above)
After the boot image is installed, to be safe, you might want to reboot again to download mode and then temporary boot twrp again just to ensure the boot image installation completed fully and is recognized (Just a guess based on my experience)
Now that you are back in twrp with the stock boot image installed, run the new magisk uninstaller (You should not need to worry about mounting anything since the magisk script does it automatically if not mounted)
Once uninstaller is complete, install the new magisk 17.1 through twrp and you should be good to go.
If you have issues with errors, try the process again. If still having issues, use the reboot menu in TWRP to switch slots back and forth and then try again.
It took me a good 30 min to find the combination that worked but it consisted of the steps above. 7 minutes of it was trying to get the damn phone to stop boot looping but my finger kept double tapping or screwing up the pressure to hold down power!
MNoisy said:
I did mine through a temporary boot of twrp
Stock boot images can be found in the spreadsheet linked in the second post of the image/firmware/boot/OTA thread here
Boot to download mode
temporary boot twrp
install stock boot image only (From thread linked above)
After the boot image is installed, to be safe, you might want to reboot again to download mode and then temporary boot twrp again just to ensure the boot image installation completed fully and is recognized (Just a guess based on my experience)
Now that you are back in twrp with the stock boot image installed, run the new magisk uninstaller (You should not need to worry about mounting anything since the magisk script does it automatically if not mounted)
Once uninstaller is complete, install the new magisk 17.1 through twrp and you should be good to go.
If you have issues with errors, try the process again. If still having issues, use the reboot menu in TWRP to switch slots back and forth and then try again.
It took me a good 30 min to find the combination that worked but it consisted of the steps above. 7 minutes of it was trying to get the damn phone to stop boot looping but my finger kept double tapping or screwing up the pressure to hold down power!
Click to expand...
Click to collapse
Seems that I have no luck. The provided boot.img in the spreadsheet is for US unlocked variant, while I have the european version. Maybe it's the same, but the point is that when I open the AFH page to download, it says "for HTC U11".
Did you try extracting the boot image from the RUU that corresponds your current firmware version? The needed decryption tool is linked in the same thread in which you found the spreadsheet.
Flashing a US RUU on a European phone without S-OFF isn't possible, btw. That's why you faced those errors, earlier.
Sent from my HTC U12+ using XDA Labs
The U11 is just a typo, it is the right stuff. You have a couple options since there is no signed stock boot available on the spreadsheet. Simply download the RUU and decrypt the payload using the instructions in the OP of the post I already provided or go to here and find yours (It is there, I checked )
Tachi91 said:
Easy fix. Flash the RUU and be on your marry way.
Thatll flash EVERYTHING back to stock. Then restore your data via TWRP that you had saved on a USB or microsdcard.
I also updated to the latest magisk, but everything is working just fine for me. (64Gig US unlocked version)
---------- Post added at 10:38 PM ---------- Previous post was at 10:35 PM ----------
https://www.htc.com/us/support/updates.aspx
Click to expand...
Click to collapse
Good news and bad news.
The good news is that I managed to flash the RUU through TWRP. That flashed everything to stock, as you said.
This is particularly good because it also fixed the USB problem.
I have now a working stock device.
The bad news is: I can't flash Magisk any more.
I did just the same I did two days ago, when everything worked perfectly.
This time I keep getting the same error (photo: https://s8.postimg.cc/b6plbphx1/20180902_182259.jpg).
If I try to restore a NAND back up, I always get the /vendor error and I can't restore. The device then bootloops (meaning that I have to flash the RUU again to make it work).
So the main problem is now this one:
how can I deal with this /vendor error and install Magisk?
Thank you (to Mnoisy as well, of course, for his help in the previous post!).
sbiricuda said:
Good news and bad news.
The good news is that I managed to flash the RUU through TWRP. That flashed everything to stock, as you said.
This is particularly good because it also fixed the USB problem.
I have now a working stock device.
The bad news is: I can't flash Magisk any more.
I did just the same I did two days ago, when everything worked perfectly.
This time I keep getting the same error (photo: https://s8.postimg.cc/b6plbphx1/20180902_182259.jpg).
If I try to restore a NAND back up, I always get the /vendor error and I can't restore. The device then bootloops (meaning that I have to flash the RUU again to make it work).
So the main problem is now this one:
how can I deal with this /vendor error and install Magisk?
Thank you (to Mnoisy as well, of course, for his help in the previous post!).
Click to expand...
Click to collapse
Have you tried switching to slot A in TWRP? Since it can't mount /system_B maybe it'll mount system A?
Flippy498 said:
Did you try extracting the boot image from the RUU that corresponds your current firmware version? The needed decryption tool is linked in the same thread in which you found the spreadsheet.
Flashing a US RUU on a European phone without S-OFF isn't possible, btw. That's why you faced those errors, earlier.
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
Since I was facing USB issues (no communication via USB betwenn the device and the PC), I flashed the whole RUU. I'm now completely stock 1.21.
As I mentioned, the problem is now that I can't root again.
Tachi91 said:
Have you tried switching to slot A in TWRP? Since it can't mount /system_B maybe it'll mount system A?
Click to expand...
Click to collapse
I have read that this is very dangerous, and in fact I have no clue about what the consequences may be.
Do you suggest to switch to slot A and flash magisk?
You might want to try going through my steps to ensure you have a stock signed boot image on there and proceed through the steps listed.
sbiricuda said:
I have read that this is very dangerous, and in fact I have no clue about what the consequences may be.
Do you suggest to switch to slot A and flash magisk?
Click to expand...
Click to collapse
It's not dangerous. You'll get stuck on a bootloop since more often than not most phones don't have anything on there. If you did have an OTA you end up on the older system. Which would cause issues since your data partition would be cached to newer software.
Either way you have an RUU that will fix the phone. S-OFF isn't permanent and I'm assuming you don't have it. With S-ON the odds of a bricking is minimal.
MNoisy said:
You might want to try going through my steps to ensure you have a stock signed boot image on there and proceed through the steps listed.
Click to expand...
Click to collapse
I'm not sure TWRP does a good job since RUU when done correctly puts the phone in OEM RUU mode. TWRP possibly doesn't flash all the partitions since it might not have access to them. I'm surprised the zip worked in TWRP.
Full RUU zip is about 2gigs. (Single Sim)
MNoisy said:
You might want to try going through my steps to ensure you have a stock signed boot image on there and proceed through the steps listed.
Click to expand...
Click to collapse
Tachi91 said:
It's not dangerous. You'll get stuck on a bootloop since more often than not most phones don't have anything on there. If you did have an OTA you end up on the older system. Which would cause issues since your data partition would be cached to newer software.
Either way you have an RUU that will fix the phone. S-OFF isn't permanent and I'm assuming you don't have it. With S-ON the odds of a bricking is minimal.
I'm not sure TWRP does a good job since RUU when done correctly puts the phone in OEM RUU mode. TWRP possibly doesn't flash all the partitions since it might not have access to them. I'm surprised the zip worked in TWRP.
Full RUU zip is about 2gigs. (Single Sim)
Click to expand...
Click to collapse
I have installed the RUU through TWRP. I had to use the 1.15 because the 1.21 gave me an error about the CID that was not coincident (but I'm sure I picked the right RUU in the spreadsheet, for my CID, the HTC__034).
So i restored the 1.15, and then installed the OTA update to 1.21. This is my current situation. And yes, I'm S-ON.
What I could do is either:
- I try to decrypt the boot.img from the RUU in the spreadsheet (but using the tool seems sooo complicated, I'm reading the thread over and over not understanding much), or
- I use the .exe version of the 1.21 RUU, from the HTC official website. If I do that, can we be sure that I have a signed boot.img? And can this work around the TWRP limits about partitions?
Oh, something I forgot to mention: I did try the switching trick MNoisy suggested (switching the slots and then switiching back), but it didn't work.