[Q] Hanging at formatting /data [FIXED] - Android Q&A, Help & Troubleshooting

Device: Samsung Galaxy Tab 7.0 Plus, P6200.
ROM: CM9.
Started with the device rebooting every time I tried to do nandroid backup when it got to backing up /data. I attempted to factory reset but then CWM (6.0.1.0) just hanged at formatting /data.
Then I attempted to do factory reset from the ROM (CM9). The device got stuck in a bootloop of trying to format /data and just hanging there. The device kept turning itself back on when turned off to go into this ridiculous loop.
Is my on-board sdcard fried or something? Anything I can do?
UPDATE: Fixed it, I hope. . . Ran f2sck from recovery on mmcblk0p10, needed three rounds before all the errors were gone. Then could successfully do factory reset and reinstall ROM. Restoring from backups now, hopefully nothing borks again,

try to get back to the stock rom via odin it will overwrite the data partition and of course the recovery image so ure back to 0 than and are able to continue what u wanted to do

Related

[Q] Stuck in boot

I've tried to flash my rom to CM7 but something went wrong with the procedure because I am stuck on the android boot screen (Android logo lightning, it gets stuck for a while and then the letters continue flashing, cycling).
I followed the normal procedure: root, installed custom recovery, I made a backup with nandroid (normal one, which I copied to my computer), wiped data+cache (both caches) and I tried to flash from SD. Update went as normal but I got stuck in this boot screen.
After trying 2 or 3 times this same procedure and being unable to move on, I tried to recover my backup using nandroid: it said it was unable to recover and to do it from adb; adb says that it's unable to mount my sdcard.
From what I've read, I would need to repartition my card.. I chose that option in the recovery; still unable to recover my backup.
I figured that it would not be too bad if I lost my data, so after giving up on CM7 I gave up on recovering my data as well.. the problem is that even after wiping data and cache I'm still stuck in this same boot screen.
Any idea?
I can access recovery and adb so this has to have a solution..
I managed to boot after formatting /system.

ATT I777 Boot Loop. Factory rest not working

Hi,
I need help!!
I have been loading custom ROM's using CWM occasionally and yesterday when I tried to flash CM9 ROM my ATT S2 got stuck at boot screen. Then I tried to do a factory reset. Doing factory reset got me stuck at "Formatting Data" and it never moved from there for 1 hr then the phone started booting again. Ever since then I am not able to boot back. I have tried all possible options - every time I try I get stuck at Formatting /data. I tried installing Siyah-v2.6.14-att vis ODIN and tried to restore from my back up. It failed saying "Error while restoring / Data!". I installed factory stock rom via ODIN still the same. I tried wiping the data using darkside super wipe it too got stuck Formatting Data and nothing happened.
Is my data corrupted? I dont know what to do. Can some one please help? Should I try re-partitioning? I am bit scared to do that.
veenaguns said:
Hi,
I need help!!
I have been loading custom ROM's using CWM occasionally and yesterday when I tried to flash CM9 ROM my ATT S2 got stuck at boot screen. Then I tried to do a factory reset. Doing factory reset got me stuck at "Formatting Data" and it never moved from there for 1 hr then the phone started booting again. Ever since then I am not able to boot back. I have tried all possible options - every time I try I get stuck at Formatting /data. I tried installing Siyah-v2.6.14-att vis ODIN and tried to restore from my back up. It failed saying "Error while restoring / Data!". I installed factory stock rom via ODIN still the same. I tried wiping the data using darkside super wipe it too got stuck Formatting Data and nothing happened.
Is my data corrupted? I dont know what to do. Can some one please help? Should I try re-partitioning? I am bit scared to do that.
Click to expand...
Click to collapse
there are chances of the data partition getting corrupted... try flashing back to stock rom...

Bootloop with a "cant mount sd card" promt.........screwed?

