[Q] Wiped System Partition need help - Sony Xperia M

Hey guys,
I installed Cyanogenmod on my Xperia M from this thread: http://forum.xda-developers.com/showthread.php?t=2584956
After that I installed Google Apps package. But I accidentally messed something up so I wiped the /system, /cache, /data via CWM recovery and re flashed the ROM. It booted up correctly, but I want to know if my procedure was incorrect or I needed to flash 4.3 firmware first before flashing Cyanogenmod to my device? Its working fine now. I just want to know if Cyanogenmod is independent or if it needs /system from 4.3 stock firmware.
Also, I want to know how to wipe my INTERNAL SD card, the card which isn't removable?
Please reply ASAP.

I found the solution.

What is the solution??
tyus2 said:
I found the solution.
Click to expand...
Click to collapse
can you please tell us in detail what the solution is??

Well, it isn't as complicated as it seems. It turned out I needed to be on stock 4.3 firmware with bootloader unlocked so I would have the correct baseband for Cyanogenmod.
After that, I wiped my /system, /cache, and /data. Then I flashed the Cyanogenmod for my device via the zips and then flashed the GApps from Paranoid Android thread on XDA.
Booted up, first time boot took up long like 4 minutes, everything works fine now, except for the battery. It merely lasts 14 hours, considering it used to last 26-28 hours on official firmware.

Related

[Q] Elk759's JB Rom not booting

Hi to all !
Pardon me if the question has already been asked.
I have actually the 0.27 of Elk759's JB Rom installed on my Desire (S-On, no Sd-Ext or whatsoever). I wanted today to install 0.34 every time I get stuck on boot animation. Not even a reboot. Just stay on boot animation. And I had the same problem on versions after 0.27.
I have made all the wipes twice (Data, cache, dalvik) to be sure, but the always stay on boot.
Have I forgotten any requirements ?
Thanks for all !
Monkeypox95 said:
Hi to all !
Pardon me if the question has already been asked.
I have actually the 0.27 of Elk759's JB Rom installed on my Desire (S-On, no Sd-Ext or whatsoever). I wanted today to install 0.34 every time I get stuck on boot animation. Not even a reboot. Just stay on boot animation. And I had the same problem on versions after 0.27.
I have made all the wipes twice (Data, cache, dalvik) to be sure, but the always stay on boot.
Have I forgotten any requirements ?
Thanks for all !
Click to expand...
Click to collapse
May be have you non stock hboot?
pdminty said:
May be have you non stock hboot?
Click to expand...
Click to collapse
he is s-on, so must be on stock hboot
@Monkeypox95, in the OP of the thread it says, YOU NEED GAPPS TO USE THIS ROM, have you flashed them straight after flashing the rom.zip?
also, if you start to install apps, you'll run out of space quite quickly without sd-ext partition. i recommend s-off, install 4ext recovery, backup sd card and partition using 4ext. enable a2sd using instructions in first post.
eddiehk6 said:
he is s-on, so must be on stock hboot
@Monkeypox95, in the OP of the thread it says, YOU NEED GAPPS TO USE THIS ROM, have you flashed them straight after flashing the rom.zip?
also, if you start to install apps, you'll run out of space quite quickly without sd-ext partition. i recommend s-off, install 4ext recovery, backup sd card and partition using 4ext. enable a2sd using instructions in first post.
Click to expand...
Click to collapse
I'm sorry, I forgot to mention that I am on stock hboot AND that I have flashed the Gapps straight after having flashed the rom.
Hi all,
I am new here and new to flashing phones with new rom's. I rooted my desire with the package: revolutionary-0.4pre4.zip
that is successfully installed. I can boot in to the recovery mode. After that i made a backup and did a full whipe. I installed the 0.34 rom (without a2sd). And directly after that (no reboot in between) i installed gapps using the link provided in the dev thread.
I have the same result, phone hangs on the CM bootscreen.
I will now try the latest update with a2sd and will let you know if i have a better result.
Thnx in advance!
~Spud
EDIT1: Got no luck with the a2sd version.
as mentioned above i think i should look at the hboot for this problem.
I am currently on hboot 6.93.1002 S-off.. is that bad for this rom?
EDIT2: So,... after doing some more reading i reformatted the SD card. with the largest available size, for swap and data. After a reboot and hanging at the bootscreen for a couple of minutes the phone has booted!
Hopes this might come in handy for some of you folks.
Thank you Elk759 its running very smooth at this moment. Did not really expect this performance from this old phone

[Q] Help! Installed AOKP over Encrypted CM11!!!

