Database Users

HELP, Galaxy Tab 10.1 (Limited Edition) is in Infinite Reboot Loop

Starting to get frustrated. When I got the Galaxy Tab 10.1 from I/O it originally had a severe back-light bleed which I described in this thread:
http://forum.xda-developers.com/showthread.php?t=1076349
Samsung Level 3 Support was quite awesome and sent out a replacement. The back-light bleed is still somewhat present, but not nearly as bad. So a few weeks have passed and ran into another major issue: it entered a infinite reboot loop.
I have only about 10 apps or so installed from the "Featured" section in the Android Market. I have never bothered rooting this, dealing with custom ROMs, or anything of that sort.
I just get white text on the display with a black background which says:
Entering upload mode...
Upload_Cause: undefined
Holding down the power button again just takes the tablet into a infinite reboot loop. I see the start up animation and the Samsung logo, then it repeats over and over.
Samsung just set up a RMA to get this re-flashed. Anyone else have this issue? Is there an easy solution to solve this without having to send it back in?
Thanks!

And I have the same issue here any help guys!!​

same issue, looking for a solution
exact same issue. Any solution or suggestions?

I have the I/O tab, unrooted. I had the exact same issue. Just overnight the tablet went bonkers. The tablet would continually load the Samsung Splash screen over and over. If I tried to wipe the table, I got Entering upload mode, Upload undefined error. I sent my tab in after pulling my hair out trying to get a fix. I couldn't even work on the tablet because it would not hold a battery charge. Some process was constantly draining the battery. I personally wish thye would just give me a production tablet. I'm afraid that when I get it back, the problem will re-occur.

I have the regular retail version. I've had it for about 9 days and have used it every single day. Last night I downloaded 2 movies onto it and everything was fine. Today it would not power on one bit! I charge it over night so the battery shouldn't have drained. Anyone experience this before???
Nevermind: Fixed my problem by doing the following!
Press and hold the on button.
At the same time, keep a finger on the screen.
Keep watching and you might see a slight change of color on the screen.
Hold it down for 15 seconds or more. Be patient.

IO Boot Loop
same issue for me - working great then all of a sudden it froze, i rebooted and got stuck in boot loop
tried:
ODIN flash recovery - still boot loop
NVFLASH recovery - installed but cannot get into recovery mode -only fastboot and ODIN
FASTBOOT mode - adb not seeing device even though ODIN sees it - installed PDANet to get Android USB driver - still not seeing device
any thoughts?

sINCE THE release of touchwiz roms, a bootloader file is included as bootloader.tar.md5. Flashing this (repartition unselected in odin) gives you retail like options in boot screen with keys combo viz. recovery and odin. Try extracting and flashing the bootloader file from stock roms I uploaded.
COUNT:5 repetitions of this solution!Gladly, though one should bother to search!Or check the similar threads suggested when starting a thread.

thanks mughalgxt - where might this bootloader.tar.md5 be downloaded? To clarify did you mean by the extracting comment below that the bootloader you provided already contains this update?
also as for repetition - since i am still looking for a solution and some of those thread have the same symptoms (boot loop) but different solution methods (nvflash, odin, fastboot) - i thought it might make sense to add my description to my issue to apply additional context/clues
mughalgxt said:
sINCE THE release of touchwiz roms, a bootloader file is included as bootloader.tar.md5. Flashing this (repartition unselected in odin) gives you retail like options in boot screen with keys combo viz. recovery and odin. Try extracting and flashing the bootloader file from stock roms I uploaded.
COUNT:5 repetitions of this solution!Gladly, though one should bother to search!Or check the similar threads suggested when starting a thread.
Click to expand...
Click to collapse

I had uploaded a stock euro rom(check under arabic rom topic in development section), courtesy of samfirmware.com. You can extract the bootloader.tar.md5 file from the rom rar file. This will help you to force key into recovery as the boot options will be replaced from fastboot to recovery. Just make sure you don't select repartition while flashing with odin as that'd leave you bootloader locked!
Hope this clears up! Once in recovery, the options are endless!

lost2030 said:
I have the regular retail version. I've had it for about 9 days and have used it every single day. Last night I downloaded 2 movies onto it and everything was fine. Today it would not power on one bit! I charge it over night so the battery shouldn't have drained. Anyone experience this before???
Nevermind: Fixed my problem by doing the following!
Press and hold the on button.
At the same time, keep a finger on the screen.
Keep watching and you might see a slight change of color on the screen.
Hold it down for 15 seconds or more. Be patient.
Click to expand...
Click to collapse
WORKED like a charm!

