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.
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
Hello,
I was playing around with the Mi A1 magisk and i was flashing it. But then i by accident pressed lock bootloader (and confirming because i did not payed attention to what it was saying) and now the phone is BRICKED :crying: Only thing i get is the connect sound when connected to PC, but the phone shows NOTHING , just black and vibrates when i hold power and any other button. (no fastboot or recovery)
I think it is done for :crying: which hurts me to say cuz i got it as gift.
I think it will be expensive to fix in service center..
PLEASE HELP IF YOU CAN AS FAST AS POSSIBLE
Thanks in advance.
Same happened to me. Did you change anything with tools? did you erase partitions? what exactly thing were you doing to brick it? only press the lock cant brickt it. Normally you can just re-unlock it and flash with the stockrom. Just give us more information about the process you were doing
Actually i booted TWRP by mohacm flashed Magisk then i powered off the phone and than it happend. When it locked i turned it on and showed the colorfull bar and Mi logo for split second and turned off every single time. After re-unlocking it was in bootloop so i tried to restore with Mi Flash tool and it showed error at the end (something wrong with partition b flash) So i tried again and it froze so i turned the tool off and it put it the state it is now.
Also the response of the phone happens only when plugged to PC
You've bricked nothing at all, just chill. I suppose you've installed all the drivers for the A1 while installing the Mi Flash if yes then install minimal adb and fastboot tool, paste all the files from the images folder from the firmware file to the directory of the minimal adb and fastboot tool, open cmdhere.exe located in minimal adb and fastboot tool folder, boot you phone into fastboot mode(press and hold volume down and power buttons at the same time till fastboot bot appears), plug the phone to the pc, enter the following commands:
- fastboot devices (You should see your device's serial tex next to fastboot text if you see nothing, install fastboot drivers properly)
- fastboot flash modem_a modem.img
- fastboot flash modem_b modem.img
- fastboot flash sbl1 sbl1.img
- fastboot flash sbl1back sbl1.img
- fastboot flash rpm rpm.img
- fastboot flash rpmbak rpm.img
- fastboot flash tz tz.img
- fastboot flash tzback tz.img
- fastboot flash devcfg devcfg.img
- fastboot flash devcfgback devcfg.img
- fastboot flash dsp adspso.bin
- fastboot flash sec sec.dat
- fastboot flash splash splash.img
- fastboot flash misc misc.img
- fastboot flash aboot emmc_appsboot.mbn
- fastboot flash abootbak emmc_appsboot.mbn
- fastboot flash boot_a boot.img
- fastboot flash boot_b boot.img
- fastboot flash system_a system.img
- fastboot flash system_b system.img
- fastboot flash lksecapp lksecapp.img
- fastboot flash lksecappbak lksecapp.img
- fastboot flash cmnlib cmnlib.img
- fastboot flash cmnlibbak cmnlib.img
- fastboot flash cmnlib64 cmnlib64.img
- fastboot flash cmnlib64bak cmnlib64.img
- fastboot flash keymaster keymaster.img
- fastboot flash keymasterbak keymaster.img
- fastboot flash userdata userdata.img
- fastboot reboot
Done!
But the problem is that i cannot boot into fastboot. The phone doesent respond to any actions. I was writing it on the top of the thread. If could boot into fastboot then i would use Mi tool again.
Also when the phone is connected to the PC and i hold the Power and volume buttons (up or down doesent matter) nothng happens just the PC does the dis and connect sounds
try hold volume and and down and then connect to pc after that hold power button volume +,- in the same time then wait 6sec . check if ur phone detect on devie manager port
The PC CAN detect the phone. The problem is not in PC but in the phone cuz it wont boot or show NOTHING on the screen whatsoever.
The PC recognizes it as Qualcomm HS-USB Diagnostics 900E (COM3)
AND you're dumb enough to not mention that. If so buy a cheap type-c cable that works on your phone, make it a deep flash cable(search on youtube how to make it) and flash the stock rom using it, that's my best bet.
dont get how someone can mess up the bootloader. i think in 10 years of my phonelife the bootloader menu never bugged.
Ok guys,
Thanks to everyone who helped my phone Is Back alive thx to Xiaomi Service center.
Ocasionally (approximately 1 out of 10 times) when I reboot my phone, I end up in the bootloader.
Whatever I do, I cannot reboot my phone at that point.
It looks like the boot_a or boot_b get corrupted ocasionally.
Then only thing which then helps is to do:
Code:
fastboot flash boot_a boot.img
fastboot reboot
Anybody has experience this? Any idea what might be causing it?
It happend both when I reboot my phone normally or when I do "adb reboot" from a command shell.
I am rooted, running beta4, but I debloated beta4 a bit.
I did some further experiments:
Make sure that both _a and _b partitions are exactly the same.
When the problem happens, I can do:
fastboot set_active a ... or
fastboot sec_active b
then:
fastboot continue
and the phone will boot normally. I checked the boot_a and boot_b and the are the same; so the boot_a/b partition is not corrupted.
But it seems the device has "lost" its active_slot ... for some weird reason.
Hi all,
This is a long shot, I hope there is someone somewhere that can help with this issue. I know it's a fairly old phone now, but if anyone has any knowledge about android recovery, it would be greatly appreciated!
Version: OxygenOS 3.6.1.
Rooted via Magisk and Bootloader Unlocked years ago.
The problem was unexpected. It was suffering battery drains for the past month, and last night, whilst on charge, I noticed it restarted. And now it's stuck on the OnePlus LOGO Screen. D:
I can only access FASTBOOT and NOT RECOVERY mode.
What I've tried:
MSM RECOVERY TOOL (w/ QCOM drivers)
Installing ABD Interface Drivers to try an ADB Sideload (but can't get to recovery)
Fastboot flashing stock and TWRP recoveries (can't boot into it - error dtb not found).
Fastboot flash_Ox211.cmd *
Spoiler: * flash_Ox211.cmd does the following
Code:
rem adb reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
rem fastboot erase recovery
rem fastboot flash recovery unofficial_twrp_2.8.7.0-bacon.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash sdi sdi.mbn
fastboot flash pmic pmic.mbn
fastboot flash hyp hyp.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oem_stanvbk static_nvbk.bin
rem fastboot flash userdata userdata_64g.img
pause
rem fastboot reboot
None of the above has worked or has fixed recovery mode.
I want to keep my userdata. Is it possible to access that partition, and/or somehow do an 'adb backup'. It might be impossible without the recovery
To keep documenting my findings on extra things that I have done or will do.
Reseating the battery
I have drained the battery and taken the battery connection out the phone for an hour.
UPDATE: After re-plugging, and putting it into charge, the phone bootloops now instead of staying stuck on the OnePlus/Android LOGO continuously. NO CHARGING INDICATOR.
Replacing the battery
If it's a battery issue, then a replacement might work. I have ordered one.
UDPATE: TBD
Fastboot Flashing other recovery img's
dtb not found (or device tree blob) - was an issue when I tried booting into a flashed recovery (stock or TWRP). According to some forum posts, it may be due to flashing the wrong recovery version on the device.
UPDATE:
stock []
twrp-2.8.7.0-oneplus2 [] - no dtb error
twrp-3.0.0-1-oneplus2 []
twrp-3.0.2-1-oneplus2 []
twrp-3.2.1-0-oneplus2 []
...
↑ Doing a fastboot boot <recovery>.img bootloops the phone.
Try asking in the op2family discord server, there are some pretty knowledgeable ppl there. Also you could try asking _undead, he's the one who made lineage 19.1 for op2, see in Original Android Development on this forum.
Huh, it sounds like you're having a similar issue as me. Except I can access recovery but not fastboot... and sideloading isn't working for me.