Database Info

[Q] Clockworkmod warns: "bad recovery" - What to do?

Hello guys,
a few days ago I dared to root my Xperia X10 Mini Pro with SuperOneClick and flashed a Cyanogenmod 7 Android 2.3.3 ROM. All in all, it worked pretty well.
After doing some apps installation stuff I rebooted in the Recovery (Clockworkmod which obviously came along with the ROM) and made a backup, just for the case. Afterwards, I selected "power off" in the CWM menu because I wanted to go to bed.
Then, immediately, CWM said something like "Error - This recovery seems to be bad" and something with a "risk". I managed however to power off. Can't remember if that worked via CWM or if I pushed the power off hardbutton or removed the battery.
Yet - the ROM seems to work. Now I'm a bit anxious because of the CWM error.
Is there really a risk? I planned to dare unlocking the bootloader soon. Is it dangerous to do this with a "bad recovery" or doesn't that matter at all?
Is there a possibility to repair CWM? Can I just install a new CWM? If yes - how?
Sorry - pretty noobish questions, I know.
Can you help me anyway?
Thanks a lot!

deleted post

Thank you for your help! I already thought that no one would answer because the thread disappered on page 3 of this forum
I've never heard from Odin before and therefore googled it. It only occured in connection with Samsung devices. Are you sure it is compatible to my Sony Ericsson?
Anyway, can I also install a new CWM via ROM Manager or wouldn't you recommend this?

Warning: I'm a noob. Take my advice at your own risk!
From what I understand, flashing CWM via Rom Manager is exactly the same as manual flashing (perhaps better, since the Rom Manager presumably keeps up to date). So I think you should be able to do so and make another recovery (without going through any of that manual flashing stuff). You should get a second opinion just because I'm so noobish, but I think this is the case.
However, from my limited understanding, I don't think the recovery will make any difference when dealing with the bootloader. The bootloader is, more or less, the very first set of instructions executed when the phone turns on. If you mess that up, your phone won't even be able to get into recovery mode. Also, the recovery images are stored on your sd card, which is wiped upon unlocking. Once again, I could be wrong.

deleted post

Dude, what are you talking about? You can't use ODIN on a non-Samsung phone.

trich025 said:
don't use rom manager just use the odin for your safety, you can bet that samsung users are the one benefiting on odin but as you can see erricson and samsung are both android phones and if you examine them both device have similar programs, and one thing, always keep in mind that you have to back up your current rom for emergency uses so you can still get back to were you started in case something went wrong.
if i helped you with this problem you could click the thanks button >>>>
Click to expand...
Click to collapse
OK now this is flat out wrong. Each Android device has a different program used. Samsung has Odin, HTC has an RUU. Not sure about SE. But never use a software made for one device on another unless you want a brick. Just because they both use android doesn't mean they are the same.

Thanks to everyone, especially Product F(RED)!
No offence, trich025, but I guess you were wrong.
Can I destroy something by re-installing or updating CWM via ROM-Manager just in case my CWM has a bug?

[Q] Stuck @ Boot Screen

Hey Everyone
I've done quite a bit of reading and nothing seems to quite fit the issue I am having so I thought I'd post and seek help.
Some background info...I've unlocked the bootloader and also generated the NVFlash files when I first bought the tablet. It was running the stock ICS Rom. I had CWM Recovery and it was rooted.
I wanted to try a new ROM called BlueAndroid as I read it was really good. I followed all of the instructions and flashed from the sdcard. It appeared successful but when I went to restart the system, it kept boot looping at the ASUS Screen. Then I thought I'd just go back to what I had before by restoring it from CWM Recovery but to my surprise, it didn't work and now it isn't even looping, just stuck on the ASUS Screen.
I tried to fastboot CWM and TeamWin Recovery. Although they were both successful writes to the tablet, they won't load. I can only get to the fastboot screen where it shows the 'wipe data' and 'USB icon'. There used to be an Android Robot icon too but it is gone now.
I even tried to NVFlash. It worked but I'm still stuck on Asus Screen.
Lastly, when I select wipe data, it erases and the Team WIN logo appears for a split second and then it goes back to Asus Screen.
I keep reading something about the possibility of incorrect partitions but I have no idea what that means.
Any help would be greatly appreciated.
Thanks
A
P.S. In the meantime, is there any way to shut the tablet off? I've tried holding the power button down but it just reboots.
Solved: Used blobunpack to get bootloader files from the stock ICS ROM (blobunpack the blob file from the ROM). Then used NVFlash to download those files to tablet. Hope this helps others with same problem. I can elaborate more tomorrow...it is really late and very sleepy but relieved!

