last week,I sent a topic,The link here
http://forum.xda-developers.com/showthread.php?p=19779397
Now,I got zhe special cable into fastboot,
I try to enter a few commands
1. fastboot -i 0x1949 flash boot boot.img
2. fastboot -i 0x1949 flash recovery recovery.img
3. fastboot -i 0x1949 -w
4. fastboot -i 0x1949 boot boot.img
fire reboot, Next pic,i'm load to here,anyboby can help me ?
http://forum.xda-developers.com/attachment.php?attachmentid=802066&stc=1&d=1322807775
Error effect:
MOUNT /CACHE Failure
http://forum.xda-developers.com/attachment.php?attachmentid=802068&stc=1&d=1322807775
/backup/backup_userdata.zip Short of
http://forum.xda-developers.com/attachment.php?attachmentid=802067&stc=1&d=1322807775
anyboby can help me ?
Well for start the picture quality is really really poor and I can't read a thing.
I made a mistake that when I do the following commands:
Code:
unzip fbmode.zip
adb push fbmode /data/local/fbmode
adb shell chmod 755 /data/local/fbmode
adb shell /data/local/fbmode
adb reboot
But i forgot to copy the TWRP 2.0.img to the device.
Now KF stuck in the fbmode, i can not get out of it. Anyone know the command to get out of fbmode, I did try fastboot -i 0x1949 reboot but it always boot to fbmode.
Thank you.
*************
I try the command
Code:
fastboot -i 0x1949 oem idme bootmode 5002m
then my KF has boot into normal mode.
Problem solve. Search button win )
Code:
fastboot -i 0x1949 oem idme bootmode 4000
That should do it.
If you are trying to install it, just run...
Code:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
u copy twrp to your fastboot folder not your kf, than do fastboot boot twrp2.0.img or whatever u have it named.
Sent from my HTC Glacier using xda premium
smirkis said:
u copy twrp to your fastboot folder not your kf, than do fastboot boot twrp2.0.img or whatever u have it named.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I did copy to my fastboot folder in my PC but didnt work, I think the correct way its copy into device root folder.
It took me almost 3 days of constantly trying to unbrick my tablet, so I thought I would post a quick guide of how I ended up doing it.
I only had Fastboot access.. (No ADB, nothing else...) due to my Recovery and Bootloader being corrupted and a failed NVflash installation. Nevertheless, I then proceeded to try hundreds of different things (flashing a straight up blob would not work no matter how many times I tried).
I finally found a solution, I downloaded the oldest blob I could find (and through a lot of work finding a compiler, compiled a BlobExtractor) I then found the bootloader and flashed it using the command.
fastboot -i 0x0b05 flash bootloader bootloader.bin
This got me to a state where I was able to flash a new Stock ASUS JB blob with
fastboot -i 0x0b05 flash system blob
This should restore it completely.
Hope this saves someone a ton of time and money... I will attach the bootloader.bin (as I frankly could not find ANY stock/custom bootloaders for this tablet ANYWHERE)
No Guarantees, but if your soft-bricked with conditions like above... might as well give it a try. :good:
not work!
damn'it again the bootloader is unrecoverable (Error is "Unrecoverable bootloader error (0x000000)") and system not start. However thank you!!! :good:
riderskull said:
damn'it again the bootloader is unrecoverable (Error is "Unrecoverable bootloader error (0x000000)") and system not start. However thank you!!! :good:
Click to expand...
Click to collapse
Were you actually able to over-write the bootloader in the first place? This may be a stupid question, but did you extract the bootloader.bin from the Rar? Note that this is a 9.4.3.30 bootloader, so actually booting with this isn't going to be possible for some but it will setup fastboot conditions enough where you can push in stock blob.
I used a JB 10.6.1.8 blob afterwards.
You may also try flashing the stock recovery file (along side the bootloader)
I'll try to help out more if I can...
I was getting InvalidSize errors when trying to flash a blob on the AndroidRoot bootloader.
iamsobored said:
Were you actually able to over-write the bootloader in the first place? This may be a stupid question, but did you extract the bootloader.bin from the Rar? Note that this is a 9.4.3.30 bootloader, so actually booting with this isn't going to be possible for some but it will setup fastboot conditions enough where you can push in stock blob.
I used a JB 10.6.1.8 blob afterwards.
You may also try flashing the stock recovery file (along side the bootloader)
I'll try to help out more if I can...
I was getting InvalidSize errors when trying to flash a blob on the AndroidRoot bootloader.
Click to expand...
Click to collapse
I extract the bootloader.bin my current versione of bootloader is (if i don't make error) : 1.00e. Released by "WW_epad-10.6.1.8-20130225" A03
How do I know if I am able to overwrite the bootloader ?
riderskull said:
I extract the bootloader.bin my current versione of bootloader is (if i don't make error) : 1.00e. Released by "WW_epad-10.6.1.8-20130225" A03
How do I know if I am able to overwrite the bootloader ?
Click to expand...
Click to collapse
hmm... it did not overwrite then.... you extracted the bin then put it in your folder with fastboot...then ran the command i gave? what output did fastboot give?
I tried flashing this, but my fastboot screen just freezes. Have to manually hold down power to reset, once reset is done I get
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\System32>cd C:\android\sdk\platform-tools
C:\android\sdk\platform-tools>adb reboot-bootloader
(Have to do this to get to bootloader screen, I have infinite bootloop to recovery which has SD mount errors and everything)
C:\android\sdk\platform-tools>fastboot -i 0x0b05 flash bootloader bootloader.bin
sending 'bootloader' (1002 KB)...
(Stuck like this until I reset)
FAILED (data transfer failure (Too many links))
finished. total time: 73.202s
(after manual reset since screen freezes, I let it sit for like 4 minutes since its only a 1002kb file)
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
Also, I have no attached devices under ADB Devices, installed all the right drivers. But its okay, I have new motherboard coming in, just experimenting with this one.
pyovue - If you have ADB access then unbricking it should be easy as you can push and edit any file on the system with it as well as fastboot? Or can ADB & Fastboot not mount (not just the sdcard) anything? If you don't care what happens to your tablet MB, then try this....
fastboot -i 0x0b05 erase system
fastboot -i 0x0b05 erase recovery
Then reboot (this should rid you of your bootloop to recovery and nothing should start)
Then download the stock ASUS Rom (from ASUS, look under Firmware)
Then try sending it with fastboot -i 0x0b05 flash system blob (you will have to extract two zips from the firmware files until you get to a file called "blob" then put it in your fastboot)
I almost guarantee if you have fastboot/adb working there is ALWAYS a way to fix it... only a hardbrick is impossible to fix.
That won't work for people who bricked their tabs with wrong recoveries. They can't use fastboot..
iamsobored said:
pyovue - If you have ADB access then unbricking it should be easy as you can push and edit any file on the system with it as well as fastboot? Or can ADB & Fastboot not mount (not just the sdcard) anything? If you don't care what happens to your tablet MB, then try this....
fastboot -i 0x0b05 erase system
fastboot -i 0x0b05 erase recovery
Then reboot (this should rid you of your bootloop to recovery and nothing should start)
Then download the stock ASUS Rom (from ASUS, look under Firmware)
Then try sending it with fastboot -i 0x0b05 flash system blob (you will have to extract two zips from the firmware files until you get to a file called "blob" then put it in your fastboot)
I almost guarantee if you have fastboot/adb working there is ALWAYS a way to fix it... only a hardbrick is impossible to fix.
Click to expand...
Click to collapse
Yeah, as soon as I use
fastboot -i 0x0b05 flash system blob
The bootloader screen freezes, longest I had it up was 20mins, and battery died, will try again too see if theres any results. Using any type of adb push or pull or even checking the sdcard's directory cant be allowed cause of no adb devices attached.
I duno if im hard bricked, or soft. When I had CWM 6.0.1.3, I couldnt mount anything. So I used
fastboot -i 0x0b05 erase system
fastboot -i 0x0b05 erase recovery
fastboot -i 0x0B05 erase userdata
fastboot -i 0x0B05 erase boot
They were all successful, through adb, and my recovery is now gone. So it boots straight to the white Asus logo screen(Not the flashy animated one), and freezes there. I can hold down while reset to get to bootloader. Flashing stock blob file now, ill post results later, gona leave it on for at least 1 hour. tehehe.
pyovue said:
Yeah, as soon as I use
fastboot -i 0x0b05 flash system blob
The bootloader screen freezes, longest I had it up was 20mins, and battery died, will try again too see if theres any results. Using any type of adb push or pull or even checking the sdcard's directory cant be allowed cause of no adb devices attached.
I duno if im hard bricked, or soft. When I had CWM 6.0.1.3, I couldnt mount anything. So I used
fastboot -i 0x0b05 erase system
fastboot -i 0x0b05 erase recovery
fastboot -i 0x0B05 erase userdata
fastboot -i 0x0B05 erase boot
They were all successful, through adb, and my recovery is now gone. So it boots straight to the white Asus logo screen(Not the flashy animated one), and freezes there. I can hold down while reset to get to bootloader. Flashing stock blob file now, ill post results later, gona leave it on for at least 1 hour. tehehe.
Click to expand...
Click to collapse
Welp, no go. It seems to erase files okay, but not writing files. Oh well. New motherboard will be here tomorrow.
pyovue said:
I tried flashing this, but my fastboot screen just freezes. Have to manually hold down power to reset, once reset is done I get
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\System32>cd C:\android\sdk\platform-tools
C:\android\sdk\platform-tools>adb reboot-bootloader
(Have to do this to get to bootloader screen, I have infinite bootloop to recovery which has SD mount errors and everything)
C:\android\sdk\platform-tools>fastboot -i 0x0b05 flash bootloader bootloader.bin
sending 'bootloader' (1002 KB)...
(Stuck like this until I reset)
FAILED (data transfer failure (Too many links))
finished. total time: 73.202s
(after manual reset since screen freezes, I let it sit for like 4 minutes since its only a 1002kb file)
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
Also, I have no attached devices under ADB Devices, installed all the right drivers. But its okay, I have new motherboard coming in, just experimenting with this one.
Click to expand...
Click to collapse
I'm having a very similar issue, except I'm able to get a "successful" fastboot return from my command prompt. I can only access the bootloader by running "adb reboot-bootloader" My bootloader menu also freezes once the write portion of fastboot starts. I've tried re-loading CWM and loading up TWRP. Everything I've tried always just boots to CWM. My SDCard fails to mount (I can mount manually) and I'm getting "Can't mount /cache/..." errors in CWM. I haven't braved the deletion of the recovery since CWM is all I can get in to.
Any suggestions? Am I out of luck?
after give it
Code:
fastboot reboot
, in the terminal i have this response
Code:
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
rebooting...
and tablet is freeze. Any solution ?
riderskull said:
after give it
Code:
fastboot reboot
, in the terminal i have this response
Code:
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
rebooting...
and tablet is freeze. Any solution ?
Click to expand...
Click to collapse
yeah, happens to me too
matt95 said:
yeah, happens to me too
Click to expand...
Click to collapse
Same sort of problem is with me......:crying: any solution please!!!!!!!
I have exactly the same problem and I tried every hint from xdadevelopers.
I hope some one can help us to reanimate our TF300T. I would be very grateful for any information.
I tried the following ...
Code:
fastboot -i 0x0B05 erase cache
fastboot -i 0x0B05 erase userdata
fastboot -i 0x0b05 erase system
fastboot -i 0x0b05 erase recovery
fastboot -i 0x0B05 erase boot
fastboot -i 0x0B05 reboot-bootloader
fastboot -i 0x0b05 flash system blob
... and then my TF300 freeze.
just a friendly bump, though i'm looking into my warranty now...would be great if there was a way to use fastboot to turn off secure/encryption stuff and to make sure its unlocked...our possible way to re-partition...don't even know if that would be helpful...
iamsobored said:
I finally found a solution, I downloaded the oldest blob I could find (and through a lot of work finding a compiler, compiled a BlobExtractor) I then found the bootloader and flashed it using the command.
Click to expand...
Click to collapse
What blob extractor did you use?
---------- Post added at 08:32 PM ---------- Previous post was at 08:05 PM ----------
Nevermind, it was BlobTools.
Everyone please note you will be flashing an ICS bootloader!!!
If you are not on ICS or have Nvflash installed you may wish to blobunpack your own JB bootloader using blobtools.
Please read the OP carefully to see if this truly applies to your tablet.
I will place proper links to blobtools when I'm not on my tablet.
forum.xda-developers.com/showpost.php?p=35208962&postcount=14
When attempting to flash the bootloader I get a FileReadFailed.
When attempting to flash the system it gets stuck sending system. I have left it alone for over 2hrs with no change.
Any ideas?
I can't wait to get home and try this
Sent from my SCH-I535 using xda app-developers app
Since the demise of cyanogen support for the Zuk Z1, Is there an archive where I can download the original CM-12 that shipped with the device?
sidd607 said:
Since the demise of cyanogen support for the Zuk Z1, Is there an archive where I can download the original CM-12 that shipped with the device?
Click to expand...
Click to collapse
There was several signed CM 12.1 images for Z1, I downloaded 2 versions when CM website was up: drive.google.com/ drive/folders/0BzpTRW4SbjMqWVJ5SktOdTZ5RlU?usp=sharing
tradiz said:
There was several signed CM 12.1 images for Z1, I downloaded 2 versions when CM website was up: drive.google.com/ drive/folders/0BzpTRW4SbjMqWVJ5SktOdTZ5RlU?usp=sharing
Click to expand...
Click to collapse
The link gives a 404 error
sidd607 said:
The link gives a 404 error
Click to expand...
Click to collapse
Remove space in the link when copypasting - i don't have enough posts for URL's.
https://download.cyanogenmod.org/
Not exactly sure if it shows- "This application is temporarily over its serving quota. Please try again later.", but I did download the stock ROM over here a few weeks ago. Might work after a few hours, keep a lookout.
Here you go
sidd607 said:
Since the demise of cyanogen support for the Zuk Z1, Is there an archive where I can download the original CM-12 that shipped with the device?
Click to expand...
Click to collapse
This is the version i have used. Its latest and it is fastboot install so you will need to have a computer to flash this.
Make new folder on Desktop
Extract the contents of Cynogen rom as well as attached zip file to the new folder
Make sure you have installed the drivers.
https://www.androidfilehost.com/?w=files&flid=159156
Use these commands (One at a time) or Simply run the flash.bat file attached to the post
fastboot -i 0x2b4c flash modem NON-HLOS.bin
fastboot -i 0x2b4c flash sbl1 sbl1.mbn
fastboot -i 0x2b4c flash dbi sdi.mbn
fastboot -i 0x2b4c flash aboot emmc_appsboot.mbn
fastboot -i 0x2b4c flash rpm rpm.mbn
fastboot -i 0x2b4c flash splash splash.img
fastboot -i 0x2b4c flash tz tz.mbn
fastboot -i 0x2b4c flash boot boot.img
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c flash -S 512M system system.img
fastboot -i 0x2b4c flash persist persist.img
fastboot -i 0x2b4c flash cache cache.img
fastboot -i 0x2b4c flash userdata userdata_64G.img
fastboot -i 0x2b4c reboot
Edit 1:
Please edit flash.bat for lines
fastboot -i 0x2b4c flash recovery twrp-3.0.2-0-Z1.img
to
fastboot -i 0x2b4c flash recovery recovery.img
Edit 2:
Download link updated
@sidd607
https://www.androidfilehost.com/?w=files&flid=159156
@[email protected]
The URL you posted needs permission to download.
Got this working with Lineage ok but decided to go back to stock. I downloaded the stock recovery rom from NV and set everything up. Inside the recovery bundle is a bat file. Usually I would flash all files manually but this time I used the bat file. It manged the first 3 or 4 commands then came up with error. The box is now stuck in a boot loop and I am unable to access over adb.
Can anyone please suggest a way around this.
Thanks
Here is the bat file
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash dtb mdarcy.dtb.img
fastboot flash vbmeta vbmeta.img
fastboot oem lock (optional step: required for certain functionality)
fastboot reboot
EDIT:
Eventually managed to flash lineage zip again. Used USB keyboard to access recovery
may i ask, what kind of keyboard did u use?
thanks in advance