Database Info

[Q] stuck in boot loop

I've got my tf300t stuck in a boot loop when i turned it on today. (Ive looked around the forums for this issue already and been able to find little or no solutions that work for me)
I'm using cm10 and twrp. last night i shut the tablet off as usual and go to turn it on today and i cant get past the white asus logo and device unlocked screen.
I can access my twrp recovery menu, wiping dalvik returns a "E:Unable to mount '/data' (tw_mount)" cache wipes fine no errors.
I'm unable to flash another rom or restore from a back up as well.
Fastboot says its working but in cmd prompt it wont list the device. (computer recognizes it and it shows in device manager as android adb interface)
If there is any other information needed I will be more than happy to provide it.
any tips or help is greatly appreciated.
thanks in advanced.

I'm not yet very fammiliar yet with TF300, but from SGS 1 and ICS I remember one trick. If you have external microSD pluged, take it out or of you don't have it plug it in and then enter TWRP.
It probably won't work but you can try anyway.
Does TWRP have any file browser? I'm using CWM so I don't know much about TWRP.

stenc55 said:
I'm not yet very fammiliar yet with TF300, but from SGS 1 and ICS I remember one trick. If you have external microSD pluged, take it out or of you don't have it plug it in and then enter TWRP.
It probably won't work but you can try anyway.
Does TWRP have any file browser? I'm using CWM so I don't know much about TWRP.
Click to expand...
Click to collapse
Yeah it does have the file browser, upon initial booting i can browse an sd card ( i have a few of various sizes none seem to to be having any affect) and i can browse the internal storage as well. Booting both with and without the sd card in the device still leaves me in the boot loop.

So, can you copy new rom to sd card, then copy from sd to internal and install new rom? I think only option you have is to reinstall rom.

stenc55 said:
So, can you copy new rom to sd card, then copy from sd to internal and install new rom? I think only option you have is to reinstall rom.
Click to expand...
Click to collapse
I can and have tried but it wont let me flash with the "unable to mount /data" error. It tells that my external sd-card and whatever rom i attempt to flash has problems

Hagenator said:
I can and have tried but it wont let me flash with the "unable to mount /data" error. It tells that my external sd-card and whatever rom i attempt to flash has problems
Click to expand...
Click to collapse
Be sure your sdk is up to date.
1. If you hold volume down plus power button to get to fastboot.
2. shift + control right click fastboot folder on computer then open command prompt.
3. type devices... and if it is not showing a device there something is not right.
4. you can try adb push to apply a flash if your device is not wanting to flash from sd card.

M
Repairtech123 said:
Be sure your sdk is up to date.
1. If you hold volume down plus power button to get to fastboot.
2. shift + control right click fastboot folder on computer then open command prompt.
3. type devices... and if it is not showing a device there something is not right.
4. you can try adb push to apply a flash if your device is not wanting to flash from sd card.
Click to expand...
Click to collapse
I've tried this as well. It was my first thought. Also it states in my original post that fastboot doesnt list my device, adb doesnt list it as well. Both are recent and up to date. However device manager does recognize it and windows makes the little notification sound. In safely remove devices it shows up as fastboot when i enable fastboot on the device.

[Q] TF300T, TWRP and ROM issues

Hola banditos, I am new here, and not really that big into android, so forgive me if I do not refer to something correctly. I am currently having multiple problems with my Asus Transformer pad. A few months ago I purchased said product and rooted it. I had a few minor issues but eventually got it working. Flash forward to yesterday night at around 10 PM, and I had wiped the system and removed the Operating system. "No problem" I thought "I can just download the Jellybean firmware from the asus website" ( I had done this before.)
I downloaded the firmware, put it on my SD card and flashed it. The only problem was that I had flashed the Japanese version of the firmware onto it.
At this point, TWRP apparently thought it would be hilarious to stop working. Upon downloading the US version of the software and loading it onto my SD card, TWRP was no longer able to mount the SD card. That my friends is the major problem.
I have checked on my computer, and the SD card is still functioning. I have went into the Japanese OS on the Android and it is still accessible and functioning. I have downloaded multiple versions of TWRP, different recovery kernels and tried multiple solutions through other threads. I have tried reformatting my SD card to EXFAT, Fat32, NTFS and regular FAT. I have tried putting the firmware on the internal SD card and loading it from there. It recognizes that the firmware is there, but fails to install it. ADB also fails to recognize the device (I have everything set up correctly on the PC but it still fails). Fastboot is working fine though.
I have crawled through web page to web page looking for a fix. About 7 hours in total, and I am yet to find one that works.
Help me out here.
My gear:
64 GB sandisk SD card
Asus tf300t running a japanese Jellybean 4.2.1
TWRP 2.6
You're my last hope

