Can't write to MoviNAND - Galaxy Tab General

Hello,
I was updating my Tab to 2.3.6 from 2.3.3, and since then, i can't write to MoviNand anymore. This means that whatever I write to /data or /sdcard doesn't actually change on the flash memory. When I remount or reboot, everything is back to normal.
This includes changes made using: mass storage, ADB, Recovery and even ODIN with repartition and a .pit file.
I've flashed the tab back to 2.3.3 and even to 2.2, but the contents of /data keeps unchanged.
I'm out of ideas. Anyone?

Related

error mounting /data- brick? LOL

I tried reflashing a sense 3.0 2.3.3 rom because of some minor issues. Now I may have nuked my /data partition. first it wouldn't format so I pulled battery numerous times. and Mounted it through mounts and storage menu, then I hit format, and it formatted, so I hit mount again and flashed the rom. and when I restarted the phone after splash screen the phone restarted and went into recovery
Tried everything including mounting /data again and it keeps saying error mounting /data. am I screwed?
I have .2007 eng bootloader btw. shoud I try the pd15img?
_ice_ said:
I tried reflashing a sense 3.0 2.3.3 rom because of some minor issues. Now I may have nuked my /data partition. first it wouldn't format so I pulled battery numerous times. and Mounted it through mounts and storage menu, then I hit format, and it formatted, so I hit mount again and flashed the rom. and when I restarted the phone after splash screen the phone restarted and went into recovery
Tried everything including mounting /data again and it keeps saying error mounting /data. am I screwed?
I have .2007 eng bootloader btw. shoud I try the pd15img?
Click to expand...
Click to collapse
I don't think you need to do that. You could do a fastboot erase, then go back into recovery and wipe data to reformat it /data, effectively starting from nothing.
jdkoren said:
I don't think you need to do that. You could do a fastboot erase, then go back into recovery and wipe data to reformat it /data, effectively starting from nothing.
Click to expand...
Click to collapse
Now I am getting mount /cache errors. aww man I think my phone is done....
edit: used the pd15img and I am back on stock :| s= off but I have the stock bootloader wtf.... how do I get my eng bootloader back?
this is how I fixed it:
I was on eng bootloader, but then I got reverted back to the stock bootloader.
This is how I encountered the problem. first of all I was having issues with raffy's fusion 3.0 rom, so I decided to reflash it, but it wouldn't flash or format /data, then I mounted it to through mounts and storage on the latest cwm 3.0.2.4 and hit format.
After that I tried reflashing his rom, it flashed but, after splashscreen I was redirected to my recovery instead. that's when I freaked because when I tried mounting data it said error cannot mount /data. so I fired up adb and did fastboot erase system -w and it erased it including cache.
then I popped up into recovery and BOOM started having cache mount errors experienced by a lot of people lately.
I thought I was SOL, but nope I downloaded the pd15img from http://www.megaupload.com/?d=V4NAODYZ
and put it on the root of my sd card and it worked....
so if anyone of you dudes are having similar problems try that ^

[Q] Tab won't boot. Clean ROM install doesn't help.

My tab froze and when I rebooted it, I get a black screen right after the AOKP logo. It just sits there forever. I can boot recovery.
My story is below, but I think my question is: How can I format the partitions, because I think /data is corrupt?
Story:
I can boot recovery, and I wiped everything, then tried adb pushing a rom to the /sdcard. That's when things got weird...
adb push failed, so I rebooted and noticed that /data wasn't mounted. (/sdcard is just a symlink to /data/media)
I mounted /data from recovery and tried to push the ROM file again. This time I got some I/O errors on the push. I also noticed that in an adb shell, the /data partition would sometimes unmount by itself, and threw disk errors when copying files around. All other partitions seem to work fine.
So I deleted everything in /data/media, formatted /data, and tried again. This time I could adb push the ROM. I installed the ROM, but I still get the same freeze after AOKP logo.
cryptyk said:
My tab froze and when I rebooted it, I get a black screen right after the AOKP logo. It just sits there forever. I can boot recovery.
My story is below, but I think my question is: How can I format the partitions, because I think /data is corrupt?
Story:
I can boot recovery, and I wiped everything, then tried adb pushing a rom to the /sdcard. That's when things got weird...
adb push failed, so I rebooted and noticed that /data wasn't mounted. (/sdcard is just a symlink to /data/media)
I mounted /data from recovery and tried to push the ROM file again. This time I got some I/O errors on the push. I also noticed that in an adb shell, the /data partition would sometimes unmount by itself, and threw disk errors when copying files around. All other partitions seem to work fine.
So I deleted everything in /data/media, formatted /data, and tried again. This time I could adb push the ROM. I installed the ROM, but I still get the same freeze after AOKP logo.
Click to expand...
Click to collapse
I would say you need to ODIN your TAB:
Use this:
http://forum.xda-developers.com/showthread.php?t=1651794

