Database Users

[K1] "Unsupported menu option selected" error & where to get TimmyDean rooted 13-13?

[K1] "Unsupported menu option selected" error & where to get TimmyDean rooted 13-13?
I just got a brand new K1. Fresh out of the box with 3-3 pre-installed, I downloaded and used TimmyDean's permanent root tool, flashing a rooted 2-2 firmware. I then enabled the backdoor and ran all the OTA updates up to 14-14. This took several hours in all. I then ran the BusyBox and SU Tools install script. Everything was looking okay. I selected the choice to exit the script with reboot. The K1 turned off and came back on with the Lenovo logo, but, at the top of the screen was red writing:
Unsupported menu option selected: 1
Unrecoverable bootloader error (0x00000002).
It stops there and goes no further. No bootup.
Attempting to research the error, it seems this is not an error too many people encounter or know about, so my guess is that my only way of fixing this problem is to flash the whole thing over again from the beginning. (Unless someone here knows something about this problem. That would be tremendously helpful.)
Having already experienced what it took to go from 2-2 to 14-14 the first time with the permanent root package, I'd certainly like to shortcut it however possible. In this thread, http://forum.xda-developers.com/showthread.php?t=1404351 , TimmyDean posted a rooted 13-13 that we can start from. However, the link to the download file for it is Multiupload.com, and Multiupload.com does not seem to be up for me. Does anyone know where else I can go to try and download a copy?
I'd have posted directly in that Development thread, but, since I am an XDA noob, the forum system only allows me to post in this General section.

After experimenting with the "permanent root" package several times now, each time ending up with the "Unsupported menu option selected: 1" error after any OTA update, I have to believe there is an incompatibility between the K1 I have and the bootloader files in the "permanent root" package. I do not know if my K1 is recently manufactured and they are now doing something different with them that causes this incompatibility or what, but I felt I should warn you all that flashing the "permanent root" package could cause your K1 to not take official updates or to otherwise brick it with the "unsupported menu option" error. Perhaps the 13-13 package, which I don't have and can't test, didn't have this problem.
My serial number is CB1245XXXX. Manufacture date is "11/11/27."
I have now given up on getting root on my K1 and would just be happy to get it back to a working condition that can take Lenovo's OTA updates without bricking. I am currently trying these instructions and will update as to whether or not that resolves the problem: rootzwiki.com/topic/13877-guide-ideapad-k1-restore-to-mostly-stock-with-ota-updates/ (The forum software will not allow me to post hot links, so copy and paste that to browser.)

The rootzwiki procedure did not work to correct the problem. After any update, the tablet is bricked with the error. There are a few threads on the Lenovo support forum on this issue now, and there is no solution.
forums.lenovo.com/t5/IdeaPad-Slate-Tablets/K1-not-booting-after-update/td-p/548285
forums.lenovo.com/t5/IdeaPad-Slate-Tablets/Unrecoverable-Boot-Loader-Error/td-p/683633
I believe these old bootloader files will not work and will brick newer K1's, so my warning is:
DO NOT ATTEMPT TO ROOT YOUR K1'S. DO NOT CHANGE THE EXISTING BOOTLOADER IN ANY WAY WITH NVFLASH. SOMETHING HAS CHANGED.
This might only apply to more recently manufactured K1's, but, since we do not know when this problem begins, it is not possible to know beforehand whether or not you will brick yours.
To be on the safe side, DO NOT ATTEMPT TO ROOT YOUR K1'S. DO NOT CHANGE THE EXISTING BOOTLOADER IN ANY WAY WITH NVFLASH. SOMETHING HAS CHANGED.
Unfortunately, there was no backup option in the rooting packages, so I could not get a copy of the stock bootloader or any other files, if they are indeed of a different and newer variety. If someone has a recently manufactured K1, perhaps you can get those files and share them, because a lot of people are starting to see this problem now.

I have one with sn#1250xxxx, mfg dt 11/11/29. I wasn't even trying to root the thing. I happened during an OTA update. I tried probably all the recovery/rooting option out there. None of them worked. I have the tablet booting at lenovo screen. But I think you are right about the bootloader. If we can get the correct bootloader, we might be able to the the tablet back to life.

fix?
Has anyone come out with the fix for your issue.. I have the same issue . Used TImmy Dean's method.. and anything updating past the 02_02 (loaded from the tool I get the error... Anyone here have access to contact JimmyDean to ask him for help?
I see that he updated the tool to K1_A301_13_13_111209_US and maybe K1_A301_14_14_111209_US but all the links are dead.. anyone have a good place to download the files?

Try out the downloads on the following Lenovo's link -
download.lenovo.com/slates/k1/OTA

those are just OTs.. not image files.. If you don't have a compatable boot loader, you can't load those files.. We don't have a compatable bootloader.. so this is why we need ver 13 of timmy dean..
rezapatel said:
Try out the downloads on the following Lenovo's link -
download.lenovo.com/slates/k1/OTA
Click to expand...
Click to collapse

Can someone who's getting this bootloader error send me a pm. I put together a stock 120109 update that may work around the issue and I need someone to test.

Was this issue ever resolved, I didnt attempt to root mine, only attempted to wipe it clean and got this..

No, no real resolution. What I ended up doing was NVFlashing one of khanning's ROMs, like this one: http://forum.xda-developers.com/showthread.php?t=1560441
I don't know what's going to happen when I have to update again, such as the upcoming Ice Cream Sandwich update promised by Lenovo.

