Related
Hi
this is my first post, apologies if I'm going about things the wrong way. I've searched the forum and Google for the problem I'm experiencing but the hits I get back are for specific error and processes. My problem is this:
Flashing to Aurora or Runnymede results in my phone throwing up "the process android com.process.xxxx has stopped unexpectedly, please try again", they vary with HTC and Google errors. I get a lot of these errors (phone, camera, media etc) and then a blank HTC whitescreen. I get signal, however if I unlock my screen the errors pop up - I cannot do anything on my phone at all.
My device is S-OFF. I've successfully flashed MIUI and Cyanogenmod many times without error, and they work without a hitch. I've a feeling that with these Sense roms I'm missing some pre-installation procedure of which I simply cannot find what. What do i need to do to get either of these ROMS working?
Thanks for the help!
Edit: I have installed an app that moved certain items to the SD card that were taking up space on the internal memory. Not sure if this has anything to do with it?
DeciMA said:
Edit: I have installed an app that moved certain items to the SD card that were taking up space on the internal memory. Not sure if this has anything to do with it?
Click to expand...
Click to collapse
It probably is your problem. The roms you tried has some kind of apps2sd implementation already check the rom thread. Technically you don't have to use any app that move your apps to SD.
I will try that out tomorrow when I have some time.
NOw that I've restored my miui backup, I have noticed that same error pops up when the phone loads and I have to run the App, then the errors disappear. I'll post back tomorrow with my efforts!
Out of curiosity, what's the name of that app you are using to move apps to sd?
Root All to Data2SD (cant post links). I'm finding it difficult to move all the items back to the internal memory.
Just from the description of the app, it seems that it will screw up the set up.
Start fresh. Backup all your apps using Titanium Backup. Copy and save all the contents of your sd to a computer. I suggest you zip the titanium backup folder on your sd before transferring it to your computer, I often get errors about the filenames inside the folder being too long with Windows7 if they are unzipped.
Repartition your sd card with fat32 and ext4 or ext3 (depending on the rom requirement)
Put your files back to the SD card and unzip the titanium backup folder as well.
Flash the rom and restore your apps using titanium backup. Do the app restore by batches. The apps should be moved to the ext partition automatically. Check the rom thread for details on the apps2sd implementation they used. Some require to flash another zip after the initial boot. Just check the thread.
DeciMA said:
I've a feeling that with these Sense roms I'm missing some pre-installation procedure of which I simply cannot find what. What do i need to do to get either of these ROMS working?
Click to expand...
Click to collapse
Just curious, did you perform full wipe before flashing your new ROM/s??
777ace said:
Just curious, did you perform full wipe before flashing your new ROM/s??
Click to expand...
Click to collapse
Pretty sure I did, which is why this is baffling me. I would've thought that flashing a new rom would replace all pre-existing required applications
To confirm, in Recovery its Wipe Data/Factory Reset?
Performing a full wipe before flashing has worked! I can get into these ROMs now finally! Thanks for the help!
I feel like an idiot
Nice.
I had the same issues many months back. I was going from LeeDROiD Froyo ROM to InsertCoin GB. No matter how many times I flashed, I got same results as you. Then someone aksed "did you full wipe"?
After that, no more problems!!
I've been very frustrated lately, and I don't want to go and do something like unroot and clear my
phone without "professional" input. So thanks for your attention.
I have been running albinoman's Jellybean RC3 since it's release. It's been working well for me
but I wanted to try the new MIUI 2.11.9 for my Incredible.
I downloaded and tried installing it through ROM Manager; I wiped the data, cache, and dalvik cache.
It got to the part where it was installing MIUI, then:
Code:
Creating symlinks
symlink: some symlinks failed
E:Error in /somedirectory/blahblah/somezipfile.zip
(Status 7)
Installation aborted.
So I cursed it and restored my JB backup.
Then it said something like this in the final part of the restore:
Code:
Restoring sd-ext...
No sd-ext found. Skipping backup of sd-ext
sd-ext won't mount and isn't visible in cmrecovery. But oddly enough, all of my files can be found in Astro, under sdcard1.
When I booted up, I got the immediate messages that apps like Talk, Email,
and Exchange Services had stopped working. So I disabled them to stop the messages. Facebook wouldn't start, and
ANY app that deals with media fails to load, i.e. Instagram, Camera, Music, Gallery, etc.
(EDIT: Recently I got Google Play to download apps after Fixing Permissions in cmrecovery)
I tried the re-downloading and re-installation of MIUI, and even a fresh RC3, all in CMrecovery, w/ and w/out wipes.
I would've let the failed install go, but it's too frustrating not being able to access my media.
Please Help
Hypherism said:
I've been very frustrated lately, and I don't want to go and do something like unroot and clear my
phone without "professional" input. So thanks for your attention.
I have been running albinoman's Jellybean RC3 since it's release. It's been working well for me
but I wanted to try the new MIUI 2.11.9 for my Incredible.
I downloaded and tried installing it through ROM Manager; I wiped the data, cache, and dalvik cache.
It got to the part where it was installing MIUI, then:
Code:
Creating symlinks
symlink: some symlinks failed
E:Error in /somedirectory/blahblah/somezipfile.zip
(Status 7)
Installation aborted.
So I cursed it and restored my JB backup.
Then it said something like this in the final part of the restore:
Code:
Restoring sd-ext...
No sd-ext found. Skipping backup of sd-ext
sd-ext won't mount and isn't visible in cmrecovery. But oddly enough, all of my files can be found in Astro, under sdcard1.
When I booted up, I got the immediate messages that apps like Talk, Email,
and Exchange Services had stopped working. So I disabled them to stop the messages. Facebook wouldn't start, and
ANY app that deals with media fails to load, i.e. Instagram, Camera, Music, Gallery, etc.
(EDIT: Recently I got Google Play to download apps after Fixing Permissions in cmrecovery)
I tried the re-downloading and re-installation of MIUI, and even a fresh RC3, all in CMrecovery, w/ and w/out wipes.
I would've let the failed install go, but it's too frustrating not being able to access my media.
Please Help
Click to expand...
Click to collapse
Status 7 refers to an error in the rom zip file. Try redownloading it and flashing it again. If it still errors, go to the roms thread and see if others are having the same issue. I no one else has the issue, try flashing TWRP recovery and then flashing the rom with it. Seems some newer roms work better with twrp than with cwm.
The sd-ext thing is normal. You will only have an sd-ext if you specificaly partitioned your sdcard to have one. If you dont have one, cwm will still check and report its backup status, ie "backing up/restoring sd-ext, no sd-ext found, skipping backup/restore of sd-ext".
So are you saying you cant flash any rom or restore a backup without having fc's and app issues?
cmlusco said:
Status 7 refers to an error in the rom zip file. Try redownloading it and flashing it again. If it still errors, go to the roms thread and see if others are having the same issue. I no one else has the issue, try flashing TWRP recovery and then flashing the rom with it. Seems some newer roms work better with twrp than with cwm.
The sd-ext thing is normal. You will only have an sd-ext if you specificaly partitioned your sdcard to have one. If you dont have one, cwm will still check and report its backup status, ie "backing up/restoring sd-ext, no sd-ext found, skipping backup/restore of sd-ext".
So are you saying you cant flash any rom or restore a backup without having fc's and app issues?
Click to expand...
Click to collapse
Thanks cmlusco, for posting.
I just downloaded a fresh .zip of miui for inc off their site, then transferred and installed it all while in TWRP recovery. I got the same Status 7
error, and had to restore my my newest JB backup.
Yes. I can't install new roms, even a fresh jellybean rc3. When I restore, it works, but I still have app issues, and I frequently recieve this error:
"Unfortunately, the process android.process.media has stopped"
Hypherism said:
Thanks cmlusco, for posting.
I just downloaded a fresh .zip of miui for inc off their site, then transferred and installed it all while in TWRP recovery. I got the same Status 7
error, and had to restore my my newest JB backup.
Yes. I can't install new roms, even a fresh jellybean rc3. When I restore, it works, but I still have app issues, and I frequently recieve this error:
"Unfortunately, the process android.process.media has stopped"
Click to expand...
Click to collapse
It must be an error in the rom file then, probably in the updater script. If you shoot me a link i will download it and see if i can get it to work.
Try formating everything in the mounts and storage menu except emmc and sdcard, and then do your restore. Sometimes wiping just data and cache arent enough.
I tried flashing it, and also got status 7. Gonna take a look and see if i can fix it.
cmlusco said:
It must be an error in the rom file then, probably in the updater script. If you shoot me a link i will download it and see if i can get it to work.
Try formating everything in the mounts and storage menu except emmc and sdcard, and then do your restore. Sometimes wiping just data and cache arent enough.
Click to expand...
Click to collapse
Yeah. Formatted everything in the wipe menu of TWRP except sd and emmc. Tried and failed to install the ROM with the same error.
Restored. Then re-installed cmrecovery to check by formatting in it's mounts and storage menu, but I got the same result.
Let me know how your install goes. I have a bad feeling it isn't the rom file.
Hypherism said:
Yeah. Formatted everything in the wipe menu of TWRP except sd and emmc. Tried and failed to install the ROM with the same error.
Restored. Then re-installed cmrecovery to check by formatting in it's mounts and storage menu, but I got the same result.
Let me know how your install goes. I have a bad feeling it isn't the rom file.
Click to expand...
Click to collapse
After messing with this for a few hrs im sad to say i give up. It has multipul errors, every time i fix one a new one pops up. The updater-script had numerous errors and the system folder is missing a bunch of files.
cmlusco said:
After messing with this for a few hrs im sad to say i give up. It has multipul errors, every time i fix one a new one pops up. The updater-script had numerous errors and the system folder is missing a bunch of files.
Click to expand...
Click to collapse
Thanks for spending time to assist me regardless. I'll figure something out. Though I'm open to anyone else that might some insight or
information regarding this issue.
It's beyond frustrating to me.
Well, fixed all my problems. I just installed Tiny's cm 10. Everything seems golden. Camera's working, gallery's available.:good:
Thanks for narrowing the problem down to the ROM, I know you put some time into that.
Resolved,
Hypherism
Using TWRP 2.6.3.0, I'm unable to wipe data. Every time I try, I get
"wiping data without wiping /data/media
E: error opening '/data/lost+found'
done."
I excluded the nonessential bits, if anyone wants a full log (something something partition details), I can make one.
I using ES File Explorer with root explorer on, I checked out /data and found two lost+found folders, which I think is causing my issue. I've tried deleting just one, but a second one is automatically generated. If I delete them both, then they're automatically recreated as well. If I delete them both and then remake one immediately after, another one will be remade.
I also checked the rest of the /data folder, and I did not find any lost+found files, so I'm pretty sure it's just the folders messing things up
I checked this thread, but I didn't find anything useful
http://forum.xda-developers.com/showthread.php?p=39497772
I ended up here after I accidentally wiped my internal storage with TWRP. I went from a 4.3 AOSP rom to 4.1.2 stock (HD RLS16). I wiped the 4.3 rom, but I think I accidentally wiped internal storage then as well, or maybe something was messed up with TWRP because the storage folder for 4.3 isn't in data/media (or at least not for the rom I was using). After that I used hyperdrive, which was super buggy with Gapps and didn't work at all. After adding an account, everything kept force closing, and things were extremely slow and took minutes to open, even after removing the account and wiping cache+dalvik.
I thought it had to do with the rom, so I went and wiped stuff, then went to CM 10.1.3 stable, but that didn't boot at all, so I tried wiping again and going to liquidsmooth 2.9, which is where my problems started again. I attempted to wipe again and go back to cm10.1.3. The wipe failed, but cm10.1.3 worked.
any ideas on how I can fix this? I was unable to find help on google.
xxkid123 said:
Using TWRP 2.6.3.0, I'm unable to wipe data. Every time I try, I get
"wiping data without wiping /data/media
E: error opening '/data/lost+found'
done."
I excluded the nonessential bits, if anyone wants a full log (something something partition details), I can make one.
I using ES File Explorer with root explorer on, I checked out /data and found two lost+found folders, which I think is causing my issue. I've tried deleting just one, but a second one is automatically generated. If I delete them both, then they're automatically recreated as well. If I delete them both and then remake one immediately after, another one will be remade.
I also checked the rest of the /data folder, and I did not find any lost+found files, so I'm pretty sure it's just the folders messing things up
I checked this thread, but I didn't find anything useful
http://forum.xda-developers.com/showthread.php?p=39497772
I ended up here after I accidentally wiped my internal storage with TWRP. I went from a 4.3 AOSP rom to 4.1.2 stock (HD RLS16). I wiped the 4.3 rom, but I think I accidentally wiped internal storage then as well, or maybe something was messed up with TWRP because the storage folder for 4.3 isn't in data/media (or at least not for the rom I was using). After that I used hyperdrive, which was super buggy with Gapps and didn't work at all. After adding an account, everything kept force closing, and things were extremely slow and took minutes to open, even after removing the account and wiping cache+dalvik.
I thought it had to do with the rom, so I went and wiped stuff, then went to CM 10.1.3 stable, but that didn't boot at all, so I tried wiping again and going to liquidsmooth 2.9, which is where my problems started again. I attempted to wipe again and go back to cm10.1.3. The wipe failed, but cm10.1.3 worked.
any ideas on how I can fix this? I was unable to find help on google.
Click to expand...
Click to collapse
I would flash back to stock in Odin and root again
xxkid123 said:
Using TWRP 2.6.3.0, I'm unable to wipe data. Every time I try, I get
"wiping data without wiping /data/media
E: error opening '/data/lost+found'
done."
I excluded the nonessential bits, if anyone wants a full log (something something partition details), I can make one.
I using ES File Explorer with root explorer on, I checked out /data and found two lost+found folders, which I think is causing my issue. I've tried deleting just one, but a second one is automatically generated. If I delete them both, then they're automatically recreated as well. If I delete them both and then remake one immediately after, another one will be remade.
I also checked the rest of the /data folder, and I did not find any lost+found files, so I'm pretty sure it's just the folders messing things up
I checked this thread, but I didn't find anything useful
http://forum.xda-developers.com/showthread.php?p=39497772
I ended up here after I accidentally wiped my internal storage with TWRP. I went from a 4.3 AOSP rom to 4.1.2 stock (HD RLS16). I wiped the 4.3 rom, but I think I accidentally wiped internal storage then as well, or maybe something was messed up with TWRP because the storage folder for 4.3 isn't in data/media (or at least not for the rom I was using). After that I used hyperdrive, which was super buggy with Gapps and didn't work at all. After adding an account, everything kept force closing, and things were extremely slow and took minutes to open, even after removing the account and wiping cache+dalvik.
I thought it had to do with the rom, so I went and wiped stuff, then went to CM 10.1.3 stable, but that didn't boot at all, so I tried wiping again and going to liquidsmooth 2.9, which is where my problems started again. I attempted to wipe again and go back to cm10.1.3. The wipe failed, but cm10.1.3 worked.
any ideas on how I can fix this? I was unable to find help on google.
Click to expand...
Click to collapse
Anytime you get that error format data (the one where you type yes) the folder gets corrupted and a format fixes it.
Sent from my SGH-I747 using xda app-developers app
Im getting the same E:Error opening '/data/lost+found' im my twrp 2.6.3.1 after flashing Official CM11 nightly dec 12.
So now my recovery is very messed up, i cant properly wipe or restore nandroid with ease anymore, did you by any chance find a solution to fixing this issue?
Mystikalrush said:
Im getting the same E:Error opening '/data/lost+found' im my twrp 2.6.3.1 after flashing Official CM11 nightly dec 12.
So now my recovery is very messed up, i cant properly wipe or restore nandroid with ease anymore, did you by any chance find a solution to fixing this issue?
Click to expand...
Click to collapse
This has happened to me twice and the only solution i have found was to wipe internal storage. unfortunately i wasnt able to backup my internal storage before wiping so eveything i had on my phone was erased. Everything in your external is safe you dont have to worry but if you had important files or anything that you wouldnt erase on your internal storage then that is very unfortunate.
As for me, i now backup everything maybe like once a month or so, just in case something like this happens again.
Its happened to me also and I could not resolve it without the wipe, that was the only viable solution that worked for me.
Sent from my SGH-I747M using Tapatalk
Although if you're using twrp I just found out you can still save some of your precious files.
How? Simple
You can go into recovery and into the file manager. I think it's in settings or advanced I'm not sure. But I know that is built into twrp. So then just go into your internal storage and select the files and move them to the external storage.
If it's your first time using the file manager then you'll have to get used to it because it's not 100% noob friendly
And remember the bigger the file the longer it'll take to move so just be patient.
Use AromaFM!
search bar will serve you..
KorGuy123 said:
Anytime you get that error format data (the one where you type yes) the folder gets corrupted and a format fixes it.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thank you very much, saved my life today!
Can i get some help please. I cant format data via TWRP, it says "E: unable to wipe data, unknow fle system, auto, unable to format to remove encryption". I did not put any encryption. What to do?
Have you tried using different versions of TWRP to wipe?
I originally installed Lollipop on my phone on 5/14 using Santod's Stock Rooted ROM. A couple of days later I reverted back to my NANDROID backup of Kit Kat. Yesterday I reflashed Santod's Lollipop ROM and now I'm "missing" several directories on my internal storage/SDCard and some files have older time stamps.
I know the "missing" directories are actually there because when I try to copy the files back to the phone I get an error message stating that the files already exist and then the copy fails with an error.
I'm using Root Explorer and have selected to show all hidden files.
Is this some strange permissions issue? Should I just reflash to Lollipop and then wipe the internal storage and recopy everything?
Any help and/or insights are greatly appreciated.
Try the fix from the following post: http://forum.xda-developers.com/showpost.php?p=57288835&postcount=2
Thanks for the link, jabrown84, I'll give it a try.
What's strange is that the files are missing while viewing on the phone and on the PC. However if I revert back to Kit Kat or use the File Manager from within TWRP I can see everything.
I may just wipe the entire phone (including internal storage). A deep cleaning never hurt anyone before.
Worked like a charm!
I'm trying to figure out why my new backed up in TWRP backups are no longer working. My SystemUI.apk is malfunctioning after a 2nd boot it will say that the SystemUI has crashed and you can report it or click ok. The first boot seems fine but the taskbar and software buttons are missing. I don't know what it is. I've looked through logcat and couldn't figure it. Can anyone help? I don't know where to begin to troubleshoot.
https://pastebin.com/raw/Q5sPQdda
XML: https://pastebin.com/WG5Ccucx
I will pay someone to fix this for me: https://drive.google.com/file/d/1mQ8x3B2WBqvayFbuYXpD3_JWAjlviEJF/view?usp=sharing
TWRP restore of a standard MOB30X backup ends with "extractTarFork() process ended with ERROR: 255". The backup is larger than the original size because symlinked files are copied multiple times, taking up extra space on an already tightly filled system partition. System is 100% used when the error happens...
Click to expand...
Click to collapse
Nexus 7'13 Stock ROM factory image MOB30X issues and solutions
SUMMARY TWRP restore fails with MOB30X backup. You need either repartitioning or the following storage space script. I use LineageOS but recently had to install the latest stock ROM due to the development of Restock app. I noticed two...
forum.xda-developers.com
If you have found no solution and have nothing to lose, try sysrepart and then hopefully you may be able to restore your backup.