xxboarderxx said:
Hey Everyone
I've done quite a bit of reading and nothing seems to quite fit the issue I am having so I thought I'd post and seek help.
Some background info...I've unlocked the bootloader and also generated the NVFlash files when I first bought the tablet. It was running the stock ICS Rom. I had CWM Recovery and it was rooted.
I wanted to try a new ROM called BlueAndroid as I read it was really good. I followed all of the instructions and flashed from the sdcard. It appeared successful but when I went to restart the system, it kept boot looping at the ASUS Screen. Then I thought I'd just go back to what I had before by restoring it from CWM Recovery but to my surprise, it didn't work and now it isn't even looping, just stuck on the ASUS Screen.
I tried to fastboot CWM and TeamWin Recovery. Although they were both successful writes to the tablet, they won't load. I can only get to the fastboot screen where it shows the 'wipe data' and 'USB icon'. There used to be an Android Robot icon too but it is gone now.
I even tried to NVFlash. It worked but I'm still stuck on Asus Screen.
Lastly, when I select wipe data, it erases and the Team WIN logo appears for a split second and then it goes back to Asus Screen.
I keep reading something about the possibility of incorrect partitions but I have no idea what that means.
Any help would be greatly appreciated.
Thanks
A
P.S. In the meantime, is there any way to shut the tablet off? I've tried holding the power button down but it just reboots.
Solved: Used blobunpack to get bootloader files from the stock ICS ROM (blobunpack the blob file from the ROM). Then used NVFlash to download those files to tablet. Hope this helps others with same problem. I can elaborate more tomorrow...it is really late and very sleepy but relieved!
Click to expand...
Click to collapse
I had the same problem. I think it is bricked. I called ASUS, told them it was unlocked, they told me to ship it to them and they would fix it. I boxed it up, and shipped it off. Could not turn it off. Hope the box did not catch on fire.

OP, where were you a week ago when I "bricked" my tablet?
I had the -exact- same issue, btw, although with different circumstances. I can verify with 100% confidence that using NVFlash successfully restores the ICS bootloader. How I understand our situation is that when you tried to flash a ROM or anything based on JB over an ICS-device, it confuses things and causes issues. So you basically have to restore the ICS bootloader to get any progress.
But you hit the nail on the head describing my problem, although I would have ended up typing a dissertation to get across the same information you did. So touche on that
I used the same steps, as well. I blob unpacked my ICS stock firmware (.29 version from ASUS website). I used the boot.blob from my NVFlash files, along with the files I unpacked from the stock blob and flashed them over NVflash.
After a week of a useless tablet, I'm up and running.
I'm going to write a guide about my experience for anyone else and I would welcome your input sir.

I think you could mean a kind of recovery loop: There is a file called "command" on the cache partition which causes the recovery image to boot. But if the recovery is broken then it will not empty cache. The recovery will boot but does not update screen (showing just boot splash). On the next time it will boot again ...
Please be just carefully: "wipe data" in the fastboot menu will create the "command" file.

ScottBroker said:
I had the same problem. I think it is bricked. I called ASUS, told them it was unlocked, they told me to ship it to them and they would fix it. I boxed it up, and shipped it off. Could not turn it off. Hope the box did not catch on fire.
Click to expand...
Click to collapse
Sorry...if I could have made this attempt last week, I may have been able to help you then. :sly:
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD

opethfan89 said:
OP, where were you a week ago when I "bricked" my tablet?
I had the -exact- same issue, btw, although with different circumstances. I can verify with 100% confidence that using NVFlash successfully restores the ICS bootloader. How I understand our situation is that when you tried to flash a ROM or anything based on JB over an ICS-device, it confuses things and causes issues. So you basically have to restore the ICS bootloader to get any progress.
But you hit the nail on the head describing my problem, although I would have ended up typing a dissertation to get across the same information you did. So touche on that
I used the same steps, as well. I blob unpacked my ICS stock firmware (.29 version from ASUS website). I used the boot.blob from my NVFlash files, along with the files I unpacked from the stock blob and flashed them over NVflash.
After a week of a useless tablet, I'm up and running.
I'm going to write a guide about my experience for anyone else and I would welcome your input sir.
Click to expand...
Click to collapse
Well, I'm sure you learned a lot during your experience of trying to get it working again - I know I did so that's a +1. I wasn't worried that my tablet was bricked because I was told that if I had the NVFLASH files, I could recover from anything save dropping it and breaking it that way. I was also able to connect to the PC using fastboot and adb so that was another positive.
If you write a guide, that would be great as while I was trying to piecemeal information together to get my tablet running again, there seemed to be dozens of people out there with a similar problem and being unable to get it working again and having to send it off to Asus. Would probably be a great contribution.
The one thing I learned though this ordeal is that the stock bootloader needs to be the same as the custom ROM before installing. I wish ROM guides would tell you this REALLY important fact...
Cheers
A
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD

xxboarderxx said:
Well, I'm sure you learned a lot during your experience of trying to get it working again - I know I did so that's a +1. I wasn't worried that my tablet was bricked because I was told that if I had the NVFLASH files, I could recover from anything save dropping it and breaking it that way. I was also able to connect to the PC using fastboot and adb so that was another positive.
If you write a guide, that would be great as while I was trying to piecemeal information together to get my tablet running again, there seemed to be dozens of people out there with a similar problem and being unable to get it working again and having to send it off to Asus. Would probably be a great contribution.
The one thing I learned though this ordeal is that the stock bootloader needs to be the same as the custom ROM before installing. I wish ROM guides would tell you this REALLY important fact...
Cheers
A
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
Really? I didn't know that....that might explain why none of the ROM's I'm flashing will work.....
At this point, I'm just going to upgrade to the stock JB firmware and flash the new JB roms. I've got my NVFlash ICS files (which saved my frickin life) so I have no hesitations about doing anything, and I really understand the NVFlash process well having bricked myself so hard.
My guide is mostly done. I spent more time writing it than I did focusing on schoolwork so I will finish it up hopefully this weekend. It's rather long and quite details so I hope it will help everyone.

