Related
from the wiki page, attempting to nvflash the stock image. Problem is after downloading 3 different times, there is NO nvflash_gtablet.bat file in there. Am I missing something? am I doing something wrong here?
http://forum.xda-developers.com/showthread.php?t=861950
I'm not a Windows user, so I don't really know if the batch works myself. I am assuming that it does.
thank you roebeet, this will be the 2nd time today youve saved my newb a$$ if it works.
Awesome
I had to use CW and repartition, scrub cache and such but I am back to factory again, now to mod this turd..Thanks a ton Roebeet!
Glad to hear that you got it working!
I've run into an issue where my Gpad flashes properly, but after being flashed, it continually goes back into APX mode on power cycle. If I issue the command "nvflash --bl bootloader.bin --go", I can confirm this as it will reload the flash bootloader. I can re-run the script to reload the tablet and it will reload the partitions over and over again, but each time the Gpad is powered off, it returns to APX mode. Thoughts?
Problem solved... I had downloaded the _46 flash image. That apparently causes the tablet to into APX mode instead of working properly if you use it. Is that for the Gpad, or for some other product??
(if anyone can, please change these to links. I'm not allowed to post links yet since I'm a new user)
First, download the froyo image from:
developer DOT nvidia DOT com SLASH tegra SLASH downloads
Then, download this and merge it with the folder that the Nvidia tools install to (you'll have to overwrite 2 files).
www DOT dropbox DOT com SLASH s SLASH wrcd87u1iy31u4e SLASH nvflash_gtablet_2010110500.zip
Download Clockwork Recovery, get the recovery.img file from the update.zip, rename it to clockwork.img, and move it into the Nvidia folder.
android DOT d3xt3r01 DOT tk SLASH cyanogen SLASH harmony SLASH root SLASH ClockworkMod_Gtab_v08.zip
Connect the G-Tab to your computer via USB and power it on while holding Vol - (NOT +!). The screen will go on for a few seconds then turn off. The tablet's not off, it's just in APX mode.
Go to Device Manager and install the drivers for it (they're in theNvidiaFolder\usbpcdriver).
Open a command prompt in the nvidia folder and enter "nvflash --bl bootloader.bin --download 9 clockwork.img"
It should do it's thing and if it goes fine, you'll get your recovery back!
You are the man!!!! I am back in business. I was on the right track, but you figured it out and I am a happy camper.
Anything you need, let me know (except girls, currency, drugs)
Quick question, Now that I have NVFlash setup and working, is there a simple way using NVFlash to take a snapshot of my Tablet so I have a backup image if I need to restore?
brookfield said:
Quick question, Now that I have NVFlash setup and working, is there a simple way using NVFlash to take a snapshot of my Tablet so I have a backup image if I need to restore?
Click to expand...
Click to collapse
You could try this: http://tosh-ac100.wetpaint.com/page/Backup+and+Restore and just use bekit's bootloader.bin.
ngorgi said:
Then, download this and merge it with the folder that the Nvidia tools install to (you'll have to overwrite 2 files).
www DOT dropbox DOT com SLASH s SLASH wrcd87u1iy31u4e SLASH nvflash_gtablet_2010110500.zip
Click to expand...
Click to collapse
I'm a little confused. This says download the file, but overwrite two files?
I have downloaded and installed the first thing. Now i have downloaded the second file but not sure what to overwrite.
You need to unzip the files into the same directory. When you do it will ask you to overwrite 2files binloader is one of them
Ok, I know that I am missing something here. I have unzipped the "nvflash" file to this directory (C:\Program Files\NVIDIA Corporation\tegra_froyo_20101105).
I am never asked to overwrite anything. Is this the "NVIDIA tools" folder mentioned in post 1?
Sorry this is so hard for my small brain.
EDIT:Nevermind, I figured it out anyway. Thanks
I'm confused as what you mean by get your recovery back. Did you have a problem where it was overwritten?
No, for some reason it just goes away. Not sure why. When you hold power + "vol +", it should boot to recovery, but it just boots to CM.
Anyway, this was a lifesaver for sure today. Thanks for your help everyone!
Thanks, that helped a lot - works fine!
T.
I hate this tablet. I got the unit today and installed the OTA update and doing so i disabled clockword recovery. I followed these steps and got it to work from cmd and it went through the downloading process. My tablet is stuck on entering nvflash recovery mode. When i reboot and try the recovery it goes black again. I am positive I did it correctly and got the confirmation screen at the end of cmd.
I had the same issue... could not boot into recovery or the rom... right after installing clockwork .12
I had to take my unit back and get a new one...
What version of the clockworkMod image do you use to FLASH into the recovery Partition. I did not use the latest, You may need to try the 2.5.1.3 (That is what I used and it works).
Thanks!
ngorgi,
I just wanted to give you a big thanks... I had borked my g tab till I ran through your walkthrough.
Thank you so much!
-Lil'
Glad to see this actually helped a few people out
Now I may be wrong here (and if I am, PLEASE correct me), but I've come to the conclusion that this device is simply UNBRICKABLE. I've had my recovery disappear, had the magic value mismatch error, even had the device freeze in Nvflash mode where I had to wait for the batteries to drain before I could restart and I've been able to fix it EVERY TIME. Nvflash is too awesome.
FWIW, this is the only method that would work for me getting clockword to install on a fresh out of the box unit....I tried the sticky and it would show me the ! for a brief second and then reboot...
thanks!
HELP recovery problem
nvflash --bl bootloader.bin --download 9 cwm254recovery.img
bootloader.bin sent succesfully
sending file: cwm254recovery.img
-851968/4026368 bytes sentdata send failed NvError 0x30012
command failure: partition dowload failed
Click to expand...
Click to collapse
HELP!!!!!!!!!!!!!!!!!!!!!!!!
haltol said:
nvflash --bl bootloader.bin --download 9 cwm254recovery.img
HELP!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Try doing:
nvflash --bl bootloader.bin --getpartitiontable mypt.text --go
To get you partition table and check the .text to confirn that part9 is SOS.
Jim
I am not so sure. One of my GTablets will no longer boot. I have to use nvflash to boot it. Battery drain, reset button inside, nvflash stock rom, TnT-light...whatever, the tablet will not boot. Nvflash and format parition 2 and I can get it to proceed into booting. I can nvflash bekits recovery and install roms or kernels.....reboot or power off and it will not come up until I nvflash "force" it to boot.
So i am not so sure they are completely unbrickable...just hard to do so. Mine started with the magic value mismatch error.
ngorgi said:
Glad to see this actually helped a few people out
Now I may be wrong here (and if I am, PLEASE correct me), but I've come to the conclusion that this device is simply UNBRICKABLE. I've had my recovery disappear, had the magic value mismatch error, even had the device freeze in Nvflash mode where I had to wait for the batteries to drain before I could restart and I've been able to fix it EVERY TIME. Nvflash is too awesome.
Click to expand...
Click to collapse
Sent from my Viewsonic 10" GTab...
help Got a brick.
Got a brick. I can not get into the APX mode.
Hold down Volume (-) and power while booting - did not work. May have other options?
Read Me First!
This will get CWM on your device's recovery partition and wipe out your stock recovery. If you wish to keep things simpler, just install ROM Manager and "flash" the T-Mobile G2x recovery from there, it doesn't actually overwrite your stock recovery, but it will still let you boot into CWM recovery, only by using ROM Manager, of course.
** Not responsible for any damage done, obviously. **
Instructions
Here is an initial test of CWM recovery for the G2X. You need to use nvflash to flash this, I've packaged it up for you and included a nice bash script to flash it, on Linux.
Pull battery.
Hold VOL UP+VOL DOWN
Plug in USB.
The phone won't do anything, but you should see it under 'lspci'.
Then grab http://mirror.dal.tdrevolution.net/ctso/g2x/nvflash-recovery.tgz
Extract it, and run flash-recovery.sh
You're not stuck on a software upgrade screen, when your computer says the recovery image was transferred successfully, just pull USB and you're done.
Changes
test2 - Properly mount /sdcard to the external SD.
test2 - Fix device name, should be p999 not p990.
test2 - Do not use custom recovery ui, navigate using VOL UP/DOWN and Power to select. (BOARD_HAS_NO_SELECT_BUTTON).
test1 - Initialness.
Wow, this was fast. I'm already loving the development on this phone.
Too sleepy to try something I'm not familiar with, but thank you SO MUCH for the quick recovery!!! I was afraid I was going to regret leaving the N1 dev scene, but seriously, I don't think I'll notice a difference...
[edit: can't do it anyways.... running windows 7 here.]
[edit 2: wait, now I'm confused. Is the entire thing linux only or just the script? I feel extremely stupid right now.]
lance713 said:
[edit: can't do it anyways.... running windows 7 here.]
[edit 2: wait, now I'm confused. Is the entire thing linux only or just the script? I feel extremely stupid right now.]
Click to expand...
Click to collapse
You can run nvflash on Windows, i just don't have the files handy. Just the tools I provided are linux-only, maybe someone will whip up a quick windows version.
Had a feeling something was going to be released so I had to starly up
Sent from my LG-P999 using XDA App
Wow good job, going to try this tomorrow.
Sent from my LG-P999 using XDA Premium App
one day after store release and already a cwm... nice!!!
gonna give this a try
Trying to do this in Windows...almost got it... but I need the NVidia APX driver in order for Win7 to recognize the device. Searching...
sudo ./nvflash --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 recovery-star-test1.img
Based on the flash-recovery.sh script above, is there a need for a fastboot.bin file as well?
joackie27 said:
sudo ./nvflash --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 recovery-star-test1.img
Based on the flash-recovery.sh script above, is there a need for a fastboot.bin file as well?
Click to expand...
Click to collapse
whoops, added it, redownload
ctso said:
whoops, added it, redownload
Click to expand...
Click to collapse
Thanks @ChrisSoyars
mapin0518 said:
Trying to do this in Windows...almost got it... but I need the NVidia APX driver in order for Win7 to recognize the device. Searching...
Click to expand...
Click to collapse
Got it... my phone says "S/W Upgrade Please wait while upgrading..."... fingers crossed..
mapin0518 said:
Got it... my phone says "S/W Upgrade Please wait while upgrading..."... fingers crossed..
Click to expand...
Click to collapse
Did you get my PM about the Nvidia APX driver?
joackie27 said:
Did you get my PM about the Nvidia APX driver?
Click to expand...
Click to collapse
Just did, and PM'ed you back. Please take a look !
EDIT: NEvermind, I got it !
For me i have been on the upgrade screen for two - three minutes with no activity, how low is this supposed to take.
also can someone pm me the original framework-res.apk i kind of foobar'd android
chrs2021 said:
For me i have been on the upgrade screen for two - three minutes with no activity, how low is this supposed to take.
also can someone pm me the original framework-res.apk i kind of foobar'd android
Click to expand...
Click to collapse
Same here, stuck on upgrade please wait screen for some time now... not sure what to do !
mapin0518 said:
Same here, stuck on upgrade please wait screen for some time now... not sure what to do !
Click to expand...
Click to collapse
Nevermind it worked !!!!!!!!!!!
It was stuck on the wait screen, but i just unplugged and rebooted and it was find. Then I powered down and booted into recovery and low and behold i have ClockWorkMod !!!!
Awesome thank you !!!
Here's a link to the Windows nvflash and the NVIDIA APX driver:
http://android.modaco.com/content/l...lash-setup-instructions-drivers-links-active/
As OP instructed: Pull battery. Put battery back in. Hold down both Volume buttons while you plug in USB. It should be recognized by Windows as an Nvidia APX device and it will search for drivers. Point it to the the driver folder when Windows asks you where it is. Once the driver is installed, run this command from command prompt:
"nvflash.exe" --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 recovery-star-test2.img
My phone was stuck on a please wait screen, but after 10 minutes I unplugged it and all was fine. (I ran this in Windows 7 Enterprise 32-bit inside a VmWare Fusion virtual machine on a Mac)
Boot into recovery by holding down Power and Volume Down. Volume buttons will scroll up/down and power button will choose selection.
watching...................
Using the windows 7 method, it shows that it sent everything over but when i try to go into recovery it just pops up with the S/W Upgrade screen
I can't seem to get the NVIDIA APX device part to come up - Windows does nothing when I plug in the USB with both volume up and down held...
EDIT: I don't know WTF the deal is with this thing but it really doesn't like to install drivers for crap... Earlier it refused to recognize ADB then after I left the phone hooked up for a few minutes and was searching for info, it suddenly recognized ADB and installed the driver. Now the first time I tried this, it didn't work. Second battery pull, it works perfectly other than the fact that Windows didn't prompt me for a driver and just said it failed so I had to do it from Device Manager.
Either way, it didn't work. Just like the last person, I was taken right back to the S/W Update screen using the Windows script.
Hi all,
I have a bricked TF101 (SBK v2) that I am trying to recover. There are numerous threads for this which I have tried following but keep hitting brick walls and as these threads tend to be in the development section, I am currently unable to post in them for advice.
I have tried a few differing programs to try and recover the device including "Oneclickrecovery", "BRK_Rootkit" and "Easyflasher"
Easy flasher (0.8.3b) seems to give the best results so far so I'm going to try and continue with this.
When running through the steps I get the following on the tablet screen:
Entering nvflash recovery mode nv3p server
chipvid: 12345678912344
!!!!!phone update sucess!!!!!
and the following from Easyflasher:
EasyFlasher for TF101 - By [email protected]
Using SBK2
---------------------------------------------------------------------------------------------------------------------------
Flashing Asus stock zip
>Extracting files.. please wait..
>Extracting blob archive..
>Blob extracted!
>Blob size 533946.73828125kb
Running Wheelie..
>Tablet is now ready for Nvflash
>Extracting from blob...
>Cleaning up before flashing...
>Checking file sizes
>SOS size 4184kb
>APP size 524288kb
>EBT size 1420.6171875kb
>LNX size 4054kb
Done!
However each time I reboot the device goes straight back in to APX mode. I have seen from the thread that different folks had different outcomes with different versions of easyflasher, but I cannot locate where to download different versions.
I am currently in the UK but the device was purchased in the US but I get the same results when trying to use any of the WW or US stock ROM update versions.
Any help locating different versions of easyflasher or any other advice you guys might have would be very well received as I now have a sore forehead from banging it on my desk.
Thanks for your time,
dhehir
reinstall recovery with easy flasher and after it finish power nadh olf button down.
vietchinh said:
reinstall recovery with easy flasher and after it finish power nadh olf button down.
Click to expand...
Click to collapse
Thanks vietchinh,
I have tried this, just keeps going back to APX mode each time.
Have you tried just a straight forward NVFLASH ROM ?
http://xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)/STOCK+ROMS/ICS+.27
The ROMs linked above will return your tablet to 100% Stock so you would need to root and flash custom recovery afterwards, but it would determine whether or not it is a hardware fault or just a bad luck combination of your custom ROM / Recovery
Just extract the NVFLASH ROM, enter APX Mode, plug the tablet into the PC and run the .bat file to flash, once it reboots it should be 100% stock
*Detection* said:
Have you tried just a straight forward NVFLASH ROM ?
The ROMs linked above will return your tablet to 100% Stock so you would need to root and flash custom recovery afterwards, but it would determine whether or not it is a hardware fault or just a bad luck combination of your custom ROM / Recovery
Just extract the NVFLASH ROM, enter APX Mode, plug the tablet into the PC and run the .bat file to flash, once it reboots it should be 100% stock
Click to expand...
Click to collapse
That link above did the trick for me! 3 months later and your post saved my device!
After installing TEAMEOS 4.2.1 (Jelly Bean) and not liking the performance and lockups, I tried to go back to the stock using first Rogue XM recovery (and didn't like it ever) and then TWRP 2.3.2.3. I tried a variety of things from different forums, but my tf101 eventually would only go into APX mode. No matter what, the screen would always remain black and I would see the device show APX in devices on my windows 7.
I tried EasyRecovery (this one didn't seem to do anything), OneRecover, direct nvflash, and nothing worked. I kept trying even more suggestions and doing the same things over and over as some people suggested worked for them (duh), and still nothing worked.
After countless hours of searching, trying different things, your easy suggestion was all I needed!
I have a C10 serial tf101 (US stock firmware).
Thanks a million!
--Eli
morroyoki said:
That link above did the trick for me! 3 months later and your post saved my device!
After installing TEAMEOS 4.2.1 (Jelly Bean) and not liking the performance and lockups, I tried to go back to the stock using first Rogue XM recovery (and didn't like it ever) and then TWRP 2.3.2.3. I tried a variety of things from different forums, but my tf101 eventually would only go into APX mode. No matter what, the screen would always remain black and I would see the device show APX in devices on my windows 7.
I tried EasyRecovery (this one didn't seem to do anything), OneRecover, direct nvflash, and nothing worked. I kept trying even more suggestions and doing the same things over and over as some people suggested worked for them (duh), and still nothing worked.
After countless hours of searching, trying different things, your easy suggestion was all I needed!
I have a C10 serial tf101 (US stock firmware).
Thanks a million!
--Eli
Click to expand...
Click to collapse
haha Great! Well, at least you picked up some knowledge on your journey
Now you know you can play around with anything you want and always be able to get back to stock when you're done
btw, give Team EOS3 #81 combined with K.A.T Kernel #69 a shot
That is JellyBean 4.1.2 and the fastest and most stable ROM for the TF101 imo
*Detection* said:
haha Great! Well, at least you picked up some knowledge on your journey
Now you know you can play around with anything you want and always be able to get back to stock when you're done
btw, give Team EOS3 #81 combined with K.A.T Kernel #69 a shot
That is JellyBean 4.1.2 and the fastest and most stable ROM for the TF101 imo
Click to expand...
Click to collapse
Hello,
I have a very similar problem with my TF101 since few months. Like "dhehir", it is always in APX mode, EasyFlasher seems to works (it displays the three lines
"Entering nvflash recovery mode nv3p server
chipvid: 12345678912344
!!!!!phone update sucess!!!!!", EasyFlasher stops at the partition 7.
The link puposed by *Detection* doesn't work, do you know where I can find it ?
Thanks,
Erev
erevlis said:
Hello,
I have a very similar problem with my TF101 since few months. Like "dhehir", it is always in APX mode, EasyFlasher seems to works (it displays the three lines
"Entering nvflash recovery mode nv3p server
chipvid: 12345678912344
!!!!!phone update sucess!!!!!", EasyFlasher stops at the partition 7.
The link puposed by *Detection* doesn't work, do you know where I can find it ?
Thanks,
Erev
Click to expand...
Click to collapse
Here you go
Code:
https://mega.co.nz/#!YZlVESKS!PVP6ixECCgapstRiD9bY9zxbWC5ctjBGvWSI1k09JhE
*Detection* said:
Here you go
Code:
https://mega.co.nz/#!YZlVESKS!PVP6ixECCgapstRiD9bY9zxbWC5ctjBGvWSI1k09JhE
Click to expand...
Click to collapse
Thanks a lot !
I'll run it tonight.
*Detection* said:
Here you go
Code:
https://mega.co.nz/#!YZlVESKS!PVP6ixECCgapstRiD9bY9zxbWC5ctjBGvWSI1k09JhE
Click to expand...
Click to collapse
Snif.... it doesn't work .
During the process, I have the same issue I had with EasyFlasher :
The proces stop at the line :
"
........
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
"
Nothing else, only a blinking cursor on the next line.
The tablet displays "Entering NvFlash recorery mode / Nv3p server
Chip Uid 037...
"
And then nothing appends. (I have waitted about 30 minutes)
Perharps it's a hardware issue :/
Are you running the flashing program as Admin? (Right click > Run as Administrator)
And which version of Windows are you running?
Ive found 32bit Windows 7 to have best compatibility for this sorta thing
I have tried this (as admin, W7 32-bit) and it runs through creating all 15 partitions, then formatting all 15 partitions, the tablet screen shows the Chip UID and then nothing else happens.
I have left it for over an hour and still nothing. The cmd window just shows Formatting Partition 15 Done! and the tablet screen remains the same.
Turn off tablet, and then still won't turn on in anything other than APX mode.
Ideas?
toweliechaos said:
I have tried this (as admin, W7 32-bit) and it runs through creating all 15 partitions, then formatting all 15 partitions, the tablet screen shows the Chip UID and then nothing else happens.
I have left it for over an hour and still nothing. The cmd window just shows Formatting Partition 15 Done! and the tablet screen remains the same.
Turn off tablet, and then still won't turn on in anything other than APX mode.
Ideas?
Click to expand...
Click to collapse
Hmm, I know it does take a long time using NVFLASH, but you should see the progress bar after the partition sections have finished it starts sending the files across, there is one partition that takes a super long time to complete though
Have you tried a different machine ?
Maybe set it going and leave it overnight in case it manages to complete whatever it's getting stuck on
*Detection* said:
Hmm, I know it does take a long time using NVFLASH, but you should see the progress bar after the partition sections have finished it starts sending the files across, there is one partition that takes a super long time to complete though
Have you tried a different machine ?
Maybe set it going and leave it overnight in case it manages to complete whatever it's getting stuck on
Click to expand...
Click to collapse
I tried EasyFlasher and left it running for hours and hours (when I previously thought it was stuck at partition 10) and it coompleted - but with no change in behaviour.
I then tried NVFlash again and left it over night - again the same result. Everything seems to 'work' in that it completes without errors but still the tablet won't turn on in anything other than APX mode.
I have tried to get the device registered as an ADB device and after spending a long time yesterday upgrading the SDK tools, I managed to get it showing in Device Manager as an ADB device and working correctly. However, running adb.exe I still cannot get it to 'show' as a device, even after running adb kill-server and adb start-server. I always get "error: device not found".
This is so frustrating as the device is clearly turning on and off but I can't seem to get it to be anything other than an APX mode.
A shot in the dark, but have you checked to see if the Volume Up button is stuck in ?
That would make it boot in APX mode each time
Quite simple to take the plastic bezel surround off and get to the micro switch under the volume rocker, just 2 screws near the port, then use a plastic flat thing to unclip the bezel
*Detection* said:
A shot in the dark, but have you checked to see if the Volume Up button is stuck in ?
That would make it boot in APX mode each time
Quite simple to take the plastic bezel surround off and get to the micro switch under the volume rocker, just 2 screws near the port, then use a plastic flat thing to unclip the bezel
Click to expand...
Click to collapse
Tried that, as expected the buttons are fine. Nothing stuck, all operating as it should.
Currently sitting in a semi-morgue state (the tablet, not me) with me having run out of ideas...
:crying:
No further suggestions?
It seems a waste to let this one die when it surely must be salvageable?
*Detection* said:
Have you tried just a straight forward NVFLASH ROM ?
(...) (I can't post the link .. it doesn't matter anyway) (...)
The ROMs linked above will return your tablet to 100% Stock so you would need to root and flash custom recovery afterwards, but it would determine whether or not it is a hardware fault or just a bad luck combination of your custom ROM / Recovery
Just extract the NVFLASH ROM, enter APX Mode, plug the tablet into the PC and run the .bat file to flash, once it reboots it should be 100% stock
Click to expand...
Click to collapse
Hi. I'm quite new here (in fact, this is my first post).
I've had an ASUS TF101 for a while now. I haven't used it in a while, and i believe that caused the batery to fully drain - as a result, i couldn't get it even to re-charge with the wall charger, much less to boot. I am now trying to revive it, so have been doing some research on the net, and reached as far here. I am able to connect it in APX mode, and tried running nvflash as above indicated (following the later posted correct link). However the bootloader doesn't seem to want to initialize. Below is what I've gotten:
C:\Users\Miguel Dias Pinheiro\Desktop\NVFLASH_ICS_9.2.1.27_WW_NOROOT>cd C:\Users
\Miguel Dias Pinheiro\Desktop\NVFLASH_ICS_9.2.1.27_WW_NOROOT\
C:\Users\Miguel Dias Pinheiro\Desktop\NVFLASH_ICS_9.2.1.27_WW_NOROOT>"nvflash.ex
e" --bct transformer.bct --setbct --configfile flash.cfg --create --bl blob.EBT
--odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x0388924041ff3457
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 2
device config fuse: 0
sdram config strap: 0
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: blob.EBT
| 1454712/1454712 bytes sent
blob.EBT sent successfully
waiting for bootloader to initialize
And that's it, it has been like this for about one hour now - is it normal to take this long.
By the way, the tablet screen is all black, nothing on it.
Can someone help me beyond this? Thanks!
Any help will be appreciated.
Had a Galaxy 10.1 that was dead. Read every possible tutorial I could get my hands on.
THEN THIS WORKED:
Downloaded Nvlfash
Connected my device
Ran the following commands:
nvflash --bl bootloader.bin --go
nvflash --resume --download 8 recovery-cwm_4.0.0.4-sam-tab-10.1.img
And magic, the device made the familiar Samsung jingle and started up. <---I THOUGHT PROBLEMS SOLVED, I'm a genius.
The device works perfect, but the moment I power it off, it's dead, wont power back on. Have to repeat the above process and that starts the device up again. Can't get into down/recovery mode etc...the above process is the only way I can get the device powered on.
Any advice for a newbie, what should I do after starting up with Nvflash to get the device to power off and on like normal again?