Problem getting 4.2.2 update: "Verification failed"

Hey everyone,
I'm having trouble getting my Nexus 7 to update to 4.2.2. My device is rooted, I recently performed a factory reset.
The update has never appeared in my "System updates" menu, so I looked around and saw that if you force stop "Google Services Framework" and clear its data, the update will appear in "System updates."
It did, but when it finishes downloading, it says "Verification failed."
I tried another factory reset, and I had to again force stop and clear data on "Google Services Framework" to get the update to appear, but again it downloads and say "Verification failed."
I'm stumped now. Do I have to unroot and reroot? Do I have to keep waiting for this update? Do anything with the bootloader? (I really hope not...)
Thanks everyone!

If some files in your system got changed for whatever reason, then you wont be able to update. You can flash the 4.2.1 stock rom and try ota update again.

Leonhan said:
If some files in your system got changed for whatever reason, then you wont be able to update. You can flash the 4.2.1 stock rom and try ota update again.
Click to expand...
Click to collapse
Is flashing the stock 4.2.1 rom the same thing as doing a factory reset to 4.2.1?
If it isn't, would flashing the 4.2.1 rom wipe my tablet?

Leonhan said:
If some files in your system got changed for whatever reason, then you wont be able to update. You can flash the 4.2.1 stock rom and try ota update again.
Click to expand...
Click to collapse
If he is trying to do an OTA to 4.2.2, would it not be more straightforward to just flash the 4.2.2 factory image? The OP has already done a factory reset, so it doesn't look like he/she is particularly attached to his current setup.
Also - the language he used was vague - it sort of sounded like the OP observed "verification failed" in the main OS rather than in the recovery. Not sure.
But it doesn't matter - newbs should not be trying to use OTAs on modified /system images or tabs with altered boot images. It's just too detailed a process to describe compactly.
@Horadrius
Before you do anything further, you should back up everything on the "SD Card" to your PC. Yes, all of it. You can throw it away later if you find you didn't need it. But if you follow the instructions for the Google (factory) images install, everything gets wiped off of /data including your pseudo - SD card.
At a minimum, that will allow you to follow the SBS instructions for installing the 4.2.2 factory images, or - you can simply install a 4.2.2 Stock ROM from over in the dev forum.
Whatever you do, start getting in the habit of making backups - and at least occasionally also getting copies of those off of the tablet.

Oh boy, lot of information to digest here....and a lot of questions
it sort of sounded like the OP observed "verification failed" in the main OS rather than in the recovery. Not sure.
Click to expand...
Click to collapse
Yes, it was the main OS - Settings -> About Tablet -> System Update.
After force stopping Google Services Framework, the update showed up there, and when the download bar reached 100%, it said "verification failed." I did a factory reset, and now when I go to System Update it simply says that my system is up to date.
This makes me think I'm not "supposed" to have the update yet, and that it will arrive, eventually. Yes?
newbs should not be trying to use OTAs on modified /system images or tabs with altered boot images.
Click to expand...
Click to collapse
So, no updating the device from System Menu because I'm rooted/unlocked bootloader? I'll have to flash everything as it comes out?
@Horadrius
Before you do anything further, you should back up everything on the "SD Card" to your PC.
Click to expand...
Click to collapse
Would Titanium Backup held in this regard? Or simply copy/paste the sdcard folder to my PC?
This whole process has been very frustrating. Is this the price you pay for rooting your device? Making simple system updates into a maze?

Horadrius said:
Oh boy, lot of information to digest here....and a lot of questions
Yes, it was the main OS - Settings -> About Tablet -> System Update.
After force stopping Google Services Framework, the update showed up there, and when the download bar reached 100%, it said "verification failed." I did a factory reset, and now when I go to System Update it simply says that my system is up to date.
This makes me think I'm not "supposed" to have the update yet, and that it will arrive, eventually. Yes?
So, no updating the device from System Menu because I'm rooted/unlocked bootloader? I'll have to flash everything as it comes out?
Would Titanium Backup held in this regard? Or simply copy/paste the sdcard folder to my PC?
This whole process has been very frustrating. Is this the price you pay for rooting your device? Making simple system updates into a maze?
Click to expand...
Click to collapse
Sounds like your download is bad if it fails at this stage. I believe it is saying the checksum of the download file doesn't match whatever is downloaded.
PS. not related to N7, why XDA use the re-captcha which I need to refresh several times to get something I can read