Acer A200 Bricked - Can't Recover

Hello. I have an Acer Iconia Tab A200, and recently I tried a factory reset. However, due to my meddling with system files, it won't reset.
I've tried to do a hard reset (Power on, Volume+, Orientation lock switch) but it says the following:
Erasing Userdata...
Erasing Cache...
It then reboots, and does nothing. It hangs on the Acer logo.
When trying to go into recovery (Power On, Volume-), it says the following:
Erasing Cache before SD update...
SD update cmd: recovery
--update_package=SDCARD:update.zip
Booting recovery kernel image
Recovery verified fail ...
Now, I mentioned that I meddled with the System Files. Here is what I did:
1. Removed unwanted Vendor Apps
2. Removed the DEFAULT LAUNCHER <-- I think this plays a big part in this
3. Placed a CUSTOM LAUNCHER in the VENDOR APPS FILE
4. Did a FACTORY RESET
My brother is more techy than me, so he tried to fix it. However, he somehow re-locked the bootloader and even replaced the bootloader with a newer version.
I talked to Acer Support claiming it's system files corrupted itself, but they won't fix it unless I also pay to fix my cracked screen. I'm willing to do so, but hey, I'd like to see if I could save $120. I don't mind the cracked screen.
NOTES:
The Acer Iconia Tab A200, along with their other tablets, has a USB port. I can probably load stuff from there somehow, but not sure.
It is a 16GB model with a 32GB Class 10 MicroSD card in it.
Any ideas? All help is appreciated.

Vuciz said:
Hello. I have an Acer Iconia Tab A200, and recently I tried a factory reset. However, due to my meddling with system files, it won't reset.
I've tried to do a hard reset (Power on, Volume+, Orientation lock switch) but it says the following:
Erasing Userdata...
Erasing Cache...
It then reboots, and does nothing. It hangs on the Acer logo.
When trying to go into recovery (Power On, Volume-), it says the following:
Erasing Cache before SD update...
SD update cmd: recovery
--update_package=SDCARD:update.zip
Booting recovery kernel image
Recovery verified fail ...
Now, I mentioned that I meddled with the System Files. Here is what I did:
1. Removed unwanted Vendor Apps
2. Removed the DEFAULT LAUNCHER <-- I think this plays a big part in this
3. Placed a CUSTOM LAUNCHER in the VENDOR APPS FILE
4. Did a FACTORY RESET
My brother is more techy than me, so he tried to fix it. However, he somehow re-locked the bootloader and even replaced the bootloader with a newer version.
I talked to Acer Support claiming it's system files corrupted itself, but they won't fix it unless I also pay to fix my cracked screen. I'm willing to do so, but hey, I'd like to see if I could save $120. I don't mind the cracked screen.
NOTES:
The Acer Iconia Tab A200, along with their other tablets, has a USB port. I can probably load stuff from there somehow, but not sure.
It is a 16GB model with a 32GB Class 10 MicroSD card in it.
Any ideas? All help is appreciated.
Click to expand...
Click to collapse
Do you have access to any a200 Update roms? Sometimes, you can pull the update.zip from the rom, place it on your ext sd card, reboot holding Vol+ and PWR, and it might install.
MD

Moscow Desire said:
Do you have access to any a200 Update roms? Sometimes, you can pull the update.zip from the rom, place it on your ext sd card, reboot holding Vol+ and PWR, and it might install.
MD
Click to expand...
Click to collapse
I have searched for some A200 ROMs, but can't find any that work using that method. I'm open for ANY Acer A200 official ROM, then simply updating using OTA. I tried an Acer A200 Recovery Pack I found. It is the exact stock Honeycomb image, but it didn't go. It always says recovery verified fail. I cannot unlock the BootLoader either.

Stockimage flashable while having bricked /DATA Partition
Hi Vuciz,
do you still have the issue with your bricked A200 ?
I got the same problem with mine, the only solution was to send it to repair, it seems the storage controller chip has some bug which destroyed the /DATA partition unrecoverable.
if you need to revert your Tablet to an locked bootloader you have to download an StockRom and modify it by removing the partition check (called "assert") in the update script.
please send me an message if you need further assistance.
regards and good luck with your tab.

