Database Develop

Bricked after/during bootloader unlock

So, i've tried to unlock bootloader using this guide: http://forum.xda-developers.com/showthread.php?t=1254225
The first part (up to step 5c) ha gone really smoothly, without any complications.
However when i tried to connect phone to Flashtool all i got was "Device connected with USB debugging off". So then i decided to do the dumbest thing (now i know that) i could do: reboot my phone. Now it's not powering on, so I'm assuming it's bricked.
So my questions:
1. Is it bricked beyond all repair, and i cannot do anything about it, or perhaps there is still some hope left for me?
2. If it's bricked, will service be able to help me? And if yes then how much approximetly would they charge me for that (I'm assuming that my warranty is void because of my attempts)?

kw4ss said:
So, i've tried to unlock bootloader using this guide: http://forum.xda-developers.com/showthread.php?t=1254225
The first part (up to step 5c) ha gone really smoothly, without any complications.
However when i tried to connect phone to Flashtool all i got was "Device connected with USB debugging off". So then i decided to do the dumbest thing (now i know that) i could do: reboot my phone. Now it's not powering on, so I'm assuming it's bricked.
So my questions:
1. Is it bricked beyond all repair, and i cannot do anything about it, or perhaps there is still some hope left for me?
2. If it's bricked, will service be able to help me? And if yes then how much approximetly would they charge me for that (I'm assuming that my warranty is void because of my attempts)?
Click to expand...
Click to collapse
try flashtool
for unlocking bootloader easier way
http://forum.xda-developers.com/showthread.php?t=1267273
flashtool http://forum.xda-developers.com/showthread.php?t=986697
for more info : http://forum.xda-developers.com/showthread.php?t=1399381

kw4ss said:
So, i've tried to unlock bootloader using this guide: http://forum.xda-developers.com/showthread.php?t=1254225
The first part (up to step 5c) ha gone really smoothly, without any complications.
However when i tried to connect phone to Flashtool all i got was "Device connected with USB debugging off". So then i decided to do the dumbest thing (now i know that) i could do: reboot my phone. Now it's not powering on, so I'm assuming it's bricked.
So my questions:
1. Is it bricked beyond all repair, and i cannot do anything about it, or perhaps there is still some hope left for me?
2. If it's bricked, will service be able to help me? And if yes then how much approximetly would they charge me for that (I'm assuming that my warranty is void because of my attempts)?
Click to expand...
Click to collapse
Answers:
1. A cellphone technician with a JTAG/RIFF BOX tool can fix your phone, or the alternative is by replacing the motherboard of your device, you cannot fix at home, that is for sure not unless you have this devices and know how to use it.
2. As for the warranty, just play dumb and say that you dont know what happen to your device. Your warranty is safe as long as they didnt find out that you have mess up the bootlader, IDK much about this, but for me this work.
It happens that, x8 that has been manufactured in 11w26 to 11w37 is problematic and 11w38 beyond is surely bricked if tried to unlock the bootlader. The issue is, they have fixed the security loophole in the bootloader in the later releases. I have 11w44 x8 black that has been hard bricked a few days ago, and I just play dumb in the service center, and they didnt asked anything, it has been covered in the warranty, so free service.

