Hi folks,
I am a total newbie to sorting out tablet problems.
My MEMoPad 8 "bricked" a while back and, try as I might, I cannot get it to recover. I had not "rooted" it and now, it is stuck on either the normal boot screen or I can get into the Droidboot screen - but I cannot enter commands such as
fastboot flash system system.img or
fastboot flash boot boot.img.
What should I do? I have followed, as far as I can, the directions on "post58341834".
I don't have a PC running Windows - my options are either a PC running Linux Mint 18.3 or a MacBook Pro running MacOS 10.13 (High Sierra). I can get into a "terminal" but that is where I come to a horribly grinding HALT!!
Can someone take me through what needs to be done, in a "step-by-step" fashion, please? (Be gentle, though...!)
Related
I have a Malata T2 with 3g and have been happily trying many of the excellent roms in development from here with no problemes. I thought i'd therefore try the new 1.2 Build T2 3g rom from the download section of the malata.com web-site but messed up and downloaded the T8 3g rom by mistake but didn't spot this until after I had run the NV Flash.
The T8 rom loaded so far but then bricks at the honeycomb screensaver (and the left half of the screen is poor resolution and the right side is a solid white block).
I have obviously tried re-connecting to my laptop so I can re-flash the Flashback rom I had been running but the tablet no longer goes into the recovery mode when starting up whilst holding down the + button; and no longer cannoect to the laptop properly if starting up whilst holding the '-' button.
If connecting to my laptop as I would to flash a rom, my windows 7 laptop makes the normal usb connection sound and recognises the tablet as the Nvida Harmony in my connected devices. However, the laptop now shows a problem with the tablet and when i check the properties it states that the 'WPD FileSystem Volume Driver' has an error code 10 and that the device cannot start. This is preventing me re-flashing an alternative ROM via NV FLASH and when i try to, the nv flash programme says that there is no tablet connected to the laptop.
Obviously, the biggest problem with the tablet is the nube idiot who mucked around and got out of his depth(... me!) but is there anyone on this forum who can help me out and tell me how to get the tablet back to the point where I can communicate with it from my laptop and nvflash a T2 rom again!
Any help would be greatfully appreciated.
Turbo_kf
Try doing the nvflash on Linux. Follow instructions in this post and run a live CD.
1. You will have to use a Linux version of the nvflash utility that you use on the T2. And, before you ask: I don't know if the Linux nvflash program for the gTab will work on the T2. It may; it may not.
2. After you've booted into the Linux desktop, download all the files needed somewhere. I recommend putting it all--both the extracted .img files and the nvflash program--into some directory in /tmp, say /tmp/nvflash-t2. Boot the T2 into APX mode, run the Terminal Emulator, then type:
Code:
$ [B]cd /tmp/[I]nvflash-t2[/I][/B] [I]Change to dir containing all files[/I]
$ [B]sudo ./nvflash [I]... [/I][/B][I]Run nvflash with superuser permissions[/I]
anyone else have a solution that doesn't involve running linux cd's
okay with windows, but not with linux
still stuck
I have taken the advice, run the linux cd and still cant rescue it. From shell, i can see it is there at ./dev/sdb and it sees the tablet when i type lsusb. But when i try and run the correct malata linux nvflash or other g-tab linux nvflashes, it starts up but then tells me that it is an 'unknown device' before terminating the nvflash.
Any suggestions... going of on holiday next week and woukd love to have it recovered by then
Turbo_kf said:
But when i try and run the correct malata linux nvflash or other g-tab linux nvflashes, it starts up but then tells me that it is an 'unknown device' before terminating the nvflash.
Click to expand...
Click to collapse
1. Most likely, you did not put the T2 into what's called APX mode--this is a common mistake. Please, read my original post more carefully.
Also see this post for more info (it's for the gTab, but, it may also apply to the T2).
2. Did you use the nvflash for the T2 (if one exists)? What were the exact commands you used?
still stuck... cant get apx mode
I can assure you that i have been trying to get APX mode from the moment it went wrong ...the inability to get APX mode no matter what i try is where the problem is.
i have run the adb.zip i read about on this forum and run dmesg on both the shell (dmesgshell.txt) and normal (dmesgnvid.txt) and have attached the two outputs.
There is clearly some software problem with having run the T8 rom that is preventing the T2 tablet form going into APX mode and a noobie like me just doesn't have the knowledge to work out what i do now...
any help in how to restore the APX mode so i can flash back the malata T2 stock base1.2 rom would be appreciated.
Thanks
Hello,
I've got Chuwi v99i (a nice intel baytrail based tablet with "retina" display). It was running fine until I wanted to root it and modified the ramdisk of boot.img to get rid of "ro.secure" etc.
Although I was sure the new boot.img was compressed and assembled correctly (I double checked all the figures in the bootloader header with a hex editor etc etc.), flashing the modified boot.img bricked the tablet.
I cannot even go into the full fastboot. When I power on the tablet normally it gets stuck on boot logo. When I power on the tablet with volume button pressed, it is still stuck on boot logo, but at least gets listed with "fastboot devices". Anyway, the only fastboot command it reacts on is "fastboot continue" (it reboots then). All others (flash, getvar etc.) end up in "remote failure".
Do you have any idea if it could be fixed? I heard about xfstk downloader tool for intel-based tablets, but one needs special dnx files, which I do not have. I don't even know if it would do the trick.
If there is nothing I can do by myself, being equipped only with a PC and an USB connection, does anybody know anybody who could fix the issue for me???
I would appreciate any hints :crying:
Cheers,
Maciej
Hi, Same problem, Have you find a solution?
I have same problem, did anybody find solution
I wanted to reflash Android after unsuccessful Xposed install and accidentally used the wrong file in the Manufacturing Flash Tool.
I now have no Android, no Windows -- just BIOS and fastboot are functional. When it boots normally all I see is a UEFI shell with the list of partitions.
I've tried using MFT with the correct file and it didn't help.
I think I need to set up proper (dual-boot) partitions thru fastboot and only then try flashing Android again. Can anyone please help?
Android flashed just fine once I switched from a Windows XP running in a VM to a laptop running Windows 7 64bit.
I'm having problems rolling over the Windows image, I'm guessing it's because I've messed up the partition table -- it can't find the drive with the images now. Anyone had that?
Hi All - I was trying to install a new image on my zenpad and ended up bricking my tablet. I think I ended up formatting everything outside of droidboot.
It only goes straight to the droidboot provision OS now.
i.imgur.com/tnzb5YT.jpg
I've tried the following:
1) Fastboot - It connects, but i don't have privilege to boot from an image. I can only do readonly type of tasks
2) ADB - my computer doesn't detect the tablet when using ADB shell, i think because it would only work if usb debugging is on... which i can't even get to anyway
3) ASUS FLash tool - there's no raw image available for this tablet
It seems like my only hope is the SD Download... but i think I need an image for that too? Any ideas and guidance please?
http://forum.xda-developers.com/u/repair/hard-brick-asus-zenpad-s8-z580ca-z580c-t3465203
Hi all,
Well, operator error is definitely at fault here... I made a series of mistakes that got me to where I am now. All I intended on doing was repairing my dad's tablet which was running atrociously slowly. I tried to follow some steps, but improvised as I was getting errors and obviously ended up making things a lot worse...
Now tuning on the tablet will directly go to a command line interface with a long series of errors and these are the last 2 lines:
Rich (BB code):
blkD :HardDisk - Alias (null)
PciRoot (0x0) /Pci (0x17,0x0) Ctrl (0x0) /HD(14,GPT,80868086-8086-8086-8086-000000000008,0x646828,0x16D47D8)
blkE :BlockDevice - Alias (null)
PciRoot (0x0) /Pci (0x17,0x0) Ctrl (0x0)
Press ESC in 1 seconds to skip startup.nsh, any other key to continue.
Shell> _
In this state it cannot be interacted with and won't be detected by my PC over USB.
This happens for normal, recovery and bootloader modes. The only mode that I can access is DNX mode but attempting to boot droidboot will result in the same command line UI described above, including when trying to restore the BIOS using the PC executable (which I assume needs to enter fastboot mode, which it can't do...).
What can I do now? Any way to get anything working in the above screen or through DNX?
I'm thinking that a partition was corrupt in addition to me wiping the ESP is causing this. Maybe it's possible to completely format and setup all the partitions and start from scratch again? How can I flash esp.img when all I have access to on the tablet is DNX mode?
Detailed history below...:
HISTORY
1)
The tablet is a Lenovo Yoga Tab 2 1050F. It was running very slowly to the point where my dad just didn't bother to use it. I thought it would be wise to factory reset it as a first step. There is no option to do so within the Lenovo skin of Android so I started by going into recovery mode and performed a factory reset from there.
After it rebooted, the Android UI would loop back to the language selection after connecting to a WiFi network and I would get "Unfortunately Google Play Services has stopped." error message. It would just loop through the Language Selection > Connect to WiFi network pages over and over.
2)
Having installed CM on my old S3 back in the day, I thought I could go about the same process and flash a gapps ZIP file in recovery mode. That didn't work, I got an error because the zip was unsigned.
I thought I could install TWRP to flash unsigned zips, reinstall Gapps and get the tablet passed the Android UI loop.
3)
I followed this guide on XDA to install an unofficial TWRP (which involved unlocking the bootloader). It didn't work because I couldn't flash over ADB (because the tablet couldn't allow Developer Mode since it was stuck in the Android UI loop). So I flashed as many files as I could in fastboot.
I eventually flashed the TWRP recovery.img but that didn't work : when turning on to Recovery mode it would just go back to the bootloader screen.
4)
I thought I must have screwed up something up so I tried to restore the BIOS using an executable I found but I realized the tablet was already upgraded to Lollipop and the only BIOS restoration exe was for Kitkat. Sure enough it got even worse and I could no longer boot Android.
5)
I still had bootloader and fastboot though so I followed a guide to restore the tablet to the original OS (which ironically I already downloaded before trying to get TWRP but forgot about and didn't unpack). I set up Intel Platform Tools but the flash process didn't work because it went to droidboot and then lost USB connection. On the Intel program it would just stay stuck at 20% Wiping ESP. It would time out twice and then give me a final error message.
6)
So I thought to explore the flash.xml file provided to see if I could do the steps manually. I knew it was stuck at wipe ESP because in droidboot it couldn't get commands from PC. So I went into fastboot and wiped ESP manually myself! Little did I know how foolish this was to do because I was simply unable to flash the provided ESP.img again. Following this I lost access to the bootloader.
7)
I found a guide to restore a bricked 1050F here on XDA but it needs droidboot which now goes to the command line UI described at the top of this post. When attempting to restore the kitkat BIOS again, droidboot is also needed which results in the same cmd UI.
8)
Which leads me to where I am now which is that the tablet doesn't boot to: normal, recovery, bootloader/fastboot or droidboot. Which is why I am now asking for help. What can I do?
I'm thinking that a partition was corrupt in addition to me wiping the ESP is causing this. Maybe it's possible to completely format and setup all the partitions and start from scratch again? How can I flash esp when all I can get access to is DNX mode?
Thanks for reading this far and if you have any more ideas, please let me know, thanks in advance.
Hi, would anyone like to weigh in on this issue?