There is another way! Inside the us software zip there is another zip inside that zip is a .blob file extract it to the directory where adb and fastboot are on your pc open up command prompt and cd to your fastboot directory: now type: fastboot flash system blob
This will take some time!
Then flash twrp and open it then wipe data system cache dalvik cache and then flash the firmware via twrp reboot!
Sent from my sensational HTC Desire C

I have grabbed the blob file from the US firmware. Upon using the "fastboot flash system blob" command, I get the message < waiting for device > I have waited a half hour, and it is still there. am I doing something wrong?
Edit-
I have since got the fastboot to work after some research. When I went to wipe the data system cache and dalvik cache, TWRP said that it had failed. TWRP still failed to recognize my SD card
Edit Edit-
Again after more searching, I have found a TWRP version that has recognized my SD card. However, One problem still remains before I am finished. I am still unable to flash the stock firmware. I navigate to my External SD card in TWRP, select the firmware zip file. Almost instantly it says that the install failed. Any ideas?

Lord Cyan said:
I have grabbed the blob file from the US firmware. Upon using the "fastboot flash system blob" command, I get the message < waiting for device > I have waited a half hour, and it is still there. am I doing something wrong?
Edit-
I have since got the fastboot to work after some research. When I went to wipe the data system cache and dalvik cache, TWRP said that it had failed. TWRP still failed to recognize my SD card
Edit Edit-
Again after more searching, I have found a TWRP version that has recognized my SD card. However, One problem still remains before I am finished. I am still unable to flash the stock firmware. I navigate to my External SD card in TWRP, select the firmware zip file. Almost instantly it says that the install failed. Any ideas?
Click to expand...
Click to collapse
cant you use fastboot to flash the stock firmware?

[Q] oh no...what have I done..!

I have spent the last 3 days trying to upgrade my Tf101 with an up to the minute os but have bitten off more than I can chew. I spent the whole of the first day just trying to root it to no avail. Ok, no problem, sleep on it. Next morning tried a different method and " hey presto " I have done it.
So, next job is download " Titanium " and make back up to micro sd card, all done. I then followed " Frederuco's Guide and installed EasyFlasher with TWRP 2.3.6.0 and with a bit of fiddling and button pushing managed to load it and followed his guide right through to the second option " Custom Rom with custom recovery ". I had loaded KatKiss 4.4.2_019.zip along with the add on pack and the latest Gapps package. So far so good. Did full the full wipe/ factory reset, cache, davlick cache, system etc, more success, nearly there. Back to TWRP home screen an click INSTALL to start the flash............where is the micro sd..........? Check further.........micro sd not mounted......oh sugar.......
So now I'm screwed, I think I have bitten off more than I can chew. My little TF101 was working fine before I messed with it albeit a bit slow but it was working. Micro sd card slot was working fine up until now. I am not that PC literate if anyone can help me it needs to be in simple terms please, but I can follow instructions. My pc is running on win 7 32 bit. The Asus was totally stock on the last firmware that ended with .27
I do have a keyboard dock with it but has not been coupled to it through out this process.
Have I trashed my little Asus..?
I appreciate any thoughts even if it bad news. This is the first time I have ever attempted something like this, a total newbie.
Thanks,
Steve

Go to the "Mount" option in TWRP and mount the MicroSD ?
If I remember correctly, with the newer TWRP builds, you have to change between Internal and External SD using a dropdown on the Install page

Also, you need to have the micro SD installed on boot I believe. It is not auto mounted in TWRP.

*Detection* said:
Go to the "Mount" option in TWRP and mount the MicroSD ?
If I remember correctly, with the newer TWRP builds, you have to change between Internal and External SD using a dropdown on the Install page
Click to expand...
Click to collapse
Tried that, it says something like " unable to mount in the logs " Did it quite a few times.
Thanks for the reply

