Guys, i have a slight problem here. I want to install a custom rom on my dell streak. The guide that i am following is from Benny's blog (http://leemn.wordpress.com/2011/02/...from-eclair-2-1-build-6941-to-stephens-1-5-1/)
What I've done:
1. Installed Android SDK (Updated the given updates, as in the screenshot. SCREENSHOT
2. Installed Dell's Windows Drivers from here (ftp://ftp.dell.com/Handheld/R288920.exe)
3. Installed Dell Mobile Sync
4. Downloaded the Fastboot tool from here (http://download143.mediafire.com/pcxqstv8scfg/yd21znuyj14/1.8.1.7-streak-clockworkrecovery.zip) , Renamed the fastboot-windows.exe to fastboot.exe .
5. Downloaded SteakDroid 1.9.0 and renamed it to Update.zip and copied it to the root of my SD card.
6. Downloaded the current version of the baseband as recomended.
7. Made a folder in C drive named Streak and extracted the clockworkrecovery.zip there. Copied the baseband into the same folder as well.
I believe these steps were all correct.
Now however, i am stuck .
8. After my streak is in the FASTBOOT_MODE , waiting for the usb connection, i connected the USB cable to my computer.
9. It said that a new device Android 1.0 has been found.
10. I choose to choose the drivers by my own, and The only drivers that were available is Android ADB interface and Android Composite ADB interface. If i were to click show compatible hardware, then only the Android ADB interface driver would be shown. SCREENSHOT
11. If i were to choose any 2, the drivers would install fine, and FASTBOOT_MODE would show up in my streak.
12. I entered into the commandline (run > cmd) and went to the C:\streak directory. Once i ran the command, fastboot devices, nothing is listed. When i ran the command fastboot reboot, all it says is waiting for device and that is it. SCREENSHOT
I tried this on a second computer, and its the same thing. I believe i should see the "ANDROID BOOTLOADER INTERFACE" driver, to proceed with the flashing. SCREENSHOT
However, i am not seeing such options on both computers, that are running Windows XP SP3.
What should i do?
It happened to me with my XP machine, no matter what I did, bootloader driver wont show up.
Ended up using a win 7 one with no problem installing the driver.
And "fastboot devices" command doesn't work for me no matter what i tried.
I would suggest you try "fastboot -i 0x413c reboot" w/o the quotes. If your streak reboots, that means fastboot it's working and you can go on with the flashing, e.g.
fastboot -i 0x413c flash recovery recovery.img
fastboot -i 0x413c flash dsp1 dsp1.mbn
fastboot -i 0x413c flash amss amss.mbn
etc.
"fastboot devices" wasted hours of my life without realizing fastboot is already working....
PS: one get around of NOT having a win 7 machine is to install pdanet program(google it). It will install the necessary drivers to get you started, just test with "fastboot -i 0x413c reboot" to see if your fastboot is working
PPS: NEVER do any erase with fastboot like fastboot -w or any sort, it will brick it... guarantee
asianftw said:
It happened to me with my XP machine, no matter what I did, bootloader driver wont show up.
Ended up using a win 7 one with no problem installing the driver.
And "fastboot devices" command doesn't work for me no matter what i tried.
I would suggest you try "fastboot -i 0x413c reboot" w/o the quotes. If your streak reboots, that means fastboot it's working and you can go on with the flashing, e.g.
fastboot -i 0x413c flash recovery recovery.img
fastboot -i 0x413c flash dsp1 dsp1.mbn
fastboot -i 0x413c flash amss amss.mbn
etc.
"fastboot devices" wasted hours of my life without realizing fastboot is already working....
PS: one get around of NOT having a win 7 machine is to install pdanet program(google it). It will install the necessary drivers to get you started, just test with "fastboot -i 0x413c reboot" to see if your fastboot is working
PPS: NEVER do any erase with fastboot like fastboot -w or any sort, it will brick it... guarantee
Click to expand...
Click to collapse
I tried installing PDA NET but it still installed with the same ADB drivers.
However, the command "fastboot -i 0x413c reboot" reboots the streak! So i shall try the flash
Edit:
Got everything working as in the steps, right until the update.zip part.
However, i ran into some error.
Here it is:
Steps followed:
Switch off the phone
Boot the phone into recovery mode by holding vol up + vol down + power simultaneously
You will see a black screen with white writing (vol buttons are up/down, camera button is enter/ok)
Select* ”Software upgrade via Update.pkg on SD Card”
You will now be on a black screen with green writing
Select* ”apply sdcard:update.zip”
Scroll* down to “Yes – Install /sdcard/update.zip)
This will load and install the update
Click to expand...
Click to collapse
Mine would say
Fotmatting System
Copying Files...
Creating Symlinks
Creating Some More Symlinks
Last Lot OF Symlinks Being Created
Setting Permissions
Kernel:Installing
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Then it would reboot the device after awhile, and i'll be back to the normal 2.2.2.
This is a screenshot of the error screen: SCREENSHOT
EDIT!! SOLVED MY ISSUE!! ITS FLASHED NOW!!
Quote from someone who guided me on a different forum. Thanks to him!!
1 - u need to install CWM via fastboot
2 - press on 2nd option will bring u to another new menu ...... if it start to install from update , means u failed ..... After installing CWM , DO NOT reboot into your ori 2.2 or else the CWM will get replaced by original recovery . Which means once u install the CWM , key in " -fastboot -0x413c reboot " and hold the 2 volume button while it reboot ..... it will take u to recovery straight after restart
3 - Choose option ( 2 ) which u bring to u to CWM
4 - Select Steven's zip file from there ....option 4 i think , cant remember correctly which is " install zip from sdcard "
Click to expand...
Click to collapse
arvin2212 said:
I tried installing PDA NET but it still installed with the same ADB drivers.
However, the command "fastboot -i 0x413c reboot" reboots the streak! So i shall try the flash
Edit:
Got everything working as in the steps, right until the update.zip part.
However, i ran into some error.
Here it is:
Steps followed:
Mine would say
Fotmatting System
Copying Files...
Creating Symlinks
Creating Some More Symlinks
Last Lot OF Symlinks Being Created
Setting Permissions
Kernel:Installing
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Then it would reboot the device after awhile, and i'll be back to the normal 2.2.2.
This is a screenshot of the error screen: SCREENSHOT
EDIT!! SOLVED MY ISSUE!! ITS FLASHED NOW!!
Quote from someone who guided me on a different forum. Thanks to him!!
Click to expand...
Click to collapse
Glad to hear Clockworkmod works for you!
Clockwork mod working
Yeah, I wasn't able to get the Clockwork mod to work for me, I kept getting a message about "E:can't find MISC:" and it would hang up from there. Would get the same message if I tried to do a nandroid backup also. So I installed Streakmod and my problems were solved. BTW I had to use a Windows XP computer to get my Streak flashed, none of my 3 W7 laptops would act right, pretty sure it was a driver problem but I was able to resolve it on those.
Another question while I am here, anyone know what has to be done to keep the Streak from random reboots????
cdzo72 said:
Yeah, I wasn't able to get the Clockwork mod to work for me, I kept getting a message about "E:can't find MISC:" and it would hang up from there. Would get the same message if I tried to do a nandroid backup also. So I installed Streakmod and my problems were solved. BTW I had to use a Windows XP computer to get my Streak flashed, none of my 3 W7 laptops would act right, pretty sure it was a driver problem but I was able to resolve it on those.
Another question while I am here, anyone know what has to be done to keep the Streak from random reboots????
Click to expand...
Click to collapse
Did you do a full factory reset?
Did you use the clear cache / dalvik cache option from the cwm menu?
I have done all those and have not had any random reboots.
**Just so you know, i've never experienced any random reboots with the streak.
Random reboots
Well I honestly think my problem has more to do with the battery cover than anything else.
Phone wise my streak doesn't lag, doesn't hang up. I can't remember the last time I got some type of error message from having to force close a program, thus taking that into consideration, I would be hard pressed to believe that I have a problem with my installation or maintenance.
I read somewhere about a fix for the battery compartment slide cover, but it's been a week now and I haven't been able to come across it again. Hoping someone else has seen it and can point me there.
cdzo72 said:
Well I honestly think my problem has more to do with the battery cover than anything else.
Phone wise my streak doesn't lag, doesn't hang up. I can't remember the last time I got some type of error message from having to force close a program, thus taking that into consideration, I would be hard pressed to believe that I have a problem with my installation or maintenance.
I read somewhere about a fix for the battery compartment slide cover, but it's been a week now and I haven't been able to come across it again. Hoping someone else has seen it and can point me there.
Click to expand...
Click to collapse
I believe i've read somewhere that the older versions of the streakdroid roms <1.9.1 has the sensors disabled for rebooting once the cover is loose. Try that
Related
Hi. I need to return my Dell Streak to O2, due to a fault that has developed with the speaker. Ie. when I make calls, I can't hear other people, but they can hear me. Calls work perfectly from speakerphone mode.
I have upgraded to 2.1, and thought that it would be a good idea to return it to a stock rom, before i return it under warrenty.
So, first of all, I copied the stock rom to the SD card, and called it Update.pkg, then tried to "update from Update.pkg" but it fails, saying that the sysem is up to date.
So i followed the thread, about using fastboot and then recover to 1.6 ( http://forum.xda-developers.com/showthread.php?t=752769 )
however, when i run the fastboot (as admin command prompt) it just says <waiting for device> even though the phone is connected to the computer in fastboot mode.
Any Ideas?
Regards, Dave
use fastboot -i 0x413c rest of command
Same Result
Thanks for the reply.
check the drivers (in windows) you may need to manually update them
Download the Dell PC Suite from support.euro.dell DOT com/support/downloads/driverslist.aspx?c=uk&cs=ukdhs1&l=en&s=dhs&ServiceTag=&SystemID=TBLT_STRK&os=ANDGL&osl=en&catid=&impid= and install. Download this folder www DOT mediafire DOT com/?yd21znuyj14 and unzip to the root drive i.e. c:\ and call it something like streak so you can navigate to c:\streak. Open up the new streak folder and find the fastboot application for your operating system and rename it to fastboot (leave the .exe file extension as it is). Put your Streak into Fastboot mode by powering on while holding the camera button. It will show a screen that says ‘Touch Calibration’ and ‘Fastboot’. Tap fastboot. You will now see ‘Wait for USB FastBoot detect....’. Connect your USB. The screen should display ‘FASTBOOT_MODE’. If not then try this. Go to device manager. You should see an errored item called Android 1.0. Right click Android 1.0, select Update Driver Software, select Browse my computer, select Let me pick, select All Hardware, scroll down to Google INC, select Bootloader and click OK.
what to do, if this happens on a mac? Still get only "< waiting for device >" in the terminal. With my N1 it was easier...
Thanks fards! This command worked when I was stuck at 'waiting for device'
I have bricked or atleast semi bricked my Folio and i dont know if it can be fixed. It began with damaged internal sd, so i try the format zip but no luck. May device have been like this 3 days now. I NEED HELP, AND YES I HAVE ASKED IN GENERAL SECTION. but i didnt get an answer for days. I need help by someone who can tell me how to set up fastboot. My folio boots i can get to clockwork recovery and i can get in to fastboot mode. I have working ADB on my computer. The install fails when recovery is writing boot.img iget this message: assert failed
write_raw_image("/cache/boot.img", "linux")
E:Error in /sdcard/FolioMod.zip
(Status 7)
It installs system.img fine. So i was thinking i could fastboot boot.img to the device and maybe it boots. So i put Folio in Fastboot mode,insert usb, and update driver, go to command prompt and write fastboot devices all i get is:
? fastboot
Is there anything special i have to keep in mind to setup fastboot for Folio. I used the fastboot that came with SDK. Do i have to add something more to .inf file for fastboot? Do have to use any special fastboot just for Tegra2 devices? Is my fastboot mode damaged? Please i need help i have waited for days in general section not one answer. Hoping on better luck here in the dev section
Are you on Windows or linux?
Normally if adb is working, fastboot should be working too. Just boot your folio into fastboot mode and connect it to your pc. Type 'fastboot devices', if something shows up you are fine (might be just a bunch of ???s).
Otherwise (on win) you need to modify the driver a little. There is a howto around here. I will add a link when I found it.
€: http://www.addictivetips.com/mobile/enable-adb-usb-drivers-for-nvidia-tegra-based-android-tablets/
But I think if adb is already working, you will be fine. Just make sure you have a recent version of fastboot from the android sdk. Older versions are incompatible with tegra2 based devices.
mblaster said:
Are you on Windows or linux?
Normally if adb is working, fastboot should be working too. Just boot your folio into fastboot mode and connect it to your pc. Type 'fastboot devices', if something shows up you are fine (might be just a bunch of ???s).
Otherwise (on win) you need to modify the driver a little. There is a howto around here. I will add a link when I found it.
€: http://www.addictivetips.com/mobile/enable-adb-usb-drivers-for-nvidia-tegra-based-android-tablets/
But I think if adb is already working, you will be fine. Just make sure you have a recent version of fastboot from the android sdk. Older versions are incompatible with tegra2 based devices.
Click to expand...
Click to collapse
I had entered the part to .inf file but havent done the echo part in command prompt, will try now. Its weird as hell all i get when writing fastboot devices is a ? fastboot. Its a windows Vista 32 im using and SDK 08. And when i enter this echo 0x955 i just get that its the wrong path.
I got fastboot working didnt know it could be ? fastboot when it was connected. I kept getting it so i tryed to send some commands and it got thru. **** so i have had it working for days. I have flashed the boot.img via fastboot and am now trying to do an advanced restore of a nandroid. Will see how it goes. If its not working can i flash system.img and boot.img? Will that work? Well atleast now i can flash standard recovery and send it to toshiba
Probleem Solved Thank you mblaster, you wrote it could look like this when writing fastboot devices: ?????? or atleast something like it so i thought maybe i am connected as my said: ? fastboot . So i tryed some commands and they got thru. So to anyone who tryes to install fastboot try commands. I was waiting for days(dumb, i know). So now im back and kickin, watch out
Moved to proper forum
Ok so I wanted to try out some new Tom's besides the cm7 weeklies and figured I should do a deeper wipe than just the normal cwm wipe but I can't seem to figure put how to get fastboot working I set it up on my phone and navigated to the file ln my laptop and just issued a reboot so I knew how it worked before I started wiping but it just sat there and never rebooted I have is there additional files I need besides the fastboot exe to do a wipe. And is it advised to erase all the partitions before flashing a new rom or is it not needed
Sent from my MB860 using XDA App
I don't know for sure so I'll just tell you what I have in my folder where I have my fastboot.exe. I also have the adb files which include:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
Not sure if that means anything though. Have you updated your drivers recently? What OS does your laptop use? I know if you have the wrong drivers it can cause problems like using 32 bit drivers on a 64 bit system.
As far as wiping, it is recommended especially if you go from a different ROM to another. I usually use this which was suggested by a user named @CaelanT:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
jonnyboyC13 said:
Ok so I wanted to try out some new Tom's besides the cm7 weeklies and figured I should do a deeper wipe than just the normal cwm wipe but I can't seem to figure put how to get fastboot working I set it up on my phone and navigated to the file ln my laptop and just issued a reboot so I knew how it worked before I started wiping but it just sat there and never rebooted I have is there additional files I need besides the fastboot exe to do a wipe. And is it advised to erase all the partitions before flashing a new rom or is it not needed
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Well just updated motohelper and no luck still no response in fastboot maybe my procedure is wrong in what way do you wipe
Sent from my MB860 using XDA App
ok learning process. didn't even realize you needed adb to use fastboot. so i got that on my laptop.
adb isn't recognizing my phone either so i think i'm still missing something
Right now i know i have the motohelper install adb and and the fastboot files. I may have some other files when i first got my phone that just installed with it was still blurred but i don't know
Do you have "USB Debugging" checked when using adb?
How did you unlock the bootloader? It seems weird that it's not working since you need an unlocked bootloader to run CM7 (which you said you had) and you need fastboot to unlock the bootloader. I don't understand what could have changed since then. Are you using a different computer now?
Just to make sure we're on the same page, are you putting the phone into fastboot before you issue the fastboot commands?
[Turn off phone->Hold Vol down and press power->Keep holding Vol down until it says "Fastboot" at the top of the screen->Release Vol down and then press Vol up]
jonnyboyC13 said:
ok learning process. didn't even realize you needed adb to use fastboot. so i got that on my laptop.
adb isn't recognizing my phone either so i think i'm still missing something
Right now i know i have the motohelper install adb and and the fastboot files. I may have some other files when i first got my phone that just installed with it was still blurred but i don't know
Click to expand...
Click to collapse
Yep usb debugging is on
honestly i don't know why it's not working it just says waiting for device, all i need to do is just put into fastboot on my phone, navigate to the fastboot.exe on the command promt. Then plug in in the phone and issues the command correct. are there any other things that need to be running to get it working. is there another step before this for the computer to recognize my phone
There are only 2 things I can think of after the details you have given me:
1. Are you making sure it says "Starting fastboot protocol" at the top of the screen before you issue the commands?
and
2. Have you rechecked your drivers? To me this sounds like the issue if everything else is in place. Try plugging the phone into your computer while it's turned on and switching the "USB Connection" from "None" to "Windows Media" then to "Mass Storage" and finally "Phone Portal", making sure you allow it to install any proper drivers on each connection (takes a few seconds). It's also important to select OK each time you change the connection.
Also, did you get the correct adb files in the same folder as fastboot.exe?
Other than these 2 suggestions I don't know what could be causing the issue. At this point I would be seeking help myself.
jonnyboyC13 said:
Yep usb debugging is on
honestly i don't know why it's not working it just says waiting for device, all i need to do is just put into fastboot on my phone, navigate to the fastboot.exe on the command promt. Then plug in in the phone and issues the command correct. are there any other things that need to be running to get it working. is there another step before this for the computer to recognize my phone
Click to expand...
Click to collapse
ok did some more searching it is the driver just have to figure out what i need to get on my computer now
Ok haven't wiped yet but i got the right driver on my computer now adb now can discover my device and a did a fastboot reboot and it worked cool beans.
just in case anyone else is having a similar problem i had to download the MOTODEV usb driver here http://developer.motorola.com/docstools/USB_Drivers/ and yes had to sign up for MOTODEV to do it but whatever got it working and i'm pumped
Not quite sure what has gone wrong with my tablet but it seems that my recovery partition has been wiped (no recovery) and my boot.img has also gone.
What caused it:
I was installing Ubuntu onto my Prime and I got to the stage where I flash the boot.img. However, fastboot said it was sending the file, then writing the file and reported both "<OKAY>". However, I am not receiving a blue bar as other people say they do, yet I have done before when following the NVFlash guide (yes, I have all my blobs and things backed up).
Anyway, I have tried installing the Universal Driver and it seems to work (shows up in Device Manager). However, any commands that I send to the tablet do not seem to work (fastboot FLASH COMMANDS).
Commands I've entered: fastboot -i 0x0b05 flash boot prime-sdlinux.blob, fastboot -i 0x0b05 flash recovery twrp.blob
Also, "commands such as fastboot -i 0x0b05 erase recovery" result in: erasing 'recovery' ... FAILED (command write failed (Unknown error))
I'm really stuck and it's getting late, not sure what to do. Hope you guys can help me out.
PS: Not sure if this helps but, I cannot turn off the device. It constantly reboots just to hang at the Asus Eee Pad Screen or to hang at the Fastboot screen (when volume_down is held).
EDIT: After troubleshooting some more I have found that uninstalling the naked driver and letting Windows find a driver will actually allow me to send a reboot command (and it'll work). However, any fastboot flash commands do not seem to work. No Progress Bar appears and any commands sent after a flash command do not work (can't reboot after sending a flash command).
Hold the volume up while pressing the power button for about 15 seconds or until it vibrates then release them and it should power off for you.
did you make an nvflash backup?
else try
Code:
downloaded the latest Virtuous Prime ROM.
extract the ZIP file and pull the file called 'blob'
rename the file as boot.blob and move it to the TOOLS folder and open Command Prompt
from the TOOLS folder, type: fastboot -i 0x0b05 flash boot boot.blob
then type: fastboot -i 0x0b05 reboot
this should make you capable to go to recovery again
Open a command prompt; type adb push virtuous_prime.....zip /sdcard/
Wait until you get a confirmation message
Flash the rom like you normally do
Done
found this solution somewhere....
I do have an NVFlash backup, just not with me right now. Will test the above method first. And thanks for the method of turning it off! Although I know it's still on. Just in APX mode.
EDIT: Windows XP (run through VirtualBox on my laptop) seems to pickup my tablet in fastboot devices now. However, I'm still not seeing a progress bar after flashing again, and have the same problems as before (cannot reboot from fastboot). Still doesn't work. I've run fastboot through a native Windows 7 machine and a Windows XP installation on a Mac. Not sure what else I can try if fastboot isn't working.
EDIT2: It seems that I no longer have the error "FAILED (command write failed (Unknown error))" with certain commands.
First, you are in the wrong section, it should be in Q&A.
Second why didn't you try nvflash?
See this: http://forum.xda-developers.com/showpost.php?p=29204285&postcount=228
I believe the reason why fastboot is not working is because you are flashing blobs whilst using AndroidRoot.mobi bootloader.
http://forum.xda-developers.com/showpost.php?p=28875606&postcount=80
I believe you'll have to blobunpack the blob and then flash the raw img files instead.
That actually makes perfect sense! Would have taken me ages to figure out by myself. Thought it was perm-bricked until I got back to my NVFlash backup files. Will try it out.
kokopuphz said:
I believe the reason why fastboot is not working is because you are flashing blobs whilst using AndroidRoot.mobi bootloader.
http://forum.xda-developers.com/showpost.php?p=28875606&postcount=80
I believe you'll have to blobunpack the blob and then flash the raw img files instead.
Click to expand...
Click to collapse
I was in a similar situation until someone pointed me in this direction. Using BlobUnpack on both recovery and boot images gives you boot.LNX.SOS and Recovery.img.SOS (or similar names)
Flashing these solved my issues.
Yea, it worked. Thanks a lot for the help guys. Just takes one extra step to flash something now, kinda annoying, but definitely worth knowing that your tablet is brick-proof.
hi
i have a issue similar to this thread http://forum.xda-developers.com/forumdisplay.php?f=1465, but just want to confirm
i have a CWM and CM10.1 installed previously but no nvflash,
but during a recently flash i accidently formatted the "system" partition.
I now can no longer boot past the asus logo unfortunately,
and tried the following
1) i can boot into CWM but it only allow flashing from /mnt/sdcard and i dont have any rom in /mnt/sdcard (wiped)
2) i can boot into fastboot (PWR+DWN) and i installed the naked driver v0.72 and it show in device manager -- however "fastboot.exe devices" show nothing
3) if i normal boot (ie stuck on "Eee Pad logo) and install some form of "ADB interface" driver, then i can "adb.exe devices" into it -- but i can push anything onto /mnt/sdard (permission denied)
4) "adb shell" wont work bc of missing "system/bin/sh" hence i cant re-root
5) i can go into APX mode (PWR+UP), but it is not nvflashed sadly
6) i have tried 2 usb cables already, so hopefully not it
Is there anything i can do ... or it is bricked and have to send back to asus for service ?
thanks in advance !
jojo665 said:
hi
i have a issue similar to this thread http://forum.xda-developers.com/forumdisplay.php?f=1465, but just want to confirm
i have a CWM and CM10.1 installed previously but no nvflash,
but during a recently flash i accidently formatted the "system" partition.
I now can no longer boot past the asus logo unfortunately,
and tried the following
1) i can boot into CWM but it only allow flashing from /mnt/sdcard and i dont have any rom in /mnt/sdcard (wiped)
2) i can boot into fastboot (PWR+DWN) and i installed the naked driver v0.72 and it show in device manager -- however "fastboot.exe devices" show nothing
3) if i normal boot (ie stuck on "Eee Pad logo) and install some form of "ADB interface" driver, then i can "adb.exe devices" into it -- but i can push anything onto /mnt/sdard (permission denied)
4) "adb shell" wont work bc of missing "system/bin/sh" hence i cant re-root
5) i can go into APX mode (PWR+UP), but it is not nvflashed sadly
6) i have tried 2 usb cables already, so hopefully not it
Is there anything i can do ... or it is bricked and have to send back to asus for service ?
thanks in advance !
Click to expand...
Click to collapse
First of all try adb push Name_of_Rom.zip /sdcard/
If that does not work try adb push Name_of_Rom.zip /system/media/
If that still does not work then download the correct TWRP blob file from the following link for your bootloader. http://www.teamw.in/project/twrp2/93
The fact that you are on CWM and was using CM 10 makes me believe that you are still on the ICS bootloader but to make 100 percent sure when you first power on the device look at where the "NVIDIA" logo is. If it is bottom center it is ICS, if it is bottom right it is Jellybean. (MAKE SURE YOU GET THE CORRECT TWRP VERSION FOR YOUR BOOTLOADER)
Now rename the blob file you downloaded to twrp.blob. Go into fastboot and type the following.
fastboot -i 0x0b05 flash recovery twrp.blob
This should install TWRP which will allow you to install a rom off an external micro sd.
turn out it is windows problem -- fastboot device driver (Naked 7.1) is installed but wont connect to the tablet. I ended up installing Ubuntu in order to get fastboot to work.
Once fastboot is working, i able to follow above advice and get my tablet back to functional state.... thanks!
ps: now time for nvflash :laugh:
jojo665 said:
turn out it is windows problem -- fastboot device driver (Naked 7.1) is installed but wont connect to the tablet. I ended up installing Ubuntu in order to get fastboot to work.
Once fastboot is working, i able to follow above advice and get my tablet back to functional state.... thanks!
ps: now time for nvflash :laugh:
Click to expand...
Click to collapse
What exactly did you do? I'm trying to extinguish all avenues before I have to RMA my tablet. Thanks for the help!