Nickbert said:
Hi Vuciz,
do you still have the issue with your bricked A200 ?
I got the same problem with mine, the only solution was to send it to repair, it seems the storage controller chip has some bug which destroyed the /DATA partition unrecoverable.
if you need to revert your Tablet to an locked bootloader you have to download an StockRom and modify it by removing the partition check (called "assert") in the update script.
please send me an message if you need further assistance.
regards and good luck with your tab.
Click to expand...
Click to collapse
Yes I do. However the screen is also cracked so they want me to pay for that. Which I'm unable to do at this time.

anything I do, fails
Vuciz said:
Yes I do. However the screen is also cracked so they want me to pay for that. Which I'm unable to do at this time.
Click to expand...
Click to collapse
I also have this tablet. I bought it for 20 bucks because the screen was cracked. replaced the screen and then found out that the bootloader was trashed. I've done almost everything I can think of to fix it. Used APX mode to get UID from ubuntu, tried to use that UID to get sbk, got the SBK and then tried using blackthunder's tool got connection failure, tried using babsector same thing, even went in ubuntu, with tablet in manual apx mode for all three and when I attempt to reflash the bootloader, all I get is that command failure message with a nvflash connection failed nv error 0x30011 message and when that happens in windows, the tablet disappears from device manager, and in ubuntu when I run nvflash with the sbk function --sbk XXXX and so on, I get the command sent failure message, and then when i rerun lsusb, the nvidia device that represents my tablet in apx mode that showed before is no longer listed unless i reboot the tablet in apx mode again. If i boot it normally, the acer logo appears and then goes to the little animation and then the iconia tab screen and thats it. I've tried attempting to flash the bootloader from that screen which i know probably wasn't going to work anyways. If anyone has any advice on something I've missed, or anything that could help, i'll all eyes. thanks in advance.

twanhines said:
I also have this tablet. I bought it for 20 bucks because the screen was cracked. replaced the screen and then found out that the bootloader was trashed. I've done almost everything I can think of to fix it. Used APX mode to get UID from ubuntu, tried to use that UID to get sbk, got the SBK and then tried using blackthunder's tool got connection failure, tried using babsector same thing, even went in ubuntu, with tablet in manual apx mode for all three and when I attempt to reflash the bootloader, all I get is that command failure message with a nvflash connection failed nv error 0x30011 message and when that happens in windows, the tablet disappears from device manager, and in ubuntu when I run nvflash with the sbk function --sbk XXXX and so on, I get the command sent failure message, and then when i rerun lsusb, the nvidia device that represents my tablet in apx mode that showed before is no longer listed unless i reboot the tablet in apx mode again. If i boot it normally, the acer logo appears and then goes to the little animation and then the iconia tab screen and thats it. I've tried attempting to flash the bootloader from that screen which i know probably wasn't going to work anyways. If anyone has any advice on something I've missed, or anything that could help, i'll all eyes. thanks in advance.
Click to expand...
Click to collapse
Just so you know, I was never able to resolve this issue.

Hello,
I search help for my Acer Iconia Tab A200.
During a flash with TWRP, it block and I have to set my A200 off using Power.
And then, my A200 don't work, don't vibrate.
I try :
Reset + Power : nothing, no vibration
Power + Vol- : nothing, no vibration
Power + Vol+ + switch : same result
Connected to PC : adb devices : nothing
All commands adb or fastboot : waiting for device
I don't know what to do...

where can I send my Acer tablet to fixed stuck on bootloader
hello I have an acer iconia 200 stuck bootloader cant find anyone to fix it. Acer wont touch it unless its under warrenty! my 90 day store warrenty has been way past! taken to 2 local computer tech both told me I needed to send it back to acer but I cant! so what can ido i or where can I send it?? anyones time and effort would greatly appreicated!!! thanx for your time

[ TF300T ] How to unbrick when wrong recovery menu was flashed.

