Probs with TWRP Recovery - not recognized Ext SD + Auto quit & booting to Android sys
Hi, I am having following problems with TWRP on my i9082 - Stock 4.2.2. I did a stock factory reset first. And then installed TWRP using Odin.
Note:My phone is rooted, using SUv2.65.
1) TWRP 3.0 + all versions. I have tried every version till the latest 3.02, but with every 3.0 and higher version, my external SD Card is not detected... Though Android System can detect the SD Card, and read and write files to it.
2) If I use TWRP 2.8.6 tar installed using Odin, then it reads the SD Card, but gives this message E:Unknown File System: 'datamedia' .
If I ignore that message, and try backing up my Stock ROM, then in about half a minute, it automatically reboots into Android system, and the Backup is not created...
Hence I am not able to create any Backup.
Could somebody please help. I can't understand that error. And also can't understand why higher versions of TWRP (which do not have this error), cannot detect the SD Card
But in every version, I cannot stop TWRP automatically quitting and the Phone booting into Android in less than a minute. I even disabled Screen timeout... Doesn't help!
johnsamshri said:
Hi, I am having following problems with TWRP on my i9082 - Stock 4.2.2. I did a stock factory reset first. And then installed TWRP using Odin.
Note:My phone is rooted, using SUv2.65.
1) TWRP 3.0 + all versions. I have tried every version till the latest 3.02, but with every 3.0 and higher version, my external SD Card is not detected... Though Android System can detect the SD Card, and read and write files to it.
2) If I use TWRP 2.8.6 tar installed using Odin, then it reads the SD Card, but gives this message E:Unknown File System: 'datamedia' .
If I ignore that message, and try backing up my Stock ROM, then in about half a minute, it automatically reboots into Android system, and the Backup is not created...
Hence I am not able to create any Backup.
Could somebody please help. I can't understand that error. And also can't understand why higher versions of TWRP (which do not have this error), cannot detect the SD Card
But in every version, I cannot stop TWRP automatically quitting and the Phone booting into Android in less than a minute. I even disabled Screen timeout... Doesn't help!
Click to expand...
Click to collapse
Hi johnsamshri
You just posted this same help request at the correct Forum and, as so, you should wait a couple of day for replies and, if you are not addressed, please report back to us.
Nice regards and good luck.
THREAD CLOSED.
.
Related
Im having real problems with my Nexus S on 2.3.4 rooted
When I start it up I just get constant force close messages from a load of apps, including system apps. I cant use the phone at all because everything crashes. I've not really made any changes apart from manually flashing the 2.3.4 update and thats been running stable for about a week
I figured I would try and flash a new ROM and/or go back to stock 2.3.1 ROM which I found in the forums here to fix it but whatever I save to my SD Card does not appear in clockwork recovery when I select "Install from zip"
I then tried to copy the ROM again which was showing on the phone through windows explorer, then when I unplugged the cable and plugged it back in, the file had disappeared and any files/folders I created on the SD Card have gone.
Any help would be much appreciated
edit*
All of the apps crashing seem to complain about the database. Im getting SQLiteExceptions from everything, either unable to find file or cannot write to a read-only database
I've tried to lock/unlock the boot loader, wipe everything via recovery (clockwork and stock) and factory resets but everytime i restart, its always the same as if i haven't wiped and the errors keep on coming
grateful for any help
i think these problems are all linked to being unable to save to the sdcard/internal storage. Is there a way to flash a rom without using the internal storage? say have it linked to the PC and do it from there?
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?
I have seen this mentioned a few times in several threads without any resolve that I can find.
Since flashing CWM 6.0.4.5 it no longer will go straight into a backup or restore without stopping at the CWR recovery screen with the following error message:
waiting for sd card to mount (20s)
SD card mounted...
Verifying SD Card marker...
SD card marker not found...
Error processing ROM manager script. Please veri
fy that you are performing the backup, restore,
or ROM installation from ROM manager v4.4.0.0 or
higher.
/tmp/recovery.log was copied to /sdcard/clockwor
kmod/recovery.log. Please open ROM manager to re
port the issue.
Well it has been reported several times and I am up to date with ROM manager.
Has anyone else experienced this? And if so were able to resolve it?
Maybe we can figure this out. :fingers-crossed:
I don"t know if this is related but in ROM Manager it identifies the sd card as: extSdCard/ But when booted in recovery CWR identifies the sd card as: /storage/sdcard1
I downgraded to ROM Manager 6.0.3.1 and now it will perform a backup or restore seamlessly without the error but I will not be able to flash any 4.4.x roms. Also the sd card path now states: /storage/extSdCard/
any help is appreciated!
I fixed it! I have converted to twrp recovery and rom installer as my interface app. (it was already on my device included in rom toolbox) they work together seamlessly. Thanks everyone for your help!
Sent from my SCH-I535 using Tapatalk
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.
I am a complete newbie to rooting. I followed the kingoroot guidelines and rooted my Idea Aurus 3 phone. Root was success. The next step I did was downloading custom recovery and cyanogenmod ROM from here to my memory card
I flashed the custom recovery with flashify. The next step I did was wiping all data from the device by entering in to recovery mode (including cache and everything)
I was hoping I could simply install zip from sd card. But when i click on this option, I cannot find my sd card nor zip file (I checked most folders including emmc, etc, sd-ext and couldn't find SD card. The custom recovery name is Phylz touch 6
Now basically I have a phone without OS and all I can do is accessing custom recovery. I don't have a back up too
I can also see an error log "Cannot mount custom path"
I formatted the memory card to exFAT from exFAT 32 hoping that would work, it didn't help as well.
Also tried to connect phone to pc using USB (thinking I can move rom to system memory), but wouldn't detect phone memory
Now, is there any way to get this fixed? Any help would be awesome
Thanks!!!
kumarj said:
I am a complete newbie to rooting. I followed the kingoroot guidelines and rooted my Idea Aurus 3 phone. Root was success. The next step I did was downloading custom recovery and cyanogenmod ROM from here to my memory card
I flashed the custom recovery with flashify. The next step I did was wiping all data from the device by entering in to recovery mode (including cache and everything)
I was hoping I could simply install zip from sd card. But when i click on this option, I cannot find my sd card nor zip file (I checked most folders including emmc, etc, sd-ext and couldn't find SD card. The custom recovery name is Phylz touch 6
Now basically I have a phone without OS and all I can do is accessing custom recovery. I don't have a back up too
I can also see an error log "Cannot mount custom path"
I formatted the memory card to exFAT from exFAT 32 hoping that would work, it didn't help as well.
Also tried to connect phone to pc using USB (thinking I can move rom to system memory), but wouldn't detect phone memory
Now, is there any way to get this fixed? Any help would be awesome
Thanks!!!
Click to expand...
Click to collapse
Hello,
Please try posting your query in Android Q&A Forum, the experts there maybe able to assist you.
Regards
Vatsal,
Forum Moderator.