Hi all, new to the forums here. Sorry if this is in the wrong section. So I was trying to update my nexus 6 to 6.0.1 from 6.0 and I got this error
supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing Update...
Source: google/shamu/shamu:6.0/MRA58K/2256973:user/release-keys
Target: google/shamu/shamu:6.0.1/MMB29K/2419427:user/release-keys
Verifying current system...
"EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot:8393958:28495c2ab9b8a2210fc396d8af35c29bc885fce9:8398054:bb5e73e0be23e9709b0acfd83db5c62140" has unexpected contents
E: Error in @/cache/recovery/block.map
(Status 7)
Installation aborted
Now I looked up status 7 errors and how to fix, but none had pertained to my particular issue, so I figured I'd check before doing anything drastic. For some info, I have rooted, unlocked bootloader, flashed a custom recovery and rom, but when Marshmallow came out, I flashed stock image for 6.0 to my phone through nexus root toolkit, which removed custom recovery, flashed to stock, but kept bootloader unlocked. So now I'm on clean stock 6.0 and I received the OTA and I tried to install it and this is the message I get. Any ideas on how to get my phone to update? Oh, and BTW if it matters, I'm on T-Mobile. Thanks in advanced!
First of all, don't rely on toolkits, it's really easy to do those steps yourself using fastboot.
Also it says that your boot.img is not stock, or stock enough, so you should reflash everything again, including boot, if you are really after the OTA. But at this point why are you trying to use the OTA, when you could just update to 6.0.1 byt flashing the boot.img and system.img, and radio. You clear cache and dalvik. and when it finishes rebooting and optimizing applications you'll have your 6.0.1.
istperson said:
First of all, don't rely on toolkits, it's really easy to do those steps yourself using fastboot.
Also it says that your boot.img is not stock, or stock enough, so you should reflash everything again, including boot, if you are really after the OTA. But at this point why are you trying to use the OTA, when you could just update to 6.0.1 byt flashing the boot.img and system.img, and radio. You clear cache and dalvik. and when it finishes rebooting and optimizing applications you'll have your 6.0.1.
Click to expand...
Click to collapse
Hey, that would be great! The only problem is I'm not particularly skilled in that field lol. Does the boot.img, system.img and radio come from the stock factory image, or do I have to download those separately? And would I install those with a particular program? Thanks, sorry for being such a noob
It's in the factory package mmb29k. Download it, and extract it, you'll have the bootloader, the radio, and a zip file with all the rest. You don't need the bootloader, it hasn't changed since the marshamllow preview. Extract the files from the zip file, then flash radio, boot.img and system.img.
For flashing you need fastboot, but the toolkit already installed it, it just calls it when you push buttons.
As for the flashing, everything is explained in the pinned post.
Related
ISSUE RESOLVED: keeping post since active since I still need the rom exe. But boot looping fixed.
My AT&T HTC One is stuck in boot loop, probably to do with the KK OTA update. I have looked everywhere, read posts all night, and tried all of the various reboots and reflashings of recovery files and firmware, erased caches, locked and unlocked bootloaders. Can anyone post the executable RUU for the stock ROM KK version 4.18.502.7? I'd really appreciate it. I can't sideload a zip (it stalls). I'm aware of the other post asking for the same thing and the response in it with a link to the file, but that link actually is only to a recovery zip with darkbootloader, which seems also to require S-OFF, even if I did have some way to sideload it.
The firmware updated before it began looping, so I can't just reinstall a prior stock ROM exe file, as far as I can tell. I tried anyway!
I hesitate to install the .1540. Dev. Ed. version of the ROM that's available because it says in the notes that it's "compatible" with my cid and PN, etc, but I think they mean for recovery file purposes and not for a full ROM install. So I think I just need the ROM exe, if anyone has it? Thanks!
more info
by the way, when it crashed i had installed the ota update and then restarted play around with it, then rebooted in bootloader and unlocked, reinstalled twrp and AndRev HD 51. I've noticed two problems there. The first is that the Xposed module's latest update totally defeats my internet wifi and especially crashes vpn sevice. prior versions did not and I could not down-install to prior version (is preinstalled in HD 51). The other problem is that in looking around for this boot loop probably, turns out that TWRP apparently doesn't get along well with the encryption. don't know why. this stuff may or may not be part of the problem, but at this point i have no OS, an erased cache and can't even get into recovery (tried flashing twrp, older twrps and CWM. thanks.
You are screwed if you have no recovery, and the phone is s-on. You need to find a way to get in recovery. Alternatively try to flash the firmware only from OTA to get stock recovery.
sent from my mobile device
randomOne1111 said:
My AT&T HTC One is stuck in boot loop, probably to do with the KK OTA update. I have looked everywhere, read posts all night, and tried all of the various reboots and reflashings of recovery files and firmware, erased caches, locked and unlocked bootloaders. Can anyone post the executable RUU for the stock ROM KK version 4.18.502.7? I'd really appreciate it. I can't sideload a zip (it stalls). I'm aware of the other post asking for the same thing and the response in it with a link to the file, but that link actually is only to a recovery zip with darkbootloader, which seems also to require S-OFF, even if I did have some way to sideload it.
The firmware updated before it began looping, so I can't just reinstall a prior stock ROM exe file, as far as I can tell. I tried anyway!
I hesitate to install the .1540. Dev. Ed. version of the ROM that's available because it says in the notes that it's "compatible" with my cid and PN, etc, but I think they mean for recovery file purposes and not for a full ROM install. So I think I just need the ROM exe, if anyone has it? Thanks!
Click to expand...
Click to collapse
This RUU does not exist yet, only the FOTA version - I've been in talks with HTC about this very thing. They do not have an ETA for the RUU, unfortunately.
SaHiLzZ said:
You are screwed if you have no recovery, and the phone is s-on. You need to find a way to get in recovery. Alternatively try to flash the firmware only from OTA to get stock recovery.
sent from my mobile device
Click to expand...
Click to collapse
Hm. I did flash the firmware from an OTA. But couldn't actually boot into recovery after that. I can flash custom recoveries but can sideload without the intall stalling about a third of the way through (just hangs, no error messages). Then after that if I restart it loops. I can maybe fix the "tampered" warning and swap it out somewhere. I think it's the encryption while using twrp maybe resulted in some hiccup. But I thought the firmware flash would fix that. And I'm not sure how you can actually tell whether the flashed firmware is successful. (it says it is in the command prompt, but the phone doesn't really do anything all that different and i already updated with the OTA so the numbers won't change).
Looking at the board today and reading through the posts I see many people reporting basically being in the same boot loop boat after the OTA update, though with diff versions maybe there's some FW problem. weird so many posts of similar boot looping.
Thanks for responding.
This issue is temporarily resolved, was able to push ARHD in TWRP (would not sideload without erroring out during install, but was able to push zip to sdcard and then install from there) after much wiping using both twrp and cwm. Did notice when using CWM recovery would not install ARHD off sdcard push, and would flag unknown files .... android..security during wipes, so i am guessing that encrypting a custom ROM at least with TWRP as recovery was a bad idea. hopefully this will stay stable until the KK OEM RUU EXE is available. Thanks for the help.
Hello all,
Since my TF701T returned from RMA (touch screen issues), it has drained the battery like hell.
So I decided to flash original firmware again (done that before sending it), only to find out it now failed with this error:
Verifying update package...
E:failed to open /sdcard/T4_SDUPDATE.zip (No such file or directory)
So I renamed the zip to that file, but it didn't help.
This package is for "K00C" devices; this is a "tf701t"
In custom recovery log, one can find this:
ro.build.product=tf701t
ro.product.device=tf701t
Installed CWM, then flashed 2 custom ROMs (CROMbi KK and last AOKP), either system is stuck on boot or systemui fails permanently preventing using the tablet.
Then I flashed the original firmware with CWM instead of stock recovery, system stuck on boot-loop, except with 11.4.1.17, boot up but systemui fails again.
It's like the tablet Asus sent me back is not really a TF701T ?
Any help would be highly appreciated as the tablet is unusable at the moment, only boot-loader and stock/custom recovery are accessible.
Can you provide a logcat of the boot process from an adb connection please. Also the recovery.log from cwm (it's in /tmp/recovery.log so adb pull /tmp/recovery.log recovery.log)
It sounds like your system partition is not getting setup correctly or /data is corrupted somehow.
Also for stock you have to flash the zip inside the zip - you did do that right?
Let me get this straight:
You are on the 11.4.1.17 bootloader? That would mean you had the latest stock 4.4.2 firmware installed right?
The T4_SDUPDATE.zip is WW JB 4.3 firmware, is it not? You tried to flash that in stock recovery?
I read about one user who tried to downgrade from 4.4.2 to 4.3 yesterday and that also failed.
Another user contacted Asus support and they told him a downgrade is not possible from 4.4.2. No idea if that is true. The Asus reps are not always well informed....
sbdags said:
Can you provide a logcat of the boot process from an adb connection please. Also the recovery.log from cwm (it's in /tmp/recovery.log so adb pull /tmp/recovery.log recovery.log)
It sounds like your system partition is not getting setup correctly or /data is corrupted somehow.
Also for stock you have to flash the zip inside the zip - you did do that right?
Click to expand...
Click to collapse
berndblb said:
Let me get this straight:
You are on the 11.4.1.17 bootloader? That would mean you had the latest stock 4.4.2 firmware installed right?
The T4_SDUPDATE.zip is WW JB 4.3 firmware, is it not? You tried to flash that in stock recovery?
I read about one user who tried to downgrade from 4.4.2 to 4.3 yesterday and that also failed.
Another user contacted Asus support and they told him a downgrade is not possible from 4.4.2. No idea if that is true. The Asus reps are not always well informed....
Click to expand...
Click to collapse
Thanks for replying. Turns out I made a series of misleading mistake
First: custom recovery was installed, so it would not install an original firmware (device identifier incorrect, k00c while expecting tf701t).
Second: tried installing a custom ROM using Aroma, but the full wipe option didn't worked and ROM would boot loop!
Third: started using a modified ZIP of the original firmware without device identifier check, which was not allowed to install in stock recovery.
Bootloader was still on 10.26, however the closest thing to work was to flash original 11.4 firmware in CWM
At the end I use the original firmware ZIP and copied it to /sdcard/S4_SDUPDATE.zip, flashed stock recovery, and it installed flawlessly. That's when I realized the full wipe never occurred, all data where still there!
Hi all.
This is a moment that I'm disconnected hacks because I am in stock (6.0.401.11) and satisfied. I had OTA updates without problems until this kitkat version but today after receiving and downloading 2 times the OTA lollipop I can not install it because installation starts well and some moments later, the screen is stuck on the phone with red triangle and I have this in the recovery:
Verifying current system ...
"/ System / bin / reboot" has unexpected content
Installation aborted
Even when I do it manually, it's the same. Yet I have just manually switch successfully 6.0.401.12 that I missed somehow.
What's the trouble?
kamso said:
Hi all.
This is a moment that I'm disconnected hacks because I am in stock (6.0.401.11) and satisfied. I had OTA updates without problems until this kitkat version but today after receiving and downloading 2 times the OTA lollipop I can not install it because installation starts well and some moments later, the screen is stuck on the phone with red triangle and I have this in the recovery:
Verifying current system ...
"/ System / bin / reboot" has unexpected content
Installation aborted
Even when I do it manually, it's the same. Yet I have just manually switch successfully 6.0.401.12 that I missed somehow.
What's the trouble?
Click to expand...
Click to collapse
this says to me, in system/bin you have modified files, you must be 100% stock so flash TWRP recovery then use this: https://www.androidfilehost.com/?fid=95864024717072880 to retore full stock rom.
DO NOT try and root or anything, 100% pure stock required.
Full Reboot into android
boot back to recovery and flash this pre-load data here: https://www.androidfilehost.com/?fid=95864024717072879
Full reboot into android
You will need TWRP recovery for both of the above files, but you will also need to flash stock recovery afterwards to update which is here: https://www.androidfilehost.com/?fid=95864024717072472
fastboot flash recovery
fastboot erase cache
fastboot reboot-bootloader
full reboot into android, then update.
DO NOT try and root or anything, 100% pure stock required.
Seanie280672 said:
this says to me, in system/bin you have modified files, you must be 100% stock so flash TWRP recovery then use this: https://www.androidfilehost.com/?fid=95864024717072880 to retore full stock rom.
DO NOT try and root or anything, 100% pure stock required.
Full Reboot into android
boot back to recovery and flash this pre-load data here: https://www.androidfilehost.com/?fid=95864024717072879
Full reboot into android
You will need TWRP recovery for both of the above files, but you will also need to flash stock recovery afterwards to update which is here: https://www.androidfilehost.com/?fid=95864024717072472
fastboot flash recovery
fastboot erase cache
fastboot reboot-bootloader
full reboot into android, then update.
DO NOT try and root or anything, 100% pure stock required.
Click to expand...
Click to collapse
Ok, thank you. But what I don't understand is that there's a long time I'm no more root, I'm full stock (Rom, recovery...), only S-off and Unlocked. So Why for previous OTA updates I have not had this problem? Why I have to manually update successfully from 6.09.401.11 version to 6.09.401.12 one? Why it is only the upgrade to the Lollipop which has problem?
What is the preload data? I already have this: https://www.androidfilehost.com/?w=...0f40a2a319761577a4c3f1e723594b05669cb009e9d00
Can I flash it and the stock recovery only?
Your problem is the lack or corruption of the file /bin/reboot
2 solutions:
Flash a custom recovery and reflash the rom
Flash a custom recovery and replace the file
migascalp said:
Your problem is the lack or corruption of the file /bin/reboot
2 solutions:
Flash a custom recovery and reflash the rom
Flash a custom recovery and replace the file
Click to expand...
Click to collapse
Ok thanks. I'm downloading the Rom and I have to flash it through TWRP, flash stock recovery and try OTA update again.
kamso said:
Ok thanks. I'm downloading the Rom and I have to flash it through TWRP, flash stock recovery and try OTA update again.
Click to expand...
Click to collapse
preload data is HTC's little hidden way of stopping you getting OTA's if you unlock your bootloader, and yes it is required to update, without it, updates will fail.
Seanie280672 said:
preload data is HTC's little hidden way of stopping you getting OTA's if you unlock your bootloader, and yes it is required to update, without it, updates will fail.
Click to expand...
Click to collapse
Ah Ok I understand. These are applications that disappear when we unlock the bootloader. I had already installed them there's a long time. As I said my OTA updates passed without problem.
Problem flashing stock Rom in TWRP:
"- Zip signature verification failed
- Error flashing zip"
I don't understand anything, what's happen?
Problem solved and phone updated. Thank you!!!
My phone is rooted running a stock 5.1 ROM.
I just got a prompt to install a system update with a security patch, etc so I clicked to install but it gets stuck in TWRP recovery instead of installing the update.
So now every time my phone boots up it restarts trying to install that update.
EDIT: Ok, after a couple reboots the update cancelled on its own. Now I'm wondering if there's any way I can still install this update without it getting stuck in TWRP.
kloan said:
My phone is rooted running a stock 5.1 ROM.
I just got a prompt to install a system update with a security patch, etc so I clicked to install but it gets stuck in TWRP recovery instead of installing the update.
So now every time my phone boots up it restarts trying to install that update.
EDIT: Ok, after a couple reboots the update cancelled on its own. Now I'm wondering if there's any way I can still install this update without it getting stuck in TWRP.
Click to expand...
Click to collapse
In twrp erase cache. That will erase the update file that downloaded.
Sent from my XT1095 using Tapatalk
Thanks yep that's what I did so it boots fine again. I read in another thread some issues people are having with installing this update if their phone is rooted so I'm just gonna skip it. I've grown tired of all the hoop jumping Android requires.
kloan said:
Thanks yep that's what I did so it boots fine again. I read in another thread some issues people are having with installing this update if their phone is rooted so I'm just gonna skip it. I've grown tired of all the hoop jumping Android requires.
Click to expand...
Click to collapse
If you have a custom recovery, you can flash this rom:
http://forum.xda-developers.com/moto-x-2014/development/rom-xt1095-flashable-stock-rom-t3185945
It has the latest stagefright patch now, and it has OTA disabled to prevent bricking issues for people that have downgraded systems or systems that are modified with root/xposed/busybox/etc.
Before I do that, will I have to reinstall my apps or change all of the system settings again? Sorry, it's been a while since I flashed a ROM, I can't remember what's affected.
You shouldn't need to factory reset considering this is a stock rom and you are coming from the same android version. 5.1 to 5.1. But the fact that your phone had issues before may be an issue. You can try it without factory reset since it won't cause any damage to see if it works.
As far as what is modified, it should only be system apps. Anything you installed or configured should remain the same as long as you don't factory reset.
Sent from my XT1095 using Tapatalk
You have to go back to stock rom first to ensure you have system partition 100% stock. You can just flash the system.img and recovery.img, then apply the OTA. If you want to do it from twrp, you dont need flash the recovery.img and apply the zip file from romracer.
Sent from my XT1095 using Tapatalk
I had the same problem. I cleaned cache and was able boot properly. But now my phone asks me to update every 2 minutes and it is annoying the crap out of me. If I unroot and remove TWRP, will I be able to update to this OTA.
Okay, I haven't been able to update since LMY48I. Back then I was on stock recovery. Re-locking bootloader and all but still was not able to take OTA (always came up with dead android guy with "Error"). I'll skip the (probably) irrelevant stuff since then and give you the current situation:
Currently unlocked, rooted, with custom recovery. Still on LMY48I. I can't take OTAs obviously, and have tried flashing OTA updates manually with no luck and have tried flashing the entire Marshmallow image and that will not work either (sideload or flashing from internal storage in recovery). Sideload comes up with Closed error (device DOES show up in device list and I can do other things). Flashing from within recovery just says "Failed".
Please help me get to Marshamallow!
Edit: On Project Fi by the way.
Edit 2: Also, I've tried the flash-all script.
Now it says the device is corrupted when I boot up. I can still access recovery. Any help walking me through getting all of the correct firmware and latest build on would be much appreciated.
Thank you.
Edit: Looks like i'm good. I flashed each .img individually. I'm super curious why flash-all, sideload, and flashing from device wouldn't work though.
altvisionx said:
......./I flashed each .img individually. I'm super curious why flash-all, sideload, and flashing from device wouldn't work though.
Click to expand...
Click to collapse
Flashall.bat stops; only m-bootloader and m-radio are flash. Google's fault. You did the right thing by extracting the images and fasbiot flash them.
You cannot sideload the full factory image or flash from storage. Only fastboot
And just to clarify, you can't take an OTA (sideloading or otherwise) if your phone is rooted, have a custom recovery or a custom kernel (or any other modification to the system). The state of the bootloader (locked or unlocked) does not affect the ability to take an OTA update.