kirmada said:
try flashtool
for unlocking bootloader easier way
http://forum.xda-developers.com/showthread.php?t=1267273
flashtool http://forum.xda-developers.com/showthread.php?t=986697
for more info : http://forum.xda-developers.com/showthread.php?t=1399381
Click to expand...
Click to collapse
Yeah, when i try
Step 1: (Downloads)
A) Download Flash Tool : From http://forum.xda-developers.com/showthread.php?t=920746 or http://www.multiupload.com/GYL7A7XQBT
B) Download S1tool : From http://forum.xda-developers.com/show...0&postcount=26
C) Download Unlocker : From http://forum.xda-developers.com/show...77&postcount=3
Step 2: (Prepare)
A) Unzip all downloaded files
B) Shut Down Phone
C) Open S1tool, Click on DO JOB, Press Back on phone, Connect it to PC.
D) Look For Line "XXXX SIMLOCK CERTIFICATE"
Step 3: (Unlock)
A) Turn the phone on, Connect it with PC in Debugging mode.
B) if XXXX is "NOT RECOGNIZED" then sorry, it can't be unlocked.
C) if XXXX is SEMC then run "msm7227_semc.cmd"
D) if "XXXX SIMLOCK CERTIFICATE" was not found then run "msm7227_Setool2.cmd"
E) Wait...
F) if "Press any key to continue . . ." is found, press any key.
Step 4: (Verify)
A) Shut Down Phone
Click to expand...
Click to collapse
This is basically what I did. However when i try to power on phone it does not respond. Also when I try the second part:
B) Open S1tool, Click on DO JOB, Press Back on phone, Connect it to PC.
C) Look For Line RUNNING S1_EROM VER "x8A029"
D) if x is "r" then it is done, Congrats...
E) if x is "R" then Sorry, Do everything again. or Search in the Frorum for Help
Click to expand...
Click to collapse
nothing happens when I connect phone to PC.
I still have the same message: "PLEASE ATTACH TURNED OFF PHONE NOW"

kirmada said:
try flashtool
for unlocking bootloader easier way
http://forum.xda-developers.com/showthread.php?t=1267273
flashtool http://forum.xda-developers.com/showthread.php?t=986697
for more info : http://forum.xda-developers.com/showthread.php?t=1399381
Click to expand...
Click to collapse
OP is in a state that it cannot be recovered through home remedies, it is a hard bricked phone. I know it because, been there done that.
Symptoms:
doesnt turn on, no LED(RED), cant enter FLASH MODE, no vibrate, nothing at all, almost same as a brick literally.
Cause:
Damaged bootlader

hixvolnutt said:
OP is in a state that it cannot be recovered through home remedies, it is a hard bricked phone. I know it because, been there done that.
Symptoms:
doesnt turn on, no LED(RED), cant enter FLASH MODE, no vibrate, nothing at all, almost same as a brick literally.
Cause:
Damaged bootlader
Click to expand...
Click to collapse
yes, its a hardbrick too i guessed,but everything is worth a try
so its for service center now

hixvolnutt said:
Answers:
1. A cellphone technician with a JTAG/RIFF BOX tool can fix your phone, or the alternative is by replacing the motherboard of your device, you cannot fix at home, that is for sure not unless you have this devices and know how to use it.
2. As for the warranty, just play dumb and say that you dont know what happen to your device. Your warranty is safe as long as they didnt find out that you have mess up the bootlader, IDK much about this, but for me this work.
It happens that, x8 that has been manufactured in 11w26 to 11w37 is problematic and 11w38 beyond is surely bricked if tried to unlock the bootlader. The issue is, they have fixed the security loophole in the bootloader in the later releases. I have 11w44 x8 black that has been hard bricked a few days ago, and I just play dumb in the service center, and they didnt asked anything, it has been covered in the warranty, so free service.
Click to expand...
Click to collapse
So there is still some hope for me! yay!
hixvolnutt said:
OP is in a state that it cannot be recovered through home remedies, it is a hard bricked phone. I know it because, been there done that.
Symptoms:
doesnt turn on, no LED(RED), cant enter FLASH MODE, no vibrate, nothing at all, almost same as a brick literally.
Cause:
Damaged bootlader
Click to expand...
Click to collapse
Yup, not even a light indicating battery charging when i connect it to charger.

kw4ss said:
Yeah, when i try
This is basically what I did. However when i try to power on phone it does not respond. Also when I try the second part:
nothing happens when I connect phone to PC.
I still have the same message: "PLEASE ATTACH TURNED OFF PHONE NOW"
Click to expand...
Click to collapse
There is nothing wrong with the procedures that has been provided by the guide, its just that there is something wrong with your phone, most probably youre x8's mfc is 11w38 or up, "remove your battery, then look for the e.g. 11w38 something like that in the back of your phone, 11 is year 38 is week that it has been manufactured."

