Setup nvflash now!!! - G Tablet Q&A, Help & Troubleshooting

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.

Related

Bricked AC100

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

[Q] Unbricking Help needed ... Bricked by crazy fool (myself) trying a T8 rom on T2!

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

[Q] Unroot Fail Need Help will pay for fix

Hi everyone,
Well I'm in that freak out stage.... where I am sure some of you have been.
Heres my issue...
I have a transformer prime that;
I just unrooted using Vipermod
Then did a factory reset
Now I am stuck in CWM recovery
I attempted to do a restore but after it gets done it brings me back into the recovery
I attempted to ADB but the command prompt opens and closes right away ( I assume from not being in USB debugging, which I cant get into without a rom)
I have no rom's currently downloaded into the prime as I just wiped everything in there as well.
Please i'll gladly pay $5 to anyone who can fix this without it breaking more (hard bricking if I havent already done so)
AHHH please guys help, I'm afraid it will run out of battery soon then I'll be royally screwedddd
anyone?
are you on windows 7?
yes windows 7 professional sp 1 32bit . to reiterate I am stuck in Clockwork mod Recovery without root, and with no roms on the internal SD. I have access to one restore that works but after it completes it reboots back in recovery.
birchnick10 said:
yes windows 7 professional sp 1 32bit . to reiterate I am stuck in Clockwork mod Recovery without root, and with no roms on the internal SD. I have access to one restore that works but after it completes it reboots back in recovery.
Click to expand...
Click to collapse
Turn on your tablet, let it boot into CWM.
Open cmd, cd to the directory with adb (for example cd C:\android), then copy this line of text below and right click > paste in the command prompt window.
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13
Click to expand...
Click to collapse
That should get you out of CWM into Android, assuming your restore works fine.
Attempted and got error device not found.
I have uninstalled the transformer drivers and also installed the universal drivers as said in other threads.
I assume to use ADB i need usb debugging on for it to read??
My issue is I cant get into any rom so turning on usb debugging is a no go.
can i fastboot push a rom to the internal sd card or better yet can i install a rom from the external SD card via Clockwork mod recovery?
birchnick10 said:
Attempted and got error device not found.
I have uninstalled the transformer drivers and also installed the universal drivers as said in other threads.
I assume to use ADB i need usb debugging on for it to read??
My issue is I cant get into any rom so turning on usb debugging is a no go.
Click to expand...
Click to collapse
Navigate to %android sdk folder%\extras\google\usb_driver, open android_winusb.inf and copy the following in the sections
"Google.NTx86" and "Google.NTamd64"
; TF201
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4D01&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4D03&MI_02
;
; Fastboot for all projects
%SingleBootLoaderInterface% = USB_Install, USB\VID_0B05&PID_4DAF
Click to expand...
Click to collapse
Save the file and then try running the adb command I gave again.
Says error device not found. I appreciate the help keep it coming it's keeping my hope alive. I really hope this isnt truly hard bricked.
I cant get ADB to read the transformer prime. When I type adb devices nothing shows up . it starts the daemon successfully but then doesn't show the tfp.
Thank you again for helping. I am honestly going to pay who ever finds the true fix. This stress sucks
birchnick10 said:
Says error device not found. I appreciate the help keep it coming it's keeping my hope alive. I really hope this isnt truly hard bricked.
I cant get ADB to read the transformer prime. When I type adb devices nothing shows up . it starts the daemon successfully but then doesn't show the tfp.
Thank you again for helping. I am honestly going to pay who ever finds the true fix. This stress sucks
Click to expand...
Click to collapse
Try the instructions here. Try using this only as a last-ditch resort.
it wont shut off either... i tried both of the above mentions and cant get adb to recognize the prime
Attempted both and stuck at recovery loop without root. any more ideas? is it possible to flash rom from external sd? or is there a recovery I could fastboot rhat has this feature?
Attempted both and neither work. I need to somehow get usb debugging enabled while in clockwork mod. Or figure out a way to install a rom via external SD card while in CWM. Any more help is appreciated!
birchnick10 said:
Attempted and got error device not found.
I have uninstalled the transformer drivers and also installed the universal drivers as said in other threads.
I assume to use ADB i need usb debugging on for it to read??
My issue is I cant get into any rom so turning on usb debugging is a no go.
Click to expand...
Click to collapse
No adb debugging is needed in cwm. Even without any ROM installed. Recovery is different from Android.
Try to long press power (at least ten seconds) to hard reboot, and see if it changes something in device detection.
Did a hard reset and it boots me back into Recovery.
I was able to get a new rom into the internal SD via the emergency/backup.zip method but after it completes and I do a reboot it just boots right back into recovery again.
Any help please is apprecaited.
$5 bounty for a fix via paypal
Oh joy. This one is a spaghetti western in the making.
Okay. Question first : Does Windows 7 RECOGNISE the device in any way shape or form. To find out if this can be done, you need to power up the device and hold the power and volume down buttons, DO NOT press volume up when it suggests a kernel image. If you get three icons, hit vol down once and up once, then plug the USB cable into the PC and the tablet.
If it sees "Something", you've a chance. Download the naked universal USB driver from the dev forum, install it and have your device pick it up on the windows computer. I'm assuming from your comments that you've GOT a working fastboot and adb so I'm going to skip the instructions on that.
If you do have a something, and it's recognised, hit fastboot -i 0x0b05 reboot, if it reboots of it's own accord at this point, you can confirm you have working ADB and Fastboot access. From there you've a few choices. My personal preference would be to ADB push a rom down -after- doing a rebuild of the recovery image via fastboot (I really recommend TWRP for this bit).
http://forum.xda-developers.com/showthread.php?p=26093546#post26093546 - This post here which I wrote will explain how to flash TWRP from fastboot access, presuming you can get it. Once that step is done, wipe EVERYTHING from TWRP, and I mean the whole nine yards, including /system. Raze the memory down to only things it can't actually nuke. Once that's done, reboot to fastboot protocol, get a ROM pushed via ADB and install from inside TWRP.
That -should- get you back in business. Though judging by the tangle you're in, I make no promises.
ADB wont recognize the device. I have installed and uninstalled the drivers about 5 times.
It wont boot into fastboot - just goes directly into Clockwork Mod recovery. Even while holding power and volume down text comes up that says looking for asus recovery. then says clockwork recovery and boots directly into that.
The only way I can get anything into the internal SD card is with MasterZen88's Emergency script tool that puts any 1 file into the internal SD card as backup.zip
It was unrooted prior to all of this as well.
*cringe*
If ADB isn't working -at all- and it's not using the naked USB drivers to get you any kind of workable access. You're starting to smell very much like a hard brick scenario. I'm honestly not sure if there's a way out of that. A lot of the solutions for unbricking absolutely require that the device is able to talk to the outside world, if it's not and the ADB shell is essentially telling you it's talking to dead air, you're in a world of pain.
It's a long shot but it may be worth speaking to ASUS to see if they are willing to, for a fee, restore your tablet to factory settings. Though I can't imagine that will be cheap or simple. If you are able to get an RMA or a means of getting ASUS to poke it, make sure to take photos. Their techies appear to have the worst case of butterfingers in the world.
Go over Pandaball's suggestion, because that's really the last step I can think of before contacting ASUS

