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.
While attempting to flash a modified OTA flashable zip I managed to disable the touchscreen by NOT flashing thee important binary blob leaving me in a permanent apx mode and booting into android OS without a functioning touchscreen, Since the update is to 4.3 the device requests permission for adb so no adb reboot recovery... Also cannt access fastboot just apx mode
Procedure to fix coming soon, testing fix at the moment have successfully installed apx drivers
Update: wheelie is currently incapable of reading Tegra notes blob.bin file, unrecognized MCRVER gives it a hang at the moment so cannot take it any further just yet...
Shaky156 said:
While attempting to flash a modified OTA flashable zip I managed to disable the touchscreen by NOT flashing thee important binary blob leaving me in a permanent apx mode and booting into android OS without a functioning touchscreen, Since the update is to 4.3 the device requests permission for adb so no adb reboot recovery... Also cannt access fastboot just apx mode
Procedure to fix coming soon, testing fix at the moment have successfully installed apx drivers
Update: wheelie is currently incapable of reading Tegra notes blob.bin file, unrecognized MCRVER gives it a hang at the moment so cannot take it any further just yet...
Click to expand...
Click to collapse
Good and bad news, but an horizon... Thumbs up Shaky. Can't wait as similar problem to you.
Note
For those who are having problems with ADB/Fastboot commands not working correct on NT7, update them to r16.01
Linux Kernel for SHIELD (and Tegra Note 7) https://github.com/linux-shield/kernel
Shaky156 said:
Procedure to fix coming soon, testing fix at the moment have successfully installed apx drivers
Update: wheelie is currently incapable of reading Tegra notes blob.bin file, unrecognized MCRVER gives it a hang at the moment so cannot take it any further just yet...
Click to expand...
Click to collapse
What happens if one "nvflash --create", would that take one to the recover straight after boot or is the recovery partition also wiped?
e8hffff said:
What happens if one "nvflash --create", would that take one to the recover straight after boot or is the recovery partition also wiped?
Click to expand...
Click to collapse
Nvflash currently doesnt support tegra 4 or atleast looks like that to me as it hangs on rcmver, doesnt pass that, will test... Also that doesnt take you to recovery it formats everything
Shaky156 said:
Nvflash currently doesnt support tegra 4 or atleast looks like that to me as it hangs on rcmver, doesnt pass that, will test... Also that doesnt take you to recovery it formats everything
Click to expand...
Click to collapse
You mahybe correct. The best I could get out of it was reporting my chip UID. Hasn't the Shield users been using nvflash?
e8hffff said:
You mahybe correct. The best I could get out of it was reporting my chip UID. Hasn't the Shield users been using nvflash?
Click to expand...
Click to collapse
Afaik shield users havent been using nvflash
Progress has been made on this...
EDIT: same issue though reading uid fails
EDIT2: Although i have the correct files apart from nvflash, I Talked to someone from nvidia, they have but wont release the nvflash cmd tool for tegra note 7, it wont happen, thread can close
Thread closed at the request of the OP.
MD
hi xda-ders
this is my first post , and i've been re-directed here to ask questions about my acer a501. so i've had my a501 for 20 months, before it suddenly developed the well documented issue of mainboard memory failure which cannot be fixed by software. i returned my a501 to acer nz to be repaired under warranty, and they replaced the mainboard. unfortunately this mainboard was also faulty with no wireless, so i had to return it again for another round of repairs.
i finally got my a501 back on friday, and realised that the mainboard replacement was on android 3.2. previously i had upgraded to android 4.0.3 using the acer iconia tab update app, but this doesn't seem to work anymore.
1. when i do a settings - about tablet - system update check, i get the message "network coverage is currently poor. please move to a location with better coverage to continue." googling this i find that acer no longer does OTA updates and have shut down their servers so i can't do it this way.
2. i called acer nz for support on upgrading to 4.0.3. they directed me to the acer nz support website where apparently i can download the update.zip and install it manually. following the instructions exactly, i can't get this to work and keep ending up with the android robot with a yellow ! icon.
can somebody help me with the steps needing to update android 3.2 to 4.0.3 manually? i've tried searching the web and xda but many of the threads are quite old from 2 years ago when ics was first released. thank you
my tablet info:
model number = A501
android version = 3.2
baseband version = Cust:R3C01 Config:R3S/3 Conf:R3C01 Protocol:R3B01 App:R3C01
kernel version = 2.6.36.3+
build number = Acer_A501_4.031.24_COM_GEN1
Did you try to update with a 2gb micro sd? The standard recovery doesn't recognize "big" micro sd., from what I saw.
One thing: I'm not 100% sure you can update your tablet without updating recovery too. Just in case, retrieve the cpuid of your tablet, it could be helpful if it goes in boot-loop!!
Same request but different scenario
So I have Acer A500 currently running Honeycomb version installed by tool "tdv4_rollback_rom". This tool helps you to get on with valid cwm recovery and rooted honeycomb rom. I assume this brings me to HC bootloader, which is not compatible with any ICS ROM. So if I understand correctly, I will have to upgrade to unlocked V8+ ICS Bootloader and from that point on flash ICS ROM (Lightspeed or Tabooney...). If my understanding is right, I am following correct guides to get unlocked ICS Bootloader on tab using AUTOMATED A500APXFlash tool. Everything goes fine and I do get PASS screen at end. After reboot, I boot in Skrilax V8 bootloader and then boot into recovery to flash ICS ROM. After flashing any ICS ROM, I am expecting my tablet to boot into corresponding ROM but after booting into primary kernel message, I am stuck at boot logo (acer, green droid based on ICS ROM I picked). No matter what I do, I can't pass this splash screen.
So far, I have tried bunch of things,
- tdv4_rollback_rom tool
- Afterota (to flash custom recovery and bootloader)
- APXManager to get unlocked ICS Bootloader V9 on tablet (Automatic and Manual as well). This has ran successfully (PASS message) multiple times, while there were times where it got stuck in second stage of uploading.
- At end, I have tried BabSector, "a501 A.bat" ran successfully, Booted in recovery formatted System (twice), While running "a501 B.bat" (in APX Mode) as following step, I got error message "bootloader status: Bct Write Failed (code: 22) message: nverror:0x42008 (0x6042008) flags: 0"
Anytime, when I am stuck in APX mode (while doing any of the above mentioned steps), I run back to tdv4_roolback_rom tool to get proper recovery and HC rom running on tablet.
So is it partially bricked or I am following some wrong steps?
Any suggestions to fix this issue? Or I should keep HC running on tablet? I am open to run pure ICS stock as well with stock recovery and bootloader, but darn thing won't pass the boot logo.
Thanks
omniastrider said:
Did you try to update with a 2gb micro sd? The standard recovery doesn't recognize "big" micro sd., from what I saw.
One thing: I'm not 100% sure you can update your tablet without updating recovery too. Just in case, retrieve the cpuid of your tablet, it could be helpful if it goes in boot-loop!!
Click to expand...
Click to collapse
actually i tried updating with a 1gb microsd but it didn't work. i have 2gb and 16gb cards at hand, but neither of them works so i don't think it's the microsd that is the problem.
how do i update recovery? i'm happy to use other types of recovery if i can get to 4.0.3 but so far all my reading hasn't showed any full factory acer rom that i can flash. :crying:
tildespace said:
actually i tried updating with a 1gb microsd but it didn't work. i have 2gb and 16gb cards at hand, but neither of them works so i don't think it's the microsd that is the problem.
how do i update recovery? i'm happy to use other types of recovery if i can get to 4.0.3 but so far all my reading hasn't showed any full factory acer rom that i can flash. :crying:
Click to expand...
Click to collapse
In the old times (a couple of years ago) I managed to update my Acer A500 from 3.2 to 4.0.3 (the leaked one from Acer) without installing another recovery, but maybe for the A501 the things are a little different.
omniastrider said:
In the old times (a couple of years ago) I managed to update my Acer A500 from 3.2 to 4.0.3 (the leaked one from Acer) without installing another recovery, but maybe for the A501 the things are a little different.
Click to expand...
Click to collapse
in the old times on my previous tablet, i updated my a501 using the OTA check update app from within the tablet. i assume that is directly from acer, however it seems the servers have been shutdown and therefore i can't use that method anymore. hence why i'm asking if anyone here on xda has the full 4.0.3 that i can use to overwrite 3.2 version.
tildespace said:
in the old times on my previous tablet, i updated my a501 using the OTA check update app from within the tablet. i assume that is directly from acer, however it seems the servers have been shutdown and therefore i can't use that method anymore. hence why i'm asking if anyone here on xda has the full 4.0.3 that i can use to overwrite 3.2 version.
Click to expand...
Click to collapse
I know, I know, no more OTA from Acer. Have you taken a look here? There's a leaked ICS rom there...
omniastrider said:
I know, I know, no more OTA from Acer. Have you taken a look here? There's a leaked ICS rom there...
Click to expand...
Click to collapse
cool thanks for that link. i have downloaded the ICS rom and opened up the zip file, it doesn't look like a normal update.zip? what does leaked rom mean, not original from acer?
i'm worried that i might brick my tablet since i'm new at this flashing thing.
tildespace said:
cool thanks for that link. i have downloaded the ICS rom and opened up the zip file, it doesn't look like a normal update.zip? what does leaked rom mean, not original from acer?
i'm worried that i might brick my tablet since i'm new at this flashing thing.
Click to expand...
Click to collapse
"Leaked" means that it comes from Acer, but it's not official (maybe it was a beta, maybe not, I don't know). From what I read, you only have to follow this flow chart in order to install it. Remember to save your data before flashing, and if you're not sure, don't flash!!
Please Help,
Two days ago my A500 freezes!
Had to force a shutdown, at start got stuck on Acer logo!
Tried the 4 official updates everyone talked about with no luck!
The only one that solved my problem was the original 3.x Honeycomb ROM:
SD_Acer_A501_Android 3.2.1_4.066.29_COM_GEN1
That Solved!
Then I downloaded a suposed Acer A500 Stock Rom to update from 3.2 to 4.0.3. Didn't notice was a rooted one, update completed then got an error.
ROM used: Acer_A500_Stock_ROM_v1.054.00_ww_gen1_rooted_4.0.3 _ICS
Now I can not even load stock recovery (vol-+ power), only power light turns on and off as i press power. No vibrate, no acer logo only a black screen!!
Can anyone help? Ideias?
PS: The A500 always was stock, no root, no special recevory, etc.
Thanks,
PereiraMan.
update
:fingers-crossed:
For the record it seams that my A500 is in APX mode.
After using a fresh install of Windows 7 with th Acer drivers, the fantastic OTA Tool: http://forum.xda-developers.com/showthread.php?t=1675939
Detected my A500 as in APX mode, and has an advanced feature specific for those like I stuck on APX mode that let's us Install Bootloader and Recovery.
First try didn't work: I downloaded and tried to install TWRP recovery and ICS Bootloader, it was stuck on FASE 2 (flashing recovery).
Will try this night with A500_Thor_Recovery_1.7.3.a500apx. :fingers-crossed:
Thanks,
PereiraMan.
No luck yet
Not giving up... no yet!
On the Windows Device Manager it detects tha A500 like "Acer USB Boot-recovery Driver"
The other night a think it was different, something like APX...
Any way in the system tray on the USB devices always shows APX device.
APX Tool and OTA Tool detect the A500 in APX mode, but none of them can flash a recovery... Windows Drivers issue?
Because ADB via command prompt doesn't detect the device!
The tools use ADB commands, right? And ADB shoud detect the device in APX mode, right?
Any APX expert?
More info:
in the driver details I have this values: "USB\VID_0955&PID_7820\5&24FD8A70&0&1"
Read somewhere the last digits are the CPUID... calculated the SBK. Hope is correct.
Thanks,
PereiraMan.
ok, first of all we need the patched bootloader to be able to flash a recovery and a custom ICS+ Rom. But to do that, you need to root first, using the ICSRoot tool, see the root guide in my sig for the download.
Then while you are there download the babsector.rar file - this file will install the patched bootloader and a recovery, but more importantly it will output an error if your tab is one of those which has a faulty memory chip. If this is the case then nothing you do will fix this issue
Put your tab into APX mode(do not use otatool or a500 manager to do this for you, you need to do it manually via the buttons) click the a.bat file and follow the onscreen instructions.
IF the bat file runs without error...congratulations, you now have the patched bootloader and recovery. But what you do not have yet is a workable rom...You must now boot DIRECTLY TO RECOVERY (PWR VOL DOWN).
The patched bootloader does not work with HC Roms which is what you still have at the moment, even tho you tried flashing ICS previously. So, flash one of the custom ICS+ roms.
The best thing to do though is wipe all your userdata first before you flash the rom. You can try and get away without the wipe but its not best practice!!!!
Once the rom is flashed you can reboot.
Just a couple of things to note - the a500 is very old now, and so are alot of the roms. You may still have trouble, altho you will have a running system, it may not run as you might want!!! I have not used my tab for this very reason...it freezes or takes along time to do anything like surf the net, emails etx...even using it as a media player seems to be too much for it,lol - I have not tried any of the JB roms, the tab is still on one of the "Flex" series of roms.
But anyway good luck with everything, feel free to ask if you have any issues
rgds dibb
Thanks dibb,
I will try to root, but don't I need the CPUID/UID for that? Everyone tells me that without it I can do nothing...
I'm stuck in APX (my A500 only turns on in apx I have nothing else) and have no CPUID... (i'm installing a Linux right know on a secondary laptop to solve that issue)
Also ICSroot link is not working!
About the A500, I bought it almost 4 years ago it had already ICS update available OTA that I apply in the first day... True it's a litle slow now when loaded with apps... A couple days ago when recovered from the "acer logo" symptom with acer recovery and honeycomb ROM I was susprise how fast it was (and yes without any apps). I was thinking about a light costum ROM or Cyanogen UnOfficial stable (version 10 i think) when i recover it.... Hope so! :fingers-crossed:
Thanks,
PereiraMan.
will try to root, but don't I need the CPUID/UID for that? Everyone tells me that without it I can do nothing...
Click to expand...
Click to collapse
YES YOU DO NEED CPUD!! Sorry, did not realise you did not have that. NONE of the auto tools will work without'!-This changes everything.
You are limited to a couple of choices to retrieve your UID
Hope your PC has stored it by you previously having Tabconnected to Pc via USB- there's a tool in my CPUIDGuide,1 forget nowwhat it is called.EDIT: USBdeview
OR
installing Linux.
I am pressed for time right at this minute will await
your reply as to this development
dibb
Success!!!
Finally Got my uid via Linux, was hard to install Linux, all my old CD's where broken, had to create a usb pen!
Anyway, my A500 UID: 0x37001474420a157
But that 17 digits, so realized the leading 0x is not part of the UID!
Flashed Bundle 17 with APX Flash Utility!
Now going to try some ROMs...
Thanks dibb!
PereiraMan
CyanogenMod
Hi dibb!
Just for the record ended up with cyanogen 12 tegraowners ROM (android 5.0.2)!
And did a litle CPU overclock with Thor Recevory from 1ghz to 1.2ghz..
I'm now a happy user of a Acer A500 with 4 years and a new life!
Thanks,
PereiraMan.
PereiraMan said:
Hi dibb!
Just for the record ended up with cyanogen 12 tegraowners ROM (android 5.0.2)!
And did a litle CPU overclock with Thor Recevory from 1ghz to 1.2ghz..
I'm now a happy user of a Acer A500 with 4 years and a new life!
Thanks,
PereiraMan.
Click to expand...
Click to collapse
Thats awesome news my friend, glad to help
I'm trying to root the brand new model with MediaTek processor (Z300M) but nothing has worked so far. Any suggestions?
I'm surprised there is no root for this ?? I'd love to get rid of all the ASUS bloatware??
any luck?
for any mt8163 devices anywhere?
Damn, hoped by now there would be something... oh well... back to the cave.
Asus ZenPad 10 Z300M (P00C) Android 6.0
Has Anyone had any luck finding a way to unlock the bootloader on a Z300M (P00C) (marshmallow 6.0, Android security patch level 1 December 2016)
I'm trying to root it so I can change the ROM on it to the new Android 7.1 . I've been reading all the post in hear about it, Tried all the intel stuff (no joy) KingRoot doesn't work, Won't pay OneClick.. Came across some dodgy webpage with a program called Autoroot tools V3.0 Which wants you to install some software first before it lets you download the program....... very suspect.. so no. Back to square one No Unlocked Bootloader, no root....... can anyone help ?
You may find this useful ..
https://forum.xda-developers.com/an...d-10-z300c-t3214802/post65188654#post65188654
Asus have released their bootloader unlock tool, it may be somewhere to start. I'd suggest you check the support section of the asus website for the Z300M. I've downloaded, installed and tried to run however it failed. I've updated the tablet to android 7.0 and made no other modifications, tried on the home WiFi and hotspot through my phone. Failing them two I attempted to reflash 7.0 in the hopes that would help... The tablet doesn't pick up the files. Possibly because it isn't so much an update?
Either way I've become stuck on this whole situation too. It's quite a pain and I don't have the knowledge to start from scratch, I'm not even sure where to start.
Guys, I'm pretty sure you don't need to unlock the bootloader to flash anything to that tablet. The Z300M and the Z380M are basically the same tablet, just with a different screen size. I've had a fully working TWRP custom recovery posted for the Z380M since April. There's also a version of Mediatek Smartphone Flash Tool that lets you flash it without any bootloader unlock. So here's what you need to do, in a nutshell, to build and flash a custom recovery for the Z300M:
Make a scatter file for this device. The partition layout may be the same as the Z380M, in which case you can just use mine (just change the project name). If not, you can build one from the GPT by reading off the first 4 or 5 sectors from the flash ROM with Flash Tool's readback function and converting the LBA addresses to byte addresses.
Take my recovery source code and import the compiled kernel from the Z300M.
Change TWRP's theme layout (e.g. to landscape mode).
Change the model/device names to ones corresponding to the stock names.
Compile and flash it with SP Flash Tool
I'll be glad to help build the scatter file, etc. Just PM me the GPT.
Removed all information due to the wrong process being used.