[Q] Can You Flash Recovery On Locked Transformer? - Asus Eee Pad Transformer Prime

First off, I am learning everything on the fly, so keep this in mind if my question sounds stupid. It's my wife's Prime and it just wouldn't boot one day.The best I can tell it had JB 4.1.1 and it is locked. I can access the bootloader with 4 options. There are no longer any recovery options on the TF201 itself. I am trying to flash a recovery from fastboot, but when it goes to write I get a failed message-invalid state error even though the blue bar goes to full on the tablet. I assume that the reason I am unable to flash the tablet is because it is locked and at this point there is no way to unlock it. I just need someone to confirm my assumption that the device is permanently bricked so I can stop the hours of research and return to a normal life. Thanks for any help.

ghiotom said:
First off, I am learning everything on the fly, so keep this in mind if my question sounds stupid. It's my wife's Prime and it just wouldn't boot one day.The best I can tell it had JB 4.1.1 and it is locked. I can access the bootloader with 4 options. There are no longer any recovery options on the TF201 itself. I am trying to flash a recovery from fastboot, but when it goes to write I get a failed message-invalid state error even though the blue bar goes to full on the tablet. I assume that the reason I am unable to flash the tablet is because it is locked and at this point there is no way to unlock it. I just need someone to confirm my assumption that the device is permanently bricked so I can stop the hours of research and return to a normal life. Thanks for any help.
Click to expand...
Click to collapse
No not possible with out unlocking - you can flash the stock asus blob which is signed and it will update your recovery back to stock but that is it.

I'm not sure what you're saying. You said it can't be flashed if the bootloader is locked, then you say I can flash a stock Asus blob.

ghiotom said:
I'm not sure what you're saying. You said it can't be flashed if the bootloader is locked, then you say I can flash a stock Asus blob.
Click to expand...
Click to collapse
Yes exactly that. You can't flash anything customised on an locked boot loader.

I didn't mention that I also tried to install the stock Asus firmware from their website using both the Fastboot method as well as a microSD card, but neither method worked. You're saying that flashing the stock firmware should work.The fact that it didn't, leads me to believe that there is probably something wrong on a hardware level and a motherboard replacement is the only option.

ghiotom said:
I didn't mention that I also tried to install the stock Asus firmware from their website using both the Fastboot method as well as a microSD card, but neither method worked. You're saying that flashing the stock firmware should work.The fact that it didn't, leads me to believe that there is probably something wrong on a hardware level and a motherboard replacement is the only option.
Click to expand...
Click to collapse
Not sure you can fastboot flash it no but you can certainly unzip it, rename it to whatever they said to and drop it on the microsd, go to bootloader, hit rck and it should flash it. You can only do this with Asus signed files.

Related

[Q] viperMOD PrimeTime v4.5 Fail on .21 - What next?

I just got a TF201. It's my first Android device, so please bear with me for this newbie issue. I wanted to root it so I tried PrimeTime without considering that I was already running version .21. Obviously it screwed up... The worst that happened is seeing a caput droid while trying to load CWM. Don't know what's the deal with that, I guess it just didn't install properly.
The device otherwise still boots fine so I'm left wondering what to do with it. Can someone explain what PrimeTime does exactly, I'd like to know in what state is my TP now...
Is there a risk that an OTA could brick it?
Can I fix CWM and flash a rooted firmware (i.e. Virtuous)?
Can I factory reset everything and lock the bootloader?
Thanks
install touch cwm or twrp and it should be fine, obiesly ota will brick it. Dunno about reseting data.
Sent from my Transformer Prime TF201 using XDA Premium App
vanista said:
I just got a TF201. It's my first Android device, so please bear with me for this newbie issue. I wanted to root it so I tried PrimeTime without considering that I was already running version .21. Obviously it screwed up... The worst that happened is seeing a caput droid while trying to load CWM. Don't know what's the deal with that, I guess it just didn't install properly.
The device otherwise still boots fine so I'm left wondering what to do with it. Can someone explain what PrimeTime does exactly, I'd like to know in what state is my TP now...
Is there a risk that an OTA could brick it?
Can I fix CWM and flash a rooted firmware (i.e. Virtuous)?
Can I factory reset everything and lock the bootloader?
Thanks
Click to expand...
Click to collapse
Another example of what may happen when people don't have patience, not reading everything.
Q: Is there a risk that an OTA could brick it?
Q: Can I fix CWM and flash a rooted firmware (i.e. Virtuous)?
A: Have you used ASUS Unlocker Tool to unlock your bootloader (thus voiding your warranty)? If you did, the awnser is yes for the first 2 questions.
Q: Can I factory reset everything and lock the bootloader?
A: Relocking bootloader isn't possible; You can factory reset everything through Android UI/stock rom only if you didn't install CWM as of yet.
bk201doesntexist said:
Q: Can I factory reset everything and lock the bootloader?
A: Relocking bootloader isn't possible; You can factory reset everything through Android UI/stock rom only if you didn't install CWM as of yet.
Click to expand...
Click to collapse
Thanks for the reply
Can you elaborate, I don't know how far PrimeTime went trying to install CWM. What happens if I reset with CWM present? Can it be cleaned?
vanista said:
Thanks for the reply
Can you elaborate, I don't know how far PrimeTime went trying to install CWM. What happens if I reset with CWM present? Can it be cleaned?
Click to expand...
Click to collapse
I think that if you try to factory reset with CWM installed it will bootloop/brick, I've read it somewhere here on xda.
Again, CWM can only be installed if bootloader has been unlocked. If you didn't and PrimeTime doesn't as well, you cannot have cwm installed.
I believe there was some information laying around about returning to stock, not sure if it's possible to return to stock recovery after flashing cwm.
bk201doesntexist said:
Again, CWM can only be installed if bootloader has been unlocked. If you didn't and PrimeTime doesn't as well, you cannot have cwm installed.
Click to expand...
Click to collapse
My bootloader is unlocked but I'm not rooted, apparently I cannot install CWM from ROM Manager. Is it possible through fastboot? When I try to go into recovery mode I get the laid down dead droid... Is that caused by a faulty CWM or just that I don't have a recovery image anymore?
I modified ViperMODS tool to add Xda user wolf849's method of downgrading a transformer without root, so you can use this http://forum.xda-developers.com/showpost.php?p=25508554&postcount=52 to downgrade to .15 then root, then install OTA rootkeeper then update via ota to .21 again. Or you can just unlock and install cwm if you want to void warranty.
Okay this is just getting more and more confusing. Everywhere I read about CWM and custom ROMs it says you have to be rooted. If that is true then I'm in a dead end because I cannot downgrade to .15 without bricking and I can't properly install CWM either.
I finally found some official doc on fastboot source.android.com/source/building-devices.html , if its accurate you don't even need CWM to flash a custom rom. That seems to be much more reliable. Isn't CWM just a wrapper for what can all be done manually through adb??
Finally found some precise instructions... androidroot.mobi/2012/02/22/introducing-cwm-for-asus-transformer-prime/
Instructions for non-rooted Primes (or those who’d rather use fastboot):
Get fastboot from here, and extract it.
Download the blob file (tfp_CWM5_androidroot.blob), and put it in the same folder as where you extracted fastboot.
Power off your prime.
Boot with Volume-down pressed. Wait when you see text appearing. The prime will then allow you to start “fastboot”.
Open up a command-line prompt, and navigate to where you extracted fastboot with “cd”.
Enter the following commandline to flash recovery: fastboot -i 0x0b05 flash recovery tfp_CWM5_androidroot.blob
Profit!
vanista said:
My bootloader is unlocked but I'm not rooted, apparently I cannot install CWM from ROM Manager. Is it possible through fastboot? When I try to go into recovery mode I get the laid down dead droid... Is that caused by a faulty CWM or just that I don't have a recovery image anymore?
Click to expand...
Click to collapse
you awnsered yourself below
bpear96 said:
I modified ViperMODS tool to add Xda user wolf849's method of downgrading a transformer without root, so you can use this http://forum.xda-developers.com/showpost.php?p=25508554&postcount=52 to downgrade to .15 then root, then install OTA rootkeeper then update via ota to .21 again. Or you can just unlock and install cwm if you want to void warranty.
Click to expand...
Click to collapse
he's unlocked, he can't run an official blob, that method does not work for him
vanista said:
Okay this is just getting more and more confusing. Everywhere I read about CWM and custom ROMs it says you have to be rooted. If that is true then I'm in a dead end because I cannot downgrade to .15 without bricking and I can't properly install CWM either.
I finally found some official doc on fastboot source.android.com/source/building-devices.html , if its accurate you don't even need CWM to flash a custom rom. That seems to be much more reliable. Isn't CWM just a wrapper for what can all be done manually through adb??
Click to expand...
Click to collapse
don't look on source.android.com, aosp doesn't support transformer prime directly, and as you might have noticed, fastboot commands are a bit different for the prime that of galaxy nexus, for example.
why some say you need to be rooted to flash cwm? because they use ROM Manager nice UI to do it, instead of teaching people how to do it without an UI. Rom Manager needs root, as you know.
vanista said:
Finally found some precise instructions... androidroot.mobi/2012/02/22/introducing-cwm-for-asus-transformer-prime/
Instructions for non-rooted Primes (or those who’d rather use fastboot):
Get fastboot from here, and extract it.
Download the blob file (tfp_CWM5_androidroot.blob), and put it in the same folder as where you extracted fastboot.
Power off your prime.
Boot with Volume-down pressed. Wait when you see text appearing. The prime will then allow you to start “fastboot”.
Open up a command-line prompt, and navigate to where you extracted fastboot with “cd”.
Enter the following commandline to flash recovery: fastboot -i 0x0b05 flash recovery tfp_CWM5_androidroot.blob
Profit!
Click to expand...
Click to collapse
exactly, use these steps from androidroot.mobi to flash cwm with fastboot. these are correct, and the only way to flash cwm, if you're unlocked but not rooted.
food for thought: i believe linux+fastboot is way safer than windows+fastboot.
Great! Thanks for the confirmation, quite reassuring, now I know where I'm headed... I'll at least fix my recovery with CWM. From there I don't know, I feel I have to do some more reading before I go ahead and flash any custom rom...
I may not know much on android yet, but I have 10 years experience in linux software dev, with a few pointers like this to get me started I should be able to do anything with this toy soon enough ;-)
Done, just flashed CWM as per the instructions and it works flawlessly. Backing up right now... I'm tempted to go ahead and flash Virtuous.
Done, totally virtuous now ... That was easy Thanks again for the help! Now I only hope I won't regret voiding the warranty

[Q] Return to ICS

Is it possible to remove jellybean from tf201 and reinstall ics. I want to unlock and root my device and after days and days of reading cannot find a way to root my device or to reinstall ica
You don't need to go to ICS. I unlocked and rooted and installed the latest Energy Rom using Urkel's fresh root on JB.
However, got to warn you that one of my 2 Primes got bricked just by installing a recovery...
kapebretoner said:
Is it possible to remove jellybean from tf201 and reinstall ics. I want to unlock and root my device and after days and days of reading cannot find a way to root my device or to reinstall ica
Click to expand...
Click to collapse
The short answer to this question is no. You may not return to ICS. You can unlock and gain root. If your prime is already on jellybean via Asus update do not attempt to install cwm or twrp for ICS or you will permanently brick like garret
Root Possible???
whycali said:
The short answer to this question is no. You may not return to ICS. You can unlock and gain root. If your prime is already on jellybean via Asus update do not attempt to install cwm or twrp for ICS or you will permanently brick like garret
Click to expand...
Click to collapse
I have unlocked my prime, but I would like to root and maybe install cwm if possible.
kapebretoner said:
I have unlocked my prime, but I would like to root and maybe install cwm if possible.
Click to expand...
Click to collapse
Guess I didnt say this plainly enough, if your prime is running ASUS official jellybean version 4.1.1 you will permanently brick (turn it into a $500 paperweight) if you install cwm. To go further there is absolutely no benefit from install cwm on the tf201 ever.
whycali said:
The short answer to this question is no. You may not return to ICS. You can unlock and gain root. If your prime is already on jellybean via Asus update do not attempt to install cwm or twrp for ICS or you will permanently brick like garret
Click to expand...
Click to collapse
You misunderstood what I said. I didn't install anything for ICS. And only One of my Two Primes got bricked. And it booted just fine 2-3 times, the TWRP on this specific Prime wouldn't run for some reason when I went to the Recovery menu. So then I pressed "wipe data" , nothing happened, I rebooted and it bricked.
From what I've seen, it just happens sometimes. I've never seen such weird devices.
Garret said:
You misunderstood what I said. I didn't install anything for ICS. And only One of my Two Primes got bricked. And it booted just fine 2-3 times, the TWRP on this specific Prime wouldn't run for some reason when I went to the Recovery menu. So then I pressed "wipe data" , nothing happened, I rebooted and it bricked.
From what I've seen, it just happens sometimes. I've never seen such weird devices.
Click to expand...
Click to collapse
I didnt misunderstand you, I read your post yesterday. I was just using your brick as an example of what can happen with a bad recovery. From what I have read the reason your prime is bricked is that your recovery is attempting to boot but cant. In most cases its because the recovery needs the correct bootloader version. When you put the wrong recovery for your bootloader you get a permanent wait. It would be nice if there was a timeout for this that caused it to just boot to the os but there is not. Smarter people than me feel free to set me straight if this is not the case.
Couldn't you just flash an ICS ROM using TWRP?
Also, go for Urkel's fresh start. There's no need to go back to ICS, just to get root.
Sent from my myTouch_4G_Slide using xda premium
whycali said:
I didnt misunderstand you, I read your post yesterday. I was just using your brick as an example of what can happen with a bad recovery. From what I have read the reason your prime is bricked is that your recovery is attempting to boot but cant. In most cases its because the recovery needs the correct bootloader version. When you put the wrong recovery for your bootloader you get a permanent wait. It would be nice if there was a timeout for this that caused it to just boot to the os but there is not. Smarter people than me feel free to set me straight if this is not the case.
Click to expand...
Click to collapse
It was the correct bootloader version. For some reason sometimes even though Urkel's fresh root tells you the recovery got installed successfully, it actually does NOT. My Prime still booted fine though until I pressed "Wipe data"...grrr
I searched a lot around the net and many people had the same problem as me. The only answer I found was RMA.
Garret said:
It was the correct bootloader version. For some reason sometimes even though Urkel's fresh root tells you the recovery got installed successfully, it actually does NOT. My Prime still booted fine though until I pressed "Wipe data"...grrr
I searched a lot around the net and many people had the same problem as me. The only answer I found was RMA.
Click to expand...
Click to collapse
well as I said "in most cases". you found another way to bork yours. Guess I wont be using Urkel to do anything to my prime.
I doubt it was Urkel's fresh root that caused the problem. That specific Prime just didn't want to accept the damn TWRP. I have no idea why.
From what I've read, the damn Primes and Asus are to blame. Tons of bricks. If only they gave us the tools we to un-brick them...we could flash from APX mode and the damn things would be unbrickable.

[Q] Need to reinstall root or recovery on TF201 JB, is it possible?

My TF201 is unlocked and I've manually updated it to the JB build from Asus. After running this I noticed that I've lost root and my recovery is broken. Is there a good method to go about fixing this yet?
MeepZero said:
My TF201 is unlocked and I've manually updated it to the JB build from Asus. After running this I noticed that I've lost root and my recovery is broken. Is there a good method to go about fixing this yet?
Click to expand...
Click to collapse
Few months ago I flashed AndroWook to my Prime. I didn't have access to a computer and cable, but I had coveted to have JB so I decided to skip the steps with NVFlash, because I did not read thoroughly the instruction and I thought that the NVFlash is a plain backup but in modern way
The true is that I lost my unlocket bootloader, because JB installation fix bootloader and lock it again
Official ICS bootloader unlocker not works with devices JB based and ASUS haven't updated this for working with JB :/
Today I know why the NVFlash was so much important. So sad, but really story... You have the same problem. I'm sorry...
gucman said:
Few months ago I flashed AndroWook to my Prime. I didn't have access to a computer and cable, but I had coveted to have JB so I decided to skip the steps with NVFlash, because I did not read thoroughly the instruction and I thought that the NVFlash is a plain backup but in modern way
The true is that I lost my unlocket bootloader, because JB installation fix bootloader and lock it again
Official ICS bootloader unlocker not works with devices JB based and ASUS haven't updated this for working with JB :/
Today I know why the NVFlash was so much important. So sad, but really story... You have the same problem. I'm sorry...
Click to expand...
Click to collapse
I have no idea what you did but you cannot relock the bootloader once you have unlocked. The only way this ever happens is if you return it for RMA and they swtich out the motherboard.
Just because it might not say unlocked bootloader in the top left anymore does not mean it has relocked.
If you have installed Androwook rom at some point and have not sent it in for RMA at any time since your device is still unlocked mate.
If you are talking about losing recovery that happens when you upgrade the bootloader and then have to flash a new recovery thru fastboot that matches the bootlader you are now on.
Maybe I should rephrase my question. If my recovery is broken, and I don't have root, is it possible to either fix recovery OR repair my root access?
MeepZero said:
Maybe I should rephrase my question. If my recovery is broken, and I don't have root, is it possible to either fix recovery OR repair my root access?
Click to expand...
Click to collapse
Yes there is mate..
Please make sure that you are definitely on the JB bootloader before proceeding. You can check this by looking at the tegra logo when you switch the machine on. If it is down the bottom right it is jellybean if it is bottom center it is ICS.
Once you are sure you are on the JB bootloader go to this post http://forum.xda-developers.com/showpost.php?p=26595675&postcount=2 and follow the Install Instructions for TWRP.
@flumpster:
I have the string "device is unlocked" in top left corner and it's the cause I didn't send it to ASUS for RMA.
General problem is that i can't get recovery and fastboot.
gucman said:
@flumpster:
I have the string "device is unlocked" in top left corner and it's the cause I didn't send it to ASUS for RMA.
General problem is that i can't get recovery and fastboot.
Click to expand...
Click to collapse
First thing you need to do is get yourself into fastboot mode.. Power off the device and then hold the volume down and power button the same time for 10 seconds until you get a load of icons on your screen. Press volume down to go over to the USB icon ( fastboot ) and then press volume up.
At this point it will say starting fastboot protocol and freeze. This is normal. You now have to look in your device manager to see if you have the drivers installed. If you have any devices in there with exclamation marks by them then install naked drivers from the dev thread.
Once that is done you can do the same as what I just said to the guy above to get a new recovery on there.. Make sure you are on JB bootloader the same as I said to him tho.
flumpster said:
Yes there is mate..
Please make sure that you are definitely on the JB bootloader before proceeding. You can check this by looking at the tegra logo when you switch the machine on. If it is down the bottom right it is jellybean if it is bottom center it is ICS.
Once you are sure you are on the JB bootloader go to this post http://forum.xda-developers.com/showpost.php?p=26595675&postcount=2 and follow the Install Instructions for TWRP.
Click to expand...
Click to collapse
It looks like I'm on the JB bootloader then. I'll take a look at this later tonight and see if I can get this thing fixed
I'm 100% sure that I'm on the JB bootloader. I know how to get fastboot But it stucks on "Starting Fastboot USB download protocol". And i could waiting to over and obver. Probably to the next end of world
I reinstalled the naked drivers few times before I noticed that I should disable driver signature enforcement, because I'm on Win 8. I did these and actually I have installed it correctly. I bought the new cable recently. I thought that it's whats wrong with my wire. No success...
But I never saw that topic about AndroWook TWRP for JB earlier and I am taking to work! I hope this help
gucman said:
I'm 100% sure that I'm on the JB bootloader. I know how to get fastboot But it stucks on "Starting Fastboot USB download protocol". And i could waiting to over and obver. Probably to the next end of world
I reinstalled the naked drivers few times before I noticed that I should disable driver signature enforcement, because I'm on Win 8. I did these and actually I have installed it correctly. I bought the new cable recently. I thought that it's whats wrong with my wire. No success...
But I never saw that topic about AndroWook TWRP for JB earlier and I am taking to work! I hope this help
Click to expand...
Click to collapse
The starting fastboot protocol and not going anywhere is completely normal mate. That is how fastboot works. You could wait all day and it will not change.
Your problem is more windows 8 with its driver verification issues. I don't have windows 8 but if you get really stuck and can't get them installed I know that WhyCali in the team has it installed and he can help you.
You are definately not locked tho
It works!
You're my god bro :highfive:
I watched the .bat file from your package and I deduced that I should have to use fastboot with "-i 0x0B05" flag.
Thank You again

