Database Info

TF300 bricked?

So I've searched thru the thread...but I don't know what to search for. Let me explain my problem:
I had Unlocked the device, had TWRP as recovery and was running cleanROM 1.2. So I downloaded cleanROM 2.5 (JB) and put that on my SD card. I also read that I needed TWRP 2.2.2.0 to load it.
So I downloaded and fastbooted TWRP 2.2.2.0 ICS.blob, recovery flashed ok and was able to install cleanROM. Upon reboot, it just bootlooped.
So I figured I needed TWRP 2.2.2.0 JB.blob. I fastboot installed that with no problem but when I rebooted to fastboot mode, I stupidly selected to wipe data from there and now the tablet bootloops with no option for the fastboot. when I try to hold down the power and volume down key the device states "Android cardhu-user bootloader (2.10 e) released by "US_ePad-9.4.3.30-20120604" A03 checking for Android ota revovery" then goes to Booting recovery kernal image.
Did I kill it?

I'm going to assume from your post that you were running ICS bootloader and had never updated to stock JB, if so you were ICS.
I read your post last night but didn't have an answer to your problem so I decided to sleep on it.
If I surmised correctly in my previous statements you had an ICS bootloader and flashed a JB rom, then you flashed a JB recovery while you still had an ICS bootloader. I don't think the data wipe is a factor here. You can't mix and match ICS and JB recoveries and roms the bootloader must match.
I know; how does this help me. We need to establish your situation absolutely if there is any chance of recovery.
I'm still thinking about your situation and your reply will give myself and many others reading your post enough info to consider your options.

I fastboot is not working and you were still on ICS bootloader, try if ADB works.
If yes type this:
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
then press enter
Then type this
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
and press enter.
Now try if you get fastboot back. If yes fastboot the ICS recovery and then you should be good to go.
1st flash the ICS Stock Rom and then fastboot the ICS recovery again. Now you should be back to normal.
If this doesn´t work dl this file:
http://www.4shared.com/zip/7XYW-4c4/WSG_UnBricker_TF300T_V102.html
unpack it
run WSGFlasher batch
choose 2 as selection and press enter
in the new window choose 1 to fully unbrick and press enter
in the new window choose 1 to Full recovery and press enter
let it run. Needs about 5 to 15 minutes
When everything is done reboot.

