[Q] TF701 bricked to APX. blob file issue.

[stream1313]

Dear All,

I hope somebody can help me with hard bricked TF701T.

My sad story: I was very happy when bought brand new TF701. It came with US 4.22 android and with non working RCK, so I was not able to make a proper backup. Device has the following problems before my first upgrdae to 4.3:

1. Periodically, screen slightly blinking (5-10 percent of normal to little more dark and back, for one-two second).
2. Several times my tab was restarting by itself, especially when I was using file manager (ES explorer)
3. Also, when lot of people was able to make an upgrade using asus menu, my tab always replied me that SW is new and upgrade is not needed.

That's why I downloaded the official "US_epaduser_10_26_1_18_UpdateLauncher.zip" from asus site, putted it into the root / and after restart, system message came - new version is available. So I did it, upgrade to 4.3 was successful.

After that, screen stop to blink. But problem with non working RCK still present. So my next step was installation of CWM, using fastboot ADB. Everything was fine, but my first test backup has been not completely fine - after system & files, md5 checksum was generating for more than one hour, and backup was not completely performed (I've interrupted the process after one hour "md5")

My last successful step was rooting of my poor tab..

Finally, I obtained the 4.3 with root access, working CWM and no more 3 of listed above problems. The only md5 issue was pending.

Than I have performed my FATAL error.. I start playing with nvram - thanks to easy flasher tool (but it is my fault, no question)

As result, I have TOTALLY DEAD TF701. Boot loop with ASUS logo, fastboot (- & power) is not available anymore;

The only thing I have it is APX availability, but according to my internet research there is no chance to unbrick tf701t for now. At list NvFlash is not recognized my device. Latest version of NvFlash tool answering me:

*************************************************************

C:\nvflash-tools-win32>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================

Waiting for device in APX mode...
[=] Chip UID: 0x2000000016ff0440
[-] Failed to read RCMVERS from blob file.

*************************************************************

(If smb knows what must be in the RCMVERS file - digital signature, CPU info or what? pls reply me)

Please, if somebody has same problem and there is any chance to unbrick my tab, reply me!!!
Btw, I have tried to call asus support, the only help I obtain was a negative experience.

 

[sbdags]

Dear All,

I hope somebody can help me with hard bricked TF701T.

My sad story: I was very happy when bought brand new TF701. It came with US 4.22 android and with non working RCK, so I was not able to make a proper backup. Device has the following problems before my first upgrdae to 4.3:

1. Periodically, screen slightly blinking (5-10 percent of normal to little more dark and back, for one-two second).
2. Several times my tab was restarting by itself, especially when I was using file manager (ES explorer)
3. Also, when lot of people was able to make an upgrade using asus menu, my tab always replied me that SW is new and upgrade is not needed.

That's why I downloaded the official "US_epaduser_10_26_1_18_UpdateLauncher.zip" from asus site, putted it into the root / and after restart, system message came - new version is available. So I did it, upgrade to 4.3 was successful.

After that, screen stop to blink. But problem with non working RCK still present. So my next step was installation of CWM, using fastboot ADB. Everything was fine, but my first test backup has been not completely fine - after system & files, md5 checksum was generating for more than one hour, and backup was not completely performed (I've interrupted the process after one hour "md5")

My last successful step was rooting of my poor tab..

Finally, I obtained the 4.3 with root access, working CWM and no more 3 of listed above problems. The only md5 issue was pending.

Than I have performed my FATAL error.. I start playing with nvram - thanks to easy flasher tool (but it is my fault, no question)

As result, I have TOTALLY DEAD TF701. Boot loop with ASUS logo, fastboot (- & power) is not available anymore;

The only thing I have it is APX availability, but according to my internet research there is no chance to unbrick tf701t for now. At list NvFlash is not recognized my device. Latest version of NvFlash tool answering me:

*************************************************************

C:\nvflash-tools-win32>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================

Waiting for device in APX mode...
[=] Chip UID: 0x2000000016ff0440
[-] Failed to read RCMVERS from blob file.

*************************************************************

(If smb knows what must be in the RCMVERS file - digital signature, CPU info or what? pls reply me)

Please, if somebody has same problem and there is any chance to unbrick my tab, reply me!!!
Btw, I have tried to call asus support, the only help I obtain was a negative experience.

As far as I am aware the nvflash tools are not yet released for the TF701T, so who knows what bootloader you have now flashed. Unless some miracle happens you look hard bricked

I'm guessing you didn't notice the devices nvflash supports which is an unfortunate and costly mistake.

 

[stream1313]

As far as I am aware the nvflash tools are not yet released for the TF701T, so who knows what bootloader you have now flashed. Unless some miracle happens you look hard bricked

I'm guessing you didn't notice the devices nvflash supports which is an unfortunate and costly mistake.

Thank you for reply. Definitely it's my fault for 100%, because I've not checked the nvflash possibility, before I start playing with blob Really stupid story, especially I have already performed all the needed things as rooting, update, CWM.

The main reason I'm posting here is to check, does anybody who has a deep knowledge of such devices design, already experienced with TF701T recovery?

I hope at list single person in the world (not counting asus engineers, as far as their company politic became similar to microsoft or oracle) knows the backdoor way to this tab recovery..?

 

[stream1313]

Help needed

Thank you for reply. Definitely it's my fault for 100%, because I've not checked the nvflash possibility, before I start playing with blob Really stupid story, especially I have already performed all the needed things as rooting, update, CWM.

The main reason I'm posting here is to check, does anybody who has a deep knowledge of such devices design, already experienced with TF701T recovery?

I hope at list single person in the world (not counting asus engineers, as far as their company politic became similar to microsoft or oracle) knows the backdoor way to this tab recovery..?

Hey people... Nobody can help me?

 

[stream1313]

Asus help us

Hello ASUS !!!

You have to HELP us, in order to keep your consumer with you. Other vice people will start to think that your ASUS brand is not a trustful brand anymore. Using such tricks as providing consumer with possibility to open a "Pandora's box" with bootloader unlock, and after you pushing consumer to pay about 300 $ for "motherboard replacing".

Following such kind of policy you will collect some money but definitely you will loose much more.

Sincerely,
Stream1313

PS: I was started to use the "unlock" etc not because I do not have other business t do but because of the serious problem in your DEFAULT STOCK software.

To: Moderator - please do not delete this post, hopefully some ASUS people will read it.

 

[ebildude123]

This is not asus' fault at all. When you unlock your bootloader you void your warranty, as with all devices not just asus transformers. When you modify your device, and tamper with it, its no longer what asus sold it to you as. If you used easy flasher which is for the tf101 and not 701, there is no one to blame for this mistake but yourself. Especially when you flash a bootloader for a different device. Unless you have a JTAG theres not much to do. Even then who knows. Im not bashing you here, just so you know. Good luck with your device, although im afraid its a pretty expensive paperweight by now.

Sent from my GS3 on PAC 4.4 using Tapatalk 4

 

[stream1313]

lol

This is not asus' fault at all. When you unlock your bootloader you void your warranty, as with all devices not just asus transformers. When you modify your device, and tamper with it, its no longer what asus sold it to you as. If you used easy flasher which is for the tf101 and not 701, there is no one to blame for this mistake but yourself. Especially when you flash a bootloader for a different device. Unless you have a JTAG theres not much to do. Even then who knows. Im not bashing you here, just so you know. Good luck with your device, although im afraid its a pretty expensive paperweight by now.

Sent from my GS3 on PAC 4.4 using Tapatalk 4

Dear ebildude123,

Seems you have some relationships with ASUS, is it? See, I'm not trying to say that it's not a my fault. If you read my post carefully, it is clearly described that I'm confirming - it is 100% my fault. but I want to say about other things:

At first, I started because of the following ASUS DEFAULT PROBLEM's: suddenly screen was blinking, w/o any reason; tab was restarting by itself, at list once per 2-3 days; Default backup was not working, battery life time was low etc.

My main message is: ASUS distributed the unlock SW on site, together with USER LEVEL SW. It is incorrect, IMHO. They should distribute it within advanced users and developers, using some more safe mechanism. As minimum they have to sign this download as potentially DANGEROUS for unexperienced user.

But currently it is open to everybody so it is like a Pandora's box, which is asking - "open me" and as result many of people getting hard bricked tabs. Then, ASUS forcing them to pay 300$ or whatever. Actually, I do not crying too much for my bricked device (I have my laptop and desktop with me, as well as my linux server) Also I know that I just need to wait a little more for compatible nvflash.. ...but I do not think that I will purchase another ASUS device in the future..

IMHO - if you DISTRIBUTING on your site the bootloader unlock tool, you have to provide nvflash or any other way to restore the tab / phone, but not pushing stupid idea about "mainboard replacement" for almost device price itself. So you have your opinion - and it is mine. Ok? Good luck

 

[ebildude123]

Dear ebildude123,

Seems you have some relationships with ASUS, is it? See, I'm not trying to say that it's not a my fault. If you read my post carefully, it is clearly described that I'm confirming - it is 100% my fault. but I want to say about other things:

At first, I started because of the following ASUS DEFAULT PROBLEM's: suddenly screen was blinking, w/o any reason; tab was restarting by itself, at list once per 2-3 days; Default backup was not working, battery life time was low etc.

My main message is: ASUS distributed the unlock SW on site, together with USER LEVEL SW. It is incorrect, IMHO. They should distribute it within advanced users and developers, using some more safe mechanism. As minimum they have to sign this download as potentially DANGEROUS for unexperienced user.

But currently it is open to everybody so it is like a Pandora's box, which is asking - "open me" and as result many of people getting hard bricked tabs. Then, ASUS forcing them to pay 300$ or whatever. Actually, I do not crying too much for my bricked device (I have my laptop and desktop with me, as well as my linux server) Also I know that I just need to wait a little more for compatible nvflash.. ...but I do not think that I will purchase another ASUS device in the future..

IMHO - if you DISTRIBUTING on your site the bootloader unlock tool, you have to provide nvflash or any other way to restore the tab / phone, but not pushing stupid idea about "mainboard replacement" for almost device price itself. So you have your opinion - and it is mine. Ok? Good luck

Haha no relationship with Asus. I guarantee it. While I agree unlock tool shouldn't be thrown around, that's not what bricks your device, it's what you flash that does. Personally I think they should use fastboot unlock instead but meh. Yes of course everyone has their own opinions. I respect yours and hope you respect mine as well. Good luck with nvflash but I have doubts your current blob would work even if they made a tool compatible with tf701 tegra4.

Sent from my GS3 on PAC 4.4 using Tapatalk 4

 

[stream1313]

lol, hope your post do not really had any Asus roots)
now I need advice, if possible..
what do you think about Linux installation, which is described in network, according to them even bricked tf701 is recoverable?
Pls, if somebody already experienced, reply me!

Sent from my Xperia Arc S using xda app-developers app

 

[stream1313]

lol, hope your post do not really has any Asus roots)
now I need advice, if possible..
what do you think about Linux installation, which is described in network, according to them even bricked tf701 is recoverable?
Please, if somebody already experienced, reply me...