hixvolnutt said:
There is nothing wrong with the procedures that has been provided by the guide, its just that there is something wrong with your phone, most probably youre x8's mfc is 11w38 or up, "remove your battery, then look for the e.g. 11w38 something like that in the back of your phone, 11 is year 38 is week that it has been manufactured."
Click to expand...
Click to collapse
11w43...
damn...
someone really should add warning about this somewhere where it would be visible

Any experiences with 11w34???

kw4ss said:
11w43...
damn...
someone really should add warning about this somewhere where it would be visible
Click to expand...
Click to collapse
there is,u did not lookout iguess
http://forum.xda-developers.com/showthread.php?t=1399381

kw4ss said:
11w43...
damn...
someone really should add warning about this somewhere where it would be visible
Click to expand...
Click to collapse
There already one, the thread "warning ahead of unlocking bootloader"...its in this section
Sent from my E15i using xda premium

kirmada said:
there is,u did not lookout iguess
http://forum.xda-developers.com/showthread.php?t=1399381
Click to expand...
Click to collapse
i meant to that thread with guide. because honestly, i only checked things that guide said i have to check, didnt look any further to find out if i can or cannot unlock.
Anyway, looks like it's a trip to service center for me.

hixvolnutt said:
Answers:
1. A cellphone technician with a JTAG/RIFF BOX tool can fix your phone, or the alternative is by replacing the motherboard of your device, you cannot fix at home, that is for sure not unless you have this devices and know how to use it.
2. As for the warranty, just play dumb and say that you dont know what happen to your device. Your warranty is safe as long as they didnt find out that you have mess up the bootlader, IDK much about this, but for me this work.
It happens that, x8 that has been manufactured in 11w26 to 11w37 is problematic and 11w38 beyond is surely bricked if tried to unlock the bootlader. The issue is, they have fixed the security loophole in the bootloader in the later releases. I have 11w44 x8 black that has been hard bricked a few days ago, and I just play dumb in the service center, and they didnt asked anything, it has been covered in the warranty, so free service.
Click to expand...
Click to collapse
How long did you receive your phone after you get sent it to the service center?

I had 11w34 and unlocked bootloader just fine but am afraid of doin it to a new one just bought 11w48, any ways i tried this morning but nothing happen just got a message on cmd adb not a valid command and to press any key to exit
Sent from my E15i using XDA

Hardbircked
I just hardbricked my friend's phone, it was a 11w41, so he is going to claim his warranty tomorrow, do you know if there is some way to unlock bootloader to a 11w41+???

Problems X8.help!!

I got through msm7227_semc the boot loader unlock the phone but then no longer clear.
I'm doing?

My phone is not clear
sorry for my english

omidsys said:
I got through msm7227_semc the boot loader unlock the phone but then no longer clear.
I'm doing?
Click to expand...
Click to collapse
By "no longer clear" you mean what?
You unlocked the boot loader and now the phone does NOT show any light, vibration or things on the screen anymore?
Simply try to describe the problem in a few words so we can get the idea.

got the same issue unlocking bootloader, wait till process is dne completely!
then verify using s1 tool if unlocked!
ur fone shud boot up! hope ur on stock rom
Sent from my E15i using XDA App

B.Jay said:
You unlocked the boot loader and now the phone does NOT show any light, vibration or things on the screen anymore?
.
Click to expand...
Click to collapse
Yes! I have exactly the same
The phone does not react.
The phone does not power.

In this case I'm very sorry to break it over to you, but this is a hard brick - especially if the manufacturing date of your phone is 11W29 or newer (11W30, 11W31, 11W32, ...) - take out the battery and look at the sticker below.
There's no way left by which you can "repair" the phone yourself. You need to either take the phone to a repair shop (if such a thing even exists in Iran) or send it in for repair.
From the hard bricks we observed around here the repair measure will be that the motherboard needs to be replaced past a working one.
Simply take a look in the X8 Q&A section and have a look at the "Warning ahead of unlocking bootloader" thread.