This is how I unbricked my TF300T that had no rom installed and a wrong bootloader/recovery combination. (4.2 bootloader with TWRP recovery JB version). Hope it helps.:good:
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster <----(credits to him) Go to this link ---> http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12 because that's the guy that wrote this procedure from above (credits to him) :
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This part was me now -ozkrtech <--- (credits to me)
In addition to that, if you simply can't see your device using the command "adb devices" go check on device manager if you see a device called just "Transformer" with a yellow icon indicating it needs a driver, and manually update driver, select "browse my computer for drivers" and then select let me pick from a list of device drivers on my computer" there you will see a list of like 3 different drivers, one of them says "bootloader" and one of the others says "adb" (i think they self explain) but just in case try with each one of them you can keep on switching drivers until you get your device recognized by the command "adb devices".
You should be asking yourself... whats the right moment to do an "adb devices" command? well my tablet same as -Buster's tablet had the wrong recovery menu flashed (wrong bootloader version) and it just kept booting into the corrupted recovery (in my case TWRP) with the "can't mount anything" and "what's the password" issue. When you get to password screen just hit cancel and try the "adb devices" commando and you'll see it gets recognized with your device serial number.
Once your device gets recognized by "adb devices" command you will proceed to use "adb reboot-bootloader" command and the tablet will reboot into the menu that had 4 options but now have 3 options and its missing the fastboot option (don't panic) in the last bootloader it is auto-fastboot mode when you reach that screen with just 3 options in it now (yeah is the screen with the RCK option) at this point try "fastboot devices" command to see if your device gets recognized same as "adb devices" procedure, it should get recognized with a different serial number (don't know why, maybe that number isn't a serial number), at this time you are SO LUCKY! now you will follow what I posted at the beginning from that other dude ---> (-Buster) or follow his link --- > http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
And you'll have an unbricked tf300t in no time =) (I personally used the stock but newest Asus ROM) 4.2.1 (10.6.1.27.1) and it worked flawlessly.
**NOTE** don't turn off nor reset your device once you have formatted the partitions, no need for that (don't know what happends but it might get really hard bricked) just proceed to flash the stock rom after erasing the partitions.
I'm 100% positive this will work if your device is in same state as ours. (had TWRP for JB) then updated bootloader to version 4.2 and forgot to update twrp to version 4.2 or installed twrp version JB by mistake and lost fastboot and TWRP is asking password.
Hope it helps. Let me know your status and if it worked for you.

So I am in the same boat as I flashed the wrong twrp. My device shows up under adb devices and I can boot into the bootloader using adb reboot-bootloader. However, once there, I can not get the device recognized with fastboot. I have tried messing with the drivers like you suggested but nothing will get it to show up with fastboot. Anybody have advice on where to go from here?
So extra info. The device bootloops into twrp 2.6. The only way I can boot into fastboot mode is with adb reboot-bootloader and I can get into APX. I can also boot directly into my current ROM (Slim beta 3) by selecting android in the bootloader menu. I have tried flashing proper recovery through flashify, which is says was successful, but the wrong twrp never gets overwritten. Rebooting the device will send it back to twrp.
Thanks if anyone can help

Thanks, man! It took a while to find this thread, but this was exactly my problem. The adb driver in windows was the pre-solution to help get back to the fastboot server in the bootloader. Awesome information. Thanks again!

I have tried "adb reboot-bootloader" and then adb devices and fastboot devices and neither will show the tab listed while the tab reaches that screen with just 3 options. I have uninstalled reinstalled drivers, it does show in device manager as Asus Android Composite ADB Interface but when running the command it will not list the tablet. Any suggestions?

Hello!
A few days ago I tried to root my Asus TF300T because before that, I changed the lcd and the touchscreen from FPC-1 to G01 version. So I had to root and update touchscreen's firmware to 02-3011-4820.ekt. I already updated with last firmware from asus.com. First, I installed a TRWP recovery but was useless since the touchscreen doesn't worked. So I tried to rewrite CWM recovery. I reset it and I don't remember exactly if I begun to install or not CWM but when I tried to wipe data (Vol- + Power), the tablet has freezed. After a few minutes I did a hardware reset (pin hole). Since that, the tablet freeze with "Device Unlocked", Asus logo and nVidia. The device was already unlocked. I don't have any backup from it. No fastboot, no adb. Just APX mode. Is it possible to do something with it anymore? I tried BootTools2, extracted bloobs from last version of firmware, tryed to flash them with nvflash and wheelie but vainly. What is the next step? I'm a beginner!
Remember please I cannot go in fastboot recovery menu, only apx. Thank you in advance!

