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
Related
If you on XDA forums then you are most probably moding your device, which means you will def. brick your device atleast once.
So I suggest that everyone setup nvFlash, instead of stressing for hours after there first brick.
You can find the full guide on how to setup nvFlash at http://forum.xda-developers.com/showthread.php?t=861950
Below I'll summarize the steps from that guide.
1. go to https://www.dropbox.com/s/wrcd87u1iy31u4e and download nvflash_gtablet_2010110500.zip and nvflash_windows_20100500.zip
2. Extract the files the two .zip files that you download and copy all the files in the same folder. (I have 32 files in my nvFlash folder)
3. Download the usb driver for apx mode from http://www.myadventvega.co.uk/
4. Once you have all three of the files above, you boot in apx mode using power & vol - key. Once in apx mode, make sure you install the drivers that you downloaded in step 3. After that you can simply run the nvflash_gtablet.bat to flack back to stock rom.
Having nvFlash will help you get back to the stock rom and start from the very beginning, which is always a very good point to start when you want to install a new rom.
I HIGHLY RECOMMEND THAT YOU FOLLOW THE ABOVE STEPS AND SETUP UP NVFLASH. IF YOU USE THE ABOVE METHOD AND NOTICE THAT YOU GET STUCK IN APX MODE AFTER YOU REBOOT YOUR DEVICE THEN USE THE nvflash_gtablet_46_2010112600.zip INSTEAD OF nvflash_gtablet_2010110500.zip.
also feel free to leave me a pm if you need more help or just post below
hope this helps a lot of new users who get stuck in bootloops or are having problems booting a new rom.
enjoy
I am stuck on the viewsonic boot screen coming from vegan 5.1 to GE rc-1. I need to nvflash but have a 64 bit windows 7 instalation. Are the instructions the same??
I read the original instructions but could not understand what to do? I am still kind of scratching my head. Probably easier than I am making it in my head.
Thanks for making a simple guide and answering our questions!!
Thanks. Guess I will be doing this when I get off work tonight!!
Rob
ya it works for x64...i m on win 7 64 bit and it works fine
Thanks for the info.
My question is -- when you say "download the ... files" - do you mean download to my PC or to my tablet?
That's the only part the is confusing as I'm not sure where the usb driver is to be installed (PC or tablet).
Thanks in advance.
My advice for NVFlash is DO NOT do it unless it is completely needed. From personal experience it can do more harm than good, as it has left me with a bricked device
barnell said:
Thanks for the info.
My question is -- when you say "download the ... files" - do you mean download to my PC or to my tablet?
That's the only part the is confusing as I'm not sure where the usb driver is to be installed (PC or tablet).
Thanks in advance.
Click to expand...
Click to collapse
download it to your pc
Citi said:
My advice for NVFlash is DO NOT do it unless it is completely needed. From personal experience it can do more harm than good, as it has left me with a bricked device
Click to expand...
Click to collapse
I think your issue is something different and does not regard nvFlash. Its most probably have something to do with repartitioning. Did you try to get cwm .8 installed again on your tablet again by the method that I suggested??? or follow any of the steps that either me and K J Rad posted on the thread that you started??
I get an error when trying to install the APX driver. It says:
Cannot Start this Hardware. There was a problem installing this hardware: NVIDIA USB Boot-recovery driver for Mobile devices. This device is not configured correctly. (Code 1)
I followed the instructions step by step. I recorded a quick video I recorded of the install process and error but I am new to XDA so it won't let me post the link. If you search for "Error installing APX," it should be the first one that shows up on the list - user name ouphikap21.
Any ideas?
I just tried on another computer and it worked fine. Could be a firewall or admin issue I suppose?
dw21 said:
I just tried on another computer and it worked fine. Could be a firewall or admin issue I suppose?
Click to expand...
Click to collapse
good stuff man....glad you were able to set up it...its going to be pretty hard for you to brick you tablet now...i have been in very tight situations have always been able to get out of them using nvFlash...sometimes it takes me some time even with nvFlash but it has never failed on me or any of the devs on this site
Yup!
Consider this your morning-after pill! :}
thanks for the info. Just picked up a gtablet today. Didnt even turn it on yet !
What do you do first? nvflash or load CWM 8 from this thread ?
rbansal2 said:
download it to your pc
Click to expand...
Click to collapse
Thanks -- that's what I thought- but I wanted to be sure.
Regards.
I am trying to do the nvflash and I have followed all the instructions perfectly as far as i can tell now when i run the .bat i get the following message.
C:\Users\chris\Desktop\NVFlash>"nvflash.exe" --bct gtablet.bct --setbct --bl boo
tloader.bin --configfile gtablet.cfg --create --go
Nvflash started
USB device not foundPress enter to continue:
and yes i have the usb driver installed and the device is in the apx mode.
Any help would be great
RichardsChris said:
I am trying to do the nvflash and I have followed all the instructions perfectly as far as i can tell now when i run the .bat i get the following message.
C:\Users\chris\Desktop\NVFlash>"nvflash.exe" --bct gtablet.bct --setbct --bl boo
tloader.bin --configfile gtablet.cfg --create --go
Nvflash started
USB device not foundPress enter to continue:
and yes i have the usb driver installed and the device is in the apx mode.
Any help would be great
Click to expand...
Click to collapse
Go in device manager and under usb see if it is connected as a usb boot recovery device(something along those lines). If it is anything else then either you are not in apx mode(have to hold power + vol - key to get in apx on boot) or you dont have the right drivers.
Also what os are u on?
rbansal2 said:
Go in device manager and under usb see if it is connected as a usb boot recovery device(something along those lines). If it is anything else then either you are not in apx mode(have to hold power + vol - key to get in apx on boot) or you dont have the right drivers.
Also what os are u on?
Click to expand...
Click to collapse
I am running windows 7 64 bit, under device manager its showing as nvidia usb boot recovery driver for mobile devices
If the computer is not seeing the tab in apx mode then you have the wrong driver installed
thebadfrog said:
If the computer is not seeing the tab in apx mode then you have the wrong driver installed
Click to expand...
Click to collapse
are there different drivers for Windows Xp x 64?
Now what?
Out of an abundance of caution, I installed NVflash preparatory to changing ROMs. Installation has apparently been successful but I'm not ready to flash the new ROM yet and I'm sitting here with a black (APX?) screen, still tied to my PC via USB.
What's the best procedure to revert to standard ops on my current ROM?
EDIT: I suppose I actually have the DRIVERS installed, not NVFlash.
Hi everyone
I got the AC100 and tried to root it and install the Gapps (i needed Gmail and Calendar).
I messed around with the adb from Google SDK and i erased the files from "system/apps" by accident
so the device now got stuck on the startup screen (the android logo keeps flashing once per second)
I searched the web alot and found instructions on how to enter recovery mode
so know i have the ac100 conected via USB to my XP machine, and i have installed the nVidia USB recovery driver
(it showed up as APX in the Device Manager once i turned on the recovery mode).
I can get to the restore screen (holding HOME while powering up) and i've tried a few "update.zip" files on a SD card, but i get the exclamation mark in the triangle as soon as i hit "1 - update" and then the device resets.
I have NVFlash downloaded and it sees the device (nvflash --sync displays info the way it should)
Can anyone please help with instructions on how to get my notebook working again?
I'll be pleased with the stock Android, i'd be happy with Cyanogen Mod.
Please help.
Thank you.
PS. sorry if it's the wrong thread, but as i've read the Folio and AC100 are pretty similar.
best option is to just push the relevant partition images using nvflash, no need to use recovery. If you have an update.zip, that should have the files you need. Have a look at the wet-paint wiki or ask on #ac100
Thanks for the reply
I do have an update.zip, but i'm not quite sure how to push it with nvflash.
I've search alot around the forums but haven't found anyone with a problem like this or i couldn't really understant the steps (in some cases, one of the steps was "push the file to the device with nvflash" but i'm quite a beginner and i would need more detailed info.
I'll try the IRC # as well but if anyone can post here a method, i'd be really glad.
Thanks
UPDATE:
Ok, with the help of some people over on #ac100, i managed to download part8.img to partition 8 (which was the apps partition) but now the devices freezes on the TOSHIBA logo screen.
Any advice?
Good news
I finally got it to run. I used the backup partition imgs i found (along with the partition table txt) and rewrote all the partitions with NVFLASH using the rawdevicewrite method described here:
tosh-ac100.wetpaint.com/page/Backup+and+Restore
It's back to stock android right now.
I'll look into installing Gmail and Gtalk later on and MUCH MORE careful
If anyone can point me in the right direction, that would be great.
Happened to me too
Hi there, I had the same problem that yours and I have solved it this way:
Prerequisites:
Tegra2 Drivers 2 abailable
Android SDK in your system
A working ROM (folio mod for example)
How to:
Extract update.zip to a known folder
Power on the folio.
When see toshiba's logo push power button 3 times and then Volume UP
Connect to the computer
Move to android sdk tools (using CMD)
type:
fastboot flash recovery recovery.img (maybe a route is requiered for last one)
fastboot flash boot boot.img
fastboot flash system system.img
put the full update.zip file into SD and do a normal update
I hope this helps.
thanks metuskale
i got my to work as well
cheers
This happened to me a while ago but I am revisiting the problem now. In the recovery menu, I think I accidentally erased all the portions and that is where I got my problem. If I boot into the tablet, it doesn't go past the Eee pad splash screen. If I try to enter recovery it just gets to entering recovery image and is stuck there and same for fastboot. Is there anyway to fix this by sideloading or something or did I brick my device?
HuskyHamburger said:
This happened to me a while ago but I am revisiting the problem now. In the recovery menu, I think I accidentally erased all the portions and that is where I got my problem. If I boot into the tablet, it doesn't go past the Eee pad splash screen. If I try to enter recovery it just gets to entering recovery image and is stuck there and same for fastboot. Is there anyway to fix this by sideloading or something or did I brick my device?
Click to expand...
Click to collapse
If you can enter the bootloader, the OS, recovery or you have your nvflash backups then you have a chance.
If you can access none of these then you are hard bricked.
Tried Ubuntu Dual Boot: bootloop/brick; but fastboot, apx, and adb access OK
Posting here because: there are varios "bricked" threads - none with exact problem as I find.
I have/had: Asus Transformer Prime tf201, ICS
Bootloader „DE_epad-9.4.2.21-201203023“ A03
Rooted with motochopper
My Problem: Tried to install to Ubuntu Dual Boot using this: https://docs.google.com/document/d/1WfYcgH3FETUAGRbt_aBE5_J21CvTvXunVBdmfcCmtLA/edit?pli=1
after I had seen this video (link from descriptions) https://www.youtube.com/watch?v=QB9u6OKgop4.
Didn't work out since I could not do this step: "Mount the micro SD-card in Better Terminal on your TF201 by typing this..."
But I continued despite the bad signs!
Then, after using Fastboot to flash the .blob from above → bootloop.
And: no nvflash installed; yes stupid me, I know.
Then tried a lot, searched XDA and Androidforums -can't quite remember all.
Edit: Also tried Urkel's Fresh start.
Only: After trying to flash a stock ASUS ROM via Fastboot I could not even enter the recovery.
(Read later that you should NEVER do this in this state: http://forum.xda-developers.com/showthread.php?t=1514088,
I might even have taken the wrong version to do so.)
Also tried installing a TWRP recovery, but it didn't work.
It doesn't even perform its bootloop anymore, it is simply
stuck on the first screen showing the EEE logo and „device unlocked“.
Then I found http://www.transformerforums.com/fo...nbrick-your-tf201-using-method-hopefully.html
and managed to get to the point where I am now:
Access via Fastboot, ADB and APX (I also have a Win7 64bit partition on my Laptop, but since in ADB the prime doesn't show up I only use Linux 32bit).
Recovery: ClockworkMod Recovery v5.8.2.0 working.
BUT the problem is: error: can't mount /sdcard
Tried formatting via CWMR, it does something (no output) but can't mount /sdcard or /data anyway later.
It seems that I can push file via ADB: did so with a Cyanogenmod.zip to /sdcard, pushed successful,
but since I can't mount via CWMR its useless. After Rebooting the prime no changes.
I wanted to install Ubuntu to learn with it – guess is have learned a lot by bricking my pad...
I really love my prime, we used to cuddle and had a nice time. But now since it doesn't respond properly anymore I feel empty and sad.
Does anybody have a clue how to revive it? Thank you.
AnotherBrickInTheWall said:
Posting here because: there are varios "bricked" threads - none with exact problem as I find.
I have/had: Asus Transformer Prime tf201, ICS
Bootloader „DE_epad-9.4.2.21-201203023“ A03
Rooted with motochopper
My Problem: Tried to install to Ubuntu Dual Boot using this: https://docs.google.com/document/d/1WfYcgH3FETUAGRbt_aBE5_J21CvTvXunVBdmfcCmtLA/edit?pli=1
after I had seen this video (link from descriptions) https://www.youtube.com/watch?v=QB9u6OKgop4.
Didn't work out since I could not do this step: "Mount the micro SD-card in Better Terminal on your TF201 by typing this..."
But I continued despite the bad signs!
Then, after using Fastboot to flash the .blob from above → bootloop.
And: no nvflash installed; yes stupid me, I know.
Then tried a lot, searched XDA and Androidforums -can't quite remember all.
Edit: Also tried Urkel's Fresh start.
Only: After trying to flash a stock ASUS ROM via Fastboot I could not even enter the recovery.
(Read later that you should NEVER do this in this state: http://forum.xda-developers.com/showthread.php?t=1514088,
I might even have taken the wrong version to do so.)
Also tried installing a TWRP recovery, but it didn't work.
It doesn't even perform its bootloop anymore, it is simply
stuck on the first screen showing the EEE logo and „device unlocked“.
Then I found http://www.transformerforums.com/fo...nbrick-your-tf201-using-method-hopefully.html
and managed to get to the point where I am now:
Access via Fastboot, ADB and APX (I also have a Win7 64bit partition on my Laptop, but since in ADB the prime doesn't show up I only use Linux 32bit).
Recovery: ClockworkMod Recovery v5.8.2.0 working.
BUT the problem is: error: can't mount /sdcard
Tried formatting via CWMR, it does something (no output) but can't mount /sdcard or /data anyway later.
It seems that I can push file via ADB: did so with a Cyanogenmod.zip to /sdcard, pushed successful,
but since I can't mount via CWMR its useless. After Rebooting the prime no changes.
I wanted to install Ubuntu to learn with it – guess is have learned a lot by bricking my pad...
I really love my prime, we used to cuddle and had a nice time. But now since it doesn't respond properly anymore I feel empty and sad.
Does anybody have a clue how to revive it? Thank you.
Click to expand...
Click to collapse
Shoot me an email here [email protected]
We can get you going and than post our finding back here to help everyone out...
Thx Josh
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
Hey Everybody!
I am new to this forum, looking for a way to root my trekstor Surftab breeze 9.6 Quad. I already tried out the recommended tools, unfortunately none of them worked out. Is anyone of you aware of a method rooting the tab? Or did anyone already rooted it?
First ofall I am looking for a way to move files and apps to the external sd and delete pre-installed apps. Farther, if possible and available, a custom rom would be pretty amazing.
I'm only familiar to nexus root toolkit on my old nexus 4, otherwise I'm a newbie in rooting.
Maybe there's some of you able to help me. If necessary, I will look up more information on the tablet.
Lucas
Maybe as an Update:
Trying to build a working adb connection using the andorid sdk tools, the surftab is not listed as a device in "adb devices"
Anyone out there who can help me with the tablet?
Alright, new update for today.
I was able to get a driver running and the root-toolkits like KingoRoot, KingRoot, One Click root etc. noticed the device, I even was able to start the rooting, but all of those tools said "Root failed" or "Your device is soild to root".
Looks like those one click solution aren't able to root the surftab. I also tried towelroot and framaroot, both without any success.
I am still looking for help
If you are still interested, I successfully dumped whole eMMC memory from this tablet, so I can send you, for example, the boot partition. You can try patch it with Magisk
The magic
Yes, if it's not difficult for you, you can share the firmware. I will be grateful
Hi!
I attached xz-compressed stock boot.img for you!
Also, I have full eMMC dump, but:
recovery partition data are not usable (overwritten by uncompatible recovery image during mine tests)
no data partition
no platform bootloader partitions mmc0boot0 and mmc0boot1
Trekstor-Surftab-Breeze-9.6-ST96416-1-emmc-dump.dd.xz [1.12 GB]
Decompress and use kpartx tool (need force to ignore omitted data partition)
I have this tablet rooted now, so you can ask me for anything about it.
With love for all open source,
petabeda
Just one thing: fastboot boot is not supported here, so If you are afraid, flash modified boot.img to recovery partition with fastboot flash recovery boot.img for test (adb reboot and then adb reboot recovery
You will lost your recovery, but, at least, no bricked device in case of error (recovery is actually second boot partition)
petabeda said:
Just one thing: fastboot boot is not supported here, so If you are afraid, flash modified boot.img to recovery partition with fastboot flash recovery boot.img for test (adb reboot and then adb reboot recovery
You will lost your recovery, but, at least, no bricked device in case of error (recovery is actually second boot partition)
Click to expand...
Click to collapse
I have two surftab tablets. One version of the SIM card is fully functional. Another wifi version will not load. When loading, the orange logo at the moment of "collection" freezes. If there is, you can go into recovery even factory reset.
But nothing changes. I believe that the EMMC resource has been exhausted and therefore this behavior.
and to be honest, I don’t know how to write the partition. Since only the adb sideload command is available in recovery mode. Apparently, it is impossible to overwrite the firmware except through the programmer.
Until that time, I could not even pull out the firmware. Since there was no root access
Thank you for your help. As a thank you, I will give you a link to a tool to repair the Nexus 7 bootloader. Through a vulnerability in the tegra cpu. As I understand it, I use this method to hack the nintendo switch. I personally bought 4 nexus 2012 on the secondary market and one of them was able to restore in this way. They of them had a damaged eMMC other power controller. And even with a soldering station, I could not replace it because there is no suitable frame for the reball. In general, nexus are not bad, but there is very little disk space for installing google services and GAPPS are useless. And it is difficult to change partition. And it makes no sense because of the available firmware.
I see, you can''t unlock bootloader, because your device is not bootable at all. So, there is no way to get into fastboot mode?
We are anti e-waste fighters giving second chances!
The first photo is the available recovery menu. Where after choosing a factory reset, nothing changes. And through the adb update, only sideload mode is available.
The factory partition is not corrupted as the restore completes successfully. But the download fails. And not just does not occur, but freezes as in the screenshot above. Most likely a hardware problem eMMC.
Earlier, I saw something similar, for example, in Asus Zenpad, if turn off or connect the camera incorrectly, then the download stops. But here animation is stuck.
I don't know how to check eMMC exactly.
logs files is empty
And with recovery, no commands are available (like adb or fasboot)
There is a one way how to diagnose/repair/have fun with that Trekstor tablet - If you could and want to disassemble it:
have your tablet powered off
disassemble the tablet
carefully disconnect FFC cables (display and digitizer)
remove mainboard screws
at back side in the center of the board, there are three testpoints.......yes you are thinking right, these are actually 1.8V UART signals and GND
Connect these signals to your serial converter (in my case, Raspberry Pi), be careful and talk with the same loundnesses
Don''t power on the tablet, only plug usb cable, tablet will try boot and run healthd (charging mode with battery animation)
Your console will show you the magic (PBL/SBL) bootloader messages and Linux log and event, maybe, the console (though no root), lalalal (/dev/ttyFIQ0)
Wish you luck
After that, if everything goes well, you should be able to use reboot fastboot command to get fastboot mode !