B.Jay said:
In this case I'm very sorry to break it over to you, but this is a hard brick - especially if the manufacturing date of your phone is 11W29 or newer (11W30, 11W31, 11W32, ...) - take out the battery and look at the sticker below.
There's no way left by which you can "repair" the phone yourself. You need to either take the phone to a repair shop (if such a thing even exists in Iran) or send it in for repair.
From the hard bricks we observed around here the repair measure will be that the motherboard needs to be replaced past a working one.
Simply take a look in the X8 Q&A section and have a look at the "Warning ahead of unlocking bootloader" thread.
Click to expand...
Click to collapse
yes.Date of manufacture 11w40
Whether the box is setool?

omidsys said:
yes.Date of manufacture 11w40
Click to expand...
Click to collapse
Yap, that phone is dead.
omidsys said:
Whether the box is setool?
Click to expand...
Click to collapse
I honestly don't get what you mean, but the hard brick you now have in your hands was caused by two facts ...
1. The phone being manufactured 11W40 (way past 11W29 where the trouble starts) means that the chips used in your phone are of a newer revision which have the security hole the boot loader unlock tool uses closed. At the moment you unlock the boot loader you kill the phone.
2. You didn't do your homework in gathering info about the boot loader unlock procedure. While the guys maintaining the "How to unlock the boot loader" are ignorant to inserting the hard brick warning, a simple in-depth reading of the X8 related boards and posts would have spared you this fate.
The only way to get the phone back to work now is to, as written above, take it to a repair shop or to send it to Sony Ericsson.

Try charging the bettery ,full, then begin the whol process again
Sent from my E15i using XDA App

B.Jay said:
Yap, that phone is dead.
I honestly don't get what you mean, but the hard brick you now have in your hands was caused by two facts ...
1. The phone being manufactured 11W40 (way past 11W29 where the trouble starts) means that the chips used in your phone are of a newer revision which have the security hole the boot loader unlock tool uses closed. At the moment you unlock the boot loader you kill the phone.
2. You didn't do your homework in gathering info about the boot loader unlock procedure. While the guys maintaining the "How to unlock the boot loader" are ignorant to inserting the hard brick warning, a simple in-depth reading of the X8 related boards and posts would have spared you this fate.
The only way to get the phone back to work now is to, as written above, take it to a repair shop or to send it to Sony Ericsson.
Click to expand...
Click to collapse
I've pm'ed the op to put the bootloader warning long ago.
To this thread op.. ur phone is dead.. take it to sony center for repair..
Sent from my Android using Tapatalk

joe200 said:
I've pm'ed the op to put the bootloader warning long ago.
Click to expand...
Click to collapse
That was a good idea on your behalf (will give a thanks to you), though it seems the warning didn't stick or wasn't understood in full.
Well, seems to be a somewhat common issue that English seems to be too hard to learn.

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

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.

stream1313 said:
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.
Click to expand...
Click to collapse
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.

sbdags said:
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.
Click to expand...
Click to collapse
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..?

Help needed
stream1313 said:
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..?
Click to expand...
Click to collapse
Hey people... Nobody can help me?

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.

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

lol
ebildude123 said:
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
Click to expand...
Click to collapse
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

stream1313 said:
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
Click to expand...
Click to collapse
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

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 said:
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
Click to expand...
Click to collapse
anybody here?

stream1313 said:
anybody here?
Click to expand...
Click to collapse
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.