I can not thank you enough!!! my tablet is now working I honestly though it was done for aha THANK YOU!!!

Howdy, folks. I recently bricked my tablet thanks to a bad install of CWM, but following the OP's guide I was successfully able to reflash stock firmware and the device runs fine now.
However, upon reflashing said firmware, it became apparent to me (from reading various threads in the development subforum), that I would need to downgrade to an older firmware version to reflash TWRP. So I did that successfully, but now I am having a problem similar, or perhaps identical, to that of Bionicbowtieguy, in that ADB appears to be broken for my tablet. I have tried uninstalling and reinstalling the Asus usb drivers, in addition to reinstalling/updating all of the ADB software. Fastboot still works fine, but as such I'm unable to root using Motochop's rooting kit (I know there are other methods out there), nor am I able to flash a new recovery. I have also tried repeatedly reflashing the older stock in the hopes that ADB would magically start working again to no avail.
Does anyone have any suggestions to getting ADB to work for my tablet again? I have scoured the web, particularly these forums, for days looking for an answer, but haven't turned anything up yet. Any help would be greatly appreciated.

Gave back 10 years of my life that I lost once I discovered I flashed the wrong TWRP version. Can't thank you enough man.

Kombatant said:
Gave back 10 years of my life that I lost once I discovered I flashed the wrong TWRP version. Can't thank you enough man.
Click to expand...
Click to collapse
Same here!
Thank you OP for making this a topic even if you didn't come up with it you made it a thread that has saved a few people like myself money and headaches. Literally I just stumbled on this thread 10 minutes after I told my wife is be Tablet shipping Black Friday. Thank you sir.

Thank you.
I did this on a hackintosh running OSX since on Win 8.1 fastboot kept crashing.
March of this year I bricked my tablet during that 1 week period where nobody knew that TWRP was broken + fastboot freezing.
I must have tried everything, Maybe that erase misc was the key factor for success.
I was about to sell this for what I could get or send it to asus, now I can use it again!

How are you guys getting your tablet into fastboot mode? I've tried power on with volume down, the reset hole with volume down, and letting the battery die then recharge, then power on with volume down... Nothing. What am I doing wrong?
Sent from my Galaxy Nexus using Tapatalk

Best thread ever!! You are a life saver !!! thank you!!

leris2 said:
Best thread ever!! You are a life saver !!! thank you!!
Click to expand...
Click to collapse
Indeed. You are a god among men. Thank you so much

This worked! I thought I was out of luck. Thanks a lot.
I accidentally flashed an incomparable version of twrp. It would only boot straight into recovery and I couldn't get into recovery. TWRP kept asking for a password even though I never set one up and it wouldn't mount the internal storage or sd card.
I had to follow the instructions at the bottom to intall the drivers so adb and fastboot to work. After that I followed the instructions at the top.
The only thing different I did was skip the "fastboot erase boot" step. I was afraid that would really brick my device if I screwed up (Does this really erase the bootaloader leaving the device with no bootloader?).

Just wondering how long the fastboot window sits displaying < waiting for device > ? All my drivers are ok and I my pad shows up fine as a fastboot device in windows.
Cheers

Fastboot
Bolandk said:
Just wondering how long the fastboot window sits displaying < waiting for device > ? All my drivers are ok and I my pad shows up fine as a fastboot device in windows.
Cheers
Click to expand...
Click to collapse
They do not sit at all they will go right to it. You must not have the right combination yet. Keep trying.
Took me awhile to get the link.
norm883

FIXED!
BY GOD, I have no words for how incredible grateful I am right now! You not only saved my TF300T's life but also a lot of money for me and gave me another lesson of Android insight.
Thanks so much for this!
Let me know if I can return the favor somehow!
Regards,
(a very happy) philleicht

