Erase /system partition on Cyanogen Recovery - Galaxy S II Q&A, Help & Troubleshooting

First of all, this is my first post on this forum, so I'd like to say hello to everybody.
I made a bit of a mess with my father's phone (it was mine before he had it, so it was already modded), and the explanation will be somewhat long because I tried everything before coming here for help.
This phone had Android 5.1.1 Lollipop, installed through the official Cyanogenmod 12.1 Nightlies. It was working perfectly, but I wanted to install more Gapps on the /system partition and switch some of the original Cyanogenmod apps with the corresponding Google apps. I used Deltadroid's modular Gapps (Thread here: http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368) to install everything I needed on the /system partition, but I only did a factory reset+cache wipe instead of wiping the /system partition too and starting from scratch, because I couldn't find the option to wipe the /system partition in the "stock" Cyanogen Recovery. Now the phone will boot, enter recovery mode and even get to the setup screen, but as soon as the Google Play Services are needed, they crash and the setup won't go on. I tried installing the CWM but the signature check fails every time, I tried using ADB but I'm no expert and I don't know how to make it work, I tried reinstalling the ROM and wiping /data and /cache once again to no avail, I tried basically everything but it seems the only thing that can be done is wiping the /system partition and reinstalling both the ROM, the Gapps and the add-ons.
The problem is, I have no idea how to wipe the /system partition, so I was wondering if anyone here could help.
Thanks in advance.

Hi @Valtekken
You just need to have a "signed" .zip to flash through that recovery. Try the philz 6.48.4 attached here. I have heard of a few people not being able to flash this one, if it doesn't install, use the other one first, reboot to recovery, and then flash 6.48.4. So -
1. Flash the philz recovery
2. Reboot to recovery, not system
2a. (Flash the other one, reboot to recovery [if you used XWMS3 first])
3. Do your wipes(you should only need to wipe /system if you want to keep your data, but I always recommend a clean install if possible - /data, /cache, and dalvik/art cache as well)
4. Install the new CM12.1 and gapps
BTW the gapps you can flash will depend on whether or not you have repartitioned. If you have stock /system partition just install a pico or minimal gapps

noppy22 said:
Hi @Valtekken
You just need to have a "signed" .zip to flash through that recovery. Try the philz 6.48.4 attached here. I have heard of a few people not being able to flash this one, if it doesn't install, use the other one first, reboot to recovery, and then flash 6.48.4. So -
1. Flash the philz recovery
2. Reboot to recovery, not system
2a. (Flash the other one, reboot to recovery [if you used XWMS3 first])
3. Do your wipes(you should only need to wipe /system if you want to keep your data, but I always recommend a clean install if possible - /data, /cache, and dalvik/art cache as well)
4. Install the new CM12.1 and gapps
BTW the gapps you can flash will depend on whether or not you have repartitioned. If you have stock /system partition just install a pico or minimal gapps
Click to expand...
Click to collapse
First of all, thank you for answering!
I tried many "-signed" .zips, but none of them worked, so I'll assume I used non-compatible ones. There was space for the Gapps on the /system partition, mainly because I made sure of getting only the Gapps and the few addons I needed, so the MB count was very low.
I'll try your recovery right now and let you know in a moment, hopefully this solves the problem and I can have the phone working again.

Managed to install the recovery, format the /system, /data and /cache partitions, install the rom, the Gapps and the add-ons. It worked, but the phone still gives me an "Unfortunately, Google Play Services has stopped". How can I get the apps to work? What could the problem be?