Hi All -
First time posting! I am very new to this and I'm in dire need of help! I will write as many details of my situation as I can!
So, I have been running a recent nightly of Cyanogenmod 11 on my d2att/i747 Samsung Galaxy S3 for the past few weeks. I decided to try out the encryption feature (first mistake). I noticed that things weren't running smoothly as they were before and decided to try flashing a new ROM (latest AOKP nightly). NOW, I am in trouble.
First, before installing AOKP, I loaded the ROM and gapps to my external SD. I then did these steps: wipe data/factory reset, then
format /data, then format /system, finally Wipe Dalvik Cache. I then installed AOKP and gapps from the external SD. Halfway through the install I noticed on the screen "E: Can't mount SDCard". However, the install appeared to go through well so I thought it might have been in error.
I then rebooted as per normal, at which point I was shocked to still see the cyanogenmod encryption unlock screen! I plugged in the password, and then watched the AOKP boot screen perpetually load. It never did fully load.
Would any of you be able to help me resurrect my phone? Thank you so much in advance!!!
What version of the AT&T ROM were you running before installing CM11?
audit13 said:
What version of the AT&T ROM were you running before installing CM11?
Click to expand...
Click to collapse
That was ages ago. MAYBE 4.1.1.
I Think I may have to try to do a stock recovery...
As long as you were not on 4.3, flashing via Odin should restore the phone to complete stock everything (ROM, Radio, bootloader).
audit13 said:
As long as you were not on 4.3, flashing via Odin should restore the phone to complete stock everything (ROM, Radio, bootloader).
Click to expand...
Click to collapse
It doesn't seem to be working when I try to flash through ODIN. It says "succeed 0/failed 0". Could that be because of running CM11 (android 4.2.2)? Or the encryption?
Possibly. You're flashing a stock AT&T rom from samfirmware?
audit13 said:
Possibly. You're flashing a stock AT&T rom from samfirmware?
Click to expand...
Click to collapse
not samfirmware. i'll try downloading one from them.
Samfirmware has the official ROM releases.
Link here: http://www.sammobile.com/firmwares/1/?model=SGH-I747&pcode=ATT#firmware
ARGH. So, in theory ODIN worked. However, after booting up again, I'm getting the same request to enter a code to get past encryption. Even better, that code is no longer working!!!
Any ideas?
doorstop25 said:
ARGH. So, in theory ODIN worked. However, after booting up again, I'm getting the same request to enter a code to get past encryption. Even better, that code is no longer working!!!
Any ideas?
Click to expand...
Click to collapse
I take it back!!! I did another factory wipe and everything turned on!!! WHOOO!!! Thanks for the help!

Several Qs: 0 folder under sdcard\download\, soft bricked, counter...etc

My I747 is currently running Carbon Rom nightly 20131102 (4.3.1), it's quite old and I want to upgrade to 4.4.
So last night I nandroid backup , format system, data, flashed Carbon KK on it, then gapps, data, cache, delvik, reboot. But it stayed at the CM alien. I reflashed several times but still stuck at there. But I can nandroid back so I'm kind of fine now. But anyone know why?
Second, I notice my \0\ folder is under sdcard\download\0\ than usual sdcard\0\, I must have done something wrong when I first flash the carbon but I don't know what it is. I usually put my .zip in download, could that be why? Could that cause the bricking I have with KK?
Last, I know there's a flash counter and when I first root/flash last year, I went thru many things to avoid that&IMEI, instead of directly flashing a recovery. I think that could be the source of the problems above??? Now 1 year is up and my warranty is already over so I don't have to worry about the counter anymore. If I want to redo everything, and have to noobiest/simpliest method to flash to KK, what should I do?
Sorry if I lack any essential information. I'd be happy to find it to help.
Did you update to the latest CWM before flashing the ROM? Is your current bootloader supported by the ROM?
Not the latest but 6.0.4.3
I'll update it to 6.0.4.7 and try again.
Unfortunately I don't know if my bootloader is supported. I don't really know how to find mine.
I would update to the latest CWM and then try to flash a 4.4.2 custom ROM. If it doesn't install, it should generate an error message.
Most custom ROMs will look for a particular bootloader. If the bootloader is not found, CWM will give you get prop errors.
audit13 said:
I would update to the latest CWM and then try to flash a 4.4.2 custom ROM. If it doesn't install, it should generate an error message.
Most custom ROMs will look for a particular bootloader. If the bootloader is not found, CWM will give you get prop errors.
Click to expand...
Click to collapse
Thanks, I'll try when I get home.
I installed the ROM fine last night without any error. So I believe the bootloader is supported then.
afyaff said:
Thanks, I'll try when I get home.
I installed the ROM fine last night without any error. So I believe the bootloader is supported then.
Click to expand...
Click to collapse
To be sure, look at the bootloaders mentioned in the ROM's updater script.

Anyone with a working CM11 on Z1c ?