Hi. I think I'm having the same problem as some of the others in this thread.
Background: Tablet is unlocked, JB Rom (Paranoid Android) was installed since March, along with TWRP recovery. In preparation of installing CM11, I used Android Terminal Emulator to install the latest TWRP from a *.blob file, but I found that the latest TWRP is still not CM11-ready...
Setup to Issue: Last night, I decided I wanted to put CM11 on my TF300T. TWRP doesn't have a compatible recovery out for CM11 (install of CM11 rom fails every time), so I reinstalled the paranoid android ROM, and attempted to get the latest recovery from clockworkmod. On cwm's website, they only have choices for "transformer" "transformer prime" and "transformer infinity" which, when downloaded, have tf101, tf201, and tf700 in their filenames. (No tf300, that is)
So... I attempted to install the tf201 recovery (closest to mine, right?) by renaming the file cwm.blob, and using android terminal emulator to install it, the same way I did with TWRP. The first few times I tried and rebooted into recovery... TWRP was still installed... which was weird to me.
The big problem: Ultimately... when I rebooted the tablet, I just see the initial "ASUS" screen with "The Device is UnLocked." in the top-left corner. When I hold the power button to turn it off... it powers back on within a few seconds, and stays at the "ASUS" screen again. It will not stay off... and will not show anything but the "ASUS" splash screen. (With one exception, described later - "the only ray of hope...") If I hold the volume up or down buttons when powering on the device, absolutely nothing different happens. (since it doesn't STAY off... I've tried all kinds of different combinations of pushing/holding the appropriate buttons for when the tablet comes back on) IMPORTANT: I never see the "three icons" as expected when holding the volume button(s). No RCK, USB, etc... when the unit turns back on, it goes to the ASUS screen, and stays there until the battery dies. As a result... I can't get into recovery, fastboot, or APX or whatever in the traditional way.
Pressing the reset button alone, or reset + volume down has the effect of temporarily turning off the unit and then on again, the same as holding the power button to turn it off and letting it turn itself back on again.
The only ray of hope that I have is that *sometimes* if I press reset + volume up with the USB cable connected to a computer... the screen will STAY BLACK, but the "device connected" sound will play on my PC (Win 7 x64) as if I just plugged the tablet into USB on my computer, and I will get a message that it's trying to install an APX device. However, it eventually tells me that the device driver could not be installed. The screen on the tablet stays black in this case... until I reset it, hold the power button, etc.
So... I'm not opposed to (or unfamiliar with) using fastboot or any other command-line app to resurrect my tablet... I just haven't been able to get it into a condition that I can try something like that yet.
Is there any hope for my tablet? Somebody please help me. I'm open to sending a few bucks via paypal or google wallet to anyone that can lead me to a resolution. That would be cheaper than buying a new tablet... not to mention the priceless value of the progress I have in Fieldrunners 2. lol.
Thanks for your time!
~Ryan

same problem reboot back to twrp
well i may be stupid because i can't understand why i have tried a couple of commands and i still get the same problem reset volume down still goes back to twrp and ask for a password can someone please explain this in alittle more detail and what commands i also get the waiting for device in my commands is there another way to push these files into this device tf201 please help is there a way to do something in the twrp recovery like terminal command