Horadrius said:
Yes, it was the main OS - Settings -> About Tablet -> System Update.
After force stopping Google Services Framework, the update showed up there, and when the download bar reached 100%, it said "verification failed." I did a factory reset, and now when I go to System Update it simply says that my system is up to date.
This makes me think I'm not "supposed" to have the update yet, and that it will arrive, eventually. Yes?
Click to expand...
Click to collapse
No. It means that for some strange reason, running a checksum program on the downloaded OTA file failed to produce the expected checksum. The most likely way this can happen is that the file is truncated - the download stopped short of the full file. Don't know why this is happening, but there you go. There could be other failure causes that are more rare, but it doesn't mean you are not "supposed" to have the OTA. It means that the download process is failing.
The *stock* recovery does a number of even more sophisticated checking than this; but it appears from your description that the recovery never even gets booted.
Horadrius said:
So, no updating the device from System Menu because I'm rooted/unlocked bootloader?
Click to expand...
Click to collapse
Yes and No. An unlocked bootloader causes no problems at all. ANY of the following CAN or WILL cause problems:
- attempting to run an OTA with a custom recovery installed instead of the stock recovery.
- having a modified boot partition (e.g. non-stock kernel, or slightly modified boot partition)
- having altered (or removed!) files in the /system partition that are targeted for patching.
- permissions changes performed by the installer script can cause root functionality to disappear
Horadrius said:
I'll have to flash everything as it comes out?
Click to expand...
Click to collapse
Not sure what you are asking here, but the basic answer is that if you stay on stock you can certainly apply OTAs easily. If you start altering things, you might or might not be able to apply an OTA; there are simply no guarantees.
[size=+1]OTAs are meant for stock installations - including a stock recovery. PERIOD. While it is possible that an OTA could succeed, it is unreasonable to have the expectation that it will do so.[/size]
Horadrius said:
Would Titanium Backup held in this regard? Or simply copy/paste the sdcard folder to my PC?
Click to expand...
Click to collapse
I presume you are talking about the future here, as you said that you already did a factory reset at least twice. If you have subsequently added stuff back in, then I suppose you might be talking about the present tense.
But, yes - either TiBu or the Carbon app can be used along with a strategy where you simply back up the apps & data you are interested in, (plus any "flashable zips" that you used to customize your device in the first place), and you simply start from scratch with a factory install followed by re-rooting, and then restore your apps & data (using TiBu or Carbon).
One other thing you can do which is EASY is this: simply wait until a developer/ROM cook publishes a "Stock" flashable ROM based on the release that the OTA is upgrading to. Don't worry about the OTA, just wait a little bit. (These ROMs are already out for the WiFi-only model, BTW).
1) Take a backup as the first thing you do. It's easy and gives you some insurance.
2) Don't wipe (no "factory reset") - just install the Stock ROM over the top of your existing ROM.
that's it. If you were using a custom kernel, re-install it.
Horadrius said:
This whole process has been very frustrating. Is this the price you pay for rooting your device? Making simple system updates into a maze?
Click to expand...
Click to collapse
[size=+1]OTAs are meant for stock installations - including a stock recovery. PERIOD.[/size]
Interpret that as you desire. It is unreasonable for you to expect that you can diddle with your phone any way you please, and a patch install upgrade methodology will be robust in the faces of arbitrary changes on your part. You are the person creating the maze, not Google.
Moreover, it is your choice to take an upgrade - it's not mandatory. My guess is your tablet was quite pleasing to you before any OTAs started rolling out. Nobody is forcing you to do anything.
OK, one last thing. It is still possible that a manual OTA can succeed on your phone if it is lightly rooted - but there are no guarantees. The procedure does not require you to wait around until an OTA arrives on your phone, but it is not for the faint-hearted:
1) Download the appropriate Stock OTA File.
2) Re-install the stock recovery onto your tablet. You will have to dig it out of the Google full factory image for the version of the OS you are currently running. (available here)
Code:
fastboot flash recovery factory-4.2.1-recovery.img
3) Soft-boot into a custom recovery, e.g.
Code:
fastboot boot openrecovery-twrp-2.4.1.0-grouper.img
5) Using the command line and adb to communicate with the soft-booted recovery, create a recovery command file:
Code:
C:\myPCsux> adb push 6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip /cache/update.zip
C:\myPCsux> adb shell
# cd /cache/recovery
# cat > command
--update_package=/cache/update.zip
^D # ( that is a Control-D character )
# sync
# reboot recovery
This will either succeed or fail. Based on your comments though, you might just want to overflash a Stock-derived ROM over the top of your existing ROM (a "no-wipe" install).
[ROM][Factory Image][4.2.2] Nakasi -::- Odex, Deodex, Rooted -::- teshxx (02/14/13) <-- NOTE for WiFi (nakasi/grouper) ONLY
good luck with your tab.
Someone once said "Rooting is a lifestyle". There's some truth to that; it eats up your time. Perhaps it is not for you.

Thanks, bftb0.
Looking through your list of reasons for why my OTA might not work, none of them applied to me.
I didn't install any custom recovery (didn't install Clockwork Mod recovery specifically to avoid dealing with flashing roms) or kernels or modify any partitions, nor to my knowledge changed any files in the /system section.
I think I'm going to give this update a week or so to pop up on my update menu before I start tinkering again.
Don't get me wrong - I enjoy this kind of tinkering, and all the perks of rooting, but my knowledge is extremely limited, which is what makes it frustrating trying to find information. The only thing I've done before this is install Cyanogen on my HP Touchpad.
Anyway, do I need to install CWM recovery to flash (overflash?) that 4.2.2 rom you linked?

if you haven't done anything other than rooting(i.e. copying a file su to it), OTA would go through. Your problem is about the download process. It can go wrong for many reasons from the download is bad to what saved to the temp area(where the download is) is bad(rare but still possible).

chimpanzeexda said:
if you haven't done anything other than rooting(i.e. copying a file su to it), OTA would go through. Your problem is about the download process. It can go wrong for many reasons from the download is bad to what saved to the temp area(where the download is) is bad(rare but still possible).
Click to expand...
Click to collapse
That's all I've done, root and unlock bootloader. The download only showed up when I cleared data and force stopped the "Google Services Framework" process. I reboot the system, and check for the update and nothing is there.

well, sounds like you have to flash it manually using fastboot then.
That said, I myself have no intention of doing the update any time soon as I don't find any specific problem with 4.2.1 and there isn't any specific feature i want in 4.2.2