I was smiling as I read the first post, but this is going to come in real handy if I nuke my bootloader. Thanks. I wish I had gotten to this first, heh, I could have told you don't flash a Jellybean ROM over an ICS bootloader, it won't boot.
Good information to have though. Thank you!

opethfan89 said:
Really? I didn't know that....that might explain why none of the ROM's I'm flashing will work.....
At this point, I'm just going to upgrade to the stock JB firmware and flash the new JB roms. I've got my NVFlash ICS files (which saved my frickin life) so I have no hesitations about doing anything, and I really understand the NVFlash process well having bricked myself so hard.
My guide is mostly done. I spent more time writing it than I did focusing on schoolwork so I will finish it up hopefully this weekend. It's rather long and quite details so I hope it will help everyone.
Click to expand...
Click to collapse
:good:

Just giving some advice to those who may jump in late, DO NOT use the "wipe data" method from holding volume down. This method relies on Asus' stock recovery image. And it somehow screws everything up when you do it on a non Asus' recovery.. Not sure why but dont ever use that

elesbb said:
Just giving some advice to those who may jump in late, DO NOT use the "wipe data" method from holding volume down. This method relies on Asus' stock recovery image. And it somehow screws everything up when you do it on a non Asus' recovery.. Not sure why but dont ever use that
Click to expand...
Click to collapse
You can do it if you have a custom recovery already flashed like TWRP or CWM. But I agree with you - after you start having a basic understanding of Android customization, there's no reason why you would want to use 'wipe data' from the volume down+power.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD

elesbb said:
Just giving some advice to those who may jump in late, DO NOT use the "wipe data" method from holding volume down. This method relies on Asus' stock recovery image. And it somehow screws everything up when you do it on a non Asus' recovery.. Not sure why but dont ever use that
Click to expand...
Click to collapse
That finally explains why it wouldn't work, thank you for elaborating on that!!
Is there a guide on how to get the stock recovery back, or does it automatically get flashed when you flash stock?

opethfan89 said:
That finally explains why it wouldn't work, thank you for elaborating on that!!
Is there a guide on how to get the stock recovery back, or does it automatically get flashed when you flash stock?
Click to expand...
Click to collapse
Automatically gets flashed when you flash stock.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD

If you are in recovery loop you cannot go into the fastboot menu. The only way to get the stock recovery back is to use nvflash.

Bricked Tf300T (0x00000000)

Hi, I have a bricked Tf300t saying Unrecoverable bootloader error (0x000000000) whenever i try to access recovery, cold-boot or wipe.
If i don't go into fastboot, the loading screen will get stuck .. says - Your Device is UnLocked.
It had WW_epad-10.6.1.8-20130225 A03 , when it was working.
Whenever i try to flash recovery using Fastboot:
sending 'recovery' (7500 KB).
OKAY [ 2.762s]
writing 'recovery'...
OKAY [ 2.465s]
finished. total time: 5.227s
Fastboot on tablet freezes, nothing happens.
Any help would be appreciated. Thanks.

I have the exact same problem.
http://forum.xda-developers.com/showthread.php?t=2205158
Let me know if you figure it out

At least im not the only person on this ship hehe.
I tried most of the solutions with no success also, i think next step is to create a bootable sdcard and maybe bootloader works, then repartition the internal directories.
Anyone can confirm if this works before i waste more time trying to boot an sdcard please?
Edit:I updated to JB 4.2.2 before i managed to brick it... also i could't find any bootable android images for external Sd's
Since the latest update, NVFlash is not functional? Please somebody enlighten me with a solution as i use this tablet for work.

Any good news ?

mohlam12 said:
Any good news ?
Click to expand...
Click to collapse
nope we all have the same trouble! holding for a solution

First of all try to reflash the bootloader in fastboot, better yet, flash asus stock rom with fastboot....
It takes a long time and sometimes it looks like the computer freezes but it will work......after that flash the patched trwp recovery for 4.2.1.
If this all works you need to do a "wipe" in the fastboot screen (not recovery)

I have already tried reflashing stock rom with fastboot, and when it's ready fastboot freezes. After that i restart by power button and still same error.
Tomorrow i will try again and leave you some feedback, maybe this time i will be lucky...

Hi again, i just ordered a new mainboard for my tab. Hopefully i will get it running after i replace my board. When the mainboard arrives I will keep you updated with the results

alvinm91 said:
Hi again, i just ordered a new mainboard for my tab. Hopefully i will get it running after i replace my board. When the mainboard arrives I will keep you updated with the results
Click to expand...
Click to collapse
Hi,I have the same situation.Where did you buy the mainboard?And how much you paid?