Sent from my Xperia Arc S using xda app-developers app

anybody here?

 

[sbdags]

anybody here?

APX mode with no nvflash blobs = hard bricked device. Your device needs specific blobs encrypted with the key. You can't even boot to working bootloader.

Even Asus don't **** around with them they just replace the mother board.

Suggest you do the same, it's THE ONLY WAY you are going to get your device back. Linux will not help you here.

 

[stream1313]

APX mode with no nvflash blobs = hard bricked device. Your device needs specific blobs encrypted with the key. You can't even boot to working bootloader.

Even Asus don't **** around with them they just replace the mother board.

Suggest you do the same, it's THE ONLY WAY you are going to get your device back. Linux will not help you here.

Hi sbdags,

Thanks for your message, currently I just trying to keep my brick charged, to prevent battery dead.. Will wait till smb from ASUS or from outside will broke the bloody encrypted bootloader, because I do not have possibility to replace he main board ((

 

[Kashban]

Well, three years later and my TF701 bricked itself over night. Only thing I see is APX in the windows device manager. I managed to get a driver for that but am now stuck with the next steps, if there are any at all.

 

[mr.bin]

Well, three years later and my TF701 bricked itself over night. Only thing I see is APX in the windows device manager. I managed to get a driver for that but am now stuck with the next steps, if there are any at all.

yep!
maybe i got a solution, but untested for mass unbrick)
i'm already unbrick few devices.
need someone with bricked device and tech skills to test for public use.

 

[Kashban]

yep!
maybe i got a solution, but untested for mass unbrick)
i'm already unbrick few devices.
need someone with bricked device and tech skills to test for public use.

Sorry for being late.

That would be great and yes, I do have the tech skills. What do you want me to test?

 

[mr.bin]

That would be great and yes, I do have the tech skills. What do you want me to test?

Sent PM with instuctions.
Please keep inform about results.

 

[perpetualxda]

yep!
maybe i got a solution, but untested for mass unbrick)
i'm already unbrick few devices.
need someone with bricked device and tech skills to test for public use.

I also have recently experienced a hard brick on an asus tf700t running KatKiss-7.1_TF700T_026
APX mode & only a TWRP backup

I would also like to try your method to unbrick
Thanks in advance

 

[mr.bin]

I also have recently experienced a hard brick on an asus tf700t

my solution works only for tf701t not tf700t

 

[jeneral69]

my solution works only for tf701t not tf700t

I have a bricked tf701t and good tech skills if you need additional testers. I'm looking forward to the progress of your solution.

 

[mr.bin]

I have a bricked tf701t and good tech skills if you need additional testers. I'm looking forward to the progress of your solution.

Sent PM with instuctions.
Please keep inform about results.
If your tab "soft" bricked, then that must help...