Save internal storage from i9505 software brick/stuck on bootlogo

Hello,
since one week my device, a samsung galaxy s4 i9505, is software bricked and stuck on bootlogo and I've been tryin to save my internal storage, but I'm close to giving up. I hope someone here can help me.
My situation:
1. Updated my TWRP to version 3.0.1-0-jfltexx with odin 3.10.0
2. Flashed new ROM "OMEGA ROM", that worked good.
3. Backup with TWRP, successfull, reboot, galaxy logo appears, flash, again -> bootloop
4. Flashed firmware "i9505XXUHOB8" BL and modem, with odin 3.10.0 in BL and CP
5. No bootloop anymore, but stuck on ROM Logo with normal start and with recovery start blue text "recovery booting..." on galaxy screen but nothing happens.
6. Saw that TWRP 2.8.7.0-i9500 is the recommended TWRP for the i9505, flashed the .img.tar with odin 3.09 in AP (is the .img a problem?) but still same problem, with TWRP 2.8.6.0-i9500.tar too.
6. Tried different firmwares: i9505XXUHOB7, i9505XXUHOF2, i9505XXUHOJ4 -> I thought the problem is the bootloader -> odin error: complete (write) operation failed or NAND write error (->problem was usb port)
7. Tried different odin versions: 1.85, 3.10.6, 3.09
8. Tried different usb cables
9. Flashed cf-auto-root to mount the data partition, but theres no option. Recovery mode is now working, but the samsung recovery, not TWRP.
10. Tried to copy internal storage with ADB, can navigate the directory but can't pull or cd /storage/sdcard0 -> no such file or directory, same with /mnt/sdcard (ADB only works during the ROM logo)
11. Flashed stock samsung firmware "i9505XXUHOJ2_i9505AUTHXXUHOJ1_i9505XXUHOJ2" with odin 3.09 -> now stuck on samsung boot logo. My ROM is now deleted, right?
12. Wipe cache don't help
13. Could wipe data/factory reset or repartition with odin but then I will lost my internal storage.....
I have a backup from the successfull backup with TWRP, but can't open the data.ext4.win001 after rename it (the .win000 is ok)....
Can anyone help me or have an idea how can I save my data and repair the system?
-Mr.Tea
use TWRP to copy files from internal storage over to external SDcard for stuff you wanna keep.
if you manage to backup the data partition you're supposed to be able to extract apps and data from a nandroid with titanium backup pro (never tried it though).
this data you wanna save, if it wasn't created while running omega rom then it wasn't likely to work with it anyway. that could be the source of your bootloops. if that data came from a previous custom rom then try to go back to it, and if successful backup apps with titanium and files to SDcard. you can't keep your data partition and go into a new rom with it.
if the data came from a stock rom you'll loose it trying to go back so extracting from a nandroid is probably your best bet there or restoring once back to stock.
3mel said:
use TWRP to copy files from internal storage over to external SDcard for stuff you wanna keep.
if you manage to backup the data partition you're supposed to be able to extract apps and data from a nandroid with titanium backup pro (never tried it though).
this data you wanna save, if it wasn't created while running omega rom then it wasn't likely to work with it anyway. that could be the source of your bootloops. if that data came from a previous custom rom then try to go back to it, and if successful backup apps with titanium and files to SDcard. you can't keep your data partition and go into a new rom with it.
if the data came from a stock rom you'll loose it trying to go back so extracting from a nandroid is probably your best bet there or restoring once back to stock.
Click to expand...
Click to collapse
TWRP is not working anymore -> blue text "Recovery booting..." on galaxy logo
In many forums they mean TWRP backup not includes the internal storage (/sdcard partition)?!
Can extract my "data.ext4.win000" and "data.ext4.win001" but not find the /sdcard location or my userdata.
Mr.Tea said:
TWRP is not working anymore -> blue text "Recovery booting..." on galaxy logo
In many forums they mean TWRP backup not includes the internal storage (/sdcard partition)?!
Can extract my "data.ext4.win000" and "data.ext4.win001" but not find the /sdcard location or my userdata.
Click to expand...
Click to collapse
try TWRP 3.0.0 by JDCteam, hundreds of happy users there. if it works first time make sure to try backing up your data partition and then wiping it. you can copy your media storage with the built-in file browser as mentioned.
you've got bigger problems if it's not data causing your problems...

