I was one of the ones with problems with trying to restore nandroids and wiping data. I got stuck going from vicious JB v1 to V2 then back to v1. Somehow, after attempting to restore numerous nandroids of ICS and my nandroid of V1 I somehow got it to boot.
Now, I've noticed that whenever I boot into recovery if I go to "mounts and storage" I see cache is mounted. I can unmount it and make a nandroid. Then if I go back to "mounts and storage" I see data is mounted and wont unmount so when trying to restore a nandroid it hangs at the data part.
He is what I do that has been working for me.
Once in recovery, I go to mounts and storage and unmount cache. Make a nandroid. Go back to mounts and storage and see data is mounted and won't unmount. I then go to "advanced" and select reboot recovery. Once it reboots into recovery I go back to mounts and storage and see that data is unmounted. I then can restore a nandroid. I've done this successfully going from vicious v3 to BAMF v2 then back to vicous v3.
I just wanted to share this and hope it helps someone.
Thanks
Ddaaaaammmnnnn......I really wish I would have seen this earlier. Blew my phone up just to get it working again. Thanks for the info. I will know what to do next time.
Sent from my Galaxy Nexus using xda app-developers app
Sorry, left out a step. After returning to recovery and finding data unmounted, I can then wipe data, system, and cache. I believe data is again mounted so go to advanced and reboot recovery again, go to mounts and storage and make sure everything is unmounted then restore your nandroid or install a new ROM.
I'm using CWM touch by the way.
Sent from my DROID RAZR using xda app-developers app
If you have adb access when in recovery, see if you can run the following and have /data unmount
Code:
umount -l /data
You'll need to be root, and if you're already in the mounts and storage screen, you'll need to go back one, and then select mounts and storage again for it to refresh. Could be something is still being accessed when it attempts to unmount /data causing the issues.
imnuts said:
If you have adb access when in recovery, see if you can run the following and have /data unmount
Code:
umount -l /data
You'll need to be root, and if you're already in the mounts and storage screen, you'll need to go back one, and then select mounts and storage again for it to refresh. Could be something is still being accessed when it attempts to unmount /data causing the issues.
Click to expand...
Click to collapse
I've finally got Vicious v3 set up to the way I like. I'll try that next time. Maybe somebody else will see this post and try it if they are stuck.
It's strange, I've flashed many ROMs in CWM touch with ICS with no issues. I saw one post where someone believed it had to do with a new "storage" folder that is created in JB. If you use a file explorer you'll see a "storage" folder and inside it it is linked to the sdcard.
Should cache be mounted when I first boot into recovery? I've never noticed that before but I haven't had a need to check until now.
Thanks for your response.
guide based on your post
hobby31 said:
I was one of the ones with problems with trying to restore nandroids and wiping data. I got stuck going from vicious JB v1 to V2 then back to v1. Somehow, after attempting to restore numerous nandroids of ICS and my nandroid of V1 I somehow got it to boot.
Now, I've noticed that whenever I boot into recovery if I go to "mounts and storage" I see cache is mounted. I can unmount it and make a nandroid. Then if I go back to "mounts and storage" I see data is mounted and wont unmount so when trying to restore a nandroid it hangs at the data part.
He is what I do that has been working for me.
Once in recovery, I go to mounts and storage and unmount cache. Make a nandroid. Go back to mounts and storage and see data is mounted and won't unmount. I then go to "advanced" and select reboot recovery. Once it reboots into recovery I go back to mounts and storage and see that data is unmounted. I then can restore a nandroid. I've done this successfully going from vicious v3 to BAMF v2 then back to vicous v3.
I just wanted to share this and hope it helps someone.
Thanks
Click to expand...
Click to collapse
Based on your post and some testing, I made a guide for people... kind of a step by step thing. Let me know if this captures the jist of your experience. http://forum.xda-developers.com/showthread.php?t=1749322
Thanks I was totally baffled yesterday when I did a full wipe and reflashed the rom only to find that my phone booted normally and all my apps and data were there. Whats the deal with getting stuck on the google screen though? Does it just take a long time? I needed my phone for work last night and couldnt wait, which is why I tried flashing a nandroid...
Step by Step
How to restore a Nandroid or flash new ROM with CWM Touch
In CWM Touch Recovery
1. Go to mounts and storage and unmount cache.
2. Make a nandroid. (Going back to mounts and storage, you will see data is mounted and will not unmount.)
3. Go to "advanced" and select reboot recovery.
4. Once phone reboots into recovery, go back to mounts and storage and see that data is unmounted. You may now wipe data, system, and cache.
5. You may now restore a nandroid or flash a new rom.
If this helped you, hit thanks. Also, thank hobby31.
Confirmed working going from vicious v1, back to a 4.04 nandroid.
Sent from my Galaxy Nexus using xda app-developers app
I have been having a similar issue
I have tried several of the JB roms, and haven't found one that will let me reboot the phone. Every one get to the google screen and never past, and I ended up having to flash the stock rom before I can get anywhere. Anyone else having this issue or found a fix?
richiewrt said:
I have tried several of the JB roms, and haven't found one that will let me reboot the phone. Every one get to the google screen and never past, and I ended up having to flash the stock rom before I can get anywhere. Anyone else having this issue or found a fix?
Click to expand...
Click to collapse
If it is what was happening to me and a few others it has something to do with the data not unmounting in CWM. I went through all the boot looping, stuck on the google screen, battery pulls and pulling my hair out. After some digging I noticed that data would not unmount in CWM so when I rebooted I quess it would hang somewhere while trying to load data. Essentially, when I was wiping data in CWM it looked like it was doing something but really wasn't.
My fix is what is in this post. Basically, going to "advanced" in CWM and "reboot recovery" usually unmounts the data then you can wipe it. Then reboot recovery again as it seems to get stuck mounted again after wiping. Then reboot the phone after making sure nothing is mounting in "Mounts and storage".
hobby31 said:
I was one of the ones with problems with trying to restore nandroids and wiping data. I got stuck going from vicious JB v1 to V2 then back to v1. Somehow, after attempting to restore numerous nandroids of ICS and my nandroid of V1 I somehow got it to boot.
Now, I've noticed that whenever I boot into recovery if I go to "mounts and storage" I see cache is mounted. I can unmount it and make a nandroid. Then if I go back to "mounts and storage" I see data is mounted and wont unmount so when trying to restore a nandroid it hangs at the data part.
He is what I do that has been working for me.
Once in recovery, I go to mounts and storage and unmount cache. Make a nandroid. Go back to mounts and storage and see data is mounted and won't unmount. I then go to "advanced" and select reboot recovery. Once it reboots into recovery I go back to mounts and storage and see that data is unmounted. I then can restore a nandroid. I've done this successfully going from vicious v3 to BAMF v2 then back to vicous v3.
I just wanted to share this and hope it helps someone.
Thanks
Click to expand...
Click to collapse
Had a similar issue but my system was not mounted, remount system and I could restore nandroid.
Sent from my Galaxy Nexus using xda app-developers app
Don't use touch cwm; use normal cwm
Sent from my i9250
bk201doesntexist said:
Don't use touch cwm; use normal cwm
Sent from my i9250
Click to expand...
Click to collapse
Not necessarily. I have tried both TWRP and CWM, and even CWM normal, and I am still screwed. Everytime I try to restore, I get an error restoring /data. Looks like I may be going back to stock.... This whole JB thing has made my Nexus feel like a Droid Bionic! :crying:
EDIT: Used the Gnex Toolkit, got back to stock, rooted and recovery installed and right back to AOKP 40. I think I will wait until this gets ironed out. Bit more work than I would like to crack flash. :laugh:
Thanks for this!
Related
I have some sort of sd-ext error when restoring a nandroid backup. At the moment my phone is stuck at the cyanogen boot loop. I've wiped everything, i tried to format the sd-ext but it will not mount. i've tried fresh installs, everything I can think of but nothing seems to be working.
sd-ext error is normal, that's actually referring to the partition where you would install apps2sd, I get that error all the time because I don't have any as well and no need to have that partition.
In ClockworkMod Recovery, the sd card is just called "sdcard"
SynbiosVyse said:
sd-ext error is normal, that's actually referring to the partition where you would install apps2sd, I get that error all the time because I don't have any as well and no need to have that partition.
In ClockworkMod Recovery, the sd card is just called "sdcard"
Click to expand...
Click to collapse
Okay. So how do I go about getting my phone operational again? As I said i've wiped everything and tried to restore backups and did fresh installs and still am stuck at the looping boot screen.
You're using clockwork mod recovery right? Format your sd card using Windows to FAT32.
Boot into recovery..format all your other partitions. Mount USB storage, put a ROM in there, try stock Virtuous seems to be more stable than CM.
Clear data/factory reset, clear cache, then clear Dalvik cache. Install Virtuous .zip.
You should be able to boot. If you still can't try taking unmounting the sd card after the ROM finishes installing, try taking it out as well.
SynbiosVyse said:
You're using clockwork mod recovery right? Format your sd card using Windows to FAT32.
Boot into recovery..format all your other partitions. Mount USB storage, put a ROM in there, try stock Virtuous seems to be more stable than CM.
Clear data/factory reset, clear cache, then clear Dalvik cache. Install Virtuous .zip.
You should be able to boot. If you still can't try taking unmounting the sd card after the ROM finishes installing, try taking it out as well.
Click to expand...
Click to collapse
I got this error trying to install Virtious:
E:Can't chown/mod /data/app
(Operation not permitted)
E:Failure at line 8:
set_perm_recursive 1000 1000 0771 0644 DATA:app
Installation Aborted.
Click to expand...
Click to collapse
I successfully installed the MIUI ROM however it doesn't even get to the boot screen. It stays on the white background HTC Incredible screen.
I saw this guy had a similar problem:
http://androidforums.com/incredible-all-things-root/181337-backup-problems-ud-cm6.html
He said that Cyanogen Mod seemed to be better for him. But he was also clearing data/cache and Dalvik AFTER he installed the mod.
It's ok to do that after, but you better make sure to do it before. Have you tried clearing both before and after? If it gets stuck on the white incredible screen I am not sure, but if it goes beyond that and then crashes right before the boot is finalized then that might be an SD card problem.
SynbiosVyse said:
I saw this guy had a similar problem:
http://androidforums.com/incredible-all-things-root/181337-backup-problems-ud-cm6.html
He said that Cyanogen Mod seemed to be better for him. But he was also clearing data/cache and Dalvik AFTER he installed the mod.
It's ok to do that after, but you better make sure to do it before. Have you tried clearing both before and after? If it gets stuck on the white incredible screen I am not sure, but if it goes beyond that and then crashes right before the boot is finalized then that might be an SD card problem.
Click to expand...
Click to collapse
Yes i've tried before and after. With cyanogen it loops the boot screen, with MIUI that I installed it doesn't get past the white screen and i cannot install virtuous at all
Anyone? I'd really like to be able to save $300 here
last loop i had with cyanogen was because i had the wrong kernel. make sure u flash a kernel that supports asop. its simple but it slips minds alot i usually use kings kernels (#2)
akawings said:
last loop i had with cyanogen was because i had the wrong kernel. make sure u flash a kernel that supports asop. its simple but it slips minds alot i usually use kings kernels (#2)
Click to expand...
Click to collapse
ive tried kings and ziggy's aosp
The phone is totally screwed up, it wont even accept unrooting and putting the stock ROM back onto it. I have *NO* idea what happened. I just got this phone replaced and did a restore and it was working fine, then it froze so i removed the battery and put it back in and then this.
http://androidforums.com/incredible...16-how-revert-back-earlier-version-hboot.html
try using that to unroot, itll take you back to 2.1 (or you could use a different ruu for whatever version youd like to revert to)
Fixed! I went out and bought a new class 6 SD card and used berserkers method to go back to stock. Thank all of you for your help!
Been having a few problems with random rebooting on my EVO. I had been using Sprint Lovers Rom since Jan. Haven't had any issues. I recently decided to try Calkulin's EViO 3 v1.0 Beta 2. Which I'm really liking as well.
But my phone has been randomly rebooting.Most times it reboots and will not boot back to main screen without me having to pull the battery , reboot into recovery and reinstall the rom. When get the phone to boot back to the main menu, it reboots at least 3 or 4 more times. I usually have to reboot into recovery, then wipe cache, dalvik, and data again in order to stop the reboots for awhile.
So I wiped everything again and used a nandroid backup to go back to SprintLovers rom. Will I had the same rebooting issues with that too, which I never had before. So I'm beginning to think I have a issue with the bootloader. I had started another thread in the wrong forum and someone suggested wiping the SD-EXT Partition of my memory card since I'm using Apps2SD. Problem is I don't have SD-EXT partition. I tried mounting it and formatting it. I keep getting a error message saying 'path volume sd-ext invalid".
Any ideas to stop this random rebooting to stop?
Using Clockwork Recovery if that matters.
Download the PC36IMG.zip file for amon_RA from HERE and flash from the bootloader screen. Afterwards, go into the wipe menu and wipe cache & dalvik and then make a nandroid backup of your current setup. Afterwards, go back to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card and then flash the rom you want to use. By the way, the sd-ext is listed in the wipe menu.
posting & replying via the XDA Premium app.
dougjamal said:
Download the PC36IMG.zip file for amon_RA from HERE and flash from the bootloader screen. Afterwards, go into the wipe menu and wipe cache & dalvik and then make a nandroid backup of your current setup. Afterwards, go back to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card and then flash the rom you want to use. By the way, the sd-ext is listed in the wipe menu.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Thanks for the reply. How is the sd-ext partition created? is it automatically created by App2SD?
shaun0207 said:
Thanks for the reply. How is the sd-ext partition created? is it automatically created by App2SD?
Click to expand...
Click to collapse
Yes. I never use A2SD because I've never even been close to running out of space, and read/write speed is faster on internal memory.
Hope wiping solves your problem
(from... Evo/MIUI/Tapatalk)
My phone was working fine until I upgraded two apps (I can't recall which ones) and my phone rebooted on its own; weird. I am running CM7 BTW.
I figured "No problem, I'll just flash my backup through Clockworkmod; not so. I keep getting "error formatting /data" regardless of any wipe, format I do.
I am not sure what to do from here. Please help. Searching revealed some RUU advice, but those were in other phone forums and I want to make sure I don't screw this up.
evil_elf said:
My phone was working fine until I upgraded two apps (I can't recall which ones) and my phone rebooted on its own; weird. I am running CM7 BTW.
I figured "No problem, I'll just flash my backup through Clockworkmod; not so. I keep getting "error formatting /data" regardless of any wipe, format I do.
I am not sure what to do from here. Please help. Searching revealed some RUU advice, but those were in other phone forums and I want to make sure I don't screw this up.
Click to expand...
Click to collapse
What version of cwm are you using?
Sent From My Optimized HTC Incredibly Dinc
It was the orange, but I upgraded it to see if it would work. uh, oh, as I write this, I fear worse...
Upgrading changed cwm to blue, but still same problems. It is almost as if the data directory has no write permissions.
I got impatient and used the ruu.exe from pvillecomp and now it gets stuck at the red eye droid screen and is on a reboot loop.
I can't get into recovery now, I get the phone icon with the red ! triangle. I figure cwm is gone now, so what, use unrevoked again? This would flash a new recovery, correct? Otherwise, how would I get the zip file onto the sd card now to flash via hboot? Even with a cwm, I imagine I will have the same formatting issues, unless the rom upate utility corrected those.
evil_elf said:
My phone was working fine until I upgraded two apps (I can't recall which ones) and my phone rebooted on its own; weird. I am running CM7 BTW.
I figured "No problem, I'll just flash my backup through Clockworkmod; not so. I keep getting "error formatting /data" regardless of any wipe, format I do.
I am not sure what to do from here. Please help. Searching revealed some RUU advice, but those were in other phone forums and I want to make sure I don't screw this up.
Click to expand...
Click to collapse
Try manually mounting /data before wiping it.
EDIT: Nevermind just read your other post about loosing cw recovery. Are you still s-off?
yeah, I tried every combination of mounting and formatting and it always failed with the same message. I am still S-off, so I imagine from here I can use unrevoked to flash cwm back onto it then I can try to restore from a saved ROM I have on my card. Should I do that?
I could copy the file to flash cwm file to my card instead I guess, but my card would have to be FAT32 I assume.
Well I flashed ClockworkMod 5.0.2.0 using HBOOT and now I am back to my original problem: Error while formatting /data! I can mount /data, but not format it, even through the mount menu option. Any ideas?
I don't know much about the file structure but does this not seem like a permissions issue to you guys? Fix permissions in CWM and factory resets don't help either.
evil_elf said:
Well I flashed ClockworkMod 5.0.2.0 using HBOOT and now I am back to my original problem: Error while formatting /data! I can mount /data, but not format it, even through the mount menu option. Any ideas?
I don't know much about the file structure but does this not seem like a permissions issue to you guys? Fix permissions in CWM and factory resets don't help either.
Click to expand...
Click to collapse
Do you have a ext2/3/4 partition on your sdcard?
cmlusco said:
Do you have a ext2/3/4 partition on your sdcard?
Click to expand...
Click to collapse
By partition, do mean directories? I formatted the card to FAT32 but did not partition it in any way. I don't believe I had separate partitions on it before, but I could be wrong. Wouldn't the partitions have shown up in my Windows OS when I plugged the card in to the reader?
evil_elf said:
Well I flashed ClockworkMod 5.0.2.0 using HBOOT and now I am back to my original problem: Error while formatting /data! I can mount /data, but not format it, even through the mount menu option. Any ideas?
I don't know much about the file structure but does this not seem like a permissions issue to you guys? Fix permissions in CWM and factory resets don't help either.
Click to expand...
Click to collapse
factory reset in hboot is different. It will probably wipe programming so you'll have to *228 1 and *228 2 to yet reprogram your phone. It'll probably wipe sdcard and emmc too. I've not tried so this is at your own risk. see if there are better options first.
Sent from my ADR6300 using Tapatalk
tiny4579 said:
factory reset in hboot is different. It will probably wipe programming so you'll have to *228 1 and *228 2 to yet reprogram your phone. It'll probably wipe sdcard and emmc too. I've not tried so this is at your own risk. see if there are better options first.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
I've already tried it before. It did not touch my card but did reset my phone's programming.
The restore function in CWM only touches the internal memory, correct?
evil_elf said:
By partition, do mean directories? If so, yes. I formatted the card to FAT32 but did not partition it in any way. I don't believe I had separate partitions on it before, but I could be wrong. Wouldn't the partitions have shown up in my Windows OS when I plugged the card in to the reader?
Click to expand...
Click to collapse
No windows would not see it if its there you would need to use a program called "gparted" on your pc to get rid of it or reformat it. Also when you tried the factory reset from hboot were you on a stock recovery then or cwm?
cmlusco said:
No windows would not see it if its there you would need to use a program called "gparted" on your pc to get rid of it or reformat it. Also when you tried the factory reset from hboot were you on a stock recovery then or cwm?
Click to expand...
Click to collapse
I tried the Factory Reset from HBOOT and also the Wipe Data/Factory Reset from CWM. Occasionally I am getting the 5 vibrations and a black screen when trying to turn off and on; battery pull allows me to boot up into ROM or HBOOT.
CM7 is working now, but the hard button bindings are screwed up along with a bunch of other stuff. CWM is able to restore the system, but fails on data so it makes sense. I can't receive calls either. I was so hoping the ruu would have fixed this...
The card should have no bearing on flashing a ROM? Or am I not understanding this?
Oh, I also tried to restore and format data manually without the card in to no avail. The Wipe Data/Factory Reset formats the data folder without errors but not the manually method of formatting or the restore method.
Could this help? http://forum.xda-developers.com/showthread.php?p=18287267
Just tried this: http://forum.xda-developers.com/showthread.php?t=1006556
Still same error.
To return my phone under warranty to a Verizon store, do I need to make sure that the stock ROM is flashed and the phone is unrooted with S-ON again? I am starting to think this is the route I am heading down and I only have a week left on my warranty.
Very short answer.........YES!!!
A kind soul helping me at http://forum.cyanogenmod.com/topic/32272-error-formatting-data-when-restoring/
*Possible Solution* If still an issue
If it is still an issue I had the same problem with my incredible.
I was playing a racing game on my phone and it just restarted on its own. When I turned it back on the phone had reset itself. Every time I would restart the phone from then on it would delete every thing I had saved like it was doing a factory reset. So I tried to do a wipe and restore and no luck. I kept getting the same errors you were getting in clockwork. I also tried the e2fsck commands from the link in the prior post and no luck.
1. I got a working HTC Incredible and booted into recovery and mounted all partitions.(/system, /data, etc.)
2. Then I used adb to pull the filesystem from the working phone with this command.
c:\android\adb pull / filesystem
This puts all the files from the phones root folder into a folder named filesystem in the same directory as the adb files.
3. After that finished I hooked the phone with the messed up partitions to the computer, booted into recovery, and mounted all partitions.
4. Then I used adb to push the filesystem from the working Incredible to the Incredible with the messed up partitions with this command.
c:\android\adb push c:\android\filesystem /
5. When it finished I rebooted the phone. It booted up and I got a few force close errors but nothing major, so I restarted and booted into recovery. When I tried to format /data it formatted like it should have.
6. Finally I downloaded the stock+ rooted rom and flashed it with clockwork and the phone booted up fine with no force closes and doesn't reset after reboot.
This worked for me and should work for anyone else that has this filesystem problem.
Can i get those files?
i dont have a working incredible. can you post a link to the working filesystem.
Thanks.
androidi1 said:
If it is still an issue I had the same problem with my incredible.
I was playing a racing game on my phone and it just restarted on its own. When I turned it back on the phone had reset itself. Every time I would restart the phone from then on it would delete every thing I had saved like it was doing a factory reset. So I tried to do a wipe and restore and no luck. I kept getting the same errors you were getting in clockwork. I also tried the e2fsck commands from the link in the prior post and no luck.
1. I got a working HTC Incredible and booted into recovery and mounted all partitions.(/system, /data, etc.)
2. Then I used adb to pull the filesystem from the working phone with this command.
c:\android\adb pull / filesystem
This puts all the files from the phones root folder into a folder named filesystem in the same directory as the adb files.
3. After that finished I hooked the phone with the messed up partitions to the computer, booted into recovery, and mounted all partitions.
4. Then I used adb to push the filesystem from the working Incredible to the Incredible with the messed up partitions with this command.
c:\android\adb push c:\android\filesystem /
5. When it finished I rebooted the phone. It booted up and I got a few force close errors but nothing major, so I restarted and booted into recovery. When I tried to format /data it formatted like it should have.
6. Finally I downloaded the stock+ rooted rom and flashed it with clockwork and the phone booted up fine with no force closes and doesn't reset after reboot.
This worked for me and should work for anyone else that has this filesystem problem.
Click to expand...
Click to collapse
Here try this one http://dinc.does-it.net/Touch_of_Blue/filesystem.zip, im interested to see if this works for you too. It seems quite a few people have been having issues with /data latley.
I get error
Code:
push: filesystem/sys/devices/platform/android_pmem.0/power/wakeup -> /sys/devices/platform/android_pmem.0/power/wakeup
failed to copy 'filesystem/sys/devices/platform/android_pmem.0/power/wakeup' to '/sys/devices/platform/android_pmem.0/power/wakeup': Operation not permitted
i get this error trying to push the filesystem. any workaround?
Running MIUI, AmonRa. Phone was totally stable, today I was charging it and it refused to turn on. Pulled battery and when I turn on, its stuck on white htc Evo screen.
I can boot to recovery and see my old nandroid's and make a new one. I can S-OFF in recovery. Restoring the nandroid doesn't seem to help, its still stuck on white boot screen.
A few things to try:
1)Reboot to bootloader and select fastboot and reboot... have had this work before...
or
2)In recovery wipe everything then restore your nandroid.
or
3)Have a copy of the MIUI version you were on? In recovery, wipe system, then flash the ROM
LG optimus LTE WON"T BOOT
My Phone won't boot after try to install CWM. The touch buttons flash couples sec after press power but phone won't turn on. When i plugged in the computer, the computer recognize it but can't do restore. HELP PLEASE!!!
Ok I managed to debug this a little bit more.
Can get to recovery, but trying to restore nandroid's failed. I did this after wiping everything, doing a factory reset, and it still fails. When I tried to mount each partition individually, it failed to mount sd-ext with the error "can't mount /dev/block/mmcblk0p2 (File exists)".
I think this was the key, as I was using dta2sd on all my roms. Luckily I had another rom which was not using sd-ext, and I was able to restore that.
Is my sd-ext partition now lost? I can't check its status using the rom I have since it doesn't support sd-ext. Obviously all my apps were installed on it and I'd like to back them up.
The sd card itself seems fine, I can see everything on it.
I was actually going to post about this, thanks for doing it for me man.
Even with sense roms just restarting the phone will get me stuck at the htc evo 4g white screen and I have to wipe all data and factor reset just to get it to boot up again but i loose all my stuff and it really sucks. My phone only has recently started doing this, any ideas on what I can do to fix it?
I tried what imhereoldman said, but that just fixes it till the next time where it does the same thing after restarting the phone and im really getting tired of it :/
---------- Post added at 03:30 AM ---------- Previous post was at 03:17 AM ----------
ECrispy said:
Ok I managed to debug this a little bit more.
Can get to recovery, but trying to restore nandroid's failed. I did this after wiping everything, doing a factory reset, and it still fails. When I tried to mount each partition individually, it failed to mount sd-ext with the error "can't mount /dev/block/mmcblk0p2 (File exists)".
I think this was the key, as I was using dta2sd on all my roms. Luckily I had another rom which was not using sd-ext, and I was able to restore that.
Is my sd-ext partition now lost? I can't check its status using the rom I have since it doesn't support sd-ext. Obviously all my apps were installed on it and I'd like to back them up.
The sd card itself seems fine, I can see everything on it.
Click to expand...
Click to collapse
I just found this and it sounds like it will be a pain but should solve the issue trying it out now and il let you know how the unroot reroot goes...
You don't have to unroot. Just run the RUU for your phone.
Also, try to do a backup of your SD Card, reformat it (Sorry if you don't have a TB backup), repartition, then restore the backup and reflash the ROM after a thorough and complete wipe.
Thanks hipkat, I should have done more research on it, I did the un-root to. But I did run the RUU file and switched to AMON this time and it seems everything is cleared up and its running fine! thanks
Okay so today I tried to flash Inspirekat v2.1 rom on my galaxy tab 3 via latest TWRP, and after I wipe system, data, dalvik cache and cache I reboot into the system and I can't get passed the samsung galaxy tab 3 splash screen after some time I found out that the problem is the unability to mount the /system file, then I tried CWM and still the same thing.
Unfortunately I didn't make a backup because I didn't have any precious data there so I just thought I would skip that, I've also tried formatting all data on internal storage but with no avail...could anyone light up a candle for me?
shokolata said:
Okay so today I tried to flash Inspirekat v2.1 rom on my galaxy tab 3 via latest TWRP, and after I wipe system, data, dalvik cache and cache I reboot into the system and I can't get passed the samsung galaxy tab 3 splash screen after some time I found out that the problem is the unability to mount the /system file, then I tried CWM and still the same thing.
Unfortunately I didn't make a backup because I didn't have any precious data there so I just thought I would skip that, I've also tried formatting all data on internal storage but with no avail...could anyone light up a candle for me?
Click to expand...
Click to collapse
If you wiped "system" after you flashed, then you no longer have a rom installed. Re-flash the rom.
Sent from my SM-G920V using Tapatalk
gr8nole said:
If you wiped "system" after you flashed, then you no longer have a rom installed. Re-flash the rom.
Sent from my SM-G920V using Tapatalk
Click to expand...
Click to collapse
Sorry I messed it up a bit in my previous post, I didn't wipe system "after" I flash but before I flashed
Every time I try to flash it just takes a minute then I reboot into the system; same thing happens then I get back into recovery to see that the /system is unmounted and can't be mounted back also when I try "repair partition" it shows that only 54mb of /system partition is used and around 1300mb is free, any insight on that?
Some errors about not being able to read storage file context and can't find path to /sdcard also appear sometimes on the log window or however it's called at the top right.
shokolata said:
Sorry I messed it up a bit in my previous post, I didn't wipe system "after" I flash but before I flashed
Every time I try to flash it just takes a minute then I reboot into the system; same thing happens then I get back into recovery to see that the /system is unmounted and can't be mounted back also when I try "repair partition" it shows that only 54mb of /system partition is used and around 1300mb is free, any insight on that?
Some errors about not being able to read storage file context and can't find path to /sdcard also appear sometimes on the log window or however it's called at the top right.
Click to expand...
Click to collapse
TWRP does have some issues mounting system sometimes.
Once you boot into recovery, choose the reboot recovery option and try the flash sgain.
Sent from my SM-G920V using Tapatalk
gr8nole said:
TWRP does have some issues mounting system sometimes.
Once you boot into recovery, choose the reboot recovery option and try the flash sgain.
Sent from my SM-G920V using Tapatalk
Click to expand...
Click to collapse
After trying different combinations of wiping and repairing and also changing partition type IT WORKED, freaking nice.
Thanks for your support!