After flashing a stock ROM, my A701 is stuck at the first screen with the "acer" logo.
I can get into fastboot mode and also start CWM recovery, but can't access external_SD - when I try to mount it in CWM, it gives an error.
So I can't copy an image to the A701 to reflash again.
Any idea how I can fix this problem ?
Many thanks in advance !
This usually happens to me when the card is removed without proper unmounting it, put the card into a cardreader and plug it in to your computer, maybe it checks for errors automatically, if it does not, scan manually.
This usually helps me when my sd card is not mountable.
Since you're able to get into recovery, have you tried to do the adb push method? Something like adb push /ROM.zip /sdcard0" I can't recall of the top of my head what the default sdcard directory is, but I hope you get the picture..
Thanks guys, I succeeded with flashing Iconian ROM from another external SD and my tablet is running again.
Now I would like to go back to a stock ROM, preferably 4.0.4 - is there any version which is CWM flashable ?
Related
Hello,
I rooted my tf101, all went well. Put clockworkmod recovery on it and still no problems. Now I wiped all partitions by mistake of my tf101. The only thing left is the recovery image (cwr) but if i try adb tool to push a file on the system it says the system is readonly. If i try nvflash tool is also says error onable to write and it disconnect the tf101.
Can any body help me, or do i have to put it back to repair
thanks Ernst
Well, if you have a microSD card, and a CWM that can read from it, you could just hook the card up to your PC (using a phone with microsd slot, or a cardreader, etc) and place the new image on the card.
Also, have you tried running 'adb root' to make sure ADB is running as root?
@Goatshocker
I tryed to insert a microSD card, but cwr does not recognize it, at least it does not appear in the menu structure.
Also tryed adb root, it sayed hat it is already in root.
ernst99999 said:
@Goatshocker
I tryed to insert a microSD card, but cwr does not recognize it, at least it does not appear in the menu structure.
Also tryed adb root, it sayed hat it is already in root.
Click to expand...
Click to collapse
If you are using cwm 5.5.0.4, go to the following link.
http://forum.xda-developers.com/showthread.php?p=23256536
@kokopopz
I have indeed version 5.5.04, have read the tread you mentioned, but no solution. My problem is that if i try to push a file to the TF than it says "read-only file-system". Tryed in cwr to fix permisions, but no help.
Problem stays the same.
@kokopopz Thanks for your link.
I Found the solution !!!! My TF is UNBricked. YES YES YES.
For the record: "adb push rom.zip /data/media/rom.zip" will do the trick, after that reboot to cwr and do install zip from sdcard.
Problem
So i was running a slim rom and suddenly my device started rebooting constantly.
What i Tried
Wiping everything (System/Data/Cache/SDCard) booting into recovery and put jellyshot rom zipfiles on the sd card.
What happens now
When i unmount USB and try to flash the new rom, the files (jellyshot rom) aren't on the sdcard. When i mount USB again they also aren't on the card.
I have repeated this constantly and can't make any sense of it.
Is my device "bricked" ?
Thanks in advance.
volowi choose
Basicly whenever i MOUNT USB, delete and add files, the next time i MOUNT USB, the files are back in their original state. Known behaviour?
This is definitely not known behavior. To me it looks like you are getting write permission on the drive once you mount. So it looks to you as if file are getting deleted or files are getting added. But once you unmount/mount again, the changes are not done. It could be a problem with the recovery that you are using. May be try to flash a different recovery in fastboot mode.
Don't you have any other ROM on SD card to flash & boot. If you can boot in to the ROM, then may be you can see if you are able to correctly use SD card and copy a new ROM before you start wiping.
try format your sd from pc
anshumandash said:
This is definitely not known behavior. To me it looks like you are getting write permission on the drive once you mount. So it looks to you as if file are getting deleted or files are getting added. But once you unmount/mount again, the changes are not done. It could be a problem with the recovery that you are using. May be try to flash a different recovery in fastboot mode.
Don't you have any other ROM on SD card to flash & boot. If you can boot in to the ROM, then may be you can see if you are able to correctly use SD card and copy a new ROM before you start wiping.
Click to expand...
Click to collapse
I am able to boot into the rom (with constant errors popping up) and turn on/off usb storage but the effect is the same.
Mount ->Change files ->Unmount -> Mount -> Nothing has changed
leap_ahead said:
try format your sd from pc
Click to expand...
Click to collapse
Tried that to no effect.
Mount -> Format -> Unmount -> Mount -> All the files are there again...
No Mobile Network or USB Connection!!!
Hey I am pretty new to rooting but I have a major problem. I recently rooted my Samsung Nexus 4G, flashed clock work mod recovery and installed a version of Jelly Bean I found in on some website. But my problem is that I began to have problems with the version of Jelly Bean I download so I tried to flash back to stock but something went horribly wrong. Now my phone does not have mobile network and when I connect it to a computer, the computer will not recognize it. Bluetooth, WiFi and SD Card still works but I cannot find a way to get my Mobile Network to come back. Please Help!!
I'll install SDK, Odin, put the phone in download mode and flash a factory image. Just saying
Envoyé depuis mon Nexus S avec Tapatalk
Odp: [Q] Help me figure out what's wrong
Hey! I had a similar problem with my i9023. I couldn't Access my files through the PC after flashing slim beam. I downloaded JellyShot and marmite kernel with my device, without using PC. Then i found those files in sdcard/download, flashed with no problems. Everything seemes to be ok now.
Sent from my Nexus S using xda app-developers app
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.
I cleaned my tablet tf300, to install a newer and different rom, now i can't get twrp to see my microsd card to install the rom, how can i get the rom file to my internal sd card to proceed, as i can't get adb to work either, i've no idea how to copy the files to internal to get going again.
Any and all help will be appreciated. Thanks.
Luca Brasi09 said:
I cleaned my tablet tf300, to install a newer and different rom, now i can't get twrp to see my microsd card to install the rom, how can i get the rom file to my internal sd card to proceed, as i can't get adb to work either, i've no idea how to copy the files to internal to get going again.
Any and all help will be appreciated. Thanks.
Click to expand...
Click to collapse
Make sure the SD card is mounted in the "Mounts" section of TWRP.
I did that but it won't stay in that mode, keeps on reverting to internal.
Luca Brasi09 said:
I did that but it won't stay in that mode, keeps on reverting to internal.
Click to expand...
Click to collapse
Did you try unmounting the internal, then mounting external?
I have zero luck in getting it to stay on external SD, I've tried to unmount the internal and then mount the ext sd, so I am stuck. I don,t even see USB mode when I hold volume down and power, the only option is recovery Android and wipe data, so I don't seem to be able to get the zipped rom i want to install copied where I can use it.
Luca Brasi09 said:
I have zero luck in getting it to stay on external SD, I've tried to unmount the internal and then mount the ext sd, so I am stuck. I don,t even see USB mode when I hold volume down and power, the only option is recovery Android and wipe data, so I don't seem to be able to get the zipped rom i want to install copied where I can use it.
Click to expand...
Click to collapse
Thats how the new bootloader works, fastboot protocol is enabled the second you boot to that menu. So make sure you are on the patched 2.4.4.0 recovery.
I've downloaded a patched version of the twrp 2.4.4.0, but i can't access usb function to use fastboot or any other method to get the patched file to my internal storage on the tablet. Any ideas as how to transfer the needed file? Hope it's not bricked beyond repair. Plus my pc fails to install device driver, i am stuck at the starting screen that says "the device is unlocked" and asus logo.
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.