Related
[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.
The third sentence of first paragraph of the first post (by whistlestop) in the thread:
Amazon Kindle Fire> Kindle Fire Android Development > CM7 for Kindle Fire (aka standing on the shoulders Giants)
begins by referring to "The update.zip file available here".
Available where? I've put hours into searching for it (or for any version of update.zip other than the original one that this one supposedly replaced), but with no luck.
BTW, I couldn't post this question in the thread I'm referring to because, apparently, I haven't earned the right to post in the Developers' Forum.
from the op:
If you're coming from a STOCK ROM then use this version to flash.
If you're upgrading from an EXISTING CM7 install then use this ROM instead.
click on "this" ...
So, since I haven't changed the ROM before, presumably the one I need is the first one, update-cm7-wipeall.zip. The second one, update-cm7.zip, would only be for somebody who has a previous version of the cm7 ROM installed, then? (I also have one called update-wipeall.zip that I downloaded from somewhere, but I'm not absolutely sure it's for the Kindle Fire.) In any case, do these have to be renamed to update.zip, or can they be used with their present names?
Anyway, I haven't proceeded with any attempt to install CM7 yet. I got diverted by trying to first install TWRP 2.0, using the method at teamw.in/project/twrp2/79. Unfortunately, my KF is now frozen (hopefully not bricked) for the second time since I started on the TWRP attempt. The first time the Fire came back to life pretty-much by itself. I'm waiting to see if it does that again.
Incidentally, I have a file named cm7barebones-sdcardroot.7z that I also got from somewhere or other. Is it of any interest?
it seems you have downloaded different roms
the barebones i only one part - it needs 2
which one do you want to install ?
and what's your problem with twrp ? - you have to fix this first ! - how did you install twrp ? - manually or kfu ? - there is a failure in the run.bat of the current kfu (0.9.3) - take the one from this post:
http://forum.xda-developers.com/showpost.php?p=23536888&postcount=1007
I mentioned in my previous post that I may have screwed up and bricked my KF. At first it would freeze after boot with just the words kindle fire displayed on the screen until I would hold down the power button to force a shutdown. At that time, it could at least be seen by System Profiler on my Mac, though not by adb or anything else. But now the words kindle fire flash on and off every few seconds when it's plugged into the computer or a charger, and the KF is totally invisible to the computer! Moreover, it appears dead altogether when not plugged in.
Anyway, I don't think this forum is the right place to discuss this problem of mine, so, perhaps after taking a bit of time out to deal with the rest of my life, including my other gadgets, and somehow then getting the Kindle working again (perhaps even by 'stealing' a logic board from a busted KF), I'll come back here.
Anybody who has any suggestions for me that aren't relevant to this forum should send me a PM.
Well, it won't let me post in the relevant thread so I figured why not make my own. I got a brand new kindle (my old one malfunctioned, non-root related), and was attempting to root it. Mind you, my old kindle rooted fine. I went with the utility option, and it all seemed to work fine. However, upon noticing this:
Code:
1862 KB/s (327980 bytes in 0.172s)
pkg: /data/local/tmp/Calendar.apk
Success
failed to copy 'apps\system\vending.apk' to '/system/app/vending.apk': Permissio
n denied
failed to copy 'apps\system\GoogleCalendarSyncAdapter.apk' to '/system/app/Googl
eCalendarSyncAdapter.apk': Permission denied
failed to copy 'apps\system\GoogleContactsSyncAdapter.apk' to '/system/app/Googl
eContactsSyncAdapter.apk': Permission denied
I noticed that root was NOT in fact installed. Mind you, all through the Kindle Fire Utility (latest version). I thought to myself, alright, maybe the tool is bugged at the moment. I went ahead and did it the old fashion way....or not. Again, it would not root. So, while following instructions (all of which say to use a version of twrp which is not the current version) I just try again, to the letter. Never once do I encounter a "Yellow Triangle". Instead, now my kindle fire will show the "Kindle Fire" logo at boot, with a little android guy above it.
I did install super user, but without root, it's useless really.
I even factory reset, to try and start from scratch. This however did not remove what I assume is FireFireFire (The android icon over the Kindle Fire Logo) as the bootloader, so that's a problem in itself. What am I doing wrong? What can I do here? I'd love root like on my old kindle fire, I'd love to have Google Play/Market, and a real youtube app. However, none of the things on the forums are actually rooting my kindle. I've no idea where to go from here, and help would be greatly appreciated.
In short:
- Tried to root with Kindle Fire Utility (Latest Version)
- Success in running, but no root.
- Tried to root manually.
- Never got "Yellow Triangle", could boot twrp, no root.
- Tried to factory reset.
- Did not remove FireFireFire, still weird kindle fire boot up logo.
- Lost. Please halp.
I used the older version .0.9.3 I believe it was worked perfect just like it did the first time on 6.2.2
Wee update.
I searched around for the actual twrp they mention in the thread, found it, and got to the yellow triangle. Continuing my adventure of solving my own problems. Just loaded into the kindle fire, testing root. Will edit this post if success, and tell others what my problem was (for them, if they see the same problems).
Nope, still getting permission denied errors when installing the vending and what not. Still no root...At least I got the triangle though?
Thepooch said:
I used the older version .0.9.3 I believe it was worked perfect just like it did the first time on 6.2.2
Click to expand...
Click to collapse
Care to clarify of what you used the older version?
..Interesting.
Well, it seems I have finally got it rooted.
Using the kindle fire utility to install vending and whatnot does not currently work on my device (made respect to the creator, it's just not working...).
I decided to try and download/install it manually, and I now have root. I'll see if the forums will let me send him a message.
As I said, I'd mention how I "fixed" (more like just trying everything) it. It was simple. I went and found the actual TWRP the guide mentioned.
For reference: twrp-fire-2.1.0 will NOT work (at least for me) to root the kindle. You require twrp-blaze-2.0.0RC0
Thanks for those who looked, lets see if I can break it now
http://m.youtube.com/#/watch?desktop_uri=/watch?v=AZ88CYWv0FU&v=AZ88CYWv0FU&gl=US I used this method the first time I rooted mine on 6.2.2 in the video description there is further guide for 6.3 but I used kindle fire utility for my daughter's on both 6.2.2 and 6.3 and for mine as well on 6.3 but all the drivers were already in place but and it was v0.9.3 utility I really think that the better way is pushing the files via adb to your device but the utility is easier I'm using twrp 2.0 works perfect if your gonna flash wipe everything factory/data cache dalvik and system have backups done and all your files where you can find them rom and gapps read ops well for flash instructions go the extra bit with your wipes it doesn't hurt just don't reboot on accident until your done flashing because you will have no system on your device use root explorer to rename your backups without spaces or the won't restore you will find your backups under SD card/twrp/backups/ooooooo familiarize yourself good with locations in explorer so you know where to navigate to before doing anything even close to a flash initial boots take considerable time I would say anywhere from 5- 10 mins depending knowledge of what your doing is key read read ask questions
PatchesOfPlenox said:
Well, it won't let me post in the relevant thread so I figured why not make my own. I got a brand new kindle (my old one malfunctioned, non-root related), and was attempting to root it. Mind you, my old kindle rooted fine. I went with the utility option, and it all seemed to work fine. However, upon noticing this:
Code:
1862 KB/s (327980 bytes in 0.172s)
pkg: /data/local/tmp/Calendar.apk
Success
failed to copy 'apps\system\vending.apk' to '/system/app/vending.apk': Permissio
n denied
failed to copy 'apps\system\GoogleCalendarSyncAdapter.apk' to '/system/app/Googl
eCalendarSyncAdapter.apk': Permission denied
failed to copy 'apps\system\GoogleContactsSyncAdapter.apk' to '/system/app/Googl
eContactsSyncAdapter.apk': Permission denied
I noticed that root was NOT in fact installed. Mind you, all through the Kindle Fire Utility (latest version). I thought to myself, alright, maybe the tool is bugged at the moment. I went ahead and did it the old fashion way....or not. Again, it would not root. So, while following instructions (all of which say to use a version of twrp which is not the current version) I just try again, to the letter. Never once do I encounter a "Yellow Triangle". Instead, now my kindle fire will show the "Kindle Fire" logo at boot, with a little android guy above it.
I did install super user, but without root, it's useless really.
I even factory reset, to try and start from scratch. This however did not remove what I assume is FireFireFire (The android icon over the Kindle Fire Logo) as the bootloader, so that's a problem in itself. What am I doing wrong? What can I do here? I'd love root like on my old kindle fire, I'd love to have Google Play/Market, and a real youtube app. However, none of the things on the forums are actually rooting my kindle. I've no idea where to go from here, and help would be greatly appreciated.
In short:
- Tried to root with Kindle Fire Utility (Latest Version)
- Success in running, but no root.
- Tried to root manually.
- Never got "Yellow Triangle", could boot twrp, no root.
- Tried to factory reset.
- Did not remove FireFireFire, still weird kindle fire boot up logo.
- Lost. Please halp.
Click to expand...
Click to collapse
For your information or anyone else's, the yellow triangle is the old FIREFIREFIRE, the bootloader. The new version has a android guy over the kindle logo. So now that you have the yellow triangle back, you're using the old Firefirefire.
To easily update FireFireFire, or TWRP, I recommend smirkis' scripts that run right through your kindle, no computer necessary (you must have root).
http://forum.xda-developers.com/showthread.php?t=1500935
Thanks jacewt muchly appreciated
---------- Post added at 06:12 PM ---------- Previous post was at 05:56 PM ----------
PatchesOfPlenox said:
Well, it seems I have finally got it rooted.
Using the kindle fire utility to install vending and whatnot does not currently work on my device (made respect to the creator, it's just not working...).
I decided to try and download/install it manually, and I now have root. I'll see if the forums will let me send him a message.
As I said, I'd mention how I "fixed" (more like just trying everything) it. It was simple. I went and found the actual TWRP the guide mentioned.
For reference: twrp-fire-2.1.0 will NOT work (at least for me) to root the kindle. You require twrp-blaze-2.0.0RC0
Thanks for those who looked, lets see if I can break it now
Click to expand...
Click to collapse
By the way twrp does not root your device its simply a custom touch recovery for the kindle download root checker or try an app that requires root like root explorer it will ask for superuser permissions when opened just check remember and allow to grant permission
I was able to root the KF in short order with the utility -just follow the instructions to the letter, make sure ADB is functioning correctly. If you are having trouble with ADB, just make sure that it says composite, and not straight android USB. If, when you go to device manager, and the driver isn't the composite variant, unplug the kindle from the computer, delete the driver entry from device manager, and then plug the kindle back in. If you've edited the correct driver files, it should pick it up and ID it as a composite device and you'll be on your way to root in a few minutes from that point.
Also - I didn't use TWRP, instead opting for CWM. No particular reason why, I'm just familiar and comfortable with CWM and I know from experience that it "just works".
Hello,
This isn't my first Nexus 7 (my kids had 2012's and I had a 2013: they were all unlocked and rooted). This year I got my oldest a 2013 model, and promptly set to unlocking it and rooting it. TWRP is my normal go-to for ROM jumping ease.
This time; I used CF-AutoRoot to get it rooted, I used the simple fastboot oem unlock and fastboot flash recovery twrp.img .. all appeared to have went fine. UNTIL; I booted into TWRP and none of the directories had any files. So I rebooted back to the OS, installed Astro file manager, looked around and sure enough; all the .zip files for trying out the ROMS were there (along with some gapps files).
So I installed twrp via the PlayStore, and fired it up. It can not see the files either!? (It also said BusyBox wasn't installed; I installed a couple (and un-installed them) to see if it would see them; it did not and doesn't appear to install what it needs even when it asks if I want to install it). I installed UPDATE-SuperSU-v2.46.zip earlier in the process also.
Ideas? I did use adb to push the files to / and again to /sdcard .. I can see they went via Astro, but when I'm in TWRP nothing is there? What gives?
Thank you,
P.S. I'm running 6.0.1, bone stock except for being rooted and unlocked.
67comet said:
Hello,
This isn't my first Nexus 7 (my kids had 2012's and I had a 2013: they were all unlocked and rooted). This year I got my oldest a 2013 model, and promptly set to unlocking it and rooting it. TWRP is my normal go-to for ROM jumping ease.
This time; I used CF-AutoRoot to get it rooted, I used the simple fastboot oem unlock and fastboot flash recovery twrp.img .. all appeared to have went fine. UNTIL; I booted into TWRP and none of the directories had any files. So I rebooted back to the OS, installed Astro file manager, looked around and sure enough; all the .zip files for trying out the ROMS were there (along with some gapps files).
So I installed twrp via the PlayStore, and fired it up. It can not see the files either!? (It also said BusyBox wasn't installed; I installed a couple (and un-installed them) to see if it would see them; it did not and doesn't appear to install what it needs even when it asks if I want to install it). I installed UPDATE-SuperSU-v2.46.zip earlier in the process also.
Ideas? I did use adb to push the files to / and again to /sdcard .. I can see they went via Astro, but when I'm in TWRP nothing is there? What gives?
Thank you,
P.S. I'm running 6.0.1, bone stock except for being rooted and unlocked.
Click to expand...
Click to collapse
Good day and welcome to XDA-Developers.
Your inquire has been reviewed.
Within moments your thread will be moved to the correct device location within the forum.
There your issues will be addressed by users whom know and understand your device.
Regards,
XDA Assist Team
Hello and thank you for using Q/A,
after touching on "install" you should see a field where you can enable ZIP. This button is located next to the flashing-bar.
Kind regards
Trafalgar Square
Trafalgar Square said:
Hello and thank you for using Q/A,
after touching on "install" you should see a field where you can enable ZIP. This button is located next to the flashing-bar.
Kind regards
Trafalgar Square
Click to expand...
Click to collapse
Okay; I went ahead and put a post on my site so I can show pictures on here ..
I've been using TWRP to install miscellaneous ROMS on my devices since my Nexus One (think I used CWM back then though). I have rooted all of my phones (Except my Kyocera piece of junk) and tablets with little to no issues (the occasional soft brick when learning, but that's normal in my book).
I've uploaded the screens I experience as I go alone with explanations on my openlug (.) com site. I've shut comments off since it is a server in my house that handles the sites, e-mail isn't available via my home server (haven't figured out how to bypass my ISP's restrictions).
I haven't posted enough to XDA to allow any external links (eg: images from my site). So please head to openlug (.) com and see what I wanted to show.
Time to go find something to post about so I can get past that 10 post limit ..
Thanks for any and all help; never had this happen before. I'm using Linux to work on my devices, so any .exe ideas w/not work.
Preamble
Hello, all.
Soooo I've never posted on this forum before. I've mainly leeched the invaluable info for my personal gain. I'm sure many a googler has come here trying to figure out how to root their phone. And I'm sure many a "swimmer" in Schitz Creek has come here via Google to figure out how to save their device from what had been perceived as an upgrade. I'm speaking, of course, of trying to root/unlock a phone and finding said phone "bricked".
Well, it’s time to give back.
Because yesterday, I was neck deep in Schitz Creek. After a series of dumb decisions and a lack of knowledge, I bricked the phone I’d bought for my wife’s birthday. I was just trying to be able to delete the Asus bloatware and install titanium backup and greenify. By the way, since when did Facebook become a system app? How is this a thing? Anyways, my wife deserves better battery life. And it’s fun to feel like Cyber MacGuyver by rooting a phone. But the situation went awry. My wife kept telling me that everything was going to be alright, but I know the limitations of my knowledge.
Brief aside: I'm decently computer/phone savvy, but I would, in no way, consider myself an advanced user. Sure, to my family, I'm a computer wizard. But that doesn't mean a whole lot. To them, opening up a command prompt in Windows is seen as an act of magic. And I haven't had my planeswalker spark yet. However, I have successfully rooted, and in most cases unlocked the bootloader, for several phones (HTC desire, Galaxy S3 [three different models over three years], Asus Zenfone 5, LG G4 [once pre-motherboard-death and once post (after a downgrade)], and now the ZE552KL). So I know how to at least fumble my way around adb, fastboot, odin, and various recoveries. As long as you’re at this level, or willing to learn, then you should be able to follow these instructions. End aside.
Mistakes not to make
Let’s get down to brass tacks. I made two big mistakes that you shouldn’t make. Both mistakes stemmed from the basic mistake of using a root method other than this one: https://forum.xda-developers.com/zenfone-3/help/guide-how-to-root-zenfone-3-ze552kl-t3471524
The problem with not using this EXACT method is that some of the files/programs which you need to use have specific versions which will ensure an easypeasy root. Honestly, if you properly follow the instructions in the above post, you will most likely not run into any problems. The only addition I can make is that instead of steps 6 and 7, you might find it easier to install SuperSU.zip through TWRP instead of pushing and sideloading.
Mistake 1: Not using the proper TWRP file and SuperSU file
For some reason, there are multiple versions of these files. Your SuperSU file should be 4.8MB. Using the wrong SuperSU will break the dm-verity. Your TWRP should NOT be the latest experimental version. It should be the one from November or earlier of 2016. Using the wrong TWRP will leave you unable to use the touchscreen. Trust me. I know from experience.
Mistake 2: KEEP TWRP READ ONLY
Disabling read only has no current benefits. It will just break the dm-verity. Your device will still be able to be written to if you keep TWRP read only. I have no idea why it’s called “read only”.
How to unbrick the phone
I’m sure some of you skipped straight to here. While I can’t blame you, please at least read the above paragraph. It will help you.
First I will describe the situation the phone was in, and then I will explain how I saved it. Before I continue, I want to give a big shout out to Niemer. Without their helpful post, I would’ve had no idea what to do. Thanks!
Situation the phone was in
--TWRP could not be used because the touchscreen wasn’t working.
--The dm-verity was messed up (i.e. “not started in enforcing mode").
Before you look at the solutions, make sure that your phone shows up in the windows device manager as an ADB device/ASUS ADB device/ADB composite device/etc. no matter which step you’re in. Google it to figure out how if you don’t already know.
The solution
Part 1 - Create and flash a system image which will restore your dm-verity
step 1. download the latest system “update” from the asus drivers website. I have a WW version of the phone, so I downloaded “WW_V13.20.10.152”. It’s a 1.76GB file, so be patient. I haven’t tested this method with other versions of the phone, but they should work in theory.
step 2. go into the updater script file (META_INF → com → google → android → updater-script). Open it with notepad ++.
step 3. delete from the beginning of the file up until the line “ui_print("Target: asus/WW_Phone/ASUS_Z012D:6.0.1/MMB29P/13.20.10.152-20161222:user/release-keys");”
The code that you are deleting checks to make sure that your phone is the proper model. But there is a good chance that it will mistakenly identify your phone as a phony. So we need to get rid of this code.
step 4. save the updater-script file
step 5. create a copy of the modified system update zip file. You should now have two 1.76GB files (or maybe slightly different if your phone is a CN, JP, or other model. Once again, I have a WW version of the phone). Name one of the files “realupdate.zip” and name the other “dmsaver.zip”. The names aren’t actually important.
step 6. enter dmsaver.zip. delete these four files: file_contexts, system.new.dat, system.patch.dat, and system.transfer.list. Exit out of the file. It should now be about 60MB.
step 7. turn on your ZE552KL and enter fastboot mode
step 8. in a cmd screen from your main folder (i.e. the one with adb, fastboot, and all the other files, including the ones you just created), type in the command “fastboot flash system dmsaver.zip”
step 9. if successful, you have just restored the dm-verity. You should now no longer get that sinister red text which has been ruining all your fun.
Part 2 - Install a proper version of TWRP
(This is only important if your version of TWRP won’t let you do anything because you can’t use your touch screen)
Download the version of TWRP that is included in the how-to-root post I linked to above. Also, you can download the oldest version (NOT the newest) from a sharing website which is linked to in a post on the ASUS website. It’s not in english though. Flash it to your phone in fastboot mode using the “fastboot flash recovery” command. Make sure you turn your phone off before turning it back on, or your recovery might not activate correctly.
Part 3 - Install a new version of your system.
Go into TWRP and install the zip file “realupdate.zip” that you created in Part 1 - step 5.
Part 4 - Root your phone
Follow the instructions in the link I posted earlier. It comes from this website, so you know it’s good. This time, though, you probably don’t need to unlock the bootloader
Part 5 - Breathe a sigh of relief
Parting words
I really hope this guide can be of assistance to you. The full procedure for fixing “my” phone wasn’t really recorded anywhere (although once again, big shout out to Niemer for their post). I went through hundreds of iterations of seemingly random fastboot, recovery, and adb actions before everything worked out. Because of this, I feel quite fortunate to have saved the phone, and I really wanted to give back. This community has been super helpful to me over the last seven years, and this is my chance to reciprocate. I sincerely hope that this post will help you.
I hope I didn’t forget anything. I have a sneaking suspicion that I did. In any event, if you have any questions, please post them, and I’ll try to be of assistance. Happy rooting!
thank you man but i start Part1 step8 "fastboot flash system dmsaver.zip" it's successful then i go into TWRP and install the zip file “realupdate.zip” dm-verity show again.
Thank again.
Raw firmware
I have the same issue. My phone was branded "tim italy". When i bought it, I flashed the WW version via asus flash tool, and I'm currently able to update till the last M version, which is the ......152.
If i try to update to Android N, my phone will not boot, giving me the corruption message and shutting down after 10 seconds. I also tried to perform the dm restore procedure; the dm error disappeared but the system is stuck on the Asus boot screen
I believe that the only solution is to flash a Nougat RAW firmware via asus Flash tool. Does Anyone have a download link for the N version ?
thank you, you helped me, now im on N
I guess the version matters then. So be careful with which firmware you download/install. If anyone has success with other versions, please share how you did it
I am stuck on Step 8. i put the 2 zips in where my adb and fastboot is located, and then proceed to type 'fastboot flash system...' and then it wont let me flash, any help?
Device Locked
When I flash the dmsaver.zip, receive the error "FAILED (remote: not allowed in locked state)". Apparently this with the bootloader locked, but I already unlocked before. Someone can help me unlock the bootloader again?
Further hyperlinks & solution ideas
Check out my solution and Ideas in those in links I posted in this thread at 4th of septembre 2017:
https://forum.xda-developers.com/ze...-zenfone-3-zoom-ze553kl-t3657239#post73661437
The hyperlinks in my post might also be useful, I hope.
Would be glad about your feedback, if it helped! :good:
how do you update the script file ..can u just post the file that u made somehow or email it or attach it to a message?
cant get it to work followed the instructions still getinf error code 7 trying to install lineage os
If you have lineage OS version not is a zip file but all the images (boot.img, system.img, ...) then you could try to flash the images through ADB...
if someone have the no verity issue, can you try a method for me please?
it consists on:
re-flash the rom kernel via fastboot
and run:
Code:
fastboot oem reset-dm-verity
Followed all the steps and twrp still has no touch function.
Tried all different twrp versions.
OS Version is a key
Hi everybody that has the same issue, I hope you read that so you can fix your problem.
So what I did was downloading old version of OS that autor mentioned "WW-13.20.10.152". It is necessary to download this version even if there are more newer versions. Then follow tutorial and you should be fine.
So again, thanks OP for posting this. You helped me a lot!