[Q] Bricked?

Hi Everyone,
my machine had HB 1.2 on it until yesterday. I wanted to update it to 1.3 and tried to get into recovery.
Now I did see the RCV logo on by screen but once I selected it I got stuck.
Next thing I wanted to get back to my normal boot and it also got stuck. Even APX no longer seems to work.
So does this mean it is really bricked? I've been searching through the net but can't find exactly this situation.
I'm afraid I don't know what to no next, apart from shipping it back to asus.
cwomeijer said:
Hi Everyone,
my machine had HB 1.2 on it until yesterday. I wanted to update it to 1.3 and tried to get into recovery.
Now I did see the RCV logo on by screen but once I selected it I got stuck.
Next thing I wanted to get back to my normal boot and it also got stuck. Even APX no longer seems to work.
So does this mean it is really bricked? I've been searching through the net but can't find exactly this situation.
I'm afraid I don't know what to no next, apart from shipping it back to asus.
Click to expand...
Click to collapse
Do you have nvFlash enabled?? If so, you should be able to recover the device... you could get in touch with the AndroidRoot team if you have nvFlash and cannot easily enter APX mode...
craigacgomez said:
Do you have nvFlash enabled?? If so, you should be able to recover the device... you could get in touch with the AndroidRoot team if you have nvFlash and cannot easily enter APX mode...
Click to expand...
Click to collapse
Well I did downloaded nvFlash, before the machine froze I was able to get into APX mode however I never enabled nvFlash.
I was in fact trying to do that when it all broke down for me.
cwomeijer said:
Well I did downloaded nvFlash, before the machine froze I was able to get into APX mode however I never enabled nvFlash.
I was in fact trying to do that when it all broke down for me.
Click to expand...
Click to collapse
Can you get into fastboot mode?? did you start the nvFlash steps?? if so, what step did you reach??
craigacgomez said:
Do you have nvFlash enabled?? If so, you should be able to recover the device... you could get in touch with the AndroidRoot team if you have nvFlash and cannot easily enter APX mode...
Click to expand...
Click to collapse
When you say "enabled" are you referring to successfully completing the nvflash process given by the AndroidRoot Team? Just for clarification.
andrewjt19 said:
When you say "enabled" are you referring to successfully completing the nvflash process given by the AndroidRoot Team? Just for clarification.
Click to expand...
Click to collapse
Some more information. If I try to boot in APX mode (PWR + Vol UP) my pc does seem to detect some device.
In fact I see a Asus Transformer Prime APX interface in my Device manager.
However adb devices does not show me anything. I can't really say if that is ok or not.
And fastboot devices is also telling me there are no devices.
So both fastboot and nvflash seem to be stuck.
cwomeijer said:
Some more information. If I try to boot in APX mode (PWR + Vol UP) my pc does seem to detect some device.
In fact I see a Asus Transformer Prime APX interface in my Device manager.
However adb devices does not show me anything. I can't really say if that is ok or not.
And fastboot devices is also telling me there are no devices.
So both fastboot and nvflash seem to be stuck.
Click to expand...
Click to collapse
mine too :crying::crying::crying::crying:
cwomeijer said:
Some more information. If I try to boot in APX mode (PWR + Vol UP) my pc does seem to detect some device.
In fact I see a Asus Transformer Prime APX interface in my Device manager.
However adb devices does not show me anything. I can't really say if that is ok or not.
And fastboot devices is also telling me there are no devices.
So both fastboot and nvflash seem to be stuck.
Click to expand...
Click to collapse
APX mode and ADB are different. The fact that you have APX showing up is a great sign. I can't help you through the nvflash process, but i know you're probably ok...
APX mode is not for use with adb or fastboot, that is why these applications will not see the device at all.
You will not be able to use nvflash/APX mode unless you have followed the instructions provided by AndroidRoot.Mobi BEFORE getting into this situation.
Enabling access to nvflash needs to be done before the device is bricked not after
Ok so i know i have big problem.
Any idea how i get out of this mess?
It seems i only have apx right now.
Sent from my GT-I9000 using xda app-developers app
Does this APX allow you to do anything else?
Im running out of ideas.
Would asus fix this?
Sent from my GT-I9000 using xda app-developers app
cwomeijer said:
Does this APX allow you to do anything else?
Im running out of ideas.
Would asus fix this?
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Hold on a sec.. Let's go back a few steps.
When you hold down volume down and power to boot it up you are getting the 4 icons. When you press volume down and go over to the usb icon and then press volume up you are still getting entering fastboot mode correct?
If you are what is now showing in device manager on your computer. Do you have any android or asus devices or do you have any icons with explanation marks on them ?