I'm in the same ship. Any solution??

Unfortunately i had problems with shipping for the motherboard but i managed to order another one yesterday.
I found tf300t 32gb motherboards on ebay for $120 shipped. That is the only known solution at the moment.
Even the local store from where i bought it didn't have a clue how to fix it, so they wanted to ship it to Asus but i declined since software issues are not covered by warranty. Will keep you updated with installation photos when the motherboard arrives. Goodluck guys!

g-member said:
First of all try to reflash the bootloader in fastboot, better yet, flash asus stock rom with fastboot....
It takes a long time and sometimes it looks like the computer freezes but it will work......after that flash the patched trwp recovery for 4.2.1.
If this all works you need to do a "wipe" in the fastboot screen (not recovery)
Click to expand...
Click to collapse
I'd try following this if you haven't already.
Are you flashing the correct blob and whatnot? I'm also assuming you're using the right fastboot commands (fastboot -i 0x0b05 blah blah). Not trying to offend, just seeing exactly what steps you took.
Or perhaps you can flash to an earlier version of the official Asus ROMs.

Yep, i already tried flashing the correct blob, cmd prompt says succeeded but the tab freezes completely.
Earlier version don't work also. The problem is that after wiping the data, bootloader locked itself again. Bug from Asus? dunno but after wiping the data on my tf300 i couldn't flash anything.

Same problem
I have the same problem and after two days of fighting, suppose there are only two solutions: change the motherboard or wait for the NVFLASH to run in APX mode commands like: wheelie / nvflash. I signed the petition to ASUS and we await news. Good Luck.

Hi expertmicro , alvinm91 and all.
I have the same error on my device which is instead an Asus ME301T (the memo smart pad); sorry for jumping in with a post about another device but I tried quite few things to fix it and no luck. The TF300T and the ME301T have anyway similarities as to root it I used a method made for the TF300T and worked fine.
While I'm still searching for a solution, here you can find the ME301T thread, in case you would like to see what I tried.
Even if I don't know what NVFLASH is, if I can help by signing the petion please share the URL where I can do so.
FYI, I found this thread where is shown another method to fix the TF300T: http://forum.xda-developers.com/showthread.php?t=1622628 - don't know if it is applicable you tried it already?

Hi guys,
I solved the problem with the bootloader error (0x0000000) assistance in sending the TF300T. I told him that during the upgrade something must have gone wrong and the OS did not boot anymore. They repaired free of charge. My dealer to whom I entrusted the tablet is Mediaworld (a chain of electronic products Italian). I hope you can serve

I managed to fix mine after beig heavily bricked, hope it works for you
Link to my thread ---> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Good Luck!

Asus tf300t(g) boot loop and stuck in TWRP wont mount, not recognized. - briked