tobdaryl said:
I'm going to assume from your post that you were running ICS bootloader and had never updated to stock JB, if so you were ICS.
I read your post last night but didn't have an answer to your problem so I decided to sleep on it.
If I surmised correctly in my previous statements you had an ICS bootloader and flashed a JB rom, then you flashed a JB recovery while you still had an ICS bootloader. I don't think the data wipe is a factor here. You can't mix and match ICS and JB recoveries and roms the bootloader must match.
I know; how does this help me. We need to establish your situation absolutely if there is any chance of recovery.
I'm still thinking about your situation and your reply will give myself and many others reading your post enough info to consider your options.
Click to expand...
Click to collapse
So I'm new to the TF300 as you can probably guess. I flash roms constantly with my S-off Rezound and my prior OG Droid. I'm not new to the game, just new to the TF300t.
I did finally grab the right keywords and found pretty similar posts to what happened to me, and it looks like I bricked it. (though I sure hope not.)
I think you are right that the data wipe isn't the factor. I just thought I needed a JB recovery to flash the JB rom. You know how a certain boot.img will just send your phone into a bootloop, but you flash the correct boot.img, and it'll boot straight into the rom? That was my thinking going into this. (guess I should have taken MORE time to read instead of bullishly charging in...
I also believe you are right in your first statement, I received the tablet with ICS. I rooted it and flashed CleanRom 1.2 immediately, and haven't flashed again. I saw jellybean (Cleanrom 2.5) out and thought, why not? Flashed TWRP 2.2.2.0 ICS and proceeded to install CleanROM 2.5. I did not know I needed to be on a JB bootloader. You are correct in that. BUT....after flashing the TWRP 2.2.2.0 JB recovery, I WAS able to go back into fastboot mode and could switch between Android/USB/Wipe Data... if only I had chosen the USB option.....
I await any help you can offer.
Thanks so much.

mikaole said:
I fastboot is not working and you were still on ICS bootloader, try if ADB works.
If yes type this:
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
then press enter
Then type this
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
and press enter.
Now try if you get fastboot back. If yes fastboot the ICS recovery and then you should be good to go.
1st flash the ICS Stock Rom and then fastboot the ICS recovery again. Now you should be back to normal.
If this doesn´t work dl this file:
http://www.4shared.com/zip/7XYW-4c4/WSG_UnBricker_TF300T_V102.html
unpack it
run WSGFlasher batch
choose 2 as selection and press enter
in the new window choose 1 to fully unbrick and press enter
in the new window choose 1 to Full recovery and press enter
let it run. Needs about 5 to 15 minutes
When everything is done reboot.
Click to expand...
Click to collapse
Thanks so much, I just returned home from a trip and will try this first thing in the morning.
Though I feel like the bootloop it's stuck in doesn't give me enough time for ADB to work. If ADB doesn't work, I think I'm bjorked.

SO if I read you guys correctly, I would manually have to flash a JB bootloader? It's not something that happens automagically when you flash a ROM? I never flashed a bootloader, just the two recoveries, then once in recovery, the ROM.

Xsoldier2000 said:
So I'm new to the TF300 as you can probably guess. I flash roms constantly with my S-off Rezound and my prior OG Droid. I'm not new to the game, just new to the TF300t.
I did finally grab the right keywords and found pretty similar posts to what happened to me, and it looks like I bricked it. (though I sure hope not.)
I think you are right that the data wipe isn't the factor. I just thought I needed a JB recovery to flash the JB rom. You know how a certain boot.img will just send your phone into a bootloop, but you flash the correct boot.img, and it'll boot straight into the rom? That was my thinking going into this. (guess I should have taken MORE time to read instead of bullishly charging in...
I also believe you are right in your first statement, I received the tablet with ICS. I rooted it and flashed CleanRom 1.2 immediately, and haven't flashed again. I saw jellybean (Cleanrom 2.5) out and thought, why not? Flashed TWRP 2.2.2.0 ICS and proceeded to install CleanROM 2.5. I did not know I needed to be on a JB bootloader. You are correct in that. BUT....after flashing the TWRP 2.2.2.0 JB recovery, I WAS able to go back into fastboot mode and could switch between Android/USB/Wipe Data... if only I had chosen the USB option.....
I await any help you can offer.
Thanks so much.
Click to expand...
Click to collapse
Please see the post directly below mine. mikaole has already provided an excellent path to recover your unit.
Good Luck!

tobdaryl said:
Please see the post directly below mine. mikaole has already provided an excellent path to recover your unit.
Good Luck!
Click to expand...
Click to collapse
Thanks all, but I can't get ADB working on it. It's just a constant reboot - loop.
I guess I need to contact ASUS and try to get it repaired... cheaply, I hope.

Xsoldier2000 said:
Thanks so much, I just returned home from a trip and will try this first thing in the morning.
Though I feel like the bootloop it's stuck in doesn't give me enough time for ADB to work. If ADB doesn't work, I think I'm bjorked.
Click to expand...
Click to collapse
Time for adb; interesting statement. It brings to mind something I have used on another unit with bootloop and on several other units to get boot logs.
I'll try to describe. In terminal you use a command and afterwards if you wish to use the same command you use up arrow and the last command is typed for you and just hit return. I think this also works in windows cmd but can't verify.
Why do we care? Get in terminal and type the first adb command given above and hit return. Now we can send this command twice in one second. Up arrow ( command typed for you ) power on unit, hit return, up arrow hit return, etc. You could verify if there is an adb window of time available by typing adb devices and look at the output. Anything other than devices and blank means there is an adb window.
Sorry; easy to do but hard to describe. Worth a try if you are ready to ship off. This is the only other thing I can think of for your situation.
Good Luck!

tobdaryl said:
Time for adb; interesting statement. It brings to mind something I have used on another unit with bootloop and on several other units to get boot logs.
I'll try to describe. In terminal you use a command and afterwards if you wish to use the same command you use up arrow and the last command is typed for you and just hit return. I think this also works in windows cmd but can't verify.
Why do we care? Get in terminal and type the first adb command given above and hit return. Now we can send this command twice in one second. Up arrow ( command typed for you ) power on unit, hit return, up arrow hit return, etc. You could verify if there is an adb window of time available by typing adb devices and look at the output. Anything other than devices and blank means there is an adb window.
Sorry; easy to do but hard to describe. Worth a try if you are ready to ship off. This is the only other thing I can think of for your situation.
Good Luck!
Click to expand...
Click to collapse
I will def. try that. I have only usually tried the adb once it's in the loop, not from cold start.
I am aware of the command line trick, I've been using Linux for about 7 years, and was surprised to see it in windows.
Great idea to get it running before hand though, enter > up Arrow . enter > up arrow......

Xsoldier2000 said:
I will def. try that. I have only usually tried the adb once it's in the loop, not from cold start.
I am aware of the command line trick, I've been using Linux for about 7 years, and was surprised to see it in windows.
Great idea to get it running before hand though, enter > up Arrow . enter > up arrow......
Click to expand...
Click to collapse
No go. I drained the battery, then plugged it in for like 20 minutes to charge. I got ADB ready with adb devices and began trying.
No devices. for the heck of it I plugged in my phone during the up arrow enter marathon, and adb picked up the phone right away.
Sucks, but thanks so much for all your help. Looking for a refurb or a repair place now.

I'm sorry but I don't know anything else to try.
There is a manual reset on the side below the sdcard.

tobdaryl said:
I'm sorry but I don't know anything else to try.
There is a manual reset on the side below the sdcard.
Click to expand...
Click to collapse
No Worries, I appreciate all your help.

My problem was more or less similar and i managed to fix mine
Link to my thread ---> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
In my case I installed the wrong recovery (TWRP-JB) with the wrong bootloader 4.2 and bricked, I also did the mistake to wipe everything. but after several tries I fixed mine, go to my thread on the link above for details.
Hope it helps.

[Utility]EZ Update Android 4.2/CWM/Root/Save Data/1 Click

Lots of people are having problems with the Android 4.2 update. They lose root or they can't get back into recovery. So BEFORE you flash 4.2 or if you already did and are having issues. Download this utility I whipped up. It will flash (or reflash) the 4.2 update (Including system, kernel and bootloader). It'll flash the latest 4.2 compatible ClockworkMod Touch Recovery. And then it'll get you all set up to re-root your N7 within the latest CWM. Instructions are included in the README file. PLEASE READ IT!
You DO NOT need to be on a stock rom to run this and it will NOT erase your data. But it is recommended when you get into CWM recovery for obvious reasons.
If anyone is having any issues and you get caught at the Google splash screen. You can use Power, Vol - to hard shut down the tablet, then Power, Vol +, Vol - to get into the bootloader. From here you can install the factory images from google. Once you're back up and running, you can run this tool to gain root and CWM back.
Updated 11/14/2012: Replaced SuperSu.apk with the latest version designed for 4.2
Updated 11/14/2012 14:41EST: This package will now contain 3 different runme files. One of them will not erase your data, one will erase your cache only and the last one will erase your data and cache. It seems people coming from some roms are having bootloops or hangs because of a lack of data wipe. You can attempt to run the one with no data wipe, but if you run into trouble, try one of the others. Some have made it through with only a cache wipe. See what works for you.
Updated 11/14/2012 16:53EST: Removed full data erase option as I forgot it will erase your SD card and therefor erase the root zip before it gets a chance to flash. There is only 1 runme file now and it will erase your cache, but leave your data alone. If you're having problems, or you want to avoid problems. Erase your data in CWM before you flash the supersu zip included in the package.
For Now - Windows ONLY, Sorry.
Linux version, on the way
Anyway:
Download and PLEASE READ the Read Me!

Saweet
Sent from my Nexus 7 using xda premium

Just trying to make it easy

im on 4.2 already ,can i use this to root?

Thanks for putting this together tucstwo, it was super helpful and easy for a lot of us here

Ok, I tried this and got stuck on the boot screen. Guess Ill try it again. I was on AOKP before.Can I just run this from there? I should I have wiped before?
edit
Ok it worked once I wiped it when it booted in CWR.
Great job. Now just have to test if it is still rooted

Im not getting something. After I press runme.bat my Nexus goes to clockwork recovery, its not touch, I have to choose from options like Start, Recovery Mode, etc. It doesnt match the instructions. Im super confused, any help?
Ugh. now my device is stuck at the google start screen, and not going anywhere. Android is too complicated sometimes for dumb people like me...

Solange82200 said:
Im not getting something. After I press runme.bat my Nexus goes to clockwork recovery, its not touch, I have to choose from options like Start, Recovery Mode, etc. It doesnt match the instructions. Im super confused, any help?
Click to expand...
Click to collapse
Its booting you in fastboot. just follow the instructions in the window that comes up when you run the runme.bat.
When it boots in fastboot just hit the space bar. It will take a couple times of hitting the spacebar before you reach the CWR stage where you flash the PlaceMeOnYourSDCardSuperSu.zip

When I click runme, it opens up the cmd window, starts the daemon, and then just sits there with a blinking cursor. Tried this few times already, nothing is happening.
EDIT: My nexus 7 is connected and has usb debugging turned on.

Hasan10 said:
When I click runme, it opens up the cmd window, starts the daemon, and then just sits there with a blinking cursor. Tried this few times already, nothing is happening.
Click to expand...
Click to collapse
Do you have ADB set up on you computer?
Did you make sure you have USB debugging selected on your nexus 7 in developer options?

trusteelfan said:
Do you have ADB set up on you computer?
Did you make sure you have USB debugging selected on your nexus 7 in developer options?
Click to expand...
Click to collapse
Figured it out. My computer recognizes the Nexus 7 as a portable device, but not recognizing it in the usb debugging mode (shows "Nexus" under Other Devices with a yellow triangle). Tried to update the driver, but it failed.

Thanks, it wasn't clear to me for some reason when I was doing it. It just kept saying after the black screen press continue, but something stopped along the way. I cant do it again because my device wont get past the Google startup screen, so I guess Im just going to flash from stock or something. Thank you for the quick help though, much appreciated!

Solange82200 said:
Thanks, it wasn't clear to me for some reason when I was doing it. It just kept saying after the black screen press continue, but something stopped along the way. I cant do it again because my device wont get past the Google startup screen, so I guess Im just going to flash from stock or something. Thank you for the quick help though, much appreciated!
Click to expand...
Click to collapse
You can run it again if it got stuck. I had to run it twice
---------- Post added at 10:04 PM ---------- Previous post was at 10:03 PM ----------
Hasan10 said:
Figured it out. My computer recognizes the Nexus 7 as a portable device, but not recognizing it in the usb debugging mode (shows "Nexus" under Other Devices with a yellow triangle). Tried to update the driver, but it failed.
Click to expand...
Click to collapse
The Nexus 7 toolkit will put the right drivers in place if you need them.

OK, I will try that.
By the way, I am currently on Android 4.1 with unlocked BL and CWM Recovery running Franco Kernel. Is this utility safe to use with this setup?
---------- Post added at 11:14 PM ---------- Previous post was at 11:07 PM ----------
OK So I have finally got the drivers, and then ran the runme. It booted me into fastboot mode and now it says sending 'bootloader' <2096 KB>... and seems to be stuck on it. I havent touched anything on my nexus 7, didn't press any buttons yet.
Unplugged it and then plugged it back in. It failed to flash the bootloader and went straight to boot and system flashing. It has now booted into Android 4.2, but I am assuming it still got the older bootloader. I think I will have to re-run the whole process to ensure new bootloader gets flashed eh? Or is there a 4.2 bootloader floating around that I can just flash using CWM and save myself the trouble?

Hasan10 said:
OK, I will try that.
By the way, I am currently on Android 4.1 with unlocked BL and CWM Recovery running Franco Kernel. Is this utility safe to use with this setup?
---------- Post added at 11:14 PM ---------- Previous post was at 11:07 PM ----------
OK So I have finally got the drivers, and then ran the runme. It booted me into fastboot mode and now it says sending 'bootloader' <2096 KB>... and seems to be stuck on it. I havent touched anything on my nexus 7, didn't press any buttons yet.
Unplugged it and then plugged it back in. It failed to flash the bootloader and went straight to boot and system flashing. It has now booted into Android 4.2, but I am assuming it still got the older bootloader. I think I will have to re-run the whole process to ensure new bootloader gets flashed eh?
Click to expand...
Click to collapse
It takes it a few minutes to run the process. You should have just waited

trusteelfan said:
It takes it a few minutes to run the process. You should have just waited
Click to expand...
Click to collapse
No I realized it didn't install the fastboot drivers before the process began. So it was actually not able to send the bootloader. Anyways, can you please read my edited post above and advise me with that to do?
EDIT: I went ahead and re-ran the process. Since all drivers were in place, the total process took less than 5 mins, arguably faster than an OTA. Still have all of my data and the goodness of 4.2.
Thanks a lot OP for this great utility.

trusteelfan said:
Ok, I tried this and got stuck on the boot screen. Guess Ill try it again. I was on AOKP before.Can I just run this from there? I should I have wiped before?
edit
Ok it worked once I wiped it when it booted in CWR.
Great job. Now just have to test if it is still rooted
Click to expand...
Click to collapse
What was it that you wiped? Just to make sure I do exactly what you did. I'm stuck on the glowing nexus logo.

essay708 said:
What was it that you wiped? Just to make sure I do exactly what you did. I'm stuck on the glowing nexus logo.
Click to expand...
Click to collapse
I had to wipe my data. It didnt like coming from AOKP

Nevermind, I wiped cache and dalvik cache and it worked for me too.

Everything is good over here. Rooted with twrp instead tho. Anyway something weird is going on with my battery, and yo seem pretty knowledgeable so I thought I'd run it by ya and see if you couldn't shed some light on the issue. Anyway my battery stats are showing that the device isn't awake.. When clearly it is and in the stats it says the screen is even on.. But not awake. Also the screen seems to brighten and dim at odd times idk if that has anything to do with it. But I flashed an ota update.. Bootloader and all. Kept root with supersu. You think something might have been corrupt or something? Here's a screenshot of the issue.. Hmm another issue, whenever I try to take a screenshot.. With more than one app, it takes a pic of an earlier point when I was on twrp getting ready for the 4.2 update. Some really strange things are going on..

help- bricked it, no recovery, what now?

Hey yall. I had the phone for 6 days before I bricked it. I am wondering if there is any stock recovery mode or anything or what I shsould do? I think something went wrong due to using the root toolbox pro app. I have done some backups within the ap as well as Titanium Backup but now the phone will not boot up and I dont know if/how to put it in factory recovery mode. Soft reset does nothing. The Motorola logo will show on startup but then the screen just blacks out forever, not off, just colored black.
A few details, the phone was rooted with Motofail2go, with no recovery and bootloader still locked as far as I know.
Should I take it to Sprint for a factory reset? Is this even an option? What are my other options?
Next time I will probably use the Moto unlock key so I can open the bootloader all legit like and have a recovery mode...

Try holding power button and the down volume key to power off. Once you power off press and hold them again. This should boot you into fastboot, Motorola's adb shell basically. This can take a couple tries, make sure the phone is powered down completely before hitting volume down and power button to get into fastboot. If you can boot into fastboot you can unlock using this guide: http://www.droid-life.com/2012/08/20/how-to-unlock-the-motorola-photon-q-bootloader/
Once unlocked flash the custom recovery of your choice (I like twrp). You can boot into custom recovery by holding volume up and the power button from a powered down state. Here is the link for instructions on how to flash twrp:
http://forum.xda-developers.com/showthread.php?t=1887070
Then you can download one of the stock backups for the Q posted in the development section and restore them using the custom recovery. Most of the ones I have seen have been compatible with twrp.
The only way to download the stock rom backups is to remove the sd card from your phone, plug your sd card into a PC or other device with a card reader, download the stock backups, and place the stock backup rom files on your sd card. Finally place the sd card with the stock backup downloads into your phone.
These backups and information on how to go through this process can be found in this thread on page 2: http://forum.xda-developers.com/showthread.php?t=2001226
The key is to make a backup of your existing rom with twrp and then move the stock backups from your sd card to the twrp/backups/yourdeiceserial/ directory. That creates a backup directory which twrp knows to look for backups in.
Don't feel bad, I've been in that state several times since getting the Q, live and learn.
Sent from my XT897 using xda app-developers app

UnicronAlpha99 said:
Try holding power button and the down volume key to power off. Once you power off press and hold them again. This should boot you into fastboot, Motorola's adb shell basically. This can take a couple tries, make sure the phone is powered down completely before hitting volume down and power button to get into fastboot. If you can boot into fastboot you can unlock using this guide: http://www.droid-life.com/2012/08/20/how-to-unlock-the-motorola-photon-q-bootloader/
Once unlocked flash the custom recovery of your choice (I like twrp). You can boot into custom recovery by holding volume up and the power button from a powered down state. Here is the link for instructions on how to flash twrp:
http://forum.xda-developers.com/showthread.php?t=1887070
Then you can download one of the stock backups for the Q posted in the development section and restore them using the custom recovery. Most of the ones I have seen have been compatible with twrp.
Don't feel bad, I've been in that state several times since getting the Q, live and learn.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
If that does not work you could drop it in water or something. You have not officially unlocked boot loader so you still have warranty. Or you could just tell sprint it quit working and act completely clueless. At least its bricked with warranty still intact.

matt2k12 said:
Hey yall. I had the phone for 6 days before I bricked it. I am wondering if there is any stock recovery mode or anything or what I shsould do? I think something went wrong due to using the root toolbox pro app. I have done some backups within the ap as well as Titanium Backup but now the phone will not boot up and I dont know if/how to put it in factory recovery mode. Soft reset does nothing. The Motorola logo will show on startup but then the screen just blacks out forever, not off, just colored black.
A few details, the phone was rooted with Motofail2go, with no recovery and bootloader still locked as far as I know.
Should I take it to Sprint for a factory reset? Is this even an option? What are my other options?
Next time I will probably use the Moto unlock key so I can open the bootloader all legit like and have a recovery mode...
Click to expand...
Click to collapse
Both of the methods above are very effective. When I had the first photon I bricked it and just dropped it in water and did a claim. Depending on the insurance you have that way may cost you $100. The other method should work. When I first got this phone I did the exact same thing and to go back and unlock then flash twrp and in stall a stock backup someone had posted.
Sent from my XT897 using Tapatalk 2

UnicronAlpha99 said:
Try holding power button and the down volume key to power off. Once you power off press and hold them again. This should boot you into fastboot, Motorola's adb shell basically. This can take a couple tries, make sure the phone is powered down completely before hitting volume down and power button to get into fastboot. If you can boot into fastboot you can unlock using this guide: http://www.droid-life.com/2012/08/20/how-to-unlock-the-motorola-photon-q-bootloader/
Click to expand...
Click to collapse
Thanks for the response. Is there anything extra extra special about getting into factory fastboot mode? I can't seem to get it done. Is there an official set of instructions anywhere? Does the phone need to be plugged into the PC? It was always my understanding (for the last week) that Power and Vol Down was the soft reset mode which reboots the phone. Therefore it always tries to reboot in normal mode. This is what keeps happening. It never powers completely down using this method.
Anyhow, once I follow your instructions, the Moto logo appears, no Sprint logo appears, the phone "powers on" but the screen is blacked out (not off). After waiting for a while at the blank/black screen, or holding down several buttons like vol or camera I get the first attachment: "Process system is not responding. Would you like to close it?" When I wait nothing happens. When I push OK nothing happens. By chance, I held down power during the notification and the power menu came up behind the ANR notice (second/third attachments). So obviously there are some things working but the main system isn't booting up. And either factory fastboot is nuked or I can't figure it out. When I power down from this accessible power menu and try to do the fastboot (Power / Vol Down) I still havent gotten it to work.
Any other ideas before I take drastic measures?
Since I bought it from Amazon would that be my best route for return or should I go thru a Sprint store?
Thanks in advance.

Hi again yall. You know once I got to thinking about it, I decided to check out the return policy on Amazon Wireless. They will accept any device under warranty for the first 30 days and it is up to Moto for the next 11 months of warranty coverage. They email me a packing label and it ships out 1 day and they ship out the new phone 1 day shipping. Hard to beat, just takes 2 days of shipping and some more fun times with my Epic, 10.1CM style, in the meantime.
Who's to say it wasnt some sort of hardware or software glitch that bricked the phone rather than my screwing around? Nobody knows and it isn't up to the consumer to prove his innocence. I bought everything legally, all the apps at the app store, and only ran the motofail2go root method. Wasn't running any custom Roms, Mods, or anything. I don't feel bad after they got me for another 2 grand for 24 months, and since I have been with Sprint for 10 years;l I have spent well over 10k or 15k with them lifetime.
If any other method pops up between now and when I ship it out I may give it a shot but if not, ah well, capitalism.

matt2k12 said:
Thanks for the response. Is there anything extra extra special about getting into factory fastboot mode? I can't seem to get it done. Is there an official set of instructions anywhere? Does the phone need to be plugged into the PC? It was always my understanding (for the last week) that Power and Vol Down was the soft reset mode which reboots the phone. Therefore it always tries to reboot in normal mode. This is what keeps happening. It never powers completely down using this method.
Anyhow, once I follow your instructions, the Moto logo appears, no Sprint logo appears, the phone "powers on" but the screen is blacked out (not off). After waiting for a while at the blank/black screen, or holding down several buttons like vol or camera I get the first attachment: "Process system is not responding. Would you like to close it?" When I wait nothing happens. When I push OK nothing happens. By chance, I held down power during the notification and the power menu came up behind the ANR notice (second/third attachments). So obviously there are some things working but the main system isn't booting up. And either factory fastboot is nuked or I can't figure it out. When I power down from this accessible power menu and try to do the fastboot (Power / Vol Down) I still havent gotten it to work.
Any other ideas before I take drastic measures?
Since I bought it from Amazon would that be my best route for return or should I go thru a Sprint store?
Thanks in advance.
Click to expand...
Click to collapse
Try using adb. If your computer has drivers on it for phone you might able to get into fast boot. If that does not work I would try Sprint store first. Have locked my phone up several times while hacking wife off in progress and have used adb every time. Only time i have been truely scared is when i soft bricked my nexus 7. had to stay at work for two hours after i got off to get it to recover because i was scared of her lol.
---------- Post added at 02:05 PM ---------- Previous post was at 01:57 PM ----------
If you get adb to recognize device you could take chance and officially unlock boot loader. Then flash twrp. There is a thread in general section about having trouble getting official update. It has a stock recovery in it. Trick would be moving files to recovery section of twrp

I have gotten the phone to soft power down and get into fast boot and custom recovery. It's a bit tricky with timing, I usually wait for the screen to go black after soft reset, let go, and immediately hold power and volume down. If you can not boot into fastboot I honestly don't know what you can do either than return the phone.
Sent from my XT897 using xda app-developers app

UnicronAlpha99 said:
I have gotten the phone to soft power down and get into fast boot and custom recovery. It's a bit tricky with timing, I usually wait for the screen to go black after soft reset, let go, and immediately hold power and volume down. If you can not boot into fastboot I honestly don't know what you can do either than return the phone.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help Unicron. I think Brandons method might be my only alternative... but you know what? I already have the box packed up to ship back to Amazon! I am still a noob; I dunno if I could go the distance on this one. I have been updating my Android SDK files since I got the phone but I never got it to recognize boot up thru ADB fastboot. disclaimer* I havent tried it in a couple days since all teh SDK updates completed.
I dunno though I am a big time DIYer when possible. If it werent for the massive amount of tape I put on the box and packing label I would already be trying this method. I can't convince myself just yet. Amazon makes it too easy. I could have the *new* phone by Friday. Then I wouldn't be wasting my remaining work week trying to hack into my personal Christmas present in order to make it function...........................................
Edit - Yes I'm impatient. My job is too demanding and I am trying to set a good precedent for 2013. Wasting the first 3 work days on a phone is not how I intend to start off the year. There is probably a valuable lesson to be learned from this as far as hacking experience and to be honest with the responses here I think I could get it to boot up from PC in SDK/ADB mode and go from there. I just didnt know if that was possible until after I made the claim with Amazon. I still have an entire day today and tomorrow if I want to indulge myself. It doesnt matter if I mail the package today or Wednesday, I can still get it by Friday. I believe this thread is still valuable because we have patterns of repeating past failures and I may find use of it when I recieve my new phone and, darn it, it mysteriously bricks as well. in the same fashion.... the only thing I was really trying to do was get all my apps on my SD card... sad huh?
Edit 2 - Opened up the box, tried fastboot and adb, nothing. Off she goes.

I don't blame you, it sounds easier to exchange in your case any way. The main suggestion I have is if you are getting into any type of build.prop or operating system tweaks that have potential to lead to boot loops or cause the phone not to boot, then unlock the bootloader and install custom recovery.
The Moto-fail method seems limited to only be able to run apps that require root. For me this has no use as I want to be able to have complete control over all aspects of the Android OS. There is not a huge mod community for the Q as yet but I believe Cyanogen will be a reality as Interloper continues working on it. I came from an Epic with Cyanogen and soft-bricked it a minimum of 50 times. CWM was very forgiving on that phone, the Q is a lot more finicky and frustrating.
If you have insurance through the carrier then you are going to pay $150 for a refurb if something goes wrong and you hard brick the phone. If you unlock bootloader and install custom recovery then you have a fail-safe in the form of nandroid backups and restores. Then you can mod away with little fear.
Good luck on the new phone and I hope you don't give up after six days of modding with the Q!
Sent from my XT897 using xda app-developers app

matt2k12 said:
Thanks for the help Unicron. I think Brandons method might be my only alternative... but you know what? I already have the box packed up to ship back to Amazon! I am still a noob; I dunno if I could go the distance on this one. I have been updating my Android SDK files since I got the phone but I never got it to recognize boot up thru ADB fastboot. disclaimer* I havent tried it in a couple days since all teh SDK updates completed.
I dunno though I am a big time DIYer when possible. If it werent for the massive amount of tape I put on the box and packing label I would already be trying this method. I can't convince myself just yet. Amazon makes it too easy. I could have the *new* phone by Friday. Then I wouldn't be wasting my remaining work week trying to hack into my personal Christmas present in order to make it function...........................................
Edit - Yes I'm impatient. My job is too demanding and I am trying to set a good precedent for 2013. Wasting the first 3 work days on a phone is not how I intend to start off the year. There is probably a valuable lesson to be learned from this as far as hacking experience and to be honest with the responses here I think I could get it to boot up from PC in SDK/ADB mode and go from there. I just didnt know if that was possible until after I made the claim with Amazon. I still have an entire day today and tomorrow if I want to indulge myself. It doesnt matter if I mail the package today or Wednesday, I can still get it by Friday. I believe this thread is still valuable because we have patterns of repeating past failures and I may find use of it when I recieve my new phone and, darn it, it mysteriously bricks as well. in the same fashion.... the only thing I was really trying to do was get all my apps on my SD card... sad huh?
Edit 2 - Opened up the box, tried fastboot and adb, nothing. Off she goes.
Click to expand...
Click to collapse
FWIW, pressing vol down + power til it resets then pressing the camera button + power once the screen is black gets you to the Boot Mode Selection Menu, where you can start recovery, fastboot, BP tools (still not sure what that is entirely) and some others. Seems to be a fairly reliable/easy method for getting to both recovery and fastboot from any point.

befrosty8612 said:
FWIW, pressing vol down + power til it resets then pressing the camera button + power once the screen is black gets you to the Boot Mode Selection Menu, where you can start recovery, fastboot, BP tools (still not sure what that is entirely) and some others. Seems to be a fairly reliable/easy method for getting to both recovery and fastboot from any point.
Click to expand...
Click to collapse
Sure wish I would have known that ahead of time. Does this work without any recovery mode and with the bootloader still locked?

matt2k12 said:
Sure wish I would have known that ahead of time. Does this work without any recovery mode and with the bootloader still locked?
Click to expand...
Click to collapse
It does work without any recovery mode and I believe it still works without the bootloader being unlocked, I didn't know about this myself until after I had already unlocked it. Sorry I couldn't help out sooner.

befrosty8612 said:
It does work without any recovery mode and I believe it still works without the bootloader being unlocked, I didn't know about this myself until after I had already unlocked it. Sorry I couldn't help out sooner.
Click to expand...
Click to collapse
Awesome, I am wanting to do the backdoor root method again but, of course, may brick it. I dont think Amazon will keep sending me new ones.... but maybe!

befrosty8612 said:
FWIW, pressing vol down + power til it resets then pressing the camera button + power once the screen is black gets you to the Boot Mode Selection Menu, where you can start recovery, fastboot, BP tools (still not sure what that is entirely) and some others. Seems to be a fairly reliable/easy method for getting to both recovery and fastboot from any point.
Click to expand...
Click to collapse
For anyone concerned, I knew it would only be a matter of time until bricking my new device. This damn Root Toolbox Pro did it to me again, and on a simple, menial task. I am going to be working thru the motions on getting this to work.
Using the instructions quoted I did get stock recovery to work or at least flash on the screen for a split second. Seems like there is a timer on the recovery screen. I am having trouble with the fastboot prompt though on the PC. Do I do it in the "platform-tools" folder which contains fastboot or in the "tools" folder of the main SDK directory? I am really a noob, can you give me the cliff notes of how to get into ADB, fastboot, etc on the Photon Q in order to do a factory reset? I already have Android SDK installed and completely up to date so that is done. And Fastboot is installed. I'm just having trouble crossing the finish line here... I can get the fastboot page opened in the stock recovery but from there I'm lost. I dont know what to type into the command prompt, in what directory, or what.... Also when I open the command prompt in the SDK folder on the PC with fastboot in the directory and type "adb reboot bootloader" it says "device not found". Maybe (surely) that is the wrong prompt?
FWIW my phone is showing the dead android guy. I didnt do anything besides try and clear up my Play Store download list which required a reboot. The phone never started back up. I dont know how much damage was done or info was lost or whatever, but seeing as how I was rooted but still locked, I had no custom recovery. So no back ups. Is there anything to restore or am I looking at a full wipe and restore?

matt2k12 said:
For anyone concerned, I knew it would only be a matter of time until bricking my new device. This damn Root Toolbox Pro did it to me again, and on a simple, menial task. I am going to be working thru the motions on getting this to work.
Using the instructions quoted I did get stock recovery to work or at least flash on the screen for a split second. Seems like there is a timer on the recovery screen. I am having trouble with the fastboot prompt though on the PC. Do I do it in the "platform-tools" folder which contains fastboot or in the "tools" folder of the main SDK directory? I am really a noob, can you give me the cliff notes of how to get into ADB, fastboot, etc on the Photon Q in order to do a factory reset? I already have Android SDK installed and completely up to date so that is done. And Fastboot is installed. I'm just having trouble crossing the finish line here... I can get the fastboot page opened in the stock recovery but from there I'm lost. I dont know what to type into the command prompt, in what directory, or what.... Also when I open the command prompt in the SDK folder on the PC with fastboot in the directory and type "adb reboot bootloader" it says "device not found". Maybe (surely) that is the wrong prompt?
FWIW my phone is showing the dead android guy. I didnt do anything besides try and clear up my Play Store download list which required a reboot. The phone never started back up. I dont know how much damage was done or info was lost or whatever, but seeing as how I was rooted but still locked, I had no custom recovery. So no back ups. Is there anything to restore or am I looking at a full wipe and restore?
Click to expand...
Click to collapse
As abnormal as it seems, your situation seems pretty normal... at least from my shoes. I went through the same scenario... I didn't know what adb was, or fastboot, etc. So, here's what I know
the fastboot commands work even if adb doesnt see it in the list of devices attached. Somehow it just works (as long as the phone is in fastboot mode).
If you're able to get to the fastboot mode, things should be okay. Just open a windows explorer window to the Platform-Tools, hold the shift key and right click on a blank space within the window, then click open command window here.
you should be able to pass any adb (if the phone is on and recognized) or fastboot (if phone is in fastboot mode) commands from that command prompt.
Also, if you have a stock recovery, CMW, or TWRP image, this is the folder to copy those .img files to. Once you get your phone into fastboot mode and its plugged into the computer, just type into the command prompt:
Code:
fastboot flash recovery recovery.img
If you're just looking to reboot the phone into recovery
If you have a CWM or TWRP recovery just replace the recovery.img with whatever the .img file that you have. Also, as a tip instead of writing the entire file name, just press the first couple letters then press the tab key within the command prompt, it should fill in the rest. keep pressing tab until you get to the .img file name you want.
To avoid doing this again, maybe I can help... what were you trying to do to begin with? From the sound of it, you were trying to root the phone with the Root Toolbox Pro but it bricked, and then you tried to reboot into recovery and then got the red android... ?

befrosty8612 said:
As abnormal as it seems, your situation seems pretty normal... at least from my shoes. I went through the same scenario... I didn't know what adb was, or fastboot, etc. So, here's what I know
the fastboot commands work even if adb doesnt see it in the list of devices attached. Somehow it just works (as long as the phone is in fastboot mode).
If you're able to get to the fastboot mode, things should be okay. Just open a windows explorer window to the Platform-Tools, hold the shift key and right click on a blank space within the window, then click open command window here.
you should be able to pass any adb (if the phone is on and recognized) or fastboot (if phone is in fastboot mode) commands from that command prompt.
Also, if you have a stock recovery, CMW, or TWRP image, this is the folder to copy those .img files to. Once you get your phone into fastboot mode and its plugged into the computer, just type into the command prompt:
Code:
fastboot flash recovery recovery.img
If you're just looking to reboot the phone into recovery
If you have a CWM or TWRP recovery just replace the recovery.img with whatever the .img file that you have. Also, as a tip instead of writing the entire file name, just press the first couple letters then press the tab key within the command prompt, it should fill in the rest. keep pressing tab until you get to the .img file name you want.
To avoid doing this again, maybe I can help... what were you trying to do to begin with? From the sound of it, you were trying to root the phone with the Root Toolbox Pro but it bricked, and then you tried to reboot into recovery and then got the red android... ?
Click to expand...
Click to collapse
Thanks for the response. So, all I have to do is: go to fastboot and flash a stock recovery image file and it will automatically wipe the phone, cache, everything, and restore the operating system? Sounds awfully easy! I found some stock files in this post : http://forum.xda-developers.com/showthread.php?t=2001226&page=2 Are these the ones you used before?
Last question: I can flash CWM or TWRP but wont be able to access them if my bootloader is locked, correct? So flashing a stock recovery will allow me to have my stock phone back again, locked and un-rooted? I guess if I cant get it to work with the stock recovery then I can unlock the bootloader and do a CWM or TWRP recovery and then flash the stock .img files?
Thanks again for your help. I already had root with the motofail2go method which I like using but seems like when I try and use some generic root feature from apps from the app store that it will crash/brick the phone cuz obviously those apps are generalized and likely to brick certain percentage of devices....

Ok what does this mean? Something with the bootlaoder obviously. Does it need to be unlocked?
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover
y qrecovery1.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (5962 KB)...
OKAY [ 0.479s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.755s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
And on the phone screen it says "invalid image size for partition recovery" twice for both times I tried this method.

You will need to flash the system image as well if you want those, as the recovery image will only flash the recovery. The files in that link are for twrp only... so you'll have to be able to get there first.
With the custom recoveries, I'm not 100% sure whether or not you will be able to use them without being unlocked. I would wait to see if anyone else can answer that question for you, but if you did try it without an unlocked bootloader, you at least have the stock recovery to fall back on if needed.
Sent from my XT897 using xda app-developers app
---------- Post added at 09:16 PM ---------- Previous post was at 09:12 PM ----------
I'm thinking it could either be that your phone is full and the image you're flashing is too large to fit on the space available...
Or you're trying to flash custom software on a locked phone.
Hopefully someone is able to answer that a little better...
Sent from my XT897 using xda app-developers app

You can't alter the stock recovery (flash a custom recovery like twrp or cwm) in fastboot without having the bootloader unlocked. Your options are to unlock your bootloader, flash custom recovery, create a backup of your current setup, download one of the stock working backups, place it in the backups folder for twrp on your external sd card, and restore one of the known working backups in the development section (befrosty linked to one). Or you could use RSD lite to return to stock using a stock factory firmware flash. That involves connecting your phone to your PC and flashing the phone back to factory stock. Information on RSD Lite and links to the FXZ's can be found here.
http://forum.xda-developers.com/showthread.php?t=2095536
Sent from my XT897 using xda app-developers app

Help, Goes straight to TWRP on startup

Hello Everyone,
I am a Noob, Yes. Please help. I was trying to install TWRP onto my TF300T. I installed it Via ADB. Had it installed with my stock ROM. I tried to do a backup so I could flash CM10. It said it wasn't mounted. I tried again and then it reboot and now goes straight to TWRP. I can get my device on ADB via the cmd screen but it says that the device is attached in recovery and my serial number is now 01233456789ABCD. Have I completely bricked my tablet? Is there anything I can do? I have been searching the forums for literally hours and am at wits end. Any suggestions would be appreciated. Sorry if this has been gone over time and time again but I can't figure it out. Please help. Thanks
Marc

To add,
When I try to do anything via fastboot it just hangs waiting for device. I can't get it to go to the fastboot page on my tablet, it just goes straight to the TWRP page.

Let me guess... You were on the Asus 4.2.1 OTA release, and installed TWRP 2.4.4.0-JB...

splashg said:
Let me guess... You were on the Asus 4.2.1 OTA release, and installed TWRP 2.4.4.0-JB...
Click to expand...
Click to collapse
Yes, that would be correct. So I managed to reset the device and cold boot back to a working device. Now i'm still wanting to flash a custom recovery and change ROMS to cyanogenmod (had it on my S1 and loved it) but am a bit nervous. How do I reset my partition and clear the old TWRP and flash a working version of CWR via fastboot or a version of TWRP that will work with my OTA rom. I thought I had done quite a bit of research before hand but am feeling a bit overwhelmed now. I don't want to go through another twelve hours of trying every trick I can find on the internet to unbrick my device.
Thanks

Just a few other things to add. So now when i have my device connected to my computer in normal function i can recognize it when I enter adb devices on my cmd prompt. Then I do the fastboot reboot bootloader which it then sends it into the fastboot screen. type in adb devices and it doesn't recognize the device anymore. I try the commands to install the cwm recovery.img and my cmd screen goes through the normal steps saying it's completed it. Then i try to reboot the device through fastboot and it freezes on the bootload screen with the green box no longer flashing on the rck box. Hold power button for six seconds to reboot and i have a working device again. So now i'm lost. How do I reset everything so I can start over, repartition so I can flash a custom recovery and carry on. any help is appreciated.

I don't know how you got yours back, even the bootloader cold-booting linux won't go into the OS for me.
That said, AFAIK, TWRP 2.4.4.0-4.2 or 2.5.0.0-4.2 are the only ones that will work with the 4.2.1 OTA update. Let me know if you somehow manage to get either on there because I can't seem to flash anything.

splashg said:
I don't know how you got yours back, even the bootloader cold-booting linux won't go into the OS for me.
That said, AFAIK, TWRP 2.4.4.0-4.2 or 2.5.0.0-4.2 are the only ones that will work with the 4.2.1 OTA update. Let me know if you somehow manage to get either on there because I can't seem to flash anything.
Click to expand...
Click to collapse
I tried flashing the new correct version of TWRP. it just freezes on the rck tab of the bootloader. It goes through the process on fastboot on my cmd prmt but does nothing on the tablet end. At least I have a working device on 4.2.1 just frustrating that TW didn't state that there is a 4.2 version not just a JB version. So now I can't get OTA updates and can't flash any custom or stock ROM's. So I'm permanently stuck with 4.2 but it's better than being stuck with a brick I guess. This isn't my first time rooting, flashing or working with ADB and fastboot. Did my research before flashing the custom recovery and thought I followed TW's steps very accurately. I hope that they update their site to stop a large number of people soft or hard bricking their devices. I at least can hold out hope that someone will figure out how to re install the bootloader. There has to be a fix as the rest of my device works so the motherboard isn't shot. Good luck. Let me know if anything or anyone figures it out.

lomoski said:
I tried flashing the new correct version of TWRP. it just freezes on the rck tab of the bootloader. It goes through the process on fastboot on my cmd prmt but does nothing on the tablet end. At least I have a working device on 4.2.1 just frustrating that TW didn't state that there is a 4.2 version not just a JB version. So now I can't get OTA updates and can't flash any custom or stock ROM's. So I'm permanently stuck with 4.2 but it's better than being stuck with a brick I guess. This isn't my first time rooting, flashing or working with ADB and fastboot. Did my research before flashing the custom recovery and thought I followed TW's steps very accurately. I hope that they update their site to stop a large number of people soft or hard bricking their devices. I at least can hold out hope that someone will figure out how to re install the bootloader. There has to be a fix as the rest of my device works so the motherboard isn't shot. Good luck. Let me know if anything or anyone figures it out.
Click to expand...
Click to collapse
I finally gave up, sent mine in today, it will cost but what the hell, i want my tablet in working order. I've tried the remedies myself, to no avail.
So off to ASUS.

Let me know what they end up charging you. I did a service request on-line, but haven't heard back yet.

steveb05 said:
Let me know what they end up charging you. I did a service request on-line, but haven't heard back yet.
Click to expand...
Click to collapse
I won't know how much it will cost until the unit is in their hands. I initiated my RMA online as well, they told me i will be contacted by phone after they examine it, I'm prepared to invest another 100 bucks as i got the unit for $299. I'll be hesitant to go much higher. I will post a number when i hear from them, if they haven't replied back to you.

I've got the same problem on my TF300T.
I'm going to try to get it working.
Not entirely sure what caused it, since I had used encryption in cm10.1 prior to flashing Asus stock 4.2.1.
BTW, I've been able to get back to fastboot by running adb reboot bootloader when TWRP is loaded.
Update: Seems to be that new 10.6.x.x bootloader... gotta love Asus :-/
--- Update II----
I can't flash anything in fastboot anymore :-/

[Q] HKC P776A Android tablet stuck in twrp/cwm bootloop

Ok I finally got this tablet rooted using some chinese oneclick root tool worked great do to it was the only kit that was able to root it and i installed supersu apk to replace to chinese version worked and i went to update supersu and hit the twrp (not knowing what it was at the tim stupid right i know lol) and now it is stuck in the twrp/cwm bootloop and i cant get into recovery mode when i try it says updating img blah blah and restarts back into the bootloop. It is running 4.1.1 JB and has a micro sd card slot.There is a pic in the atachment because i dont know how to upload it to this post but it is just a pic no "extras" are included no viruses maleware ect just a pic

parkourgamer said:
Ok I finally got this tablet rooted using some chinese oneclick root tool worked great do to it was the only kit that was able to root it and i installed supersu apk to replace to chinese version worked and i went to update supersu and hit the twrp (not knowing what it was at the tim stupid right i know lol) and now it is stuck in the twrp/cwm bootloop and i cant get into recovery mode when i try it says updating img blah blah and restarts back into the bootloop. It is running 4.1.1 JB and has a micro sd card slot.There is a pic in the atachment because i dont know how to upload it to this post but it is just a pic no "extras" are included no viruses maleware ect just a pic
Click to expand...
Click to collapse
Super old I know but my kids tablet is doing this now. Did you ever find a fix?

KilluminatiStyle said:
Super old I know but my kids tablet is doing this now. Did you ever find a fix?
Click to expand...
Click to collapse
Pro tip: Don't bumb old threads like this. You might not even have similar problems. Instead create a new thread regdaring your issue.
Now, post your tablet info HERE:
Root staus?
Can you boot in recovery? If yes what recovery do you have?
Tablet model
Android version
What happened
What have tried to fix it

janekmuric said:
Pro tip: Don't bumb old threads like this. You might not even have similar problems. Instead create a new thread regdaring your issue.
Now, post your tablet info HERE:
Root staus?
Can you boot in recovery? If yes what recovery do you have?
Tablet model
Android version
What happened
What have tried to fix it
Click to expand...
Click to collapse
Root Status = ROOTED
I cannot boot into recovery mode (but when i try i get this, look in pic 2&3)
Tablet Type = HKC (NOT HTC) p776a
ANDROID Version I think (98% shure) is 4.1.1 beta JB
What happened = A few years ago 2013 i think a got this tablet then i learned about rooting, roms, and such so i spent the next year or two trying to root the tablet. I finally got it rooted with a chinese root program and all was well (i don't remember the name of the program) then there was a update for su and i pressed the twrp/cwm mode on accident (I think I was talking to someone at the time) and now it does what is shown in the image 1 it is on some boot loop. When I try to access the hboot menu it does what is shown in these images 2&3. Also my tablet has a MicroSD card slot and the battery can not be taken out. the regular bootloop picture is image file 1 that is what it looks like when it does its continuous bootloop and P.S. the tablet turns off and on automatically during the bootloop. To try and fix it i have let it do its bootloop for hours on end turn it on and off tried looking for a compatible rom (to no avail) and let the battery completely die that is about it.

parkourgamer said:
Root Status = ROOTED
I cannot boot into recovery mode (but when i try i get this, look in pic 2&3)
Tablet Type = HKC (NOT HTC) p776a
ANDROID Version I think (98% shure) is 4.1.1 beta JB
What happened = A few years ago 2013 i think a got this tablet then i learned about rooting, roms, and such so i spent the next year or two trying to root the tablet. I finally got it rooted with a chinese root program and all was well (i don't remember the name of the program) then there was a update for su and i pressed the twrp/cwm mode on accident (I think I was talking to someone at the time) and now it does what is shown in the image 1 it is on some boot loop. When I try to access the hboot menu it does what is shown in these images 2&3. Also my tablet has a MicroSD card slot and the battery can not be taken out. the regular bootloop picture is image file 1 that is what it looks like when it does its continuous bootloop and P.S. the tablet turns off and on automatically during the bootloop. To try and fix it i have let it do its bootloop for hours on end turn it on and off tried looking for a compatible rom (to no avail) and let the battery completely die that is about it.
Click to expand...
Click to collapse
Okay. Just a few more questions.
Does your tablet boot into recovery (picture 1) even if you try to boot normally? (fastboot maybe)
Can you boot into anything else other than recovery? (try different button combinations)
Does ADB recognise your tablet when it's in recovery mode? (if you don't know about this, just post your computer OS and if you have ADB/Fastboot drivers installed on your PC)
If the anwser the the first question is no:
Does ADB recognise the device while it's in the bootloop.

janekmuric said:
Okay. Just a few more questions.
Does your tablet boot into recovery (picture 1) even if you try to boot normally? (fastboot maybe)
Can you boot into anything else other than recovery? (try different button combinations)
Does ADB recognise your tablet when it's in recovery mode? (if you don't know about this, just post your computer OS and if you have ADB/Fastboot drivers installed on your PC)
If the anwser the the first question is no:
Does ADB recognise the device while it's in the bootloop.
Click to expand...
Click to collapse
sorry, i forgot to clarify the hboot. it pops up the "words" or whatever then automatically reboots there is no way to select options or keep the device on so i cant use fastboot unless there is a way i dont know of. P.S. the tablet restarts automatically so it is on for like 25 maybe 30 seconds then shuts off then turns back on and repeats till the battery is dead. My thought originally to fix it was to get a rom put it on the sdcard and see if that works but the manufacture does not supply the rom for my model only the p771a. and the only physical buttons are the home, power, the pinhole reset button, the volume and such buttons are virtual on the screen when it is fully on. And picture 1 i dont fully know what that screen symbol is the hboot one is similar but not that but yes it does but to picture 1 nomadder what i do even if i try to get to hboot menu. Sorry if this is a "little" scattered having explaining it. If it would help i can make a video and rar it and upload it here.

parkourgamer said:
sorry, i forgot to clarify the hboot. it pops up the "words" or whatever then automatically reboots there is no way to select options or keep the device on so i cant use fastboot unless there is a way i dont know of. P.S. the tablet restarts automatically so it is on for like 25 maybe 30 seconds then shuts off then turns back on and repeats till the battery is dead. My thought originally to fix it was to get a rom put it on the sdcard and see if that works but the manufacture does not supply the rom for my model only the p771a. and the only physical buttons are the home, power, the pinhole reset button, the volume and such buttons are virtual on the screen when it is fully on. And picture 1 i dont fully know what that screen symbol is the hboot one is similar but not that but yes it does but to picture 1 nomadder what i do even if i try to get to hboot menu. Sorry if this is a "little" scattered having explaining it. If it would help i can make a video and rar it and upload it here.
Click to expand...
Click to collapse
here is the video

parkourgamer said:
sorry, i forgot to clarify the hboot. it pops up the "words" or whatever then automatically reboots there is no way to select options or keep the device on so i cant use fastboot unless there is a way i dont know of. P.S. the tablet restarts automatically so it is on for like 25 maybe 30 seconds then shuts off then turns back on and repeats till the battery is dead. My thought originally to fix it was to get a rom put it on the sdcard and see if that works but the manufacture does not supply the rom for my model only the p771a. and the only physical buttons are the home, power, the pinhole reset button, the volume and such buttons are virtual on the screen when it is fully on. And picture 1 i dont fully know what that screen symbol is the hboot one is similar but not that but yes it does but to picture 1 nomadder what i do even if i try to get to hboot menu. Sorry if this is a "little" scattered having explaining it. If it would help i can make a video and rar it and upload it here.
Click to expand...
Click to collapse
1. Download fixcache.bat.zip on your computer. Extract cachefix.bat from the file.
2. Run it. It should say just "Waiting for device..."
3. Now reset your tablet with the reset button and QUICKLY plug it into the computer and wait a few minutes.
Now try to get to that text in picture 1 and tell me what happends.
Also post the text you see on the computer from the file I sent you.
Tell me if

janekmuric said:
1. Download fixcache.bat.zip on your computer. Extract cachefix.bat from the file.
2. Run it. It should say just "Waiting for device..."
3. Now reset your tablet with the reset button and QUICKLY plug it into the computer and wait a few minutes.
Now try to get to that text in picture 1 and tell me what happends.
Also post the text you see on the computer from the file I sent you.
Tell me if
Click to expand...
Click to collapse
this is what happens to the .bat fikle when i open it

parkourgamer said:
this is what happens to the .bat fikle when i open it
Click to expand...
Click to collapse
also would there be any way to pop the hood and flip a switch to reset it like on a pc tower?

parkourgamer said:
also would there be any way to pop the hood and flip a switch to reset it like on a pc tower?
Click to expand...
Click to collapse
Umm, you said there is a reset button on the tablet so pressing that would probably reset it.
The error you are getting is because adb is not installed on your PC. Use this simple adb installer to instal adb. When installing just press yes to everything. MAKE SURE THE PHONE IS PLUGGED IN THE COMPUTER WHILE INSTALLING AND THAT IT'S ON!
Now run the file again.
If you want you can add me on Skype: janekmuric
---------- Post added at 13:51 ---------- Previous post was at 13:26 ----------
If you want to know what is happening:
You are in what's called a recovery bootloop. It's when you can't get out of the recovery. What is happening in this case is that Superuser app tried to install it's binaries via recovery. Because some people don't know how to install binaries manually, the app puts a file on the cache partition so the recovery automaticly installs the zip upon booting. Now, this would be good so you don't mess up your device, but the zip file it's trying to install is faulty so it just breaks the device.
My attept at fixing this is to delete the /cache/recovery folder so it doesn't just install the file, and instead boots into a working recovery.

janekmuric said:
Umm, you said there is a reset button on the tablet so pressing that would probably reset it.
The error you are getting is because adb is not installed on your PC. Use this simple adb installer to instal adb. When installing just press yes to everything. MAKE SURE THE PHONE IS PLUGGED IN THE COMPUTER WHILE INSTALLING AND THAT IT'S ON!
Now run the file again.
If you want you can add me on Skype: janekmuric
---------- Post added at 13:51 ---------- Previous post was at 13:26 ----------
If you want to know what is happening:
You are in what's called a recovery bootloop. It's when you can't get out of the recovery. What is happening in this case is that Superuser app tried to install it's binaries via recovery. Because some people don't know how to install binaries manually, the app puts a file on the cache partition so the recovery automaticly installs the zip upon booting. Now, this would be good so you don't mess up your device, but the zip file it's trying to install is faulty so it just breaks the device.
My attept at fixing this is to delete the /cache/recovery folder so it doesn't just install the file, and instead boots into a working recovery.
Click to expand...
Click to collapse
That would be great but i cant keep my tablet on for more than like 30 seconds before it auto shuts off and it automatically tries to go into recovery when i add power to the device it wont just boot to the OS

parkourgamer said:
That would be great but i cant keep my tablet on for more than like 30 seconds before it auto shuts off and it automatically tries to go into recovery when i add power to the device it wont just boot to the OS
Click to expand...
Click to collapse
30 seconds is more than enough. Especally with an automated script like the one I sent you.
The first thing we have to do to fix your tablet is to establish a working ADB connection. Use the ADB installer i sent you. And look up on how to install Google USB driver for ADB.

janekmuric said:
30 seconds is more than enough. Especally with an automated script like the one I sent you.
The first thing we have to do to fix your tablet is to establish a working ADB connection. Use the ADB installer i sent you. And look up on how to install Google USB driver for ADB.
Click to expand...
Click to collapse
ok will try