sbdags said:
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.
Click to expand...
Click to collapse
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 ((

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.

Kashban said:
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.
Click to expand...
Click to collapse
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.

mr.bin said:
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.
Click to expand...
Click to collapse
Sorry for being late.
That would be great and yes, I do have the tech skills. What do you want me to test?

Kashban said:
That would be great and yes, I do have the tech skills. What do you want me to test?
Click to expand...
Click to collapse
Sent PM with instuctions.
Please keep inform about results.

mr.bin said:
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.
Click to expand...
Click to collapse
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

perpetualxda said:
I also have recently experienced a hard brick on an asus tf700t
Click to expand...
Click to collapse
my solution works only for tf701t not tf700t

mr.bin said:
my solution works only for tf701t not tf700t
Click to expand...
Click to collapse
I have a bricked tf701t and good tech skills if you need additional testers. I'm looking forward to the progress of your solution.

jeneral69 said:
I have a bricked tf701t and good tech skills if you need additional testers. I'm looking forward to the progress of your solution.
Click to expand...
Click to collapse
Sent PM with instuctions.
Please keep inform about results.
If your tab "soft" bricked, then that must help...

[Q] Unlock bootloader wipes all data ?

Hello.
Im abit new to the forum but here goes.
Ive read tons of posts everywhere and there aint any exact answers anywhere to find.
In the past ive never known about the TA and DRM so happy as i am i just unlocked the bootloader on all the phones and still happy. The latest phone is the Xperia Z1. It has been abit buggy to say the least but im hoping software updates will cure this.
Anyway, i rooted my phone and unlocked the bootloader on the .681 firmware and now i am on .757 firmware. Using Doomlords kernel. I thought id check if i could backup my TA partition after unlocking the bootloader. And from what ive read its suppose to be wiped when you unlock the bootloader.
Well it was no problem backing up the TA partion. All files were there and it came out with no errors. So the question, how is this possible ?
I posted this same thing in General, sorry for that but i posted it here now so if a moderator finds this post in general then please delete it.
/Jonas740

If you Unlocked your Bootloader without Backup TA (DRM keys) first, then your DRM Keys are lost forever and you can Backup TA how much you want but there is no DRM Keys at all. The application to Backup TA do not give errors because you can backup partitions with or without DRM Keys, in the case you want switch between Locked and Unlocked Bootloader.
So long story short, you don't have DRM Keys, your warranty is lost forever, you cannot Update via OTA,PC Companion or SUS.

eclyptos said:
If you Unlocked your Bootloader without Backup TA (DRM keys) first, then your DRM Keys are lost forever and you can Backup TA how much you want but there is no DRM Keys at all. The application to Backup TA do not give errors because you can backup partitions with or without DRM Keys, in the case you want switch between Locked and Unlocked Bootloader.
So long story short, you don't have DRM Keys, your warranty is lost forever, you cannot Update via OTA,PC Companion or SUS.
Click to expand...
Click to collapse
The one time I had to use my warranty there was no problem with missing TA.
So there is hope for people without it
Sent from my C6903 using XDA Premium 4 mobile app

well.
HellRoot said:
The one time I had to use my warranty there was no problem with missing TA.
So there is hope for people without it
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
dunno if the previous author saw what i wrote in my post but when i relocked my Xperia V using flashtool i could update with the pc companion or sony update or whats it called nowdays
And funny thing is, i actually have a case at Sony about this phone since i do have some issues with it but i think thats software related since ppl have been getting all sorts of errors from the KitKat firmwares. But i said how it was that i have unlocked bootloader and all that and she replied that my warranty was still valid and i could send it in for them to test it.
And i need to say this. Since sony posts an official way on their webpage, for ANYONE to read about how to unlock the bootloader and they also supply the code for unlocking it. Then i think it shouldnt affect the phone in any way or brake the warranty. (Sure it does say something about that, but all aint reading stuff like that). So if a developer wanted to unlock the phone. Why not have them contacting sony instead.
And surley, DRM keys (i just think sony shouldnt even bother having them) can be put back in if you let Sony do it. They put it there in the first place you know. And in the lovely electronic world we live in we all know that, if Sony can put thoose there, anyone could do it with the knowhow. But since the keys dont really mean anything, not that ive noticed you could really think about what use they actually do. And Sony knows that if ppl cant have the phone it was meant to be even with a unlocked bootloader, they will probably get some other phone or just whine hard enough so that Sony makes a software where everything works the same way with locked or unlocked. Camera stopped to work if you unlocked before 4.3 right ? What can you read about that like everywhere ? Loads of whining and Sony released a software that works just as good with locked or unlocked.
God damn this became a long post. So with this said im just saying. Why even bother in the first place having DRM keys if the rules dont apply anyway ? An everyday user doesent even need them either, he or she doesent even know what rooting or unlocking is anyway. And the ones that do know about it, also know about how to whine to get sony to fix the errors wich an unlock will produce

Jonas740 said:
dunno if the previous author saw what i wrote in my post but when i relocked my Xperia V using flashtool i could update with the pc companion or sony update or whats it called nowdays
And funny thing is, i actually have a case at Sony about this phone since i do have some issues with it but i think thats software related since ppl have been getting all sorts of errors from the KitKat firmwares. But i said how it was that i have unlocked bootloader and all that and she replied that my warranty was still valid and i could send it in for them to test it.
And i need to say this. Since sony posts an official way on their webpage, for ANYONE to read about how to unlock the bootloader and they also supply the code for unlocking it. Then i think it shouldnt affect the phone in any way or brake the warranty. (Sure it does say something about that, but all aint reading stuff like that). So if a developer wanted to unlock the phone. Why not have them contacting sony instead.
And surley, DRM keys (i just think sony shouldnt even bother having them) can be put back in if you let Sony do it. They put it there in the first place you know. And in the lovely electronic world we live in we all know that, if Sony can put thoose there, anyone could do it with the knowhow. But since the keys dont really mean anything, not that ive noticed you could really think about what use they actually do. And Sony knows that if ppl cant have the phone it was meant to be even with a unlocked bootloader, they will probably get some other phone or just whine hard enough so that Sony makes a software where everything works the same way with locked or unlocked. Camera stopped to work if you unlocked before 4.3 right ? What can you read about that like everywhere ? Loads of whining and Sony released a software that works just as good with locked or unlocked.
God damn this became a long post. So with this said im just saying. Why even bother in the first place having DRM keys if the rules dont apply anyway ? An everyday user doesent even need them either, he or she doesent even know what rooting or unlocking is anyway. And the ones that do know about it, also know about how to whine to get sony to fix the errors wich an unlock will produce
Click to expand...
Click to collapse
closed for being a duplicate.
use this link for other thread.
http://forum.xda-developers.com/showthread.php?t=2730169

[Q] Waranty Please Help

Hi guys i have a problem with my phone and i want it repaired. I have changed the Rom a couple of times but now i Flashed it back to stock version 4.0.3. The bootloader is locked and it has no root.I want to know if this can make a problem to the device waranty.If it changed the IMEI or other things. Please help!

IAmHardCore said:
Hi guys i have a problem with my phone and i want it repaired. I have changed the Rom a couple of times but now i Flashed it back to stock version 4.0.3. The bootloader is locked and it has no root.I want to know if this can make a problem to the device waranty.If it changed the IMEI or other things. Please help!
Click to expand...
Click to collapse
Your bootloader isn't really locked, it's just what it shows.You only reverted your ROM to stock ICS, you didn't change the motherboard or anything so IMEI etc. should all be the same.
LG service would probably know that you unlocked the bootloader, even though it looks like it's locked.So be prepared to void your warranty.
PS: What's the problem with your phone anyway? Maybe you can fix it on your own.

ottomanhero said:
Your bootloader isn't really locked, it's just what it shows.You only reverted your ROM to stock ICS, you didn't change the motherboard or anything so IMEI etc. should all be the same.
LG service would probably know that you unlocked the bootloader, even though it looks like it's locked.So be prepared to void your warranty.
PS: What's the problem with your phone anyway? Maybe you can fix it on your own.
Click to expand...
Click to collapse
Thanks a lot. The problem with the phone is that the unlock button doesnt work well. I need to push it pretty hard to unlock the screen.I have a spot on the interior of the screen. I dont know how the hell it appeard there :laugh:. . The phone was held in normal conditions. No exta moisture or something else.And the plastic on the left side is getting off.
There is a way to "really" block the bootloader ?

IAmHardCore said:
Thanks a lot. The problem with the phone is that the unlock button doesnt work well. I need to push it pretty hard to unlock the screen.I have a spot on the interior of the screen. I dont know how the hell it appeard there :laugh:. . The phone was held in normal conditions. No exta moisture or something else.And the plastic on the left side is getting off.
There is a way to "really" block the bootloader ?
Click to expand...
Click to collapse
there is a way, via fuse editing, there is a thread somewhere explaining our bootloader fuse file, and which bytes determine state of bootloader. however, i don't think anyone had done it before. also, be prepared to get your phone back with permanently locked bootloader. LG's servicers have nasty habbit of blowing all the fuses and locking the bootloader forever for some reason.

Flying_Bear said:
there is a way, via fuse editing, there is a thread somewhere explaining our bootloader fuse file, and which bytes determine state of bootloader. however, i don't think anyone had done it before. also, be prepared to get your phone back with permanently locked bootloader. LG's servicers have nasty habbit of blowing all the fuses and locking the bootloader forever for some reason.
Click to expand...
Click to collapse
Thank you a lot i will see what i can do

Search unlock.apk here in the forum (topic title is something like "16 chances to...")... It locks the bootloader too, you just have to root it again.
If I helped you, please hit thanks.

What's your location? Based on the problems you named an unlocked bootloader shouldn't void your warranty if you are in Europe for example. The changes you made to the software most probably aren't the cause of your problems, and therefore the warranty should still be in place. This however depends on your local law.
Sent from my LG-P880 using XDA Free mobile app

balloon27 said:
What's your location? Based on the problems you named an unlocked bootloader shouldn't void your warranty if you are in Europe for example. The changes you made to the software most probably aren't the cause of your problems, and therefore the warranty should still be in place. This however depends on your local law.
Sent from my LG-P880 using XDA Free mobile app
Click to expand...
Click to collapse
I Am From Romania i dont know if they will void my waranty or not but i dont want to risk it. I have tryed to lock it with the fuse blow but i cant do it.
IT keeps saying this : echo fffffffffefeffed And it will be Permanently Locked and All fuses will be blown >/sys/firmware/fuse/odm_reserved
and when i copy into the terminal the bootloader is still unlocked

IAmHardCore said:
I Am From Romania i dont know if they will void my waranty or not but i dont want to risk it. I have tryed to lock it with the fuse blow but i cant do it.
IT keeps saying this : echo fffffffffefeffed And it will be Permanently Locked and All fuses will be blown >/sys/firmware/fuse/odm_reserved
and when i copy into the terminal the bootloader is still unlocked
Click to expand...
Click to collapse
If you're in Romania you should be fine. If they find out you've unlocked it, they'll probably tell you your warranty doesn't cover it, so you'll have to be that annoying Mr. Know It All guy for a bit and tell them why they're wrong (Google it, and there's been a thread about it on this forum as well with some links), they'll be intimidated and will believe you on your word, then they'll fix it and you'll be happy and buy an ice cream with the money you saved.
If you're still planning on relocking just to be safe, I don't think that will work. The repair guys have their ways of hunting down unlocked phones and can probably see yours has been unlocked too.
Sent from my LG-P880 using XDA Free mobile app

balloon27 said:
If you're in Romania you should be fine. If they find out you've unlocked it, they'll probably tell you your warranty doesn't cover it, so you'll have to be that annoying Mr. Know It All guy for a bit and tell them why they're wrong (Google it, and there's been a thread about it on this forum as well with some links), they'll be intimidated and will believe you on your word, then they'll fix it and you'll be happy and buy an ice cream with the money you saved.
If you're still planning on relocking just to be safe, I don't think that will work. The repair guys have their ways of hunting down unlocked phones and can probably see yours has been unlocked too.
Sent from my LG-P880 using XDA Free mobile app
Click to expand...
Click to collapse
Thank You A lot. I thinked about this the phone have fizical problems. So maybe they wont check the bootloader status. Or is it a comonly procedure to check it? Tomorow i will flash it back to 4.0.3 and then maybe i will send it to service.Anyway thank you and lets hope it will be fine :fingers-crossed::fingers-crossed: