Hey guys,
apart from my Un-Bricking-Thread I wanted to start a Thread dealing with how to prevent a brick in the first place.
--- Already bricked your Prime? Read on here, maybe you can recover it ---
In the last days I learned quite a few things about the TFP, its CWM and how to work with it. I also hard bricked my Prime so I certainly know what I am talking about
Unfortunately ASUS didn't fully unlock our Bootloader. We still can't use NVFLASH for low level flashs.
This also means that we can't recover some things we could with NVFLASH access (like a broken bootloader).
So lets start with the things you better not do:
DON'T
Once you unlocked the prime and installed CWM, do NOT try to install a super blob from ASUS (that is a blob file from one of the 'full' updates from their site)
It seems that doing so totally bricks your Prime with no chance of recovery... (happened at least twice so far)
Don't flash kernels like you used to flash (with write_raw_image to /boot). This does not work on the Prime. More on how to do it later.
Don't rely on your newly created ROM to work, ALWAYS have a backup of a working ROM on your sdcard (or a zip of a working ROM)
Currently we can't mount the USB-Storage from inside CWM, so transferring files to the Prime while being in recovery is not as easy for many not so advanced users.
Always make sure you have all files you need before rebooting to recovery.
DO
Kernel flashing: There seem to be two methods on how to flash a new kernel. One is safer but needs a bit more work, and the other is rather unsafe but okay when you (or the ROM dev) know what needs to be done.
Flash your boot.img via fastboot. This is usually rather safe (as safe as fastboot can be) but needs you to have a working fastboot environment. Update: It seems kernel flashing via fastboot does not work at all. Fastboot doesn't give you an error but it doesn't update the kernel either...
Flash your kernel via the /staging partition. In order to use this method you first need to pack your boot.img into a blob file.
Then you need put the data from the blob file to the /staging partition.
Once you reboot the kernel gets automatically installed.
Please be aware that you can flash almost everything like this, even the bootloader.
So if you screw up packing the blob file, you could easily brick your Prime.
The advantage of this method is that the user doesn't need to do anything, but you really need to take care of what you are doing.
Also make sure that the /staging partition is ALWAYS unmounted before flashing anything to it. Otherwise this will result in a Brick 3.
Always make a backup of your current ROM before flashing anything else. As stated earlier, we currently have no access to the sdcard in recovery, so transferring files to Prime is not as easy in recovery mode.
So I hope I can find some more topics in the future, but for now that's it
Diamondback said:
DON'T
Once you unlocked the prime and installed CWM, do NOT try to install a super blob from ASUS (that is a blob file from one of the 'full' updates from their site) It seems that doing so totally bricks your Prime with no chance of recovery... (happened at least twice so far)
Click to expand...
Click to collapse
But but but how can I has update?! I want Update! RWAR!
Thanks, thanks, bump, and thanks again! Due to the current state of our device's development (especially with an early build of CWM), misinformation floating around, etc. this is invaluable! Now I know what "staging" is and what its use is. Well done - keep up the great work
Sent from my Transformer Prime TF201 using xda premium
mtotho said:
But but but how can I has update?! I want Update!
Click to expand...
Click to collapse
Use custom ROMs. We currently don't really know if it ALWAYS bricks your Prime. We just know that two updates bricked two primes
I think nobody wants to try
Diamondback said:
Use custom ROMs. We currently don't really know if it ALWAYS bricks your Prime. We just know that two updated bricked two primes
I think nobody wants to try
Click to expand...
Click to collapse
Yea I am just kidding. I knoweth better plus I like custom roms (and I am very flash happy)
I won't be happy until we get some sort of nightly rom that I can flash daily
thanks diamondback this prob saved me lots of time and the almost $700 i have in my device+dock
Sent from my Transformer Prime TF201 using xda premium
Will be possible to use NVFLASH anytime? Have we to look for a dev or is Asus that must upgrade its apk?
Thanks Diamondback for making this. This needs to become a sticky immediately. To many people are blindly unlocking then get mad when they find out they can't do OTA updates. Or people installing CMW without even unlocking and blaming others issues on that when they found out device should've been unlocked first..lmfao
Unlock tool release=operation sabotage for those who don't know any better or ignorant or lazy to research first. QnA section had several people with semi or hard bricked primes. Primes are dying off left n right..lol
Diamondback said:
Unfortunately ASUS didn't fully unlock our Bootloader.
Click to expand...
Click to collapse
So you download their software, run it to completely void your warranty (they've already denied support on one unrelated hardware issues that I know of), and you STILL don't have full access?
WTF!?!?!!?
Not being able to use NVFlash has completely put me off, for me NVFlash was the ultimate aim for unlocking the bootloader ... pretty **** !
(unhappy smiley)
Diamondback, I'm so sorry to hear that you bricked your Prime! Any luck getting unbricked yet?
Thank you so much for posting this invaluable guide. You are generous beyond words, to go to this effort to save other users from the lessons you had to learn the hard way. There aren't enough thanks in the world.
If we can at least ATM use fastboot that's a good thing. A good thing for fastboot is you can first do-
fastboot boot boot.img and it will boot the kernel the first time, basically so you can test it before it writes the .img
then you can fastboot flash boot.img to write the image. It'll work for now, sucks that any non-dev who just wants to flash a kernel has to set up fastboot
Edit- girluvsdroid- just saw you were in wilmington- me too.
This was very helpful.
BUMP!
Reading is fundamental! Lol I don't know how many times I've just glanced over post, just to get the newest firmware, and kernals, just to end up on the verg of a bricked device. Thanks.
What ?
So If I UnlockBootLoader
I cant OTA Anymore ? Seriously
AndyMclamb said:
What ?
So If I UnlockBootLoader
I cant OTA Anymore ? Seriously
Click to expand...
Click to collapse
But why would you unlock if you were not going to install custom roms (that have the latest OTA built in) anyway?
Diamondback said:
Flash your boot.img via fastboot. This is usually rather safe (as safe as fastboot can be) but needs you to have a working fastboot environment.
Click to expand...
Click to collapse
Hmm.. Does not seem to work for me. Built a kernel, switched in fastboot mode. Then:
Code:
$ sudo ./fastboot -i 0x0b05 boot zImage blob.LNX-ramdisk.cpio.gz
creating boot image...
creating boot image - 4214784 bytes
downloading 'boot.img'...
OKAY [ 0.748s]
booting...
FAILED (remote: ()
finished. total time: 0.749s
Prime displays: Failed to process command boot error(0x120000)
Any advice?
saturn_de said:
Hmm.. Does not seem to work for me. Built a kernel, switched in fastboot mode. Then:
Code:
$ sudo ./fastboot -i 0x0b05 boot zImage blob.LNX-ramdisk.cpio.gz
creating boot image...
creating boot image - 4214784 bytes
downloading 'boot.img'...
OKAY [ 0.748s]
booting...
FAILED (remote: ()
finished. total time: 0.749s
Prime displays: Failed to process command boot error(0x120000)
Any advice?
Click to expand...
Click to collapse
Yes. fastboot boot does not work at all.And we also found out that kernel flashing via fastboot does not work either.
You have to flash your kernels via a custom made blob ;-)
Gesendet von meinem Desire HD mit Tapatalk
Prime Stuck in CWM boot loop hell.
I have a Prime that is stuck in a CWM Recovery boot loop.
Brick 1a
All thanks (sincerely) to Viperboy and his ViperMOD PrimeTime 4.5, I had my Prime rooted, boot loader unlocked and loaded with ClockworkMOD Recovery 5.5.0.4.
I used CWM to create a backup, wipe the data/factory, cache partition and Dalvik cache, rebooted the system (from CWM menu) just to verify that the unit was really wiped back to setup, powered down the unit, rebooted into CWM Recovery (using Power while holding Vol.Down, wait for small/white text, Vol.Up) and Restored using the previously created Backup.
I rebooted Android from CWM menu and my Prime was restored.
Everything was great, but not for long.
The next time that I booted into CWM recovery I selected “Reboot System Now”.
It went dark, displayed the ASUS splash screen, went dark and went back into CWM.
I am stuck in that loop.
I have tried all the suggested fixes I can find but all methods are useless because:
1. I can’t acquire an ADB connection because Windows doesn’t identify the bricked Prime correctly and won’t install the USB drivers. Device Manager sees “Full Android as Emulator”.
2. I can’t boot into the boot loader to use Fastboot because I never see the option to choose it. It boots or reboots directly into CWM after “Booting Recovery Kernel Image”, ever while holding the Vol.Down button.
I have repeatedly tried installing and uninstalling the drivers by installing and uninstalling the Asus Sync and Asus Android USB Drivers. I have repeatedly tried to install the drivers via the Device Manager. No good. I’ve installed and uninstalled Android SDK Tools repeatedly.
Is there a way out of this? I hope I'm not efed.
Thank you in advance for any help.
Temporalmind said:
I have a Prime that is stuck in a CWM Recovery boot loop.
Brick 1a
[..]
I apologize for the length of this post. I hope I’m not efed.
Click to expand...
Click to collapse
Please try to manually installing these drivers here
http://forum.xda-developers.com/showthread.php?t=1426502
Adb should be working afterwards
Universal Naked Driver works great!
Ok, you saved me and my precious.
Your drivers were exactly what I needed.
After installing them in Device manager I was able to achieve a “ASUS Android Composite ADB Interface” connection.
Following the “How to Unbrick your Transformer Prime (or not)”, Option 1a and restoring I’m up and running.
Thank you!
Then, I deliberately caused the boot looping condition again to see if I could figure out how I got there.
There is an app that I think comes preinstalled on the Prime called ”Transformer Recovery Boot”. The icon is labeled "Recovery". This is the app that took me into the Brick 1a the first time and I duplicated it the next time I used it.
Then I was able to ADB my way back to civilization, again.
Thought I’d pass that on incase it helps to determine why the unlocked Prime seems to be so susceptible to bricking.
Again, Thank You!
Related
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
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
Hey guys, if this is in the wrong section feel free to move it. For whatever reason there still isn't a sub-section for the Pantech Flex...
Anyways, long story short, I had some issues with the stock setup and so I used the built-in Reset option under Settings -> Backup & Reset..
This resulted in a soft-brick of sorts, I can't get past the AT&T logo screen, and since it had just been reset, USB Debugging is NOT enabled.. *sigh*
So, I'm trying to use Fastboot to flash/boot CWM so I can recover from this little predicament (I hadn't successfully flashed CWM yet).. but on 99% of Fastboot commands, I get the following error:
Code:
C:\> fastboot flash recovery cwm.img
sending 'recovery' (8076 KB)...
OKAY [ 0.608s]
writing 'recovery'...
FAILED (remote: Not Support !!)
finished. total time: 0.608s
Which leads me to believe I need to unlock some things.. and upon looking around (the VERY limited information for this device...) I found a few suggestions of using "fastboot oem unlock", however it gives the same "FAILED (remote: Not Support !!)" command..
Anyone know anything that may help? Thanks guys!
You probably should be able to get out of trouble with this thread: http://forum.xda-developers.com/showthread.php?t=2472487
Ur lucky its soft brick!
Mine got super hard bricked.....
There are many ways to solve soft brick....
Just go cwm and flash a right rom for u.....
If u dont have cwm feel free to search in the forum......
Sent from my iPad mini using Tapatalk HD
Thy Boss said:
Ur lucky its soft brick!
Mine got super hard bricked.....
There are many ways to solve soft brick....
Just go cwm and flash a right rom for u.....
If u dont have cwm feel free to search in the forum......
Sent from my iPad mini using Tapatalk HD
Click to expand...
Click to collapse
OP stated that they have not had any luck getting CWM to work.
And to OP - sorry! I just double checked the instructions I linked to, but realized you need adb working for the method if you are already on JB. Please let me know if you are ICS or JB and I'll see if I can't give you better direction...
es0tericcha0s said:
OP stated that they have not had any luck getting CWM to work.
And to OP - sorry! I just double checked the instructions I linked to, but realized you need adb working for the method if you are already on JB. Please let me know if you are ICS or JB and I'll see if I can't give you better direction...
Click to expand...
Click to collapse
Sadly yes, I'm already on JB.. My apologies for the slow reply, didn't get notifications like I thought I had set.
Also, I've gotten it to boot up, but the launcher seems to have been erased and so I get a black screen. Status bar still appears but I can't pull it down to access settings. Navigation buttons respond to input but are still useless without a launcher.
On another note, I've tried flashing a few zips via stock recovery's adb sideload mode, everything from cwm to an entire (stock and otherwise) rom, even just a launcher since that should be all I need, but every time I tried to sideload, it would get to 49% and suddenly "Installation Aborted!" Not sure why that doesn't work... *sigh*
FalloutState said:
Sadly yes, I'm already on JB.. My apologies for the slow reply, didn't get notifications like I thought I had set.
Also, I've gotten it to boot up, but the launcher seems to have been erased and so I get a black screen. Status bar still appears but I can't pull it down to access settings. Navigation buttons respond to input but are still useless without a launcher.
On another note, I've tried flashing a few zips via stock recovery's adb sideload mode, everything from cwm to an entire (stock and otherwise) rom, even just a launcher since that should be all I need, but every time I tried to sideload, it would get to 49% and suddenly "Installation Aborted!" Not sure why that doesn't work... *sigh*
Click to expand...
Click to collapse
Got yourself a tricky one here.
http://forum.xda-developers.com/showpost.php?p=37320624&postcount=88
Use that modded stock recovery to have proper adb access in recovery, and do: adb install launcher.apk (non /system version with that command, and launcher.apk can be named anythingyouwant.apk)
I kind of think that isn't going to be enough though.
If that doesn't work, it might be worth trying to fastboot boot a version of CWM, have the rom you need on the SD card and use that to flash. CWM won't stay, but if you boot and all is well, that can be re-added easily. Let's get the easy option out of the way first though.
es0tericcha0s said:
Got yourself a tricky one here.
http://forum.xda-developers.com/showpost.php?p=37320624&postcount=88
Use that modded stock recovery to have proper adb access in recovery, and do: adb install launcher.apk (non /system version with that command, and launcher.apk can be named anythingyouwant.apk)
I kind of think that isn't going to be enough though.
If that doesn't work, it might be worth trying to fastboot boot a version of CWM, have the rom you need on the SD card and use that to flash. CWM won't stay, but if you boot and all is well, that can be re-added easily. Let's get the easy option out of the way first though.
Click to expand...
Click to collapse
I saw that first link while searching for solutions, however that dropbox link is dead. @timmythanoob, do you still have this file available?
As far as your second idea of using "fastboot boot xxx.img" or whatever have you, the issue with that is that the "boot" command is one of the Fastboot commands I mentioned in the OP that gives the "Remote: Not Support!!" error, which from what I can find is an issue with "aboot" in the JB update...
If I can get ahold of timmythanoob's recovery image with ADB access, then even if adb install'ing a launcher doesn't work, I could still have WAY more options to work with and I'm confident that with full ADB access I could restore the device to working order... IF someone can get me that recovery w/ adb :|
EDIT: Actually I don't think even timmythanoob's recovery image will work since I don't have access to the "fastboot boot" command... I really think my only options are PDL mode and sideloading a zip in recovery. PDL won't work because of the lack of PDL's for our device (and Pantech refusing to give me one), and sideloading a zip in recovery, for whatever reason, always seems to fail with an Installation Aborted... -_-
Anyone have any ideas?
Sorry, a lot of the info for this phone is mixed and matched between instructions for ICS and JB. So, basically, it seems you are boned. Only way to properly get fastboot to work would be to downgrade the aboot, which you can't do because you have to be rooted and booted while on JB to do so. Same thing with CWM on JB. Have to be rooted and booted. :/ Sorry man.
Last resort I can see would be trying to flash the JB OTA zip via stock recovery:
http://forum.xda-developers.com/showpost.php?p=46025559&postcount=164
But even that guy who obviously knows these devices a bit better than we do says it probably wouldn't work for someone in your situation a bit later in that thread:
http://forum.xda-developers.com/showpost.php?p=46209691&postcount=174
But that's pretty much your last option at this stage other than sending it into Pantech so they can use their firmware flashing tool since they won't share it with anyone.
I tried that JB OTA, didn't work. 49% and then Installation Aborted. I was going to send it to Pantech but I imagine they won't help since thanks to my recovery attempts, in the bootloader screen it shows as being rooted and tampered with.
Sucks man. One of the downsides of their being so many different devices out there. Only so many developers to go around and that combined with little to no support from Pantech... :/
I'm going to claim OP resurrection rights and bring this back up in hopes that someone can help. Anyone know anything?
Sent from my YP-G1 using Tapatalk
Evening all,
Hoping someone can help me with the following please? Please be as technical as you like, I'm fairly tech-savvy (I have CFW on my PSP, I build my own computers and have flashed/cfw various devices in the past) if I don't understand I can google it, but I need to know WHAT to google first and I'm a bit lost...! :good:
I have stock TF201 which is getting pretty painful despite a recent re-install. I've noticed that there is still no real idea as to if/when KitKat will be rolled out for it and was rather p!ssed off to see my missus's Nexus 7 (2012 version!) get 4.4.3 today!
I've done a lot of googling and forum reading but I'm a little confused as to the best route to go...
Having come across the "one-click method to root" using motochopper (and/or other methods) would it then be possible to install 4.4.2 for example using CM11 and a guide such as this (google "Install Android 4.4.2 KitKat on Asus Transformer Prime TF201" as I can't post URLs) - or will this only work for OFW release like 4.2?
In summary, am I missing the point (I get the feeling I may need to be unlocked as well to have a custom recovery?), THEN root etc...
Long and short is I'm not after doing anything crazy other than getting my TF201 to the latest STABLE(ish) version of Android. I understand the risks of bricking, CFW/OFW & OTA etc. I guess I'm basically after a simple list of steps (or pointing at the relevant thread) to achieve this - from the guides I've seen I have to unlock, root and then go down the CM11 route but I want to know if I can get there more easily/safely using one-click root or another method for example?
All advice gratefully received!
Mark
mistral_blue said:
Evening all,
Hoping someone can help me with the following please? Please be as technical as you like, I'm fairly tech-savvy (I have CFW on my PSP, I build my own computers and have flashed/cfw various devices in the past) if I don't understand I can google it, but I need to know WHAT to google first and I'm a bit lost...! :good:
I have stock TF201 which is getting pretty painful despite a recent re-install. I've noticed that there is still no real idea as to if/when KitKat will be rolled out for it and was rather p!ssed off to see my missus's Nexus 7 (2012 version!) get 4.4.3 today!
I've done a lot of googling and forum reading but I'm a little confused as to the best route to go...
Having come across the "one-click method to root" using motochopper (and/or other methods) would it then be possible to install 4.4.2 for example using CM11 and a guide such as this (google "Install Android 4.4.2 KitKat on Asus Transformer Prime TF201" as I can't post URLs) - or will this only work for OFW release like 4.2?
In summary, am I missing the point (I get the feeling I may need to be unlocked as well to have a custom recovery?), THEN root etc...
Long and short is I'm not after doing anything crazy other than getting my TF201 to the latest STABLE(ish) version of Android. I understand the risks of bricking, CFW/OFW & OTA etc. I guess I'm basically after a simple list of steps (or pointing at the relevant thread) to achieve this - from the guides I've seen I have to unlock, root and then go down the CM11 route but I want to know if I can get there more easily/safely using one-click root or another method for example?
All advice gratefully received!
Mark
Click to expand...
Click to collapse
Man your asking for alot
Shoot me a PM lets see if we can point you in the right direction.....
Thx Josh
mistral_blue said:
(I get the feeling I may need to be unlocked as well to have a custom recovery?), THEN root etc...
Click to expand...
Click to collapse
Yep, that's the only route to custom ROM and vital you make NVFlash backups:
1. Unlock device using the official tool from Asus website - its says "for ICS" but works fine on JB.
2. Assuming you are on the latest official stock JellyBean (Asus v 10.4.2.18) then go get the latest TWRP 2.6 for TF201 JB from the bottom of this page: http://techerrata.com/browse/twrp2/tf201 Flash that blob using fastboot following the instructions in the section titled "Download - Recovery Image / Fastboot Method (using ICS or JB Asus bootloader)" on this page: http://teamw.in/project/twrp2/93.
3. Follow the instructions in the tutorial here for making NVFlash backups: http://matthill.eu/android/transform...ybean-nvflash/
4. You are now ready flash a custom ROM of your choice. If you really want to go straight to KK then my advice would be to look no further than CROMBi-kk: http://forum.xda-developers.com/showthread.php?t=2773812. You will get plenty of help here from people who know about the tf201. Read the whole thread but pay particular attention to post #4 where Josh has written a step by step guide for people starting from scratch.
Finally, though you are pretty safe now with your NVFlash backups and even though you are well experiences at flashing, follow all the instructions to the letter and avoid the sadly well tested routes to brick. I don't believe there is another android device in current use that is so easy to brick as the prime.
1. Use only TWRP recoveries. Steer completely clear of CWM and ROM Manager. They never did produce an official recovery for JB on the prime and installing the last one from their site onto the JB bootloader will most certainly land you with a brick. The flatline process leaves behind its own version of CWM but has been made compatible. However, you probably won't be able to see your external SD card with it and it is based on a clunky non-touch version so best advice would be to ditch it straight away for TWRP 2.6 even though you will be upgrading that shortly anyway,
2. Always check you are flashing the correct version of TWRP for your current bootloader and ROM
3. Never, ever press that Wipe Data button on the fastboot screen - that too will kill your tablet.
Oh, and have fun!
EDIT: just seen Josh has offered to hold your hand - don't let go and you'll be fine
Thanks for the quick replies gents... Restorer, I'll read up on the methods you suggest (thanks for the detailed list with links, exactly what I was after) and then Josh I'll be in touch to check I've not missed anything before I start following the Yellow BRICK road:laugh:
Taking The Plunge!
Restorer said:
Yep, that's the only route to custom ROM and vital you make NVFlash backups:
1. Unlock device using the official tool from Asus website - its says "for ICS" but works fine on JB.
2. Assuming you are on the latest official stock JellyBean (Asus v 10.4.2.18) then go get the latest TWRP 2.6 for TF201 JB from the bottom of this page: http://techerrata.com/browse/twrp2/tf201 Flash that blob using fastboot following the instructions in the section titled "Download - Recovery Image / Fastboot Method (using ICS or JB Asus bootloader)" on this page: http://teamw.in/project/twrp2/93.
3. Follow the instructions in the tutorial here for making NVFlash backups: http://matthill.eu/android/transform...ybean-nvflash/
4. You are now ready flash a custom ROM of your choice. If you really want to go straight to KK then my advice would be to look no further than CROMBi-kk: http://forum.xda-developers.com/showthread.php?t=2773812. You will get plenty of help here from people who know about the tf201. Read the whole thread but pay particular attention to post #4 where Josh has written a step by step guide for people starting from scratch.
Finally, though you are pretty safe now with your NVFlash backups and even though you are well experiences at flashing, follow all the instructions to the letter and avoid the sadly well tested routes to brick. I don't believe there is another android device in current use that is so easy to brick as the prime.
1. Use only TWRP recoveries. Steer completely clear of CWM and ROM Manager. They never did produce an official recovery for JB on the prime and installing the last one from their site onto the JB bootloader will most certainly land you with a brick. The flatline process leaves behind its own version of CWM but has been made compatible. However, you probably won't be able to see your external SD card with it and it is based on a clunky non-touch version so best advice would be to ditch it straight away for TWRP 2.6 even though you will be upgrading that shortly anyway,
2. Always check you are flashing the correct version of TWRP for your current bootloader and ROM
3. Never, ever press that Wipe Data button on the fastboot screen - that too will kill your tablet.
Oh, and have fun!
EDIT: just seen Josh has offered to hold your hand - don't let go and you'll be fine
Click to expand...
Click to collapse
Restorer thanks for the instructions...like the title I am about to take the "plunge" and flash this Prime and I want to got to KK. Just one thing.. below you state: "4. You are now ready flash a custom ROM of your choice. If you really want to go straight to KK then my advice would be to look no further than CROMBi-kk: http://forum.xda-developers.com/show....php?t=2773812. " but when I go to the link it says that I must be on Hairybean and the bootloader 4.2.1. I am currently on the stock 10.4.2.18 and downloaded the unlock v6 .apk file from Asus to do the bootloader "unlocking" Just for the sake of clarity...I am new to this...should I still unlock using the Asus util and once done then do the Hairybean update? which will in turn upgrade the bootloader (10.6.1.27.1)?
Tim
tim2min said:
Restorer thanks for the instructions...like the title I am about to take the "plunge" and flash this Prime and I want to got to KK. Just one thing.. below you state: "4. You are now ready flash a custom ROM of your choice. If you really want to go straight to KK then my advice would be to look no further than CROMBi-kk: http://forum.xda-developers.com/show....php?t=2773812. " but when I go to the link it says that I must be on Hairybean and the bootloader 4.2.1. I am currently on the stock 10.4.2.18 and downloaded the unlock v6 .apk file from Asus to do the bootloader "unlocking" Just for the sake of clarity...I am new to this...should I still unlock using the Asus util and once done then do the Hairybean update? which will in turn upgrade the bootloader (10.6.1.27.1)?
Tim
Click to expand...
Click to collapse
Yes, you can't flash anything until the device is unlocked and you have installed a TWRP recovery.
But make sure to then make your NVFlash backups and once you have those files safely stored go straight on to follow Josh's step-by-step guide for in post #4 of the ROM thread. His guide was written specifically for TF201 people coming from stock. Follow it to the letter but be sure to ask if there is something you don't understand.
Good Luck!
Taking The Plunge!
Restorer said:
Yep, that's the only route to custom ROM and vital you make NVFlash backups:
1. Unlock device using the official tool from Asus website - its says "for ICS" but works fine on JB.
2. Assuming you are on the latest official stock JellyBean (Asus v 10.4.2.18) then go get the latest TWRP 2.6 for TF201 JB from the bottom of this page: http://techerrata.com/browse/twrp2/tf201 Flash that blob using fastboot following the instructions in the section titled "Download - Recovery Image / Fastboot Method (using ICS or JB Asus bootloader)" on this page: http://teamw.in/project/twrp2/93.
3. Follow the instructions in the tutorial here for making NVFlash backups: http://matthill.eu/android/transform...ybean-nvflash/
4. You are now ready flash a custom ROM of your choice. If you really want to go straight to KK then my advice would be to look no further than CROMBi-kk: http://forum.xda-developers.com/showthread.php?t=2773812. You will get plenty of help here from people who know about the tf201. Read the whole thread but pay particular attention to post #4 where Josh has written a step by step guide for people starting from scratch.
Finally, though you are pretty safe now with your NVFlash backups and even though you are well experiences at flashing, follow all the instructions to the letter and avoid the sadly well tested routes to brick. I don't believe there is another android device in current use that is so easy to brick as the prime.
1. Use only TWRP recoveries. Steer completely clear of CWM and ROM Manager. They never did produce an official recovery for JB on the prime and installing the last one from their site onto the JB bootloader will most certainly land you with a brick. The flatline process leaves behind its own version of CWM but has been made compatible. However, you probably won't be able to see your external SD card with it and it is based on a clunky non-touch version so best advice would be to ditch it straight away for TWRP 2.6 even though you will be upgrading that shortly anyway,
2. Always check you are flashing the correct version of TWRP for your current bootloader and ROM
3. Never, ever press that Wipe Data button on the fastboot screen - that too will kill your tablet.
Oh, and have fun!
EDIT: just seen Josh has offered to hold your hand - don't let go and you'll be fine
Click to expand...
Click to collapse
Restorer said:
Yes, you can't flash anything until the device is unlocked and you have installed a TWRP recovery.
But make sure to then make your NVFlash backups and once you have those files safely stored go straight on to follow Josh's step-by-step guide for in post #4 of the ROM thread. His guide was written specifically for TF201 people coming from stock. Follow it to the letter but be sure to ask if there is something you don't understand.
Good Luck!
Click to expand...
Click to collapse
Sorry just one more question, since I have a TF201 and and want to use this ROM, it seems I am essentially turning my Prime into aTF300, which is ok, now right after unlocking the boot loader and then running TWRP (2.7 TF300) it is at this point I flash the hairybean update or do the creation & backing up for NVFlash first then the hairybean?...sorry for the elemental question...just want to be sure!
Tim
tim2min said:
now right after unlocking the boot loader and then running TWRP (2.7 TF300)
Click to expand...
Click to collapse
No you're not a TF300 yet! Unlock then flash the latest TWRP version for TF201 from the page I linked to (still 2.6). Then do your NVFlash backups. Then you can pick up Josh's guide again where you flash "Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip". It's just the guide assumes you already have your backups .
Taking The Plunge!
Restorer said:
No you're not a TF300 yet! Unlock then flash the latest TWRP version for TF201 from the page I linked to (still 2.6). Then do your NVFlash backups. Then you can pick up Josh's guide again where you flash "Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip". It's just the guide assumes you already have your backups .
Click to expand...
Click to collapse
Hey restorer this can all be done on a non-root device correct? Should root first if so what is the best way you suggest ...read a little something about motochopper.?
Taking The Plunge!
tim2min said:
Hey restorer this can all be done on a non-root device correct? Should root first if so what is the best way you suggest ...read a little something about motochopper.?
Click to expand...
Click to collapse
Have a possible issue when trying to after renaming the original file flat_tf201 (image file) to twrp.blob it looks like on the windows 7 side it sent it fine but on the tablet I did not see the "blue bar". So worried it did not send I tried it again and got the "error cannot open twrp.blob" when I did a dir of the fastboot directory it is there but noticed is the command prompt after renaming (per instructions from TWRP) the full file name was twrp.blob.img should not matter but renamed it (from command prompt) w/o the .img extension still would not send.
I am thinking eventhough it initially looked like it did send (based on output in command prompt initially) is it possible I missed the blue bar on the tablet?... Should I have seen it? Does it take awhile?
The tablet shows "starting Fastboot USB download protocol"
any help what be appreciated
tim2min said:
Have a possible issue when trying to after renaming the original file flat_tf201 (image file) to twrp.blob it looks like on the windows 7 side it sent it fine but on the tablet I did not see the "blue bar". So worried it did not send I tried it again and got the "error cannot open twrp.blob" when I did a dir of the fastboot directory it is there but noticed is the command prompt after renaming (per instructions from TWRP) the full file name was twrp.blob.img should not matter but renamed it (from command prompt) w/o the .img extension still would not send.
I am thinking eventhough it initially looked like it did send (based on output in command prompt initially) is it possible I missed the blue bar on the tablet?... Should I have seen it? Does it take awhile?
The tablet shows "starting Fastboot USB download protocol"
any help what be appreciated
Click to expand...
Click to collapse
Why rename the the .img file to a .blob file ?
Not really the best thing you could do .....
Just boot to fastboot and run the command
Code:
fastboot flash recovery flatline_tf201.img
The blue bar will show up and fill on the write part of the command ...
Once that is done do this command .....
Code:
fastboot reboot-bootloader
Let the tablet reboot into bootloader and VOL up on RCK
Now your golden ......
Make sure you understand what need to be done in flatline ...
Thx Josh
tim2min said:
Hey restorer this can all be done on a non-root device correct? Should root first if so what is the best way you suggest ...read a little something about motochopper.?
Click to expand...
Click to collapse
No need to root first - the custom ROM you will be installing will be rooted.
---------- Post added at 08:09 AM ---------- Previous post was at 07:59 AM ----------
tim2min said:
Have a possible issue when trying to after renaming the original file flat_tf201 (image file) to twrp.blob it looks like on the windows 7 side it sent it fine but on the tablet I did not see the "blue bar". So worried it did not send I tried it again and got the "error cannot open twrp.blob" when I did a dir of the fastboot directory it is there but noticed is the command prompt after renaming (per instructions from TWRP) the full file name was twrp.blob.img should not matter but renamed it (from command prompt) w/o the .img extension still would not send.
I am thinking eventhough it initially looked like it did send (based on output in command prompt initially) is it possible I missed the blue bar on the tablet?... Should I have seen it? Does it take awhile?
The tablet shows "starting Fastboot USB download protocol"
any help what be appreciated
Click to expand...
Click to collapse
Sounds like you have downloaded (and renamed) the .img file and not the .blob file! "openrecovery-twrp-2.6.3.0-tf201-JB.blob" is the one you want if you are follwoing the instructions on the TWRP page I linked you too. The blob file Josh refers to is the one in this zip file and has a shorter name. You can either use Josh's instructions or TWRP's but not a mixture of the two
@lj50036 I think he referring to the instructions from TWRP on the downloads page which say to rename the file to a shorter form.
@tim2min don't let this renaming stuff confuse you - TWRP are only suggesting it because their full names are so long and prone to error when you are typing them out!
EDIT: Sorry, I hadn't realised Josh had already prepared and renamed the files for you. Just use all 3 of his files contained in his zip and not from my links or you may get further confused.
Restorer said:
No need to root first - the custom ROM you will be installing will be rooted.
---------- Post added at 08:09 AM ---------- Previous post was at 07:59 AM ----------
Sounds like you have downloaded (and renamed) the .img file and not the .blob file! "openrecovery-twrp-2.6.3.0-tf201-JB.blob" is the one you want if you are follwoing the instructions on the TWRP page I linked you too. The blob file Josh refers to is the one in this zip file and has a shorter name. You can either use Josh's instructions or TWRP's but not a mixture of the two
@lj50036 I think he referring to the instructions from TWRP on the downloads page which say to rename the file to a shorter form.
@tim2min don't let this renaming stuff confuse you - TWRP are only suggesting it because their full names are so long and prone to error when you are typing them out!
EDIT: Sorry, I hadn't realised Josh had already prepared and renamed the files for you. Just use all 3 of his files contained in his zip and not from my links or you may get further confused.
Click to expand...
Click to collapse
Does no one use auto-complete any more ......
Thx Josh
lj50036 said:
Does no one use auto-complete any more ......
Thx Josh
Click to expand...
Click to collapse
Haha, yes. Why do command windows have to be so primitive .
Restorer said:
No you're not a TF300 yet! Unlock then flash the latest TWRP version for TF201 from the page I linked to (still 2.6). Then do your NVFlash backups. Then you can pick up Josh's guide again where you flash "Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip". It's just the guide assumes you already have your backups .
Click to expand...
Click to collapse
Just an observation Restorer I note that you said never to select "Wipe Data" in the boot menu but in Josh step by step he suggested to do that which can take a while. In this case it ok to do it since we are putting on a new ROM. I have my backups (blob files) as well as the NVFlash file
Tim
tim2min said:
Just an observation Restorer I note that you said never to select "Wipe Data" in the boot menu but in Josh step by step he suggested to do that which can take a while. In this case it ok to do it since we are putting on a new ROM. I have my backups (blob files) as well as the NVFlash file
Tim
Click to expand...
Click to collapse
How is this saying anything about wiping from bootloader ?
I am sure it say NOW ENTER RECOVERY ....
But maybe I missed something or maybe you did ....
lj50036 said:
Now enter recovery....
Make sure its verison 2.7.1.0
Go to Wipe////Format Data////Type yes
This can take up to 90 mins to format
DO NOT INTERRUPT THE FORMAT !!!!!!!
Click to expand...
Click to collapse
Thx Josh
Taking The Plunge!
lj50036 said:
How is this saying anything about wiping from bootloader ?
I am sure it say NOW ENTER RECOVERY ....
But maybe I missed something or maybe you did ....
Thx Josh
Click to expand...
Click to collapse
Man it was going so well until my computer could no longer see my tablet via USB! so I can now longer use FASTBOOT because the device is not found. This happen right after flashing Hariybean and I was about to run"
Interesting my Win7 computer says that it sees the Asus device:but fastboot does not see it. Also initially the it saw it as an APX device but no longer so I can not do the next step which is to adb reboot-bootloader and then do flash @ne0zone75 TWRP recovery per the instuctions. I have tried re-pointing to the Universal Naked drivers trying to select a diffrent drvier but to no avail. looks like the tablet can no longer communicate to the computer. I will copy the contents of the fastboot directory to another computer and see if that will work
any ideas?
Tim
tim2min said:
Man it was going so well until my computer could no longer see my tablet via USB! so I can now longer use FASTBOOT because the device is not found. This happen right after flashing Hariybean and I was about to run"
Interesting my Win7 computer says that it sees the Asus device:but fastboot does not see it. Also initially the it saw it as an APX device but no longer so I can not do the next step which is to adb reboot-bootloader and then do flash @ne0zone75 TWRP recovery per the instuctions. I have tried re-pointing to the Universal Naked drivers trying to select a diffrent drvier but to no avail. looks like the tablet can no longer communicate to the computer. I will copy the contents of the fastboot directory to another computer and see if that will work
any ideas?
Tim
Click to expand...
Click to collapse
Sounds like another windows driver issue .....
I really cant help much here as I dont use windows ...
But there is a short term solution at least to get you booted up ....
@ne0zone75's flashable zip twrp
Download this and move it into your folder that contains the fastboot.exe ... Then rename it to twrp.zip
Then boot into the recovery and run this command from CMD window
Code:
adb push twrp.zip /sdcard
Let that happen should not take long, find the zip file under install and flash it .....
YOU MUST DO A REBOOT AFTER THIS NOT JUST A REBOOT INTO BOOTLOADER ...
So lets run this command ....
Code:
adb reboot
Let it fully boot into a bootloop then with the buttons get back to the bootloader screen and enter RCK ...
then once you have done that continue on your way ....
Let me know this works for you ....
Thx Josh
tim2min said:
Just an observation Restorer I note that you said never to select "Wipe Data" in the boot menu but in Josh step by step he suggested to do that which can take a while. In this case it ok to do it since we are putting on a new ROM. I have my backups (blob files) as well as the NVFlash file
Tim
Click to expand...
Click to collapse
Josh has answered you. But this is another fine example of why people here keep banging on about reading things carefully and then following instructions to the letter .
Taking the Plunge
Well, after some "trying" moments I got this ROM on the Prime!...must say extremely excited seems like my TF201 has more than just a "heartbeat" left in her, shoot she may be able to run hard a little longer!. I must admit some EXTREME anxiety occured and I really got scared when after flashing hairybean/bootloader my computer could not find/see my tablet AT ALL!!. This lost of connection was madddding especially when Windows would add the tablet in device manager and you would hear the computer chime every time I connected/disconnect the USB cable from the computer while the other end was in the tablet. I had to fuss around with Android APD Interface/Android APX drivers until my computer settled on one that actually worked after running c:\fastboot>fastboot devices 50x's and if finally saw my tablet I literally shedded a tear, this is definetely not for the faint of heart...lol Needless to say I hurried up and finished going down the instructions just for fear my computer might "inexplicably " loose connection again!....lol
Many thanks to Restorer for chiming in with my question also Josh (especially for the step by step instructions) also to the whole team that made this ROM!
Just a question though: If you wanted to change the color theme on boot up (which now shows in blue "CROMBi-KK") how would I go about that?
Tim
I was trying to figure out how to install a larger GApps package on my tablet, and I used GNU parted to do repartition. I've resized the system partition to 3GB and still can't install the full package.
Anyway I didn't do anything disastrous except that I accidentally deleted misc partition, I made a new partition and name it as misc and thought it was all good.
I didn't realize what I've done until I tried to reboot, my tablet is now completely a brick, the screen doesn't turn on no matter what I do
What can I do now? Is there any possible solution?
Nathaniel_Wu said:
I was trying to figure out how to install a larger GApps package on my tablet, and I used GNU parted to do repartition. I've resized the system partition to 3GB and still can't install the full package.
Anyway I didn't do anything disastrous except that I accidentally deleted misc partition, I made a new partition and name it as misc and thought it was all good.
I didn't realize what I've done until I tried to reboot, my tablet is now completely a brick, the screen doesn't turn on no matter what I do
What can I do now? Is there any possible solution?
Click to expand...
Click to collapse
If you can't see/access device in fastboot nothing can be done short of board replacement (factory/fastboot cables won't work). Even if it does respond in fastboot only a few have been successful in reviving the device after a repartitioning which is BAD idea on this device. I lack the necessary experience so will not be able to guide you further. Assumes an unlocked bootloader; you're done if device is still locked.
Davey126 said:
If you can't see/access device in fastboot nothing can be done short of board replacement (factory/fastboot cables won't work). Even if it does respond in fastboot only a few have been successful in reviving the device after a repartitioning which is BAD idea on this device. I lack the necessary experience so will not be able to guide you further. Assumes an unlocked bootloader; you're done if device is still locked.
Click to expand...
Click to collapse
Fastboot device list doesn't show anything… My bootloader is unlocked, but that doesn't matter now I guess…:crying:
hello i think minse one is break or so, was serving in internet it hang over, now it only starts in fastboot mode, wantet to flash twrp there but comes error: fash write failure, what can i do?
brill_e said:
hello i think minse one is break or so, was serving in internet it hang over, now it only starts in fastboot mode, wantet to flash twrp there but comes error: fash write failure, what can i do?
Click to expand...
Click to collapse
Can't flash or boot TWRP on this device. Consult index or other threads for info on reloading FireOS via stock recovery.