Hello
I have an asus tf300tg and I did update to 4.2.1 JB. bootloader was unlocked before the update. Tablets started ok then I put TWRP 2.5.0 but it seemed like something was not working well because I could not see external sd card when I tried to give you wipe from TWRP, but said faild. I rebooted the tablet I entered fastboot and in this mode shows, three icons. RTK, android, and wipe again. And naturally I did wipe once, then never turned on.
Now bootloader is unlocked and starts straight into TWRP.
At first my pc (win7 64bit) Recognize that "transformes" then I searched and found "Naked drivers 0.72" in the idea of ​​connecting the tablet in fastboot and write something-anything but I DON'T HAVE SUCCES.
I installed in various ways (asus adb, google adb) of naked driver but I could not communicate via fastboot. Maybe I don't chose the right way
Does anyone else have a procedure that can be repaired?
And that since the corect connection mode that allows me to write on tablet via fastboot ?
I saw that the problem occurs in many places and forums (like here: http://www.teamw.in/project/twrp2/97 Note the comments) but I dont found a solutions.
BR
Mihnea
I wait with many interes your sugestions.

Sorry to say but you should have read a little more about what you were doing. It CLEARLY says over and over and in this forum NOT to use THAT wipe option.
You've just wiped all the files from your device. There are now no files to boot from.
If you can get into fastboot or ADB you may have a chance of saving your tablet. There's a very good chance that you've just bricked it though. Best of luck.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2

wetbiker7 said:
Sorry to say but you should have read a little more about what you were doing. It CLEARLY says over and over and in this forum NOT to use THAT wipe option.
You've just wiped all the files from your device. There are now no files to boot from.
If you can get into fastboot or ADB you may have a chance of saving your tablet. There's a very good chance that you've just bricked it though. Best of luck.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
I dont understand ... WHY is happend that ? TWRP is sucks because I thing that soft dont have safety belt... ??? Because before to upgrate I do wipe and all was very ok .... or other is cause? I think that Asus dont put this obtion ... that people damage our tablets...
I think that good answer must be come from twrp team ???

I had also wiped my device and would have been stuck had I not had nvflash...please guys take all possible precautions before you start messing around with your devices and ensure you can go back and flash a stock ROM...now all I do is get into APX mode, fire up wheelie.exe and I unbrick my device. Did you nvflash your device before? If you can get into fastboot mode there may be some hope yet...
This is a good place to start: http://forum.xda-developers.com/forumdisplay.php?f=1579
If all else fails, please PM me...

mihnea_gsm said:
I dont understand ... WHY is happend that ? TWRP is sucks because I thing that soft dont have safety belt... ??? Because before to upgrate I do wipe and all was very ok .... or other is cause? I think that Asus dont put this obtion ... that people damage our tablets...
I think that good answer must be come from twrp team ???
Click to expand...
Click to collapse
Dude, you really didn't even get into TWRP recovery. If you would have tapped the RCK tab you would have went into TWRP. Don't go blaming it on TWRP because you failed to do your homework. I know there are probably 10 threads where people have done the same thing and tapped the wrong WIPE tab. If I can find and read them then so can you. You just failed to do so.
It really sux that you've messed your tablet up but when you've got a device that costs that much, you are supposed to do your research before trying something you know nothing about. I read through this forum for over a week before I bought and rooted mine because I wanted to make sure I knew what i was doing and didn't end up with a $300 paperweight. If I didn't know or couldn't find the answer I asked questions. :good:

wetbiker7 said:
Dude, you really didn't even get into TWRP recovery. If you would have tapped the RCK tab you would have went into TWRP. Don't go blaming it on TWRP because you failed to do your homework. I know there are probably 10 threads where people have done the same thing and tapped the wrong WIPE tab. If I can find and read them then so can you. You just failed to do so.
It really sux that you've messed your tablet up but when you've got a device that costs that much, you are supposed to do your research before trying something you know nothing about. I read through this forum for over a week before I bought and rooted mine because I wanted to make sure I knew what i was doing and didn't end up with a $300 paperweight. If I didn't know or couldn't find the answer I asked questions. :good:
Click to expand...
Click to collapse
Man no longer take ptr defense that I think you're wrong ...
Look .. when I got the asus app to unlock bootloader it says clearly: If using application note is lost ... guarantee ...
But here in this case I have taken away from the site fisirele .. and nothing in there that you do not press WIPE button
* That's what ... ok there is a software bug and it's understandable ... waiting to see how to solve ...
And another thing ... I have a GSM service ... so I pass many phones and tablets by hand and install a lot and CWM and TWRP and it is the first time that happens ... so do not need me to tell me that I have not done my homework.
Then I recommend the Samsung Galaxy Tab that anything is much simpler and solutions are at hand ... including bootloder destroyed ... then we rewrite bootloder JTAG on the tablet and tablet repair in 1 hour .. simple as that.
Today I gave mail to all those who produce JTAG interfaces (riff jtag, meduse jtag, vulcanobox, easy jtag) to see if anyone has any solutions for NVIDIA Tegra3 jtag, although I do not think ... but if I stick to appear instant boot tablet and restore bootloader, but many people don't have this interfeces...
BR
Mihnea

wetbiker7 said:
Dude, you really didn't even get into TWRP recovery. If you would have tapped the RCK tab you would have went into TWRP. Don't go blaming it on TWRP because you failed to do your homework. I know there are probably 10 threads where people have done the same thing and tapped the wrong WIPE tab. If I can find and read them then so can you. You just failed to do so.
It really sux that you've messed your tablet up but when you've got a device that costs that much, you are supposed to do your research before trying something you know nothing about. I read through this forum for over a week before I bought and rooted mine because I wanted to make sure I knew what i was doing and didn't end up with a $300 paperweight. If I didn't know or couldn't find the answer I asked questions. :good:
Click to expand...
Click to collapse
I've also read those warnings, but if bootloader's wipe is safe with stock recovery and bricks tablet with TWRP flashed, then there is clearly something wrong with TWRP.

mihnea_gsm said:
Man no longer take ptr defense that I think you're wrong ...
Look .. when I got the asus app to unlock bootloader it says clearly: If using application note is lost ... guarantee ...
But here in this case I have taken away from the site fisirele .. and nothing in there that you do not press WIPE button
* That's what ... ok there is a software bug and it's understandable ... waiting to see how to solve ...
And another thing ... I have a GSM service ... so I pass many phones and tablets by hand and install a lot and CWM and TWRP and it is the first time that happens ... so do not need me to tell me that I have not done my homework.
Then I recommend the Samsung Galaxy Tab that anything is much simpler and solutions are at hand ... including bootloder destroyed ... then we rewrite bootloder JTAG on the tablet and tablet repair in 1 hour .. simple as that.
Today I gave mail to all those who produce JTAG interfaces (riff jtag, meduse jtag, vulcanobox, easy jtag) to see if anyone has any solutions for NVIDIA Tegra3 jtag, although I do not think ... but if I stick to appear instant boot tablet and restore bootloader, but many people don't have this interfeces...
BR
Mihnea
Click to expand...
Click to collapse
Man, if you would have read , you would have known not to use the wipe tab. As I said before, there are threads all over the place in here stating NOT TO USE THAT WIPE OPTION. You may have done SOME research but you didn't do enough on THIS tablet. The research on all the other devices you know about doesn't count. LOL It's TF300 series we're talking about.
Oh, and you said for me not to take offense because I think you're wrong. Bro, I don't take offense because you disagree with me. I'm just trying to get you to man up and admit that you made the mistake and didn't do enough reading. LOL
quidrick said:
I've also read those warnings, but if bootloader's wipe is safe with stock recovery and bricks tablet with TWRP flashed, then there is clearly something wrong with TWRP.
Click to expand...
Click to collapse
Well, let me ask you a question. Why would you want to wipe the tablet anyways when it's not in recovery? You MUST press RCK to enter the recovery. The wipe option you guys are talking about is not even a part of TWRP recovery.

Moe5508 said:
I had also wiped my device and would have been stuck had I not had nvflash...please guys take all possible precautions before you start messing around with your devices and ensure you can go back and flash a stock ROM...now all I do is get into APX mode, fire up wheelie.exe and I unbrick my device. Did you nvflash your device before? If you can get into fastboot mode there may be some hope yet...
This is a good place to start: http://forum.xda-developers.com/forumdisplay.php?f=1579
If all else fails, please PM me...
Click to expand...
Click to collapse
in this moment I am in this point:
in this point adb recognized my tablet
C:\adb>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
0123456789ABCDEF recovery
but after I want to flash blob
C:\adb>fastboot -i 0x0B05 flash system blob
< waiting for device >
BR
Mihnea

Well, let me ask you a question. Why would you want to wipe the tablet anyways when it's not in recovery? You MUST press RCK to enter the recovery. The wipe option you guys are talking about is not even a part of TWRP recovery.
Click to expand...
Click to collapse
a) Because it's official method to do factory reset, recommended by ASUS when you have problems with your tablet. It is working perfectly fine on stock recovery and some users are used to do this that way.
b) Because it's quite easy to do this by mistake, when you are trying to enter recovery. Please, give me fast and honest answer without checking - which button changes option, and which enters selected option?
My tablet is perfectly fine, running TWRP and custom ROM, but someone has to defend users who used wipe data.
Unless we hear sensible explanation from one of TWRP developers why this option is working fine on stock recovery and is bricking tablets on TWRP, and why it can't work correctly (or at least safe) on custom recovery, then it should be treated as a custom recovery bug.