I solved the problem, finally...I changed the Gapps package (I used TK's Gapps) and managed to install it and make everything work.
Thanks for all your help! I think the thread can be closed now.

Related

[Q] PARANOIDANDROID is CM9 compatible ?

Hi all,
for now I'm still on a GS2, but I am considering buying a GNote your rom and I like a lot. So I plan to install it on my S2 to go to.
A question: I am in CM9 for now, with your rom (which is based on CM9) can I do the update with the available Nightly of CM9 ?
Or maybe I did not understand (which should not wonder ) and it can not work like that?
Thank you in advance for the answer.
If you are on PARANOIDANDROID v1.0 and update to a nightly from CM9. You will then be on CM9 not PARANOIDANDROID.
Even tho it is based on CM9 it is two different things.
Updates that get put in to CM9 nightlys will be put in to PARANOIDANDROID when they want and their rom will be updated, so will there thread and the OTA updater.
To sum up, if you flash a CM9 Nightly then you will lose your PARANOIDANDROID rom.
Also make sure you use the extended steps to install a new rom.
The steps on the OP are very clear but apparently some users miss some things or can't get a properly installation so, here are the extended steps (personally i'm always use this method):
1.Reboot into recovery
2.Wipe Data / Factory Reset
3.Wipe Cache Partition
4.Install the Main ROM
5.In recovery go to Advanced
6.Wipe Dalvik Cache
7.Fix Permissions
8.Wipe Cache Partition
9.Reboot
10.If at the first boot you can't do the configuration of the google account, skip this step and continue
11.When you boot into the system, it's probably that you don't have data enabled (3g, H+) just reboot
12.When you boot again into the system the data will be enable and you can do the configuration of Google Account (if you don't do this before)
13.This is the moment for install all the extras like themes, fix's, kernels, etc.
14.Enjoy!!!
Thank's all.
Still Confused....
dwightvanbentem said:
Also make sure you use the extended steps to install a new rom.
The steps on the OP are very clear but apparently some users miss some things or can't get a properly installation so, here are the extended steps (personally i'm always use this method):
1.Reboot into recovery
2.Wipe Data / Factory Reset
3.Wipe Cache Partition
4.Install the Main ROM
5.In recovery go to Advanced
6.Wipe Dalvik Cache
7.Fix Permissions
8.Wipe Cache Partition
9.Reboot
10.If at the first boot you can't do the configuration of the google account, skip this step and continue
11.When you boot into the system, it's probably that you don't have data enabled (3g, H+) just reboot
12.When you boot again into the system the data will be enable and you can do the configuration of Google Account (if you don't do this before)
13.This is the moment for install all the extras like themes, fix's, kernels, etc.
14.Enjoy!!!
Click to expand...
Click to collapse
I have rooted my GT N7000 with Stock ICS ROM from SAMSUNG [India]
BaseBand Version : N7000DDLP4
Kernel : 3.0.15-N7000DDLP8
How do I go about?
Do I need to first downgrade it to GB Stock India
N7000DDLC1---------2.3.6---------2012 March---------N7000ODDLC1-----------India--------------------------------------
OR
Do I downgrade it to SGN_XX_OXA_KJ1_FACTORYFS ???
please guide what to do...
Issue installing
http://forum.xda-developers.com/showthread.php?t=1729331&fb_source=message
Can someone help me. Tried to post a question in that post itself but need to have 10 comments or something.
Anyways, followed the following instruction which said to (i think)
boot into cwm
wipe data/factory reset
wipe cache partition
wipe dalvik cache
then i tried to install the file that i get from mediafire using install zip from sdcard
Find the file (in the download folder is where i saved it) but as soon as it starts to install it, stops ..calling out to an error (something 7)
Could someone see if i did it correctly or there is some other issue?
Currently running broodrom rc5

Help needed - Installing Infamous PAC ROM 4.3

I am getting a fc in setup wizard after installing the Infamous ROM 4.3 "pac_p4_4.3-Infamous_20131017.zip".
Followed below steps:
1. using CWM 6.0.2.7, wipe data/factory reset
2. wipe cache partition
3. wipe delvik cache
4. Flashed Infamous ROM
5. Flashed gaps "gapps-jb-20130813-signed"
6. Reboot
after getting the fc on setup wizard i tried, 1) wiping cache and rebooting 2) reflashing the infamous rom on top again.
both solutions did not work.
I am coming from Ganbarou 4.3 ROM and before that i had Toldo's v8 ICS rom. Ganbarou ROM was working well.
Just wanted to test different JB 4.3 roms.
can someone help me out?
thanks.
Have you tried reflashing gapps?
Sent from my iPhone using Tapatalk - now Free
haven't done that yet. i will try reflashing gaps.
thanks.
ahsenz said:
haven't done that yet. i will try reflashing gaps.
thanks.
Click to expand...
Click to collapse
First you need to update your recovery to 6.0.3.6. You can get it from Droidbasement.
Secondly, before flashing you need to format system under Mounts and Storages in addition to the wipes you mentioned above.
After installation wipe cache and dalvik cache again and then reboot.
The gapps is okay as it is same as mine, and I never had any issues.
Cheers.
Sent from my GT-P7500 using xda app-developers app
John Kester said:
First you need to update your recovery to 6.0.3.6. You can get it from Droidbasement.
Secondly, before flashing you need to format system under Mounts and Storages in addition to the wipes you mentioned above.
After installation wipe cache and dalvik cache again and then reboot.
The gapps is okay as it is same as mine, and I never had any issues.
Cheers.
Sent from my GT-P7500 using xda app-developers app
Click to expand...
Click to collapse
Great advice...
I also always suggest a system format...
I just wanted to add that with the older recovery...it doesn't like 4.3 gapps. You can boot after ROM flash. Then go back to recovery and flash gapps...wipe cache and dalvik before. And that will work also and I've seen gapps cause some weird issues with this device as well as my e4gt..
Or just use twrp...I've had zero issues with flashing anything since switching...
Thanks for the advice. (John and Gil81)
I followed the steps as advised i.e.
1. under Mount and Storage, format system
2. format cache
3. format data
4. flash rom, this time i flashed CM10.2/SGT7 rom.
5. reboot
everything was working smooth, so moved on to
6. flashing gaps
7. reboot and now
8. Enjoying. (restoring apps)
great work from all the developers of 4.3 roms for our device.
have not upgraded the CWM recovery yet, but please advise if it is absolutely necessary to do that. May be i would do it with any future upgrades.
also to get better understanding of the recovery, what is the difference between format data and format sdcard option?
thanks.
ahsenz said:
Thanks for the advice. (John and Gil81)
I followed the steps as advised i.e.
1. under Mount and Storage, format system
2. format cache
3. format data
4. flash rom, this time i flashed CM10.2/SGT7 rom.
5. reboot
everything was working smooth, so moved on to
6. flashing gaps
7. reboot and now
8. Enjoying. (restoring apps)
great work from all the developers of 4.3 roms for our device.
have not upgraded the CWM recovery yet, but please advise if it is absolutely necessary to do that. May be i would do it with any future upgrades.
also to get better understanding of the recovery, what is the difference between format data and format sdcard option?
thanks.
Click to expand...
Click to collapse
Formatting sdcard will wipe everything in your device including the media partition where your user generated data like pictures, videos, downloads etc and also all the files copied to the device from PC. So be careful NOT to format the sdcard.
Formatting data, on the other hand will remove your installed gapps and the associated data. This is necessary when migrating from an older ROM to a newer one that will need you to install different version of gapps that is suitable for the newer ROM. Even when crossing from one ROM to another based on the same version of android, it becomes necessary to format data to get a clean install so the data from the different ROMs do not conflict.
The recovery version, as I understand it, is necessary for the changes to the filing system of 4.3 which is different from 4.2.2. In addition it is also designed to support the multiuser feature of 4.3. I am a single user so I can't attest to how it helps there.
Cheers.
Sent from my GT-P7500 using xda app-developers app