frederuco said:
Also, you need to have the micro SD installed on boot I believe. It is not auto mounted in TWRP.
Click to expand...
Click to collapse
I thought that and that could have been my first mistake as I had not got the files on it when the Guide told me me to install the rom to flash.
I then put the files on a inserted the card but obviously it still did not mount. I did try the " mounting option " in the program but as you can see I did not manage it. I will try again but I am not holding my breath...!
Thanks for your reply.
Steve

Tyr flashing a different version with Easyflasher
http://forum.xda-developers.com/showthread.php?t=1688012
Or
Download a different flashable TWRP zip - 2.3.2.3 is the latest official build
Connect PC > TF and boot into TWRP
Use adb to push version 2.3.2.3 to the TF internal sdcard
adb push twrp.zip /sdcard/
Then flash from internal sd
You could do the same with the ROM

ok, lost me there....what is ADB ?

Just use Easyflasher, it's easy and quick
ADB
http://www.geek.com/mobile/what-is-adb-and-how-do-i-use-it-1461697/

I'm still trying now, have Easyflsher open but am struggling with it.......I've done so much reading my brain is pickled...!

I have been trying to use ABD sideload but it is not loading........

I am still trying to sort my problem out.
I have downloaded fresh copy of EasyFlasher- 0.8.3b-STABLE_2.6.3.0 which I assume is the latest version?
I am able to get the TF101 into APX mode and load TWRP.
It would appear that the TF is not connecting to my win7 PC because of a driver issue. When I go to device manager the Android ATP device has a yellow triangle through it which I asume is the driver issue. It keeps trying to load a new deiver but ends up as " Failed "
The drivers that I am pointing it at are " Universal Naked Driver 0.72 which I thought where the ones required or perhaps I am doing something wrong...?
I assume if I can get this connected I can move forward.
Can anyone help me with this issue please. I tried till 02.30 this morning, I never figured that it was going to be this hard..!
Thanks in advance
Steve

trwp 6.3.2.0
i am the first homebrew said:
I am still trying to sort my problem out.
I have downloaded fresh copy of EasyFlasher- 0.8.3b-STABLE_2.6.3.0 which I assume is the latest version?
I am able to get the TF101 into APX mode and load TWRP.
It would appear that the TF is not connecting to my win7 PC because of a driver issue. When I go to device manager the Android ATP device has a yellow triangle through it which I asume is the driver issue. It keeps trying to load a new deiver but ends up as " Failed "
The drivers that I am pointing it at are " Universal Naked Driver 0.72 which I thought where the ones required or perhaps I am doing something wrong...?
I assume if I can get this connected I can move forward.
Can anyone help me with this issue please. I tried till 02.30 this morning, I never figured that it was going to be this hard..!
Thanks in advance
Steve
Click to expand...
Click to collapse
Hi, don't panic, you have already install TWRPP. At first be sure your microsd card is always on fat32 and get rom and googapps
If ok put your pad off and insert your sd in. Reboot on twrp. To see your sd card hit install, on the high of the screen you can see "choose a zip to install", above hit on "storage internal storage", a new screen will open, select micro sd, your rom and should be here. If you want to remake all wipe before flasing hit the back arrow in the hight right corner. Hit Wipe on the menu, select partitions to wipe, hit all except micro sd and external (of course). Install rom and gapps, wipe cache and dalvik cache, reboot. I try it this day on twrp 2.6.3.10, i don't remenber for 2.6.3.0, but the way is the same. Good luck

jh1969 said:
Hi, don't panic, you have already install TWRPP. At first be sure your microsd card is always on fat32 and get rom and googapps
If ok put your pad off and insert your sd in. Reboot on twrp. To see your sd card hit install, on the high of the screen you can see "choose a zip to install", above hit on "storage internal storage", a new screen will open, select micro sd, your rom and should be here. If you want to remake all wipe before flasing hit the back arrow in the hight right corner. Hit Wipe on the menu, select partitions to wipe, hit all except micro sd and external (of course). Install rom and gapps, wipe cache and dalvik cache, reboot. I try it this day on twrp 2.6.3.10, i don't remenber for 2.6.3.0, but the way is the same. Good luck
Click to expand...
Click to collapse
Thanks for the reply.
I had 3 hrs on it yesterday before your reply and got nowhere so decided to give it a break last night..!
I appreciate your help with this and will attempt to follow your instructions tonight after work. Are you saying that I should disregard the driver issue as you think I am connected to TWRP ok?
Thanks again

