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
Related
On my Atrix 4G, I can't get the fastboot to work. I have installed the latest drivers for windows and created the rules files in linux and for both operating systems when I try to run fastboot I just get a <waiting for device>. Can anyone help me with this problem?
enderx1 said:
On my Atrix 4G, I can't get the fastboot to work. I have installed the latest drivers for windows and created the rules files in linux and for both operating systems when I try to run fastboot I just get a <waiting for device>. Can anyone help me with this problem?
Click to expand...
Click to collapse
That happen to me. All i did was put the phone in fastboot mode and it connect right away. Press volumn down button while powering on the phone. When the screen said Fastboot, then you press up on the volumn button.
I'd suggest trying to run "fastboot devices" before any other commands, just to verify that you have connected to the phone successfully. If you don't get any response from the "fastboot devices" command, you've still got an issue. For my money, the probable sources are lack of drivers, or phone isn't in fastboot mode.
the piont is how to do?
I have the phone in fastboot mode, and fastboot devices returns nothing. Where would I get the correct drivers? I believe I have the correct ones, for windows that is. For linux I have configured the rules.d files as well.
Hi,
Use moto-fastboot, you can find links in the dev section from -eval and others, it will detect the device, also it supports large partitions, unlike the regular fast boot binary you might find via Google. If you do a lsusb and it shows an nvidia entry, you are good to go on the phone side.
Cheers!
Hi,
I have been searching the forums for it, and I have not been able to find the moto-fastboot binary. Could you link to it?
http://forum.xda-developers.com/showthread.php?t=1138092
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.
I let my cousin borrow my prime while I went out of town for a few days and when I came back my tablet was completely wiped. All that it has on it is fastboot and fastboot only has two options wipe data or usb. My tablet won't show up in adb but when I use fastboot devices command I get 00000 fastboot. I don't know if fastboot is seeing my tablet or not I'm just hoping I can fix it. After taking with people in other forums I've been trying this method
http://forum.xda-developers.com/showthread.php?p=27354963&highlight=fastboot#post27354963
It seems to work until I get to where I have to flash Roach's modded CWM recovery. After inputting the command this is the result I get.
sending 'recovery' (5398 KB)... FAILED (command write failed (Unknown error)) finished
Does anyone here have any idea what's happening with my prime? If so please help, it will be very much appreciated.
Well, first I would make sure my PC recognizes my TPrime using "devices" command in ADB. If not, remove/uninstall any previous TPrime drivers and install Naked drivers. After that, test by using "devices" command again in ADB. After that, you can begin to utilize ADB and Fastboot commands. Also, I'd stay away from CWM and go with TWRP.
Sent from my Transformer Prime TF201 using Tapatalk 2
Second option, tell your cousin he owes you 500 bucks, go buy a new prime or infinity and give him the one he broke.
Skitsofrantik said:
I let my cousin borrow my prime while I went out of town for a few days and when I came back my tablet was completely wiped. All that it has on it is fastboot and fastboot only has two options wipe data or usb. My tablet won't show up in adb but when I use fastboot devices command I get 00000 fastboot. I don't know if fastboot is seeing my tablet or not I'm just hoping I can fix it. After taking with people in other forums I've been trying this method
http://forum.xda-developers.com/showthread.php?p=27354963&highlight=fastboot#post27354963
It seems to work until I get to where I have to flash Roach's modded CWM recovery. After inputting the command this is the result I get.
sending 'recovery' (5398 KB)... FAILED (command write failed (Unknown error)) finished
Does anyone here have any idea what's happening with my prime? If so please help, it will be very much appreciated.
Click to expand...
Click to collapse
it is highly unlikely it is bricked for good, you could try running through the steps to enable nvflash, and at the final step rather than booting into android (which you cant) run fastboot boot recovery
I've tried that but thanks for the input
SOTK said:
Well, first I would make sure my PC recognizes my TPrime using "devices" command in ADB. If not, remove/uninstall any previous TPrime drivers and install Naked drivers. After that, test by using "devices" command again in ADB. After that, you can begin to utilize ADB and Fastboot commands. Also, I'd stay away from CWM and go with TWRP.
I've tried every driver I could find. I just can't get it to show up in adb devices. going through fastboot seems to work though when i use the command for fastboot to reboot the tablet it reboots. I think I will try TWRP though.
Click to expand...
Click to collapse
lilstevie said:
it is highly unlikely it is bricked for good, you could try running through the steps to enable nvflash, and at the final step rather than booting into android (which you cant) run fastboot boot recovery
Click to expand...
Click to collapse
I'm gonna try this. Thanks for the tip.
Skitsofrantik said:
SOTK said:
Well, first I would make sure my PC recognizes my TPrime using "devices" command in ADB. If not, remove/uninstall any previous TPrime drivers and install Naked drivers. After that, test by using "devices" command again in ADB. After that, you can begin to utilize ADB and Fastboot commands. Also, I'd stay away from CWM and go with TWRP.
I've tried every driver I could find. I just can't get it to show up in adb devices. going through fastboot seems to work though when i use the command for fastboot to reboot the tablet it reboots. I think I will try TWRP though.
Click to expand...
Click to collapse
At one time, I had issues getting my PC to recognize my Prime too. You need to completely remove all prior device drivers and THEN install the naked drivers. There's a tutorial in that thread as well as a tool (I think) which you can run on your PC to help you remove previous drivers. Once you know they are gone, follow the directions to install the naked drivers. Its a little cumbersome but the process works. You're gonna keep having issues until you get your PC to recognize your Prime in ADB and Fastboot. You say Fastboot works kinda? So, in the device manager in Windows, it shows your Prime is connected as you're in Fastboot mode? If it doesn't or if it shows as an unrecognized device, I don't see how you're gonna be able to fix your issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Tried NVFlash
I tried NVFlash but I can't get past the first step. When I do this command fastboot -i 0x0b05 flash staging ebtblob.bin I get this result:
sending 'staging' (998 KB)...
OKAY [0.962s]
writing 'staging'...
FAILED (unknown status code)
finished. total time: 10970.597s
Anyone know what's going wrong?
SOTK said:
Skitsofrantik said:
At one time, I had issues getting my PC to recognize my Prime too. You need to completely remove all prior device drivers and THEN install the naked drivers. There's a tutorial in that thread as well as a tool (I think) which you can run on your PC to help you remove previous drivers. Once you know they are gone, follow the directions to install the naked drivers. Its a little cumbersome but the process works. You're gonna keep having issues until you get your PC to recognize your Prime in ADB and Fastboot. You say Fastboot works kinda? So, in the device manager in Windows, it shows your Prime is connected as you're in Fastboot mode? If it doesn't or if it shows as an unrecognized device, I don't see how you're gonna be able to fix your issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Where is the tutorial and tool? I went through it and didn't see it. Even when I completely remove the drivers, when I plug the tablet into the computer when there are no drivers it tries to install it's own drivers and sometimes they install and I get Asus android device in the device manager with Asus fastboot interface as the driver. other times it just fails to install drivers. I know if I get the drivers right I can limp this tablet back to life but it just seems like no matter what drivers i use i just cant get the tablet to show up in adb.
Click to expand...
Click to collapse
Skitsofrantik said:
SOTK said:
Where is the tutorial and tool? I went through it and didn't see it. Even when I completely remove the drivers, when I plug the tablet into the computer when there are no drivers it tries to install it's own drivers and sometimes they install and I get Asus android device in the device manager with Asus fastboot interface as the driver. other times it just fails to install drivers. I know if I get the drivers right I can limp this tablet back to life but it just seems like no matter what drivers i use i just cant get the tablet to show up in adb.
Click to expand...
Click to collapse
If you go into device manager and rightclick the asus android device then update drivers. Now do not let windows choose, do it manually and point windows to the naked driver... Also there are 2 drivers.. one for intel 86 and the other for amd... 64 the numbers are at the end of the file name if I remember correctly... be sure to choose the correct one for your pc chip otherwise yeah you can do it all day and get no where... When you try adb, I will assume you are in recovery mode and not fastboot because they are 2 different horses... If you only have fastboot then you should consider installing an older version of twrp like 2.1... I posted it somewhere in here.... that should get you into recovery where you can adb a rom to the prime.... check for posts by me, I have explained this a few times here.....
From a previous post.....
go here ....http://forum.xda-developers.com/show....php?t=1615990 this is twrp.... download then follow the fastboot install instructions
At this point you probably want to follow the nvflash instructions to install the custom bootloader since twrp says it needs it... go back here and follow instructions... http://forum.xda-developers.com/show....php?t=1774352
start again from ******now boot to recovery....
From the sounds of it you have no rom atm... no big deal... download a rom.. i suggest blackbean or eos...
blackbean found here... http://rootzwiki.com/index.php?/topi...ackbean-(8-15)
eos found here.. http://forum.xda-developers.com/show....php?t=1782413
Download and install http://forum.xda-developers.com/show....php?t=1426502 naked drivers.... follow the instructions...
I prefer blackbean... anyways.... now download nvflash from here http://androidroot.mobi/?p=452
Unzip the file.. put your rom where you find adb.exe shoudl be in C:\nvflash\tf201_nvflashpack if you put the file in C:
*******Now.... boot to recovery... connect tab to the pc.... with the windows open (nvflashpack) clcik in the window... press and hold shift button the right clcik mouse and select open command prompt here... this should give you the command prompt.
Now copy this adb devices right click in the command prompt window and paste... press enter... you should see your transformer...
now type adb push /name of rom you downloaded .zip/ sdcard
This should push the rom to your tab... it will take about 5 minutes be patient....
Install the zip through cwm....
After you accomplish this, you should complete the nvflash instructions and make your backups...
Click to expand...
Click to collapse
I installed R3 rom but my wifi cant be turned on. Latest I found that also my USB internet passthrough is not working. I got hint from one member but I absolutely dont know how to perform this.
flash the boot.img inside the R3's zip file using fastboot.
Commands:
fastboot erase cache
fastboot flash boot boot.img
How to flash something inside zip file? do I have to extract it and put it into root?
How to execute commands at all? Where to put them? What do I need to perform? I am total noob and every simple step I ever done took me a day. Now I am stuck. IF someone knows how to make this, please help.
Thank you.
First question do you have ADB installed?
Then you need to unpack boot.img from rom.zip.
When I get my answer we'll go further.
nlooooo said:
First question do you have ADB installed?
Then you need to unpack boot.img from rom.zip.
When I get my answer we'll go further.
Click to expand...
Click to collapse
I should have ADB, because I was rooting my phone month ago and ADB was required. How do I find out? I have SDK tools and i have adb.exe, adbwinapi.dll, fastboot.exe, recovery.img in C\Android. Actually I was trying to connect phone through USB and start adb.exe but it just popped out, scrolled down fast and closed (it was looking like command prompt- black window).
And I unpacked boot.img from R3.zip to my sdcard
Copy boot.img to android folder (where you have SDK platform tools installed), reboot phone to fastboot, connect it to PC and issue commands:
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase cache
And then reboot your phone.
Copy boot.img to android folder (where you have SDK platform tools installed), reboot phone to fastboot, connect it to PC and issue commands:
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase cache
And then reboot your phone.
Actually I tought this is the way, but let me tell you what is happening:
1.Turned phone off
2.entered fastboot on my phone
3.opened adb.exe in my Android-sdk/platform-tools folder
4.the adb window just opened for a 1second, everything scrolled down fast
5.adb window closed.
This is the reason why I need help, but really thank you for taking care
janickonajkrajsi said:
Copy boot.img to android folder (where you have SDK platform tools installed), reboot phone to fastboot, connect it to PC and issue commands:
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase cache
And then reboot your phone.
Actually I tought this is the way, but let me tell you what is happening:
1.Turned phone off
2.entered fastboot on my phone
3.opened adb.exe in my Android-sdk/platform-tools folder
4.the adb window just opened for a 1second, everything scrolled down fast
5.adb window closed.
This is the reason why I need help, but really thank you for taking care
Click to expand...
Click to collapse
You shouldn't click the adb. exe, open cmd and type the commands there.
Sent from my awesome fridge
I'm just wandering how did you manage to unlock bootloader at all.
MaartenXDA said:
You shouldn't click the adb. exe, open cmd and type the commands there.
Sent from my awesome fridge
Click to expand...
Click to collapse
yeah, I also did this according to this post http://forum.xda-developers.com/showthread.php?t=1752270
and this post http://forum.xda-developers.com/showthread.php?t=860421
but Cmd could not recognize this. I tried "fastboot devices" and this was not recognized too.
Then I reinstalled HTC drivers and then tried again. So then I was trying to open adb.exe and then you told me to issue command through cmd and here we are. sorry I am real noob in android things. I was using iphone and everything worked like magic
Isnt there a way to perform this "boot.img flashing" through recovery mod? I mean without the usb connection and without the cmd black hole
janickonajkrajsi said:
yeah, I also did this according to this post http://forum.xda-developers.com/showthread.php?t=1752270
and this post http://forum.xda-developers.com/showthread.php?t=860421
but Cmd could not recognize this. I tried "fastboot devices" and this was not recognized too.
Then I reinstalled HTC drivers and then tried again. So then I was trying to open adb.exe and then you told me to issue command through cmd and here we are. sorry I am real noob in android things. I was using iphone and everything worked like magic
Click to expand...
Click to collapse
First use the command "cd C:\Android"
After that do the commands again.
Be sure you've uninstalled HTC Sync (NOT the drivers) before doing this.
Sent from my awesome fridge
nlooooo said:
I'm just wandering how did you manage to unlock bootloader at all.
Click to expand...
Click to collapse
He didn't get your point...
Sent from my toaster using TapaToast HD
Thank you guys, now it is working.
Quote:
Originally Posted by nlooooo View Post
I'm just wandering how did you manage to unlock bootloader at all.
He didn't get your point...
Yeah it was meant like "hod did this stupid noob even managed to unlock bootloader at all. I got his point, and the right answer was "step by step guide" so actually You didnt got my point.
Dont forget that things that are automatic and obvious to you, are not obvious to everyone. My grandma is learning to work with computers and when she asks me how to send an email, I have to tell her "grab a mouse, then move it there........"
)))))))
Does not matter, thank you guys!
Once you learn to use adb and fastboot it's always the same, so my point was that you've never learned how to use it, you just typed what you saw, without any wish to learn.
Point is to try and learn, not to ask again.
Nobody said you're stupid, just lazy.
Cant get the R3 working. HTC Sense UI crashed error at lock screen
I flashed the sense revolution r3 today but could not get it working.
The following are the issues faced.
1) It starts without installing the mods package, but lacks the full sense widgets like htccontacts, htc calender etc.
2) when i flashed the r3 mod package, it gets stuck at the lock screen. The Sense UI crashes.
3) Without the mods, i faced another bug in people widget. it crashes when i click the phone dialer from it.
I am currently on sense r3.
Please help me install it in full.
Im trying to learn fastboot and adb sideload and adb overall commands.
I downloaded original rom for Asus z380c form Asus support site and as i read somewhere the difference between fastboot and adb was that fastboot cant do one function as adb can i cant remember which function it was (command, process) but as i understood fastboot was limited. Now im trying to flash Asus z380C through abd sideload but its impossible because z380c is in fastboot by default. Yes i tried atp or what is called asus flash tool. Its ok it flashes but z380 wont fully boot. I did almost everything. It seems that boot logo is stuck because i made it work to first installation windows language etc etc. set up. But i did it by chance plugging in usb and disconnection changing cable, power brick etc. So im not sure why there is a lag or bug delay in set up. I want to use adb or fastboot which ever in command prompt to install original rom from site but cmd or adb wont recognize installation. I tried many commands but it doesnt work. Tnx in advance if anyone can help me. Ah yes fastboot reads only img files but original rom from asus is in zip format and inside its standard view of system files. I need img files all of them like in mtk htc type of roms. so i can install rom from img files on fastboot.