[Q] CyanogenMod 10.1.3 How to install on S2?

I've recently downloaded the Stable version of CM and I don't know how to install it, after installing it will I lose my data? App game datas?
Thanks a lot
True. When you install a new rom you should wipe data. Otherwise it crashes on startup. You can back up the data that
duykhanh187 said:
True. When you install a new rom you should wipe data. Otherwise it crashes on startup. You can back up the data that
Click to expand...
Click to collapse
So how do I install it?
I've looked into the other installation guides but those are for CM10.2 (Andorid 4.3) so I think its different installation method from 10.1, but I cant find a tutorial
C'mon...Read the first page of the CM10 thread & follow the installation instructions. Doesn't take a MENSA member to get it done
If you have used titanium backup root hayz to backup game data. Want to install a new ROM to install it into RECOVERY. If the rom you download it tails. ZIP Remember to wipe data + cache + dakvil before.
My device GT-i9100G
note: im always start all my flash from stock ROM (meaning stock JB 4.1.2)
my usual method, all can be done in the phone, no need odin if youre already stock;
-download all related file, CM10.1.3, CM GApps, Blazing kernel v8 (if you dont want your binary counter to change)...put them in external SD
-boot into recovery, select apply update from external storage, select file blazing kernel v8, let it finish and reboot normally
-then reboot into recovery again and install your Cm10.1.3 and GApps by navigating to your external SD (sorry cant remember the path)
-after finish installing both above file, let it reboot...if bootloop, reboot back into recovery and wipe data, cache and dalvik, and then reboot
now your CM10.1.3 is ready~
-hit thanks if my post helps you-

