Howdy,
Installed Goo Manager, rebooted into recovery mode on accident (I think) and now my TFP is stuck in a boot loop. Vol down + Power brings up a screen saying BOOTING RECOVERY IMAGE but I don't have one.
Anyone help??
Edit : I have NVFlash and can boot into APX mode (vol up + power).
Nightpath said:
Howdy,
Installed Goo Manager, rebooted into recovery mode on accident (I think) and now my TFP is stuck in a boot loop. Vol down + Power brings up a screen saying BOOTING RECOVERY IMAGE but I don't have one.
Anyone help??
Edit : I have NVFlash and can boot into APX mode (vol up + power).
Click to expand...
Click to collapse
If you have nvflash you must recovery.... probably your only option is if you can put it into adb mode and flash trwp to it.... unfortunately you will likely need to reinstall your rom.... it is unlocked correct? Be sure to use the right twrp... there is a different one for ics and jb... dont use the wrong one
Yeah it's unlocked and NVflashed, all that stuff.
I'm pretty pissed atm, trying to install Linux and the damned install is hanging.
Guess I might wait till tomorrow. Sigh
I might add that VOL Down + Power keeps looping, no matter what I do. Only APX Mode works.
I'm so damned lost right now, been out of the loop for 6-7 months. If anyone can give me a few pointers or a how to I'd be grateful.
Tried this :
http://forum.xda-developers.com/showpost.php?p=31858100&postcount=435
Was able to get NVFlash going in APX mode, but its still stuck in the damned boot loop ffs.
Nightpath said:
Tried this :
http://forum.xda-developers.com/showpost.php?p=31858100&postcount=435
Was able to get NVFlash going in APX mode, but its still stuck in the damned boot loop ffs.
Click to expand...
Click to collapse
Go to the androwook thread.... talk to flumpster if he can't figure it out no one can... you have gone beyond my expertise I would only be guessing at this point.
HUZZAH!!
Found this :
Depends on the kind of brick... but for the most case, you could do this...
1. Download a ROM from the Asus site and extract the blob using BlobTools (blobunpack)
2. Enter APX mode [Power + Vol-Up]
3. Run wheelie to start nvFlash mode [This is the blob.bin specific to your device generated while enabling nvFlash]
Code:
wheelie --blob blob.bin
4. Flash the bootloader
Code:
nvflash -r --download 4 blob.EBT
5. Flash the recovery image
Code:
nvflash -r --download 5 blob.SOS
6. Flash the kernel image
Code:
nvflash -r --download 6 blob.LNX
5. Flash the system image
Code:
nvflash -r --download 10 blob.APP
6. Reboot [This should reboot your device, else long-press the power button to reboot]
Code:
nvflash -r --go
Performed these steps, once I did I reset it a couple of times, now it's back to stock...time to update it again. I'm so happy n_n
So if I had NVFlash, I take it I don't lose it by doing what I did, and I can upgrade to Jelly Bean now right?
Nightpath said:
So if I had NVFlash, I take it I don't lose it by doing what I did, and I can upgrade to Jelly Bean now right?
Click to expand...
Click to collapse
I don't think you can loose Nvflash at any time. You should be able to go up to jb now yes...
How in the hell do I boot into recovery mode with TWRP?? Any ideas, I'm on ICS
Nightpath said:
How in the hell do I boot into recovery mode with TWRP?? Any ideas, I'm on ICS
Click to expand...
Click to collapse
vol down +power, when you see the white writting in top left corner release power and go vol up
Gage_Hero said:
vol down +power, when you see the white writting in top left corner release power and go vol up
Click to expand...
Click to collapse
I try it but the screen doesn't change to anything else, basically goes black.
Sigh
Think I have it all figured out...Androwook installing now with JB
TWRP was giving me some massive problems, had to work around it and reinstall a few times before updates would work.
Glad you got it going
Sent from my SGH-I747M using xda premium
Related
So I successfully (I think) took my gtab back to stock rom using NVFlash. Then When i try to install clockwork mod (to eventually move to TNT lite 4.4) I killed it. I copied over the update.zip and recovery folder when attempting to do clockwork. Then I powered down. Now it won't do anything. ie. The screen doesn't even turn on. I tried disconnecting the main battery and letting it sit for up to 20 sec but that doesn't help either. Won't turn on while holding +Vol either (that's how I tried first).
Connect it to your computer via USB and see if it's in APX mode. If it is then you'll likely need to nvflash again. If you do make sure that you are using the right drivers and bekit's 1105 image. Then once you have it up and running you'll likely need to repartition it.
ok. And if that works Can I update the tablet with the new viewsonic release or do I have to keep the old version to run clockwork and then tnt 4.4? I guess 5 has been taken down?
The latest Viewsonic release (build 4349) is NOT compatible with the standard clockworkmod.
TnTLite has been retired and replaced by it's developer with Mountain Laurel which you can find over at SlateDroid. It is based on the latest stock build so you could upgrade to that with no trouble if you choose to.
Alright. Thanks for the help so far. It was indeed still in apx mode. Any Idea's on how to get it out? I can NVFlash it with no problem but every time I reboot (update or just power down) it comes back in APX and I have to re-NVFlash.
You have an APX brick. Unless KJ Rad has come up with a fix yet your stuck right nnow nvflashing everytime you boot
starfltcdrjr said:
Alright. Thanks for the help so far. It was indeed still in apx mode. Any Idea's on how to get it out? I can NVFlash it with no problem but every time I reboot (update or just power down) it comes back in APX and I have to re-NVFlash.
Click to expand...
Click to collapse
1) nvflash - bekit's 1105 image (nvflash _gtablet_2010110500.zip)
2) wipe data/cache
3) Install CWM
4) reboot into CWM
5) repartition 2048 and 0
6) nvflash bekit's 1105 image again
7) wipe data/cache
If you get any error at any step (especially during the nvflash) stop and let me know. If you're not sure how to do any of those steps I'll be happy to point you in the right direction.
I'm hoping to have something better than this in the next few days but for now this is the best we have to get you working at a good factory load.
Ok. What do I do for steps 2-5 thanks for the help.
2) Wipe Data: This can be done either through "Settings - Security - Factory Data Reset" or Method I from http://forum.xda-developers.com/showthread.php?t=1030915
3) Install ClockworkMod (CWM): The first part of this post: http://forum.xda-developers.com/showthread.php?t=865245 (Just do the CWM install)
4) Shutdown the tablet then restart it while holding down the Volume Up key until the words "Recovery Key Detected" appear in the upper left hand corner of the VS Birds Logo screen.
5) Once in CWM, Look for partitioning under Advanced menu. Select it and answer the two questions 2048 and 0. This will take a few minutes.
update: Ok I think its out of its APX loop (somehow) Now in version 1.0-2638.
Another update:
Boy am I a dumbass. When I put the thing back together I put the VOL key in backwards.... DOH! CW mod is working fine.
I'm guessing I need to update stock software to get best results now? Is that possiblcard if I can't get it to boot in anything but APX anyway???
The best I've been able to do is using the NVFlash found here: http://droidpirate.com/2011/03/10/g-tab-users/
I can see the viewsonic splash for a split second at startup when holding the Vol+ and power then back to APX
I was hoping the data wipe would clear the loop. What ROM did you have on the device before all this started?
starfltcdrjr said:
The best I've been able to do is using the NVFlash found here: http://droidpirate.com/2011/03/10/g-tab-users/
I can see the viewsonic splash for a split second at startup when holding the Vol+ and power then back to APX
Click to expand...
Click to collapse
Two things... First, I cannot help you effectively if you choose to use resources other than those I recommend. I have no idea what is in that nvflash from droidpirate nor do I have the time to research each and every one so please use the references I provide.
Second, Are you absolutely certain that you're holding down the Volume Up key to go into recovery? You'd be amazed how many folks (myself included) make a mistake here every now and then.
update: Ok I think its out of its APX loop (somehow) Now in version 1.0-2638.
Still can't boot into CW. (VOL+ + Power) DLed version 8 from here: http://forum.xda-developers.com/showthread.php?t=865017
I'm guessing I'm unbricked but just using wrong CWMod version
is this the one I need?
I guess it depends on which ROM I'd like to run correct? If you could reccommend one and help me get there that'd be great.
That one should work fine for the ROM's on here. If you're going to use the VS stock 4349 build or one of Roebeet's ROM's from slatedroid then you'll need to use the one compiled for the 1.2 development branch.
update: Ok I think its out of its APX loop (somehow) Now in version 1.0-2638.
Another update:
Boy am I a dumbass. When I put the thing back together I put the VOL key in backwards.... DOH! CW mod is working fine.
I'm guessing I need to update stock software to get best results now? Is that possible without wifi as I won't have that until the weekend?
I've re-partitioned the SD card.
I'm going to try and get TNT light 4.2.1 from droidpirate to run
looks like TNT Lite 4.2.1 went on OK. Thanks for the help and remember + is on the right
Glad you got it working. Enjoy!
K J Rad said:
2) Wipe Data: This can be done either through "Settings - Security - Factory Data Reset" or Method I from http://forum.xda-developers.com/showthread.php?t=1030915
3) Install ClockworkMod (CWM): The first part of this post: http://forum.xda-developers.com/showthread.php?t=865245 (Just do the CWM install)
4) Shutdown the tablet then restart it while holding down the Volume Up key until the words "Recovery Key Detected" appear in the upper left hand corner of the VS Birds Logo screen.
5) Once in CWM, Look for partitioning under Advanced menu. Select it and answer the two questions 2048 and 0. This will take a few minutes.
Click to expand...
Click to collapse
Hi,
I'm in the APX loop and have been unable to progress through these instructions.
My error was that I successfully flashed CWM v08 and Vegan, then tried to use ROM Manager to switch to Cyanogen. ROM Manager forced me to update the CWM to 2.xx, and then on the reboot it had the 'Magic' error.
I've done NVFlash and can get into TnT but can't get past the APX loop to install the CWM (as per step 3) - my holding down power + vol+ just results in a black screen, then when I check for APX mode, it is still in that mode.
Step 2 (clear cache) forces a reboot - is that right? I've tried the other method of clearing cache ('Method I').
Any ideas? I only got this thing a few hours ago, lol!
simmo35 said:
Any ideas? I only got this thing a few hours ago, lol!
Click to expand...
Click to collapse
Searched APX bootloop and got this:
http://forum.xda-developers.com/showthread.php?t=994046
Worked for me.
simmo35 said:
Hi,
I'm in the APX loop and have been unable to progress through these instructions.
My error was that I successfully flashed CWM v08 and Vegan, then tried to use ROM Manager to switch to Cyanogen. ROM Manager forced me to update the CWM to 2.xx, and then on the reboot it had the 'Magic' error.
I've done NVFlash and can get into TnT but can't get past the APX loop to install the CWM (as per step 3) - my holding down power + vol+ just results in a black screen, then when I check for APX mode, it is still in that mode.
Step 2 (clear cache) forces a reboot - is that right? I've tried the other method of clearing cache ('Method I').
Any ideas? I only got this thing a few hours ago, lol!
Click to expand...
Click to collapse
And stop using ROM Manager
Yes, I know this is a common issue. But My Gtab is really stuck. I tried days of following the stock Bekit install. Everything installs just fine and after the nvflash it goes right into the opening screen and starts up normally. Never see birds.
The issue is if I power off, it cannot reboot, always goes to APX mode. I tried several times.
If I run a command such as nvflash --bl bootloader.bin --sync --go I can get back into the startup screen and the tablet runs normally.
There must be a file missing that is part of the normal booting sequence. Is there something missing that the stock install doesn't do?
Yes I have installed CWM and repartitioned and cleared the data. Many times.
Can run the tablet fine if I start it from APX mode, just can't start it from the power button.
I also tried to update to 3588 with same results. Nothing allows a boot from the power button.
I also tried all the files on the "dummies" site. 1.1 and 1.2 install and run just fine, It's just if I power down the tablet. I only get APX mode when powering up.
I also let the tablet update over the internet to version 1.2.5699. It downloaded, then did a restart and went into APX mode. When I forced a boot in APX mode it came up with an android and a red triangle. Another APX boot got me back into version 1.2.4349
Even if I do a reboot from CWM it shuts off tablet and then the power button goes into APX mode
Any help is greatly appreiated.
Try this. My old Gtablet got stuck in APX mode....was like that for about 8 or 9 months until I followed the link in this thread here...
http://forum.xda-developers.com/showpost.php?p=19175683&postcount=106
Possible vol rocker internally stuck
dcol said:
Yes, I know this is a common issue. But My Gtab is really stuck. I tried days of following the stock Bekit install. Everything installs just fine and after the nvflash it goes right into the opening screen and starts up normally. Never see birds.
The issue is if I power off, it cannot reboot, always goes to APX mode. I tried several times.
If I run a command such as nvflash --bl bootloader.bin --sync --go I can get back into the startup screen and the tablet runs normally.
There must be a file missing that is part of the normal booting sequence. Is there something missing that the stock install doesn't do?
Yes I have installed CWM and repartitioned and cleared the data. Many times.
Can run the tablet fine if I start it from APX mode, just can't start it from the power button.
I also tried to update to 3588 with same results. Nothing allows a boot from the power button.
I also tried all the files on the "dummies" site. 1.1 and 1.2 install and run just fine, It's just if I power down the tablet. I only get APX mode when powering up.
I also let the tablet update over the internet to version 1.2.5699. It downloaded, then did a restart and went into APX mode. When I forced a boot in APX mode it came up with an android and a red triangle. Another APX boot got me back into version 1.2.4349
Any help is greatly appreiated.
Click to expand...
Click to collapse
Could be the contact portion of the volume rocker is stuck (I've heard of one user with this issue). Remove the back cover & disconnect the volume switch connector at the motherboard (see attachment) and then try booting.
Al
Tried tcrews suggestion. Same result. APX only on power on. Only thing different was the partitioining 3 times. Didn't work.
Volume button works perfectly. When I am in the tablet, it adjusts volume up and down correctly.
Give K J Rad's technique a whirl.
Tried that one already. Think I am going to just toss it and give up on this and just assume there is some sort of hardware problem with this Gtablet.
I must have reflashed it at least 25 times and spent days on it. I give up. Shame it works fine if you boot it from the APX mode, just not from the power button.
dcol said:
Tried tcrews suggestion. Same result. APX only on power on. Only thing different was the partitioining 3 times. Didn't work.
Volume button works perfectly. When I am in the tablet, it adjusts volume up and down correctly.
Click to expand...
Click to collapse
Did you do all the partitionings ?
Like I said, mine was stuck for near 9 months (just kept it charged and running...if it shutdown would APX boot it).
I tried every nvflash fix that was posted but when I followed the one I linked exactly, it worked. Shocked me since I had tried so many other sure fire methods didn't.
dcol said:
Think I am going to just toss it and give up on this and just assume there is some sort of hardware problem with this Gtablet.
Click to expand...
Click to collapse
Before you give up, do this for me.
Get bekit's standard 2010110500 zip file. Edit the batch file (or shell script) in it and remove the ``--go'' parameter if there is one. Flash the images. The tablet should remain in APX mode. Now run this command:
Code:
C:\SOME\PATH> [B].\nvflash -r --read 2 a2.img --read 3 a3.img --read 4 a4.img --read 5 a5.img[/B]
After the command completes power the tablet off and immediately boot it back into APX mode. Run this command:
Code:
C:\SOME\PATH> [B].\nvflash --bl bootloader.bin --read 2 b2.img --read 3 b3.img --read 4 b4.img --read 5 b5.img --go[/B]
Let the tablet boot into the Tap 'N Tap desktop, then power off. Put the tablet into APX mode and run the previous command again (change the file names to cn.img). Now you will have 3 sets of img files. Upload all of them somewhere so I can compare them with each other and with my bekit img files.
If everything checks out ok, I'll give you another nvflash command to run and if that fails, you can give up.
I've tried all techniques posted and I can't boot anymore and don't see birds either.
I can nvflash all day long but once it shuts down, I need to use nvflash to boot it up again.
Go it.
I used nvflash to stock 1.2-4349 as I had been doing according to these instructions:
slatedroid com/topic/22124-how-to-recovery-when-gtab-does-not-turn-on-and-stay-in-apx-mode/
Then, after booting to the main screen, I let it download 1.2-5699 and shutdown.
I'm still in APX mode at this point.
Then, I referred back to those instructions and and held Vol+ along with power but I never let Vol+ go. It brought me to the blue Android recovery. I ran 'update.zip' right from that menu and it brought up something different I had never seen at the bottom in yellow text (unfortunately I was so suprised that when I grabbed the tab, I hit the home button to reboot) but it said something like /tmp/bootloader.bin=[0]....
I pressed power by itself and I finally saw birds. 4 days of this **** I'm leaving it alone for a while. :-D
after installation: recovery-clockwork-touch-5.8.1.8-tf201.zip
think my tablet is broken: (
Do not start!
if I want to run in recovery mode (PWR + Vol-down)
I have just read:
Android cardhU-user bootloader ,2.10 e. relased by "WW_epad-9.4.2.15-20120221" A03
Booting recovery kernel image
and nothing more
tablet hangs on this screen
What can I do???
ADB device not found
only works : APX mode
How about fastboot?
Sent from my Transformer Prime TF201
How can I run mode fastboot?
I choose at startup:
recovery mode - pwr+vol-
APX mode - pwr+vol+
any other combination?
RMA is probably only
http://forum.xda-developers.com/showthread.php?p=22897771
There is no APX mode here. When booting with vol -/power, and doing nothing after, you must face a screen with three icons. You go on the middle icon with vol down and validate by volume up and you're in fastboot mode.
When booting with vol down + power then immediately after volume up then you boot in recovery mode.
Are you sure to do the right thongs?
the problem is that when booting with vol -/power, I've screen with "Booting recovery kernel image" and nothing more!!
I don't have with three icons
Zenk_77 said:
the problem is that when booting with vol -/power, I've screen with "Booting recovery kernel image" and nothing more!!
I don't have with three icons
Click to expand...
Click to collapse
have you tried the 1a option form the unbricking thread?
leime68 said:
have you tried the 1a option form the unbricking thread?
Click to expand...
Click to collapse
is not possible to connection by ADB,
PC does not see the TF201 in Device Manager, and it is not a issue drivers
Zenk_77 said:
is not possible to connection by ADB,
PC does not see the TF201 in Device Manager, and it is not a issue drivers
Click to expand...
Click to collapse
I think you hard bricked your tp
but how did you brick you tp?
after installation recovery-clockwork-touch-5.8.1.8-tf201.zip
Sent from my Sensation using xda
Zenk_77 said:
after installation recovery-clockwork-touch-5.8.1.8-tf201.zip
Sent from my Sensation using xda
Click to expand...
Click to collapse
did you install It via adb?
No,
From CWM 5.5.0.4
Sent from my Sensation using xda premium
have you tried to install the drivers in apx mode?
Yes,
APX it works very well, but nothing can do about it.
When booting, are you trying to boot into recovery or is it automatically booting to recovery.
After flashing the recoveries that Roach has in his thread, you have to let the tablet try to boot normally. This is the point at which the recovery is actually flashed.
When you flash the zip it puts the files to the staging partition and then when you boot normally the staging partition flashes the new recovery.
I hope that all makes sense.
Basically if you haven't tried to boot normally since flashing the zip, then the flash process has not yet completed.
Well, I had the same problem today... and am in the same situation... rebooted the system after flashing and it just sits at the screen trying to boot into recovery... Can get into APX but not into recovery or Fastboot.
I guess I either send it in for service, or wait for NVFLasher.
Well after some long conversation with Asus, basically it is bricked. I can send it to them at my expense and they will give me a quote on repair. They said according to their records my serial number has the bootloader unlocked and is therefor off warranty.
This is true, but I just wanted to offer an update on my situation..
great , i think i did the same thing
can you pass me the contact?
Recently, I was foolish enough to play around with the tool WSG UnBricker v1.0.3, and I went to flash the recovery (option to flash own image), I then drap the one that's bundled with the tool to flash it, after that I couldn't enter the stock recovery to see the familiar dead Andy, nor can I factory reset the device any more.
When trying to factory reset it, I kept getting the error (in red) that says "Unrecoverable bootloader error 0x00000000", then the device just hangs there.
My TF201 is still locked, not rooted, it is on Jelly Bean and other functions are still OK. I can still boot it and use it normally, just can't factory reset it and get the "Unrecoverable bootloader error 0x00000000" error.
So, please, If anyone has any idea to deal with this, please help me!!! I've been looking all around but to no available. How foolish of me to have done it!!!
What exactly did you try to do with the WSG tool??
Anyway, you could try one of these methods to do a complete restore...
Download the stock ROM (http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_Prime_TF201/#download)... it has a zip within a zip... extract the first zip and you should have a file with a name like US_epad-user-10.4.2.15.zip (or WW or TW depending on which zip you downloaded)
1. Flash via recovery
- Copy the update zip (e.g. US_epad-user-10.4.2.15.zip) to your sdcard
- Open adb shell and enter the following command
Code:
echo '--update_package=/sdcard/US_epad-user-10.4.2.15.zip' >> /cache/recovery/command
- Reboot and enter recovery mode [Power + Vol Down, then select RCK and press Vol Up]
- You should see the recovery screen (green Android with progress bar)
- It should reboot & then you see the blue progress bar on the Asus splash screen
- Let it finish and boot up.
- Now start it up using the Power + Vol Down key, then use the Vol Down key to highlight Wipe Data and pre the Vol Up key. This may take a few minutes.
2. Flash via fastboot
- Extract the blob from the update zip (e.g. US_epad-user-10.4.2.15.zip) on your computer
- Start the device in fastboot mode [Power + Vol Down, then select the USB symbol and press Vol Up]
- Run the follow command in a terminal window
Code:
fastboot -i 0x0b05 flash staging blob
- You should see the fastboot command transfering the files. Once that is done, reboot
Code:
fastboot -i 0x0b05 reboot
- It should reboot & then you see the blue progress bar on the Asus splash screen
- Let it finish and boot up.
- Now start it up using the Power + Vol Down key, then use the Vol Down key to highlight Wipe Data and pre the Vol Up key. This may take a few minutes.
craigacgomez said:
What exactly did you try to do with the WSG tool??
Anyway, you could try one of these methods to do a complete restore...
Download the stock ROM (http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_Prime_TF201/#download)... it has a zip within a zip... extract the first zip and you should have a file with a name like US_epad-user-10.4.2.15.zip (or WW or TW depending on which zip you downloaded)
1. Flash via recovery
- Copy the update zip (e.g. US_epad-user-10.4.2.15.zip) to your sdcard
- Open adb shell and enter the following command
Code:
echo '--update_package=/sdcard/US_epad-user-10.4.2.15.zip' >> /cache/recovery/command
- Reboot and enter recovery mode [Power + Vol Down, then select RCK and press Vol Up]
- You should see the recovery screen (green Android with progress bar)
- It should reboot & then you see the blue progress bar on the Asus splash screen
- Let it finish and boot up.
- Now start it up using the Power + Vol Down key, then use the Vol Down key to highlight Wipe Data and pre the Vol Up key. This may take a few minutes.
2. Flash via fastboot
- Extract the blob from the update zip (e.g. US_epad-user-10.4.2.15.zip) on your computer
- Start the device in fastboot mode [Power + Vol Down, then select the USB symbol and press Vol Up]
- Run the follow command in a terminal window
Code:
fastboot -i 0x0b05 flash staging blob
- You should see the fastboot command transfering the files. Once that is done, reboot
Code:
fastboot -i 0x0b05 reboot
- It should reboot & then you see the blue progress bar on the Asus splash screen
- Let it finish and boot up.
- Now start it up using the Power + Vol Down key, then use the Vol Down key to highlight Wipe Data and pre the Vol Up key. This may take a few minutes.
Click to expand...
Click to collapse
Thanks a lot, craigacgomez!!! I had to try to use the 2nd option you gave me (flash via fastboot), as my Recovery was probably screwed; as I said before, I couldn't get into Recovery (stock recovery I think, because it's still not unlocked, not rooted), just says "Unrecoverable bootloader error 0x00000000". However, even with the 2nd option, when I try the reboot command, the device just stays there, and the writing process before it only took about 3s as the picture I attached herewith. I tried to manually reboot it after "fastboot -i 0x0b05 flash staging blob", but the device still booted as If nothing was done using the command.
I think the jellybean stock recovery is screwed, only by successfully re-flashing it, can I do the factory reset. Now, it can boot and be used normally but not factory reset. The reason I tried to play with the tool was because I am one of the very "luck" users that have to live with the infamous "Serial unknown" feature!!! For one second of misthought and alcohol, I somehow screwed it like this.
So, what can I do now to re-flash the stock recovery, please tell me! Thanks a lot again man.
I just tried to cold boot the device using the Volume down+Power and let it pass the 10s. After that, the screen says it's cold booting linux or something, then a signature match, but it hangs there. I pressed and held Power until It reboots, but this time It won't even get passed the Asus splash screen. I just officially get an expensive "temporary" paperweight!!! Someone, please help!!!!!!!
Please, anyone???
Same original problem as OP. Not sure about the bricking problem...
I also receive that error when attempting to boot from recovery. However, I can still boot normal and seems I can wipe data. Also, I can start fastboot...but it seems to only be responsive to one command before it becomes unresponsive. Adb doesn't seem to be seeing the device anymore. And I can boot into APX.
This doesn't really help the OP if bricked, but providing these details, because I am still trying to find a solution to the same original problem.
Maybe it's time for me to use Asus's warranty service?
found the solution to this problem?
found the solution to this problem? I am presenting the same problem! someone please help me
same here... I have 10.6.1.8 bootloader currently, courtesy the previous owner and I can't seem to flash anything. After sending a command to the device, it becomes unresponsive and just freezes.
Now, as it is possible to send a file over to the device, does it stay there? It looks like there is only one command that can be executed and that is sending. Maybe if the file was there, the one command would be flashing the file? Just grasping at straws
I have a similar problem.
Can access fastboot, but the unrecoverable error appears every time i enter recovery or wipe mode.
Also fastboot freezes after i flash something.
My opinion: Hard brick. You need to replace the motherboard.
I am almost ready to accept it... However, as the bootloader is from TF300, would it be possible to use those drivers to communicate with the device? I'm at work right now so can't test, but it seems like a remote possibility
Sent from my HTC Sensation using xda app-developers app
similar here
I also have the bootloader error 0x00000000,
bought the prime second hand and thought I would unlock and try some new ROM, I have done successful root flash etc on my old HTC desire to get it running JB ROMs so thought would give it a go on PRIME, big mistake!! rushed into it like an absolute moron and now have a lovely paperweight!
Everything I have read suggests this is unfixable but I found the tool WSG unbrick and thought hey hey here we go!! but no dice.
The erasing tools seem to do everything but when I tried to install the full unbrick option (write partitions) it just goes straight to the reboot menu with a message that "this menu is only for when the device is in bootloader mode" same for any other install option!
Every time I try to flash something in fastboot it seems like it disconnects or fastboot stops working,
I am pretty much ready to give up and admit defeat, phone call to ASUS!!!
example of what happens in fastboot:-
C:\Android-adb>fastboot devices
???????????? fastboot
C:\Android-adb>fastboot devices
015d078754040a06 fastboot
C:\Android-adb>fastboot flash recovery TWRP.blob
sending 'recovery' (7726 KB)...
OKAY [ 2.795s]
writing 'recovery'...
OKAY [ 1.410s]
finished. total time: 4.207s
C:\Android-adb>fastboot devices
???????????? fastboot
have to physically reboot the prime
C:\Android-adb>fastboot devices
015d078754040a06 fastboot
C:\Android-adb>
I have found a solution to my particular problem on this thread http://forum.xda-developers.com/showthread.php?t=2179759
I am writing this from my now fully functional paperweight!!!
Sent from my Transformer Prime TF201 using XDA Premium HD app
Hi,
I could really need some help.
What happend, i prepared to go from HairyBean to CM11 downloaded bootloader files roms, ...
Via the Power Menu i could not reboot into recovery so I tried via GooManager.
After this:
The Prime gets stuck hat the boot screen ( The Device is unlocked + Asus Logo )
If i reboot the device with both Vol Down + Vol Up pressed the screen stay dark but i get an APX Device ( via USB)
I red through some threads about wheelie blobs and ?? but could sort things out.
Any help is highly welcome !
Br,
Jörg
Hi,
Results so far
- can not boot to recovery
- can not boot to fastboot
- can not boot to android os
- can boot to apx (with screen dark)
which is not of any use because i do not have to blob files ( and i believe it is not possible to create them with then bootloader which was installed)
last thing it did:
boot to recovery via goomanager
so i thing this caused the brick
Br,
What happens when you power on the device while holding only the volume down button?
Sent from my SO-04E using xda app-developers app
kokopuphz said:
What happens when you power on the device while holding only the volume down button?
Sent from my SO-04E using xda app-developers app
Click to expand...
Click to collapse
It will get stuck at the screen with message:
device unlocked and the Asus logo
..invite, longer the 60 mins
br
Jörg
i to appear to be stuck in exactly the same situation, if anyone can shed any light? no errors or nothing i tried CWM install via rom manager,