Tab 10.1 root/rom running 4.1.1
I just flashed a jelly bean ROM and it was working perfectly until I set up google now and rebooted. It rebooted several times and made it back to the lock screen but it became worse everytime it rebooted until it was stuck at the boot animation.
I properly backed up all my data with the latest CWM version. BUT.......when I try to restore I get a E: Cant mount /sdcard. That means no factory reset. This thing doesnt have a physical sd card either so its not as simple as going to buy another one.
Is this a hardware/driver issue? Im kinda screwed here.........thoughts?
Some days ago, I had a similar problem. After flashing mobile Odin and reboot, I got a boot loop. factory reset and restore backup doesn't work. I'll had to flash stock rom with Odin because of a bad petition on my internal storage.
so if you want to flash, try to backup all data on PC (but I don't know how to do when the tab only goes to cwm).
After flashing the stock rom, I had to do a factory reset in stock recovery. I after that, my tab works fine. now I'm back in jb 4.1.1 Rom

Soft brick - stuck at boot logo; need suggestions

Hey all,
I've got a N7105 (Galaxy Note II LTE) running CM12.1 and TWRP which I was planning to change shortly as it's old and the USB port has issues (charges but doesn't pass data; luckily it has a microsd slot). As it happens, the other day I left it discharge fully and turning it back on left it stuck at Samsung logo (not boot animation, the splash screen before it) forever.
I am: not a noob, I've rooted and flashed plenty of devices before.
I tried: removing battery for a while, charging fully, removing microsd and sim, clearing Cache and Dalvik. Nothing works.
I can: get into ODIN mode (but it's useless as USB data is not working); get into TWRP recovery; explore the Data partition in TWRP
I cannot: mount the System partition in TWRP, not even manually. It just does not let me select it, and gives an error whenever it needs to access it (e.g. if I try to backup it is says Error: unable to mount System)
I want: if possible to solve the issue without formatting Data. I had a TB backup but kinda old, so I got a Nandroid of Data and Boot out from TWRP and I suppose I could then recover stuff extracting from Nandroid through TB, but I've never done it and would rather be able to get a fresh TB backup and move on from there.
A few questions I have: any idea on why I am not able to mount System in TWRP? Could it help to reflash Boot or System, and if so how do I go to do that considering what I have is the whole CM rom package? (I remember being able to fastboot flash single partitions on Nexus devices but that's because the stock rom comes packaged in separate images).
Any input would be greatly appreciated!
Lazer Bear said:
Hey all,
I've got a N7105 (Galaxy Note II LTE) running CM12.1 and TWRP which I was planning to change shortly as it's old and the USB port has issues (charges but doesn't pass data; luckily it has a microsd slot). As it happens, the other day I left it discharge fully and turning it back on left it stuck at Samsung logo (not boot animation, the splash screen before it) forever.
I am: not a noob, I've rooted and flashed plenty of devices before.
I tried: removing battery for a while, charging fully, removing microsd and sim, clearing Cache and Dalvik. Nothing works.
I can: get into ODIN mode (but it's useless as USB data is not working); get into TWRP recovery; explore the Data partition in TWRP
I cannot: mount the System partition in TWRP, not even manually. It just does not let me select it, and gives an error whenever it needs to access it (e.g. if I try to backup it is says Error: unable to mount System)
I want: if possible to solve the issue without formatting Data. I had a TB backup but kinda old, so I got a Nandroid of Data and Boot out from TWRP and I suppose I could then recover stuff extracting from Nandroid through TB, but I've never done it and would rather be able to get a fresh TB backup and move on from there.
A few questions I have: any idea on why I am not able to mount System in TWRP? Could it help to reflash Boot or System, and if so how do I go to do that considering what I have is the whole CM rom package? (I remember being able to fastboot flash single partitions on Nexus devices but that's because the stock rom comes packaged in separate images).
Any input would be greatly appreciated!
Click to expand...
Click to collapse
The note 2 has this issue that makes it unable to be recognized by PC, so this isn't your phone problem, the only way to solve it is replacing the usb socket in your phone, anyway i can recommend dirty flashing your rom first, just flash the rom in recovery and wipe cache and Dalvik cache only then reboot.
If that didn't work, I'm afraid you might have to...... clear data ?
MigoMujahid said:
The note 2 has this issue that makes it unable to be recognized by PC, so this isn't your phone problem, the only way to solve it is replacing the usb socket in your phone, anyway i can recommend dirty flashing your rom first, just flash the rom in recovery and wipe cache and Dalvik cache only then reboot.
If that didn't work, I'm afraid you might have to...... clear data
Click to expand...
Click to collapse
Thanks for the input, I was thinking something along those lines but I wasn't totally sure, I always avoided dirty flashing as I heard of people having issues. Happily, it worked! Weirdest think I saw in a while, it gave me a bunch of errors with System partition (unable to mount, unmount, find), then it gave a "proceeding to patch system partition unconditionally", then it completed. The whole thing took less than 20secs so I do not think it even actually flashed the ROM. Now I am just getting some Play Services error, likely need to reinstall gapps, but phone boots just fine!

Serious issue with the TWRP/Nandroid backup - twrp backup failed to mount system root structure needs cleaning - keeps looping back into TWRP

So, I can't restore my backup due to the error above. When I restore my backup, I get that error and a reboot loops me straight back into TWRP. You can read all that stuff below if you need the backstory.
(I had Lineage OS 18.1 installed and wanted to restore a backup from two weeks ago. So, I booted into TWRP, did a normal factory reset and restored the Backup of Lineage. However, it put out an error regarding something in root (structure needs cleaning). I tried rebooting into system, but it ended in fastboot mode. So I googled it and one thread said you can solve that by formatting system. "System" is backed up anyway, so I thought there was no harm, wiped it and restored the same backup once again. No error this time.
However, when I rebooted into system, the unlock pattern didn't work any more, even though I never changed it and always use the same one. I had to reboot into recovery, and now the TWRP unlock pattern didn't work either. Had to skip it and did another reset.
Now, every time I restore a backup (and those backups contain basically every partition available) it works, but when I reboot into system it just stops at the boot logo, then reboots into recovery. Basically a boot loop plus. Tried a fresh flash, same loop.
Also, all of my pictures and downloaded files are gone, because it's encrypted. I had to wipe data, which led to the whole encryption issue going away, however, I'm still stuck in that loop.
Does anyone know how to solve this cluster****? How do I get it to boot into system?
Edit: Managed to flash LIneage new after wiping data and system and it actually boots, hallelujah, but when I flash the back up I'm still at square one with the same fail and it fails to boot. )

Categories

Resources