How to correctly swtich ROM's

Hi there,
I may be being stupid here I want to move from Lineage OS to crDroid. Im currently on the latest 01/01/2019 LOS build, with 8.12.24 vendor firmware. I didnt flash the disable encryption patch so my device is encrypted. Im guessing I need to remove any security off the lock screen? Im using the unofficial TWRP build - 12/12/2018.
So to make the switch, do i need to wipe my data, or can I migrate over?
And when I go to flash, which wipes do I need to do before installing the ROM?
Im just worried about flashing and then locking my phone with the encryption because I've missed a step This is my first phone that uses android 9.0, and im not used to the forced encryption stuff.
If someone could give me a lil list of steps, that would be much appreciated!
Thanks!
That I do is:
-wipe system, data, cache, Dalvik
-flash new rom, flash gapps
**Flash any custom kernel if you want
Now here is the differences
1) if I want keep the encryption but format the internal storage I just do a factory reset or format data or internal storage, all are the same and reboot in the system
2) if I don't want keep the encryption, I reboot into recovery, later format data, then flash the zip to keep the phone unencrypted (FDE? I don't remember the name exactly but it is in a post on the guide section), and last flash magisk, then reboot system
3) if you have the phone without encryption and you want keep it in that way, just do the wipe to the system,data,cache,dalvik then flash system, gapps, any kernel at your choice, magisk and reboot into system
PD: remember if you flash a vendor zip, the phone will be encrypt
PS:I hope that I don't get wrong in something

Can't mount system, Lineage 16

