Hi,
After a serious software problems (crashed with 4.0.3 OTA update) i managed install a ROM, but my screentouch doesnt respond to my touch. The screen and all buttons function very well but i cant put the pin because touchscreen doenst work.
Could it be Software or is definitely Hardware?
Could be software. Have you tried flashing a new ROM (and appropriately wiping beforehand)?
Have you tried to access to the recovery ? Some recoveries use the touchscreen as the TWRP for example
Harbb said:
Could be software. Have you tried flashing a new ROM (and appropriately wiping beforehand)?
Click to expand...
Click to collapse
I try do clean install a custom rom and 2.3.6 OTA and in both the touch doesnt work.
I install the touch recovery, but after dont work i install a regular one via fastboot.
Clean install (format system, wipe everything, etc) and nothing work.
Will continue try another custom roms
Cyrille28410 said:
Have you tried to access to the recovery ? Some recoveries use the touchscreen as the TWRP for example
Click to expand...
Click to collapse
I can acess to recovery sometimes
When it fails push it in PC via fastboot.
Now i cant enter in recovery and cant connect via usb to flash another recovery
I'm screwed!
I cant get into recovery, when i pressed appears a android toy whith a warning sine.
I cant connect to PC, when in bootloader and connect to PC, in bottom appears "fastboot fails invalid command".
I´ve installed a stock rom 2.3.6 and the touch screen doesn´t work to iniciate the phone. Try to install franco kernell but it´s the same situation.
When i can connect the phone to PC i´ve try´de 3 different custom roms and none works.
Going to warranty.
Looks like your touchscreen may have just given up. Everything else is normal, you probably don't have fastboot/adb setup properly and that warning sign is the stock recovery. I'd sort out fastboot and lock the bootloader before sending it in. Also, if you don't have a backup of your sdcard you can mount it through a custom recovery (use "fastboot boot recovery.img").
Harbb said:
Looks like your touchscreen may have just given up. Everything else is normal, you probably don't have fastboot/adb setup properly and that warning sign is the stock recovery. I'd sort out fastboot and lock the bootloader before sending it in. Also, if you don't have a backup of your sdcard you can mount it through a custom recovery (use "fastboot boot recovery.img").
Click to expand...
Click to collapse
I´ve format SD card and have nothing inside.
"I'd sort out fastboot and lock the bootloader before sending it in"
How can i do that?
Remember that i cant access to recovery or turn on by computer.
Read the rooting guide or check out NexusSHacks.com, all the info you'll need.
How are you "pushing" recoverys via fastboot if you don't have fast boot set up properly?
Anyways. Speaking of fastboot. Get the official fastboot images for your phone and flash them all. If you still have issues with the screen its a hardware problem.
You should make a full backup and then flash the official factory images (ICS 4.0.4), made for your hardware version, through fastboot. You can find the exact version beneath your battery on a sticker.
If the problem persists after this, it's most likely a HW problem.
If the mobile is not recognized in bootloader / fastboot mode, then connect it to a Linux PC, and then post here the output of the following commands (as root):
Code:
tail /var/log/messages
Code:
lsusb
albundy2010 said:
How are you "pushing" recoverys via fastboot if you don't have fast boot set up properly?
Anyways. Speaking of fastboot. Get the official fastboot images for your phone and flash them all. If you still have issues with the screen its a hardware problem.
Click to expand...
Click to collapse
When i was able to connect the phone to pc i push it with code flashboot flash recovery Some.img
Now i cant "push it".
I cant enter in fastboot
I´ve been able to enter in recovery.
Unroot and back to stock.
Now already of screentoch doent work, some buttons dont work.
Going to warranty. Thanks everyone for the effort.
My phone stopped reading SD cards and they're going to send me a replacement so I want to at LEAST flash the stock recovery but is this even possible without an SD card? or am I stuck?
i just found out you can flash recovery without an sdcard, using fastboot. you can grab a stock recovery image here: http://forum.xda-developers.com/showpost.php?p=17384145&postcount=7, then fastboot flash it. you might even manage to flash a stock system this way too!
Thank you very much!
wait I just realized, doesn't my phone need to be connected to my computer as a "drive"? My phone won't let me do that unless I have an SD card
No, not for fastboot. The USB access is purely for sending fastboot commands; your phone won't show up as an accessible drive on your PC while in fastboot USB mode.
I rooted my NS4G running stock ics but I get an error when try to flash cwm recovery using ROM Manager. Any advise, I need help please.thanks
Galaxy Note
I'm assuming you unlocked via fastboot? You might be better off flashing the recovery image through there instead. You'll have better luck that way:
Snag the recovery image from here
Make sure the file is in the same location as adb. Turn your phone off and then power it on to the bootloader screen (pwr + vol up). Once there, open your command prompt, attach the phone via USB, and type fastboot devices to make sure your phone is recognized. Once you're okay there, proceed to type
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo4g.img, this is assuming you haven't changed the name of the image. You can copy it and paste it as well.
Once you get the recovery image flashed, you'll need to ensure that the stock recovery doesn't replace CWM. Steps can be found in
This post
HTH
Attempting to root, to backup then to install cm 10.1 or other rom
I've installed cwm from this thread http://forum.xda-developers.com/showthread.php?t=1668173
I can boot into recovery ok, however I get the following errors:
can't mount /cache/recovery/command
can't mount /cache/recovery/log
can't mount /cache/recovery/last_log
can't mount /cache/recovery/.
when trying to access internal or external sd card get:
can't mount /sdcare/
can't mount /emmc
Any help appreciated
Update: tried twrp 2.4.3.0 does the same thing
The new update has encryption by default. That's why you can't mount anything. I am not sure if team win will release an update for their recovery or if Asus needs to do it. Seems like this update really screwed over some people.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
elesbb said:
The new update has encryption by default. That's why you can't mount anything. I am not sure if team win will release an update for their recovery or if Asus needs to do it. Seems like this update really screwed over some people.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
wow not good news. Guess I'l just have to monitor sites and see what happens over time.
Disappointing for sure as this last update screwed up the hdmi out, I have functional tablet it might as well be a bricked pos, arg !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
It's worthless to me in it's present state
Hmm where is the phone num so i can call gripe at asus
tonyjsan said:
wow not good news. Guess I'l just have to monitor sites and see what happens over time.
Disappointing for sure as this last update screwed up the hdmi out, I have functional tablet it might as well be a bricked pos, arg !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
It's worthless to me in it's present state
Hmm where is the phone num so i can call gripe at asus
Click to expand...
Click to collapse
Think you can only email them :/
I dont think its asus who encrypted it. I think it was google. I am not sure though so dont quote me xD
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
elesbb said:
Think you can only email them :/
I dont think its asus who encrypted it. I think it was google. I am not sure though so dont quote me xD
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
twrp I think might support that sort of thing already, i went back into twrp2 and it does ask for a password at first, a check of the logs by twrp said can't decrypt
Who ever set the encryption, needs to show how to unset it.
I'm having the same issue that tonyjsan described.
This was I did:
1 - I updated to 4.2.1 via OTA.
2 - Download Asus unlock apk & unlocked the boot loader.
3 - Then installed the CWM 6.0.2.3 via fast boot.
4 - Tried to installed CM10.1 nightly couldn't acess SD started to get the following:
can't mount /cache/recovery/command
can't mount /cache/recovery/log
can't mount /cache/recovery/last_log
can't mount /cache/recovery/.
when trying to access internal or external sd card get:
can't mount /sdcare/
can't mount /emmc/
Now it's the point where I got stupid, and decided to go into the bootloader and do a full wipe, which I THINK wiped everything and installed the recovery Kernel (which now is CWM) into the main image.
Now my TF300T only boot to CWM and I can acess it via ADB do thing like push files, but i've lost the boot loader and cannot go into fastboot.
Really need the expertise of a guru right now
Help is appreciated
Getting Same Issues
Both the latest TWRP2 and latest CWM are a bust for me too.
If the recovery kernel image can't get at the disk partitions - then no custom ROMS
can be installed.
I guess being the first non-nexus with 4.2.1 isn't such great news after all.
xbill9 said:
If the recovery kernel image can't get at the disk partitions - then no custom ROMS
can be installed.
Click to expand...
Click to collapse
Starting to get the felling I have a 300$ dollar brick on my desk
Same Here
I've run into the same thing. I did the OTA update to 4.2.1, and then I decided to root, so I followed these instructions: http://forum.xda-developers.com/showthread.php?t=2041627.
Unlocked worked.
Recovery Flash worked.
Mounting any part of the sdcard (internal or external) does not work in recovery.
I can still boot into the OS, so I'm not bricked, but I can't install root because I can't see the internal storage to flash it.
Is it possible to flash back to 4.1.1?
Yes, but your recovery must be working.
vconceicao said:
I'm having the same issue that tonyjsan described.
This was I did:
1 - I updated to 4.2.1 via OTA.
2 - Download Asus unlock apk & unlocked the boot loader.
3 - Then installed the CWM 6.0.2.3 via fast boot.
4 - Tried to installed CM10.1 nightly couldn't acess SD started to get the following:
can't mount /cache/recovery/command
can't mount /cache/recovery/log
can't mount /cache/recovery/last_log
can't mount /cache/recovery/.
when trying to access internal or external sd card get:
can't mount /sdcare/
can't mount /emmc/
Now it's the point where I got stupid, and decided to go into the bootloader and do a full wipe, which I THINK wiped everything and installed the recovery Kernel (which now is CWM) into the main image.
Now my TF300T only boot to CWM and I can acess it via ADB do thing like push files, but i've lost the boot loader and cannot go into fastboot.
Really need the expertise of a guru right now
Help is appreciated
Click to expand...
Click to collapse
vconceicao said:
Starting to get the felling I have a 300$ dollar brick on my desk
Click to expand...
Click to collapse
as sad as it seems :'( you are more than likely bricked. Every thread I read, even on 4.1 stock, once you do the "wipe all" option in bootloader menu, without a stock recovery. You become bricked.
wirikidor said:
I've run into the same thing. I did the OTA update to 4.2.1, and then I decided to root, so I followed these instructions: http://forum.xda-developers.com/showthread.php?t=2041627.
Unlocked worked.
Recovery Flash worked.
Mounting any part of the sdcard (internal or external) does not work in recovery.
I can still boot into the OS, so I'm not bricked, but I can't install root because I can't see the internal storage to flash it.
Is it possible to flash back to 4.1.1?
Click to expand...
Click to collapse
You should be able to fastboot the stock Asus 4.1.1 .blob file.
Sent from my SGH-T999
"So I put my phone into airplane mode and threw it... worst transformer ever. -.-" -My friend
vconceicao said:
Now it's the point where I got stupid, and decided to go into the bootloader and do a full wipe, which I THINK wiped everything and installed the recovery Kernel (which now is CWM) into the main image.
Now my TF300T only boot to CWM and I can acess it via ADB do thing like push files, but i've lost the boot loader and cannot go into fastboot.
Really need the expertise of a guru right now
Help is appreciated
Click to expand...
Click to collapse
When you said wipe, you used the wipe data option, when sitting at the first menu (boot loader menu) after pressing power and vol down ?
One other thing I'd share here to is that the factory wipe, from within settings, for me does not work, it boots to twrp / recovery, when I exit all data still there. So was wondering which one you used ?
Is the encryption on the partitions from sbk nvflash crap (i'm thinking not ??) or just an encrypted ext4 partition ??
elesbb said:
You should be able to fastboot the stock Asus 4.1.1
Click to expand...
Click to collapse
If I drop back to 4.1.1 will I have the same problem with not being able to access cache, data etc. in twrp or cwm, will it be encrypted ?
I'm also wondering dropping back to 4.1.1 will the 4.2.1 multi-user stuff mess with the downgrade, appears to be using sym links to create separate directory for each user.
tonyjsan said:
If I drop back to 4.1.1 will I have the same problem with not being able to access cache, data etc. in twrp or cwm, will it be encrypted ?
I'm also wondering dropping back to 4.1.1 will the 4.2.1 multi-user stuff mess with the downgrade, appears to be using sym links to create separate directory for each user.
Click to expand...
Click to collapse
Hello I have 4.1.1 It is unlocked. I have flashed the CWM and when I boot into recovery I only see the sd card and will not let me rrot via the zip either. I get an error in CWM saying that root persmissions need to be fixed. I have tried to fix then not to fix. Still nothing.
Not sure if this is inline with what everyone else is seeing.
ASUS did push from .17 to .20 the other day.
This is a fishing trip. 4.2 is multi-user, for multi-user to work the tablet has to be encrypted or users could access each others space. I don't have 4.2 so I can't test. If multi-user is deactivated encryption is not necessary. If multi-user is turned off can you find a setting to unencrypt?
It seems I remember someone unencrypting with twrp or fastboot but it took three tries, multi-user would still need to be off. This is not a suggestion just my thoughts.
My version of fastboot does not list unencrypt as an option.
Holy cow I now have cm 10.1, root, and hdmi out problem fixed. After lots digging to be sure I did not screw the tablet up here is what I did.
1) Downgrade to US_10.4.2.20, using fastboot and blob from asus web site.
2) after rebooting I had the previous boot-loader screen (in which usb icon shows), I re-installed recovery twrp2.
3) I did not even bother to boot into 10.4.2.20, went straight to recovery and I had access to cache, data, sdcard etc...
4) adb pushed the cm 10.1 zip to the sdcard and the gapps zip as well.
5) flash cm 10.1 then gapps
6) reboot and all is well.
There is one word of caution, not sure what happen but do not use the usb port on the keyboard dock with cm 10.1, it zapped a usb jump drive and a 500 gb portable drive , still looking into if I can recovery the drive and what caused it.
I's so glad I'm on CM 10.1 tablet running faster just seems to perform better.
I have also had this issue and managed to come back from it.
In doing some testing of the new ota update 4.2.1 (10.6.1.8) I have found that this issue is a direct result of the new 4.2.1 bootloader, it will not work with any custom recovery. twrp will give password prompt and be unable to mount anything but possible system, same goes for cwm minus the password prompt.
After doing a full wipe from twrp and then flashing just the new 4.2.1 bootloader, I rebooted back into twrp and it's encrypted, can't mount anything.
This method will not work if you cannot flash from fastboot successfully. In fact if you have attempted any other way to fix it may not work.
After I rebooted twrp to find it was encrypted the first thing I did was to reboot into fastboot mode and did the following:
flashed the 4.2.1 stock recovery, I have uploaded to here
Copy the "stock.blob" file to your android-sdk\platform-tools folder.
Also download the "US_epaduser_10_4_2_20_UpdateLauncher.zip" from the Asus website and unzip,
In the unzipped folder you will then have another zip file "US_epad-user-10.4.2.20.zip" unzip this also and now in that unzipped folder you will have a "blob" file, copy this to your android-sdk\platform-tools folder.
Boot into fastboot and check your pc can see your device:
open a command prompt and cd to your platform-tools directory.
Code:
fastboot devices
This should return your device serial, if not then fastboot is not setup correctly.
Next:
Code:
fastboot -i 0x0b05 flash recovery stock.blob
fastboot -i 0x0b05 reboot
Boot back into fastboot:
Code:
fastboot -i 0x0b05 flash system blob
fastboot -i 0x0b05 reboot
The system blob will take some time 10min or so to flash, so just give it some time then issue the reboot command.
Also first reboot after system blob flash will take some time, you will see a progress bar under the Asus logo.
Once your tablet has fully loaded you can now boot back into fastboot and flash a custom recovery & flash custom rom again.
I do suggest skipping the 4.2.1 update for now until this issue has been fixed.
As I have said this may not work for everyone depending on if you have attempted any other commands via fastboot or adb.
This has worked for me twice now but try at own risk.
pjc21 said:
I have also had this issue and managed to come back from it.
In doing some testing of the new ota update 4.2.1 (10.6.1.8) I have found that this issue is a direct result of the new 4.2.1 bootloader, it will not work with any custom recovery. twrp will give password prompt and be unable to mount anything but possible system, same goes for cwm minus the password prompt.
After doing a full wipe from twrp and then flashing just the new 4.2.1 bootloader, I rebooted back into twrp and it's encrypted, can't mount anything.
This method will not work if you cannot flash from fastboot successfully. In fact if you have attempted any other way to fix it may not work.
After I rebooted twrp to find it was encrypted the first thing I did was to reboot into fastboot mode and did the following:
flashed the 4.2.1 stock recovery, I have uploaded to here
Copy the "stock.blob" file to your android-sdk\platform-tools folder.
Also download the "US_epaduser_10_4_2_20_UpdateLauncher.zip" from the Asus website and unzip,
In the unzipped folder you will then have another zip file "US_epad-user-10.4.2.20.zip" unzip this also and now in that unzipped folder you will have a "blob" file, copy this to your android-sdk\platform-tools folder.
Boot into fastboot and check your pc can see your device:
open a command prompt and cd to your platform-tools directory.
Code:
fastboot devices
This should return your device serial, if not then fastboot is not setup correctly.
Next:
Code:
fastboot -i 0x0b05 flash recovery stock.blob
fastboot -i 0x0b05 reboot
Boot back into fastboot:
Code:
fastboot -i 0x0b05 flash system blob
fastboot -i 0x0b05 reboot
The system blob will take some time 10min or so to flash, so just give it some time then issue the reboot command.
Also first reboot after system blob flash will take some time, you will see a progress bar under the Asus logo.
Once your tablet has fully loaded you can now boot back into fastboot and flash a custom recovery & flash custom rom again.
I do suggest skipping the 4.2.1 update for now until this issue has been fixed.
As I have said this may not work for everyone depending on if you have attempted any other commands via fastboot or adb.
This has worked for me twice now but try at own risk.
Click to expand...
Click to collapse
Question: You said you reflashed the stock bootloader. I had gotten my tf300 couple days ago but went through the ota update not thinking of issues if wanted to root so I'm not rooted totally stock on 4.2.1but if possible would like to flash back to stock locked bootloader if possible. After reading all the issues with trying to flash custom recovery and root after ota figured I'd just wait till some of the issues are figured out. I'm new to this device but have rooted many other android phones in the passed so not a total noob just learning about this one been reading alot. Just wondering if there were a way to do so for future updates as i read you lose ota capability if unlocked. Thanks
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
aerdely said:
Question: You said you reflashed the stock bootloader. I had gotten my tf300 couple days ago but went through the ota update not thinking of issues if wanted to root so I'm not rooted totally stock on 4.2.1but if possible would like to flash back to stock locked bootloader if possible. After reading all the issues with trying to flash custom recovery and root after ota figured I'd just wait till some of the issues are figured out. I'm new to this device but have rooted many other android phones in the passed so not a total noob just learning about this one been reading alot. Just wondering if there were a way to do so for future updates as i read you lose ota capability if unlocked. Thanks
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
This approach recovered the tablet.
As long as the bootloader is working - it is probably fixable.
Here is how I got it to work:
-preloaded my ROM and Gapps on the SD card
-flashed stock system blob (for the right region) from the ASUS website
-let the stock ROM reboot
-it hangs - but will be visible from ADB
-reboot to fastboot
-install TWRP or CWM from fastboot
-reboot recovery
-then flash ROM + Gapps
There has to be something in the new OTA bootloader or OTA system that
locks down the partitions.
xbill9 said:
This approach recovered the tablet.
As long as the bootloader is working - it is probably fixable.
Here is how I got it to work:
-preloaded my ROM and Gapps on the SD card
-flashed stock system blob (for the right region) from the ASUS website
-let the stock ROM reboot
-it hangs - but will be visible from ADB
-reboot to fastboot
-install TWRP or CWM from fastboot
-reboot recovery
-then flash ROM + Gapps
There has to be something in the new OTA bootloader or OTA system that
locks down the partitions.
Click to expand...
Click to collapse
Yea should of mentioned im not rooted haven't done that yet as if you are on the 4.2.1 ota you can't without issues. Device works fine I'm on stock recovery and firmware but just an unlocked bootloader and just little worried because some have mention can lose any future ota's if thats not the case than i guess no issue at all but not sure on that and was just looking for a way to either relock the bootloader or reflash it. Probably isn't at the moment but some have been asking about this because of issues with the ota.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I've unlocked bootloader and i'm trying to install CWM (or any other recovery). I access fastboot, flash the .img file and the debug screen says everything ok. I wait the flash method, normaly reboots, access adb and type : adb reboot recovery, but i ended up on android stock recovery, with the green android.
What can I do ?
sky0165 said:
I've unlocked bootloader and i'm trying to install CWM (or any other recovery). I access fastboot, flash the .img file and the debug screen says everything ok. I wait the flash method, normaly reboots, access adb and type : adb reboot recovery, but i ended up on android stock recovery, with the green android.
What can I do ?
Click to expand...
Click to collapse
I had the same issue, after 3 days of frustration I finally managed to get it working.
First download the MR. PARKINSON'S DROIDHD UTILITY 2.0 found here http://forum.xda-developers.com/showthread.php?t=2241788
The light version should be fine.
After downloading unzip and create a folder inside the "DROIDHD UTILITY 2.0" folder named "twrp"
Inside that folder put the recovery image you want to use. (It doesn't have to be TWR, it could be CWR or OUDHS.)
Now open the DROIDHD UTILITY 2.0 and select option 2 (Roots, unlocks...)
Then select option 5, Say Yes and continue.
After doing all that you should be good to go. Go to recovery mode and check.
If your phone is operational, you could also download flashify from the android market and flash a new recovery from the phone without using ADB.
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en