Possible Unbrick Solution for Unrecoverable Bootloader & Wrong TWRP Flashes.

I found the following post while doing my daily read thru all the other forums and some people are saying that it has rescued them from wrong TWRP flash and Unrecoverable Bootloader errors.
I would try to do all the other methods available first but if you are completely bricked then you have nothing to lose.
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
flumpster said:
I found the following post while doing my daily read thru all the other forums and some people are saying that it has rescued them from wrong TWRP flash and Unrecoverable Bootloader errors.
I would try to do all the other methods available first but if you are completely bricked then you have nothing to lose.
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Click to expand...
Click to collapse
Flumpster, I was going to start a separate thread to take my brick issues out of your dev thread and saw your thread here. So the option here is to reboot into fastboot, basically wipe everything and then flash the system blob from a stock ROM.
My main question is what if the person is on a TF300T bootloader, in my case 10.6.1.8. Would flashing the latest stock Asus JB ROM over 'system' for the TF200 replace the bootloader as well?
trogdan said:
Flumpster, I was going to start a separate thread to take my brick issues out of your dev thread and saw your thread here. So the option here is to reboot into fastboot, basically wipe everything and then flash the system blob from a stock ROM.
My main question is what if the person is on a TF300T bootloader, in my case 10.6.1.8. Would flashing the latest stock Asus JB ROM over 'system' for the TF200 replace the bootloader as well?
Click to expand...
Click to collapse
To answer myself, yes it does replace the bootloader. The latest ROM on Asus (from last Dec 2012) installs bootloader 1.00e ww_epad-10.4.2.18-20121122 a03
I installed stock TWRP 2.5.0 here for JB based on this thread and was able to get into TWRP and install the Hairybean Upgrade for 2.3, followed by the HB 2.3, and am now booting into the ROM. W00t! Great link in the OP flumpster.
trogdan said:
To answer myself, yes it does replace the bootloader. The latest ROM on Asus (from last Dec 2012) installs bootloader 1.00e ww_epad-10.4.2.18-20121122 a03
I installed stock TWRP 2.5.0 here for JB based on this thread and was able to get into TWRP and install the Hairybean Upgrade for 2.3, followed by the HB 2.3, and am now booting into the ROM. W00t! Great link in the OP flumpster.
Click to expand...
Click to collapse
Ah. I see you have it fixed now.
Ignore the pm I just sent you then.
I have the same issue and i solved it with your link
Can't get in to fastboot?
I just cant get in to fastboot mode.
KingJelle said:
I just cant get in to fastboot mode.
Click to expand...
Click to collapse
adb reboot bootloader
When in recovery.
I just got a used prime and was trying to root/unlock/custom recovery/rom but I think I did something wrong.
This process seems a lot more delicate and volatile than my phone
I installed cwm through the CWM Rom Manager app after unlocking and rooting both of which went smoothly and device booted, and the device was properly rooted. After flashing recovery through CWM Rom Manager app I am ASUS boot screen
The one with "the device is unlocked" in the upper right corner and just sits in that state indefinitely. Can't do anything other than restart and get back to that screen. Any ideas?
hypocritelecteur said:
I just got a used prime and was trying to root/unlock/custom recovery/rom but I think I did something wrong.
This process seems a lot more delicate and volatile than my phone
I installed cwm through the CWM Rom Manager app after unlocking and rooting both of which went smoothly and device booted, and the device was properly rooted. After flashing recovery through CWM Rom Manager app I am ASUS boot screen
The one with "the device is unlocked" in the upper right corner and just sits in that state indefinitely. Can't do anything other than restart and get back to that screen. Any ideas?
Click to expand...
Click to collapse
Unfortunately you never read up on anything before attempting it. There are warnings everywhere on this forum saying not to use cwm on the prime and not to use rom manager and goo manager.
The last official version of cwm on the prime was for the ICS bootloader and if you flash that recovery onto jellybean bootloader then chances are you are going to brick yourself. Rom manager doesn't check what you are on and just installs the ICS version anyway. I reported this to Koush 2 years ago and he did nothing about it.
If you can't get to the bootloader or recovery by holding down volume down and power the same time and you also don't have nvflash backups then I am afraid that you are hard bricked.
There are only 2 options. Either pay Asus to fix it which will cost you more than you paid for it or you buy a motherboard off ebay or one with a smashed screen but still working and swap the motherboard out.
hypocritelecteur said:
Drat. Is there absolutely no chance, no method that might possibly work? No system dumps or backups or anything I can snag from another user to bootstrap my way back to functionality? I admit I jumped the gun here defs. I've been mucking with roms and hacks for android for years and never hard bricked anything and never run into a system this volatile. Didn't realize I was even being reckless! Just a different world I guess. This is however my first tab--are they in general more risky?
Click to expand...
Click to collapse
I know how you feel mate as before getting this tablet I have had numerous android devices and have had lots since and this is by far the easiest to hard brick. With other devices you can mess up but normally there is a method back in (odin etc) but Asus decided to tie it down completely.
The nvflash guys did a great job to make our devices brick proof but you have to make sure that you have your backups first. No one elses backups can be used. They are specific to your motherboard.
You can pick up motherboards quite cheap on ebay and someone here on one of the recent posts even put a tf300 motherboard in there instead as it was a lot cheaper ($50). They are basically the same machines anyway.
Was it unlocked when you got it ? If it was ask the original owner if he ever made nvflash backups.
tf201 maybe bricked
flumpster said:
I know how you feel mate as before getting this tablet I have had numerous android devices and have had lots since and this is by far the easiest to hard brick. With other devices you can mess up but normally there is a method back in (odin etc) but Asus decided to tie it down completely.
The nvflash guys did a great job to make our devices brick proof but you have to make sure that you have your backups first. No one elses backups can be used. They are specific to your motherboard.
You can pick up motherboards quite cheap on ebay and someone here on one of the recent posts even put a tf300 motherboard in there instead as it was a lot cheaper ($50). They are basically the same machines anyway.
Was it unlocked when you got it ? If it was ask the original owner if he ever made nvflash backups.
Click to expand...
Click to collapse
well i tried all these thinks but i can not get into fastboot or into my OS doesn't see my micro sd card also at all it does is go back to the twrp recovery 2.6.3.0 it is wrong file in the twrp recovery all files are empty did i brick my tf201 and is it a paper weight this all it does can't back up or install anything no files and don't see my sd card also need help please
Exterminator77 said:
well i tried all these thinks but i can not get into fastboot or into my OS doesn't see my micro sd card also at all it does is go back to the twrp recovery 2.6.3.0 it is wrong file in the twrp recovery all files are empty did i brick my tf201 and is it a paper weight this all it does can't back up or install anything no files and don't see my sd card also need help please
Click to expand...
Click to collapse
When in TWRP you should have adb access if you have the drivers installed.
Try.
Code:
adb reboot bootloader
to get you back to fastboot.
I managed to install original system blob. But what now? After start I have again four options, but my Prime is not booting into system or recovery. It always hang up on starting screen with ASUS logo or wit a dead robot.
Thank you.
---------- Post added at 09:05 PM ---------- Previous post was at 08:06 PM ----------
ok, now I am totally bricked, I restarted my Prime and it is black, even backlight is dead. It only reacts to power button, when I hold it, it vibrates after a while.
Fastboot or ADB cannot contol it.
Dammit
Did you ever manage to get your system back?
I used ADB to make a backup of my TF201.
I couldn't get ROM manager to flash a new ROM - every time RM restarted the TF201 I simply got the screen The Device is UnLocked together with the graphical menu for Recovery, Android, USB and Wipe and it just sat there and did nothing.
Eventually, I pushed the CWM ZIP into /SDCARD/ renamed it to UPDATE.ZIP then tried rebooting to see if it would treat that like an OTA update - it didn't.
So then I chose the Wipe option. It sat there for ages with nothing happening.
So I then rebooted - now I get the The Device is Unlocked in the top left hand corner, the ASUS logo in the middle and the Powered by NVIDIA`TEGRA` in the bottom right but it does not boot - it is bricked!
My PC no longer sees it in ADB or FASTBOOT so I can't either flash something or restore my carefully taken backup.
It won't boot into anything other than the screen above - so the key combination for Fastboot doesn't work any more.
Prior to all this it was running stock 4.1.1 but was successfully rooted and had been like that for quite some time.
Any ideas?
Kind Regards
Steve
Hi, I have the same problem than the last message. It's impossible!! any ideas please??
Thanks
Vanessa
Hrd Bricked tf201
sdemills said:
Did you ever manage to get your system back?
I used ADB to make a backup of my TF201.
I couldn't get ROM manager to flash a new ROM - every time RM restarted the TF201 I simply got the screen The Device is UnLocked together with the graphical menu for Recovery, Android, USB and Wipe and it just sat there and did nothing.
Eventually, I pushed the CWM ZIP into /SDCARD/ renamed it to UPDATE.ZIP then tried rebooting to see if it would treat that like an OTA update - it didn't.
So then I chose the Wipe option. It sat there for ages with nothing happening.
So I then rebooted - now I get the The Device is Unlocked in the top left hand corner, the ASUS logo in the middle and the Powered by NVIDIA`TEGRA` in the bottom right but it does not boot - it is bricked!
My PC no longer sees it in ADB or FASTBOOT so I can't either flash something or restore my carefully taken backup.
It won't boot into anything other than the screen above - so the key combination for Fastboot doesn't work any more.
Prior to all this it was running stock 4.1.1 but was successfully rooted and had been like that for quite some time.
Any ideas?
Kind Regards
Steve
Click to expand...
Click to collapse
Hi Steve:
Well darn it, I'm another one with a completely bricked tf201. Without going into how I got there, I have the same situation as you... with "The Device is Unlocked" in the upper-left of the screen, "ASUS" in the center and "Powered by Tegra" in the lower right. If I boot with either just the power button, or the power botton and volume down, I get the affore-mentioned screen.
If I boot with power button and volume up, I get a completely black screen. I was very interested in whether you received a reply to your question?
I've noticed that the greater percentage of these questions, as I've described my system, remain unanswered. Not that I am complaining, but I am certainly interested in whether or not there is a remedy as of this date? I am not able to afford sending my tablet to ASUS, so would really appreciate any work arounds I could try.
Cheers man. Hope to hear from you.
Jim