i am the first homebrew said:
Thanks for the reply.
I had 3 hrs on it yesterday before your reply and got nowhere so decided to give it a break last night..!
I appreciate your help with this and will attempt to follow your instructions tonight after work. Are you saying that I should disregard the driver issue as you think I am connected to TWRP ok?
Thanks again
Click to expand...
Click to collapse
Yes, that the way i try first, if you can boot on TWRP there'snt any reason to reflash it !

To jh1969
I followed your instuctions......perfect, I don't think I would have figured it without your help. My micro sd card was formatted in NTFS...! Did format to fat32 and things started to work. Started form the beginning again and now I have it working again....!
I did a back up using Titanium (Apps+data) to the micro sd before I screwed it all up, just got to figure out how to restore that then things will be a lot better. Any idea how I get Gmail back ?
Thanks again for your help.

Figured out my Gmail problem, found the app on the play store, not sure how I missed it the first time.
Could not figure out Titanium, did try loads of times to restore apps & data but no luck so another late night downloading all the apps one by one and getting them all going.
At least I now have my pad working again but still have some issues to sort out.
I cannot get the camera working, when I try to open it I get " Unfortunately, Gallery has stopped"........I get the response also when I try to open " Gallery "
I have not yet figured out a quick way to look at the Micro SD....on the stock TF101 rom there was an icon you could open up in the bottom left corner but of course that has gone now. Any ideas?
Overall I am very please the way it is performing now, it is much quicker than it was prior to this update so thanks to all for there time for all who have developed these software's/roms etc to enable people like me to enjoy my TF101 and extend its life further. I would like to increase it speed a bit more but I think I had better get any issues sorted before I attempt anything else. I have not put it in its dock yet so will try that later today.

[Q] Can't flash from SD Card

Good evening, XDA :cyclops:
I am having issues flashing from recovery!
Some device info: Motorola Xoom WiFi, fully stock and fully updated, unrooted, bootloader unlocked today, device wiped multiple times. This is my first day trying anything custom on this device.
I decided today that i wanted to go custom on my Xoom today and update it to KitKat via this method.
I have downloaded all the required files per the mentioned guide. While in recovery i go to apply update from USB drive, but it is not finding any of the downloaded files from the guide.
What I see is
Code:
Android system recovery <3e>
Choose a package to install:
/sdcard
../
The ../ is my only option to click and it obviously returns me to the main recovery menu.
All the zip files are on the root of the SD card, not in sub folders. I have confirmed via PC and another phone that the files are indeed there. I tried with a different, fresh, formatted (fat32) SD card, but I'm getting the same results.
The Xoom is indeed reading the SD card, confirmed via settings>storage.
I've tried using adb, but it's telling me the image isn't correct, but it's certainly possible I'm missing a step with adb.
Code:
C:\Xoom bootloader unlocker2>adb reboot bootloader
C:\Xoom bootloader unlocker2>fastboot flash R.A.H._TWRPv2.6.3_BigPart_selinux.zip
unknown partition 'R.A.H._TWRPv2.6.3_BigPart_selinux.zip'
error: cannot determine image filename for 'R.A.H._TWRPv2.6.3_BigPart_selinux.zip'
Yes, the zip is in that folder. I thought maybe I'd root first, so I tried that method with the root zip, but I'm getting the same error.
Is there something I can do to repartition this device and get it rommed, or am I doomed to use it stock?
Thank you for your time!

I found some information stating that I need to enable the SD card, but since I'm running up to date SW, and I can see the SD card from settings, I'm assuming that this isn't the case, correct?

I'm still stuck. Anyone around who could give me some advice?