Horadrius said:
Anyway, do I need to install CWM recovery to flash (overflash?) that 4.2.2 rom you linked?
Click to expand...
Click to collapse
TL;DR Yes and No.
People that use toolkits seem to use hard-flashed installs of custom recoveries, as they don't really understand what goes on under the hood, even if the toolkit offers them a means to soft-boot any image the toolkit operator downloads. (I assume that the toolkits probably allow this; as I don't use them I don't know for sure.)
What I am saying is that the answer depends on your knowledge. So long as you have an unlocked bootloader, you can soft-boot any boot image you like - including custom recoveries.. (This also pre-supposes correctly-functioning device drivers, but that is a Windows/user training issue, it has nothing to do with Android).
When I say soft-boot, I mean that the image is transferred to the tablet, which then hands over control and starts executing that image - but it is not "flashed" to Flash memory, so the next time a boot occurs, the same boot images are still stored in either "boot" or "recovery".
In this configuration, the phone should be much more likely to complete an OTA as it will have the stock recovery present most of the time, and only temporarily present when you attach to your PC and kick things off with a custom recovery.
The OTA could still fail, but it probably would succeed for a very lightly rooted stock configuration (other than problems with losing root).
The only downside to this arrangement is that you can't be flashing roms or making nandroid backups or other forms of rooter activities when you are away from the PC.
For the IT-OCD or obsessive ROM hopper, that could be a good thing.
good luck... the rest is up to you.

Ok, I installed Clockwork Mod from a toolkit because going into fastboot and choosing "Recovery mode" led me to a picture of the Android guy with a red triangle on his back saying "No Command."
I'm just going to install 4.2.2 myself now. Question regarding that link - odex/deodexed - I looked up the difference but can't tell which one is appropriate for me - I'm guessing it's odex because that seems to be closer to stock.
Edit: It worked! Thanks for your assistance, everyone!

IMO, google should not ship odex image now that we have fast enough hardware. odex is just a form of 'pre-compilation' which only benefit first time load(or when the cache is cleared). Too little gain for such a complicated setup.

New update available for KIW-L24

Honor released an update today for its KIW-L24
This will upgrade your system to KIW-L24C567B351 from any of the versions given below.
If you are in KIW-L24C567B331CUSTC567D003 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74510/f1/full/update.zip
If you are in KIW-L24C567B334 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74512/f1/full/update.zip
This update consists of latest January Google security patches and few important bug fixes for device.

vsriram92 said:
Honor released an update today for its KIW-L24
This will upgrade your system to KIW-L24C567B351 from any of the versions given below.
If you are in KIW-L24C567B331CUSTC567D003 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74510/f1/full/update.zip
If you are in KIW-L24C567B334 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74512/f1/full/update.zip
This update consists of latest January Google security patches and few important bug fixes for device.
Click to expand...
Click to collapse
Thanks for the note, but either there is an issue with the update or the file got corrupted on the download. I flashed it and emui went through the update process, rebooted and then said my SD card was corrupt and to format it.
I have a 128GB card full of music TBU and saved ROMs that I did not want to lose. Went back via TWRP to previous and no damaged SD card and all is well.
Might have been the file was corrupted but just be caareful and always backup before you make any changes.

So nice of their support site to be down...

tomlogan1 said:
Thanks for the note, but either there is an issue with the update or the file got corrupted on the download. I flashed it and emui went through the update process, rebooted and then said my SD card was corrupt and to format it.
I have a 128GB card full of music TBU and saved ROMs that I did not want to lose. Went back via TWRP to previous and no damaged SD card and all is well.
Might have been the file was corrupted but just be caareful and always backup before you make any changes.
Click to expand...
Click to collapse
Instructions > https://forum.xda-developers.com/honor-5x/how-to/guide-force-installing-stock-ota-t3502874

What are the bug fixes???
Are there any new features???
I am currently on custom ROM and would like to know the answers to these questions to see if it's worth it to go back to stock rom

Hi, is there a full firmware package for this new version? Tried to upgrade and got soft-bricked and I don't know if it's safe to flash the full B331 package.
[EDiT]
Flashed the full B331, booted and applied the B351 update by powering off and pressing Vol+ & Vol -. After booting it still says B331 and my WiFi is dead.

m0ndul said:
Hi, is there a full firmware package for this new version? Tried to upgrade and got soft-bricked and I don't know if it's safe to flash the full B331 package.
[EDiT]
Flashed the full B331, booted and applied the B351 update by powering off and pressing Vol+ & Vol -. After booting it still says B331 and my WiFi is dead.
Click to expand...
Click to collapse
So much miss information .. no one bothers to find the truth

Can I ask where/when/how you found these files? There seems to be nothing official available, nor will Huawei provide any information about any prospective update.

animeme said:
Can I ask where/when/how you found these files? There seems to be nothing official available, nor will Huawei provide any information about any prospective update.
Click to expand...
Click to collapse
Link below or install the Huawei Firmware Finder form the Google Play Store and set it up to get OTA files in settings.
http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=kiw-l24

deleted

So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.

GrimReaper24 said:
So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.
Click to expand...
Click to collapse
What he said.
I'm hoping it's nothing more than a VoLTE update that LOS maintainers warn against anyway, if there's actually no one to further explain what it is

received this B351 update over B331, also did factory reset, GUI lag seems gone, not noticing new feature

