I recently purchased an Asus Transformer Prime TF201 from ebay with a custom rom preinstalled. I was not a fan of said rom so I decided I would do a factory reset and thought that the previous owner would back up the original OS. Now every time I boot up my prime it goes to CWM... I have tried every option but I am stuck in a boot loop with CWM. I tried to restore from a backup, when it is complete it says it was successful but I am still stuck in this loop. I have downloaded ADB and when I write "adb devices" it comes back with nothing. When I write "adb logcat" it comes back with "-waiting on device-". So I assume the drivers were not set up. I have downloaded the drivers but I cannot get them to install properly through my Windows XP system. It just says failed every time. I'm guessing it is not recognizing it since it has no operating system. What should I do? I feel like I have exhausted all resources. I can give any detailed information that you want, but just be specific about what you want from me. Thank you in advance, I am pulling my hair out at the moment.
cjoconne said:
I recently purchased an Asus Transformer Prime TF201 from ebay with a custom rom preinstalled. I was not a fan of said rom so I decided I would do a factory reset and thought that the previous owner would back up the original OS. Now every time I boot up my prime it goes to CWM... I have tried every option but I am stuck in a boot loop with CWM. I tried to restore from a backup, when it is complete it says it was successful but I am still stuck in this loop. I have downloaded ADB and when I write "adb devices" it comes back with nothing. When I write "adb logcat" it comes back with "-waiting on device-". So I assume the drivers were not set up. I have downloaded the drivers but I cannot get them to install properly through my Windows XP system. It just says failed every time. I'm guessing it is not recognizing it since it has no operating system. What should I do? I feel like I have exhausted all resources. I can give any detailed information that you want, but just be specific about what you want from me. Thank you in advance, I am pulling my hair out at the moment.
Click to expand...
Click to collapse
You try to just flash a new rom? Also follow these steps?
http://forum.xda-developers.com/showthread.php?t=1514088
I cannot flash a new rom since i can not move any file onto the internal memory since my computer does not recognize my tablet. I also cannot follow those steps since I cannot access my tablet.
anyone?
Use a micro-sd card?
Or SD card if you have the dock...
I don't have an SD card, I will have to pick one up tonight. I figured that was my only option. But if my computer cannot recognize my tablet, will it once it is in my tablet? I could always put a rom on the sd card with another computer and than move it over and try to flash. Is there anyway I could find the stock rom, I have searched high and low.
cjoconne said:
I don't have an SD card, I will have to pick one up tonight. I figured that was my only option. But if my computer cannot recognize my tablet, will it once it is in my tablet? I could always put a rom on the sd card with another computer and than move it over and try to flash. Is there anyway I could find the stock rom, I have searched high and low.
Click to expand...
Click to collapse
Getting an sd card is not going to fix your problem. You are stuck in a cwm bootloop which is called brick type 1a and you need to sort that first.
The link in the post above takes you to the page that shows you how to get out of brick type 1a but without adb you are not going to be able to do it so you need to get drivers working on your machine or go onto another machine and get drivers installed then fix that first.
Once that is fixed you have 3 options. You can either restore your backup and it should now work or you can adb push a new rom to the internal sd and flash that or you can flash TWRP thru fastboot and that will give you access to an external sd once you have bought one and flash that way.
Either way you are going to have to fix brick type 1a first.
HTH
Hi all I've updated my G9 80 many times and tried all the available ROM's with a few hiccups but have always managed to recover the tab with the info on this forum. On my latest update the tablet appears to refuse to load a ROM from the SDE menu? If I boot the tab normally it halts at the ARCHOS boot screen but I can see the tab in device manager/Disc drives as ARCHOS_A80S but not in the explorer window and the USB is shown as an unknown device. If I boot up into the SDE/Archos A80S Recovery menu and then select (Update Firmware) it opens up a drive on my win7 system labeled A80S_REC as per normal and I can transfer the (fimware_archos_it4.aos) update file across to the tab but when I select (OK to disconnect) the tab starts the update in progress which fails after about 20 seconds with a Update failed (221) message. This is the method that has always solved any problems in my previous operating excursions but after a few days of trying to solve this problem I'm now at an impasse has anybody any ideas or is it time to upgrade to the Gen 10 and retire this tab as bricked
Thanks for any info
Ken.
I made the basic mistake of trying to update with an older ROM (kicks own backside for making such a basic mistake) aaaaa well back to trying to brick it again but I happy as the screen of my old backup Hannspad is doing my eys in
The 221 error usually means that you have tried to install an older official Archos firmware than the last official Archos firmware you had installed.
If you know exactly which one that was, then you can find a link to download it hidden in-between all of the other rooted and custom ROMs in this list.
Go into Recovery / SDE and do a full Reformat. Do not try to install anything, just go thru the steps (without connecting to your computer) and let it fail the firmware upgrade process. Then exit out so your tablet turns off. Then start back up in Recovery / SDE and do another full Reformat. Then connect to your computer and copy over the Archos .aos file.
If it still shows a 221 error after that, then you may have at some point installed a higher official Archos firmware. Start all over with the above steps, but with the next higher Archos firmware download.
I really do not know just what might happen if say you had the official Archos 4.0.7 firmware installed and then installed a 'rooted' 4.0.25 or 4.0.26 firmware. That could possibly somehow make the tablet only allow you to install that specific official Archos firmware afterwards also.
Let us know what luck you have?
Now OK
Hi I came to the same conclusion myself and solved the problem 5 min after starting the thread but thanks for the info, it's much appreciated. I cannot understand how I missed this for so long as I've loaded the majority of the roms on this site. I solved it by downloading the latest rooted Firmware 4.0.26 from surdu_petru (GENIUS ROM MAKER )
Thanks again
Ken.
55mls said:
The 221 error usually means that you have tried to install an older official Archos firmware than the last official Archos firmware you had installed.
If you know exactly which one that was, then you can find a link to download it hidden in-between all of the other rooted and custom ROMs in this list.
Go into Recovery / SDE and do a full Reformat. Do not try to install anything, just go thru the steps (without connecting to your computer) and let it fail the firmware upgrade process. Then exit out so your tablet turns off. Then start back up in Recovery / SDE and do another full Reformat. Then connect to your computer and copy over the Archos .aos file.
If it still shows a 221 error after that, then you may have at some point installed a higher official Archos firmware. Start all over with the above steps, but with the next higher Archos firmware download.
I really do not know just what might happen if say you had the official Archos 4.0.7 firmware installed and then installed a 'rooted' 4.0.25 or 4.0.26 firmware. That could possibly somehow make the tablet only allow you to install that specific official Archos firmware afterwards also.
Let us know what luck you have?
Click to expand...
Click to collapse
Hi all,
I recently got a new Dell Venue 7 3740 (yeah, not my first choice, but it was free for buying a computer). Anyway, started reading up on how to root the thing. I have a couple of apps that require root.
I found this thread: http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
and also the main Dell page: http://opensource.dell.com/releases/Venue_7_3740_Merrifield/developer-edition/
Following Dell's guide to rooting appears to NOT root it. Installing Root Checker confirms I don't have root. Unbricked it and got it back up from 4.4.2 to 4.4.4. By reading the first guide for the 3840, my question is ...
Is the boot image linked there compatible with my 3740?
(yeah, I know this should be in the developer section ... unfortunately I don't have enough posts ... also, I am familiar with rooting/flashing/etc, my first device that I put CM7 on was the original Galaxy S1 ... and I have CM10 on my S3.)
Tried, failed
Yeah I got this tablet with a PC too and tried rooting. It FUBAR'd on me and I had to wrestle with unbricking it. Which sorry to say is a job and a half, the images on Dell's site are corrupt for this WiFi only version (no partition.tbl file, system image incomplete). Ending up downloading the LTE versions firmware to get the missing files and rewriting the batch as the file names for the fastboot commands were wrong too. And even then the tablet wouldn't boot, so I had to store the OTA on an SD card and use recovery to flash it. Unfortunately that leaves me with 4.4.2 and the dreaded clock and browser issues. And OTA doesn't work, it keeps saying no updates are available. Spoke with a Dell rep who said OTAs were suspended and to try again in a week but I think OTA was broken for me when I tried rooting and boot loader was unlocked (which the PDF on Dell's site warns you about).
So now I have a working tablet that skips hours ahead and has general stability issues.
reaper-death said:
Yeah I got this tablet with a PC too and tried rooting. It FUBAR'd on me and I had to wrestle with unbricking it. Which sorry to say is a job and a half, the images on Dell's site are corrupt for this WiFi only version (no partition.tbl file, system image incomplete). Ending up downloading the LTE versions firmware to get the missing files and rewriting the batch as the file names for the fastboot commands were wrong too. And even then the tablet wouldn't boot, so I had to store the OTA on an SD card and use recovery to flash it. Unfortunately that leaves me with 4.4.2 and the dreaded clock and browser issues. And OTA doesn't work, it keeps saying no updates are available. Spoke with a Dell rep who said OTAs were suspended and to try again in a week but I think OTA was broken for me when I tried rooting and boot loader was unlocked (which the PDF on Dell's site warns you about).
So now I have a working tablet that skips hours ahead and has general stability issues.
Click to expand...
Click to collapse
Hmm ... Interestingly enough, I ran through the unbrick procedure from Dell, and didn't have any issues with it whatsoever. I'm not sure if they updated the TGZ since you updated.
I have read that root is for ADB to start with. Can anyone confirm this? If so, then which package could I get for a superuser binary?
ProfM2 said:
Hmm ... Interestingly enough, I ran through the unbrick procedure from Dell, and didn't have any issues with it whatsoever. I'm not sure if they updated the TGZ since you updated.
I have read that root is for ADB to start with. Can anyone confirm this? If so, then which package could I get for a superuser binary?
Click to expand...
Click to collapse
I did this process just a couple days ago so everything I pulled from opensource.dell was current. The unbrick tgz on the site shows up as 128mb for the wifi only A1195 and the A5195 shows as 821mb (odd). When I extracted the tgz it said "unexpected end" or something like that on the system image. Then again when I extracted from that extracted tgz.
Following the root process initially worked and the temp cwm recovery let me flash the supersu update. It booted with su just fine and I tried a couple apps that needed root and they worked. Once I rebooted again the tablet showed up with a USB icon and would go no further. Never having dealt with Intel SoC drivers it took me a while to get them installed properly, and then I eventually understood what "full power off" meant lol.
Do you know how I can relock the bootloader and get OTA working again, assuming I'm already on 4.4.2 from the OTA zip installed via recovery?
Thanks.
reaper-death said:
I did this process just a couple days ago so everything I pulled from opensource.dell was current. The unbrick tgz on the site shows up as 128mb for the wifi only A1195 and the A5195 shows as 821mb (odd). When I extracted the tgz it said "unexpected end" or something like that on the system image. Then again when I extracted from that extracted tgz.
Following the root process initially worked and the temp cwm recovery let me flash the supersu update. It booted with su just fine and I tried a couple apps that needed root and they worked. Once I rebooted again the tablet showed up with a USB icon and would go no further. Never having dealt with Intel SoC drivers it took me a while to get them installed properly, and then I eventually understood what "full power off" meant lol.
Do you know how I can relock the bootloader and get OTA working again, assuming I'm already on 4.4.2 from the OTA zip installed via recovery?
Thanks.
Click to expand...
Click to collapse
You better redo the unbrick procces cause as you are now, you won't be able to update your tablet and 4.4.2 has some issues with the clock and browser. The best way to root is by thetered cwm, I did it and it's working great.
reaper-death said:
I did this process just a couple days ago so everything I pulled from opensource.dell was current. The unbrick tgz on the site shows up as 128mb for the wifi only A1195 and the A5195 shows as 821mb (odd). When I extracted the tgz it said "unexpected end" or something like that on the system image. Then again when I extracted from that extracted tgz.
Click to expand...
Click to collapse
This is quite odd. From the documentation, it appears that the A195 is for the LTE version, and the A150 is Wifi only. Since I have the 3740 Wifi only, I only pulled the A150 version.
The Unbricking process was very straightforward and everything went smoothly, and after it rebooted, it prompted that there was a system update from Dell, and that took me from the 4.4.2 from the TGZ, to 4.4.4
ProfM2 said:
This is quite odd. From the documentation, it appears that the A195 is for the LTE version, and the A150 is Wifi only. Since I have the 3740 Wifi only, I only pulled the A150 version.
The Unbricking process was very straightforward and everything went smoothly, and after it rebooted, it prompted that there was a system update from Dell, and that took me from the 4.4.2 from the TGZ, to 4.4.4
Click to expand...
Click to collapse
http://opensource.dell.com/releases/Venue_7_3740_Merrifield/developer-edition/Doc/OSS_A150&A195.pdf
* For Wifi-only device on A150 and Wifi / LTE device on A195
I see it now, I think I was misinterpreting the above statement which means I've been flashing the A195 rom this whole time. Thank you all for your help! :good:
After getting my 3740 back to "Unbricked" mode, and OTA upgraded to 4.4.4, it appears that I'm completely locked out of the rooting process.
I've tried to start over with the Dell info (unlocking bootloader), however, neither of my PC's will detect the tablet when using xFSTK (one PC - Win8.1-64bit, other XP-32bit). The tablet IS detected, however, it appears that the drivers are no longer correct(?).
I normally run Ubuntu, and thats where my Android development setup is on ... I see that xFSTK is available for Linux ... has anyone used it? or would I be better trying to fight Windows?
ProfM2 said:
After getting my 3740 back to "Unbricked" mode, and OTA upgraded to 4.4.4, it appears that I'm completely locked out of the rooting process.
I've tried to start over with the Dell info (unlocking bootloader), however, neither of my PC's will detect the tablet when using xFSTK (one PC - Win8.1-64bit, other XP-32bit). The tablet IS detected, however, it appears that the drivers are no longer correct(?).
I normally run Ubuntu, and thats where my Android development setup is on ... I see that xFSTK is available for Linux ... has anyone used it? or would I be better trying to fight Windows?
Click to expand...
Click to collapse
It is mentioned somewhere that the 3740 and the 3840 use the same firmware. Assuming that, what you can do is download the latest SuperUser zip, copy it to the internal or external storage, then use THIS, or THIS to root through CWM.
graphdarnell said:
It is mentioned somewhere that the 3740 and the 3840 use the same firmware.
Click to expand...
Click to collapse
Hmmm ... I took this to mean that I could use the same boot.img as the Venue 8, and tried the process from this thread: http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
NOPE. (Don't try, it'll cause the tablet to go into the "help my androids' fallen and can't get up" icon. )
ProfM2 said:
Hmmm ... I took this to mean that I could use the same boot.img as the Venue 8, and tried the process from this thread: http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
NOPE. (Don't try, it'll cause the tablet to go into the "help my androids' fallen and can't get up" icon. )
Click to expand...
Click to collapse
I'm curious as to what it is you're trying to do. Why do you insist on having a developer's root (just the use of ADB shell), as opposed to full root flashing SuperSu from custom recovery?
graphdarnell said:
I'm curious as to what it is you're trying to do. Why do you insist on having a developer's root (just the use of ADB shell), as opposed to full root flashing SuperSu from custom recovery?
Click to expand...
Click to collapse
I just want full root.
Most of the info that I've read on here and elsewhere are geared to the 3830/3840. Not as much for the 3740. So, by playing with the device and learning what works/doesn't work, possibly others may find this info useful to them.
I've been having issues seeing the device from XP, Win8.1 and Ubuntu, in the 'off' state of the tablet, when the PC should be seeing the merrifield. Just this morning, after bricking it last night, I discovered that my PC seems to see the device right away if I press Vol+ while plugging in the microUSB. (again, something that may help someone else) I was planning on double checking this info later today, to make sure that it wasn't a fluke.
I do appreciate both of the links that you've posted in this thread, and I will check them out. Of course, both are labelled for the Venue 8, not the Venue 7 that I have. Since I've gained knowledge on the unbrick process I feel more comfortable trying them.
I've installed (or tried to install) SuperSU from the Play store, but it didn't appear to help much, since I didn't have the custom recovery setup at that time. I'll work on that tonight.
ProfM2 said:
I just want full root.
Most of the info that I've read on here and elsewhere are geared to the 3830/3840. Not as much for the 3740. So, by playing with the device and learning what works/doesn't work, possibly others may find this info useful to them.
I've been having issues seeing the device from XP, Win8.1 and Ubuntu, in the 'off' state of the tablet, when the PC should be seeing the merrifield. Just this morning, after bricking it last night, I discovered that my PC seems to see the device right away if I press Vol+ while plugging in the microUSB. (again, something that may help someone else) I was planning on double checking this info later today, to make sure that it wasn't a fluke.
I do appreciate both of the links that you've posted in this thread, and I will check them out. Of course, both are labelled for the Venue 8, not the Venue 7 that I have. Since I've gained knowledge on the unbrick process I feel more comfortable trying them.
I've installed (or tried to install) SuperSU from the Play store, but it didn't appear to help much, since I didn't have the custom recovery setup at that time. I'll work on that tonight.
Click to expand...
Click to collapse
A quick word on getting the device recognized in off mode, what worked for me was it needs to be completely powered off and nothing showing on the tablet screen then connect and bring up the device manager. Whatever shows up needs to be "Intel SoC" so change the driver to that if needed. When flashing firmware to unlock the bootloader the device's boot screen will show an "Intel Inside" logo instead of the normal "Dell" logo. I ended up running xFSTK commands in advance (they'll wait) and then running over to hook up the tablet (powered off) via USB as for some reason it'll show up and then I hear "da-Dunk" in Windows (device disconnected) after a short while which interrupts the process (same with fastboot commands). This was the unbrick process in a nutshell for me and I'm leaving it now as is (OTA'd to 4.4.4) until hopefully the supposed update to Lollipop comes around and maybe some progress is made on rooting it.
Hope this helps you!
reaper-death said:
A quick word on getting the device recognized in off mode, what worked for me was it needs to be completely powered off and nothing showing on the tablet screen then connect and bring up the device manager. Whatever shows up needs to be "Intel SoC" so change the driver to that if needed. When flashing firmware to unlock the bootloader the device's boot screen will show an "Intel Inside" logo instead of the normal "Dell" logo. I ended up running xFSTK commands in advance (they'll wait) and then running over to hook up the tablet (powered off) via USB as for some reason it'll show up and then I hear "da-Dunk" in Windows (device disconnected) after a short while which interrupts the process (same with fastboot commands). This was the unbrick process in a nutshell for me and I'm leaving it now as is (OTA'd to 4.4.4) until hopefully the supposed update to Lollipop comes around and maybe some progress is made on rooting it.
Hope this helps you!
Click to expand...
Click to collapse
I have finally settled down and got the tablet rooted. What's really odd, was Win8.1 kept losing the proper driver. I'm not sure exactly why ... but suffice it to say, I got it working. It did appear to be more stable when I hit the Vol+ and plugged in the USB, but then again it may have been a coincidence.
Open source dell
If you follow the link to dell open source, they do have a detailed PDF download for unlocking the boot loader etc. The file was too large for me to upload on XDA. I just found it today while I was researching how to root this tablet. I have not had a chance to try it yet.
http://opensource.dell.com/
That doesnt work for 3740 lte. I;ve done everything that was in PDF. OTA image should be with unlocker bootloader and root but its not. ;/
Its adb root not su big difference
Does anyone have any idea to root dell venue 7 3740 lte
The open source is for venue 7 3740 wifi
how can i hard reset this device please tell me.
Mahisasur said:
how can i hard reset this device please tell me.
Click to expand...
Click to collapse
Reset any android tbalet with ...
Setting >>>>> Backup & Reset >>>>> Factory Data Reset >>>>> Reset Tablet >>> Erase Everything
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?
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.