Related
So it had been quite some time since I tried messing with my tf300 so....
I was on cm-9, when to update to cm-10.1, tried to update twrp then it wouldn't boot to recovery, tried to flash back to stock JB bootloader using "fastboot flash system.blob" gave me a flash error (invalid size) and for some reason fastboot doesnt recognize my device.
So I have no recovery and no rom.
I tried "fastboot boot boot.blob" from cm-9 and cm-10 and it wont boot. just stuck on "waiting for device"
When I type "fastboot devices" it just starts a new command line, no serial number.
I can include any information needed to help my situation, I just need to be told where to look.
To be honest, I couldn't remember what bootloader I was on. It had been a while. Is there a way to tell?
Can't get the tablet to stay off either while I wait for help. Lol
Sent from my LG-LS970 using xda premium
Any ideas?
Sent from my LG-LS970 using xda premium
Now I think my situation might have gotten worse.
I can't get into fastboot now. It just keeps trying to go into recovery mode but there is no recovery so it just continuously reboots.
No one can help?
Sent from my LG-LS970 using xda premium
Well that sucks...
Sent from my LG-LS970 using xda premium
Depends on what you were trying to do, were you trying to update the recovery first and to what version. I believe cm 9 is based on an older build of bootloader. What exactly did you do. From my knowladge as to reading and seeing so many people just flashing before reading the threads you should first update the bootloader then the recovery depending on what recovery version you were trying to update to. From what it sound like you tried to update the recovery before bootloader just not sure what version of recovery but if wrong one and didnt update bootloader sounds like you maybe un recoverably bricked like what everyone else is doing before reading and as of now. Aslo if you have an nvflash backup there may be a fix i'm just not sure how as i never had it but accorging to some it seems that was the only hope for them to get out. Reaad the threads there maybe help on here some where just so many are flashing and bricking before reading people are getting frustrated because theres no help for it.
I know it doesn't help, but since you wanted to know what happened, I can tell you that much. Since you were on CM9, you had to be on the original ICS bootloader. Stock JB can't be fastboot-flashed over ICS because of changes to the partitioning and other low-level stuff, which is why it wouldn't flash and why it subsequently failed to boot.
I'm also just picking up my TF300 for the first time since August. I just recovered from a soft-brick today (my story, which in hindsight was a complete f-up on my part), which was why I hadn't been using it. I ended up fastboot-flashing the newest ICS firmware (I actually tried it back in August, but fastboot wouldn't work; I didn't do anything differently today, but fastboot had been updated recently and magically worked), then performing the NVFlash backups from the sticky thread (this isn't quite where our paths diverged, but it may have been a good idea to do that before you tried upgrading to JB -- not that it helps now, but for future reference).
Like you, I tried fastboot-flashing the stock JB firmware over the ICS firmware and got the same error you got. So, I tried flashing the ICS firmware again, but got the same Invalid Size error. At this point, my tablet wouldn't boot past the splash screen (not the animation with the spinner; the first one with the NVidea logo in the corner), and fastboot wouldn't flash any firmware.
This next part is the part where our stories more-or-less fork.
Faced with another soft brick just hours after fixing one, I fastboot-flashed TWRP instead (made sure to use an ICS version since the JB firmware didn't flash, and the NVFlash bootloader I had was based on the ICS bootloader), which worked, and I booted into recovery. I used TWRP to flash the ICS firmware (I actually had it on my internal SD card in August, but I could have also pushed it with ADB if I didn't already have it), and I got a functioning tablet again.
Next, to upgrade to Jellybean correctly, I booted into Android and used ADB to push the Jellybean firmware to my tablet. I put it on the root of the internal storage, and the tablet saw it and alerted me to the update. Since TWRP had been replaced by the stock recovery when I flashed the ICS firmware, I just let the tablet do its thing with the update, and I ended up with a perfectly-functioning stock Jellybean ROM. I then performed each subsequent update (I never once skipped any update steps) the same way until I was on the newest 4.1.1 firmware (I'm not updating to 4.2.1 until CM10.1 works with it).
I'm not sure how much research you did before you updated your tablet, but I was trolling the TF300 forums for a good 2 or 3 hours before I even tried upgrading, and I still had trouble (I never saw any posts about people trying to fastboot-flash JB over ICS, so I didn't know it wouldn't work until I tried it at least 3 times). From the limited details you provided, it doesn't sound like you did much searching before you started flashing. In the future, it may be a good idea to research a lot more than you think you have to before flashing things on expensive devices.
Also, in the future, when you're asking for help like this, it's best to go overboard on the details - just like a murder investigation, we want to help you figure out what killed your tablet, but we can't do that if you don't tell us about the strange footprints you saw in your neighbor's lawn the night before. Mention every single icon or word that appears on the tablet, every single button-press you've made, every keystroke you've typed, etc., whether it seems important or not. We can't be there with you, so you have to bring your situation to us.
At this point, the only advice I can give is to let the tablet die, charge it again (so the battery's full but the tablet's powered off), and try again when the battery's full. If you can get ADB to work while the tablet is trying to boot recovery, you may be able to flash a new recovery and then try flashing the ICS firmware (flashing the JB firmware might work, but then you can't use NVFlash). That's about the best you can do if you can't get it into fastboot mode (short of RMAing your tablet). If you can get fastboot to work somehow, then you can easily flash a new recovery and follow the steps I took. But if you do get your tablet booting with the ICS firmware, perform the NVFlash backups ASAP before you update to Jellybean.
I hope you can get your tablet to work. I thought mine was a goner until I got lucky with an updated fastboot. Now, I'm ecstatic that it works, and I'm going to be a lot more careful in the future.
Hi,
I've come here as last resort, been trying to upgrade to Androwook 2.2 but always getting stuck in bootloop on Asus load screen. I'll try and be as detailed as possible concerning what I've already tried, but please bear with me as I'm quite a beginner with Android;
I'm currently running Androwook 2.11 on my TF700, but I'm getting some small issues such as frequent Google Play crashes and random restarts, it's livable but I wanted to upgrade to 2.2, which seems to have quite a lot of fixes compared to 2.11.
My Infinity is unlocked and rooted, I've done a complete nandroid backup using TWRP 2.6. which I pushed using ADB/Fastboot method, but there is something I don't quite understand; when I boot into bootloader using volume down and power buttons, I only see 3 icons, the USB icon is missing from the lot. Message on the top left says "Key driver not found... Booting OS, Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14.4-20130329" A03, Satrting Fastboot USB download protocol". Funny thing is that running the "adb devices" command from my Windows 7 Ultimate PC results in a blank "List of devices attached" message, but when running the "fastboot -i 0x0B05 flash recovery twrp.blob" it actually flashes the device correctly. Furthermore, when running "adb devices" while booted into the OS, the device is recognized but indicated as offline. Is the fact that I'm not seeing the USB icon in bootloader a problem or is it ok as fastboot still seems to work?
Anyway I download and copy the "13683789011409181222_Hairybean 2.2".zip file to my external SD card, follow the full instructions as indicated on the official Androwook XDA thread, installation is successfull but on reboot I always go into the Asus logo bootloop. I've left this running for about 30 minutes with no success, the Rom just doesn't boot up.
So I started searching the forums for solutions and tried what I could find; found some guys saying that checking the "Install custom boot animation" box during the Androwook setup before the installation seemed to have gotten them out of bootloop, but didn't work for me. I've of course tried to redownload the Hairybean 2.2 zip file thinking that it might have gotten corrupted but 3 different download locations and still no success.
I'm thinking that pushing Androwook 2.2 via ADB/Fastboot might help, but I'm not quite sure of exactly how to do that, anyone think it's worth a try?
I can't list exactly everything I've tried to get this working as I've been trying for about a month now, but believe me, I've spent a lot of time searching and trying, to no avail. So I would really appreciate it if someone could take the time to accompany me to Androwook 2.2, back to 2.11 and really getting frustrated now
Thanks in advance!
Foolmax said:
Hi,
I've come here as last resort, been trying to upgrade to Androwook 2.2 but always getting stuck in bootloop on Asus load screen. I'll try and be as detailed as possible concerning what I've already tried, but please bear with me as I'm quite a beginner with Android;
I'm currently running Androwook 2.11 on my TF700, but I'm getting some small issues such as frequent Google Play crashes and random restarts, it's livable but I wanted to upgrade to 2.2, which seems to have quite a lot of fixes compared to 2.11.
My Infinity is unlocked and rooted, I've done a complete nandroid backup using TWRP 2.6. which I pushed using ADB/Fastboot method, but there is something I don't quite understand; when I boot into bootloader using volume down and power buttons, I only see 3 icons, the USB icon is missing from the lot. Message on the top left says "Key driver not found... Booting OS, Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14.4-20130329" A03, Satrting Fastboot USB download protocol". Funny thing is that running the "adb devices" command from my Windows 7 Ultimate PC results in a blank "List of devices attached" message, but when running the "fastboot -i 0x0B05 flash recovery twrp.blob" it actually flashes the device correctly. Furthermore, when running "adb devices" while booted into the OS, the device is recognized but indicated as offline. Is the fact that I'm not seeing the USB icon in bootloader a problem or is it ok as fastboot still seems to work?
Anyway I download and copy the "13683789011409181222_Hairybean 2.2".zip file to my external SD card, follow the full instructions as indicated on the official Androwook XDA thread, installation is successfull but on reboot I always go into the Asus logo bootloop. I've left this running for about 30 minutes with no success, the Rom just doesn't boot up.
So I started searching the forums for solutions and tried what I could find; found some guys saying that checking the "Install custom boot animation" box during the Androwook setup before the installation seemed to have gotten them out of bootloop, but didn't work for me. I've of course tried to redownload the Hairybean 2.2 zip file thinking that it might have gotten corrupted but 3 different download locations and still no success.
I'm thinking that pushing Androwook 2.2 via ADB/Fastboot might help, but I'm not quite sure of exactly how to do that, anyone think it's worth a try?
I can't list exactly everything I've tried to get this working as I've been trying for about a month now, but believe me, I've spent a lot of time searching and trying, to no avail. So I would really appreciate it if someone could take the time to accompany me to Androwook 2.2, back to 2.11 and really getting frustrated now
Thanks in advance!
Click to expand...
Click to collapse
I can only shed a tiny little light on your problem since I am not familiar with Androwook.
JB 4.2 defaults to fastboot mode if and when you boot into the bootloader. So in 4.2 you only have the icons for recovery, Android and Wipe Data.
To use ADB you have to be booted into the rom. Actually, I have read with the correct drivers yo can also use ADB in recovery, but I have never tried that myself.
Just ignore the 'key driver not found'. Every TF700 displays that message when you boot into the BL.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
AndroWook 2.2 works fine on my TF700 and technically it should on yours. It shares the same base as CROMi-X 4.x. Have you tried CROMi-X to see if it boots?
I think flumpster recommended you do a clean install for AndroWook 2.2 as well have you tried that? Also which bootloader are you on? I'm reluctant to recommend TWRP 2.6 just yet as users have reported some problems with it, so I'd also recommend you drop back down to TWRP 2.5.
Thanks for your replies, I was beginning to despair when I saw that my post had 35 views and no replies
@berndblb: Thanks for that confirmation, at least I can stop searching in that direction, it's just that most tutorials, even recent ones, indicate the USB icon, I guess there musn't be many of us on TF700 running JB roms.
@sbdags: nope, haven't tried CROMi-X yet, will do when I get home after work tonight if you think it's worth it, thanks for the tip. Concerning the clean install I've already tried if you mean completely wiping Internal memory via TWRP. I just haven't wiped the SD card as it was containing the rom.
Concerning the bootloader I thought I had given the version in my first post (Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14.4-20130329" A03), isn't that it? I know the bootloader could be an issue as originally I installed it with a pack destined to the TF300, that might be something I could try, but which bootloader shoul I install and what is the best method for installing it? If that isn't my bootloader version where can I find it?
I know what you mean with TWRP 2.6, I'm ususally also very carefull with new versions, but have same issue on TWRP 2.5 and 2.4.4 (in fact most of my failed attempts were done on 2.4.4), haven't tried lower yet.
Foolmax said:
Thanks for your replies, I was beginning to despair when I saw that my post had 35 views and no replies
@berndblb: Thanks for that confirmation, at least I can stop searching in that direction, it's just that most tutorials, even recent ones, indicate the USB icon, I guess there musn't be many of us on TF700 running JB roms.
@sbdags: nope, haven't tried CROMi-X yet, will do when I get home after work tonight if you think it's worth it, thanks for the tip. Concerning the clean install I've already tried if you mean completely wiping Internal memory via TWRP. I just haven't wiped the SD card as it was containing the rom.
Concerning the bootloader I thought I had given the version in my first post (Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14.4-20130329" A03), isn't that it? I know the bootloader could be an issue as originally I installed it with a pack destined to the TF300, that might be something I could try, but which bootloader shoul I install and what is the best method for installing it? If that isn't my bootloader version where can I find it?
I know what you mean with TWRP 2.6, I'm ususally also very carefull with new versions, but have same issue on TWRP 2.5 and 2.4.4 (in fact most of my failed attempts were done on 2.4.4), haven't tried lower yet.
Click to expand...
Click to collapse
Do me a favour go to my CROMi-X thresd (linked in my sig) for the TF700 and download and install the bootloader and recovery package for your SKU. This will give you a working bootloader on 10.6.1.14.8 and TWRP 2.5
Then we can take it from there.
sbdags said:
Do me a favour go to my CROMi-X thresd (linked in my sig) for the TF700 and download and install the bootloader and recovery package for your SKU. This will give you a working bootloader on 10.6.1.14.8 and TWRP 2.5
Then we can take it from there.
Click to expand...
Click to collapse
It'll be done tonight as soon as I get home, thanks for your time, I'll keep you posted ASAP.
Well, your advice worked; thanks a lot! Only thing is that Androwook still won't install but your Rom does, I'm busy testing it at the moment to see if it suits me, might stay on it, so far so good (well done for that work!)
Downloaded the 10.6.1.14.8 WW Bootloader and TWRP 2.5.0.0, dropped it on my SD card and flashed it via Recovery. I immediately tried to flash Androwook again after the successfull installation of the bootloader and recovery, but same thing happened; bootloop on ASUS screen. One of the things I haven't tried yet is to Wipe Cache/Delvik after the Rom installation, before the reboot to the actual Rom, could that make a difference?
Noticed two things when installing the above package via TWRP though; you say the install should last about a minute, on my device in 20 seconds it was done, blue bar just progressed in two phases; once until halfway and full almost 10 seconds later. In TWRP, after each message during the installation process I'm getting a "Done" line, but on the last command, which is "updating partition details", I'm not getting the "Done" confirmation, it just stays on that last line. Same when I click the top right icon (right of "back" and "home" buttons buttons on TWRP Home screen); it starts updating partitions but freezes right there, have to restart tablet with power button to get back in Recovery. Could there be something screwed up in my partitions?
Foolmax said:
Well, your advice worked; thanks a lot! Only thing is that Androwook still won't install but your Rom does, I'm busy testing it at the moment to see if it suits me, might stay on it, so far so good (well done for that work!)
Downloaded the 10.6.1.14.8 WW Bootloader and TWRP 2.5.0.0, dropped it on my SD card and flashed it via Recovery. I immediately tried to flash Androwook again after the successfull installation of the bootloader and recovery, but same thing happened; bootloop on ASUS screen. One of the things I haven't tried yet is to Wipe Cache/Delvik after the Rom installation, before the reboot to the actual Rom, could that make a difference?
Noticed two things when installing the above package via TWRP though; you say the install should last about a minute, on my device in 20 seconds it was done, blue bar just progressed in two phases; once until halfway and full almost 10 seconds later. In TWRP, after each message during the installation process I'm getting a "Done" line, but on the last command, which is "updating partition details", I'm not getting the "Done" confirmation, it just stays on that last line. Same when I click the top right icon (right of "back" and "home" buttons buttons on TWRP Home screen); it starts updating partitions but freezes right there, have to restart tablet with power button to get back in Recovery. Could there be something screwed up in my partitions?
Click to expand...
Click to collapse
Sorry should have said don't flash the bootloader package and rom at the same time.
Not sure what is going on with the freezing. It doesn't sound quite right. Sorry I don't know the fix.
sbdags said:
Sorry should have said don't flash the bootloader package and rom at the same time.
Not sure what is going on with the freezing. It doesn't sound quite right. Sorry I don't know the fix.
Click to expand...
Click to collapse
Absolutely no need to apologize, you helped me out man, thanks^^
When I said immediately I meant after a reboot, might not be an android expert but I know that rebooting after each process is strongly advised
Anyway, point is; TWRP 2.5 and bootloader are correctly installed (I can do without the partition thingys I guess), and your Rom seems fine and stable, so I'm all fixed basically, I'll just try to avoid flashing new Roms on this tablet, might be a hardware issue.
Another nub question to finish; what is the officail way of marking this thread a solved?
Edit: Just donated a couple of bucks to your account, Rom really seems stable, haven't had a single issue yet, thanks again!
Foolmax said:
Absolutely no need to apologize, you helped me out man, thanks^^
When I said immediately I meant after a reboot, might not be an android expert but I know that rebooting after each process is strongly advised
Anyway, point is; TWRP 2.5 and bootloader are correctly installed (I can do without the partition thingys I guess), and your Rom seems fine and stable, so I'm all fixed basically, I'll just try to avoid flashing new Roms on this tablet, might be a hardware issue.
Another nub question to finish; what is the officail way of marking this thread a solved?
Edit: Just donated a couple of bucks to your account, Rom really seems stable, haven't had a single issue yet, thanks again!
Click to expand...
Click to collapse
Cheers mate for the donation! Glad you got it all sorted!
Darren
My friend gave me his bricked Xoom, which I accepted as a challenge, because I've been rooting and flashing my phones for years, but after 10+ hours of searching in the last couple weeks, I have been unable to locate coherent information on how to un-brick a Xoom that has had its internal storage wiped. My friend was trying to do a thorough wipe, and he succeeded in that, if nothing else.
My first obstacle was finding a driver, because Motorola Device Manager wants nothing to do with the Xoom, and whenever I finally found a link to a driver, it was at developer.motorola.com, and there apparently is no such domain, because every link takes me straight to motorola.com/us/home, where all that's waiting for me is the bloody Moto Device Manager.
The only post I found that seemed like it was aiming at where I want to get is at http://forum.xda-developers.com/showthread.php?t=2317986, but I ran into problems that weren't foreseen by the author, and I haven't been able to find anything pertinent that doesn't direct me to developer.motorola.com again.
The Xoom has TWRP v.2.6.3.0(runandhide05 edition) for a recovery; and I'm aware that there is a 3.3 version, but I'm nervous about flashing a recovery update when there is no OS on the tablet. It was running EOS 4.2.2 I think, before the bricking.
According to the guide I found, I put TWRP into adb sideload and was able to get my PC to communicate by installing a universal adb driver from https://github.com/koush/UniversalAdbDriver, so in my system Device Manager, the Xoom is listed as a GOOGLE GALAXY NEXUS ADB INTERFACE.
When TWRP is in adb sideload, I can interface with the Xoom via cmd.exe, but when I try to push a ROM, I keep getting an error on TWRP:
Code:
file_getprop:failed to stat "/system/build.prop" no such file or directory
...whatever that means. Another thing that kind of worries me is that when I type adb devices, it shows my device as 1234567890ABCDEF, which doesn't seem right.
I have yet to try fastboot, because I don't know what .img files I need to flash, and I don't think blind flashing is going to make things any better.
I think I have all the pieces, SDK and JDK are installed and updated, and I have the stock rom (HWI69.zip). I reckon if I can get the stock 3.x OS running, I'll have a jumping-off point, and be good to go; the process from there is well-documented.
Can anyone give me a nudge in the right direction, please?
~Fake
Status 7 errors
Those are usually caused by either a not-so-compatible recovery image. Some TWRP versions have issues with certain ROMs. I had this happen to me with my Asus TF300, ended up trying a few different TWRP versions before I found one that worked right.
The other cause is an invalid ROM image, if you open the ROM.zip file on your PC, does it look ok, did you check its MD5sum???
Were you able to wipe the Xoom from TWRP without error???
-Mike
When I got it, it had been wiped completely, so I presume that twrp wiped okay.
Not sure about the MD5sum, just that twrp didn't find one during the adb installation. Do you think flashing cwm might help?.
I got it worked out, opened up the HWI69.zip stock image and fastboot flashed the individual .img files, and it booted right up. Thanks!
Hello, my name is Shagington
I have been slowly unlocking the potential of my tf700t, yet I have come to a point where I am stuck loading the android OS. The problem started when I installed xposed to gain the ability to modify the permission of apps. Now it just sits with the loading circle spinning around and 'round. I tried wiping from the bootloader yet the same thing happens. While looking into the bootloader more, I found twrp installed after what I thought were many failed attempts. I tried a wipe from that as well and the same thing happens. I was thinking about just flashing a stock (rooted) rom with twrp but I am afraid of getting into a worse spot than I already am in, any help is appreciated.
Thanks, Shag
You need to post your bootloader version (read the tiny script when you boot with Power and Volume Down) and your recovery version.
That will determine what you can flash or what type of repair you can try.
Do you have fastboot and adb setup on your PC?
Check if you have a fastboot connection when booted into the bootloader and adb when booted into recovery.
See if you can capture a logcat of the boot process in adb.
Then report back.
Whatever you do, do not use the Wipe Data option from the bootloader!!!!!!!!!
Thank you for the quick reply berndblb, it seems im on build us 10.6.1.14.8-20130514. I just reformatted my pc to windows 10 tech preview so im not quite sure how that will work with adb but I will give it a go tomorrow. Will any custom rom work with the current build i have?
Thanks again, Shagington (Newbington)
shagington said:
Thank you for the quick reply berndblb, it seems im on build us 10.6.1.14.8-20130514. I just reformatted my pc to windows 10 tech preview so im not quite sure how that will work with adb but I will give it a go tomorrow. Will any custom rom work with the current build i have?
Thanks again, Shagington (Newbington)
Click to expand...
Click to collapse
Yes, there are. You are one version behind to the latest (and last) bootloader 10.6.1.14.10. Might be a good idea to update to the latest while you're at it...
Which recovery and version thereof did you flash?
Once we are sure that you have compatible software installed you can flash a bootloader/TWRP package to get you up to date, but let's resolve your current pickle first.
berndblb said:
Yes, there are. You are one version behind to the latest (and last) bootloader 10.6.1.14.10. Might be a good idea to update to the latest while you're at it...
Which recovery and version thereof did you flash?
Once we are sure that you have compatible software installed you can flash a bootloader/TWRP package to get you up to date, but let's resolve your current pickle first.
Click to expand...
Click to collapse
Thanks again for responding good sir, I am on twrp 2.8.5.0, which still loads just fine.
-shagington
When you install xposed it puts an emergency uninstall zip on the internal sdcard partition. Try flashing that from twrp to reverse it out.
Be careful with xposed it can sofbrick easily as you have found out.
shagington said:
I just reformatted my pc to windows 10 tech preview so im not quite sure how that will work with adb
Click to expand...
Click to collapse
I tried the first Win10 preview, and I just had to connect the tablet and run adb.exe - it worked fine with the automatically installed drivers.
Thanks for the replies guys, I couldnt find any zips on my internal, I looked through almost every folder. After looking through the adb tutorials, it is a little to intimidating for me. Kinda sad, I was under the impression that now I have twrp I could just throw some other rom on quickly or even a download a backup from someone else with the same versions to recover and be done with it. I think im just going to leave it soft bricked for a while and use my nexus 7 for now. Appreciate the help guys, it's just a little over my head.
-Shag
Hi guys,
A while ago, I've rooted/unlocked my device in order to install Cyanogenmod, installed PhilZ bootloader. Been running through some versions, never happy with the result - slow response, games not running that well, etc. The last time, I got some new update (can't remember which one though ...) which was the worst nightmare. Without any app running, I thought I was on some Eboda tablet, the cheapest one. Last night I've tried to connect the tablet to my laptop, to put some ebooks on it, without success. Nothing I did convinced the 2 devices to see one another. So, I tried to go back to some previous ROM, boot the device in recovery mode and did a wipe. Forgot that at some point I erased all ROMs from it ... now, I still can't connect to it, so that I can copy some version of ROM, any version, although Windows shows it as installed and connected. Bottom line is that now I got no ROM on the tablet, not installed and also not one that I can install, only got the PhilZ bootloader. Is there any way to get my tablet back or is it bricked ?
You are confusing bootloader and recovery. But as long as you can get to the bootloader *or* to your recovery, it is possible to restore your tablet.
To talk to the bootloader, you need to use fastboot.
To talk to the recovery, you need to use adb.
For more details, read berndblb's comprehensive guide in the General section.
_that said:
You are confusing bootloader and recovery
Click to expand...
Click to collapse
You are right, I have to admit I have not been very thorough the first time I went about this
Thank you very much, I will track down this guide, perhaps I will be able to restore my tablet to some use ...
Hi all,
As it turns out, I had only to push one flashable image (used CM11) and was able to put the tablet back on it's feet. Many thanks to berndblb
Have fun!