Related
Eee Pad is bricked. Here's the story. I used http://forum.xda-developers.com/showthread.php?t=1125714 (pure root) to root the device about less than a month ago.
Just today i saw an update for the OS and i updated, but when i turned it back on it was bricked. WHAT DO I DO? PLEASE HELP
try this
turn off your TF
plug it to your computer
turn on your TF while holding the "up" volume key
if your computer detects your TF, then good news, there's hope for you. your TF is not bricked, and you still have access to NVFLASH.
you can use it to restore your TF into a functional state in many ways.
one of those ways is enumerated here: WARNING, this will erase all your data.
http://forum.xda-developers.com/showthread.php?t=1123429
remember that the image files gets extracted to the same folder as the .bat or .sh files, (some people misplace them and think it didn't work)
Sent from my Transformer TF101 using Tapatalk
ilive12 said:
Eee Pad is bricked. Here's the story. I used http://forum.xda-developers.com/showthread.php?t=1125714 (pure root) to root the device about less than a month ago.
Just today i saw an update for the OS and i updated, but when i turned it back on it was bricked. WHAT DO I DO? PLEASE HELP
Click to expand...
Click to collapse
I agree with finalhit about how to fix it, but am curious what you actually did where you say " Just today i saw an update for the OS and i updated ". ?
Did you apply an OTA update, apply some other thing , and if so, which other thing? You might just be a quick partition 5 nvflash from success (restoring CWM to a reasonable version for your system). Which flavor of TF? US, WW, TW? more info.
THANKS IT WORKED!
Well actually it was my father who updated. I rooted his TF for him (to get netflix working) back on 3.1, and today he just decided to update OTA to 3.2 (the US version.). Glad its working again or i would have been screwed
Hello, dear fans
Yes.... I think also that TF700 is piece of crap and not solid tablet but anyway.... I have Asus Transformer Pad Infinity (TF700) with last official update (WW_epad-user-10.4.4.25.zip) JB stock ROM... But the tablet is still laggy and unstable. I want try to another ROM. Unofrtunatelly, I cannot unlock my device (Maybe you see the message: An unknown error occurs, which may be a network connection issue. please wait and try again later). If I cannot unlock I cannot get the ROOT on JB also I saw in some thred that people with earlier or equal ROM with 9.4.5.26 can unlock the device and in 9.4.5.30 and later NOT. But I cannot flash to .26 ROM because JB needs almost .30 ROM and later (I tried writing blob via fastboot and update via EP201_768_SDUPDATE.zip on SDcard also... But I can install only .30 ROM as MINIMUM! But on this ROM I cannot unlock my device ALSO. I really try anything... Any ideas? Of course, I wrote very ugly mail to ASUS support but without effects (I tried before viac HOT LINE but without any response!) This tablet is reaaaaly piece of trash. Thanks for advice.
In that case I'll give ya $100 for it.
Sent from my Galaxy Nexus using Tapatalk 2
zrebec said:
Hello, dear fans
Yes.... I think also that TF700 is piece of crap and not solid tablet but anyway.... I have Asus Transformer Pad Infinity (TF700) with last official update (WW_epad-user-10.4.4.25.zip) JB stock ROM... But the tablet is still laggy and unstable. I want try to another ROM. Unfortunately, I cannot unlock my device (Maybe you see the message: An unknown error occurs, which may be a network connection issue. please wait and try again later). If I cannot unlock I cannot get the ROOT on JB also I saw in some thread that people with earlier or equal ROM with 9.4.5.26 can unlock the device and in 9.4.5.30 and later NOT. But I cannot flash to .26 ROM because JB needs almost .30 ROM and later (I tried writing blob via fastboot and update via EP201_768_SDUPDATE.zip on SDcard also... But I can install only .30 ROM as MINIMUM! But on this ROM I cannot unlock my device ALSO. I really try anything... Any ideas? Of course, I wrote very ugly mail to ASUS support but without effects (I tried before via HOT LINE but without any response!) This tablet is really a piece of trash. Thanks for advice.
Click to expand...
Click to collapse
Well my friend not exactly the best words to start with if needing help from the many fine members of this forum.
The unlock tool will eventually work if that's what you want to do.
Personally your being "really ugly" to Asus thru e-mail could be why they remain unresponsive.
If you could perhaps take the calm approach those trying to help would be much more willing.
absurd paradox
Unfortunately I can understand where all these negative feelings derive from.
I am the rightful owner of a tf700 too.
To be quite frank (and I won't surprise anyone), I am not pleased.
There is no reason why I can't enjoy a smooth and flowing experience.
There is no reason why in order to make the best out of the tf700 it is recommended that I flash a custom rom.
I refuse to unlock my tf700 because there is no reason why I should void my warranty, trying to fix it - this is an absurd paradox!
It is about time someone filed a class action in order to stop this "tf700 incident",
so Asus will start to make their excuses in court or maybe solve this unfortunate condition,
once and for good.
cheers.
Nothing stopping you from filing a class action lawsuit is there?
Or you could just take control and unlock and flash a custom ROM and be done with it....
Choice is yours as Asus are not going to help you.
wish it was that simple
I wish flashing a clean rom was that simple, but there is no plain guide.
Everywhere I go (including xda forums) there are "half explanations" and I am tired of trying to solve this puzzle.
For example, I read a guide which explains how to unlock and install a custom recovery using an "adb tool",
but there is no explanation how to install the newest version of TWRP, which is required for cromi 3.4.X.
Anyone know a plain and full guide for 10.4.4.25 build?
http://forum.xda-developers.com/showthread.php?t=2088176
No very ugly
OK, that wasnt very ugly mail, just I wrote to ASUS that I tried contact HOTLINE twotimes and nobody response me I was very frustrated that I cannot unlock my tablet Can someone explain me, why doesn't exists alternative way around unlock? The processor is crypted or what? Thanks
zrebec said:
OK, that wasn't very ugly mail, just I wrote to ASUS that I tried contact HOTLINE two times and nobody response me I was very frustrated that I cannot unlock my tablet
Can someone explain me, why doesn't exists alternative way around unlock?
The processor is encrypted or what?
Thanks
Click to expand...
Click to collapse
A work around for the unlock isn't available.
Seems as though the key for the bootloader is encrypted very well.
Until someone leaks the key to the internet we're stuck.
My understanding is:
Asus wants the embedded serial for any tablet requesting a bootloader unlock.
The serial is registered with Asus from an outside server database.
Asus voids the warranty then shuts off OTA's because they don't want to push updates over any customisation to the tablets firmware.
This would most likely result in a bricked\non-functioning device.
Asus knows people inherently re-code devices with non-manufacturer firmware and risky applications.
The manufacturer is saying to the buyer we can't be responsible for user induced damage.
zrebec said:
Hello, dear fans
Yes.... I think also that TF700 is piece of crap and not solid tablet but anyway.... I have Asus Transformer Pad Infinity (TF700) with last official update (WW_epad-user-10.4.4.25.zip) JB stock ROM... But the tablet is still laggy and unstable. I want try to another ROM. Unofrtunatelly, I cannot unlock my device (Maybe you see the message: An unknown error occurs, which may be a network connection issue. please wait and try again later). If I cannot unlock I cannot get the ROOT on JB also I saw in some thred that people with earlier or equal ROM with 9.4.5.26 can unlock the device and in 9.4.5.30 and later NOT. But I cannot flash to .26 ROM because JB needs almost .30 ROM and later (I tried writing blob via fastboot and update via EP201_768_SDUPDATE.zip on SDcard also... But I can install only .30 ROM as MINIMUM! But on this ROM I cannot unlock my device ALSO. I really try anything... Any ideas? Of course, I wrote very ugly mail to ASUS support but without effects (I tried before viac HOT LINE but without any response!) This tablet is reaaaaly piece of trash. Thanks for advice.
Click to expand...
Click to collapse
Another woe-is-me post! Someone please get me a hankie, quick!
zrebec said:
OK, that wasnt very ugly mail, just I wrote to ASUS that I tried contact HOTLINE twotimes and nobody response me I was very frustrated that I cannot unlock my tablet Can someone explain me, why doesn't exists alternative way around unlock? The processor is crypted or what? Thanks
Click to expand...
Click to collapse
First of all you could use the search button
Here is a thread where I specified how I got my tablet unlocked: http://forum.xda-developers.com/showthread.php?t=2146543
Just keep in mind that the Asus Support employees are not personally responsible that the MDM-server in Taiwan does not know your tablet. Don't act like a jackass and don't act like mister-know-it-all, then they will help you, like they helped me.
I wish flashing a clean rom was that simple, but there is no plain guide.
Everywhere I go (including xda forums) there are "half explanations" and I am tired of trying to solve this puzzle.
Click to expand...
Click to collapse
These forums here provide all information one needs to unlock/ root/ install custom ROMs. I got all information from here and I did not have any problem whatsoever.
You know, people here are willing to share their experience and to help out each other, but the burden to do the work is on you. Also the risk of bricking your device is on you.
Just don't expect anybody to do your work.
As a matter of fact, installing custom ROMs on the TF700 is not trivial. You do need ADB and Fastboot to flash a recovery first. Also you have to have some basic knowledge about how computers work in general and about Android devices.
Even as complete noob, you can find all needed information here. So either you take your time and educate yourself - like I did - or you use the stock ROM or you hire somebody who does the work for you.
Root it but keep it locked! I was loosing sleep at night because I thought I was suckered into believing this was a quality machine and its got tons of glitches, no doubt. But they are mainly lack-of-RAM related. If you root, and disable most of your startups, you can get a clean 500MB after boot, and that makes all the difference in the world, trust me. I was in you boots and was actually dreaming about getting an iPad (please forgive me guys). Honestly, I was sick to my stomach then the rage set in. I decided to learn and root before throwing this POS on ebay or craigs list, and starting over with another brand, probably an Apple, I was so hurt by lack of quality and testing/debug.
Like day and night! Now I love this thing. Hasn't had a random reboot, app crash, etc. in nearly a month now. Before I was getting 5 per day. Its an amazing difference attributed to the OS and apps having room (RAM) to run in. Whoever decided that 1GB RAM for a 4-core droid tablet was enough should be tarred and feathered then shot in the head twice!!! If it had been 2GB instead of 1GB we wouldn't be having this discussion at all.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Unlocked! Yay!
Hello dears,
so I have my tablet Unlocked now... I forgot.... You must register account and then register tablet here https://vip.asus.com/login.aspx?. So maybe this can help to someone... OK, I have installed Clean Rom Inherited now and it looks and works fine Thanks to all.
So steps to reproduce:
1) Create account on https://vip.asus.com/login.aspx?.
2) Register device after that
3) Download Unlock Device App: Unlock boot loader from Android -> Utilities from http://support.asus.com/download.as...Pad Infinity TF700T&hashedid=fq2B3oq64av1O95u
4) Run the application
5) Tick the you understand that your warranty is now VOID
6) Type your google account login and password
7) After restart you should see in up-left corner message "Device is unlocked"
8) Enjoy
Update: Fixed my last known problem which was wifi streaming movies to the device from external source (wifi HDD or network connected storage). Got Dice Player, that's all I have to say. Now EVERYTHING is working perfectly. No more random reboots, app issues, conflicting apps, got plenty of RAM, got all my desired startups loaded including System Tuner with a few tweaks added, Browser2RAM, RAM booster, etc. and device runs fast, smooth, and without any "glitches". I finally have achieved rooted stability and will now take a rest and enjoy this tablet a bit before I do anything more to it because this has been a hair-puller to get to this point. Finally very happy with this device but I had to venture far from stock to get here and it was worth it.
By the way, what day of the week is it?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
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.
Hi I managed to brick a locked tf300 with JB 4.2.1 via ota. I have no idea how to unbrick it and I can't find any solution I really have no idea evenhow to flash a stock rom
godutch said:
Hi I managed to brick a locked tf300 with JB 4.2.1 via ota. I have no idea how to unbrick it and I can't find any solution I really have no idea evenhow to flash a stock rom
Click to expand...
Click to collapse
Nobody has found a solution, we're stuck for now
I managed to fix it by flashing the image blob from stock firmware in fastboot, I found a guide googling a bit more
godutch said:
I managed to fix it by flashing the image blob from stock firmware in fastboot, I found a guide googling a bit more
Click to expand...
Click to collapse
How did you do that? Could you link me the guide
Doesn't matter, I've seen that you bricked it in a different way
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?
BR
Mihnea
matt95 said:
How did you do that? Could you link me the guide
Doesn't matter, I've seen that you bricked it in a different way
Click to expand...
Click to collapse
For all those looking for a solution (in some cases): http://www.androidauthority.com/transformer-pad-tf300t-restore-stock-firmware-108016/
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.