So I installed ASUS 4.2.1 Build 10.6.1.15.3. I followed the instructions for installing the twrp.blob via fastboot. All of this worked.
Now when boot into recovery mode, TWRP sees no files. If you click the log on the upper right hand side, it's filled with errors like:
E:Unable to find partition size for '/misc'
E:Unable to find partition size for '/staging'
E:Unable to find partition size for '/data'
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/boot'
E:Unable to mount '/cache'
And so on... I cannot see the files that I have placed in the folders both for internal storage and for a 8GB Micro SD. I'm at a loss. At this point, I'm not even sure how to reflash the ASUS image so that I might start completely over, though I don't know why I'd want to. Any ideas?
I was having the same issue and this worked for me http://forum.xda-developers.com/showthread.php?t=1672108&page=76&nocache=1. its a couple of post down.
Sounds like you flashed a recovery with -JB at the end instead of -42. The -JB recoveries are for the 4.1 bootloader (OTA version 10.4.x). You are on the 4.2 bootloader (OTA version 10.6.x). ASUS changed a bunch of important filesystem stuff in the 4.2 bootloader. When you flashed the 4.1 recovery, it erased all your device nodes (the file representation of the hardware on the system, specifically where each filesystem partition resides), so as far as your recovery is concerned, you don't have any internal storage. That's why it can't open anything.
So far, nobody has been able to recover a tablet in this condition.
Also, this is the wrong section. This thread belongs in the Q&A section. It has nothing to do with development.
EndlessDissent said:
Sounds like you flashed a recovery with -JB at the end instead of -42. The -JB recoveries are for the 4.1 bootloader (OTA version 10.4.x). You are on the 4.2 bootloader (OTA version 10.6.x). ASUS changed a bunch of important filesystem stuff in the 4.2 bootloader. When you flashed the 4.1 recovery, it erased all your device nodes (the file representation of the hardware on the system, specifically where each filesystem partition resides), so as far as your recovery is concerned, you don't have any internal storage. That's why it can't open anything.
So far, nobody has been able to recover a tablet in this condition.
Also, this is the wrong section. This thread belongs in the Q&A section. It has nothing to do with development.
Click to expand...
Click to collapse
I used fastboot and rewrote the recovery with the "42" one and it fixed my issues.
Ah. I apologize for picking the wrong section. So there's no way to reflash my device via fastboot?
maddog94d said:
I used fastboot and rewrote the recovery with the "42" one and it fixed my issues.
Click to expand...
Click to collapse
Wow. Ok, let me give that a shot.
maddog94d said:
I used fastboot and rewrote the recovery with the "42" one and it fixed my issues.
Click to expand...
Click to collapse
That doesn't work for most people. Typically, the tablet freezes as soon as fastboot tries to write anything. The correct recovery can never be flashed. Maybe you got lucky. Maybe your situation was slightly different.
Also, the link you posted doesn't seem to lead to a post with any sort of guide. On my phone, in the XDA Premium app, it opens the last page of the TWRP thread, specifically to f69m's most recent post, in which he says that this situation has caused lots of bricks. Ironic, IMO.
sorry bout where the link lead to. it was on the last page explaining what happened. maybe i did get lucky, all i did was the same method for fastboot for the recovery install.
And it worked. Thanks for the head's up. Sorry again for choosing the wrong forum.
I didn't use the link. I just reflashed the 42 twrp using fastboot and it worked.
Glad it worked for you.... maybe 2 of us got lucky lol
maddog94d said:
sorry bout where the link lead to. it was on the last page explaining what happened. maybe i did get lucky, all i did was the same method for fastboot for the recovery install.
Click to expand...
Click to collapse
Other than one poor soul being told that his tablet might be bricked, there is nothing on that page dealing with the OP's problem. The other posts are about flashing a -42 recovery on the 10.6.1.8 OTA and having to update to the 10.6.1.15.3 OTA to fix it.
Edit: it seems like I'm trying to argue something. I'm not. I'm just confused about exactly where the link should have gone.
Also, maybe the fact that you and the OP are on the newest OTA made a difference. Almost everybody I've seen with that problem did it on the first 4.2 OTA. Maybe ASUS fixed something in the newest updates. The newest updates fixed custom recoveries in general, so it could have had other fixes, like for fastboot.
The real question now, is it safe to use custom ROM's on top of this 4.2.2 JB? I suddenly am worried about messing with it...
strakajagr said:
The real question now, is it safe to use custom ROM's on top of this 4.2.2 JB? I suddenly am worried about messing with it...
Click to expand...
Click to collapse
As long as you pay attention to which recovery you're using, there shouldn't be a big problem. That is, if you're positive that the fix worked. Have you made any backups or tried wiping cache/Dalvik? The recovery no longer gives you "can't mount" errors?
If it seems to be working properly, flashing ROMs shouldn't be an issue, but I don't blame you for being cautious. If in doubt, just stick to the stock ROM.
Right, I'm in business. I already used it to flash superuser, and then verified that I have root. Everything seems to be in order.
I'd been using 10.6.1.15.3, so maybe that's why this worked.
Same thing happened to me. It ended up being that i was on the older OS. I followed this thread to the T
http://forum.xda-developers.com/showthread.php?t=2187982
Works perfect!
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
Hi!
Also, here has been described the same situation, in the simplest way possible !
Good luck !
I don't have fastboot or adb available to use, am I out of luck?
Mine just boots into twrp every time. Cannot mount anything. No recovery available on boot. I just get the unlocked message in the top left corner on boot. I can't even stop the boot using the volume buttons. How can I get fastboot/adb back?
Hmmmm....
strakajagr said:
I didn't use the link. I just reflashed the 42 twrp using fastboot and it worked.
Click to expand...
Click to collapse
Two folks who "got lucky." Interesting.
Thread moved,
Please keep all questions to the Q&A section, the development section is for development threads only
Related
Hi all.
I found this look through the Kindle thread.
I didn't know it existed until now.
Check it out...looks interesting.
http://www.youtube.com/watch?feature...&v=xMdj_QzfGmw
http://teamw.in/project/twrp2
Naice! Just read about this on AndroidPolice but didn't see that video, nice to see it working right off the bat on a Gtab
wow neat! I wonder what android kernel version this is based of off...
fosser2 said:
wow neat! I wonder what android kernel version this is based of off...
Click to expand...
Click to collapse
Yeah..I bit the bullet and DL it and followed directions.
I couldn't boot into recovery.
It hangs at the birds.
Normal boot runs the underlying ROM fine though.
I'm on a 1.2BL. Was running a series of FB from 8.0 to 10.1 without NVFlashing.
I had only factory reset and wipe and booted into Beasty/Clem Ultimate as the latest ROM. (This FROYO is very fast and stable btw...)
Tried the TWRP 2.0 but couldn't get it to work either.
It's on the YT video though. Obviously it works
I wonder maybe they were on the 1.1 BL...
Anybody running 1.1BL confirm this recovery works?
qkster said:
I wonder maybe they were on the 1.1 BL...
Anybody running 1.1BL confirm this recovery works?
Click to expand...
Click to collapse
Works fine on the 1.1 bootloader.
rajeevvp said:
Works fine on the 1.1 bootloader.
Click to expand...
Click to collapse
Yup, confirmed by Jazzruby.
only for 1.1 BL.
JR did emailed TeamWin re: possible 1.2BL application
thanks..
how do you like it btw?
Looks like they just changed one of the 2 links...both were pointing to the same 1.1 file yesterday.
Now one points to twrp-harmony-12-2.0.0RC0.zip (1.2) & the other to twrp-harmony-11-2.0.0RC0.zip (1.1).
Al
aabbondanza said:
Looks like they just changed one of the 2 links...both were pointing to the same 1.1 file yesterday.
Now one points to twrp-harmony-12-2.0.0RC0.zip (1.2) & the other to twrp-harmony-11-2.0.0RC0.zip (1.1).
Al
Click to expand...
Click to collapse
will give it a try...thanks
fosser2 said:
I wonder what android kernel version this is based of off...
Click to expand...
Click to collapse
It's a (newly compiled) stock VS kernel for 1.1 and a clemsyn kernel for 1.2 bootloaders.
---------- Post added at 09:02 PM ---------- Previous post was at 08:45 PM ----------
qkster said:
JR did emailed TeamWin re: possible 1.2BL application
Click to expand...
Click to collapse
It's easy enough to insert a 1.2 kernel into any recovery partition since the both the boot and the recovery partition on the gTab has an identical structure (necessarily so).
1. Download any of pershoot's kernel zips.
2. Replace the kernel/zImage file in the zip file with either a stock 1.2 kernel from an existing recovery image (Or, just use pershoot's 1.2 kernel).
3. Edit META-INF/com/google/android/updater-script and
a) get rid of the lines involving /system
b) change the string "boot" to "recovery" in the first run_program() and the write_raw_image() directive.
4. Pack everything up into a zip file and then just flash it.
how do you like it btw?
Click to expand...
Click to collapse
Works as advertised.
Has anyone else gotten this to work? I flashed it and now I can't boot into recovery - my GTab just hangs at the three birds (with the message about the recovery key being pressed at the top left). I can boot into Flashback just fine, just not recovery. I'm on BL1.2, and I downloaded TWRP 2.0 for BL1.2 and followed the instructions.
timbck2 said:
Has anyone else gotten this to work? I flashed it and now I can't boot into recovery - my GTab just hangs at the three birds (with the message about the recovery key being pressed at the top left). I can boot into Flashback just fine, just not recovery. I'm on BL1.2, and I downloaded TWRP 2.0 for BL1.2 and followed the instructions.
Click to expand...
Click to collapse
This is a TWRP screwup. Both zip files have identical MD5/SHA1 checksums, which means that both have the same recovery image, and hence, the same kernel--ie. a 1.1 kernel.
This was the reason for my post, above.
rajeevvp said:
This is a TWRP screwup. Both zip files have identical MD5/SHA1 checksums, which means that both have the same recovery image, and hence, the same kernel--ie. a 1.1 kernel.
This was the reason for my post, above.
Click to expand...
Click to collapse
Ah, I see. Did they give any indication when you contacted them that they were going to fix this? I don't know how to replace the kernel in the recovery.img file myself (I can't seem to find anything that can extract or mount the .img file so I can modify it).
timbck2 said:
Did they give any indication when you contacted them that they were going to fix this?
Click to expand...
Click to collapse
Haven't contacted them--I'm running on a 1.1 bootloader, and, as I said, the problem is easy enough to fix on your own.
I don't know how to replace the kernel in the recovery.img file myself (I can't seem to find anything that can extract or mount the .img file so I can modify it).
Click to expand...
Click to collapse
You don't need any tools if you have a 1.2 kernel ready; otherwise you need the unpackbootimg program.
See post #9 and just use a pershoot 1.2 kernel.
I contacted them, and they say the zip downloads have been fixed. I checked, and the BL1.2 download has been updated. I can't try it until I get home this evening, but I will and I'll post the results.
Update: After NVflashing and then installing TWRP 2.0 from the new download, it works as advertised. Very nice! One thing I'm disappointed about is that it doesn't appear to recognize CWM backups.
Update #2: The next time I rebooted and tried to go into recovery, my GTab wouldn't boot again; it got stuck at the three birds image, and did NOT give me the message about the recovery key being pressed. Even worse, it refused to boot normally after this - essentially, it appears that TWRP soft-bricked my tablet. I'm NVflashing again and going back to CWM. Very disappointing.
timbck2 said:
I contacted them, and they say the zip downloads have been fixed. I checked, and the BL1.2 download has been updated. I can't try it until I get home this evening, but I will and I'll post the results.
Update: After NVflashing and then installing TWRP 2.0 from the new download, it works as advertised. Very nice! One thing I'm disappointed about is that it doesn't appear to recognize CWM backups.
Update #2: The next time I rebooted and tried to go into recovery, my GTab wouldn't boot again; it got stuck at the three birds image, and did NOT give me the message about the recovery key being pressed. Even worse, it refused to boot normally after this - essentially, it appears that TWRP soft-bricked my tablet. I'm NVflashing again and going back to CWM. Very disappointing.
Click to expand...
Click to collapse
Same here...
I had NVflashed back to 4349.
Comfirmed the stock 4349 worked.
Booted into cwm.
Wiped everything in cwm. Partition 4096 then back to 2048/0
Aplied the twrp update.
Booted into recovery.
TWRP 2 looks great. The menu and screen is responsive.
Tried wiping with it...looks good
I then flashed a rom with it...Beasty/Clem Ultimate to be exact.
Installation reported complete.
Booted up and...got the birds....nothing else...
Tried going back in recovery... recovery is also gone too...
Soft bricked...
Good thing I know how to nvflashed back to stock but for someone new to gtablet, twrp2 may be bad news.
I saw a few post with people having twrp2 installed...has anyone successfully install a rom with twrp?
I have gone total brick (no boot, no recovery) twice and both times TWRP2 was loaded. I can't prove it is the cause, but I never had that problem before even with heavy duty flashing of ROMs etc.
However, all you really need to do is clear the MSC partition.
Use the --getpartitiontable command in nvflash and figure out what your MSC partition is (mine was #7). Then grab a "stock image" and flash its MSC partition (look in the cfg file, usually 7 although my true blue stock was at 6) into partition 7 with --download.
That has fixed it with no data loss every time for me.
Meanwhile, I've gone back to cwm.
Oh, I should say that TWRP2 did work most of the time. But sometimes I would reboot and just hang permanently until MSC gets reflashed.
I liked it in general, although it looked on the internal SD and not external like the version of CWM I have does. Would be nice to either pick or have a 2nd version. But if it keeps corrupting MSC and hanging the box, it isn't worth the trouble. CWM is clunky but fine.
wd5gnr said:
However, all you really need to do is clear the MSC partition.
Use the --getpartitiontable command in nvflash and figure out what your MSC partition is (mine was #7). Then grab a "stock image" and flash its MSC partition (look in the cfg file, usually 7 although my true blue stock was at 6) into partition 7 with --download.
Click to expand...
Click to collapse
It's better to wipe it clean using the ``--format_partition'' flag to nvflash instead of relying on someone else's partition images.
I accidentally wiped my TF300 and now i cant even get it to go into bootloader, it just goes straight to TWRP. I'm know what i did wrong - causing the wipe- but now i cant get any img to apply to the tab. it will mount system but not cache or anything else. i cant change my recovery because i cant get to bootloader. Any ideas??
LancasterCI said:
I accidentally wiped my TF300 and now i cant even get it to go into bootloader, it just goes straight to TWRP. I'm know what i did wrong - causing the wipe- but now i cant get any img to apply to the tab. it will mount system but not cache or anything else. i cant change my recovery because i cant get to bootloader. Any ideas??
Click to expand...
Click to collapse
Dude... I could be wrong, but enjoy your paperweight.
You might have luck doing this. Go to Asus site and download the full image for your tablet based on SKU region. Extract it to get the blob file. Do you have fastboot setup? Turn off your tablet completely and turn it on my holding the vol down and power it should allow you to boot into fast boot. You can flash the image that way. By
> fastboot -i 0x0B05 flash system C:...\Path-to-blob\blob
> fastboot -i 0x0B05 reboot
LancasterCI said:
I accidentally wiped my TF300 and now i cant even get it to go into bootloader, it just goes straight to TWRP. I'm know what i did wrong - causing the wipe- but now i cant get any img to apply to the tab. it will mount system but not cache or anything else. i cant change my recovery because i cant get to bootloader. Any ideas??
Click to expand...
Click to collapse
If you were on JB download 10.4.2.20, unzip once and place the new zip on your external sdcard. If you were on ICS choose 9.4.3.30 unzip once and place the new zip on your external sdcard.
install zip with twrp.
Good Luck!
hmm
ok just to make sure i am looking for my correct SKU would it be JP or US i beleive the latter since i am in ths US, but i do want to make sure as to to make the problem worse
LancasterCI said:
ok just to make sure i am looking for my correct SKU would it be JP or US i beleive the latter since i am in ths US, but i do want to make sure as to to make the problem worse
Click to expand...
Click to collapse
If you have a US tablet then US.
more issues
So i have the correct Firmware matching SKU, but whe i go to flash i get the following error
E: unable to mount ' /data ' (tw_mount)
E: unable to mount ' /cache ' (tw_mount)
then is repeats but it dose verify the filesystems and partition sizes
Any other ideas. just but this but not sure if bricked is and excuse for a return
LancasterCI said:
So i have the correct Firmware matching SKU, but whe i go to flash i get the following error
E: unable to mount ' /data ' (tw_mount)
E: unable to mount ' /cache ' (tw_mount)
then is repeats but it dose verify the filesystems and partition sizes
Any other ideas. just but this but not sure if bricked is and excuse for a return
Click to expand...
Click to collapse
Were you on 4.2.1 prior to this or encrypted?
LancasterCI said:
So i have the correct Firmware matching SKU, but whe i go to flash i get the following error
E: unable to mount ' /data ' (tw_mount)
E: unable to mount ' /cache ' (tw_mount)
then is repeats but it dose verify the filesystems and partition sizes
Any other ideas. just but this but not sure if bricked is and excuse for a return
Click to expand...
Click to collapse
Don't use clockwork. Extract the zip until you see the blob file. Use fastboot to flash it. It is very easy to do. see my post above. Good luck
defiantj3 said:
Don't use clockwork. Extract the zip until you see the blob file. Use fastboot to flash it. It is very easy to do. see my post above. Good luck
Click to expand...
Click to collapse
OP can't access the bootloader menu so he can't access fastboot.
Thanks for trying.
tobdaryl said:
Were you on 4.2.1 prior to this or encrypted?
Click to expand...
Click to collapse
i did have the latest ota update i believe 4.2.1
LancasterCI said:
i did have the latest ota update i believe 4.2.1
Click to expand...
Click to collapse
I was afraid that was where we were going.
The good, bad, and the ugly.
I'm sorry to tell you that you will probably stuck here until we get the full firmware update from Asus. We are hoping it will drop this week.
I don't know how to help yet on 4.2.1.
Here is a thread you might want to subscribe to where people with your issue are gathering till a resolution is found.
I wish I had better news but the one good thing I can say is there are some devs watching the thread and preparing for the release.
Good Luck!
tobdaryl said:
I was afraid that was where we were going.
The good, bad, and the ugly.
I'm sorry to tell you that you will probably stuck here until we get the full firmware update from Asus. We are hoping it will drop this week.
I don't know how to help yet on 4.2.1.
Here is a thread you might want to subscribe to where people with your issue are gathering till a resolution is found.
I wish I had better news but the one good thing I can say is there are some devs watching the thread and preparing for the release.
Good Luck!
Click to expand...
Click to collapse
Well any idea exactly what happened or if it is even fixable??
LancasterCI said:
Well any idea exactly what happened or if it is even fixable??
Click to expand...
Click to collapse
We think it has to do with encryption of your tablet when updating to 4.2.1 and the effects are not removed by downgrading.
update-binary also changed with 4.2.1 and we are looking into the changes as they need to be known to create zips for flashing. Other changes as well.
4.2.1 appears to encrypt by default; I think it is done to enable multi-user to restrict access to any other account.
Sorry I forgot fixable. Yes I believe once the update drops it will be resolved. That is why I provided the link.
tobdaryl said:
We think it has to do with encryption of your tablet when updating to 4.2.1 and the effects are not removed by downgrading.
update-binary also changed with 4.2.1 and we are looking into the changes as they need to be known to create zips for flashing. Other changes as well.
4.2.1 appears to encrypt by default; I think it is done to enable multi-user to restrict access to any other account.
Sorry I forgot fixable. Yes I believe once the update drops it will be resolved. That is why I provided the link.
Click to expand...
Click to collapse
Thanks to all for the help will continue to chck back.. Thank god for my nexus 7
LancasterCI said:
Thanks to all for the help will continue to chck back.. Thank god for my nexus 7
Click to expand...
Click to collapse
I'm sorry.
Good Luck!
Hi LancasterCI,
After several test with the new ota update I have also had similar issue with recovery no being able to mount anything but system.
However my fastboot was still working so we need to get that up and running first.
What I believe is happening is that the new bootloader is not actually encrypting anything but rather reformatting the cache, data partitions to a format that twrp & cwm are not looking for.
pjc21; said:
After reading through some of the posts in the twrp thread with similar issues. I seems that twrp looks for these partitions (data, system, cache, etc) to be in a certain format, ie ext4. However is the ext twrp is looking for does not exist (say the ext4 is now ext3) twrp will assume that it is encrypted and will bring up a password prompt and be unable to mount.
So with the test I have done to confirm that flashing just the new 4.2.1 bootloader and nothing else wiil encrypt the custom recoveries, could it be that the new 4.2.1 bootloader is reformatting these partitions to some other format making twrp & cwm assume that these partitions are now encrypted??
Click to expand...
Click to collapse
What we need to do 1st is get fastboot working for you, now I think we can get adb working by following this how-to just follow on from the device manager part to get adb working in recovery provided you have adb setup on your pc already.
Once you have adb working try the following command to reboot into bootloader, sometimes the tab just needs a hard reboot.
Code:
adb reboot bootloader
If this works, boot into fastboot and follow my post here, once done you'll be back on stock 4.1.1 but will then be able to boot back into fastboot and flash custom recovery and custom rom again.
Hope this helps.
pjc21 said:
Hi LancasterCI,
After several test with the new ota update I have also had similar issue with recovery no being able to mount anything but system.
However my fastboot was still working so we need to get that up and running first.
What I believe is happening is that the new bootloader is not actually encrypting anything but rather reformatting the cache, data partitions to a format that twrp & cwm are not looking for.
What we need to do 1st is get fastboot working for you, now I think we can get adb working by following this how-to just follow on from the device manager part to get adb working in recovery provided you have adb setup on your pc already.
Once you have adb working try the following command to reboot into bootloader, sometimes the tab just needs a hard reboot.
Code:
adb reboot bootloader
If this works, boot into fastboot and follow my post here, once done you'll be back on stock 4.1.1 but will then be able to boot back into fastboot and flash custom recovery and custom rom again.
Hope this helps.
Click to expand...
Click to collapse
ok I got back into the boot loader but i cant flash anyhting it wont even let me change my recovery
I get this message
"erroe: cannot load 'stock.blob' : No error"
The 4.2.1 update is on Asus so with luck we will start to see resolutions for these problems
Found the ultimate recovery, the receipt!!! The retailer exchanged it no questions asked. I know it the noon way out but now I have a fresh slate to start with and won't be flashing 4.2 anytime soon. I do however want to thank you all for your support and help. I'm definitely gonna be modding my tab as soon as the devs get a good fix going. BTW would love to for and a toolkit for this eventually, please devs??
Sent from my Nexus 7 using xda app-developers app
Hello guys, as the title suggest i can't mount any partition on my tab...
i'm using TWRP 2.4.4.0 and i'm on the 4.2 JB bootloader...
what should i do to get it working again?
also in the bootloader i can see this
Code:
Key driver not found... Booting OS
Android cardhU-user bootloader <1.00 e> released by "WW_epad-10.6.1.8-20130225" A03
matt95 said:
Hello guys, as the title suggest i can't mount any partition on my tab...
i'm using TWRP 2.4.4.0 and i'm on the 4.2 JB bootloader...
what should i do to get it working again?
Click to expand...
Click to collapse
As long as you can use fastboot, replace it with the version that works on your bootloader:
TWRP 2.4.4. 0-4.2.
CAREFUL: A lot of people bricked their tablets in this state.
Read one of the many threads on this particular issue.
Sent from my TF300T using Tapatalk HD
i've tried to flash the new recovery but it remains always the same, for instance i've flashed the 2.5.0.0 4.2 version but every time i boot into recovery it says TWRP 2.4.4.0 (which is the one i had before)
matt95 said:
i've tried to flash the new recovery but it remains always the same, for instance i've flashed the 2.5.0.0 4.2 version but every time i boot into recovery it says TWRP 2.4.4.0 (which is the one i had before)
Click to expand...
Click to collapse
Weird.
Are you using fastboot to flash?
What messages are you getting from fastboot?
Sent from my TF300T using Tapatalk HD
Code:
ERROR: could not get pipe properties
and then it flashes it correctly but nothing seems to change
matt95 said:
Code:
ERROR: could not get pipe properties
and then it flashes it correctly but nothing seems to change
Click to expand...
Click to collapse
OK, so flashing fails silently for some reason.
Do you see the blue flash bar on the bootloader screen, when fast boot says "writing"?
Never had any fastboot issues on Linux, but I have seen lots of people having issues with drivers on Windows. If you are using Windows, you might want to read up, how to make sure you have the proper drivers installed.
Short of that, no idea. :-/
Maybe can you post the full output of fastboot?
Should not be more than a couple of lines, right?
Sent from my TF300T using Tapatalk HD
i'm not at home now, i'll post them as soon as i get to it...
anyway i used MacOs, Linux and Windows
Make sure you're using the newest fastboot. There may be a bug on your current version.
Back in August I soft-bricked my tablet - no recovery and no ADB access. Fastboot would turn on on the tablet, but fastboot on my computer (Debian) kept hanging on "waiting for device". I had used fastboot on the same computer a couple weeks earlier to flash a recovery, and lsusb showed all the correct device info, so I thought fastboot was broken on the tablet and I was SOL. Well, fastboot got added to the Debian repos at some point, and I installed that version. 8 months and 2 fastboot updates went by before I even attempted to fix my tablet again (2 weeks ago), but somehow it worked, and I now have an awesome tablet to play with. I have no idea what happened with fastboot when my tablet first bricked, but I can only assume that one of the fastboot updates fixed a nasty bug that only showed up when I bricked the tablet.
I know your device is being recognized by fastboot, and your situation is much different than mine was, but you could be experiencing a completely different bug.
EndlessDissent said:
Make sure you're using the newest fastboot.
Click to expand...
Click to collapse
Good point!
matt, any progress?
http://forum.xda-developers.com/showthread.php?p=40809070
mb it will help you
sorry guys today i was very busy, i'll try to solve it tomorrow
matt95 said:
sorry guys today i was very busy, i'll try to solve it tomorrow
Click to expand...
Click to collapse
In your bootloader, what version of ASUS firmware does it say you are running. It makes a big difference for which version of TWRP you should be using.
edit:
sorry in your first post i could see you listed it, I think you may be getting this besause you dont have the TWRP version for 4.2 jellybean. the versions that are compatible are labeled -4.2 at the end.
here is the link for the right twrp for asus firmware 10.6.1.8 - http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
Version 2.5.5.0-4.2. of twrp is only compatible with the update for our tab that came out last week-asus firmware 10.6.1.15.3
CBank said:
In your bootloader, what version of ASUS firmware does it say you are running. It makes a big difference for which version of TWRP you should be using.
edit:
sorry in your first post i could see you listed it, I think you may be getting this besause you dont have the TWRP version for 4.2 jellybean. the versions that are compatible are labeled -4.2 at the end.
here is the link for the right twrp for asus firmware 10.6.1.8 - http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
Version 2.5.5.0-4.2. of twrp is only compatible with the update for our tab that came out last week-asus firmware 10.6.1.15.3
Click to expand...
Click to collapse
at first i didn't install the correct TWRP but now i can't even flash the correct one that's my problem
I believe this may be the same issue that alot of devices suffered from when the 4.2.1 update first came out.
Here is a thread on the issue
http://forum.xda-developers.com/showthread.php?t=2179874
From what I understand it seems that the 4.2.1 bootloader changed the way that the partition table was setup and thus all previous versions of custom recoveries could not mount any partitions (twrp would ask for password & not be able to mount any partition & cwm also not able to mount any partition) and a new twrp-4.2 version had to be made specifically for the 4.2.1 bootloader.
Still not sure as to why this caused the fastboot issue with the majority of people that flashed an incompatible version of twrp or cwm.
The fastboot issue I am talking about is that when you use the "flash" command everything will seem to go fine , it will say writing... and successful on the command prompt but you will not get any blue progress bar on the tablet itself and after the flash command has completed the fastboot reboot command will not reboot the tablet. Which I find very odd as other fastboot commands will still work without issue.
The only know solution if this is the issue you have is to replace the motherboard.
pjc21 said:
The only know solution if this is the issue you have is to replace the motherboard.
Click to expand...
Click to collapse
bad news
matt95 said:
bad news
Click to expand...
Click to collapse
Well, don't give up yet. That there is no known solution does not mean we can't find any.
If fastboot is broken, can you access via adb, while in recovery?
Also there was a thread on unbricking with fastboot issues. Might try that:
http://forum.xda-developers.com/showthread.php?t=2236885
Sent from my TF300T using Tapatalk HD
i'm able to use adb and also fastboot commands... the recovery however do not work obviously because it isn't the right one... i'm here on xda since 2010 and i still make such mistakes stupid me
matt95 said:
i'm able to use adb and also fastboot commands... the recovery however do not work obviously because it isn't the right one... i'm here on xda since 2010 and i still make such mistakes stupid me
Click to expand...
Click to collapse
Just shows that it can happen to the best of us!
Why don't you try the method from the thread in my last post?
Seems the guy had the same issue with fastboot and solved it.
Sent from my TF300T using Tapatalk HD
i'll definitely try that method! i'll let you know, thanks guys
matt95 said:
i'll definitely try that method! i'll let you know, thanks guys
Click to expand...
Click to collapse
I'm in the same situation that you're in. I can send simple fastboot and ADB commands to the tab but as soon as I try to write anything, it just freezes and requires a hard reset. You'll find that you will be able to erase and send simple reset/info request but no write commands. You'll be able to erase your recovery partition but you will not be able write anything new to it. Good luck!
I ordered a MB from ebay last night. Now I just need to find a guide on replacing it.....
Hello, I seem to have soft bricked my tf700.
I flashed a newish pacman nightly in CWM (after wiping data/cache/dalvik cache), which completed with no errors, then I flashed the corresponding GAPPS. But my device became stuck in the pacman boot intro.
So I tried flashing slimkat which led to my device not getting past the first bootup screen (where you can enter recovery if pressing the corresponding buttons).
After this screw-up I stupidly hit the wipe data button on the bootloader. I then tried doing the method of using fastboot to erase system, cache, and all that so I could flash system blob of the newest asus US SKU (that is correct for a US bought tf700 right?). Either this or wiping the data caused me to have a different bootloader as pictured below as I no longer have the android button and it does not ask me to press volume up to access recovery (the only way to access recovery is by hitting the wipe data button in bootloader).
I can still fastboot flash CWM, but trying to flash TWRP does not work as it finishes but going into recovery causes the tablet to just restart. Trying to flash asus stock as above would always give me an error like the one pictured below. Similar errors occur if trying to flash any rom inside CWM via an external sd card.
I do not have access to adb as i believe i dont have usb debugging enabled since the pacman rom or any other rom did not ever start. It just gives me the device not found error even after manually installing the drivers on two different computers.
Cant seem to get these pics to load, but copying the url and pasting it works.
http://imgur.com/AaU0GMt
http://imgur.com/vDTVa4B
You probably flashed the wrong Rom. Try flashing the >right< stock Rom and go from there. Double check everything you flash.
tylerleo said:
You probably flashed the wrong Rom. Try flashing the >right< stock Rom and go from there. Double check everything you flash.
Click to expand...
Click to collapse
Whats the "right" rom here? Talking about the original asus stock rom? I have now tried the the pacman nightly, pacman release, slim kat release, clean rom release, an ICS asus stock rom, and two different versions of the jellybean asus stock rom. These were either done in CWM via internal sd card, external sd card, or done through fastboost flash system blob and flash zip.
gio3505 said:
Whats the "right" rom here? Talking about the original asus stock rom? I have now tried the the pacman nightly, pacman release, slim kat release, clean rom release, an ICS asus stock rom, and two different versions of the jellybean asus stock rom. These were either done in CWM via internal sd card, external sd card, or done through fastboost flash system blob and flash zip.
Click to expand...
Click to collapse
Whatever Rom came on the device,(Good thing to have, da) I'm not familiar with this device.
tylerleo said:
Whatever Rom came on the device,(Good thing to have, da) I'm not familiar with this device.
Click to expand...
Click to collapse
As far as i know, i have installed the stock rom, or atleast multiple versions of it with no success as it gives me an error stating something like staging or system when trying to write it.
gio3505 said:
As far as i know, i have installed the stock rom, or atleast multiple versions of it with no success as it gives me an error stating something like staging or system when trying to write it.
Click to expand...
Click to collapse
Hmm, I'd Download a stock Rom for the device offline, take on the sd card and put it on there real quick and try to flash that, if not, you probably bricked your device. I wouldn't know how to fix it beyond that. Ask the dev that made the Rom were everything that went south and an email to cwm wouldn't hurt either
I am also not sure if I need to have my external sd card formatted a certain way or download a specific CWM to allow flashing the stock rom. Ive spent over 10 hours trying to figure this out, very frustrating.
I have run CWM 6.0.4.6, CWM 6.0.4.7, and older versions to see if I could flash the stock rom with no luck. I have also tried different versions of TWRP but they always hang and reboot my tf700. I get errors ranging from status 6, status 7, cannot mount data, cannot mount staging, and cannot mount system. I am completely lost on what I can do. I have even tried a seperate sdcard to see if maybe the one I was originally using was bad with no luck. GG :/
gio3505 said:
I have run CWM 6.0.4.6, CWM 6.0.4.7, and older versions to see if I could flash the stock rom with no luck. I have also tried different versions of TWRP but they always hang and reboot my tf700. I get errors ranging from status 6, status 7, cannot mount data, cannot mount staging, and cannot mount system. I am completely lost on what I can do. I have even tried a seperate sdcard to see if maybe the one I was originally using was bad with no luck. GG :/
Click to expand...
Click to collapse
You gotta stop flashing stuff and slow down!
During all of this you never posted your bootloader version, so you may have been on the wrong bootloader to begin with - who knows.
When you hit the Wipe Data in the bootloader menu you caused the BL do write a wipe data command to the misc partition, causing the tablet to boot to recovery each time you booted (I'm guessing here) and then interrupting it. Usually, with CWM installed, it eventually sorts it out and executes the wipe data command, but that takes hours! You just have to leave it alone.
Hard to tell where you are now since you flashed all kinds of stuff since then.
Can you still boot into the bootloader and have a fastboot connection?
What's the BL version number?
If you boot, what does it boot into?
The picture links are broken - at least in Tapatalk. Post them again?
berndblb said:
You gotta stop flashing stuff and slow down!
During all of this you never posted your bootloader version, so you may have been on the wrong bootloader to begin with - who knows.
When you hit the Wipe Data in the bootloader menu you caused the BL do write a wipe data command to the misc partition, causing the tablet to boot to recovery each time you booted (I'm guessing here) and then interrupting it. Usually, with CWM installed, it eventually sorts it out and executes the wipe data command, but that takes hours! You just have to leave it alone.
Hard to tell where you are now since you flashed all kinds of stuff since then.
Can you still boot into the bootloader and have a fastboot connection?
What's the BL version number?
If you boot, what does it boot into?
The picture links are broken - at least in Tapatalk. Post them again?
Click to expand...
Click to collapse
Yes, the pictures are broken. You can still copy paste the url though. Couldnt figure out why it wouldnt work.
The tablet boots into the first screen that states it is unlocked, but does not go any further.
There is no bootloader version on the top left when holding down power + volume down.
I can still get to the place where it allows me to wipe data or fastboot, but the android icon to boot into android is now gone.
adb does not recognize my device even after manually installing the drivers, but fastboot works fine.
Is there any other way to find my bootloader version?
gio3505 said:
Yes, the pictures are broken. You can still copy paste the url though. Couldnt figure out why it wouldnt work.
The tablet boots into the first screen that states it is unlocked, but does not go any further.
There is no bootloader version on the top left when holding down power + volume down.
I can still get to the place where it allows me to wipe data or fastboot, but the android icon to boot into android is now gone.
adb does not recognize my device even after manually installing the drivers, but fastboot works fine.
Is there any other way to find my bootloader version?
Click to expand...
Click to collapse
Maybe you want to edit your post with the urls then.... Makes it easier for people trying to help...
You're seriously messed up, I think. I see a USB icon in there which would indicate that your bootloader is ancient. But then it says: "starting USB fastboot protocol".
Is that after you selected the USB icon?
Anyway, I think you're only chance is buster99's method to get it back. Did you try that already?
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Naturally you have to extract the system blob from the 10.6.1.14.10 US Asus firmware, but then you can try to fastboot flash it with buster's method.
Good luck!
berndblb said:
Maybe you want to edit your post with the urls then.... Makes it easier for people trying to help...
You're seriously messed up, I think. I see a USB icon in there which would indicate that your bootloader is ancient. But then it says: "starting USB fastboot protocol".
Is that after you selected the USB icon?
Anyway, I think you're only chance is buster99's method to get it back. Did you try that already?
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Naturally you have to extract the system blob from the 10.6.1.14.10 US Asus firmware, but then you can try to fastboot flash it with buster's method.
Good luck!
Click to expand...
Click to collapse
Its starts the usb fastboot automatically if no input is selected. I had a different bootloader up until i tried that thing that buster did. It always gives me an error like cant write to system or something if i try it.
gio3505 said:
Its starts the usb fastboot automatically if no input is selected. I had a different bootloader up until i tried that thing that buster did. It always gives me an error like cant write to system or something if i try it.
Click to expand...
Click to collapse
Which blob did you flash with buster's method?
I'm afraid you flashed something totally incompatible with your tablet...
You did not generate your nvflash blobs sometime prior to this, did you?
berndblb said:
Which blob did you flash with buster's method?
I'm afraid you flashed something totally incompatible with your tablet...
You did not generate your nvflash blobs sometime prior to this, did you?
Click to expand...
Click to collapse
I flashed the asus stock rom downloaded from their website. The US version as it was bought in the US (right? 0.o). I hadnt heard of nvflash before trying to install a rom so i did not make a backup.
gio3505 said:
I flashed the asus stock rom downloaded from their website. The US version as it was bought in the US (right? 0.o). I hadnt heard of nvflash before trying to install a rom so i did not make a backup.
Click to expand...
Click to collapse
Are you sure you downloaded the correct firmware? For the TF700?
Do you still have the original zip you extracted the blob from?
Post the exact file name please.
berndblb said:
Are you sure you downloaded the correct firmware? For the TF700?
Do you still have the original zip you extracted the blob from?
Post the exact file name please.
Click to expand...
Click to collapse
US_epaduser10_6_1_14_10_UpdateLauncher (2)
or
US_epaduser_VER104425UpdateLauncher
or
US_epad_user_9_4_5_30_20120907_UpdateLauncher
Ive downloaded a lot of different versions from the asus website. The last one came from a forum post listing older firmware, which I have tried a lot of different ones.
gio3505 said:
US_epaduser10_6_1_14_10_UpdateLauncher (2)
or
US_epaduser_VER104425UpdateLauncher
or
US_epad_user_9_4_5_30_20120907_UpdateLauncher
Ive downloaded a lot of different versions from the asus website. The last one came from a forum post listing older firmware, which I have tried a lot of different ones.
Click to expand...
Click to collapse
You flashed all of those blobs???
In which order?
With what result?
Jeez - I think you're done for...
Sorry mate, but gotta catch some sleep now. Maybe somebody else has a bright idea...
berndblb said:
You flashed all of those blobs???
In which order?
With what result?
Jeez - I think you're done for...
Sorry mate, but gotta catch some sleep now. Maybe somebody else has a bright idea...
Click to expand...
Click to collapse
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
gio3505 said:
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
Click to expand...
Click to collapse
Right stop flashing random stuff - you have combinations of JB4.2.1, JB4.1.1 and ICS 4.0.3 just listed there.
Let me put a call out to @lj50036 who may be able to save you but if you have messed the bootloader up with no nvflash backups you are not going to be happy with the result. If you can still get to the bootloader screen then he can perform miraculous superhero acts and *maybe* save your device.
gio3505 said:
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
Click to expand...
Click to collapse
Shoot me an email at [email protected]
We can use hangouts see if there is a solution to your issue ...
Thx Josh
:crying: To start, I made lots of bad choices.
I have an HTC Droid Incredible. Firstly, I used Ext4 4 all to move /data/data to /data and move the Dalvik cache to the old data partition.
Moving the 160 MB Dalvik cache to the 150 MB /data/data partition was bad idea #1.
Oh, and I though I made a nandroid backup but hadn't. Bad idea #0.5.
Next, I realized my mistake with the Dalvik cache and tried to download the restore zip file. However, the website was down, so I decided to edit init.rc myself. How hard could it be?
That was bad idea #2.
I followed the directions at" droidcore .blogspot. com /2012/12/ how-to-edit-initrc-in-android .html" (please remove the spaces; I can't post links yet) and edited init.rc to remove the line that mounts /data/data to /data/dalvik-cache. I literally followed the directions perfectly. I also saved my old boot.img (that was the only good idea). When I rebooted the phone...it never finished turning on. It now boot loops after staying at the "HTC Droid Incredible" screen for about 5-10 seconds.
I tried to make an update.zip of the original boot image by following the instructions under the Android Enthusiasts post "http: / /android. stackexchange. c om/questions/36265 /flash -boot-img- without -using-fastboot- usb" (again, can't post links yet; remove the spaces), but Clockwordmod just says "Installation failed".
Now I have NO idea of what to do next. I can't use fastboot to reflash the original boot.img because I never unlocked my bootloader (I used to think that was S-Off).
Can anyone help me?
BTW, my Droid Incredible is running a leaked Android 2.3 that I found a few months before it Verizon officially released it. I have no idea where the heck I got it from and can't find it again. It says "TMartin GingerInc". Besides, I still don't know how to reflash the boot.img.
TechMinerUK said:
Are you sure you can't flash stock unmodified firmware to your phone as on other phones even with a locked bootloader you can flash verified images.
Anyway, can you at least get into the fastboot/bootloader to unlock it or flash firmware to it
Click to expand...
Click to collapse
I can't flash anything with fastboot. I can go into fastboot and recovery.
TechMinerUK said:
Are you opposed to unlocking the bootloader of your phone to restore it?
Click to expand...
Click to collapse
I could, but I've heard bad things about HTCDev's guide (i.e. it bricks phones, probably worse than my phone already is). Unless there's something I missed?
kirbyfan64sos said:
I can't flash anything with fastboot. I can go into fastboot and recovery.
Click to expand...
Click to collapse
By Recovery, are you referring to the Custom Recovery or the Stock Recovery ? Your first post does not shed any light. Please understand that bootloader expects certain partitions in certain places as the Partition table is defined in the Firmware. So your device may not boot if you tried to flash wrong partition in the wrong place.
I think you might be running [Flashable GB Update]Incredible_C_GB_S_VERIZON_WWE_4.01.605.0_Radio_2.1 5.10.05.06_NV at this time.
Please review [FYI]If You're New to Modding/Rooting, Read This First! (Updated 08/05/10)
Now if its space you are worried about, please review [HOW TO] Fix the "Low on space" problem (in plain English)
If its Stock firmware you want, please see HTC Incredible Shipped Roms (RUUs)
Perseus71 said:
By Recovery, are you referring to the Custom Recovery or the Stock Recovery ? Your first post does not shed any light. Please understand that bootloader expects certain partitions in certain places as the Partition table is defined in the Firmware. So your device may not boot if you tried to flash wrong partition in the wrong place.
I think you might be running [Flashable GB Update]Incredible_C_GB_S_VERIZON_WWE_4.01.605.0_Radio_2.1 5.10.05.06_NV at this time.
Please review [FYI]If You're New to Modding/Rooting, Read This First! (Updated 08/05/10)
Now if its space you are worried about, please review [HOW TO] Fix the "Low on space" problem (in plain English)
If its Stock firmware you want, please see HTC Incredible Shipped Roms (RUUs)
Click to expand...
Click to collapse
Yes, that's it!
I have ClockwordMod, so I meant "custom recovery". I'm pretty sure I didn't mess up the partition tables. I double-checked the partitions I saved everything to. It was the same one I extracted boot.img from.
please review the threads I linked earlier. Post as necessory on the right thread.
Thread Closed. Thank you.