I was a fool for flashing wrong recovery!
DrPhant0m said:
Hi. I think I'm having the same problem as some of the others in this thread.
Background: Tablet is unlocked, JB Rom (Paranoid Android) was installed since March, along with TWRP recovery. In preparation of installing CM11, I used Android Terminal Emulator to install the latest TWRP from a *.blob file, but I found that the latest TWRP is still not CM11-ready...
Setup to Issue: Last night, I decided I wanted to put CM11 on my TF300T. TWRP doesn't have a compatible recovery out for CM11 (install of CM11 rom fails every time), so I reinstalled the paranoid android ROM, and attempted to get the latest recovery from clockworkmod. On cwm's website, they only have choices for "transformer" "transformer prime" and "transformer infinity" which, when downloaded, have tf101, tf201, and tf700 in their filenames. (No tf300, that is)
So... I attempted to install the tf201 recovery (closest to mine, right?) by renaming the file cwm.blob, and using android terminal emulator to install it, the same way I did with TWRP. The first few times I tried and rebooted into recovery... TWRP was still installed... which was weird to me.
The big problem: Ultimately... when I rebooted the tablet, I just see the initial "ASUS" screen with "The Device is UnLocked." in the top-left corner. When I hold the power button to turn it off... it powers back on within a few seconds, and stays at the "ASUS" screen again. It will not stay off... and will not show anything but the "ASUS" splash screen. (With one exception, described later - "the only ray of hope...") If I hold the volume up or down buttons when powering on the device, absolutely nothing different happens. (since it doesn't STAY off... I've tried all kinds of different combinations of pushing/holding the appropriate buttons for when the tablet comes back on) IMPORTANT: I never see the "three icons" as expected when holding the volume button(s). No RCK, USB, etc... when the unit turns back on, it goes to the ASUS screen, and stays there until the battery dies. As a result... I can't get into recovery, fastboot, or APX or whatever in the traditional way.
Pressing the reset button alone, or reset + volume down has the effect of temporarily turning off the unit and then on again, the same as holding the power button to turn it off and letting it turn itself back on again.
The only ray of hope that I have is that *sometimes* if I press reset + volume up with the USB cable connected to a computer... the screen will STAY BLACK, but the "device connected" sound will play on my PC (Win 7 x64) as if I just plugged the tablet into USB on my computer, and I will get a message that it's trying to install an APX device. However, it eventually tells me that the device driver could not be installed. The screen on the tablet stays black in this case... until I reset it, hold the power button, etc.
So... I'm not opposed to (or unfamiliar with) using fastboot or any other command-line app to resurrect my tablet... I just haven't been able to get it into a condition that I can try something like that yet.
Is there any hope for my tablet? Somebody please help me. I'm open to sending a few bucks via paypal or google wallet to anyone that can lead me to a resolution. That would be cheaper than buying a new tablet... not to mention the priceless value of the progress I have in Fieldrunners 2. lol.
Thanks for your time!
~Ryan
Click to expand...
Click to collapse
I have exactly this! I hope someone knows the answer for this issue. Else the tablet will learn how to fly!
I tried to push the reset button as described earlier but nothing changes. Not able to go into recovery Just stuck at ASUS in the middle NVidia in the bottomright corner en upperleft corner 'this device is unlocked'

[Q] A500 Android Screen Bootloop

I have an Acer a500 8gb version which I bought and gave to my girlfriend. It was on ICS stock. Stock everything, never rooted. Recently it ran out of battery and now when it only loads into the android screen and bootloops there.
I have tried the software reset button press and rotation lock method without any luck. it just says Erasing Userdata.. Erasing cache... blacks out and reboots back into the bootloop.
I have tried the update.zip methods with the three remaining roms I could find on the stock firmware forum but every time I try each one, it just loads with the red exclamation with the android laying down.
Was going to try flashing the EUU one, but I can't seem to get my CPUID as blackthunders A500 manager needs to have USB debug on, which I don't think was set before the tablet went bad. Just wanted to see what my options are as I am feeling a bit stuck right now. I have been searching the forum pretty tirelessly, but it is getting hard to figure what choices I have left. Any help would be much appreciated.

Bricked Hp Slate Extreme7

Have had this running on stock rom ever since i got it several months ago. From what i understand these are a tegra note 7 with a different name on it. Bottom line is it had a OTA update and i decided finally to let it run. Probably shouldn't have. It downloaded and rebooted into recovery and installed, After the install was complete the screen turned black and it seized to function. No buttons worked no screen nothing. What i have figured out so far it is in APX mode for some reason. From what i have read so far i have to flash it using nvflash. So far i have downloaded the Advent tool to reflash but cannot get it to do anything so far. Can run the command to start it but that's all it does it never gets past the start I really like this tablet and according to HP my warranty is expired so i really need some help trying to get this thing re-flashed and working
Was having issues with not running due to not being able to read the serial. So then tried this command that was suggested to try "nvflash --blob blob.bin --bct flash_signed.bct --setbct --odmdata 0x4069E000 --odm limitedpowermode --configfile flash_signed.cfg --create --bl bootloader_signed.bin --reset normal 0 " However i get the same result it says nvflash and blob are started but that is as far as it goes just a blinking cursor. Have let it sit over a half hour and nothing. The only thing my tablet does is power off or APX mode is does not matter what key combinations I use.
This is as far as it goes
C:\Users\slick\Desktop\VegaNote7\VegaNote7>nvflash --blob blob.bin --bct flash_s
igned.bct --setbct --odmdata 0x4069E000 --odm limitedpowermode --configfile flas
h_signed.cfg --create --bl bootloader_signed.bin --reset normal 0
Nvflash 3.09.1700 started
Using blob 3.09.1700
chip uid from BR is: 0x600000015c4110c62400000009ff0540

I have a funny feeling that the HP Slate Extreme 7 has a different odmdata code which might be why it doesn't work for you in APX mode.