scubab said:
I'm still stuck. Anyone around who could give me some advice?
Click to expand...
Click to collapse
It appears the XOOM does not like SD Cards that were formatted using Windows
(or perhaps Quick Formatted using Windows).
Using a 4GB FlashDrive formatted as Fat32 using Linux (i.e. Linux Mint 17.3 Cinnamon 64 bit boot CD)
resolved the issue.

[Q] Soft Bricked tab, no custom recovery and no way of selecting USB debugging option

So i soft bricked my device while trying to install the latest 4.0.1 image. I tried hard wiping the device and wipe cache partion from Stock Recovery but didn't help, still wouldn't boot. I tried installing the image in Stock Recovery from Apply Update From External SD Card, but i got a few errors first "E:Failed to map file Operation aborted", i took a look at the file and it had about 1.67gb extra in "Userdata" i tried deleting that file and reinstalling from external sd card but then i got "E:footer is wrong" "E:signature verification failed" Operation Aborted.
Now i'm trying to install update from ADB (Surprisingly if i have the tab connected and im in Apply Update from ADB the tab is recognized in ADB
Code:
adb devices
serial # sideload and i have updated the drivers) But if i try to flash the recovery file 4.0.1 (provided from the developers site [cant post links]) "i just get waiting for device"
Anyone know how to get around this issue in ADB or properly install from external sd card without getting errors?
(Alternative read to my problem posted in the Nvidia Forums 98% sure i soft bricked my device [cant post links]

Did you ever find a fix? I'm having a similar problem.

Try to use fastboot restore everything.

I can't get it to connect to fastboot. When it loads the boot loader and I try to select fastboot protocol it fails.

Wow this thing sucks! I'm really appreciating my Samsung with Odin right now! So I finally got it to connect to fastboot (don't ask me how, I don't know) unlocked the bootloader and flashed twrp. Now it won't flash supersu in adb sideload so I put it on an SD card (which now magically mounts and works now) and flashed the zip in recovery but it says at the very end of the process while trying to update the partitions that it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so which one? I have no idea which version bootloader, kernel, or os is or was on this device...
Update: I think I may start a new thread in the Q&A/Help section so that I can try to get a vast concensus. Thanks!

rom fiend said:
Wow this thing sucks! I'm really appreciating my Samsung with Odin right now! So I finally got it to connect to fastboot (don't ask me how, I don't know) unlocked the bootloader and flashed twrp. Now it won't flash supersu in adb sideload so I put it on an SD card (which now magically mounts and works now) and flashed the zip in recovery but it says at the very end of the process while trying to update the partitions that it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so which one? I have no idea which version bootloader, kernel, or os is or was on this device...
Update: I think I may start a new thread in the Q&A/Help section so that I can try to get a vast concensus. Thanks!
Click to expand...
Click to collapse
Yes flash a ROM in recovery.
Try Resurrection Remix. It'll resurrect your device

Just tried flashing bliss 6.2 and it won't get past the nvidia screen. It says it flashes successfully but I still get a bunch of "can't mount such and such partition" errors during the flash sequence. Not sure what to do, I can post pics if you guys want.

If you got/can get TWRP on there now, the advanced wipe menu will allow you to check /data for errors. As for /system, wipe it. If you get errors that e2fsck can't fix in your TWRP log, you'll have to put on your data recovery hat on. If it's that important to you, my advice is to adb pull the right file under /dev/block. You won't get a block device, you'll get an exact image of your data partition. Once it's fully pulled (it'll be 10 GB or more on a 16GB device), make a copy of it first thing, and use data recovery tools (testdisk, or if you really know what you're doing, debugfs). If you don't have anything valuable on /data (remember that any backups you took from recovery go in /data/media by default), just format that and be done with it.
Pray that there are no errors after you format everything, because that usually means your NAND is toast.
If your errors are hardware ones, you're royally screwed. Same thing happened to my Nexus 7 2013 model a year ago. Only way to use it is to flash a modified kernel that will use an attached USB drive exclusively as storage. If the NAND is toast inside the boot partiti,try replacing recovery, otherwise, you have to tether boot it (fastboot boot) every time you want to run it, unless you have the guts to try repartitioning the NAND (unlike on PCs, messing up there is an instabrick).
Since the Shield Tablet can use SD cards, you're better off. No USB drive needed.