my kiwi-L24 got re-flashed today, it is weird that this B351 update is no longer available from B331's update check
searched on internet, there is news about "honor 5c" getting a B351 nougat update

This came up on one of the 5X's that I have. Updated and forgot to put back stock recovery. Don't be like me and forget to do that. Now it won't work properly and I can't get to start any apps to try and fix it. I can put back TWRP and wipe it, but I don't want to lose my data. I also have that problem now where it keeps telling that the SD card is corrupted. I backed up the data and scrubbed the card in the phone but it keeps coming back with the same thing.
If someone did an actual successful update properly (with stock recovery) then please update and say if everything is working. If not, I'm going to have to find some way to backup the data and then scrub it.
*EDIT*
I believe something like this happened to me before. I was on B151 and went to B331 with TWRP installed by accident. What happened was that the OS was still running EMUI 3.1 but the build was saying B331. After fighting with it (and community support) I managed to get it to B331 fully and EMUI 4.0 - since then and a few custom ROMs I'm back on B151 EMUI 3.1 due to stability. Games and some apps just didn't work on the new one. The second phone was on B331 fully though - then I made the same mistake and it went to B351. This time though, the phone seems screwed. No apps will load. I can get into settings and the file manager, but no Titanium Backup and no Flashify. Going to put back TWRP and try to flash GAPPS and see if it will help me get into Play Store. From there I'll try to reinstall Flashify and flash the ZIP of the update. Will post back once done.
*EDIT*
Well that didn't work. Even after going back and trying to root the device again - then checking the option for it to not detect the dirty flash - still didn't work. Kept complaining that stock apps are already present.
I'm going to try and get some files off the device, but keep having issues. Not sure why. May just have to scrub. Will update again.
*EDIT*
With TWRP on I used "ADB PULL" to get certain files from the root system which I couldn't access otherwise for some reason. Then copied the other things (photos and such) and will now be using the UPDATE.APP to get it working. For this I formatted the SD from within TWRP and created the DLOAD folder (with no caps - so that's dload - but I'm not sure if it matters) and will be copying the UPDATE.APP. Not sure which version yet, because there was some problem with one I had downloaded before. So I need to double-check and re-download.
*EDIT*
So I've successfully flashed the UPDATE.APP from the SD card (same one the phone was claiming is corrupted). Just for reference, here is the file information and hashes.
File Name: Honor 5X_Firmware_KIW-L24_Android 6.0.1_EMUI 4.0_C567D003_United States.zip
Size: 1762266487 bytes
ADLER32: 27cb0c31
CRC32: 1d9379b9
MD2: 6517c34dc9bac0cd8680e3c4fd09d8d9
MD4: 4a803765c0ed54cb5d6853a9f365cd3b
MD5: 04f60b067d546ad71f556e44a7934dc7
SHA1: 8d2718568ac6509a40c95e42857d400395eb88d2
SHA256: 82975923172b3800d3f09f76691f2a694ab98110e3f909084a02bd566448386f
SHA384: da53b58b8e20395595590fd0cec30e56fa6a62e638ec53e46a74ebf58d051fdd7576602019bd3130ca5c00cc432715a0
SHA512: 806e0e8969c293ca8b497a786699ee306352ad6ef434552f2d23decff8a5279c7fd605e046c13f11c2f87947f5a2bdf23d78fdec6263661e68f023fd72bf4381
RIPEMD128: 9d963e5d51c9df9554fa3422da84dd27
RIPEMD160: a1e5b8f08b65dd2bb08e04d62db270ad8f4cf51a
TIGER128: 66fb4e4e4ce11cb30626aea807355f83
TIGER160: 66fb4e4e4ce11cb30626aea807355f8345f1dd79
TIGER192: 66fb4e4e4ce11cb30626aea807355f8345f1dd79dbb39488
GOST: 93774537f6ca49d4406f9d3a0316d014e1e099b34fc1cd9b968dacc870700827
The file name may be different, but as long as you got the right one you should be OK. If you have issues when copied to an SD card - verify that the file on the SD card has the correct hashes. To make it faster use CRC32. For more surety, use MD5. You can get a tool like WinMD5 to check. It's free.
So now that it's done, I'm going to set it up as a new phone and wait to see if the update comes back on. If it does, I'll get it down and upload the B351 recovery. After that I'll need to remember that I have to put back the stock recovery before running any updates. Flashify FTW.
BTW - during the initial setup after connecting to wireless it came back with the update. Pics to follow.
Files will be uploaded here: https://drive.google.com/open?id=0BzqEmGyNP_v6aTZTZDN6bWo2ZEk
*EDIT*
So the files are uploading to the folder. The screenshot is attached. Had one issue where after the update I couldn't get back into the phone. Had to wipe/factory reset. I've used FASTBOOT BOOT TWRP.IMG to take the backups of the BOOT and RECOVERY. Hopefully one of the gurus can use that and give the IMG files. I'm going to try root and get FLASHIFY to backup the stock recovery and add to the folder.