quidrick said:
a) Because it's official method to do factory reset, recommended by ASUS when you have problems with your tablet. It is working perfectly fine on stock recovery and some users are used to do this that way.
b) Because it's quite easy to do this by mistake, when you are trying to enter recovery. Please, give me fast and honest answer without checking - which button changes option, and which enters selected option?
My tablet is perfectly fine, running TWRP and custom ROM, but someone has to defend users who used wipe data.
Unless we hear sensible explanation from one of TWRP developers why this option is working fine on stock recovery and is bricking tablets on TWRP, and why it can't work correctly (or at least safe) on custom recovery, then it should be treated as a custom recovery bug.
Click to expand...
Click to collapse
Man you are right 100% wipe buton from asus MUST BE - wipe data from recovery (twrp) but I thing that twrp team is not agree with us...
Most important for me in this moment like other people I want to make table tablet alive....
BR
Mihnea

quidrick said:
a) Because it's official method to do factory reset, recommended by ASUS when you have problems with your tablet. It is working perfectly fine on stock recovery and some users are used to do this that way.
b) Because it's quite easy to do this by mistake, when you are trying to enter recovery. Please, give me fast and honest answer without checking - which button changes option, and which enters selected option?
My tablet is perfectly fine, running TWRP and custom ROM, but someone has to defend users who used wipe data.
Unless we hear sensible explanation from one of TWRP developers why this option is working fine on stock recovery and is bricking tablets on TWRP, and why it can't work correctly (or at least safe) on custom recovery, then it should be treated as a custom recovery bug.
Click to expand...
Click to collapse
You guys aren't getting my point at all. I'm not saying that the wipe data option screwing people's tablets up is right. All I'm saying is that the info is here in this forum saying not to do it. Lol If the time is taken to read the info in these threads we wouldn't even have this thread. :thumbup:
If myself and all the other people have been able to find this information and avoid tapping the wrong wipe data option then so should other people. THAT IS MY POINT.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2

At this point it really does not matter who is and who is not, right ... matter to be able to start and run ok tablets ...
So I expect all of which can give you an idea
BR
Mihnea

This is a question for developers more familiar with our partition layout. My working knowledge of android is limited, but I do have background in linux. If he can see his device under ADB, shouldnt it be possible for someone to do an adb pull of their system, data, bootloader, and recovery partitions for him to push to his?
The only reason I could think of that not working is if the wipe option deletes the entire partition table and they need to be repartitioned from scratch. Its either that or the Bootloader partition is getting wiped instead of the Data partition. Just bouncing ideas in my head here. It was on a kyocera zio and on gingerbread, but this was one way I was able to help restore a device.
NVflash seems capable of repartitioning the drive........ Does adb have commands to set up partitions as well?
One would also think odin should be able to help with repartitioning. There has to be a way.
-Edit-
Ok so if you DO have fastboot, you might be able to recover. Read this post !
http://forum.xda-developers.com/showthread.php?t=2236885

