Related
I tried flashing the Rom yesterday and was successful. The issues I had revolve around restoring my apps. I used My Backup Root for stock to Froyo, but this time it seemed as though the apps were on the phone and the card, which cause an error stating that I didn't have enough memory. What should I have done to restore the apps to preserve the memory? I also received force close error for SetCPU, SlideIt (which I love), and a few others.
Also, what is the benefit of partitioning my sd card and does doing so erase it's current contents?
Lastly, are the nightlies a full rom or just part that needs to be flashed? If found some on CMs website, but not here.?
Yes, I'm a NOOB.
kabell4 said:
I tried flashing the Rom yesterday and was successful. The issues I had revolve around restoring my apps. I used My Backup Root for stock to Froyo, but this time it seemed as though the apps were on the phone and the card, which cause an error stating that I didn't have enough memory. What should I have done to restore the apps to preserve the memory? I also received force close error for SetCPU, SlideIt (which I love), and a few others.
Also, what is the benefit of partitioning my sd card and does doing so erase it's current contents?
Lastly, are the nightlies a full rom or just part that needs to be flashed? If found some on CMs website, but not here.?
Yes, I'm a NOOB.
Click to expand...
Click to collapse
Regarding your nightly question, they are full ROMs...the difference between them is the code that was committed within the previous 24 hours. Of course that also means that, in theory, some of the nightlies could be 100% the same...anyway, the nightlies can be a beautiful thing or a disasterous thing...usually if there's an issue with a nightly it is quickly found by those who flash each nightly and it is brought up around 3.2 million times and it is typically fixed by the next nightly.
Partitioning usually does mean a wipe of data on the SD. Careful!
When I upgraded to a 32GB flash from the stock 2GB from my Aria, I backed up the entire contents and restored on the new one. Apparently there is volume information stored somewhere (not sure where) and the phone couldn't recognize the card and asked me to partition it.
Because I had a backup, I decided to do so, but instead of partitioning for the entire size of the chip, it partitioned only 2GB!
So I had to stick it into a reader and repartition it manually and then selectively restore music, etc back on the card.
After that it worked just fine. So short version: yes it does.
kabell4 said:
I tried flashing the Rom yesterday and was successful. The issues I had revolve around restoring my apps. I used My Backup Root for stock to Froyo, but this time it seemed as though the apps were on the phone and the card, which cause an error stating that I didn't have enough memory. What should I have done to restore the apps to preserve the memory? I also received force close error for SetCPU, SlideIt (which I love), and a few others.
Also, what is the benefit of partitioning my sd card and does doing so erase it's current contents?
Lastly, are the nightlies a full rom or just part that needs to be flashed? If found some on CMs website, but not here.?
Yes, I'm a NOOB.
Click to expand...
Click to collapse
You will need to creaate an sd-ext partition to fix the issue of installing (larger) apps with CM7.
The best way would be through ROM Manager.
wifi
Installed the RC2 and can't connect to a hidden SSID wifi network.
That is a known issue with the wifi driver on cm7 thus far. Not sure if it will be corrected though. Anyone else know if it is in the works?
"Do you mind if I turn up the AC?"
I believe if you flash to nightly 14 all will be good, not 100% sure though.
TheFurnace said:
That is a known issue with the wifi driver on cm7 thus far. Not sure if it will be corrected though. Anyone else know if it is in the works?
"Do you mind if I turn up the AC?"
Click to expand...
Click to collapse
As far as I know there are no plans to change it. But then again we weren't supposed to get fm radio working either...
Sent from my cm7 Aria using XDA App
Too true. Never know what is coming down the pipeline!
"Do you mind if I turn up the AC?"
stellarhopper said:
You will need to creaate an sd-ext partition to fix the issue of installing (larger) apps with CM7.
The best way would be through ROM Manager.
Click to expand...
Click to collapse
Great input from everyone. Thanks! Following up on the sd-card partitioning... I have a new 8g card and want to more to CM7. If I partition it, what happens when I restore the backed up app using My Backup Root? And, what is the best partition configuration, why, and what info get store in each section (ext)?
Thanks...
kabell4 said:
Great input from everyone. Thanks! Following up on the sd-card partitioning... I have a new 8g card and want to more to CM7. If I partition it, what happens when I restore the backed up app using My Backup Root? And, what is the best partition configuration, why, and what info get store in each section (ext)?
Thanks...
Click to expand...
Click to collapse
The easiest way to partition is using your ROM manager.
Just select the max size for SD-EXT (I think it would got to 512MB), and none for swap.
I'm not sure if this would have any effect on your backup - I myself started out from scratch and got my apps from the market even though I had made an Astro backup...
You will store all your stuff - music, pictures etc in the normal partition. The SD-EXT will be automatically handled by the phone.
Tried flashing Nightly 22 on my Aria from 17. I spent a lot of time customizing 17. Is there a way to keep all of the old home screens? Also, GPS lock isn't working for me. Using MyBackup Root for Apps, but it seems to duplicate the apps?
kabell4 said:
Tried flashing Nightly 22 on my Aria from 17. I spent a lot of time customizing 17. Is there a way to keep all of the old home screens? Also, GPS lock isn't working for me. Using MyBackup Root for Apps, but it seems to duplicate the apps?
Click to expand...
Click to collapse
You should be able to flash each new nightly without losing any of your settings/customizations/homescreens and apps.
While upgrading from ROM manager, just check the backup option, don't check wipe data and cache.
I can confirm this works transitioning from 14 to 22 because I just did it yesterday night
As for the GPS problem, thats a known issue - the workaround is to make a nandroid backup of your current cm7, then do a complete phone reset, then do a nandroid restore of cm6 or 6.1 (hope you have one), do another factory reset, and restore your cm7 from the backup you took in the 1st step
stellarhopper said:
You should be able to flash each new nightly without losing any of your settings/customizations/homescreens and apps.
While upgrading from ROM manager, just check the backup option, don't check wipe data and cache.
I can confirm this works transitioning from 14 to 22 because I just did it yesterday night
As for the GPS problem, thats a known issue - the workaround is to make a nandroid backup of your current cm7, then do a complete phone reset, then do a nandroid restore of cm6 or 6.1 (hope you have one), do another factory reset, and restore your cm7 from the backup you took in the 1st step
Click to expand...
Click to collapse
first of all, i would never suggest using rom manager for things such as that. historically it has only caused problems and has been more of an inconvenience than anything. second of all, when you boot into CWM and do it the right way, don't wipe data, it's suggested but not necessary that you wipe cache and dalvik, then flash the rom and you'll be good.
Thanks to both of you. Big help and not deleting the data did the trick. Looks like I'm good to go and GPS is working well again. Is there a way to ensure I don't have duplicate apps taking up space on the card and phone? I'm getting errors on moving some apps to the sd card.
kabell4 said:
Thanks to both of you. Big help and not deleting the data did the trick. Looks like I'm good to go and GPS is working well again. Is there a way to ensure I don't have duplicate apps taking up space on the card and phone? I'm getting errors on moving some apps to the sd card.
Click to expand...
Click to collapse
Not all apps can be moved to the FAT32 partition on the SD card. Widgets also, won't work properly if moved to the SD FAT32.
If you need more memory, look into (read up) partitioning your sd card with a ext3 partition and installing S2E or Dark Tremor a2sd (DT a2sd).
zervic said:
first of all, i would never suggest using rom manager for things such as that. historically it has only caused problems and has been more of an inconvenience than anything. second of all, when you boot into CWM and do it the right way, don't wipe data, it's suggested but not necessary that you wipe cache and dalvik, then flash the rom and you'll be good.
Click to expand...
Click to collapse
Oh, I had no idea about that, thanks for the info.
I've been using ROM manager without any problems so far, apart from one lately, that when I reboot to recovery, I always get an error screen - exclamation mark in triangle...but I just pull the battery and reboot into recovery manually and it starts whatever command I had given it (backup/new rom) automatically...
Hi, my device is running a CM10.1 nightly. After encrypting it, TWRP 2.4.2.0 is not able to decrypt the /data partition when I enter the password. So I updated to 2.5.0.0 using the Goo Manager thinking it will fix this issue. 2.5.0.0 seems to accept the password but burps a" 'unable to mount /data' message when I try to access data storage. TWRP seems to see /data as the entire size of the internal storage too. Then I flashed 2.5.0.0 with ODIN, to exclude any problems related to local installation, and still the same issue is there. From what i read TWRP should support encryption, these bugs show that there are serious issues, how would I go about reporting that to them? Also is there a way I can resolve this without tearing down this setup?
Another issue is that my file manager cannot access my /data partiton any longer. Everytime it comes up it hangs and crashes without showing any directories. Maybe this issue would go away with a firmware update but I can't get that going because of the issue above.
you can also try CWM touch recovery if that doesn't work. just flash it from odin and install another custom rom. good luck.
-------------------------------------
please let me know if i'm wrong and CLICK thanks if i help
SRIRAM
sent from my GT-I9300 running CM10.1 RC4.4 by Temasek
Do you have a similar setup to mine I want to confirm that this is a general bug rather than an issue with mine specifically. If you are anyone else let me know I'd appreciate it. From what I have researched CWM does not support encryption so it would be a non-starter.
For last couple of days, Google play services has been throwing up an error dialogue on my phone that it has stopped with OK and Report Button Although there doesn't seem any downside for it, except for its annoyance that I have to click OK , the error comes up randomly. For hours it might not come but it can also come up many times in an hour. Screenshot of what is contained in crash report is attached
Anyway, first I thought my ROM had corrupted. So, I wiped everything and re-installed a new ROM. However, the error didn't go away, again it will come up randomly. So I thought it was due to f2fs format since I had formatted /data, /data/media and /cache partitions to f2fs using arter97's recovery (I was using his kernel also). So I formatted them back to ext4, also changed my recovery back to philz's and installed stock CM rom. But again the error started coming
So I thought maybe it was due to I had been restoring apps via Titanium Backup which is causing the issue. So I stopped restoring apps, however It didn't work either, I was still getting the error. I started flashing many different ROMs (CM, omni, aosp, custom touchwiz) , gapps combination's (banks, 0day PA, others), factory resetting 10s of times, using MegaWipe script to format everything, removing the memory card permanently, however the error is still coming.
So in the end, I flashed stock samsung 4.3 ROM via ODIN and did a factory reset, however the error is still coming
I don't know what else to do ? Is my phone NAND corrupted ? Is there any test I can do to make sure ?
Please suggest..
First my setup: I've a RN3 SE (Kate) and I installed de developer MIUI, did an unofficial unlock, flashed twrp and installed lineageos (first official version), root package and pico gapps. That's it. I used Titanium backup to restore some of my apps data, but I installed every apk via the play store.
I started to notice that some apps were disappearing after a reboot. Everything I'll lose between 5-10 apps, mostly the apps that were updated very recently. After installing the missing apps back, I didn't loose anything, all settings of the app are intact. I've no idea if this happens because of the Google Backup and Restore function of Android itself, or because that app data never were missing.
I've installed every update of LineageOS, but no luck, every time it'll lose some apps. Even some apps stop working after a reboot until I reinstall them. It's getting annoying, therefore I start this thread.
Anyone faced this problem and has any idea what's happening?
Bump
Try a fresh install
I'll try that in the coming days, but this is already the second clean install i did. Both with this issue.
Use this app and check your phone:
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=en
If there are errors after a full scan, you have a problem with your flash memory.
Did you wipe and format internal storage through TWRP before installing LOS?
I think i just think that this is the begining symptoms of the emmc_brick bug i recommend u to check for any disk errors.
Thanks for the tips, luckily the test came out just fine ("Congratulations. Test Passed. 159s. 31268536320 bytes (29.1GB) 190.2MB/s"). No emmc errors and I didn't have any problems on 6.0.1, it started on 7.1.1. I think it has to do with the new ART and JIT compilers, as it only happens with apps that got updated recently.
Before installing LOS, I did a wipe of system, cache and data. I don't think I did a complete format of internal storage as well.
Hi together,
i have an problem with the tablet encryption.
i wanna swap from xiaomi.eu to another more actual custom rom..
i tried PixelExperience , Havoc-OS, dotOS, ArrowOs .. and everytime i activate the encryption it's end in an bootloop regardless of pin,password,pattern ..
I'm using the latest TWRP Version
- Wipe Dalvik/ART Cache, Cache, System, Vendor, Data
- Flash from zip
- start os and enable encryption
-> bootloop
My experience with this device is limited, but I faced a similar problem switching from stock rom to an older ROM not using any encryption.
I think it was only succesful after removing encryption. Maybe it also helps in your case?!
There are many guides how to remove encryption, most of them suggest "Advanced Swipe" combined with changing the file system.
I used TWRP to swipe "data" to ext2, then again swipe "data" back to ext4 and afterwards it still needed a tap on "File System Repair" for the "system" partition. After that, the flash and boot worked for that older ROM.
Maybe that will leave you with a better starting point for activating encryption of your ROM.
(But as I wrote: Just a guess, not based on experience.)
aes32 said:
My experience with this device is limited, but I faced a similar problem switching from stock rom to an older ROM not using any encryption.
I think it was only succesful after removing encryption. Maybe it also helps in your case?!
There are many guides how to remove encryption, most of them suggest "Advanced Swipe" combined with changing the file system.
I used TWRP to swipe "data" to ext2, then again swipe "data" back to ext4 and afterwards it still needed a tap on "File System Repair" for the "system" partition. After that, the flash and boot worked for that older ROM.
Maybe that will leave you with a better starting point for activating encryption of your ROM.
(But as I wrote: Just a guess, not based on experience.)
Click to expand...
Click to collapse
Hi,
thanks for your answer. As i wrote i delete nearly everything
The OS booted, but at the point where i want to enable encryption most roms get stuck in a bootloop.
After endless roms i found carbonrom which works.. Additionally i found an post from TWRP about encryption.. i don't know if it's connected, but i guess it's an similar problem cause AOSP..
Why doesn't TWRP support encryption on my device?
Why doesn't TWRP support encryption on my device?TWRP encryption is supported in 2 phases. The first item is keeping up with the newest support from AOSP, wh...
twrp.me
So i found a working rom, but not the solution or true cause of the bootloop problem
Ok, I understand.
I guess I don't know the encryption feature well enough to help.
Found some interesting stuff to read about it, not sure if it applies to the Mi Pad 4 and its custom ROMs, though:
Any way to encrypt /data/data and /sdcard on Xiaomi EU ROM?
Hello, Xiaomi EU ROM is running decrypted, that's a security breach... Is there a way to use Xiaomi EU ROM, based on Miui 10, in a encrypted phone? Thanks
forum.xda-developers.com
So the bootloop seems to be expected and if I got it right then the fstab.qcom needs an edit at least.
Mhm it's confusing me.. cause i run nearly 5 years xiaomi.eu rom encrypted from scratch on. i think with FDE .. the rom says encrypted and twrp says encrypted and the sdcard folder is only crypted filenames.. also interesting the article.. but i'm sceptical that edit the fstab.qcom maybe work on more "normal" AOSP roms..
so i found a working rom i'm not motivated enough to try the edit xD
xXZaretXx said:
Mhm it's confusing me.. cause i run nearly 5 years xiaomi.eu rom encrypted from scratch on. i think with FDE .. the rom says encrypted and twrp says encrypted and the sdcard folder is only crypted filenames.. also interesting the article.. but i'm sceptical that edit the fstab.qcom maybe work on more "normal" AOSP roms..
so i found a working rom i'm not motivated enough to try the edit xD
Click to expand...
Click to collapse
Yes, sorry, I fully understand your point of view.
It is confusing me as well.
I'm currently experimenting with some ROM's, so yesterday I gave encryption on Havoc-OS a try - even by starting with encrypted stock rom, flashing Havoc-OS and modifying fstab.qcom - but without success. It rebooted immediately and then seemed to be hanging idle during boot for a long time.
I was not interested in encryption so far, but of course it would be great if it worked. And I should be interested for the sake of privacy.
Thanks for reporting that it works with the carbon ROM.
Edit: In Lineage OS it will probably work too, based on the description of the ROM.
I will probably try that one next, because it is also supposed to have the "split screen" feature which I am looking for.
Encryption in Lineage OS seems to work fine, as expected.
I tried to analyze Havoc OS encryption once more: It seems not to be supported at all.
It does "something" trying to encrypt... because TWRP asked for a password the next time I rebooted to recovery. Problem is, decryption in TWRP did not work with the previously given password and the data partition seemed to be messed up (file system type was "emmc", and the data partition was not responding to any of tune2fs, e2fsck or alike).
I looked at the dmesg log, it seems during the boot attempt, the system just cannot work with data any more (hence the idle hang, I assume).
There are many many log lines, showing attempts to work with data and that the system actually expects an ext4 file system for "userdata" (=mmcblk0p64):
Code:
[ 2.990548] EXT4-fs (mmcblk0p64): VFS: Can't find ext4 filesystem
[ 2.990698] EXT4-fs (mmcblk0p64): VFS: Can't find ext4 filesystem
[ 2.996651] EXT4-fs (mmcblk0p64): VFS: Can't find ext4 filesystem
[ 2.996795] EXT4-fs (mmcblk0p64): VFS: Can't find ext4 filesystem