khat17 said:
This came up on one of the 5X's that I have...............
Click to expand...
Click to collapse
I don't really like to do double replies, but I guess for ease of finding the info it's better this way. Unless a mod thinks differently and wants to merge all the info.
Google Drive Link With Files
https://drive.google.com/open?id=0BzqEmGyNP_v6aTZTZDN6bWo2ZEk
This contains TWRP backups of the recovery and boot images. There's also a file called KIW-L24-B351 which was created with Flashify. I assume you can add the IMG extension to it and flash as needed.
Basically I had this update run on another phone (my wife's) and it messed with the phone due to the recovery being TWRP and not stock. My fault - forgot to do that before handing the phone back to her. I believe it happened to me before but it never messed up the phone this way. Nothing would work except core apps like settings and the stock file manager. The Play Store wouldn't even open.
Anyways - back to factory with UPDATE.APP then run the automatic update from an OTA update on wireless, then FASTBOOT BOOT TWRP.IMG and capture the backups. Then flash SuperSU to get root. Then Flashify. Files are uploaded for your convenience.
Warning that during the initial OTA it took a while. And after it was done I couldn't get into the phone with the password. Had to factory wipe/reset again and setup again. Disable passwords just in case I guess. Hope this helps others - have fun.
No major differences. I haven't really used the stock OS6 but some things look a little different. Nothing major. Will see when she's using it if it lags or has improved memory and such. Not sure if I'll be able to test with apps that wouldn't run previously for me, but will see. Tested with TransDrone and it failed. Once SeedBox information is loaded it still crashes. Only happens on OS6 so I'm sticking with OS5 on mine. Does not happen with custom roms however (from what I recall - would have to check back).

Hello every one,
I have the Honor 5X KIW-L24 rooted with TWRP, stock ROM.
I received this OTA update and saddly i pressed the update button. Now the phone is in TWRP loop.
What can I do please help. I already wipe cache and Dalvik, didnt work.

raulpcamara said:
Hello every one,
I have the Honor 5X KIW-L24 rooted with TWRP, stock ROM.
I received this OTA update and saddly i pressed the update button. Now the phone is in TWRP loop.
What can I do please help. I already wipe cache and Dalvik, didnt work.
Click to expand...
Click to collapse
Follow this video if don't know how to flash back stock recovery through adb. Then take a look at those threads how to downgrade, here, here, here. Hope it helps.

bluesky299 said:
received this B351 update over B331, also did factory reset, GUI lag seems gone, not noticing new feature
Click to expand...
Click to collapse
Same here.
It had been too many months of the Honor 5X in the closet so i almost lost track what to do but what i did was revert all the way back to Stock ROM (had to flash an extracted/saved Recovery.IMG) and then do the UPDATE.APP from Dload complete and repeat on up to the current B351.
Of course lost Root but when ready can add that back too.
Yes the Honor 5X runs much smoother now than before plus that Battery Drain issue (Remember That?) where we had to dig deep to change 4 to 0 i think, well Battery Life is also greatly improved on mine.

GrimReaper24 said:
So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.
Click to expand...
Click to collapse
I tried to update as the previous user did using TWRP and got the corrupted SD card message. I then tried to go back to stock ROM. Went into bootloop.
Been having a hell of a time getting anything to work properly since.

HELP: boot, system and vendor partition flashes failing!

I woke up to the OTA for the latest Android P update on my Essential phone this morning. Like a kid at Christmas, I couldn't wait. I started the OTA download and shortly after the download finished the install failed. So I tried it again thinking maybe there was a hiccup in the download, same result. Once I got home from work I figured I'd just download the fastboot image from the site and try that. Going through the steps as listed and all of a sudden random images would fail on flashing. All of the images flashed with the exception of boot, system and vendor.
What really has me worried is that the product name, bootloader version and serial number are all showing differently now afterwards.. which has me really worried that the phone is toast. I'm very careful with my devices; they aren't dropped and are always in a case with a screen protector. I'm not new to flashing roms or updates, I've been doing this for years and never had a problem.. and before someone asks, yes, flashing unlock and flashing unlock_critical was done before I started flashing the different partitions.

MRR0GERS said:
I woke up to the OTA for the latest Android P update on my Essential phone this morning. Like a kid at Christmas, I couldn't wait. I started the OTA download and shortly after the download finished the install failed. So I tried it again thinking maybe there was a hiccup in the download, same result. Once I got home from work I figured I'd just download the fastboot image from the site and try that. Going through the steps as listed and all of a sudden random images would fail on flashing. All of the images flashed with the exception of boot, system and vendor.
What really has me worried is that the product name, bootloader version and serial number are all showing differently now afterwards.. which has me really worried that the phone is toast. I'm very careful with my devices; they aren't dropped and are always in a case with a screen protector. I'm not new to flashing roms or updates, I've been doing this for years and never had a problem.. and before someone asks, yes, flashing unlock and flashing unlock_critical was done before I started flashing the different partitions.
Click to expand...
Click to collapse
Don't flash using the script. Flash them yourself with the commands from the script "fastboot flash system system.img" etc.

crixley said:
Don't flash using the script. Flash them yourself with the commands from the script "fastboot flash system system.img" etc.
Click to expand...
Click to collapse
That's what I did. I've never liked or trusted the scripts from those. I'm back to my Nexus 6 for now till I can hopefully fix the Essential.

Actually I've met this things yesterday when I was trying to flash the DP 3 for my phone. At the first time I stucked when flash the system image and I restarted to bootloader, after reboot I saw a strange serial number doesn't start with PM1LH, and got the no such partition error when I try to flash everything. I googled a lot and no miracle cames, so I just use the command that specified slot (which means I go over all the commands with specifying the slot a at first time and with slot b at second time) , it seems that all images can be flashed into slot a and b at this way except system image, but I re-flashed the system image to slot a and b successfully after flash all other images. And now I get my phone at DP 3, all functions work fine except the serial number is still a strange one. Hope this is useful to help you since I know it is really a bad feeling when the phone seems bricked. Also a hint is when you flash the image with specifying the slot, you may also get the error which says error remote flashing (maybe not accurate), I just re-ran the command and it works. Since English is not my native language, if any thing has grammar error please just ignore it.

MRR0GERS said:
I woke up to the OTA for the latest Android P update on my Essential phone this morning. Like a kid at Christmas, I couldn't wait. I started the OTA download and shortly after the download finished the install failed. So I tried it again thinking maybe there was a hiccup in the download, same result. Once I got home from work I figured I'd just download the fastboot image from the site and try that. Going through the steps as listed and all of a sudden random images would fail on flashing. All of the images flashed with the exception of boot, system and vendor.
What really has me worried is that the product name, bootloader version and serial number are all showing differently now afterwards.. which has me really worried that the phone is toast. I'm very careful with my devices; they aren't dropped and are always in a case with a screen protector. I'm not new to flashing roms or updates, I've been doing this for years and never had a problem.. and before someone asks, yes, flashing unlock and flashing unlock_critical was done before I started flashing the different partitions.
Click to expand...
Click to collapse
It seems I have the same problem. After flashing the latest Android P beta DP3 through fastboot, some images like system and vendor didn't flash on the first attempt for me. After multiple bootloader reboots I managed to flash everything one by one, but phone's serial number is completely messed up. At first I didn't notice this and continued to configure and use the phone for half a day since I'm on wifi, but then I realized the network is not working either. That is, it shows either no network or zero bars and I cannot place calls or use data. The situation with the network was the same when I flashed Oreo images. I checked my sim card works with another phone, and a sim card from my friend also didn't work with my phone. Could it be due to a weird serial number? If so, how do we revert it back?

What exactly is the error message when you flash those partitions? AFAIK those partitions are the big ones that give a warning about sparse header size which should just be ignored

craznazn said:
What exactly is the error message when you flash those partitions? AFAIK those partitions are the big ones that give a warning about sparse header size which should just be ignored
Click to expand...
Click to collapse
I honestly don't recall what the exact error was.. That being said, there was a new release of the platform tools after I had posted so I installed those, tried again and successfully restored the device to working order!

Which platform tools did you get? Mine are all dated 5/22/2018 after I updated... but for some reason I had to manually flash both sides... for some reason, I get an error trying to flash like this:
fastboot flash nvdef nvdef.img
The error looks like this:
Writing 'nvdef__a' FAILED (remote: No such partition.
But this works for me:
fastboot flash nvdef_a nvdef.img
fastboot flash nvdef_b nvdef.img
If a new/different set of platform tools fixes this, that'd be great.

Has anyone found a solution to this? Namely, did you manage to change back your serial number? I still have no network on my phone, I don't know if it's related.

[SOLVED] Cascading failures leading to bootloop and softbrick

Hello all. I am about done with this phone. Let me give you a quick timeline.
I had a bootloader error, so I flashed the NPN25.137-35 images to get it working
I used it for about 1 week, installing all of the OTA security updates
One morning, my phone had restarted (I know because "You must enter your pattern after a restart")
Over the course of this day, google apps starting force closing and opening some of them would soft reboot the phone.
The next day, random apps were doing it too
Finally, after one crash, the OS never came back up, it was bootlooping
Upon a hard restart, the phone only boots into bootloader.
This is where I am now. I have downloaded NPN...35-5, NPNS...93-10, and NPNS...92.14. Unfortunately, trying to flash any of these give me a "prevaildation failed security update downgrade" error on every partition I try to flash. The phone just bootloops when I try to restart it.
Things I have tried:
Using fastboot to manually install one of the 3 packages mentioned above.
Using a toolkit to automate the install of the 3 packages.
Using Motorola Device Manager (Never got it to launch)
Flashing the blankflash bin (No usable image file found)
Android OEM unlock setting was not set before this crash, so I cannot unlock the bootloader.
Praying to various deities.
Unzipping the packages, editing the *info.txt file into androidinfo.txt and rezipping to use as an update package (Invalid info.txt error)
I have no idea what to do next. I find it frustrating that Motorola doesn't differentiate between 32GB, 64GB, Amazon ads, no amazon ads, US, EU, or indian variant in it's model numbers! Everything is just "XT1687" and none of the update files are named with words, so knowing what the hell I'm flashing is impossible.
So, frustrations aside, does anyone have any suggestions as to how I can get this phone working again. On a side note, the only thing that I can think of that would cause such a cascading failure from Stock OS is RAM or Storage corruption / failing. Any thoughts on that as well?
=~=~=~=~= SOLUTION FOUND =~=~=~=~=
This may not be a good solution for anyone else that has this issue, but recently Oreo came out and the OTA update was captured. I was able to flash the new OTA because it had a higher security level and at least got the phone bootable.

Do you know what software channel you were on? E.g. retus, retla, etc? If your phone was completely up to date with the OTA, then you can't use a firmware version of less than 92-14 or 93-14. Whether or not you use 92 or 93 depends on the channel.
Locked bootloader limits other possibilities unfortunately.

Retus. I can't guarantee it, but that looks familiar to me, like I had seen it somewhere in the "about phone" section. Is there a released Stock image that has the current security patch? I can't find it on XDA and I'm not trusting androidfixfiles.info or a link in a youtube video.

93-14 hasn't been leaked yet. So you'll be stuck for now.

Kilo__ said:
I have no idea what to do next. I find it frustrating that Motorola doesn't differentiate between 32GB, 64GB, Amazon ads, no amazon ads, US, EU, or indian variant in it's model numbers! Everything is just "XT1687" and none of the update files are named with words, so knowing what the hell I'm flashing is impossible.
So, frustrations aside, does anyone have any suggestions as to how I can get this phone working again. On a side note, the only thing that I can think of that would cause such a cascading failure from Stock OS is RAM or Storage corruption / failing. Any thoughts on that as well?
Click to expand...
Click to collapse
As a last resort you might try booting TWRP in fastboot mode, download and flash the TWRP flashable version of NPNS25.137-93-14. and see if that gets you back to a working phone. Just a suggestion. I don't know if it will boot when the bootloader is locked but it is worth a try.

pastorbob62 said:
As a last resort you might try booting TWRP in fastboot mode, download and flash the TWRP flashable version of NPNS25.137-93-14. and see if that gets you back to a working phone. Just a suggestion. I don't know if it will boot when the bootloader is locked but it is worth a try.
Click to expand...
Click to collapse
The phone was completely stock. It has the stock recovery and bootloader.

Kilo__ said:
The phone was completely stock. It has the stock recovery and bootloader.
Click to expand...
Click to collapse
I get that. What I am suggesting is not installing TWRP, but booting it from fastboot, if it is even possible. Given your results trying to flash a ROM I would say not. But what do you have to lose by trying?

pastorbob62 said:
I get that. What I am suggesting is not installing TWRP, but booting it from fastboot, if it is even possible. Given your results trying to flash a ROM I would say not. But what do you have to lose by trying?
Click to expand...
Click to collapse
I've tried that with a locked bootloader myself, it doesn't allow a non-signed image to boot. OP should give it a go as a 'hail Mary' attempt, but I wouldn't be holding my breath.

I've never heard of a phone that was fully stock with no mods or flashing ever done on it getting a bootloader error. The only bootloader error I am aware of is when the bootloader and ROM build are mismatched which doesn't happen unless the phone is being manually flashed. Was the phone on a custom ROM and you tried to return to full stock? Did you purchase the phone used?
If no to both exactly what did you see when you got the bootloader error? What was the message and what was the phone doing?
People who are on full stock with a locked bootloader don't usually flash system images so your story is a little hard for me to understand unless there is more to it. Normally a factory reset would be the logical solution when your phone is acting odd--flashing a system image seems pretty extreme and it sounds like flashing the wrong system image might be the cause of your current problems.

jhs39 said:
I've never heard of a phone that was fully stock with no mods or flashing ever done on it getting a bootloader error. The only bootloader error I am aware of is when the bootloader and ROM build are mismatched which doesn't happen unless the phone is being manually flashed. Was the phone on a custom ROM and you tried to return to full stock? Did you purchase the phone used?
If no to both exactly what did you see when you got the bootloader error? What was the message and what was the phone doing?
People who are on full stock with a locked bootloader don't usually flash system images so your story is a little hard for me to understand unless there is more to it. Normally a factory reset would be the logical solution when your phone is acting odd--flashing a system image seems pretty extreme and it sounds like flashing the wrong system image might be the cause of your current problems.
Click to expand...
Click to collapse
I agree. :good:

While my phone was wholly stock, I am not new to phone rooting or custom ROMS. I bought the phone from someone who was trying to unlock it. They screwed something up and couldn't get the phone to boot. I bought it, flashed the NPN25.137-35 image after reading plenty of XDA posts about it. This one was the Retus / North America stock image. Flashed using the suggested guidelines that are along the lines of "fb_oem_mode ... flash oem oem.bin ... flash partition sparsechunk1.img" (Something like that). That got it running and once booted, it had many OTAs update in quick succession. After about a week the phone started having trouble. Google apps would crash frequently, then non-google apps started crashing and restarting my phone. After one said restart, the phone would only bootloop. I tried rebooting into recovery to do a factory reset and got the bootloader instead. I can go take a look at the bootloader and see if it says it's secure / oem or what

Kilo__ said:
While my phone was wholly stock, I am not new to phone rooting or custom ROMS. I bought the phone from someone who was trying to unlock it. They screwed something up and couldn't get the phone to boot. I bought it, flashed the NPN25.137-35 image after reading plenty of XDA posts about it. This one was the Retus / North America stock image. Flashed using the suggested guidelines that are along the lines of "fb_oem_mode ... flash oem oem.bin ... flash partition sparsechunk1.img" (Something like that). That got it running and once booted, it had many OTAs update in quick succession. After about a week the phone started having trouble. Google apps would crash frequently, then non-google apps started crashing and restarting my phone. After one said restart, the phone would only bootloop. I tried rebooting into recovery to do a factory reset and got the bootloader instead. I can go take a look at the bootloader and see if it says it's secure / oem or what
Click to expand...
Click to collapse
Try flashing just the stock recovery, as it sounds like that is corrupt. Ideally you'd want to get a recovery that was the same build as you were on after all the OTAs had installed. At least you'd hope that that would give you the factory reset option.
If that doesn't work, there's fastboot commands to erase user data, cache, which would be pretty much what a factory reset would do. Hope you had your data backed up.

Oreo OTA came out recently. Someone grabbed the update file and uploaded it. I was able to flash it and get the phone to boot. The verdict is still out on if it'll be stable.