Something new...
We all know that in the above case is bricked tablet that starts directly in TWRP ... even if we start trying to po fastboot (volume down + power) it will start directly in TWRP
Now to answer adb shell like this:
c: \ Adb> adb devices
List of devices attached
0123456789ABCDEF recovery
But if I try to send something to it (like a touchscreen driver) see the answer and receives information
c: \ Adb> adb push 02-3011-4820.ekt / data / local / tmp /
* Daemon not running. starting it now on port 5037 *
* Successfully started daemon *
1027 KB / s (32868 bytes in 0.031s)
In other words we can send information in tablets briked .. I think now matter what name send.
I have here 2 tablets bricked (tf300tg and TF300T) and 3 functional TF300T tablet (but with broken touchscreen). The point is that I do not know what commands to send, and how to pull information from functional and tablets to the tablets who have problem
Now comes my question logic ... We can not copy anything from a 100% functional tablet and send this information to a tablet briked?? Can only boot, or recovery?

mihnea_gsm said:
in this moment I am in this point:
in this point adb recognized my tablet
C:\adb>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
0123456789ABCDEF recovery
but after I want to flash blob
C:\adb>fastboot -i 0x0B05 flash system blob
< waiting for device >
BR
Mihnea
Click to expand...
Click to collapse
Have the same problem...
fastboot stock at < waiting for device >
my device boot/reboot or power on without any touch....always boot into recovery twrp ( but can´t mount and do nothing)
Any help?

Boot your tablets up into the selection screen where you can select to wipe data, fastboot, recovery or load OS. If you have updated your bootloader and firmware to 4.2 then the fastboot option disappears and now you are already in fastboot mode when when you load the selection screen. All you will need to do is plug the USB cable into your tablet and your computer will recognize this and load the ADB interface. Btw if your having problems with TWRP 2.5, simply flash back to 2.4.4.0.. which is exactly what I did.
I updated my bootloader and firmware to 4.2 ASUS stock and then flashed TWRP 2.5... I was having issues such as split screen, coudn't mount anything and when I loaded into recovery I was asked for password. I simply flashed back 2.4.4.0 JB TWRP.
I was back to normal.

anaschillin said:
I updated my bootloader and firmware to 4.2 ASUS stock and then flashed TWRP 2.5... I was having issues such as split screen, coudn't mount anything and when I loaded into recovery I was asked for password. I simply flashed back 2.4.4.0 JB TWRP.
I was back to normal.
Click to expand...
Click to collapse
No - I think this part is wrong. Do not use JB version of TWRP with bootloader version 4.2. You must use TWRP version ending in -4.2.

bwiberg said:
No - I think this part is wrong. Do not use JB version of TWRP with bootloader version 4.2. You must use TWRP version ending in -4.2.
Click to expand...
Click to collapse
OK .. to start over ... I had Asus tf 300TG firmware version 4.1.1 and I did the OTA update to 4.2.1. After that I put some revovery TWRP 2.5.0.0 (most probably was not what I had) and broke the tablet.
Now my tablet is in this variant:
C: \ adb> adb devices
adb server is out of date. killing ...
* Successfully started daemon *
List of devices attached
0123456789ABCDEF recovery
But after I want to flash blob
C: \ adb> fastboot flash system's 0x0B05 blob
<Waiting for device>
You say that I should write: openrecovery-TWRP-2.5.0.0-TF300T tablet-4.2.blob as did the OTA update to 4.2.1 right?
* But in this moment I realize WHY I broke the tablet ... because I wrote this file: openrecovery-TWRP-2.5.0.0-tf300tg-JB.blob ...
Why I wrote this? because if you look here: http://techerrata.com/browse/twrp2/tf300t he write: If you have the 4.2 official update, choose one of the files that ends with -4.2. If you choose the wrong file you may brick your tablet.
* THIS FILE NOT EXSIT: openrecovery no-TWRP-2.5.0.0-tf300tg-4.2.blob .....exist only for tf300t not for tf 300tg
I write a post at twrp blog : http://www.teamw.in/project/twrp2/97
* Now see another file: openrecovery-TWRP-2.5.0.0-TF300T-JB.img .... what to do with this file?
OK and now...
What should I do? which file should I write?
And how (mode - fastboot, apx ???) should be the tablet to write the file?
And who would command if the tablet would be in that mode (fastboot, apx)
BR
MIHNEA

