My ASUS Transformer TF700 will not load the OS (Android 4.2)
The ASUS load screen runs for hours, but never delivers me to the desktop
When I attempt to reset, I get three options: 1) RCK(?) 2) Android icon 3) wipe data
The first two options give you a message that says "Android updating", but within 5 seconds, it crashes and says "ERROR"
My computer doesn't recognize the tablet when I connect via USB
ASUS technical support said it was a software, not a hardware problem
The tablet wasn't dropped or mishandled in any way.
How do I restore and/or upgrade the OS?
Thanks for any input and direction you can provide!
Sincerely,
B. Hartley
Blarsmanzio said:
My ASUS Transformer TF700 will not load the OS (Android 4.2)
The ASUS load screen runs for hours, but never delivers me to the desktop
When I attempt to reset, I get three options: 1) RCK(?) 2) Android icon 3) wipe data
The first two options give you a message that says "Android updating", but within 5 seconds, it crashes and says "ERROR"
My computer doesn't recognize the tablet when I connect via USB
ASUS technical support said it was a software, not a hardware problem
The tablet wasn't dropped or mishandled in any way.
How do I restore and/or upgrade the OS?
Thanks for any input and direction you can provide!
Sincerely,
B. Hartley
Click to expand...
Click to collapse
Have you tried rooting the device? This sounds like a classical bootloop problem.
First thing to try would be a data reset. If that doesn't work, then try the alternative firmware upgrade method described here:
http://forum.xda-developers.com/showthread.php?t=1755576
Dassem_ultor said:
Have you tried rooting the device? This sounds like a classical bootloop problem.
Click to expand...
Click to collapse
Is there a beginners guide to rooting that you can recommend?
Thanks!
B. Hartley
He was asking because a bad attempt at rooting the device will cause this issue, not that rooting will resolve your issue.
Related
Welcome to the comprehensive guide on rooting and unbricking your precious TF103C!
Some words of wisdom and truth
You will most likely be here because, you know, your device is bricked.
First of all, I would like to say that none of the downloadable links are made by me. I happened to find them laying around XDA after looking for a solution for a long time.
Skip this if you don't want to know the reason behind this thread
I got this device a while back (my guess is 4 months), and loved it from the start. Rooted it, of course, and soon after, it didn't want to boot anymore.
As there isn't much development going on (due to the locked bootloader), it's hard to find a solution for bricking. While scrolling, I came upon a post from member gouster3, which came to the solution below. I myself have used this successfully, and have my tablet back. In my opinion, also on rooting, there was no dedicated thread available that really explained the steps to root the device, so as a thank you to the guys who got my tablet fixed, here it is!
The rooting process
The rooting of this tablet is quite easy, really! I'll explain in a few simple steps.
Head into settings > security > then turn on unknown sources
Download the Rootzenfone .apk file. get it here
Install the app (if it is still in your notification bar you can just press the downloaded file, or you can navigate to it's location to install from there)
Turn on airplane mode before you open the app
Open the app, and hit "OK, I know, please root!" (when you press this, a number of screens and a popup will show, ignore those)
5 seconds after pressing, restart your tablet.
Hooray! You are now rooted!
Unbricking your device
Luckily, unbricking is almost as easy as rooting the phone, if you know the steps you have to follow. Here's what you could do (it worked for me) if you still have acces to DROIDboot.
As always, install the adb drivers first! get it here
# You can also make sure the correct driver is installed when plugging in the device in DROIDboot mode. In you device manager it should show up as Android Debug Bridge#
Download these files, containing a clean system. get it here
Make sure the device is turned off, and the battery is at least 50% (just to ensure a complete flash before your battery runs out)
Hold volume+ and power untill the asus screen pops up, then release the power button.
Plug in the tablet to your pc (usb cable) when DROIDboot has been loaded.
Open the downloaded folder, and find 'update_image.bat'
Right click the .bat file, and choose 'run as administrator'
A CMD screen should open on your PC indicating the flashing status. All you have to do now (assuming that it works as intended) is wait untill the process is completed.
Your tablet will reboot automatically when the process is done.
That's it! the 2 things that keep this tablet alive. I would like to send a thanks to the members who were so kind to help me out on this.
gouster3, for providing the link to the unbrick solution
Eclipse00, for giving the link to the rootzenfone apk
Monki, for giving me a clean system.img and putting effort into getting my tablet running again
To all of you, thanks!
It works on my TF103CX too. (it is same hardware).
When i bricked my TF103CX, i had around 80% of battery, but i was not able to charge,
so be careful when bricking. Always do interventions to system with full battery.
//I think, we need add our TF103C to xda device list. it will be nice.
I heared that using Intel Manufacting Tool we can get UEFI instead of Droidboot, and boot Ubuntu/Windows on IntelBay tablets. I found guide for Teclast: http://forum.xda-developers.com/android/general/teclast-x98-air-3g-tablet-9-7-2048x1536-t2913035 But i cannot find any UEFI fot TF103C. I dont want to full brick m device with trying flash it.
Here is original thread in russian language.
Thanks
Thanks for helping me rescue my tablet. Much appreciated
Could anyone please confirm if the rooting method may be used on the TF103CG (K018) model? Or in general is the app able to root any device that is anyhow Zen-related?
this don´t work if you have lillipop on tf103c, the droidboot don´t load, You only get Fasboot starting and nothing more...
i want the raw lollipop image ( system.img ) for tf103c
will this essentially work as a factory reset? mine touch isn't working; and i just want to nuke all my data off the device
Hello all, I just ordered a TF0310C (Best Buy exclusive) from woot.com which will be here tomorrow and the closest thing I can find information on is the TF103C (both are Intel processors), and just trying to find as much info on it as I can. I was unable to find any roms or anything for the TF0310c, will things from the TF103C work on the TF0310C such as rooting or custom recovery at least?
http://computers.woot.com/offers/asus-transformer-pad-10-1-android-tablet-1
Unbrick not working on tf103c running KK. It looked like it was doing something, but no luck. Any common troubleshooting tips?
m374llic4 said:
Will things from the TF103C work on the TF0310C such as rooting or custom recovery at least?
http://computers.woot.com/offers/asus-transformer-pad-10-1-android-tablet-1
Click to expand...
Click to collapse
I know its a bit late, but perhaps better than never. I'd say those devices are identical, but somehow there is a weird naming mixup. Here are the official ASUS pages for them:
http://www.asus.com/supportonly/ASUS Transformer Pad TF0310C/HelpDesk/
https://www.asus.com/Tablets/ASUS_Transformer_Pad_TF103C/specifications/
Whatever you do on the first link, it will be eventually redirected to somewhere that belongs to the second. Their specifications are also basically the same. This is still a guessing game tough, so the best would be to compare 2 build properties, partition tables etc. of those devices to know more.
Rooting will most likely work, Zenroot should do it regardless of device type.
hello,
i have tried different way to unbrick my tf103c, but none is working
i have access to fastboot
i successfully run your bat file to copy the image, but after it reboot and stays on the "asus" logo
if i launch the command after modified the name of the "AS-TF103C-v67.43-capsule.bin" into "capsule.bin", it reboot then a blue progress bar is showing, when the bar is complete the tab reboots, but again it stays on the "asus" logo :'(
do you have any advise ?
Same issue
Hello,
I have the same issue with my tf103c ; i was trying to apply a new update from asus support (to get android 5).
It didn't work and in addition to that, my device results to be bricked.
I have successfully run the bat file, but then i get stuck at Asus logo and device never boot...
Icarolo did you manage to solve your issue ? Is someone really succeed in unbrick tf103c device ?
Thank you in advance
Dead
Hi! I have an asus tf103c and i rooted it with the rootzenfone.apk but now it doesn't turn on at all. after i pressed okay, waited about 15 sec and then i restarted it, but it just turned off. And now it's dead. What should i do?
ASUS K010 (TF103C). I forgot how to enter Recovery
Hello everyone, I have an ASUS K010 (TF103C). The complete model is TF103C-MB1-BLK-DK.
I forgot how to enter Recovery. My Asus is bricked. I know it is possible to enter the recovery because a few months ago I entered and also enter droidboot mode. On that occasion I discovered pressing the buttons energy, volume +, volume - somehow, because I did not work the methods that were in different sites websites, but now I do not remember the exact way of pressing the buttons. I tried many methods but they do not work, only the "Asus looking for incredible" logo appears. The battery has a charge (I charge it manually).
If someone has this same model and knows how to enter the recovery would greatly appreciate it.:good:
I think you can enter the droidboot menu by pressing Volume Up + Power for several secondes.
i dont have acces to DROIDboot.
How can unbrick my tf103c.. thanks
i dont have acces to DROIDboot.
How can unbrick my tf103c.. thanks
Brick3d said:
Welcome to the comprehensive guide on rooting and unbricking your precious TF103C!
Some words of wisdom and truth
You will most likely be here because, you know, your device is bricked.
First of all, I would like to say that none of the downloadable links are made by me. I happened to find them laying around XDA after looking for a solution for a long time.
Skip this if you don't want to know the reason behind this thread
I got this device a while back (my guess is 4 months), and loved it from the start. Rooted it, of course, and soon after, it didn't want to boot anymore.
As there isn't much development going on (due to the locked bootloader), it's hard to find a solution for bricking. While scrolling, I came upon a post from member gouster3, which came to the solution below. I myself have used this successfully, and have my tablet back. In my opinion, also on rooting, there was no dedicated thread available that really explained the steps to root the device, so as a thank you to the guys who got my tablet fixed, here it is!
The rooting process
The rooting of this tablet is quite easy, really! I'll explain in a few simple steps.
Head into settings > security > then turn on unknown sources
Download the Rootzenfone .apk file. get it here
Install the app (if it is still in your notification bar you can just press the downloaded file, or you can navigate to it's location to install from there)
Turn on airplane mode before you open the app
Open the app, and hit "OK, I know, please root!" (when you press this, a number of screens and a popup will show, ignore those)
5 seconds after pressing, restart your tablet.
Hooray! You are now rooted!
Unbricking your device
Luckily, unbricking is almost as easy as rooting the phone, if you know the steps you have to follow. Here's what you could do (it worked for me) if you still have acces to DROIDboot.
As always, install the adb drivers first! get it here
# You can also make sure the correct driver is installed when plugging in the device in DROIDboot mode. In you device manager it should show up as Android Debug Bridge#
Download these files, containing a clean system. get it here
Make sure the device is turned off, and the battery is at least 50% (just to ensure a complete flash before your battery runs out)
Hold volume+ and power untill the asus screen pops up, then release the power button.
Plug in the tablet to your pc (usb cable) when DROIDboot has been loaded.
Open the downloaded folder, and find 'update_image.bat'
Right click the .bat file, and choose 'run as administrator'
A CMD screen should open on your PC indicating the flashing status. All you have to do now (assuming that it works as intended) is wait untill the process is completed.
Your tablet will reboot automatically when the process is done.
That's it! the 2 things that keep this tablet alive. I would like to send a thanks to the members who were so kind to help me out on this.
gouster3, for providing the link to the unbrick solution
Eclipse00, for giving the link to the rootzenfone apk
Monki, for giving me a clean system.img and putting effort into getting my tablet running again
To all of you, thanks!
Click to expand...
Click to collapse
Hi, I see that the thread is old, but I need to fix my old pad. I can do all the steps, but the problem is that I can not find a clean system I can install. I will really appreciate if someone could give me a link to one.
Unbricking tf103c
Hello,
Is it possible to unbrick somehow a device like mine. I dont have either bootloader or recovery or anything (I have two same tablets) and I mess one up. After new update touch screen stopped working so I installed something (I dont remember) i installed new recovery and then tried to install new rom...Every time I power it on (doesnt matter standar od with combos it just show asus logo in search of incredible and that's it. I managed if I press both VOL - and VOL + AND PWRBTN I get something in device manager "Unknown USB Device (Device Descriptor Request Failed)"! Is there anything I can do?
Good eveing-
I'm not sure where to start. I have a kindle fire HDX 7, and just attempted to root the device yesterday. I was able to roll back to 3.2.8, then upgrade to 4.5.2 and successfully root the device. Everything was good.
I then toyed around with a few methods to install GAPPS. With each method, if I didn't achieve the desired results, I would factory reset, rollback to 3.2.8, upgrade to 4.5.2, root... etc. A process which I went through 3 or 4 times just to try and get access to the google play store. The final method was to use the steps layed out In This Thread, which is where my current problem started.
I was not able to get the play store working correctly. I then attempted to do a factory reset, and **** hit the fan. Upon reboot, I was greeted by the stock android welcome screen, asking me to select a language, and giving me the option to make an emergency call. My best guess is something in the "system" folders/files in the gapps zip doesn't jive with FireOS. From the provided setup screen, I am able to select a language and hit next, and then it takes me through to the FireOS wireless setup screen - and that's where things come to a halt. The process won't advance, the device is somewhat functional.. I can pull down the menu from the top, I can infact authenticate to wireless, I can fully access settings, I made a MAYDAY call... But I cannot get to a home screen. In theory - I believe this to be a "soft brick" as it doesn't do anything.. Though the operating system, is running.
I was toying around in ADB trying to get it to push the 3.2.8 bin image to /storage/emulated/0/, but it wasn't cooperating. After doing some research, I came to the conclusion that the stock USB cable won't work, and I need to order a Fastboot cable? Any truth to this?
I'm just looking for some direction here if anyone has any advice. Amazon said they won't replace it - so I'm kinda stuck at this point.
Any help is much appreciated!
http://forum.xda-developers.com/showpost.php?p=59186495&postcount=9
Hi - thank you for that link. Am I to take one of the Kindle setup bin's and rename it to an apk?
Just a little vague on the instructions.
NM - I'm following it now.. Didn't realize someone else had my problem. Hoping this works - will tune back once confirmed!
You saved my kindle - thank you!
Hi, I need your help PZ.
positivehxcgo said:
You saved my kindle - thank you!
Click to expand...
Click to collapse
I have same problem like you. so Follow OnyXis's thread but not solve the problem.
May i ask you a Q? how did you solve this problem? PZ. show me instruction....
thankyou!! have a nice day~
positivehxcgo said:
[Excerpt] ... I was toying around in ADB trying to get it to push the 3.2.8 bin image to /storage/emulated/0/, but it wasn't cooperating. After doing some research, I came to the conclusion that the stock USB cable won't work, and I need to order a Fastboot cable? Any truth to this?
Click to expand...
Click to collapse
For anyone who stumbles upon this post ...
Cables DO make a difference but a 'fastboot' cable is not necessarily the solution. HDX models do not respond to fastboot cables in the same way most other android devices do; they are effectively useless on this device for recovery purposes. However, a crappy cable can create all sorts of havoc, both with data transfer and charging. Whenever a tether isn't working as expected one of the first troubleshooting steps is to switch cables. Visually it is hard to tell the difference between a good/bad cable so you may have to go through a few. Fastboot cables are generally constructed to higher standards which may fool some HDX users into thinking that was the solution. More likely any high-quality USB cable would have done the trick.
I have solved this problem.
cjdfyd2 said:
I have same problem like you. so Follow OnyXis's thread but not solve the problem.
May i ask you a Q? how did you solve this problem? PZ. show me instruction....
thankyou!! have a nice day~
Click to expand...
Click to collapse
Follow Onyxis´s thread but not skip mark ´ and after rebooting you must skip wifi connect
And then u show start stable welcome display connect wifi. that´s all thankyou onyxis and who interest my problem have a nice day
Hello,
I download from the ASUS website the firmware with version "V10.4.2.18 Only for WW SKU (Android 4.1)" and the pop-up for update de firmware appear normally to me.
Then, the TF201 restarted and since then does not passes through the ASUS Logo.
I Was on 4.0.0.3, firmware 9.4.2.28 and tried to upgrade to a superior version (my mistake as I can see now).
Even when restarting with Power + VOL DOWN the only thing that appears is :
----......................
The Device is Unlocked.
Android cardhu-user bootloader <2.10 e> released by "WW_epad-9.4.2.28-20120525" A03
Checking for android ota recovery
Booting recovery kernel image
-----------
And stays here forever... No option with the 3 icons, so I can choose USB... And neither the VOL UP during this process does nothing...
Anyone can help?
Thanks in advance
Looks like you updated to an incompatible version. The first thing you needed to do was to unlock the bootloader. Volume up will not work unless you specifically enable nvflash, which is the second thing you needed to do. Considering that you still have usb, you may be able to use fastboot to replace your recovery. From there you may still be able install an older rom. If you can get at least some kind of rom running, you'll want to enable nvflash first thing so that you can make your tablet bricksafe. Let us know if you get that far...
sl0mar said:
Looks like you updated to an incompatible version. The first thing you needed to do was to unlock the bootloader. Volume up will not work unless you specifically enable nvflash, which is the second thing you needed to do. Considering that you still have usb, you may be able to use fastboot to replace your recovery. From there you may still be able install an older rom. If you can get at least some kind of rom running, you'll want to enable nvflash first thing so that you can make your tablet bricksafe. Let us know if you get that far...
Click to expand...
Click to collapse
I installed the drives and the PC recognizes the TF-201.
But it seems that fastboot can't recognize the tablet.
Well, I didn't get so far...
But I still want to try, but I'm a little lost...
Any help?
what you see when u run fastboot devices ?
inbg said:
what you see when u run fastboot devices ?
Click to expand...
Click to collapse
From my PC device manager I can see the asus transformer Prime APX Interface and is saying that "This device is working properly.".
However, every command that I sent from fastboot the result is always the same:
< waiting for device >
I'm completely out of ideas to get this back to work...
THATS BAD do u have working adb ?
No i don't...
HOW to Reserruct from APX mode^
HI all,
I have been searching for months how to unbrick the tf201 after trying to load the official update from Asus.
I see so many users stuck like myself in APX mode with the "unlocked" message and Asus Logo.
I have tried in all described ways on the forums to get it to fastboot mode but nothing is helping.
Asus as many have written, are charging a lot for repair, I even bought another used one hoping I could upload the saved blob file from it but it is device related as I read. Is there any solution that will help?
I see a lot of advanced users creating roms and upgrades but never proposing how to unbrick this device in APX mode.
Thank you for all developers here who take the time to push things forward. :angel:
logicmate said:
HI all,
I have been searching for months how to unbrick the tf201 after trying to load the official update from Asus.
I see so many users stuck like myself in APX mode with the "unlocked" message and Asus Logo.
I have tried in all described ways on the forums to get it to fastboot mode but nothing is helping.
Asus as many have written, are charging a lot for repair, I even bought another used one hoping I could upload the saved blob file from it but it is device related as I read. Is there any solution that will help?
I see a lot of advanced users creating roms and upgrades but never proposing how to unbrick this device in APX mode.
Thank you for all developers here who take the time to push things forward. :angel:
Click to expand...
Click to collapse
Logicmate, seems there is no help how to unbrick the tf201 in APX mode...
Did you get lucky meanwhile?
I have just got a Bricked Nextbook Ares 8A from eBay for 20$, I was wanting to fix it and after some time I have reached a Dead-end and I hope you guys can figure out what I should do next.
When you try to boot it up normally, It will stay on the "nextbook powered by android" screen and do nothing, It does not go to the android booting animation.
I have tried
1. Factory Resetting it
2. Wiping cache
3. tried the "reboot to bootloader" and It just goes the bios screen and does nothing
4. Holding down the Volume - Button, but that does nothing
Hope this is all you guys need for a fix
thank you =)
Are you still stuck on this? I've been doing some work with these Nextbooks. They're actually tablet pc's.
I have 4.. all bricked, at least for the Android side of them. I JUST figured out how to install Windows (8 so far) and Linux on them and am working on being able to install their original Androids, which so far looks like it will be somewhat simple after getting the initial trial/erroring out of the way. The only object would be having an OTG cable. I could very much help with yours.
However, I'm planning to make a guide for converting Android Nextbooks to the originally intended "Tablet PC" form to try to make it easier for those who have (bricked) one of these. Soon should follow the "How to Reinstall Android" part if I can get that figured.
Do you have OTG cable?
I have nextbook ares 8A and it's soft bricked as well. how did you unbrick it with otg cable?
CornholeOS_x86 said:
Are you still stuck on this? I've been doing some work with these Nextbooks. They're actually tablet pc's.
I have 4.. all bricked, at least for the Android side of them. I JUST figured out how to install Windows (8 so far) and Linux on them and am working on being able to install their original Androids, which so far looks like it will be somewhat simple after getting the initial trial/erroring out of the way. The only object would be having an OTG cable. I could very much help with yours.
However, I'm planning to make a guide for converting Android Nextbooks to the originally intended "Tablet PC" form to try to make it easier for those who have (bricked) one of these. Soon should follow the "How to Reinstall Android" part if I can get that figured.
Do you have OTG ca
CornholeOS_x86 said:
Are you still stuck on this? I've been doing some work with these Nextbooks. They're actually tablet pc's.
I have 4.. all bricked, at least for the Android side of them. I JUST figured out how to install Windows (8 so far) and Linux on them and am working on being able to install their original Androids, which so far looks like it will be somewhat simple after getting the initial trial/erroring out of the way. The only object would be having an OTG cable. I could very much help with yours.
However, I'm planning to make a guide for converting Android Nextbooks to the originally intended "Tablet PC" form to try to make it easier for those who have (bricked) one of these. Soon should follow the "How to Reinstall Android" part if I can get that figured.
Do you have OTG cable?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
BlazeeHD123 said:
I have nextbook ares 8A and it's soft bricked as well. how did you unbrick it with otg cable?
Click to expand...
Click to collapse
Well then let's see!
Can you describe the nature of your brick?
How it happened?
Does it have TWRP?
First we'll attempt the usual methods of unbricking, which should get you your Android back. Shouldn't be too much of a hassle.
The OTG cable would come in should the usual ways fail or if you would fancy an entirely other OS. As these tablets are actually mini pc's. With the OTG cable and USB Keyboard attached, mash 'Esc' while turning on and you'll get a different screen with 6 options. Use arrow keys to navigate and select "SCU", this will bring you to your BIOS settings.
BE VERY CAREFUL WHAT YOU CHANGE HERE,
rather
don't change anything just yet until we are in contact.
I started a Telegram group for tablets of this nature.
If you've got Telegram the room's called "NextbookAresTablets"
(Telegram links not allowed I suppose)
CornholeOS_x86 said:
Well then let's see!
Can you describe the nature of your brick?
How it happened?
Does it have TWRP?
First we'll attempt the usual methods of unbricking, which should get you your Android back. Shouldn't be too much of a hassle.
The OTG cable would come in should the usual ways fail or if you would fancy an entirely other OS. As these tablets are actually mini pc's. With the OTG cable and USB Keyboard attached, mash 'Esc' while turning on and you'll get a different screen with 6 options. Use arrow keys to navigate and select "SCU", this will bring you to your BIOS settings.
BE VERY CAREFUL WHAT YOU CHANGE HERE,
rather
don't change anything just yet until we are in contact.
I started a Telegram group for tablets of this nature.
If you've got Telegram the room's called "NextbookAresTablets"
(Telegram links not allowed I suppose)
Click to expand...
Click to collapse
i just did a reformat on a stock recovery after that its just stuck at nextbook powered by android logo.
BlazeeHD123 said:
i just did a reformat on a stock recovery after that its just stuck at nextbook powered by android logo.
Click to expand...
Click to collapse
Sorry about the wait. (dickmove) I replied to you guys.
Hi everyone!
I've one old Asus Transform TF103C aka K010.
I find out that it's possible to update to Android 5 (and I need it for some app).
Right now, my firmware it's WW2.2.33.143 but on the Asus support page, there is the WW2.2.33.144 update that it's mandatory before trying to install the update to Lollipop.
OTA doesn't find anything and either manual download works. The manuals say that after copying the file the system will recognize the update and ask me about...obviously, this doesn't happen.
Someone know an "how to" about?
Problem solved!
How did you solve it?
How did you do it? I have a perfectly good TF103c that is useless because the version of Android is too old. It probably has enough ompff in the hardware to run the latest android if it was available.
if you have TF103C you can install Windows or Linux on it i still searching for drivers ( for wifi sound and charging solution ) ..
For now if you install Windows or Linux on it and your battery die you will need manualy charge battery ..
FullMetalGlicoz said:
Problem solved!
Click to expand...
Click to collapse
how did you solve it?
Hello,
I have an old Asus Tablet of the transformer style (docked to a keyboard) model TF103C or K010. It came along with Android 4.4.2 installed. I rooted the device sometime ago, and can verify that is rooted by using the app “Root Check”.
It is still a nice tablet, but with such an old version of android it tends to be limited and with less features, hotfixes, etc. Long story short, I was trying to install a new rom in a little bit of a hurry, used adb to boot into recovery mode (adb reboot bootloader), and used some images and scripts that I downloaded for a similar device (not exactly mine)…Then I went ahead and used scripts – which mostly used fastboot.exe adb.exe. The problem now is that nothing has changed as far as I can see, and I am no longer able to boot in the quick boot mode (using “adb reboot bootloader”): whenever I try to reboot the K010 connected to my computer in quick boot mode it simply restarts, goes to the splash screen (“Asus in search of the incredible powered by android”) with the caveat that there is a red blinking red stripe at the bottom of the splash screen, and then it simply turns the K010 off (battery charging screen)
Is there any hope to enter into the quick boot mode and fix that mess? Thanks for any insights.