Related
Apparently no one else is having this issue so it's gotta have something to do with what I'm doing, and I can't figure it out. My problem is that when I press download ROM in ROM manager, the only manifests it retrieves are the all device ones, which only include the two superuser binaries. It doesn't actually download or display the espresso manifests. I checked my build.prop to make sure everything said espresso, not something else, and it does. There was ONE thing that said htc_espresso, but no one else is having the issue so it can't be my build.prop. I have a premium license, and advanced mode is enabled, and there are no options in the settings menu to set the manifests manually. Erghhh. Anyone have any suggestions? I don't see why it just doesn't show up for me. I just did a full wipe before I flashed cm7 RC1 last night, so it can't be that.
Edit: figured out part of the problem. Apparently, it relies on you actually installing clockwork recovery, which I have avoided doing, one, because I have my cache bind mounted to data, so when it tries to flash update.zip from /cache/download, it fails, and my roms don't install, and two, I use cw3, and it's permanently flashed. So I have just been manually overriding the installation, which is why it doesn't show rom downloads. Any workaround to this, or some way to put the cw3 img into a zip?
Edit 2; solution: Took some hoop jumping and a LOT of tedious nandroiding and such, but I finally got it to work. In the end, I had to raise my cache from 1.5 mb to 2.5 mb and push the update.zip for 2.5.0.7 recovery to /cache, while in recovery (can't do it while booted, since /cache is just bound to /data/cache, hence the whole issue in the first place). So, when you reboot into recovery from rom manager, yes, it still copies an update.zip to what it THINKS is /cache, but is actually /data/cache, but it doesn't matter since I've already pushed a pre-existing update.zip to the REAL /cache (partition scheme is now 140 mb /system and 2.5 mb /cache, only 1mb of /data lost)
Ultimately, the issue with no downloads was that I had overridden the installation of clockworkmod recovery, so ROM manager showed for the version as clockwork unknown, which I guess meant unknown device as well. Once I installed cw recovery via rom manager, downloads began appearing again. I re-fastboot flashed cw2 over cw3, since it was causing compatibility issues with ROM Manager. If anyone is going to try this solution however, make a nandroid, it corrupted my entire internal storage and I had to restart without a nandroid, redoing mtd and everything. Thank god for titanium backups, eh?
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
All right, first thing first. Thanks to everybody for this amazing forum and all support.
Well. Here's my story:
1) Planned on installing CM10 nightly
2) Went to recovery (TWRP v2.2.0) and by mistake wiped everything :/ (Cache, Dalvik Cache, Factory Reset, System Internal Storage)
3) In effect i wiped everything including system.
4) Still have access to TWRP and download mode.
Does anybody have a clue how to fix that and install CM10 again?
PS.
1) internal storage does not mount under system (WIN7)
2) TWRP does not recognize microSDXC (32gbz) formated to either exFat or NTFS. (Tried 4 (four) of them)
Should i buy another micro sd like 2gb, format it to Fat32 and drop CM.zip there ? Or need i do something else?
Very respectfully.
That happened to me I just downloaded the rom to a sd card from my old phone put it in my s3 and installed it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Hey thank you for quick answer. Do you know if there is any limitation for TWRP? It does not read my 32gb MicroSDXC.
Go into download mode and re flash then stock rooted rom.
Then install your twrp and try cm again.
Sent from my SGH-I747M using xda app-developers app
Personally, I would (try to?) use adb with the phone booted into TWRP to transfer the ROM you want to flash over to the phone's internal storage, and go from there.
If that's not a possibility for whatever reason, you'd be best off starting by reflashing a stock rooted image with Odin and going from there.
Well. First of all thank you all for all your help in support. Got it back to stock with root (Odin flash). However there is another small problem that i can't figure out. TWRP itself seem not to have access to anything. I mean it sees all / but after openning /sdcard or anything else all it sees is empty folders. It doesn't have an access to external sd either (when you check log it sees that it couldn't mount ext sd correctly [even if after boot to stock system it recognizes it witout any issues).
Any idea how to solve this problem? What has been tried:
1) Reflash recovery (TWRP 2.2 using ODIN)
2) moving all files to /
3) RootExplorer see files (cm.zip) after reboot TWRP doesn't
4) Installing GooManager (it crashes after granting supersu permissions)
Very Respectfully.
With all those problems, flash to stock rooted and start over. You will be better off in the long run. You may want to also format your external sd.
Don't flash twrp with Odin.
Rooted stock
Dl and use goo manager to get twrp
What about a stock kernel? Just my chime in
Sent from my SAMSUNG-SGH-I317 using xda premium
Allright small update.
1) ReFlashed to rooted stock (root66_ATT_I747UCDLK3.tar.md5)
2) Installed GooManager
3) Installed TWRP (using GooManager)
4) Downloaded lastest CM10 nightly (cm-10.1-20121218-NIGHTLY-d2att.zip) using GooManager
5) Flashed cm-10.1-20121218-NIGHTLY-d2att.zip from GooManager menu (FlashROM) - Wiped Dalvik & Cache
Now I'm stacked with CM boot splash for past 5 min hoping it just takes longer that it should.
Any ideas?
Very Respectfully.
EDIT:
Booting into recovery and performing factory reset fixes problem.
Thanks to everybody who helped.
widofmaker said:
Allright small update.
1) ReFlashed to rooted stock (root66_ATT_I747UCDLK3.tar.md5)
2) Installed GooManager
3) Installed TWRP (using GooManager)
4) Downloaded lastest CM10 nightly (cm-10.1-20121218-NIGHTLY-d2att.zip) using GooManager
5) Flashed cm-10.1-20121218-NIGHTLY-d2att.zip from GooManager menu (FlashROM) - Wiped Dalvik & Cache
Now I'm stacked with CM boot splash for past 5 min hoping it just takes longer that it should.
Any ideas?
Very Respectfully.
EDIT:
Booting into recovery and performing factory reset fixes problem.
Thanks to everybody who helped.
Click to expand...
Click to collapse
GJ take it sure and slow. Other than flashing stock/rooting form Odin I wouldn't flash anything form Odin. Once you have super user on your phone, leave Odin out and do everything from phone
That's the safest route and it gets easier from here. The countless hours you spent are much easier the more you do it. Shouldn't take more than 20 minute to backup and flash roms and new apps from now on
Oh boy.
Almost done. But here are another tiny problems that just bother me and but I think they're solvable.
1) GooglePlay suddenly gives "No Connection" error, even though every other app that requires connection (Messenger, Browser) work just fine.
Have to mention that it worked for a while, installed couple apps (drop some more to install in queue and when I woke up - FAIL!)
Things done:
-Forced to stop
-ClearedData & Cache
Is there any other solution to fix it rather than reflashing gapps ?
2) The ExternalSD is mounted under PC as Internal Storage and vice versa.
When you click "Samsung -GHS-I747) in my computer it shows both with proper sizes but once you click them it opens the other.
No clue how to solve that one.
Very respectfully.
widofmaker said:
Oh boy.
Almost done. But here are another tiny problems that just bother me and but I think they're solvable.
1) GooglePlay suddenly gives "No Connection" error, even though every other app that requires connection (Messenger, Browser) work just fine.
Have to mention that it worked for a while, installed couple apps (drop some more to install in queue and when I woke up - FAIL!)
Things done:
-Forced to stop
-ClearedData & Cache
Is there any other solution to fix it rather than reflashing gapps ?
2) The ExternalSD is mounted under PC as Internal Storage and vice versa.
When you click "Samsung -GHS-I747) in my computer it shows both with proper sizes but once you click them it opens the other.
No clue how to solve that one.
Very respectfully.
Click to expand...
Click to collapse
1. you are flashing a version of gapps that is out of touch with your rom or you did not flash it correctly/cleanly. I remember no matter how many times I flashed gapps I wouldn't get it to sync. Backed all user apps to Titanium backup. Did a clean install from scratch, and wallah it worked. Last sort.
Without doing that though there is usually one that is compatible that is listed on your rom page. Flash that one. For me that is 10/22 but I remember it giving that same error for a while so I ended up flashing the previously compatible version before that which was 7/26. Goo.im might help here, I haven't used it myself. Once you find a working gapps version etc. Store your 'safe' builds in one folder
2. Not sure what you mean. When you click your phone you should see internal and external storage on your phone. They are what they say they are. People tend to piss on not being able to find the right file size and folder attributes on this phones usb mount. It is a common problem. Probably one of the few problems on the phone. Annoying but manageable
zetsui said:
2. Not sure what you mean. When you click your phone you should see internal and external storage on your phone. They are what they say they are. People tend to piss on not being able to find the right file size and folder attributes on this phones usb mount. It is a common problem. Probably one of the few problems on the phone. Annoying but manageable
Click to expand...
Click to collapse
1) Ended up reflashing gapps with goomanger (script to TWRP)
2) What i mean is that under phone it recognizes them perfectly. Just when I connect phone through USB to PC, my PC tends to mix them up. Just shows ExSD as Internal and Internal as ExSD. No biggy, just tried to fix as many tiny issues as possible before I hit deployment.
Very respectfully.
That is a known, and stated, issue with cm 10.1
Hi,
my G3 and me have a small problem.
I wanted to update from official Cyanogenmod 12.1 to 13.0, backed up my data, etc.
First, there were tno Problems, but very fast battery drainage, and that my mSD card was now not "sdcard1" anymore but some numbers.
I tried fixing permissions in TWRP, had a bootloop. Updated TWRP (now 3.0.0 installed) and it worked somehow.
After one night it said process.acore quit unexpectedly. I had some crashes of the Google Play Services as well.
Then, it would boot, give me like 10 Seconds, and then jump to the boot screen of Cyanogenmod.
I tried to wipe data,system,dalvik. First there were problems with wiping dalvik, then there were problems with wiping system.
It says can't mount system: invalid argument. When looking around with twrp file explorer, the system folder is empty.
I would really appreciate your help!
You must check the partition type. Check if this as Ext4 or f2fs. In any case, try to repair the system of partitions from TWRP.
Okay, so:
Filesystem of /system is ext4
When trying to fix:
Repairing System using ef2fsck....
/sbin/e2fsck -fp /dev/block/mmcblk0p40 process ended with ERROR: 8
Unable to repair file system.
I assume it's because its ext4 and not f2fs?
btw I found something that may be important: when I try to wipe /cache, it takes forever.
Codagon said:
Okay, so:
Filesystem of /system is ext4
When trying to fix:
Repairing System using ef2fsck....
/sbin/e2fsck -fp /dev/block/mmcblk0p40 process ended with ERROR: 8
Unable to repair file system.
I assume it's because its ext4 and not f2fs?
btw I found something that may be important: when I try to wipe /cache, it takes forever.
Click to expand...
Click to collapse
Try to reinstall cyanogedmon 12.1 without wipes. Then, you enter again to the recovery and apply the wipes. I am not sure if for our model, cyanogedmon is compatible with the type of partitions f2fs and if is required a kernel with support for f2fs file system. You could try to changing the partitions (file system to f2fs), installing the rom and see if it starts but could cause a boot loop. Make a nandroid before making any changes.
cesarandres_8911 said:
Try to reinstall cyanogedmon 12.1 without wipes. Then, you enter again to the recovery and apply the wipes. I am not sure if for our model, cyanogedmon is compatible with the type of partitions f2fs and if is required a kernel with support for f2fs file system. You could try to changing the partitions (file system to f2fs), installing the rom and see if it starts but could cause a boot loop. Make a nandroid before making any changes.
Click to expand...
Click to collapse
Okay, i will try this tomorrow and then report back!
Thank you so far
Okay,
when trying to install the latest Snapshot of official CM, it just says ZIP File is corrupt. It said the same about an older build I still had on my PC.
When I try to flash the CM 13.0 build i had previously, TWRP just goes black and reboots (into recovery).
I also have to manually mount /system every time. If I try to mount /system again after dismounting it, it says 'failed to mount /system : Invalid Argument' .
This applies to all other partitions but the external SD Card.
When I try to change the file system to f2fs, it says OPeration successfull, but it didn't change anything, and the file system keeps being displayed as ext4.
Furthermore, i can't just 'Reboot Recovery' with TWRP- I have to take ot the Battery every time.
Codagon said:
Okay,
when trying to install the latest Snapshot of official CM, it just says ZIP File is corrupt. It said the same about an older build I still had on my PC.
When I try to flash the CM 13.0 build i had previously, TWRP just goes black and reboots (into recovery).
I also have to manually mount /system every time. If I try to mount /system again after dismounting it, it says 'failed to mount /system : Invalid Argument' .
This applies to all other partitions but the external SD Card.
When I try to change the file system to f2fs, it says OPeration successfull, but it didn't change anything, and the file system keeps being displayed as ext4.
Furthermore, i can't just 'Reboot Recovery' with TWRP- I have to take ot the Battery every time.
Click to expand...
Click to collapse
Why dont you start from the beginning.flash lp kdz through lg up then try installing cm 13.it might work for you.
jokerpappu said:
Why dont you start from the beginning.flash lp kdz through lg up then try installing cm 13.it might work for you.
Click to expand...
Click to collapse
I didn't want to lose my files
But it seems this is the only way soon- TWRP is giving me Error 7 when trying to flash CM 13.0. ....
:crying:
Codagon said:
I didn't want to lose my files
But it seems this is the only way soon- TWRP is giving me Error 7 when trying to flash CM 13.0. ....
:crying:
Click to expand...
Click to collapse
Which is your recovery version? If your recovery version is 3.0, you could try performing a downgrade of your recovery. If the errors persist, make an clean installation of the rom from LG Flash Tool (KDZ).
cesarandres_8911 said:
Which is your recovery version? If your recovery version is 3.0, you could try performing a downgrade of your recovery. If the errors persist, make an clean installation of the rom from LG Flash Tool (KDZ).
Click to expand...
Click to collapse
My Version is indeed 3.0. I had 2.8 before. Should I downgrade even further?
What would you recommend?
Besides:
I tried saving my files with the Terminal and [cp * /data/data/media/ /external_sd/Backup -r] and others, but it keeps giving me Zero-Byte Files.
Is this due to the Recovery version too?
You guys really are a big help! Thanks!
Codagon said:
My Version is indeed 3.0. I had 2.8 before. Should I downgrade even further?
What would you recommend?
Besides:
I tried saving my files with the Terminal and [cp * /data/data/media/ /external_sd/Backup -r] and others, but it keeps giving me Zero-Byte Files.
Is this due to the Recovery version too?
You guys really are a big help! Thanks!
Click to expand...
Click to collapse
I think that you try to save an empty folder. Use any backup applications to accomplish this. I have installed recovery twrp version 3 and I have no problem.
cesarandres_8911 said:
I think that you try to save an empty folder. Use any backup applications to accomplish this. I have installed recovery twrp version 3 and I have no problem.
Click to expand...
Click to collapse
Ok but doing it woth cp * /sdcard/WhatsApp it keeps doing the same.
The only thing that matters to me now are my WhatsApp Images
I was able to grab the chatlogs but not more.
Sometimes it even copies all pictures (Like 8.000 files) but all of them are 0-Bytes.
I will try the downgrade tomorrow.
Thank you so far!
Were you able to resolve this? I have an identical issue. I was playing CoC on my LS990 with CM13 before it went black and now it always boots in to twrp recovery 3.0. The only thing that mounts is the external sd card.
I've tried the following and all fail:
adb push cm13 and then install from recovery
adb sideload cm13
lg flash tool via firmware upgrade, roms:ZV4, ZV6, ZV8
Is the internal sd damaged? Please help XDA gods. Thanks
Hi Everyone
You'll probably guess from what I'm about to say that I should have researched better, but here is where I am, and hopefully, you can help. I was trying to upgrade my Moto G6 Play XT1922-9 to LineageOS 18.1. I was able to install TWRP, but I kept getting an error bad key and couldn't load data folder or wipe it. So after doing a bit of searching, I came across a fix that ultimately bricked my device, no-verity-opt-encrypt zip. Now even when I go into Recovery mode, I can't wipe to factory default. I tried loading the lineageOS 18.1 unofficial, but it says the zip failed verification; I've tried downloading it multiple times from different browsers to no avail, and I load it off of an SD Card as ADB sideload doesn't work. Any suggestions for help would be great as I am plum out of ideas.
So I ended up reloading the stock rom with the app Rescue_and_Smart_Assistant_v6.2.1.9_prod_setup from Motorola in Windows, kinda hoped there was a Linux version but it didn't work under Wine, so needed to get virtual box in on the action. I guess at least I'm back to square one and can try and get TWRP running again, oh well
was able to reload TWRP and then only able to load LineageOS 18.1 Lite, ended up wiping advanced the data folder to ext2fs and back to ext4 for it to work, including load Mind the Gapps
The strange thing, though was that it only loaded the arm Mapps, not arm64, and lineageOS Lite 18.1 rotation isn't working correctly, and only sound comes out the headphones, not speakers, tried it with PixelOS 2.1 got the same problems, tried loading the full version of LineageOS 18.1 but it kept rebooting and trying to run Decrypt in TWRP got the builds off of Telegram
everything works fine with the stock ROM
now any version of TWRP I use won't allow me to change the filesystem to ext2 and then back to ext4 so I can wipe the /data folder, not sure what I'm doing differently or if the many rebuilds I've made of the original ROM is choking the device
i got it working again, not sure if it was because I wiped my stock build with TWRP and then rebooted back into the stock or because I changed the file system to ext2 then back to ext4fs and then formated and checked to see if it was mounted from the command line or what but I was able to flash lineage lite with mapps arm64
I also got the sound working thanks to
ianos21​with his telegram suggestion, to copy
mixer_paths.xml
audio_platform_info.xml
although I didn't know that TWRP had a file manager and was able to copy the files to the vendor/etc folder from my sd card
now I just need to figure out what's up with the rotation and sometimes the keyboard wonks out
now the vendor/etc folder is missing from multiple ROMs, I just don't get it??!?! how is this happening, I can't tell if I'm having a memento moment or if it's my phone? Has anyone ever had that problem? as in the folders suddenly disappear?