quidrick said:
a) Because it's official method to do factory reset, recommended by ASUS when you have problems with your tablet. It is working perfectly fine on stock recovery and some users are used to do this that way.
b) Because it's quite easy to do this by mistake, when you are trying to enter recovery. Please, give me fast and honest answer without checking - which button changes option, and which enters selected option?
My tablet is perfectly fine, running TWRP and custom ROM, but someone has to defend users who used wipe data.
Unless we hear sensible explanation from one of TWRP developers why this option is working fine on stock recovery and is bricking tablets on TWRP, and why it can't work correctly (or at least safe) on custom recovery, then it should be treated as a custom recovery bug.
Click to expand...
Click to collapse
I have nothing to do with twrp and certainly am no dev.
What I do know is the partition for recovery is a limited space and there is not enough room to emulate stock recovery and still have enough space to provide for the way we use twrp.
The "factory reset" recommended by Asus is located in settings. This is "wipe data" located in the bootloader. I have not heard or read of Asus suggesting use of wipe data but I have seen factory reset.
Now I don't believe in flaming anyone!
Explaining a mistake is positive, it helps the user know what not to do in the future but only if presented properly.
I'm sure the reply came from frustration of wanting to help but understanding that recoveries from wipe data are few.
No one wants to see a brick!
Sorry for taking space without providing any help for the OP!
If anyone has any suggestions for the OP please present them.
I was so slow posting I see help has arrived.

[Q] What if NVFlash got updated

Hi everyone,
So lets say that the sun would rise from the west tomorrow and Asus/Nvidia released an update for NVFlash compatible with 4.1 and 4.2. Would people including myself who have a bricked tf300t with nonfunctional "fastboot flash" be able to save the tablet or are we simply screwed? (changing motherboard is not worth it in my opinion) Could some body with enough knowledge be kind and explain?
By the way, if you haven't signed the NVFlash petition yet. Do a favor and do it now! Thanks.

I think you can only install nvflash on not-yet bricked devices!
Sent from my Transformer Pad TF300T using xda app-developers app

vahid_shirvani said:
Hi everyone,
So lets say that the sun would rise from the west tomorrow and Asus/Nvidia released an update for NVFlash compatible with 4.1 and 4.2. Would people including myself who have a bricked tf300t with nonfunctional "fastboot flash" be able to save the tablet or are we simply screwed? (changing motherboard is not worth it in my opinion) Could some body with enough knowledge be kind and explain?
By the way, if you haven't signed the NVFlash petition yet. Do a favor and do it now! Thanks.
Click to expand...
Click to collapse
1. It will only work on UNLOCKED devices
2. It requires access to Fastboot to prepare device first time
3. It won't work on fully bricked devices (See 2.)
from http://androidroot.mobi
http://androidroot.mobi/nvflash-for-tegra3-transformer-tf300t/

tobdaryl said:
1. It will only work on UNLOCKED devices
2. It requires access to Fastboot to prepare device first time
3. It won't work on fully bricked devices (See 2.)
from http://androidroot.mobi
http://androidroot.mobi/nvflash-for-tegra3-transformer-tf300t/
Click to expand...
Click to collapse
I'm not sure why that has to be the case. On the Iconia A500 and the TF101, getting into apx mode with the code allows NVflash to wipe the NAND clean, rewrite the partition table and then rewrite the bootloader. Which retros you back to the state antebellum, which would allow reinstallment of a rom of choice after. This, at least theoretically. I make no pretense at being an expert at it, but perhaps android mobi's is not the only possible way. If truth be told, instructions by mobi's are about as clear as mud for debutants. If enough devils get involved, we may even have an automated device not unlike the APX Flash Tool or BadSector for the A500. Again, I could be missing some critical elements big time. Please enlighten us if you could, tobdaryl. Many thanks.

graphdarnell said:
I'm not sure why that has to be the case. On the Iconia A500 and the TF101, getting into apx mode with the code allows NVflash to wipe the NAND clean, rewrite the partition table and then rewrite the bootloader. Which retros you back to the state antebellum, which would allow reinstallment of a rom of choice after. This, at least theoretically. I make no pretense at being an expert at it, but perhaps android mobi's is not the only possible way. If truth be told, instructions by mobi's are about as clear as mud for debutants. If enough devils get involved, we may even have an automated device not unlike the APX Flash Tool or BadSector for the A500. Again, I could be missing some critical elements big time. Please enlighten us if you could, tobdaryl. Many thanks.
Click to expand...
Click to collapse
Once nvflash is installed what you present is correct (at least that is my understanding - I have only done a simple restore for testing purposes). Look at my signature for a guide to restore with nvflash. The second method presented is what you suggest for the tf101.
The situation to install is different because Asus has locked the tablet to exclude installing nvflash.
I am in the dark as you are. I only know what I can and can't do on my tablet. Otherwise I can pass information provided by others.
My reference is the Nook Tablet. I can delete every partition and rebuild the drive from a blank state this is possible because the tablet can boot from an sdcard.
I had a pm request to provide an nvflash installation guide. I complied but did not present it on xda. The member making the request was pleased and successfully used it to install nvflash. I have since used it to install nvflash on one tablet. Honestly my guide is no better than the guide provided, just a different presentation and can be done by anyone who wishes go step by step through the guide already presented. Just copy and paste the info and do some minor rewording.
I wish I could truly help but I honestly can't. I have come to accept some related info as fact since I have not been able to prove otherwise and have grown tired while chasing dead ends. I don't have the expertise, experience, or hardware to move forward.