910c; /efs issue, can't mount /efs or use TWRP, but I have full TWRP's (with efs)

My phone isn't working and I get the "dm-verity" issue as well as "can't mount /efs" issues at stock recovery
I've used TWRP backup/restore before and I have several month-old backups of the /efs partition, but they aren't restoring properly
Whatever issue I'm having is with the particular /efs format of the phone
I've already done stock format and reinstall via ODIN (including the NAND wipe, pit file, etc). I've also booted into TWRP to run terminal commands, which briefly resulted in me being able to boot up with a stock image (albeit with no network registration signal), until I attempted to recover /efs from TWRP
I'm stuck, any of you know what to do?
try repair with 4 files firmware for your phone - choose your csc - https://firmware.gem-flash.com/index.php?a=browse&b=category&id=7615

SM-T580 TWRP issues

So I successfully Flashed TWRP on my Galaxy Tab A SMT580. Two issues I'm experiencing tho....
1.) TWRP is unable to mount my internal storage which shows as 0MB. Thus I obviously have no ROM I can boot into. It reads and mounts my SD card and the correct size shows up. Unfortunately I have nothing on my SD card and I can't get ADB Sideload to work.
2.) Which brings me to my next issue whenever I do attempt to boot it says failure to verify. Which is fixed by flashing that DM-Verity zip file. But I can't since it's not on my SD card and, ADB Sideload won't work.
Any thoughts on how to fix these two issues.
I feel stupid having forgotten to put the file on my SD Card prior to flashing TWRP
Silicon Knight said:
So I successfully Flashed TWRP on my Galaxy Tab A SMT580. Two issues I'm experiencing tho....
1.) TWRP is unable to mount my internal storage which shows as 0MB. Thus I obviously have no ROM I can boot into. It reads and mounts my SD card and the correct size shows up. Unfortunately I have nothing on my SD card and I can't get ADB Sideload to work.
2.) Which brings me to my next issue whenever I do attempt to boot it says failure to verify. Which is fixed by flashing that DM-Verity zip file. But I can't since it's not on my SD card and, ADB Sideload won't work.
Any thoughts on how to fix these two issues.
I feel stupid having forgotten to put the file on my SD Card prior to flashing TWRP
Click to expand...
Click to collapse
By default, the data partition on the T580 is encrypted. In order to install a custom ROM, you must first format that partition. Click wipe then format data, type in "yes" and when it finishes, reboot to recovery. Your internal storage should no longer show 0mb.
ok that worked, my internal storage is now mounted, but my SD Card is not. Now I just need to figure out how to get the custom ROM files and the DM Verity file onto my internal storage.
how can I just flash the tablet back to stock recovery and ROM
so I got everything working, I didn't need to flash a rom, it booted to the stock rom, ony issue that remains, is for some reason the WIFI will no longer turn on. When I tap on it in settings to turn it on, it just says its turning on, but never actually turns on. Just hangs there. I can't figure out what to do
anyone ? I really need to get this fixed...should I reflash the stock rom using ODIN, maybe a fresh install will fix it ?
Also, when I plug my tablet into the laptop, it says connected device cannot access data, and the tablet doesn't show up on the laptop, so I have no way to transfer files or anything. It does show up on ADB, I thought about trying to push the files that way, but not sure if thats possible, been a long time since I used ADB.

Categories

Resources