[Q] TF201 stuck at ASUS splash screen after..

So my Transformer Prime is stuck at ASUS logo splash screen..
Please let me explain what I have done to cause this.
0. Using Transformer Prime on the original Android system (4.1??) - I took the following steps to install android kit kat 4.4.?
1. I rooted it then unlocked it
2. I installed the recovery system - http://forum.xda-developers.com/devdb/project/?id=2229#downloads
following the instruction below =>
original thread - http://www.transformerforums.com/forum/transformer-prime-roms/41446-re-install-using-nvflash.html
If you haven't already found a recovery flasH the one found here
Cyanogenmod 11.0 Unofficial TF201 - xda-developers DevDB - http://forum.xda-developers.com/devdb/project/?id=2229#downloads
Place it in your fastboot folder. Open a command prompt in the fastboot folder by right-clicking in the folder and choosing "open command prompt here"
Reboot tablet into fastboot and connect to pc. Then type:
fastboot devices
You should see your tablet listed.
If so type:
fastboot -i 0xb05 flash recovery recovery.img.SOS
You should see a blue progress bar under an Asus logo.
Once done, reboot tablet into recovery and you should be good to go.
Click to expand...
Click to collapse
3. I used the recovery system to successfully install the followings
* cm-11-20131229-UNOFFICIAL-tf201.zip (kit kat android system 4.4?)
* gapps-kk-20131119.zip
4. After this I rebooted the tablet then now it''s stuck at the ASUS screen.
I have found that quite a few people have experienced this... but I'm not very certain of what I need to do so I would appreciate if any of you can help me to resolve this issue. My ultimate goal now is to be able to boot the tablet to a usable state(with apps).
Currently,
* fastboot cannot be done
* can connect to PC in APX(?) mode
* downloaded rom(?) US_epad-user-10.4.2.18.zip from http://www.asus.com/Tablets/Eee_Pad_Transformer_Prime_TF201/HelpDesk_Download/ but I hae no idea how i can use this.
* i have 'nvflash' folder on pc, in the folder I have blob.bin.... I have attached a screenshot of what's in the folder
Thank you in advance.
You have to flash the correct version of TWRP for the bootloader you are on. Flashing any random TWRP without knowing is a sure way to brick the machine.
Please show me the link to the instructions you were following. I don't think you can tell me your exact bootloader version from what you can see so please also tell me where the Tegra logo is on your screen. Bottom center or bottom right ?
Edit. I forgot to say the good news is you have nvflash backups so you should be able to fix it anyway. If you just want to go ahead and try and recover it yourself start here. http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
flumpster said:
You have to flash the correct version of TWRP for the bootloader you are on. Flashing any random TWRP without knowing is a sure way to brick the machine.
Please show me the link to the instructions you were following. I don't think you can tell me your exact bootloader version from what you can see so please also tell me where the Tegra logo is on your screen. Bottom center or bottom right ?
Edit. I forgot to say the good news is you have nvflash backups so you should be able to fix it anyway. If you just want to go ahead and try and recover it yourself start here. http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
Click to expand...
Click to collapse
Hi flumpster, thank you so much for trying to help me.
Initially I followed this tutorial to unlock my TF201 and backed up Blobs and Enabling Nvflash access.
https://matthill.eu/android/transformer-prime-tf201-jellybean-nvflash/
this flatline recovery? was what I had and it did NOT install cm-11-20131229-UNOFFICIAL-tf201.zip (kit kat android system 4.4?)
Then I found this thread to find another user having the same installation error problem - http://www.transformerforums.com/forum/transformer-prime-roms/41446-re-install-using-nvflash.html
In the thread above, I followed a post by a guy named 'mediadriven'' to re-install another recovery(?).
File: recovery.img - http://forum.xda-developers.com/devdb/project/?id=2229#downloads
With the recovery tool, I was able to install
* cm-11-20131229-UNOFFICIAL-tf201.zip (kit kat android system 4.4?) - http://www.mediafire.com/download/xdwpk61crqttmib/cm-11-20131229-UNOFFICIAL-tf201.zip
* gapps-kk-20131119.zip - https://www.androidfilehost.com/?fid=23252070760974567
After the installation, I rebooted the tablet then now it''s stuck at the ASUS screen.
---
You have to flash the correct version of TWRP for the bootloader you are on. Flashing any random TWRP without knowing is a sure way to brick the machine.
Click to expand...
Click to collapse
>> where could I download a correct version of TWRP for the bootloader and how may I install this..?
I don't think you can tell me your exact bootloader version from what you can see so please also tell me where the Tegra logo is on your screen. Bottom center or bottom right ?
Click to expand...
Click to collapse
>> i'm sorry, im not sure which version of bootloader im using. Tegra logo is on bottom right screen. (image attached)
I forgot to say the good news is you have nvflash backups so you should be able to fix it anyway. If you just want to go ahead and try and recover it yourself start here. http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
Click to expand...
Click to collapse
Thank you for the link, before posting this thread here I have attempted to follow the thread above to unbrick my tf201. I was able to follow up to step 5 to be in nvflash mode.
I was not able to follow from step 6.. perhaps that is because I do not have these files - blob.EBT, blob.SOS, blob.LNX, and blob.APP
List of files that I have in nvflash is in the picture attached in my first post.
Thank you.
The files you are missing for step 6 are all in a zip file at the bottom of the link I gave you. Here is the direct link.
https://goo.im/devs/craigacgomez/prime/TF201-JB-10.4.2.15-Unblobed.zip/
flumpster said:
The files you are missing for step 6 are all in a zip file at the bottom of the link I gave you. Here is the direct link.
Click to expand...
Click to collapse
thanks flumpster, ill try the guide again with the zip file tonight. Will let you know how it goes!
flumpster said:
The files you are missing for step 6 are all in a zip file at the bottom of the link I gave you. Here is the direct link.
Click to expand...
Click to collapse
so each time i ran a nvflash command it successfully completes then rebooted itself to the Asus splash logo screen.. I have to reboot my device into apx mode then wheelie back into nvflash before being able to go to the next step..
When I ran the last command below it did not seem like it did anything.. output i got from the nvflash was "[resume mode]".
nvflash.exe -r --go
Rebooting the tablet makes the system stuck at ASUS splash logo screen..
I can reboot my device into APX mode.. and can also use nvflash but I may not have been follow the steps in the guide properly as it rebooted itself each time I ran nvflash commands.
What could I do?
jinseiichido said:
so each time i ran a nvflash command it successfully completes then rebooted itself to the Asus splash logo screen.. I have to reboot my device into apx mode then wheelie back into nvflash before being able to go to the next step..
When I ran the last command below it did not seem like it did anything.. output i got from the nvflash was "[resume mode]".
nvflash.exe -r --go
Rebooting the tablet makes the system stuck at ASUS splash logo screen..
I can reboot my device into APX mode.. and can also use nvflash but I may not have been follow the steps in the guide properly as it rebooted itself each time I ran nvflash commands.
What could I do?
Click to expand...
Click to collapse
I'm not sure what you are doing wrong mate. I would do it all again from scratch starting from the beginning of the instructions.
Also while you are on the Asus splash screen try holding down the volume down button and the power button for 10 seconds until it restarts and then keep holding them. Do you end up in the bootloader screen now ?
flumpster said:
I'm not sure what you are doing wrong mate. I would do it all again from scratch starting from the beginning of the instructions.
Also while you are on the Asus splash screen try holding down the volume down button and the power button for 10 seconds until it restarts and then keep holding them. Do you end up in the bootloader screen now ?
Click to expand...
Click to collapse
flumpster, unfortunately it does not show the bootloader screen. posted this problem to - http://forum.xda-developers.com/showpost.php?p=60640712&postcount=211
I'm still needing help to get my tablet working again..
If you could help me to get the tablet working again.. i will donate you $20(US) either paypal or via this forum.
Thank you.
jinseiichido said:
I'm still needing help to get my tablet working again..
If you could help me to get the tablet working again.. i will donate you $20(US) either paypal or via this forum.
Thank you.
Click to expand...
Click to collapse
Unfortunately the money doesn't help, I cannot see what you are doing wrong. Everything I have said should work for you and if I had the machine here I am pretty sure I could get it working in under an hour.
If you was in the UK I would offer to let you send it to me as long as you paid the return postage but from the US that is just way too expensive. The only thing I can advise at this point is to try and find someone on here from the US who is willing to take a look at it for you.
If I had been you I would have tested multiple PCs with the universal drivers and also tried different usb ports (2 and 3) then if all that failed I would have booted off a live linux cd and tried it in there. If that still failed I would have used the script from the end of craigs nvflash post that puts the machines partitions and everything else back to stock but this has to be done in linux also.
Have you solved this problem now ?
In case you haven't, I found a possible solution for the 'stuck at Asus logo problem'
My prime was suffering the same problem; except that hadn't done an nvflash backup. What worked for me was a pressing the of the power and reset button (with a needle) and volume up button (I believe) at the same time. I don't know what combination exactly since I was trying some things with the reset button and boom it worked

Categories

Resources