Hello
I unlocked my bootloader with sony provided key and I followed the tutorial here http://wiki.cyanogenmod.org/w/Install_CM_for_amami to install CM11 M8 snapshot.
Since I did everything as stated, I can't figure out why I can't stop a bootloop to happen.
When I tried to reflash I noticed that the wipe of DATA apparently fails because CWM can't mount data.
Previously I used the duallocked recovery hack and I had a stock rom rooted.
Could it be because I flashed a 4.4.3 gapps file and cm11 M8 is 4.4.4 ??
Anyway, apart from reflashing a stock rom, what can I do ??
Thanks for answers
Nico.
nico1375 said:
Hello
I unlocked my bootloader with sony provided key and I followed the tutorial here http://wiki.cyanogenmod.org/w/Install_CM_for_amami to install CM11 M8 snapshot.
Since I did everything as stated, I can't figure out why I can't stop a bootloop to happen.
When I tried to reflash I noticed that the wipe of DATA apparently fails because CWM can't mount data.
Previously I used the duallocked recovery hack and I had a stock rom rooted.
Could it be because I flashed a 4.4.3 gapps file and cm11 M8 is 4.4.4 ??
Anyway, apart from reflashing a stock rom, what can I do ??
Thanks for answers
Nico.
Click to expand...
Click to collapse
I think I read some users reports that CyannogenMod M8 isn't working well for amami,
but all older releases were working fine.
Yes, accepted the M8 is not too good ....
Sent from my iPad using Tapatalk HD
nico1375 said:
Hello
I unlocked my bootloader with sony provided key and I followed the tutorial here http://wiki.cyanogenmod.org/w/Install_CM_for_amami to install CM11 M8 snapshot.
Since I did everything as stated, I can't figure out why I can't stop a bootloop to happen.
When I tried to reflash I noticed that the wipe of DATA apparently fails because CWM can't mount data.
Previously I used the duallocked recovery hack and I had a stock rom rooted.
Could it be because I flashed a 4.4.3 gapps file and cm11 M8 is 4.4.4 ??
Anyway, apart from reflashing a stock rom, what can I do ??
Thanks for answers
Nico.
Click to expand...
Click to collapse
After unlocking bootloader you need to wipe data/media, in order to format the internal storage which is wiped in the unlocking procedure. And yeah, go with nightlies for now I'd say. Working fine for me!
Rekoil said:
After unlocking bootloader you need to wipe data/media, in order to format the internal storage which is wiped in the unlocking procedure. And yeah, go with nightlies for now I'd say. Working fine for me!
Click to expand...
Click to collapse
I managed to reflash the dual recovery from NUT, start TWRP and repair data partition, it seem to work well now
Thx
This is development section.. You should post it in Q & A section.. @mods please move this thread to correct section..
Sent from my Xperia Z1 Compact (D5503)

[Solved]Nexus won't boot after ROM and other things

Hello guys, I've searched a little and didn't find any posts that could help me specifically for the Galaxy Nexus.
I've flashed my phone a long time ago and have been using Paranoid Android for probably over a year.
The problem is, my cellphone was really really slow. So I decided to try a new ROM and re-flash it. And So I did.
I've tried flashing this Full_Auto R11 kernel then the CyanogenMod 12 and finally GAPPS.
I was getting error status 6 on Clockwork mod on gapps, but eventually got around it. But it didn't install play store, I've tried manually adding but it didn't work.
So I went for another 5.0 ROM (I'm really interested in getting android 5.0). Wiped all the data, all the cache, installed everything and rebooted.
Bam! Infinite booting screen.
No, I didn't create a nandroid backup because I'm really dumb.
So, I need your help. What I want to do is to get my phone working again with a 5.0 ROM (if possible).
I can boot into ClockWork Recovery just fine, if that helps.
Thank you for the attention.
I would recommend to install latest full factory package from Google.
Then you will start with everything stock, so flash latest TWRP recovery via fastboot (CWM is no longer supported, so error 6 when installing new Lollipop Google Apps appears).
Then in TWRP, do a factory reset, wipe /cache and /system partitions.
Then you can install your Lollipop ROM (over ADB or by pushing ROM package to emulated sdcard).
After this, install latest Full_Auto kernel.
At the end, install Pico Google Apps.
You must install the Pico version, because our /system parition is too small to handle Lollipop with all Google Apps included.
This should work for you, and you will have fully working Lollipop on your Galaxy Nexus
P.S: If you intall the AOSP Lollipop ROM by @freshgiammi and you miss root access, install latest SuperSU flashable zip.
Thank you!
Thank you man!
I've ran into some troubles but managed to do everythings correctly =)
This post can be locked up now.
Thanks again for the reply, LamarrCZ!!

Categories

Resources