running on 4.2.2 stock rom GT-i9060 rooted, twrp 3.02 and unlocked bootloader with ez-unlock (fastboot isnt working)
steps I used to flash the ROM:
1. flashing stock rom and getting root
2. enable USB debugging and unlocking bootloader
3. wiping cache, dalvik cache and data, 2nd time tried wiping cache, dalvik cache, data and system, 3rd time wiped cache, dalvik cache, data and added format script to update-script before mounting and extracting files (internal storage was never included because it doesn't make a difference)
4. flashing both of the ROM and gapps
the rom is made for my phone and i'm certain of it if i'm gonna be asked about it (GT-i9060 Baffinlite)
5. Wiping dalvik cache, cache and data
been more than a week working on flashing this rom but all goes back to the bottom
tried removing the assert line
added execute permissions to the zip, didn't make a difference
recovery version is 3.0.2 and tried twrp 2.7, twrp 2.8 and cwm 5.06 but the one the rom developer asked to use wasn't booting but kept powering the phone off after showing device logo, it's on the attachements
after getting error 7 couple of times without editing anything then i tried editing updater-script myself by changing the mount order but i guess the previous is the one used on every lineage rom so that failed too
there's a cm11 rom for the dvice working but full of bugs so what i'm not getting is why the lineage 16 one isn't mounting at all although the other one do
"detected filesystem ex4 for /dev/block/mmcblk0p17
mount: failed to mount /dev/block/mmcblk0p17 at /system"
that comes right after the extracting packages script (system.new.dat.br
ticking the system on twrp gives on log: can't mount system (invalid argument)
there is enough space on system for the rom too
i'm also sure that the system block is "mmcblk0p17" because it worked with the other ROM
the gapps mentioned that the android veriob I am using after installing the ROM is 5.1 (SDK 22) not 9.0 but I ignored it after checking the build.prop inside the system img
im ready for testing if there's a dev getting a solution
I know there would be lots of bugs by running pie on that phone because of the specifications but im okay with it
if someone could fix the mounting ROM bug or tell me if there is something i missed about flashing
Rom by knuxfanwin8
(androidfilehost.com/?fid=6006931924117889489)
Recovery by made_in_androland
(androidfilehost.com/?fid=457095661767119752)
NOT-Working recovery by knuxfanwin8
(androidfilehost.com/?fid=6006931924117902394)
I have the same problem, please give we a solution!
---------- Post added at 10:19 AM ---------- Previous post was at 10:10 AM ----------
Azureus. said:
running on 4.2.2 stock rom GT-i9060 rooted, twrp 3.02 and unlocked bootloader with ez-unlock (fastboot isnt working)
steps I used to flash the ROM:
1. flashing stock rom and getting root
2. enable USB debugging and unlocking bootloader
3. wiping cache, dalvik cache and data, 2nd time tried wiping cache, dalvik cache, data and system, 3rd time wiped cache, dalvik cache, data and added format script to update-script before mounting and extracting files (internal storage was never included because it doesn't make a difference)
4. flashing both of the ROM and gapps
the rom is made for my phone and i'm certain of it if i'm gonna be asked about it (GT-i9060 Baffinlite)
5. Wiping dalvik cache, cache and data
been more than a week working on flashing this rom but all goes back to the bottom
tried removing the assert line
added execute permissions to the zip, didn't make a difference
recovery version is 3.0.2 and tried twrp 2.7, twrp 2.8 and cwm 5.06 but the one the rom developer asked to use wasn't booting but kept powering the phone off after showing device logo, it's on the attachements
after getting error 7 couple of times without editing anything then i tried editing updater-script myself by changing the mount order but i guess the previous is the one used on every lineage rom so that failed too
there's a cm11 rom for the dvice working but full of bugs so what i'm not getting is why the lineage 16 one isn't mounting at all although the other one do
"detected filesystem ex4 for /dev/block/mmcblk0p17
mount: failed to mount /dev/block/mmcblk0p17 at /system"
that comes right after the extracting packages script (system.new.dat.br
ticking the system on twrp gives on log: can't mount system (invalid argument)
there is enough space on system for the rom too
i'm also sure that the system block is "mmcblk0p17" because it worked with the other ROM
the gapps mentioned that the android veriob I am using after installing the ROM is 5.1 (SDK 22) not 9.0 but I ignored it after checking the build.prop inside the system img
im ready for testing if there's a dev getting a solution
I know there would be lots of bugs by running pie on that phone because of the specifications but im okay with it
if someone could fix the mounting ROM bug or tell me if there is something i missed about flashing
Rom by knuxfanwin8
(androidfilehost.com/?fid=6006931924117889489)
Recovery by made_in_androland
(androidfilehost.com/?fid=457095661767119752)
NOT-Working recovery by knuxfanwin8
(androidfilehost.com/?fid=6006931924117902394)
Click to expand...
Click to collapse
I have The same problem, please help me.
I have the galaxy grand neo and i try to install lineage os 16.0 but not work, i have read in a thread that the problem will be the bootloader (its version is too old)
In the post it was written to update the bootloader but for the galaxy grand neo the only one verison of android is 4.2.2.
Maybe i'm wrong, i'm not a pro but i can understand somethings.
Hey any one there?????¿?
Please post a quick reply to help three of us from this drastical problem..........??????
Error 7 occurs when there is not enough space for flashing gapps or rom in system. Can you resize system partition from twrp?
kouseralamin said:
Error 7 occurs when there is not enough space for flashing gapps or rom in system. Can you resize system partition from twrp?
Click to expand...
Click to collapse
Tried but nothing
kouseralamin said:
Error 7 occurs when there is not enough space for flashing gapps or rom in system. Can you resize system partition from twrp?
Click to expand...
Click to collapse
Androcomtweaker said:
Tried but nothing
Click to expand...
Click to collapse
TWRP doesn't give you option Resize Partition but only option Resize File System - what is nothing else than expanding the related FS to reclaim wasted space.

Categories

Resources