Hi !
I´ve got a serious problem with my device (TF101).:crying:
When I had default ROM by Asus (4.0.3), system sometimes rebooting about twice down per day. But system always booted and worked "fine".
After time a made root (one click root), next I made install recovery-clockwork-touch-5.8.1.8-tf101-repack. Then I made full wipe and flashed ROM. I tried Revolver, Revolution CM10 .. Every rom install is good, but after few hours system frozen.
When I made restart stay stuck on boot logo on every times, helps only full wipe. but after is happend over and over..
Does anybody know what to do?
Thank you so much for your time !
Sorry about my english
Tom
Maybe try an other kernel (kat kernel work fine for me...)
Envoyé depuis mon Galaxy Nexus avec Tapatalk
If you want to know "why" it happens, try "adb logcat" while your device is connected and booting forever. It'll show what's going on.
TWRP is the recommended recovery nowadays it seems, you can install it from Goo Manager (link in my sig).
Thank you guys
[ADB logcat] How can I do that? I must install logcat apk into device, turn on debug mod and next ?
Thank you for your answer.
galvanizer said:
Thank you guys
[ADB logcat] How can I do that? I must install logcat apk into device, turn on debug mod and next ?
Thank you for your answer.
Click to expand...
Click to collapse
You need to connect your tablet via USB to your computer and have USB debugging enabled in Settings - Dev Options.
Install the universal naked drivers for the TF101 to get the ADB device recognized.
Then get the adb.exe file from the Android SDK.
In a command prompt on your PC run the command "adb logcat" from the folder with the adb.exe file in it.
galvanizer said:
After time a made root (one click root), next I made install recovery-clockwork-touch-5.8.1.8-tf101-repack. Then I made full wipe and flashed ROM. I tried Revolver ICS, Revolution ICS CM10 JellyBean .. Every rom install is good, but after few hours system frozen.
When I made restart stay stuck on boot logo on every times, helps only full wipe. but after is happend over and over..
Tom
Click to expand...
Click to collapse
Hi Tom,
Looking at your post, I am curious how you went from CM10 back to ICS. Did you restore a Nandroid or just simply flash an ICS ROM straight away? The thing is, you can't go from JellyBean back to ICS as the partition layouts are different.
Here is my thinking. Use Easyflasher from the Development section and flash back to stock ICS. You can find the stock firmwares here. You can even flash a custom recovery through EasyFlasher as well.
I think that you need a "Truely" clean restart as I am betting something got cross flashed somewhere.
Okey, I´ll flash stock ROM
but one simply question > i downloaded naked driver > connect with PC (debug mod is on) > in device manager uninstall every befere install drivers > and I update new drivers to ASUS android device and asus MTP device, right?
Must I see new storage disk in My compter(Transformer) or not ? Because I cant see nothing.
Thanks all of you !
No. You download the Naked Drivers and put them somewhere. Then boot your Tablet into APX mode (Power + Volume Up at same time). In APX mode your screen will not turn on nor will it be "seen" as a storage/MTP device. Plug into PC and it should download the drivers itself (if Win7 machine). If not then go into Device Manager and find the APX with the yellow ! next to it. Hit Install Drivers from location and point it to the Naked Drivers you downloaded. From there you should be good to go in EasyFlasher.
Take care though, EasyFlasher will wipe your internal SD.
Same with the ADB driver. It will not be the MTP device, it will be another device in the device tree.
Damn, really in time Thanks:good:
Okey, I switched to APX mode, install manualy naked drivers successfully. After that I start easyFlasher (downloaded custom rom into asusupdate folder).
Next I flashed STOCK .. program progress bar is in 10% and showing "Extract files, please wait" for 10 minutes.. Is normally?
I dont think so .. what now?
Thanks!
galvanizer said:
Damn, really in time Thanks:good:
Okey, I switched to APX mode, install manualy naked drivers successfully. After that I start easyFlasher (downloaded custom rom into asusupdate folder).
Next I flashed STOCK .. program progress bar is in 10% and showing "Extract files, please wait" for 10 minutes.. Is normally?
I dont think so .. what now?
Thanks!
Click to expand...
Click to collapse
It is normal. Took me about 15 mins for it to fully run it's actions.
Not sure about putting a custom ROM in the asusupdate folder though as I think it has to be stock to work correctly. Not sure if you use SBK1 or SBK2. It kind of depends on your device. The EasyFlasher OP tells what the difference is.
Woody said:
It is normal. Took me about 15 mins for it to fully run it's actions.
Not sure about putting a custom ROM in the asusupdate folder though as I think it has to be stock to work correctly. Not sure if you use SBK1 or SBK2. It kind of depends on your device. The EasyFlasher OP tells what the difference is.
Click to expand...
Click to collapse
Good, im waiting (btw still 10% progress) .. I use SBK2 (on my box of transformer is serial number B80KA ******) I decide is SBK2, right?
For now, I thank you so much !
I do this operation on my notebook (win7) behind me. A i dont see alert with commander rewrite all I press ALL. Next alert was about is in my device in APX mode > OK > finally shows some progress!
Edit:
Yes !! It works ! I have stock rom now !
So main reason why I flash another ROM was than original rom by asus does about 2 restart per day I want to try another rom but, how can i do that? I dont want be in exactly case like now.
Thanks!
Welcome back my friend.
Ok, all you have to do in EasyFlasher is see the box in the upper left corner? It will say recovery. Click the dropdown to pick the recovery that you want (I use TWRP). Hit it and Start. Once it is done, you can reboot just to be safe. Once that pulls up, shut the tablet down. Then use the finger combo to reboot into recovery (Power + Volume Down, see writing in upper left and then hit Volume Up and release Power). It will boot into which ever recovery you chose to flash in EasyFlasher.
The TWPR in Easy is outdated (but still works). Once I go where I needed to go, I installed Goomanager from the market and updated my recovery to most current version.
Good luck and now you know how to get out of a real bad situation. Happy Flashing.
Thanks,
but bad situation is back now, I do what you writed before (your post was sending) I install Rogue and i want start device its again stuck on boot logo :-/ So i switched to APX mode and flash TWRP and wipe all..
Why stuck on boot logo again ?
If you're trying to install 4.2 you need a compatible recovery. You can install the latest TWRP from GooManager (TWRP link in my sig), then 4.2 roms should work without problems.
Edit: I think you need at least TWRP 2.3.2.x
Lethe6 said:
If you're trying to install 4.2 you need a compatible recovery. You can install TWRP for GooManager (TWRP link in my sig), then 4.2 roms should work without problems.
Click to expand...
Click to collapse
Yes, but i have stock ROM by ASUS now again stuck on boot logo animation
Oh sorry I thought you flashed another rom. You can install logcat live on your device or use "adb logcat" to see what's going on.
Which boot logo? The first one with Asus "innovation" stuff or the one after that with the small text gone?
---------- Post added at 04:49 PM ---------- Previous post was at 04:47 PM ----------
Also did you reinstall any apps at all before you flashed your recovery? Maybe it's an app causing it.
Lethe6 said:
Oh sorry I thought you flashed another rom. You can install logcat live on your device or use "adb logcat" to see what's going on.
Which boot logo? The first one with Asus "innovation" stuff or the one after that with the small text gone?
---------- Post added at 04:49 PM ---------- Previous post was at 04:47 PM ----------
Also did you reinstall any apps at all before you flashed your recovery? Maybe it's an app causing it.
Click to expand...
Click to collapse
Now my transformer runs thanks god 6 minutes up time, i have clean stock rom without app.
But problem is that after while tablet freeze and restarts and stuck on boot logo ASUS animation with running circle over and over.
frederuco said:
You need to connect your tablet via USB to your computer and have USB debugging enabled in Settings - Dev Options.
Install the universal naked drivers for the TF101 to get the ADB device recognized.
Then get the adb.exe file from the Android SDK.
In a command prompt on your PC run the command "adb logcat" from the folder with the adb.exe file in it.
Click to expand...
Click to collapse
Sorry, but where I get adb.exe file? On storage in android?
edit: Stupid question, I tried this http://forum.xda-developers.com/showthread.php?t=1071584
Related
I rooted my Asus Transformer TF101-B1, but I can't get into Recovery. I know rooting was successful because I get the # prompt in ADB shell and can run root-only apps like Titanium Backup. I've tried every method for getting into CWM/Recovery that I've been able to turn up on XDA and Google, including:
* Running "adb reboot recovery"
* Holding Power + Vol down during boot, then pressing Vol up within 5 seconds of the device powering on.
* Selecting "reboot into recovery" from the ROM Manager app.
Nothing works, it just does a normal boot every time. I even did a factory reset to try and get into the stock recovery (a suggestion I found on another thread here), but that didn't work, either (and my device still appears to be rooted).
I'm hoping someone out there can provide more insight/advice, as I'm pretty well out of options.
Device info:
Android version: 3.0.1
Kernel: 2.6.36.3-00003-g8038d35, android 'at' Mercury #1
Build: HRI66.US_epad-8.2.3.9-20110423
(all stock)
ok, I managed to get into CWM and now my question is, "where can I get the latest version of CWM?" I've seen several posts that just say, "head over to the CWM thread and download the newest version", but they don't give links and I didn't find much searching the forums.
Sorry for being such a n00b...
Im also having a similar problem though my transformer wont do anything after i choose to boot into recovery.
kfarstrider said:
ok, I managed to get into CWM and now my question is, "where can I get the latest version of CWM?" I've seen several posts that just say, "head over to the CWM thread and download the newest version", but they don't give links and I didn't find much searching the forums.
Sorry for being such a n00b...
Click to expand...
Click to collapse
How did you get into recovery? No matter what I do it just boots normally. adb doesn't see the tablet anymore either..and I already rooted it so adb *was* working.
ferparedes said:
How did you get into recovery? No matter what I do it just boots normally. adb doesn't see the tablet anymore either..and I already rooted it so adb *was* working.
Click to expand...
Click to collapse
For real. I rooted succesfully. Currently trying to flash a rom, but I don't know how to get into CWM.
Same issue here. Can someone write how they got into CWM?
I used RazorClaw to root my Transformer, yet when I try to reboot into recovery, it gives me the Android with the Caution symbol in the middle. It looks like I cannot get into ClockWorkMod, either.
On www (dot) clockworkmod (dot) com, it does not list the Asus Transformer as being supported with a version of CWM. Rom Manager shows the same thing, so I am forced to select the Xoom or Nook Color.
What are the steps to get from Root to CWM Recovery?
Thanks!
Ok so I'm at the same part of the problem everyone else is in this thread.
I've done the following steps:
Installed Java SDK
Installed Andriod SDK
Rooted via Razorclaw
device is recognized when i do "adb devices" in command shell
install ROM Manager by Clockwork Mod from App store
tried to boot into recovery while connected to PC using Vol Down + Power Button and I get Android Man with Caution with nothing going further. if I unplug the cable from the PC I can't seem to get into Boot Recovery. I've asked for help in asus-transformer on Freenode.net with no help what so ever. From what I can tell my model is a B50
Any help would be appreciated from what I can peice together on the forums the install order would be
Root
CWM on App Market
CWM Recovery by roach
Nandriod
install ROM
Correct me if I'm wrong.
---------- Post added at 08:18 AM ---------- Previous post was at 07:49 AM ----------
Edit: Problem solved, I read somewhere that you needed to enable USB Debugging on the tablet which is correct. But you should not do it until the correct time I enabled it from the start which is wrong
jlscarpa said:
I used RazorClaw to root my Transformer, yet when I try to reboot into recovery, it gives me the Android with the Caution symbol in the middle. It looks like I cannot get into ClockWorkMod, either.
On www (dot) clockworkmod (dot) com, it does not list the Asus Transformer as being supported with a version of CWM. Rom Manager shows the same thing, so I am forced to select the Xoom or Nook Color.
What are the steps to get from Root to CWM Recovery?
Thanks!
Click to expand...
Click to collapse
Exactly what I get!
No Such Luck
[/COLOR]Edit: Problem solved, I read somewhere that you needed to enable USB Debugging on the tablet which is correct. But you should not do it until the correct time I enabled it from the start which is wrong[/QUOTE]
I don't get it. I've been having the same problem as you. So I turned off usb debugging and still had no success getting into recovery in spite of a successful root. Advice anyone?
TommyGunn
If anyone ever received a solution, I'd love to hear it, I'm having the same problem...
Have the same Problem need help.
Hi
My tablet was with some problems and I decided to change the rom. I tried to install the "[ROM] Android Revolution HD 3.5.1 | High Quality & Performance | ICS | TF101/101G" but in they said to do a full super wipe first. I made that but now I have my tablet sucked on CWM. I can't access the external sd to install the rom and I can't send the rom to sd via cable because of driver error when connecting the tablet to the computer via cable.
Anyone have a solution?
Thank you
I had the same problem, here's the solution.
* Download CWM6 touch external.
* Reboot to recovery
* Connect to your pc/laptop
* go to command prompt
* adb shell
* mount /dev/block/mmcblk1p1 /data
* exit
* adb push recovery.zip /data/media/recovery.zip
then go to recovery , install , choose recovery.zip restart and get back to recovery, you can access external SD card now
I found the solution at this link:
http://forum.xda-developers.com/showthread.php?p=24007127#post24007127
rafaair said:
Hi
My tablet was with some problems and I decided to change the rom. I tried to install the "[ROM] Android Revolution HD 3.5.1 | High Quality & Performance | ICS | TF101/101G" but in they said to do a full super wipe first. I made that but now I have my tablet sucked on CWM. I can't access the external sd to install the rom and I can't send the rom to sd via cable because of driver error when connecting the tablet to the computer via cable.
Anyone have a solution?
Thank you
Click to expand...
Click to collapse
mailvamsi said:
I had the same problem, here's the solution.
* Download CWM6 touch external.
* Reboot to recovery
* Connect to your pc/laptop
* go to command prompt
* adb shell
* mount /dev/block/mmcblk1p1 /data
* exit
* adb push recovery.zip /data/media/recovery.zip
then go to recovery , install , choose recovery.zip restart and get back to recovery, you can access external SD card now
I found the solution at this link:
http://forum.xda-developers.com/showthread.php?p=24007127#post24007127
Click to expand...
Click to collapse
Hi
When I connect to my computer the driver "ASUS Android MTP Device" failed to install. I tried to do this manually with no success. Any solution?
I just tried to install Android Revolution as well and im having this problem as well, after the super wipe my tablet wont load up just hangs at the eee pad screen and when i go into recovery it says no files found so i cant flash anything, when i connect it with usb to pc is says drivers not installed any help please
bayniner said:
I just tried to install Android Revolution as well and im having this problem as well, after the super wipe my tablet wont load up just hangs at the eee pad screen and when i go into recovery it says no files found so i cant flash anything, when i connect it with usb to pc is says drivers not installed any help please
Click to expand...
Click to collapse
Use this: (http://forum.xda-developers.com/showthread.php?t=1688012)
JoinTheRealms said:
Use this: (http://forum.xda-developers.com/showthread.php?t=1688012)
Click to expand...
Click to collapse
thanks for the link quick question how do i get the device into apx mode and how do i know its in apx mode thanks for any help
mailvamsi said:
I had the same problem, here's the solution.
* Download CWM6 touch external.
* Reboot to recovery
* Connect to your pc/laptop
* go to command prompt
* adb shell
* mount /dev/block/mmcblk1p1 /data
* exit
* adb push recovery.zip /data/media/recovery.zip
then go to recovery , install , choose recovery.zip restart and get back to recovery, you can access external SD card now
I found the solution at this link:
http://forum.xda-developers.com/showthread.php?p=24007127#post24007127
Click to expand...
Click to collapse
In adb it says: error: device not found.
I checked the driver and it is up to date, but it says a code 10 error. Do you now anything about that?
bayniner said:
thanks for the link quick question how do i get the device into apx mode and how do i know its in apx mode thanks for any help
Click to expand...
Click to collapse
Turn the tf101 off and hold power, volume up and down all at the same time and if its already plugged into the computer you should hear the windows 7 device detected sound, but the screen on the tf101 will stay black, it should recognise the tf101 as "nvidiaapx" or something along those lines.
Step-by-step please
I have spent the last 5 days, on and off, trying to find a clear set of instructions on how to fix the problem with always rebooting to recovery.
I have a TF101 running Android Revolution 3.51. The recovery version is 5.8.3.4 or so it says. I can cold boot to make the tablet usable so its not the end of the world.
I have tried flashing in a number of different ways with all the popular tools such GOO, flashing zips in recovery, recovery installer, ROM toolbox etc. etc. etc. Also with about 5 different ZIP for various recovery version. No joy! The new versions never stick.
I have ADB installed and the latest drivers etc. and have used it in the past for other things and I suspect this will have to be used to solve this problem.
I just can't find a simple step-by-step instruction on how to fix the problem. :crying:
I have searched on about 4 or 5 forums but the instructions are frequently for slightly different problems or are taken in a different direction. I must either be dense or nobody has exactly the same problem .....
Can someone provide a thread location or provide clear step-by-step instructions on exactly how to solve this problem ..... I am at the point of just giving up on this problem.
Grateful for the help - I'm dying here!
Toolmanz
toolmanz said:
I have spent the last 5 days, on and off, trying to find a clear set of instructions on how to fix the problem with always rebooting to recovery.
I have a TF101 running Android Revolution 3.51. The recovery version is 5.8.3.4 or so it says. I can cold boot to make the tablet usable so its not the end of the world.
I have tried flashing in a number of different ways with all the popular tools such GOO, flashing zips in recovery, recovery installer, ROM toolbox etc. etc. etc. Also with about 5 different ZIP for various recovery version. No joy! The new versions never stick.
I have ADB installed and the latest drivers etc. and have used it in the past for other things and I suspect this will have to be used to solve this problem.
I just can't find a simple step-by-step instruction on how to fix the problem. :crying:
I have searched on about 4 or 5 forums but the instructions are frequently for slightly different problems or are taken in a different direction. I must either be dense or nobody has exactly the same problem .....
Can someone provide a thread location or provide clear step-by-step instructions on exactly how to solve this problem ..... I am at the point of just giving up on this problem.
Grateful for the help - I'm dying here!
Toolmanz
Click to expand...
Click to collapse
PROBLEM SOLVED!!!!!
1. download the latest firmware on http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#download
2. download easyflasher on http://www.mediafire.com/easyflasher
3. Unrar easy flash
4. put the zip downloaded on 1 on ....\EasyFlasher-0.8.3b\asusupdate folder (dont unrar)
5. Pug the tablet on the computer
6. Click on power butom + volume+ + volume- all together until the tablet enter on apx mode (black screen and windows will install the driver)
7. Open easyFlaser on ...\EasyFlasher-0.8.3b folder
8. select sbk1 or sbk2 (depending on your serial)
9. click run asus stock zip.
10. it will install the rom and some things will be written on your tablet. When finished, just remove the cable and reset the tablet.
It's all that I have done!
THANK YOU FOR EVERYONE THAT HELPED ME!
toolmanz said:
No joy! The new versions never stick.
Can someone provide a thread location or provide clear step-by-step instructions on exactly how to solve this problem ..... I am at the point of just giving up on this problem.
Grateful for the help - I'm dying here!
Toolmanz
Click to expand...
Click to collapse
Try this
You need to get rid of that "bad" recovery. Go to the dev section, get one of the recovery there, your choice doesn't matter.
(TWRP is a one I'm using myself)
boot into recovery and flash the new recovery.
When done do NOT use reboot option in the recovery.
Use the Vol down plus power button and let it get to the 2 options of wipe data or cold boot linux.
Once it boot to your OS, use terminal (free in Play Store).
Open terminal and type in the following
Code:
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Reboot
*press ENTER after each line.
baseballfanz said:
Try this
You need to get rid of that "bad" recovery. Go to the dev section, get one of the recovery there, your choice doesn't matter.
(TWRP is a one I'm using myself)
boot into recovery and flash the new recovery.
When done do NOT use reboot option in the recovery.
Use the Vol down plus power button and let it get to the 2 options of wipe data or cold boot linux.
Once it boot to your OS, use terminal (free in Play Store).
Open terminal and type in the following
Code:
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Reboot
*press ENTER after each line.
Click to expand...
Click to collapse
It's alive - it's alive!!!!!! :highfive:
Thanks to the both of you for your responses. I decided to try the easy one first and it worked :laugh::good::good::good::highfive: you are day man!!
I am very grateful as I tend to obsess over this type of thing!
I'd buy you a beer if I could - imagine a virtual frosty one in your hand.
I think someone should sticky this solution - I'm probably not the only one frustrated by this.
Thanks again!
Toolmanz
JoinTheRealms said:
Turn the tf101 off and hold power, volume up and down all at the same time and if its already plugged into the computer you should hear the windows 7 device detected sound, but the screen on the tf101 will stay black, it should recognise the tf101 as "nvidiaapx" or something along those lines.
Click to expand...
Click to collapse
Thanks a million finally got it up and running, took me about 20 tries to get it into apx and computer to detect it but it worked i thought my tablet was dead man thanks
rafaair said:
PROBLEM SOLVED!!!!!
1. download the latest firmware on http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#download
2. download easyflasher on http://www.mediafire.com/easyflasher
3. Unrar easy flash
4. put the zip downloaded on 1 on ....\EasyFlasher-0.8.3b\asusupdate folder (dont unrar)
5. Pug the tablet on the computer
6. Click on power butom + volume+ + volume- all together until the tablet enter on apx mode (black screen and windows will install the driver)
7. Open easyFlaser on ...\EasyFlasher-0.8.3b folder
8. select sbk1 or sbk2 (depending on your serial)
9. click run asus stock zip.
10. it will install the rom and some things will be written on your tablet. When finished, just remove the cable and reset the tablet.
It's all that I have done!
THANK YOU FOR EVERYONE THAT HELPED ME!
Click to expand...
Click to collapse
Easy flasher doesn't work for the TF101G model, is there anything that does?
OMG!
WOW! Same thing happened to me today, I've been running JB on my TF101 for a month, and its laggy as hell and crap so I'm changing back to ARHD, but after I superwiped, everything got screwed up. TYVM!! I'm going to try and fix it right now, just downloaded the firmware from ASUS and EasyFlasher. On my ASUS TF101 I have a sticker on it still, it says S/A B70KA blah blah blah. so is my Serial number B70? is that sbk1 or sbk2
---------- Post added at 10:47 PM ---------- Previous post was at 10:22 PM ----------
droyd4life said:
WOW! Same thing happened to me today, I've been running JB on my TF101 for a month, and its laggy as hell and crap so I'm changing back to ARHD, but after I superwiped, everything got screwed up. TYVM!! I'm going to try and fix it right now, just downloaded the firmware from ASUS and EasyFlasher. On my ASUS TF101 I have a sticker on it still, it says S/A B70KA blah blah blah. so is my Serial number B70? is that sbk1 or sbk2
Click to expand...
Click to collapse
I can't get this crap to work APX mode IS NOT WORKING AHHHHH. :cyclops:
droyd4life said:
WOW! Same thing happened to me today, I've been running JB on my TF101 for a month, and its laggy as hell and crap so I'm changing back to ARHD, but after I superwiped, everything got screwed up. TYVM!! I'm going to try and fix it right now, just downloaded the firmware from ASUS and EasyFlasher. On my ASUS TF101 I have a sticker on it still, it says S/A B70KA blah blah blah. so is my Serial number B70? is that sbk1 or sbk2
---------- Post added at 10:47 PM ---------- Previous post was at 10:22 PM ----------
I can't get this crap to work APX mode IS NOT WORKING AHHHHH. :cyclops:
Click to expand...
Click to collapse
First off, calm down.... lol secondly your B70 so you can be SBK1 or SBK2 try them both.
JoinTheRealms said:
First off, calm down.... lol secondly your B70 so you can be SBK1 or SBK2 try them both.
Click to expand...
Click to collapse
It's still not working.. How do I make sure I am in APX mode?
---------- Post added at 11:14 PM ---------- Previous post was at 11:10 PM ----------
JoinTheRealms said:
First off, calm down.... lol secondly your B70 so you can be SBK1 or SBK2 try them both.
Click to expand...
Click to collapse
just tried both SBK1 and SBK2. My computer doesn't show it installs APX drivers though. SO when easyflasher asks if im in APX mode i just hit yes anyways. right now im at the Eee Pad/Asus/powered by Nvida Tegra boot up screen
---------- Post added at 11:48 PM ---------- Previous post was at 11:14 PM ----------
droyd4life said:
It's still not working.. How do I make sure I am in APX mode?
---------- Post added at 11:14 PM ---------- Previous post was at 11:10 PM ----------
just tried both SBK1 and SBK2. My computer doesn't show it installs APX drivers though. SO when easyflasher asks if im in APX mode i just hit yes anyways. right now im at the Eee Pad/Asus/powered by Nvida Tegra boot up screen
Click to expand...
Click to collapse
YESSSSSSSSSS I FIXED IT!!!!!!!!!!!!!!!!!! I installed manually the APX drivers. I downloaded universal anked driver and then went to device manager, selected the APX device and manually located the naked driver folder, then it just searched and matched the drivers up, now im flashing the stock rom YAY!!!!!!!!!! ANDROID RAPES!!!!! HELL YES!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!:good:
Right, I searched on numerous pages on these wonderful forums, but couldn't quite find what I was looking for. So I'll try my luck here. I'll describe my problem.
My TF101 was rooted using the CWM recovery. After doing more research I found out I shouldn't be doing this. But, unfortunately the damage has already been done. After several succesful ROM installations I wasn't quite happy with, I tried one last CM10 install. That's when it all went to ****. My TF101 has been stuck on the Eee Pad splash screen for nearly 2 months now.
Normally when going into the recovery mode I can simply select install from SD card and install a new rom. Now it can't seem to mount and displays E:Can't mount \SD card or whatever.
Further on, I tried using the ADB tools to manually restore system files. Without luck. After which I tried to install the naked USB drivers using http://forum.xda-developers.com/showthread.php?t=1426502. Without luck as well. I simply ran out of ideas.
The thing is, in Device manager I do see a device called Android. But, for some reason I can't seem to install any drivers for it. I guesse this would be the first step towards getting it back to work? Or perhaps I should just get it fixed at the computer store?
Any sugestions would be more than welcome!
Easy Flasher will get you back to stock as long as you can access APX. You will lose all data however.
1st mistake read forum before you do something, coz you would have learnt abt CWM issues, anyway thatsvan old story
You got Two options, find an flash able twrp.zip and flash it using current recovery if its still working otherwise as the other guy says easyflasher
To use easy flash you need
Easy flash software from forum
Universal naked driver installed
Asus firmware and PATIENCE
Follow the steps given in the forum and you should get back a tablet running stock rom, then if you want then use easy flash to root your device again but this time use TWRP recovery.....
Sent from my Transformer TF101 using xda app-developers app
Right, so far I've done everything I could find. I have installed the naked ADB files and thus was able to make a connection through USB. However, I wasn't able to push any files onto the tablet through ADB commands.
I entered the (what I assumed to be) APX mode and tried to use EasyFlasher. It seemed to have worked, because a DOS screen asked me whether or not I wanted to overwrite several files. After ending the procedure I rebooted my tablet. And guesse what: CWM is still there and the tab is still stuck on the Splash screen. Also the internal SD still can't be mounted.
What am I doing wrong. I'm slowly but surely going mad here....
hmmm, easyflasher should not prompt you to overwrite anything, it should just wipe it clean. The only prompt is when you select SBK1 or SBK2.
Can you post screenshots? It'd help us understand what exactly is going on...
Lethe6 said:
hmmm, easyflasher should not prompt you to overwrite anything, it should just wipe it clean. The only prompt is when you select SBK1 or SBK2.
Can you post screenshots? It'd help us understand what exactly is going on...
Click to expand...
Click to collapse
Right. Apparently I didn't put it in APX mode correctly. Windows asked me to install APX drivers. Which I now did. I then (I assume) was able to install the new recovery. The screen says !!!!phone update succes!!!!!. As we speak I am trying to install the stock ROM. Fingers crossed.....
AlbertGJBos said:
Right. Apparently I didn't put it in APX mode correctly. Windows asked me to install APX drivers. Which I now did. I then (I assume) was able to install the new recovery. The screen says !!!!phone update succes!!!!!. As we speak I am trying to install the stock ROM. Fingers crossed.....
Click to expand...
Click to collapse
I'll just sum up what I've been doing so far, because it still ain't working for me....
1) Put the TF101 in APX mode using POWER + VOLUME UP
2) Started up EasyFlasher 0.8.3 and selected "Flash Asus stock zip / Unbrick"
3) When prompted "file ..\temp\META-INF\MANIFEST.MF" already exists I selected "A(u)to rename all"
4) And then starts doing it's thing
5) Stuck at creating and formatting 15 partitions with several three letter codes.
I've ran the program three times now, but without luck. Any sugestions?~
[EDIT]Alright, managed to get it to work! Ended the tasks in through task manager about 4 times, but the 5th time was a charm. Exactly work as said. All thanks to EasyFlasher![/EDIT]
I bricked a TF300T today, and I'd like to know if there is possibility that it might be repaired.
I was attempting to install CyanogenMod 10.1 on the tablet for my friends, which I offered to do since I have a bit of experience doing similar on other devices. It was running Android 4.2, and had the latest firmware (v10.6.1.15.3, WW). After researching the XDA forums, I unlocked and rooted the device, and installed the TWRP recovery (2.5.0.0). I used TWRP to flash CM 10.1 and the Google apps, but when I tried to boot I got stuck at the Asus logo. After some more research I realized that the official release of CM doesn't work with the 4.2 bootloader, and that if I wanted to install that ROM I would need to downgrade my bootloader (right?).
The trouble occurred during the downgrade. I downloaded the 10.4.2.20 firmware and used flashboot to flash it. The flash completely successfully and I was going to run "flashboot reboot." Thinking I'd save keystrokes on the command line, I hit the up arrow to call up my last command, and meant to delete the last half of it, but I managed to hit 'enter' instead, starting the flash over again. I cancelled the command (^C), which might not have been wise -- but then I made my dumbest move, and powered the device off. (I'm not really sure why; I guess I assumed I'd still be able to get into fastboot mode.)
Now the device will not boot at all, except into APX mode -- i.e., the screen is blank, but when plugged into the computer the device registers. From what I've read here, there isn't really anything useful I can do in APX mode, given that I never setup nvflash, and I can't figure out any way of getting the tablet to do anything else.
Is there anything I've missed? Is there anything I could accomplish by cracking open the tablet (popping out the battery)? I've seen references to replacing the logic board – would that work, and how should I go about this? I know most if not all of these questions have been answered in different places before, and I tried to do my homework, but I figured I'd ask in case anyone had new experience or expertise to share.
I think to only solution is to replace the main board OR buy a new tablet :'(
Sent from my ASUS Transformer Pad TF300T
jay-roc said:
I bricked a TF300T today, and I'd like to know if there is possibility that it might be repaired.
I was attempting to install CyanogenMod 10.1 on the tablet for my friends, which I offered to do since I have a bit of experience doing similar on other devices. It was running Android 4.2, and had the latest firmware (v10.6.1.15.3, WW). After researching the XDA forums, I unlocked and rooted the device, and installed the TWRP recovery (2.5.0.0). I used TWRP to flash CM 10.1 and the Google apps, but when I tried to boot I got stuck at the Asus logo. After some more research I realized that the official release of CM doesn't work with the 4.2 bootloader, and that if I wanted to install that ROM I would need to downgrade my bootloader (right?).
The trouble occurred during the downgrade. I downloaded the 10.4.2.20 firmware and used flashboot to flash it. The flash completely successfully and I was going to run "flashboot reboot." Thinking I'd save keystrokes on the command line, I hit the up arrow to call up my last command, and meant to delete the last half of it, but I managed to hit 'enter' instead, starting the flash over again. I cancelled the command (^C), which might not have been wise -- but then I made my dumbest move, and powered the device off. (I'm not really sure why; I guess I assumed I'd still be able to get into fastboot mode.)
Now the device will not boot at all, except into APX mode -- i.e., the screen is blank, but when plugged into the computer the device registers. From what I've read here, there isn't really anything useful I can do in APX mode, given that I never setup nvflash, and I can't figure out any way of getting the tablet to do anything else.
Is there anything I've missed? Is there anything I could accomplish by cracking open the tablet (popping out the battery)? I've seen references to replacing the logic board – would that work, and how should I go about this? I know most if not all of these questions have been answered in different places before, and I tried to do my homework, but I figured I'd ask in case anyone had new experience or expertise to share.
Click to expand...
Click to collapse
APX mode is useless without nvflash installed and nvflash can only be installed while on ICS and once you leave ICS you can't go back.
Some Info: the vehicles to recover without nvflash are
1. recovery - stock or twrp
2. adb
3. fastboot
Do any of these work?
Try this link to find ways you may not have used yet -to get to the bootloader - thus recovery or fastboot
[GUIDE] Enter APX mode or Bootloader-recovery menu!
For future reference here is the way I see the recovery and rom matching issue.
4.1 bootloader - 10.4.2.9, 10.4.2.13, 10.4.2.17, 10.4.2.18, 10.4.2.20 - twrp openrecovery-twrp-2.5.0.0-tf300t-JB.blob
4.2 bootloader - 10.6.1.8 - twrp openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
4.2.1 bootloader - 10.6.1.15.3 - twrp openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
tobdaryl said:
APX mode is useless without nvflash installed and nvflash can only be installed while on ICS and once you leave ICS you can't go back.
Some Info: the vehicles to recover without nvflash are
1. recovery - stock or twrp
2. adb
3. fastboot
Do any of these work?
Try this link to find ways you may not have used yet -to get to the bootloader - thus recovery or fastboot
[GUIDE] Enter APX mode or Bootloader-recovery menu!
Click to expand...
Click to collapse
Thanks for the response. I've already tried the relevant methods in the guide, except for disconnecting the battery. I can get into APX mode -- the tablet registers as an APX device when plugged into the computer -- but I can't get it to enter the bootloader, so recovery, adb, and fastboot do not work. At this point I don't have much hope that the device will ever boot again without replacing the motherboard.
jay-roc said:
Thanks for the response. I've already tried the relevant methods in the guide, except for disconnecting the battery. I can get into APX mode -- the tablet registers as an APX device when plugged into the computer -- but I can't get it to enter the bootloader, so recovery, adb, and fastboot do not work. At this point I don't have much hope that the device will ever boot again without replacing the motherboard.
Click to expand...
Click to collapse
I'm sorry, I hoped the guide would give you a chance of recovery.
I definitely appreciate the help, and the guide's a great resource.
tobdaryl said:
I'm sorry, I hoped the guide would give you a chance of recovery.
Click to expand...
Click to collapse
jay-roc said:
I definitely appreciate the help, and the guide's a great resource.
Click to expand...
Click to collapse
You are welcome!
I had wished for better results.
Good Luck!
noahvt said:
I think to only solution is to replace the main board OR buy a new tablet :'(
Click to expand...
Click to collapse
Is there any tips for buying mainboard? Should it be exactly the same as in my tablet (I mean the same region and, therefore, version of ROM installed), maybe serials.
I have a bricked TF300T, and the only way I have to resurrect it - MB replacement. So, please, ANY info will be useful. Thanks in advance.
try to get it into fastboot somehow - i was stuck in apx too but with a bit of trying i was able to get to fastboot (try resetbutton + vol-down, let it completly drain of power, charge it back and try again)
here is what i did after i regained fastboot:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
gl
-Buster
Buster99 said:
try to get it into fastboot somehow - i was stuck in apx too but with a bit of trying i was able to get to fastboot (try resetbutton + vol-down, let it completly drain of power, charge it back and try again)
here is what i did after i regained fastboot:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
gl
-Buster
Click to expand...
Click to collapse
I'm so damn appreciated! Thank you so much)) I'd add this way to get to fastboot - adb reboot fastboot - just from faulty CWM. Other way it didn't worked.
I got mine working this way
Link to my thread --> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps. Try It!
ozkrtech said:
Link to my thread --> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps. Try It!
Click to expand...
Click to collapse
I have the same problem...
My TF300T got bricked and now i cant boot at all anymore, i just see the Asus logo.
Vol down and power doesnt work but i think i can boot it into APX mode, screen stays black but my pc recognises an APX device.
At first my pc didnt install the driver but than i found APX drivers in these forums.
I've downloaded the APX drivers from a thread and i can choose to install various drivers, i tried all of them.
The one i think i need is the Asus Transformer ADB interface driver but this one along with every other one i can choose from doesn't work.
After installing and trying fastboot devices and adb devices i never had a device name show up
im kinda stuck right now
Can anyone please give me some advice ?
Cheers, any help is appreciated
marty
martyzzz said:
I have the same problem...
My TF300T got bricked and now i cant boot at all anymore, i just see the Asus logo.
Vol down and power doesnt work but i think i can boot it into APX mode, screen stays black but my pc recognises an APX device.
At first my pc didnt install the driver but than i found APX drivers in these forums.
I've downloaded the APX drivers from a thread and i can choose to install various drivers, i tried all of them.
The one i think i need is the Asus Transformer ADB interface driver but this one along with every other one i can choose from doesn't work.
After installing and trying fastboot devices and adb devices i never had a device name show up
im kinda stuck right now
Can anyone please give me some advice ?
Cheers, any help is appreciated
marty
Click to expand...
Click to collapse
Can you explain me step by step what you did to get bricked? Are you on bootloader 4.1 or 4.2+? 10.4.x.x is 4.1 and 10.6.x.x is 4.2+
ozkrtech said:
Can you explain me step by step what you did to get bricked? Are you on bootloader 4.1 or 4.2+? 10.4.x.x is 4.1 and 10.6.x.x is 4.2+
Click to expand...
Click to collapse
Bought the Asus tab a year back and kept it original and updated by Asus for a few months.
Begin this year i unlocked it through a guide here on XDA (i dont thin through the Asus APK but another way).
After it succesfully unlucked (you could see "your device is unlocked" in the left top of the Asus boot screen i installed CWM.
After CWM i installed Cyogenmod 10.1 and kept it updated for months
This was all in the beginning of this year...
In june after updating Cyogenmod 10.1 to a newer version it wouldnt boot up anymore (i still had acces to my CWM recovery at this time).
So i switched back to the last working Cyogenmod 10.1 version (think it was 15th or 16th june).
I left it again for 2 months, still everything was fine till i saw that Cyogenmod 10.2 was out on XDA.
The upcomming is all last week;
First i tried to install 10.2 through CWM but my tab wouldnt boot up.
Than i switched recovery through fastboot because i have read that 10.2 was only compatible with TWRP 2.5+ so i got the latest TWRP
(2.6.0.0 i think)
After booting into TWRP i fully wiped the tab (i might have wiped everything because i dont know TWRP so well), after the wipe i wanted to install 10.2 again.
My tab still didnt boot so i got anctious and wanted to switch back to my latest version 10.1 (june 2013 that did work) so i could at least use my tab again.
Installing 10.1 again didnt work through TWRP, after that i came to the conclusion that i couldt install any rom anymore, at every rom i got an error in TWRP so i thought i had the wrong TWRP installed. (see my other post for a link to the screenshot of the error msge, i just cant find it atm).
Last but not least i tried to load my old CWM again as recovery, after i did this i couldnt get into recovery anymore...
Thans basicly the whole story.
Hope some1 can help me out.
Thanks in advance !
Cheers
martyzzz said:
Bought the Asus tab a year back and kept it original and updated by Asus for a few months.
Begin this year i unlocked it through a guide here on XDA (i dont thin through the Asus APK but another way).
After it succesfully unlucked (you could see "your device is unlocked" in the left top of the Asus boot screen i installed CWM.
After CWM i installed Cyogenmod 10.1 and kept it updated for months
This was all in the beginning of this year...
In june after updating Cyogenmod 10.1 to a newer version it wouldnt boot up anymore (i still had acces to my CWM recovery at this time).
So i switched back to the last working Cyogenmod 10.1 version (think it was 15th or 16th june).
I left it again for 2 months, still everything was fine till i saw that Cyogenmod 10.2 was out on XDA.
The upcomming is all last week;
First i tried to install 10.2 through CWM but my tab wouldnt boot up.
Than i switched recovery through fastboot because i have read that 10.2 was only compatible with TWRP 2.5+ so i got the latest TWRP
(2.6.0.0 i think)
After booting into TWRP i fully wiped the tab (i might have wiped everything because i dont know TWRP so well), after the wipe i wanted to install 10.2 again.
My tab still didnt boot so i got anctious and wanted to switch back to my latest version 10.1 (june 2013 that did work) so i could at least use my tab again.
Installing 10.1 again didnt work through TWRP, after that i came to the conclusion that i couldt install any rom anymore, at every rom i got an error in TWRP so i thought i had the wrong TWRP installed. (see my other post for a link to the screenshot of the error msge, i just cant find it atm).
Last but not least i tried to load my old CWM again as recovery, after i did this i couldnt get into recovery anymore...
Thans basicly the whole story.
Hope some1 can help me out.
Thanks in advance !
Cheers
Click to expand...
Click to collapse
What happends when you press volume down+ power?
It jeeps rebooting or it goes to black screen? Have you tried pressing the reset button is below the micro sdcard slot.
You should be able to boot any recovery.
is I recall correctly cm switched partition layout to 4.2 on tf300.
if you still have fastboot try my guide to flash stock and then flash recovery and cm10.2. since it sounds a lot like my error I had with cm it should work for you as well.
good luck
Sent from my TF300T using xda app-developers app
ozkrtech said:
What happends when you press volume down+ power?
It jeeps rebooting or it goes to black screen? Have you tried pressing the reset button is below the micro sdcard slot.
You should be able to boot any recovery.
Click to expand...
Click to collapse
When i press vol down+power i get the asus boot screen for a minute or 2, the tab switches off and on again to the same boot screen.
I cant boot into recovery
---------- Post added at 06:51 PM ---------- Previous post was at 06:42 PM ----------
Buster99 said:
is I recall correctly cm switched partition layout to 4.2 on tf300.
if you still have fastboot try my guide to flash stock and then flash recovery and cm10.2. since it sounds a lot like my error I had with cm it should work for you as well.
good luck
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
I dont have fastboot in any way.
I can only power on the device with volume up + power to enter APX mode, than only my pc sees a USB device.
I tried a lot of differtent drivers but for nome of them i can ADB of Fastboot to the device.
It would help if someone that has managed to unbrick through APX mode posted the right driver for a TF300T
Cheers
have you tried the apx drivers that come with the sdk?
Sent from my GT-I9505 using xda app-developers app
Buster99 said:
have you tried the apx drivers that come with the sdk?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Ive tried searching in the SDK forders but i cant find any.
If i try to install drivers automaticly and than point to the root SDK folder i get the windows msge the best drivers are already installed (no matter what driver is in stalled at that time)
martyzzz said:
Ive tried searching in the SDK forders but i cant find any.
If i try to install drivers automaticly and than point to the root SDK folder i get the windows msge the best drivers are already installed (no matter what driver is in stalled at that time)
Click to expand...
Click to collapse
don't just point at the folder
manually select the driver for the device from android-sdk\extras\google\usb_driver
gl
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