I think I bricked my phone.

Alright so I have a rooted D6708 device. I got an itch today and wanted to explore some custom roms. I was told that I could flash one of these roms onto the device and it would work.
So I did so with the use of TWRP. TWRP said the install was a success and I needed to reboot. So, I rebooted and now it won't load anything. I can get into the stock System Recovery Menu but nothing else. I can't get back into TWRP and I can't get the device to connect to my PC.
What can I do to fix this?
EDIT: I can get the computer to recognize it as "S1 Boot Fastboot" Anything I can do from here?
Seannnn said:
Alright so I have a rooted D6708 device. I got an itch today and wanted to explore some custom roms. I was told that I could flash one of these roms onto the device and it would work.
So I did so with the use of TWRP. TWRP said the install was a success and I needed to reboot. So, I rebooted and now it won't load anything. I can get into the stock System Recovery Menu but nothing else. I can't get back into TWRP and I can't get the device to connect to my PC.
What can I do to fix this?
EDIT: I can get the computer to recognize it as "S1 Boot Fastboot" Anything I can do from here?
Click to expand...
Click to collapse
I dont own a Z3V however i own a Z3, i haven't experienced boot loop on the Z3, however i have with previous Xperia Devices i solved the issue by installing Flashtool and downloading my stock FTF file.
Seannnn said:
Alright so I have a rooted D6708 device. I got an itch today and wanted to explore some custom roms. I was told that I could flash one of these roms onto the device and it would work.
So I did so with the use of TWRP. TWRP said the install was a success and I needed to reboot. So, I rebooted and now it won't load anything. I can get into the stock System Recovery Menu but nothing else. I can't get back into TWRP and I can't get the device to connect to my PC.
What can I do to fix this?
EDIT: I can get the computer to recognize it as "S1 Boot Fastboot" Anything I can do from here?
Click to expand...
Click to collapse
Whoever told you that you can install these doesn't know the z3v. It's a different phone from any other z3 and can't take those custom Rom.
Your best solution is to try the tft install as described in the downgrade section of the root thread. That would bring you back to a stock Verizon.
Seannnn said:
Alright so I have a rooted D6708 device. I got an itch today and wanted to explore some custom roms. I was told that I could flash one of these roms onto the device and it would work.
So I did so with the use of TWRP. TWRP said the install was a success and I needed to reboot. So, I rebooted and now it won't load anything. I can get into the stock System Recovery Menu but nothing else. I can't get back into TWRP and I can't get the device to connect to my PC.
What can I do to fix this?
EDIT: I can get the computer to recognize it as "S1 Boot Fastboot" Anything I can do from here?
Click to expand...
Click to collapse
Sorry I did not check your PM much earlier to prevent you from doing this. Whoever did tell you about flashing a custom rom sure does owe you another phone. You have to wait until Verizon brings out the Lollipop rom, but until then, you have to somehow flash back to the original rom that came with. 4.4.4 is enjoyable enough as it is, just the lack of volte is what's the wait for on the Lollipop rom.
A rep told me today that when the Z4v, there's sure likely a quick follow up on releasing the update since they may as well base it off of it. And that's hoping if the new one even gets VoLTE...
Thanks for the help guys, I can access the phone via USB with fastboot. I am trying to flash the ftf file but I don't think I am doing it right or its not working. Is there any way I can switch it to adb mode through a fastboot command?
Sorry I don't entirely know what I am doing.
Seannnn said:
Thanks for the help guys, I can access the phone via USB with fastboot. I am trying to flash the ftf file but I don't think I am doing it right or its not working. Is there any way I can switch it to adb mode through a fastboot command?
Sorry I don't entirely know what I am doing.
Click to expand...
Click to collapse
to connect in flashmode you need to hold volume down and connect the phone to the pc with a usb cable
Unfortunately I was not able to get it into flash mode.
Good news is that the phone was still in warranty and I got it replaced for no charge.
Seannnn said:
Unfortunately I was not able to get it into flash mode.
Good news is that the phone was still in warranty and I got it replaced for no charge.
Click to expand...
Click to collapse
It's a good thing you were fortunate enough to have it replaced with no charge. Now don't make that same mistake again and wait like the rest of us. At least you confirmed for sure that flashing an incompatible ROM is death of the phone. lol
Seannnn said:
Unfortunately I was not able to get it into flash mode.
Good news is that the phone was still in warranty and I got it replaced for no charge.
Click to expand...
Click to collapse
I'm aware that I'm coming across as a jerk for this. That is THE reason they don't want us rooted and such. When people screw it up they expect someone else to pay for the mistake
sherdog16 said:
I'm aware that I'm coming across as a jerk for this. That is THE reason they don't want us rooted and such. When people screw it up they expect someone else to pay for the mistake
Click to expand...
Click to collapse
I agree. People always complain about carriers preventing root and locking boot loader. The main argument is that it doesn't damage the phone. Unfortunately, I've seen many people on xda abuse the system. When they brick their phone through bad flash or when their phone dies after it overheated because they over clocked, they go for warranty replacement.
Can't blame Verizon for trying to avoid these extra costs.
tsachi said:
I agree. People always complain about carriers preventing root and locking boot loader. The main argument is that it doesn't damage the phone. Unfortunately, I've seen many people on xda abuse the system. When they brick their phone through bad flash or when their phone dies after it overheated because they over clocked, they go for warranty replacement.
Can't blame Verizon for trying to avoid these extra costs.
Click to expand...
Click to collapse
yes you can... simply exclude warranty on non OEM code... very simple to solve....
sherdog16 said:
I'm aware that I'm coming across as a jerk for this. That is THE reason they don't want us rooted and such. When people screw it up they expect someone else to pay for the mistake
Click to expand...
Click to collapse
That is why the Z3v has a hash code on the phone that shows when you root it and can't be flashed over so they know if it has been rooted even if you flash back to the correct firmware. "Settings>About phone>Status" You send it in they charge you full price.
tsachi said:
I agree. People always complain about carriers preventing root and locking boot loader. The main argument is that it doesn't damage the phone. Unfortunately, I've seen many people on xda abuse the system. When they brick their phone through bad flash or when their phone dies after it overheated because they over clocked, they go for warranty replacement.
Can't blame Verizon for trying to avoid these extra costs.
Click to expand...
Click to collapse
Uh, VZW says it is about the "network", not bad flashes on phones. So which is it?
If VZW wasn't so anal about rooting Sony lets you root in a foolproof way, failed rooting is VZW's fault if it happens.
Any one got the solution.... my phone not working
shashikiran said:
Any one got the solution.... my phone not working
Click to expand...
Click to collapse
What did you do this time?
no recovery mode
GigaSPX said:
What did you do this time?
Click to expand...
Click to collapse
flashed flashable prerooted.zip file and not even getting recovery mode, no charging symbol, only can access fastboot mode. continiously rebooting with vibration. no display
My Z3v is rooted and is working just fine, except the annoying ads I get on my quick charge screen, now.
Anyway... I assume you haven't tried to use the Sony/Verizon Software Upgrade Assistant? It comes on your phone to install to your PC and lets you upgrade (probably never gonna get an upgrade) and factory your phone over USB. Not sure if you can download it, or if it only comes on the phone as a separate partition to install from. Can't hurt to try.

Categories

Resources